The installation and deployment of SAS Activity-Based Management release 7.1 with JBoss 4.3 as the web application server completes without error. However, attempts to log on to that SAS Activity-Based Management 7.1 server fail with the following error presented in an on-screen dialog box:

com.ctc.wstx.stax.WstxInputFactory cannot be cast to javax.xml.stream.XMLInputFactory

This error occurs because the application EAR includes a JAR file that was required for JBoss 4.2 but conflicts with JBoss 4.3.

The following steps correct the problem:

1. Stop the JBoss server to which SAS Activity-Based Management 7.1 is deployed. When using multiple Managed Servers, this is SASServer9.
2. Move <sas.activitybasedmanagement7.1.ear> from the JBoss managed server's <deploy_sas> directory to another location. The default path for deploy_sas in a multiple managed server deployment is

   <JBoss installation path>\jboss-as\server\SASServer9

   It is important to save a copy of the original file in case it is necessary to re-deploy in the future.
3. Locate the exploded <sas.activitybasedmanagement7.1.ear> directory in the

   <\Lev1\Web\Staging\exploded\>

   directory under the SAS configuration path on the mid-tier server. Copy the directory and its contents to the <deploy_sas> directory mentioned in step 2.
4. Remove the file <jsr173_api.jar> from the

   <deploy_sas\sas.activitybasedmanagement7.1.ear\lib\>

   directory.
5. Restart the managed server to which SAS Activity-Based Management 7.1 is deployed.

You should now be able to log on to the SAS Activity-Based Management 7.1 server.

Operating System and Release Information

Product Family	Product	System	Product Release		SAS Release
			Reported	Fixed*	Reported	Fixed*
SAS System	SAS Activity-Based Management	Microsoft Windows Server 2003 Datacenter Edition	7.1	7.11	9.2 TS2M3	9.3 TS1M0
		Microsoft Windows Server 2003 Enterprise Edition	7.1	7.11	9.2 TS2M3	9.3 TS1M0
		Microsoft Windows Server 2003 Standard Edition	7.1	7.11	9.2 TS2M3	9.3 TS1M0
		Microsoft Windows Server 2003 for x64	7.1	7.11	9.2 TS2M3	9.3 TS1M0
		Microsoft Windows Server 2008	7.1	7.11	9.2 TS2M3	9.3 TS1M0
		Microsoft Windows Server 2008 for x64	7.1	7.11	9.2 TS2M3	9.3 TS1M0
		Microsoft Windows XP Professional	7.1	7.11	9.2 TS2M3	9.3 TS1M0
		Windows 7 Enterprise 32 bit	7.1	7.11	9.2 TS2M3	9.3 TS1M0
		Windows 7 Enterprise x64	7.1	7.11	9.2 TS2M3	9.3 TS1M0
		Windows 7 Professional 32 bit	7.1	7.11	9.2 TS2M3	9.3 TS1M0
		Windows 7 Professional x64	7.1	7.11	9.2 TS2M3	9.3 TS1M0
		Windows 7 Ultimate 32 bit	7.1	7.11	9.2 TS2M3	9.3 TS1M0
		Windows 7 Ultimate x64	7.1	7.11	9.2 TS2M3	9.3 TS1M0
		Windows Vista	7.1	7.11	9.2 TS2M3	9.3 TS1M0
		Windows Vista for x64	7.1	7.11	9.2 TS2M3	9.3 TS1M0

* 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.

---

Installation and deployment complete without error. But, you are not able to log on to a SAS Activity-Based Management 7.1 server if the mid-tier server was deployed on JBoss 4.3. It is possible to circumvent the problem by removing a specific JAR file from the exploded application EAR file.

Type:	Installation Note
Priority:	alert

Date Modified:	2011-07-21 03:48:47
Date Created:	2010-12-22 14:09:39