In the Linux operating environment, a SOAP error might be generated when all of the following conditions occur:

• SAS Content Server is deployed on IBM WebSphere Application Server.
• You are using either SAS^® Management Console or SAS^® Enterprise Guide^®.
• You perform either of the following tasks:
  • In SAS Management Console, you navigate to a report or an image, right-click the report or image, and select Properties. Note: On the Content tab in the Properties dialog box, you might see SOAP Exception.
  • You save a SAS Enterprise Guide project to SAS Folders.

The error that occurs is as follows:

[8/12/09 15:23:41:683 EDT] 000000d7 WebApp        E   [ServletError]-[spring-ws]: java.lang.NoClassDefFoundError:
com.sun.xml.wss.impl.SecurableSoapMessage (initialization failure)
        at java.lang.J9VMInternals.initialize(J9VMInternals.java:132)
        at com.sun.xml.wss.ProcessingContext.setSOAPMessage(ProcessingContext.java:217)

To resolve the issue, the xalan.jar file must be included in sas.wip.services9.2.ear. To include xalan.jar in the EAR file, follow these steps:

1. Navigate to a path similar to the following:
   /SAS/SASWebInfrastructurePlatform/9.2/Picklists/wars/sas.wip.soapservices
2. Copy the picklist file and save it as picklist.old.
3. Open the picklist file and add the Xalan lines in the positions shown below. (Note that the lines are alphabetical and the values use initial capitalization). The version must match the xalan.jar file that is found in a directory similar to the /SAS/SASVersionedJarRepository/9.2/eclipse/plugins/Xalan_2.7.0.0_SAS_20081023153039/xalan.jar.
   name=Slide_webdav version=2.2.0.pre1_SAS_20081023153045 name=Xalan version=2.7.0.0_SAS_20081023153039 name=XmlSchema version=1.2.0.0_SAS_20081023153127
4. Save the modified picklist.
5. Copy the file webAppExcludes_IBM_WIP_SOAPSERVICES.pattern and rename it webAppExcludes_IBM_WIP_SOAPSERVICES.pattern.old. The path in which this file resides should be similar to /SAS/SASDeploymentManager/9.2/products/cfgwizard__92210__prt__xx__sp0__1/Utilities/webAppExcludes_IBM_WIP_SOAPSERVICES.pattern.

   Note: If you have multiple cfgwizard directories,\ select the directory with the highest number because that is the latest version.

6. Open the webAppExcludes_IBM_WIP_SOAPSERVICES.pattern file and add comment delimiters to the xalan.jar line, as shown in this example:
   # **/xalan.jar
7. Rename the file sas.wip.services9.2.ear ( /SAS/Config/Lev1/Web/Staging) to sas.wip.services9.2.ear.old.
8. Rebuild the EAR file as follows:
   1. Invoke the SAS^® Deployment Wizard using the config.exe file that resides in a directory similar to /SAS/Software/SASDeploymentManager/9.2.
   2. Select English. Then click OK.
   3. Rebuild the web applications. Then click Next.
   4. Select Configuration Directory (which should be set, by default). Then click Next.
   5. Enter your password for the user ID sasadm@saspw. Then click Next.
   6. Select Web Infrastructure Platform 9.2. Then click Next.
   7. Click Start to build a new sas.wip.services9.2.ear file, which should be larger than the original file that you saved as sas.wip.services9.2.ear.old.
9. To ensure that the xalan.jar file is in the directory /WebInfrastructurePlatformServices9.2.ear/sas.wip.soapservices.war/WEB-INF/bin, you can use either the WinZip utility or JAR commands. To use JAR commands:
   1. Change your directory, as follows:
      cd /SAS/Config/Lev1/Web/Staging
   2. Submit the following JAR command to unpack the EAR file:
      jar xvf sas.wip.services9.2.ear
   3. Then submit the following command to list the files:
      jar tvf sas.wip.soapservices.war

      At this point, you should see the file xalan.jar in the WEB-INF/lib directory.

10. Use the WebSphere Administration Console to undeploy the old instance of sas.wip.services9.2.ear and deploy the newly rebuilt instance.

Operating System and Release Information