Adapter Engine Issue in RWB

Hi,
I am getting a error in the RWB:
Self-Test Status: HTTP request failed. Error code: "500". Error message: "Internal Server Error [http://host:port/AdapterFramework/rtc]"
I have a mail channel setup that is running on this Adapter Engine. I am able to monitor the channel on this Adapter Engine and the channel is collecting mails from the POP3 mailbox and delivering the message to the Integration server. However I am getting the error above.
Please can you assist to get this matter resolved.
Many Thanks
Regards
Willie Hugo

Hi,
This problem is still persisting. I have however not mentioned that we are running PI 7.10 and therefore there is no Visual Administrator only NWA. This was a new install. I have changed all the Host Names to use fully qualified domain names. This is the exchange profile and sxmb_adm, RZ70, sldapicust and in the RFC's user on the ABAP side. Also I have checked out the destinations on NWA and changed the Host Names the to fully qualified domain namesand also the SLD Data Supplier Configuration. I also changed the FQ D names on the JCO RFC Destinations. All well so far.
I however still has the same error on the Adapter Engine in the RWB. What I have notice though is where the error is displayed in the RWB then the Host Name is not FQ. Where can I correct this?
Also I have noticed when going into SXI_Cache > Goto > Adapter Engine Cache then there is no cache for the Adapter Engine.
I have changed the host name of the integration server on the SLD to FQ D names as well.
I think that I need to delete all the entries for this tech+business system and all the assosiations to it from the SLD and then re-register the whole PI to the SLD again, but is not sure how to do that again.
Please can any one assist.
Regards
Willie

Similar Messages

Adapter Engine issue

Hi,
I am workingon JDBCXIRFC scenario.
After creating Data types, message types, message interfaces and etc, i started defining communciation channel template under "Adapter Objects".
While selecting the particular Adapter type, the window is popping up with message "Objects Not Found".
How to resolve this bug?
Does this means that we need to install Adapter Engine?
If its already installed, how to check the available adapters in XI server?
Regards
Pavan

Hi Pavan,
i guess u have some post-installation problem.Can u check in ID wheather all adapters are installed there??in any communication channel when u gonnna select a adapter ...r u getting the same error???
Go and import the SAP BASIS 6.4 or 7.0 Software COmponent Version into Integration Repository.
For this tpz file you can get from -
Copy XI3_0_SAP_BASIS_6.40_09_00.tpz from <Components DVD>/XI /XI_CONTENT to directory /usr/sap/<SAPSID>/SYS/global/xi/repository_server/import/
better u check this thread
Adapters Metadata Problem
Regards
BILL

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 nodes(In RWB) for CCMS tree are not updated

Hi Experts,
We are implementing CCMS monitoring on XI-700 SP12.But when we are trying to check monitoring node for runtime work bench (alert categories and Rules) its not updated in ccms tree and not collecting updated data.Can you please help us on this.
Thanks and Regards
Suveer

Have you checked the Audit log in Runtime Workbench? Using it, you could come to know which module of the receiver channel went in error. Are you doing some user mapping or is it a standard one? The problem could be related to the undeployed mapping or mismatch in the format.
Regards,
Prateek

SOAP messages not visible in RWB - Message Monitoring - Adapter Engine

Hi,
following scenario:
ERP is sending IDocs to PI.
Within PI an integration process sends the IDoc data through a SOAP (WS) receiver channel to a system far far away.
In RWB -> Communication Channel Monitoring I can see all delivered messages selecting my SOAP channel.
But:
I can´t see the SOAP messages in RWB -> Message Monitoring -> Messages of Adapter Engine.
In RWB -> Message Monitoring -> Messages of Integration Engine I only see SOAP messages with status "Error".
Successful column is empty.
Do I have to adjust some system / monitoring parameters also seeing SOAP messages in RWB->Message Monitoring?
Thanks in advance,
André

Hi Ravi,
thanks.
But there are thousands of successful messages delivered to the receiver.
These successful messages can only be seen in the Channel Monitoring.
I can´t find these successful messages in Message Monitoring.
Only some with status "Error" are displayed.
Strange...
Cheers,
André

Reg: Error in adapter Engine Monitoring

Hi Guys,
In my RFC to File Scenario i got error as Adapter message property was configured was mandatory element but there is no Dynamic ocnfiguration elementin XI MEssage Header. This is occur in adapter engine monitoring in RWB.
Thanks

This error comes if you there is a problem in passing the file via dynamic configuration
for this if you want temporary solution like filename not necessarily be dynamic then go to receiver file adapter then
adapter specific message attributes deselect filed Failif file name does not.... sme option where you can uncheck the failure option
and in this case need to provide the filename and file will get generated with this filename if there is no filename generates using dynamic configuration
for this to resolve permanently then check the filename is passed or not to file adapter in moni in dynamicconfiguratuoin tab of callAdapter pipeline service
HTH
Rajesh

Adapter engine queue monitoring

