Working with Exploded EAR Files in a Development Environment

It can be useful to run a SAS Web application from an exploded EAR file rather than an EAR file when you want to debug or develop new JavaServer Pages (JSP). SAS provides the Web applications as exploded EAR files in SAS-config-dir\Lev1\Web\Staging\exploded. Deployment of modified EAR files from an exploded directory varies with the Web application server as follows:
JBoss Application Server
JBoss has direct support for deployment of exploded EAR files. To deploy an exploded EAR file, move the exploded directory to the deploy_sas directory. Because the exploded directory name must be the same as the original EAR file, the original EAR file must be removed from the deployment directory.
Oracle WebLogic Server
WebLogic Server has direct support for deployment of exploded EAR files. To deploy an exploded EAR file using the WebLogic Server Administrative Console, select the full path to the exploded EAR.
IBM WebSphere Application Server
WebSphere Application Server explodes deployed EAR files on its own. Deployed files must be either EAR files or WAR files.
Starting with WebSphere Application Server 6.1, you can update an existing deployed application with individual files or modules. By selecting the full path to the JSP or WAR directory, individual components of a modified, exploded EAR file can be used in a deployed application. You can use the Integrated Solutions Console to update a deployed application.