No Adapter Engine in the Configuration

All,
When we create a new communication channel and select the adapter type (say File) , the transport protocol and message protocol appear - but there is no Adapter engine (which used to be Integration server earlier). Recently the team moved the SLD from one box to another. Is this related?
Any ideas as to why this problem would occur?
Thanks.

>>>Recently the team moved the SLD from one box to another. Is this related?
Sure this could be related - confirm that the SLD moved was correctly. Check Note 720717 to double check the steps and perform the listed checks if you haven't already.
Regards,
Jin

Similar Messages

How to set main host for Adapter Engine in the HA enviroment

Hi, all.
Our XI env. is like the following.
XI 3.0 SP11 on Windows 2003 + SQL Server.
Central Instance(ABAP + J2EE Addon) is running on Host A,
Dialog Instances(ABAP + J2EE Addon) are running on Host B and Host C.
Our design was to have J2EE Adapter engine mainly running on Host A(CI). But after installation, Adapter Engine is running on Host C(one of DIs). When we check from the Runtime WorkBench. It shows Adapter Engine is running on Host C while IS is running on the Host A(CI).
Where can we change this configuration? We want the J2EE AE running on the Central Instance Host.
Any advice appreciated.
Best Regards.

Hi Sejoon,
when we changed the host of XI server in one of our projects one of the things we had to change was the exchange profile entries
http://server:port/exchangeProfile/index.html
to see how your adapter engine is configured
http://server:port/sld
SLD -> Content Maintenance
then
Subset: landscape description
Class: XI Adapter Framework
buth check the exchange profile entries first
Regards,
michal

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

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

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

Unable to Find out Adapter Engine in the Communication Channel

Hi Experts,
I am Unable to select the Adapter Engine As Integration Server in the File Sender Communication Channel.
Please Let Me Know
Regards
Khanna

HI Khanna
Check the SLD that Adapter Engine is insatlled and all the adapter has the metadata there.
Go to Transaction Code SXI_CACHE in the Inetgration Server(XI- ABAP stack) Then you can see the list of components.
Just have a look into Menu Bar - in there goto : GoTo->Adapter Engine Cache ( if the status is green - then it is correct-otherwise you need to refreshit.)
You just go thru mentioned document from service.sap.com/nw04
You will get the full info about that.
/people/michal.krawczyk2/blog/2005/09/07/xi-why-dont-start-searching-for-all-errors-from-one-place
/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions
http://help.sap.com/saphelp_nw2004s/helpdata/en/0d/28e1c20a9d374cbb71875c5f89093b/frameset.htm
Just try with Visual Administrator to check the services for the adapter engine are running or not
All services starts with SAP XI..
SAP XI AF Core
SAP XI AF CPA Cache
SAP XI AF Messaging
SAP XI Adapter XI
SAP XI AF Security
Check SAP note on CPACache- 741214 and also 824236.
Let me know if any errors..
Cheers..
Vasu
** Reward Points if found useful **

Message split on adapter engine for the java based IDoc adapter

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

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

PI 7.11 - Configuration: Adapter Engines Not found

Hi,
We have a PI 7.11 System that is connected to a central SLD. There are also two PI 7.0 systems connected to this SLD. If i open a communicationChannel i get following message:
Adapter Engines Not foundNo SLD elements of type SAP_XIAdapterFramework found
If i look in the SLD Technical Systems (Exchange Infrastructure), i see the three PI systems but only the Adapter Engines of the two PI 7.0 systems.
How can i check if the adapter engine is up and running and if it has correctly been registered by my SLD. Are there any documentation according this configuration?
Thanks in advance