Hi All,
I have one doubt about adapter engine queue.
We can see adapter engine queue in RWB->Message Monitoring-> Adapter engine-> Display .
Here in queue if one message goes in to system error status, remaining all messages from that queue goes on holding status.
So unless someone manually clears this system error message, remaining messages from same queue will not be processed.
Is there anything to automate this process? Because currently someone has to manually monitor this queue and clear the message if it is in system error.
Thanks in advance.
Warm Regards,
Gouri

Hi Bhavesh,
I am getting a PO file from source system which contains data and control record. But target system expects two different files for data and control. So in mapping program I have done this.
When interface split happens for one scenario and the multiple messages are going to the same receiver, an internal queue name is generated from the message ID of the original message, to ensure that the correct processing sequence is maintained. As a result, the quality of service switches from EO to EOIO. Here is the reference link:
http://help.sap.com/saphelp_nw04/helpdata/en/28/68073c8e56f658e10000000a114084/frameset.htm
Also can you please elaborate on CCMS?
Thanks in advance.
Warm Regards,
Gouri

Exporting processed messages from adapter engine monitoring to excel

Hey experts,
I have some messages that are processed successfully. I can see them in the message monitoring for adapter engine in the RWB. I want to know if there is a way to export these messages to excel file.
Also we have a files archived by PI with a .001 extension attached to them. Is there a way to open these files and look at the processed messages?
Any help would be greatly appreciated.
Regards.

I can see them in the message monitoring for adapter engine in the RWB. I want to know if there is a way to export these messages to excel file.
I don't think so.But you can right click.Select View Source.And then save the message in a notepad.
Also we have a files archived by PI with a .001 extension attached to them. Is there a way to open these files and look at the processed messages?
I don't get this! You can open these files by doing a right click.Open with wordpad.

Monitoring Adapter Engine J2SE

Hi,
I have setupt he SLD Accessor on the J2SE Adapter Engine. If one check in the log the connecting to the SLD is successful.
Also the Adapter Engine is registered in the SLD as type XI Adapter Engine in Technical Systems > Process Integration.
I can also see this J2SE Adapter Engine in the RWB. However the LED is red and the error status is "Unable to establish connection to "https://"hostname":-1/rtc.
Please can you assists to resolve this matter.
Much appriciated.
Regards
Willie Hugo

Hi ,
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,
joel

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

Error in Adapter engine in RWB

Hi,
I'm facing 2 type of issues in RWB,
Issue 1) Adapter Engine is in Red State in Component monitoring,
Error: Details for 'Is the Adapter Engine Running?'
Response from Adapter Engine: Fatal ArchiveJob (Archiving) failed.(Details: Code: MS.JOB.ARCHIVE; Location: com.sap.engine.messaging.impl.core.job.executor.ArchiveExecutor; Reason: java.io.IOException: The HTTP request of command "MODIFYPATH" did not reach the XMLDAS. This may indicate that the credentials for the HTTP destination have expired.; Time: 31.03.2011 00:00:05)Response from Adapter Engine: Fatal ArchiveJob (Archiving) failed.
2) If I click, any one of the option like Communication Channel monitoring, Engine Status etc, I'm getting the error
"Internet Explorer cannot display the webpage"
It seems to be the URL to open these component(Communication Channel monitoring, Engine Status etc ) is wrong. Fromwhere the URL address is taken? Where we need check the host name??
I searched in sdn, but could not find any related topics.
Kindly help me resolve this issue ASAP.
Thanks & Regards,
Baskaran K

Hi Baskaran,
For 1), did you check if the XML DAS communication user (used in destination "DASdefault") is configured correctly according to the documentation http://help.sap.com/saphelp_nwpi71/helpdata/EN/43/68fac39a363d33e10000000a11466f/frameset.htm and is assigned to the "XMLDASSecurityRole" role?
And check if you have configured the rules for your Archiving job (Component Monitoring -> Adapter Engine XIE -> Background Processing).
It seems the archiving does not work because of configuration issues.
An archiving job without rules means: all messages are relevant for archiving. The delete job will only delete messages which are not relevant for archiving. So it does not do anything in this system. It can lead to the database table keeps growing, if it's the case too.
You should check the archiving configuration so that the archiving job runs successfully.
If you do not want to archive the messages, please deactivate the archiving job. Then the delete job should clean the old messages with the next execution.
You may delete it straightly on the Background Processing.
For the 2), "Internet Explorer cannot display the webpage", try using the compatibility mode of your browser.
Regards,
Caio Cagnani

"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

How to hide a payload in sxmb_moni and RWB and Adapter engine.

Hi
I need to hide the pay load in sxmb_moni, RWB, Adapter engine. Because payload has some sensite information.
I need to hide the pay load for perticuler interface Name (http://filetoidoc.com) only. not all payloads.
Please help us this.
advanced thanks
Sati

Ofcourse you can:)
below are the fields mentioned in blogs
We can also tell exactly which interface/service/namespace can be used:
SXMBPARTY= Communication Party
SXMBPRTAG= Issuing Agency
SXMBPRTTYP= Identification Scheme
SXMBSERV= Service
SXMBIFNS = Interface Namespace
In your case you will use the last one SXMBIFNS
Thanx
Aamir

Adapter Engine Issue in RWB

Similar Messages

Maybe you are looking for