Adapter Engine Red

Hi All,
In Run Time Work Bench, under Component Monitoring, I find that the Adapter Engine is Red in color.
Red LED; Component Status contains an error-Adapter Engine X01
What could be the reason for this error??
Regards
Kartik

check the communication channel monitoring...if any adapter is in error then it status is always red...
even if in the next attempt if interface testing is successful the adapte status will remain RED...
other alternative...inactive the adatper, activate the chage..again activate and chage it..I think then it will show green status..if every thing goes ok with that adapter:)
Thanks
Farooq.

Similar Messages

Help!Cache status of object for Central Adapter Engine is incorrect

this problem cconfused me several days!
version:PI 7.1
after i activate the communication channel, the cache not update for central adapter engine
problem: in cache status overview, the update for central adapter engine not yet started, but notification is ok.
the update for integration server and mapping run time are all correct.
then when i display wsdl for sender agreement(SOAP sender), show message:Cache status of object abcd123 for Central Adapter Engine is incorrect
if i ignore this message, error message popup:dapter Engine af.xid.sapittest for communication channel abcd123 not registered in SLD
who can help me solve this problem.
thank you in advance.

Hi cheng,
Kindly check if you have set theparameter 'com.sap.aii.connect.integrationserver.sld.name' in your
Exchange Profile, since it's not set by default. Open note #1278563 and follow the procedures.
And you may check the following notes:
#1031321 - Self-Registration of Adapter Engine and RWB fails
#1334053 - No automatic PI 7.10 SLD Registration (Here you'll see the note 764176 which you have already applied and also the note #1117249).
In RWB, is the adapter Engine "red light"? If yes, what is the specific error?
Regards,
Caio Cagnani

Adapter engine in red color status

Dear All,
I got pi production system.When i verified componenet in RWB everything is fine except adapter engine.
Adapter Engine in red color status.Error in Are registrations of connections and protocol handler without errors?
I clicked on details.Please see below
13 of 23 connection(s) registered successfully(it was showing 5 of 23 success after i restarted it's showing 13 of 23)
8 of 8 protocol handler registered successfully
Connection registration failed for connection BC_http://sap.com/xi/XI/System on node 106310950 due to: Failed to register connection BC_http://sap.com/xi/XI/System. Reason: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Failed to load messages into Queue BC_http://sap.com/xi/XI/SystemRecv from database. Reason: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection.
Possible reasons:
1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks.
2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable
3) Connections are not enough for current load.
I tried many ways to resolve this problem unfirtunately i couldn't.Whether this gives any issues i mean shall i ignore this if not please suggest me to resolve this.
Thanks in advance
Regards
Kumar

Dear Team,
I am facing the same issue in SLD(PI Java Stack).
Please find below snapshot. Please Help. Many Thanks .....

Red LED: Adapter Engine ? Help

Hi All,
The status of Adapter Engine in Integration Server is showing status "RED". Displays the messages components contains errors.
Please advise me on resolving the issue .
Kind Regards
Shiva

Hello
As your Adapter engine status in the monitoring is red you can find out which particular channel is having errors. To do this Go to Component Monitoring and click the Adapter Engine under components and then click the Communication Channel Monitoring.
A separate Window would appear for communication channel monitoring and then in filter select Status->Channels with error.
and click Use filter.
it will show you all the channels with errors.
and you can selecting each with radio button you can see the error details and modify accordingly.

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

Adapter Engine / Integration Server Problem

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

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

Configuration of JMS Adapter in Central Adapter Engine

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

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

Error in Adapter Engine

Hi Experts,
In the Component Monitoring, the ADAPTER ENGINE have a RED status, show the message:
Details for Ping Status
Message: Cannot construct correct URL for runtime check using entries in SLD for component af.pid.<hostname>; correct entries in SLD
Stacktrace:
com.sap.aii.rwb.exceptions.OperationFailedException: Cannot construct correct URL for runtime check using entries in SLD for component af.pid.<hostname>; correct entries in SLD
at com.sap.aii.rwb.core.XIJavaRTCComponent.getConnector(XIJavaRTCComponent.java:188)
at com.sap.aii.rwb.core.XIRTCComponent.ping(XIRTCComponent.java:209)
at com.sap.aii.rwb.web.componentmonitoring.model.CompTestModel.doPing(CompTestModel.java:581)
at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage.doPing(CmDynPage.java:425)
at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage.updateTests(CmDynPage.java:525)
at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage.selectNode(CmDynPage.java:552)
at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage.process_treeClick(CmDynPage.java:481)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
Any idea.
Tks in advance.

