Adapter Engine self-test status red / Error

Hi.
Im having trouble figuring out what to do about this error.
In Runtime Workbench --> Component Monitoring --> Integration Server --> Adapter Engine, the Adapter Engine self-test (and ping status) are in error.
The error message is: HTTP Request failed. Error code: "403". Error Message: "Forbidden [http://<server>:<port>/AdapterFramework/rtc]".
Anyone have an idea?
Regards...
Peter

Hi again.
Looking in the default trace I get this Info:
Hope it contribute to a solution.
Regards...
Peter
ACCESS.ERROR:
Authorization check for caller assignment to J2EE security role [sap.com/com.sap.aii.af.app*AdapterFramework : xi_af_rtc].
Exception when reading settings:
Thrown:
MESSAGE ID: com.sap.aii.rwb.exceptions.rb_CommunicationException.HttpReqFailed
com.sap.aii.rwb.exceptions.RequestFailedException: HTTP request failed. Error code: "403". Error message: "Forbidden [http://<server>:<port>/AdapterFramework/rtc]"
at com.sap.aii.rwb.exceptions.RequestFailedException.forHttpErrorCode(RequestFailedException.java:79)
at com.sap.aii.rwb.rtcheck.rtcclient.GrmgConnector.request(GrmgConnector.java:238)
at com.sap.aii.rwb.rtcheck.rtcclient.GrmgConnector.getSettings(GrmgConnector.java:105)
at com.sap.aii.rwb.core.XIRTCComponent.refreshConfigParameters(XIRTCComponent.java:279)
at com.sap.aii.rwb.web.componentmonitoring.model.CmMainModel.getConfigParameterCategoriesForSelectedXIComponent(CmMainModel.java:424)
at jsp_component_monitoring1209546798419._jspService(jsp_component_monitoring1209546798419.java:579)
at com.sap.engine.services.servlets_jsp.server.jsp.JspBase.service(JspBase.java:112)
at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:566)
at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:190)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
at com.sapportals.htmlb.page.PageProcessorServlet.handleRequest(PageProcessorServlet.java:68)
at com.sapportals.htmlb.page.PageProcessorServlet.doPost(PageProcessorServlet.java:22)
at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmPageProcessor.doPost(CmPageProcessor.java:35)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
at jsp_FC_Secure1209546795341._jspService(jsp_FC_Secure1209546795341.java:15)
at com.sap.engine.services.servlets_jsp.server.jsp.JspBase.service(JspBase.java:112)
at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:566)
at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:190)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
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:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
User XIRWBUSER, IP address
HTTP request processing failed. HTTP error [403] will be returned. The error is [You are not authorized to view the requested resource.No details available].

Similar Messages

RWB - Integration Engine self test - web service security and proxy

Hi,
I am working with a new installation of PI 7.0. In the runtime workbench, under self test for integration engine, there is this error/warning:
""Details for 'Is Web service security available?'
Communication error: Proxy calls are not permitted on sender or receiver side on the IS (client)""
What exactly is the problem? Is there any additional configuration needed within PI to use proxies? We do not have the cryptographic toolkit installed. Is that nesseccary to work with proxies? We have done several other scenarios with RFC, MAIL, HTTP, etc and they work fine. If anyone else had this problem and managed to fix it, please let me know..
Thanks,
Lasya

You can ignore this error. It is simply a warning that says message level security has not been configured. Without message security too, you can do proxy communication.
But, if you want to configure messag level security, go through XI Config guide section 12.4.
Message was edited by: Jay

Message stuck in Adapter Engine queue with status "Delivering"

Hi All,
I have a File to File EOIO scenario. The messages are sucessfully delivered from IE to AE. All entries have a chequered flag in SXMB_MONI. No messages are stuck in IE queue (SMQ2). But the message is stuck in AE queue with status "Delivering". I can not resend or cancel the message coz the status is "delivering".
The reason it is in "delivering" status is due to some config error that I made in Communication Channel FTP parameters. Now it is corrected. But how do I deal with this message now?
Restart of server is not an option here. Is there are place I can delete the message from AE queue?
Thanks
Jaishankar

You can see the queues status (and number of stuck entries etc) through the link:
http://<host>:<port>/MessagingSystem/monitor/systemStatus.jsp
There, you can maintain the queues.
There is also a link for the EOIO Sequence Monitor:
http://<host>:<port>/MessagingSystem/monitor/sequenceMonitor.jsp
There you can see the stuck messages and maintain these.
Make sure to handle the proper message IDs.
All of these are acessible through the Messaging System main page:
http://<host>:<port>/MessagingSystem/
Regards,
Henrique.

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

Adapter Engine Error

