Last updated on JANUARY 18, 2015
Applies to:Oracle Communications IP Service Activator - Version 4.0.1 to 5.2.4 [Release 4.0 to 5.2]
Oracle Solaris on SPARC (64-bit)
Oracle Solaris on SPARC (32-bit)
Sun Solaris SPARC (64-bit)Sun Solaris SPARC (32-bit)
** Currency review Jan-2015**
Each Integration Manager instance runs one and only one copy of the master Object Model(OM). When a user (thread) needs to write to the Object Model (OM) from the Integration Manager, the OM is locked and everyone else on that Integration Manager(IM) has to wait. The more users on a single IM the slower it will operate.
At any point, the client can either issue an abort (which empties the queue) or a commit (which performs the queued operations on the model). If the client disconnects, this is treated as an abort (after an appropriate timeout).
When the queued operations begin to be applied to the model, it is locked for all other clients. Should other clients attempt to access the model, they will be blocked. This situation resolves in one of two ways:
1. The transaction is successfully applied into the model, model validation succeeds and the changes are successfully registered with the main object model in the policy server.
2. One of the above steps triggers or encounters an error. The client is notified of transaction success/failure and the model re-opened to all clients.
You can have more than one Integration Manager installed but this will be based on the hardware specs as well as other components or applications installed on the machine.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms