Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Deploying a EclipseLink Application (ELUG)"
m (linked to oracle docs) |
m |
||
| Line 1: | Line 1: | ||
<div style="margin:5px;float:right;border:1px solid #000000;padding:5px">__TOC__ | <div style="margin:5px;float:right;border:1px solid #000000;padding:5px">__TOC__ | ||
| − | [[Special:Whatlinkshere/Deploying | + | [[Special:Whatlinkshere/Deploying an EclipseLink Application (ELUG)|Related Topics]]</div> |
| − | + | ||
| − | + | ||
For more information, see the following: | For more information, see the following: | ||
* [[Integrating%20EclipseLink%20with%20an%20Application%20Server%20(ELUG)|Integrating EclipseLink with an Application Server]] | * [[Integrating%20EclipseLink%20with%20an%20Application%20Server%20(ELUG)|Integrating EclipseLink with an Application Server]] | ||
* [[Creating%20EclipseLink%20Files%20for%20Deployment%20(ELUG)|Creating EclipseLink Files for Deployment]] | * [[Creating%20EclipseLink%20Files%20for%20Deployment%20(ELUG)|Creating EclipseLink Files for Deployment]] | ||
| − | * [[Packaging%20a%20EclipseLink%20Application%20(ELUG)|Packaging | + | * [[Packaging%20a%20EclipseLink%20Application%20(ELUG)|Packaging an EclipseLink Application]] |
| Line 31: | Line 29: | ||
Optionally, you may also consider [[#Performing Hot Deployment of EJB|Performing Hot Deployment of EJB]]. | Optionally, you may also consider [[#Performing Hot Deployment of EJB|Performing Hot Deployment of EJB]]. | ||
| − | |||
| Line 37: | Line 34: | ||
After you packaged your JPA application, deploy it to an application server of your choice. | After you packaged your JPA application, deploy it to an application server of your choice. | ||
| − | For more information, see [[Packaging and Deploying EclipseLink JPA Applications (ELUG)|Deploying | + | For more information, see [[Packaging and Deploying EclipseLink JPA Applications (ELUG)|Deploying an EclipseLink JPA Application]]. |
| + | |||
| − | ==Deploying | + | ==Deploying an EclipseLink Database Web Service== |
This section describes the following: | This section describes the following: | ||
| − | * [[#How to Deploy | + | * [[#How to Deploy an EclipseLink Database Web Service to OC4J|How to Deploy an EclipseLink Database Web Service to OC4J]] |
| − | * [[#What You May Need to Know About Deploying | + | * [[#What You May Need to Know About Deploying an EclipseLink Database Web Service|What You May Need to Know About Deploying an EclipseLink Database Web Service]] |
| − | ===How to Deploy | + | ===How to Deploy an EclipseLink Database Web Service to OC4J=== |
| − | To deploy | + | To deploy an EclipseLink database Web service to OC4J, you can use any development tool that supports deployment to OC4J. |
| − | ====To Deploy | + | ====To Deploy an EclipseLink Database Web Service to OC4J==== |
# Generate your EclipseLink database Web service.For more information, see [[Creating%20EclipseLink%20Files%20for%20Deployment%20(ELUG)|Creating Deployment Files for EclipseLink Database Web Services]]. | # Generate your EclipseLink database Web service.For more information, see [[Creating%20EclipseLink%20Files%20for%20Deployment%20(ELUG)|Creating Deployment Files for EclipseLink Database Web Services]]. | ||
| − | # Package your EclipseLink database Web service WAR file.For more information, see [[Packaging%20a%20EclipseLink%20Application%20(ELUG)|Packaging | + | # Package your EclipseLink database Web service WAR file.For more information, see [[Packaging%20a%20EclipseLink%20Application%20(ELUG)|Packaging an EclipseLink Database Web Service]]. |
# Choose how to deploy your EclipseLink database Web service depending on how you packaged it: | # Choose how to deploy your EclipseLink database Web service depending on how you packaged it: | ||
## If you chose not to package the EclipseLink database Web service WAR in an EAR, deploy the EclipseLink database Web service as a standalone Web module.For more information, see the ''[http://www.oracle.com/technology/documentation/index.html Oracle Fusion Middleware Enterprise Architecture and Deployment Guide]''. | ## If you chose not to package the EclipseLink database Web service WAR in an EAR, deploy the EclipseLink database Web service as a standalone Web module.For more information, see the ''[http://www.oracle.com/technology/documentation/index.html Oracle Fusion Middleware Enterprise Architecture and Deployment Guide]''. | ||
| Line 60: | Line 58: | ||
| − | ===What You May Need to Know About Deploying | + | ===What You May Need to Know About Deploying an EclipseLink Database Web Service=== |
For production, you must deploy your EclipseLink database Web service to OC4J. | For production, you must deploy your EclipseLink database Web service to OC4J. | ||
| − | For more information, see [[#How to Deploy | + | For more information, see [[#How to Deploy an EclipseLink Database Web Service to OC4J|How to Deploy an EclipseLink Database Web Service to OC4J]]. |
For complete details on deploying a Java EE application, see the ''[http://www.oracle.com/technology/documentation/index.html Oracle Fusion Middleware Enterprise Architecture and Deployment Guide]''. | For complete details on deploying a Java EE application, see the ''[http://www.oracle.com/technology/documentation/index.html Oracle Fusion Middleware Enterprise Architecture and Deployment Guide]''. | ||
| Line 69: | Line 67: | ||
For more information, see the following: | For more information, see the following: | ||
* [[Creating%20EclipseLink%20Files%20for%20Deployment%20(ELUG)|Creating Deployment Files for EclipseLink Database Web Services]] | * [[Creating%20EclipseLink%20Files%20for%20Deployment%20(ELUG)|Creating Deployment Files for EclipseLink Database Web Services]] | ||
| − | * [[Packaging%20a%20EclipseLink%20Application%20(ELUG)|Packaging | + | * [[Packaging%20a%20EclipseLink%20Application%20(ELUG)|Packaging an EclipseLink Database Web Service]] |
Revision as of 16:58, 18 December 2007
Contents
For more information, see the following:
- Integrating EclipseLink with an Application Server
- Creating EclipseLink Files for Deployment
- Packaging an EclipseLink Application
Deploying Java Applications
Build the JAR file (see Packaging Java Applications) and place it on the classpath.
For more information on accessing EclipseLink from your client application, see Acquiring and Using Sessions at Run Time.
Deploying JavaServer Pages and Servlets
After you build the WAR and JAR files (see Packaging JavaServer Pages and Servlet Applications), build them into an EAR file for deployment. To deploy the EAR to your JSP servlet server, copy the EAR to a commonly used directory. You may also need to use server-specific deployment tools. For more information, see the server documentation.
For more information on accessing EclipseLink from your client application, see How to Load a Session from sessions.xml with an Alternative Class Loader.
Deploying Session Bean Applications
After you build the WAR and JAR files (see Packaging Session Bean Applications), build them into an EAR file for deployment. To deploy the EAR file to your Java EE server, copy the EAR to a commonly used directory. You may also need to use server-specific deployment tools. For more information, see the server documentation.
For more information on accessing EclipseLink from your client application, see How to Load a Session from sessions.xml with an Alternative Class Loader.
Optionally, you may also consider Performing Hot Deployment of EJB.
Deploying JPA Applications
After you packaged your JPA application, deploy it to an application server of your choice.
For more information, see Deploying an EclipseLink JPA Application.
Deploying an EclipseLink Database Web Service
This section describes the following:
- How to Deploy an EclipseLink Database Web Service to OC4J
- What You May Need to Know About Deploying an EclipseLink Database Web Service
How to Deploy an EclipseLink Database Web Service to OC4J
To deploy an EclipseLink database Web service to OC4J, you can use any development tool that supports deployment to OC4J.
To Deploy an EclipseLink Database Web Service to OC4J
- Generate your EclipseLink database Web service.For more information, see Creating Deployment Files for EclipseLink Database Web Services.
- Package your EclipseLink database Web service WAR file.For more information, see Packaging an EclipseLink Database Web Service.
- Choose how to deploy your EclipseLink database Web service depending on how you packaged it:
- If you chose not to package the EclipseLink database Web service WAR in an EAR, deploy the EclipseLink database Web service as a standalone Web module.For more information, see the Oracle Fusion Middleware Enterprise Architecture and Deployment Guide.
- If you chose to package the EclipseLink database Web service WAR in an existing application's EAR, deploy the EclipseLink database Web service by deploying the EAR.For more information, the Oracle Fusion Middleware Enterprise Architecture and Deployment Guide.
What You May Need to Know About Deploying an EclipseLink Database Web Service
For production, you must deploy your EclipseLink database Web service to OC4J.
For more information, see How to Deploy an EclipseLink Database Web Service to OC4J.
For complete details on deploying a Java EE application, see the Oracle Fusion Middleware Enterprise Architecture and Deployment Guide.
For more information, see the following:
- Creating Deployment Files for EclipseLink Database Web Services
- Packaging an EclipseLink Database Web Service
Performing Hot Deployment of EJB
Many Java EE containers support hot deployment, a feature that enables you to deploy EJB on a running server. Hot deployment allows you to do the following:
- Deploy newly developed EJB to a running production system.
- Remove (undeploy) deployed EJB from a running server.
- Modify (redeploy) the behavior of deployed EJB by updating the bean class definition.
The client receives deployment exceptions when attempting to access undeployed or re-deployed bean instances. The client application must catch and handle the exceptions.
How you configure hot deployment of EJB depends on the type of Java EE application you are deploying:
- POJO application (see How to Perform Hot Deployment in a POJO Application).
For more information about hot deployment, see the Java EE container documentation.
How to Perform Hot Deployment in a POJO Application
When you take advantage of hot deployment in a POJO application, you must refresh the EclipseLink session using the SessionManager method getSession with the appropriate arguments (see How to Refresh a Session when the Class Loader Changes.
If you do not use this SessionManager method, then your application is responsible for destroying or refreshing the session when a hot deployment (or hot redeployment) occurs.