Adapter Engine / Integration Server Problem

Hi,
I'm new to SAP and I have some questions regarding my new PI 7.0 SP10 setup.
Problem:
In Integration Directory, when I tried to define a communication channel, after specifying the "Adapter Type" (File in my case), I had to specify the "Adapter Engine" from a drop-down. But the dropdown list is empty!
What I've done & Observations:
1. I've recently imported the file "XI7_0_SAP_BASIS_7.00_06_00.tpz" (From the installation DVD). After importing, I've refreshed the SLD cache.
2. SLDCHECK reveals that the connection to SLD is successful.
3. RWB component monitoring shows:
    Integration Server - No light (Node cannot be expanded)
    Integration Engines - No light (Node cannot be expanded)
    Non-Central Adapter Engines -
        Adapter Engine ootspdbs02 (Red Light)
          - Self Test Failed - Details: Client 010 is not available in this system.
          - Cache Connectivity Test:
            Attempt to fetch cache data from Integration Directory failed; cache could not be updated
            [Fetch Data]: Unable to find an associated SLD element (source element: SAP_XIIntegrationServer, [CreationClassName, SAP_XIIntegrationServer, string, Name, is.01.ootspdbs02, string], target element type: SAP_BusinessSystem)
    J2SE Adapter - No light (Node cannot be expanded)
    Tools
        - System Landscape Directory ootspdbs02 (Green Light)
        - Integration Directory ootspdbs02 (Green Light)
        - Integration Repository ootspdbs02 (Green Light)
        - Runtime Workbench ootspdbs02 (Green Light)
4. In my SLD - I've defined a business system PI_BS_01
    Role: Integration Server
    Pipeline URL: http://OOTSPDBS02:8001/sap/xi/engine?type=entry
    Group - No Group Assigned.
    Client: 001 of PI1
    Technical System: PI1 on ootspdbs02 - Release 700
Given the above observations, can anyone please point out to me where I went wrong?
Any advise is greatly appreciated.
Thank you.
Best Regards,
Ron Lai

Hi Archana,
The configuration in SLD DataSupplier is:
Latest Send Activity               
     2007/01/04  09:18:09:564
Used HTTP Parameters [http host:port] [user] [protocol]     
     [ootspdbs02:50100] [SLDDSUSER] [http]
Sending Node [nodeID] [hostname]     
     [11621750] [ootspdbs02]
Send Result     
     Success
Next Automatic Send Timestamp     
     2007/01/04  21:18:08:189
Send Type
     Automatic (Time Scheduled)
Configuration Status     
     Valid
The hierarchy of this business system is:
Business System:
   BS_NAUTICUS_OOTS [Role = Application System, Related Integration Server = PI1_BS_01, Technical System = TS_NAUTICUS_OOTS]
Technical System:
   TS_NAUTICUS_OOTS [Type = Third Party, Software Component = SWC_NAUTICUS_OOTS, Product = Product_NAUTICUS_OOTS]
Basically I created product, software component, technical system, business system from scratch.
I did not put any dependencies to existing products/software components.
Regards,
Ron

