NonStop SOAP 4.1 User's Manual

GENERIC-CGI 1
HTTPD 1
NOTE:
• AXIS2CGI represents a server class name.
• A value of 1 for GENERIC-CGI or HTTPD indicates that iTP WebServer is running.
• A value of 0 for GENERIC-CGI or HTTPD indicates that iTP WebServer is not running
and an error number is displayed in the respective ERROR column. For more information
about the error and its resolution, see the NonStop TS/MP Pathsend and Server
Programming Manual.
After NonStop SOAP 4 is deployed and running, you can access the echo sample service. The
echo sample returns the same value in the response which you send in the request.
Accessing the echo service
To access the echo service, run the command-line client echo.exe. The echo.exe file is located
in the <NonStop SOAP 4 Deployment Directory>/client/echo directory.
OSS> cd <NonStop SOAP 4 Deployment Directory>/client/echo
OSS> ./echo.exe http://<ip address>:<port>/<url_pattern>/services/echo
The echo.exe file sends requests to the NonStop SOAP 4 server and displays the following output:
No CLIENT HOME specified. Using default AXIS2C_HOME=<NonStop SOAP 4 Deployment Directory>
Using endpoint : http://www.nonstopsoap.com/axis2c/services/echo
Sending OM : <ns1:echoString xmlns:ns1="http://ws.apache.org/axis2/services/echo
"><text>Hello</text></ns1:echoString>
Received OM : <ns1:echoString xmlns:ns1="http://ws.apache.org/axis2/c/samples"><
text>Hello</text></ns1:echoString>
echo client invoke SUCCESSFUL!
The echo sample generates echo.log and echo.log.trc log files in the <NonStop SOAP 4
Deployment Directory>/logs directory.
The echo.log file contains log messages from NonStop SOAP libraries. The log levels are set in
itp_axis2.config file. For information on setting the log levels, see “Defining the Log Levels
of the NonStop SOAP 4 Server” (page 178).
The echo.file.trc file contains the message processing details. The log contains both the entry
and exit points for functions in the order in which they are run. The messages in echo.file.trc
file are used for debugging the echo sample.
Setting up Multiple NonStop SOAP Deployment Instances in a Single iTP WebServer
To set up multiple deployment instances of NonStop SOAP to run in a single instance of iTP
WebServer, complete the following steps:
1. Create more than one NonStop SOAP deployment directories using deploy.sh script.“Setting
up the Deployment Environment” (page 38):
• <NonStop SOAP Deployment Directory 1>
• <NonStop SOAP Deployment Directory 2>
For multiple directories, you can create directories, such as NonStop SOAP Deployment
Directory 3, 4.....
Setting Up NonStop SOAP on a NonStop System 43