cancel
Showing results for 
Search instead for 
Did you mean: 

PI 7.1 Adapter Engine Issue

0 Kudos

HI All,

In PI 7.1 getting this error , and Adapter Engine is RED status.

Perforemd Cache refresh and included Adapter engine manually in PI (but stopping starting the service)

Only change made was the another PI system is registered to this PI system and there are two Adapter engines ,Two integration engines shown in Technical system fro Process Integration.

Cache refresh etc are working fine,below is teh error message.

============================

Message: Cannot construct correct URL for runtime check using entries in SLD for component af.dp1.mngnetmcdb; make correct entries in SLD

Stacktrace:

com.sap.aii.rwb.exceptions.OperationFailedException: Cannot construct correct URL for runtime check using entries in SLD for component af.dp1.mngnetmcdb; make correct entries in SLD

at com.sap.aii.rwb.core.XIJavaRTCComponent.getConnector(XIJavaRTCComponent.java:211)

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

at com.sap.aii.rwb.web.componentmonitoring.model.CompTestModel.doSelftest(CompTestModel.java:648)

at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage.doSelftest(CmDynPage.java:313)

============================

Before that we were gettign this error

===========

com.sap.aii.af.ra.ms.api.ConfigException: Some of the IS access information is not available. SLDAcess property may be set to true, but SLD is not available.

For which i have updated SAPXIAFC16P_12.SCA XI component.

But still Apdapter Engine is still RED in Componet Monitoring.

Pls suggest.

Regards

Ajay

Accepted Solutions (0)

Answers (1)

Answers (1)

shyam_dontamsetty
Active Participant
0 Kudos

Ajay,

Have checked all the SLD entries are ok.

It looks while accesing the SLD entries the check is throwing error.

Cannot construct correct URL for runtime check using entries in SLD for component af.dp1.mngnetmcdb; make correct entries in SLD is that DP1 a instance that registered in your SLD,if so you can look more into the details.

Best Regards,

Shyam Dontamsetty

0 Kudos

Shyam

SLDCHECK is working fine.

Can you let me know which enteries and where i have to check.

DP1 is PI system and SLD is running here.

Regards

Ajay

shyam_dontamsetty
Active Participant
0 Kudos

Ajay,

Check this thread :

Try the solution provided in this thread.

Best Regards,

Shyam Dontamsetty

0 Kudos

Shaym

Thanks it was helpful.

But i have restarted com.sap.aii.af.app service couple of time but of no use.

After restarting XPI service and AF core service ,Adapter Framework is in yellow colour with this error for self test

=========

IS Adapter Framework running

Message matrix is not activated on server node 79430050; result of self-test is not available for this node

=============

Regards

Ajay

0 Kudos

Hi All,

Followed this note 804124 and changed the SLD hostname and port for the XPI Service CPA Cache

Removed the Adapter framework from SLD and tried to register it again by restarting adapterframework related services.

But Adapter Framework is no registring with the SLD adn it now not available in SLD technical Systems.

I reverted the changes made to XPI service and restarted J2ee engien but still Adapter is not available.

Any pointers pls.

Regards

Ajay

Former Member
0 Kudos

Hi Ajay,

Check SAP Note 1117249 - Incomplete Registration of PI components in SLD.

See if the steps in the note helps to reregister the Adapter Engine.

Cheers....,

Raghu

0 Kudos

Hi Raghu

I have tried the steps in this note but Adapter Engine is not registering with the SLD.

Only changes i made were the

SLD.selfregistration.httpPort"

"SLD.selfregistration.httpsPort"

"SLD.selfregistration.hostName"

Properties for Adapter Enngine as per Note 804124.

Regards

Ajay

Edited by: Ajay Sandal on Feb 17, 2010 2:29 PM

Former Member
0 Kudos

Hi,

Adapter engine is in red doesn't mean there is some problem with the functionality with your engine.

Is may be due to some of the communication channels might not be functioning properly, ask your developer to check what is the porblem with the communication channels. This could be one of the reason.

I dont think this is some problem with your sld.

Regards,

Vamshi.

0 Kudos

Hi Vamshi

Was not aware of this.

What i did is ..removed the Adapter Engine from SLD and tried to register it again.But its not happeining now.

I changed the properties of XPI Service CPA Cache Service and then tried the same ,no luck so reverted the change and set the properties to default.

Now trying to register the Adapter Engine ,by restarting the service but that is not happening.

Regards

Ajay

Former Member
0 Kudos

Hi,

You have to restart the system not the application. Restart your system, you will find your engine again.

Regards,

Vamshi.

0 Kudos

Restarted the System ..No luck.

Tried to update SAP XIAF component from SP08 to SP09 but JSPM throwing error in that with status error buti n componet info the SAP XIAF level is 09. Tried to again update with JSPM but JSPM is strucking with error that J2EE is not running.

Seems like there is a timeout for JSPM to check the j2ee and j2ee nodes are coming up in 3-4 minutes and JSPM is throwing error that J2ee server not avaialbe in 2 minutes.

====================================

Pls see the JSPM deployment log


Mngnetmcdev\sapmnt\trans\EPS\in\SAPXIAF09_5-20001975.SCA --> com.sap.aii.af.app.sda for component sap.com/com.sap.aii.af.app aborted. Detailed message:

1. Aborted deployment archive:

sdu id: sap.com_com.sap.aii.af.app

contained in software archive:

sdu id: sap.com_SAP_XIAF. Deployment of archive
Mngnetmcdev\sapmnt\trans\EPS\in\SAPXIAF09_5-20001975.SCA --> com.sap.xi.mdt2.sda for component sap.com/com.sap.xi.mdt2 is rejected because deployment of other component it depends on is rejected. Detailed message:

1. Aborted deployment archive:

sdu id: sap.com_com.sap.aii.af.app

contained in software archive:

sdu id: sap.com_SAP_XIAF. Deployment of archive
Mngnetmcdev\sapmnt\trans\EPS\in\SAPXIAF09_5-20001975.SCA --> com.sap.aii.af.service.trex.ws.sda for component sap.com/com.sap.aii.af.service.trex.ws is rejected because deployment of other component it depends on is rejected. Detailed message:

1. Aborted deployment archive:

sdu id: sap.com_com.sap.aii.af.app

contained in software archive:

sdu id: sap.com_SAP_XIAF. Deployment of archive
Mngnetmcdev\sapmnt\trans\EPS\in\SAPXIAF09_5-20001975.SCA --> com.sap.aii.adapter.soap.app.sda for component sap.com/com.sap.aii.adapter.soap.app is rejected because deployment of other component it depends on is rejected. Detailed message:

1. Contains Aborted deployment component:

sdu id: sap.com_com.sap.aii.af.app

sdu file path: G:\usr\sap\DP1\DVEBMGS07\j2ee\cluster\server1\.\temp\tcbldeploy_controller\archives\152\SAPXIAF09_5-20001975_SCA1266411672656\DEPLOYARCHIVES\com.sap.aii.af.app.sda

version status: HIGHER

deployment status: Aborted

description: 1. [ERROR CODE DPL.DS.5402] JLinEE reported following erros for sap.com/com.sap.aii.af.app application.

ERRORS:

  • Bean Interfaces: The local home interface "com.sap.aii.af.lib.util.dispatch.DispatchingServiceLocalHome" cannot be found in the search path., file: com.sap.aii.af.ejb.jar#META-INF/ejb-jar.xml, column 0, line 0, severity: error * Bean Interfaces: The local interface "com.sap.aii.af.lib.util.dispatch.DispatchingServiceLocal" cannot be found in the search path., file: com.sap.aii.af.ejb.jar#META-INF/ejb-jar.xml, column 0, line 0, severity: error * Bean Interfaces: stateless bean "JobDispatcherBean" should have at least one of the following interface pairs: "local" and "local-home", "home" and "remote" or service endpoint interface, file: com.sap.aii.af.ejb.jar#META-INF/ejb-jar.xml, column 0, line 0, severity: error

Hint: 1) Given application file is not valid one.. Deployment of archive
Mngnetmcdev\sapmnt\trans\EPS\in\SAPXIAF09_5-20001975.SCA for component sap.com/SAP_XIAF aborted. <b>Software component SAP_XIAF deployment messages:</b>.