It seems adapter engine is not registered properly. For more details, please refer to the following sap notes:
1. [Note 764176 - Error in XI due to inconsistent SLD contents|https://service.sap.com/sap/support/notes/764176]
2. [Note 1117249 - Incomplete Registration of PI components in SLD|https://service.sap.com/sap/support/notes/1117249]
3. [Note 1292803 - Configuration Wizard: PI SLD Self Registration|https://service.sap.com/sap/support/notes/1292803] .
Regards,
Sunil Chandra

Installation and then Configuration of Plain J2se Adapter Engine

Hi All,
Actually we want to use JMS Adapter for that we had installed Plain J2SE Adapter Engine but after installing and following the initial steps of Adapter.pdf we are not able to access the Adapter Engine through URL.We are using the URL http://<hostname>:8200/MessagingSystem/receive/AFW/XI
this URL is there in our SLD but we are not able to access the page.
So Please can somebody help me to resolve this issue.
Thanks & Regards
Sathya

Hi Amol,
I am trying to send read data from MQSeries using JMS adapter. We are successful in opening the Adapter Engine and the GUI. We have cofigured the adpter as follows. But when we try to restart the adapter to get the changes get saved we are getting the following error
"ERROR CALLING THE RESTART ADAPTER"
Also status is shown is yellow and version is shown as not set.
Where ever I have changed the configuration data I have shown it in bold
JMS-Adapter Configurarion
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.
#XI.SenderParty=Sender
XI.SenderService=MQSeries
#XI.ReceiverParty=Receiver
XI.ReceiverService=MTX
XI.InterfaceNamespace=http://xitest
XI.Interface=MI_Out_File
XI.TraceLevel=1
XI.LoggingLevel=1
XI.QualityOfService=EO
XI.QueueId=ABCD
XI.ContentType=text/xml
# *************************************************************************************************************
#
URL of XI IS to send the messages to
XI.TargetURL=http://bwxi:50000/sap/xi/engine?type=entry
XI.User=XIAF
XI.Password=XIPASS
# *************************************************************************************************************
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=xisuper
JMS.QueueConnectionFactoryImpl.password=xxx
#
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 JAVA.CHANNEL
JMS.QueueConnectionFactoryImpl.method.setTransportType=java.lang.Integer {com.ibm.mq.jms.JMSC.MQJMS_TP_CLIENT_MQ_TCPIP}
JMS.QueueConnectionFactoryImpl.method.setQueueManager=java.lang.String QM_BWXI
JMS.QueueImpl.classname= com.ibm.mq.jms.MQQueue
JMS.QueueImpl.constructor=java.lang.String postcard
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
Can you please help me in resolving the error.
Regards,

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

Alerts in the Adapter engine

Hi all
I´m working in a BPM scenario, I have raised an alert from the BPM and it arrives to my inbox(alert framework). And also i can see it in the CCMS. But now I trying to configure an alert to be raised in case of an error in the Adapter engine (file adapter). I´m on sp15 and i have create a alert categorie and an alert rule setting this with the value Adapter engine and the adapter type File.
I have checked the alert with "RSALERTTEST" and it works fine it arrive to my alert inbox and to the ccms. But i have an error in the file adapter and is not arriving anything. The communication channel is a Sender. There is some thing missing in my configuration?
Any help please?
Regards
Noelia

Here are my hints:
1) http://help.sap.com
Alert Notification Step-by-Step
http://help.sap.com/saphelp_nw04/helpdata/en/49/cbfb40f17af66fe10000000a1550b0/frameset.htm
Alert Configuration
http://help.sap.com/saphelp_nw04/helpdata/en/80/942f3ffed33d67e10000000a114084/content.htm
2) Michal's blog: XI FAQ
/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions
XI: Alerts - Troubleshooting guide
/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--troubleshooting-guide
XI: Alerts - Step by step
/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--step-by-step
3) Notes:
750287 XI 3.0 Runtime Workbench: Alert configuration does not start
768456 Troubleshooting Runtime Workbench XI 3.0
813703 XI RWB alert configuration is incompletely displayed
840849 XI 3.0 Runtime Workbench: SSO2 is not active in this system
824039 XI30 Runtime Workbench: Display of XI alerts in CCMS
0000906044 XI30 Alerting: Wrong hostanme in the URL of the XI Alert
0000905896 XI30 Alerting: Message without recipient creates no alert
0000904825 Synchronous message processing: Error in CCMS connection
0000902022 XI30 Alertrule insensitive to Receiver Interface
0000882215 XI 3.0 Runtime Wkbnch: Java Adaptr does not generate alerts
0000876546 XI 3.0 Runtime Workbench: Missing alerts
0000870232 XI 3.0 Runtime Workbench: New Alerting functionality
But start with this one:
913858 XI3.0 Alerting: Troubleshooting
4) User roles
SAP_ALM_CUSTOMIZER -- Alert Management: Role for Customizing
SAP_ALM_ADMINISTRATOR -- Alert Management Administrator
SAP_BC_ALM_ALERT_USER -- ALM: Role for the alert user
SAP_BC_ALM_ADMIN
SAP_BC_ALM_CUST
SAP_XI_RWB_SERV_USER
SAP_XI_RWB_SERV_USER_MAIN
Regards,
Sandro

Decentralised Adapter Engine Configuration

