Integration with JMS queue from BizTalk 2013R2

Hi All,
We are planning to integrate biztalk application with Oracle Siebel CRM (8.1.1.11). they wanted to use JMS queue to receive xml message from BizTalk2013R2 and also send message to BizTalk for more reliability.
IS there any out of box adapter by which we can connect to their JMS queue.
We dont want to go with 3rd party software like jt adapter for JMS queue
Regards,
Manish
Manish

Hi Manish,
As of now there is no out-box-adapter for JMS queue.
If you don’t want JNBridge adapter (I hope you’re referring to same. There is no “jt” adapter as you mentioned), you can create a custom adapter which access the JMS queue.
Use WCF LOB adaper (WCF Lob
Adapter Wizard)and create an adapter.
Following article details about the .NET code for messaging with JMS queue, try the code.
Use JMS Messaging in your C# Applications
And following articles give details about using WCF LOB adapter/Wizard:
What Is the WCF LOB Adapter SDK?
Sample:
https://msdn.microsoft.com/en-us/library/bb798102.aspx
http://geekswithblogs.net/michaelstephenson/archive/2009/02/10/129302.aspx
Use similar code (one from above codeproject article where how to do messaging between JMS queue is shown) to wrapper it around custom WCF LOB adapter.
Give it a try, if you don’t want to spend anything on a 3rd party adapter.
Regards,
M.R.Ashwin Prabhu
If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

Similar Messages

ODI integration with JMS Queue

Hi,
I've been searching for some instructions on how to integrate ODI with JMS Queue but there's a distinct lack of information on the internet.
Can anybody point me to a step by step guide they have come across?
Any help is gratefully received.
Thanks
Gav

Hi Manish,
As of now there is no out-box-adapter for JMS queue.
If you don’t want JNBridge adapter (I hope you’re referring to same. There is no “jt” adapter as you mentioned), you can create a custom adapter which access the JMS queue.
Use WCF LOB adaper (WCF Lob
Adapter Wizard)and create an adapter.
Following article details about the .NET code for messaging with JMS queue, try the code.
Use JMS Messaging in your C# Applications
And following articles give details about using WCF LOB adapter/Wizard:
What Is the WCF LOB Adapter SDK?
Sample:
https://msdn.microsoft.com/en-us/library/bb798102.aspx
http://geekswithblogs.net/michaelstephenson/archive/2009/02/10/129302.aspx
Use similar code (one from above codeproject article where how to do messaging between JMS queue is shown) to wrapper it around custom WCF LOB adapter.
Give it a try, if you don’t want to spend anything on a 3rd party adapter.
Regards,
M.R.Ashwin Prabhu
If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

JCA Message Inflow Integration With JMS Queue

Hi,
I want to integrate JCA message inflows with JMS Queue. I know JCA Message Inflow destination can be Message Driven Bean. But is it possible to specify a JMS queue as destination of JCA Message Inflow.
i.e.
JCA -> MDB -> JMS Queue
OR
JCA -> JMS Queue
Thanks

Hi Manish,
As of now there is no out-box-adapter for JMS queue.
If you don’t want JNBridge adapter (I hope you’re referring to same. There is no “jt” adapter as you mentioned), you can create a custom adapter which access the JMS queue.
Use WCF LOB adaper (WCF Lob
Adapter Wizard)and create an adapter.
Following article details about the .NET code for messaging with JMS queue, try the code.
Use JMS Messaging in your C# Applications
And following articles give details about using WCF LOB adapter/Wizard:
What Is the WCF LOB Adapter SDK?
Sample:
https://msdn.microsoft.com/en-us/library/bb798102.aspx
http://geekswithblogs.net/michaelstephenson/archive/2009/02/10/129302.aspx
Use similar code (one from above codeproject article where how to do messaging between JMS queue is shown) to wrapper it around custom WCF LOB adapter.
Give it a try, if you don’t want to spend anything on a 3rd party adapter.
Regards,
M.R.Ashwin Prabhu
If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

Integration with JMS Weblogic server, Couldn't connect to any host

Hi ,
I am doing XI to JMS integration(weblogic JMS server) ,have created a communication channel of type JMS and gave the following parameters.
Transport Protocal : Access JMS Provider with JNDI
Message protocal : JMS 1.X
JNDI Lookup name with
queueconnectionfactory :MyJMSConnectionFactory
JNDI Lookup name with JMS Queue : MyJMSQueue
Name of JNDI initial context factory : weblogic.jndi.WLInitialContextFactory
JNDI Server Address: http://isccap:7001/
all these parameters are working fine when used in a Client java program by which i am able to put and retrive message from Weblogic JMS server queue.
But the same is not working in XI adapter ,
I am getting the following error in adapter monitoring
Zsrl_JMS_Reciever Receiver channel. Details: Couldn't connect to any host
I guess the problem is with JNDI Server Address: http://isccap:7001/
Is the format "http://host:port" correct for weblogic server,
are the JMS port and JNDI port same or different .
I have deployed the required drivers "wlclient.jar" in XI server .
Thanks in advance ,
srikanth Lanka

weblogic works on the Tenga3 protocol and hence the URL to connect to the JNDI provider of weblogic is
t3://host:port
At least in case of Weblogic you connect to your J2EE resources using your JNDI registry so the port would be the same.
Rgds,
Amol

Migration of JMS Queues from Weblogic 10.3 to 12c

Hi - We are currently planning to move our JMS Queues from existing 10.3 server to 12c and for the same we are looking for some feedback :
We need to define a rollback strategy in case our migration to 12c does not work well and we need to revert back to using weblogic 10.3. Are messages sent to weblogic 12c backward compatible with version 10.3? As part of rollback, business would want to drain out any remaining messages from 12c and feed them back to 10.3 queues to allow them for processing. Is this feasible? If yes then, could you please suggest how, If not then could you please suggest a strategy for rollback and process remaining messages in 12c?
We would also want to know if we can keep the same Database for both 10.3 and 12c JMS persistent stores for the same queues or should we define a completely new DB? With weblogic we can define prefixes for the DB stores which would make queue tables to have different names between 10.3 and 12c for same queues. However we are not sure if there are any other internal tables that JMS creates in the persistent stores DB, not using these prefixes, which would then corrupt the data since both 10.3 and 12c tables would be on the same DB.
Thanks
Nitin

Hello,
the final release for WLP is 10.3.6, running on WebLogic Server 10.3.6.
Emmanuel

Dynamic queue name with JMS Queue XML?

Hi,
Is it possible to use dynamic queue name with JMS Queue XML?
I tried using a variable in the JNDI URL, and supply the value in a package. I specified the following in the JNDI URL in the Topology:
e.g.
<JMS_RESOURCE>?d=<DTD_FILE>&s=<SCHEMA>&JMS_DESTINATION=#PROJECT_NAME.dest_var
I declared and set the variable in a package, then tried to load data from the above data server to database. But executing this package gave me the following error:
7000 : null : java.sql.SQLException: javax.jms.JMSException: Cannot find the target in JNDI (#PROJECT_NAME.dest_var)
java.sql.SQLException: javax.jms.JMSException: Cannot find the target in JNDI (#PROJECT_NAME.dest_var)
 at com.sunopsis.jdbc.driver.bg.executeQuery(bg.java)
 at com.sunopsis.jdbc.driver.bh.executeQuery(bh.java)
 at com.sunopsis.jdbc.driver.l.f(l.java)
 at com.sunopsis.jdbc.driver.l.executeUpdate(l.java)
 at com.sunopsis.sql.SnpsQuery.executeUpdate(SnpsQuery.java)
 at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execSrcOrders(SnpSessTaskSql.java)
 at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTaskTrt(SnpSessTaskSql.java)
 at com.sunopsis.dwg.dbobj.SnpSessTaskSqlC.treatTaskTrt(SnpSessTaskSqlC.java)
 at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java)
 at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java)
 at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java)
 at com.sunopsis.dwg.cmd.DwgCommandScenario.treatCommand(DwgCommandScenario.java)
 at com.sunopsis.dwg.cmd.DwgCommandBase.execute(DwgCommandBase.java)
 at com.sunopsis.dwg.cmd.e.i(e.java)
 at com.sunopsis.dwg.cmd.g.y(g.java)
 at com.sunopsis.dwg.cmd.e.run(e.java)
 at java.lang.Thread.run(Unknown Source)
Am I doing it wrongly?
Thanks!

hi,
as it's not in Adapter-Specific Message Properties
http://help.sap.com/saphelp_nw04/helpdata/en/10/b1b4c8575a6e47954ad63438d303e4/content.htm
looks like you cannot do it with jms adapter in standard
use proxy or your own adapter instead
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Need help to connect tibco jms queues from OSB

