Maximo List Archive

From: Victor (2011-09-29 19:23)

Hello All,
After doing a lot of research and resolving the DOCLINKS HTTP 404 error. I thought of sharing this with the group.
Configuration Set up :
1.Unix or Windows Platform/Bea Oracle Weblogic 9.2 MP2
2. Maximo v7117
3. Oracle 10g
Issue Details :
We were having this issue, when we use to deploy the DOCLINKS as web application on Oracle Weblogic 9.2 MP2, after configuring Maximo for DOCLINKS after the deployment. We were able to upload a document, but we cannot view the document until we "redeploy" or "Update" the DOCLINKS Web Application and it used to give the HTTP 404 Page not found error.
Resolution :
Below are the observations and solutions for the HTTP 404 error for the DOCLINKS attachment web application :
1. Issue is with WLS 9.2 MP2.
2. Background & Analysis:
If the WebLogic proxy plugin is used in a Web Server to load balance requests across WebLogic servers in a cluster, then the plugin sends a dummy request to the cluster in order to retrieve the cluster server list. The cluster server list is present in the HTTP Response Header and not in the body. So, it does not matter if a non-existent web application is requested. That's why a request is made to a non-existent web application/context called /bea_wls_internal/WLDummyInitJVMIDs, thereby resulting in a HTTP 404 error, even though the objective of obtaining the cluster server list is achieved. Well, Oracle could have handled this functionality better by internally deploying a dummy application to prevent these HTTP 404 errors.
3. Solutions :
There are two solutions to get rid of the HTTP 404 errors:
SOLUTION 1: Configure a default web application which does nothing (dummy).
SOLUTION 2 : Solution for the stand alone web application which targets directly to a weblogic server : Change the weblogic.xml context root
Existing statement : <context-root>/bea_wls_internal</context-root>
Modify it to : <context-root>/</context-root>
Note : This was the test ran on the Amgen Local environment box.
SOLUTION 3 : Solution for the web applications targetting to an Enterprise Application : If you package the Web Application as part of an Enterprise Application (.ear archive or exploded .ear), specify the context-root in application.xml. Note that the application.xml context-root takes precedent over the weblogic.xml value.
SOLUTION 4: Obtain patch CR271671 (for 9.2 MP2) from Oracle to suppress HTTP 404 errors in access logs if you do not wish to configure a default web application. If you're using another version of WebLogic Server, request Oracle for a suitable patch similar to CR271671.
Root Cause :
/bea_wls_internal/WLDummyInitJVMIDs is a non-existent web application since the WebLogic proxy plugin obtains required information from HTTP Response Headers alone.
For admin servers :
OPTION-1). Please assign the "context-root" element value as /
It will make your WebApplication a default web application on the server..
To change context root in weblogic.xml following entry is needed:
Example:
1 <?xml version='1.0' encoding='UTF-8'?>
2 <weblogic-web-app xmlns="http://www.bea.com/ns/weblogic/90" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
3 <context-root>/</context-root>
4 </weblogic-web-app>
OPTION-2). If you don't want to change your "weblogic.xml" then Please login to admin console-
Servers->YourManagedServerName(Click)->Protocol (Tab)->Http (Sub Tab)->Default WebApp Context Root:
NOTE:- In the above Field Please specify your WebApplications Context Root Preceding by forward slash(/). (Example: /MyContextRoot)...so that after Server restart that Application will become your Servers Default WebApp.
Important Note : If you are deploying the DOCLINKS on managed server, just select "I want to access application from specified folder_location" while deploying the folder as an application.
This will complete the process and there will be no issues while retrieving the attachments when the managed server URL is provided in the maximo system properties.
Hope this helps.
Thanks,
Victor