JAVA Adapter Engine is  missing in XI 7.0

Hi All,
    I am working on new xi server 7.0 .While the configure time adapter engine was missed.After that we installed service pack 08(for Both ABAP stack & JAVA STACK).After installing also Adapter Engine is not vissibile.
          We installed these service pack 08 files for the java stack.
sap.com  SAP-JEECOR  7.00 SP8 (1000.7.00.8.0.20060608124100)  SAP AG  SAP AG 20060909180132 
sap.com  CORE-TOOLS  7.00 SP8 (1000.7.00.8.0.20060601105000)  SAP AG  SAP AG  20060909180127 
sap.com  SAP_JTECHF  7.00 SP8 (1000.7.00.8.0.20060601105100)  SAP AG  SAP AG  20060909180133 
sap.com  BASETABLES  7.00 SP8 (1000.7.00.8.0.20060518071900)  SAP AG  SAP AG  20060909180134 
sap.com  JLOGVIEW  7.00 SP8 (1000.7.00.8.0.20060601105200)  SAP AG  SAP AG  20060909180130 
sap.com  SAP-JEE  7.00 SP8 (1000.7.00.8.0.20060608124100)  SAP AG  SAP AG  20060909180140 
sap.com  LM-TOOLS  7.00 SP8 (1000.7.00.8.0.20060601141123)  SAP AG  MAIN_APL70VAL_C  20060909180136 
sap.com  JSPM  7.00 SP8 (1000.7.00.8.0.20060618023100)  SAP AG  SAP AG  20060909180133 
sap.com  ADSSAP  7.00 SP8 (1000.7.00.8.0.20060524131300)  SAP AG  SAP AG  20060909180128 
sap.com  CAF-UM  7.00 SP8 (1000.7.00.8.0.20060519071848)  SAP AG  MAIN_APL70VAL_C  20060909180125 
sap.com  KM-KW_JIKS  7.00 SP8 (1000.7.00.8.0.20060601105400)  SAP AG  SAP AG  20060909180131 
sap.com  UMEADMIN  7.00 SP8 (1000.7.00.8.0.20060531093731)  SAP AG  MAIN_APL70VAL_C  20060909180133 
sap.com  BI_MMR  7.00 SP8 (1000.7.00.8.0.20060529231100)  SAP AG  SAP AG  20060909180135 
sap.com  SAP_JTECHS  7.00 SP8 (1000.7.00.8.0.20060608124200)  SAP AG  SAP AG  20060909180139 
sap.com  BI_UDI  7.00 SP8 (1000.7.00.8.0.20060529235200)  SAP AG  SAP AG  20060909180129 
sap.com  CAF  7.00 SP8 (1000.7.00.8.0.20060531093727)  SAP AG  MAIN_APL70VAL_C  20060909180121 
sap.com  SAP_XITOOL  7.00 SP8 (1000.7.00.8.2.20060828165800)  SAP AG  SAP AG  20060909180134 
sap.com  SAP_XIAF  7.00 SP8 (1000.7.00.8.1.20060803090400)  SAP AG  SAP AG  20060909180125 
sap.com  SAP-XIAFC  7.00 SP8 (1000.7.00.8.2.20060828165800)  SAP AG  SAP AG  20060909180128 
Please help me..
Thanks,
Gopi

Hi Gopi,
Last time this happened to us, we traced the problem to convoluted CIM data in SLD.
Look at oss note 764176, to see if you have the same symptons.
We deleted all XI related CIM data from SLD, restart our XI systems, and then followed OSS note 764176 to fix the CIM data.
Also please make note that there is a hot fix now for the following
sap.com      SAP-XIAFC      7.00 SP8 (1000.7.00.8.2.20060828165800)      SAP AG      SAP AG      20060919075421
sap.com      SAP_XIAF      7.00 SP8 (1000.7.00.8.1.20060803090400)      SAP AG      SAP AG      20060919075417
sap.com      SAP_JTECHF      7.00 SP8 (1000.7.00.8.1.20060706171200)      SAP AG      SAP AG      20060919075425
sap.com      SAP_JTECHS      7.00 SP8 (1000.7.00.8.1.20060706171300)      SAP AG      SAP AG      20060919075430
sap.com      SAP_XITOOL      7.00 SP8 (1000.7.00.8.2.20060828165800)      SAP AG      SAP AG      20060919075426
Hope this helps/Farshad

