IBM BPM, V8.0.1, All platforms > Programming IBM BPM > Developing client applications for BPEL processes and tasks > Developing JMS client applications (deprecated)
(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:
process instance. A business process administrator has all privileges. Request Required authorization 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>