IBM MqSeries configuration

hi all,
i m using mqseries 5.3. I have created Sender QMgr & Receiver QMgr & in that i have created sender queue & receiver queue.
In sender queue i have created two channels
1) Server connection channel
2) sender channel
In receiver queue i have created
1) receiver channel.
All the above mentioned things i have created using MQseries explorer & both these QMgrs are on the same machine.
When i tried to test communication between two channel using ping then i am getting following error on MQ Explorer
Unexpected Error(AMQ4048)
& in AMQERR01.log file i m getting the following error.
"AMQ6120: An internal WebSphere MQ error has occurred.
EXPLANATION:
An error has been detected, and the MQ error recording routine has been called.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
----- amqxfdcp.c : 626 --------------------------------------------------------
12/11/2005 10:38:24
AMQ6184: An internal WebSphere MQ error has occurred on queue manager SenderQ.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 1536.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
----- amqxfdcp.c : 660 --------------------------------------------------------
12/11/2005 10:38:25"
can anyone pls help. i m looking for the solution from last 5 days.
pls its urgent
thanx a lot in adv.
reg,
ritu

I'm sure the people here will help if possible, but you'll probably have better luck on at http://www.mqseries.net/
I take it you've already tried the obvious...
http://www-1.ibm.com/support/docview.wss?uid=swg21110451

Similar Messages

  • Sender JMS adapter configuration for IBM MQSeries

    Dear All,
    i am doing a IBM MQSeries 5.2.x Message ->sender JMS adapter -> XI server -> receiver RFC adapter -> R/3.
    i have deployed the JMS adapter with the required jar files of IBM MQSeries 5.2.x in XI server.
    in Sender JMS adapter configuration for IBM MQSeries 5.2.x, i have put following data:
    1. Transport Protocol: Websphere MQ - is it okay?
    in JMS provider settings:
    2. in channel name - what should be there?
    3. Transport Network protocol should be TCP/IP or WebsphereMQ - how to decide this thing.
    4. JMS Complaint - whether WebsphereMQ or JMS API.
    in JMS Settings:
    5. JMS Queue user - is this IBM MQSeries 5.2.x Queue User or someother user?
    6. JMS Message Selector - what data to take here.
    So if anybody has connected IBM MQSeries 5.2.x to XI via JMS adapter, please answer my above queries.
    Regards,
    Rajeev Gupta

    Hi Swaroop,
    you can send me those documents at my gmail-id : [email protected]
    Hi All,
    one more question - to connect XI server to IBM MQSeries via JMS adapter in ID, do we need to have a MQSeries Client installed on XI server - or - just by configuring JMS adapter, we can send messages from IBM MQSeries to XI server without any MQSeries client on XI server?
    Why Channel name is required in JMS configuration data?
    Thanks,
    Rajeev Gupta

  • Newbie : Problem starting OPG for IBM MQseries: TNS-00530,  Error Code 2

    Hi All
    First of all, if this is the wrong place to post this question, I apologize.
    I have installed a new installation of Oracle 9.2.0.1 and at a separate home location the OPG for IBM MQSeries for 9.2.0.1 off the same bits.
    The configuration said that the default SID of PG4MQS92 would be setup since I was using a local MQ queue manager but I didnt see any entries in the listener.ora or the tnsames.ora so added the following.
    listener.ora
    (SID_DESC =
    (SID_NAME = pg4mqs92)
    (ORACLE_HOME = C:\Software\oracle\pg4mqs92)
    (PROGRAM = pg4mqs92)
    tnsnames.ora
    ORACLE_QM =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = TCP)(HOST = testmachine)(PORT = 1521))
    (CONNECT_DATA =
    (SID = pg4mqs92)
    (HS=OK)
    When I ran tnsping on ORACLE_QM it was resolved. But when I start the putsample.sql program after importing all the required packages using the pgmdeploy9.sql script I get the following output.
    DECLARE
    ERROR at line 1:
    ORA-04052: error occurred when looking up remote object
    [email protected]
    ORA-00604: error occurred at recursive SQL level 1
    ORA-28545: error diagnosed by Net8 when connecting to an agent
    NCRO: Failed to make RSLV connection
    ORA-02063: preceding 2 lines from PG4MQ
    In the listener.log I see the following error
    07-DEC-2005 07:34:19 * (CONNECT_DATA=(SID=pg4mqs92)) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.1.100)(PORT=1271)) * establish * pg4mqs92 * 12500
    TNS-12500: TNS:listener failed to start a dedicated server process
    TNS-12560: TNS:protocol adapter error
    TNS-00530: Protocol adapter error
    32-bit Windows Error: 2: No such file or directory
    I noticed that during the install a boot file for the pgm4mqs92 SID was not found anywhere. Is it maintained in the registry, if so where ?
    If the boot file is missing is there a sample I can use and where do I need to put it ?
    Am running on Windows XP Professional.
    Have been stuck with this a while and cannot find any information on this, so any help would be appreciated.
    Thanks
    - Deepak

    I am getting the same error while starting or stopping the listener
    LSNRCTL> start CSCLIST
    Starting tnslsnr: please wait...
    TNS-12560: TNS:protocol adapter error
    TNS-00530: Protocol adapter error
    LSNRCTL> stop CSCLIST
    Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=CSCINDAE708070)(PORT=152
    2)))
    NL-00303: syntax error in NV string
    TNS-01153: Failed to process string: (DESCRIPTION=(CONNECT_DATA=(CID=(PROGRAM=)
    (HOST=)(USER=Manager(REMOVE)))(COMMAND=stop)(ARGUMENTS=64)(SERVICE=CSCLIST)(VERS
    ION=186646784)))
    Pls help
    Listener.ora:
    # listener.ora Network Configuration File: D:\Sagaya\11gDBhome\product\11.2.0\dbhome_1\network\admin\listener.ora
    # Generated by Oracle configuration tools.
    CSCLIST =
    (DESCRIPTION_LIST =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = CSCINDAE708070)(PORT = 1522))
    (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1522))
    SID_LIST_CSCLIST =
    (SID_LIST =
    (SID_DESC =
    (SID_NAME = CLRExtProc)
    (ORACLE_HOME = D:\Sagaya\11gDBhome\product\11.2.0\dbhome_1)
    (PROGRAM = extproc)
    (ENVS = "EXTPROC_DLLS=ONLY:D:\Sagaya\11gDBhome\product\11.2.0\dbhome_1\bin\oraclr11.dll")
    ADR_BASE_CSCLIST = D:\Sagaya\11gDBhome

  • JMS versus IBM MQSeries

    1. What is the difference between JMS and IBM MQSeries ?
    2. If JMS is all about APIs to interact with Message Oriented Middleware (MOM) that IBM MQSeries supports, why not use a simple JAVA program that would import com.ibm. * packages instead of JMS APIs ? What is the benefit we derive from using JMS ?

    I think what you are saying is JMS is the preferred
    way to communicate with MOM (i.e. MQ) as it is
    standard and not vendor dependant. My concern is
    this:
    If we write a stand alone program to send/retrieve
    meessage from MQ then how do we create
    ConnectionFactory and connection? Personally I prefer to use Dependency Injection using a library like Spring to configure things like JMS connection factories, JDBC DataSources etc.
    http://www.springframework.org/
    though the more typical (and some would say official) way of doing it is to use JNDI in your application. So create a JNDI context and pull the JMS ConnectionFactory and destinations out of JNDI.
    e.g. like this
    http://svn.activemq.org/trunk/activemq/modules/core/src/test/org/activemq/demo/SimpleProducer.java?rev=1&view=auto
    Then you need to refer to your JMS provider's documentation on how to configure a JNDI context. Typically its a case of adding a jndi.properties file to the classpath configured to your provider's JNDI provider.
    Don't we need MQ
    classes to create these objects.Yes, you need the classes from your JMS provider to create connections & sessions. (Its not like EJB remoting where you can create client side proxies from the EJB interfaces).
    James
    http://logicblaze.com/

  • IBM MQSeries Gateway

    I would like to connect to IBM MQSeries v.5.3
    from an Oracle 9.2.
    According to Metalink and Oracle documentation,
    I could use PG4MQ
    (Oracle Procedural Gateway) or
    Messaging Gateway using AQ.
    They have different architecture
    and different configuration.
    Which one is better ?
    During the Oracle installation I
    have only the PG4MQ option,
    so how I could use Oracle Procedural Gateway
    Thanks

    Dear Yang!
    I have the same problem considering the two possibilities to connect ibm with oracle...
    Did you get some useful information or do you have some experience now? If yes could you please update the post!
    Thanks
    Markus

  • Remote queue in XI server for IBM MQSeries

    Dear All,
    my scenario is IBM MQSeries -> message via sender JMS adapter -> XI -> receiver RFC adapter -> R/3.
    now for IBM MQSeries to send a message to XI via a transmission queue in MQSeries - it needs a remote queue name and  queue  manager name in XI server.
    So now where can i find these information regarding remote queue name and  queue  manager name in XI server. I currently do not know whether in XI server, currently is there any remote queue or not? So how to find this information. If we do not have remote queue manager in XI currently, then how to install a remote queue name and  queue  manager in XI server.
    It is slightly urgent. So i request you all to please reply quickly.
    Thanks and Regards,
    Rajeev Gupta

    Dear Sebastin,
    Thanks for your inputs.
    I have to connect to MQSeries 5.2.1 to XI server.
    am getting the below error in Communicatin Channel Monitoring for my sender JMS adapter:
    Error during channel initialization; exception trace: javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for '<IP_ADRESS>:<MQ_QUEUE_MANAGER>'
    at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:546)
    at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1137)
    at com.ibm.mq.jms.MQConnection.createQMNonXA(MQConnection.java:799)
    com.ibm.mq.MQException: Message catalog not found
    at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:171)
    at com.ibm.mq.MQClientManagedConnectionFactoryJ11._createManagedConnection(MQClientManagedConnectionFactoryJ11.java:228)
    i have written '<IP_ADRESS>:<MQ_QUEUE_MANAGER>' just to hide the data - i am getting <IP_ADRESS> as IP Adress i gave in JMS adapter and <MQ_QUEUE_MANAGER> as Queue Manager i gave in JMS adapter.
    i am using the correct IP and 1414 port of MQSeries server. I have used a MQQueueManager defined in MQSeries. i have deployed JMS adapter properly in XI server.
    So can anybody suggest what could be the possible reason of this error and how to rectify it. It is slightly urgent.
    One more question - should the queue manager in MQSeries server be a local or remote queue manager..........i was not able to create a remote queue manager in MQSeries 5.2.1 as by default it is creating a local queue manager.......
    Thanks and Regards,
    Rajeev Gupta

  • Java Doc for IBM MQSeries

    Hi,
    Can anyone tell me where i can get javadoc for IBM MQSeries Classes.
    Regs
    David Jeyam

    http://www-3.ibm.com/software/ts/mqseries/library/manuals/

  • J2EE and IBM MQSeries

    Hi
    We are planning to use IBM MQSeries as a JMS server for message driven beans.
    We are using OC4J 2.0 developer preview, but can't figure out how to connect to MQSeries. It looks like we have to use JNDI, but how?
    Best regards
    Ole

    Hi Ole,
    The following may help you...
    http://kb.atlassian.com/content/orion/docs/resource-providers/resource-providers.html
    Good Luck,
    Avi.

  • JMSAdapter for MQSeries - Configuration

    Hi guys - quick question (and I'm following the OracleAS Adapters 10.1.3.1.0 manual here). I'm not overly familar with MQ, so some of this may be obvious...
    Exactly which (of the many in the installation tree) oc4j-ra.xml and application.xml files do I need to edit to incorporate the <connector-factory> and MQ jar location recommendations described in the manual for configuring for IBM WebSphere JMS?
    Also can someone tell me the relationship of the QueueManager=QM_test setting in the sample Factory Properties step to the rest of the configuration - i.e what is QM_test ?
    Thanks
    Dennis

    Hi,
    I am trying to configure the JMSAdapter for MQSeries.
    I have added the mq.jar and mqjms.jar to the application.xml. But still I keep getting the error that
    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.
    [Caused by: com.ibm.mq.jms.MQQueueConnectionFactory not found]
    Did u run into this issue and if yes how did u resolve it. Will appreciate your help.
    Regards,
    PB

  • Message Bus to IBM MQSeries bridging?

    Hi,
    I need to connect from Azure to IBM MQ series queues. I have found some documentation about a MSMQ->MQSeries bridge which is part of some Hosting software which doesn't exist anymore. 
    In pratical terms, how to approach this from Azure? What steps to take? 
    Werner

    hi Werner,
    There is a document about message connection between IBM queues and azure service bus. You could refer to
    http://blrp.org/2013/03/ibm-websphere-message-broker-azure-service-bus/ .
    Hope it helps.
    Regards,
    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.

  • IBM MQSeries JAR's needed

    Hey Folks,
    i'm searching for the following JAR's:
    MQSeries 5.2
    com.ibm.mq.jar
    com.ibm.mqjms.jar
    MQSeries 5.3
    com.ibm.mq.jar
    com.ibm.mqbind.jar
    com.ibm.mqjms.jar
    connector.jar (this file can also be retrieved from the SAP J2EE server directory)
    I try to add these to the JMS Adapter, but i can't find them. Please help.
    Thank you!
    Best Regards
    Robert

    Hi
    Check this link
    http://www.java2s.com/Code/Jar/Spring-Related/Downloadconnectorjar.htm
    http://www.niratul.com/wmqtool002.htm
    Regards
    Ramesh
    Edited by: Venkataramesh Boppana on May 11, 2009 5:16 PM

  • Why use IBM MQSeries when Weblogic already provides JMS?

    i kind of understand that MQSeries works the same as JMS provided by WebLogic, so there is not much a point to use MQSeries, but why do companies still use MQSeries when JMS is already provided by WebLogic?
    what are the advantages of using MQSeries over WebLogic provided JMS?

    I don't think there's necessarily much reason to adopt MQ, unless perhaps you have very specific messaging extensions or capability requirements. There are performance, manageability, and scalability benefits in using WebLogic JMS, especially when it is integrated with WebLogic applications. There also happen to be benefits in using the Oracle DB's built in messaging (AQ JMS).
    There are tens of thousands (if not 100s of thousands) of production WL JMS deployments out in the wild - some of which are "mission critical" and quite large, and some of which have been running for 10+ years. It's not unlikely that you generate multiple WL JMS transactions per day, just going about your daily life (phone, bank, credit card, financials, etc.).
    Of course your mileage may vary - and keep in mind that you're posting to WebLogic JMS forum. :-)
    Tom Barnes
    Oracle WebLogic Messaging Team

  • Using MDB with IBM MQSeries

              Hi All,
              I want to use MDB with MQSeries as Messaging medium.
              My Weblogic App. server version is 6.0
              I want MDB to get invoked whenever any message comes in MQSeries queue.
              I think 8.1 version provides a option to add external JMS server.
              Is it possible in 6.0 version?
              Please let me know ASAP.
              Waiting for reply!
              Thanks,
              Prasanna Laddha
              

    Hi Prasanna,
              The best resource is the white-paper, which mentions MQ directly:
              http://dev2dev.bea.com/resourcelibrary/whitepapers/jmsproviders.jsp
              But it does not take into account the following 8.1 feature:
              http://edocs.bea.com/wls/docs81/ConsoleHelp/jms_config.html#accessing_foreign_providers
              Tom
              prasanna wrote:
              > Hi Tom,
              > I had weblogic 7 now.
              > Is there any document which can help me in setting up connection with MQSeries
              > for MDB beans?
              >
              > Pls let me know ASAP.
              > Thanks lot.
              > Prasanna
              >
              >
              >
              > Tom Barnes <[email protected]> wrote:
              >
              >>In 6.0, for non-transactional case, I'm fairly
              >>sure that you can drive the MDB directly from MQ. See
              >>the white-paper:
              >>
              >>http://dev2dev.bea.com/resourcelibrary/whitepapers/jmsproviders.jsp
              >>
              >>But, as with most customers, my guess is that you need
              >>to transfer the messages transactionally
              >>(exactly-once). In which case more work is needed:
              >>
              >>By far the easiest option is to upgrade to WL7.0 or
              >>WL8.1 which can drive an MDB transactionally
              >
              >>from MQ directly. WL8.1 provides enhancements
              >
              >>to wrap foreign vendor resources to simplify
              >>the process even farther.
              >>
              >>Another option is to use a WL6.1SP3 or later
              >>server running a messaging bridge to bridge from MQ
              >>to WL6.0. I'm not sure if these are capable of
              >>bridging to 6.0 exactly-once (transactionally) though.
              >>
              >>For the transactional case, I think you will
              >>end up needing to
              >>write your own "bridge" that runs from within
              >>a startup class or servlet.
              >>The following example shows how to bridge from
              >>wl to mqseries transactionally using a startup class.
              >>To drive the MDB exactly-once, you will need
              >>modify this code to do bridge from MQ into
              >>a WL queue instead, then the queue in turn can
              >>be used to drive the WL MDB:
              >>
              >>http://dev2dev.bea.com/codelibrary/code/mqseries.jsp
              >>
              >>Tom
              >>
              >>
              >>Prasanna wrote:
              >>
              >>>Hi All,
              >>>I want to use MDB with MQSeries as Messaging medium.
              >>>My Weblogic App. server version is 6.0
              >>>
              >>>I want MDB to get invoked whenever any message comes in MQSeries queue.
              >>>I think 8.1 version provides a option to add external JMS server.
              >>>Is it possible in 6.0 version?
              >>>
              >>>Please let me know ASAP.
              >>>Waiting for reply!
              >>>Thanks,
              >>>Prasanna Laddha
              >>>
              >>
              >
              

  • Configuring MQSeries 5.2 JMS With Weblogic 7.0

    Hi :
              Has anyone configured MQ Series 5.2 under weblogic 7.0 ?. I would appreciate
              if you could let me step by step configuration.
              I have tried all the configuration steps in Weblogic 7.0 but still i am
              getting an exception while the MessageBridge is trying to get a connection
              from the Target Destination (in my case MQSeries).
              The exception:
              <Oct 17, 2002 11:17:37 AM PDT> <Error> <Connector> <190006> <Error granting
              connection request.>
              javax.resource.spi.ResourceAllocationException: CreateManagedConnection
              Error: Failed to start the connection
              at
              weblogic.connector.common.internal.ConnectionPool.makeResources(ConnectionPo
              ol.java:993)
              at
              weblogic.connector.common.internal.ConnectionPool.getConnection(ConnectionPo
              ol.java:1762)
              at
              weblogic.connector.common.internal.ConnectionPoolManager.getConnection(Conne
              ctionPoolManager.java:163)
              at
              weblogic.connector.common.internal.ConnectionManagerImpl.allocateConnection(
              ConnectionManagerImpl.java:25)
              at
              weblogic.jms.adapter.JMSBaseConnectionFactory.getTargetConnection(JMSBaseCon
              nectionFactory.java:126)
              at
              weblogic.jms.bridge.internal.MessagingBridge.getConnections(MessagingBridge.
              java:733)
              at
              weblogic.jms.bridge.internal.MessagingBridge.execute(MessagingBridge.java:89
              9)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)
              thanks,
              Balaji.
              

    Hi Dongbo:
              It worked, as you have said it was configuration problem of the PATH
              variable in my end.
              thanks,
              Balaji.
              "Dongbo Xiao" <[email protected]> wrote in message
              news:[email protected]...
              > Your configuration looks fine except that you are not recommended to
              > put MQSeries stuff in the AdapterClasspath attribute. Instead, the
              > following is what you should do according to the doc.
              >
              > Before starting WebLogic Server:
              >
              > Supply the provider's CLASSPATH in the WebLogic Server CLASSPATH.
              >
              > Include the PATH of any native code required by the provider's
              > client-side libraries in the WebLogic Server system PATH. (This variable
              > may vary depending on your operating system.)
              >
              > You can also check the Messaging Bridge part of the following doc:
              >
              >
              http://dev2dev.bea.com/resourcelibrary/whitepapers.jsp?highlight=whitepapers
              >
              > If the bridge still does not work after you correctly set everything,
              > you need to check all the values that you set for the attributes
              > (ConnectionURL
              > and etc)of the JMSBridgeDestination corresponding to the MQSeries queue.
              > Make sure
              > you can access MQSeries with those values from a client.
              >
              > It should work. Most commonly seen problems are configuration problems
              > or
              > environment problems.
              >
              > Good luck.
              > Dongbo
              >
              > Balaji Venkataraman wrote:
              > >
              > > Hi Dongbo: Please find herewith the information requested by you.
              > >
              > > Related Properties from Config.xml:
              > >
              > > <Application Deployed="true" Name="jms-xa-adp"
              > > Path="C:\bea\weblogic700\server\lib" TwoPhase="true">
              > > <ConnectorComponent Name="jms-xa-adp" Targets="adminserver"
              > > URI="jms-xa-adp.rar"/>
              > > </Application>
              > >
              > > JMS Related Entries:
              > >
              > > <JMSBridgeDestination ConnectionFactoryJNDIName="ediJMSFactory"
              > > DestinationJNDIName="MQ_WEBEDI_TO_OPUSTX"
              > > Name="MQSourceDestination"/>
              > > <JMSBridgeDestination
              > > Classpath="c:\Program
              > > Files\IBM\MQSeries\Java\samples\base;c:\Program
              > > Files\IBM\MQSeries\java\lib\com.ibm.mq.jar;c:\Program
              > > Files\IBM\MQSeries\java\lib\com.ibm.mqjms.jar;c:\Program
              > > Files\IBM\MQSeries\java\lib\jms.jar;c:\Program
              > > Files\IBM\MQSeries\java\lib\jndi.jar;c:\Program
              > > Files\IBM\MQSeries\java\lib\fscontext.jar;c:\Program
              > > Files\IBM\MQSeries\java\lib\providerutil.jar;c:\Program
              > > Files\IBM\MQSeries\java\lib\connector.jar;"
              > > ConnectionFactoryJNDIName="mqXAQCF"
              > > ConnectionURL="file://c:\bea\wlsmq" DestinationJNDIName="mqQ"
              > >
              InitialContextFactory="com.sun.jndi.fscontext.RefFSContextFactory"
              > > Name="MQTargetDestination"/>
              > > <JMSConnectionFactory AllowCloseInOnMessage="true"
              > > JNDIName="ediJMSFactory" Name="ediJMSFactory"
              > > Targets="adminserver" UserTransactionsEnabled="true"
              > > XAConnectionFactoryEnabled="true" XAServerEnabled="true"/>
              > > <JMSFileStore Directory="filestore" Name="MyJMSFile Store"/>
              > > <JMSServer Name="MyJMSServer" Store="MyJMSFile Store"
              > > Targets="adminserver">
              > > <JMSQueue DeliveryModeOverride="Persistent"
              > > JNDIName="MQ_WEBEDI_TO_OPUSTX" Name="OpusQueue"
              > > StoreEnabled="true"/>
              > > </JMSServer>
              > >
              > > Message Bridge:
              > >
              > > <MessagingBridge Name="MyMessaging Bridge"
              > > SourceDestination="MQSourceDestination"
              > > TargetDestination="MQTargetDestination" Targets="adminserver"/>
              > >
              > > thanks,
              > > Balaji.
              > >
              > > "Dongbo Xiao" <[email protected]> wrote in message
              > > news:[email protected]...
              > > >
              > > > Please send your configuration for the source bridge destination,
              > > > target bridge destination and the bridge itself.
              > > >
              > > > Dongbo
              > > >
              > > > Balaji Venkataraman wrote:
              > > > >
              > > > > Hi :
              > > > >
              > > > > Has anyone configured MQ Series 5.2 under weblogic 7.0 ?. I would
              > > appreciate
              > > > > if you could let me step by step configuration.
              > > > >
              > > > > I have tried all the configuration steps in Weblogic 7.0 but still i
              am
              > > > > getting an exception while the MessageBridge is trying to get a
              > > connection
              > > > > from the Target Destination (in my case MQSeries).
              > > > >
              > > > > The exception:
              > > > > <Oct 17, 2002 11:17:37 AM PDT> <Error> <Connector> <190006> <Error
              > > granting
              > > > > connection request.>
              > > > > javax.resource.spi.ResourceAllocationException:
              CreateManagedConnection
              > > > > Error: Failed to start the connection
              > > > > at
              > > > >
              > >
              weblogic.connector.common.internal.ConnectionPool.makeResources(ConnectionPo
              > > > > ol.java:993)
              > > > > at
              > > > >
              > >
              weblogic.connector.common.internal.ConnectionPool.getConnection(ConnectionPo
              > > > > ol.java:1762)
              > > > > at
              > > > >
              > >
              weblogic.connector.common.internal.ConnectionPoolManager.getConnection(Conne
              > > > > ctionPoolManager.java:163)
              > > > > at
              > > > >
              > >
              weblogic.connector.common.internal.ConnectionManagerImpl.allocateConnection(
              > > > > ConnectionManagerImpl.java:25)
              > > > > at
              > > > >
              > >
              weblogic.jms.adapter.JMSBaseConnectionFactory.getTargetConnection(JMSBaseCon
              > > > > nectionFactory.java:126)
              > > > > at
              > > > >
              > >
              weblogic.jms.bridge.internal.MessagingBridge.getConnections(MessagingBridge.
              > > > > java:733)
              > > > > at
              > > > >
              > >
              weblogic.jms.bridge.internal.MessagingBridge.execute(MessagingBridge.java:89
              > > > > 9)
              > > > > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152)
              > > > > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)
              > > > >
              > > > > thanks,
              > > > > Balaji.
              > >
              > > <?xml version="1.0" encoding="UTF-8"?>
              > > <!--If your domain is active, please do not edit the config.xml file.
              Any changes made to that file while the domain is active will not have any
              effect on the domain's configuration and are likely to be lost. If your
              domain is inactive, you may edit this file with an XML editor. If you do so,
              please refer to the BEA Weblogic Server Configuration Reference
              documentation available from http://edocs.bea.com/wls/docs70/config_xml. In
              general, we recommend that changes to your configuration file be made
              through the Administration Console.-->
              > > <Domain ConfigurationVersion="7.0.0.0" Name="edixml">
              > > <Application Deployed="true" Name="DefaultWebApp"
              > > Path=".\applications" StagedTargets="" TwoPhase="false">
              > > <WebAppComponent Name="DefaultWebApp" Targets="adminserver"
              URI="DefaultWebApp"/>
              > > </Application>
              > > <Application Deployed="true" Name="certificate"
              > > Path=".\applications" StagedTargets="" TwoPhase="false">
              > > <WebAppComponent Name="certificate" Targets="adminserver"
              URI="certificate.war"/>
              > > </Application>
              > > <Application Deployed="true" Name="jms-xa-adp"
              > > Path="C:\bea\weblogic700\server\lib" TwoPhase="true">
              > > <ConnectorComponent Name="jms-xa-adp" Targets="adminserver"
              URI="jms-xa-adp.rar"/>
              > > </Application>
              > > <ApplicationManager Name="edixml"/>
              > > <Cluster ClusterAddress="208.193.6.143:7001,208.193.6.143:8001"
              > > MulticastAddress="237.0.0.4" MulticastPort="7777"
              Name="edixmlcluster"/>
              > > <EmbeddedLDAP
              > > Credential="{3DES}iLJIRpiJCbQYHvktF5nq32XqGBhWLQpLEcMRXP+KJi0="
              Name="edixml"/>
              > > <FileRealm Name="wl_default_file_realm"/>
              > > <JDBCConnectionPool DriverName="oracle.jdbc.driver.OracleDriver"
              > > Name="OracleDBPool"
              > >
              Properties="user=webedi7;password=webedi7;dll=ocijdbc8;protocol=thin"
              > > Targets="adminserver" TestConnectionsOnReserve="true"
              > > TestTableName="numberblockmaster"
              URL="jdbc:oracle:thin:@192.168.222.6:1521:ora8"/>
              > > <JDBCTxDataSource JNDIName="OracleTxDS" Name="OracleTxDS"
              PoolName="OracleDBPool"/>
              > > <JMSBridgeDestination ConnectionFactoryJNDIName="ediJMSFactory"
              > > DestinationJNDIName="MQ_WEBEDI_TO_OPUSTX"
              Name="MQSourceDestination"/>
              > > <JMSBridgeDestination
              > > Classpath="c:\Program
              Files\IBM\MQSeries\Java\samples\base;c:\Program
              Files\IBM\MQSeries\java\lib\com.ibm.mq.jar;c:\Program
              Files\IBM\MQSeries\java\lib\com.ibm.mqjms.jar;c:\Program
              Files\IBM\MQSeries\java\lib\jms.jar;c:\Program
              Files\IBM\MQSeries\java\lib\jndi.jar;c:\Program
              Files\IBM\MQSeries\java\lib\fscontext.jar;c:\Program
              Files\IBM\MQSeries\java\lib\providerutil.jar;c:\Program
              Files\IBM\MQSeries\java\lib\connector.jar;"
              > > ConnectionFactoryJNDIName="mqXAQCF"
              > > ConnectionURL="file://c:\bea\wlsmq" DestinationJNDIName="mqQ"
              > >
              InitialContextFactory="com.sun.jndi.fscontext.RefFSContextFactory"
              Name="MQTargetDestination"/>
              > > <JMSConnectionFactory AllowCloseInOnMessage="true"
              > > JNDIName="ediJMSFactory" Name="ediJMSFactory"
              > > Targets="adminserver" UserTransactionsEnabled="true"
              > > XAConnectionFactoryEnabled="true" XAServerEnabled="true"/>
              > > <JMSFileStore Directory="filestore" Name="MyJMSFile Store"/>
              > > <JMSServer Name="MyJMSServer" Store="MyJMSFile Store"
              Targets="adminserver">
              > > <JMSQueue DeliveryModeOverride="Persistent"
              > > JNDIName="MQ_WEBEDI_TO_OPUSTX" Name="OpusQueue"
              StoreEnabled="true"/>
              > > </JMSServer>
              > > <JTA Name="edixml"/>
              > > <JTARecoveryService Name="primary"/>
              > > <JTARecoveryService Name="secondary"/>
              > > <Log FileName=".\wl-domain.log" Name="edixml"/>
              > > <MessagingBridge Name="MyMessaging Bridge"
              > > SourceDestination="MQSourceDestination"
              > > TargetDestination="MQTargetDestination" Targets="adminserver"/>
              > > <MigratableTarget Cluster="edixmlcluster"
              > > Name="primary (migratable)"
              > > Notes="This is a system generated default migratable target for
              a server. Do not delete manually." UserPreferredServer="primary"/>
              > > <MigratableTarget Cluster="edixmlcluster"
              > > Name="secondary (migratable)"
              > > Notes="This is a system generated default migratable target for
              a server. Do not delete manually." UserPreferredServer="secondary"/>
              > > <PasswordPolicy Name="wl_default_password_policy"/>
              > > <Realm FileRealm="wl_default_file_realm" Name="wl_default_realm"/>
              > > <SNMPAgent Name="edixml"/>
              > > <Security GuestDisabled="false" Name="edixml"
              > > PasswordPolicy="wl_default_password_policy"
              > > Realm="wl_default_realm" RealmSetup="true"/>
              > > <SecurityConfiguration
              > >
              Credential="{3DES}du0wFpH35kta7XFhGk6UV2mve7IhavFhAJ8uSzz1W4Gt2i9CV4PDWSLsnb
              6nJjMiej2UAIGHrmT3RGIQG1sn9R0xaYz1STwV" Name="edixml"/>
              > > <Server ListenAddress="208.193.6.143" ListenPort="9001"
              > > Name="adminserver" NativeIOEnabled="true"
              ServerVersion="7.0.0.0">
              > > <COM Name="adminserver"/>
              > > <ExecuteQueue Name="default" ThreadCount="15"/>
              > > <IIOP Name="adminserver"/>
              > > <JTAMigratableTarget Cluster="" Name="adminserver"
              UserPreferredServer="adminserver"/>
              > > <KernelDebug Name="adminserver"/>
              > > <Log FileName=".\adminserver\adminserver.log"
              Name="adminserver"/>
              > > <SSL Enabled="true" HostnameVerificationIgnored="true"
              > > ListenPort="9002" Name="adminserver"
              > > ServerCertificateChainFileName="ca.pem"
              > > ServerCertificateFileName="democert.pem"
              ServerKeyFileName="demokey.pem"/>
              > > <ServerDebug Name="adminserver"/>
              > > <ServerStart Name="adminserver"/>
              > > <WebServer DefaultWebApp="DefaultWebApp"
              > > LogFileName=".\adminserver\access.log" LoggingEnabled="true"
              Name="adminserver"/>
              > > </Server>
              > > <Server Cluster="edixmlcluster" JTARecoveryService="primary"
              > > ListenAddress="208.193.6.143" ListenPort="7001" Name="primary"
              > > NativeIOEnabled="true" ServerVersion="7.0.0.0">
              > > <COM Name="primary"/>
              > > <ExecuteQueue Name="default" ThreadCount="15"/>
              > > <IIOP Name="primary"/>
              > > <JTAMigratableTarget Cluster="edixmlcluster" Name="primary"
              UserPreferredServer="primary"/>
              > > <KernelDebug Name="primary"/>
              > > <Log Name="primary"/>
              > > <SSL Name="primary"/>
              > > <ServerDebug Name="primary"/>
              > > <ServerStart Name="primary"/>
              > > <WebServer Name="primary"/>
              > > </Server>
              > > <Server Cluster="edixmlcluster" JTARecoveryService="secondary"
              > > ListenAddress="208.193.6.143" ListenPort="8001" Name="secondary"
              > > NativeIOEnabled="true" ServerVersion="7.0.0.0">
              > > <COM Name="secondary"/>
              > > <ExecuteQueue Name="default" ThreadCount="15"/>
              > > <IIOP Name="secondary"/>
              > > <JTAMigratableTarget Cluster="edixmlcluster" Name="secondary"
              UserPreferredServer="secondary"/>
              > > <KernelDebug Name="secondary"/>
              > > <Log Name="secondary"/>
              > > <SSL Name="secondary"/>
              > > <ServerDebug Name="secondary"/>
              > > <ServerStart Name="secondary"/>
              > > <WebServer Name="secondary"/>
              > > </Server>
              > > </Domain>
              

  • Reg: Is it possible in weblogic 5.1 or 6 to get Transaction suport for MQseries & Oracle

              Hi
              I would like to know whether weblogic 5.1 or 6 provides support in a single transaction,
              transaction support for both oracle and MQseires, if so where can i find suitable
              documentation on this topic
              with regards
              Priya
              

    The answer is definitely yes, starting in WLS 6.0, with
              some two reasonable limitations.
              There are limitations are the following:
              1. It must be on the server side. The registration of the XAResource
              can't happen in a client. It must happen in a startup class
              or EJB or servlet, etc. You can start it from a client (invoke
              an EJB or servlet) but the resource work must be
              on the server side.
              2. MQSeries can't be included if it is being used to drive a
              Message Driven Bean. Because the message is passed
              from MQ Series to WLS outside of a transaction, after
              which WLS will start a transaction (if so configured) and
              pass it to the MDB, the MQ Series message is not part
              of the transaction. The JavaSoft specs don't handle this case.
              For WLS JMS, this works because we have defined such
              an interface and implemented it. At least one other vendor
              understands the importance of having this feature and is
              interested in implementing it (it's not IBM).
              So to do what you want, it is necessary to:
              1. Use the XAResource version of the JDBC driver for Oracle.
              WLS is smart enough to look at the driver and see if it
              implements the XAResource interface and automatically
              register it as a resource. This has been documented
              in this newsgroup already or see
              http://e-docs/wls/docs60/adminguide/jdbc.html#1075694.
              2. Register the XAResource interface for MQSeries programmatically
              in the application. The code to do this has been posted
              at the BEA developer site for a few months in an article
              entitled "Using JTA Transactions to envelope WLS JMS and
              IBM MQSeries" (could I be more explicit), located at
              http://developer.bea.com/docs/jmsjta.jsp. It references
              another document that has more code, describing how to
              plug in a "foreign" (non-WLS) JMS provider, of which MQSeries
              is one, in a non-transaction manner (you need to do that
              first and then just add the resource registration) - see
              http://developer.bea.com/docs/jmsproviders.jsp.
              All of the necessary code is included in the documents (including
              how to download and install the Java libraries for MQSeries).
              Several people have told me that they have been able to
              use this as a starting place for their applications.
              You might also want to look at the JMS FAQ at
              http://developer.bea.com/docs/jmsfaq.jsp.
              In 6.1, support is added for importing foreign transactions.
              That means that in 6.0, WLS can drive a transaction with
              WLS JMS, Oracle, and MQ series, with WLS being the
              driving force. In WLS 6.1, a non-WLS transaction manager can
              drive a transaction that includes (transactionally infects)
              WLS resources (like WLS JMS).
              There are no white papers that I know of in this area and I haven't
              tested it myself (the goal is to have someone try out
              having WebSphere drive a transaction with WLS resources, soon).
              "Priya" <[email protected]> wrote in message news:[email protected]...
              >
              > Hi
              >
              > I would like to know whether weblogic 5.1 or 6 provides support in a single transaction,
              > transaction support for both oracle and MQseires, if so where can i find suitable
              > documentation on this topic
              >
              > with regards
              > Priya
              

Maybe you are looking for