Migrating Custom Packages
You can migrate the custom packages created in webMethods Microsoft Package 7.1 to use these custom packages in webMethods Microsoft Package 9.0.
To migrate custom packages created in
webMethods Microsoft Package 7.1 to
webMethods Microsoft Package 9.0
1. Shut down the host Integration Server.
2. Set the dependency on the custom packages you want to migrate by editing the manifest.v3 file. The manifest.v3 file is located in the same folder as your custom package.
Go to the folder of each custom package that you want to migrate, and edit the requires tag in the manifest.v3 file, as shown below:
3. To migrate the services with assembly path set as Mapped Drives or Shared UNC Paths, follow the directions below:
If your custom package consists of .NET services that refer to Mapped Drives as their assembly path, move those DLLs to local system drives, and update the Assembly Path property from Designer.
If your custom package consists of .NET services that refer to Shared UNC Path as their assembly path, run the windows service named
webMethods Package for Microsoft .NET with Administrator user account (who has privileges to access the shared paths) and then migrate the .NET services.
4. Start the host Integration Server and verify that the dependency has been set correctly by doing the following:
a. Go to Integration Server Administrator, and select Packages > Management.
b. Select your custom package from the Package List.
c. Verify that the value for Packages on which this package depends is WmDotNet;9.0.
5. Start Designer and run the service pub.dotnet.migration:upgradeDotNetServices.
Verify that the service output is as follows:
6. Open wmSystem.exe.config file from Software AG_directory /DotNetHost folder.
Verify that the value of the
WhitelistDirectories element is updated correctly. For information on white-listed directories, see
Specifying white-listed directories.
The migrated custom packages can now be used with webMethods Microsoft Package 9.0.