11.4 Performing Post-Deployment Tasks

This section describes some of the typical post-deployment tasks that need to be performed after the SOA application has been deployed. Post-deployment tasks include:

Setting up Notifications
Redeploying the SOA Application
Undeploying the SOA Application

11.4.1 How to Set Up Notifications

Many of the MBeans packaged with OC4J include the ability to generate notifications triggered by a state change registered by the MBean. For example, you can subscribe to a notification that will alert you when a selected application has stopped.

To subscribe to specific JMX event notifications:

Navigate to the OC4J Home page.
Click Administration.

Enterprise Manager displays the OC4J Administration page, which lists all the administration tasks you can perform for this instance.
Click the Task icon in the Notification Subscriptions row of the table.

Enterprise Manager displays the Notification Subscriptions page, which lists all the available notifications, grouped by application and service.
Select the check box in the Subscribe column for every notification you want to receive.

11.4.2 How to Redeploy the Application

After you deploy the application, you may need to undeploy the application or redeploy a newer version of the application. Application Server Control accommodates these scenarios by offering the ability to redeploy an application.

To redeploy an application:

Navigate to the OC4J Home page for the OC4J instance.
Click Applications.
Select the application and click Redeploy.

11.4.2.1 What Happens When You Redeploy the Application

Redeploying a J2EE application packaged within an EAR file prompts OC4J to undeploy the previous instance of the J2EE application, including any embedded resource adapters packaged with the application.

If changes are made to any of the following configuration files as part of redeployment, OC4J must be restarted for the changes to take effect. Otherwise, a restart of OC4J is not required after redeploying an application.This requirement applies only to configuration files that are already installed on the server.

data-sources.xml
jms.xml
rmi.xml

The application is completely inaccessible during redeployment, and incoming requests will not be processed until the updated application is restarted by OC4J when deployment is complete.

11.4.2.2 Impact of Redeploying a Parent Application

After redeploying an application that is the parent of one or more child applications, you should ideally restart each child application. Restarting will ensure that the child applications are able to access any inherited classes or shared libraries provided through the parent.

11.4.3 How to Undeploy the Application

After you deploy the application, you may need to undeploy the application or redeploy a newer version of the application. Oracle Enterprise Manager Application Server Control accommodates these scenarios by offering the ability to undeploy an application.

To undeploy an application:

Navigate to the OC4J Home page for the OC4J instance.
Click Applications.
Select the application and click Undeploy.

11.4.3.1 What Happens When You Undeploy the Application

Removing a J2EE application from an OC4J instance results in the following:

The application is removed from the OC4J runtime.
All bindings for the Web applications are removed from all the Web sites to which the Web modules are bound.
All application files are removed from both the applications/ and application-deployments/ directories.

11.4.3.2 Impact of Undeploying a Parent Applications

When an application that is the parent of one or more child applications is undeployed, the child applications are also undeployed.

This means that all of the related applications - the parent as well as its dependent applications - must be redeployed. Bear this in mind before undeploying a parent application.

11.4.4 Troubleshooting Deployment Errors

This section discusses common errors that occur during deployment

Interruptions During Application Deployment

If the deployment process is interrupted for any reason, you may need to clean up the temp directory, which by default is /var/tmp, on your system.

The Application Server Control Console Deployment wizard uses approximately 20 MB in swap space of the temp directory for storing information during the deployment process. At completion, the deployment wizard cleans up the additional files in the temp directory.

However, if the wizard is interrupted, it may not have the time or opportunity to clean up the temp directory. You must manually clean up any additional deployment files in the directory. Otherwise, the temp directory may run out of space and further deployment will not be possible.

You can change the temp directory at OC4J startup by setting the java.io.tmpdir command-line option to a new location. For more information on setting the system properties, refer to Oracle Containers for J2EE Configuration and Administration Guide.