PM95108: APPCENTERCONSOLE DOES NOT WORK IN WAS WITH JUNCTION BECAUSE IT CALCULATED THE WRONG CONTEXT ROOT

APAR status

• Closed as program error.

Error description

• In a clustered WAS with junction, there is always a prefix in
  the URI before our context root.
  
  A typical URI then looks like:
  
  http://myserver:myport/junction1/appcenterconsole/index.html
  
  This is a standard feature of WAS which is not taken into
  account by AppCenter.
  
  
  Look at the following code in utils.js:
  
  utils.getContext = function(page){
      //  summary:
      //      Returns the first member of the path name of the url
      //      This is the context of the web app.
      //      Main HTML page must store this context in the
  config.pureMeap.context object.
      //      Widgets must access only to the
  config.pureMeap.context object.
      //  page: String
      //      The HTML page from the context.
      if(window.location.pathname == page){
          return "";
      }
      var context = window.location.pathname.split("/");
  
      return "/" + context[1];    // String
  };
  
  
  This will cause the end point query to become
  http://myserver:myport/junction1/services?action=endpoint
  
  However, correct would be
  http://myserver:myport/junction1/appcenterconsole/services?actio
  n=endpoint
  
  The Application Center should handle junctions properly. (Maybe
  this requires additional configuration).
  
  NOTE: the same effect most likely occurs in the installers.html
  and in inst.html.
  

Local fix

• Create transparent path junctions for "applicationcenter" and
  "appcenterconsole".  This is only a partial workaround, is it
  only permits one instance of Application Center behind a given
  reverse proxy.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Administrators that are deploying the Application Center     *
  * Console on a complex path.                                   *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * If the Application Center console is deployed on the server  *
  * on a complex path (other than http://server/appcontext), for *
  * example, in a WAS environment using junctions, the           *
  * Application Center console application is not starting.      *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * -                                                            *
  ****************************************************************
  

Problem conclusion

• The context root retrieval algorithm was modified to support an
  arbitrary deployment path of the application.
  
  The fix for this APAR is currently available in fixpack 6.0.0.1.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WORKLIGHT CONSU

• Fixed component ID

  5725I4301

Applicable component levels

• R600 PSY

     UP