Sterling Secure Proxy Instructions for Installing the New Castor jar file from IBM Fix Central for the Security Advisory. APAR IT06628 2015/01/23 This process will allow the Customer to pull a new Castor jar from the IBM Fix Central site and replace the existing Castor jar in the installed instances of Sterling Secure Proxy (SSP) Engine and SSP Configuration Manager (CM). Note that Castor is not used by the Sterling Secure Proxy Perimeter Server (PS) or the Sterling External Authentication Server (SEAS). This jar file will be folded into the next cumulative maintenance iFixes for each supported version, if you prefer to wait for that. STEP 1 IS DONE ONCE AND CAN BE DONE WHILE THE PRODUCT IS RUNNING. 1. Download the Castor jar file from Fix Central to a work directory. The file name is castor-1.3.3-xml.jar. When moving / copying the file, be sure to move it in binary mode (not ascii or text). STEPS 2 AND FOLLOWING ARE DONE FOR EACH INSTANCE OF THE STERLING SECURE PROXY ENGINE AND CONFIGURATION MANAGER. 2. Make a backup of the target directory before you begin. 3. Take the target SSP Engine and/or Configuration Manager (CM) instance down 4. Move the existing castor.jar file out of the /lib/thirdparty directory. We will place it in the installation directory as a backup. UNIX: cd mv lib/thirdparty/castor.jar ./castor.jar.orig Windows: cd move lib\thirdparty\castor.jar .\castor.jar.orig 5. Copy the new castor-1.3.3-xml.jar file from the work directory to the /lib/thirdparty directory. It will keep the castor-1.3.3-xml.jar name. UNIX: cp /castor-1.3.3-xml.jar lib/thirdparty Windows: copy \castor-1.3.3-xml.jar lib\thirdparty 7. Start the Sterling Secure Proxy Engine or CM. 8. Duplicate this process (starting with step 2) for any other Sterling Secure Proxy Engine or Configuration Manager install locations.