Configuring scriptframework.properties

Use the IM_HOME/data/scriptframework.properties file, which provides extended documentation for these tasks, to configure major scripting functions.

Following are the major scripting functions:

Extensions

Specifies which extensions to load for each host component. To load more than a single extension for any host component, add a suffix to the properties key (each key must be unique). For example:

ITIM.extension.IdentityPolicy=com.ibm.itim.policy.script.IdentityPolicyExtension
ITIM.extension.IdentityPolicy.service=com.ibm.itim.script.extensions.ServiceExtension

Interpreters

Configures the interpreter to use for each host component. The default is the IBM® JSEngine.

The other option is FESI, which can be used only if the fesi.jar file exists in IM_HOME/lib/. It is only to be used by customers of IBM Security Identity Manager Version 4.6 and earlier who wrote their own custom FESI extensions.

Wrappers

All objects available to scripts are really Java™ objects that are used by IBM Verify Identity Governance. To prevent security issues, IBM Verify Identity Governance wraps these objects in wrappers. Use this area of the scriptframework.properties file to change the default wrappers that are used by IBM Verify Identity Governance. Default scripts that are provided by IBM Verify Identity Governance assume the use of default wrappers. If you change the scripts, functions might stop working. This area is for advanced use only.

Miscellaneous

Determines whether profiling information is collected and included in the trace log and whether plain text passwords can be accessed from Person and Account objects.