Error in JMS Adapter for MQ series

We have configured a JMS Adpater to connect to MQ Serries queue manager running on our local server. The XI Server is a remote server where JMS adapter is deployed.
Upon deployment we see following string in JMS adapter log -
Sender channel. Details: com.ibm.mq.jms.MQQueueConnectionFactory
And the status of Adpater is RED.
The Adpater is configured in sender mode.
We have created a local queue in Queme Manger and a Server Connectio channel which is being used in adpater configuration.
Please suggest what could be the missing link here.
Appreciate if you can provide us link s to any docuemtn which details the steps to configure an MQ JMS adapter.
Thanks,
Garima

Hi Garima,
Please check the following:
1. Add dhbcore.jar also to aii_af_jmsproviderlib.sda and deploy it.
2. Check the existence of your JMS drivers.
3. Check the following link and Install the drivers as the way it is mentioned in the guide 'How To Install And Configure External Drivers For JDBC & JMS'
https://websmp204.sap-ag.de/~form/sapnet?_SHORTKEY=01200252310000071155&_SCENARIO=01100035870000000202
There are 4 files which needs to be added. http://help.sap.com/saphelp_nw04/helpdata/en/cd/d85a9d6fab7d4dbb7ae421f710626c/frameset.htm
Any of the above solutions should help you solve the problem.
Regards,
Abhy

Similar Messages

Error in JMS Adapter Configuration.

Hi,
Its regarding JMS receiver adapter for MQ Series.
We have MQ 6.0 installed on PI server. While trying to connect thorough JMS receiver adapter we are getting a connection failure error at communication channel level.
The MQ administrator is of the opinion that as MQ is local to the PI server a channel is not required.
In the MQ server, the administrator has created a Manager and Queue which we are using in the JMS receiver channel.
We have provided the queue connection factory as the default one used for MQ 5.3
class also as the default. (All the extra jar files required for MQ 6.0 is deployed).
The error description says:
Error during channel initialization; exception trace: javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for '10.23.86.134:XBEIG_QMGR1'
at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:586)
at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:2110)
at com.ibm.mq.jms.MQConnection.createQMNonXA(MQConnection.java:1532)
com.ibm.mq.MQException: MQJE001: An MQException occurred: Completion Code 2, Reason 2059
MQJE011: Socket connection attempt refused.
Any inputs would be very helpful...
Many Thanks,
Rosine.

you can check the SAP Note 856346 - FAQ on JMS adapter it might have some info

The problem of creating service for adapter for mq series v8.1

Hi everyone, I have some problem when I try to create service for adapter for mq series using application integration design console. Everything is fine when I define the service but some error shows when I try to test it. The error message is:
-------- Begin level 0 Exception Stack Trace --------
com.bea.wlai.client.ApplicationViewException: Failed to locate deployment information for service ' on ApplicationView 'AppView1'
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:186)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:290)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:247)
at __WLAdapter4MQSeries_Prototype_48f240ab.AppView1_6k4mbt_EOImpl_814_WLStub.getRequestDocumentDefinition(Unknown Source)
at com.bea.wlai.client.ApplicationView.getRequestDocumentDefinition(ApplicationView.java:573)
at jsp_servlet.__testrslt._jspService(__testrslt.java:361)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:33)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1006)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:419)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:315)
at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:638)
at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:423)
at weblogic.servlet.jsp.PageContextImpl.include(PageContextImpl.java:154)
at jsp_servlet.__display._jspService(__display.java:659)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:33)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1006)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:419)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:315)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6718)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3764)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2644)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
-------- End level 0 Exception Stack Trace --------
And my request document is:
<?xml version="1.0"?>
<ns0:s1 xmlns:ns0="wlai/AppView1_s1_request">
<Data>123</Data>
</ns0:s1>
The following is the schema for the request document:
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema elementFormDefault="qualified"
targetNamespace="wlai/AppView1_s1_request"
xmlns="wlai/AppView1_s1_request"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="s1">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Data"
type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
Anybody got some idea about this problem? Thanks for your help.

