Adapter engine Error not caught in alert rule &alert category

Hi All,
I have cretaed my alert rule as follow.
Conditions
      Connected To Message ; Not Relavant
       Sender Service   : *
       Sender Interface : Test_OB
       Sender NameSpace   :urn:abc.com
       Receiver party : *
       Reciver Service:*
       Receiver Interface : *
       Receiver Namespace:*
Where did the error occur
    No restriction.
When i tested this alert rule, mails are getting triggered for Integration engine alerts. But when messages fails in adapter engine, i am not getting any alerts/mails at all. Why this happens?
How should i debug this?

Check this for troubleshooting: /people/michal.krawczyk2/blog/2005/09/09/xi-alerts--troubleshooting-guide
Also the alert should be raised in Adapter Engine for Test_OB as source interface.
Uncheck Suppress Multiple Alerts of This Rule checkbox.
Regards,
Abhishek.

Similar Messages

How to get Alerts mail for adapter engine errors in SAP PI 7.0

Hi Friends,
I configured Alerts in PI 7.0. with the help of t-code u2018ALRTCATDEF and created a new alert catergory.
In container tab i have mentioned all give below elements.
SXMS_MSG_GUID, SXMS_RULE_NAME, SXMS_ERROR_CAT, SXMS_ERROR_CODE, SXMS_FROM_PARTY, SXMS_FROM_SERVICE, SXMS_FROM_NAMESPACE, SXMS_FROM_INTERFACE, SXMS_TO_PARTY, SXMS_TO_SERVICE, SXMS_TO_NAMESPACE,SXMS_TO_INTERFACE
I am getting alerts when I manually test the alerts configurations by running the report u2018RSALERTTESTu2019.
I am getting mail as :
Alert ID: ##00009##
Dear Administrator,
This is with respect to XI Scenario. During processing of XML file from ECC or XYZ Server, Following error has been occured:
Message ID:
Interface:
NOTE: To check the file name, go to SXMB_MONI and search for above message ID.
Double click on that message ID and click on error in left hand tree.
Please take appropriate action in co-ordination with respective functional and BASIS consultant.
But When I am getting a error , I am not getting an alert mail. Right now iam doing in XI Development.
I am not getting an Alert mail , when my message is in status of : System Error . Error catergory is : XI_J2EE_ADAPTER_JDBC.
Kindly tell how to get alert mail for error catergory : XI_J2EE_ADAPTER_JDBC and in Adapter engine errors.
How to get alert mail when my message is failed with any reason in Adapter engine.
Waiting for quick replay. Please help me out.
Regards,
Ahmed.

Hi thanks for quick reply.
As per your given link : http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/14877. [original link is broken]
I have done all these steps. But still little problem.
as per link he is getting Error description , error message id , alert rule..
In my case I am not getting these information. when my messages failed. When I am doing manully testing the alert getting an mail as :
Alert ID: ##00009##
Dear Administrator,
This is with respect to XI Scenario. During processing of XML file from ECC or XYZ Server, Following error has been occured:
Message ID:
Interface:
NOTE: To check the file name, go to SXMB_MONI and search for above message ID.
Double click on that message ID and click on error in left hand tree.
Please take appropriate action in co-ordination with respective functional and BASIS consultant.
Is it okay the body of mail??.
I am not getting alert mail when my messages failed in adapter engine and Integration Engine.
Ex my message is failed in AE:as below.
My messages flow as : SAP --> XI --> DB.
Messages is success (in ECC moni)> XI moni also success> XI Adapter engine getting error as (Status: System Error) and (Error Category : XI_J2EE_ADAPTER_JDBC).
Regards,
Ahmed.

Alert for adapter engine error

Hello experts
We have configured the alerts for the adapter engine errors .We have configured the variable &SXMS_TO_ADAPTER_ERRTXT& element which is having the CHAR70 type for getting the adapter engine error text in the alert inbox.so for any adapter engine error greater than 70 chracters ,it is getting truncated to 70 chracters only.but we want to have the whole adapter error log text.
Can anyone please throw some light on this.
Thanks
sabyasachi

