WebDynpro-App. developed in WebAS6.40, deployment in WebAS7.00 fails

[Former Member]

Hello,

i've developed a WebDynpro-SoftwareComponent.

It contains of 53 DevelopmentComponents.

Development-System: WebAS6.40 SP18

Target-System: WebAS7.00 SP11.

I'm using SDM-Tool of WebAS7.00 for deployment.

Problem: deployment of 10 DCs is aborting during the deployment of .sca-Archive.

43 DCs were deployed successfully.

Errormessage:

##################################################################

Caught exception during application deployment from SAP J2EE Engine's deploy service:

java.rmi.RemoteException:

Cannot deploy application my_test.de/abcdef. Reason:

Clusterwide exception: Failed to deploy application my_test.de/abcdef.

Check causing exception for details (trace file).

Hint: Are all referenced components deployed and available

on the engine?;

nested exception is: com.sap.engine.services.deploy.container.DeploymentException:

Clusterwide exception: Failed to deploy application my_test.de/abcdef.

Check causing exception for details (trace file).

Hint: Are all referenced components deployed and available

on the engine?

(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)

Deployment of my_test.de/abcdef finished with Error (Duration 3140 ms)

##################################################################

But i'm sure, there are all needed DCs (UsedDCs) in the .SCA-File.

Deployment of this .SCA-File in WebAS6.40 runs without any Errors.

Target-System(WebAS7.00) has this Files:

SAP_BUILDT

SAP_JTECHS

SAP-JEE

of 7.00/SP11-Version, the Development-System(WebAS6.40) has this files in Version 6.40/SP18, but i guess it doesnt matter.

Did someone already deploy any 6.40-SCAs on WebAS7.00???

Please help.

Thanks.

Artur.

[BeGanz · Accepted solution]

Hallo Artur,

what's written to the trace file? Within NW 04s SP 10 we added a new function to the deployment manager: it now detects during deployment whether a newly deployed Web Dynpro DC comprises entities which were already deployed in another DC but in the same Java package namespace and with the same name. In this situation the Web Dynpro Runtime Repository is not able to differentiate between duplicate Web Dynpro entities (with the same fully qualified name) stored in separate DC. But I'm not sure whether this is the reason for your error symptom.

Regards, Bertram

[Former Member · Accepted solution]

Hello Bertram,

i've solved the problem.

The thing was:

my 53 DCs (developed in WebAS6.40) had more then 20 Applications (30).

Only 1 Application was necessary, the other 29 Apps were just for testing.

All 53 DCs are working together, so i needed only the first application.

I deleted 29 applications in 29 DCs and SCA could be deployed without any errors.

So i guess, the configuration of the WebAS7.00 is wrong, there is probably some restriction by 20 Applications.

This Number: 20 Applications i've found as i deployed the DCs as EARs (available in _comp\gen\default after build) one after another in different orders.

Everytime there were 10 Applications (each time other) which couldn't be deployed.

The Error-Message of SDM (log)was every time the same:

"Are all referenced components deployed and available

on the engine?;"

However, it would be better, when SDM would give more exactly error-messages.

The rest of WebAS7.00 is very nice.

I was very impressed, as i saw, that my UI-Controls look other/better in WebAS7.00 as befor, as the Application ran on WebAS6.40.

So i would say: nice work guys!

It's a pleasure to work with WebAS!!!

In german i would say: "hammergeil".

So, the problem is solved.

But maybe u can give me an answer:

where/how can i set the property vor a max.number of applications, which can be deployed on WebAS7.00?

In Visual Admin?

Thanks for your reply.

Artur.