Setting Up Aliases for Source and Target Servers
You set up aliases for both source and target servers or only target servers, target groups, and source repositories in the <Environment> tag. For example:
<Environment>
<{webMethods
Broker|ProcessModel|IS|MWS|Optimize|EventServer|RulesServer|EDA|APIGateway|MFT
|DES|UniversalMessaging|TargetGroup|Repository}>
<{broker|pm|is|mws|optimize|eventserver|rulesserver|edaserver|
universalmessaging|rep}alias>
tags
</{broker|pm|is|mws|optimize|eventserver|rulesserver|edaserver|
universalmessaging|rep}alias>
</{webMethods Broker|ProcessModel|IS|MWS|Optimize|EventServer|RulesServer|EDA|
UniversalMessaging|TargetGroup|Repository}>
</Environment>
The following sections describe each tag within the <Environment> tag in detail.
If Deployer already contains an alias with the same name as one you define, Deployer overwrites the alias.
Note: The credentials for <user>, <pwd>, and <pwdHandle> asset tags must be those for a user with Administrator ACL authorization or for a user that belongs to a group that has Internal, Developer, and Deployer Admin ACLs to create Deployer runtime aliases and projects.