Feb 17, 2010 5:07:20 AM [Info]: Overal deployment message : Deployment finished with error..

Feb 17, 2010 5:07:21 AM [Info]: You can find additional information in log file G:\usr\sap\DP1\DVEBMGS07\j2ee\JSPM\log\log_2010_02_17_04_52_11\DETECT_SYSTEM_COMPONENTS_03.LOG.

Feb 17, 2010 5:07:25 AM [Info]: Loaded usage type data from data source jdbc/pool/DP1.

Feb 17, 2010 5:07:25 AM [Info]: Detected system products and usage types.

Feb 17, 2010 5:07:26 AM [Info]: Loaded usage type data from data source jdbc/pool/DP1.

Feb 17, 2010 5:07:26 AM [Info]: Detected system products and usage types.

Feb 17, 2010 5:07:26 AM [Info]: Activating any new usage types...

Feb 17, 2010 5:07:26 AM [Info]: Activated necessary usage types.

Feb 17, 2010 5:07:26 AM [Info]: Dialog DeployQueue: you have chosen Next.

Feb 17, 2010 5:07:26 AM [Info]: DeployQueue dialog has been processed.

Feb 17, 2010 5:07:26 AM [Info]: Trusted connection will be used to control local instance DVEBMGS07.

Feb 17, 2010 5:07:26 AM [Info]: Checking the state of instance 07 of system DP1...

Feb 17, 2010 5:07:26 AM [Info]: You can find additional information in log file G:\usr\sap\DP1\DVEBMGS07\j2ee\JSPM\log\log_2010_02_17_04_52_11\ENGINE_OPERATION_03.LOG.

Feb 17, 2010 5:07:26 AM [Info]: Instance 07 of system DP1 is stopped.

Feb 17, 2010 5:07:26 AM [Info]: System DP1 is not running.

Feb 17, 2010 5:07:26 AM [Info]: JSPM statistics data saved in G:/usr/sap/DP1/DVEBMGS07/j2ee/JSPM/log/log_2010_02_17_04_52_11/JspmEvaluation_1.xml.

Feb 17, 2010 5:07:26 AM [Info]: Starting Finish dialog...

=====================================

And when restarting com.sap.aii.af.app service

=================

Local Adapter Message Data MBean#

#1.5 #0024E8745C6C00220000001B0000149C0B05EC18ABABA662#1266418373890#com.sap.engine.services.deploy##com.sap.engine.services.deploy####n.a.##205348f01bd411dfc7b10024e8745c6c#System [44]##0#0#Warning#1#/System/Server/Services/Deploy#Plain###Starting application sap.com/com.sap.aii.adapter.soap.app, which is in IMPLICIT_STOPPED, because the resource sap.com/com.sap.aii.af.app with type application, for which it waits is now available. The reference type to this resource is hard.#

#1.5 #0024E8745C6C00220000001E0000149C0B05EC18ABABA662#1266418374109#com.sap.engine.services.deploy##com.sap.engine.services.deploy####n.a.##205348f01bd411dfc7b10024e8745c6c#System [44]##0#0#Warning##Plain###

Warning occurred on server 79430050 during startApp sap.com/com.sap.aii.af.app : Cannot load servlet [com.sap.aii.af.app.servlet.AdapterFrameworkServlet]. Error is: [java.lang.NoClassDefFoundError: com/sap/aii/af/service/sld/SldLockException].#

===============

Re executed the NWA Initial Setup but that also didn't helped.

Pls throw some light.

Regards

Ajay

Former Member
0 Kudos

Hi,

Upgrading the SP for XIAF alone is not advisable.

Just follow the below note you will be able to see the adapter engine in your sld after performing this actions and restarting the java stack.

Note 1031321 - Self-Registration of Adapter Engine and RWB fails

Regards,

Vamshi.

0 Kudos

This note has been followed lot of times.

Restarting the application/service and then J2EE Engine is nto helping and Adapter Engine is not registering.

Regards

Ajay

Former Member
0 Kudos

Ajay,

