Before Migrating Deployer Settings, Server Aliases, Target Groups, and Projects
1. Make sure you have upgraded all source and target product servers that were defined in the old Deployer to their 9.9 releases, and have migrated all product data and assets to the 9.9 releases, as instructed in this guide.
2. Make sure you have upgraded the Integration Server 9.9 that hosts Deployer 9.9 and migrated its data using the instructions in this guide.
3. Make sure you are a member of the Administrators ACL, or of the Internal, Developer ACLs, and DeployerAdmin ACLs, for both the Integration Server that hosts the old Deployer and the Integration Server that hosts Deployer 9.9. For instructions, see webMethods Integration Server Administrator’s Guide 9.9.
4. In the old Deployer, edit all connections to old source and target product servers to point to the new 9.9 source and target product servers. You do not have to supply user names and passwords if you do not know them.
5. If you installed Deployer 9.9 on the same machine as the old Deployer, you might want Deployer 9.9 to use the ports that were used by the old Deployer. If so, do the following:
a. In Integration Server Administrator, point to the Integration Server that hosts the old Deployer and go to the Security > Ports page.
b. Click Add Port, click webMethods/HTTP, and click Submit. Enter the port details, click Yes for Enable, click WmRoot under the package name, and click Save Changes.
c. Click Change Primary Port, click the new port, and click Update.
d. In the Access Mode column of the new port, click Edit. In the Edit Access Mode page for the port, click Set Access Mode to Allow by Default. Click OK on the warning pop-up. The message Successfully changed access mode for Port Service Access Settings appears.
e. Disable the old port by clicking Yes in the Enabled column for that port.
Contact Support
|
Community
|
Feedback