User Application 3.5.1 installation using WebSphere must use the default context name

  • 7003909
  • 17-Jul-2009
  • 26-Apr-2012

Environment

Novell User Application 3.5.1
IBM WebSphere Application Server 6.1

Situation

During the installation of Novell User Application 3.5.1 using IBM WebSphere Application Server 6.1 as the Application Server, if the context is changed from IDMProv (for the Provisioning version) or IDM (for the Standard version) the new context name will not replace the default value through out the code in the User Application.  The war will be created with the new context, but code will still use IDMProv or IDM and not the new context name.  As a result, when a user tries to access the User Application in a browser using the context entered during the install they will receive an error similar to the following:

Error 404: No Target servlet configured for uri:/IDMProv/portal/cn/GuestContainerPage/Welcome

or

Error 404: No Target servlet configured for uri:/IDM/portal/cn/GuestContainerPage/Welcome

Also, the URL in the browser will be changed to the default context of IDMProv or IDM instead of the context that was entered



The behavior is not experienced when selecting Red Hat JBoss as the Application Server during the installation.

Resolution

This is a Bug with version 3.5.1 of the Novell User Application and it only occurs when selecting IBM WebSphere as the Application Server during the install.

This bug has been fixed in version 3.6.0 of the Novell Identity Manager Roles Based Provisioning Module (User Application)

For version 3.5.1 of the Novell User Application, the default contexts of IDMProv (for the Provisioning version) and IDM (for the Standard version) that are presented during the installation must be used.  The context names can not be changed during the installation when using IBM WebSphere as the Application Server.

Additional Information

Here is an  example:

During the installation of the Provisioning version of the User Application 3.5.1 with WebSphere as the Application Server, the context was set to 'MyPortal'.  The war name would be 'MyPortal.war'.  However, the code within the war would still be using 'IDMProv' instead of 'MyPortal'. 

When trying to access the deployed war on WebSphere using the context specified during the installation:

HTTP://%server%:%port%/MyPortal

The following error will be presented in the browser:

Error 404: No Target servlet configured for uri:/IDMProv/portal/cn/GuestContainerPage/Welcome

Also, the URL in the browser will now be:

HTTP://%server%:%port%/IDMProv/portal/cn/GuestContainerPage/Welcome