Check for entry 'com.sap.aii.connect.integrationserver.r3.r3name' in exchangeprofile and what's the value assigned to it.

you may get back to me upon checking...

- Sekhar

Former Member
0 Kudos

Ajay,

Check for entry 'com.sap.aii.connect.integrationserver.r3.r3name' in exchangeprofile and what's the value assigned to it.

you may get back to me upon checking...

- Sekhar

0 Kudos

Hi Sekar

I checked the property and the value is SID of the system.

Regards

Ajay

Former Member
0 Kudos

hi Ajay,

Not sure if you have attempted to do CPACache full refresh? if not please try that and post the error if any.

And also, logon to your SLD system check if you have all required Associations (for Integration Server there should be 3 associations).

Write to me at my personal/official mail ID if required.

-Sekhar

Edited by: sekhar on Feb 22, 2010 5:13 AM

0 Kudos

HI All

When i am trying to start the RWB its throwing an exception that service

===========

Details: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5035] Application sap.com/com.sap.xi.rwb cannot be started. Reason: it has hard reference to resource com.sap.xi.mdt.beans with type application, which is not active on the server.

at com.sap.engine.services.deploy.server.ReferenceResolver.processReferenceToApplication(ReferenceResolver.java:843)

at com.sap.engine.services.deploy.server.ReferenceResolver.processMakeReference(ReferenceResolver.java:580)

at com.sap.engine.services.deploy.server.ReferenceResolver.beforeStartingApplication(ReferenceResolver.java:496)

at com.sap.engine.services.deploy.server.application.StartTransaction.beginCommon(StartTransaction.java:166)

at com.sap.engine.services.deploy.server.application.StartTransaction.begin(StartTransaction.java:134)

at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:411)

at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:498)

at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:554)

at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter

==============

I doubt that following SAP note 1358812 when i tried to update MESSAGING and XIAF componet to latest SP09 JSPM error stopped saying Java is down ,but in fact it was coming up with Starting Apps phase.

JSPM is not able to patch any componetn Message or XIAF alone or together.Is there any timeout value need to be set or increased.

Pls suggest.

Regards

Ajay

0 Kudos

Hi All,

MESSAGING componet is not updating to SP09 and deployment is failing ,see the error in JSPM logs

========

1. Parsing ws-deployment-descriptor, Vitrual Interfaces and WebService Definitions failed. The application will not be started.

-> 3. Deployment of archive
Mngnetmcdev\sapmnt\trans\EPS\in\MESSAGING09_5-20001897.SCA --> com.sap.xi.mdt.beans.sda for component sap.com/com.sap.xi.mdt.beans aborted. Detailed message:

1. Aborted deployment archive:

sdu id: sap.com_com.sap.xi.mdt.beans

contained in software archive:

sdu id: sap.com_MESSAGING. Deployment of archive
Mngnetmcdev\sapmnt\trans\EPS\in\MESSAGING09_5-20001897.SCA --> com.sap.xi.itsam.soa.mdt.sda for component sap.com/com.sap.xi.itsam.soa.mdt is rejected because deployment of other component it depends on is rejected. Detailed message:

1. Aborted deployment archive:

sdu id: sap.com_com.sap.xi.mdt.beans

contained in software archive:

sdu id: sap.com_MESSAGING. Deployment of archive
Mngnetmcdev\sapmnt\trans\EPS\in\MESSAGING09_5-20001897.SCA --> com.sap.xi.mdt.soa.sda for component sap.com/com.sap.xi.mdt.soa is rejected because deployment of other component it depends on is rejected. Detailed message:

1. Contains Aborted deployment component:

sdu id: sap.com_com.sap.xi.mdt.beans

sdu file path: G:\usr\sap\DP1\DVEBMGS07\j2ee\cluster\server0\.\temp\tcbldeploy_controller\archives\482\MESSAGING09_5-20001897_SCA1266987636328\DEPLOYARCHIVES\com.sap.xi.mdt.beans.sda

version status: HIGHER

deployment status: Aborted

description: 1. Parsing ws-deployment-descriptor, Vitrual Interfaces and WebService Definitions failed. The application will not be started.

