Stateful transactions - weblogic 81 integration server

I have a process that involves input from different clients within the process
life cycle. I use a standalone web service client to invoke the process. None
of the clients are human clients. How do I then ensure that the second client
gets a handle to the same process? This sounds a very simple question, but I am
unable to find the answer in the docs.
Thanks in advance
OR

Mike,
Thanks for that.
However I still don't understand how you set the conversational headers on the
web service proxy as generated using the weblogic clientgen tool.
Yes I can create a header, but I don't see how I pass it into the method call.
Again, any help much appreciated.
OR
"Mike Blevins" <[email protected]> wrote:
Oliver,
A WLI process has a conversation ID (what would normally be thought of
as an
instance id). If your web service clients use the same conversation id,
they'll go to the same process instance.
There's documentation for constructing the conversation id in the workshop
documentation, under:
How do I...
Web Service Clients
How Do I: Tell Developers of Non-WebLogic Workshop Clients
How
to Participate in Conversations?
"Oliver Roberts" <[email protected]> wrote in message
news:3f60689f$[email protected]..
I have a process that involves input from different clients withinthe
process
life cycle. I use a standalone web service client to invoke the process.None
of the clients are human clients. How do I then ensure that the secondclient
gets a handle to the same process? This sounds a very simple question,but
I am
unable to find the answer in the docs.
Thanks in advance
OR

