SUPPORT / SAMPLES & SAS NOTES
 

Support

Installation Note 50888: Using SAS® Digital Marketing 5.41 with Hot Fix F60008 or later with JBoss 5.1 is supported but requires manual updates after configuration

DetailsAboutRate It

Using SAS Digital Marketing 5.41 with JBoss 5.1 is supported with Hot Fix F60008 or later. However, manual updates are required after the initial installation and configuration and after each hot fix application. Attempting to use JBoss 5.1 without these changes results in the middle-tier components failing to start with the following error:

"vfsfile:/C:/jboss-eap-5.1/jboss-as/server/SASServer6/deploy_sas/sdm.war/" is in error due to the following
reason(s): org.xml.sax.SAXException: The content of element type "web-app" must match

To work around this problem, perform the following actions after you run sconfig as part of the installation or hot fix application and before you redeploy the newly configured bess.war and sdm.war files:

  1. Unzip the newly created sdm.war and bess.war files.
  2. Delete the xml-apis.jar file that is found in the sdm.war and bess.war files.
  3. Modify the web.xml file that is associated with the sdm.war file. Locate the folllowing in web.xml:

    <web-app> ... <filter/> <filter-mapping/> <filter/> <filter-mapping/> </web-app>

    Make the following changes so that all the <filter/> elements occur before all the <filter-mapping/> elements:

    <web-app> ... <filter/> <filter/> <filter-mapping/> <filter-mapping/> </web-app>

    Note that this update is NOT required for bess.war.

  4. Rezip the files.

Ensure that you deploy the corrected versions of the sdm.war and bess.war files to your JBoss web application server (or servers, in a double bess.war architecture) following your installation or hot fix installation instructions.



Operating System and Release Information

Product FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemSAS Digital MarketingMicrosoft® Windows® for x645.419.3 TS1M2
Microsoft Windows 8 Enterprise 32-bit5.419.3 TS1M2
Microsoft Windows 8 Enterprise x645.419.3 TS1M2
Microsoft Windows 8 Pro 32-bit5.419.3 TS1M2
Microsoft Windows 8 Pro x645.419.3 TS1M2
Microsoft Windows Server 2003 Datacenter Edition5.419.3 TS1M2
Microsoft Windows Server 2003 Enterprise Edition5.419.3 TS1M2
Microsoft Windows Server 2003 Standard Edition5.419.3 TS1M2
Microsoft Windows Server 2003 for x645.419.3 TS1M2
Microsoft Windows Server 20085.419.3 TS1M2
Microsoft Windows Server 2008 R25.419.3 TS1M2
Microsoft Windows Server 2008 for x645.419.3 TS1M2
Microsoft Windows Server 2012 Datacenter5.419.3 TS1M2
Microsoft Windows Server 2012 Std5.419.3 TS1M2
Microsoft Windows XP Professional5.419.3 TS1M2
Windows 7 Enterprise 32 bit5.419.3 TS1M2
Windows 7 Enterprise x645.419.3 TS1M2
Windows 7 Home Premium 32 bit5.419.3 TS1M2
Windows 7 Home Premium x645.419.3 TS1M2
Windows 7 Professional 32 bit5.419.3 TS1M2
Windows 7 Professional x645.419.3 TS1M2
Windows 7 Ultimate 32 bit5.419.3 TS1M2
Windows 7 Ultimate x645.419.3 TS1M2
Windows Vista5.419.3 TS1M2
Windows Vista for x645.419.3 TS1M2
64-bit Enabled AIX5.419.3 TS1M2
64-bit Enabled HP-UX5.419.3 TS1M2
64-bit Enabled Solaris5.419.3 TS1M2
HP-UX IPF5.419.3 TS1M2
Linux for x645.419.3 TS1M2
Solaris for x645.419.3 TS1M2
* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.