Taulia experience center

Article Number: 000008593

Overview

In an effort to ensure proper security levels, Taulia is mandating a POD software certificate update to be implemented for SAP customers using a POD connection. The update replaces a previously used self-signed certificate with a Certificate Authority (CA) issued certificate.


Actions

• Verify your POD version (From %POD_DIR%/wrapper run java -jar tauliaBase.jar -v)

• Verify your host name (Located in the POD directory > %POD_DIR%/wrapper/pod/mem/pod.config)

• Verify your Java Version (Open a command window and enter the java –version command)

• If required to update, review your options for update and schedule time to implement the changes.

Current Versions

The following POD versions were issued with the new certificate already installed:

• Version 2.2.3 r1 and greater

• Version 2.2.4 r2 and greater

• Version 2.2.5 and greater

Steps to Update the POD Certificate - CURRENT VERSIONS

1. Stop the POD.

2. Upgrade the Java to 1.8.0_144 + or greater.

3. Access the pod.config file. (%POD_DIR%/wrapper/pod/mem/pod.config)

   1. Update the host name as follows:

      1. Staging Test Environment: host = dispatch.staging.taulia.com

      2. NA1 Production: host = dispatch.na.taulia.com

      3. EU1 Production: host = dispatch.eu.taulia.comReview the port and ensure it is set to 443

   2. Review the trustStore name and update: trustStore = ssl/pod_truststore_v1

4. Start the POD.

5. Verify a successful connection is obtained and data is transferred.

Older Versions

If you are running any POD version older than those mentioned, you will need to perform the steps to update your certificate.
 

• Versions 2.0.8 - 2.2.3 r0

Taulia offers two paths for completing this update:
 

1. If you have a planned upgrade of your SAP add-on & POD before the end of the year, you do not need to take any action. The new files will be provided in the upgrade process.

2. If you do not have a planned upgrade of your SAP add-on & POD before the end of the year, you can adjust the files directly. We recommend making the change in your DEV and/or QA environment first, testing and then making the change in production.
    

Steps to Update the POD Certificate - OLD VERSIONS
 

1. Click here to download the certificate.

2. Stop the POD.

3. Upgrade the Java to 1.8.0_144 + or greater.

4. Navigate to the POD folder for the Truststore files. (%POD_DIR%/wrapper/ssl)

5. Add/Replace the file provided by Taulia.

   1. Note: If you elect to change the file name, please record that name to verify in the pod.config file.

6. Access the pod.config file. (%POD_DIR%/wrapper/pod/mem/pod.config)

   1. Update the host name as follows:

      1. Staging Test Environment: host = dispatch.staging.taulia.com

      2. NA1 Production: host = dispatch.na.taulia.com

      3. EU1 Production: host = dispatch.eu.taulia.com

   2. Review the port and ensure it is set to 443

   3. Review the trustStore name and verify that it matches the new file name just updated. trustStore = ssl/pod_truststore_v1 is the expected value.

7. Start the POD.

8. Verify a successful connection is obtained and data is transferred.

Unsupported Versions

If you are running a version that is older than 2.0.8, you will have to test if your POD version works with Java 1.8.0_144+. We would suggest to upgrade your development environment or a sand box environment that is available.


Steps to validate Java 1.8.0_144+
 

1. Stop the POD.

2. Upgrade the Java to 1.8.0_144 + or greater.

3. Start the POD.

4. Verify a successful connection is obtained and data is transferred and only continue if successful. 

5. Click here to download the certificate.

6. Navigate to the POD folder for the Truststore files. (%POD_DIR%/wrapper/ssl)

7. Add/Replace the file provided by Taulia.

   1. Note: If you elect to change the file name, please record that name to verify in the pod.config file.

8. Access the pod.config file. (%POD_DIR%/wrapper/pod/mem/pod.config)

   1. Update the host name as follows:

      1. Staging Test Environment: host = dispatch.staging.taulia.com

      2. NA1 Production: host = dispatch.na.taulia.com

      3. EU1 Production: host = dispatch.eu.taulia.com

   2. Review the port and ensure it is set to 443

   3. Review the trustStore name and verify that it matches the new file name just updated. trustStore = ssl/pod_truststore_v1 is the expected value.

9. Start the POD.

10. Verify a successful connection is obtained and data is transferred.

Java upgrade not successful 

If your Java upgrade is not successful with your current POD version, you will have to upgrade your POD software and Taulia Add-on to be able to move forward. Please contact your Taulia business point of contact for further help. 


Additional Resources
 

• For additional assistance, please reach out to your Taulia business point of contact.

• For specifics on Java versions, determining location of POD files, please reference the Taulia Business Exchange for SAP: POD Install Guide