webMethods Deployer 10.3 | webMethods Deployer Documentation 10.3 | Mapping a Project | Mapping a Project to Target Servers and Target Groups
 
Mapping a Project to Target Servers and Target Groups
You can map a project to individual target servers, target groups, or both.
* To map a project to target servers
1. In Deployer, go to the Deployer > Projects page.
2. If locking is enabled, in the Lock Status column for the project, click to lock the project.
3. In the Name column, click the project.
4. In the right-hand pane, click  Map. Deployer displays the Projects > project > Map page and lists all maps that exist for the selected project.
5. In the left-hand pane, click Create Deployment Map.
6. In the Name box, accept the default deployment map name or replace it with a name that you choose. The name can be up to 32 characters long and cannot contain spaces or the following illegal characters:
$ ~ / \ # & @ ^ ! % * : ; , + = > < ‘ ’ "
7. In the Description box, type a description for the map. The description length has no limit and can include any characters.
8. Click Create.
9. Under the Deployment Map Topology area, in the Set Mapping column for a deployment set, map to the target servers to which to deploy the assets, as follows:
To add a...
Do this...
Individual target server
Click Add Target Server and then perform one of the following:
*For runtime-based projects, select the check box next to each target server to which to deploy the assets in the deployment set and then click Add.
*For repository-based projects:
i. In the Select Server list, click the runtime type of the target server.
ii. Select the check box next to each target group to which to deploy the assets in the deployment set and then click Add.
Notes:
*For runtime-based projects, Deployer lists only those servers running compatible versions for selection as target servers. Repository-based deployment does not support mapping to target servers of versions that are different than the source repository. For information about selecting the versions of source servers, see Connecting to webMethods Servers.
*If you are mapping a repository-based project that contains BPM ProcessModels, you must also select the physical Integration Server servers or My webMethods Servers for each logical server in the deployment set from the Map Logical Servers area of the Add Targets pane.
*If a server you want to map to does not appear in the list, you have not yet set it up to work with Deployer. For instructions, see Starting Deployer and Connecting to Servers. Then click Refresh this Page to update the list of servers on this page.
Note: When you deploy Trading Networks assets, Deployer updates the Trading Networks database with the deployed assets. If Trading Networks is installed on multiple Integration Servers, map deployment sets that contain Trading Networks assets to only one of the Integration Servers. Do not map to multiple Integration Servers or you will experience unpredictable results when you deploy.
Target group
Click Add Target Group and then perform one of the following:
*For runtime-based projects, select the check box next to each target group to which to deploy the assets in the deployment set and then click Add.
*For repository-based projects:
i. In the Select Server list, click the runtime type of the target server.
ii. Select the check box next to each target group to which to deploy the assets in the deployment set and then click Add.
Notes:
*For runtime-based projects, Deployer lists only those target groups whose version is compatible with the source servers in the deployment set. Repository-based deployment does not support mapping to target servers of versions that are different than the source repository. For information about selecting the versions of source servers, see Connecting to webMethods Servers.
*If you are mapping a repository-based project that contains BPM ProcessModels, you must also select the physical Integration Server servers or My webMethods Server target groups for each logical server in the deployment set from the Map Logical Servers area of the Add Targets Groups pane.
10. If you are mapping a runtime-based deployment deletion set, under the Deployment Map Topology area, in the Set Mapping column, follow the instructions in the previous step, but map to the target servers from which to delete the assets. The important note is also true for deletion sets.
11. When Deployer returns to the map > Properties page, the Deployment Map Topology area might show or .
*For repository-based deployment projects, Deployer verifies whether the target servers or target groups are available for deployment when you add them to the deployment map. The Status column shows if the server is available for deployment and if it is not.
*For runtime-based deployment sets, appears in the Referenced Assets column and indicates that you resolved an unresolved dependency using the Exists option, but Deployer has found that the referenced asset does not exist on target servers. Click to see the missing referenced asset. You can then place the referenced asset on the target servers, or you can return to the project definition stage and re-resolve the dependency in a different way. For more information, see Resolving Dependencies (for runtime-based deployment).
*For deletion sets, dependencies work in the opposite direction from deployment sets. Deployer finds all assets on the target servers that depend on assets in the deletion set. If you were to delete the assets in the deletion set from the target servers, the dependent assets would no longer work properly. On the map >Properties page, in the Deployment Map Topology area, therefore, the icon appears in the Dependent Assets column, and indicates that dependent assets exist. Click to see the dependent assets, then choose whether to Add the dependent assets to the deletion set or to Remove the assets they depend on from the deletion set.
Note: Keep the following points in mind when working with dependencies:
*Deployer cannot detect dependencies across products. Make sure assets you want to delete are not required by assets of other products.
*If you do not address problems at this time, Deployer will write messages about them to the simulation report. If you deploy without addressing problems, Deployer will not deploy the assets identified in the deployment set or delete the assets identified in the deletion set.
12. If you are mapping a runtime-based deployment or deletion set and you resolved dependencies in the previous step, the contents of the deletion set have changed. As a result, you must rebuild the project (see Rebuilding a Build). If you exported the deletion set definition or the project build, you must also re-export the definition (see Exporting and Importing Deletion Set Definitions) and the build (see Exporting and Importing a Build).
Copyright © 2013-2018 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.