Access a JCo dest define in the Web Content Administrator

Question

I have got a J2EE application developed on NDS and i want to access and use a JCo destination defined in the Web Dynpro Content Administrator as a Web Dynpro application done.
First: is it possible or not ?
and if yes please tell me how ?
Cheers,
Eric Gourdou.

Answer 1

Hi, we're trying the solution described above.
The application cannot be deployed on the WAS due to the following call:
WDJCOClientConnection client =
WDSystemLandscape.getJCOClientConnection(“myJCOClient”);
Here is the exception thrown by the deployment service:
server ID 8240151:com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Application xxx cannot be started.
Reason: it has hard reference to resource tcwdwebdynpro with type service, which is not active on the server.
at com.sap.engine.services.deploy.server.ReferenceResolver.processReferenceToService(ReferenceResolver.java:458)
at com.sap.engine.services.deploy.server.ReferenceResolver.processMakeReference(ReferenceResolver.java:396)
at com.sap.engine.services.deploy.server.ReferenceResolver.beforeStartingApplication(ReferenceResolver.java:328)
at com.sap.engine.services.deploy.server.application.StartTransaction.beginCommon(StartTransaction.java:178)
at com.sap.engine.services.deploy.server.application.StartTransaction.beginLocal(StartTransaction.java:152)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:356)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runMe(ParallelAdapter.java:80)
at com.sap.engine.services.deploy.server.application.ParallelAdapter$1.run(ParallelAdapter.java:218)
at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
Do you have any information on how to activate the service or how to reference the jar in the J2EE application.
By trying to define the service with a weak reference, the deployment works but a ClassNotFound exception is thrown.