How Does Siebel EAI JMS Transport Service Handle Sending Requests To And Receiving Requests From JMS Queues When Multiple server:port Entries Are Defined In The jndi.properties File? (Doc ID 2209890.1)

Last updated on DECEMBER 15, 2023

Applies to:

Goal

QUESTIONS

1. Is it possible to access distributed queues from Siebel EAI JMS Transport business service?

2. Can Siebel support other than t3 client with WebLogic?

3. Can the url to the JMS load balancer in the jndi.properties file use https instead of http?

For example: java.naming.provider.url=https://active_passive_url.<DOMAIN_NAME>

4. What happens when there are multiple servers/ports listed for the java.naming.provider.url for Siebel EAI JMS Transport SendReceive method?

For example, if our jndi.properties file looks like this,

java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory
java.naming.provider.url=t3://server1:8011,server2:8011,server3:8011

Will the receiver component ever connect to server2 or server3? Or, will it disregard them?

5. What happens when there are multiple servers/ports listed for the java.naming.provider.url for Siebel EAI JMS Transport JMSReceiver component tasks?

For Siebel Inbound message handling through the receivers, if there are multiple Weblogic servers listed in the properties file (e.g. java.naming.provider.url=t3://server1:8011,server2:8011,server3:8011), how does Siebel poll each of these servers? Does it retrieve all the messages from server 1, then retrieve all messages from Server 2, then server 3, etc.?

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.