Configuring target system operation locking
Some target systems do not allow multiple client connection attempts to occur simultaneously, so connectors write lock files to prevent this from happening. Locks are also created when other programs connect to a target system.
Some connector concurrency rules are pre-defined; for example:
NDS (and related target systems such as GroupWise) have a pre-defined lock:
%LDIR%NWCLIENT.lock
If an operation on the NDS target system nds1 triggers a lock, the following lock file is created:
<Program Files path>\Bravura Security\Bravura Security Fabric\Locks \NWCLIENT.lock
No other target systems that use this lock (groupwise1, nds2) can do anything until the lock is removed.
Windows server target systems have a pre-defined lock:
%LDIR%NTCLIENT%HOST%.lock
So if an operation on the Windows server target system nt1 triggers a lock, the following lock file is created:
<Program Files path>\Bravura Security\Bravura Security Fabric\Locks \NTCLIENTNT1.lock
No other operations can be performed on nt1, however operations can still be performed on other Windows server target systems.