Identify Source Integration Servers
1 In the Deployer, go to the Projects page.
2 In the Name column, click the name of the project you want to define.
3 In the right pane, click .
4 Click Source Servers. In the right pane, the Deployer lists all remote servers defined to the Integration Server that hosts the Deployer.
5 In the Select column, select the check box next to each Integration Server that contains items you want to add to the project.
6 Click Save.
7 Make sure every Integration Server you identified as a source is equipped with the Deployer resource package. To do so, go to the Tools > Servers page and check whether the Resource Package column displays the word Installed for those Integration Servers.
If the column does not show that word, you must install the resource package on the Integration Servers. In the Install column, select the check box next to each Integration Server you identified as a source, then click Install.
Create a Deployment Set
You can add administration items, packages, and Trading Networks items to a deployment set. As you add items to a set, the Deployer might find that some items require other items that you have not added to the deployment set, and you will have to resolve these dependencies.
1 On the Deployer Projects > project > Define page, click Create Deployment Set.
2 In the Name and Description boxes, type the name to use for the deployment set and a brief description of the set. 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.
3 Click Create.
To identify source Integration Servers:
Note: If Integration Servers you want to use as sources do not appear in the list, you must define them as remote servers to the host Integration Server. This includes the host Integration Server; if you want to use the host Integration Server as a source, you must define it as a remote server to itself. For instructions, see the webMethods Integration Server Administrator’s Guide.
To create a deployment set:
Create a Deployment Set
Add Administration Items to the Deployment Set
1 In the Deployment Sets area, under the deployment set to which to add administration items, click the Administration folder. The Deployer lists all Integration Servers you identified as source Integration Servers in the right pane.
2 In the right pane, open the tree to show the administration items on the source Integration Servers.
3 Select the check box next to each item to add to the deployment set.
4 Click Save. The Deployer shows your choices in the left pane under the Administration folder for the deployment set.
5 If you are not going to add any more items to the deployment set, go to “Resolve Dependencies” on page 31.
Add Packages to the Deployment Set
When you add a package to the deployment set, you can do one of the following:
Add the package in its entirety
Add selected package components only Add selected package files only
A package from which you have added selected components or files only is called a partial package. You can add both entire packages and partial packages to a deployment set.
To add administration items to the deployment set:
Important! If you add a scheduled task to the deployment set, the task requires the user that is specified on the scheduled task on the runAsUser parameter. If the user does not already exist on the target Integration Servers, you must add it to the deployment set. If you do not, the Deployer will deploy the task but will not activate it, even if you chose to activate scheduled tasks on the Activate After Deployment project property.
Important! If you add a port to the deployment set, the port requires the package that contains the port’s configuration. If the package does not already exist on the target Integration Servers, you must add it to the deployment set. If you do not, the target Integration Servers will throw exceptions during deployment and the Deployer will not deploy the port.
C H A P T E R 4 D e f i n i n g a P r o j e c t
you would deploy the files that make up the new service and delete the files that make up the old service.
Add an Entire Package to the Deployment Set
1 In the Deployment Sets area, under the deployment set to which to add packages, click the Packages folder. The Deployer lists all Integration Servers you identified as source Integration Servers in the right pane.
2 In the right pane, open the tree to show the packages on the source Integration Servers.
3 Select the check boxes next to the packages you want to add in their entirety.
4 Click Update. The Deployer shows the entire package icon ( ) in the left pane under the Packages folder for the deployment set. The Deployer also shows the entire package icon for selected packages in the package list in the right pane, and the check boxes next to the packages are marked with a black check mark.
5 If you are done adding packages to the deployment set, go to “Set the Package Properties” on page 29.
Add Package Components to the Deployment Set
1 In the Deployment Sets area, under the deployment set to which to add package components, click the Packages folder. The Deployer lists all Integration Servers you identified as source Integration Servers in the right pane.
2 In the right pane, open the tree to show the packages on the source Integration Servers.
3 Click the name of a package that contains components you want to add to the deployment set.
To add an entire package to the deployment set:
Important! If you add a port to the deployment set, the port requires the package that contains the port’s configuration. If the package does not already exist on the target Integration Servers, you must add it to the deployment set. If you do not, the target Integration Servers will throw exceptions during deployment and the Deployer will not deploy the port.
Important! You can select package components to add to the deployment set, or you can select package files to add to a deployment set, but you cannot select both. If you select components, then later select files, the Deployer will add the file selections to the deployment set and remove the component selections.
To add package components to the deployment set:
Create a Deployment Set
4 In the Select Components area, open the tree to show the components in the package.
5 Select the check box next to each component to add to the deployment set.
6 Click Save.
7 Click Return to Package List. The Deployer shows the partial package icon ( ) in the left pane under the Packages folder for the deployment set. The Deployer also shows the partial package icon for the selected package in the package list in the right pane, and the check box next to the package is marked with a gray check mark (as opposed to the black check mark used for selected entire packages).
8 If you are done adding packages to the deployment set, go to “Set the Package Properties” on page 29.
Add Package Files to the Deployment Set
1 In the Deployment Sets area, under the deployment set to which to add package files, click the Packages folder. The Deployer lists all Integration Servers you identified as source Integration Servers in the right pane.
2 In the right pane, open the tree to show the packages on the source Integration Servers.
3 Click the name of a package that contains files you want to add to the deployment set.
4 Click Select Files. The Deployer lists all files in the package.
5 Do one of the following:
Note: If you later decide you want to include the entire package (as opposed to selected components only), cancel the selection of the components by clearing the appropriate check boxes, then save the deployment set, and then select the entire package as explained in “Add an Entire Package to the Deployment Set” on page 26.
Important! You can select package files to add to the deployment set, or you can select package components to add to a deployment set, but you cannot select both. If you select files, then later select components, the Deployer will add the component selections to the deployment set and remove the file selections.
To add package files to the deployment set:
If you want to add... Action All the files in the list Click All files.
C H A P T E R 4 D e f i n i n g a P r o j e c t
6 If a package of the same name as this partial package already exists on one of the deployment set’s target Integration Servers, and the existing package contains files you want to delete after deployment, type the fully qualified names of the files to delete in the Files to Delete from Target Package box. Type each file name on its own line, and end each line with a semicolon (;). For example:
code/classes/wm/administratorResource/admin.class;
code/classes/wm/administratorResource/user.class;
ns/wm/administratorResource/
7 Click Save.
8 Click Return to Package List. The Deployer shows the partial package icon ( ) in the left pane under the Packages folder for the deployment set. The Deployer also shows the partial package icon for the selected package in the package list in the right pane, and the check box next to the package is marked with a gray check mark (as opposed to the black check mark used for selected entire packages).
9 If you are done adding packages to the deployment set, go to “Set the Package Properties” on page 29.
Only files other than those you select in the list
Click All except selected files, then press the CTRL button and click each file to not add to the deployment set.
All files in the list whose name contains a specified string
Click Files specified by filter, then type the string on which to match. You can use an asterisk (*) as a wild card (for example, *.java or *.class).
All files in the list whose name does not contain a specified string
Click All except files specified by filter, then type the string on which to match. You can use an asterisk (*) as a wild card (for example, *.java or *.class).
If you want to add... Action
Note: If you later decide you want to include the entire package (as opposed to selected files only), cancel the selection of the files by navigating to the file selection page and clicking None, then save the deployment set, and then select the entire package as explained in “Add an Entire Package to the Deployment Set” on page 26.
Create a Deployment Set
Set the Package Properties
You must set the package properties for each package you added to the deployment set.
1 In the Deployment Sets area, under the deployment set to which you added entire or partial packages, click a package name.
2 In the Package Type area, indicate how the Deployer should proceed if it finds that the source package already exists on target Integration Servers. You can use either option below for both entire and partial packages.
Whether the Deployer actually deploys depends on the version numbers of the source package and the existing package. If the source package’s version number is the same or higher than the existing package’s version number, the Deployer deploys. If the source package’s version number is lower than the existing package’s version
number, the Deployer does not deploy. The version number the Deployer uses for the source package in the comparison is the number in the Version box in the Package Information area (see step 6).
3 In the Recommendations for Target area, you can recommend the minimum version of Integration Server and Java Virtual Machine (JVM) to run the source package. If the JVM version on the target Integration Server is lower than you specify here, the Deployer will deploy the source package but will not activate it, regardless of the setting of the Activate After Deployment option, and the target Integration Server will display a warning about the JVM version. The defaults shown in this area reflect the Integration Server and JVM that host the source package.
4 For the Activate After Deployment option, indicate whether the Deployer should enable the package on the target Integration Servers after deploying it. You might choose to not enable a package automatically after deployment if the deployed package is intended to replace another package of a different name, but not immediately.
5 In the Sync Documents option, indicate whether to synchronize the document types in To set properties for a package:
If you want the Deployer to... Click...
Deploy the source package over the entire existing package Full Deploy the components and files in the source package over the
corresponding components and files in the existing package
Upgrade
Note: Before you deploy a project, you can find out which items the Deployer will overwrite by generating the pre-deployment report.
C H A P T E R 4 D e f i n i n g a P r o j e c t
If you set this option to Yes, and a Broker that is connected to a target Integration Server is not available, the Deployer deploys the document types on the target Integration Server but cannot synchronize them with the Broker. The Deployer also writes a message to this effect to the deployment report.
If you set this option to No, the Deployer deploys the document types on the target Integration Servers but does not synchronize them with connected Brokers. You will have to synchronize document types with the Brokers manually after deployment.
6 The Package Information area shows values as they have been recorded (if they have been recorded) in Integration Server Administrator and Developer for the source package. You can assign different values.
In the Version box, you can supply the version number to use for the source package in comparisons with existing packages on target Integration Servers, as described in step 2. The Deployer stores this version number in project builds and assigns it to the deployed package on the target Integration Servers.
If you chose the Full option in the Package Type area (see step 2), you can complete the boxes listed below as follows:
7 Click Save.
8 Repeat these steps for each package in the deployment set.
9 If you are not going to add any more items to the deployment set, go to “Resolve Dependencies” on page 31.
Note: The Deployer can detect Broker unavailability when you generate the pre-deployment report and will write a message advising you of the problem to the report.
Note: The version number for the source package on the source Integration Server is not affected by your entry here.
Box Entry
Build You can supply the build number to assign to the deployed package on the target Integration Servers.
Patches
Included You can supply the list of patches that have been applied to the deployed package on the target Integration Servers. Specify the patch numbers, separated by commas (for example, 44, 45, 55).
Brief
Description You can supply a description to use for the deployed package on the target Integration Servers (for example, “December 2003 release with patches to correct OrderProcess problem.”)
Create a Deployment Set
Add Trading Networks Items to the Deployment Set
When you deploy Trading Networks items to an Integration Server, the Deployer updates the Trading Networks database that is connected to the Integration Server with the deployed items. When defining a project that includes deploying Trading Networks items to a clustered environment, then, keep in mind that you can deploy the items to only one Trading Networks-equipped Integration Server in the cluster. Do not deploy to multiple Integration Servers in the network, or you will experience unpredictable results.
1 In the Deployment Sets area, under the deployment set to which to add Trading Networks items, click the Trading Networks folder. The Deployer lists all Integration Servers you identified as source Integration Servers in the right pane.
2 In the right pane, open the tree to show the Trading Networks items on the source Integration Servers.
3 Select the check box next to each item to add to the deployment set.
4 Click Save. The Deployer shows your choices in the left pane under the Trading Networks folder for the deployment set.
5 If you are not going to add any more items to the deployment set, go to “Resolve Dependencies”, below.
Resolve Dependencies
Administration items, packages, and Trading Networks items often require other items.
For example, a user-defined ACL requires all user-defined groups associated with the To add Trading Networks items to the deployment set:
Important! If you add a processing rule from a 6.0.1 Trading Networks to a deployment set, the processing rule might require custom contact types. If the custom contact types do not already exist on the target Integration Servers, you must add them to the deployment set. If you do not, the Deployer will log an error to the deployment report and the processing rule will not be deployed. (This is not an issue when adding processing rules from a 6.1 Trading Networks.)
If you add a Trading Networks document type with the Duplicate Checking option set to Use Custom Service, the Deployer does not detect the dependency on the service. If the service does not already exist on the target Integration Servers, you must add the service to the deployment set. If you do not, the Deployer will log an error to the deployment report and will not deploy the document type.
C H A P T E R 4 D e f i n i n g a P r o j e c t
referenced items but they are all included in the deployment set, the Deployer shows a in the Dependencies column for the deployment set in the left pane. If there are referenced items and some of them are not included in the deployment set, the Deployer shows in the Dependencies column for the set and considers the deployment set to have unresolved dependencies. You must resolve all unresolved dependencies before you can continue to the next task (that is, the project build task).
If necessary, you can later un-resolve a dependency you have resolved and re-resolve it a different way.
The Deployer cannot always detect all dependencies. If you are aware that an item has a dependency on a package component, and the Deployer has not detected this
dependency, you can manually add that dependency.
1 In the Dependencies column for the deployment set, click Edit. The Deployer shows all unresolved dependencies on the Unresolved Dependencies page. The Referenced Item column lists the missing referenced items. The next column offers the possible ways you can resolve the unresolved dependency. The Project Item column shows the dependent items.
2 Tell the Deployer how to resolve each unresolved dependency as described below. If you want to resolve all items in a folder the same way, you can set the resolution at
2 Tell the Deployer how to resolve each unresolved dependency as described below. If you want to resolve all items in a folder the same way, you can set the resolution at