I want to ask before I will spend time with installation if it is posible to deploy and run WebDynpro applications on the latest Application Server and use Java EE 5 services?
I want to use WebDynpro for GUI, but backend should use EJB3. How can I do this?
to backup the previous statement I’d like to recommend using Java Server Faces to implement the presentation logic of your application. The preview edition is compliant to Java EE 5 specification stack; therefore it provides built-in support for JSF, which applications can directly use.
Yes, it is requirement to use WebDynpro as frontend and Java EE 5 as backend. As the development will take some time I hope that when we finish there will be fully supported version.
> - To what extend will SAP support JSF as part of Java
> EE 5?
To the extend that we offer whatever is in the standard in our standard compliant server.
> - What is SAP's roadmap concerning WebDynpro and JSF?
There is a roadmap for WD from SAP and there is a roadmap for for JSF not from SAP. We do provide support to integrate JSF into WebDynpro environments.
>
> - How the roadmap on the related tool support?
As tool support is more and more defined through open source projects (see WTP) we will rather support there then opening our own thread of tools.
It is possible to deploy and run Web Dynpro applications on Java EE 5 Edition server after you installed Netweaver Adminstrator (which is shipped with the DVD/download and will enhance the Java EE 5 engine with a Web Dynpro runtime). However it is not possible to develop Web Dynpro applications with the IDE contained in this preview.
Accessing EJB3 from Web Dynpro is possible but not officially support at the moment. One could get a reference to an EJB3 SessionBean via JNDI-lookup and use them within a Web Dynpro component controller. To have design-time support for JPA entities returned by a SessionBean the JavaBean model importer can be used because JPA entities are just simple POJOs. However this approach would require an additional engine and its IDE with full Web Dynpro support.
I am also trying to run a WebDynPro application inside Java EE 5.
I installed the NWAdmin tool by running the install in the Java EE 5 directory, I can access the NWAdmin tool successfully so it looks like that part is working.
I create my webdynpro archive, my question is, now what? It looks like the deployment is different, how do I get it onto the Java EE server, which is different than 2004s?
If you want to deploy a Web Dynpro archive you should try to use the view "Deploy View" of the Java EE 5 Developer Studio instead of the WTP deployment. However I fear that you might have problems with running a Web Dynpro application on the Java EE 5 Edition that was built with a Developer Studio for NW 2004s. Maybe you just give it a try and share your results with us here.
I created a simple WebDynPro, just a screen with a message.
I created the archive in NW 2004s.
When I tried to deploy it in the Deploy View of JAVA EE 5 Studio, it failed with this message:
S U M M A R Y
~~~~~~~~~~~~~~~~~~~
Successfully deployed: 0
Deployed with warnings: 0
Failed deployments: 1
~~~~~~~~~~~~~~~~~~~
An error occurred while deploying the deployment item 'local_TestWDP'.; nested exception is:
java.rmi.RemoteException: class com.sap.engine.services.dc.gd.DeliveryException: An error occurred during deployment of sdu id: local_TestWDP
sdu file path: C:\Documents and Settings\PCleary\Documents\SAP\workspace\TestWDP\TestWDP.ear
version status: NEW
deployment status: Admitted
description:
1. Error:
Error occurred while deploying ear file C:\Documents and Settings\PCleary\Documents\SAP\workspace\TestWDP\TestWDP.ear.
Reason: Exception while validating application local/TestWDP.
No one of the [] containers, which processed it, returned deployed component names.
The registered containers in this moment were [com.sap.security.ume, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, JMSConnector, Monitoring Configurator, dbschemacontainer, appclient, orpersistence, JDBCConnector, EJBContainer, webservices_container, scheduler~container].
Possible reasons :
1.An AS Java service, which is providing a container, is stopped or not deployed.
2.The containers, which processed it, are not implemented correct. They deployed or started initially the application, but didn't return deployed components in the application deployment info.
. Cannot deploy it.; nested exception is:
java.rmi.RemoteException: class com.sap.engine.services.deploy.server.utils.DSRemoteException: Error occurred while deploying ear file C:\Documents and Settings\PCleary\Documents\SAP\workspace\TestWDP\TestWDP.ear.
Reason: Exception while validating application local/TestWDP.
No one of the [] containers, which processed it, returned deployed component names.
The registered containers in this moment were [com.sap.security.ume, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, JMSConnector, Monitoring Configurator, dbschemacontainer, appclient, orpersistence, JDBCConnector, EJBContainer, webservices_container, scheduler~container].
Possible reasons :
1.An AS Java service, which is providing a container, is stopped or not deployed.
2.The containers, which processed it, are not implemented correct. They deployed or started initially the application, but didn't return deployed components in the application deployment info.
1. File:C:\Documents and Settings\PCleary\Documents\SAP\workspace\TestWDP\TestWDP.ear
Name:TestWDP
Vendor:local
Location:LOKAL
Version:0.2007.02.28.16.20.56
Deploy status:Aborted
Version:NEW
Description:
1. Error:
Error occurred while deploying ear file C:\Documents and Settings\PCleary\Documents\SAP\workspace\TestWDP\TestWDP.ear.
Reason: Exception while validating application local/TestWDP.
No one of the [] containers, which processed it, returned deployed component names.
The registered containers in this moment were [com.sap.security.ume, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, JMSConnector, Monitoring Configurator, dbschemacontainer, appclient, orpersistence, JDBCConnector, EJBContainer, webservices_container, scheduler~container].
Possible reasons :
1.An AS Java service, which is providing a container, is stopped or not deployed.
2.The containers, which processed it, are not implemented correct. They deployed or started initially the application, but didn't return deployed components in the application deployment info.
2. The deployment item could not be delivered. The reason is: An error occurred during deployment of sdu id: local_TestWDP
sdu file path: C:\Documents and Settings\PCleary\Documents\SAP\workspace\TestWDP\TestWDP.ear
version status: NEW
deployment status: Admitted
description:
1. Error:
Error occurred while deploying ear file C:\Documents and Settings\PCleary\Documents\SAP\workspace\TestWDP\TestWDP.ear.
Reason: Exception while validating application local/TestWDP.
No one of the [] containers, which processed it, returned deployed component names.
The registered containers in this moment were [com.sap.security.ume, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, JMSConnector, Monitoring Configurator, dbschemacontainer, appclient, orpersistence, JDBCConnector, EJBContainer, webservices_container, scheduler~container].
Possible reasons :
1.An AS Java service, which is providing a container, is stopped or not deployed.
2.The containers, which processed it, are not implemented correct. They deployed or started initially the application, but didn't return deployed components in the application deployment info.
Reason: An error occurred while deploying the deployment item 'local_TestWDP'.; nested exception is:
java.rmi.RemoteException: class com.sap.engine.services.dc.gd.DeliveryException: An error occurred during deployment of sdu id: local_TestWDP
sdu file path: C:\Documents and Settings\PCleary\Documents\SAP\workspace\TestWDP\TestWDP.ear
version status: NEW
deployment status: Admitted
description:
1. Error:
Error occurred while deploying ear file C:\Documents and Settings\PCleary\Documents\SAP\workspace\TestWDP\TestWDP.ear.
Reason: Exception while validating application local/TestWDP.
No one of the [] containers, which processed it, returned deployed component names.
The registered containers in this moment were [com.sap.security.ume, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, JMSConnector, Monitoring Configurator, dbschemacontainer, appclient, orpersistence, JDBCConnector, EJBContainer, webservices_container, scheduler~container].
Possible reasons :
1.An AS Java service, which is providing a container, is stopped or not deployed.
2.The containers, which processed it, are not implemented correct. They deployed or started initially the application, but didn't return deployed components in the application deployment info.
. Cannot deploy it.; nested exception is:
java.rmi.RemoteException: class com.sap.engine.services.deploy.server.utils.DSRemoteException: Error occurred while deploying ear file C:\Documents and Settings\PCleary\Documents\SAP\workspace\TestWDP\TestWDP.ear.
Reason: Exception while validating application local/TestWDP.
No one of the [] containers, which processed it, returned deployed component names.
The registered containers in this moment were [com.sap.security.ume, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, JMSConnector, Monitoring Configurator, dbschemacontainer, appclient, orpersistence, JDBCConnector, EJBContainer, webservices_container, scheduler~container].
Possible reasons :
1.An AS Java service, which is providing a container, is stopped or not deployed.
2.The containers, which processed it, are not implemented correct. They deployed or started initially the application, but didn't return deployed components in the application deployment info.
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:734)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:220)
at com.sap.ide.eclipse.deployer.dc.deploy.DeployProcessor70.deploy(DeployProcessor70.java:111)
at com.sap.ide.eclipse.j2ee.engine.deploy.view.deploy.action.DeployAction$DeployActionJob.run(DeployAction.java:223)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
Caused by: com.sap.engine.services.dc.cm.deploy.DeploymentException: An error occurred while deploying the deployment item 'local_TestWDP'.; nested exception is:
java.rmi.RemoteException: class com.sap.engine.services.dc.gd.DeliveryException: An error occurred during deployment of sdu id: local_TestWDP
sdu file path: C:\Documents and Settings\PCleary\Documents\SAP\workspace\TestWDP\TestWDP.ear
version status: NEW
deployment status: Admitted
description:
1. Error:
Error occurred while deploying ear file C:\Documents and Settings\PCleary\Documents\SAP\workspace\TestWDP\TestWDP.ear.
Reason: Exception while validating application local/TestWDP.
No one of the [] containers, which processed it, returned deployed component names.
The registered containers in this moment were [com.sap.security.ume, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, JMSConnector, Monitoring Configurator, dbschemacontainer, appclient, orpersistence, JDBCConnector, EJBContainer, webservices_container, scheduler~container].
Possible reasons :
1.An AS Java service, which is providing a container, is stopped or not deployed.
2.The containers, which processed it, are not implemented correct. They deployed or started initially the application, but didn't return deployed components in the application deployment info.
. Cannot deploy it.; nested exception is:
java.rmi.RemoteException: class com.sap.engine.services.deploy.server.utils.DSRemoteException: Error occurred while deploying ear file C:\Documents and Settings\PCleary\Documents\SAP\workspace\TestWDP\TestWDP.ear.
Reason: Exception while validating application local/TestWDP.
No one of the [] containers, which processed it, returned deployed component names.
The registered containers in this moment were [com.sap.security.ume, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, JMSConnector, Monitoring Configurator, dbschemacontainer, appclient, orpersistence, JDBCConnector, EJBContainer, webservices_container, scheduler~container].
Possible reasons :
1.An AS Java service, which is providing a container, is stopped or not deployed.
2.The containers, which processed it, are not implemented correct. They deployed or started initially the application, but didn't return deployed components in the application deployment info.
at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:186)
at com.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:47)
at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:177)
at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:76)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:624)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:483)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:206)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:153)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:807)
at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:253)
at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:109)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:841)
at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:125)
at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:59)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:168)
Caused by: java.rmi.RemoteException: class com.sap.engine.services.dc.gd.DeliveryException: An error occurred during deployment of sdu id: local_TestWDP
sdu file path: C:\Documents and Settings\PCleary\Documents\SAP\workspace\TestWDP\TestWDP.ear
version status: NEW
deployment status: Admitted
description:
1. Error:
Error occurred while deploying ear file C:\Documents and Settings\PCleary\Documents\SAP\workspace\TestWDP\TestWDP.ear.
Reason: Exception while validating application local/TestWDP.
No one of the [] containers, which processed it, returned deployed component names.
The registered containers in this moment were [com.sap.security.ume, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, JMSConnector, Monitoring Configurator, dbschemacontainer, appclient, orpersistence, JDBCConnector, EJBContainer, webservices_container, scheduler~container].
Possible reasons :
1.An AS Java service, which is providing a container, is stopped or not deployed.
2.The containers, which processed it, are not implemented correct. They deployed or started initially the application, but didn't return deployed components in the application deployment info.
. Cannot deploy it.; nested exception is:
java.rmi.RemoteException: class com.sap.engine.services.deploy.server.utils.DSRemoteException: Error occurred while deploying ear file C:\Documents and Settings\PCleary\Documents\SAP\workspace\TestWDP\TestWDP.ear.
Reason: Exception while validating application local/TestWDP.
No one of the [] containers, which processed it, returned deployed component names.
The registered containers in this moment were [com.sap.security.ume, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, JMSConnector, Monitoring Configurator, dbschemacontainer, appclient, orpersistence, JDBCConnector, EJBContainer, webservices_container, scheduler~container].
Possible reasons :
1.An AS Java service, which is providing a container, is stopped or not deployed.
2.The containers, which processed it, are not implemented correct. They deployed or started initially the application, but didn't return deployed components in the application deployment info.
at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.performDeployment(ApplicationDeployer.java:162)
at com.sap.engine.services.dc.gd.impl.GenericDeliveryImpl.deploy(GenericDeliveryImpl.java:54)
at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:157)
... 16 more
Caused by: java.rmi.RemoteException: class com.sap.engine.services.deploy.server.utils.DSRemoteException: Error occurred while deploying ear file C:\Documents and Settings\PCleary\Documents\SAP\workspace\TestWDP\TestWDP.ear.
Reason: Exception while validating application local/TestWDP.
No one of the [] containers, which processed it, returned deployed component names.
The registered containers in this moment were [com.sap.security.ume, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, JMSConnector, Monitoring Configurator, dbschemacontainer, appclient, orpersistence, JDBCConnector, EJBContainer, webservices_container, scheduler~container].
Possible reasons :
1.An AS Java service, which is providing a container, is stopped or not deployed.
2.The containers, which processed it, are not implemented correct. They deployed or started initially the application, but didn't return deployed components in the application deployment info.
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:302)
at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.performDeployment(ApplicationDeployer.java:150)
It seems that the Web Dynpro Runtime that is provided with the NWA is not registered to the deploy service of the engine (only a rough guess). Anyway,Web Dynpro is not supported officially with this preview version of the Server. I think that you should wait for the official product (Composition Environment) or the next downloadable preview version.
Web Dynpro applications built with the NW 04 or 2004s Developer Studio cannot be automatically deployed and run on the Java EE 5 Edition of AS Java. They need to be rebuilt in a Java EE 5 Developer Studio with Web Dynpro design time support. This will be available in the SAP NW Composition Environment as Robin already mentioned.
our current preview does not have yet WD implemented. This is planned and will be available at a later point in time.
Theoretically you could use two servers and run a 2004s and a JEE5 version and let them connect remotely. But that is quite ambitious as the preview is not for productive use and we also cannot guarantee for a specific ship data of the unrestricted version.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.