You must define a Web application to allow the Java container to locate the WSA.
Note: The steps below assume that the sample WSA Web application provided with OpenEdge is installed in the OpenEdge-Install-Directory/servlets/wsa directory.
To define a Web application for the WSA:
1. If you are running a production server, or if you do not want to lose your deployed Web services when installing another version of OpenEdge, copy the entire sample WSA Web application directory tree to another disk location, outside the OpenEdge installation directory. For an example of how this might be done see the information on copying the WSA sample Web application in Configuring a Web Services Adapter Installation.
2. Configure the Java container to recognize the WSA Web application. Depending upon the Java container, you might have to edit one of its configuration files or install the WSA Web application by using a browser-based administration interface. In addition, each Java container typically has a directory where a Web application resides. See your Java container vendor's documentation for the specific directory name and a discussion of Web applications.
Note: If a Web application installation procedure requests the path to the Web application deployment file, enter the path to the WSA Web application. For example, the Web application deployment path created during OpenEdge installation is OpenEdge-Install-Directory/servlets/wsa.
3. If you chose to enable security when you installed the WSA Web application sample, you must now define the WSA administration user names and roles in the Java container. For more information, see your Java container vendor's documentation. The WSA comes preconfigured to use the role definitions PSCAdmin and PSCOper (case-sensitive). With security enabled, the WSA requires the Java container to authenticate and authorize a user before passing the HTTP request to the Java container for handling. For more information on WSA security, see Web Services Adapter Security Configurations.
