If you have to redeploy any of the SAS 9.2 Web applications on IBM Websphere 6.x / 7.x, you must be sure to update the Classloader policy and mode for the EAR file and the Classloader mode for each WAR module that is contained in the EAR file. The correct setting for all of the SAS Web applications is Classes loaded with application class loader first.

You must use the WebSphere Application Server administration console (available at http://host-name.company.com:9060/ibm/console) to manually deploy SAS Web applications. Complete the following steps to set or check the Classloader policy and mode settings:

1. 1. From the Enterprise Applications menu, select the SAS Web application's link.
   2. Click the Classloading and update detection link for the application EAR file and ensure that the Classes loaded with application class loader first radio button is selected for this EAR file.

Note: By default, the WAR file's class-loading policy at the EAR level is set to MULTIPLE, so no action is required.

1. You might be forced to enter a value for Polling interval for updated files. If that is the case, enter 3 since 3 seconds is the default value for the Web Application Server.
2. On the Enterprise Applications page for this application, click the Manage Modules link.
3. You now must select each WAR module, choosing Classes loaded with application class loader first from the list menu for Class loader order.
4. Save your work.

   Note: You should wait to save your work until you have set the Classloader modes for all WAR modules.

These instructions are also documented in the file SAS_configuration_directory\Lev1\Documents\Instructions.html.

If you set the Classloader policy and mode incorrectly, one or more of the following errors might appear in WebSphere's Systemout.log file:

Error 1

[12/7/09 14:07:17:256 EST] 0000006c HttpMethodDir I org.apache.commons.httpclient.HttpMethodDirector isRedirectNeeded Redirect requested but followRedirects is disabled
[12/7/09 14:07:17:272 EST] 0000006c HTTPSender    I org.apache.axis2.transport.http.HTTPSender sendViaPost Unable to sendViaPost to url[http://sasbi.demo.sas.com:9080/SASBIDashboard/services/CandidateIndicatorListService]
                                 org.apache.axis2.AxisFault: Transport error: 302 Error: Found
    at org.apache.axis2.transport.http.HTTPSender.handleResponse(HTTPSender.java:298)
    at org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:192)
    at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:77)
    at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:327)
    at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:206)
    at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:396)
    at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:374)
    at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:211)
    at org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
    at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:528)
    at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:508)
    at org.apache.axis2.rpc.client.RPCServiceClient.invokeBlocking(RPCServiceClient.java:101)
    at com.sas.bi.eventgen.EventGenUtil.invokeRPCBlockingAuthenticated(EventGenUtil.java:128)
    at com.sas.bi.dashboard.egfhandlers.BidEventCandidateRefHandler.getCandidateIndicatorList
(BidEventCandidateRefHandler.java:137)
    at com.sas.bi.dashboard.egfhandlers.BidEventCandidateRefHandler.getEventCandidateList
(BidEventCandidateRefHandler.java:182)
    at com.sas.bi.eventgen.EventCandidateRefManager.execHeartbeat(EventCandidateRefManager.java:113)
    at com.sas.bi.eventgen.EventCandidateRefHeartbeatThread.run(EventCandidateRefManager.java:214)

Error 2

[12/7/09 14:08:14:169 EST]]00000065 ServletWrappe E SRVE0068E: Uncaught exception thrown in one of the service methods of the servlet: /tiles-components/indicatorEditor.jsp. Exception thrown : com.sas.ComponentException: com.sas.framework.webapp.util.TemplateFile.supportsRequiredInterfaces(): Exception loading interface class : com.sas.collection.StaticDictionaryInterface

The following behaviors might occur:

• SAS^® BI Dashboard might have missing OK and Cancel buttons and duplicate menus. It might also display the following error in the browser:

Error 500: ServletException in '/tiles-components/manageModels.jsp': com.sas.framework.webapp.util.TemplateFile.supportsRequiredInterfaces(): 
Exception loading interface class : com.sas.collection.StaticDictionaryInterface

• SAS^® Information Delivery Portal might display the following error after you supply login credentials in the browser:

A serious error occurred. Contact the portal administrator

• SAS^® Enterprise Guide^® might display the following error when saving a project to a SAS Folder:

Error in ProjectFile.CopyTo
SAS.EG.SDS.WebServices.WebServicesException: Query failed for services registry ---> System.Net.WebException: The request failed with HTTP status 407: Proxy Authentication Required.

If these errors occur, check to make sure that you followed the steps above correctly in setting the Classloader policy and mode.