5-6 Oracle Fusion Middleware Third-Party Application Server Guide
For example, Jython scripts are not available to configure the Java Object Cache in a clustered environment.
5.3.2 Asynchronous Web Services
Asynchronous Web services are supported on platforms other than WebLogic Server. For asynchronous Web services to function, the following JMS default queues must be
present:
■
oracle.j2ee.ws.server.async.DefaultRequestQueue
■
oracle.j2ee.ws.server.async.DefaultResponseQueue
■
oracle.j2ee.ws.server.async.DefaultRequestErrorQueue
■
oracle.j2ee.ws.server.async.DefaultResponseErrorQueue
■
weblogic.jms.XAConnectionFactory To create these queues, you must configure Oracle JRF Asynchronous Web Services
using the Oracle Fusion Middleware Configuration Wizard. You do so in the Add Products to Cell screen in the Configuration Wizard as described in
Configuring Oracle WSM
on page 5-2. Once you have created or extended a cell with this template, the JMS queues are available for use.
5.3.3 JDeveloper
When using JDeveloper, the remote Oracle WSM policy store on a WebSphere server is not available.
5.4 Differences and Restrictions When Managing Web Services Components on IBM WebSphere
The following sections describe the differences and restrictions for managing Web services components on IBM WebSphere:
■
Automatic Discovery of Oracle WSM Policy Manager
■
Web Services Atomic Transactions
■
No Support for Native Web Services
■
Reliable Messaging
■
Enterprise Manager Fusion Middleware Control
5.4.1 Automatic Discovery of Oracle WSM Policy Manager
Automatic discovery of the Oracle WSM policy manager is not supported by third-party application servers, such as WebSphere. For details about connecting to the
policy manager, see Configuring Oracle WSM on IBM WebSphere
on page 5-2.
5.4.2 Web Services Atomic Transactions
Web Services Atomic Transactions WSAT are not supported and will result in runtime errors.
Managing Web Services on IBM WebSphere 5-7
5.4.3 No Support for Native Web Services
Native Web services, such as those that are deployed to a stack other than the Oracle Infrastructure Web Services stack, are not exposed in the WSIL. Only the deployed
Oracle Infrastructure Web Services are listed. The WSIL application is deployed on every server as part of the JRF template and the URI to access the application is
inspection.wsil. The wsil application uses basic HTTP authentication to ensure that only authorized users can access the list of Web services.
5.4.4 Reliable Messaging
WS-Reliable Messaging WS-RM is supported on IBM WebSphere with the following limitations:
■
WS-RM includes support for persistent database DB message store with Oracle databases only.
■
WS-RM supports clustering only when Coherence is installed and available. This behavior is the same as WebLogic Server on all the platforms where Coherence is
available.
5.4.5 Enterprise Manager Fusion Middleware Control
On IBM WebSphere, you access the Web services pages in Fusion Middleware Control using either of the following methods:
■
From the main WebSphere Cell menu, select Web Services, then the desired Web services page, as shown in
Figure 5–3 .
Figure 5–3 Web Services Menu
5-8 Oracle Fusion Middleware Third-Party Application Server Guide
■
In the navigation pane, right-click on the target cell name, then select Web Services
, then the desired Web services page. The following limitations and differences apply when managing Web services using
Fusion Middleware Control:
■
You cannot view or manage Web services at the server level.
■
The bulk policy attachment feature is not available.
■
The registered sources and services, and publish to UDDI features are not available.
■
The Application Deployment Summary page does not include the list of Web Services, or the Most Requested table.
■
Native WebSphere Web services are not supported.
■
The Usage Analysis page displays the WebSphere cell and server names.
5.5 Using the Web Services wsadmin Commands
