Set up the development environment
When you install Connections, a set of TDI components are installed on the system. These components are used by the population wizard and other TDI tasks, such as the synchronization tasks, to populate and update the Connections user directory. They are stored in a compressed file referred to as the TDI solution directory (tdisol.zip or tdisol.tar).
The TDI Solution directory is created by running...
mkdir TDI_HOME/TDISOL
cp $CNX_INSTALL_MEDIA/TDISOL/tdisol.tar TDI_HOME/TDISOL
cd $TDI_HOME/TDISOL
tar xvf tdisol.tarThe solution directory includes a set of connectors, used to build custom TDI assembly lines. Your custom assembly lines can:
- Use an available plug point, such as an alternate source for profiles data or custom delete processing
- Interact with the profiles, photos, pronunciation, or code sections of profiles through the available connectors.
This section describes how to set up a development environment for writing custom assembly lines using the Profiles TDI connectors provided in the Connections installation package.
To set up the development environment.
- Create a directory to store the TDI connector source files.
Since you might create multiple iterations of the code we are developing, use a directory naming system that will help you keep track of each iteration. For example, you could add a subdirectory named version, where version is the version number and date of the copy of the tdisol.zip file that you will extract into the directory. Alternatively, you could name the directory after the assembly line you will be creating, such as custdel if we are working on custom delete processing logic. For example...
C:\TDIProject\20120530
c:\tdiprojects\40\custdel
- Extract the files from the TDI solution directory (tdisol.zip or tdisol.tar) into the directory you created in the previous step. We can find the solution directory in...
C:\IBM\Connections\TDISOL This action adds a tdi subdirectory to the directory path. For example: C:\TDIProject\20120530\TDI or c:\tdiprojects\40\custdel\tdi.
- When you start the Configuration Editor, specify the location of the Profiles TDI solution directory using the -s command-line option :
tdi_install_dir/ibmditk -s your_TDI_directory
where:
- tdi_install_dir is the name of the directory where you installed TDI.
- your_TDI_directory is the subdirectory that you created in the previous step.
For example:
C:\IBM\TDI\V7.0/ibmditk -s C:\TDIProject\20120530\TDI
The workspace used for development must reference a TDI solution directory containing all the Profiles TDI artifacts. It is not sufficient to create a new TDI solution directory or use one that does not contain these artifacts. If we attempt to use a Profiles TDI component, such as one of the connectors, and they do not appear in the connector list, then you do not have the workspace and solution configured correctly.
- When you start the Tivoli Directory Integrator Configuration Editor, we are asked to specify a workspace. This is a working directory to store things related to your development project. When prompted, specify the same file path that we are using for the connector files, but replace TDI with workspace.
For example: C:\TDIProject\20120530\workspace or c:\tdiprojects\40\custdel\workspace The editor creates the workspace subdirectory if it does not already exist.
Results
You now have a TDI solution environment used to edit the Profiles Tivoli Directory Integrator connectors.
What to do next
Refer to connector-specific documentation for details about each connector. Scripts created in this environment can be executed from the Configuration Editor in the same way that you would execute standard TDI assembly lines.
Parent topic:
Develop custom TDI assembly lines for Profiles
Related:
Use a custom source repository connector
Related: