如何在WebLogic 12c中配置使用远程JMS提供者？

Hey folks, I get it—dealing with that outdated Oracle FAQ for cross-domain WebLogic JMS connections can be frustrating since it skips the actual "how-to" steps. Let's break this down: first I'll recap the critical info the FAQ lists you need, then fill in the missing configuration details you're probably hunting for.

FAQ Recap: Required Info for Remote JMS Communication #

Q. 建立与远程JMS提供者的通信需要哪些信息？
A. 建立与远程JMS提供者的通信需要以下信息：

• 目标类型：明确是队列（Queue）还是主题（Topic），这定义了JMS资源的核心类型
• 远程集群连接地址：远程WebLogic集群的监听URL（通常用T3协议，格式如 t3://remote-node-1:7001,remote-node-2:7001，多节点集群用逗号分隔）
• 认证凭据：远程WebLogic域中拥有JMS资源访问权限的用户名和密码
• JNDI名称：远程JMS连接工厂的JNDI路径，以及目标队列/主题的JNDI名称

Step-by-Step Configuration (WebLogic Console) #

Since the old FAQ skips these, here's how to actually set up the connection:

1. Create a Remote JMS Connection Factory #

• Log into your local WebLogic domain console, navigate to Services > Messaging > JMS Modules, and select your target JMS module.
• Click New > Connection Factory, give it a descriptive name, and select the Remote connection type.
• In the Connection URL field, paste the remote cluster's T3/T3s URL (use t3s for SSL-enabled connections).
• Enter the remote domain's username and password in the corresponding fields, then save the configuration.

2. Set Up a Foreign JMS Server (for Resource Mapping) #

• Still in your JMS module, click New > Foreign JMS Server.
• Configure the Initial Context Factory as weblogic.jndi.WLInitialContextFactory.
• Input the remote domain's JNDI connection URL and authentication credentials.
• Under the Foreign JMS Server, create a Foreign JMS Destination: map the remote target's JNDI name to a local JNDI alias. This lets your local apps use the alias to access the remote JMS resource without hardcoding remote details.

3. Validate the Connection #

• Use WebLogic's built-in JNDI Browser to test if you can look up the remote JMS resources via your local configuration.
• Deploy a simple test app (like a message sender/receiver) to confirm messages flow between domains successfully.

Key Notes #

• Ensure the remote cluster's firewall allows traffic on the T3/T3s port (default 7001 for plaintext, 7002 for SSL).
• The remote user account must be granted permissions for JMSConnectionFactory and JMSDestination resources in the remote domain.
• For SSL connections, import the remote domain's SSL certificate into your local domain's trust store to avoid handshake errors.

内容的提问来源于stack exchange，提问作者Tuomas Toivonen