Adapter Engine missing in SLD and RWB

Hi all,
I have no Adapter Engine in RWB or under technical systems in the SLD.
In Integration Directory I have "central adapter engine" in the adapter engine field in my File adapter .
But I get this message when I open the communication Channel:
"No SLD elements of type SAP_XIAdapterFramework found"
Please advice,
Thanks!

Hi Thomas,
Your Adapter Framework is probably not registered in the SLD. You may force the
registration if you perform the action as follows:
1. In the J2EE administrator tool in cluster - server - services - deploy
(application view), stop the J2EE applications:
a. sap.com/com.sap.aii.af.service.cpa.monitor
b. sap.com/com.sap.aii.af.
2. Restart the sap.com/com.sap.aii.af application.
Refer sapnote in chapter 8.2 for more in the link provided below on Trouble shooting.
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/bd5950ff-0701-0010-a5bc-86d45fd52283
Cheers,
Ram.

Similar Messages

  • Adapter engine missing in RWB,

    THis is the  log info
    No SLD elements of type SAP_XIAdapterFramework found
    Thrown:
    com.sap.aii.ib.bom.landscape.SLDElementNotFoundException: No SLD
    elements of type SAP_XIAdapterFramework found
    at
    com.sap.aii.ib.server.sldquery.SLDQueryRequester.getMyAdapterFrameworkArray(SLDQueryRequester.java:906)
    at com.sap.aii.ib.server.abapcache.sld.AdapterEngineQueries.getAllAEs
    (AdapterEngineQueries.java:171)
    at
    com.sap.aii.ibdir.server.cache.monitoring.CacheMonitor.listAvailableCacheInstances(CacheMonitor.java:63)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke
    (NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke
    (DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at com.sun.jmx.mbeanserver.StandardMetaDataImpl.invoke
    (StandardMetaDataImpl.java:414)
    at javax.management.StandardMBean.invoke(StandardMBean.java:323)
    at com.sap.pj.jmx.server.MBeanServerImpl.invoke
    (MBeanServerImpl.java:944)
    at
    com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke
    (MBeanServerWrapperInterceptor.java:288)
    at com.sap.engine.services.jmx.CompletionInterceptor.invoke
    (CompletionInterceptor.java:400)
    at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke
    (BasicMBeanServerInterceptor.java:277)
    at com.sap.jmx.provider.ProviderInterceptor.invoke
    (ProviderInterceptor.java:340)
    at com.sap.engine.services.jmx.RedirectInterceptor.invoke
    (RedirectInterceptor.java:340)
    at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke
    (MBeanServerInterceptorChain.java:330)
    at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke
    (MBeanServerSecurityWrapper.java:288)
    at com.sap.engine.services.jmx.ClusterInterceptor.invoke
    (ClusterInterceptor.java:813)
    at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke
    (MBeanServerInterceptorChain.java:330)
    at com.sap.engine.services.monitor.mbeans.Template.pollDynamicData
    (Template.java:891)
    at com.sap.engine.services.monitor.mbeans.Template.handleNotification
    (Template.java:853)
    at
    com.sap.engine.services.jmx.server.AscynchronousProxyListener.handleNotification(AscynchronousProxyListener.java:51)
    at javax.management.NotificationBroadcasterSupport.handleNotification
    (NotificationBroadcasterSupport.java:221)
    at javax.management.NotificationBroadcasterSupport.sendNotification
    (NotificationBroadcasterSupport.java:184)
    at com.sap.engine.services.jmx.timer.j2ee.Timer.sendTimerNotification
    (Timer.java:431)
    at com.sap.engine.services.jmx.timer.j2ee.TimerNotificationEntry.timeout(TimerNotificationEntry.java:69)
    at com.sap.engine.services.timeout.TimeoutNode.synchronousRun
    (TimeoutNode.java:95)
    at com.sap.engine.services.timeout.TimeoutManagerImpl.singleThreadRun
    (TimeoutManagerImpl.java:663)
    at com.sap.engine.services.timeout.TimeoutManagerRunner.run
    (TimeoutManagerRunner.java:18)
    at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
    at com.sap.engine.core.thread.impl5.SingleThread.execute
    (SingleThread.java:144)
    at com.sap.engine.core.thread.impl5.SingleThread.run
    (SingleThread.java:242)
    Caused by: com.sap.aii.ib.core.extobjects.ExternalOasProcessException:
    An error occurred when accessing the SLD server
    at com.sap.aii.ib.server.sldaccess.SLDElementAccessor.getExtObjects
    (SLDElementAccessor.java:58)
    at com.sap.aii.ib.server.extobjects.EOAServiceImpl.getExtObjects
    (EOAServiceImpl.java:58)
    at
    com.sap.aii.ib.server.sldquery.SLDQueryRequester.getMyAdapterFrameworkArray(SLDQueryRequester.java:903)
    ... 31 more
    Caused by: com.sap.aii.utilxi.misc.api.ResourceException: An error
    occurred when accessing the SLD server
    at com.sap.aii.ib.server.sldquery.SLDCache.actualize(SLDCache.java:46)
    at com.sap.aii.utilxi.core.cache.MapBasedCache.getValue
    (MapBasedCache.java:125)
    at com.sap.aii.utilxi.core.cache.Cache.getSingleValue(Cache.java:112)
    at com.sap.aii.utilxi.core.cache.Cache.get(Cache.java:87)
    at com.sap.aii.utilxi.core.cache.Cache.getValue(Cache.java:204)
    at com.sap.aii.utilxi.core.cache.Cache.getSingleValue(Cache.java:112)
    at com.sap.aii.utilxi.core.cache.Cache.get(Cache.java:87)
    at com.sap.aii.utilxi.core.cache.Cache.getValue(Cache.java:204)
    at com.sap.aii.utilxi.core.cache.Cache.getSingleValue(Cache.java:112)
    at com.sap.aii.utilxi.core.cache.Cache.get(Cache.java:87)
    at
    com.sap.aii.ib.server.sldaccess.SLDElementAccessor.performStandardQuery
    (SLDElementAccessor.java:160)
    at
    com.sap.aii.ib.server.sldaccess.SLDElementAccessor.performAssociatorChainQuery(SLDElementAccessor.java:122)
    at com.sap.aii.ib.server.sldaccess.SLDElementAccessor.getExtObjects
    (SLDElementAccessor.java:45)
    ... 33 more
    Caused by: com.sap.aii.ib.server.sldquery.SLDQueryException: An error
    occurred when accessing the SLD server
    at
    com.sap.aii.ib.server.sldquery.SLDQuery.readSLDElementAssociatorKeyList
    (SLDQuery.java:468)
    at com.sap.aii.ib.server.sldquery.SLDQuery.selectSLDElementList
    (SLDQuery.java:94)
    at com.sap.aii.ib.server.sldquery.SLDCache.actualize(SLDCache.java:41)
    ... 45 more
    Caused by: com.sap.lcr.api.cimclient.LcrException: CIM_ERR_FAILED: [6]
    No such
    instance: //pr41xpi/sld/active:SAP_XIIntegrationDirectory.CreationClassName="SAP_XIIntegrationDirectory",Name="directory.pip.pr41xpi"
    at
    com.sap.lcr.api.cimclient.SimpleResponseAnalyser.raiseExceptionOnError
    (SimpleResponseAnalyser.java:120)
    at com.sap.lcr.api.cimclient.SimpleResponseAnalyser.getIResult
    (SimpleResponseAnalyser.java:53)
    at com.sap.lcr.api.cimclient.CIMOMClient.sendImpl(CIMOMClient.java:220)
    at com.sap.lcr.api.cimclient.CIMOMClient.send(CIMOMClient.java:148)
    at com.sap.lcr.api.cimclient.CIMOMClient.associatorNamesImpl
    (CIMOMClient.java:346)
    at com.sap.lcr.api.cimclient.CIMOMClient.associatorNames
    (CIMOMClient.java:876)
    at com.sap.lcr.api.cimclient.CIMClient.associatorNames
    (CIMClient.java:439)
    at
    com.sap.aii.ib.server.sldaccess.SLDReader.getAssociatedCIMInstancenameList(SLDReader.java:213)
    at
    com.sap.aii.ib.server.sldquery.SLDQuery.readSLDElementAssociatorKeyList
    (SLDQuery.java:441)

    Raghu,
    i have already tried the note , but that didnt help..
    adapter engine is still missing..
    This is the error i see inthe log now along with the previous error i posted
    Message:     Cannot get aliases for [sap.com/cafeugpuisupport] application.
    The error is: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5005] Application sap.com/cafeugpuisupport is not deployed on cluster element  get its aliases and it is not possible to .00215E322EB0002900000003000A800A00CAD0C75E9E2457
    Edited by: GerardChristopher on Feb 4, 2010 7:32 PM

  • 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

  • Adapter engine missing in Qa

    Hi all,
    After transporting objects from Dev to Qa we are experiencing some problems:
    1: in the "Component Moinitoring" of the RWB "Adapter Engine" is listed twice (under Integration Server).
    2: In the communication channels the the drop down selection box where you choose "Adapter Engine" is empty.
    3: The communication channels are not taking in data.
    Please advice, Thanks

    Hi all,
    After removing and re-registering the Adapter Engine only one engine shows in technical systems in the SLD (instaed of two). - Thants good
    But now i have an entry called "Domain Null" (type XI Domain).
    What does this mean, and will this cause problems?
    Thanks

  • Auto restart of messages failed in Adapter Engine PI 7.0 and 7.1

    Hi,
    I am trying to figure out a way to automatically restart the messages failed with in the adapter engine (because of the target system not available etc.). These messages are in System Error status and I can restart them from RWB. But I am looking for any report or something available either on Java or ABAP engines so that I can automate the process.
    Thanks for the help.
    VJ

    I have come across the web service AdapterMessageMonitoring in PI 7.0 (Found it in Web service navigator) with possibly useful methods. But I could not find the same service on PI 7.1. Any clue on this?
    Also, the getMessageList methods works perfectly as expected but the resendMessages mehtod fails with the exception -
    com.sap.engine.services.ejb.exceptions.BaseEJBException xmlns:ns1="http://sap-j2ee-engine/client-runtime-error">Exception in method resendMessages.</ns1:com.sap.engine.services.ejb.exceptions.BaseEJBException>
    Will post more if move forward.
    VJ

  • Unable to determine name of central adapter engine

    We have a central SLD set up. I am now moving some configuration and testing from our dev environment to our qa environment. When I do a cache notification from the Integration Directory I receive a message stating that "Unable to determine the name of the central Adapter Engine from the System Landscape Directory". When I look under the technical system type of Exchange Infrastructure of the system landscape directory I do not see the Adapter Engine of my QA or Production environment. I only see one central adapter engine listed. That of my development environment. It will not let me define another technical system to add these adapter engines because the button New Technical System is grayed out. How do I get these adapter engines defined in the SLD?
    Thanks,
    Jim

    I also had the same problem. But when I opened Integration Directory and Repository from the links, it got added to the Technical system under Exchange Infrastructure. Only Adapter Engine was not getting added.
    But after applying the note 764176. Adapter Engine added to SLD and after refreshing cache now Adapter Engine also got added to RWB components.
    Only one problem now - in Message monitoring, If I select Adapter Engine from the drop down, I get page cannot be displayed. Is it due to the fact that I dont have any adapters configured?? and also no messages available for that matter?? as it is a fresh box..
    Message was edited by: Thilothama v

  • Adapter Engine not visible in SLD, RWB and Directory

    Hi all,
    I have problem with the registration of the adapter engine in my sld. When I search for it in Technical Systems doesn´t appears.
    I have implemented SAP notes 764176 and 804124 and it doesn´t work.
    My system is SAP PI 7.0 and the SLD is configured on a differente machine. The SAP PI machine can reach SLD machine (is not network problem).
    Any suggestions?
    Thank for your postings.

    Hi -
    Do you have your SLD Data Supplier service (within Visual Admin tool) for PI Java server pointed to the host of the SLD machine?   If so, you should at least see a Technical System (type Web AS Java) for your PI system in your SLD.
    Regards,
    Jin

  • Error in RWB - Component Monitoring - Adapter Engine

    Hi,
    After we install an Additional Application Server Instance, we are facing an issue with the Runtime Workbench, specifically with the Adapter Engine status.
    On the RWB we're have this error:
    Ping Status: Unable to establish connection to
    "http://<Additional AS Host>:<Central Instance JAVA Port>/AdapterFramework/rtc"
    All the time it's pointing to the Additional AS with the Primary AS Java Port.
    We are using a central SLD in PIP system.
    We already reviewed, the point 8.12 of the "SAP NetWeaver PI 7.1 Including SAP EHP 1 - Troubleshooting Guide"
    Any idea to solve this?
    Regards,
    GCC PI

    Hi GCC,
    Please change in the http://<host>:<j2ee_port>/exchangeProfile this settings:
    Exchange Profile
    Connections:
    - com.sap.aii.connect.directory.name
    - com.sap.aii.connect.landscape.name
    - com.sap.aii.connect.repository.name
    RuntimeWorkbench:
    - com.sap.aii.rwb.server.centralmonitoring.r3.ashost
    Please change the value in the:
    Config Tool -> cluster-data -> Global Server -> Configuration ->
    Services -> com.sap.aii.af.cpa.svc ->
       SLD.selfregistration.hostName
       SLD.selfregistration.httpPort
       SLD.selfregistration.httspPort
    Also see notes: #1113161 - Links in Component Monitoring not working
    and #764176 - Error in XI due to inconsistent SLD contents
    After that, please restart the j2ee engine.
    Regards,
    Luis Diego

  • "Non-Central Adapter Engines" in RWB

    Hi.
    We install XI system and we changed host name according to notes 757692.
    After then, We found one problem in RWB.
    When we run Component Monitor in RWB, Adapter engine is in "Non-Central Adapter Engines".
    Why Adapter engine is in "Non-Central Adapter Engines" node ?
    Any ideas ?
    Regards, Arnold.

    Hello Sonali
    This is most likely caused by errors registering the XI components in the SLD. Apply the notes below:
    #764176 Error in XI due to inconsistent SLD contents
    #1117249 Incomplete Registration of PI components in SLD
    #1334053 No automatic PI 7.10 SLD Registration
    Also search the forum for similar issues registering the adapter engine in the SLD components.
    Regards
    Mark

  • 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

  • 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.
    Thanking you in advance..
    Regards
    Sonali

    Hello Sonali
    This is most likely caused by errors registering the XI components in the SLD. Apply the notes below:
    #764176 Error in XI due to inconsistent SLD contents
    #1117249 Incomplete Registration of PI components in SLD
    #1334053 No automatic PI 7.10 SLD Registration
    Also search the forum for similar issues registering the adapter engine in the SLD components.
    Regards
    Mark

  • Adapter Engine Field missing --

    Hi All,
    I'm trying to create new Communication Channel in our QA system.
    I'm using 'Sender File Adapter'  But somehow When I choose below option, the last value (Adapter Engine) is blank.
    - Adapter type : Sender FILE   http://sap.com/xi/XI/System  SAP BASIS 7.00
    - Transport Protocal : File System (NFS).
    - Message Protocal : File
    - Adapter Engine : ???????  (Blank)..
    We are under PI 7.0 and I did same in Dev but it's not in QA.  I think the value of 'Adapter Engine ' should be 'Integration Server'
    automatically.   Any Idea?
    Thanks in advance.

    Hi,
    Yes, if your adapter reside in the central adapter engine then it should be in the IS.
    Adapters that host in different adapter engine, then decental adapter engine need to be selected.
    Check you SLD configuration, whether there is an entry for your Adapter Engine or  not.
    Have a Look on this SAP Note : 764176, do hope it will resolve you problem.
    Look for these discussion: Unable to determine name of central adapter engine
    Missing Adapter Engine in the XI Domain (in the RTWB view)
    Thanks
    Farooq.
    Edited by: Farooq Farooqui on Jul 31, 2008 7:19 AM
    Edited by: Farooq Farooqui on Jul 31, 2008 7:29 AM

  • RWB - Cache Connectivity Test - Adapter Engine shows error

    Hello Friends,
    In our one production system (PI 7.1), while do 'Cache Connectivity Test' from RWB -> Component Monitoring, it shows the following error for Adapter Engine under Integration Directory.
    Error:
    Cache notification from Integration Directory failed Error when accessing the System Landscape Directory.
    No SLD elements of type SAP_XIAdapterFramework found
    But, Integration Server - ABAP, Integration Server - JAVA shows green color. The messages are flowing through the Adapter Engine fine. i.e I am seeing 2 Adapter Engines under Integration Server in Component Monitoring. One Adapter Engine is in grey and another Adapter Engine shows green color.
    When I click the grey color adapter engine, it immediately turns to red color and some different host name url is displayed (http://<wronghost>:53000/AdapterFramework/rtc).
    So, what could be the problem ?
    Kindly clarify, friends.
    Thanking you.
    Kind regards,
    Jegathees P.

    Hello Jegathees
    Apply the solution in note #804124 HTTP communication with XI Adapter Engine fails. Set the parameters:
    SLD.selfregistration.hostName     
    SLD.selfregistration.httpPort     
    SLD.selfregistration.httspPort    
    as described in the note.
    Regards
    Mark

  • Installation and then Configuration of Plain J2se Adapter Engine

    Hi All,
    Actually we want to use JMS Adapter for that we had installed Plain J2SE Adapter Engine but after installing and following the initial steps of Adapter.pdf we are not able to access the Adapter Engine through URL.We are using the URL http://<hostname>:8200/MessagingSystem/receive/AFW/XI
    this URL is there in our SLD but we are not able to access the page.
    So Please can somebody help me to resolve this issue.
    Thanks & Regards
    Sathya

    Hi Amol,
    I am trying to send read data from MQSeries using JMS adapter. We are successful in opening the Adapter Engine  and the GUI. We have cofigured the adpter as follows. But when we try to restart the adapter to get the changes get saved we are getting the following error
    <b>"ERROR CALLING THE RESTART ADAPTER"</b>
    Also status is shown is yellow and version is shown as not set.
    Where ever I have changed the configuration data I have shown it in bold
    JMS-Adapter Configurarion
    This Configuration is a sample for a JMS sender channel (inbound, sends to XI IS)
    Set XI message protocol version. This sample is designed for XI 3.0
    version=30
    JMS message receiver class
    classname=com.sap.aii.messaging.adapter.ModuleJMS2Transport
    set if a transacted JMS Session should be used (default: true)
    #JMSSession.sessionTransacted=false
    set delay in milliseconds before processing next message after an error (default: 0)
    errorDelay=10000
    #set delay in milliseconds before trying to reestablish the JMS Connection after a connection error (default: -1 (do not try to reconnect))
    #reconnectDelay=10000
    set the Message Formats you want to process (Formats only needed if they can not be evaluated at runtime)
    TransportMessage Type can be set to TransportMessage of XMBMessage. It is used for sending and receiving Transport and XMBMessages
    #TransportMessage.type=TransportMessage
    TransportMessage.type=XMBMessage
    uncomment and adjust parameters for Transformation Type (Binding of JMS-Transport Message),
    insert your class here for an individual binding between JMS and Transport Message
    uncomment the following line for using Bindings that belong to Tunneling
    #transformClass=com.sap.aii.messaging.adapter.trans.JMSTunneling
    uncomment the following line for using Bindings that belong to Single Payload Binding
    transformClass=com.sap.aii.messaging.adapter.trans.JMSSinglePayloadBinding
    ID Garbage Collector: For EO(IO) handling XI adapters store the JMS/XI message ID's in the ID logger
    Uncomment the following lines and change the default values if you recognized "out of memory" problems due to
    very large ..\tech_adapter\Data\*_ID.dat files which will be kept in the memory as well
    eoExpirationAfterDays is the period of keeping the message ID in days. Afterwards the message ID might be used again
    garbageCollectorInterval is the period in milliseconds when the ID garbage collector is started. It will however only
    be started if messages are exchanged otherwise ID logs won't be created anyway
    eoExpirationAfterDays=365
    garbageCollectorInterval=86400000
    <b>#
    the following parameters are used in some Bindings that belong to Single Payload Binding needing XMBHeader Information
    uncomment and adjust parameters according your requirements. Please note, that the party identfier needs not to be
    configured in case of A2A scenarios.
    #XI.SenderParty=Sender
    XI.SenderService=MQSeries
    #XI.ReceiverParty=Receiver
    XI.ReceiverService=MTX
    XI.InterfaceNamespace=http://xitest
    XI.Interface=MI_Out_File
    XI.TraceLevel=1
    XI.LoggingLevel=1
    XI.QualityOfService=EO
    XI.QueueId=ABCD
    XI.ContentType=text/xml
    #</b> *************************************************************************************************************
    <b>#
    URL of XI IS to send the messages to
    XI.TargetURL=http://bwxi:50000/sap/xi/engine?type=entry
    XI.User=XIAF
    XI.Password=XIPASS
    #</b> *************************************************************************************************************
    URL of file adapter if a loopback JMS to File should be configured
    XI.TargetURL=//localhost:8210/file/receiver
    <b># uncomment the following settings if needed (independent on JMS provider)
    JMS.QueueConnectionFactoryImpl.user=xisuper
    JMS.QueueConnectionFactoryImpl.password=xxx
    #</b>
    uncomment and adjust parameters for loading JMS administrated objects via JNDI
    uncomment and adjust parameters if not the default context should be used
    #JNDI.InitialContext.property.1=java.lang.String {javax.naming.Context.INITIAL_CONTEXT_FACTORY}, java.lang.String com.sap.engine.services.jndi.InitialContextFactoryImpl
    #JNDI.InitialContext.property.2=java.lang.String {javax.naming.Context.PROVIDER_URL}, java.lang.String localhost:50004
    #JNDI.InitialContext.property.3=java.lang.String {javax.naming.Context.SECURITY_PRINCIPAL}, java.lang.String Administrator
    #JNDI.InitialContext.property.4=java.lang.String {javax.naming.Context.SECURITY_CREDENTIALS}, java.lang.String sap
    set the Lookup Names
    #JMS.JNDILookupNameQueueConnectionFactory=jmsfactory/default/joetest
    #JMS.JNDILookupNameQueue=jmsQueues/default/sapDemoQueue
    uncomment and adjust parameters for loading JMS administrated objects from filesystem ***
    #JMS.FileNameQueueConnectionFactory=SAPQueueConnectionFactory.ser
    #JMS.FileNameQueue=SAPQueue.ser
    uncomment and adjust parameters for creating SonicMQ JMS administrated objects ***
    JMS.QueueConnectionFactoryImpl.classname=progress.message.jclient.QueueConnectionFactory
    JMS.QueueConnectionFactoryImpl.constructor=java.lang.String localhost:2506
    JMS.QueueImpl.classname= progress.message.jclient.Queue
    JMS.QueueImpl.constructor=java.lang.String SampleQ1
    <b># uncomment and adjust parameters for creating MQSeries JMS administrated objects ***
    JMS.QueueConnectionFactoryImpl.classname=com.ibm.mq.jms.MQQueueConnectionFactory
    JMS.QueueConnectionFactoryImpl.method.setHostName=java.lang.String BWXI
    JMS.QueueConnectionFactoryImpl.method.setChannel=java.lang.String JAVA.CHANNEL
    JMS.QueueConnectionFactoryImpl.method.setTransportType=java.lang.Integer {com.ibm.mq.jms.JMSC.MQJMS_TP_CLIENT_MQ_TCPIP}
    JMS.QueueConnectionFactoryImpl.method.setQueueManager=java.lang.String QM_BWXI
    JMS.QueueImpl.classname= com.ibm.mq.jms.MQQueue
    JMS.QueueImpl.constructor=java.lang.String postcard
    JMS.QueueImpl.method.setTargetClient=java.lang.Integer {com.ibm.mq.jms.JMSC.MQJMS_CLIENT_NONJMS_MQ}
    #</b> *************************************************************************************************************
    uncomment and adjust parameters for using a dispatcher ***
    #Dispatcher.class=com.sap.aii.messaging.adapter.ConversionDispatcher
    #Dispatcher.namespace=namespace1
    #namespace1.ConversionDispatcher.logPayload=true
    #namespace1.Service.1=Plain2XMLService
    #namespace1.Plain2XMLService.class=com.sap.aii.messaging.adapter.Conversion
    #namespace1.Plain2XMLService.xml.conversionType=SimplePlain2XML
    #namespace1.Plain2XMLService.xml.processFieldNames=fromConfiguration
    #namespace1.Plain2XMLService.xml.fieldNames=a,b,c
    #namespace1.Plain2XMLService.xml.fieldSeparator=;
    #namespace1.Service.2=XSLTService
    #namespace1.XSLTService.class=com.sap.aii.messaging.adapter.XSLTConversion
    #namespace1.XSLTService.XSLTConversion.XSLTFileName=Data/DemoConversion.xsl
    Can you please help me in resolving the error.
    Regards,

  • Adapter Engine not  visible in RWB

    Hi Guys,
             I coudnt find the Adapter engine in Component Monitoring and Message monitoring in RWB.
    while displaying the components of Integration Engine getting the below error. I am using PI 7.1
    Kindly let me know where to check if the components are not visible in RWB.
    java.lang.NullPointerException:
         at com.sap.aii.mdt.web.MonitorDynPage.setNewComponent(MonitorDynPage.java:635)
         at com.sap.aii.mdt.web.MonitorDynPage.process_go_button(MonitorDynPage.java:496)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:585)
         at com.sapportals.htmlb.page.DynPage.doProcessCurrentEvent(DynPage.java:172)
         at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:102)
         at com.sapportals.htmlb.page.PageProcessorServlet.handleRequest(PageProcessorServlet.java:62)
         at com.sapportals.htmlb.page.PageProcessorServlet.doPost(PageProcessorServlet.java:22)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
         at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:66)
         at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:32)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:431)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:289)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:376)
         at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:85)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
         at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:160)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
         at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:67)
         at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
         at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
         at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
         at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
         at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
         at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
         at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
         at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:295)
         at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.run(Processor.java:222)
         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:152)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:247)
    With Regards
    Pradeep N

    Check page 129 of this document:
    [SAP XI TroubleShooting Guide|https://websmp109.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000659947&_OBJECT=011000358700005909032005E]

Maybe you are looking for

  • Sql Query To Find Out list of users not having a particular resource provisioned

    Hi, I know the query for all the resources tagged to user with their account status. Can anybody help me with a query to fetch just the user details for the following scenario: 1)Active users having  having no instance of a particular resource. Condi

  • Emac completely restore help

    how do i completely restore my emac to its factory settings? help please!

  • Sending IDocs as 'control messages' to a Logical System

    Hi all, I have defined an external Logical System to where I send Idocs. The Idocs are received and processed by a SAP Java Connector on that LS. At the moment, when for example a purchase order is created for a specific vendor, a message to that ven

  • Creating a progress bar on a HTTP Service

    Hello All, As the top title suggests, does anyone know the best way of doing this? The HTTP service is simply pulling some XML data and I want to inform the user of how long this is going to take or what % it is currently completed. I dont have much

  • Cannot open saved project/make new projekt - whats wrong?!?

    i made last days a nice idvd project with a lot of slideshows. all was working fine, i was able to save it, open it again, work on it etc...but then: when i want to open saved project idvd just mark the file, i hear my harddrive working - and nothing