Did you check these links ->
http://www.adp-gmbh.ch/ora/admin/creatingdbmanually.html
http://www.dbasupport.com/oracle/ora10g/CreateDBManually.shtml
http://download.oracle.com/docs/cd/B19306_01/server.102/b14231/create.htm#ADMIN002
Regards.
Satyaki De

JMS Adapter (for DI) does not allow passing username and password to JMS connection

Post Author: PLed76
CA Forum: Data Integration
JMS Adapter (for DI) does not allow passing username and password to JMS connection. It has those fields only for MSMQ. Our Production environment does not allow us to connect to JMS (we use Tibco EMS) anonymously, so it prevents us from use of Data Integrator. Is there any way to pass those params, or obtain the correct version of JMS Adapter, or obtain source codes of the JMS Adapter so we can correct them ourselves (we can send you the corrected sources back) ? Thanks in advance for any help. (PL)ed76 Renaissance Capital

Bump - Were having the same issue.
Has anyone found a way to connect to Tibco with a user/pwd?
Version 14.0.297.

JMS Adapter for TIBCO BUSINESS WORKS v5.6

Hi,
We have a requirement to send a data from BI system to TIBCO BUSINESS WORKS via PI 7.1.
We are suggested to to use JMS adapter for connecting TIBCO BUSINESS WORKS. I searched in the forum, but could not find any related thread for TIBCO BUSINES WORK.
Please share your experience on TIBCO BUSINES WORK with SAP PI with JMS adapter.
1. How to get the drivers of TIBCO and installed it in Java stack
2. What is the Transport protocol??
3. Queue name,server etc?
4. XSD file for receiver. ( Hope, 3rd party ll provide )
Thanks in advance
Regards
Baskaran K

Selvam,
It was long time before I did.. I guess I did added com.sap.aii.adapter.lib_api.jar file as well in addition to the required driver files.
Cheers
Agasthuri

Anyone successfully deployed BPEL + JMS Adapter (for MQ) to WebSphere?

Anyone successfully deployed BPEL Process Manager + JMS Adapter (for MQ) to WebSphere (i.e not OAS/OC4J)?
If you have - I would love to see a valid example of the ra.xml and oc4j-ra.xml files in your jca/JmsAdapter.rar file - to see how you configured access for the JMS Adapter to your remote MQ queues.
Thank you
Dennis

Hi Garima,
Please check the following:
1. Add dhbcore.jar also to aii_af_jmsproviderlib.sda and deploy it.
2. Check the existence of your JMS drivers.
3. Check the following link and Install the drivers as the way it is mentioned in the guide 'How To Install And Configure External Drivers For JDBC & JMS'
https://websmp204.sap-ag.de/~form/sapnet?_SHORTKEY=01200252310000071155&_SCENARIO=01100035870000000202
There are 4 files which needs to be added. http://help.sap.com/saphelp_nw04/helpdata/en/cd/d85a9d6fab7d4dbb7ae421f710626c/frameset.htm
Any of the above solutions should help you solve the problem.
Regards,
Abhy

Configuring JMS adapter for a BPEL process which puts a msg in a Q of MQ

Hi,
I am trying to develop a BPEL process which picks up a message from a Q in Websphere MQ and puts that message in another Q of MQ after processing that.
I have updated the oc4j-ra.xml with the following inputs:
<connector-factory location="eis/MQSeries/Queue" connector-name="Jms Adapter">
          <config-property name="connectionFactoryLocation" value="com.ibm.mq.jms.MQQueueConnectionFactory"/>
          <config-property name="factoryProperties" value="QueueManager=TestManager;TransportType=1;Hostname=machine's ip address;Port=1414;Channel=channel name for connecting to client"/>
          <config-property name="acknowledgeMode" value="AUTO_ACKNOWLEDGE"/>
          <config-property name="isTopic" value="false"/>
          <config-property name="isTransacted" value="true"/>
          <config-property name="username" value="admin"/>
          <config-property name="password" value="welcome"/>
     </connector-factory>
