WSS contains a web application that can be deployed into any servlet container or application server that conforms to the Java Servlet Specification. The deployable web archive is called wsstack.war and comes with the installation.
The information is organized under the following headings:
The admin servlet is accessible at the following URL:
http://localhost:<port>/wsstack/
Note:
The default CTP port is 49981. In case of deployment in custom
application servers, the port is configured by the corresponding server
administration tools.
After the deployment of the deployable web archive, you can follow one of the links:
Services
See a list of the available deployed services. After installation, you
have deployed only the Version service (that gives
information for the version of Axis 2) and WSS.
Validate
Check whether the required libraries for the system are in place and
view system information.
Administration
Access the Axis 2 installation.
Web Service Stack distributes the bouncy castle JCE provider. It is required by the security module (Rampart) for retrieving cryptographic algorithms implementation used in encryption and/or signing of messages.
The bouncy castle provider is added to the run-time list of Java security providers (when required for the first time).
The bouncy castle provider might not be available to other web application if Web Service stack is deployed in a servlet container and the bouncy castle classes are loaded from the Web Services Stack web application classloader. Once added to the global list of security providers no other application running in the same virtual machine will be able to add it again. In this case, if the bouncy castle is required by other web application in the servlet container, place the bouncy castle JAR in a common/shared lib folder of the servlet container and ensure it is loaded from there and not by a web application classloader.
Note:
If Web Services Stack is undeployed, it will take care of
unregistering bouncy castle from the Java security providers list (only in case
it was loaded by the Web Services Stack webapp classloader). In this case, you
do not need to clean up the security providers or restart JRE.
This section describes the deployment steps for the different web containers.
The information is organized in the following topics:
If you want to deploy the WSS web application to your own Tomcat installation, perform the following steps:
To deploy to your own Tomcat installation
Stop Tomcat.
Make sure that the attribute
unpackWars is set to "true" in the
server.xml of your Tomcat installation.
Copy wsstack.war to the webapps folder of your Tomcat installation.
Start Tomcat. The content of wsstack.war is expanded into the wsstack folder under the webapps folder of the Tomcat installation.
If you want to deploy the WSS web application to JBoss, perform the following steps:
To deploy to JBoss
Stop JBoss.
Create a folder wsstack.war in the JBOSS-Installation\server\default\deploy folder.
Unzip the content of wsstack.war file into this wsstack.war folder.
Start JBoss.
If you want to deploy the Web Services Stack web application to BEA WebLogic, perform the following steps:
To deploy to BEA WebLogic
Stop the BEA WebLogic server.
Create a folder wsstack.war in the autodeploy folder of your domain (under Windows, for example, C:\bea10\wlserver_10.0\samples\domains\wl_server\autodeploy).
Unzip the content of wsstack.war file into this wsstack.war folder.
Start BEA WebLogic Server.
If you want to deploy the Web Services Stack web application to WebSphere 6, perform the following steps:
To deploy to WebSphere 6
Log on to the Administrative Console and navigate to the Applications >Install New Application node.
Enter the location of file wsstack.war or browse to it using the File chooser dialog.
Enter "wsstack" as Context root.
After installation, navigate to Applications > Enterprise Applications.
Click on wsstack_war to open the configuration dialog.
Click Class loading and update detection.
For Class loader order, choose "Classes loaded with application class loader first".
For WAR class loader policy, choose "Single class loader for application".
Navigate to Applications> Enterprise Applications.
Start the Web Services Stack web application.
If you want to deploy the Web Services Stack web application to WebSphere 7, perform the following steps:
To deploy to WebSphere 7
Copy <Web Services Stack_Install_Folder>/webapp/wsstack.war to a temporary location.
Unpack the WAR file
Copy all MAR files from WEB-INF/modules to WEB-INF/lib and change their extensions to JAR.
Important:
MS Office might constitute an issue with the mapping of MAR
files. When you have MS Office installed, you cannot rename those files using
Windows Explorer. In this case, use the command prompt ren
command. For example, <TEMP_Folder>\WEB-INF\modules>copy
addressing-1.41.mar ad dressing-1.41.jar copies the MAR file and changes
its extension from MAR to JAR.
Recreate the WAR file. You can use WinZIP or any other application with support for ZIP files.
Log on to the Administrative Console and navigate to the Applications ->Install New Application node.
Enter the location of file wsstack.war or browse to it using the File Chooser dialog.
Enter "wsstack" as Context root.
After installation, navigate to Applications > Enterprise Applications.
Click on wsstack_war to open the configuration dialog.
Click Class loading and update detection.
For Class loader order, choose "Classes loaded with application class loader first".
For WAR class loader policy, choose "Single class loader for application".
Navigate to Applications> Enterprise Applications.
Start the Web Services Stack web application.
If you want to deploy the Web Services Stack runtime to WebSphere Community Edition (Version 1), perform the following steps:
To deploy to WebSphere
Log on to the Administrative Console and navigate to the Applications/Deploy New node.
Enter the location of the wsstack.war or browse to it using the File chooser dialog.
Make sure the Redeploy application and Start app after install options are selected. Click Install.
