Building a Project

In document webMethods Deployer Installation and Users Guide (Page 36-42)

Overview

You can create a project build using the Deployer interface or a command.

If a project build you create becomes out of sync with the current project definition, or if the build contains items that you know have changed on the source Integration Servers, you can rebuild the project build to bring it up to date. You can rebuild a project build using the Deployer interface or a command.

If you define and test deployment projects in a development environment, when you are ready to actually deploy the projects in your production environment, you will have to move the appropriate project builds to your production environment. You do this by exporting the builds from the development Deployer, copying them to the production environment, and importing them into the production Deployer. You can export and import a project build using the Deployer interface or a command.

Create a Project Build

Create a Build Using the Deployer Interface

1 In the Deployer, go to the Projects page.

2 In the Name column, click the name of the project for which you want to create a build.

3 The project definition contains items that existed on source Integration Server at the time you created the definition. To make sure the project does not contain items that have since been removed from source Integration Servers, synchronize the project definition with the source Integration Servers as follows:

a In the right pane, click .

b In the Deployment Sets area, under each deployment set, do the following:

1 If you added administration items to the set, click the Administration folder, then click Save.

2 If you added packages to the set, click the Packages folder, then click Save.

3 If you added Trading Networks items to the set, click the Trading Networks folder, then click Save.

Important! You must resolve all unresolved dependencies in a project before you can create a build for that project. If you try to create a build for a project that contains unresolved dependencies, the build process will fail. For instructions on viewing and resolving unresolved dependencies, see “Resolve Dependencies” on page 31.

To create a project build using the Deployer interface:

Create a Project Build

4 Click . The Deployer displays the Projects > project > Build page and lists all builds that exist for the selected project.

5 In the left pane, click Create Build.

6 In the Name box, type the name to use for the build. The name can be up to 32-characters long and can include any character that is valid for a file name in your operating system.

7 Click Create. The Deployer creates the build and stores it as a file in the Integration Server_directory/packages/WmDeployer/persist/projects/project_name/builds directory.

8 Click in the Build Report column in the right pane to view the build report. The build report tells you which items were successfully included in the build, describes any errors that occurred during the build process, and informs you if the project contains unresolved dependencies.

Create a Build Using a Command

The syntax for the CreateBuild command is as follows:

Note: The Status column on the Projects > project > Build page indicates whether each project build is in sync with the current project definition. If the build and the current project definition are in sync, the column shows . If the project definition has changed since the build was created, the column shows . You can rebuild such a project if you want. For instructions, see “Rebuild a Build” on page 38.

Important! If the project for which you are trying to create the build contains unresolved dependencies, you will receive a message to that effect and the build process will fail. For instructions on viewing and resolving unresolved dependencies, see “Resolve Dependencies” on page 31.

CreateBuild -h host -p port -u user -x password -r build_name -f project [-d]

Parameter Description

-h host -p port Host name or IP address and port for the Deployer host machine.

-u user -x password User name and password to use to log onto the Deployer.

-r build_name Name to use for the build. The name can be up to

32-C H A P T E R 5 B u i l d i n g a P r o j e c t

Rebuild a Build

The Status column on the Projects > project > Build page indicates whether each project build is in sync with the current project definition. If the build and the current project definition are in sync, the column shows . If the project definition has changed since the build was created, the column shows .

If a project build is out of sync with the current project definition or contains items that you know have changed on the source Integration Servers, and you want to recreate the build to bring it up to date, click in the Rebuild column for the build.

If you want to rebuild a build using a command, use the CreateBuild command as described in “Create a Build Using a Command”, above, and specify the name of the existing build on the -r build_name parameter.

Export and Import a Build

Export and Import a Build Using the Deployer Interface

1 Export the build from the development environment as follows:

a In the development Deployer, go to the Projects > project > Build page.

b Locate the build to export and click in the build’s Export column. The Deployer creates a file that contains the build. The file is named project_build and is stored in the Integration Server_directory\packages\WmDeployer\replicate\outbound folder.

2 Move the build into the production environment as follows:

a Copy the project_build file to the Integration Server_directory\packages\

WmDeployer\replicate\inbound directory on the machine that hosts the production Deployer.

b In the production Deployer, go to the Tools > Import Build page.

-f project Name of the project from which to create the build.

[-d] Optional. Tells the Deployer to write debug information to standard output. By default, standard output echoes to your console.

Parameter Description

To export and import a project build from the Deployer interface:

Export and Import a Build

c In the Project Build list, click the project_build file you just copied to the inbound directory.

d Click Import.

3 Use the production Deployer to map and deploy the build as described in the appropriate chapters in this guide.

Export and Import a Build Using Commands

The syntax for the ExportBuild command is as follows:

The syntax for the ImportBuild command is as follows:

ExportBuild -h host -p port -u user -x password -f project -r build -o {true|false} [-d]

Parameter Description

-h host -p port Host name or IP address and port for the Deployer host machine.

-u user -x password User name and password to use to log onto the Deployer.

-f project Name of the project from which the build you are exporting was created.

-r build Name of the build to export.

-o {true|false} Indicates whether to overwrite an existing project_build file, if there is one.

[-d] Optional. Tells the Deployer to write debug information to standard output. By default, standard output echoes to your console.

ImportBuild -h host -p port -u user -x password -r project_build [-d]

Parameter Description

-h host -p port Host name or IP address and port for the Deployer host machine.

-u user -x password User name and password to use to log onto the Deployer.

-r project_build Name of the file to import (project_build).

C H A P T E R 5 B u i l d i n g a P r o j e c t

C H A P T E R

6

Mapping a Project

Identify Target Integration Servers . . . 42 Map the Project to the Target Integration Servers . . . 42 Change Configuration Parameters for Deployed Items . . . 43

In document webMethods Deployer Installation and Users Guide (Page 36-42)