cancel
Showing results for 
Search instead for 
Did you mean: 

Adapter Engine - self-test error

Former Member
0 Kudos

All,

I'm in the Runtime Workbench --> Component Monitoring.

When I click on the Adapter Engine, I get an error saying:

Message: HTTP request failed. Error code: "500". Error message: "Internal Server Error [http://scxxidci:50000/AdapterFramework/rtc]"

Stacktrace:

com.sap.aii.rwb.exceptions.RequestFailedException: HTTP request failed. Error code: "500". Error message: "Internal Server Error [http://scxxidci:50000/AdapterFramework/rtc]"

at com.sap.aii.rwb.exceptions.RequestFailedException.forHttpErrorCode(RequestFailedException.java:79)

at com.sap.aii.rwb.rtcheck.rtcclient.GrmgConnector.request(GrmgConnector.java:238)

at com.sap.aii.rwb.rtcheck.rtcclient.GrmgConnector.selftest(GrmgConnector.java:96)

at com.sap.aii.rwb.core.XIRTCComponent.selftest(XIRTCComponent.java:315)

.....

- The Ping Status shows a green light.

- FQDN is used @ ExchangeProfile

- SLD parameters should work too because SLD is accessible and transaction SLDCHECK returns no errors.

Please advice.

Thanks a lot in advance.

Dimitri

Accepted Solutions (1)

Accepted Solutions (1)

sunilchandra007
Active Contributor
0 Kudos

>

> All,

>

> I'm in the Runtime Workbench --> Component Monitoring.

>

> When I click on the Adapter Engine, I get an error saying:

>

> Message: HTTP request failed. Error code: "500". Error message: "Internal Server Error [http://scxxidci:50000/AdapterFramework/rtc]"

> Stacktrace:

> com.sap.aii.rwb.exceptions.RequestFailedException: HTTP request failed. Error code: "500". Error message: "Internal Server Error [http://scxxidci:50000/AdapterFramework/rtc]"

> at com.sap.aii.rwb.exceptions.RequestFailedException.forHttpErrorCode(RequestFailedException.java:79)

> at com.sap.aii.rwb.rtcheck.rtcclient.GrmgConnector.request(GrmgConnector.java:238)

> at com.sap.aii.rwb.rtcheck.rtcclient.GrmgConnector.selftest(GrmgConnector.java:96)

> at com.sap.aii.rwb.core.XIRTCComponent.selftest(XIRTCComponent.java:315)

> .....

>

> - The Ping Status shows a green light.

> - FQDN is used @ ExchangeProfile

> - SLD parameters should work too because SLD is accessible and transaction SLDCHECK returns no errors.

>

> Please advice.

>

> Thanks a lot in advance.

>

> Dimitri

Hi,

Try these steps -

1. First trigger self-registration of RWB by running this URL in browser

>http://<host>:<port>/rwb/rtc?op=init

2. Register adapter engine by restart the following applications from Visual Administrator :

>sap.com/com.sap.aii.af.app

>sap.com/com.sap.aii.af.cpa.app

3. Check the Adapter engine status in Runtime Workbench --> Component Monitoring.

Let me know if it works...

Regards,

Chandra

Former Member
0 Kudos

Hi Chandra,

I did the steps you mentioned, but the problem remains. I still got

HTTP request failed. Error code: "500". Error message: "Internal Server Error [http://scxxidci.securex.erp:50000/AdapterFramework/rtc]" Last Retry Jun 5, 2009 8:01:08

While restarting the J2EE applications you mentioned, I saw in the NWA that not all com.sap.aii.af applications are started. Is this needed?

Kind regards

Dimitri

Edited by: Dimitri Sannen on Jun 5, 2009 9:17 AM

I just checked with some developers and their scenarios seem to work.

But the error still remains and I don't think this should be the case, is it?

Edited by: Dimitri Sannen on Jun 5, 2009 9:47 AM

I opened the URL http://scxxidci.securex.erp:50000/AdapterFramework/rtc and I'm getting the following result. Please check it, maybe something is not ok:

This is the subsystem af on scxsrv51b

Class in SLD package: com.sap.aii.utilxi.sld.XIAdapterFramework

subsystem com.sap.aii.utilxi.sld.XIAdapterFramework@6798ef2c

applicationId af

technicalHost com.sap.aii.utilxi.sld.J2EESystem@697e66d6

host scxxidci

httpPort 50000

httpsPort -1

contextRoot null

user PIAFUSER

password ******

locale en

level {7.0,0}

level.release 7.0

level.SP 0

technicalRoleId J2EE_SERVER

typeId AF_SERVER

SLD Data

landscapeDirectory com.sap.aii.utilxi.sld.SystemLandscapeDirectory@6991a1b5

IS Data

