Local Adapter Engine

[Former Member]

Hi All,

Here we installed Local AE on both Sender and Receiver Systems but stuckup with configuring these Adapters.

Step1:How to configure the SLD part if am working with Local AE's?

Step2:How can XI recognize these Local AE's?

Step3:In the Communication channels while defining the File Adapters,At the Adapter Engines option i have to choose Local AE instead of Integration Server.To get(display) this option (Local adapters) what all the connections are configurations need to be done at XI and Sender/Receiver?

Any suggestions??

Thanks,

Kalyan.

[Former Member]

answered

[deidre_logan]

We have an SAP XI installation that is starting to have issues staying up with the number of JMS messages we are processing.

We would like to bring up a decentral adapter engine to handle some of the load.

In the documentation it says you need to have a stand alone J2EE engine. This requires a database... is there a way to use the Central adapter engine database? Or do I need a whole use system id and system number?

Is there a way to use an existing Java server?

Just trying to understand how to get this going....

thanks,

Deidre Logan

[Former Member]

Hi,

Please go through thhes links to install and configure the J2EE adapter engine

http://saptechnical.com/Tutorials/XI/J2EEAdapterEngine/Part1.htm

http://saptechnical.com/Tutorials/XI/J2EEAdapterEngine/Part2.htm

Thanks,

Kalyan.

[Former Member]

hi kalyan

The local adapter engine is installed on any system that will run on WAS and while creating the Adapter in the Integration Directory select the adapter engine from your central or local adapter engine

check this webinar presentation on

Configuring a LocalAdapter Engine to Work with a Central Instance

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/03fd85cc-0201-0010-8ca4-a32a119a...

<removed by moderator>

regards

kummari

Edited by: Mike Pokraka on Jul 24, 2008 12:59 PM

[Former Member]

Hi Kummari,

Thanks for your valuable suggestion.

Here I am having one more doubt.The thing is when we select that Local AE for Adapter Engine in communication channel.It will ask to give the same parameters lets Directory Name,File Name ,Processing Mode etc which we will get when our Adapter Engine is set as Integration Server.

Or

We have to mention all these parameters lets say Directory Name,File Name and etc in Local Adapter Engine itself?

Thanks,

Kalyan.

[Former Member]

hi,

In the Integration Directory select the adapter engine from your central or local adapter engine ,accordingly specify the parameters

regards

kummari

[prateek]

The communication channel will show the same fields like Directory Name,File Name ,Processing Mode etc in both Integration Server or local adapter engine.

We have to mention all these parameters lets say Directory Name,File Name and etc in Local Adapter Engine itself?

No

The use of local adapter engine only ensures the server on which the processing takes palce. The configuration steps in ID always remains same.

Regards,

Prateek

[Former Member]

Hi Kummari,

Thanks for ur reply.

I am Sorry to ask the doubts again and again.

Is the Plain J2SE Adapter Engine is a Local Adapter Engine?

If we have install the Plain J2SE Adapter Engine on both Sender/Receiver,Do we need to follow the same steps as u mentioned earlier or is there any changes?

How can XI communicate with this Plain J2SE adapter engine?

what all the configuration steps need to be done?

Thanks,

Kalyan.

[Former Member]

Hi,

J2SE Adapter Engine is not a non Central AE.

While configuring scenarios with J2SE adapter Enigine...

You need to configure Sender File Adapter at J2SE side and a Sender XI adapter at XI end to get the data fro J2SE file adapter.

Follow the link for getting an insight on how to configure J2SE adapters

http://help.sap.com/saphelp_nw04/helpdata/en/6f/246b3de666930fe10000000a114084/frameset.htm

Regards

Shailesh

[Former Member]

Hi Sailesh,

If suppose my receievr is also installed with Plain J2SE adapter for that which communication channel shud i use in Configuration part.

Please suggest me regarding this.

Thanks,

Kalyan.

[Former Member]

HI Kalyan,

The Plain J2SE Adapter Engine is one of the PI messaging components responsible for message processing and protocol handling. This type of adapter engine was already available with XI 2.0 and merely requires a Java Virtual Machine to run. It can be used as a non-central adapter engine, but it hosts only a subset of the adapter functions and does not support standard security features such as security logs or integrated user management

The Plain J2SE Adapter Engine does not access the exchange profile, because the connection data is kept locally. It does, however, register itself in the System Landscape Directory (SLD).

for

Technical Communication

http://help.sap.com/saphelp_nw04s/helpdata/en/5e/f85141196ff423e10000000a155106/frameset.htm

Adapters Running in the Plain J2SE Adapter Engine

http://help.sap.com/saphelp_nw04s/helpdata/en/43/a745d8823017b5e10000000a1553f6/frameset.htm

<removed by moderator>

regards

kummari

Edited by: Mike Pokraka on Jul 24, 2008 1:00 PM

[Former Member]

Hai All,

We have configured Plain J2SE engines on both Sender and Receievr systems and when we place a file in Source directory file is picked up by the sender plain J2SE adapter and sent to the XI but we are not getting that file at receievr System which has already configured with receievr plain J2SE adapter.

When i check in SXMB_MONI we are getting the status as recorded for outbound processing.

Can anyone suggest me regarding this.

As we have configrued the XI adapter as receievr in ID part.

Thanks,

Kalyan.

[Former Member]

As i have given the parameters at receievr end as

XI.httpPort=8210

XI.httpService=http://<IP Address>:8210/file/test

and i mention the URL in XI receievr adapter as

http://<IP Address>:8210/file/test

USERID=Logon ID for recever adapter engine

password=password for the rever adapter engine

Any suggetsions???

Thanks,

Kalyan.

Edited by: Kalyan chakravarthy p on Jul 28, 2008 9:41 AM