Hi Pedrão, how are you?
Look at Exchange Profile, if the entries about RWB are the same the entries in the SLD.
You can confirm the Technical System type Process/Exchange Integration and its application system is right.
Follow link about troubleshooting guide:
http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/webcontent/uuid/b0458509-49c1-2a10-1188-af2aeb97ed9a
Regards.
Bruno

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

Adapter engine showing error for file adapters

Hi,
I had configured communication channel using FTP . Because of which the Adapter engine is showing red in the component monitoring. It is saying one of the communicaion channel has error. But when I do a check in the CCs they doesn't show any error. I am getting the same error for NFS as well.
Has anyone come across such a kind of situation? Is it because of wrong entry in CC parameters or is it some BASIS configuration (patch) issue?
Could anyone of you give some guidance on this?
Thanks and Regards
Sanil

Sanil,
Just for testing purpose , delete ur comm.channel and check whether still u r facing the errors. If no errors then its bcoz of u comm.channel. Then we can narrow down the approach. Even after deleting the comm.chanel u get error then check all the channels across all clusters.
Note:After deleting the channel ,give some time and check the same.
Best regards,
raj.

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

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 !!

XI Adapter engine not working

Hi Masters,
Please help to solve the below issue since the system is very high priority.
Adapter Engine showing red index
Connection to system REPOSITORY using application REPOSITORY lost. Detailed information: Error accessing "http://vacifgx:50000/rep/conntest/int?" with user "PIRWBUSER". Response code is 503, response message is "Service Unavailable"
I check the SLDCHECK t-code every thihg is working fine and the password for PIRWBUSER also corrrect.
How to resolve the issue "Service Unavailable " and i getting this message in rwb, integration directory
Thanks in advance
Sunny

Hi Sunny,
U r java services are down.So, check with u r Basis team.
Whenever java services down always comes this type of error.
Thanks
Ravi

Adapter Engine Alert Error

hi team
I have developed Adapter Engine Alerts and i have received an Error. when i checked ion the message monitor and also in the communication chhannel monitoring the following error is being displayed
" Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: No transition found from state: ERROR, on event: process_commence for DFA: Receiver communication chhannel:5601afa75060350a8aae48e821307ba3"
the Receiver communication chhannel is in red colour
please help me out
thanx in advance

Check
How to deploy 3rd party drivers in PI 7.1
SAP Note: 1138877
/people/michal.krawczyk2/blog/2010/03/17/pixi-deploy-a-jmsjdbc-driver-without-jspm
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/60237e74-ef19-2b10-5a9b-b35cc6a28e83?quicklink=index&overridelayout=true
Which version of PI r u using?
chirag.
Edited by: Chirag Gohil on Jul 27, 2010 1:28 PM

Component monitoring - adapter engine error, but no channel in error actual

Hi,
We have a problem in displaying a status of Adapter Engine in RWB. In component monitoring there's a red light and the status - "Are communication channels without errors?" says there's an communication channel in error. But when I click the Communication channel monitoring, everything's green there. Yes, there was an error before, but it's ok now. Why is the AE item in Component monitoring still red? How to make it to reflect the current status?
Thank you,
Olian

Hi Olian,
i am saying to use the cache connectivity test button option from RWB -> compnent monitoring , so have you done cache test using this? if yes, click on refresh display to see the latest adapter engine status..............if it is green, then it is okay..............but if it is red here, it means some comm channel is erroring sometimes - i guess it can be a file adapter using ftp or some rfc adapter......................
if it is green here and compnent monitoring - adapter engine status is red because some comm channel errored in past.........then i think some cache is not getting refreshed - i do not know exactly how to rectify it...........but i can tell you some workaround for it..............the comm channel which was erroring just stop it from comm channel monitoring........then close RWB and again open it and see compnent monitoring - adapter engine status again in it - i think it should be green now.......or try by changing any comm channel description data in ID and save and activate it.........then again check your compnent monitoring - adapter engine status..................but dont worry i think this is a temporary problem
Regards,
Rajeev Gupta
Edited by: RAJEEV GUPTA on Mar 26, 2008 11:50 AM

Adapter Engine Red

Similar Messages

Maybe you are looking for