But while testing the BPEL process, I get the error:
<remoteFault>
<part name="code" >
<code>null</code>
</part>
<part name="summary" >
<summary>file:/D:/OraBPELPM_2/integration/orabpel/domains/default/tmp/.bpel_MQMessaging_1.0.jar/Outbound.wsdl [ Produce_Message_ptt::Produce_Message(SourceEmployee) ] - WSIF JCA Execute of operation 'Produce_Message' failed due to: Adapter Framework unable to create outbound JCA connection. file:/D:/OraBPELPM_2/integration/orabpel/domains/default/tmp/.bpel_MQMessaging_1.0.jar/Outbound.wsdl [ Produce_Message_ptt::Produce_Message(SourceEmployee) ] - : The Adapter Framework was unable to establish an outbound JCA connection due to the following issue: ORABPEL-12141 ERRJMS_CONN_FAC_NOT_FOUND. Unable to instantiate connection factory. JMS adapter was unable to look up the connection factor com.ibm.mq.jms.MQQueueConnectionFactory neither through JNDI nor instantiate it as a Java class Please examine the log file to determine the problem. ; nested exception is: ORABPEL-12511 Adapter Framework unable to create outbound JCA connection. file:/D:/OraBPELPM_2/integration/orabpel/domains/default/tmp/.bpel_MQMessaging_1.0.jar/Outbound.wsdl [ Produce_Message_ptt::Produce_Message(SourceEmployee) ] - : The Adapter Framework was unable to establish an outbound JCA connection due to the following issue: ORABPEL-12141 ERRJMS_CONN_FAC_NOT_FOUND. Unable to instantiate connection factory. JMS adapter was unable to look up the connection factor com.ibm.mq.jms.MQQueueConnectionFactory neither through JNDI nor instantiate it as a Java class Please examine the log file to determine the problem. Please examine the log file for any reasons. Enable DEBUG logging in the BPEL Console. </summary>
</part>
<part name="detail" >
<detail>null</detail>
</part>
</remoteFault>
Can anyone tell me what has gone wrong in setting the connection factory for the Q or what else I have to configure to sort out this problem?
Thanks,
Jayatu

I am experiencing the exact same issue while configuring for Tibco EMS!!!
I have also checked the oc4j-xa.xml file etc and I am also unable to find any guidance on the steps required from XML config files through to adapter wizard entries!

Error in JMS adapter 11g

Hi
I have configured a JMS Adapter in Jdev 11.1.1.3.0 to consume message from a queue(JNDI Name as eis/wljms/WLQueue) on a weblogic server(10.3.1) in a different domain and deployed my BPM process to the soa server 11g.
I created a new outbound connection pool (eis/wljms/WLQueue) in Deployments->JMSAdapter->Configuration->Outbound Connection Pools with Connection Pool Interface: oracle.tip.adapter.jms.IJmsConnectionFactory
Also updated the factory properties field for eis/wljms/WLQueue with :
java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory;java.naming.provider.url=t3://10.75.85.151:9021;java.naming.security.principal=weblogic;java.naming.security.credentials=weblogic
And finally updated the deployment plan for JMSAdapter.
However I am getting the following error :
<May 24, 2010 10:08:29 AM GMT+05:30> <Warning> <oracle.soa.adapter> <BEA-000000>
<JMSAdapter sample JMSMessageConsumer_init: Retrying connection; attempt #1>
<May 24, 2010 10:08:29 AM GMT+05:30> <Warning> <oracle.soa.adapter> <BEA-000000>
<JMSAdapter sample
BINDING.JCA-12141
ERRJMS_CONN_FAC_NOT_FOUND.
ERRJMS_CONN_FAC_NOT_FOUND.
Unable to instantiate connection factory. JMS adapter was unable to look up the
connection factory neither through JNDI nor instantiate it as a Java class.
Please examine the log file to determine the problem.
at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getConnectionF
actory(JMSConnectionFactoryFactory.java:207)
at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getQueueConnec
tionFactory(JMSConnectionFactoryFactory.java:86)
at oracle.tip.adapter.jms.JMS.JMSConnection.init(JMSConnection.java:173)
at oracle.tip.adapter.jms.inbound.JmsConsumer.init(JmsConsumer.java:862)
Caused by: javax.naming.AuthenticationException [Root exception is java.lang.Sec
urityException: User: weblogic, failed to be authenticated.]
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(Exceptio
nTranslator.java:42)
at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLIni
tialContextFactoryDelegate.java:787)
at weblogic.jndi.WLInitialContextFactoryDelegate.pushSubject(WLInitialCo
ntextFactoryDelegate.java:681)
at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialCon
textFactoryDelegate.java:469)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLIni
tialContextFactoryDelegate.java:376)
at weblogic.jndi.Environment.getContext(Environment.java:315)
at weblogic.jndi.Environment.getContext(Environment.java:285)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialCont
extFactory.java:117)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:6
67)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at oracle.tip.adapter.jms.JMS.JMSFactory.getInitialContext(JMSFactory.ja
va:183)
at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getConnectionF
actory(JMSConnectionFactoryFactory.java:131)
... 26 more
Caused by: java.lang.SecurityException: User: weblogic, failed to be authenticat
ed.
at weblogic.common.internal.RMIBootServiceImpl.authenticate(RMIBootServi
ceImpl.java:116)
at weblogic.common.internal.RMIBootServiceImpl_WLSkel.invoke(Unknown Sou
rce)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
dSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
a:473)
at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.jav
a:118)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173
Anyone has come across this issue? if yes, how do I resolve this?
Thanks

