IBM BJ0NJML Integration Guide - Page 192
Integration Queue, Configuring J2EE Restrictions
![]() |
View all IBM BJ0NJML manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 192 highlights
Integration Queue Integration Queue The Java Message Service (JMS) queues that are used by integration processing support basic J2EE security (user ID and password-based authentication and authorization). You can prevent unauthorized access to the queue by assigning a user ID and password to the Java Naming and Directory Interface (JNDI) Name, even if the JNDI name of the queue is known. Multiple queues can use the same or different user identifications. You can set these J2EE restrictions by using the server administrative console. Configuring J2EE Restrictions The following property names must be configured to enable J2EE restrictions. T java.naming.security.principal (for user identification) T java.naming.security.credentials (for password) To let the system integration producer and consumer programs access the queue, enter the same user ID and password in the Add/Modify Queues dialog box in the External Systems application. You access this dialog from the Select Action menu. For the continuous queue, update the message-driven bean (the consumer of the continuous queue) deployment descriptors as follows, to access a secured queue. 1 Under the section in the ejb-jar.xml file, add the following elements shown in bold text: JMSContQueueProcessor-1 psdi.iface.jms.JMSContQueueProcessor Container javax.jms.Queue MESSAGEPROCESSOR java.lang.String psdi.iface.jms.QueueToMaximoProcessor maximouser 178 Integration Guide
![](/manual_guide/products/ibm-bj0njml-integration-guide-77e799f/192.png)