Transaction with Sunapplication server

Dear All,
I am working on some project with sun application server. The project was done in weblogic and it was working fine. Now our management decided move the working version to sunapplication server. I am having big trouble in finding when does server commits the transaction. Is there any indiaction in the log file and any information that we can trace for transactions that are being commited or rolledback. / any thing to indiacte in the sun-ejb-jar.xml
the flow is like main application conatct session bean which generates event, once event is generated the application generates other 4 records related different persons(insert 4 records into 4 diff tables).
in 5th step program retrieves the values from tables based on what they inserted in previous steps.
session bean which initiates applications generated event and use hybernate to store record, the other 4 recordes are created using entity beans.
I am able to populate the beans(for storing) and retrieve the information from beans. but the actual values are not in the database.
If some one can help that would be great help.
thanks
Srini

To find out what each transaction ended with you have to change your instance's Log Level for JTA and JTS from default INFO to FINE or FINEST. You could also throw in FINE for EJB Container if you need to check what your EJBs are up to.
You can chenge Log Level setting via admin console:
instance-config --> Logger Settings --> Log Levels tab
Once you change the logger settings rerun your test and loads of info would be printed into instance's server.log.

Similar Messages

  • Transaction with the server failed error 405

    HI,
    Thanks in advance.
    We are working on the MDM service provided by apple using the iPCU and have configured the server with valid certificate. But still we notice some other error. Please help us to resolve this.
    Error:
    (Error) MDM: Cannot Authenticate. Error: NSError:
    Desc   : A transaction with the server at failed with the status 405.
    US Desc: A transaction with the server at has failed with the status 405.
    Domain : MCHTTPTransactionErrorDomainCode   : 23001
    Type   : MCFatalErrorParams : ("https://xxxxx.xxx.com/Checkin.aspx",    405)
    (Error) MC: Cannot install MDM com.xxx.mdm.mdm3. Error: NSError:
    Desc   : The payload com.xxx.mdm.mdm3 could not be installed.
    Sugg   : A transaction with the server at https://xxxx.xxx.com/Checkin.aspx has failed with the status 405.
    US Desc: The payload com.xxx.mdm.mdm3 could not be installed.
    US Sugg: A transaction with the server at https://xxxx.xxx.com/Checkin.aspx has failed with the status 405.
    Domain : MCInstallationErrorDomainCode   : 4001
    Type   : MCFatalErrorParams : (    "com.xxx.mdm.mdm3")...Underlying error:NSError:
    Desc   : A transaction with the server at https://xxxxx.xxx.com/Checkin.aspx has failed with the status 405.
    US Desc: A transaction with the server at https://xxxxx.xxx.com/Checkin.aspx has failed with the status 405.
    Domain : MCHTTPTransactionErrorDomainCode   : 23001
    Type   : MCFatalErrorParams : (    "https://xxxxx.xxx.com/Checkin.aspx",    405)

    But in 2005 B I did the same without using license file.
    Moreover, I can access the other machine's(Server) Companies from different SAP B1 server by using change Server on Choose Company Screen.
    But If I install the client on a system, I am not able to access the companies.
    Is it mandatory to have License to install the Client of a server?
    Is it new guideline in 2007 or was it already exist in previous versions.

  • Error when adding new service invoice with DI Server, error -1114

    <b>Hi everybody.
    I'm trying to add an serviceinvoice (DocType = 'Service Transaction') with DI Server AddObject method.
    The xml-request document looks like this:</b>
    <?xml version='1.0' encoding='UTF-16' ?>
    <env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/'>
    <env:Header>
    <SessionID>........</SessionID>
    </env:Header>
    <env:Body>
    <dis:AddObject xmlns:dis='http://www.sap.com/SBO/DIS'>
    <BOM>
    <BO>
    <AdmInfo>
    <Object>oInvoices</Object>
    </AdmInfo>
    <Documents>
    <row>
    <DocNum>1241</DocNum>
    <HandWritten>1</HandWritten>
    <DocDate>10/08/2005</DocDate>
    <DocDueDate>10/08/2005</DocDueDate>
    <CardCode>V1010</CardCode>
    <DocType>S</DocType>
    </row>
    </Documents>
    <Document_Lines>
    <row>
    <Currency>USD</Currency>
    <LineTotal>7500,00</LineTotal>
    <AccountCode>_SYS00000000001</AccountCode>
    <TaxCode>LA</TaxCode>
    </row>
    <row>
    <Currency>USD</Currency>
    <LineTotal>-7500,00</LineTotal>
    <TaxCode>LA</TaxCode>
    </row>
    </Document_Lines>
    </BO>
    </BOM>
    </dis:AddObject>
    </env:Body>
    </env:Envelope>
    <b>...But I get error eveytime I try to do it, the response document as follows:</b>
    <?xml version="1.0"?>
    <env:Envelope xmlns:env="http://www.w3.org/2003/05/soap-envelope">
    <env:Body>
    <env:Fault>
    <env:Code>
    <env:Value>env:Receiver</env:Value>
    <env:Subcode>
    <env:Value>-1114</env:Value>
    </env:Subcode>
    </env:Code>
    <env:Reason>
    <env:Text xml:lang="en">Schema Validation Failed</env:Text>
    </env:Reason>
    <env:Detail>
    <ErrorList>
    <Error>System Id = 193271344, Line Number = 1, Column Number = 359, Description = Datatype error: Type:InvalidDatatypeFacetException, Message: Invalid chars encountered..</Error><Error>System Id = 193271344, Line Number = 1, Column Number = 488, Description = Datatype error: Type:InvalidDatatypeFacetException, Message: Invalid chars encountered..</Error>
    </ErrorList>
    <Object>13</Object>
    <ObjectIndex>1</ObjectIndex>
    <Command>AddObject</Command>
    <SessionID>............</SessionID>
    </env:Detail>
    </env:Fault>
    </env:Body>
    </env:Envelope>
    <b>Why? Which fields are missing or which field values of those I'm sending might be wrong?</b>

    Did you try to set the AccountCode also for the 2nd line?
    HTH,
    Frank

  • MQSeries as a Transactional Resource Manager with Weblogic Server

              I am trying to setup the example given in the BEA white paper:
              Using MQSeries as a Transactional Resource Manager with Weblogic Server.
              Version 1.
              October 25, 2001.
              I followed the instructions given in the documents, but when i run client program
              >java MQClient t3://localhost:7001 "MQSeries test"
              I received the following exception below. Does anyone how what is the reason for
              this exception(s) and how i can solve the problem? My MQSeries Server and Weblogic
              6.1 sp2 are installed on seperate NT machines. I installed the MQSeries classes
              for java and the MQSeries classes for Java Message Service on the weblogic
              server machine.
              sending: "MQSEries test"
              Exception in thread "main" java.rmi.ServerError: A error occurred the server; ne
              sted exception is:
              java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
              Start server side stack trace:
              java.rmi.ServerError: A error occurred the server; nested exception is:
              java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
              java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
              at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
              at java.lang.Runtime.loadLibrary0(Runtime.java:749)
              at java.lang.System.loadLibrary(System.java:820)
              at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
              at java.security.AccessController.doPrivileged(Native Method)
              at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
              at com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
              at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
              at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
              149)
              at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
              tion(MQBindingsManagedConnectionFactoryJ11.java:139)
              at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
              ion(MQBindingsManagedConnectionFactoryJ11.java:157)
              at com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
              a:80)
              at com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
              ctionManager.java:150)
              at com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
              a:666)
              at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
              at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
              at com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
              at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
              at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
              at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
              at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
              at com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
              at com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
              AQueueConnectionFactory.java:53)
              at weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
              QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
              at MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
              at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
              at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
              at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
              at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
              a:267)
              at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
              .java:22)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              End server side stack trace
              ; nested exception is:
              java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
              Start server side stack trace:
              java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
              at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
              at java.lang.Runtime.loadLibrary0(Runtime.java:749)
              at java.lang.System.loadLibrary(System.java:820)
              at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
              at java.security.AccessController.doPrivileged(Native Method)
              at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
              at com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
              at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
              at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
              149)
              at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
              tion(MQBindingsManagedConnectionFactoryJ11.java:139)
              at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
              ion(MQBindingsManagedConnectionFactoryJ11.java:157)
              at com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
              a:80)
              at com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
              ctionManager.java:150)
              at com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
              a:666)
              at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
              at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
              at com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
              at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
              at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
              at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
              at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
              at com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
              at com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
              AQueueConnectionFactory.java:53)
              at weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
              QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
              at MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
              at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
              at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
              at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
              at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
              a:267)
              at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
              .java:22)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              End server side stack trace
              java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
              Start server side stack trace:
              java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
              at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
              at java.lang.Runtime.loadLibrary0(Runtime.java:749)
              at java.lang.System.loadLibrary(System.java:820)
              at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
              at java.security.AccessController.doPrivileged(Native Method)
              at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
              at com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
              at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
              at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
              149)
              at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
              tion(MQBindingsManagedConnectionFactoryJ11.java:139)
              at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
              ion(MQBindingsManagedConnectionFactoryJ11.java:157)
              at com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
              a:80)
              at com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
              ctionManager.java:150)
              at com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
              a:666)
              at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
              at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
              at com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
              at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
              at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
              at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
              at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
              at com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
              at com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
              AQueueConnectionFactory.java:53)
              at weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
              QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
              at MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
              at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
              at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
              at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
              at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
              a:267)
              at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
              .java:22)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              End server side stack trace
              <<no stack trace available>>
              --------------- nested within: ------------------
              weblogic.rmi.extensions.RemoteRuntimeException - with nested exception:
              [java.rmi.ServerError: A error occurred the server; nested exception is:
                      java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
              Start server side stack trace:
              java.rmi.ServerError: A error occurred the server; nested exception is:
                      java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
              java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
                      at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
                      at java.lang.Runtime.loadLibrary0(Runtime.java:749)
                      at java.lang.System.loadLibrary(System.java:820)
                      at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
                      at java.security.AccessController.doPrivileged(Native Method)
                      at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
                      at com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
                      at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
                      at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
              149)
                      at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
              tion(MQBindingsManagedConnectionFactoryJ11.java:139)
                      at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
              ion(MQBindingsManagedConnectionFactoryJ11.java:157)
                      at com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
              a:80)
                      at com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
              ctionManager.java:150)
                      at com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
              a:666)
                      at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
                      at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
                      at com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
                      at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
                      at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
                      at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
                      at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
                      at com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
                      at com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
              AQueueConnectionFactory.java:53)
                      at weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
              QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
                      at MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
                      at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
                      at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
                      at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
                      at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
              a:267)
                      at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
              .java:22)
                      at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
                      at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              End  server side stack trace
              ; nested exception is:
                      java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
              Start server side stack trace:
              java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
                      at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
                      at java.lang.Runtime.loadLibrary0(Runtime.java:749)
                      at java.lang.System.loadLibrary(System.java:820)
                      at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
                      at java.security.AccessController.doPrivileged(Native Method)
                      at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
                      at com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
                      at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
                      at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
              149)
                      at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
              tion(MQBindingsManagedConnectionFactoryJ11.java:139)
                      at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
              ion(MQBindingsManagedConnectionFactoryJ11.java:157)
                      at com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
              a:80)
                      at com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
              ctionManager.java:150)
                      at com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
              a:666)
                      at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
                      at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
                      at com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
                      at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
                      at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
                      at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
                      at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
                      at com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
                      at com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
              AQueueConnectionFactory.java:53)
                      at weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
              QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
                      at MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
                      at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
                      at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
                      at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
                      at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
              a:267)
                      at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
              .java:22)
                      at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
                      at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              End  server side stack trace
              at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:60)
              at $Proxy1.bridgeWLS2MQS(Unknown Source)
              at MQClient.main(MQClient.java:54)
              

    The point is that over TCPIP the MQ XA connection factory is not available.
              The MQ shared memory/JNI driver is required to access it, which limits
              access to those processes that are on the same box as the MQ q manager.
              This is an MQ series limitation.
              Douglas WF Acheson wrote:
              > Hello,
              >
              > If memory server me correct, default connection to MQ Series is through
              > JNI calls and shared memory. You have to change the protocol to TCPIP when
              > connection to the queue manager on another box (do not know much about XA
              > with MQ Series); that is when you connect to MQ Series vi JMS on another
              > box you must do something like the following:
              >
              > qcf = new MQQueueConnectionFactory() ;
              > qcf.setHostName(hostName) ;
              > qcf.setPort(port) ;
              > qcf.setTransportType(JMSC.MQJMS_TP_CLIENT_MQ_TCPIP) ;
              > qcf.setQueueManager(qManagerName) ;
              >
              > Then when you create you queues, sesions etc. you are point at the correct Q
              > manager.
              >
              > Hope this helps ...
              >
              > Douglas WF Acheson
              >
              > "Raja Mukherjee" <[email protected]> wrote in message
              > news:[email protected]...
              > > On a closer look at the original post (sorry for missing that, it was
              > early
              > > in the morning), you would not be able to use XA if your QM and WLS are in
              > > different boxes. Check on this newsgroup, there are several posts on this
              > > subject. The whitepaper, if I recall correctly, installs both MQ and WLS
              > on
              > > the sames box. This is a MQSeries limitation not WLS.
              > >
              > > .raja
              > >
              > >
              > > "ibrahim Nehme" <[email protected]> wrote in message
              > > news:[email protected]...
              > > >
              > > > I am trying to setup the example given in the BEA white paper:
              > > > Using MQSeries as a Transactional Resource Manager with Weblogic Server.
              > > > Version 1.
              > > > October 25, 2001.
              > > > I followed the instructions given in the documents, but when i run
              > client
              > > program
              > > >
              > > > >java MQClient t3://localhost:7001 "MQSeries test"
              > > > I received the following exception below. Does anyone how what is the
              > > reason for
              > > >
              > > > this exception(s) and how i can solve the problem? My MQSeries Server
              > and
              > > Weblogic
              > > > 6.1 sp2 are installed on seperate NT machines. I installed the MQSeries
              > > classes
              > > > for java and the MQSeries classes for Java Message Service on the
              > weblogic
              > > > server machine.
              > > > ---------------------------------------
              > > > sending: "MQSEries test"
              > > > Exception in thread "main" java.rmi.ServerError: A error occurred the
              > > server; ne
              > > > sted exception is:
              > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
              > > >
              > > > Start server side stack trace:
              > > > java.rmi.ServerError: A error occurred the server; nested exception is:
              > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
              > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
              > > > at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
              > > > at java.lang.Runtime.loadLibrary0(Runtime.java:749)
              > > > at java.lang.System.loadLibrary(System.java:820)
              > > > at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
              > > > at java.security.AccessController.doPrivileged(Native Method)
              > > > at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
              > > > at
              > > com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
              > > > at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
              > > > at
              > > com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
              > > > 149)
              > > > at
              > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
              > > > tion(MQBindingsManagedConnectionFactoryJ11.java:139)
              > > > at
              > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
              > > > ion(MQBindingsManagedConnectionFactoryJ11.java:157)
              > > > at
              > > com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
              > > > a:80)
              > > > at
              > > com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
              > > > ctionManager.java:150)
              > > > at
              > > com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
              > > > a:666)
              > > > at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
              > > > at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
              > > > at
              > com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
              > > > at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
              > > > at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
              > > > at
              > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
              > > > at
              > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
              > > > at
              > > com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
              > > > )
              > > > at
              > > com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
              > > > AQueueConnectionFactory.java:53)
              > > > at
              > > weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
              > > > QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
              > > > at
              > > MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
              > > > at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
              > > > at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
              > > > at
              > > weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
              > > > at
              > > weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
              > > > a:267)
              > > > at
              > > weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
              > > > java:22)
              > > > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              > > > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              > > > End server side stack trace
              > > > ; nested exception is:
              > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
              > > >
              > > > Start server side stack trace:
              > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
              > > > at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
              > > > at java.lang.Runtime.loadLibrary0(Runtime.java:749)
              > > > at java.lang.System.loadLibrary(System.java:820)
              > > > at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
              > > > at java.security.AccessController.doPrivileged(Native Method)
              > > > at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
              > > > at
              > > com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
              > > > at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
              > > > at
              > > com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
              > > > 149)
              > > > at
              > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
              > > > tion(MQBindingsManagedConnectionFactoryJ11.java:139)
              > > > at
              > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
              > > > ion(MQBindingsManagedConnectionFactoryJ11.java:157)
              > > > at
              > > com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
              > > > a:80)
              > > > at
              > > com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
              > > > ctionManager.java:150)
              > > > at
              > > com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
              > > > a:666)
              > > > at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
              > > > at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
              > > > at
              > com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
              > > > at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
              > > > at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
              > > > at
              > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
              > > > at
              > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
              > > > at
              > > com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
              > > > )
              > > > at
              > > com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
              > > > AQueueConnectionFactory.java:53)
              > > > at
              > > weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
              > > > QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
              > > > at
              > > MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
              > > > at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
              > > > at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
              > > > at
              > > weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
              > > > at
              > > weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
              > > > a:267)
              > > > at
              > > weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
              > > > java:22)
              > > > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              > > > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              > > > End server side stack trace
              > > >
              > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
              > > >
              > > > Start server side stack trace:
              > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
              > > > at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
              > > > at java.lang.Runtime.loadLibrary0(Runtime.java:749)
              > > > at java.lang.System.loadLibrary(System.java:820)
              > > > at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
              > > > at java.security.AccessController.doPrivileged(Native Method)
              > > > at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
              > > > at
              > > com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
              > > > at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
              > > > at
              > > com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
              > > > 149)
              > > > at
              > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
              > > > tion(MQBindingsManagedConnectionFactoryJ11.java:139)
              > > > at
              > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
              > > > ion(MQBindingsManagedConnectionFactoryJ11.java:157)
              > > > at
              > > com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
              > > > a:80)
              > > > at
              > > com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
              > > > ctionManager.java:150)
              > > > at
              > > com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
              > > > a:666)
              > > > at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
              > > > at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
              > > > at
              > com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
              > > > at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
              > > > at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
              > > > at
              > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
              > > > at
              > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
              > > > at
              > > com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
              > > > )
              > > > at
              > > com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
              > > > AQueueConnectionFactory.java:53)
              > > > at
              > > weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
              > > > QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
              > > > at
              > > MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
              > > > at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
              > > > at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
              > > > at
              > > weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
              > > > at
              > > weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
              > > > a:267)
              > > > at
              > > weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
              > > > java:22)
              > > > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              > > > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              > > > End server side stack trace
              > > >
              > > > <<no stack trace available>>
              > > > --------------- nested within: ------------------
              > > > weblogic.rmi.extensions.RemoteRuntimeException - with nested exception:
              > > > [java.rmi.ServerError: A error occurred the server; nested exception is:
              > > >         java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
              > > >
              > > > Start server side stack trace:
              > > > java.rmi.ServerError: A error occurred the server; nested exception is:
              > > >         java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
              > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
              > > >         at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
              > > >         at java.lang.Runtime.loadLibrary0(Runtime.java:749)
              > > >         at java.lang.System.loadLibrary(System.java:820)
              > > >         at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
              > > >         at java.security.AccessController.doPrivileged(Native Method)
              > > >         at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
              > > >         at
              > > com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
              > > >         at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
              > > >         at
              > > com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
              > > > 149)
              > > >         at
              > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
              > > > tion(MQBindingsManagedConnectionFactoryJ11.java:139)
              > > >         at
              > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
              > > > ion(MQBindingsManagedConnectionFactoryJ11.java:157)
              > > >         at
              > > com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
              > > > a:80)
              > > >         at
              > > com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
              > > > ctionManager.java:150)
              > > >         at
              > > com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
              > > > a:666)
              > > >         at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
              > > >         at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
              > > >         at
              > com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
              > > >         at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
              > > >         at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
              > > >         at
              > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
              > > >         at
              > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
              > > >         at
              > > com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
              > > > )
              > > >         at
              > > com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
              > > > AQueueConnectionFactory.java:53)
              > > >         at
              > > weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
              > > > QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
              > > >         at
              > > MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
              > > >         at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
              > > >         at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
              > > >         at
              > > weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
              > > >         at
              > > weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
              > > > a:267)
              > > >         at
              > > weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
              > > > java:22)
              > > >         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              > > >         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              > > > End  server side stack trace
              > > > ; nested exception is:
              > > >         java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
              > > >
              > > > Start server side stack trace:
              > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
              > > >         at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
              > > >         at java.lang.Runtime.loadLibrary0(Runtime.java:749)
              > > >         at java.lang.System.loadLibrary(System.java:820)
              > > >         at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
              > > >         at java.security.AccessController.doPrivileged(Native Method)
              > > >         at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
              > > >         at
              > > com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
              > > >         at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
              > > >         at
              > > com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
              > > > 149)
              > > >         at
              > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
              > > > tion(MQBindingsManagedConnectionFactoryJ11.java:139)
              > > >         at
              > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
              > > > ion(MQBindingsManagedConnectionFactoryJ11.java:157)
              > > >         at
              > > com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
              > > > a:80)
              > > >         at
              > > com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
              > > > ctionManager.java:150)
              > > >         at
              > > com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
              > > > a:666)
              > > >         at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
              > > >         at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
              > > >         at
              > com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
              > > >         at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
              > > >         at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
              > > >         at
              > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
              > > >         at
              > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
              > > >         at
              > > com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
              > > > )
              > > >         at
              > > com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
              > > > AQueueConnectionFactory.java:53)
              > > >         at
              > > weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
              > > > QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
              > > >         at
              > > MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
              > > >         at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
              > > >         at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
              > > >         at
              > > weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
              > > >         at
              > > weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
              > > > a:267)
              > > >         at
              > > weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
              > > > java:22)
              > > >         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              > > >         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              > > > End  server side stack trace
              > > > ]
              > > > at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:60)
              > > > at $Proxy1.bridgeWLS2MQS(Unknown Source)
              > > > at MQClient.main(MQClient.java:54)
              > >
              > >
              

  • Transaction control with DI Server and B1WS

    Hi everyone,
    recentily I started working with DI server and B1WS, and talking with friends and with a brief research in the foruns Its seens to be impossible to have a Rollback in database transactions performed with DI server and B1WS.
    Its really true? I mean, I receive the Session ID when I use the login service, it shouldn't be so difficult to have a rollback function with this info...

    Really? Anyone knows?

  • Connectivity with sql server

    Dear community members;
    I am using Oracle 10g DB. Now I want to connect with SQL Server 2005. Is there any possiblity for connectivity. Because we have to pick some data from sqlserver on online transaction entry time.
    Waiting for usefull response.
    Thanks
    Shahab Ahmed Khan

    I am using oracle 11gR1 on windows 2003.
    This is my initaccessdb.ora(Path HS/ADMIN)
    HS_FDS_CONNECT_INFO = ACCESSDB
    HS_FDS_TRACE_LEVEL = OFF
    Listner File
    LISTENER =
    (DESCRIPTION_LIST =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1))
    (ADDRESS = (PROTOCOL = TCP)(HOST = APPSERVER)(PORT = 1521))
    SID_LIST_LISTENER=
    (SID_LIST=
    (SID_DESC=
    (SID_NAME=PLSExtProc)
    (ORACLE_HOME=E:\app\Administrator\product\11.1.0\db_1)
    (PROGRAM=extproc)
         (SID_DESC =
         (SID_NAME = accessdb)
    (ORACLE_HOME = E:\app\Administrator\product\11.1.0\db_1)
    (PROGRAM = ACCESSDB)
         (ENVS=LD_LIBRARY_PATH=D:\)      
    TNSNAME.ORA
    ORCL =
    (DESCRIPTION =
         (ADDRESS = (PROTOCOL = TCP)(HOST = 172.16.0.14)(PORT = 1521))
         (CONNECT_DATA =
              (SERVER = DEDICATED)
              (SERVICE_NAME= ORCL)
    ACCESSDB =
    (DESCRIPTION=
         (ADDRESS =(PROTOCOL = TCP)(HOST=172.16.0.14)(PORT=1521))
              (CONNECT_DATA =
              (SERVICE_NAME=ACCESSDB))
                   (HS = OK)
    I successfully completed all steps as mentioned in your sending links documents but when i test my dblink query it gives the error message
    SQL> conn sys as sysdba
    Enter password:
    Connected.
    SQL> conn ahmed
    Enter password:
    Connected.
    SQL> drop database link test;
    Database link dropped.
    SQL> create database link test using 'ACCESSDB';
    Database link created.
    SQL> SELECT * FROM EMPLOYEE@TEST;
    SELECT * FROM EMPLOYEE@TEST
    ERROR at line 1:
    ORA-28545: error diagnosed by Net8 when connecting to an agent
    Unable to retrieve text of NETWORK/NCR message 65535
    ORA-02063: preceding 2 lines from TEST
    Note: Please tell me that should i install ODBC driver ("Microsoft Access Driver *.mdb).If this should be installed then i have done correctly.
    Thanks

  • Sql Exception on Testing Configuration with SQL Server JDBC driver for XA

    I have a requirement of analyzing the behavior of SQL Server JDBC data sources for XA transactions in our application.We have been using Non-XA drivers for both Oracle and SQL Server as we had no requirement for transactions spanning across multiple databases in past.I have setup and tested the XA driver for Oracle (Oracle Driver (Thin XA) for Instance Connections 9.0.1,9.2.0,10,11) in Weblogic 11g and its working perfectly for transactions spanning across two databases.No when I am trying to configure weblogic 11g R1 for Sql server JDBC driver to support XA transactions with driver details as follows,
    Server:Weblogic 11g R1
    Driver Type: MS Sql Server
    Database Driver :Oracle's MS SQL Server Driver(Type 4 XA) Version:7.0,2000,2005)
    Database:SQL Server 2005(Single Instance)
    and try to create a new data source and select "Test Configuration" and following error is thrown ,
    <Mar 17, 2011 4:49:49 PM GMT+05:30> <Error> <Console> <BEA-240003> <Console encountered the following error java.sql.SQLException: [OWLS][SQLServer JDBC Driver][SQLServer]xa_open (0) returns -3
    at weblogic.jdbc.sqlserverbase.BaseExceptions40.createAppropriateSQLExceptionInstance(Unknown Source)
    at weblogic.jdbc.sqlserverbase.BaseExceptions40.createSQLException(Unknown Source)
    at weblogic.jdbc.sqlserverbase.BaseExceptions.createException(Unknown Source)
    at weblogic.jdbc.sqlserverbase.BaseExceptions.getException(Unknown Source)
    at weblogic.jdbc.sqlserver.tds.TDSRequest.processErrorToken(Unknown Source)
    at weblogic.jdbc.sqlserver.tds.TDSRequest.processReplyToken(Unknown Source)
    at weblogic.jdbc.sqlserver.tds.TDSRPCRequest.processReplyToken(Unknown Source)
    at weblogic.jdbc.sqlserver.tds.TDSRequest.processReply(Unknown Source)
    at weblogic.jdbc.sqlserver.SQLServerImplStatement.getNextResultType(Unknown Source)
    at weblogic.jdbc.sqlserverbase.BaseStatement.commonTransitionToState(Unknown Source)
    at weblogic.jdbc.sqlserverbase.BaseStatement.postImplExecute(Unknown Source)
    at weblogic.jdbc.sqlserverbase.BasePreparedStatement.postImplExecute(Unknown Source)
    at weblogic.jdbc.sqlserverbase.BaseStatement.commonExecute(Unknown Source)
    at weblogic.jdbc.sqlserverbase.BaseStatement.executeUpdateInternal(Unknown Source)
    at weblogic.jdbc.sqlserverbase.BasePreparedStatement.executeUpdate(Unknown Source)
    at weblogic.jdbcx.sqlserver.SQLServerImplXAResource.executeXaRpc(Unknown Source)
    at weblogic.jdbcx.sqlserver.SQLServerImplXAResource.executeXaRpc(Unknown Source)
    at weblogic.jdbcx.sqlserver.SQLServerImplXAResource.open(Unknown Source)
    at weblogic.jdbcx.sqlserverbase.BaseXAConnection.init(Unknown Source)
    at weblogic.jdbcx.sqlserverbase.BaseXAConnection40.init(Unknown Source)
    at weblogic.jdbc.sqlserverbase.BaseClassCreatorForJDBC40.createXaConnection(Unknown Source)
    at weblogic.jdbcx.sqlserverbase.BaseXADataSource.getXAConnection(Unknown Source)
    at com.bea.console.utils.jdbc.JDBCUtils.testConnection(JDBCUtils.java:550)
    at com.bea.console.actions.jdbc.datasources.createjdbcdatasource.CreateJDBCDataSource.testConnectionConfiguration(CreateJDBCDataSource.java:450)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.apache.beehive.netui.pageflow.FlowController.invokeActionMethod(FlowController.java:870)
    at org.apache.beehive.netui.pageflow.FlowController.getActionMethodForward(FlowController.java:809)
    at org.apache.beehive.netui.pageflow.FlowController.internalExecute(FlowController.java:478)
    at org.apache.beehive.netui.pageflow.PageFlowController.internalExecute(PageFlowController.java:306)
    at org.apache.beehive.netui.pageflow.FlowController.execute(FlowController.java:336)
    at org.apache.beehive.netui.pageflow.internal.FlowControllerAction.execute(FlowControllerAction.java:52)
    at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431)
    at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.access$201(PageFlowRequestProcessor.java:97)
    at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor$ActionRunner.execute(PageFlowRequestProcessor.java:2044)
    at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors$WrapActionInterceptorChain.continueChain(ActionInterceptors.java:64)
    at org.apache.beehive.netui.pageflow.interceptor.action.ActionInterceptor.wrapAction(ActionInterceptor.java:184)
    at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors$WrapActionInterceptorChain.invoke(ActionInterceptors.java:50)
    at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors$WrapActionInterceptorChain.continueChain(ActionInterceptors.java:58)
    at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors.wrapAction(ActionInterceptors.java:87)
    at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processActionPerform(PageFlowRequestProcessor.java:2116)
    at com.bea.console.internal.ConsolePageFlowRequestProcessor.processActionPerform(ConsolePageFlowRequestProcessor.java:261)
    at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236)
    at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processInternal(PageFlowRequestProcessor.java:556)
    at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.process(PageFlowRequestProcessor.java:853)
    at org.apache.beehive.netui.pageflow.AutoRegisterActionServlet.process(AutoRegisterActionServlet.java:631)
    at org.apache.beehive.netui.pageflow.PageFlowActionServlet.process(PageFlowActionServlet.java:158)
    at com.bea.console.internal.ConsoleActionServlet.process(ConsoleActionServlet.java:256)
    at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414)
    at com.bea.console.internal.ConsoleActionServlet.doGet(ConsoleActionServlet.java:133)
    at org.apache.beehive.netui.pageflow.PageFlowUtils.strutsLookup(PageFlowUtils.java:1199)
    at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.executeAction(ScopedContentCommonSupport.java:686)
    at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.processActionInternal(ScopedContentCommonSupport.java:142)
    at com.bea.portlet.adapter.scopedcontent.PageFlowStubImpl.processAction(PageFlowStubImpl.java:106)
    at com.bea.portlet.adapter.NetuiActionHandler.raiseScopedAction(NetuiActionHandler.java:111)
    at com.bea.netuix.servlets.controls.content.NetuiContent.raiseScopedAction(NetuiContent.java:181)
    at com.bea.netuix.servlets.controls.content.NetuiContent.raiseScopedAction(NetuiContent.java:167)
    at com.bea.netuix.servlets.controls.content.NetuiContent.handlePostbackData(NetuiContent.java:225)
    at com.bea.netuix.nf.ControlLifecycle$2.visit(ControlLifecycle.java:180)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:324)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:130)
    at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:395)
    at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361)
    at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:352)
    at com.bea.netuix.nf.Lifecycle.runInbound(Lifecycle.java:184)
    at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:159)
    at com.bea.netuix.servlets.manager.UIServlet.runLifecycle(UIServlet.java:388)
    at com.bea.netuix.servlets.manager.UIServlet.doPost(UIServlet.java:258)
    at com.bea.netuix.servlets.manager.UIServlet.service(UIServlet.java:199)
    at com.bea.netuix.servlets.manager.SingleFileServlet.service(SingleFileServlet.java:251)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    at com.bea.console.utils.MBeanUtilsInitSingleFileServlet.service(MBeanUtilsInitSingleFileServlet.java:47)
    at weblogic.servlet.AsyncInitServlet.service(AsyncInitServlet.java:130)
    at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
    at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
    at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
    at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3592)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
    at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2202)
    at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108)
    at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    I followed the instruction in weblogic jdbc drivers guide to configure the JTA Transactions to support XA on SQL Server machine and weblogic server which included,
    1.Copying sqljdbc.dll copied to SQL_Server_Root/bin directory from WL_HOME\server\lib.
    2.Copied instjdbc.sql to sql server machine and executed the script with following output,
    Changed database context to 'master'.
    Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
    Cannot drop the procedure 'xp_jdbc_open', because it does not exist or you do not have permission.
    Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
    Cannot drop the procedure 'xp_jdbc_open2', because it does not exist or you do not have permission.
    Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
    Cannot drop the procedure 'xp_jdbc_close', because it does not exist or you do not have permission.
    Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
    Cannot drop the procedure 'xp_jdbc_close2', because it does not exist or you do not have permission.
    Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
    Cannot drop the procedure 'xp_jdbc_start', because it does not exist or you do not have permission.
    Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
    Cannot drop the procedure 'xp_jdbc_start2', because it does not exist or you do not have permission.
    Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
    Cannot drop the procedure 'xp_jdbc_end', because it does not exist or you do not have permission.
    Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
    Cannot drop the procedure 'xp_jdbc_end2', because it does not exist or you do not have permission.
    Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
    Cannot drop the procedure 'xp_jdbc_prepare', because it does not exist or you do not have permission.
    Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
    Cannot drop the procedure 'xp_jdbc_prepare2', because it does not exist or you do not have permission.
    Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
    Cannot drop the procedure 'xp_jdbc_commit', because it does not exist or you do not have permission.
    Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
    Cannot drop the procedure 'xp_jdbc_commit2', because it does not exist or you do not have permission.
    Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
    Cannot drop the procedure 'xp_jdbc_rollback', because it does not exist or you do not have permission.
    Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
    Cannot drop the procedure 'xp_jdbc_rollback2', because it does not exist or you do not have permission.
    Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
    Cannot drop the procedure 'xp_jdbc_forget', because it does not exist or you do not have permission.
    Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
    Cannot drop the procedure 'xp_jdbc_forget2', because it does not exist or you do not have permission.
    Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
    Cannot drop the procedure 'xp_jdbc_recover', because it does not exist or you do not have permission.
    Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
    Cannot drop the procedure 'xp_jdbc_recover2', because it does not exist or you do not have permission.
    creating JDBC XA procedures
    instxa.sql completed successfully.
    3.Verified that MSDTC service is running on both SQL Server and weblogic machines with XA Transaction enabled and DTC option enabled for both inbound and outbound connections.
    4.Copied sqljdbc.jar (version 3.0 downloaded from msdn portal) to "C:\Oracle\Middleware\wlserver_10.3\server\ext\jdbc\sqlserver" directory and updated weblogic_classpth variable in commEnv.cmd file.
    set WEBLOGIC_CLASSPATH=%JAVA_HOME%\lib\tools.jar;%BEA_HOME%\utils\config\10.3\config-launch.jar;%WL_HOME%\server\lib\weblogic_sp.jar;%WL_HOME%\server\lib\weblogic.jar;%FEATURES_DIR%\weblogic.server.modules_10.3.2.0.jar;%WL_HOME%\server\lib\webservices.jar;%ANT_HOME%/lib/ant-all.jar;%ANT_CONTRIB%/lib/ant-contrib.jar;C:\Oracle\Middleware\wlserver_10.3\server\ext\jdbc\sqlserver\server\ext\jdbc\sqlserver\sqljdbc.jar
    Can some one please provide some input on whats causing this and any other steps needs to be followed to implement XA support using SQL Server JDBC driver.

    You seem to have done everything correctly and diligently. I would ask that you open
    an official support case.

  • How to set up SAPconnect with email server

    Hi,
    Does any one know <b>how to set up SAPconnect with email server</b>
    We are using workflow and when it fails it we are sending the notification mail to the user on his company mail id, i.e. [email protected]
    This is working in the current production system. We are doing the new development which will replace the current production system. The existing Basis team does not know how it was setup in production system and how to set it up in the new system.
    When we send any mail notification from workflow we can see the mail in SCOT transaction but it is not received at the specified mail address.
    Can any one provide the configuration steps or any document for this.
    Thanks in advance..
    Pratik

    Hi Pratik,
    Check the following link:-
    /people/thomas.jung3/blog/2004/09/08/sending-e-mail-from-abap--version-610-and-higher--bcs-interface
    http://help.sap.com/saphelp_nw04/helpdata/en/2b/d925bf4b8a11d1894c0000e8323c4f/frameset.htm
    these link will help u to config SMTP.
    And one more thing u have to do..
    Go to SE11 n open Table sxnodes in change mode.
    And change F_ESMTP field to false i.e. BLANK for the Field NODE = SMTP.
    Hope this will work For U.
    Regards
    Sachin Dhingra

  • DeadLocks on Query Notifications with SQL Server 2008 SP3

    Hello,
    according to this article https://support.microsoft.com/kb/975090 the issue with deadlocks on query notifications should be fixed with SQL Server 2008 SP3 (10.0.5500.0). But we still get deadlocks in the following manner:
    <resource-list>
    <keylock hobtid="72057598393909248" dbid="5" objectname="MyDB.sys.query_notification_1411013420" indexname="cidx" id="lock1731c1f00" mode="RangeX-X" associatedObjectId="72057598393909248">
    <owner-list>
    <owner id="process573dc8" mode="RangeX-X"/>
    </owner-list>
    <waiter-list>
    <waiter id="process58ddc8" mode="RangeS-U" requestType="wait"/>
    </waiter-list>
    </keylock>
    <keylock hobtid="72057598372872192" dbid="5" objectname="MyDB.sys.query_notification_253437289" indexname="cidx" id="lock800c8780" mode="RangeS-U" associatedObjectId="72057598372872192">
    <owner-list>
    <owner id="process58ddc8" mode="RangeS-U"/>
    </owner-list>
    <waiter-list>
    <waiter id="process573dc8" mode="RangeS-U" requestType="wait"/>
    </waiter-list>
    </keylock>
    </resource-list>
    Is there any need to install another fix?
    Thanks in Advance!

    Hello,
    SQL Server 2008 SP4 and all cumulative updates of SP3 do not have fixes related to deadlocks.
    Maybe the following workarounds and solutions can help in your scenario.
    http://stackoverflow.com/questions/3707137/understanding-deadlocks-with-sql-server-query-notifications
    Deadlock Prevention. In case you need to lock multiple conversation groups in a transaction, you need to take the same order to lock the different conversation groups in all transactions, otherwise you will have a deadlock issues.
    Source:
    http://blogs.msdn.com/b/kangmo/archive/2008/12/17/a-brief-guide-on-sql-server-service-broker.aspx
    Try to may transactions more simple and shorter.
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com

  • Problem with BizTalk server 2013 SFTP adapter on Cloud VM

    All, 
    We have deployed Microsoft Biztalk Server 2013 Enterprise edition on a cloud VM. We are facing an issue with SFTP adapter to receive. Following are the details; 
    On this VM, we are facing an issue with BizTalk server 2013 SFTP adapter. The SFTP location can receive and send message through SFTP clients and .Net code. But using BizTalk server 2013 SFTP adapter we are only able to send the file on SFTP location but
    could not receive the files from same location.
    We are getting  just one line error in system event log that is :
    Event#7011. A timeout (30000 milliseconds) was reached while waiting for a transaction response from the BTSSvc$BizTalkServerApplication service.
    Regards, 
    Shoaib Danish

    Hi
    BizTalk Server 2013 is available on Windows Azure. BizTalk Server 2013 can be installed locally on your hardware
    and in Windows Azure as a virtual machine. Please follow the procedures to check it on your side.
    Configuring BizTalk Server 2013 on a Windows Azure VM
    Create a BizTalk Virtual Machine in Windows Azure
    Create the BizTalk Group Prerequisites
    Configure the BizTalk Group
    Best regards
    Angie
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • How to call a transaction with a variant

    Hi all
    I created a bdc program after updating it should call another transaction with predefined variant that that transaction program is of type module pool.
    can anyone tell me the syntax how to call a transaction with a variant.

    Hi
    goto Tcode SHD0
    enter the Tcode for which Tran Variant has to be created(dialog Tcode)
    enter Trans variant to be created
    press create button
    it will go through all the screens of that Tcode and save
    and modify the fields as per requirement
    we can create Transaction Variants Using SHD0 Transaction.
    Transaction Variants and Screen Variants
    Transaction variants can simplify transaction runs as they allow you to:
    Preassign values to fields
    Hide and change the 'ready for input' status of fields
    Hide and change table control column attributes
    Hide menu functions
    Hide entire screens
    In particular, hiding fields in connection with screen compression, and hiding screens, can result in greater clarity and simplicity.
    Transaction variants are made up of a sequence of screen variants. The field values and field attributes for the individual screens found in transaction variants are stored in screen variants. Each of these variants is assigned to a specific transaction, can, however, also contain values for screens in other transactions if this is required by transaction flow. The transaction that the variant is assigned to serves as initial transaction when the variant is called.
    There are both client-specific and cross-client transaction variants. All screen variants are cross-client, but may be assigned to a client-specific transaction variant.
    A namespace exists for cross-client transaction variants and screen variants and both are automatically attached to the Transport Organizer. Client-specific transaction variants must be transported manually.
    In principle, transaction and screen variants can be created for all dialog and reporting transactions. There are, however, certain Restrictions that apply to certain transactions, depending on their internal structure.
    No transaction variants are possible with transactions already containing preset parameters (parameter transactions and variant transactions).
    Regards
    Anji

  • Using Weblogic MDB to consume message using a XA transaction with third party JMS Provider

              I understood from the WebLogic documentation that we can invoke a third party JMS
              using its XA interface from within a MDB where transaction-type is Container and
              trans-attribute is Required. Also we will need to specify its XAConnection factory
              name as connection-factory-jndi name. It that sufficient ?? Or do i need to set
              up some other attributes also ??.
              

              Hi Neeru,
              I understand u were able to solve this issue.
              I am using similar kind of configuration but instead of tibco i am using Webmethods.
              Could u please let me know what did u do to solve the problem?
              -thanks and regards.
              Praveen
              "Neeru Munjal" <[email protected]> wrote:
              >
              >Hi Rob,
              >I used the same whitepaper and tried to use TIBCO JMS with Weblogic server),
              >I
              >started with MDB example specified in Weblogic 7.0 release in examples/ejb20/message
              >and modified it to use trans-attribute as Required. Also I used connection
              >factory
              >which supports XA, but my MDB does not get called.
              >
              >Thanks & Regards
              >Neeru
              >
              >Rob Woollen <[email protected]> wrote:
              >>Here's a white paper about integrating 3rd party JMS providers with
              >WLS:
              >>
              >>http://dev2dev.bea.com/resourcelibrary/whitepapersdetail.jsp?highlight=whitepapers&filePath=components%2Fdev2dev%2Fresourcelibrary%2Fwhitepapers%2Fwp_jmsproviders.htm
              >>
              >>-- Rob
              >>
              >>Neeru Munjal wrote:
              >>> I understood from the WebLogic documentation that we can invoke a
              >third
              >>party JMS
              >>> using its XA interface from within a MDB where transaction-type is
              >>Container and
              >>> trans-attribute is Required. Also we will need to specify its XAConnection
              >>factory
              >>> name as connection-factory-jndi name. It that sufficient ?? Or do
              >i
              >>need to set
              >>> up some other attributes also ??.
              >>>
              >>
              >
              

  • Kpro usages with common server storage and Content server storage

    Hi Sap Gurus,
    Can any one tell me is KPro tick that we make in Document type if it is related to the storage types we are going to use,
    Can this KPro feature for Document type can be used for any document type irrespective of the Storage type, like weather storage type may be Vault, Archive, SAP DataBase, or the Content Server,
    let me also know waht is the benifits of going for this Kpro Tick in Document type (apart from Storing n no of original files in the DIR)
    we are trying to store original files in acommon Server (not content server) can we avail all the features of Kpro Tick.
    Points awaiting,
    Thanks and regards
    Shanti

    Hi,
    Kpro marked in any of the document type is for indication of using content server as a external storage system.
    Yes, Kpro can be ticked to any document type but since this is related to only external storage device so this wont support storage systems like Sap Database, Vault but supports to Archieve through Archievelink interface.
    Benefits are many and depends upon the business requirement..
    1. all the documents related to the organisation can be storaged in external content server rather thn in SAP database of R/3 system which avoids load on R/3 database.
    2. as you said, n number of files can be attached.
    3. it can be used in terms of attachments in Additional files, product stucture and so on.
    4. if Content sever is used also along with cache server then this main server can be used as a central storage location from where globally users can do transaction of documents without and error and in short time.
    Only Kpro storage provides all the functionality, you will be using common server which will be only accesible for storage purpose but not for the extra functions which Kpro provides..
    hope this helps u..
    Thank You,
    Manoj
    pls consider points if useful..!!

  • Error in Full Deployment in ATG 10.0.3 with JBOSS server.

    Hi All,
    I'm getting following error while full deployment in ATG 10.0.3 (OS : Linux) with JBOSS server,
    ERROR [ProductCatalog_production] SQL Statement Failed: [++SQLDelete++]
    DELETE FROM dcs_folder WHERE folder_id = ?
    -- Parameters --
    p[1] = {pd: id} fld330005 (atg.adapter.gsa.SingleValueGSAId)
    [--SQLDelete--]
    Can you please give answer to fix this issue!!!
    Thanks & Regards,
    Murail.Ch
    Edited by: Murali.Chitturi on Mar 11, 2013 9:33 PM

    Hi Shaik,
    2013-03-11 19:53:20,883 INFO [nucleusNamespace.atg.epub.DeploymentServer] (RepositoryWorkerThread-1(Pre-Deployment)) DEBUG 1100002:Production:atg.deployment.adapter.DistributedDeploymentAdapter$ApplyCommittedSynchronization.afterCompletion(DistributedDeploymentAdapter.java:3285) ApplyCommittedSynchronization.afterCompletion
    2013-03-11 19:54:54,342 WARN [com.arjuna.ats.jta.logging.loggerI18N] (Thread-14) [com.arjuna.ats.internal.jta.recovery.xarecovery1] Local XARecoveryModule.xaRecovery got XA exception javax.transaction.xa.XAException, XAException.XAER_RMERR
    2013-03-11 19:54:54,344 WARN [com.arjuna.ats.jta.logging.loggerI18N] (Thread-14) [com.arjuna.ats.internal.jta.recovery.xarecovery1] Local XARecoveryModule.xaRecovery got XA exception javax.transaction.xa.XAException, XAException.XAER_RMERR
    2013-03-11 19:54:54,346 WARN [com.arjuna.ats.jta.logging.loggerI18N] (Thread-14) [com.arjuna.ats.internal.jta.recovery.xarecovery1] Local XARecoveryModule.xaRecovery got XA exception javax.transaction.xa.XAException, XAException.XAER_RMERR
    2013-03-11 19:54:54,348 WARN [com.arjuna.ats.jta.logging.loggerI18N] (Thread-14) [com.arjuna.ats.internal.jta.recovery.xarecovery1] Local XARecoveryModule.xaRecovery got XA exception javax.transaction.xa.XAException, XAException.XAER_RMERR
    *2013-03-11 19:54:58,477 ERROR [nucleusNamespace.atg.commerce.catalog.ProductCatalog_production] (RepositoryWorkerThread-3(Destination Synchronization)) SQL Statement Failed: [++SQLDelete++]*
    DELETE FROM dcs_folder
    WHERE folder_id = ?
    *-- Parameters --*
    *p[1] = {pd: id} fld350005 (atg.adapter.gsa.SingleValueGSAId)*
    *[--SQLDelete--]*
    2013-03-11 19:54:58,607 INFO [nucleusNamespace.atg.epub.DeploymentServer] (Main deployment thread: ) DEBUG 1100002:Production:atg.deployment.adapter.DistributedDeploymentAdapter.deploymentCompleted(DistributedDeploymentAdapter.java:3153) DeploymentListener.deploymentCompleted called for deployment with ID: 1100002
    2013-03-11 19:54:58,607 INFO [nucleusNamespace.atg.epub.DeploymentServer] (Main deployment thread: ) DEBUG 1100002:Production:atg.deployment.adapter.DistributedDeploymentAdapter.deploymentCompleted
    2013-03-11 19:57:05,407 WARN [com.arjuna.ats.jta.logging.loggerI18N] (Thread-14) [com.arjuna.ats.internal.jta.recovery.xarecovery1] Local XARecoveryModule.xaRecovery got XA exception javax.transaction.xa.XAException, XAException.XAER_RMERR
    2013-03-11 19:57:05,409 WARN [com.arjuna.ats.jta.logging.loggerI18N] (Thread-14) [com.arjuna.ats.internal.jta.recovery.xarecovery1] Local XARecoveryModule.xaRecovery got XA exception javax.transaction.xa.XAException, XAException.XAER_RMERR
    2013-03-11 19:57:05,411 WARN [com.arjuna.ats.jta.logging.loggerI18N] (Thread-14) [com.arjuna.ats.internal.jta.recovery.xarecovery1] Local XARecoveryModule.xaRecovery got XA exception javax.transaction.xa.XAException, XAException.XAER_RMERR
    2013-03-11 19:57:05,416 WARN [com.arjuna.ats.jta.logging.loggerI18N] (Thread-14) [com.arjuna.ats.internal.jta.recovery.xarecovery1] Local XARecoveryModule.xaRecovery got XA exception javax.transaction.xa.XAException, XAException.XAER_RMERR
    *2013-03-11 19:57:27,944 ERROR [nucleusNamespace.atg.commerce.catalog.ProductCatalog_production] (RepositoryWorkerThread-3(Destination Synchronization)) SQL Statement Failed: [++SQLDelete++]*
    DELETE FROM dcs_folder
    WHERE folder_id = ?
    *-- Parameters --*
    *p[1] = {pd: id} fld350006 (atg.adapter.gsa.SingleValueGSAId)*
    *[--SQLDelete--]*
    2013-03-11 19:57:28,452 INFO [nucleusNamespace.atg.epub.DeploymentServer] (Main deployment thread: ) DEBUG 1100002:Production:atg.deployment.adapter.DistributedDeploymentAdapter.deploymentCompleted(DistributedDeploymentAdapter.java:3153) DeploymentListener.deploymentCompleted called for deployment with ID: 1100002-switch
    The error is displaying in server.log. Above error is displaying in both ATG10.0.3 and ATG10.1.2
    Please suggest why this error is coming for both versions.
    Thanks in advance...
    Regards,
    Srinivasa R

  • Oracle ODBC Failed to enlist global transaction with DTC

    Hi Everyone,
    I have installed a COM+ application on a Windows Server 2008 R2 x64 machine. Which is using Oracle Client version 11.1.7.0 (32 bit).
    Application is using 11.1.7.0 (x64) Database running on another server with same OS. When I run some functionality in the application, I am getting a message saying
    "The Error [Oracle][ODBC]Failed to enlist global transaction with DTC".
    This error happened in a production environment. It is working on my test machine under same situation. The application is certified on above Oracle version.
    Please let me know what can be cause of the problem.
    Thanks & Regards,
    Anil

    I have the same problem with Oracle OLEDB provider also. Use
    Microsoft drivers they work and faster...
    Eddy

Maybe you are looking for

  • How can I change my primary apple id to a new email address?

    I have an apple id that is linked to an email address that will be changing?  I would somehow like to change my primary address so that I can still access my apple id via an email address that isn't an me.com account.  Also, I had other apple id acco

  • Ipod touch 3rd gen keeps crashing after 4.2.1 update

    so I downloaded the new iOS 4.2.1 update and ever since then my ipod touch 3rd generation (which is a refurb by the way) kept crashing -- didn't matter what app it was on (even on some of the programmed in apps), it would just crash and go back to th

  • Use of asp:Grid in SharePoint 2010

    Hi, I have a form in SharePoint where data from a table in Database is exposed to user via asp:Grid. This grid has bunch of input fields and checkboxes to represent data in the table. There is also a Save button on the form upon pressing it, data sho

  • API to update ap_invoices_all table

    Hello all, is there any API to update ap_invoices_all table? Please let me know. thanks,

  • SELECT FOR UPDATE with the SKIP LOCK clause

    Hi, I have a query regarding the SELECT FOR UPDATE with the SKIP LOCK clause. Whether this will be really good for parallel processing. Also if we are selecting a set of records in a cursor whether the lock will be done at the records level once we f