Property | Description |
|---|---|
Name | Name of the service. The name is not case sensitive and must be unique within the domain. It cannot exceed 128 characters or begin with @. It also cannot contain spaces or the following special characters: ` ~ % ^ * + = { } \ ; : ' " / ? . , < > | ! ( ) ] [ You cannot change the name of the service after you create it. |
Description | Description of the service. The description cannot exceed 765 characters. |
License | License object that allows use of the service. |
Node | Node on which the service runs. |
Backup Nodes | If your license includes high availability, nodes on which the service can run if the primary node is unavailable. |
Property | Description |
|---|---|
Database Type | The type of database. |
Username | The database user name for the Model repository. |
Password | Repository database password for the database user. |
JDBC Connect String | The JDBC connection string to connect to the Model repository database. Use the following syntax for each supported database:
To connect to Oracle using Oracle Connection Manager, use the following connection string: jdbc:Informatica:oracle:TNSNamesFile=<fully qualified path to the tnsnames.ora file>;TNSServerName=<TNS server name>; |
Secure JDBC Parameters | If the Model repository database is secured with the SSL protocol, you must enter the secure database parameters. Enter the parameters as name=value pairs separated by semicolon characters (;). For example: param1=value1;param2=value2 |
Dialect | The SQL dialect for a particular database. The dialect maps java objects to database objects. For example: org.hibernate.dialect.Oracle9Dialect |
Driver | The Data Direct driver used to connect to the database. For example: com.informatica.jdbc.oracle.OracleDriver |
Database Schema | The schema name for a particular database. |
Database Tablespace | The tablespace name for a particular database. For a multi-partition IBM Db2 database, the tablespace must span a single node and a single partition. |
Secure Database Parameter | Description |
|---|---|
EncryptionMethod | Required. Indicates whether data is encrypted when transmitted over the network. This parameter must be set to SSL. |
ValidateServerCertificate | Optional. Indicates whether Informatica validates the certificate that the database server sends. If this parameter is set to True, Informatica validates the certificate that the database server sends. If you specify the HostNameInCertificate parameter, Informatica also validates the host name in the certificate. If this parameter is set to False, Informatica does not validate the certificate that the database server sends. Informatica ignores any truststore information that you specify. |
HostNameInCertificate | Optional. Host name of the machine that hosts the secure database. If you specify a host name, Informatica validates the host name included in the connection string against the host name in the SSL certificate. |
cryptoProtocolVersion | Required. Specifies the cryptographic protocol to use to connect to a secure database. You can set the parameter to cryptoProtocolVersion=TLSv1.1 or cryptoProtocolVersion=TLSv1.2 based on the cryptographic protocol used by the database server. |
TrustStore | Required. Path and file name of the truststore file that contains the SSL certificate for the database. If you do not include the path for the truststore file, Informatica looks for the file in the following default directory: <Informatica installation directory>/tomcat/bin |
TrustStorePassword | Required. Password for the truststore file for the secure database. |
Property | Description |
|---|---|
Search Analyzer | Fully qualified Java class name of the search analyzer. By default, the Model Repository Service uses the following search analyzer for English: com.informatica.repository.service.provider.search.analysis.MMStandardAnalyzer You can specify the following Java class name of the search analyzer for Chinese, Japanese and Korean languages: org.apache.lucene.analysis.cjk.CJKAnalyzer Or, you can create and specify a custom search analyzer. |
Search Analyzer Factory | Fully qualified Java class name of the factory class if you used a factory class when you created a custom search analyzer. If you use a custom search analyzer, enter the name of either the search analyzer class or the search analyzer factory class. |
Property | Description |
|---|---|
Maximum Heap Size | Amount of RAM allocated to the Java Virtual Machine (JVM) that runs the Model Repository Service. Use this property to increase the performance. Append one of the following letters to the value to specify the units:
Default value is1024m. |
JVM Command Line Options | Java Virtual Machine (JVM) command line options to run Java-based programs. When you configure the JVM options, you must set the Java SDK classpath, Java SDK minimum memory, and Java SDK maximum memory properties. You must set the following JVM command line options:
Note: To use Git version control system in AIX operating system, append -Dhttps.protocols=TLSv1.2 to the existing options. |
Property | Description |
|---|---|
Enable Cache | Enables the Model Repository Service to store Model repository objects in cache memory. To apply changes, restart the Model Repository Service. |
Cache JVM Options | JVM options for the Model Repository Service cache. To configure the amount of memory allocated to cache, configure the maximum heap size. This field must include the maximum heap size, specified by the -Xmx option. The default value and minimum value for the maximum heap size is -Xmx128m. The options you configure apply when Model Repository Service cache is enabled. To apply changes, restart the Model Repository Service. The options you configure in this field do not apply to the JVM that runs the Model Repository Service. |
Property | Description |
|---|---|
Version control system type | The supported version control system that you want to connect to. You can choose Perforce, SVN, or Git. |
Host | For Perforce, enter the URL, IP address, or host name of the machine where the Perforce version control system runs. This option is not available for SVN and Git version control system. |
URL | For SVN, enter the URL of the SVN version control system repository or the subfolder. For Git, enter the URL for the remote Git repository. This option is not available for Perforce version control system. |
Port | Required. For SVN and Perforce, enter the port number that the version control system host uses to listen for requests from the Model Repository Service. This option is not available for Git version control system. |
Path to repository objects | For Perforce, enter the path to the root directory of the version control system that stores the Model repository objects. Note: When you complete editing Versioning properties, the Model repository connects to the version control system and generates the specified directory if the directory does not exist yet. Only one Model Repository Service can use this directory. For Perforce, use the syntax: //directory/path where directory is the Perforce directory root, and path is the remainder of the path to the root directory of Model repository objects. Example: //depot/Informatica/repository_copy Note: If you change the depot path after you synchronize the Model repository with the version control system, version history for objects in the Model repository is lost. This option is not available for SVN and Git version control system. |
Username | For Perforce, SVN, or Git, enter the user account for the version control system user. For SVN, the account type must be a Subversion user and not Windows login or Linux login user and must have write permissions on the version control system. For Perforce, the account type for a Perforce version control system must be a Standard user. For Git, enter the user name for the remote Git repository. |
Password | Password for the version control system user. For Git, enter the password of the remote Git repository user. |
VCS Local Repository Path | For Git, enter the file path of the local Git repository. The directory must be accessible from the machine on which you installed the Model Repository Service and from other nodes if you configured high availability for Model Repository Service. |