Have you tried cross-domain security or domain trust?

Error in JMS adapter MQ to PI

Hi,
We are connecting to Websphere MQ using the JMS adapter.
The message coming from MQ is a flat structure. So we have configured the Message Transform Bean to do the conversion from plain to xml structure according to
http://wiki.sdn.sap.com/wiki/display/XI/HowTo...ContentconversionmodulewithJ2EEJMS+adapter
But when we test a message we end up with this error:
TransportException: No MIME header found at com.sap.aii.adapter.jms.core.channel.filter.ConvertBinaryToXiMessageFilter.filter
I'm not sure if this is related to the content conversion or general settings in the JMS adapter.
Any inputs are highly appreciated.
Thanks
Shakthi

Hi Shakthi,
Actually, it is the error that tells you where the error took place:
com.sap.aii._adapter.jms_.core.channel.filter.ConvertBinaryToXiMessageFilter.filter
You might also want to refer to this thread: Error in JMS Sender Adpater for a few ideas to solve your problem. In general, it is connected to your adapter configuration. Please review it once again ang you should have the problem fixed.
Hope this helps,
Greg

Error in JMS Adapter Configuration...Pls help..

Hi,
My scenario is that FTP->MQ Queue->Local JMS Queue->XI.
MQ Queue has successfully picked up the files from FTP and posted successfully into Local JMS Queue. But XI is unable to pick them up from Local JMS Queue.
It is giving the following error:-
Error during channel initialization; exception trace: javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for '153.88.140.28:ESEALMW303'
Here are the details what I enetered in the Sender JMS Adapter Configuration:-
Transport Protocol-> WebsphereMQ(Non JMS)
QueueConnection Factory Java Class-> com.ibm.mq.jms.MQQueueConnectionFactory
Queue Java Class->com.ibm.mq.jms.MQQueue
IP address:            153.88.140.28
Server port:            1414
Queue Mgr name ESEALMW303
Channel name        MQMA_ESEALMW303_1
JMS queue            EAB_MDMTOCBS_LQ01
Any help would be appreciated

Soumya,
Refer Abhy's reply in the below thread
XI JMS error MQJMS2005 : failled to create MQQueuemanager for ....
raj.

Error with JMS adapter