hi all,
I have already installed DAE for a XI server.
Right now i am able to see it in RWB.But it is not visible in Adapter engine dropdown of communication channel.
I wanted to know whether some settings in visual admin of XI server also has to be done.
regards,
ujjwal kumar

Hi Ujjwal,
Please ignore my previous post and follow this as i would like to add to it:
The non-central Adapter Engine provides a configuration option called Java Proxy mode (JPR mode). In this mode, the adapter registration in the SLD is disabled so that the underlying system becomes a plain Java proxy application system (just like an ABAP system with ABAP proxies). The collaboration partner agreement (CPA) service no longer reads the CPA cache data from the Integration Directory.
In this case, you can use a service property to configure the user for sending messages to the Integration Server (outbound scenario). The Integration Server uses an access control list (ACL) to check receiving messages based on this configuration setting (see SAP Note 852237). The ACL check is always skipped when the Adapter Framework service user (usually PIAFUSER) is used for sending.
To switch the Adapter Engine to JPR mode, perform the following configuration settings:
       1.      In the Visual Administrator, choose the SAP XI AF CPA Cache service and set the SLDAccess property to false.
       2.      Save your settings and restart the service.
       3.      Make sure that the cacheType property still has the value DIRECTORY.
       4.      In the Visual Administrator, choose the SAP XI Adapter: XI service and set the respective values (user, password, Integration Server URL, client, and language) for the properties xiadapter.isconfig.*.
       5.      On the Integration Server, call transaction SMICM to ensure that you have maintained the correct Integration Server URL.
       6.      On the Integration Server, call transaction SU01 to create the new user and assign it the role SAP_XI_AF_SERV_USER_MAIN. You can copy PIAFUSER for this purpose.
If a password change is required, log on to the Integration Server with the new user and change the initial password. Otherwise the communication will fail.
       7.      In the Visual Administrator, check if the ABAP-Java user synchronization was successful.
       8.      Log on to the SLD and choose Content Maintenance ® XI Adapter Framework.
       9.      Select your non-central Adapter Engine and remove it.
Also refer:
http://help.sap.com/saphelp_nw2004s/helpdata/en/3e/e3fb40f17af66fe10000000a1550b0/content.htm
After you are done with your installations there are some verifications that needs to be done at the visual admin side before monitoring your Decentral Adapter engine:
1)Start the J2EE from SAP management console and start the J2EE
(If you have dynamic IP address, then hosts file in server should be changed before starting decentral AE)
2)Start Visual Administrator & login to your Default connection
3)Navigate to Services à SLD Data Supplier and
verify the SLD connection
4)Navigate to Services à Security Provider and verify the users (its synchronized with the XI Server)
Now check in RWB -> Component Monitoring -> Non-central AE
Also refer page 25-29 of the following pdf:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/events/webinars-nw-rig/configuring%20a%20local%20adapter%20engine%20to%20work%20with%20a%20central%20instance%20-%20webinar%20powerpoint.pdf
Hope this helps.
Regards,
Shibani
*Ps reward with points if helpful*

No values in the dropdown for Adapter Engine

Hello Colleague,
While configuring a sender adapter engine in the integration directory, there are no value displayed when we select an Adapter and do a dropdown on the "Adapter Engine" Field.
Could you pls. help.
Regards,
Gajendra.

Hi Gajendra,
Have you imported the SAP_BASIS content into yor repository?? If not do that.
Also you can go through the below thread
No Adpater Engine available in Communication Channel creation
Regards
Sunita

Whats the Advanced Adapter Engine ?

What is Advanced Adapter Engine and how its different from normal adapter engine

HI Prathna
You use the Advanced Adapter Engine to connect the Integration Engine to SAP systems (RFC adapter) and non-SAP systems. You use the various adapters in the Adapter Engine to convert XML- and HTTP-based messages to the specific protocol and format required by these systems, and the other way around.
Using Integrated Configuration you can define a local Message Processing on the Advanced Adapter Engine. The Advanced Adapter Engine provides mapping and routing for this locally. Message Processing is only executed on the Advanced Adapter Engine from one adapter to another without the involvement of the Integration Engine. You can gain a great improvement in performance.
You can implement all adapters on the Adapter Engine for a local Message Processing on the Advanced Adapter Engine, apart from the RNIF adapters and the CIDX adapters.
If you do not use Integrated Configuration, Message Processing will always be performed by the Integration Engine to execute the routing and mapping there.
The Advanced Adapter Engine is a separate software component that is automatically installed on the Integration Server. In this case, it is the central Advanced Adapter Engine. However, you can also install the Advanced Adapter Engine separately on another host. This is then a non-central Advanced Adapter Engine.
cheers
Abhishek

