MQSeries with ALSB2.5

I am trying to use MQSeries with ALSB2.5. MQSeries supports 1. WebSphere JNDI 2. file system 3. LDAP server. I can use IPlanet LDAP to work with MQSeries successfully. but the Client does not want to go with iPlanet LDAP server. They do not want to introduce a 3rd party product just to bind 3 objects. They want to see if WebLogic embedded LDAP can handle this. I could connect and view WLS9.2 embedded LDAP. But when I configure MQSeries to use embedded LDAP, I am getting following error when I try to bind a queue.
InitCtx> def xaqcf(ChaseMQCF) qmanager(WSPQM) HOSTNAME(10.176.18.143) PORT(6003) TRANSPORT(CLIENT)
Unable to bind object
javax.naming.directory.SchemaViolationException: [LDAP: error code 65 - Object Class Violation]; remaining name 'cn=ChaseMQCF'
I tried to export the LDIF file from iPlanet, but it will not let me import to embedded LDAP. Does WebLogic server default embedded LDAP support schema update? or is it possible to bind MQSeries' objects to embedded LDAP?
Thanks

I am trying to use MQSeries with ALSB2.5. MQSeries supports 1. WebSphere JNDI 2. file system 3. LDAP server. I can use IPlanet LDAP to work with MQSeries successfully. but the Client does not want to go with iPlanet LDAP server. They do not want to introduce a 3rd party product just to bind 3 objects. They want to see if WebLogic embedded LDAP can handle this. I could connect and view WLS9.2 embedded LDAP. But when I configure MQSeries to use embedded LDAP, I am getting following error when I try to bind a queue.
InitCtx> def xaqcf(ChaseMQCF) qmanager(WSPQM) HOSTNAME(10.176.18.143) PORT(6003) TRANSPORT(CLIENT)
Unable to bind object
javax.naming.directory.SchemaViolationException: [LDAP: error code 65 - Object Class Violation]; remaining name 'cn=ChaseMQCF'
I tried to export the LDIF file from iPlanet, but it will not let me import to embedded LDAP. Does WebLogic server default embedded LDAP support schema update? or is it possible to bind MQSeries' objects to embedded LDAP?
Thanks