We are using a JMS adapter with XML input files and we are getting the following error:
:#1.#00144F80C55600310000001A00001BC700DD9B18A4E85181#1288983973313#com.sap.engine.messaging.impl.core.queue.consumer.SendConsumer##com.sap.engine.messaging.impl.core.queue.consumer.SendConsumer.handleRetriesOnException(MessagingException, QueueMessage, MessageController)#J2EE_GUEST#223963##<applicationserver_hostname>_<SID>_623765##8bfba530dea111dfbf9b00144f80c556#MS Queue Worker [JMS_http://sap.com/xi/XI/SystemSend]##0#0#Error##Java###Transmitting the message to endpoint using connection failed, due to: .#3#JMS_http://sap.com/xi/XI/System#com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error transmitting the message over HTTP. Reason: java.io.IOException: Error writing to server#http://<hostname>:50000/sap/xi/engine?type=entry#
One that is interesting is that these errors are occurring on application servers only. Could it be that the Integration Server URL is not fully qualified. In the SLD it's just <hostname>, not <hostname>.test.com (as an example).
Any help is greatly appreciated.

Dear George,
Concerning the issue, in the Integration Engine please try increasing the value of the parameter :
   - icm/HTTP/max_request_size_KB
from the default size of 100MB to e.g., 2GB.
Kindly go through the following link :
- http://help.sap.com/saphelp_nwpi71/helpdata/en/58/108b02102344069e4a31758bc2c810/frameset.htm
for details.
Additionally, it is recommended to setup a large message queue,
i.e.,
add an entry and appropriate value (e.g., 20480 KB) for the TUNING parameter : 'EO_MSG_SIZE_LIMIT'
using
TCODE
   sxmb_adm
    Integration Engine Configuration
      Select Edit mode and Add the TUNING parameter
I Hope this helps.
Best Regards
Nishwanth

Error in JMS Adapter:

Receiving the below error, thought of JMS Drivers problems undeployed and re-deployed several times, but still problem persist in XI.
Success     MP: Processing local module localejbs/SAP XI JMS Adapter/ConvertMessageToBinary
2010-09-09 11:45:21     Error     MP: Exception caught with cause com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at SAP XI JMS Adapter, the whole lookup name is localejbs/SAP XI JMS Adapter/ConvertMessageToBinary.
2010-09-09 11:45:21     Error     Exception caught by adapter framework: Path to object does not exist at SAP XI JMS Adapter, the whole lookup name is localejbs/SAP XI JMS Adapter/ConvertMessageToBinary.
Error     Delivery of the message to the application using connection JMS_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Path to object does not exist at SAP XI JMS Adapter, the whole lookup name is localejbs/SAP XI JMS Adapter/ConvertMessageToBinary.: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at SAP XI JMS Adapter, the whole lookup name is localejbs/SAP XI JMS Adapter/ConvertMessageToBinary..
2010-09-09 11:45:22     Success     The message status set to WAIT.
2010-09-09 11:45:22     Success     The asynchronous message was successfully scheduled to be delivered at Thu Sep 09 11:50:21 CDT 2010.
The JNDI Libraries are available in Visual Admin, not sure what else causing the issue. Any guru's help is appreciated

XI 3.0 SP20
Regarding the note, that only applied below sp4. We are on SP20. The default values appears but those are not working.This seems to be a problem with Dev only, Q and P is working fine at this moment
If i actually delete module processor's from Sender and Receiver channel, things are working fine. But not sure if it is going to break anything. And this needs to be applied in all landscape. But i have to present a reason, why this weird behavior all of a sudden
Sender
    SAP XI JMS Adapter/ConvertJMSMessageToBinary
    SAP XI JMS Adapter/ConvertBinaryToXMBMessage
Receiver
    SAP XI JMS Adapter/ConvertMessageToBinary
    SAP XI JMS Adapter/SendBinarytoXIJMSService

Error in JMS Adapter while communicating with WebSphere MQ 7.5

Guys,
I am trying to integrate JMS Adapter with WebSphere MQ.
JMS Adapter : 14.0.2.0
WebSphere MQ : 7.5
I am getting error like below. Please help me out. Thanks
17/04/14 16:25:49 java.lang.NoSuchMethodError: com.ibm.msg.client.jms.JmsSession.createQueue(Ljava/lang/String;)Ljavax/jms/Queue;
at com.ibm.mq.jms.MQSession.createQueue(MQSession.java:708)
at com.acta.adapter.jms.MQConfigHandler.getQueue(MQConfigHandler.java:74)
at com.acta.adapter.jms.JMSAdapter.getQueue(JMSAdapter.java:547)
at com.acta.adapter.jms.JMSGetOperation.start(JMSGetOperation.java:398)
at com.acta.adapter.sdk.OperationWrapper.runOperation(OperationWrapper.java:171)
at com.acta.adapter.sdk.OperationWrapper.run(OperationWrapper.java:94)
at java.lang.Thread.run(Thread.java:662)
I have added following jars in class path of the adapter.

