7.4   Update com.ibm.iis.xmeta.repo.conn.POJO_STAGING property

Run the following command on the services tier to update com.ibm.iis.xmeta.repo.conn.POJO_STAGING property:

{IS install path}/ASBServer/bin/xmetaAdmin.sh setProperty -file {IS install path}/ASBServer/conf/imam_staging_repository.properties -dbfile {IS install path}/ASBServer/conf/database.properties com.ibm.iis.xmeta.repo.conn.POJO_STAGING

8     Configure DSODB

These steps are for configuring TLS support for the DSODB MS SQL SERVER database connections.

8.1    Configure MS SQL SERVER to Support SSL Connections

If the DSODB database is co-located with the repository database, then the MS SQL SERVER instance was already configured to support SSL connections in the previous steps.

If the DSODB data is not co-located with the repository database, then perform the same steps on the DSODB database instance that were performed on the XMeta repository database instance.

8.2    Configure the Information Server Engine Tier

Import the MS SQL SERVER Certificate into the Java Trust Store

This step can be skipped if the engine tier is co-located with the services tier.

This step is for importing the MS SQL Server certificate into the trust stores of the Java instances that are used when running Information Server tools and installation upgrades.

1. Determine the directory locations of the Java instances.  The following Java trust store locations need to be updated, if they exist in your installation:
   1. {IS install path}/jdk/jre/lib/security/cacerts
   2. {IS install path}/jdk32/jre/lib/security/cacerts
   3. {IS install path}/_uninstall/_jvm/lib/security/cacerts
   4. {IS install path}/Updates/_jvm/lib/security/cacerts
2. Run the following command for each Java trust store instance to import the SQL Server certificate that was generated in the section 5:
   
   {IS install path}/jdk/jre/bin/keytool -import -file {certificate file} -alias SQLCert -keystore {Java trust store} -storepass changeit

Update the Registered Database Server

Run the following command on the services tier to list the registered databases:

{IS install path}/ASBServer/bin/RepositoryAdmin.sh -listDatabases

For each database in the list that has been configured to use SSL connections, do the following steps.

Run the following command to display the registered database properties, where {database name} is the name of the database that was returned from the -listDatabases command:

{IS install path}/ASBServer/bin/RepositoryAdmin.sh -displayDatabase -dbName {database name}

Make sure that the database details are correct. If they need any update, do it by following below.

If the database server port needs to be updated to the security port, then run the following command to update the port, where {database version} and {database server host} are found in the output of the -displayDatabase command and {database server security port} is the security port that was configured previously:

{IS install path}/ASBServer/bin/RepositoryAdmin.sh -updateDatabaseServer -databaseType SQLSERVER -databaseVersion {database version} -serverHost {database server host} -serverPort {database server security port}

Update the Registered DSODB Repository

Run the following command on the services tier to list the registered repositories:

{IS install path}/ASBServer/bin/RepositoryAdmin.sh -listRepositories

Locate the repository name of the registered DSODB repository (e.g. dsodb) in the command output.

Run the following command to display the registered DSODB repository properties, where {repository name} is the name of the registered DSODB repository that was returned from the -listRepositories command:

{IS install path}/ASBServer/bin/RepositoryAdmin.sh -displayRepository -reposName {repository name}

Update the connectionURL by appending EncryptionMethod=SSL;CryptoProtocolVersion=TLSv1.2; to the existing connectionURL. Run the following command to update the connectionURL:

{IS install path}/ASBServer/bin/RepositoryAdmin.sh -updateRepositoryConnection -reposName {repository name} -connectionURL "{url}"

Update the DSODBConnect.cfg File

Make a backup of the existing DSODBConnect.cfg file by running the following commands on the engine tier:

cd {IS install path}/Server/DSODB

copy DSODBConnect.cfg DSODBConnect.cfg.orig

Generate a new connection file by running the following command:

{IS install path}/ASBNode/bin/RegistrationCommand.sh -user {admin user} -password {password} -gcf -repository {dsodb repository name} -cf DSODBConnect.tmpl -results DSODBConnect.cfg