During execution of the validation step for SAS BI Portlets, you might see the following error message in the Instructions.html file:

Error 500: Filter [SanitizingRequestFilter]: could not be initialized.

To resolve this error:

1. Copy the sas.portlet.container.runtime.extensions.jar file from the /Lev1/Web/Staging/Exploded/sas.biportlets4.X.ear/lib directory to the WEBSPHERE-HOME/lib directory of the IBM WebSphere Application Server.
2. Restart the WebSphere application server.

Notes:

• These manual steps are required because of a limitation in the WebSphere application server.
• In UNIX operating environments, the JAR file must be copied using the same account that is used to install the WebSphere application server.

Alternative Method Using the IBM WebSphere Console Application

The following steps are an alternative method to resolve the error. The displays that are shown are from WebSphere 6.x, but they also apply to WebSphere 7.x.

1. Copy the sas.portlet.container.runtime.extensions.jar file into a folder similar to C:\AppServers\SharedLibraryITAADN.
2. Open the WebSphere console and navigate to Environment and Shared Libraries.
3. Choose the Cell scope (for example, Cell=SASDmgr01Cell).
4. Click New.
5. Set a name (for example, BIPortlets for the shared library and insert the full JAR file path in the Classpath field, as shown in the following display:








6. Click OK and save the configuration.
7. Select Servers ► Application Servers and select SASServer1.
8. In the Server Infrastructure category, expand Java and Process Management. Then, click Class loader.








9. Click New.
10. Leave the selection Class loaded with parent class loader first as is.
11. Click OK.
12. Click the new classloader_xxxxx link.
13. Click the Library Reference link.
14. Click Add and select BIPortlets for Library name.








15. Save the configuration.
16. Stop the deployment manager and the node agent.
17. Delete the sas.portlet.container.runtime.extensions.jar file from WebSphere-home-directory/lib if it exists.
18. Restart the deployment manager and node agent.

Operating System and Release Information