Moha,
It seems that it cannot support more than that.
Problem with Alert Text
Re: Message Size in ALERTS
It is worth taking a look at this blog:
/people/community.user/blog/2006/10/16/simple-steps-to-get-descriptive-alerts-from-bpm-in-xi
Regards,
---Satish

Abap tables for adapter engine errors

Hello,
Which ABAP tables in PI will have the data relating to adapter engine errors (like the communication channel errors). Is there any way I can get the adapter engine errors from abap tables?
Any help is very much appreciated.
Thanks
MLS

Hello,
What I am trying to do is write a report in ABAP, which will read the table for errors (for messages which are not processed successfully in Integration engine or adapter engine) and email those errors to users. If there is communication channel error in RWB, the message in sxmb_moni is still shown as success and is not being updated in table SXMSPERROR.
We cannot use PI Alerts here since the email list is dynamic for the same PI interface.
Any ideas on how to accomplish this?
Thanks
MLS

Adapter Engine is not working

hi all
My Adapter Engine is not working in RWB.
In runtime workbench - message monitoring u2013 message from component - adapter engine is not working
experts provide me the solution
Regards
Raju

Hi
What u r not getting kindly elobrate.
R u using Component MOnitoring r Message Monitoring.
Component Monitoring --> Adapter Eninge --> u can see all CC
Im Message Moniotring --> AE --> u can Set the Sender and receiver System to view the messages
srini

PI 7.11 Central Adapter Engine is not started

Hi Experts,
After active objects list, in the central adapter engine: ache update not yet started.
Looking for this error, is possible that is the RFC INTEGRATION_DIRECTORY_HMI because responde 403 forbidden,
Did you have any tips?
Thank you!
Bruno

Are you sure supplied credentials are valid for PIISUSER?
1) HTTP response does not contain a valid XML root tag or Error 'HTTP status code 400 Bad Request' while executing HTTP request (calling method 'get_status')
The error 'HTTP response does not contain a valid XML root tag' occurs when path prefix of the destination is '/dir/hmi_cache_refresh_service/ext'.
The error 'Error 'HTTP status code 400 Bad Request' while executing HTTP request (calling method 'get_status')' when path prefix is '/dir/CacheRefresh'.
Solution: Go to transaction sm59 and open destination of type 'H' INTEGRATION_DIRECTORY_HMI. Select "Connection Test". The connection test should return HTTP response 200.
Now go to "Logon & Security" tab and ensure that username and password are stored in the system. Fixing credentials should fix the problem.
Note: Credentials cannot be tested via "Connection Test" tool. If used credentials are wrong, the server simply returns login html page (using HTTP response code 200). As the login html page is not a valid cache refresh xml document, an error is shown in sxi_cache.

Cache Refresh for Adapter Engine is not working

Hi,
our adaper engine is not working. At RTW no there are no channels visible and the button "Test Cache Connectivity" leads to a yellow icon for the adapter engine with the error text: "Attempt to fetch cache data from Integration Directory not yet started or still in process".
The error reason is at http://<j2ee host>:<port>/CPACache/history.jsp available: com.sap.aii.af.service.cpa.impl.exception.CPADirectoryCacheException: Couldn't open Directory URL (http://pixd1.digoff.no:55200/dir/hmi_cache_refresh_service/ext?method=CacheRefresh&mode=C&consumer=af.xd1.dat-dof-xi), due to: HTTP 403: Forbidden
The cache refreh request from adapter engine to directory gets an 403 error. What is strange: No problem, to execute that request in a browser, i get the right message, no fault.
I searched for notes or other threads, i could find only <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bc_xi/~form/handler%7b5f4150503d3030323030363832353030303030303031393732265f4556454e543d444953504c4159265f4e4e554d3d373531383536%7d">SAP note 751856</a> , but it is valid for XI 3.0; we are on PI 7.0.
I checked out:
- no user blocked
- all system users have standard authorisations
- reimport of SAP BASIS SWC
- SICF services for XI active
- destination INTEGRATION_DIRECTORY_HMI working
Any idea, how i can get the adapter engine working?
Regards,
Udo

