Error loading configuration bootstrap XML after upgrading OSP

After upgrading OSP, the catalina.out log during tomcat startup reports the following error:

Error loading configuration bootstrap XML: Class: XmlParseException

   Class: LoggableMessage

      Level: SEVERE

      Code: internal.atlaslite.jcce.xml.w3c.XMLUtil.loadConfigFile() [2975]

      Thread: localhost-startStop-1

      Correlation Id: dd3e5bfe-ca01-421f-a09d-d1fb17b9124f

      Text: An error occurred attempting to parse an XML document.

      Root cause:

 

         java.io.FileNotFoundException

/opt/netiq/idm/apps/tomcat/webapps/osp/WEB-INF/conf/current/bootstrapcfg.xml (No such file or directory)

            java.io.FileInputStream: FileInputStream.java: open0: -2

            java.io.FileInputStream: FileInputStream.java: open: 195

            java.io.FileInputStream: FileInputStream.java: <init>: 138

            java.io.FileInputStream: FileInputStream.java: <init>: 93

            sun.net.www.protocol.file.FileURLConnection: FileURLConnection.java: connect: 90

Additionally, when attempting to access /idmdash or any other Identity Application, no login page is visible, and in it's place is this error:

{"Fault":{"Code":{"Value":"Sender","Subcode":{"Value":"XDAS_OUT_ENTITY_NON_EXISTANT"}},"Reason":{"Text":"Not found: idm"}}}

There is a core file name change that occurred between OSP 6.0.0.5 and OSP 6.1.3 and later. If you modify the setenv.sh (setenv.bat for Windows) file to point to the new file name, the issue is resolved.

 

The default location for setenv.sh on Linux - /opt/netiq/idm/apps/tomcat/bin

The default location for setenv.bat on Windows - C:\netiq\idm\apps\tomcat\bin

1. Stop tomcat.
2. Open up the setenv file in a text editor.
3. Under CATALINA_OPTS there should be a line:
1. -Dcom.netiq.osp.ext-context-file=/opt/netiq/idm/apps/osp/lib/osp-conf.jar
4. Change the osp-conf.jar to osp-conf-edir.jar.
5. Save the change.
6. Start tomcat.

This .jar file is required for proper OSP startup. In an older Identity Applications environment, the file was originally named osp-conf.jar. When you upgrade to a later version of OSP, the osp-conf.jar ends up replaced with osp-conf-edir.jar. The setenv file contains several environment variables for the Identity Applications environment, and doesn't get updated with the OSP upgrade. Changing this file to point to the new, proper osp-conf-edir.jar resolves the problem.