Configuring Custom Certificates

Using custom certificates with for Java RMI with SSL.

Procedure

  1. On the Dashboard pane, navigate to Trading Partner > Certificates.
  2. To create the System Certificate:
    1. Navigate to Trading Partner > Digital Certificates.
    2. Go to System and select Create to create the System Certificate.
  3. To check-in the System Certificate:
    1. Navigate to Trading Partner > Digital Certificates.
    2. Go to System and select Check in to check-in the System Certificate.
  4. Check out the CA certificate:
    1. Under Trading Partner > Digital Certificates, go to System and enter the name of your custom certificate in the search box.
    2. Select the check out option.
  5. Check-in the downloaded certificate in the CA certificate column.
    1. Under Trading Partner > Digital Certificates, go to CA and select the check in option.
  6. Modify the customer_overrides.properties file.
    For example, consider the following certificate names for the certificates that are checked in:
    • System Certificate: Sample_System_Cert
    • CA Certificate: Sample_CA_Cert
    Now, add the following lines to the customer_overrides.properties file:
    Note:
    • You must add the following properties to both ASI node and Adapter Container nodes:
      SSLRmiserver.systemCertificate=Sample_System_Cert
SSLRmiserver.caCertificate=Sample_CA_Cert
    • You must restart the Sterling B2B Integrator after you modify the customer_overrides.properties file.

Results

Windows:
To verify Sterling B2B Integrator is configured with the correct SSL certificates, attempt to start the ASI node (Node1) using the following script:
<Install_Dir>/bin/startASIWindowsService.cmd
  • If the certificate is configured correctly, the Sterling B2B Integrator and the Dashboard will appear.
  • If the certificate is configured incorrectly and all the components of Sterling B2B Integrator are started at the same time, Liberty might lead to errors at startup and cause the startWindowsService.cmd script to freeze. This script must be stopped using CTRL + C from command prompt and stop the “Liberty Profile” service from the Windows Services application.