Version 9.5 SP1
 —  Introduction to Web Services Stack  —

Installation Directories

Software AG Installer sets the Web Services Stack installation in several directories on the file system. Depending on the concrete usage of Web Services Stack in the means of different runtime or repository, you need to provide the corresponding configuration settings into different locations. This chapter outlines the available directory structures and the corresponding configuration files of the Web Services Stack that are set by the installer.


Web Services Stack Web Application

Software AG Installer sets a Web Services Stack installation that uses a Standalone Server into the \Software AG\WS-Stack directory on the file system. The table below outlines the contents of the subdirectories and the available configuration files of the Standalone Server.

\argus

Contains binary files and other resources needed by Web Services Stack SMH agents.

\bin

Contains batch files and shell scripts that facilitate the usage of Web Services Stack console utilities.

\conf

Contains the axis2.xml configuration file that is needed for the configuration of the Standalone Server.

\lib

Contains all third party libraries and libraries owned by Software AG that are needed for developing, building, and running of Web services artifacts (clients and services).

\miscellaneous

This directory contains all modules that have experimental or optional status and are not deployed by default. To use the content of the module, copy it manually into the Web Services Stack web application or into the Standalone Server repository that is in use by a given client.

For example, the Kandula2 module and the needed libraries are stored into the miscellaneous folder.

\repository

Contains the binary files and text configuration files that are needed on the client side and are spread in separate subdirectories

\repository\conf

Contains the axis2.xml configuration file that is needed to run the Web Service client applications on the Standalone Server.

\repository\modules

Contains the Web Services Stack modules that provide additional functionality to the Standalone Server. For example, security, reliable messaging, and so on. The modules are packed into Java archives and bear the module archives (MAR) file extension.

\repository\services

Contains the Web services either packed into Java archives bearing the Axis archive (AAR) file extension, or in an expanded directory structure. When you deploy a Web service on the Standalone Server, the corresponding .aar file is saved in this directory on the file system.

\webapp

Contains the Web Services Stack web application and a packed WAR file (wsstack.war) for an installation on a custom web application container

\webapp\wsstack\axis2-web

Contains the web resource files *.jsp, *.css, and *.inc that are used by the Standalone Server.

\webapp\wsstack\META-INF

Contains the MANIFEST.MF file for the web archive of the Standalone Server.

\webapp\wsstack\WEB-INF

Contains the web.xml (web application configuration descriptor file) of the Standalone Server.

Top of page

Web Services Stack Using a Platform Tomcat Server

Software AG Installer sets a Web Services Stack installation that uses a Platform Tomcat Server into multiple directories within the Software AG_directory directory. The table below outlines the contents of the subdirectories and the available configuration files of the Tomcat Server.

Software AG_directory\profiles\CTP\workspace\wsstack\repository\conf

Contains the axis2.xml configuration file that is needed to run the Web Service client applications on the Platform Tomcat Server.

Software AG_directory\profiles\CTP\workspace\wsstack\repository\modules

Contains the Web Services Stack modules that provide additional functionality to the Platform Tomcat Server. For example, security, reliable messaging, and so on. The modules are packed into Java archives and bear the module archives (MAR) file extension.

Software AG_directory\profiles\CTP\workspace\wsstack\repository\services

Contains the Web services either packed into Java archives bearing the Axis archive (AAR) file extension, or in an expanded directory structure. When you deploy a Web service on the Platform Tomcat Server, the corresponding .aar file is saved in this directory on the file system.

For additional information on deployment, see Deployment of the Runtime

Top of page