You can configure the batch processor to communicate with
your DB2® database over SSL.
Procedure
- Check the value of mdm.database.uri in
the $home/properties/Batch.properties file to
determine how the batch processor is currently configured to connect
to the MDM database.
- If the batch processor is configured to connect to the
MDM database using the datasource, then you do not need to configure
the batch processor. For example, you do not need to change the configuration
if the setting for mdm.database.uri is jndi:jdbc/DWLCustomer.
When the datasource on the WebSphere® Application
Server is configured to use SSL, the batch processor automatically
uses SSL to communicate with the database server.
- If the batch processor is configured to connect to the
MDM database using JDBC driver, then configure the mdm.database.uri property
and the mdm.database.prop.sslConnection property
in the $home/properties/Batch.properties file.
For example, if the setting for mdm.database.uri is jdbc:db2://shire:50000/ARUBA;user=db2user;password={xor})z4yMS8wMzY8Jg==,
you can change the port setting and then set the mdm.database.prop.sslConnection property
to true:
- mdm.database.uri - Change the value to use
the database SSL port. For example,
mdm.database.uri=jdbc:db2://shire:50001/ARUBA;user=db2user;password={xor})z4yMS8wMzY8Jg==
- mdm.database.prop.sslConnection - To use
SSL, set the value of mdm.database.prop.sslConnection to true: mdm.database.prop.sslConnection=true
- When you first connect to a SSL-enabled MDM database (or
the first time you connect to a SSL-enabled MDM database server after
the SSL certificate for the server has changed), a prompt appears
that asks you to verify the SSL signer certificate of the target server.
Reply y to add the signer to the trust store.
What to do next
You can run the $home/bin/ivt.sh script
to verify that batch processor installation was successful. If the
verification test fails, see the troubleshooting link at the end of
this topic.