Previous Topic: Input ValidationNext Topic: Stored Procedures


Operation Bindings

An operation binding is additional logic, such as a stored procedure or a script, that you can bind to a particular operation to specialize the handling of that operation. You can specify the timing of the logic invoked by the stored procedure in relation to the operation, that is, will it run before, after, or instead of the operation.

When CA IAM Connector Server performs any operation, CA IAM Connector Server verifies whether there are any operation bindings that tell it to invoke some logic before, instead of, or after that operation.

For example, imagine you want to add a user to an endpoint. You have the user's given name and family name. On the endpoint system, however, the record for that user is an attribute made up of a particular combination of their given name and family name. To resolve this situation, you can create a script that combines the two names to match the endpoint format and then, using an operation binding, specify that this script must run before any search you perform on the endpoint system.

You can apply an operation binding to any object class. For example, if you want to record all modify operations to either an account object or a group object in a log file, you could use a single operation binding and apply it to both.

You can apply multiple operation bindings with the same timing (before, after, instead of) to a single object. For example, invoking two stored procedures to run before a particular operation.

Note: Connector Xpress does not support binding an operation to a compound class.