To ensure that other users with provisioning permissions cannot modify your setup, you can lock:
- A specific artifact (for examplee.g., a virtual asset, virtual asset deployment, JDBC controller, message proxy, test scenario, file, or provisioning action)
- A component, including component—including all associated artifacts
- A complete environment, including environment—including all associated components and all artifacts used in those components
Any user with provisioning permissions (for examplee.g., a provision, system, or admin-level user) can add locks and unlock any lock that he or she locked.
...
- An entire component was locked in CTP,
- A locked asset will interfere with provisioning, or
- You have direct control over the lock (for examplee.g., you are able to unlock it)
...
If a component instance cannot be provisioned due to a locked asset (for examplee.g., another user locked the entire component or locked a virtual asset deployment used in the selected component instance), a lock icon will be added that instance's label. A tool tip indicates who added the lock and what asset is locked.
...
Locking/Unlocking a Component
Locking
To lock a component as component—as well as lock all artifacts that used in that component and all of that component's instances:
- With the environment diagram in regular (not Edit) mode, select the component, then click the the Lock in the toolbar.
Anchor whatiflocked whatiflocked
...
To unlock a component that you previously locked as locked—as well as unlock the associated artifacts and component instances that you previously locked:
...