Securing Communications between ESCWA and ESMAC using TLS

A started enterprise server instance, or region, must have a Web Services and J2EE listener to enable a JSON interface for monitoring and controlling the live instance. This JSON interface is part of the component known as ESMAC.

Communications between ESCWA and ESMAC can be secured by configuring the Web Services and J2EE listener. See To Create a Secure Listener and SSL Options for more information.

ESCWA will communicate with ESMAC as a client and should be configured as such. See Installing a Client Certificate for Enterprise Server for more information. You should configure the root in mf-client.dat on the ESCWA host machine such that it points to the Certificate Authority (CA) list .pem file which contains the public CA certificate information that has signed the certificate used by the Web Services and J2EE listeners. Otherwise, your DemoCA installation under private/CARootcert.pem will be checked.