Hi,
There are two ways to display the content of the CPA cache refresh.
1. The Cache-Update Content-XML
Document can be stored in the Adapter Framework database (J2EE schema) for further analysis. Here you have to set the property in the J2EE Visual Administrator tool.
To do so, proceed as follows:
=>J2EE-service SAP XI AF CPA Cache
=> set property trackCacheUpdateXML= true
=> You can now display the cache update XML with the alias CPACache
=> View Cache Update History
=> View Cache Update XML
2. The content of the cache refresh from the Integration Directory intothe CPA cache can be written to an XML file: Here you have to set the property inthe J2EE Visual Administrator tool:
=>J2EE-service SAP XI AF CPA Cache
=> set property J2EE service SAP XI AF CPA Cache cacheUpdateDebugFile = true
=> the CPA cache refresh XML file will be in the server(0) directory search for the following file names:
=> value of the property cacheUpdateDebugFile.deltaif you intend to see the delta refresh accordingly and the value of the property cacheUpdateDebugFile.full if
you intend to see the full cache refresh content
Note: After your analysis, do not forget to reset the properties value to false.
You can delete the XML cache-
refresh table: alias CPACache
=> View Cache Update History
=> Delete History
Also check out the user and its permission.
regards
Aashish Sinha
PS : Reward points if Helpful

J2SE Adapter Engine Error

Hi everyone,
I am facing couple of issues with J2SE adapter engine.
1. First Issue
Config in SLDaccessor -
file adapter java class
classname=com.sap.aii.messaging.adapter.ModuleSLDaccessor
SLD.host=<HOST>
SLD.port=50xxx
SLD.user=user
SLD.password=pass
SLD.adapterEngineName=AdapterEngine
Config in Sender File Channel
file adapter java class
classname=com.sap.aii.messaging.adapter.ModuleFile2XMB
version=30
mode=FILE2XMBWITHROWCONVERSION
XI.SLDConfiguration=SLDaccessor
#XI.TargetURL=http://<HOST>:<50xxx>/sap/xi/engine/?type=entry
XI.TargetURL=<fromSLD>
XI.QualityOfService=EO
XI.Client=001
<Other parameters like InterfaceName / FCC>
If I use XI.SLDConfiguration=SLDaccessor and XI.TargetURL=<fromSLD>, I get an error of HTTP 401 unauthorized.
If I ignore the SLDaccessor, the message is processed successfully.
Am I missing anything in the above configuration?
The user id user is having the roles of SAP_SLD_CONFIGURATOR and SAP_XI_APPL_SERV_USER.
2. Second Issue
In RWB -> Component Monitoring -> J2SE Adapter Engine, there is an error coming up - Unable to establish connection to "https://<LocalHost>:50001/rtc"
The port is wrong ... it should be 8200. My question is, from where to fix this?
Any help will be highly appreciated.
Thanks,
Neetesh

Hi Neetesh,
After copying tech_adapter on your local machine douple click on run_adapter.bat and then open internet explorer and enter http://l<ocalmachine_ip_address>:8200/adapter.html
After doing this you will get logon popup, enter user & password and configure the adapters.
Secondly you can see the port in SLDAPICUST if I am not mistaken. (not very sure)
Compare your configuration with below one
file adapter java class
classname=com.sap.aii.messaging.adapter.ModuleFile2XMB
version=30
mode=FILE2XMB
Integration Engine address and document settings (example, see docu)
XI.TargetURL=http://<host>:8000/sap/xi/engine?type=entry
XI.User=testuser
XI.Password=pass123
XI.QualityOfService=EO
#XI.SenderParty=
XI.SenderService=LocalSystem
#XI.ReceiverParty=
XI.ReceiverService=LocalSystem
XI.Interface=IM_J2SE
XI.InterfaceNamespace=http://abc.com/j2se/test
##File Adapter specific parameters (example, see docu)
file.type=BIN
#file.type=TXT
file.encoding=UTF-8
file.sourceDir=c:/sender
file.sourceFilename=sender1.xml
#file.processingMode=test
file.processingMode=delete
#file.processingMode=archiveWithTimeStamp
#file.archiveDir=./temp_archive
#file.retryInterval=20
file.pollInterval=30
Regards,
Sarvesh

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

