Perform the following steps on the Ecosystem Manager Client and any other clients you are configuring with SSL.
- Change empublisher service start up script /opt/teradata/client/em/bin/empublisher to include SSL options.
- Make a copy of the existing file: cp "/opt/teradata/client/em/bin/empublisher "/opt/teradata/client/em/bin/empublisher.original
-
Open the empublisher file and locate the following line in the function start:
"nohup $JAVA -Dservice_name=empublisher $SERVICE_FLAGS -Djava.util.logging.config.file=$LOGGING_CONFIG -classpath $CLASSPATH_SERVICE $PUBLISHER_CLASS --threadPoolSize=$NUM_THREADS > $EM_HOME/logs/empublisher.log 2>&1 &"
-
Change code to:
“nohup $JAVA -Djavax.net.ssl.keyStore=/home/em/client.ks - Djavax.net.ssl.keyStorePassword=password - Djavax.net.ssl.trustStore=/home/em/client.ts - Dservice_name=empublisher $SERVICE_FLAGS - Djava.util.logging.config.file=$LOGGING_CONFIG -classpath $CLASSPATH_SERVICE $PUBLISHER_CLASS --threadPoolSize=$NUM_THREADS > $EM_HOME/logs/empublisher.log 2>&1 &”
- Copy $EM_HOME/conf/transport.properties to $EM_HOME/conf/transport.properties.original.
- Edit $EM_HOME/conf/transport.properties to change 61616 to 61617 and tcp to ssl.
- Stop and start the empublisher service: /etc/init.d/empublisher stop /etc/init.d/empublisher start
- Check the log file: tail -f /opt/teradata/client/em/logs/empublisher0_0.log
- Send a sample sendevent and check the EM repository or EM Explorer portlet to verify.