IS XI Support BEA Weblogic JMS Queue

Hi
I have a scenario where i have to send and recive message from the Weblogic JMS Queue ..
Is XI support Weblogic JMS Queue ..if it is which tranport protocol i have to use to connect to Weblogic queue
SV

Hi
Thanks Ravi..
U mean to say i have to use the Transport Protocol
Access JMS Provider with JNDI
I have few more questions like ..
what needs to filled in Connection parameters:
JNDI Look up name of Queue Connection Factory:
JNDI Look up name of JMS Queue:
Name of JNDI Initial Context Factory:
JNDI Sever Address:
JNDI Logon User:
JNDI Logon Password:
When i selected the Protocol some default Values came in do i have have to change any thing
JNDI Look up name:
JNDI Look up name of JMS Queue:
Name of JNDI Initial Context:
as u mentioned in Server address i will put : t3://server:XXX
and i have given the user id and Password ..
the user id and password is same for both JNDI logon and JMS Queue User..
SV

Similar Messages

Connect from Weblogic JMS queue to SAP WAS JMS queue

Hi,
I am trying to setup a WLS 8.1 messaging bridge between a weblogic JMS queue and a SAP WAS JMS queue. I have configured a queue on both Weblogic and SAP WAS and I have set up the messaging bridge and bridge destintations in weblogic. However when weblogic tries to get the SAP initial context factory it fails with the error below.
I have added the SAP Client jars to the weblogic system classpath, and in the weblogic startup script but it still fails. Has anyone connected from an external JMS queue to a SAP WAS JMS queue that could provide me with some guidence?
<10/08/2006 08:23:45 AM WST> <Warning> <Connector> <BEA-190032> << Weblogic Mess
aging Bridge Adapter (XA)_eis/jms/WLSConnectionFactoryJNDIXA > ResourceAllocatio
nException of javax.resource.ResourceException: ConnectionFactory: failed to get
initial context (InitialContextFactory =com.sap.engine.services.jndi.InitialCon
textFactoryImpl, url = ux0800:55304, user name = username) on createManagedConnectio
n.>
Thanks
Warren

Stoyan,
Thanks for that.
My problem ended up being a classpath problem. I referenced the directory of the SAP jars in the weblogic start up script. When I changed this to reference each jar individually it worked.
I have a new issue now which may have something to do with security. The trace suggests it is logging on as the guest user, even though I entered my username and password in the Messaging bridge.
#1.5#000E7FED310600A30000008A0000302D00041AA399E338B4#1155189870559#com.sap.jms##com.sap.jms.server.sessioncontainer.InboundBus instance=BWIP#J2EE_GUEST#0####165536f0283611db8903000e7fed3106#SAPEngine_Application_Thread[impl:3]_126##0#0#Error##Plain###com.sap.jms.server.exception.JMSServerInvalidDestinationException: No destination with ID=0 found.
        at com.sap.jms.server.service.impl.RegistryServiceImpl.getDestinationContext(RegistryServiceImpl.java:404)
        at com.sap.jms.server.sessioncontainer.InboundBus.getDestinationContext(InboundBus.java:98)
        at com.sap.jms.server.sessioncontainer.InboundBus.process(InboundBus.java:153)
        at com.sap.jms.server.sessioncontainer.InboundBus.enqueue(InboundBus.java:116)
        at com.sap.jms.server.sessioncontainer.SessionContainer.receiveFromDispatcher(SessionContainer.java:63)
        at com.sap.jms.server.routingcontainer.RoutingContainer.receiveFromDispatcher(RoutingContainer.java:447)
        at com.sap.jms.server.JMSServerContainer.dispatchRequest(JMSServerContainer.java:635)
        at com.sap.jms.server.JMSServerFrame.request(JMSServerFrame.java:536)
        at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
        at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
        at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
        at java.security.AccessController.doPrivileged(Native Method)
        at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
        at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Warren

Error when trying to enqueue message on to weblogic JMS queue

