You must set up at least two UBE queues. This is required because Oracle's JD Edwards EnterpriseOne Adapter for WebSphere MQ relies on the use of a subsystem UBE (R00460). Like all subsystem UBEs, the R00460 operates in a permanent processing mode that consumes the queue in which it runs to an extent where no other UBE jobs running on the server can operate in the same queue. As a result, you must define at least two UBE queues, where one queue is dedicated to normal UBE processing and the other is dedicated to the JD Edwards EnterpriseOne Adapter for IBM WebSphere MQ subsystem.
This section describes:
Setting up the JD Edwards EnterpriseOne server to support multiple UBE queries.
Setting up a client to support the R00460 Subsystem UBE.
Configure the JD Edwards EnterpriseOne server to support additional UBE queues through the client to run the R00460 subsystem UBE.
If you submit or start the R00460 subsystem UBE from a JD Edwards EnterpriseOne Microsoft Windows client, you must temporarily modify that client's jde.ini file. The temporary modification is required so that the client can direct the R00460 subsystem to the appropriate UBE queue name. After the client submits or starts the R00460 subsystem UBE, you must undo the temporary change so that the client can regain access to normal UBE submissions to the server-based UBE queue.
On the client machine from which you want to submit or start the R00460 subsystem UBE, ensure the following jde.ini setting is correct:
| Parameter | Description |
|---|---|
| [NETWORK QUEUE SETTINGS]
UBEQueue= |
Defines the name of the local or server-based UBE queue.
If you want the client to start or submit the R00460 subsystem, enter a value that corresponds with the value set by the UBEQueue1= on the JD Edwards EnterpriseOne server. If you want the Microsoft Windows client to use the normal server-based UBE processing queue, enter a value that corresponds with the equivalent value for that queue on the JD Edwards EnterpriseOne server. |
Caution:
Any time you modify settings in the jde.ini file on the Microsoft Windows client, you must exit and restart JD Edwards EnterpriseOne in order for those changes to become effective.