Switch from HTTP to HTTPS Mode Using a Secure HTTP Server Adapter

You can switch from HTTP to HTTPS mode by creating a new HTTP Server adapter instance with SSL enabled.

  1. Create a new HTTP Server adapter instance with SSL enabled. You must configure the following parameters as specified:
    • User Authentication Required is set to No
    • Use SSL is set to Must
  2. Deploy required WAR files to the HTTP Server adapter instance with SSL enabled.
    Note: All WAR files must be picked up from the /install_dir/install/noapp/deploy directory when configuring the HTTP Server Adapter instance. Additionally, the context name of the admin web application must match the ADMIN_CONTEXT_PATH parameter in /install_dir/install/properties/sandbox.cfg file. For all the other web applications, the context name should be the name of the war file without the ".war" extension.

    This is necessary so that any changes made via a patch or hotfix are automatically reflected in the HTTP Server adapter deployment.

    The required WAR files include:
    • admin.war
    • dashboard.war
    • gbm.war
    • myaft.war
    • portlets.war

    Additional WAR files may be required to support new functionality added by you to your Dashboard.

  3. Verify the context name of the admin.war web application matches the ADMIN_CONTEXT_PATH parameter in the /install_dir/install/properties/sandbox.cfg file.
  4. Verify the Dashboard Web application is accessible via the HTTP Server adapter by accessing https://host:<secure_http_server_adapter_port>/dashboard.
  5. Verify the GPM Web application is accessible via the secure HTTP Server adapter by accessing https://host:<secure_http_server_adapter_port>/gbm/pmodeler/ProcessModeler.jnlp.
  6. Navigate to /install_dir/install/properties.
  7. Open the sandbox.cfg file.
  8. Modify the following parameters: 
    WEBAPP_PROTOCOL=https
WEBAPP_LIST_PORT=<secure_http_server_adapter_port>
    These parameters are used by the GPM for communication with the server.
  9. (Optional, Recommended) If you want to turn off the deployment of the Dashboard and GPM Web applications on the base port, specify the following parameters in a customer_overrides.properties file: 
    SKIP_BASEPORT_DEPLOYMENT_WARS=admin,dashboard,gbm,communitymanagement,myaft,portlets
HTTPS_REDIRECT_WARS=admin,dashboard,gbm,communitymanagement,myaft,portlets
HTTPS_LIST_PORT=<secure_http_server_adapter_port>
    For example: 
    
## Identifies the war files to be skipped during deployment on the base port.
## Use comma-separated list to specify multiple wars
noapp.SKIP_BASEPORT_DEPLOYMENT_WARS=admin,dashboard,gbm,communitymanagement,myaft,portlets
## Identifies wars for auto-redirect to the https port.
## Use comma-separated list to specify multiple wars
noapp.HTTPS_REDIRECT_WARS=admin,dashboard,gbm,communitymanagement,myaft,portlets
## Identifies the https port for the redirected wars.
## If specified, this should match the WEBAPP_LIST_PORT in sandbox.cfg
noapp.HTTPS_LIST_PORT=<secure_http_server_adapter_port>
  10. (Optional) If you want to send cookies from the browser using a secure protocol like HTTPS, specify the following parameter in a customer_overrides.properties file: 
    ## sending cookies as secure over https
http.useSecureCookie=true
  11. Save and close the file.
  12. Navigate to /install_dir/install/bin.
  13. Stop Sterling B2B Integrator.
  14. Apply the configuration changes. Enter ./setupfiles.sh.
  15. Deploy the new configuration. Enter ./deployer.sh.
  16. Start Sterling B2B Integrator.
  17. If you turned off the deployment of the Dashboard and GPM Web applications on the base port (Step 9), verify the following:
    • Dashboard Web application access on http://host:baseport/dashboard is redirected to https://host:<secure_http_server_adapter_port>/dashboard automatically.
    • GPM Web application access on http://host:baseport/gbm/pmodeler/ProcessModeler.jnlp is redirected to https://host:<secure_http_server_adapter_port>/gbm/pmodeler/ProcessModeler.jnlp automatically.