Hi,
i am working on MQ-XI-BW Scenario.i have configured JMS Adapter in Plain J2SE Adapter Engine.But the status is red with a message
"javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for 'BWXI:TEST.QMGR'
 at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:546)
 at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1450)
 at com.ibm.mq.jms.MQConnection.createQMNonXA(MQConnection.java:960)
 at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:159)
 at com.ibm.mq.jms.MQQueueConnectionFactory.createQueueConnection(MQQueueConnectionFactory.java:215)
 at com.sap.aii.messaging.adapter.ModuleJMS2Transport.init(ModuleJMS2Transport.java:382)
 at com.sap.aii.messaging.adapter.ModuleHandlerImpl.run(ModuleHandlerImpl.java:576)
 at java.lang.Thread.run(Unknown Source)"
My class path looks fine.i am on SP9. there is an OSS note with similar error. But the Pre requisite is given as SP5.
what could be the reason behind this issue?
When i try to refresh the central integration server cache in ID using Env->Cache Notifications, i am getting a message
 http connection to "http://bwxi:8200/CPACache/invalidate" returns the status code "401" in response
This particular URL is not accepting any user and password. Do i need to set the user name and password somewhere so that i can have access to this?
Please help me out.
Regards
Sathya

Hi Amol,
 Thanks a lot.I am not very confident in my configuration.Could you please verify the configuration parameters once?
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
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.
XMB.SenderBusinessSystem=MQSeries
XMB.SenderService=BS_MQ
XMB.SenderInterfaceNamespace=http://xitest
XMB.SenderInterfaceName=MI_Out_File
XMB.ReceiverBusinessSystem=MTX
XMB.TraceLevel=1
XMB.LoggingLevel=1
XMB.QualityOfService=EO
XMB.QueueId=ABCDEFABCDEF
XMB.ContentType=text/xml
URL of XI IS to send the messages to
XMB.TargetURL=http://bwxi:8000/sap/xi/engine?type=entry
XMB.User=XIISUSER
XMB.Password=Mind2005
XMB.Client=100
URL of file adapter if a loopback JMS to File should be configured
XI.TargetURL=//localhost:8210/file/receiver
uncomment the following settings if needed (independent on JMS provider)
JMS.QueueConnectionFactoryImpl.user=MUSR_MQADMIN
JMS.QueueConnectionFactoryImpl.password=Mind2005
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
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 CH_BWXI
JMS.QueueConnectionFactoryImpl.method.setTransportType=java.lang.Integer {com.ibm.mq.jms.JMSC.MQJMS_TP_CLIENT_MQ_TCPIP}
JMS.QueueConnectionFactoryImpl.method.setQueueManager=java.lang.String TEST.QMGR
JMS.QueueImpl.classname= com.ibm.mq.jms.MQQueue
JMS.QueueImpl.constructor=java.lang.String LQ
JMS.QueueImpl.method.setTargetClient=java.lang.Integer {com.ibm.mq.jms.JMSC.MQJMS_CLIENT_NONJMS_MQ}
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
Regards
Sathya

In RWB----component monitoring --adapter engine-- status

Hi ,
In the Runtime work bench component monitoring if we click on adapter engine we get two tabls
CCMS Status: Last Retry Jan 26, 2011 1:55:15 PM CET Ping and Self-Test Help
Ping Status: HTTP request failed. Error code: "404". Error message: "Not Found [http://lYYYY:ZZZZ/AdapterFramework/rtc]" Last Retry Jan 26, 2011 2:03:05 PM CET ... Details
Self-Test Status: HTTP request failed. Error code: "404". Error message: "Not Found [http://lYYYY:ZZZZ/AdapterFramework/rtc]" Last Retry Jan 26, 2011 2:03:05 PM CET ... Details

Hi Sandeep,
Besides updating the patch level to the latest and ensure the SP are in the same level, the notes I would recommend would be:
#1285224 - Http 404 error in details display for Adapter Engine
#804124 - HTTP communication with XI Adapter Engine fails (this one you have already mentioned)
Hope it helps too
Regards,
Caio

CPALookupException while sending a Test message to Adapter engine

Hello Experts,
I am getting following exception while sending a test message to Adapter engine through Runtime Workbench.
Error while sending message: com.sap.engine.interfaces.messaging.api.exception.ConfigException: ConfigException in XI protocol handler. Failed to determine a receiver agreement for the given message. Root cause: com.sap.aii.af.service.cpa.impl.exception.CPALookupException: Couldn't retrieve outbound binding for the given P/S/A values: FP=<Configured Party>;TP=;FS=<Configured Communication component>;TS=;AN=<Configured Outbound Interface>;ANS=<Configured Namespace>
This scenario works fine when I submits the message through Integration engine. So ID configuration is perfect. Also cache contents are upto date.
Thanks in advance.
Regards
Rajeev

