Installer 10.15 | Complete Installation and Upgrade Information for Software AG Products | Command Central | Configuring Command Central and Platform Manager | Using the Secure Socket Layer (SSL) Protocol and Certificates in Command Central | Preparing to Replace the Default Keystore and Truststore | Update the HTTPs Port of the Command Central Server
 
Update the HTTPs Port of the Command Central Server
You can update the default HTTPs port of Command Central to use the custom keystore, or configure a new HTTPs port (with unique alias and port number). However, if you choose to create and enable a new HTTPs port, you should disable the default HTTPs port of Command Central to avoid confusion.
In the HTTPs port configuration for CCE (in the web user interface; or OSGI-CCE if you use the sagcc create configuration data CLI command), specify the following security configuration details:
*Key Alias - An alias for the custom keystore.
*Type - The keystore type. Command Central supports the JKS and PKCS12 keystore types. The default is JKS.
*Location - The location of the custom keystore file, for example /path/to/ccnode.jks.
*Password - The password to access the custom keystore.
To verify the HTTPs connection to the Command Central server, use the "https://" URL of Command Central in a browser. For example, if you updated the default HTTPs port to use the custom keystore, type "https://localhost:8091/cce". Note that the browser might still indicate (with a warning or an error message) that the connection is not secure, because the browser does not recognize your CA certificate as issued by a verified authority. To get the secure connection green mark from the browser, you should import the custom CA certificate you generated (for example ccroot.cer) in the browser CA list.