ODI provides two methods for handling concurrent changes:
• Concurrent Editing Check:
– Set this user parameter to true to prevent you from erasing the work performed by another user.
– If another user has made changes, the object cannot be saved.
• Object Locking:
– Automatically activated.A pop-up window appears to ask if you want to lock the object.
– Manual locking
Several users can work simultaneously in the same ODI project or model. They may all be
connected to the same repository and so the changes they perform are considered concurrent.
ODI provides two methods for handling these concurrent changes: Concurrent Editing Check
and Object Locking. These two methods can be used simultaneously or separately.
• Concurrent Editing Check: A user parameter, check for concurrent editing, can be set to true to prevent you from erasing the work performed by another user on the object that you try to save. If this parameter is set to true, when you save changes to any object, ODI checks whether other changes have been made to the same object by another user since you opened it. If another user has made changes, the object cannot be saved, and you must cancel your changes.
• Object Locking
- Automatic Object Locking. This mechanism is automatically activated. When an object is opened in a user interface, a pop-up window appears to ask if you want to lock the object. As long as an object is locked, only the user owning the lock can modify the object, such as editing or deleting. Other operations, such as executing,can be performed by other users, but with a warning. An object locked by you appears with a yellow lock icon. An object locked by another object appears with a red lock icon. When the editing window is closed, a pop-up window appears to ask
if you want to unlock the object.
- You can also manually manage locks on objects. To manually lock an object,
select the object in the tree view, right-click and select Locks > Lock.
• Concurrent Editing Check:
– Set this user parameter to true to prevent you from erasing the work performed by another user.
– If another user has made changes, the object cannot be saved.
• Object Locking:
– Automatically activated.A pop-up window appears to ask if you want to lock the object.
– Manual locking
Several users can work simultaneously in the same ODI project or model. They may all be
connected to the same repository and so the changes they perform are considered concurrent.
ODI provides two methods for handling these concurrent changes: Concurrent Editing Check
and Object Locking. These two methods can be used simultaneously or separately.
• Concurrent Editing Check: A user parameter, check for concurrent editing, can be set to true to prevent you from erasing the work performed by another user on the object that you try to save. If this parameter is set to true, when you save changes to any object, ODI checks whether other changes have been made to the same object by another user since you opened it. If another user has made changes, the object cannot be saved, and you must cancel your changes.
• Object Locking
- Automatic Object Locking. This mechanism is automatically activated. When an object is opened in a user interface, a pop-up window appears to ask if you want to lock the object. As long as an object is locked, only the user owning the lock can modify the object, such as editing or deleting. Other operations, such as executing,can be performed by other users, but with a warning. An object locked by you appears with a yellow lock icon. An object locked by another object appears with a red lock icon. When the editing window is closed, a pop-up window appears to ask
if you want to unlock the object.
- You can also manually manage locks on objects. To manually lock an object,
select the object in the tree view, right-click and select Locks > Lock.
No comments:
Post a Comment