Integration Queue
178
Integration Guide
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 <enterprise-beans> section in the ejb-jar.xml file, add the following
elements shown in bold text:
<enterprise-beans>
<message-driven id="MessageDriven_JMSContQueueProcessor_1">
<ejb-name>JMSContQueueProcessor-1</ejb-name>
<ejb-class>psdi.iface.jms.JMSContQueueProcessor</ejb-class>
<transaction-type>Container</transaction-type>
<message-driven-destination>
<destination-type>javax.jms.Queue</destination-type>
</message-driven-destination>
<env-entry>
<env-entry-name>MESSAGEPROCESSOR</env-entry-name>
<env-entry-type>java.lang.String </env-entry-type>
<env-entry-value>psdi.iface.jms.QueueToMaximoProcessor</env-
entry-value>
</env-entry>
<security-identity>
<run-as>
<role-name>maximouser</role-name>
</run-as>
</security-identity>
</message-driven>
To Next Page
Loading...