Adapter engine is null

Dear All,
I am facing the following problem with Adapter engine.
No correct URL exists for the RuntimeCheck. Enter a correct URL in the System Landscape Directory .
I have checked the pipeline URL and it is : http://172.17.61.41:8003/sap/xi/engine?type=entry.
I have 2 instances on the same server. XID and XIQ. IN XID i can see the adapter engine but in XIQ it shows as null.
Vinay

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/ac6de690-0201-0010-54ac-8923089dcc97 - configuration guide
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/bd5950ff-0701-0010-a5bc-86d45fd52283 - troubleshooting guide

Similar Messages

Adapter Engine null

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

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

Null Pointer Exception in Plain J2SE Adapter Engine

Hi All,
I am able to start the J2SE Adapter Engine. But when ever i click any button on my JMS Adapter i am getting
Error stopping adapter: java.lang.NullPointerException
Error terminating adapter: java.lang.NullPointerException
Can somebody guide me why this error is comming or the possible reasons for the error.
Thanks in Advance.
rahul

Hi Rahul,
Please can you go through the thread
J2SE Adapter Engine / JMS Adapter
It does not talk about the error but the config need to be done for JMS. Hope this helps.
Regards
Vijaya

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

Adapter engine messaging URL returns HTTP 403

Hi all,
I currently have a problem with the following scenario: SOAP Adapter -> XI -> JDBC Adapter. I have configured the scenario and everything seems to be running correctly (in the component monitoring the adapters and the integration engine are green). However when I send a request to the SOAP Adapter I get the following response:
<s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
 <context>XIAdapter</context>
 <code>DeliveryException</code>
 <text><![CDATA[
com.sap.aii.af.mp.module.ModuleException
 at
Caused by: com.sap.aii.messaging.srt.BubbleException: failed to call the adapter engine [null "null"]; nested exception caused by: com.sap.aii.af.ra.ms.api.DeliveryException: Received HTTP response code 403.
</text>
</s:SystemError>
In the Message Display tool of the runtime workbench I get the following trace:
2005-06-05 11:03:08 Success SOAP: request message leaving the adapter (call)
2005-06-05 11:03:08 Success Application attempting to send an XI message synchronously using connection AFW.
2005-06-05 11:03:08 Success Trying to put the message into the call queue.
2005-06-05 11:03:08 Success The message was successfully retrieved from the call queue.
2005-06-05 11:03:08 Success The message status set to DLNG.
2005-06-05 11:03:08 Success Message successfully put into the queue.
2005-06-05 11:03:08 Error Returning synchronous error notification to calling application: Received HTTP response code 403..
2005-06-05 11:03:08 Error Transmitting the message using connection http://<host>:8000/sap/xi/engine?type=entry failed, due to: Received HTTP response code 403..
2005-06-05 11:03:08 Error The message status set to FAIL.
2005-06-05 11:03:08 Error Returning to application. Exception: Received HTTP response code 403.
So it seem that somehow the adapter framework is not allowed to send a message to the integration engine via the messaging URL.
Any ideas how to resolve this problem?
Thanks for you help,
Christian

Hi,
If you've changed the passwords for XI service users
then you may also want to check this note: 721548
XI 3.0: Changing the passwords of the XI service users
Regards,
michal

SOAP adapter engine with system error, problem with fault message.

HI,
I have IDOC -> PI -> SOAP scenario.
Idoc to PI is async. I have no problem in receiving the idoc in PI. The message mapping is carried out and sent to the adapter engine. I can also see the technical routing payload. It is sucessful at XML monitoring in SXMB_MONI.
The error is at PI -> SOAP.
I have wsdl provided by the receiver webservice. Which I have imported.
And created a service interface against this wsdl. I tried changing it to both sync and async.
I have also provided fault message.
I have set a receiver soap communication channel and provided the target URL like "http://xxx/services" and soap
action = processDocument. Also provided user id and password.
I have a
Sender Agreement
Receiver determination
Interface determination
Receiver Agreement
I check in RWB adapter engine, this message goes to system error. The error log is as shown at the bottom.
When I see the message content, the SOap document shows me the details about IDOC, Instead I feel it should match
with the wsdl, where they have specified the corresponding interface name and address location etc.Please correct me.
How does the receiver know which service interface is it? The Service Interface which I created in the ER is
different from the WSDL, Does this have to be same? I see that the soap document in the adapter engine has the
Service interface name which I created in the ER. Where in the document the Reciever interface name is sent?
Where can I see the generated soap document for the receiver?
Is there some setting/configuration required in PI for this to work?
I tried using the tcpgw to see the error. If I dont provide the service interface name in the communication channel
then I get the following error in the TCPGW. "The service cannot be found for the endpoint reference"
When I provide the service interface name in the communication channel I get a valid fault message.
Similarly
When I use SOAPUI, I can see the fault exception being return. The adapter engine doesnot show an equivalent message
instead it goes into system error as shown at the bottom. I guess this is expected, if so what is the work around? (I found this weblog /people/alessandro.guarneri/blog/2011/01/10/soap-fault-in-sap-pi-hijack-it, do I need to implement this? Or use ALEAUD?
The fault message what I see in SOAPUI has the below format.
<soapenv:Fault xmlns:axis2ns1="http://schemas.xmlsoap.org/soap/envelope/">
 <faultcode>axis2ns1:Server</faultcode>
 <faultstring>nested exception is: psdi.util.MXApplicationException: BMXAA7136E - Validation failed when the
 database default values were set. See the associated message for more information.
 BMXAA4190E - Country NZ is not in the value list.</faultstring>
 <detail>
 <Exception>org.apache.axis2.AxisFault: nested exception is: psdi.util.MXApplicationException: BMXAA7136E
 - Validation failed when the database default values were set. See the associated message for more information.
 BMXAA4190E - Country NZ is not in the value list.
 /Exception>
 </detail>
</soapenv:Fault>
And the fault message in my ER service interface is stanadard datatype ExchangeFaultData, which is different from
the above. Is this the problem? Can I change the data type here to be the same as above?
Audit log in the RWB adapter engine.
Time Stamp Type Description
30.09.2011 15:10:57 Information MP: processing local module Localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
30.09.2011 15:10:57 Information SOAP: request message entering the adapter with user J2EE_GUEST
30.09.2011 15:10:57 Information SOAP: completed the processing
30.09.2011 15:10:57 Information SOAP: sending a delivery error ack ...
30.09.2011 15:10:57 Information SOAP: sent a delivery error ack
30.09.2011 15:10:57 Error MP: exception caught with cause
com.sap.engine.interfaces.messaging.api.exception.MessagingException
30.09.2011 15:10:57 Error Adapter Framework caught exception: null
30.09.2011 15:10:57 Error Delivering the message to the application using connection
SOAP_http://sap.com/xi/XI/System failed, due to:
com.sap.engine.interfaces.messaging.api.exception.MessagingException.
30.09.2011 15:10:57 Information The message status was set to WAIT.
30.09.2011 15:10:57 Information The asynchronous message was successfully scheduled to be delivered at Fri Sep 30
15:15:57 NZDT 2011.

I tried changing it to both sync and async.
I have also provided fault message.
dont feel that you need to do above steps.
I have a
Sender Agreement
ideally you dont need a sender agreement (and a channel) for IDOC --> PI flow.
When I see the message content, the SOap document shows me the details about IDOC
this is fine...you may see fields as seen in EDI_DC40 of the IDOC...
How does the receiver know which service interface is it?
receiver need not know about the SI created in PI.
The Service Interface which I created in the ER is
different from the WSDL, Does this have to be same?
you should the WSDL (external definition) as the Request Message in your service interface.
Is there some setting/configuration required in PI for this to work?
nothing specific...AFAIK
I have set a receiver soap communication channel and provided the target URL like "http://xxx/services" and soap action
can you open the URL from Internet explorer...from your machine or from the machine which is in the same network as your PI server?
Things to check:
WSDL structure in PI and in target system is exactly the same.
does the target system require mesage in SOAP format (SOAP envelope - SOAP Header + SOAP body)?
target system is up and running?

Decentralized Adapter Engine working

Hi guys,
I have installed a decentralized adapter engine for my XI Server. I have a scenario which i run with default Adapter Engine(Integration Server), runs fine.
However, when i run it with choosing Decentralized AE it gives such errors in
Message Monitoring:
Exception caught by adapter framework: null
Delivery of the message to the application using connection AFW failed, due to: RecoverableException.
Also i am testing this for two simple file2file scenarios. It's acting differently; in a scenario sender commn channel picks file, in other not.
Is there any configuration settings that's remaining? Or something else?
Regards
Arpil

Hi,
For the picked message, i see this in moni....
<Trace level="1" type="T">--start sender interface action determination</Trace>
<Trace level="1" type="T">select interface MI_XmlFile_out*</Trace>
<Trace level="1" type="T">select interface namespace urn:Plain2XML</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--start receiver interface action determination</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface *</Trace>
<Trace level="1" type="T">select interface namespace</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
<Trace level="1" type="T">Hence set action to DEL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
Any clue?
Regards
Arpil

Cannot resend messages in adapter engine

Hi all,
I encountered thousand messages in adapter engine yesterday with error category: XI_J2EE_ADAPTER_ENGINE, error code: JMS_TRANSMISSION_ERROR.
First I checked the affected communication channel, and there was an error in MQ side. Also, our database crashed. But these issues were resolved already. Then I tried to resend the messages, but still it ended up in system error. As I looked in the log,
MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: Connector for ConnectionProfile of channel: JMS_--_Receiveron node: -having object id: - encountered error: MQJMS2007: failed to send message to MQ queue in sending to destination queue:///?targetClient=1, the message message: JMS Message class: jms_text JMSType: null JMSDeliveryMode: 2 JMSExpiration: 0 JMSPriority: 4 JMSMessageID: null JMSTimestamp: 1193614619284 JMSCorrelationID:--
Exception caught by adapter framework: Connector for ConnectionProfile of channel: JMS_----
MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: Pending message discovered: -
.The channel is configured throw an recoverable, temporary error for this warning (default). Decide whether you want to bypass this message. If so, set the Pending Handling channel parameter to 'Bypass' and restart the message afterwards.
Exception caught by adapter framework: Pending message discovered: -
.The channel is configured throw an recoverable, temporary error for this warning (default). Decide whether you want to bypass this message. If so, set the Pending Handling channel parameter to 'Bypass' and restart the message afterwards.
Every time I tried to resend the message, it ended up in error stated above. But there are successful messages today which means that the communication channel is working fine.
How can I resend the messages stucked in the adapter engine? Hope someone can help me.
Thanks a lot in advance.

May be when u tried to send the message some of the message got stuck in AE due to some Error.
As I no the message can stuck in AE when....Target Systems is down, Test data is not valid for receiver..then few of the messages goes in System Error and later message come in waiting/Holding/To be Delieverd state...
Check all the messages that has in System Error status...
Thanks
Farooq.

Soap LookupService with Decentralized Adapter Engine

Hi Experts,
I would like to use a Decentralized adapter engine with the Lookup Service on PI 7.1 , but when try to use that, it doesn't work, because Lookup Service is default configure to use Central adapter only. I would like how to set a decentralize adapter.
How to do a Soap Lookup using a Decentral adapter?
Now, I use the following:
Channel channel = LookupService.getChannel("BC_SF_***","CC**");
SystemAccessor accessor = null;
accessor = LookupService.getSystemAccessor(channel);
Thanks in advance.
Fernando Pena.

You define in the communication channel, which adapter engine should be used, not in the mapping.

Adapter engine missing in Qa

Hi all,
After transporting objects from Dev to Qa we are experiencing some problems:
1: in the "Component Moinitoring" of the RWB "Adapter Engine" is listed twice (under Integration Server).
2: In the communication channels the the drop down selection box where you choose "Adapter Engine" is empty.
3: The communication channels are not taking in data.
Please advice, Thanks

Hi all,
After removing and re-registering the Adapter Engine only one engine shows in technical systems in the SLD (instaed of two). - Thants good
But now i have an entry called "Domain Null" (type XI Domain).
What does this mean, and will this cause problems?
Thanks

Developing User Enhancement Modules in Adapter Engine Teched07 attender?

Hi,
I am looking for the Java code of one of the hands on curses in the SAP Teched07.
The course was a XI/PI, Developing User Enhancement Modules in the Adapter Engine, and I need the Java code of the Java Bean that was used.
The name of the file is GetHostNameXXBean
If someone can help me i would appreciate it.
Thanks in advance.
Eduardo

[code]package com.teched06.usermodule;
// Classes for EJB
import javax.ejb.CreateException;
import javax.ejb.SessionBean;
import javax.ejb.SessionContext;
// Classes for Module development & Trace
import com.sap.aii.af.mp.module.Module;
import com.sap.aii.af.mp.module.ModuleContext;
import com.sap.aii.af.mp.module.ModuleData;
import com.sap.aii.af.mp.module.ModuleException;
import com.sap.aii.af.ra.ms.api.Message;
import com.sap.aii.af.ra.ms.api.MessageDirection;
import com.sap.aii.af.service.trace.Trace;
// XML parsing and transformation classes
import javax.xml.parsers.*;
import org.w3c.dom.*;
import java.io.InputStream;
import java.io.ByteArrayOutputStream;
import java.net.InetAddress;
import java.net.UnknownHostException;
import com.sap.aii.af.ra.ms.api.XMLPayload;
import javax.xml.transform.*;
import javax.xml.transform.Source;
import javax.xml.transform.Result;
import javax.xml.transform.dom.DOMSource;
import javax.xml.transform.stream.StreamResult;
import com.sap.aii.af.service.auditlog.*;
@ejbHome <{com.sap.aii.af.mp.module.ModuleHome}>
@ejbLocal <{com.sap.aii.af.mp.module.ModuleLocal}>
@ejbLocalHome <{com.sap.aii.af.mp.module.ModuleLocalHome}>
@ejbRemote <{com.sap.aii.af.mp.module.ModuleRemote}>
@stateless
public class GetHostName implements SessionBean, Module {
 public static final String VERSION_ID = "$Id://tc/aii/30_REL/src/_adapters/_sample/java/user/module/GetHostName.java#1 $";
 private static final Trace TRACE = new Trace(VERSION_ID);
 private SessionContext myContext;
 public void ejbRemove() {
 public void ejbActivate() {
 public void ejbPassivate() {
 public void setSessionContext(SessionContext context) {
 myContext = context;
 public void ejbCreate() throws CreateException {
 public ModuleData process(ModuleContext moduleContext, ModuleData inputModuleData) throws ModuleException {
 String SIGNATURE = "process(ModuleContext moduleContext, ModuleData inputModuleData)";
 Object obj = null;
 Message msg = null;
 String hostName = getHostName();
 AuditMessageKey amk = null;
 try {
 obj = inputModuleData.getPrincipalData();
 msg = (Message) obj;
 if (msg.getMessageDirection().equals(MessageDirection.OUTBOUND))
 amk = new AuditMessageKey(msg.getMessageId(), AuditDirection.OUTBOUND);
 else
 amk = new AuditMessageKey(msg.getMessageId(), AuditDirection.INBOUND);
 Audit.addAuditLogEntry(amk, AuditLogStatus.SUCCESS, "GetHostName: Module called");
 catch (Exception e) {
 ModuleException me = new ModuleException(e);
 throw me;
 // Read the channel ID, channel and the module configuration
 String hostElementName = null;
 try {
 // CS_GETMODDAT START
 hostElementName = (String) moduleContext.getContextData("HostElementName");
 // CS_GETMODDAT END
 if (hostElementName == null) {
 TRACE.debugT(SIGNATURE, "HostElementName parameter is not set. Default used: HostName.");
 Audit.addAuditLogEntry(amk, AuditLogStatus.WARNING, "HostElementName parameter is not set. Default used: HostName.");
 hostElementName = "HostName";
 TRACE.debugT(SIGNATURE, "HostElementName is set to ", new Object[] );
 Audit.addAuditLogEntry(amk, AuditLogStatus.SUCCESS, "HostElementName is set to ", new Object[] );
 } catch (Exception e) {
 TRACE.catching(SIGNATURE, e);
 TRACE.errorT(SIGNATURE, "Cannot read the module context and configuration data");
 Audit.addAuditLogEntry(amk, AuditLogStatus.ERROR, "Cannot read the module context and configuration data");
 ModuleException me = new ModuleException(e);
 TRACE.throwing(SIGNATURE, me);
 throw me;
 try {
 XMLPayload xmlpayload = msg.getDocument();
 DocumentBuilderFactory factory;
 factory = DocumentBuilderFactory.newInstance();
 DocumentBuilder builder = factory.newDocumentBuilder();
 Document document = builder.parse((InputStream)
 xmlpayload.getInputStream());
 Element rootNode = document.getDocumentElement();
 if(rootNode != null) {
 Element childElement =
 document.createElement(hostElementName);
 childElement.appendChild(document.createTextNode(hostName));
 rootNode.appendChild(childElement);
 // Transforming the DOM object to Stream object.
 TransformerFactory tfactory = TransformerFactory.newInstance();
 Transformer transformer = tfactory.newTransformer();
 Source src = new DOMSource(document);
 ByteArrayOutputStream myBytes = new
 ByteArrayOutputStream();
 Result dest = new StreamResult(myBytes);
 transformer.transform(src,dest);
 byte[] docContent = myBytes.toByteArray();
 if(docContent != null) {
 xmlpayload.setContent(docContent);
 inputModuleData.setPrincipalData(msg);
 catch (Exception e) {
 ModuleException me = new ModuleException(e);
 throw me;
 return inputModuleData;
 private static String getHostName() {
 String host = "unknown";
 try {
 InetAddress inet = InetAddress.getLocalHost();
 host = inet.getHostName().toLowerCase();
 int i = host.indexOf(".");
 if (i > 0) {
 host = host.substring(0, i);
 catch (UnknownHostException e) {
 host = "error";
 return host;
[/code]

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.

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

Adapter engine e Monitor de serviço da SEFAZ NFE 4.0 OFF

Sap Gears! Estou com um problema depois da atualização para NFE 4.0
Antes da atualização, o monitor de status estava ok
Foi feito atualização dos SPK, TPZ files no XI, Atualização JSPM (JAVA)
Também foi atualizado o APP do NFE e aplicado as notas correspondente ao SPK 16 (ainda não disponível )
Algum santo aqui teria um rumo pra eu seguir?
Agradeço ai pessoal!!!
<< Elabore melhor a questão e dê detalhes que sejam suficientes para entendermos o problema >>
Editado pela Moderação: Fernando Ros on Sep 29, 2010 5:36 PM
Veja Regras de Comportamento item 2

Raphael,
Quando você diz "Monitor de serviço da SEFAZ" você quer dizer o monitor do GRC (http://:80/sap/bc/webdynpro/xnfe/nfe_main)? Se sim, quando você tenta acessar, ocorre um erro?
Se sim, verifique na transação SICF se os servicos do nó default_host -> sap -> bc -> webdynpro (e seus sub-nós) estão ativos.
Quando você diz Adapter Engine, significa que, ao entrar no RWB, Component Monitoring, o Status dele aparece como vermelho, indicando no "Self-test" que o item "Is the Adapter Engine running?" está vermelho?
Se sim, dê uma olhada no defaultTrace em busca de erros.
BTW, poste mais detalhes dos problemas para que fique mais claro onde é o problema.
[]'s

Guide for J2EE Adapter Engine on WAS 6.40 with XI 3.0

Hi all,
we are currently struggling with our AE. We are going to migrate from Xi 2.0 to XI 3.0, we run into problems while configuring our old J2SE AE (for which I have found a good PDF document on the SAP Service Marketplace).
Now we would like to test/configure the J2EE AE on XI 3.0.
But I cant find any guide for this on the SAP Service Marketplace. Does anyone know where to find this?
Thanks
Nesimi Buelbuel

Hi Nesimi,
There is a webinar replay of "Troubleshooting the J2EE Adapter Engine" at
https://www.sdn.sap.com/sdn/webinar.sdn?res=/irj/servlet/prt/portal/prtroot/com.sap.sdn.wcm.compound.docs//library/uuid/47a9a361-0301-0010-d39a-dd40d34b2e9d
Also make sure you check these links:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/events/webinars/configuring a local adapter engine.pdf
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/3.0/configuration guide - sap xi 3.0.pdf
Regards,
Sridhar

Adapter engine is null

Similar Messages

Maybe you are looking for