Running Business Processes and Composite Applications 10.4 | Running Business Processes and Composite Applications | Universal Messaging Administration Guide | Using Command Central to Manage Universal Messaging | Securing Communication Between Command Central and Universal Messaging
 
Securing Communication Between Command Central and Universal Messaging
 
Considerations When Using System Properties to Specify Truststore and Keystore Files
Configuring the JSSE System Properties
Configuring the Universal Messaging Client Properties
Switching Off the System Properties Mode
If you want to guarantee secure communication between Command Central and Universal Messaging, you must have only an nhps or nsps port (interface) configured on the Universal Messaging server. When the Universal Messaging server instance is configured with a single nhps or nsps interface, Command Central uses this interface to connect automatically to the Universal Messaging server. By default, Command Central uses the same truststore file and, in case of client-side authentication, the same keystore file that are configured in the nhps or nsps interface.
If you want to specify truststore and keystore files that are different from the ones configured in the nhps or nsps interface, you can use either the standard Java Secure Socket Extension (JSSE) system properties or the Universal Messaging client system properties for secure communication. For information about how to configure the properties, see Configuring the JSSE System Properties and Configuring the Universal Messaging Client Properties.

Copyright © 2019 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.
Innovation Release