Installation for PowerCenter and Data Quality

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

Back Next

Content Management Service Parameters and Database

After you configure the Data Integration Service, you can configure the parameters for the Content Management Service.

If you chose to create a Content Management Service during the installation, the

Content Management Service

page appears.

Enter the Content Management Service parameters.

The following table describes the service parameters that you must set:

Port	Description
Content Management Service name	Name of the Content Management Service to create in the Informatica domain.
HTTP Protocol	Type of connection to the Content Management Service. Select one of the following options: HTTP. Requests to the service uses an HTTP connection. HTTPS. Requests to the service uses a secure HTTP connection.
HTTP Port	Port number to use for the Content Management Service. Default is 8105.

If you select an HTTPS connection, specify whether to use the default Informatica SSL certificates or to use your SSL certificates to secure the connection to the Content Management Service.

The following table describes the SSL certificate options for securing the Content Management Service:

Option	Description
Use the default Informatica SSL certificate files	Use the default SSL certificates provided by Informatica. If you do not provide an SSL certificate, Informatica uses the same default private key for all Informatica installations. If you use the default Informatica keystore files, the security of your domain could be compromised. To ensure a high level of security for the domain, select the option to specify the location of the SSL certificate files.
Enter the location of the SSL certificate files	Use the SSL certificates that you provide. You must specify the location of the keystore files.

Option

Description

Use the default Informatica SSL certificate files

Use the default SSL certificates provided by Informatica.

If you do not provide an SSL certificate, Informatica uses the same default private key for all Informatica installations. If you use the default Informatica keystore files, the security of your domain could be compromised. To ensure a high level of security for the domain, select the option to specify the location of the SSL certificate files.

Enter the location of the SSL certificate files

Use the SSL certificates that you provide. You must specify the location of the keystore files.

If you provide the certificate, specify the location and passwords of the keystore files.

The following table describes the parameters that you must enter for the SSL certificate files:

Property	Description
Keystore file	Required. Path and file name for the keystore file that contains the private keys and SSL certificates for the database.
Keystore password	Required. Password for the keystore file for the secure database.

The keystore certificate types for the Content Management Service depends on the certificate types that the Administrator tool uses:

If you used the default keystore certificate for the Administrator tool, you can use either the default or a custom keystore certificate for the Content Management Service.

If you used a custom keystore certificate for the Administrator tool, you must use a custom keystore certificate for the Content Management Service.

Click

On the

Content Management Service

page, enter the database and user account information for the reference data warehouse database.

The following table describes the properties that you specify for the database and user account:

Property	Description
Database type	Database for the reference data warehouse. Select one of the following databases. Oracle IBM DB2 Microsoft SQL Server Microsoft Azure SQL Database PostgreSQL, using JDBC
Database user ID	User account for the reference data warehouse database.
User password	Password for the database user account.

If you select IBM DB2, specify the tablespace for the repository tables:

Property	Description
Tablespace	Name of the tablespace in which to create the tables. Specify a tablespace that meets the pageSize requirement of 32768 bytes. In a single partition database, if this option is not selected, the installer creates the tables in the default tablespace. In a multipartition database, select this option and specify the name of the non-partitioned tablespace that resides in the catalog partition of the database.

Property

Description

Tablespace

Name of the tablespace in which to create the tables. Specify a tablespace that meets the pageSize requirement of 32768 bytes.

In a single partition database, if this option is not selected, the installer creates the tables in the default tablespace.

In a multipartition database, select this option and specify the name of the non-partitioned tablespace that resides in the catalog partition of the database.

If you select Microsoft SQL Server or PostgreSQL, specify the schema for the repository tables and database connection:

Property	Description
Schema name	Name of the schema that will contain the repository tables. If not selected, the installer creates the tables in the default schema.
Trusted connection	Indicates whether to connect to Microsoft SQL Server through a trusted connection. Trusted authentication uses the security credentials of the current user to make the connection to Microsoft SQL Server. If not selected, the installer uses Microsoft SQL Server authentication.

Enter the database connection information.

You can specify the connection properties for the JDBC URL or provide the JDBC connection string.

To enter the connection information using the JDBC URL, select

JDBC URL

and specify the database connection properties.

Property	Description
Database address	Host name and port number for the database in the format <host name>:<port number> .
Database service name	Service or database name: Oracle: Enter the service name. Microsoft SQL Server: Enter the database name. IBM DB2: Enter the service name.
JDBC parameters	Optional parameters to include in the database connection string. Use the parameters to optimize database operations for the database. Verify that the parameter string is valid. The installer does not validate the parameter string before it adds the string to the JDBC URL. If not selected, the installer creates the JDBC URL string without additional parameters.