Similar Messages

  • Transaction in Weblogic 5.1 Server

              Hi All,
              Can any one tell me How to set XA DataSource details in weblogic.properties
              file in weblogic 5.1 server.
              Thanx
              Ramana Murthy
              

    While they aren't java-specific, if you're looking for XA/2PC details,
    these 2 are good:
    Transaction Processing: Concepts and Techniques (Morgan Kaufmann Series
    in Data Management Systems)
    by Jim Gray, Andreas Reuter
    Principles of Transaction Processing
    by Philip A. Bernstein, Eric Newcomer (Contributor)
    5.1 does not support XA or 2 phase-commit. However, it does allow
    multiple cluster members to enlist in the same transaction as long as
    all database access goes through the same JDBC connection.
    WLS 6.0 and later do support XA and 2PC.
    -- Rob
    chandrasekar wrote:
    Hi all,
    Does Weblogic 5.1 support Distributed Transactions?.Please suggest me some
    books or documentation regarding Distributed Transactions, and about the XA compliant
    resources.

  • Error while starting weblogic 9.0 server .

    Hi ,
    When I start weblogic 9.0 server , I'm getting the following error and the server gets disconnected .
    JRockit dump produced after 0 days, 00:00:45 on Wed Jul 25 11:19:01 2007
    Additional information is available in:
    C:\bea92\user_projects\domains\dbAdapter\jrockit.1344.dump
    C:\bea92\user_projects\domains\dbAdapter\jrockit.1344.mdmp
    If you see this dump, please open a support case with BEA and
    supply as much information as you can on your system setup and
    the program you were running. You can also search for solutions
    to your problem at http://forums.bea.com in
    the forum jrockit.developer.interest.general.
    Error Message: Illegal memory access. [54]
    Exception Rec: EXCEPTION_ACCESS_VIOLATION (0xc0000005) at 0x0044CE73 - memory at 0x00000034 could not be read.
    Minidump : Wrote mdmp. Size is 173MB
    Version : BEA JRockit(R) R25.2.0-28 dra-45238-20050523-2021-win-ia32
    GC : System optimized over throughput (initial strategy singleparpar)
    : GC strategy for GC 0 was singleparpar
    : GC strategy for GC 1 was genparpar
    : mmHeap->data = 0x00620000, mmHeap->top = 0x10620000
    : mmStartCompaction = 0x0E622030, mmEndCompaction = 0x0F620000
    : Heap is not included in dumps.
    CPU : Intel Pentium 4 SSE SSE2 NetBurst
    Number CPUs : 1
    Tot Phys Mem : 1071628288
    OS version : Microsoft Windows XP Service Pack 2 (Build 2600)
    State : JVM is running
    I need to run embedded adapter using weblogic 9.0 .
    JRockit used is jrockit90_150_03.
    Please help me urgently.

    I have downloaded developer license ,but it's still throwing the error .
    To start WebLogic Server, use a username and *
    password assigned to an admin-level user. For *
    server administration, use the WebLogic Server *
    console at http:\\hostname:port\console *
    tarting weblogic with Java version:
    ava version "1.5.0_03"
    ava(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_03-b07)
    EA JRockit(R) (build dra-45238-20050523-2021-win-ia32, R25.2.0-28)
    tarting WLS with line:
    :\bea92\JROCKI~1\bin\java -jrockit -Xms256m -Xmx512m -Djrockit.codegen.optpriority=1 -Xverify:none -da -Dplatform.home
    \bea92\WEBLOG~1 -Dwls.home=C:\bea92\WEBLOG~1\server -Dwli.home=C:\bea92\WEBLOG~1\integration -Dweblogic.management.discov
    true -Dweblogic.ProductionModeEnabled= -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.di
    C:\bea92\patch_weblogic901\profiles\default\sysext_manifest_classpath -Dweblogic.Name=AdminServer -Djava.security.policy=C
    ea92\WEBLOG~1\server\lib\weblogic.policy weblogic.Server
    Jul 25, 2007 2:52:35 PM GMT+05:30> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with BEA JRockit(R) Vers
    dra-45238-20050523-2021-win-ia32 from BEA Systems, Inc.>
    Jul 25, 2007 2:52:37 PM GMT+05:30> <Info> <Management> <BEA-141107> <Version: WebLogic Server 9.0 Sun Jul 3 21:15:00 PDT
    5 598247 >
    Jul 25, 2007 2:52:40 PM GMT+05:30> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:
    nable to start WebLogic Server!
    xception occurred while reading the license file.
    lease make sure you have a valid license.bea
    ile in the BEA home directory associated with this
    nstallation. For more information about the license.bea
    ile, see the installation guide for the version of the
    oftware you are using at http://e-docs.bea.com.
    Jul 25, 2007 2:52:40 PM GMT+05:30> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
    Jul 25, 2007 2:52:40 PM GMT+05:30> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut
    elf down>
    Jul 25, 2007 2:52:40 PM GMT+05:30> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
    Could you please advise me as to what all I should inclde in the classpath to start weblogic 9.0 server.

  • Message File Adapter - XI Integration Server not arriving

    We have configured a file adapter to read a file.  According to the audit log the file is successfully read and converted to XML; however, the message is never posted to XI.  We have checked to make sure that no XI* users are locked and we have bounced the server.
    The following error message is listed in the audit log:
    Transmitting the message to endpoint http://kansbwul01:50000/sap/xi/engine/entry?action=execute using connection AFW failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: java.io.IOException: Error writing to server.
    The following is the application log:
    #1.5#0003BA54D61900190000000C000030E60003EEAAD1138641#1106842349700#/Applications/ExchangeInfrastructure/AdapterFramework/ThirdPartyRoot/comsap/Server/Adapter Framework##com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory.stop()######3e38f290707e11d996610003ba54d619#SAPEngine_System_Thread[impl:5]_35##0#0#Info#1#com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory#Java###The running MCF with GUID will be stopped now#1#8fa37160707811d995b00003ba54d619#
    #1.5#0003BA54D619001900000014000030E60003EEAAD16F4730#1106842355713#/Applications/ExchangeInfrastructure/AdapterFramework/ThirdPartyRoot/comsap/Server/Adapter Framework##com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory.stop()######3e38f290707e11d996610003ba54d619#SAPEngine_System_Thread[impl:5]_35##0#0#Info#1#com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory#Java###MCF with GUID was stopped successfully.#1#8fa37160707811d995b00003ba54d619#
    #1.5#0003BA54D619006000000009000030E60003EEAAD1A4DD9D#1106842359225#/Applications/ExchangeInfrastructure/AdapterFramework/ResourceAdapter/MessagingSystem/System/Clustering##com.sap.aii.af.ra.ms.runtime.MessagingSystem.reassignMessages(String, String[])#J2EE_GUEST#0#####SAPEngine_Application_Thread[impl:3]_11##0#0#Error#1#com.sap.aii.af.ra.ms.runtime.MessagingSystem#Java###Could not redistribute messages due to #1#LockingManager must be initialized before usage.#
    #1.5#0003BA54D6190040000000000000316A0003EEAAD9D40B8C#1106842496535#/Applications/ExchangeInfrastructure/AdapterFramework/Services/SecurityService##com.sap.aii.af.security.MessageSecurityServiceFrame.MessageSecurityServiceFrame.start()#######SAPEngine_System_Thread[impl:5]_24##0#0#Info#1#com.sap.aii.af.security.MessageSecurityServiceFrame#Java###QUEUE_CONNECTION_FACTORY: , ERROR_QUEUE: , QUEUE: , JARM_PREFIX: , JARM_USER: , JARM_ENABLED: .#6#jmsfactory/default/QueueConnectionFactory#jmsqueues/default/MessageSecurityErrorQueue#jmsqueues/default/MessageSecurityQueue#XI:Security:#XISecurityUser#false#
    #1.5#0003BA54D619004A000000060000316A0003EEAADD1ABF82#1106842551500#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File##com.sap.aii.adapter.file.File2XI.processFileList()#J2EE_GUEST#0#SAP J2EE Engine JTA Transaction : [016ffffffabffffffb60001]###9b9677a1707e11d9a9010003ba54d619#SAPEngine_Application_Thread[impl:3]_39##0#0#Error#1#com.sap.aii.adapter.file.File2XI#Plain###Module Exception 'com.sap.aii.af.mp.module.ModuleException: senderChannel 'c5a6ccb89b113e8c92474a4aa0df5858': Catching exception calling messaging system' found, cause: com.sap.aii.af.ra.ms.api.ConfigException: SLDAccess set to true, but not available.#
    #1.5#0003BA54D619004A000000080000316A0003EEAADD1AC8F6#1106842551503#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File##com.sap.aii.adapter.file.File2XI.processFileList()#J2EE_GUEST#0#SAP J2EE Engine JTA Transaction : [016ffffffabffffffb60001]###9b9677a1707e11d9a9010003ba54d619#SAPEngine_Application_Thread[impl:3]_39##0#0#Error#1#com.sap.aii.adapter.file.File2XI#Plain###Delivery Exception for guid'96f35561-707e-11d9-a16c-0003ba54d619' - non recoverable error, retry anyway#
    #1.5#0003BA54D619004A0000000A0000316A0003EEAADD1ACE8D#1106842551504#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File##com.sap.aii.adapter.file.File2XI.processFileList()#J2EE_GUEST#0####9b9677a1707e11d9a9010003ba54d619#SAPEngine_Application_Thread[impl:3]_39##0#0#Error#1#com.sap.aii.adapter.file.File2XI#Plain###Channel CDWExtFile: Sending file failed with com.sap.aii.af.ra.ms.api.ConfigException: SLDAccess set to true, but not available. - continue processing#
    #1.5#0003BA54D6190011000000FD0000316A0003EEAADF49F9C7#1106842588150#/Applications/ExchangeInfrastructure/AdapterFramework/ThirdPartyRoot/comsap/Server/Adapter Framework##com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory.SpiManagedConnectionFactory()######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Info#1#com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory#Plain###This SPIManagedConnectionFactory has the GUID: cc6372c0-707e-11d9-ca96-0003ba54d619#
    #1.5#0003BA54D6190011000001030000316A0003EEAADF4ADA00#1106842588207#/Applications/ExchangeInfrastructure/AdapterFramework/ThirdPartyRoot/comsap/Server/Adapter Framework##com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory.start()######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Info#1#com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory#Java###MCF with GUID is started now. (,)#3#cc6372c0707e11d9ca960003ba54d619#com.sap.engine.services.deploy.server.ApplicationLoader@5293b95#cc6372c0707e11d9ca960003ba54d619#
    #1.5#0003BA54D6190011000001090000316A0003EEAADF4AEA33#1106842588211#/Applications/ExchangeInfrastructure/AdapterFramework/ThirdPartyRoot/comsap/Server/Adapter Framework##com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory.start()######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Info#1#com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory#Java###MCF with GUID was started successfully.#1#cc6372c0707e11d9ca960003ba54d619#
    #1.5#0003BA54D6190051000000040000316A0003EEAAE1DFB940#1106842631518#/Applications/ExchangeInfrastructure/Repository#sap.com/com.sap.xi.repository#com.sap.aii.ib.core.applcomp.ApplicationComponent#J2EE_GUEST#0####e63e40d0707e11d9b8020003ba54d619#SAPEngine_Application_Thread[impl:3]_21##0#0#Info#1#com.sap.aii.ib.core.applcomp.ApplicationComponent#Plain###Startup of XI Application "REPOSITORY" ok.#
    #1.5#0003BA54D6190054000000170000316A0003EEAAE4BA42E1#1106842679394#/Applications/SL/UTIL##com.sap.sl.util.cvers.impl.DBConnector#J2EE_ADMIN#339####02bf9dd0707f11d9b9830003ba54d619#SAPEngine_Application_Thread[impl:3]_12##0#0#Error#1#com.sap.sl.util.cvers.impl.DBConnector#Plain###get data source CVERS failed! Trying SAP/BC_UME... #
    #1.5#0003BA54D619004C000000080000316A0003EEAAE692D9D6#1106842710366#/Applications/ExchangeInfrastructure/Directory#sap.com/com.sap.xi.directory#com.sap.aii.ib.core.applcomp.ApplicationComponent#J2EE_GUEST#0##kansbwul01.erc.ge.com_LB1_148575#Guest#d8164a70707e11d9a3490003ba54d619#SAPEngine_Application_Thread[impl:3]_26##0#0#Info#1#com.sap.aii.ib.core.applcomp.ApplicationComponent#Plain###Startup of XI Application "DIRECTORY" ok.#
    #1.5#0003BA54D619004D000000040000316A0003EEAAEB3DF548#1106842788689#/Applications/ExchangeInfrastructure/Directory#sap.com/com.sap.xi.directory#com.sap.aii.ib.server.util.BasicJMSClient#WSHAUN#466#SAP J2EE Engine JTA Transaction : [016ffffffabffffffb6000ffffff90]###43ec08c0707f11d99f8b0003ba54d619#SAPEngine_Application_Thread[impl:3]_32##0#0#Error#1#com.sap.aii.ib.server.util.BasicJMSClient#Plain###TopicConnectionFactory not found#
    #1.5#0003BA54D619004D000000050000316A0003EEAAEB3E07B0#1106842788693#/Applications/ExchangeInfrastructure/Directory#sap.com/com.sap.xi.directory#com.sap.aii.ib.server.util.BasicJMSClient#WSHAUN#466#SAP J2EE Engine JTA Transaction : [016ffffffabffffffb6000ffffff90]###43ec08c0707f11d99f8b0003ba54d619#SAPEngine_Application_Thread[impl:3]_32##0#0#Error#1#com.sap.aii.ib.server.util.BasicJMSClient#Plain###Exception during JMS startup for topic "SYNCHRONIZED_CACHE"
    Thrown:
    com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at java:comp, the whole lookup name is java:comp/env/jms/topic/xi/TopicConnectionFactory.
         at com.sap.engine.services.jndi.implserver.ServerContextImpl.getLastContainer(ServerContextImpl.java:258)
         at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:621)
         at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:344)
         at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:254)
         at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:271)
         at javax.naming.InitialContext.lookup(InitialContext.java:347)
         at javax.naming.InitialContext.lookup(InitialContext.java:347)
         at com.sap.aii.ib.server.util.BasicJMSClient.initJmsResources(BasicJMSClient.java:77)
         at com.sap.aii.ib.server.util.BasicJMSClient.init(BasicJMSClient.java:54)
         at com.sap.aii.ib.server.util.BasicJMSClient.<init>(BasicJMSClient.java:48)
         at com.sap.aii.ib.server.util.ClusterSyncedCache.<init>(ClusterSyncedCache.java:41)
         at com.sap.aii.ib.server.cpa.AdapterMDCache.<clinit>(AdapterMDCache.java:27)
         at com.sap.aii.ib.sbeans.misc.MiscServicesBean.getAdapterMetadata(MiscServicesBean.java:226)
         at com.sap.aii.ib.sbeans.misc.MiscServicesRemoteObjectImpl10.getAdapterMetadata(MiscServicesRemoteObjectImpl10.java:2028)
         at com.sap.aii.ib.sbeans.misc.MiscServicesRemoteObjectImpl10p4_Skel.dispatch(MiscServicesRemoteObjectImpl10p4_Skel.java:284)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:291)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:119)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
         at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
    #1.5#0003BA54D6190004000000060000316A0003EEAAED036F71#1106842818407#/Applications/SL/UTIL##com.sap.sl.util.cvers.impl.DBConnector######55770040707f11d9c6ea0003ba54d619#SAPEngine_System_Thread[impl:5]_16##0#0#Error#1#com.sap.sl.util.cvers.impl.DBConnector#Plain###get data source CVERS failed! Trying SAP/BC_UME... #
    #1.5#0003BA54D6190004000000120000316A0003EEAAED1F56F6#1106842820236#/Applications/SL/UTIL##com.sap.sl.util.cvers.impl.DBConnector######55770040707f11d9c6ea0003ba54d619#SAPEngine_System_Thread[impl:5]_16##0#0#Error#1#com.sap.sl.util.cvers.impl.DBConnector#Plain###get data source CVERS failed! Trying SAP/BC_UME... #
    #1.5#0003BA54D61900040000001E0000316A0003EEAAED2014BF#1106842820285#/Applications/SL/UTIL##com.sap.sl.util.cvers.impl.DBConnector######55770040707f11d9c6ea0003ba54d619#SAPEngine_System_Thread[impl:5]_16##0#0#Error#1#com.sap.sl.util.cvers.impl.DBConnector#Plain###get data source CVERS failed! Trying SAP/BC_UME... #
    #1.5#0003BA54D61900040000002A0000316A0003EEAAED20EE43#1106842820341#/Applications/SL/UTIL##com.sap.sl.util.cvers.impl.DBConnector######55770040707f11d9c6ea0003ba54d619#SAPEngine_System_Thread[impl:5]_16##0#0#Error#1#com.sap.sl.util.cvers.impl.DBConnector#Plain###get data source CVERS failed! Trying SAP/BC_UME... #
    #1.5#0003BA54D6190004000000360000316A0003EEAAED21A105#1106842820386#/Applications/SL/UTIL##com.sap.sl.util.cvers.impl.DBConnector######55770040707f11d9c6ea0003ba54d619#SAPEngine_System_Thread[impl:5]_16##0#0#Error#1#com.sap.sl.util.cvers.impl.DBConnector#Plain###get data source CVERS failed! Trying SAP/BC_UME... #
    #1.5#0003BA54D6190004000000420000316A0003EEAAED2268E0#1106842820438#/Applications/SL/UTIL##com.sap.sl.util.cvers.impl.DBConnector######55770040707f11d9c6ea0003ba54d619#SAPEngine_System_Thread[impl:5]_16##0#0#Error#1#com.sap.sl.util.cvers.impl.DBConnector#Plain###get data source CVERS failed! Trying SAP/BC_UME... #
    #1.5#0003BA54D61900040000004E0000316A0003EEAAED233205#1106842820489#/Applications/SL/UTIL##com.sap.sl.util.cvers.impl.DBConnector######55770040707f11d9c6ea0003ba54d619#SAPEngine_System_Thread[impl:5]_16##0#0#Error#1#com.sap.sl.util.cvers.impl.DBConnector#Plain###get data source CVERS failed! Trying SAP/BC_UME... #
    #1.5#0003BA54D61900040000005A0000316A0003EEAAED23EDCB#1106842820537#/Applications/SL/UTIL##com.sap.sl.util.cvers.impl.DBConnector######55770040707f11d9c6ea0003ba54d619#SAPEngine_System_Thread[impl:5]_16##0#0#Error#1#com.sap.sl.util.cvers.impl.DBConnector#Plain###get data source CVERS failed! Trying SAP/BC_UME... #
    #1.5#0003BA54D6190004000000660000316A0003EEAAED249350#1106842820580#/Applications/SL/UTIL##com.sap.sl.util.cvers.impl.DBConnector######55770040707f11d9c6ea0003ba54d619#SAPEngine_System_Thread[impl:5]_16##0#0#Error#1#com.sap.sl.util.cvers.impl.DBConnector#Plain###get data source CVERS failed! Trying SAP/BC_UME... #
    #1.5#0003BA54D6190051000000090000316A0003EEAAF39F13CA#1106842929271#/Applications/ExchangeInfrastructure/IntegrationServer#sap.com/com.sap.xi.services#com.sap.aii.ib.core.applcomp.ApplicationComponent#XIDIRUSER#526####97b7c160707f11d9837b0003ba54d619#SAPEngine_Application_Thread[impl:3]_21##0#0#Info#1#com.sap.aii.ib.core.applcomp.ApplicationComponent#Plain###Startup of XI Application "RUNTIME" ok.#
    #1.5#0003BA54D619003C0000000C0000316A0003EEAAFD1B729D#1106843088417#/Applications/ExchangeInfrastructure/AdapterFramework/ResourceAdapter/MessagingSystem/System/Queue##com.sap.aii.af.ra.ms.runtime.ListenerFinder.run()#J2EE_GUEST#0####b4a1c0b1707e11d98d600003ba54d619#SAPEngine_Application_Thread[impl:3]_19##0#0#Error#1#com.sap.aii.af.ra.ms.runtime.ListenerFinder#Java###Message listener could not be created for connection after attempts.#3#localejbs/TestListener#test#10#
    #1.5#0003BA54D6190058000000050000316A0003EEAB27D41690#1106843805160#/Applications/SL/UTIL##com.sap.sl.util.cvers.impl.DBConnector#J2EE_ADMIN#635####a1c95a40708111d9887c0003ba54d619#SAPEngine_Application_Thread[impl:3]_28##0#0#Error#1#com.sap.sl.util.cvers.impl.DBConnector#Plain###get data source CVERS failed! Trying SAP/BC_UME... #
    The following is the trace file:
    #1.5#0003BA54D6190000000000140000316A0003EEAAD72107D8#1106842451248#com.sap.engine.core.service630.container.ReferenceResolver##com.sap.engine.core.service630.container.ReferenceResolver#######Thread[Thread-1,5,main]##0#0#Error##Plain###Component com.sap.aii.af.security has a hard reference to service com.sap.aii.af.service.cpa with manual startup mode.#
    #1.5#0003BA54D6190036000000000000316A0003EEAAD94B1302#1106842487558#com.sap.engine.library.monitor.mapping.ccms.Trace##com.sap.engine.library.monitor.mapping.ccms.Trace#######SAPEngine_System_Thread[impl:5]_56##0#0#Info##Plain###************************************************************#
    #1.5#0003BA54D6190036000000010000316A0003EEAAD94C908B#1106842487656#com.sap.engine.library.monitor.mapping.ccms.Trace##com.sap.engine.library.monitor.mapping.ccms.Trace#######SAPEngine_System_Thread[impl:5]_56##0#0#Info##Plain###**************     CCMS CONNECTOR (System)    **************#
    #1.5#0003BA54D6190036000000020000316A0003EEAAD94C936D#1106842487657#com.sap.engine.library.monitor.mapping.ccms.Trace##com.sap.engine.library.monitor.mapping.ccms.Trace#######SAPEngine_System_Thread[impl:5]_56##0#0#Info##Plain###************************************************************#
    #1.5#0003BA54D6190036000000030000316A0003EEAAD94C9621#1106842487657#com.sap.engine.library.monitor.mapping.ccms.Trace##com.sap.engine.library.monitor.mapping.ccms.Trace#######SAPEngine_System_Thread[impl:5]_56##0#0#Info##Plain###Tracelevel: 0#
    #1.5#0003BA54D6190036000000040000316A0003EEAAD94E292D#1106842487760#com.sap.mona.api.MonitoringAgent##com.sap.mona.api.MonitoringAgent#######SAPEngine_System_Thread[impl:5]_56##0#0#Info##Plain###************************************************************#
    #1.5#0003BA54D6190036000000050000316A0003EEAAD94F65F2#1106842487842#com.sap.mona.api.MonitoringAgent##com.sap.mona.api.MonitoringAgent#######SAPEngine_System_Thread[impl:5]_56##0#0#Info##Java###*******     Java Monitoring API - Version      ********#1#1.8.8#
    #1.5#0003BA54D6190036000000060000316A0003EEAAD9525DA5#1106842488036#com.sap.mona.api.MonitoringAgent##com.sap.mona.api.MonitoringAgent#######SAPEngine_System_Thread[impl:5]_56##0#0#Info##Plain###************************************************************#
    #1.5#0003BA54D6190036000000070000316A0003EEAAD9547512#1106842488173#com.sap.mona.api.MonitoringAgent##com.sap.mona.api.MonitoringAgent#######SAPEngine_System_Thread[impl:5]_56##0#0#Info##Java###Host: , OS: , JDK: .#3#kansbwul01.erc.ge.com#SunOS_sparcv9_5.9#1.4.2_06#
    #1.5#0003BA54D6190036000000080000316A0003EEAAD95490A6#1106842488180#com.sap.mona.api.MonitoringAgent##com.sap.mona.api.MonitoringAgent#######SAPEngine_System_Thread[impl:5]_56##0#0#Info##Plain###Calculated library path: /global/usr/sap/LB1/DVEBMGS00/j2ee/cluster/server0/bin/ext/com.sap.mona.api#
    #1.5#0003BA54D6190036000000090000316A0003EEAAD954A29A#1106842488185#com.sap.mona.api.MonitoringAgent##com.sap.mona.api.MonitoringAgent#######SAPEngine_System_Thread[impl:5]_56##0#0#Info##Plain###System.load [2] /global/usr/sap/LB1/DVEBMGS00/j2ee/os_libs/libjmon.so#
    #1.5#0003BA54D61900360000000A0000316A0003EEAAD95617BA#1106842488280#com.sap.mona.api.MonitoringAgent##com.sap.mona.api.MonitoringAgent#######SAPEngine_System_Thread[impl:5]_56##0#0#Info##Java###Version of JNI library: .#1#3.12 Non-Unicode Version#
    #1.5#0003BA54D61900360000000B0000316A0003EEAAD9562000#1106842488283#com.sap.mona.api.MonitoringAgent##com.sap.mona.api.MonitoringAgent#######SAPEngine_System_Thread[impl:5]_56##0#0#Info##Java###Java tracelevel set to .#1#Error#
    #1.5#0003BA54D61900360000000C0000316A0003EEAAD9577C95#1106842488372#com.sap.mona.api.MonitoringAgent##com.sap.mona.api.MonitoringAgent#######SAPEngine_System_Thread[impl:5]_56##0#0#Info##Java###Connected () to segment (), , .#5#attach#0#read/write#system mode#40000000 bytes#
    #1.5#0003BA54D6190009000000010000316A0003EEAAD97D6C04#1106842490858#com.sap.aii.af.ra.ms.impl.core.queue.Queue##com.sap.aii.af.ra.ms.impl.core.queue.Queue.run()#######SAPEngine_System_Thread[impl:5]_73##0#0#Error##Java###Failed to retrieve message from MessageStore for queue .#2#aef38c80-707d-11d9-a639-0003ba54d619(OUTBOUND)#AFWSend#
    #1.5#0003BA54D6190014000000020000316A0003EEAAD988D5C9#1106842491606#com.sap.aii.af.ra.ms.impl.core.queue.Queue##com.sap.aii.af.ra.ms.impl.core.queue.Queue.run()#######SAPEngine_System_Thread[impl:5]_28##0#0#Error##Java###Failed to retrieve message from MessageStore for queue .#2#ea9f3be0-707c-11d9-834f-0003ba54d619(OUTBOUND)#AFWSend#
    #1.5#0003BA54D619003F000000000000316A0003EEAAD9CFB274#1106842496250#com.sap.aii.af.service.cpa.impl.cache.CacheManager##com.sap.aii.af.service.cpa.impl.cache.CacheManager.performCacheUpdate(boolean)#######SAPEngine_System_Thread[impl:5]_65##0#0#Error##Java###CPA Cache not updated with directory data, due to: #1#Couldn't open Directory URL (http://kansbwul01:50000/dir/hmi_cache_refresh_service/ext?method=CacheRefresh&mode=C&consumer=af.lb1.kansbwul01), due to: HTTP 503: Service Unavailable#
    #1.5#0003BA54D619003F000000010000316A0003EEAAD9D09295#1106842496307#com.sap.aii.af.service.cpa.impl.cache.CacheManager##com.sap.aii.af.service.cpa.impl.cache.CacheManager.performCacheUpdate(boolean)#######SAPEngine_System_Thread[impl:5]_65##0#0#Error##Java###Confirmation handling failed, due to: #1#Couldn't send confirmation, due to: Couldn't access Confirmation URL, due to: HTTP 503: Service Unavailable#
    #1.5#0003BA54D6190046000000000000316A0003EEAAD9E5FAD6#1106842497710#com.sap.aii.af.protocol.ispeak.clustercontext.ISPClusterContext##com.sap.aii.af.protocol.ispeak.clustercontext.ISPClusterContext.setCurrentNodeID(int)#######SAPEngine_System_Thread[impl:5]_43##0#0#Info#1#/Version#Plain###Current node set to 1485750#
    #1.5#0003BA54D6190046000000010000316A0003EEAAD9E62B77#1106842497723#com.sap.aii.af.protocol.ispeak.clustercontext.ISPClusterContext##com.sap.aii.af.protocol.ispeak.clustercontext.ISPClusterContext.setEnvironmentState(int)#######SAPEngine_System_Thread[impl:5]_43##0#0#Info#1#/Version#Plain###Environment state set to : ENV_INCOMPLETE#
    #1.5#0003BA54D6190049000000000000316A0003EEAAD9F40CB0#1106842498632#com.sap.aii.af.service.cpa.impl.container.CPAObjectEntry##com.sap.aii.af.service.cpa.impl.container.CPAObjectEntry.getValue(boolean)#######SAPEngine_System_Thread[impl:5]_77##0#0#Error##Java###Decryption failed, due to .#1#<null>#
    #1.5#0003BA54D6190049000000010000316A0003EEAAD9FB0888#1106842499090#com.sap.aii.af.service.cpa.impl.container.CPAObjectEntry##com.sap.aii.af.service.cpa.impl.container.CPAObjectEntry.getValue(boolean)#######SAPEngine_System_Thread[impl:5]_77##0#0#Error##Java###Decryption failed, due to .#1#<null>#
    #1.5#0003BA54D6190049000000020000316A0003EEAAD9FB3838#1106842499102#com.sap.aii.af.service.cpa.impl.container.CPAObjectEntry##com.sap.aii.af.service.cpa.impl.container.CPAObjectEntry.getValue(boolean)#######SAPEngine_System_Thread[impl:5]_77##0#0#Error##Java###Decryption failed, due to .#1#<null>#
    #1.5#0003BA54D6190049000000030000316A0003EEAAD9FB61D0#1106842499113#com.sap.aii.af.service.cpa.impl.container.CPAObjectEntry##com.sap.aii.af.service.cpa.impl.container.CPAObjectEntry.getValue(boolean)#######SAPEngine_System_Thread[impl:5]_77##0#0#Error##Java###Decryption failed, due to .#1#<null>#
    #1.5#0003BA54D6190009000000020000316A0003EEAADA5386CF#1106842504889#com.sap.aii.af.ra.ms.impl.core.queue.SendConsumer##com.sap.aii.af.ra.ms.impl.core.queue.SendConsumer.onMessage(QueueMessage)######9998abd0707e11d9cd270003ba54d619#SAPEngine_System_Thread[impl:5]_73##0#0#Error##Java###Transmitting the message to endpoint using connection failed, due to: .#3#AFW#com.sap.aii.af.ra.ms.api.RecoverableException: com.sap.aii.af.ra.ms.api.RecoverableException: java.io.IOException: Error writing to server#http://kansbwul01:50000/sap/xi/engine/entry?action=execute#
    #1.5#0003BA54D6190014000000030000316A0003EEAADA542AB7#1106842504931#com.sap.aii.af.ra.ms.impl.core.queue.SendConsumer##com.sap.aii.af.ra.ms.impl.core.queue.SendConsumer.onMessage(QueueMessage)######99afb640707e11d9a86c0003ba54d619#SAPEngine_System_Thread[impl:5]_28##0#0#Error##Java###Transmitting the message to endpoint using connection failed, due to: .#3#AFW#com.sap.aii.af.ra.ms.api.RecoverableException: com.sap.aii.af.ra.ms.api.RecoverableException: java.io.IOException: Error writing to server#http://kansbwul01:50000/sap/xi/engine/entry?action=execute#
    #1.5#0003BA54D619004D000000000000316A0003EEAADAF321D0#1106842515349#com.sap.aii.proxy.xiruntime.web.TransportServlet#sap.com/com.sap.xi.proxyserver#com.sap.aii.proxy.xiruntime.web.TransportServlet.init(...)#J2EE_GUEST#0####a1006c50707e11d99ea30003ba54d619#SAPEngine_Application_Thread[impl:3]_32##0#0#Info##Plain###Initialized#
    #1.5#0003BA54D619004D000000010000316A0003EEAADAF32B88#1106842515352#com.sap.aii.proxy.xiruntime.web.TransportServlet#sap.com/com.sap.xi.proxyserver#com.sap.aii.proxy.xiruntime.web.TransportServlet.init(...)#J2EE_GUEST#0####a1006c50707e11d99ea30003ba54d619#SAPEngine_Application_Thread[impl:3]_32##0#0#Info##Plain###Registered with Adapter Framework Monitor#
    #1.5#0003BA54D6190055000000010000316A0003EEAADCAC81FD#1106842544275#com.sap.pmi.io.HttpPostThread##com.sap.pmi.io.HttpPostThread######b1f90ee0707e11d9c4300003ba54d619#Thread[Thread-42,5,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/System/Server#Plain###Error sending PMI records to http://kansbwul01:8000/sap/bc/sapi_gate, HTTP response: 404Not found. Please check the HTTP destination "pmistore".#
    #1.5#0003BA54D619004A000000050000316A0003EEAADD1ABD1C#1106842551499#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.processFileList()#J2EE_GUEST#0#SAP J2EE Engine JTA Transaction : [016ffffffabffffffb60001]###9b9677a1707e11d9a9010003ba54d619#SAPEngine_Application_Thread[impl:3]_39##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Module Exception 'com.sap.aii.af.mp.module.ModuleException: senderChannel 'c5a6ccb89b113e8c92474a4aa0df5858': Catching exception calling messaging system' found, cause: com.sap.aii.af.ra.ms.api.ConfigException: SLDAccess set to true, but not available.#
    #1.5#0003BA54D619004A000000070000316A0003EEAADD1AC765#1106842551502#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.processFileList()#J2EE_GUEST#0#SAP J2EE Engine JTA Transaction : [016ffffffabffffffb60001]###9b9677a1707e11d9a9010003ba54d619#SAPEngine_Application_Thread[impl:3]_39##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Delivery Exception for guid'96f35561-707e-11d9-a16c-0003ba54d619' - non recoverable error, retry anyway#
    #1.5#0003BA54D619004A000000090000316A0003EEAADD1ACD22#1106842551504#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.processFileList()#J2EE_GUEST#0####9b9677a1707e11d9a9010003ba54d619#SAPEngine_Application_Thread[impl:3]_39##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CDWExtFile: Sending file failed with com.sap.aii.af.ra.ms.api.ConfigException: SLDAccess set to true, but not available. - continue processing#
    #1.5#0003BA54D619004A0000000C0000316A0003EEAADD1B3AEE#1106842551532#com.sap.engine.services.ts##com.sap.engine.services.ts#J2EE_GUEST#0####9b9677a1707e11d9a9010003ba54d619#SAPEngine_Application_Thread[impl:3]_39##0#0#Error#1#/System/Server#Java#ts_0021##Thread is not associated with any transaction context.##
    #1.5#0003BA54D619004A0000000D0000316A0003EEAADD1B41AE#1106842551533#com.sap.engine.services.ts##com.sap.engine.services.ts#J2EE_GUEST#0####9b9677a1707e11d9a9010003ba54d619#SAPEngine_Application_Thread[impl:3]_39##0#0#Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.ts.exceptions.BaseIllegalStateException: Thread is not associated with any transaction context.
         at com.sap.engine.services.ts.jta.impl.TransactionManagerImpl.rollback(TransactionManagerImpl.java:441)
         at com.sap.aii.adapter.file.File2XI.processFileList(File2XI.java:1756)
         at com.sap.aii.adapter.file.File2XI.run(File2XI.java:1007)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
    #1.5#0003BA54D6190011000000790000316A0003EEAADDAE5C4B#1106842561174#com.sap.engine.services.jmsconnector##com.sap.engine.services.jmsconnector######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Error#1#/System/Server#Plain###JMS Connector Container Application: sap.com/com.sap.xi.ibresources factory name: jms/topic/xi/TopicConnectionFactory loader does not exist:  . Using default class loader!!!#
    #1.5#0003BA54D61900110000007A0000316A0003EEAADDAFCE2B#1106842561269#com.sap.engine.services.jmsconnector##com.sap.engine.services.jmsconnector######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Error##Plain###Factory: jms/topic/xi/TopicConnectionFactory loader does not exist:  . Using default class loader!!!#
    #1.5#0003BA54D61900110000007C0000316A0003EEAADDAFE340#1106842561274#com.sap.engine.services.jmsconnector##com.sap.engine.services.jmsconnector######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Error#1#/System/Server#Plain###JMS Connector Container Application: sap.com/com.sap.xi.ibresources factory name: jms/queue/xi/QueueConnectionFactory loader does not exist:  . Using default class loader!!!#
    #1.5#0003BA54D61900110000007D0000316A0003EEAADDB040CB#1106842561298#com.sap.engine.services.jmsconnector##com.sap.engine.services.jmsconnector######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Error##Plain###Factory: jms/queue/xi/QueueConnectionFactory loader does not exist:  . Using default class loader!!!#
    #1.5#0003BA54D6190011000000B20000316A0003EEAADE6877ED#1106842573371#com.sap.engine.services.jmsconnector##com.sap.engine.services.jmsconnector######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Error#1#/System/Server#Plain###JMS Connector Container Application: sap.com/com.sap.aii.af.ispeak.app factory name: ISPXAConnectionFactory loader does not exist:  . Using default class loader!!!#
    #1.5#0003BA54D6190011000000B30000316A0003EEAADE68A1E8#1106842573382#com.sap.engine.services.jmsconnector##com.sap.engine.services.jmsconnector######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Error##Plain###Factory: ISPXAConnectionFactory loader does not exist:  . Using default class loader!!!#
    #1.5#0003BA54D6190011000000C10000316A0003EEAADE837B81#1106842575141#com.sap.aii.af.protocol.ispeak.clustercontext.ISPClusterContext##com.sap.aii.af.protocol.ispeak.clustercontext.ISPClusterContext.setEnvironmentState(int)######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Info#1#/Version#Plain###Environment state set to : ENV_COMPLETE#
    #1.5#0003BA54D6190011000000C20000316A0003EEAADE83D50E#1106842575164#com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPEventSession##com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPEventSession.initialize()######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Info#1#/Version#Plain###Looked up factory : com.sap.engine.services.jmsconnector.cci.QueueConnectionFactoryImpl@6cbd9138#
    #1.5#0003BA54D6190011000000C30000316A0003EEAADE83D78C#1106842575165#com.sap.aii.af.protocol.ispeak.j2ee.services.ISPStartupService##com.sap.aii.af.protocol.ispeak.j2ee.services.ISPStartupService.onAllAppStart()######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Info#1#/Version#Plain###Calling onServerStart on ISPClusterContext...#
    #1.5#0003BA54D6190011000000E60000316A0003EEAADF147D24#1106842584644#com.sap.engine.services.jmsconnector##com.sap.engine.services.jmsconnector######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Error#1#/System/Server#Plain###JMS Connector Container Application: sap.com/com.sap.ip.me.insttool factory name: InstToolTopicFactoryCreateEmptyImage loader does not exist:  . Using default class loader!!!#
    #1.5#0003BA54D6190011000000E70000316A0003EEAADF14A82D#1106842584655#com.sap.engine.services.jmsconnector##com.sap.engine.services.jmsconnector######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Error##Plain###Factory: InstToolTopicFactoryCreateEmptyImage loader does not exist:  . Using default class loader!!!#
    #1.5#0003BA54D6190011000000E90000316A0003EEAADF14B7A3#1106842584659#com.sap.engine.services.jmsconnector##com.sap.engine.services.jmsconnector######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Error#1#/System/Server#Plain###JMS Connector Container Application: sap.com/com.sap.ip.me.insttool factory name: InstToolTopicFactoryFinishImage loader does not exist:  . Using default class loader!!!#
    #1.5#0003BA54D6190011000000EA0000316A0003EEAADF14DC56#1106842584669#com.sap.engine.services.jmsconnector##com.sap.engine.services.jmsconnector######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Error##Plain###Factory: InstToolTopicFactoryFinishImage loader does not exist:  . Using default class loader!!!#

    The problem was the Pipeline URL for the integration server.
    http://<server>:50000/sap/xi/engine/entry?action=execute
    is the defective URL. 
    Once we logged into SLD and selected the business system for the integration server we change the pipeline URL to the following
    http://<server>:8000/sap/xi/engine?type=entry
    we then restarted the J2EE server and it worked fine.

  • Getting Error while  creating Integration server Connection ...PLS help me

    Hi everybody,
    While creating the Integration server connection I am getting the below error.
    Please help me to solve it.
    I am using 10.1.3.1 .
    Application Server: OK
    BPEL Process Manager Server: FAILED
    ESB Server: FAILED
    Thanks in advance.
    Ramana

    Now i can able to login to my weblogic admin console and find that listen address is blank i have given the listen address as localhost now i can able to create the application server connection successfully ...Listen address blank means your server will accept connections on all network addresses i.e. on localhost, on 127.0.0.1 and on IP/Host name of machine
    If you want to access this server from a remote machine as well, then better keep the listen address field as blank OR assign the value of hostname/IP of machine as listen address. In case you set listen address as hostname/IP of machine, server will not listen anymore to localhost or 127.0.0.1
    1)Now iam working in local machine so that i am giving localhost .... In case i doing some bpel work in my local machine and after completing the work if want to move to my server ...do i want to change the connectionand give my server hostname ha?If your BPEL server is a remote server then better create a new connection for that (using listen address and port of that server)
    How to see errors in Admin server log C:\Oracle\Middleware\user_projects\domains\Soa_base_domain\servers\AdminServer\logs ...is it i want to check it here?Yes, you need to check the logs in this directory in file AdminServer.log
    How to check this?Under $Domain_Home/bin (C:\Oracle\Middleware\user_projects\domains\Soa_base_domain\bin), there will be a file setSOADomainEnv.cmd. If you open this file using notepad, you would see a setting like below -
    set DEFAULT_MEM_ARGS=-Xms512m -Xmx768mThis setting defines the heap memory.
    Regards,
    Anuj

  • BPM Acknowledgement message reading the wrong integration server name

    HI
    I have a scenario where I have BPM which sends data to A MS SQL Server database and waits for a TRANSPORT Acknowledgement. The Mesage going to the Database is processed successfully but the acknowledgement messasge fails giving the following error when viewed in the message monitor.
    IS_DETAILS_GET_ERROR
    no_integration_server_found: Unable to find Integration Server is.XX.XXXXXXXX
    Error while reading access data (URL, user, password) of Integration Server is.XX.XXXXXXXX
    Actually the string "is.XX.XXXXXXXX" contains the name of the integration server.
    Now my problem is the actual  value contained in the above string is the name   of the integration server . But this name is not correct ,  I mean it is not what the actual name should be. We are not able to find out from where this incorrect name is being picked up. Can anyone tell from where the actaul name and url  of the integration server is read. Is it stored in different locations for inbound messages and acknowledgement msgs. Will refreshing any of the caches will help.
    Please suggest.
    regards
    Nilesh Taunk.

    Hi Nilesh,
    your problem is very strange because your BPM is sending data correctly to SQL DB .....your db is processed.....but the ack msg when coming in bpm gives IS_DETAILS_GET_ERROR.
    i think just see all the objects in IR and ID are activated.....after that by SXI_CACHE transaction do a cache refresh.........see the return code of BPM is zero or not......the retun code of BPM shuld be zero.......
    again run your this scenario.......now please tell what happens......
    Thanks,
    Rajeev Gupta

  • Services not showing in Integration Server.

    Hi,
      I have created File Adapter(Sender),RFC Adapter(Reciever) scenario in Integration Repository and Integration Directory. But none of Services,Communication Channels ,Receiver Determination etc are showing in Integration Server (transaction SXI_CACHE) after Activating them in Integration Directory.
    Cache clearing is happening properly(full and delta mode).
    Can anybody help, how to solve this problem.
    Regards
    Abhi

    Hi Michal,
    After installation of XI, CPACache refresh was failed.
    But now cache refresh is sucessfull when we tried with URL http://sapxiserver:port/CPACache/refresh?mode=full in browser.And when i try the following URL to check history
    http://server:50000/CPACache/history.jsp, no errors.
    Is there any other settings do I am missing? What are the possible cases Services are not shown in IS?
    Regards
    Abhi

  • Integration Server Queues Stopping

    Hi People,
    We are doing a FCC scenario (.CSV to XML), with the content conversion parameters as follows:
    Recordset Name: Recordset
    Recordset Structure: DataTable1,1
    Recordsets per message: 1
    As it is clear from the configuration, <b>when the source file will contain multiple line items, XI will create multiple XML files, each containing data for a single line item.</b> My problem is, <b>whenever the source file contains a large number of line items, I see them being picked up (In SXMB_MONI), but the Integration Server inbound queues stop and they show a green flag in MONI with tooltip "Message Scheduled On the Outbound Side". I have to go to SMQ2 and manually activate the queues to release the blocked messages.</b> How to alleviate this problem..because it is really irksome to go and everytime manually activate the queues. Is there any report that can be scheduled so that it caueses the queues to activate automatically when they are blocked?
    P.S: We can not change the design. Also, I have seen
    <a href="/people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically">Naveen Pandarangi's Blog On XI Message re-Scheduling</a>..but the report stated there is not working out for me!
    Awaiting your expert views,
    Thanks in anticipation,
    Regards,
    Amitabha

    Hi Shabarish,
    I followed your instructions, but they did not work out for me...the problem still persists!
    Regards,
    Amitabha

  • Integration Server

    Hi SAP Gurus,
    Please give me a generic answer, if you could:
    How many pipelines are there in the Integration Server?
    1. Receiver Identification, Interface Identification, Message Branch, Request Message Branch, Outbound Binding, Call Adapter, Request Message Mapping
    2. Receiver Identification, Interface Identification, Message Branch, Request Message Branch, Outbound Binding
    3. Message Branch, Request Message Mapping, Outbound Binding, Call Adapter, Request Message Mapping
    Or may be I am asking the question wrong. Could someone please help.
    Thanks,
    Adnan Abbasi

    Hi
    pipeline is a set of services that process XML messages
    on the integration engine
    When a source message reaches the Integration server, it performs 6 steps before the message reaches the destination. The steps are:
    1) Receiver Determination: This steps determines the system that participates in the exchange of the message.
    2) Interface Detremination: For each receiver determine which interface will should receieve the message.
    3) Message Split: If more than one receievers are found, Xi will instantiate new message for each receiver.
    4) Message Mapping: Mapping to transform the source message to destination message format.
    5) Technical Routing: Bind a specific destination and protocol to the message.
    6) Call outbound Adapter: Send the transformed message to the adapter or a proxy.
    One can examine these steps in Runtime Workbench using the Transaction: SXMB_MONI.
    XI pipleine steps are-
    Sender Agreement->Reciever Determination->Interface Determination->Interface Mapping->Reciever Agreement.
    1) Sender adapter will poll the data into XI . This is carried out by Adapter Engine
    Once it reached XI, it will in XI Message pipeline in the integration engine.
    2) Reciever Determination is executed - to look into who is the reciever
    3) Then Interface determination- Sender Interface and Reciever Interface Mapping
    4) reciever Agreement- with adapter or proxy structure.
    Regards
    Sami
    Reward points if helpful.

  • Wrong Integration Server Data retrivied from Adapter

    For unclear reasons the wrong URL to connect to Integration Server was retrieved by Adapter Framework.
    This happened only once, and in this situation the xml message of a productive interface were sent to IS of an
    other system (!).
    As I can see in the default trace, during the call from AF
    CPA cache service to SLD, the wrong host was retrieved.
    In other circumstances, we have found that sometimes the IS hostname is filled with blank, causing the AF to not dispatch successfully the messages to IS. But in this case, thanks to the patch 14 of XI AF, the message are re-sent after the next polling sequence (15 min.).
    I kindly need an help to discover which is the root cause of this kind of problem.
    I red note 764176 about finding inconsistencies on sld, but I have some doubts on the correct implementation in my case. In the note it's discussed about the same domain written two times (for example one in fully-qualified host name and one with a short host name). In our productive SLD there are three domain that have the same name for the technical system point of view, but three definition as CIM data, since there are originally three XI instance on the same host. So, I don't know if we are in the same condition as reported in the note.
    Does anyone have encountered a similar situation? Any workaround? For example, I view in the default traces that during the SLD Access performed by CPA service, there is no defualt value for Integration Server URL, but for default client yes (100). Is there a mode to force adapter framework to set the IS Url without asking it to sld, since I.S. url is always the same?
    Thanks
    Danilo

    Hi,
    The connection to the SLD is established by creating an RFC destination and The server program is called with the HTTP address as a parameter that is maintained with transaction SLDAPICUST.
    Hope this link will be useful.
    http://help.sap.com/saphelp_nw04s/helpdata/en/0b/8512417301ee6fe10000000a1550b0/frameset.htm
    and 25th page of config guide.
    https://websmp101.sap-ag.de/nw04installation
    Regards,
    Madhu

  • SOAPFault received from Integration Server. ErrorCode/Category: XIServer/IN

    Hello All,
    I work on PI 7.1 and needed to create an interface using a simple File-to-File scenario. I created this without using any IR/ESR Objects as per a technical article on the website saptechnical dot com /Tutorials/XI/File2File/Demo1.htm
    This worked perfectly fine in my dev environment. However, when I moved it to Test environment, I am having issues. Error message shown in RWB for Adapter engine is
    SOAPFault received from Integration Server. ErrorCode/Category: XIServer/INBOUND_BINDING_ERROR; Params: BS_ECC100, http://abc, ecc-to-external; AdditionalText: null; ApplicationFaultMessage: null; ErrorStack: Error in sender agreement for party , service BS_ECC100, interface namespace http://abc interface ecc-to-external  No sender agreement found for , , , , , 
    Error Transmitting the message to endpoint http://piq.uk.rweutil.net/sap/xi/engine?type=entry using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Received HTTP response code 500 : Error during Sender Agreement Determination.
    I checked the Sender agreement. It seems fine. All other components are also active, however I do not see the sender agreement  in SXI_CACHE transaction. Any clues what could be wrong ?
    Many thanks in advance .
    Regards
    Rajiv

    Hi Rajiv,
    Please perform below tasks
    1. Logon Integration Directory
    2. Click on 'Modification' icon, put a 'dummy' change (may a space) in the description field
    3. Save the change
    4. Active the changed objects
    5. Repeat 2, 3, 4 steps for all those objects you moved to Test environment.
    All the above steps, eventually leads to have forceble cache refresh, if this won't helps resolve, Please perform full CPACache refresh using below URl
    http://<host name>:<http port>/CPACache/refresh?mode=full
    I presume these instructions will help to resolve the issue.
    Regards
    Sekhar

  • Integration Server in SLD shows no System

    Hello,
    I have the following problem. When I log into the SLD, go to technical System, filter for XI then I See Adapter Engine, Integration Directory etc. For each of them the column System is filled (SAP-System and Host). Only for the Integration Server it isn't.
    And when I log into the Runtime Workbench and select Configuration then I et an error that no Integration Server is available in the SLD.
    Does anybody know what is the problem for that.
    thanks
    Michaela

    Hi,
    The best way what you could do is goto transaction RZ70 and enter the appropriate details in the SLD Bridge tab
    then do the proposal and finally press the esecute button to start the data collection.
    This will automatically create an entry in the SLD then you need to maintain business system manually.
    But before executing the data collection remove the existing IS server info if it's already present.
    More details on this can be found in XI Post installation document.
    RGds,
    Vasanth.

  • No Messages in integration server

    Hi all,
        I have configured the sender file adapter which picks up the file from file adapter and is sending it successfully to integration server. But i am not able to
    see the messages in integration server using the transaction sxmb_moni. There are no messages at all.
    here i am giving the log of the sender file adapter. Plz suggest.
    15:40:08 (4001): File adapter terminated
    Wed Jan 12 15:40:08 IST 2005 *****
    15:40:08 (4012): "Guaranteed Delivery" operation for 2 file(s) pending
    15:40:12 (4023): File adapter initialized successfully
    15:40:12 (4007): File adapter started
    15:40:14 (4029): Process 1 file(s):
    15:40:14 : custbank.txt
    15:40:15 (4030): Start processing "TXT" file "custbank.txt" size 18 in "EO mode
    15:40:15 (4059): Start converting to XML format 
    15:40:15 (4061): Converted complete file content to XML format 
    15:40:15 (4062): Sending text message "277f23b1-6482-11d9-8369-d084ac190476" type "text/plain" to Integration Engine... (message size: 164 bytes, URL: "http://ht56f4:8000/sap/xi/engine/?type=entry")
    15:40:15 (4037): "custbank.txt" sent to Integration Engine successfully
    15:40:15 (4038): Confirmation complete. File deleted on FTP server "custbank.txt"

    These are the xml messages with error.
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Receiver Grouping
      -->
    - <SAP:TechnicalRouting xmlns:SAP="http://sap.com/exchange/MessageFormat">
    - <SAP:serviceEntry version="20">
      <SAP:sender>PS_LEGACY</SAP:sender>
    - <SAP:outboundInterface>
      <SAP:nameSpace>http://ps_crm.com</SAP:nameSpace>
      <SAP:name>Customer_out</SAP:name>
      </SAP:outboundInterface>
      <SAP:receiver>BUS_SAP</SAP:receiver>
    - <SAP:inboundInterface>
      <SAP:nameSpace>urn:sap-com:document:sap:idoc:messages</SAP:nameSpace>
      <SAP:name>DEBMAS.DEBMAS03</SAP:name>
      </SAP:inboundInterface>
    - <SAP:address version="20">
      <SAP:systemKey>BUS_SAP</SAP:systemKey>
      <SAP:endpointType>IDOC</SAP:endpointType>
      <SAP:url>IDOC://SAPER2?RFCDEST=test&DOCREL=3.0&VERSION=3&SAPREL=620</SAP:url>
      </SAP:address>
    - <SAP:auth version="20">
      <SAP:authMethod />
      </SAP:auth>
      </SAP:serviceEntry>
      </SAP:TechnicalRouting>

  • Integration Server configuration error

    Hi all,
    I have an issue with the XI Integration server configuration.
    When I have tested the configuration I have detected that there is an error in the Integration server (transaction SXMB_ADM)
    The value was:
    http://xxx:xxxx:/sap_xi/engine?type=entry
    instead of
    http://xxx:xxxx/sap_xi/engine?type=entry
    note that the fisrt value have : after the port number.
    I have tested the SLD Bussines System configuration and had the same issue, I have solved too.
    But when I execute the test for integration server in transaction SXMB_ADM i have the next message:
    Corresponding Integration Server: Current Configuration <> System Landscape
    For the SLD Role of Bussines System the value in this test is the old value, not the new.
    Could somebody tell me if i forget something?
    Thanks in advance,
    RP

    HI,
    This is somthing related to Cache . Try to refresh Cache.
    see below links regarding cache
    XI Runtime cache error: Cache contents are obsolete
    Cache Refresh - SAI_CACHE_REFRESH
    /people/sravya.talanki2/blog/2005/11/03/cache-refresh-errors--new-phenomena
    /people/sravya.talanki2/blog/2005/12/02/sxicache--ripped-off
    Regards
    Chilla

  • Configure Role of Business System " as Central Integration Server , PI

    Hi Experts,
    I am running transaction code IDX5 in my xi system it is showing as "system is not a central integration server unable to start the program ".In SXMB_ADM role of business system need to configured .If we need to configure how to do this .
    Regards
    Praveen

    Hi Praveen,
    For configuration of integration server please go to SXMB_ADM>In configuration choose Integration engine configuration->And add one runtime parameter IS_URL...and specify the role  of business system as  Integration server and specify the corresponding Integration server i.e dest://httpdestination. This destination is RFC destination that should be created in PI sytem of type 'H 'which contains the target host as host name of PI system and path prefix as  '/sap/xi/engine?type=entry'.
    Thanks & Regards,
    Priyanka Anagani

