Although IBM Director is designed to meet the system management needs of most small to medium companies, your organization might require a customized solution that is not provided by the IBM Director product directly out-of-the-box. Toward this end, the IBM Director Software Development Kit (SDK) enables you to customize and enhance IBM Director to meet your organization's needs.
This SDK provides documentation and sample code for extending IBM Director. Using the guidelines described in Getting started with programmed extensions, you can develop application programs (extensions) that can be fully integrated into Director. To extend Director programmatically, you must be experienced in Java or C++ programming, preferably in a systems development environment.
If you use a browser without frames support, you can invoke the file f_getstart.html as a starting point and link to the instructional files from this document. Refer to How the SDK Files Are Organized for information on how the files are labeled and grouped. The only Javascript code invoked is at the beginning of the table of contents link structures to clear the windows. If your browser does not support Javascript, these links might not resolve correctly.
Variable | Value |
JDK_X86_DIR | The base JDK directory |
SERVERINSTALL | The directory where IBM Director is installed |
MSSDK | The MSSDK directory |
The jar files containing IBM Director class files (Director.jar, DirLibs.jar, DirAgent.jar); JFC class files (swing10.jar, swing.jar, windows.jar); and other class files are located in the subdirectory lib_jav. The output class files described in this SDK will run on a system on which IBM Director has been installed. To locate the path to the IBM Director classes, use the registry editor, regedit, and look up the entry for the name Root under HKEY_LOCAL_MACHINE\SOFTWARE\Tivoli\Director\CurrentVersion. The value of Root is the path to the installed Director. The Java classes should be located in the Classes subdirectory under that path.
The following table describes all of the include file subdirectories provided by the IBM Director SDK:
Subdirectory Name | Contents |
---|---|
inc | Contains include files that are common to all platforms. These files will compile conditionally based on which platform and compiler are used. |
inc_w32 | Contains include files that are specific to all 32-bit Windows operating systems supported by Director, specifically Windows NT 4.0, Windows 95, Windows 98, and Windows 2000. |
The following table describes all of the subdirectories provided by the IBM Director SDK that contain libraries with which your extensions will need to link:
Subdirectory Name | Contents |
---|---|
lib_w32 | Contains link libraries that are specific to 32-bit Windows operating systems. These libraries were built using the Microsoft 32-bit C++ Optimizing Compiler Version 4.2 |
lib_w32.bor | Contains link libraries that are specific to 32-bit Windows operating systems. These libraries were built using the Borland C++ Version 4.52 Compiler. |
lib_nov | Contains link libraries that are specific to the Novell operating system. These libraries were built using the Watcom C/C++ V10.6 compiler. |
lib_jav | Contains jar files for the Java portion of the SDK. |
The IBM Director SDK also contains some include files and library files which were not shipped as part of the IBM Director product. The files included in this SDK are:
The 32-bit Windows samples are found in subtree w32. These samples are coded to build with the Microsoft 32-bit C++ Optimizing Compiler Version 4.2 or 5.0. If you compile the 32-bit Windows samples with Microsoft C++ Version 6.0, you should define the compiler switch NO_STRICT to turn off strict type checking. This will permit compatible linking with the libraries provided in this SDK. The makefiles provided with the C++ samples define NO_STRICT.
All of the Java source code for the samples is sorted differently from the C++ code because of the package naming feature of Java. All of the Java source for the samples can be found under the samples\javasrc directory.
These files begin with e_ and are installed in the
docs\
directory.
The reference files begin with r_ and are installed in the
docs\
directory.
The Java class descriptions are grouped into Javadoc
packages.
For example, the com.tivoli.twg.alertmgr package describes the class
files needed to extend the IBM Director event management task. All Javadoc
files are installed in the docs\javadoc directory.
Java sample source files are installed in subdirectories of samples\javasrc\com.
Native C++ samples are installed in other subdirectories of the
samples
directory. For example, resource monitor agent samples are installed in
samples\monagent.
The sample overview files begin with s_ and are installed in the docs\ directory.