Automated building and deployment framework for WebSphere Commerce products based on Agile Mode (3)

Source: Internet
Author: User
Tags resource

Deploying incremental Code Packs using the WebSphere Commerce build and Deployment Tool

The deployment mechanism of was

When deploying a customized resource through WCBD, WCBD will invoke the local was interface, communicate with the remote connection protocol to remote-end was, and invoke the deployment mechanism of remotely was to deploy, so understanding the deployment mechanism of was will help the reader understand how to deploy incremental code in essence Package. Was contains three deployment modes: Single file mode, multiple file mode, and module file mode. Package resources in different packages for different modes. The GUI interface for these three deployment patterns can be found in the administrative Console interface of was. This article will guide the reader through the configuration of WCBD to implement the deployment of applications running in the was environment on a command-line basis. The following is a brief description of the three deployment patterns supported by was.

Single file Mode

This pattern applies to simply updating a single file in an application. A single file can be any file in the ear, or it can contain a number of Command, a jar package for the Data Bean, or an updated JAVA code that can be considered for use with a single file deployment, as long as the files exist in the ear as a JAR package. It should be noted that the file cannot be an application module file type, such as an EJB module or a Web module.

Multi-file mode (partial application)

This mode is useful for updating or deleting multiple single files in an application. These files do not need to come from the same module. When deployed through a multiple-file schema, if the file does not exist in was, the file is added. If the file already exists, the file will be updated. In a multiple-file deployment model, all resources are lumped together and placed in a compressed file according to their respective directory structure. Packaging multiple application files includes the following three phases:

Create a directory to contain all the resources that need to be deployed, which will represent the root of the EAR.

Collect all the resources that need to be deployed and place them under the newly created root directory. The directory structure of a resource in this directory must be consistent with its directory structure in the JAVA EE application.

Package all resources into a single compressed file (. zip format)

Modular file mode (module files)

This pattern is useful for adding, updating, or deleting a module in an application. such as updating an entity's EJB module or updating a WAR package.

The WCBD deployment scripts are deployed in multiple-file mode and module file mode, requiring the user to configure the WCBD before initiating the deployment. This article will instruct readers to customize the WCBD script and consolidate the binary incremental code generated by the automated build module into the WCBD deployment script for automated deployment. Next we introduce how to configure WCBD and how to integrate WCBD into an automated framework.

The framework and WCBD of integrated automation construction

The automated build framework creates the resources for deployment for WCBD, WCBD gets the generated resource bundles and implements the deployment of the resource by calling the deployment mechanism of was, as shown in Figure 1. In order to integrate the Automation building framework with the WCBD, and to implement automated deployment of incremental code, the following steps need to be implemented:

Gets the WCBD deployment script. Based on this script, the deployment module is modified into an automated framework.

Configure the WCBD deployment package. The relevant parameters for the pre-deployment deployment are used for subsequent code deployment.

Modify the WCBD deployment script. Consolidate the incremental code packages generated by the automated build framework into WCBD deployment scripts, and allow the build framework master to start the WCBD deployment process for automated code deployment.

Figure 1. Build module and Deployment module run frame diagram

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.