Hi,
We have a requirement in our project "to connect tibco JMS Queues from OSB".
The Queres are created by some othes in remote system, they provided us the details to connect the Queue. the detail are:
Queue Name :EXT_WEALTHHUB.TO_EXT.SYNC.REQ
Jndi Factory :SSLQueueConnectionFactory
and hostName , PORT
Credentails are provided.
We entered the same details in Business service in transport page by choosing 'jms' as protocol and EndpointURI as.
"jms://100.10.XX.YY:1234/SSLQueueConnectionFactory/EXT_WEALTHHUB.TO_EXT.SYNC.REQ"
And we created a service account to maintain the credentials and browsed the same at service account in the business service.
In JMS Transport Page we selected
Response Queue : One for all Request URI's
Response Pattern : JMS CorrelaltionID
Response UI :jms://100.10.XX.YY:1234/SSLQueueConnectionFactory/EXT_WEALTHHUB.TO_EXT.SYNC.RESP
when we are trying to establish a connection with the above queue getting
javax.naming.CommunicationException [Root exception is weblogic.socket.UnrecoverableConnectException: [Login failed for an unknown reason: er.deployer.MessageDrivenBeanInfoImpl.getInitialContext(MessageDrivenBeanInfoImpl.java:733)
 at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.getInitialContext(MessageDrivenBeanInfoImpl.java:689)
 at weblogic.jms.common.CDS$DD2Listener$1.run(CDS.java:1018)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
 at weblogic.jms.common.CrossDomainSecurityManager.runAs(CrossDomainSecurityManager.java:130)
 at weblogic.jms.common.CDS$DD2Listener.getInitialContextFromListener(CDS.java:1012)
 at weblogic.jms.common.CDS$DD2Listener.getInitialContext(CDS.java:984)
 at weblogic.jms.common.CDS$1.run(CDS.java:436)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
 at weblogic.jms.common.CrossDomainSecurityManager.runAs(CrossDomainSecurityManager.java:130)
 at weblogic.jms.common.CDS.createInitialContext(CDS.java:431)
 at weblogic.jms.common.CDS.getDDMembershipInformation(CDS.java:270)
 at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.createMDManagers(MessageDrivenBeanInfoImpl.java:1455)
 at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.activate(MessageDrivenBeanInfoImpl.java:1252)
 at weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1320)
 at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:493)
 at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227)
 at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:531)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
 at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:165)
 at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:157)
 at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
 at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
 at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
 at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
 at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
 at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
 at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
 at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
 at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
 at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
 at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
 at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
 at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
 at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
 at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
 at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
 at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: weblogic.socket.UnrecoverableConnectException: [Login failed for an unknown reason: in.checkLoginSuccess(Login.java:131)
 at weblogic.rjvm.t3.MuxableSocketT3.connect(MuxableSocketT3.java:403)
 at weblogic.rjvm.t3.ConnectionFactoryT3.createConnection(ConnectionFactoryT3.java:34)
 at weblogic.rjvm.ConnectionManager.createConnection(ConnectionManager.java:1777)
 at weblogic.rjvm.ConnectionManager.findOrCreateConnection(ConnectionManager.java:1417)
 at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:437)
 at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:316)
 at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:254)
 at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:197)
 at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:238)
 at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:200)
 at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:170)
 at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:153)
 at weblogic.jndi.WLInitialContextFactoryDelegate$1.run(WLInitialContextFactoryDelegate.java:345)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
 at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:340)
 at weblogic.jndi.Environment.getContext(Environment.java:315)
 at weblogic.jndi.Environment.getContext(Environment.java:285)
 at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
 at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
 at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
 at javax.naming.InitialContext.init(InitialContext.java:223)
 at javax.naming.InitialContext.<init>(InitialContext.java:198)
 at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl$2.run(MessageDrivenBeanInfoImpl.java:748)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
 at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.doPrivilagedAction(MessageDrivenBeanInfoImpl.java:2238)
 at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.getInitialContext(MessageDrivenBeanInfoImpl.java:733)
 at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.getInitialContext(MessageDrivenBeanInfoImpl.java:689)
 at weblogic.jms.common.CDS$DD2Listener$1.run(CDS.java:1018)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
 at weblogic.jms.common.CrossDomainSecurityManager.runAs(CrossDomainSecurityManager.java:130)
 at weblogic.jms.common.CDS$DD2Listener.getInitialContextFromListener(CDS.java:1012)
 at weblogic.jms.common.CDS$DD2Listener.getInitialContext(CDS.java:984)
 at weblogic.jms.common.CDS$1.run(CDS.java:436)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
 at weblogic.jms.common.CrossDomainSecurityManager.runAs(CrossDomainSecurityManager.java:130)
 at weblogic.jms.common.CDS.createInitialContext(CDS.java:431)
 at weblogic.jms.common.CDS.getDDMembershipInformation(CDS.java:270)
 at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.createMDManagers(MessageDrivenBeanInfoImpl.java:1455)
 at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.activate(MessageDrivenBeanInfoImpl.java:1252)
 at weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1320)
 at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:493)
 at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227)
 at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:532)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
 at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:165)
 at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:158)
 at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1269)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
 at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
 at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
 at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
 at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
 at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
 at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
 at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
 at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
 at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
 at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
 at weblogic.deploy.internal.targetserver.DeploymentM