Hi,
I have developed a BPEL process to enqueue message on to a JMS queue in weblogic 10.3.1.BPEL process manager version is 10.1.3.4. I have referred the Oracle note 549016.1 for configuring the Jms adapter for BEA Weblogic JMS Provider.
In the invoke activity, I am getting the following error:
"Missing class: weblogic.security.acl.UserInfo
Dependent class: weblogic.jndi.WLInitialContextFactory
Loader: JmsAdapter:0.0.0
Code-Source: /D:/product/10.1.3.1/orasoa/j2ee/oc4j_soa/connectors/JmsAdapter/JmsAdapter/weblogic.jar
Configuration: <code-source> in D:\product\10.1.3.1\orasoa\j2ee\oc4j_soa\connectors\JmsAdapter\JmsAdapter
The missing class is not available from any code-source or loader in the system."
I could not find a resolution. Please provide your inputs.
Thanks.
John

Could be this, if the above fix was by generating a wlfull client jar:
http://download.oracle.com/docs/cd/E14571_01/web.1111/e13717/jarbuilder.htm#BABCGHFH
Edited by: atheek1 on Jul 28, 2010 9:39 PM

Oracle PL/SQL send/receive message in weblogic jms queue

I am looking for a very simple way using oracle plsql to send and receive messages in a weblogic jms queues.
Thanks

Even i am looking for the same . Would be great if someone would help ..The jms setup has to be done in weblogic like the jms server, jms module, Jms connection factory , jms queue and then the jndi names . Now thw Problem here lies to me is that i really dont knw what should be the connection factory targets ,jndi names and where do i give the schema details as in the user name ,password , db name . Also if there is any explaination with eg on how to send /receive messages from a db trigger to jms queues .

Oracle PL/SQL procedure/function to post message into weblogic jms queue

Hi All,
Is it possible to post messages to weblogic JMS queue from pl/sql procedure/function?
From this Queue, message will be read by OSB interface.
Any help will be highly appreciated.
Regards,
Steve

904640 wrote:
Hi All,
Is it possible to post messages to weblogic JMS queue from pl/sql procedure/function?
From this Queue, message will be read by OSB interface.
Any help will be highly appreciated.
http://www.lmgtfy.com/?q=oracle+pl/sql+weblogic+jms+queue

Oracle PL/SQL procedure to post message into weblogic jms queue

Hi All,
Is it possible to post messages to weblogic JMS queue from pl/sql procedure/function?
From this Queue, message will be read by OSB interface.
Any help will be highly appreciated.
Regards,
Steve

904640 wrote:
Hi All,
Is it possible to post messages to weblogic JMS queue from pl/sql procedure/function?
From this Queue, message will be read by OSB interface.
Any help will be highly appreciated.
http://www.lmgtfy.com/?q=oracle+pl/sql+weblogic+jms+queue

Alsb trying to reach weblogic jms queues through VIP

Hi,
I have jms queues created in wLS. ALSB business service which puts the message into the queue .
ALSB and WLS are in 2 different boxes. When the end pointas follows jms://hostname:portnumber/connection factory/JNDI name is given the service is able to reach the Q.
The problem arises when VIP is used to connect to any of the queues in the box. the jms protocol is getting converted to "t3" protocol which is not understood by VIP and hence resulting in connection timed out exception .
Can anybody please help me to access jms queues through VIP from ALSB service .
Thanks in Advance ,
LKV

the jms protocol is getting converted to "t3" protocol which is not understood by VIP and hence resulting in connection timed out exception . Virtual IP as such doesnt influence anything...what it matters is what is listening at the Virtual IP, If you have configured weblogic server listen thread at this port then it should be able to understand t3.. Weblogic server's listen thread can interpret all supported protocol's ( http, t3, iiop, ldap etc) on its listen port...
So check at your wls side whether the server is listening at virtual ip and port. If you have firewall between alsb and wls then it could be an issue as firewalls can block certain protocols on an opened port..

About BEA WebLogic JMS on the cluster

