17 Deploying / Redeploying / Undeploying Java EE Applications

From the Enterprise menu, select Provisioning and Patching, then select Middleware Provisioning.

Select the Java EE Application procedure from the list and click Launch. You can also use the following method to launch the deployment procedure:

• Click Middleware from the Targets menu.

• Right click on a WebLogic Domain from the list and from the context sensitive menu, select Provisioning, then select Deploy / Undeploy Java EE Applications.

• In the Deployment Procedure Manager page, select the Java EE Application Provisioning procedure and click Launch.

In the Deploy/Undeploy Java EE Applications: Select Targets page, choose the Deploy operation.

Figure 17-1 Deploy / Undeploy Java EE Applications: Select Target

Select WebLogic Domains and select the targets on which the Java EE application is to be deployed. Click Add WebLogic Domains. Choose one or more WebLogic domains from the list and click Select.

The selected WebLogic domains are listed in the Targets table. Select the targets (clusters or managed servers) for each domain and click Next.

In the Deploy / Undeploy Java EE Applications: Select Applications page, add the archives and other related files that are to be deployed from the Software Library. Click Add to select one or more archives and other application related files or components from the Software Library. The Add Application popup is displayed. In the Component Name field, enter a file name or a wild card pattern to search for and retrieve components from the Software Library. Select the Show Java EE Application Components Only checkbox to list only the Java EE Application components in the Components in Software Library column. Select the archives and click the right arrow to move them to the Components Selected for Deployment section.

Figure 17-2 Deploy / Undeploy Java EE Applications: Add Applications

In the Type field, the type of each component is displayed. The Type can be:

• Archive: This is the archive file which can be a .ear, .war, .jar, or .rar file.

• Plan: This is an .xml file containing the deployment options for this application.

• Pre Deploy Script: This is a script containing WLST commands. The Management Agent runs this script on the Administration Server of each WebLogic domain before the application is deployed. You can use this script to create data sources, JMS end points, and any other resources that might be needed by the application that is being deployed.

• Post Deploy Script: This is a WLST script that is executed by the Management Agent on the Administration Server after the application is deployed. You can use this script to perform any post deployment configuration. For example, if you need to roll back and undo the changes made by the pre deploy script, you can select this option.

  Note:

  The archive, plan, predeploy, and postdeploy scripts can be moved only to the Administration Server.

• Additional File: You can add one or more files that will be required by the application that are not part of the application archive. These files can be of any type and can be moved only to the selected targets (managed servers and clusters).

• Target Execution Script: These scripts can be used to set up the required environment or replace tokens in the additional files like property files. These scripts will be executed on selected targets.

In the Location On Target field, for each component, specify the location on the WebLogic Server Host on which the application is to be deployed. This can be an absolute path or relative to the $WLS_HOME for the selected targets.

After selecting the required files for deployment, enter a unique name for the application and specify the Staging Mode which can be:

• Default: Each server in the WebLogic Domain maintains two attributes which are Staging Mode and StagingDirectoryName. The Staging Mode is the default staging mode for the server and StagingDirectoryName is the location on which the staged files are stored. Select this option to use the default staging mode for all the targets.

• Stage: Select this option if the archive files should be moved to the destination machine.

• No Stage: Select this option if the archive files should not be moved to the destination machine.

Select the Deploy this archive as library option if the application needs to be deployed as a shared library. You can select this option if one or more applications need the same set of files.

Select the Start Mode for deployment which can be:

• Start in full mode (servicing all requests): Select this option to make the deployed application available to all users.

• Start application in admin mode (servicing only administration requests): If you select this option, the deployed application is available only to the Administrator.

• Do not start: The application is deployed but not started. You can select this option if any manual post-deployment configuration is required.

Click OK to add the archive and return to the Select Applications page. You can add more archives or click Next to proceed. If you have added more than one archive, select the Skip on Failure checkbox to skip any failed deployments and continue deploying the remaining applications.

