(Deprecated)Authorization for JMS renderings (deprecated)
To authorize use of the Business Process Choreographer
JMS API, security settings must be enabled in WebSphere® Application
Server.
Attention: The Business Process Choreographer
JMS API is deprecated. To develop JMS-based client applications, use
the Business Process Choreographer web services API with the SOAP/JMS
transport protocol.
When Business Flow Manager is configured, the role JMSAPIUser must be mapped to a user ID. This user ID is used to issue all JMS API requests. For example, if JMSAPIUser is mapped to "User A", all JMS API requests appear to the BPEL process engine to originate from "User A".
The JMSAPIUser role must be assigned the following authorities:
| Request | Required authorization |
|---|---|
| forceTerminate | Process administrator |
| sendEvent | Potential activity owner or process administrator |
Note: For all other requests, no special authorizations are
required.
Special authority is granted to a person with the role of business process administrator. A business process administrator is a special role; it is different from the process administrator of a process instance. A business process administrator has all privileges.
You cannot delete the user ID of the process starter from your
user registry while the process instance exists. If you delete this
user ID, the navigation of this process cannot continue. You receive
the following exception in the system log file:
no unique ID for: <user ID>
This topic only applies to BAW, and is located in the BAW repository. Last updated on 2025-03-13 12:15