The Script Connector enables you to write your own Connector in JavaScript.
A Script Connector must implement a few functions to operate. If you plan to use it for iteration purposes only (for example, reading, not searching or updating), you can operate with two functions only. If you plan to use it as a fully qualified Connector, you must implement all functions. The functions do not use parameters. Passing data between the hosting Connector and the script is enabled by using predefined objects. One of these predefined objects is the result object, which is used to communicate status information. Upon entry in either function, the status field is set to normal, which causes the hosting Connector to continue calls. Signaling end-of-input or error is done by setting the status and message fields in this object. Two other script objects are defined upon function entry, the entry object and the search object.
One workaround is to remove the old Script Connector from the AssemblyLine and reintroduce it.
For a generic container, you write the Script Connector yourself in JavaScript, and it provides the modes you write into it. See "JavaScript Connector" in .
For a list of Supported Modes, see Legend for the Supported Mode columns.
In Script-based Connectors, a potential source of problems exists if you made direct Java™ calls into the same libraries as IBM Security Directory Integrator. A new version of IBM Security Directory Integrator might have updated libraries (with different semantics), or you might have upgraded your libraries since the last time you used your Connector.