We can access our own custom Java classes from inside the IBM Tivoli Directory Integrator framework as long as the these are public classes and methods. These libraries must be packaged into a .jar or .zip file, and then be placed in the TDI_install/jars directory, preferably in our own subdirectory. We can also use the CLASSPATH environment variable or the Java runtime environment extension folder, but both of these methods are discouraged. These methods let you call classes from within our own classes only if the loader happens to load the classes before our own.
If you are running the server from the Config Editor, restart the Config Editor before it detects new classes in the TDI_install/jars directory and subdirectories.
After putting the .jar files in the jars subdirectory, we can create an instance of the class to refer to within the IBM Tivoli Directory Integrator. Note that the Java Function Component allows us to open .jar files, browse objects contained in them as well as their methods. Once we have chosen the function to call, the FC prepares your Input and Output schema to match the parameters needed by the Java function.
For more information about calling Java classes from script, see Instantiating a Java class.
Parent topic: The AssemblyLine