Linking a WSIF service to the underlying implementation of the service
A Web Services Invocation Framework (WSIF) service is linked to the underlying service through a WSIF provider. A provider is an implementation of a WSDL binding that can run a WSDL operation through a binding-specific protocol. Providers implement the interface between the WSIF API and the implementation of a service.
Providers are pluggable within the WSIF framework, and are registered according to the namespace of the WSDL extension that they implement. Some providers use the Java EE programming model to use Java EE services. If a provider is available, but its required class libraries are not, then the provider is disabled.
To use the providers that are supplied with WebSphere Application Server, see the following topics:
Tasks
- Link a WSIF service to a SOAP over HTTP service.
- Link a WSIF service to a JMS-provided service (SOAP over JMS, or native JMS).
- Link a WSIF service to a local Java application.
- Write the WSDL extension that lets the WSIF service invoke an enterprise bean.
Subtopics
- Linking a WSIF service to a SOAP over HTTP service
The SOAP provider allows WSIF stubs and dynamic clients to invoke SOAP services. Add WSDL extensions to the web service WSDL file so that the service can use the SOAP provider.- Linking a WSIF service to a JMS-provided service
The JMS providers enable a WSIF service to be invoked through either SOAP over JMS, or native JMS. Add Web Services Description Language (WSDL) extensions to the web service WSDL file so that the service can use the JMS providers.- Writing the WSDL extension that lets the WSIF service invoke a method on a local Java object
Using the Web Services Invocation Framework (WSIF) Java provider, WSIF can invoke Java code. This means that, in a thin-client environment such as a JVM or Tomcat test runtime environment, we can define shortcuts to local Java programs. Use this procedure to help you to write the Web Services Description Language (WSDL) extension that links the WSIF service to a local Java application.- Writing the WSDL extension that lets the WSIF service invoke an enterprise bean
Using the EJB provider, WSIF clients can invoke enterprise beans through Remote Method Invocation over Internet Inter-ORB Protocol (RMI-IIOP). Use this information, and associated code fragments, to help you to write the WSDL extension that links the WSIF service to a service implemented as an enterprise bean.
Developing a WSIF service Interacting with the Java EE container in WAS Use complex types Use WSIF to bind a JNDI reference to a web service Running WSIF as a client