Enables the Model Repository Service to store Model repository objects in cache memory. To apply changes, restart the Model Repository Service.

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.

Required. Account for the repository database. Set up this account using the database client.

Required. Repository database password for the database user.

Optional. The schema name for a particular database.

Required for a DB2 database only. When you configure a tablespace name, the Model Repository Service creates all repository tables in the same tablespace. You cannot use spaces in the tablespace name.

For a multi-partition IBM DB2 database, the tablespace must span a single node and a single partition.

Required. Database types include:

db2
oracle
mssqlserver
sybase

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
Azure SQL Server.
jdbc:informatica:sqlserver://<host_name>:<port_number>;DatabaseName=<database_name>;SnapshotSerializable=true; SnapshotSerializable=true;EncryptionMethod=SSL;HostNameInCertificate=*.<hostnameincertificate>;ValidateServerCertificate=true
Oracle.
jdbc:informatica:oracle://<host_name>:<port_number>;SID=<database_name>;MaxPooledStatements=20;CatalogOptions=0;BatchPerformanceWorkaround=true

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:

The SQL dialect for a particular database. The dialect maps java objects to database objects.

For example:

The Data Direct driver used to connect to the database.

For example:

Fully qualified Java class name of the search analyzer.

By default, the Model Repository Service uses the following search analyzer for English:

You can specify the following Java class name of the search analyzer for Chinese, Japanese and Korean languages:

Or, you can create and specify a custom search analyzer.

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.

Required to configure versioning properties for the Model repository on Perforce.

The URL, IP address, or host name of the machine where the Perforce version control system runs.

Do not use this option when you configure SVN or Git as the version control system.

Required to configure versioning properties for the Model repository on SVN and Git.

URL of the Subversion repository. For example:

VCS.URL=https://myserver.company.com/svn/

Do not use this option when you configure Perforce as the version control system.

Required to configure versioning properties for the Model repository.

Port number that the version control system host uses to listen for packets from the Model repository.

Required to configure versioning properties for the Model repository.

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 connect to the version control system through this account.

For the Perforce version control system, the account type must be a Standard user.

Required to configure versioning properties for the Model repository.

Password for the version control system user.

Required to configure versioning properties for the Model repository.

The supported version control system that you want to connect to. You can choose Perforce, SVN, or Git.

Required to configure versioning properties for the Model repository with Perforce.

Path to the root directory of the version control system copy of Model repository objects. 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

Do not use this option when you configure SVN or Git as the version control system.