Frequently Asked Questions
What is the difference between a system-locked element and a read-only element?
None. “System lock” is a term used to denote an element that has read-only files on the webMethods Integration Server. The server administrator usually applies system locks to files (makes them read-only).
Can I select multiple elements to lock or unlock in Package Navigator view simultaneously?
Yes, you can select multiple elements to lock or unlock in the Package Navigator view of Designer, as long as your selection does not contain the following:
A server
A folder or package
and its contents
A package and any other element
An adapter notification record
You can also lock or unlock all elements in a package or folder that have not been previously locked/unlocked by right-clicking the package or folder and selecting Lock or Unlock.
Where is the lock information (such as names of elements that are locked, and when they were locked) stored?
If you are using local service development, lock information is stored in the VCS repository only.
Important:
It is not recommended that you use locking and unlocking 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, during development to eliminate these issues.
Should I archive derived files?
Generally, you should not archive derived files such as the .class file that is generated when you compile a Java service.
What happens to the locks on elements when I replicate a package?
Locking information is not preserved when you replicate and publish a package. This is expected behavior and is part of the feature’s design. You can, however, preserve system locks (read-only file attributes).