Error is clearly saying that it is unable to find receiver agreement for that particular interface.
Please check your receiver agreement for the interface.
If your receiver agreement is fine then do CPA cache refresh using following URL:-
http://<host>:<port>/CPACache/refresh?mode=full

Adapter Engine Message in Delivering Status

Hi All,
Any idea how to cancel/delete the messages which are in delivering status in Adapter Engine.
In my case a single EOIO message is stuck in the AE with delivering status. Other messages are flowing successfully using the same cc.
Earlier during such cases we had to restart j2ee/ stop/start AF Messaging to resolve the problem.
Just wondering if theres any other solution?
btw : The message was in delivering status because the password mentioned in the receiver channel was wrong. There were other messages which failed but the status of those messages went into "System Error". Nothing wrong with that, but just wondering why did a single message remain in the "Delivering" status.
I have already been through this thread Re: How to delete message in "Delivering" status. Only exists in Adapter Engine and didnt find/understand anything which could help me.
Thanks
Sumit

Look at these blogs,
How to deal with stuck EOIO messages in the XI 3.0 Adapter Framework : How to deal with stuck EOIO messages in the XI 3.0 Adapter Framework
XI : How to Re-Process failed XI Messages Automatically
Message stuck in Adapter Engine queue with status "Delivering"
Hope this helps

Trigger Alert for error ansynchronous transaction in adapter Engine

Hi XI expert.
As i know that if we have error in ansyncronous transaction, i would not be able to see from SXMB_MONI, i am only can see from message monitoring. the adapter engine will be keep retry until max retry value.
how to trigger alert when the adapter engine already reach the maximum retry ? so the administrator will be aware of the error.
Thank you and Best Regards
Fernand

Hi,
U can raise adapter engine and Integration server related errors by creating alert rule. check the below link and see whether that is what u r looking for.
For raising an alert you need to first configure the alert please follow the below weblog written by Michal Krawczyk
/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--step-by-step
Configuration steps are: go to transaction ALRTCATDEF
1) Define Alert Category
2) Create container elements which are used for holding an error messages.
3) Recipient Determination.
Triggering alert by configuring a rule from RWB.
http://help.sap.com/saphelp_nw2004s/helpdata/en/56/d5b54020c6792ae10000000a155106/content.htm
chirag

Problem in the RuntimeWorkBench, Adapter Engine

Hi Experts,
In the RWB> Component Monitoring>Adapter Engine if i double click on this, it is showing the following error:
CCMS Status: Last Retry Jan 14, 2009 10.42.32 AM CET
Ping Status: HTTP request failed Error Code: "401" Error message "Unauthorized[http://<hostName:Port Number/AdapterFramework/rtc]"
Last Retry Jan 14, 2009 10.43.57 AM CET
Self-Test Status: HTTP request failed Error Code: "401" Error message "Unauthorized[http://<hostName:Port Number/AdapterFramework/rtc]"
Last Retry Jan 14, 2009 10.44.17 AM CET
Ping Status & Self-Test Status trafic light colur is RED.
and also iam not able to open Message Monitoring it is asking 3 times user id and password finally it is displaying Unauthorized error.
It is production system, can any body help on this issue
Regards
Rohit

Hi Rohit
for not able to open Message Monitoring
Check if you have Runtime workbench access. You will require to have SAP_XI_MONITOR role authorization with your user id.
also Check if the XI users (in ABAP) on the system running the SLD are locked. If some are, unlock them.
There is a Monitoring Guide avaiable which will be very useful for you. Please check the User Profile settings described in it.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/0b4580be-0601-0010-d3ad-bd6ce51ae916
There is also a post:
Adapters not working, SLDAccess msg in adapter monitor
take help of this post also
Error: HTTP_RESP_STATUS_CODE_NOT_OK 401 Unauthorized
for HTTP request failed Error Code: "401"
check if user: XIRWBUSER is not locked in R/3
also check if you got a correct password in the XI exchange profile :
com.sap.aii.rwb.serviceuser.name
com.sap.aii.rwb.serviceuser.pwd
com.sap.aii.rwb.serviceuser.language
also try Changed pw in AE and connection is should work
Regards
Abhishek
Edited by: Abhishek Agrahari on Jan 15, 2009 5:55 AM

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

CCMS Status red

hi ,
Integration engine is in status red in component monitoring .I tried a self test and the CCMS status is red.
I cleared all the alerts in CCMS and repeated selft test.Even then the integration engine is in red and the CCMS too.
Anybody please help to resolve the issue.
Thnks,
Am