Non Central adapter engine error

Hi All, Here is my Scenario: Trying implement /configure Non-central adapter engine hosted separate (J2EE) server. This will be connected to XI server(Integration engine and SLD) from where messages are sent/received. When I try to post message from XI to Non_central adapter engine following is the message u201CThe requested protocol u201CXIu201D is currently unavailableu201D Then I realized there is a problem in Non-central adapter engine configuration, which will be connected to SLD and Integration engine. I can see technical system and business system in SLD for Non-central adapter engine. Following is the findings in NWA of same host where non-central adapter engine. 1) I see all J2EE services are running 2) Application u201Ccom.sap.aii.adapter.soap.libu201D is no started and status is u201Cfailed to startu201D. Later I tried to restart and following are the 4 error messages in sequence from trace file. a) Message: Access to XI AF MS resource failed. Date: 2010-07-02 Time: 22:05:15:273 Category: com.sap.aii.adapter.soap.ra.SPIManagedConnectionFactory Location: com.sap.aii.adapter.soap.ra.SPIManagedConnectionFactory.SPIManagedConnectionFactory() Application: Thread: Deploy Start Application Thread Data Source: j2ee\cluster\server0\log\defaultTrace_00.trc B) [ERROR CODE DPL.DS.5029] Exception in operation [startApp] with application [sap.com/com.sap.aii.adapter.soap.lib]. [EXCEPTION] com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5029] Exception in operation [startApp] with application [sap.com/com.sap.aii.adapter.soap.lib]. at com.sap.engine.services.deploy.server.application.ApplicationTransaction.rollbackPart(ApplicationTransaction.java:619) at com.sap.engine.services.deploy.server.application.StartTransaction.rollbackPart(StartTransaction.java:653) at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:506) at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:483) at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:584) at com.sap.engine.services.deploy.server.application.ParallelAdapter.runMe(ParallelAdapter.java:180) at com.sap.engine.services.deploy.server.application.ParallelAdapter.access$000(ParallelAdapter.java:43) at com.sap.engine.services.deploy.server.application.ParallelAdapter$1.run(ParallelAdapter.java:340) at com.sap.engine.frame.core.thread.Task.run(Task.java:73) at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:175) at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:274) Caused by: com.sap.engine.services.connector.exceptions.BaseDeploymentException: Cannot bind "com.sap.aii.adapter.soap.lib";. at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.instantiateMCF(ResourceAdapterStarter.java:393) at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.initResourceAdapter(ResourceAdapterStarter.java:122) at com.sap.engine.services.connector.deploy.ConnectorContainerImpl.prepareStart(ConnectorContainerImpl.java:303) at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.prepareStart(ContainerWrapper.java:363) at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:251) at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:209) at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:502) ... 8 more Caused by: com.sap.engine.services.jndi.persistent.exceptions.NameAlreadyBoundException: Object with name com.sap.aii.adapter.soap.lib is already bound. at com.sap.engine.services.jndi.implserver.ServerContextImpl.bind(ServerContextImpl.java:343) at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:850) at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:695) at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:912) at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.bind(ResourceAdapterStarter.java:487) at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.instantiateMCF(ResourceAdapterStarter.java:375) C) Cannot bind "com.sap.aii.adapter.soap.lib";. [EXCEPTION] com.sap.engine.services.connector.exceptions.BaseDeploymentException: Cannot bind "com.sap.aii.adapter.soap.lib";. at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.instantiateMCF(ResourceAdapterStarter.java:393) at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.initResourceAdapter(ResourceAdapterStarter.java:122) at com.sap.engine.services.connector.deploy.ConnectorContainerImpl.prepareStart(ConnectorContainerImpl.java:303) at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.prepareStart(ContainerWrapper.java:363) at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:251) at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:209) at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:502) at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:483) at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:584) at com.sap.engine.services.deploy.server.application.ParallelAdapter.runMe(ParallelAdapter.java:180) at com.sap.engine.services.deploy.server.application.ParallelAdapter.access$000(ParallelAdapter.java:43) at com.sap.engine.services.deploy.server.application.ParallelAdapter$1.run(ParallelAdapter.java:340) at com.sap.engine.frame.core.thread.Task.run(Task.java:73) at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:175) at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:274) Caused by: com.sap.engine.services.jndi.persistent.exceptions.NameAlreadyBoundException: Object with name com.sap.aii.adapter.soap.lib is already bound. at com.sap.engine.services.jndi.implserver.ServerContextImpl.bind(ServerContextImpl.java:343) at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:850) at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:695) at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:912) at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.bind(ResourceAdapterStarter.java:487) at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.instantiateMCF(ResourceAdapterStarter.java:375) d) Global operation [startApp] over [application] [sap.com/com.sap.aii.adapter.soap.lib] finished with errors for [16]ms on server [4796750 >>> without warnings << >> Errors <<< 1). Cannot bind "com.sap.aii.adapter.soap.lib";. -> Object with name com.sap.aii.adapter.soap.lib is already bound. 2). com.sap.engine.services.connector.exceptions.BaseDeploymentException: Cannot bind "com.sap.aii.adapter.soap.lib";. at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.instantiateMCF(ResourceAdapterStarter.java:393) at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.initResourceAdapter(ResourceAdapterStarter.java:122) at com.sap.engine.services.connector.deploy.ConnectorContainerImpl.prepareStart(ConnectorContainerImpl.java:303) at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.prepareStart(ContainerWrapper.java:363) at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:251) at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:209) at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:502) at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:483) at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:584) at com.sap.engine.services.deploy.server.application.ParallelAdapter.runMe(ParallelAdapter.java:180) at com.sap.engine.services.deploy.server.application.ParallelAdapter.access$000(ParallelAdapter.java:43) at com.sap.engine.services.deploy.server.application.ParallelAdapter$1.run(ParallelAdapter.java:340) at com.sap.engine.frame.core.thread.Task.run(Task.java:73) at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:175) at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:274) Caused by: com.sap.engine.services.jndi.persistent.exceptions.NameAlreadyBoundException: Object with name com.sap.aii.adapter.soap.lib is already bound. at com.sap.engine.services.jndi.implserver.ServerContextImpl.bind(ServerContextImpl.java:343) at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:850) at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:695) at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:912) at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.bind(ResourceAdapterStarter.java:487) at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.instantiateMCF(ResourceAdapterStarter.java:375) Any of you have seen this kind of problem. Thanks Sam Edited by: sam robert on Jul 2, 2010 10:24 PM

