Slogan: Java certificates have expired for Element Manager (EM) and Node B Eleme nt Manager (BEM) Revision

History: A- First Revision Affected Node: RNC, RBS Affected Releases: All Releases prior to those specified in the Solutions Delivery Plan Affected Product: UTRAN PHASE: All Phases prior to those specified in the Solutions Delive ry Plan Product number: All Product Name: RNC, RBS SW identity: All prior to those specified in the Solutions Deliver y Plan Configuration info: All TR references: Problem Description: An issue has been identified with the Java certificates contained within RNC/RBS jar files which are due to or have expired. These jar files are used by Element Manager (EM) & Node B Element Manager (BEM) applications. HP23790

The problem is visible if the related jar files are missing or have been deleted from the client workstation or OSS cache and therefore need to be fetched again from RNC/RBS. In this case it will not be possible to fetch these files due to the expired Java certificates. If however these files are cached as expected on the client workstation they will not need to be fetched again and therefore ther e will be no issues with EM/BEM activities. Solution/Workaround: Stand Alone Windows PC (No OSS) In order to run the EM/BEM applications from a Windows PC which is missing the r equired jar files and after the Java certificate expiry date mentioned in the pr oblem description, please follow the steps below: 1. If you don't have EM/BEM applications installed, connect to the node from an http browser (http://<nodeip>/em/index.html) and run the EM/BEM application installation 2. Change the clock on the Windows PC (from Control panel -> Date & Time) to a date before the Java certificate expiry date (example 1/12/2011). 3. Start the EM (RNC) application, connect to the RNC node and then start th e following applications from the tools menu:

RBS - Java certificates expired 2011-12-11 RNC - Java certificates expired 2011-12-16

a. b. c.

RNC Site Basic Configuration Wizard RNC Hardware Configuration Tool Performance Scanner.

The EM jar files will be fetched from the RNC and stored in the cache directory (example: C:\Users\<userid>\Ericsson\). Note the cache directory is not cleared if the Windows PC restarts. 4. For BEM (RBS) it is sufficient to start the application to fetch the nece ssary BEM jar files. 5. Change the date back to the current date on the Windows PC.

By performing these actions the EM/BEM applications will skip the certificate ch eck as the files are now stored in the local Windows PC cache. The important jar files are: EM C:\Users\<userid>\Ericsson\<LM_PRODUCT_NUMBER>\<LM_REVISION_NUMBER>\guiCommon.ja r C:\Users\<userid>\Ericsson\<LM_PRODUCT_NUMBER>\<LM_REVISION_NUMBER>\siteBasic.ja r C:\Users\<userid>\Ericsson\<LM_PRODUCT_NUMBER>\<LM_REVISION_NUMBER>\icm.jar C:\Users\<userid>\Ericsson\<LM_PRODUCT_NUMBER>\<LM_REVISION_NUMBER>jdom.jar C:\Users\<userid>\Ericsson\<LM_PRODUCT_NUMBER>\<LM_REVISION_NUMBER>\RncJaxb.jar C:\Users\<userid>\Ericsson\<LM_PRODUCT_NUMBER>\<LM_REVISION_NUMBER>\performances canner.jar C:\Users\<userid>\Ericsson\<LM_PRODUCT_NUMBER>\<LM_REVISION_NUMBER>\RadioNetwork .jar C:\Users\<userid>\Ericsson\<LM_PRODUCT_NUMBER>\<LM_REVISION_NUMBER>\Area.jar C:\Users\<userid>\Ericsson\<LM_PRODUCT_NUMBER>\<LM_REVISION_NUMBER>\Equipment.ja r C:\Users\<userid>\Ericsson\<LM_PRODUCT_NUMBER>\<LM_REVISION_NUMBER>\IP.jar C:\Users\<userid>\Ericsson\<LM_PRODUCT_NUMBER>\<LM_REVISION_NUMBER>\ATM.jar C:\Users\<userid>\Ericsson\<LM_PRODUCT_NUMBER>\<LM_REVISION_NUMBER>\Signalling.j ar C:\Users\<userid>\Ericsson\<LM_PRODUCT_NUMBER>\<LM_REVISION_NUMBER>\IP_stack.jar C:\Users\<userid>\Ericsson\<LM_PRODUCT_NUMBER>\<LM_REVISION_NUMBER>\ATM_stack.ja r BEM C:\Users\<userid>\Ericsson\<LM_PRODUCT_NUMBER>\<LM_REVISION_NUMBER>\bem.jar

C:\Users\<userid>\Ericsson\<LM_PRODUCT_NUMBER>\<LM_REVISION_NUMBER>\bemviews.jar C:\Users\<userid>\Ericsson\<LM_PRODUCT_NUMBER>\<LM_REVISION_NUMBER>\bemhlp.jar OSS Solaris Machine 1. First the steps from the Stand Alone Windows PC procedure should be follo wed on the Windows PC to fetch the required jar files. 2. Locate the EM/BEM jar files mentioned above on the Windows PC and copy th em to the following directory in the OSS Solaris Machine: /var/opt/ericsson/nms_cppem/node/<nodetype>/Ericsson/<LM_PRODUCT_NUMBER>/<LM_REV ISION_NUMBER>/<xyz.jar> Note: Ensure that the jar files are copied to the correct CXC directory on the OSS Solaris Machine.

Solutions Delivery Plan: The updated Java certificates have been delivered in the following releases: W10B CP3 IP13 - planned release 2011-12-16 W11A CP3 IP10 - planned release 2011-12-22 W11B CP1 IP1 - planned release 2011-12-16 RISK IF SOLUTION/WORKAROUND IS NOT IMPLEMENTED: EM/BEM applications will not work if there are no jar files in the cache directo ry and the Java certificates have expired on the Nodes.

DO NOT change the clock on the OSS Solaris Machine. Use ftp in binary mode during transfer of the files.