As shown in Figure 5, the WSA is implemented as a Java servlet that runs in the context of a Java container as a Web application. The Java container can run stand-alone (that is, with an integrated Web server), or in the context of an optional, separate Web server (such as Apache or IIS).
When the WSA runs within the context of a Java container or Web server, several WSA instances can run within the context of the WSA Web application (such as wsa1 and wsa2 shown in the above figure). In addition to the WSA Web application other Web applications can run within the Java container, including additional WSA instances.
The configuration of a Web server-based WSA is as follows:
Web server ( root )
Java container ( web-server-context )
WSA Web application ( wsa-webapp-context )
WSA instance ( wsa-instance )
...
...
Non-WSA Web application
...
...
Non-Java container Web resource, such as a static html page
...
...
In the Web server-based WSA configuration:
1. There is a separate Web server.
2. The Web server comprises one or more Java containers (web-server-context) and one or more non-Java container Web resources, such as static HTML pages.
3. Each Java container comprises one or more WSA Web applications (wsa-webapp-context) and one or more non-WSA Web applications.
4. Each WSA Web application comprises one or more WSA instances (wsa-instance).
If the Java container runs stand-alone (that is, with an integrated Web server), the Java container-based WSA configuration is as follows:
In both these configurations, web-server-context, wsa-webapp-context, and wsa-instance appear in bold because they are components of the URL for accessing the WSA.