Hi Sam,
1- What is your PI version?
2- Do you use a High Availability system?
3- Can you describe your scenario?
From the 503 error, here is a generic description:
The error message 503 Service unavailable Application stopped! is displayed.
Description:The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. If known, the length of the delay MAY be indicated in a Retry-After header. If no Retry-After is given, the client SHOULD handle the response as it would for a 500 response.
Note: The existence of the 503 status code does not imply that a server must use it when becoming overloaded. Some servers may wish to simply refuse the connection.
Possible Tips: Because of J2EE application com.sap.aii.af.ms.app not active
u2022 Try to (re)start the application using the Visual Administrator Choose Server --> Services --> Deploy --> View on Application or restart the J2EE engine
u2022 The problem is that not all J2EE services can be started by the J2EE. i.e Start the Visual Administrator and select Server->Services->Deploy in the tree on the left. On the right-hand side, choose the Runtime tab page. You see a tree in the right window with all applications if you select the APPLICATION radio button. Check if they are running, otherwise choose Start. Usually the J2EE engine starts all services automatically.
u2022 Refer SAP Note 803145,807000,791655
Regards,
Caio Cagnani

Reg Unable to find URL for Adapter Engine Error

Hello,
During execution of a scenario, i am getting these errors in sxmb_moni:
AE_DETAILS_GET_ERROR
3: Unable to find URL for Adapter Engine af.xip.poecspxioo4
Error when reading the access data (URL, user, password) for the Adapter Engine.
Seems like it is a problem of XI Server unable to locate the Central adapter engine due to some parameter not set properly.
So, what are the points we can check while installation of XI so as to rectify this problem.

