WAS v8.5 > Administer applications and their environment > Administer web services - Invocation framework (WSIF)Administer WSIF
An overview of where and how the Web Services Invocation Framework (WSIF) is installed as part of WebSphere Application Server, and information about configuring a WSIF client to invoke a web service through JMS, and modifying the contents of the wsif.properties file. WSIF is a thin abstraction layer between application code and the relevant invocation infrastructure.
WSIF is provided in a JAR file named com.ibm.ws.runtime.jar. The JAR file contains the WSIF classes, and the Java, EJB, SOAP over HTTP and SOAP over JMS providers. Additional providers are packaged as separate JAR files. When you install WAS, the com.ibm.ws.runtime.jar file is put on the WebSphere or JVM class path.
WSIF requires no further configuration, apart from the following administrative tasks:
- Enable a WSIF client to invoke a web service through JMS.
Use the dmgr console to configure the JMS resources (a queue destination and a queue connection factory) required to enable a service to be invoked through JMS by a WSIF client application.
- Modify the contents of the wsif.properties file.
You might have to modify the contents of this file, for example to change the default SOAP provider
Subtopics
- Enable a WSIF client to invoke a web service through JMS
The ways in which the Web Services Invocation Framework (WSIF) interacts with the JMS, and the steps to take to enable a service to be invoked through JMS by a WSIF client application.- wsif.properties file - Initial contents
The WSIF properties are stored in the com.ibm.ws.runtime.jar file, in a properties file named wsif.properties. You might have to modify the contents of this file, for example to change the default SOAP provider, so for reference here is a copy of the "as shipped" contents of the wsif.properties file.
Related concepts:
WSIF
Related
Change the default WSIF SOAP provider
Troubleshooting WSIF
Enable a WSIF client to invoke a web service through JMS