Any pointers on how to resolve the above issue will be a greate help to us.
Thanks in Advance

Wrong forum, please ask this on dedicated weblogic or soa forums

How to view messages in Jms queue from OEM 12c Cloud Control

Hi All,
How can I view messages in a Jms queue from OEM 12c Cloud Control without logging into WebLogic Administration Console?
Thanks in Advance!!

EMCC 12c gets down to the JMS message queue/topic level in regards to the metrics being collected. It doesn't provide a view into the actual messages themselves. Are you trying to capture/track messages with a particular payload?

NoClassDefFoundError while accessing JMS Queue from JDev 10.1.3.3

Hi,
I'm trying to get a handle of a JMS queue, which resides on Oracle App Server 10.1.3.4, from a Java Program which I'm trying to run from JDeveloper 10.1.3.3.
I'm trying to make an RMI connection to the App server from JDeveloper by passing following information to the intialContext:
env.put("java.naming.factory.initial",
"oracle.j2ee.rmi.RMIInitialContextFactory");
env.put(Context.PROVIDER_URL,
"ormi://wafedabpelqa10.corp.weyer.pri:12402");
env.put("java.naming.security.principal","oc4jadmin");
env.put("java.naming.security.credentials","welcome1");
Where the above information is related to our App Server.
I'm successfully able to establish an RMI connection from JDev to Oracle App Server and can lookup datasources created on the App server using their
JNDI names. However if I try to look up a JMS Queue from the App server using its JNDI name, I get an error as:
java.lang.NoClassDefFoundError: oracle/tip/adapter/api/OracleConnectionFactory
I have also tried to use the value "com.evermind.server.rmi.RMIInitialContextFactory" for "java.naming.factory.initial",
however I still get the same error.

Hi,
this should work and you need to download the rmi library http://www.oracle.com/technology/software/products/ias/htdocs/utilsoft.html
thanks
# String queueName = "jms/MyJMSQueue";
# String queueConnectionFactoryName = "jms/MyJMSQCF";
# Context ctx;
# try {
# Properties parm = new Properties();
# parm.setProperty("java.naming.factory.initial","com.evermind.server.rmi.RMIInitialContextFactory");
# parm.setProperty("java.naming.provider.url","ormi://localhost:23791/");
# parm.setProperty("java.naming.security.principal","oc4jadmin");
# parm.setProperty("java.naming.security.credentials","welcome");
# ctx = new InitialContext(parm);
# QueueConnectionFactory connectionFactory =
# (QueueConnectionFactory)ctx.lookup(queueConnectionFactoryName);
# connection = connectionFactory.createQueueConnection();
# connection.start();
# session = connection.createQueueSession(false, Session.AUTO_ACKNOWLEDGE);
# queue = (Queue)ctx.lookup(queueName);
# sender = session.createSender(queue);
# receiver = session.createReceiver(queue);
# } catch (JMSException je) {
# throw new RuntimeException("Fout opgetreden bij het starten ",
# je);
# } catch (Throwable t) {
# throw new RuntimeException("Fout opgetreden bij het starten ",
# t);
# }

Writing to a JMS queue from Tux-service?

Greetings,
is there any way to write to a JMS-queue from a Tuxedo/atmi service without
using WebLogic Server (because of WTC needing it)?
Lara

