Maintaining the WSIF properties file

The Web Services Invocation Framework (WSIF) properties are stored in the wsif.jar file, in a properties file named wsif.properties.

 

Overview

The wsif.jar file is located in the install_root/lib directory, where install_root is the root directory for your installation of IBM WebSphere Application Server.

You must keep the "as shipped" wsif.properties file on the class path, so that WSIF can find it and the client administrator can use it to configure WSIF. However if you make any changes to the file, you do not replace the original copy in the wsif.jar file. Instead, you save the modified version in the install_root/lib/properties directory.

Here is a copy of the initial contents of the wsif.properties file. All the possible properties are listed and described.

 

Example

# Two properties are used to override which WSIFProvider is selected when there
# exists multiple providers supporting the same namespace URI. These properties are: 
#
#    wsif.provider.default.CLASSNAME=N
#    wsif.provider.uri.M.CLASSNAME=URI
#
# CLASSNAME is the WSIFProvider class name
# N is the number of following default wsif.provider.uri.M.CLASSNAME properties 
# M is a number from 1 to N to uniquely identify each wsif.provider.uri.M.CLASSNAME
#   property key.
# For example the following two properties would override the default SOAP provider 
# to be the Apache SOAP provider:
#
# wsif.provider.default.org.apache.wsif.providers.soap.ApacheSOAP.WSIFDynamicProvider_ApacheSOAP=1
# wsif.provider.uri.1.org.apache.wsif.providers.soap.ApacheSOAP.WSIFDynamicProvider_ApacheSOAP=\
# http://schemas.xmlsoap.org/wsdl/soap/
#

# maximum number of milliseconds to wait for a response to a synchronous request. 
# Default value if not defined is to wait forever.
# Timeout properties are only used by providers which support timeouts.
wsif.syncrequest.timeout=10000

# maximum number of seconds to wait for a response to an async request. 
# if not defined on invalid defaults to no timeout  
# Timeout properties are only used by providers which support timeouts.
wsif.asyncrequest.timeout=60

 

What to do next

To enable your legacy Web services to continue to work with WSIF, you might need to change the default WSIF SOAP provider back to the former Apache SOAP provider.

---

 

Related Tasks

Enabling security for WSIF
Troubleshooting the Web Services Invocation Framework
Changing the default WSIF SOAP provider

 

---