integrationServer com.sap.aii.utilxi.sld.XIIntegrationServer@580fa838

isAsMap {subsystem=com.sap.aii.utilxi.sld.XIIntegrationServer@580fa838, applicationId=is, technicalHost=com.sap.aii.utilxi.sld.AbapClientSystem@6bed21b2, host=scxxidci.securex.erp, httpPort=50000, httpsPort=, contextRoot=run, user=PIISUSER, password=******, locale=en, businessSystem=null, systemNumber=00, clientNumber=001}

sunilchandra007
Active Contributor
0 Kudos

Hi,

Check the following setting :

1. Make sure that their is entry for XI as technical system in SLD - Technical Landscape.

2. Check all the J2EE application containing com.sap.aii., com.sap.xi. or com.sap.lcr.* are running.

3. Check cache notification in Integration directory, click on menu Environment -> Cache Notification.

Also have a look at these links -

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d0d9a978-5f59-2a10-1cae-d4cf0c92... (Page 121)

https://service.sap.com/sap/support/notes/764176

/people/venugopalarao.immadisetty/blog/2007/03/15/adapter-engine-cannot-be-found-in-integration-directory

Also let me the SP level.

Regards,

Chandra

Edited by: sunil chandra on Jun 5, 2009 2:26 PM

Former Member
0 Kudos

Hi Chandra,

When I go to the Netweaver Administrator --> JAVA EE applications and use filter com.sap.aii, I see the following apps are not started:

com.sap.aii.af.core.migration

com.sap.aii.axis.app

com.sap.aii.af.ms.svc.migration

com.sap.aii.ibdir.itsam.app

com.sap.aii.adapter.sample.module.app

com.sap.aii.adapter.mail.app

com.sap.aii.adapter.marketplace.app

com.sap.aii.adapter.jms.app sa

com.sap.aii.af.ms.dbc

com.sap.aii.adapter.bc.app

com.sap.aii.sec.dbc

com.sap.aii.af.mod.trans.app

com.sap.aii.af.cpa.svc.migration

com.sap.aii.af.3rdparty.migration

com.sap.aii.adapter.soap.app

com.sap.aii.adapter.rfc.app

com.sap.xi.exprofui

com.sap.xi.dbschema.ibrun

com.sap.xi.ctc.app

com.sap.xi.dummy

com.sap.xi.mdt

com.sap.xi.content

com.sap.xi.dbschema.ibrep

com.sap.xi.ib.exchangeProfile

com.sap.xi.dbschema.ibreppvc

com.sap.xi.dbschema.ibdirpvc

com.sap.xi.dbschema.ibdir

com.sap.xi.dbschema.rwb

The application com.sap.lcr is started.

Concerning the SP Level:

Make Release NW07_07_REL

SPS Number 07

Thanks,

Dimitri

Edited by: Dimitri Sannen on Jun 5, 2009 11:18 AM

Maybe OSS Note 1282862 could help, don't you?

sunilchandra007
Active Contributor
0 Kudos

Go to the Netweaver Administrator --> JAVA EE applications and use filter, then select the service and then restart

○ sap.com/com.sap.aii*

○ sap.com/com.sap.lcr*

○ sap.com/com.sap.xi*

Regards,

Chandra

Former Member
0 Kudos

Hi Chandra,

I saw a lot of applications were not started, that's why I started all of them.

Now com.sap.aii, com.sap.lcr and com.sap.xi are started.

But the error still remains.

Then I restarted the J2EE engine.

Afterwards, I checked the J2EE applications and a lot of services were stopped again!

Kind regards,

Dimitri

sunilchandra007
Active Contributor
0 Kudos

1. Did you check entry for XI as technical system in SLD - Technical Landscape.

2. Check cache notification in Integration directory, click on menu Environment -> Cache Notification.

Let me know the status ...

Regards,

Chandra

Former Member
0 Kudos

Yep, looks good...

The cache status overview shows all green lights

Former Member
0 Kudos

Hi Chandra,

Please help me to understand what does the below URL does and when we use it.

http://<servername>:<port>/rwb/rtc?op=init

And how this is diff. from Administration->Java Web Start Administration->reinitialize/restore archive.

Thanks

Sekhar

Answers (1)

Answers (1)

Former Member
0 Kudos

Anybody has some advise?

Thanks a lot

Dimitri

Former Member
0 Kudos

Hi ,

In the column, "Send Message to" :

Type:

http://<hostname_XI>:<port>/sap/xi/engine?type=entry

Then send the message.

Thanks,

Shaily

Former Member
0 Kudos

FYI

We found the error after logging a message at SAP.

The thing is that the patch level of our Adapter Framework (SAPXIAF) was too low.

We are at PL 5 and should go to PL 6.

We did this and the problem was solved.

Kind regards

Dimitri