Remote Server Configuration. It is not recommended that you use Cooperative Development functionality in an Integration Server cluster. Locking information for elements could be inadvertently shared with another Integration Server in the cluster. Use a standalone Integration Server not a cluster, while developing to eliminate these Cooperative Development problems.

Server User Names. When logging on to the Integration Server, use a distinct user name. Locking is based on your user name, so it is important that each user log on to the server with a unique user name (not “Administrator” or “Developer”).

Package Replication and Publishing

Always back up your packages every day or night using package replication and publishing. Because locking information does not travel with packages (or partial packages) when they are replicated, it is recommended that you apply a version to each package according to date. Do not replace or overwrite packages; delete the old package entirely and then install the new package.

When you replicate and publish a package, the locking information is not preserved. This is expected behavior and is part of the feature's design. You can, however, preserve system locks (read-only file attributes).

Before you publish a package, keep in mind that user locks are not preserved.

When you salvage a deleted package, lock information is not preserved. Before you salvage or delete a package, make sure that all locks are removed from the destination package.

Package and Folder Organization. Use a single package or folder per developer or per Java/C service.

Source Code. If there has been a significant change to the source code, always reload the package to reflect the latest system locks.

Upgrading IBM webMethods Integration Server. When you upgrade the IBM webMethods Integration Server to a new version, you lose all lock information. Therefore, before upgrading, make sure that all locks are removed and all changes are saved.