Lara,
One way to write to a JMS-queue from a Tux service would be by using JNI functions.
Inside your server's tpsvrinit function you can create a JVM (using JVM_CreateJavaVM
function) and instantiate a couple of Java objects. You may then call Java methods
on these objects from your Tux services. At the server's tpsvrdone function you
must then destroy the Java objects and the JVM.
Regards,
Lazaros
"Lara Faiazza" <[email protected]> wrote:
Greetings,
is there any way to write to a JMS-queue from a Tuxedo/atmi service without
using WebLogic Server (because of WTC needing it)?
Lara

How to send to Weblogic 9.1 JMS queue from EJB running in Glassfish?

Hi.
I hope this is the correct forum.
I need to send a message to a jms queue on a remote weblogic 9.1 server. To this end I believe I will have to:
1) Install one or more weblogic client libraries/jar files on my glassfish application server. The weblogic server expects communication in the "t3" protocol, which I believe tunnels iiop, jms etc. inside their own proprietary protocol
2) Define the jms queue in my glassfish application server with a queue connection factory that creates the queue using classes from the weblogic jars?
3) Otherwise code the EJB methods sending messages as I would code and send messages to any jms queue
It's the first two steps that have me baffled. The more I dig in glassfish administrator's manual, the more confused I become.
Anybody have any idea if/how this can be accomplished?
Some reference to where I may find information as to how to accomplish this?
Thank you,
Jacob.

