Installation and Configuration Guide > Part IV: After You Install the Services > Create and Configure Application Services > Create and Configure the Model Repository Service
  

Create and Configure the Model Repository Service

The Model Repository Service is an application service that manages the Model repository. The Model repository stores metadata created by Informatica clients and application services in a relational database to enable collaboration among the clients and services.
When you access a Model repository object from the Developer tool, the Analyst tool, the Administrator tool, or the Data Integration Service, the client or service sends a request to the Model Repository Service. The Model Repository Service process fetches, inserts, and updates the metadata in the Model repository database tables.

Create the Model Repository Service

Use the service creation wizard in the Administrator tool to create the service.
    1. In the Administrator tool, click the Manage tab.
    2. Click Actions > New > Model Repository Service.
    The New Model Repository Service dialog box appears.
    3. 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.
    4. Click Next.
    The New Model Repository Service - Step 2 of 2 page appears.
    5. 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.
    Password
    Repository database password for the database user.
    Database Schema
    Available for Microsoft SQL Server. 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.
    6. 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
    • - 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
    7. 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.
    8. Click Test Connection to verify that you can connect to the database.
    9. Select No content exists under specified connection string. Create new content.
    10. Click Finish.
    The domain creates the Model Repository Service, creates content for the Model repository in the specified database, and enables the service.
    Note: When you update the Model Repository Service properties, you must restart the Model Repository Service for the modifications to take effect.
After you create the service through the wizard, you can edit the properties or configure other properties.

Create the Model Repository User

If the domain does not use Kerberos authentication, the domain uses a user account to authenticate other application services that make requests to the Model Repository Service. You must create a user account and assign the user the Administrator role for the Model Repository Service.
When you create an application service that depends on the Model Repository Service, you provide the name of the Model Repository Service and of this Model repository user.
    1. In the Administrator tool, click the Security tab.
    2. On the Security Actions menu, click Create User to create a native user account.
    Note: If you set up LDAP authentication in the domain, you can use an LDAP user account for the Model repository user.
    3. Enter the following properties for the user:
    Property
    Description
    Login Name
    Login name for the user account. The login name for a user account must be unique within the security domain to which it belongs.
    The name is not case sensitive and cannot exceed 128 characters. It cannot include a tab, newline character, or the following special characters:
    , + " \ < > ; / * % ? &
    The name can include an ASCII space character except for the first and last character. All other space characters are not allowed.
    Password
    Password for the user account. The password can be from 1 through 80 characters long.
    Confirm Password
    Enter the password again to confirm. You must retype the password. Do not copy and paste the password.
    Full Name
    Full name for the user account. The full name cannot include the following special characters:
    < > “
    Description
    Description of the user account. The description cannot exceed 765 characters or include the following special characters:
    < > “
    4. Click OK.
    The user properties appear.
    5. Click the Privileges tab.
    6. Click Edit.
    The Edit Roles and Privileges dialog box appears.
    7. On the Roles tab, expand the Model Repository Service.
    8. Under System Defined Roles, select Administrator and click OK.