• No results found

Deploying a Project

Overview

You can deploy a project using the Deployer interface or using a command.

Deploy Using the Deployer Interface

1 If you chose to suspend triggers, ports, and scheduled tasks, but a service is triggered by one of these items before the Deployer suspends them, and the service is a long-running service, the Deployer might overwrite the service during deployment. Make sure long-running services have completed before you deploy.

2 In the Deployer, go to the Projects page.

3 In the Name column, click the name of the project you want to deploy.

4 In the right pane, click . The Deployer displays the Projects > project > Deploy page and lists all deployment candidates that exist for the selected project.

5 In the left pane, click Create Deployment Candidate.

6 In the Name and Description boxes, type the name to use for the deployment candidate and a brief description of the candidate. The name can be up to 32-characters long; the description length has no limit. Both name and description can include any character that is valid for a file name in your operating system.

7 In the Project Build list, click the project build to deploy.

8 In the Deployment Map list, click the deployment map that identifies the target Integration Servers to which to deploy the items in the selected project build.

To deploy a project using the Deployer interface:

Note: If the icon is not enabled, you have not successfully completed one or more of the preceding steps (that is, define, build, and map). You must complete those steps successfully before you can deploy the project. For instructions, see the chapters on those topics in this book.

Important! If the words Missing referenced items appears next to the map name in the list, it means that you resolved an unresolved dependency using the Exists option, but the Deployer found during the mapping task that the referenced item in fact does not exist on the target Integration Server. You can place the referenced item on the target Integration Servers, or you can return to the project definition stage and re-resolve the dependency in a different way (see “Resolve Dependencies” on page 31, step 4).

If you do not address the problem during the mapping task, the Deployer will write a message about the problem to the pre-deployment report. If you deploy without addressing the problem, the Deployer will not deploy the deployment set.

Deploy Using a Command

9 Click Create.

In the candidate list in the left pane, if the selected build and the current project definition are in sync, the Status column shows . If the project definition has changed since the build was created, the column shows . You can rebuild the project build before proceeding. For instructions, see “Rebuild a Build” on page 38.

10 Generate the pre-deployment report. To do so, in the Deployment Candidates list, click . The pre-deployment report appears in the right pane in the Pre-Deployment History area. Click in the Pre-Deployment Report column to display the report. The pre-deployment report contains information such as the following:

Items that will be suspended during deployment Items that will be enabled after deployment

Changes that will occur on the target Integration Servers, such as the items that will be added or overwritten, and configuration parameters that will be changed Messages about problems, such as unresolved dependencies

Read the report and address all problems.

11 Deploy the project. To do so, click in the Deploy column for the deployment candidate. The Deployer deploys the items in the selected project build to the target Integration Servers you identified in the selected deployment map.

The Deployer creates a deployment report and lists the report in the Deployment History area. Click in the Deployment Report column to display the report. The report contains similar information to the pre-deployment report, except that the events have actually occurred at this point.

Deploy Using a Command

The syntax for the Deploy command varies based on whether you are creating a new deployment candidate and deploying it or deploying an existing deployment candidate.

If you are creating a new deployment candidate and deploying it, the syntax for the Deploy command is as follows:

Important! If you do not address all problems at this time, you will probably experience errors during the deployment.

C H A P T E R 7 D e p l o y i n g a P r o j e c t

If you are deploying an existing deployment candidate, the syntax for the Deploy command is as follows:

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 Name of the project from which the build you are deploying was created.

-n new_candidate_name Name to use for a new deployment candidate.

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.

-s new_candidate_description Brief description of the new deployment candidate. The description length has no limit and can include any character that is valid for a file name in your operating system.

-b build Name of the project build to deploy.

-m map Name of the deployment map that identifies the target Integration Servers to which to deploy the items in the selected project build.

-l {true|false} Tells the Deployer to either generate the pre-deployment report (true) or to deploy the deployment candidate (false).

[-d] Optional. Tells the Deployer to write debug

information to standard output. By default, standard output echoes to your console.

Deploy -h host -p port -u user -x password -e candidate -r project -l {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.

-e candidate Name of an existing deployment candidate to deploy.

Deploy Using a Command

-r project Name of the project from which the build you are deploying was created.

-l {true|false} Tells the Deployer to either generate the pre-deployment report (true) or to deploy the deployment candidate (false).

[-d] Optional. Tells the Deployer to write debug

information to standard output. By default, standard output echoes to your console.

Parameter Description

C H A P T E R 7 D e p l o y i n g a P r o j e c t

Index

administration items, add to deployment sets 25

authorize security groups to perform tasks 20

B

Brokers, synchronize deployed document types with 29

build file name and location 37 build projects, overview 10 builds

create using a command 37

create using the Deployer interface 36 export and import using the Deployer

interface 38

by copying an existing project 18 by creating a new project 18 overview 8

CreateBuild command 37

D

define projects, overview 9

delete files from existing packages on target Integration Servers 28

to target Integration Server not accessible to the local Integration Server 38

I n d e x

add package components to 26 add package files to 27

add Trading Networks items to 31 create 24

overview 9

resolve dependencies in 32 unresolve dependencies in 33

document types, synchronize with Brokers 29 documentation

additional 6 conventions used 5 feedback 6

E

enable deployed ports and scheduled tasks 20 export builds

using a command 39

using the Deployer interface 38 ExportBuild command 39

H

hardware requirements for the Deployer 14 home page, create and view 21

I

deploy to targets not accessible to local Integration Server 38

identify sources 15, 24 identify targets 15, 42 items

add administration items to deployment sets 25

add entire packages to deployment sets 26

add package components to deployment sets 26

add package files to deployment sets 27 add Trading Networks items to deployment

sets 31

operating systems supported by the Deployer 14

overwrite existing project items on target Integration Servers 19

P

packages

activate after deployment 29

add entire packages to deployment sets 26 add package components to deployment

sets 26

add package files to deployment sets 27 delete files from existing packages on targets

Integration Server 28 set properties for 29

parameters, change for deployed items 43 platforms supported by the Deployer 14 pre-deployment report, generate 47

program code conventions in this document 5 project build file name and location 37 projects

authorize security groups to perform tasks 20

build using a command 37

build using the Deployer interface 36 build, overview 10

Index

create by copying an existing project 18 create by creating a new project 18 create home page for 21

create, overview 8 define, overview 9

deploy on target Integration Server not accessible to the local Integration Server 38

deploy using a command 47

deploy using the Deployer interface 46 deploy, overview 11

enable deployed ports and scheduled tasks 20

generate pre-deployment report 47 map 42

map, overview 10

overwrite existing project items on target Integration Servers 19

rebuild 38

set properties for 19

suspend operationg of existing items on target Integration Servers during

security groups, authorize to perform tasks 20 source Integration Servers, identify 15, 24

suspend operation of existing items on target Integration Servers during deployment 19 synchronize deployed document types with

Brokers 29

T

target Integration Servers, identify 15, 42 Trading Networks items, add to deployment

sets 31

troubleshooting information 6

typographical conventions in this document 5

U

webMethods components required by Deployer 14

X

XML file, project definition 9

I n d e x

Related documents