Configuring the SAP Event Stream Processor SOAP Provider

Use the wsp.xml and axis2.xml configuration files to configure the ESP SOAP Provider.

1. In the %STREAMING_HOME%\wsp\wsp.xml file:
   Note When performing a custom installation of ESP, the installer sets cluster parameters in wsp.xml to the values provided during setup.
   1. Enable the ESP Web Services Providers by setting <webService enabled ="true">.
   2. Set the protocol and port number for the SOAP provider to which you are connecting the ESP SOAP Provider.
   3. Set cacheSize to the number of publishing transactions to make before comitting.
   4. (Optional) Edit the cluster information in the <DefaultCluster> section to avoid having to specify full connection details for the cluster each time you send a request. If you do not edit this section, the information for the cluster you created during the installation process is specified by default.

      Property	Description
      <Hostname>	(Required) Specify the name of the host on which the cluster resides.
      <Port>	(Required) Specify the cluster's port number.
      <Workspace>	(Required) Specify the workspace associated with the cluster. The default value is default.
      <Authtype>	(Required) Specify the authentication type.Valid values are user, rsa, and kerberos.
      <SslEnabled>	(Required) Specify whether SSL is enabled. Valid values are true or false.
      <projectLoading>	(Required) Specify the maximum number of socket connections (either publish or subscribe) to ESP to create for each project instance.

   5. If you are using HTTPS, specify the keystore type, file, and password in the <Security> section. If you are using HTTP, this section is ignored.
2. Edit the thread pool configuration that Jetty uses by editing the values in the <threadPool> section:
   1. In the <minThreads> parameter, specify the minimum number of threads you want Jetty to spawn. The default value is 20.
   2. In the <maxThreads> parameter, specify the maximum number of threads that Jetty may spawn to service incoming connections. The default value is 500.
   3. In the <idleTimeout> parameter, specify the amount of time, in milliseconds, that a threads needs to idle before becoming eligible to be stopped. The default value is 30000.
3. In your Web service client code, specify values for the authType and cred parameters. Valid values and syntax are:

   Authentication Type	Parameters and Values
   RSA	authType=rsa cred=keystore:user:password Note For the keystore parameter, enter the full path to the keystore file. If you are using Windows, surround the file path in single quotation marks.
   Username/Password	authType=user cred=user:password
   Kerberos	authType=kerberos cred=user:service:cache Note For the Kerberos parameter, enter the full path to the Kerberos cache file. If you are using Windows, surround the file path in single quotation marks.

   See the %STREAMING_HOME%\examples\java\wspexample\src\com\sybase\esp\wsp\example\WSPExample.java file for an example of Web service client code.

4. (If Kerberos authentication is enabled on the ESP Server) In the %STREAMING_HOME%\wsp\wsp.bat or $STREAMING_HOME/wsp/wsp.sh script, add:

   -Djava.security.krb5.realm=<RealmName> -Djava.security.krb5.kdc=<ServerName> 

5. In the %STREAMING_HOME%\wsp\webapps\axis2\WEB-INF\conf\axis2.xml file, set the HTTP and HTTPS listening ports for the SOAP server. For example:
   HTTP:

   <transportReceiver name="http" class="org.apache.axis2.transport.http.AxisServletListener">
                 <parameter name="port">9090</parameter>
          </transportReceiver>

   HTTPS:

   <transportReceiver name="https" class="org.apache.axis2.transport.http.AxisServletListener"> 
                 <parameter name="port">9443</parameter> 
          </transportReceiver>