Jacob,
I suggest you try, either a GlassFish forum (http://forums.java.net/jive/forum.jspa?forumID=56), or perhaps the GenericJMSRA project https://genericjmsra.dev.java.net .This forum is primarily about the Sun JMS provider, Java MQ or Open MQ -- or the JMS Specification.
-- Ed Bratt

Receiving Unknown Byte Messages in JMS Queues from MDM 2.0

I am receiving unknown Byte messages in JMS CCB MDM Queue from MDM 2.0.
It keeps on increasing. Please let me know how to avoid this. and what may be the error.

Hi,
Set these flags with in your startup script like setDomainEnv.sh file or startWebLogic.sh file.
set these option near java_properties or options.
once you set please restart and one more point I missed here once you set these debug flags change the logging patter patter to debug mode under
server >> logging
change all the logging severity to debug mode and collect the debug.
Regards,
Kal

Use ODI with JMS Queue

I'm new user in ODI and also JMS. I successfuly use odi to integrate data from two oracle database applications. I'm trying to integrate applications using JMS Queues (or Topics) and I failed to create odi "data server" for this technology. Can someone help me to do this or give me a sample to follow it?
thanks.

Hi there,
You can actually create 2 different types of connections to a JMS Queue or Topic. Flat or XML. The simplest to start with is flat. This will basically cause ODI to view the contents of the queue as simple flat file data. Note, this is a bit advanced use of ODI, so I would perhaps go through connecting to an RDBMS first before walking through this. It will make more sense.
To set this up, you will need to:
1. Copy the necessary client files from OC4J, place them in the <ODI_HOME>/oracledi/drivers directory and restart ODI. The files you need are:
- <OC4J_HOME>/j2ee/home/oc4jclient.jar
- <OC4J_HOME>/j2ee/home/lib/javax77.jar
- <OC4J_HOME>/j2ee/home/lib/jta.jar
Sop copy those files and restart ODI.
2. Create a physical connection (Topology Application/Physical Architecture/Technologies -> right click JMS Queues and select "Insert Data Server")
3. In the Description tab, simpl fill in the Name field.
4. In the JNDI tab , fille in the following:
- JNDI Authentication - Simple
- JNDI User: application user - this is the equivalent of javax.naming.Context.SECURITY_PRINCIPAL
- Password: application password - this is the equivalent of javax.naming.Context.SECURITY_CREDENTIALS
- JNDI Driver: This is the equivalent of javax.naming.Context.INITIAL_CONTEXT_FACTORY, so enter com.evermind.server.rmi.RMIInitialContextFactory
- JNDI Url: This is the equivalent of javax.naming.Context.PROVIDER_URL, so put in ormi://<hostname>[:<port>]/<application>. For instance, with the basic OC4J install, I put in ormi://localhost/default.
- JNDI Resource: This is the JNDI lookup key for your Queue Connection factory. For example, for the default OC4J installation, I put in jms/QueueConnectionFactory
5. Click the Test button and click OK in the window that pops up. You should get a message box saying that your connection was successful.
6. Click Apply or OK and a new window will pop up. In this window, go to the Context tab and click the Add button and in the row that appears, click on the right most field (it says <Undefined> and replace <undefined> with a logical name for your connection. Hit Enter and click OK)
7. You've now connected to the Queue, to create the Queue object in ODI, go to the Designer window, go to models and create a new model.
8. Set the name to whatever makes sense to you. Set the technology to JMS Queue and the Logical Schema to the logical connection name you created in step 6. In the Reverse tab, select Global from the Context dropdown menu.
9. Click OK. You now have a container for any Queues that are in this connection.
10. To point to the queue, right click your new model and select Insert Datastore.
11. In the new window, name your datastore whatever you'd like. Set the resource name to the JNDI resource name for the queue (for example, with the default OC4J configuration, you could set this to jms/demoQueue.
12. In the Files tab, set the File Format to fixed, and set the record separator to Windows or Unix (it doesn't really matter which one you pick)
13. In the Columns tab, click the add button to add a column. Name the column something like DATA and set is to a String of size 1000.
14. Click OK. You'll now be able to right click this new datastore and view data, granted in a very simple format. You can create a more complex flat file structure if you' like but this gives you a quick and easy to view the contents of the queue.
I'd suggest trying to connect this way, post if you were successful and I will then post how to connect to an XML structured queue (it's a little teenie bit different)

Posting to JMS queue from WLI BPM 7.0

Hi,
I am trying to invoke a workflow process from a servlet by exchanging two JMS
messages.
I have configured my own JMS event queue com.bea.wli.bpm.EventQueueExt and generated
and installed the MDB for it as described in the docs. The servlet sends a XML
JMS to the normal com.bea.wli.bpm.EventQueue which starts the process. This half
works. The process then tries to send an XML to the newly configured queue - but
this fails.
The server console shows that there are absolutely no messages on my new queue.
The java servlet waits forever to receive on it and the workflow process instance
never completes the sending of the XML JMS.
I have attached the sample servlet code that I am trying this with. Would anyone
be able to spot what I am doing wrong?
1000 Thanks in advance,
Karsten
[BaseServlet.java]

Just wondering , why create a separate JMS server for this queue?
"Jared" <[email protected]> wrote in message
news:3f16dfde$[email protected]..
>
I am not sure if I exactly understand what you did -- but if you generatedanother
queue using the utility that WLI provided, I think you may be using itincorrectly.
That kind of queue is meant to be used in addition to the originalEventQueue
-- as an input queue to WLI. Maybe your messages were immediately sentback to
WLI -- in an attempt to start a workflow?
I would create a separate JMS server (from the WLI jms server) and createyour
queue on that server.
"Karsten " <[email protected]> wrote:
Hi,
I am trying to invoke a workflow process from a servlet by exchanging
two JMS
messages.
I have configured my own JMS event queue com.bea.wli.bpm.EventQueueExt
and generated
and installed the MDB for it as described in the docs. The servlet sends
a XML
JMS to the normal com.bea.wli.bpm.EventQueue which starts the process.
This half
works. The process then tries to send an XML to the newly configured
queue - but
this fails.
The server console shows that there are absolutely no messages on my
new queue.
The java servlet waits forever to receive on it and the workflow process
instance
never completes the sending of the XML JMS.
I have attached the sample servlet code that I am trying this with. Would
anyone
be able to spot what I am doing wrong?
1000 Thanks in advance,
Karsten

SAP SNC Supplier Network Collaboration integration with SAP ERP via BizTalk - experiences?

Hello,
had anybody experience in integration of SAP SNC Supplier Network Collaboration with SAP ERP via BizTalk Server?
Versions: SAP ECC 6.0 Ehp5 SPS11, SAP SNC current version (7.0?)
We will have to integrate following processes:
Master Data integration, PO Purchase Order, Forecast, SMI Supplier Managed Inventory
Usually SAP takes an SAP PI middleware for this, where the full implementation can be downloaded from the SAP marketplace, but we want to avoid having an additional Integration Platform with maintenance etc.
Are there experiences, success stories, pitfalls, issues to be known, recommendations, known efforts in this forum?
Thanks in advance.
Jens

HI Jens,
In our forum, we discussed topic about BizTalk & SAP Integration before, hope it helps you.BizTalk
& SAP Integration
Best regards,
Angie
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Integration with JMS queue from BizTalk 2013R2

Similar Messages

Maybe you are looking for