Installation for Data Engineering

10.5.3
- 10.5.7
- 10.5.6
- 10.5.5.1
- 10.5.5
- 10.5.4
- 10.5.2
- 10.4.1
- 10.4.0

Back Next

Create the Model Repository Service

Use the service creation wizard in the Administrator tool to create the service.

In the Administrator tool, click the

Manage

tab.

Click

Actions

New

Model Repository Service

The

New Model Repository Service

dialog box appears.

On the

New Model Repository Service - Step 1 of 2

page, enter the following properties:

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: ` ~ % ^ * + = { } \ ; : ' " / ? . , < > \| ! ( ) ] [
Description	Description of the service. The description cannot exceed 765 characters.
Location	Domain and folder where the service is created. Click Browse to choose a different folder. You can move the service after you create it.
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.

Click

The

New Model Repository Service - Step 2 of 2

page appears.

Enter the following properties for the Model repository database:

Property	Description
Database Type	The type of the repository database.
Username	The database user name for the repository. You can enter the Windows NT user name for trusted connection for Microsoft SQL Server.
Password	Repository database password for the database user. You can enter the Windows NT password for trusted connection for Microsoft SQL Server.
Database Schema	Available for Microsoft SQL Server and PostgreSQL. Name of the schema that will contain Model repository tables.
Database Tablespace	Available for IBM DB2. Name of the tablespace in which to create the tables. For a multi-partition IBM DB2 database, the tablespace must span a single node and a single partition.

Enter the JDBC connection string that the service uses to connect to the Model repository database.

Use the following syntax for the connection string for the selected database type:

Database Type	Connection String Syntax
IBM DB2	"jdbc:informatica:db2://<host name>:<port number>;DatabaseName=<database name>;BatchPerformanceWorkaround=true;DynamicSections=3000"
Microsoft SQL Server	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" Microsoft Azure. jdbc:informatica:sqlserver://<host_name>:<port_number>;DatabaseName=<database_name>;SnapshotSerializable=true; SnapshotSerializable=true;EncryptionMethod=SSL;HostNameInCertificate=.<hostnameincertificate>;ValidateServerCertificate=true Azure SQL Database with Active Directory authentication. "jdbc:informatica: sqlserver://<host_name>:<port_number>;database=<database_name>;encrypt=true;AuthenticationMethod=ActiveDirectoryPassword;trustServerCertificate=false;hostNameInCertificate=.database.windows.net;loginTimeout=<seconds>" If you specified the Windows NT credentials for the Model repository database on Microsoft SQL Server, specify the connection string syntax to include the authentication method as NTLM. Microsoft SQL Server that uses the default instance with Windows NT credentials: "jdbc:informatica:sqlserver://<host name>:<port number>;DatabaseName=<database name>;SnapshotSerializable=true;authenticationMethod=NTLM" Microsoft SQL Server that uses a named instance with Windows NT credentials: "jdbc:informatica:sqlserver://<host name>\<named instance name>;DatabaseName=<database name>;SnapshotSerializable=true;authenticationMethod=NTLM"
Oracle	"jdbc:informatica:oracle://<host name>:<port number>;SID=<database name>;MaxPooledStatements=20;CatalogOptions=0;BatchPerformanceWorkaround=true"
PostgreSQL	"jdbc:informatica:postgresql://<host name>:<port number>;DatabaseName= "

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.

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.

Click

Test Connection

to verify that you can connect to the database.

Select

No content exists under specified connection string. Create new content.

Click

Finish

The domain creates the Model Repository Service, creates content for the Model repository in the specified database, and enables the service.

After you create the service through the wizard, you can edit the properties or configure other properties.

Rename Saved Search

Table of Contents

Installation for Data Engineering

Installation for Data Engineering

Create the Model Repository Service

Create the Model Repository Service