Hi,
I have 3 files which together build in 1 EAR, then deploy on the cluster. I can see my message publish to the distributed topic successfully, but the listener process is not work. Could anyone give me a little clue.
// this one publish msg to the distributed topic.
import javax.naming.*;
import javax.jms.*;
import javax.rmi.PortableRemoteObject ;
import java.util.*;
public class PublishTopic {
public final static String JNDI_FACTORY = "weblogic.jndi.WLInitialContextFactory" ;
public final static String JMS_FACTORY = "weblogic.jws.jms.QueueConnectionFactory" ;
public final static String URL = "t3://localhost:7003,localhost:7005" ;
public final static String DIST_TOPIC = "dist_topic" ;
public String publishMsg(String s) throws Exception {
InitialContext ic = getInitialContext();
TopicConnectionFactory tcf = (TopicConnectionFactory) PortableRemoteObject.narrow
(ic.lookup(JMS_FACTORY),TopicConnectionFactory.class);
TopicConnection tc = tcf.createTopicConnection();
TopicSession ts = tc.createTopicSession(false,Session.AUTO_ACKNOWLEDGE);
Topic t = ts.createTopic(DIST_TOPIC);
TopicPublisher tpub = ts.createPublisher(t);
TextMessage msg = ts.createTextMessage(s);
tc.start();
tpub.publish(msg);
tc.close();
return "publish - : " + msg.getText();
public static InitialContext getInitialContext()throws NamingException {
Hashtable ht = new Hashtable();
ht.put(Context.INITIAL_CONTEXT_FACTORY, JNDI_FACTORY);
ht.put(Context.PROVIDER_URL,URL);
return new InitialContext(ht);
=================================================
// the listener one.
import javax.rmi.PortableRemoteObject ;
import java.util.HashMap;
import java.util.Date;
import javax.naming.*;
import javax.jms.*;
import java.io.*;
public class ListenMsg implements MessageListener {
private static HashMap hm ;
private static TopicConnection tcon ;
static {
// the coding inside static will process once every time
// class load. The code inside here should be
// 1. subscrib to the distributed topic
// 2. refresh the static var.
ListenMsg lm = new ListenMsg();
lm.retrieveDB();
lm.subscribTopic();
lm = null ;
public void onMessage(Message m) {
try {
PrintWriter p = new PrintWriter(new FileOutputStream
("C:/bea/user_projects/applications/TestJMS/JMSLog.txt",true));
p.println(new Date().toLocaleString());
p.println(((TextMessage)m).getText() + "\n");
// check to see the content of m then decide whether
// to call retrieveDB.
} catch (Exception e) {
} finally {
if (tcon != null)
try {
tcon.close();
} catch (Exception e) {}
private void retrieveDB () {
// connect to DB then select the allow/unallow-list.
private void subscribTopic(){
try {
InitialContext ic = PublishTopic.getInitialContext();
TopicConnectionFactory tcf = (TopicConnectionFactory) PortableRemoteObject.narrow
(ic.lookup(PublishTopic.JMS_FACTORY),TopicConnectionFactory.class);
tcon = tcf.createTopicConnection();
TopicSession tsess = tcon.createTopicSession(false,Session.AUTO_ACKNOWLEDGE);
// crateTopic doesn't actually create a new one but instead
// obtain a reference to the object which given name.
Topic t = tsess.createTopic(PublishTopic.DIST_TOPIC);
TopicSubscriber tsub = tsess.createSubscriber(t);
tsub.setMessageListener(this);
tcon.start();
} catch(JMSException je) {
je.printStackTrace();
} catch (NamingException ne) {
ne.printStackTrace();
} catch (Exception e) {
e.printStackTrace();
public boolean isAuthorized(String username, String servicename) {
// check against hm.
return true ;
===============================================
// the web service file.
public class TestPublish implements com.bea.jws.WebService
static final long serialVersionUID = 1L;
* @common:operation
public String sendMsg(String s) throws Exception {
String r = "";
try {
PublishTopic pt = new PublishTopic();
r = pt.publishMsg(s);
} catch(Exception e) {
e.printStackTrace();
throw e;
return r;
A big thanks in advance.
Tanin

Hi
Please verify that the listener points to the correct JNDI name
Do you see any error in the log ?
Jin

JMSML - XML Based Mark-Up Language for BEA WebLogic JMS and JMX

          JMSML is a Mark-Up language designed and developed to make Java Messaging Service
          (JMS) and Java Management Extensions (JMX) programming easy by hiding all the
          JMS and JMX Java API complexity behind a few, simple, easy to use XML tags.
          Both the White Paper and the binary download are available in dev2dev.beasys.com
          at the link below:
          http://dev2dev.beasys.com/resourcelibrary/whitepapers.jsp?highlight=whitepapers
          Regards
          [email protected]


Hi,
I finally managed to post a message to ActiveMQ 5.4.2 from WLS 10.3. I created a foreign JMS Server in WLS. I am not sure if you still have this issue, but I was facing this problem and managed to resolve it so posting the reply!
I placed the activemq-all-5.4.2.jar file in WLS server classpath.
The settings I used for the Foreign Server are:
General tab
JNDI Initial Context Factory: org.apache.activemq.jndi.ActiveMQInitialContextFactory
JNDI Connection URL: tcp://localhost:61616
Destinations Tab
Name: TestQueue
Local JNDI Name: TestQueue
Remote JNDI Name: dynamicQueues/TestQueue (I tried with a normal queue, but it didn't work. So used dynamicQueues here. Will try with other queue also)
Connection Factories Tab
Name: AMQConnectionFactory (
Local JNDI Name: AMQConnectionFactory
Remote JNDI Name: ConnectionFactory (This is default name given by Active MQ, you can change by adding names in jndi.properties file and placing it in config folder of ActiveMQ installation. Please check here: http://activemq.apache.org/jndi-support.html)
Using this configuration I was able to post message to ActiveMQ queue from Oracle Service Bus. One more issue to be taken care is that if the message type is not "Text" then the message body was coming as blank in ActiveMQ. So set the message type as "Text" explicitly.

Unable to post messages to Weblogic JMS queue

Hi All,
I am using weblogic 10.3.3.0, SOA and JDev 11.1.1.3.0.
(Weblogic came with JDev.)
I have created a JMS Server, JMS Module, ConnectonFactory and Queue in weblogic.
I am able to see that queue in my JDev and trying to enque some simple message as opaque data.
But I am getting below error while enqueuing.
CF: jms/PavanQueue/PavanQueueCF
QueueName: jms/Pavan4sQueue
<fault>
<bpelFault>
<faultType>0</faultType>
<bindingFault>
<part name="summary">
<summary>Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'Produce_Message' failed due to: JCA Binding Component connection issue. JCA Binding Component is unable to create an outbound JCA (CCI) connection. HelloWorldBPEL:EnqueueToMyQueue [ Produce_Message_ptt::Produce_Message(opaque) ] : The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: BINDING.JCA-12510 JCA Resource Adapter location error. Unable to locate the JCA Resource Adapter via .jca binding file element <connection-factory/> The JCA Binding Component is unable to startup the Resource Adapter specified in the <connection-factory/> element: location='jms/PavanQueue/PavanQueueCF'. The reason for this is most likely that either 1) the Resource Adapters RAR file has not been deployed successfully to the WebLogic Application server or 2) the '<jndi-name>' element in weblogic-ra.xml has not been set to jms/PavanQueue/PavanQueueCF. In the last case you will have to add a new WebLogic JCA connection factory (deploy a RAR). Please correct this and then restart the Application Server ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. </summary>
</part>
<part name="detail">
<detail>JCA Resource Adapter location error. Unable to locate the JCA Resource Adapter via .jca binding file element <connection-factory/> The JCA Binding Component is unable to startup the Resource Adapter specified in the <connection-factory/> element: location='jms/PavanQueue/PavanQueueCF'. The reason for this is most likely that either 1) the Resource Adapters RAR file has not been deployed successfully to the WebLogic Application server or 2) the '<jndi-name>' element in weblogic-ra.xml has not been set to jms/PavanQueue/PavanQueueCF. In the last case you will have to add a new WebLogic JCA connection factory (deploy a RAR). Please correct this and then restart the Application Server </detail>
</part>
<part name="code">
<code>12510</code>
</part>
</bindingFault>
</bpelFault>
</fault>I am able to see Weblogic-ra.xml files in 5 locations.
one in user_projects/....../JmsAdapter/../Meta-INF
and other in wlserver_10.3\server\lib JMS folders.
Which file I have to check. And I did not find any details about CFs or Queues in these XMLs.
Please show the way.
Regards
PavanKumar.M
Edited by: pavan4s on Sep 17, 2010 6:56 AM

Hi !
Did you add jms/PavanQueue/PavanQueueCF in the JMSAdapter outbound connection pools ?
Deployments > JMS Adapter > Configuration > Outbound connection pools
Add jms/PavanQueue/PavanQueueCF with the correct parameters.
Then, don't forget to redeploy the JMS Adapter.
Romain.

Bea weblogic jms server to sun seebeyond IQ Manager jms server

Dear All
I am working on Bea web logic webserver.
Now I want deploy message driven bean in it to listen remote queue, which resides in Sun see beyond IQ manager. So is it possible? If yes give me suggestion.
And both jms servers context was different.
Thanks
Vijay

I am seeing this same error. Was there any resolution to this? We are running WLS 8.1 SP3 on Solaris.
Thanks

Automatic failover not currently supported by WebLogic JMS?

          Hi,
          does this apply to Weblogic 8.1 as well? When will automatic failover be implemented?
          Thanks,
          A.


Hi,
          You can setup a "node manager" process to automatically
          restart a failing server, but there is no automatic
          fail-over to a new machine.
          To achieve automatic failover use
          third party HA framework software and disk replication
          software such as is supplied by Veritas. I'm not aware
          of any plans to add automated fail-over to the next release.
          Tom
          Iggy wrote:
          > Hi,
          >
          > does this apply to Weblogic 8.1 as well? When will automatic failover be implemented?
          >
          > Thanks,
          >
          > A.
          >
          >

Problem Connecting to JMS queue with C sharp client

Hi there,
I am trying to connect to a JMS queue using a C# client but i have a problem trying to connect. The problem comes in when i run the C# script a dialog box appears requesting a T3TransportFactory.cs which i do not have on the client. and when i close it i get an exception on
IContext context = ContextFactory.CreateContext(paramMap);
Exception - Failed to connect using URL <t3://10.103.130.18:7001>
StackTrace - at WebLogic.Messaging.Physical.T3TransportFactory.CreateT3Transport(IDictionary`2 paramMap) in c:\weblogic\dev\src1032\modules\weblogic-jms-dotnetclient\jmsimpl\src\WebLogic\Messaging\Physical\T3TransportFactory.cs:line 226
at WebLogic.Messaging.Physical.ContextPhysical.CreateContext(IDictionary`2 paramMap) in c:\weblogic\dev\src1032\modules\weblogic-jms-dotnetclient\jmsimpl\src\WebLogic\Messaging\Physical\ContextPhysical.cs:line 83
at WebLogic.Messaging.Context.CreateContext(IDictionary`2 paramMap) in c:\weblogic\dev\src1032\modules\weblogic-jms-dotnetclient\jmsimpl\src\WebLogic\Messaging\Context.cs:line 56
The stacktrace indicates that it is looking for a T3TransportFactory.cs file in that particular path on the client (This is my speculation) but this directory path does not exist on the client machine with the c# code.
I got a WebLogic.Messaging.dll referenced in my c# project and the ip/port numbers are correct (we know this cause we tried a java client that connected successfully)
Can anyone assist me on this issue?

The issue might be the dll file you are referring to. Did you use the dll from the weblogic installation folder (BEA_HOME/modules/com.bea.weblogic.jms.dotnetclient_1.X.X.X).
Refer - http://docs.oracle.com/cd/E15051_01/wls/docs103/jms_dotnet/install.html#wp1075258
Hope this helps.
Thanks,
Patrick

Using Weblogic JMS for internal delivery channel

hi,
I want my B2B to talk to back-end application through Weblogic JMS queues. I have configured internal delivery channel for this. I am getting error message 'Max retry exceeded' in b2b_idc_transport.log
2008.09.24 at 12:09:53:713: B2BStarter thread: (DEBUG) initialize TransportReceiver: [WLIOutbound_TServer < jms > < Wholesale >]
2008.09.24 at 12:09:53:713: B2BStarter thread: (DEBUG) JMSReceiver.init() started ....
2008.09.24 at 12:09:53:713: B2BStarter thread: (DEBUG) Establishing JMS Connection.
2008.09.24 at 12:10:03:704: B2BStarter thread: (DEBUG) Establishing JMS Connection.
2008.09.24 at 12:15:03:428: B2BStarter thread: (ERROR) Max retry exceeded, closing everything
java.lang.Exception: Max retry exceeded
     at oracle.tip.transport.basic.jms.JMSMonitor.reconnect(JMSMonitor.java:833)
     at oracle.tip.transport.basic.JMSReceiver.init(JMSReceiver.java:333)
     at oracle.tip.transport.b2b.B2BTransport.init(B2BTransport.java:379)
     at oracle.tip.adapter.b2b.transport.AppTransportInterface.initialize(AppTransportInterface.java:282)
     at oracle.tip.adapter.b2b.engine.Engine.initialize(Engine.java:512)
     at oracle.tip.adapter.b2b.init.B2BServer.initialize(B2BServer.java:280)
     at oracle.tip.adapter.b2b.init.B2BStarter.startB2B(B2BStarter.java:297)
     at oracle.tip.adapter.b2b.init.B2BStarter.run(B2BStarter.java:143)
     at java.lang.Thread.run(Thread.java:534)
I have applied latest patch 7322333.
kindly let me know what is workaround for this? also, how can do debugging of this issue in B2B.
Thanks in advance.
Regards,
Vaibhav
Edited by: vaibs on Sep 26, 2008 12:15 AM

hi Sinkar,
Thanks for reply. I have checked connectivity from b2b server to weblogic server, using java stub. Stub can connect to the Q successfully.
here is my b2b.log
2008.09.24 at 12:09:49:233: main: B2B - (DEBUG) B2B initialize
2008.09.24 at 12:09:49:233: Main thread: B2B - (DEBUG) This is Main thread executing..
2008.09.24 at 12:09:49:233: Main thread: B2B - (DEBUG) B2B start
2008.09.24 at 12:09:49:233: Main thread: B2B - (DEBUG) B2B start - context started
2008.09.24 at 12:09:49:233: B2BStarter thread: B2B - (DEBUG) B2BStarter - This is B2BStarter thread executing..
2008.09.24 at 12:09:49:233: B2BStarter thread: B2B - (DEBUG)
Maximum Heap Size = 530907136
Memory Allocated = 8323072
Free Memory = 842560
2008.09.24 at 12:09:50:544: B2BStarter thread: BusinessLogicLayer - (INFORMATION) ExecutionContextManager initialization is done
2008.09.24 at 12:09:50:544: B2BStarter thread: BusinessLogicLayer - (INFORMATION) User's maxCachedSessions is set to 0
2008.09.24 at 12:09:50:560: B2BStarter thread: B2B - (DEBUG) B2BStarter - Context Initialized
2008.09.24 at 12:09:51:762: B2BStarter thread: B2B - (DEBUG) B2BStarter - Start B2B
2008.09.24 at 12:09:51:762: B2BStarter thread: B2B - (DEBUG) B2BStarter - Starting B2B
2008.09.24 at 12:09:51:762: B2BStarter thread: B2B - (DEBUG) B2BStarter - configuration oained
2008.09.24 at 12:09:51:762: B2BStarter thread: B2B - (DEBUG) B2BStarter - clear global cache
2008.09.24 at 12:09:51:793: B2BStarter thread: B2B - (DEBUG) XEngine not running. So no need to clear cached objects inside XEngine.
2008.09.24 at 12:09:51:824: B2BStarter thread: B2B - (INFORMATION) Repository:print: [0] HL7 over MLLP Exchange
2008.09.24 at 12:09:51:824: B2BStarter thread: B2B - (INFORMATION) Repository:print: [1] EDI X12 over AS1
2008.09.24 at 12:09:51:824: B2BStarter thread: B2B - (INFORMATION) Repository:print: [2] Custom Document over Generic Exchange
2008.09.24 at 12:09:51:824: B2BStarter thread: B2B - (INFORMATION) Repository:print: [3] EDI EDIFACT over Generic Exchange
2008.09.24 at 12:09:51:824: B2BStarter thread: B2B - (INFORMATION) Repository:print: [4] RosettaNet over RNIF
2008.09.24 at 12:09:51:824: B2BStarter thread: B2B - (INFORMATION) Repository:print: [5] EDI X12 over Generic Exchange
2008.09.24 at 12:09:51:824: B2BStarter thread: B2B - (INFORMATION) Repository:print: [6] Custom Document over MLLP Exchange
2008.09.24 at 12:09:51:824: B2BStarter thread: B2B - (INFORMATION) Repository:print: [7] Custom Document over AS1
2008.09.24 at 12:09:51:824: B2BStarter thread: B2B - (INFORMATION) Repository:print: [8] EDI EDIFACT over AS1
2008.09.24 at 12:09:51:824: B2BStarter thread: B2B - (INFORMATION) Repository:print: [9] HL7 over Generic Exchange
2008.09.24 at 12:09:51:824: B2BStarter thread: B2B - (NIFORMATION) Repository:print: [10] Custom Document over Internet
2008.09.24 at 12:09:51:824: B2BStarter thread: B2B - (INFORMATION) Repository:print: [11] Custom Document over ebMS
2008.09.24 at 12:09:51:824: B2BStarter thread: B2B - (INFORMATION) Repository:print: [12] EDI X12 over Internet
2008.09.24 at 12:09:51:824: B2BStarter thread: B2B - (INFORMATION) Repository:print: [13] EDI EDIFACT over Internet
2008.09.24 at 12:09:51:981: B2BStarter thread: B2B - (DEBUG) Repository:constructCertSQL SELECT cert.ID, cert.CLASSTYPE FROM TIP_Certificate_ra cert, TIP_Party_ra party, TIP_DocumentExchange_ra docex WHERE cert.ID = docex.signingcredential AND cert.tradingpartner = party.ID AND party.ishosted != 'Y'
2008.09.24 at 12:09:52:355: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.ebms.EBMSExchangePlugin:initialize Enter
2008.09.24 at 12:09:52:355: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.ebms.EBMSExchangePlugin:header name: ebXML SOAP Envelope
2008.09.24 at 12:09:52:355: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.ebms.EBMSExchangePlugin:header name: ebXML SOAP Message Header
2008.09.24 at 12:09:52:386: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.ebms.EBMSExchangePlugin:initialize Exit
2008.09.24 at 12:09:52:402: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:initialize Enter
2008.09.24 at 12:09:52:433: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:initialize Exit
2008.09.24 at 12:09:52:511: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:initialize Enter
2008.09.24 at 12:09:52:511: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:initialize resetListener = true
2008.09.24 at 12:09:52:511: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:initialize initdcx = true
2008.09.24 at 12:09:52:543: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:initialize initialize TPAProcessor
2008.09.24 at 12:09:52:558: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:initialize Clear TPA Cache
2008.09.24 at 12:09:52:558: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:initialize initialize DataContext. Pool Size 0
2008.09.24 at 12:09:52:574: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:initialize Treat Response as Request = false
2008.09.24 at 12:09:52:574: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:initialize Exit
2008.09.24 at 12:09:52:574: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:initialize initialize Transport
2008.09.24 at 12:09:52:574: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.TransportInterface:initialize Initialize Transport Logger.
2008.09.24 at 12:09:52:574: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.TransportInterface:initialize Transport LogLevel = STATUS
2008.09.24 at 12:09:52:605: B2BStarter thread: B2B - (INFORMATION) Repository:getDeliveryEndPointList: Putting http://localhost
2008.09.24 at 12:09:52:605: B2BStarter thread: B2B - (INFORMATION) oracle.tip.adapter.b2b.transport.TransportInterface:initialize: Props: http://localhost port = 7777
PROTOCOL_ENDPOINT = null
2008.09.24 at 12:09:52:636: B2BStarter thread: B2B - (DEBUG) initialize TransportReceiver: [Wholesale_Transport_Server < http > < Wholesale >]
2008.09.24 at 12:09:53:682: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.AppTransportInterface:initialize Initialize AppTransport Logger.
2008.09.24 at 12:09:53:682: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.AppTransportInterface:initialize AppTransport LogLevel = WARNING
2008.09.24 at 12:09:53:698: B2BStarter thread: B2B - (INFORMATION) Repository:getInternalDeliveryEndPointList: Putting jms://[email protected]
2008.09.24 at 12:09:53:698: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.AppTransportInterface:initialize main Endpoint loop jms://[email protected]
2008.09.24 at 12:09:53:698: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.AppTransportInterface:initialize looping through transport Endpoint: jms://[email protected]
2008.09.24 at 12:09:53:698: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.AppTransportInterface:initialize add jms transport Endpoint: jms://[email protected] {Destination Provider Properties=java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory;java.naming.provider.url=t3://10.76.168.156:7010, jms.receiver.destination_password=weblogic, Connection Factory Location=weblogic.jws.jms.QueueConnectionFactory, jms.receiver.jndi_connection_factory_location=weblogic.jws.jms.QueueConnectionFactory, isTopic=false, Message Type=bytes, jms.receiver.is_topic=false, jms.receiver.factory_provider_properties=java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory;java.naming.provider.url=t3://10.76.168.156:7010, transport_callout_waittime=30, jms.receiver.jndi_destination_provider_properties=java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory;java.naming.provider.url=t3://10.76.168.156:7010, jms.receiver.polling_interval=10, polling_interval=10, Factory Provider Properties=java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory;java.naming.provider.url=t3://10.76.168.156:7010, jms.receiver.jndi_destination_location=[email protected], jms.receiver.destination_username=weblogic}
2008.09.24 at 12:09:53:713: B2BStarter thread: B2B - (DEBUG) initialize TransportReceiver: [WLIOutbound_TServer < jms > < Wholesale >]
2008.09.24 at 12:35:52:276: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:startListen Enter
2008.09.24 at 12:35:52:276: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:startListen Exit
2008.09.24 at 12:35:52:276: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:run Thread start
2008.09.24 at 12:35:52:276: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:initialize Exit
2008.09.24 at 12:35:52:276: B2BStarter thread: B2B - (DEBUG) B2BStarter - B2B initialized
2008.09.24 at 12:35:52:884: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:run initialize Enter
2008.09.24 at 12:35:53:087: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:run initialize B2BListen turned off, will not listen on IP_OUT_QUEUE for messages
2008.09.24 at 12:35:53:087: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:run start listening on message
Thanks,
Vaibhav
Edited by: vaibs on Sep 28, 2008 3:20 AM

Weblogic JMS authentication while sending or consuming message

I have to configure a weblogic jms queue in such a way when a remote sender send a message it has to connect using some authentication. Like when creating the initial context or the connectionFactory. But nowhere I got the steps for configuring it that way. Can you please let me know what is the out-of-the-box steps for achieving it. I am using all out-of the-box tools(no foreign jndi provider). Is it that the authentication comes as a default when you setup the connectionFactory. In that case is it the usercode/password of the weblogic server( or the subdeployment target, e.g. SOA server)

The discussion here might be useful for you:
Newbie question on securing JMS resources
Shortly, You need to create new user/group/roles in the security realm and configure the JMS destination for secured access based on roles. Then in the client code they need to pass the a valid user/password which has access to the destination.
Note: Weblogic doesn't honour the user id passed in the createConnection() call.. Instead what is checked is the JNDI Security_Principal passed when creating the intial context,, See the above link for details,
Edited by: atheek1 on May 25, 2010 4:17 PM

IS XI Support BEA Weblogic JMS Queue

Similar Messages

Maybe you are looking for