IBM Support

Secure Proxy engine fails to start after upgrading from version 3.4.1.x to 3.4.3.0

Technical Blog Post


Abstract

Secure Proxy engine fails to start after upgrading from version 3.4.1.x to 3.4.3.0

Body

Secure Proxy engine fails to start after upgrading from version 3.4.1.x to 3.4.3.0

The startEngine.out file in the engine bin directory shows this error:
Caused by: java.lang.NullPointerException
 at java.io.File.<init>(File.java:288)
 at com.sterlingcommerce.csp.logger.ProxyLogger.<clinit>(ProxyLogger.java:312)

Cause:    During an upgrade from SSP 3.4.1.x to 3.4.2.0 or 3.4.3.0 there are a couple of files that don't get updgraded. The reason is during the upgrade it detects that those files are present and doesn't upgrade them. However, those files have changed significantly and will not work for version 3.4.2.0 and 3.4.3.0.
    
    The 2 files are:
    /<SSP_Engine_Install>/bin/log.properties
    /<SSP_Engine_Install>/conf/log4j2.xml

Workaround:
    
    Change directory to /<SSP_Engine_Install>/bin/
    mv log.properties log.properties.orig
    mv log.properties.install log.properties
    
    Change directory to /<SSP_Engine_Install>conf/
    mv log4j2.xml log4j2.xml.orig
    mv log4j2.xml.install log4j2.xml
    
    Start the engine now.

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS4PJT","label":"IBM Sterling Connect:Direct"},"Component":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

UID

ibm11123323