NonStop SOAP 4.1 User's Manual

NOTE: The location specified for ICU_DATA must be a valid, existing location containing the
ICU files to be used for encoding. If the location does not exist, SOAP server logs an error message.
If the files in the given location are missing or corrupt, then encoding features will work only for
the UTF-8 encoding type.
Defining the Log File Size
The NonStop SOAP 4 server supports log and trace file rollover after the files reach a specific size.
The default file size is set to 20 MB, after which the logging and tracing rolls over for
soaperror.log and soaperror.log.trc files.
For specifying a different rollover size, set the LOG_SIZE OSS environment variable in the
itp_axis2.config file. The value must be numeric and the base unit is in MB. The minimum
value is 1, which indicates that the file size of 1 MB triggers a rollover.
CAUTION: A negative or zero value indicates that rollover must not be attempted. In this case
the file sizes can reach the maximum file size supported by the underlying file system. HP does
not recommend a negative or zero value for LOG_SIZE.
Defining Separate Log and Trace Files for NonStop SOAP 4 Servers
By default all the static and dynamic SOAP servers running in a specific iTP WebServer PATHMON
logs information to the same soaperror.log or soaperror.log.trc files.
To create separate log and trace files for individual NonStop SOAP 4 servers, in the
itp_axis2.config file, set the LOG_PER_PROCESS OSS environment variable to Yes. With
this setting, different files are created with the process name as a suffix to the log or trace file name.
The axis2.xml File
The axis2.xml file in the <NonStop SOAP 4 Installation Directory> directory is used
to configure a specific instance of a NonStop SOAP 4 deployment. The axis2.xml file is created
when the <NonStop SOAP 4 Deployment Directory>/bin/deploy.sh script is run to
deploy NonStop SOAP 4.
The configurations set in the axis2.xml configuration file are loaded during the NonStop SOAP
4 server startup, and applied to all the services deployed under the specific NonStop SOAP 4
deployment.
The axis2.xml file is used to perform the following tasks:
• “Setting the Message Receiver and the Message Exchange Pattern” (page 180)
• “Attaching a Module at the Global Level” (page 181)
• “Attaching Message Receiver User Functions at the Global Level” (page 181)
• “Specifying the Order of Phase Invocation in NonStop SOAP 4 Message Processing” (page 182)
Setting the Message Receiver and the Message Exchange Pattern
During startup, NonStop SOAP 4 reads the name of the Message Receiver class and the default
message exchange pattern (MEP) from the axis2.xml file.
NonStop SOAP 4 enables you to set the Message Receiver and the MEP to communicate with the
service. For more information about Message Receiver and Message Exchange Pattern, see
“Introduction to NonStop SOAP” (page 27).
You can set the Message Receiver and MEP using the class and mep attribute of the Message
Receiver elements in the axis2.xml configuration file as follows:
<messageReceiver class="message-receiver-class" mep="name of the mep"/>
where,
180 NonStop SOAP 4 Configuration Files