Similar Messages

  • Versin iformation for adapter engine is missing in the SLD

    Hi,
       Just imported my Integration Directory  changes into receiving PI System and have come to do the manual activation of the change lists that was asked for. When I do I get the activation cancelling with a message that a communication channel cannot be validated as the version info for the adapter engine is missing in the SLD.
    Can anyone tell me what I have to do to get past this problem ?
    Many thanks,
    Ross

    Hello Ross,
    It looks compatability problem with the Adapter engine and CC.
    Check the system information and apply required patches if require. May be you can go to SAP raising a message.
    http://<pihostname>:<port> systeminfo
    Regards
    Pothana

  • Adapter Engine URL missing in RWB

    Hi All,
    In my newly configured PI 7.0 system, the Adapter Engine URL is missing at the fol. location:
    RWB -> Component Monitoring -> Adapter Engine -> Test Message.
    But when I open SXI_CACHE -> AE Cache, I am able to see the url http://pidev:50000/MessagingSystem/receive/AFW/XI     
    I think that this means that my ABAP stack is configured properly, but JAVA stack has some problem for Adaptr engine.
    Please confirm if I am right and how to resolve this.
    regards,
    Piyush

    Hi,
    Are you using the FQHN?
    Check also note #764176 if you have components missing on SLD.
    Last, you may want to configure your system in order to check each of the steps.
    Use this link -> Wizard-Based Basic Configuration:
    http://help.sap.com/saphelp_nw70/helpdata/en/a0/40084136b5f423e10000000a155106/frameset.htm
    Regards,
    Caio Cagnani

  • 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

  • Java Adapter Compile Error - Missing Libraries

    I am trying to convert my project from being deployed on Flex Data Services 2 To LiveCycle Data Services. I dont know very much about java and have hit a snag when trying to recompile my custom java adaptor.
    It compiles fine under a FDS2 project, but when compiled under a LCDS deployment on JRun, Eclipse gives me the following error when trying to compile:
    Project PTSChat_Java is missing required library: lib/commons-codec.jar
    Project PTSChat_Java is missing required library: lib/commons-httpclient.jar
    The project cannot be built until build path errors are resolved
    It appears that the libraries have been renamed to commons-codec-1.3.jar & commons-httpclient-3.0.1.jar in LCDS, but I am not sure where to update these references? They are not direct library imports in my java code.
    As a shot in the dark, I tried just copying the old FDS2 libraries back over to the WEB-INF\lib\ DIR since there are named differently. It resolved the missing library error, but then I got a compile error with service cannot be resolved in references to my MessageService msgService = (MessageService) service; java code. I quickly realized this is not the correct path to head down.
    Does anyone have any clues what I may be doing wrong? Any help is much appreciated.
    Thanks!

    I resovled the problems I was having.
    I was able to figure out how to change the library linking in eclipse and switched the commons-codec-1.3.jar & commons-httpclient-3.0.1.jar in the place of commons-codec.jar & commons-httpclient.jar libraries previously used with the project (properties:libraries).
    I was not able to correct the service cannot be resolved. Everything I did kept crashing and dropping my connection tot he channel. I ended up just switching the code in my java adapter from:
    MessageService msgService = (MessageService) service
    to
    MessageBroker broker = MessageBroker.getMessageBroker(null);
    MessageService msgService = (MessageService) broker.getService("message-service");
    This appears to be working as desired for my use of the java adapter for the session management & logging. I am not really certain why the "service" became undefined between FDS2 & LCDS, something must have been depreciated or changed around.

  • Adapter Engine Component Missing

    Hi All,
    In the Integration Directory, The Adapter Engine field dropbox is not showing the central Adapter Engine component.Because of this the adapters (other than HTTP and IDoc adapters)can't be used during configuration.
    Can anyone help?
    Thanks and Regards,
    Soumya

    Hi Soumya,
    Go thru following document from service.sap.com , it may help you about Adapter Engine Components are configured or not .
    https://websmp103.sap-ag.de/~sapdownload/011000358700002757652005E/HowtoMintorAF.pdf
    Hope this helps
    Regards,
    Moorthy

  • "Adapter Engine is missing in Communication Channel".

    Hi Experts,
    I am Unable to Find out  the Adapter Engine As Integration Server in the File Sender Communication Channel.
    please let me know
    Regards
    Khanna

    hi,
    /people/venugopalarao.immadisetty/blog/2007/03/15/adapter-engine-cannot-be-found-in-integration-directory
    note : points pls if it helps you

  • Missing Adapter Engine in the XI Domain (in the RTWB view)

    Team,
    I am running at in a bizarre situation at a client site.  We have one SLD that is shared by 2 XI installations (a POC and a SandBox).
    In the POC (in run time workbench view), I can see all the XI component (integration engine, BPM engine, Adapter engine, etc) under it's domain.
    In the SandBox, … the Adapter Engine is missing ...
    We have applied the #764176 note. It has terminated successfully (no error), but we are still in the same situation - the Adapter Engine is missing ...
    We have imported (the SWCV basis 7.0 and the ABAP 7.0).
    Are we missing something?!?!
    Thank !
    A+

    Hi Naveen,
    We have ran (and setup) the RZ70 trx successfully.
    In the SLD the Business System for our sandbox is present (as the same for our POC business system). All authorizations are in.
    The basis guy, at installation time, has given an existing SLD. He does not remember at the end of the installation if the adapter was missing or not (I was not there a the time of the installation, but I presume that it was OK).
    Later in the week, they (customer) decided to switch the XI sandbox to another SLD. The adapter is missing in action since then.
    Still does not work ;-(
    Is there a way i can see (or attach) a couple of screen shot of my error ?
    Thank in advance
    A+

  • Missing Audit Log of Adapter Engine in Message Monitoring

    Hi!
    I've a problem with a fresh installed PI:
    The Adapter Engine doesn't log anything in the Message Monitoring. The Integration Engine logs everything properly, but all entries from the adapter engine are missing. It looks like no message was processed by the AE, but in fact AE is processing the messages properly, only logging fails.
    What can cause this behaviour?
    Best regards,
    Daniel

    Hi Agasthuri,
    yes, maybe something gone wrong in the post install, I will ask the guy which did the installation of the PI. Therefore I didn't have the logon data for performing a cache refresh, but in the log entries it seems that this is working properly.
    Hi Praveen,
    in Communication Channel Monitoring (In PI this is no longer found under Adapter Monitoring), I can see that the messages are delivered, but I can't see the Audit Log entries there.
    I checked the MDT, but there are also no messages displayed.
    End-to-End-Monitoring seems to be a good solution, but it seems that it is something configured wrong in this installation I will try to get the guy which cares for Basis to look after it.
    Best regards,
    Daniel

  • 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

  • Message split on adapter engine for the java based IDoc adapter

    Hi Guys,
    Do you know if message split on adapter engine is available for the java based IDoc adapter on the single stack (PI 7.31)?
    I'm getting such exception when I try to post 3 IDocs
    Transmitting the message to endpoint <local> using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.idoc.exception.IDOCAdapterException: Error before sending due to idoc parsing error: (7) IDOC_ERROR_PARSE_FAILURE: Invalid XML 1.0 character encountered within IDocXML for type <ns0:Messages>:
    state=EXPECTING_IMMEDIATE_TAG_END, charPosition=68, lineNumber=1, columnNumber=69, invalidChar=U+0078,
    sourceSnippet=...UTF-8" standalone="no"?><ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge"><ns0:Message1><...
    ^
    Mapping is one to many.
    Each IDoc content has been compared manually against the xsd schema and it was fine.  
    I know that old way of modifying xsd is still possible.
    Best regards,
    Wojciech

    Did you find a solution to this? Having a similar error right now.
    Thanks and kind regards
    Jens

  • Message Monitor Missing Messages in Adapter Engine

    All,
    I had over 200 messages in my adapter engine but recently I only see 115 for the same period.  
    Additionally, all of the 850 (PO) inbound messages are gone.   I see them in the Integration Engine but not in the Adapter Engine anymore.    
    I need to repeat processing for a particular 850 message and so I am wondering:
    (1)   Any suggestions on why these messages are missing ?
    (2)   Is this a retention period issue ?  If so, how do I control the period ?
    (3)   How can I retrieve these messages ?
    (4)   Is there another place where I can re-process the 850 messages I need.   Where and how ?
    Thanks everyone in advance for your help.
    Regards,
    Andy

    Hi,
    >>>(1) Any suggestions on why these messages are missing ?(2) Is this a retention period issue ? If so, how do I control the period ?
    It may be caused coz of some adapter failure which you are using for that particular  scenario. Also for rention period you can check it in the particular communication channel, but i don't think it will be the issue. try finding it in moni, if it is not there go to RWB and then find it for you particular interface. If it is not there try to find the status.
    >>>(3) How can I retrieve these messages ?(4) Is there another place where I can re-process the 850 messages I need. Where and how ?
    In RWB -> message monitoring you will find all the message, Try searching it for your interface and the you can select all messages and you can reprocess it.
    For error message , in RWB go to particular adapter, and check if it is running or not. It must be in running status. so check and let us know about it.
    Regards
    Aashish Sinha

  • Monitor message in adapter engine through java code

    Hi all,
    I need to write a java code to monitor message using message ID in adapter engine.
    Is it possible to write such a code?
    If yes, then please provide information regarding to that.

    Hi,
    Check these threads
    Retrieving a message id
    Re: How to extract XI-header fields from XI-message in JAVA?
    Thanks!

  • Basic URLs of adapter engine associations properties are missing

    Dear all
    We are running on the nw 7.11 pi version.
    And we recently enabled the ssl on the system.. we have HA in place with web dispatcher.
    We updated the exchane profile parameter with all ssl n required parameters.
    CPA cache refresh is working fine.. but. While doing the Intergration server ABAP cache its failing.
    And we checked the sap note 1678104 under the XRIA assoctiation and as well as under the Basic urls of adapter engine "Secure URL"  properties are missing . Since we r not able to update this property.. the adapter engine is still ponting to http url instead https.
    Please see the screen shot.
    Regards
    Manoj K

    Hi Agasthuri,
    yes, maybe something gone wrong in the post install, I will ask the guy which did the installation of the PI. Therefore I didn't have the logon data for performing a cache refresh, but in the log entries it seems that this is working properly.
    Hi Praveen,
    in Communication Channel Monitoring (In PI this is no longer found under Adapter Monitoring), I can see that the messages are delivered, but I can't see the Audit Log entries there.
    I checked the MDT, but there are also no messages displayed.
    End-to-End-Monitoring seems to be a good solution, but it seems that it is something configured wrong in this installation I will try to get the guy which cares for Basis to look after it.
    Best regards,
    Daniel

  • 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

Maybe you are looking for