Problem solved after removing j2ee.jar file from classpath !

Error Installing Biztalk Adapter for Enterprise (BT2013)

Hi everybody,
I'm attempting to install the adapter for enterprise application, the machine is a win7-64 (phisical) and previously in this laptop had BT 2010. I guess that is something related to the previous version of BizTalk.
The message is:
"An error occured while applying security settings. Users is not a valid user o group. This could ba a problem with tha package, or a problem connecting to a domain controller on the network"
This machine is a sandbox and the user that is running the setup is part of the administrator's group of the machine and is part of the company domain (AD), and the machine is connected to the net.
In advance, I Apreciate your help.
Thanks in advance,
Luis Cardozo

Hi Luis,
Have you verified that the user is member of Biztalk groups ?I think you need to add the user to biztalk group such as Biztalk Administrator ,SSO Administrator etc prior to running the setup .
Another way around is to create groups manually .
perform the following steps and run the installation again:
Create a new user called CREATOR OWNER (Type this command on the command prompt – net user "CREATOR OWNER" /add)
Create a new group called Users (Type this command on the command prompt – net localgroup Users /add)
You can find detailed document at
link here
Thanks
Abhishek

JMS adapter for MQSeries: Changing from MQ5.3 to 6.X libraries

Hi,
Can someone point in the direction of documentation as to how I would migrate/update a BPEL 10.1.3.5.0 environment using JMS adapters for MQSeries 5.3 to use new libraries for MQSeries 6.x.
In a test env I have located the following, but I am not sure now to proceed.
[bpel@omv2rrm2 5.3]$ pwd
/opt/oracle/product/10.1.3.1/OracleAS_1/j2ee/oc4j_soa/shared-lib/oracle.mqseries/5.3
[bpel@omv2rrm2 5.3]$
[bpel@omv2rrm2 5.3]$ ls -l
total 2124
-rwx------ 1 bpel dba 352652 Apr 17 2008 com.ibm.mq-5.3.jar
-rwx------ 1 bpel dba 1798896 Apr 17 2008 com.ibm.mqjms-5.3.jar
[bpel@omv2rrm2 5.3]$
...and...
[bpel@omv2rrm2 config]$ pwd
/opt/oracle/product/10.1.3.1/OracleAS_1/j2ee/oc4j_soa/config
[bpel@omv2rrm2 config]$ cat server.xml
<?xml version="1.0"?>
<application-server xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://xmlns.oracle.com/oracleas/schema/application-server-10_1.xsd" localhostIsAdmin="true"
application-directory="../applications"
check-for-updates="adminClientOnly"
deployment-directory="../application-deployments"
connector-directory="../connectors"
schema-major-version="10" schema-minor-version="0" >
<shared-library name="global.libraries" version="1.0" library-compatible="true">
<code-source path="../applib"/>
<import-shared-library name="oracle.ws.jaxrpc"/>
</shared-library>
<shared-library name="oracle.mqseries" version="5.3">
<code-source path="/opt/oracle/product/10.1.3.1/OracleAS_1/j2ee/oc4j_soa/shared-lib/oracle.mqseries/5.3/com.ibm.mqjms-5.3.jar"/>
<code-source path="/opt/oracle/product/10.1.3.1/OracleAS_1/j2ee/oc4j_soa/shared-lib/oracle.mqseries/5.3/com.ibm.mq-5.3.jar"/>
<import-shared-library name="oracle.ws.jaxrpc"/>
</shared-library>

Just upgrade your SOA to 10.1.3.5.0 and then point to the newer MQ jars in those 2 files.

Error in JMS Adapter for MQ series

Similar Messages

Maybe you are looking for