Hi all,
I got the similar error in my scenario and i solved the same.Actually i ma not pretty surte this will solve your problem.
In my case proxy generation settings was mis configured in the sender system. so its caused the reason.
I made an entry in the SPROXSET table and i did other activities like RFC and application system also.
Then its worked for me. Its not matching with your case please do ignore this one
Regards
Vijay

Schema Validation using Adapter Engine : Error

Hello Guys,
For SOAP message coming into PI, I am doing schema validation by adapter engine but getting below error message
com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessageFormatException: Schema Schema1.xsd not found in /usr/sap/PID/<Server>/j2ee/cluster/server1/validation/schema/af7c332075ce11e08e23ddce0a512253/urncompany.comcrmexternald2c/ServiceRequest_Out/urncompany.comcrm~enhancements/Schema1.xsd (validation/schema)
* at com.sap.aii.adapter.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:1178)*
* at sun.reflect.GeneratedMethodAccessor336.invoke(Unknown Source)*
* at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)*
* at java.lang.reflect.Method.invoke(Method.java:585).........................*
Here are some details
- Using standard SAP Message Type
- Enhance data type
- while exporting schema, there are 3 files in zip file
1) mainschema (renamed it to MessageType name)
2) Schema1.xsd
3) Schema2.xsd
I have followed the step according to below document
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d06dff94-9913-2b10-6f82-9717d9f83df1?QuickLink=index&overridelayout=true
I have also checked schema1.xsd on PI server and File is there but still getting error.
Any suggestions ?
Thanks
Edited by: chetan patel on Jan 31, 2012 10:50 PM

Please make sure that main xsd uses import or include tag to reference both schema1.xsd and schema2.xsd. If the main xsd does not do it, Pi cannot verify it. Since you package all the files as zip file, also make sure the path for the secondary files are in proper location.
In short, the import element allows you to use schema components from any schema; the include element allows you to add all the components of an included schema to the containing schema. If the target namespace is same for both then include tag should be good enough. If you don't find one, you might have to use include tag element in the main or parent xsd file.
Edited by: Baskar Gopal on Jan 31, 2012 5:18 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 Cache not getting Updated

Hello Everyone,
My adapter engine Cache is not getting updated in my development server,
PFA... file for the error description after i refresh my Full ID cache from Administration tab
Regards,
Sushant

Hi Sushant,
Please check the RFC destination "INTEGRATION_DIRECTORY_HMI" is working or not?
Check the parameters as suggested by others for this destination type.
Check the USER which is mentioned for this RFC destination is locked or not? if so please unlock it.
Try to change the pwd for this user and try again..
IF none of them are working please refer this notes 764176
Regards
Bhargava Krishna

Adapter Engine Error Message on RWB

Hello
We are getting an Red color error message on Adapter engine on RWB
monitoring ---> Component Monitoring.
Here is the error message:
SLD access SLD host:port = sap03:50000
Error getting JPR configuration from SLD. Exception: No entity of class
SAP_BusinessSystem for XID.SystemHome.sap03 found
No access to get JPR configuration
Please advise for solving the error message on adapter engine.
Thanks & regards
AK
SAP Version : NW04 (XI 3.0) SP20

Hi Senthil,
As suggested by others there is no problem with your communication channels ,,, the problem you face is because Your DBA has initiated the SHUTDOWN IMMEDIATE command. This will shutdown Oracle and terminate all active operations.
Please tell him to start the services and Wait until Oracle has been restarted by your DBA.
Regards
joel

Adapter engine Error not caught in alert rule &alert category

Similar Messages

Maybe you are looking for