"Performance" problems with the File adapter on Plain J2SE Adapter Engine

Hi,
At the moment I'm on a customer side to solve some XI issues for a few days. One of the issues is the performance of the Plain J2SE Adapter Engine, using the file adapter to transfer XML messages(already XI message format) from the legacy system to the Integration Engine. The File adapter has to deal with "large" XML messages(max at the moment is 65 Mb) and the engine fails with the following error when transferring the big XML file: "ERROR: Finished sending to Integration Engine with error "java.lang.OutOfMemoryError". Skip confirmation and quit this loop".
As far I got the information from the customer the memory use of the Plain adapter engine is set to 512Mb. This is maybe to low. But I don't know where to look for this, I only have the adapter web interface in front of me, no access to the OS it self via for example remote connection.
On the Integration Engine I know there is the ability to split large message with the file adapter(File Content Conversion), but I don't know this for the Plain Adapter Engine. Is there a possibility to do this also on the Plain Adapter Engine?
Thanks in advance for any input.
Greetings,
Patrick

Hi Sameer,
Thanks for your answers.
On the first solution, yes that is possible, we first decided to see if the legacy system can do the splitting, before starting developing a Java program.
On the second solution, as far as I know is this solution possible on the Integration Engine. But we are facing the problems on the Plain J2SE Adapter Engine. I went trough that documentation(link:
http://help.sap.com/saphelp_nw04/helpdata/en/6f/246b3de666930fe10000000a114084/frameset.htm ), to look for I similiar solution in the Plain Adapter Engine. So my question is, is this possible with the Plain Adapter? And if so, what kind of parameters I need to use to achieve this.
Regards,
Patrick

Messages are in To be delivered state in the Adapter engine

Hi,
For all the receiver file adapters the messages are successful processed through Integration Engine ,no messages are stuck in SMQ1 & SMQ2 on Inegration engine.
All the messages are stuck in Adapter Engine with the status "To be Delivered ". These are all asynchorus scenarios. The quality of service is also EO.
We restarted the J2EE engine also several times but no luck.
Did anyone had similar issue?
Thanks
Sachin

Hi,
Status: TO_BE_DELIVERED
Which means that the message was successfully delivered from Integration Server point of view and it states that the messages is initially handed over to the Messaging System.
TO_BE_DELIVERED occurs while the message is put into the Messaging System receive queue.
Solution:
This is done via the Messaging System receive servlet:
http://<Host>:<PORT>/MessagingSystem/receive/<CONNECTION>
/<PROTOCOL>
Only if this was executed successfully the Messaging System returns HTTP 200 to the Integration Server and the Status TO_BE_DELIVERED moves to DELIVERING
Try logging into Sap GUI with two users: XIAPPLUSER & XIAFUSER
to see if they are blocked
We can check the messages:
AdapterFramework
com.sap.aii.adapterframework.serviceuser.language
com.sap.aii.adapterframework.serviceuser.name = XIAFUSER
com.sap.aii.adapterframework.serviceuser.pwd
ApplicationSystem
com.sap.aii.applicationsystem.serviceuser.language
com.sap.aii.applicationsystem.serviceuser.name = XIAPPLUSER
com.sap.aii.applicationsystem.serviceuser.pwd
in the exchange profile to make sure the right passwords and tcode - SXMB_ADM and "active" the queue then the messages and check it out.
Regards
Agasthuri Doss

Error while reading access data (URL, user,password) for the Adapter Engine

Hi,
Any idea on below message? I am doing file to file scenario and got the below tarce from sxmb_moni.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">AE_DETAILS_GET_ERROR</SAP:Code>
<SAP:P1>af.pi1.piserver1</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>no_messaging_url_found: Unable to find URL for Adapter Engine af.pi1.piserver1</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error while reading access data (URL, user, password) for the Adapter Engine af.pi1.piserver1</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Thanks
Balaji

It looks like the adapter engine is not able to register him self on SLD, you have to check in the SLD the "Exchange Infrastructure" domain, you have to verify restarting the J2EE the adapter engine update the entries in the SLD related to the specific XI Domain.
Launch Visual Administrator >> Server >> Services >> SAP AF CPA Cache
Enter the appropriate values for:
SLD.selfregistration.hostname (Use fully qualified hostname)
SLD.selfregistration.httpPort
SLD.selfregistration.httpsPort
Sandro

No Adapter Engine in the Configuration

Similar Messages

Maybe you are looking for