Setting runtime properties

Properties such as the login provider or host name and port are specified with the madclient.properties file.

1. Create a text file called madclient.properties.
2. Type (or copy and paste) the following text into the madclient.properties file. Note that the value for hostPort corresponds to the value for WC_defaulthost or the WC_defaulthost_secure port defined in the IBM® WebSphere® Application Server Administration Console. If you choose the value for WC_defaulthost_secure port then the SSL properties will apply.

   loginProvider.classname=com.initiate.client.internal.DefaultLoginProvider
   loginProvider.username=
   loginProvider.password=
   contextFactory.hostName=localhost
   contextFactory.hostPort=9080
   contextFactory.useSSL=false
   contextFactory.secLib=SSL
   contextFactory.sslVersion=SSLv3
   contextFactory.sslCertVerify=false
   contextFactory.userName=
   contextFactory.password=
   contextPool.initialSize=0
   contextPool.maxSize=10
   contextPool.maxWaitMillis=-1
   soap.binding.version=1.1

   Adjust values to suit your environment. See Table 1 for a description of each property.

   Note: The ESOA web services can be deployed with SOAP version 1.1 or 1.2. The default is version 1.1. See the W3C specification for information about the difference between the versions. The version would need to change only based on a specific requirement within your environment.
   
   A version of the WSDL for both SOAP versions is included in the ISI_Client_xx.x.x package generated by InfoSphere® MDM Workbench in the \wsdl directory. If using SOAP version 1.2, use the madclient-soap12-dotnet.wsdl to generate the .NET client stubs.
3. To encrypt the password property in the madclient.properties file, use the WebSphere Application Server command PropFilePasswordEncoder.
   In the following commands, $NODE_HOME represents the home folder of the WebSphere Application Server node.

   • For Microsoft Windows systems, use the command:

     $NODE_HOME\bin\PropFilePasswordEncoder.bat file_path\madclient.properties loginProvider.password

   • For UNIX or Linux systems, use the command:

     $NODE_HOME/bin/PropFilePasswordEncoder.sh file_path/madclient.properties loginProvider.password

4. Browse to the directory that contains madclient.war file.
5. Create the subdirectory WEB-INF\classes.
6. Place the madclient.properties file in WEB-INF\classes.
7. On the command line, use the command
   jar uf madclient.war WEB-INF\classes\madclient.properties
   to embed the properties file in the WAR file. Alternatively, you can place the madclient.properties file in a common location accessible by the web application server.