Click the Lock icon to lock the fields you have configured.

Click Next. Specify the credentials for each domain you have selected, the host on which the Administration Server is running, and the hosts to which the additional files or execution scripts are to be moved. You can choose:

• Preferred Credentials: This option is selected by default and the preferred credentials stored in the Management Repository are used. This option is available only if it has already been defined in Cloud Control.

• Named Credentials: A named credential specifies the authentication information for a user and can be a combination of username / password, public and private key pair, and can be used to perform provisioning, patching, run jobs, and other system management tasks.

• New Credentials: You can override the preferred credentials and specify a separate set of credentials for each host and WebLogic domain being deployed.

For more information on setting up the credentials, see the Enterprise Manager Security chapter in the Enterprise Manager Administration Guide.

Click the Lock icon to lock the fields you have configured. These fields cannot be edited once they are locked.

In the Schedule Deployment page, you can schedule the date on which the Java EE Application deployment procedure should be executed.

Click Next. On the Review page, review the details you have provided for the Deployment Procedure. If you are satisfied with the details, then click Submit to run the Deployment Procedure according to the schedule set. If you want to modify the details, click the Edit link in the section to be modified or click Back repeatedly to reach the page where you want to make the changes.

After you submit the deployment procedure, you will return to the Procedure Activity page where you can view the status of the Deployment Procedure. After the Java EE Application has been deployed, you can search for the target and navigate to the Target Home page.

From the Enterprise menu, select Provisioning and Patching, then select Middleware Provisioning.

Select the Java EE Application procedure from the list and click Launch. You can also use the following method to launch the deployment procedure:

• Click Middleware from the Targets menu.

• Right click on a WebLogic Domain from the list and from the context sensitive menu, select Provisioning, then select Deploy / Undeploy Java EE Applications.

• In the Deployment Procedure Manager page, select the Java EE Application Provisioning procedure and click Launch.

In the Select Targets page, choose the Redeploy operation.

Click Add WebLogic Domains to add one or more WebLogic domains. In the list of targets displayed, choose a target and click Select.

The deployment targets are listed in the Targets table. Select the applications that need to be redeployed and click Next.

In the Select Applications page, a list of applications that can be redeployed are displayed. Select an application and click Edit to modify the archive details and other application related files. In the Application Details window, enter a file name or a wild card pattern to search for and retrieve files from the Software Library. Select the archives and click the right arrow to move them to the Components Selected for Deployment section.

In the Type field, the type of each component is displayed. The Type can be:

• Archive: This is the archive file which can be a .ear, .war, .jar, or .rar file.

• Plan: This is an .xml file containing the deployment options for this application.

• Pre Deploy Script: This is a script containing WLST commands. The Management Agent runs this script on the Administration Server of each WebLogic domain before the application is deployed. You can use this script to create data sources, JMS end points, and any other resources that might be needed by the application that is being deployed.

• Post Deploy Script: This is a WLST script that is executed by Management Agent on the Administration Server after the application is deployed. You can use this script to perform any post deployment configuration. For example, if you need to roll back and ndo the changes made by the pre deploy script, you can select this option.

  Note:

  The archive, plan, predeploy, and postdeploy scripts can be moved only to the Administration Server.

• Additional File: You can add one or more files that will be required by the application that are not part of the application archive. These files can be of any type and can be moved only to the selected targets (managed servers and clusters).

• Target Execution Script: These scripts can be used to set up the required environment or replace tokens in the additional files like property files. These scripts will be executed on selected targets.

Review the default location on the target machine on which the component will reside. This can be an absolute path or relative to the $WLS_HOME for the selected targets.

After selecting the required files for deployment, enter a unique name for the application and specify the Staging Mode which can be:

• Default: Each server in the WebLogic Domain maintains two attributes which are Staging Mode and StagingDirectoryName. The Staging Mode is the default staging mode for the server and StagingDirectoryName is the location on which the staged files are stored. Select this option to use the default staging mode for all the targets.

• Stage: Select this option if the archive files should be moved to the destination machine.

• No Stage: Select this option if the archive files should not be moved to the destination machine.

Select the Start Mode for deployment which can be:

• Start in full mode (servicing all requests): Select this option to make the deployed application available to all users.

• Start application in admin mode (servicing only administration requests): If you select this option, the deployed application is available only to the Administrator.

• Do not start: The application is deployed but not started. You can select this option if any post-deployment configuration is required.

Specify the Retirement Policy for the application. You can select:

• Allow the application to finish its current sessions and then retire: Select this option if all the current sessions should be completed before retirement.

• Retire the previous version after retire timeout: Specify a timeout period after which the application will be automatically retired.

Click OK to add the archive and return to the Select Applications page. You can add more archives or click Next to proceed. If you have added more than one archive, select the Skip on Failure checkbox to skip any failed deployments and continue deploying the remaining applications.

Click the Lock icon to lock the fields you have configured. These fields cannot be edited once they are locked.

Click Next. Specify the credentials for each domain you have selected, the host on which the Administration Server is running, and the hosts to which the additional files or execution scripts are to be moved. You can choose:

• Preferred Credentials: This option is selected by default and the preferred credentials stored in the Management Repository are used. This option is available only if it has already been defined in Cloud Control.

• Named Credentials: A named credential specifies the authentication information for a user and can be a combination of username / password, public and private key pair, and can be used to perform provisioning, patching, run jobs, and other system management tasks.

• New Credentials: You can override the preferred credentials and specify a separate set of credentials for each host and WebLogic domain being deployed.

For more information on setting up the credentials, see the Enterprise Manager Security chapter in the Enterprise Manager Administration Guide.

Click the Lock icon to lock the fields you have configured. These fields cannot be edited once they are locked.

In the Schedule Deployment page, you can schedule the date on which the Java EE Application deployment procedure should be executed.

Click Next. On the Review page, review the details you have provided for the Deployment Procedure. If you are satisfied with the details, then click Submit to run the Deployment Procedure according to the schedule set. If you want to modify the details, click the Edit link in the section to be modified or click Back repeatedly to reach the page where you want to make the changes.

After you submit the deployment procedure, you will return to the Procedure Activity page where you can view the status of the Deployment Procedure. After the Java EE Application has been deployed, you can search for the target and navigate to the Target Home page.

From the Enterprise menu, select Provisioning and Patching, then select Middleware Provisioning.

Select the Java EE Application procedure from the list and click Launch. You can also use the following method to launch the deployment procedure:

• Click Middleware from the Targets menu.

• Right click on a WebLogic Domain from the list and from the context sensitive menu, select Provisioning, then select Deploy / Undeploy Java EE Applications.

• In the Deployment Procedure Manager page, select the Java EE Application Provisioning procedure and click Launch.

In the Select Targets page, choose the Undeploy operation.

Click Add WLS Domains to add one or more WebLogic domains. In the list of targets displayed, choose a target and click Select.

The deployment targets are listed in the Targets table. When an application is undeployed from the WebLogic domain, select the applications that need to be undeployed and click Next.

Click Next. Specify the credentials for each domain you have selected, the host on which the Administration Server is running, and the hosts to which the additional files or execution scripts are to be moved. You can choose:

• Preferred Credentials: This option is selected by default and the preferred credentials stored in the Management Repository are used. This option is available only if it has already been defined in Cloud Control.

• Named Credentials: A named credential specifies the authentication information for a user and can be a combination of username / password, public and private key pair, and can be used to perform provisioning, patching, run jobs, and other system management tasks.

• New Credentials: You can override the preferred credentials and specify a separate set of credentials for each host and WebLogic domain being deployed.

For more information on setting up the credentials, see the Enterprise Manager Security chapter in the Enterprise Manager Administration Guide

Specify the deployment schedule and click Next.

Review the details and click Undeploy. You will return to the Procedure Activity page where you can check the status.