Last updated on AUGUST 18, 2016
Applies to:Oracle API Gateway - Version 126.96.36.199.0 to 188.8.131.52.1 [Release 11gR1]
Information in this document applies to any platform.
Using Oracle Enterprise Gateway 184.108.40.206.x.
A JMS service is configured, for example with IBM Websphere or WebLogic, as the JMS broker.
The patch for <Bug 13798494> - OEG DOES NOT START WHEN WEBSPHERE MQ IS UNAVAILABLE is applied.
- When the JMS broker is down, a configuration where OEG only sends to the JMS broker can be deployed. However, the JMS Service (which is the basis for all policies related to JMS) then cannot be initiated at policy deployment time.
This then requires some additional activity, such as restarting the gateway, or deploying the policies again once the JMS broker is available again.
- When the JMS broker is down, a configuration where OEG reads from the JMS broker cannot be deployed.
An example of the error messages shown from Policy Studio when WebLogic is used as the JMS broker is as follows:
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms