NonStop SOAP 4.1 User's Manual

OSS> cd /home/usr/mysdl
4. Generate the SDL file using the SoapAdminCL tool:
OSS> SoapAdminCL –e <SDL file name>
For example:
OSS> SoapAdminCL –e soapapp.sdl
The SoapAdminCL command extracts all the services defined in the SDR file and generates
the SDL file for the NonStop SOAP 3 application in the current directory.
NOTE:
• The default values of the Url and ServerAddress attributes in the sdl element are filled
in with default values of /axis2c and http://www.nonstopsoap.com respectively. You
must modify these values in the extracted SDL file so that it conforms to your NonStop SOAP
deployment environment.
• The DDL dictionaries must be available at the Guardian location specified in the
DDLDictionaryLocation attribute of the generated SDL file. If the DDL dictionaries are
not available, compile the DDL file to generate the DDL dictionaries at the location mentioned
in the DDLDictionaryLocation.
• You must have read access to the Guardian location where the DDL dictionaries are present.
Modifying the SDL File
After generating the SDL file, modify the Url and ServerAddress attributes in the sdl element
to the NonStop SOAP 4 deployment values.
To modify the SDL file, complete the following steps:
1. Add or update the value of the Url attribute in the SDL element to access the NonStop SOAP
4 service in the SDL file:
Url="/<url_pattern>"
For example:
<sdl Url="/axis2c" ServerAddress=”http://127.0.0.1:8080” >
where,
axis2c is the string entered for the <url_pattern> during the installation procedure.
2. Add or update the IP address and port number of iTP WebServer integrated with the NonStop
SOAP 4 deployment:
ServerAddress="http://<ip address>:<port>"
For example:
<sdl Url="/axis2c" ServerAddress=”http://127.0.0.1:8080” >
NOTE: You must retain the generated SDL file because NonStop SOAP 4 does not allow
you to generate the SDL file from the WSDL files.
Generating the HTML Client, WSDL, XML Schema, and services.xml Files to Deploy the Service
Generate the HTML client file, the WSDL file, XML schema files, and the services.xml file to
deploy the service in NonStop SOAP, using the SoapAdminCL tool:
OSS> SoapAdminCL –o <NonStop SOAP 4 Deployment Directory> -i <SDL file> -m
where,
-o <NonStop SOAP Deployment Directory>
specifies that the client and service must be created in the <NonStop SOAP 4.1 Deployment
Directory>.
54 Migrating NonStop SOAP 3 Services to NonStop SOAP 4 or Higher Versions