Maybe you are looking for

  • I got following erro message in Apache error log file

    Why mod_plsql is not started while trying to use Oracle Apex I got connection error as below into modplsql log file <106296140 ms>[ReqStartTime: 11/Sep/2007:14:48:50] <106296140 ms>Request ID ReqID:5160_1189536530 <106296140 ms>Connecting to database

  • Reinstalling Creative Suite 5.5 on a new HD

    My MacBook Pro HD failed and I had the Apple Store install a new HD and they also upgraded my OS to Yosemite. I'm in the process of seeking a data retrieval company to get all of my data off my old HD but in the meantime I want to reinstall CS 5.5 on

  • Qustion for wireless card Satelite Pro M30

    Hello, I laptop has the Intel 2100. Would a 2200 Intel card purchased from the open market operate, or must I purchase the Toshiba one? Thanks and Regards George

  • Moire problem?

    Prolgoue:  Old man who doesn't have a lot of time to study manuals, etc. Video Camera: Canon hmf 41, filming in auto mode, (MXP), 1920x1080(i ?).  Video copied from camera in MTS mode to hard drive, imported into CS5, Premiere and After Effects. Cond

  • ECC cryptography in 1.5_11

    I am trying to use the ECC algorithm (http://java.sun.com/j2se/1.5.0/docs/guide/security/jce/JCERefGuide.html#ECC-Support ) but when i execute the following code try Cipher cipher= Cipher.getInstance("ECIES"); catch (NoSuchPaddingException ex) ex.pri