To configure inbound JMS connections, you must edit the IntegrationGateway.properties file as described in the procedure.
Open the IntegrationGateWay.properties file from the following directory:
bea\wlserver6.1\config\peoplesoft\applications\PSIGW\WEB-INF |
where, bea is the WebLogic installation directory.
Edit the file for the JMS queue listener properties.
You can configure multiple queues by using the convention ig.jms.queue1, ig.jms.queue2, ig.jms.queue3, and so on. Configuring Inbound JMS Connections shows how the JMS listener is configured for the GenericOutQueue.
ig.jms.Queues=1 |
“1” indicates only one queue. |
|
ig.jms.Queue1=GenericOutQueue |
The first queue name “GenericOutQueue”, must be the same in the .bindings file. The Java code used to generate the entry in the .bindings is:
|
|
ig.jms.Queue1.Provider=SunSeeBeyond |
The “SunSeeBeyond” entry must match the configuration entry in the integrationgateway.properties file: ig.jms.JMSProvider.JNDIFactory.SeeBeyond=com.sun.jndi.fscontext.RefFSContextFactory |
|
ig.jms.Queue1.JMSFactory=QueueConnectionFactory |
“QueueConnectionFactory” is the JNDI name in the .bindings file. Use the following Java code to generate the entry:
|
|
ig.jms.Queue1.MessageSelector= | ||
ig.jms.Queue1.Url=file:c:/jndibindings/ |
The URL of the .bindings file. Because PeopleSoft only supports fcontext, this is a directory name. |
|
ig.jms.Queue1.User=Administrator |
User name to Enterprise Service Bus JMS server. |
|
ig.jms.Queue1.Password=SwBAuVVABok= |
Encrypted value of the password to Enterprise Service Bus JMS server. Use the PeopleSoft utility pscipher to get the encrypted value. |
Edit the file for the JMS queue listener properties.
You can configure multiple queues by using the convention ig.topic1, ig.topic2, ig.topic3, and so on. The table shows how to configure the JMS topic to use the GenericOutTopic.
ig.jms.Topics=1 |
“1” indicates only one topic. |
|
ig.jms.Topic1=GenericOutTopic |
The first topic name “GenericOutTopic”, must be the same in the .bindings file. The Java code to generate this entry in the .bindings is:
|
|
ig.jms.Topic1.Provider=SunSeeBeyond |
The “SunSeeBeyond” entry must match the configuration entry in the integrationgateway.properties file: ig.jms.JMSProvider.JNDIFactory.SeeBeyond=com.sun.jndi.fscontext.RefFSContextFactory |
|
ig.jms.Topic1.JMSFactory=TopicConnectionFactory |
“TopicConnectionFactory” is the JNDI name in the .bindings file. Use the following Java code to generate the entry: TopicConnectionFactory tgttcf = null;
|
|
ig.jms.Topic1.MessageSelector= |
Refer to the queue table. |
|
ig.jms.Topic1.Url=file:c:/jndibindings/ |
Refer to the queue table. |
|
ig.jms.Topic1.User=Administrator |
Refer to the queue table. |
|
ig.jms.Topic1.Password=SwBAuVVABok= |
Refer to the queue table. |