Hi,
The alerts contain a status indicator with a color and a numerical value. Yellow means a warning, red means a problem, and the numerical value shows the severity of the reported error.
You can configure the CCMS alert :
RZ20>>activate maintenance mode>>>Monitor >>create
create a new monitor by copying an SAP monitor
change the rules to include all systems
select your new monitor >>change>>select node ccms_define_r3_system, Edit>>change and change the parameter values for systems
enablee remote monitoring in RZ21
create a peoperties variant and activate it.
go back i RZ20 and assign methods
you can also define auto reaction method to enable emails in case of alerts. and assign method to a node...
Also check:
http://help.sap.com/saphelp_nw04/helpdata/en/0c/e65b3b18debb64e10000000a11402f/frameset.htm
regards,
Jyoti

No Adapter Engine value in File Adapter Config

Hello,
When we configured File adapter in Integration Directory we noticed that ADAPTER ENGINE pull down is empty.
I cannot assign any value to Adapter Engine field.
It is a new test system and should all be configured already. I wonder if this is ok or not. My experience was that I should be able to see Adapter Engine there??
Moreover Adapter Engine field has a red star which means is mandatory field but I am not sure...?!
I will appreciate any directions from experienced or xi basis people.
Thanks

Follow the steps given in this BLOG for adapter enginer coming in ID -
Adapter Engine cannot be found in Integration Directory
Gud Luck !!

Adapter Engine null

Hi,
I have an error with the adapter engine (PI 7.0):
under Runtime Workbench / Component Monitoring / Integration Server
Adapter Engine is shown with red light: "Adapter Engine null".
Details are saying: "No correct URL exists for the RuntimeCheck. Enter a correct URL in the System Landscape Directory"
If i go to SLD / Administration / Content Maintenance and choose (left side) subject "Landscape Description" and (right side) "XI Adapter Framework" and choose Adapter Engine, there is an empty field "ISMsgURL", which is described with "The URL that points to the integration server. The URL is used to transfer messages from the adapter framework to the integration server".
I can fill it with the URL to IE, but unfortunately it is again empty, if i restart the Java Stack.
Does anybody have had that error or does anybody have an idea how to solve it?
Best regards,
Udo

Hi Udo,
I hope Post configuration is completed.
Have you imported the BASIS component. If not import the BASIS component which is specified in the installation guide.
hope it will solve your problem
Regards,
Ramesh P

XI Production Issue In Adapter Engine Messsege Monitoring

HI every one ,
I am facing a starnge problem. When I am going to SXMB_MONI to check flag status, all messeges are OK and processed. However when I am going to Runtime
workbench - >Messege monitoring - >Adapter Engine, and seeking for system errors/ waiting/ holding / I am getting this as an error.:
Time Stamp Status Description
2008-05-05 11:59:14 Success Admin action: Trying to fail message.
2008-05-05 11:59:14 Success Admin action: The message was successfully
set to status failed.
2008-05-05 11:59:14 Error Trying to deliver asynchronous error
notification (message ID: 94c7b8d0-1a6c-11dd-c9c9-00145e743aaa
(INBOUND)) to sending application:
com.sap.aii.af.ra.ms.api.DeliveryException: Message failed by admin..
2008-05-05 11:59:14 Success Asynchronous error notification
successfully delivered
This messege is available in the Error Log .
Can any one help me why this is happening , and where should I check to detect the probable reason for this!!
points would be Awarded .
Thanks in advance
Arnab
Edited by: Mohd Abdul Khalid on May 5, 2008 9:38 AM

Pls see the error below, this is all what I have......Incase u need some other information, revert back.
Time Stamp Status Description
2008-05-09 00:59:53 Success Trying to put the message into the send queue.
2008-05-09 00:59:53 Success Message successfully put into the queue.
2008-05-09 00:59:53 Success The message was successfully retrieved from the send queue.
2008-05-09 00:59:53 Success The message status set to DLNG.
2008-05-09 00:59:53 Error Received XI System Error. ErrorCode: NO_BACK_SYSTEM_IN_HOPLIST ErrorText: ErrorStack: Legacy system to which acknowledgment message is to be sent is missing in hoplist (with wasread=false)
2008-05-09 00:59:53 Error Transmitting the message to endpoint http://isrxiprd:8000/sap/xi/engine?type=entry using connection AFW failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: NO_BACK_SYSTEM_IN_HOPLIST:.
2008-05-09 00:59:53 Success The asynchronous message was successfully scheduled to be delivered at Fri May 09 01:04:53 GMT+05:30 2008.
2008-05-09 00:59:53 Success The message status set to WAIT.
2008-05-09 01:04:53 Success Retrying to send message. Retry: 1
2008-05-09 01:04:53 Success The message was successfully retrieved from the send queue.
Thanks in advance!!!
Arnab

Adapter Engine self-test status red / Error

Similar Messages

Maybe you are looking for