What's New and Changed > Part V: Version 10.2.1 > 10.2.1 What's New > Application Services
  

Application Services

This section describes new application service features in version 10.2.1.

Content Management Service

Effective in version 10.2.1, you can optionally specify a schema to identify reference tables in the reference data database as a property on the Content Management Service.
To specify the schema, use the Reference Data Location Schema property on the Content Management Service in Informatica Administrator. Or, run the infacmd cms updateServiceOptions command with the DataServiceOptions.RefDataLocationSchema option.
If you do not specify a schema for reference tables on the Content Management Service, the service uses the schema that the database connection specifies. If you do not explicitly set a schema on the database connection, the Content Management Service uses the default database schema.
Note: Establish the database and the schema that the Content Management Service will use for reference data before you create a managed reference table.
For more information, see the "Content Management Service" chapter in the Informatica 10.2.1 Application Service Guide and the "infacmd cms Command Reference" chapter in the Informatica 10.2.1 Command Reference.

Data Integration Service

Effective in version 10.2.1, the Data Integration Service properties include a new execution option.
JDK Home Directory
The JDK installation directory on the machine that runs the Data Integration Service. Required to run Sqoop mappings or mass ingestion specifications that use a Sqoop connection on the Spark engine, or to process a Java transformation on the Spark engine. Default is blank.

Mass Ingestion Service

Effective in version 10.2.1, you can create a Mass Ingestion Service. The Mass Ingestion Service is an application service in the Informatica domain that manages mass ingestion specifications. You configure the mass ingestion specifications in the Mass Ingestion tool to ingest large amounts of data from a relational source to a Hive or HDFS target.
To manage mass ingestion specifications, the Mass Ingestion Service performs the following tasks:
For more information on the Mass Ingestion Service, see the "Mass Ingestion Service" chapter in the Informatica 10.2.1 Application Service Guide.

Metadata Access Service

Effective in version 10.2.1, you can create a Metadata Access Service. The Metadata Access Service is an application service that allows the Developer tool to access Hadoop connection information to import and preview metadata. When you import an object from a Hadoop cluster, the following adapters use Metadata Access Service to extract the object metadata at design time:
For more information, see the "Metadata Access Service" chapter in the Informatica 10.2.1 Application Service Guide.

Model Repository Service

Azure SQL Database as Model Repository

Effective in version 10.2.1, you can use the Azure SQL database as the Model repository.
For more information, see the "Model Repository Service" chapter in the Informatica 10.2.1 Application Service Guide.

Git Version Control System

Effective in version 10.2.1, you can integrate the Model repository with the Git version control system. Git is a distributed version control system. When you check out and check in an object, a copy of the version is saved to the local repository and to the Git server. If the Git server goes down, the local repository retains all the versions of the object. To use the Git version control system, enter the URL of the global repository for Git in the URL field, login credentials for the global repository in the Username and Password fields, and the path of the local repository for the Model Repository Service in the VCS Local Repository Path field.
For more information, see the "Model Repository Service" chapter in the Informatica 10.2.1 Application Service Guide.