Similar Messages

  • Mqseries with weblogic7.0

              Currently i have the requirement of connecting MqSeries with weblogic7.0
              server . looking thro the edocs , I cannot figure out how to configure the
              jms adapter(xml files in the jms-xa-adp.rar file) to use the mqseries .
              Is it the way to do ? or is there some other way ?
              I have looked at the wlmqseries.zip file at the dev2dev site also , but it
              does not help very much.
              Does anybody have a step by step configuration example to integrate mqseries
              with WLS7.0 using messaging bridge? atleast some guidance would help .
              hoping to hear from u guys .
              -Gowda
              

    Please see comments in line.
              "golibaar" <[email protected]> wrote in message
              news:[email protected]...
              >
              > Currently i have the requirement of connecting MqSeries with weblogic7.0
              > server . looking thro the edocs , I cannot figure out how to configure the
              > jms adapter(xml files in the jms-xa-adp.rar file) to use the mqseries .
              You have to deploy the adapter through the console or in the
              config.xml. The way to deploy the adapters are the same as you deploy any
              Connector adapters. Please refer to the Connector doc. Or check out
              "Deployingthe Bridge Adapters" section in the
              following link:
              http://e-docs.beasys.com/wls/docs70/adminguide/msgbridge.html#1047954
              You have to configure two JMS Bridge Destinations (for the
              destination on the WebLogic side and MQSeries side repectively)
              and one Messaging bridge. You can find detailed information in the
              e-doc given above.
              > Is it the way to do ? or is there some other way ?
              The messaging bridge automatically transfer messages from one destination to
              another. If you just want a WebLogic EJB to read
              messages from MQSeries destinations, you can use MDB.
              http://e-docs.beasys.com/wls/docs70/ejb/message_beans.html#1050867
              > I have looked at the wlmqseries.zip file at the dev2dev site also , but it
              > does not help very much.
              >
              > Does anybody have a step by step configuration example to integrate
              mqseries
              > with WLS7.0 using messaging bridge? atleast some guidance would help .
              >
              By the way, there is a white paper to be published soon in dev2dev for
              integration of 3rd party messaging products with WebLogic Server.
              Hope this helps.
              Dongbo
              

  • How to integrate MQSeries with Oracle BPM Studio 10.3.0.0.0

    Recently I received one requirement which is integrate MQSeries with Oracle BPM Studio 10.3.0.0.0,
    Please help me on this configuration any one who aware.

    We just finsihed a BPM 6.0.4 project that integrates with IBM Websphere MQ 6.0.
    There are many, many steps that are needed to be done in order to integrate but it works very well.
    If you email me at [email protected] I will send you what I have.

  • JMS Receiver MQSeries with zipped payload

    I have tried to add the MessageTransformBean and the PayloadZipBean to the modules in my communication channel according to note 965256 and Stefan Grubes blog about the file receiver. The file is delivered to MQSeries but the zip file is not valid.
    Has anyone managed to do this?
    Regards,
    CJ Nyberg

    Yes, I did enter them before the standard modules in the JMS receiver.
    AF_Modules/MessageTransformBean - module key = contentType
    AF_Modules/PayloadZipBean - module key = zip
    localejbs/SAP XI JMS Adapter/ConvertMessageToBinary
    localejbs/SAP XI JMS Adapter/SendBinarytoXIJMSService
    Module key = contentType
    Parameter name = Transform.ContentType
    Parameter value = text/plain; charset="UTF-8"; name="customer.xml"
    Module key = zip
    Parameter name = zip.filenameKey
    Parameter value = payloadName
    Module key = zip
    Parameter name = zip.mode
    Parameter value = zipOne
    The file sent to MQSeries can't be opened in WinRAR. I get the following error message: Unexpected end of archive
    Assumed I could set the file name inside the zip file by using the MessageTransformBean.
    Maybe the standard module ConvertMessageToBinary is the problem but it has to be there.

  • WLS Cluster with Message Driven Beans and MQSeries on more than one Host

              With the Examples of http://developer.bea.com/jmsproviders.jsp and http://developer.bea.com/jmsmdb.jsp
              a MDB can be
              configured to work with MQSeries with one WLS Server. This works only, if a Queuemanager
              is started at the same Host that runs the WLS Server too.
              And the QueueConnectionFactory (QCF) is configured to TRANSPORT(BIND).
              In my configuration should be two WLS Servers and one JMS Queue (MQS) with the
              Queuemanager.
              A Message Driven Bean is deployed on both WLS Servers wich should get the Messages
              of this Queue.
              If one of the two WLS Servers fails the other WLS Server with the corresponding
              MDB should get the Messages of the
              MQSeries Queue.
              If the QCF is configured to TRANSPORT(Client) the Message Driven Bean can't start
              and the following Exception is thrown:
              <Jul 18, 2001 3:52:49 PM CEST> <Error> <J2EE> <Error deploying EJB Component :
              mdb_deployed
              weblogic.ejb20.EJBDeploymentException: Error deploying Message-Driven EJB:; nested
              exception is:
              javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for
              'btsun1a:TEST'
              javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for 'btsun1a:TEST'
              at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:434)
              I'm wondering, because their is a MQQueueManager on btsun1a; all Servers throws
              the same Exception when the MDB is deployed.
              The configuration of JMSadmin on both Hosts is the following:
              dis qcf(myQCF2)
              HOSTNAME(btsun1a)
              CCSID(819)
              TRANSPORT(CLIENT)
              PORT(1414)
              TEMPMODEL(SYSTEM.DEFAULT.MODEL.QUEUE)
              QMANAGER(TEST)
              CHANNEL(JAVA.CHANNEL)
              VERSION(1)
              dis q(myQueue)
              CCSID(819)
              PERSISTENCE(APP)
              TARGCLIENT(JMS)
              QUEUE(MYQUEUE)
              EXPIRY(APP)
              QMANAGER(TEST)
              ENCODING(NATIVE)
              VERSION(1)
              PRIORITY(APP)
              I think only TRANSPORT(CLIENT) can be used when i don't wan't to install a Queue
              and a QueueManager on each WLS Server.
              Does anybody know a problem of WLS 6.0 SP2 to cope with TRANSPORT(CLIENT)?
              

              With the Examples of http://developer.bea.com/jmsproviders.jsp and http://developer.bea.com/jmsmdb.jsp
              a MDB can be
              configured to work with MQSeries with one WLS Server. This works only, if a Queuemanager
              is started at the same Host that runs the WLS Server too.
              And the QueueConnectionFactory (QCF) is configured to TRANSPORT(BIND).
              In my configuration should be two WLS Servers and one JMS Queue (MQS) with the
              Queuemanager.
              A Message Driven Bean is deployed on both WLS Servers wich should get the Messages
              of this Queue.
              If one of the two WLS Servers fails the other WLS Server with the corresponding
              MDB should get the Messages of the
              MQSeries Queue.
              If the QCF is configured to TRANSPORT(Client) the Message Driven Bean can't start
              and the following Exception is thrown:
              <Jul 18, 2001 3:52:49 PM CEST> <Error> <J2EE> <Error deploying EJB Component :
              mdb_deployed
              weblogic.ejb20.EJBDeploymentException: Error deploying Message-Driven EJB:; nested
              exception is:
              javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for
              'btsun1a:TEST'
              javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for 'btsun1a:TEST'
              at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:434)
              I'm wondering, because their is a MQQueueManager on btsun1a; all Servers throws
              the same Exception when the MDB is deployed.
              The configuration of JMSadmin on both Hosts is the following:
              dis qcf(myQCF2)
              HOSTNAME(btsun1a)
              CCSID(819)
              TRANSPORT(CLIENT)
              PORT(1414)
              TEMPMODEL(SYSTEM.DEFAULT.MODEL.QUEUE)
              QMANAGER(TEST)
              CHANNEL(JAVA.CHANNEL)
              VERSION(1)
              dis q(myQueue)
              CCSID(819)
              PERSISTENCE(APP)
              TARGCLIENT(JMS)
              QUEUE(MYQUEUE)
              EXPIRY(APP)
              QMANAGER(TEST)
              ENCODING(NATIVE)
              VERSION(1)
              PRIORITY(APP)
              I think only TRANSPORT(CLIENT) can be used when i don't wan't to install a Queue
              and a QueueManager on each WLS Server.
              Does anybody know a problem of WLS 6.0 SP2 to cope with TRANSPORT(CLIENT)?
              

  • 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>
              

  • Problems while doing a rollback on MQSeries using a java client

    Hi,
    I'm new to using MQSeries with Java client. I have a kind of similar problem. I have a set of messages in a Queue. When i'm doing a rollback on certain message it's returing to the same pointer where it had come from in the queue. When i'm iterating through the messages in the queue using a for loop, the same message is again retireved. So, i tried to set the setMQGMO_MARK_SKIP_BACKOUT flag to true. But i'm getting an RequestException with error code 2046: MQRC_OPTIONS_ERROR
    Any help on this would be highlly appreciated.
    I'm pasting the code snippet below.
    Class X {
    public void receive(
    com.stc.connector.webspheremqadapter.message.IMessage input, com.stc.connector.webspheremqadapter.message.IMqOtd
    MQSeries_1){
    int msginqueue = MQSeries_1.getCurrentDepth();
    String corrID = "";
    byte[] corrIDInputArray = input.getMsgHeader().getCorrelationId();
    String corrInputID = (new String( corrIDInputArray )).trim();
    for (int i = 0; i < msginqueue; i = i + 1) {
    MQSeries_1.getQueue().getGMO().setMQGMO_SYNCPOINT( true );
    MQSeries_1.getQueue().getWithOptions();
    byte[] corrIDArray = MQSeries_1.getMessage().getMsgHeader().getCorrelationId();
    corrID = (new String( corrIDArray )).trim();
    if (corrID.equalsIgnoreCase( corrInputID )) {
    MQSeries_1.commit();
    } else {
    MQSeries_1.getQueue().getGMO().setMQGMO_MARK_SKIP_BACKOUT( true );
    MQSeries_1.backout();
    }

    I agree that you should check for a specific axis / tomcat forum (maybe on apache website??;)) anyway ... check the path and classpath you use while building the wsdd file and when running the adminclient, and check the syntax of its invokation

  • IDOC interface change platform (from MQseries to XI)

    Dear all,
    Need your advice. We have existing IDoc inbound and outbound communicating with partner by using EDI XML file port. FYI, MQseries is sitting in between our SAP system and partner system.
    For now, we are changing 2 things:
    1. Replace MQseries with XI. Means in future our inbound and outbound IDoc is going through XI.
    2. While for Port, it is changing from EDI XML file port to normal TRFC port (these are in WE20).
    Might need your favor for below:
    1. For outbound, I need to change the ALE setting by pointing to XI. Am i right?
    2. While for inbound, i do not need to do anything. Am i right?
    3. Since we change the communication method to TRFC port. So just want to know do we need to change or fix anything on the existing Inbound and Outbound program.
    Need your expertise advise here.
    Thanks in advance.

    Hi !
    Check this links:
    Introduction to IDoc-XI-File scenario and complete walk through for starters.
    ALE configuration for pushing idocs from SAP to XI
    Regards,
    Matias
    ps: please award points if helpful!

  • Unzipping

    Have a scenerio in which source is a zip file
    The zip files contains xml files
    Sender Adaper : JMS
    Have to unzip the file in Sender adaper.
    There is a standard module which meets this functionality.
    Module Name: AF_Modules/PayloadZipBean(Sap Note:965256)
    I have tried the same and it worked sucessfully when the sender adapter was file adapter.But not working with JMS
    Just want to know whether the same can be used for JMS adapter as well.
    If yes, where do i have to place in the module(in module tab in channel configuration).Following are the modules present by default in JMS adapter:
    1)ConvertJMSMessageTOBinary
    2)ConvertBinaryToXMBMessage
    3)CallSSapAdapter
    Currently i am using the following configuration:
    Module name: AF_Modules/PayloadZipBean
    Module key:zip
    Parameter Name: zip.mode
    Parameter Value: unzip
    Message was edited by:
            Amit Chandnani

    Hi Amit !!
    Check this thread:
    JMS Receiver MQSeries with zipped payload
    or
    Re: JMS Receiver MQSeries with zipped payload
    It talks about using....
    In the JMS receiver channel you click on the module tab. Here you add for the module SendBinarytoXIJMSService the Parameter JMSMessageType with value Bytes.
    To make the /PayloadZipBean to work.
    Regards,
    Matias.

  • XML   to   IDOC

    HI....PI Experts
    I am early bird on PI space,
    My boss just given me a   XML file and asked to convert into XML using PI System.
    We have a readily installed PI System in place.
    What other information i have to get , know, discover to convert the XML to IDOC.
    I understand ...some  explicitly mapping to my XML to IDOC document structure is required. ..am i right ?
    if some explain more about this, We will be greatful and move further in this requirement.
    I tried this but was really not useful
    http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/46759682-0401-0010-1791-bd1972bc0b8a
    Regards
    PR

    which is your target IDoc ?
    How you are picking this XML ?
    If you are picking that from folder as ABC.xml, so scenario is XML file to IDoc.
    If you are picking up that directly from MQSeries, so you will make connections between MQSeries & SAP PI.
    Take help for that from the link for making connection between MQSeries & SAP PI :
    How to use MQseries with PI?
    make scenario using XSD Schema of sender side IDoc.

  • Listener port  could not be started.

    Hello ,
    I am using JMS,MDB and IBM MQSeries with Websphere Application server 6.0. i have configured every thigh in WAS like MQQueue connection cactory and MQQueue Destination.
    After that , i have configured listener port for the message driven bean. .
    configuratin's are :
    Application servers > server1 > Message Listener Service > Listener Ports > mdblistener
    Name --- mdblistener
    Initial State --- Started
    Connection factory JNDI name----jms/nb21queueconnectionfactory
    Destination JNDI name----jms/nb21queuedestination
    when i am starting mdblistener port it's giving following error
    Listener port mdblistener could not be started.
    The Exception in websphere log file is :
    [2/8/06 20:09:04:922 IST] 0000002f SystemErr R javax.management.InstanceNotFoundException: MBeanServer cannot find MBean with ObjectName WebSphere:type=ListenerPort,name=mdblistener,node=nvenkataNode01,process=server1,*
         at mx4j.server.MX4JMBeanServer.findMBeanMetaData(MX4JMBeanServer.java:493)
         at mx4j.server.MX4JMBeanServer.getMBeanInfo(MX4JMBeanServer.java:1318)
         at com.ibm.ws.management.AdminServiceImpl.getMBeanInfo(AdminServiceImpl.java:1026)
         at com.ibm.ws.management.AdminServiceImpl.checkForOpDeprecation(AdminServiceImpl.java:1719)
         at com.ibm.ws.management.AdminServiceImpl.preInvoke(AdminServiceImpl.java:1670)
         at com.ibm.ws.management.AdminServiceImpl.access$400(AdminServiceImpl.java:100)
         at com.ibm.ws.management.AdminServiceImpl$1.run(AdminServiceImpl.java:899)
         at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java(Compiled Code))
         at com.ibm.ws.management.AdminServiceImpl.invoke(AdminServiceImpl.java:817)
         at com.ibm.ws.console.servermanagement.messagelistener.ListenerPortCollectionAction.execute(ListenerPortCollectionAction.java:317)
         at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)
         at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:275)
         at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1486)
         at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:528)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java(Compiled Code))
         at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java(Compiled Code))
         at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java(Compiled Code))
         at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:80)
         at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:1657)
         at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:77)
         at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:421)
         at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:367)
         at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:276)
         at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminaters(NewConnectionInitialReadCallback.java:201)
         at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:103)
         at com.ibm.ws.tcp.channel.impl.WorkQueueManager.requestComplete(WorkQueueManager.java:548)
         at com.ibm.ws.tcp.channel.impl.WorkQueueManager.attemptIO(WorkQueueManager.java(Compiled Code))
         at com.ibm.ws.tcp.channel.impl.WorkQueueManager.workerRun(WorkQueueManager.java:934)
         at com.ibm.ws.tcp.channel.impl.WorkQueueManager$Worker.run(WorkQueueManager.java:1021)
         at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java(Compiled Code))
    [2/8/06 20:09:04:922 IST] 0000002f SystemErr R      at mx4j.server.MX4JMBeanServer.findMBeanMetaData(MX4JMBeanServer.java:493)
    [2/8/06 20:09:04:922 IST] 0000002f SystemErr R      at mx4j.server.MX4JMBeanServer.getMBeanInfo(MX4JMBeanServer.java:1318)
    [2/8/06 20:09:04:922 IST] 0000002f SystemErr R      at com.ibm.ws.management.AdminServiceImpl.getMBeanInfo(AdminServiceImpl.java:1026)
    [2/8/06 20:09:04:922 IST] 0000002f SystemErr R      at com.ibm.ws.management.AdminServiceImpl.checkForOpDeprecation(AdminServiceImpl.java:1719)
    [2/8/06 20:09:04:922 IST] 0000002f SystemErr R      at com.ibm.ws.management.AdminServiceImpl.preInvoke(AdminServiceImpl.java:1670)
    [2/8/06 20:09:04:922 IST] 0000002f SystemErr R      at com.ibm.ws.management.AdminServiceImpl.access$400(AdminServiceImpl.java:100)
    [2/8/06 20:09:04:922 IST] 0000002f SystemErr R      at com.ibm.ws.management.AdminServiceImpl$1.run(AdminServiceImpl.java:899)
    [2/8/06 20:09:04:922 IST] 0000002f SystemErr R      at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java(Compiled Code))
    [2/8/06 20:09:04:922 IST] 0000002f SystemErr R      at com.ibm.ws.management.AdminServiceImpl.invoke(AdminServiceImpl.java:817)
    [2/8/06 20:09:04:922 IST] 0000002f SystemErr R      at com.ibm.ws.console.servermanagement.messagelistener.ListenerPortCollectionAction.execute(ListenerPortCollectionAction.java:317)
    [2/8/06 20:09:04:922 IST] 0000002f SystemErr R      at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)
    [2/8/06 20:09:04:922 IST] 0000002f SystemErr R      at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:275)
    [2/8/06 20:09:04:922 IST] 0000002f SystemErr R      at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1486)
    [2/8/06 20:09:04:922 IST] 0000002f SystemErr R      at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:528)
    [2/8/06 20:09:04:922 IST] 0000002f SystemErr R      at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
    [2/8/06 20:09:04:922 IST] 0000002f SystemErr R      at javax.servlet.http.HttpServlet.service(HttpServlet.java(Compiled Code))
    [2/8/06 20:09:04:922 IST] 0000002f SystemErr R      at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java(Compiled Code))
    [2/8/06 20:09:04:922 IST] 0000002f SystemErr R      at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java(Compiled Code))
    [2/8/06 20:09:04:922 IST] 0000002f SystemErr R      at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:80)
    [2/8/06 20:09:04:922 IST] 0000002f SystemErr R      at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:1657)
    [2/8/06 20:09:04:922 IST] 0000002f SystemErr R      at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:77)
    [2/8/06 20:09:04:922 IST] 0000002f SystemErr R      at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:421)
    [2/8/06 20:09:04:922 IST] 0000002f SystemErr R      at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:367)
    [2/8/06 20:09:04:922 IST] 0000002f SystemErr R      at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:276)
    [2/8/06 20:09:04:922 IST] 0000002f SystemErr R      at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminaters(NewConnectionInitialReadCallback.java:201)
    [2/8/06 20:09:04:922 IST] 0000002f SystemErr R      at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:103)
    [2/8/06 20:09:04:922 IST] 0000002f SystemErr R      at com.ibm.ws.tcp.channel.impl.WorkQueueManager.requestComplete(WorkQueueManager.java:548)
    [2/8/06 20:09:04:922 IST] 0000002f SystemErr R      at com.ibm.ws.tcp.channel.impl.WorkQueueManager.attemptIO(WorkQueueManager.java(Compiled Code))
    [2/8/06 20:09:04:922 IST] 0000002f SystemErr R      at com.ibm.ws.tcp.channel.impl.WorkQueueManager.workerRun(WorkQueueManager.java:934)
    [2/8/06 20:09:04:922 IST] 0000002f SystemErr R      at com.ibm.ws.tcp.channel.impl.WorkQueueManager$Worker.run(WorkQueueManager.java:1021)
    [2/8/06 20:09:04:922 IST] 0000002f SystemErr R      at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java(Compiled Code))
    Any one can help me to over come this problem.
    Thanks in advance
    venkat

    Worked for me, cheers! (I had problems in Mozilla so used IE9)
    843844 wrote:
    Hello All,
    I ran into the exact same issue when configuring WAS 6.0.2, WCS 6.0, MQ 6.0, etc... I will not claim this will resolve everyones issues, but in my case a simple restart of the server was in order, and the MDB started up ok, with the listener port started.
    I think it may have something to do with the fact that the "default mode = started" was choosen, but it had not been started yet. But do not quote me on that!
    I hope this info helps someone who finds themself in the same situation.
    Regards,
    Me

  • Anyone passing & successfully?

    Hi all - we've run into a scenario where the ampersand is a legitimate piece of data from our external source, but are realizing as a control character in XML, it poses a problem for us.  Is anyone else dealing with this?  If so, how?  Tdata comes to/from XI via MQSeries with a JMS adapter.  We're parsing the messages into XI/XML in an internal java mapping, and it blows up upon receiving the &.  We also know both < and > are coming soon, so we're hoping someone has found a solution we can borrow.  Thanks

    If you treat the < or > as a part of your data, you need to escape them in the source as "&lt;" or "&gt;", and in your parsing program, you need to treat them as ONE character length.
    Hope this helps.
    Hart

  • Error listening to Queue carnot Queue

    I get the following error in my application.log and do not really know, what to do with it:
    java.lang.InstantiationException: Error: com.evermind.server.jms.EvermindQueueSession
         at com.evermind.server.jms.OrionServerSessionPool.getServerSessionFull(OrionServerSessionPool.java:377)
         at com.evermind.server.ejb.MessageDrivenHome.run(MessageDrivenHome.java:769)
         at com.evermind.util.ThreadPoolThread.run(ThreadPoolThread.java:66)
    my jms.xml looks as follows:
    <?xml version="1.0"?>
    <!DOCTYPE jms-server PUBLIC "Orion JMS server" "http://xmlns.oracle.com/ias/dtds/jms-server.dtd">
    <jms-server port="9127" host="127.0.0.1">
    <!--Queue bindings, these queues will be bound to their respective JNDI path for later retrieval -->
    <queue-connection-factory location="jms/carnotQCF" password="carnot" port="9127" username="admin">
    </queue-connection-factory>
    <queue-connection-factory location="jms/appointmentQCF" password="carnot" port="9127" username="admin">
    </queue-connection-factory>
    <queue-connection-factory location="jms/objectMessageQCF" password="carnot" port="9127" username="admin">
    </queue-connection-factory>
    <queue-connection-factory location="jms/d0012QCF" password="carnot" port="9127" username="admin">
    </queue-connection-factory>
    <!-- path to the log-file where JMS-events/errors are stored-->
    <!-- log>
    <file path="../log/jms.log" />
    </log -->
    <queue name="carnot Queue" location="jms/carnotqueue" persistence-file="../persistence/MDB/carnot.queue" >
    <description>Appointment Queue</description>
    </queue>
    <queue name="Appointment Queue" location="jms/appointmentQ" persistence-file="../persistence/MDB/appointment.queue" >
    <description>Appointment Queue</description>
    </queue>
    <queue name="Object Message Queue" location="jms/objectMessageQ" >
    <description>Object Message Queue</description>
    </queue>
    <queue name="D0012 Queue" location="jms/d0012Q" persistence-file="../persistence/MDB/d012.queue" >
    <description>D012 queue</description>
    </queue>
    </jms-server>
    orion-ejb-jar.xml for the MDB:
    <message-driven-deployment name="MessageListener" destination-location="jms/carnotqueue" connection-factory-location="jms/carnotQCF" max-instances="10">
    Anybody an idea?
    cheers,
    Klaus

    Hi Klaus
    We had the same error as you have.
    After a lot of troubles we are now able to run IBMs MQSeries with OC4J v. 9.0.3.0.0
    Here is an overview of our configuration (on Windows 2000)
    Added the following lines to C:\OC4J\j2ee\home\config\application.xml
    This is to use connect to MQSeries with a file based JNDI. We created the file .bindings in C:\JNDI with IBMs JMSAdmin tool.
    <resource-provider
    class="com.evermind.server.deployment.ContextScanningResourceProvider"
    name="MQSeries">
    <description> MQSeries </description>
    <property name="java.naming.factory.initial" value="com.sun.jndi.fscontext.RefFSContextFactory"> </property>
    <property name="java.naming.provider.url" value="file:/C:/JNDI"> </property>
    </resource-provider>
    We copied the following files from MQSeries to C:\OC4J\j2ee\home\lib
    com.ibm.mq.jar
    com.ibm.mqjms.jar
    com.ibm.mqbind.jar
    mqji.properties
    fscontext.jar
    providerutil.jar
    Added the following line to C:\OC4J\j2ee\home\config\server.xml
    <library path="../lib" />
    This points to C:\OC4J\j2ee\home\lib where our MQSeries .jar files are located.
    In line 176 in com.evermind.server.jms.OrionServerSessionPool.class (located in OC4J.jar) we changed the following lines:
    ((AQjmsSession)new_session).setCloseCheckInterval(2);
    new_consumer = ((QueueSession)new_session).createReceiver((Queue)destination, messageSelector);
    ((AQjmsQueueReceiver)new_consumer).setNavigationMode(1);
    new_connection.start();
    to this:
    new_consumer = ((QueueSession)new_session).createReceiver((Queue)destination, messageSelector);
    new_connection.start();
    The reason to this, is that it looks like OC4J do not accept other queue system than AQ. If we dont change those lines, we get the following error:
    java.lang.InstantiationException: Error: com.evermind.server.jms.EvermindQueueSession at com.evermind.server.jms.OrionServerSessionPool.getServerSessionFull(OrionServerSessionPool.java:377)
    at com.evermind.server.ejb.MessageDrivenHome.run(MessageDrivenHome.java:769)
    at com.evermind.util.ThreadPoolThread.run(ThreadPoolThread.java:66)
    In the MDB sample (C:\OC4J\j2ee\home\demo\mdb) we changed the following (ivtTCF, ivtQCF, ivtT and ivtQ are MQSeries factories and connections):
    Orion-ejb-jar.xml
    <?xml version="1.0" encoding="utf-8"?>
    <!DOCTYPE orion-ejb-jar PUBLIC "-//Evermind//DTD Enterprise JavaBeans 1.1 runtime//EN" "http://xmlns.oracle.com/ias/dtds/orion-ejb-jar.dtd">
    <orion-ejb-jar deployment-version="9.0.3.0.0" deployment-time="ec68ca361c">
    <enterprise-beans>
    <session-deployment
    name="MyCart"
    max-instances="10"
    location="MyCart">
    <resource-ref-mapping
    name="ivtTCF"
    location="java:comp/resource/MQSeries/ivtTCF">
    </resource-ref-mapping>
    <resource-env-ref-mapping
    name="ivtT"
    location="java:comp/resource/MQSeries/ivtT">
    </resource-env-ref-mapping>
    <resource-ref-mapping
    name="ivtQCF"
    location="java:comp/resource/MQSeries/ivtQCF">
    </resource-ref-mapping>
    <resource-env-ref-mapping
    name="ivtQ"
    location="java:comp/resource/MQSeries/ivtQ">
    </resource-env-ref-mapping>
    </session-deployment>
    <message-driven-deployment
    name="MessageBeanTpc"
    connection-factory-location="java:comp/resource/MQSeries/ivtTCF"
    destination-location="java:comp/resource/MQSeries/ivtT"
    subscription-name="MDBSUB">
    <resource-ref-mapping
    name="ivtTCF"
    location="java:comp/resource/MQSeries/ivtTCF">
    </resource-ref-mapping>
    <resource-env-ref-mapping
    name="ivtT"
    location="java:comp/resource/MQSeries/ivtT">
    </resource-env-ref-mapping>
    <resource-ref-mapping
    name="ivtQCF"
    location="java:comp/resource/MQSeries/ivtQCF">
    </resource-ref-mapping>
    <resource-env-ref-mapping
    name="ivtQ"
    location="java:comp/resource/MQSeries/ivtQ">
    </resource-env-ref-mapping>
    </message-driven-deployment>
    <message-driven-deployment
    connection-factory-location="java:comp/resource/MQSeries/ivtQCF"
    destination-location="java:comp/resource/MQSeries/ivtQ"
    name="MessageBeanQue">
    <resource-ref-mapping
    name="ivtTCF"
    location="java:comp/resource/MQSeries/ivtTCF">
    </resource-ref-mapping>
    <resource-env-ref-mapping
    name="ivtT"
    location="java:comp/resource/MQSeries/ivtT">
    </resource-env-ref-mapping>
    <resource-ref-mapping
    name="ivtQCF"
    location="java:comp/resource/MQSeries/ivtQCF">
    </resource-ref-mapping>
    <resource-env-ref-mapping
    name="ivtQ"
    location="java:comp/resource/MQSeries/ivtQ">
    </resource-env-ref-mapping>
    </message-driven-deployment>
    </enterprise-beans>
    <assembly-descriptor>
    <default-method-access>
    <security-role-mapping name="&lt;default-ejb-caller-role&gt;" impliesAll="true" />
    </default-method-access>
    </assembly-descriptor>
    </orion-ejb-jar>
    ejb-jar.xml
    <?xml version="1.0"?>
    <!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 1.2//EN" "http://java.sun.com/j2ee/dtds/ejb-jar_1_2.dtd">
    <ejb-jar>
    <description>A demo cart bean package.</description>
    <display-name>A simple cart jar</display-name>
    <enterprise-beans>
    <session>
    <description>A simple shopping cart.</description>
    <display-name>Shopping Cart</display-name>
    <ejb-name>MyCart</ejb-name>
    <home>cart.ejb.CartHome</home>
    <remote>cart.ejb.Cart</remote>
    <ejb-class>cart.ejb.CartEJB</ejb-class>
    <session-type>Stateful</session-type>
    <transaction-type>Container</transaction-type>
    <resource-ref>
    <res-ref-name>ivtQCF</res-ref-name>
    <res-type>javax.jms.QueueConnectionFactory</res-type>
    <res-auth>Container</res-auth>
    <res-sharing-scope>Shareable</res-sharing-scope>
    </resource-ref>
    <resource-env-ref>
    <resource-env-ref-name>ivtQ</resource-env-ref-name>
    <resource-env-ref-type>javax.jms.Queue</resource-env-ref-type>
    </resource-env-ref>
    <resource-ref>
    <res-ref-name>ivtTCF</res-ref-name>
    <res-type>javax.jms.TopicConnectionFactory</res-type>
    <res-auth>Container</res-auth>
    <res-sharing-scope>Shareable</res-sharing-scope>
    </resource-ref>
    <resource-env-ref>
    <resource-env-ref-name>ivtT</resource-env-ref-name>
    <resource-env-ref-type>javax.jms.Topic</resource-env-ref-type>
    </resource-env-ref>
    </session>
    <message-driven>
    <description></description>
    <display-name>MessageBeanTpc</display-name>
    <ejb-name>MessageBeanTpc</ejb-name>
    <ejb-class>cart.ejb.MessageBean</ejb-class>
    <transaction-type>Container</transaction-type>
    <message-driven-destination>
    <destination-type>javax.jms.Topic</destination-type>
    <subscription-durability>Durable</subscription-durability>
    </message-driven-destination>
    <resource-ref>
    <res-ref-name>ivtQCF</res-ref-name>
    <res-type>javax.jms.QueueConnectionFactory</res-type>
    <res-auth>Container</res-auth>
    <res-sharing-scope>Shareable</res-sharing-scope>
    </resource-ref>
    <resource-env-ref>
    <resource-env-ref-name>ivtQ</resource-env-ref-name>
    <resource-env-ref-type>javax.jms.Queue</resource-env-ref-type>
    </resource-env-ref>
    <resource-ref>
    <res-ref-name>ivtTCF</res-ref-name>
    <res-type>javax.jms.TopicConnectionFactory</res-type>
    <res-auth>Container</res-auth>
    <res-sharing-scope>Shareable</res-sharing-scope>
    </resource-ref>
    <resource-env-ref>
    <resource-env-ref-name>ivtT</resource-env-ref-name>
    <resource-env-ref-type>javax.jms.Topic</resource-env-ref-type>
    </resource-env-ref>
    </message-driven>
    <message-driven>
    <description></description>
    <display-name>MessageBeanQue</display-name>
    <ejb-name>MessageBeanQueBMT</ejb-name>
    <ejb-class>cart.ejb.MessageBean</ejb-class>
    <transaction-type>Bean</transaction-type>
    <message-driven-destination>
    <destination-type>javax.jms.Queue</destination-type>
    </message-driven-destination>
    <resource-ref>
    <res-ref-name>ivtQCF</res-ref-name>
    <res-type>javax.jms.QueueConnectionFactory</res-type>
    <res-auth>Container</res-auth>
    <res-sharing-scope>Shareable</res-sharing-scope>
    </resource-ref>
    <resource-env-ref>
    <resource-env-ref-name>ivtQ</resource-env-ref-name>
    <resource-env-ref-type>javax.jms.Queue</resource-env-ref-type>
    </resource-env-ref>
    <resource-ref>
    <res-ref-name>ivtTCF</res-ref-name>
    <res-type>javax.jms.TopicConnectionFactory</res-type>
    <res-auth>Container</res-auth>
    <res-sharing-scope>Shareable</res-sharing-scope>
    </resource-ref>
    <resource-env-ref>
    <resource-env-ref-name>ivtT</resource-env-ref-name>
    <resource-env-ref-type>javax.jms.Topic</resource-env-ref-type>
    </resource-env-ref>
    </message-driven>
    </enterprise-beans>
    <assembly-descriptor>
    <container-transaction>
    <method>
    <ejb-name>MyCart</ejb-name>
    <method-name>*</method-name>
    </method>
    <trans-attribute>Required</trans-attribute>
    </container-transaction>
    <container-transaction>
    <method>
    <ejb-name>MessageBeanTpc</ejb-name>
    <method-name>onMessage</method-name>
    </method>
    <trans-attribute>Required</trans-attribute>
    </container-transaction>
    <container-transaction>
    <method>
    <ejb-name>MessageBeanQue</ejb-name>
    <method-name>onMessage</method-name>
    </method>
    <trans-attribute>Required</trans-attribute>
    </container-transaction>
    </assembly-descriptor>
    </ejb-jar>
    In MessageBean.java I removed the few lines code related to AQ, and added the following imports to MessageBean.java and CartEJB.java:
    import com.ibm.*;
    import com.ibm.mq.*;
    import com.ibm.mq.jms.*;
    import com.ibm.jms.*;
    It works!!!
    Good luck
    Ole

  • JMS receiver adapter supports SSL??

    Hi
    We have a interface in our project which uses JMS adapter and to make it secured communication , we are requested to use SSL.
    Can anyone please suggest if JMS receiver adapter supports SSL.
    If no possible, coould you please let us know any other alternative approach to this.
    Regards
    Jagruth

    Look into below discussions
    JMS To MQSeries with SSL.
    Regards
    Aashish Sinha

  • MQ-XI-BW

    Hi ppl,
          i am able to load data into BW as soon as an XML file is posted in MQSeries.My source XML File includes the Message Type details and the namespace details along with the attributes.Now i need to connect my MQSeries with some OLTP System(for instance Oracle).How can i expect my end users to send input file in such a format maintained in the message mapping(with Message Type name and namespace name)? Is there any way to convert the incoming input file with respect to the defined template before posting it in MQSeries?
    Regards
    Sathya

    Hi,
      Thanks for quick reply. The input file that i am posting in MQSeries is something like this...
    <?xml version="1.0" encoding="UTF-8"?>
    <ns:MT_Input_File xmlns:ns="http://xitest">
      <datasource>6AIS_XMLDATA</datasource>
      <data>
        <item>
          <calday>20020201</calday>
          <material>835</material>
          <amount>900</amount>
          <currency>DM</currency>
        </item>
      </data>
    </ns:MT_Input_File>
    Now instead of posting the file directly into MQSeries, i have to get it from Oracle Server whenever a new record has been created.I have 4 fields created in Oracle(calday, material,amount,currency). I need to insert record into MQ whenerver this table has been inserted with new records. Now how do i convert this record into an xml file with the datasource and namespace defined as per the above file and post it in MQ.
    Thanks a lot.
    Regards
    Sathya

Maybe you are looking for

  • Diffrent Currency in AR Invoice and Incoming Payments

    Dear Experts, I have an situation here where the AR invoice reads one currency but the incoming payments read a different one. What could be causing this ?

  • Space to the right of the trackpad...

    I got my MacBook less than a month ago and I noticed that the space to the right of my tackpad (where my wrist rests while I'm tying) feels loose. It's hard to explain, but when I lift my right hand up from typing I hear a "click" type sound. It almo

  • InDesign style sheets?

    I'm wondering if there is a way in cs6 to create an external styles doc in indesign? Similar to how linking images works and are alerted when the image is missing, is there a way to link a style sheet to any type of style? I aware that you can load c

  • Vista PDF Preview handler installed on Win 7 32 bit does not work.

    There is no discoverable information regarding failure to preview Adobe PDF files on Win 7 32 bit. The advice for 64 bit does not work. Adobe continues to install the Vista preview handler on my Windows 7 computer, which I suspect is the issue. Is th

  • Methods of Class

    Hi, Is there a way to know the methods defined in a class. For e.g if I want to know if there is a way to get the member name and thier details for e.g in java.math.BigInteger Any info is appreciated. Thanks