Similar Messages

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

  • XI 3.0 -- Local Adapter Engine

    Hi all,
    I can sent the file of my local PC to the XI 3.0 by using the local adapter engine of XI 2.0.  But I can't do it by using the File Adapter Communication Channel in XI 3.0.
    In my XI 2.0 local adapter engine, I startup the RUN_ADAPTER.BAT in my local adapter engine folder. And create the file_inbound adapter: File_2_M47 as:
    <b>## file adapter java class
    classname=com.sap.aii.messaging.adapter.ModuleFile2XMB
    mode=FILE2XMB
    Integration Engine address and document settings (example, see docu)
    XMB.TargetURL=http://10.37.217.65:8000/sap/xi/engine?type=entry
    XMB.User=xiuser
    XMB.Password=xipass
    XMB.SenderBusinessSystem=FILE_SYSTEM
    XMB.SenderInterfaceNamespace=http://trevorecc5.com/xi/file
    XMB.SenderInterfaceName=ZMI_SO_IDOC
    XMB.ContentKind=B
    #XMB.ContentKind=T
    XMB.ContentType=application/xml
    #XMB.ContentType=text/xml
    #XMB.ContentType=text/plain
    XMB.QualityOfService=EO
    ##File Adapter specific parameters (example, see docu)
    file.sourceDir=C:/filetoidoc
    file.sourceFilename=.
    file.processingMode=setAttribute
    #file.processingMode=delete
    #file.processingMode=archive
    #file.archiveDir=c:/temp_archive
    file.pollInterval=20
    ##xml conversion properties if mode FILE2XMBWITHROWCONVERSION specified (example, see docu)
    #xml.fieldFixedLengths=15,25
    xml.processFieldNames=notAvailable
    xml.fieldSeparator=;</b>
    Note: The IP address (10.37.217.65 ) is my XI 3.0 server.
    I can send the file of my folder - C:/filetoidoc.
    I have configured the Comunication Channel in XI 3.0.
    And the related parameters like as:
    <b>Comunication Channel: CC_FILE_IDOC
    Service                : FILE_SYSTEM
    Adapter type           : File
                           : Sender
    Transport Protocol     : File System(NFS)
    Message   Protocol     : File
    Adapter   Engine       : Integration Server
    Source    Directory    : C:/filetoidoc
    File      Name         : .
    Quality   Service      : Exactly Once
    Poll      Interval     : 20
    Processing Mode        : Set to Read-Only
    Empty-File Handling    : Do Not Create Message
    Process   Sequence     : By Name
    File Type              : Binary
    Status                 : Active
    The sender comunication channel CC_FILE_IDOC has been assigned to the sender aggreement /File_System/ZMI_SO_IDOC/ of namespaces: http://trevorecc5.com/xi/file</b>
    But it can't work! 
    I don't know how to configure the file adapter Comunication Channel for my sending in XI 3.0.
    Any help is appreciated.
    Regards,
    Trevor
    Message was edited by:
            Trevor Zhang

    Hi,
    ><i>I think the XI 2.0 local adapter engine is more useful than the XI 3.0 comunication channel.</i>
    I ve never had the opportunity to work on XI 2.0 but the difference lies in the entire architecture of the Adapter Engine in XI 2.0 and XI 3.0
    While XI 2.0 had the adapter Engine as a J2SE  based engine, XI 3.0 is based on the J2EE framework and thereby allows more features including modules , and also supports different types of adapters and custom developed adapters as well.
    There is no real difficulty in configuring an adapter in XI 3.0 but ofcourse one should take in mind that the network level details should be beyong an XI developers job role.
    You need to look at the fact that the problem you are facing is not because XI 3.0 adapter has some problem, but rather because you seem to have network restrictions!!
    Regards,
    Bhavesh

  • Configuration of JMS Adapter in Central Adapter Engine

    Hi all,
    I have configured Sender JMS Adapter in Central Adapter Engine with the following parameters:
    Adapter type : JMS
    Transport Protocol : WebSphere MQ (non-jms)
    Message Protocol : JMS1.x
    Adapter Engine : Integration Server
    Queue Connection Factory java class :Com.ibm.mq.jms.MQQueueConnectionFactory
    Queue java class : com.ibm.mq.jms.MQQueue
    ipadd : localhost
    port : 1414
    Queue Manager name : TEST.QMGR
    Channel Name : CH1
    JMS Queue : LQ
    CCSID : 437
    Protocol : TCP/IP
    JMS-compliant : WebSphere MQ(non-jms)
    JMS Queue user : MUSR_MQADMIN
    Mapping of message : Entire Message = JMS Payload
    But the status is red with an error message Sender Details : NULL
    Could you please tell me what went wrong?
    Regards
    Sathya

    Hi,
    Make sure that Websphere MQ server is running.
    If u r comfortable with java, you can even write a Java code to acces the server and check if the JMS server is working fine. Some times there will be sample applications provided by Websphere MQ itself.
    Once the java program works then it will be easy to debug the error over here.
    Regards,
    P.Venkat

  • Decentralized Adapter Engine working

    Hi guys,
    I have installed a decentralized adapter engine for my XI Server. I have a scenario which i run with default Adapter Engine(Integration Server), runs fine.
    However, when i run it with choosing Decentralized AE it gives such errors in
    Message Monitoring:
    Exception caught by adapter framework: null
    Delivery of the message to the application using connection AFW failed, due to: RecoverableException.
    Also i am testing this for two simple file2file scenarios. It's acting differently; in a scenario sender commn channel picks file, in other not.
    Is there any configuration settings that's remaining? Or something else?
    Regards
    Arpil

    Hi,
    For the picked message, i see this in moni....
    <Trace level="1" type="T">--start sender interface action determination</Trace>
      <Trace level="1" type="T">select interface MI_XmlFile_out*</Trace>
      <Trace level="1" type="T">select interface namespace urn:Plain2XML</Trace>
      <Trace level="1" type="T">no interface found</Trace>
      <Trace level="1" type="T">--start receiver interface action determination</Trace>
      <Trace level="1" type="T">Loop 0000000001</Trace>
      <Trace level="1" type="T">select interface *</Trace>
      <Trace level="1" type="T">select interface namespace</Trace>
      <Trace level="1" type="T">no interface found</Trace>
      <Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
      <Trace level="1" type="T">Hence set action to DEL</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
    Any clue?
    Regards
    Arpil

  • In the XI Szenario i cannot assign Adapter Engine in Communicationchannel

    Hi There,
    i have a new problem. I imported now the whole Scenario from my XI Cons System into the XI Prod System.
    After that i have to reconfigure the Communication Channels.
    URL etc.. but in Prod System i cannot Assign Integration Server to Adapter Engine..
    i maked a screenshot so you cann see what i mean:
    (If you cannot see the screenshots.. please provide me a Mail Adress.. then i can send them to you)
    This is our Consolidation System:
    http://img16.imageshack.us/img16/7546/xik1.jpg
    You see what i mean in the read mark.
    And here you can see our Prod System.. i cannot Assign here the Integration Server...
    http://img14.imageshack.us/img14/4581/xip1g.jpg
    Can you tell me whats wrong here?
    Thanks
    Bjoern

    Hi,
    please check this threads, this may help you
    Can not select Integration Server for Adapter Engine in File adapter
    No Integration Server under Adapter Engine at Communication Channel config
    Regards,
    pradeep A.

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

  • Adapter engine missing in the comm channal configuration

    Hi Experts,
    I am creating a File-IDOC scenario. While doing the configuration for the sender communication channel for file adpter the integration server is missing in the adapter engine drop down.
    But when i checked for other adapter type like Idoc and Http adapter, the Integration channel is available in the adapter engine drop down(only for these two apater type only, for other adapters also i am not getting the integration server).
    Can anyone help me regarding this, how to resolve this problem.
    Any SAPnotes or blogs for that.
    Help will be apprediated and rewarded as well.
    Thanks
    Manisha

    hi manisha,
    check the previous reply....the blog is nice
    and also check the note 764176
    check below
    1. Open the "Content Maintenance" view under "Administration" in the SLD editing interface. (in 7.10: the view "CIM Instances".) Select "XI Integration Server" from the drop-down menu and navigate to the associations of the integration server. Select the "XI Integration Server Logical Identity" association and delete the association by pressing the 'Remove' button.
    2. Switch to "Home" in the "Technical Landscape" view, and select the "Exchange Infrastructure" technical system type there. (as of 7.10: "Process Integration".) Select all domains and XI components for the host and delete these by selecting them and pressing 'Remove'.
    3. Start the J2EE server. After you restart the server, the XI components log on to the SLD again and create a new entity of the "XI Integration Server" class.
    4. To register the directory and repository again, you must also log on to the two tools.
    5. Under 'Technical Landscape' in the SLD, select the "Exchange Infrastructure" technical system type. (as of 7.10: "Process Integration") and check whether all XI components (Adapter Engine, Integration Directory, Integration Repository, Integration Server and Runtime Workbench/RWB) are logged on correctly. The Adapter Engine component may be missing. In this case, start the registration of the Adapter Engine as described in Note 1031321, step 2.
    6. Change again to the administration interface --> Content Maintenance (7.10: "CIM Instances") to the associations of the XI integration server.
                  Create a new association by pressing the 'New Association' button, select the "XI Sub-System viewed Application System" associations type here, and, in the next step, choose the BC system for the Integration Server. Save the association by selecting 'Associate'.
                  Create a new association by pressing the 'New Association' button, select the "XI Integration Server Logical Identity" association type here, and, in the next step, choose the business system for the Integration Server. Save the association by selecting 'Associate'.
    7. Under 'Technical Landscape' in the SLD, select the "Exchange Infrastructure" technical system type. (7.10: "Process Integration") and check whether the association to the application system is displayed there (in column "Application System", the business system on which the integration server runs should be displayed).
    8. To make the changed associations known in the directory, the SLD temporary storage must be deleted in the directory. To do this, log on to the Integration Directory and select the 'Environment --> Delete temporary storage areas for SLD data' menu option.
    reward  points if helpfull
    regards
    kummari
    Edited by: kummari on Jul 10, 2008 8:42 AM

  • Messaging URL of Integration Server error

    Hi everyone;
    We set up NW EHP1 PI 7.1 on our company.
    We've done all post installation steps both in Abap +Java side.
    It seems my adapter engine has some problem...
    First we were getting 2 errors when we try to do SLD registration. 1st eror was:CPA cache update URL used by Adapter Engine: http://sapsrv2.sap.medyasoft:50400/dir/hmi_cache_refresh_service/ext?method=CacheRefresh&mode=<Mode>&consumer=af.mpi.sapsrv2  CPA cache update URL stored in SLD: URL currently used by Adapter Engine and URL stored in SLD are different!
    we've fixed it by using Java System Properties,XPI CPA services,directory url under NWA .
    But we coundn't solve the second one:
    Messaging URL of Integration Server used by Adapter Engine: http://sapsrv2.sap.medyasoft:50400/sap/xi/engine?type=entry
    Messaging URL of Integration Server stored in SLD: http://SAPSRV2:50400/sap/xi/engine?type=entry
    Messaging URL of Integration Server: URL currently used by Adapter Engine and URL stored in SLD are different!
    Is the anyone who knows how we can change messaging URL of Integration Server stored in SLD?
    Kind Regards,
    Seyda

    It seems you are using different urls for AE and SLD (http://sapsrv2.sap.medyasoft:50400/sap/xi/engine?type=entry is different from http://SAPSRV2:50400/sap/xi/engine?type=entry). Try using the same for the configurations you have done
    For example: http://sapsrv2.sap.medyasoft:50400/sap/xi/engine?type=entry for both configurations
    Regards,
    Federico

  • Purpose of having central adapter engine

    What is the purpose of having Centeral Adapter Engine when any WAS 6.40 has an adapter engine that can communicate de-centrally with the IS?
    Regards
    chandrakanth.K

    Hi Chandra,
    The Adapter Engine is a separate software or software component  that is automatically installed on the Integration Server. In this case, we will call it as central Adapter Engine. You can also install the Adapter Engine separately on another host. This is then a non-central Adapter Engine.
                    By installing the adapter engine centrally on Integration Server, all the components like adapter engine, integration engine, mapping runtime etc will be at single place which increases the preformance.
               In the case of non central adapter engine, where we will install the adapter engine at another system(may be in another place) which decrease your total server performance.
    thanks,
    madhu

  • Ping error in RWB for J2SE Adapter Engine

    Hi,
    we have several external J2SE adapter engines and they function great other than from a monitoring perspective. In RWB "Ping Status" I'm getting the following:
    HTTP request failed. Error code: "401". Error message: "Authorization Required"
    Suggestions?
    Cheers,
    Mattias

    <u>This is not an answer to your question.</u>
    I've tried to get an answer for: how to register J2SE adapter with Integration Server ?
    I tried using SLDAccess service on J2SE adapter with no luck (with this J2SE Adapter Engine is registered in the SLD). My J2SE adapter was never available in the configuration means, in the communication channel ex: file adapter, for the adapter engine drop down all I have is Integration Server, my J2SE adapter was never listed there.
    If you know an answer please post.
    thanks
    SKM<u></u>

  • Sand box Non-central adapter engine entry is shown under development rwb

    Hi All,
    Recently we had a sand box which is a sytem copy of our development server, and everything works fine now.
    I have observed a strange issue here is, in the developement rwb under the Non-Central Adapter engines I see a entry as "Adapter Engine T49 (sand box host name)" the SID seen here is a sand box SID, and till today we never installed any non-central adapter engine either on dev or sand box, I am suprised to see this entry, can some one
    please help me to understand why is this sand box entry is shown under development rwb and where can I set this or where how can I delete this entry.
    Surprisingly I do not see the same non central adapter engine entry on sand box rwb.
    All the servers are XI 3.0 (SP 19).
    Thanking you in advance..
    Regards
    Sonali
    Edited by: Sonali R on Sep 14, 2009 10:59 AM

    Hi Sonali,
    The adapter and integration server engines gets registered with the data in SLD. Please check SLD associations for all XI classes.
    Best Regards
    Raghu

  • How to register an Integration Server with an SLD?

    In my SLD I can see:
    - Adapter Engine
    - Integration Directory
    - Integration Repository
    - RWB
    But the Integration Server is not there.
    I have tried:
    - Restarting the PI 7 system
    - OSS Note 764176 (Error in XI due to inconsistent SLD contents)
    - Registering to the SLD using the Visual Administrator and RZ70
    Any ideas?
    Thanks.

    HI Paul,
    Just check in Integration repository whiole creating the Communication channel for File Adapter
    Are you able to see the entry for Adapter Engine as--integration Server as shown in the Blog OR missing that???
    If you are missing that means you need to implement that Blog which i provided
    If you just want to create the Integration Server in Sld means , follow this
    The specified item was not found.
    Regards
    Seshagiri

  • No monitor browser named "SAP XI Adapter Engine" in PI 7.1

    In PI 7.0 there is a monitor tree in NWA monitor browser named "SAP XI Adapter Engine"
    as follows: Monitoring > Java System Report > Select Monitor Browser > Show: Predefined Local J2EE View > Select All view > Selcet SAP XI Adapter Engine in Server Node
    Enable all children node for data collection would have allowd to collect all the adapter engine related error in CCMS in RZ20 by using MTE class SAP_XIJ2EE_ND.
    Now after upgrading to PI 7.1 this monitor node is not available anymore in NWA.
    There are some monitor node for runtime cache and messaging system montoring in NWA but not the one I am looking for.
    And in RZ20 there is no more error reported using MTE class SAP_XIJ2EE_ND; it shows No MTEs currently available. Though I have some error in adapters.
    Does anyone know how the adapter engine errors can be collected in CCMS for 7.1?

    Suman,
    The adapter engine node itself is not visible in Java system reports of NWA.
    XPI:AF core is enable true and sevice re started.
    Also in RZ20 adapter node is not visible for CCMS
    Please suggest.

  • Adapter Engine

    I am trying to learn on Adapter Engine. Any good blogs or any good links?
    Specially I am tryingto understand How a message is Treated in Adapter Engine on what methodology an Adapter Engine process a Message?
    Thanks.

    hi Pete,
    >>>>How a message is Treated in Adapter Engine on what methodology an Adapter Engine process
    I see you're very interested in deeper (more low level) flows
    I have something for you then
    there is no better sap cpurse for this then this one:
    http://www50.sap.com/useducation/curriculum/course.asp?cid=60199148
    I will explain on very low level how
    the messages flow in XI (in adapter engine, integration engine)
    and all tuning possibilities
    Regards,
    michal
    <a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

Maybe you are looking for

  • Dynamic color in report column

    Hi, All I design a report and display the column as Text field, in the column "Element Attributes", I put in style= "width:400px;height:400px;background-color:green.;font-size:100px;font-weight:bold;text-align:center",+ the column will be displayed i

  • Oracle 10g Discoverer Reports & export to xls fails for large reports

    Hi , We have following configurations: 1: RHEL 5.4 2: Discoverer :Version 10.1.2.48.18 3: Oracle10g Apps Version : Version 10.1.2.0.2 Issue: Most of small reports works fine ....but when large discoverer reports are executed the page keeps on refresh

  • Convert PDF documents (Invoice, Shipping docs etc) to XML?

    Hi. I'm the IT mgr of a company that does a lot of shipping & logistics. We hand key a lot of invoices, and shipping documents into our system. We receive PDFs which is supposed to be EDI but thats not EDI. How can I convert these to XML so I can use

  • Execution plan caching in oracle

    Does oracle store the explain plan in memory cache? Edited by: :) on Aug 2, 2011 10:45 PM

  • IOS 7.0.4 Update Causing my original iPad Mini to Crash / Reboot Several Times a Day

    After running the 7.0.4 update on my original iPad Mini, now the device crashes / reboots randomly when I use it. I have already tried a complete reset and restore. I redownloaded 7.0.4 using iTunes, setup as new but it is still happening. Looking at