-> 3. Deployment of archive
Mngnetmcdev\sapmnt\trans\EPS\in\MESSAGING09_5-20001897.SCA for component sap.com/MESSAGING aborted.

Feb 23, 2010 9:04:40 PM [Info]: Overal deployment message : Deployment finished with error..

Feb 23, 2010 9:04:41 PM [Info]: You can find additional information in log file G:\usr\sap\DP1\DVEBMGS07\j2ee\JSPM\log\log_2010_02_23_20_59_24\DETECT_SYSTEM_COMPONENTS_02.LOG.

Feb 23, 2010 9:04:43 PM [Info]: Loaded usage type data from data source jdbc/pool/DP1.

Feb 23, 2010 9:04:43 PM [Info]: Detected system products and usage types.

Feb 23, 2010 9:04:44 PM [Info]: Loaded usage type data from data source jdbc/pool/DP1.

Feb 23, 2010 9:04:45 PM [Info]: Detected system products and usage types.

Feb 23, 2010 9:04:45 PM [Info]: Activating any new usage types...

Feb 23, 2010 9:04:45 PM [Info]: Activated necessary usage types.

Feb 23, 2010 9:04:45 PM [Info]: Dialog DeployQueue: you have chosen Next.

Feb 23, 2010 9:04:45 PM [Info]: DeployQueue dialog has been processed.

Feb 23, 2010 9:04:45 PM [Info]: Trusted connection will be used to control local instance DVEBMGS07.

Feb 23, 2010 9:04:45 PM [Info]: Checking the state of instance 07 of system DP1...

Feb 23, 2010 9:04:45 PM [Info]: You can find additional information in log file G:\usr\sap\DP1\DVEBMGS07\j2ee\JSPM\log\log_2010_02_23_20_59_24\ENGINE_OPERATION_02.LOG.

Feb 23, 2010 9:04:45 PM [Info]: Instance 07 of system DP1 is stopped.

Feb 23, 2010 9:04:45 PM [Info]: System DP1 is not running.

Feb 23, 2010 9:04:45 PM [Info]: JSPM statistics data saved in G:/usr/sap/DP1/DVEBMGS07/j2ee/JSPM/log/log_2010_02_23_20_59_24/JspmEvaluation.xml.

Feb 23, 2010 9:04:45 PM [Info]: Starting Finish dialog...

==========

When starting RWB ,gettign exception that

=============

Details: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5035] Application sap.com/com.sap.xi.rwb cannot be started. Reason: it has hard reference to resource com.sap.xi.mdt.beans with type application, which is not active on the server.

at com.sap.engine.services.deploy.server.ReferenceResolver.processReferenceToApplication(ReferenceResolver.java:843)

at com.sap.engine.services.deploy.server.ReferenceResolver.processMakeReference(ReferenceResolver.java:580)

at com.sap.engine.services.deploy.server.ReferenceResolver.beforeStartingApplication(ReferenceResolver.java:496)

at com.sap.engine.services.deploy.server.application.StartTransaction.beginCommon(StartTransaction.java:166)

at com.sap.engine.services.deploy.server.application.StartTransaction.begin(StartTransaction.java:134)

at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:411)

at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:498)

at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:554)

at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:251)

at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:392)

at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3389)

at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3375)

at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:749)

at com.sap.engine.services.servlets_jsp.server.deploy.impl.ApplicationManager.start(ApplicationManager.java:180)

at com.sap.engine.services.servlets_jsp.server.deploy.impl.ApplicationManager.analyseAppStatusMode(ApplicationManager.java:288)

at com.sap.engine.services.servlets_jsp.server.DeployContext.startLazyApplication(DeployContext.java:334)

=================

In NWA the service com.sap.xi.rwb is not sunnign as it is saying that it has hard refrence to com.sap.xi.mdt.beans.

Pls suggest how to proceed, tried to undeploy com.sap.xi.mdt.benas.sda with TELNET but it ther ei says it has dependencies.

Regards

Ajay

0 Kudos

Resolved!!

Updated the MESSAGINNG component and now RWB as well as Adapter Engine is available.Thank you all.

Former Member
0 Kudos

How did you updated the messaging component?