Customizing WSIF |  print-friendly version |
Customizing your WSIF installation
This part of documentation is meant to help developers who want to modify WSIF by adding or changing its providers and implementing new protocols.
There are many points within the WSIF API that allow for customization. An advanced WSIF sample demonstrates how to write your own WSIF service factory so that dynamic binding selection follows your own customized algorithm. The user can discover other customization points by examining WSIF's core API.
Larger scale customization involves finding ways to expose software that uses your proprietary protocols through WSDL, so that you can then access this software using WSIF's APIs. To do this, you need to take care of the following:
- Writing your own WSDL extensions to support new protocols
- Writing your own WSIF providers to support customized WSIF extensions
WSIF defines binding extensions so that EJBs, local java classes, software accessible over message queues using the JMS API and software that can be invoked using the Java Connector architecture can also be described in WSDL. WSIF is packaged with providers that allow transparent invocation of such software given the corresponding WSDL description. Here are the documents that describe these bindings:
- Local java binding extensions for WSDL
- EJB binding extensions for WSDL
- JMS binding extensions for WSDL
- JCA binding extensions for WSDL
You may find also useful to read about using Soap Attachments using WSIF and always important when debugging - how to use tracing in WSIF.
