Application Service Guide > Model Repository Service > Properties for the Model Repository Service

Properties for the Model Repository Service

Use the Administrator tool to configure the following service properties:

•General properties
•Repository database properties
•Search properties
•Advanced properties
•Cache properties
•Versioning properties
•Custom properties

If you update any of the properties, you must restart the Model Repository Service for the modifications to take effect.

If you modify the repository database for a Model Repository Service that is configured for monitoring, then you must restart the domain. If you do not restart the domain after you modify the repository database, then the Model Repository Service does not resume statistics collection.

General Properties for the Model Repository Service

The following table describes the general properties for the service:

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.

Repository Database Properties for the Model Repository Service

The following table describes the database properties for the Model repository:

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 used to connect to the Model repository database. Use the following JDBC connect string syntax for each supported database: - IBM DB2. jdbc:informatica:db2://<host_name>:<port_number>;DatabaseName=<database_name>;BatchPerformanceWorkaround=true;DynamicSections=3000 - Microsoft SQL Server that uses the default instance. jdbc:informatica:sqlserver://<host_name>:<port_number>;DatabaseName=<database_name>;SnapshotSerializable=true - Microsoft SQL Server that uses a named instance. jdbc:informatica:sqlserver://<host_name>\<named_instance_name>;DatabaseName=<database_name>;SnapshotSerializable=true - Oracle. jdbc:informatica:oracle://<host_name>:<port_number>;SID=<database_name>;MaxPooledStatements=20;CatalogOptions=0;BatchPerformanceWorkaround=true
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.

JDBC Parameters for Secure Databases

If the Model repository database is secured with the SSL protocol, you must enter the secure database parameters in the Secure JDBC Parameters field.

Enter the parameters as name=value pairs separated by semicolon characters (;). For example:

param1=value1;param2=value2

Enter the following secure database parameters:

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.

Note: Informatica appends the secure JDBC parameters to the JDBC connection string. If you include the secure JDBC parameters directly in the connection string, do not enter any parameter in the Secure JDBC Parameters field.

Search Properties for the Model Repository Service

The following table describes the search properties for the Model Repository Service:

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

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.

Advanced Properties for the Model Repository Service

The following table describes the Advanced properties for the Model Repository Service:

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: - b for bytes. - k for kilobytes. - m for megabytes. - g for gigabytes. Default is 768 megabytes.
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: - Xms. Minimum heap size. Default value is 256 m. - MaxPermSize. Maximum permanent generation size. Default is 128 m. - Dfile.encoding. File encoding. Default is UTF-8.

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:

- b for bytes.
- k for kilobytes.
- m for megabytes.
- g for gigabytes.

Default is 768 megabytes.

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:

- Xms. Minimum heap size. Default value is 256 m.
- MaxPermSize. Maximum permanent generation size. Default is 128 m.
- Dfile.encoding. File encoding. Default is UTF-8.

Cache Properties for the Model Repository Service

The following table describes the cache properties for the Model Repository Service:

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

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.

Versioning Properties for the Model Repository Service

To connect to a version control system, you must configure versioning properties in the Model Repository Service.

You can configure versioning properties for the Perforce or Subversion version control systems. Subversion is abbreviated "SVN".

Some of the properties refer to the version control system host machine and user accounts. Contact the version control system administrator for this information.

After you configure versioning properties, you restart the Model repository, and then run infacmd mrs PopulateVCS to synchronize Model repository contents to the version control system.

Note: While the Model repository synchronizes its contents with the version control system for the first time, the Model repository is unavailable. Model repository users must close all editable objects before the process starts.

The following table describes the versioning properties for 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 or SVN.
Host	The URL, IP address, or host name of the machine where the Perforce version control system runs. When you configure SVN as the version control system, this option is not available.
URL	The URL of the SVN version control system repository. When you configure Perforce as the version control system, this option is not available.
Port	Required. Port number that the version control system host uses to listen for requests from the Model Repository Service.
Path to repository objects	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 When you configure SVN as the version control system, this option is not available. 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.
Username	User account for the version control system user. This account must have write permissions on the version control system. After you configure the connection with this single version control system user and password, all Model repository users use this account. For the Perforce version control system, the account type must be a Standard user.
Password	Password for the version control system user.

Custom Properties for the Model Repository Service

Configure custom properties that are unique to specific environments.

You might need to apply custom properties in special cases. When you define a custom property, enter the property name and an initial value. Define custom properties only at the request of Informatica Global Customer Support.