By Acshorten-Oracle on Oct 13, 2015
In last few releases of the Oracle Utilities Application Framework, a series of changes were introduced to enhance our Web Services capabilities. In summary the following changes were implemented:
- Inbound Web Services (IWS) was introduced to replace the XML Application Integration (XAI) capability. This basically allows web services to be housed and managed natively within the J2EE Web Application Server. This means that additional security and protocols are now supported for SOAP services such as Oracle Web Services Manager Support, WS-Policy Support and Web Services metrics.
- Inbound Web Services was delivered as a separately deployable component managed by the J2EE Web Application Server.
- The MPL was replaced with a set of Oracle Service Bus adapters and a native Message Driven Bean (MDB) for JMS inbound integration.
The new release extends these capabilities even further with the following enhancements:
- The Message Driven Bean (MDB) is now housed in the Inbound Web Services deployment rather than within the online server. This transforms the Inbound Web Services deployment to the role of an Integration Server. Long term technology integrations will be centralized in this Integration Server to support channel based configuration.
Note: Customers on IBM WebSphere should continue to use the current MDB implementation as the new MDB implementation is not supported on IBM WebSphere platforms.
- XAI supported legacy Maintenance Object based services, also known as Page Services, that implementations found difficult to convert to newer IWS based adapters. Inbound Web Services deployment has now been extended to automatically recognize these legacy services and make them available via the Inbound Web Services deployment. This means they can take advantage of the Inbound Web Services capabilities natively, facilitating migration from XAI to IWS. Note: This feature does not support XAI Inbound Services that use the Business Adapter as those should be converted to Inbound Web Services directly.
These are just the start on our long term plans for the Integration capability over the next few releases. Customers using XAI should migrate to the Inbound Web Services capability as soon as practical. Customers using MPL should also migrate to OSB/MDB as soon as practical. Both XAI and MPL have been announced as deprecated which freezes their functionality in anticipation of removal in a future release.