Deploying an Application

You use the deploy command to deploy an application archive to an AppSpace.

You can deploy multiple applications to an AppSpace. You can deploy and run multiple versions of same application on the same AppNode at the same time.

bwadmin Command Line

When using the deploy command, the EAR filename is the relative location of the archive with respect to the BW_HOME\domains\domain_name\archives folder. For example, if MyDomain contains the AppSpace to deploy to and the archive file is located in the BW_HOME\domains\MyDomain\archivesdirectory, do not specify a qualifier for the archive file location.

Execute the following command from the command line to deploy an uploaded application archive to MyAppSpace: 

BW_HOME\bin>bwadmin deploy -d MyDomain -a MyAppSpace tibco.bw.sample.binding.rest.BookStore.application_1.0.0.ear

Replacing a deployed archive file will undeploy the application. To replace an archive file that has been uploaded, but not deployed, use the -replace option with the upload command to upload the archive again. When the -replace option is used to replace an archive file that has been uploaded and deployed, the following error message is displayed, 
Upload Operation Cancelled. As Application MyApplication from archive MyApplication.ear has been deployed to those AppSpaces. 
Please use force replace (-f)option with the upload command i.e 
[upload -domain D -replace -f C:/Users/Administrator/Desktop/EAR/MyApplication.ear]]
The force replace option will undeploy the existing archive file and replace the old archive file with the new file.

Admin UI

Procedure

  1. Select the domain and open the Application Archives page. Drill down into an archive. On the Application Archive page for the selected archive, click the Deploy button.
  2. In the Deploy Application dialog box, enter the following information:
    • AppSpace: The AppSpace to deploy to.
    • Profile: The profile file to use for deployment. (An application profile can be changed after deployment. See Configuring an Application. Click Upload to upload a new profile.
    • Start applications on AppNodes after deployment: Starts the application on AppNodes after deployment.
    • Replace any existing version: Replaces an existing version of the same application. If the Replace any existing version check box is selected, a warning message is displayed, indicating that the upload action will undeploy the existing application from the Appspace.
      Note: If the EAR file is uploaded but not deployed, the warning message is not displayed and the EAR file is replaced.
    • App name/Version: Read-only fields that display the application name and version.
    • Description: Optional description; pulled from archive.

    The archieved applications are displayed on the Application Archives page. The Deployed To column displays the number of AppSpaces where the application has been deployed.

    To view deployment history of the application archive, open the Deployment History tab. You can view the commands that were issued on an application archive, the execution status of the commands and the timestamp.

    To view multiple versions of the same application, open the Applications page.