IBM Tivoli Directory Integrator
The IBM Support Assistant (ISA) is a free local software
serviceability workbench that helps resolve questions and problems
with IBM software products. It is a stand-alone application
that can be installed on any workstation and then enhanced by installing
plug-in modules for IBM products.
The three basic components of ISA are:
- Concurrent Search tool - This searches
across the bulk of IBM documentation as well as product
infocenters and returns the results categorized by source for easy
reviews.
- Product Information feature - This
has links to the product home page, support page, news groups, forums
and other links relevant to the product.
- Service Feature - This consists of a data
collection tool and a problem submission tool. There are two types
of data collection tools.
The first type is the System Collector
that is provided by ISA and gathers general information from the
operating system, registry, and so forth.
The second type is
a product specific data collector that is driven by a control file
defined by the respective product teams. Collector output file names
have the format collector_timestamp.jar.
These JARs can then be attached to a problem report.
The problem
submission tool helps in the creation and submission of problem reports.
To log into the tool, called ESR (Electronic Service Request), you
need the following information:
- IBM ID
- IBM password
- IBM customer number
- Country or region
IBM Support Assistant can be downloaded from http://www-306.ibm.com/software/support/isa/.
A useful demo on ISA and its features can be found at http://publib.boulder.ibm.com/infocenter/ieduasst/v1r1m0/index.jsp.
Detailed information for developers can be obtained from https://wst.austin.ibm.com/isahome/dev_corner.html.
The TDI version of the Plug-in gathers the following info from
the TDI Installation (and Solution Directory, if defined):
- Logs from the TDI_install_dir/logs folder -
ibmdi.log, ibmditk.log, tdisrvctl.log
- For TDI versions prior to v7.0, all property, XML and rules files
from the TDI_install_dir/etc folder:
build.properties
ce-log4j.properties
CSServersInfo.xml
derby.properties
executetask.properties
global.properties
jlog.properties
log4j.properties
reconnect.rules
tdisrvctl-log4j.properties
- From TDI v7.0 onwards various issues will be categorized. You
will have the option to select a category and only the log files pertaining
to that category will be collected. The following categories are available:
- TDI Server Related Issues.
- AMC Related Issues.
- TDI Install Related Issues.
- TDI Config editor Related Issues.
- TDI Plug-in Related Issues.
We have the option to select anyone of these issues and start
collecting files by clicking the Collect button.
After selecting the type of issue, you are prompted to specify appropriate
directory paths to collect various log files. The default TDI installation
folders (on Windows/Linux/UNIX) are supplied by default for convenience.
Also, a PMR number should be specified and the output .zip file with the
collected info will be placed in the installation directory specified, with the following name:
ISA_[Type]_PMR#[Number].zip
where [Type] can be Server/AMC/Install/CE/Plugins
and [Number] is the PMR number specified (none if left empty).
Details
about the files being collected are as follows:
- TDI Server Related Issues
- We will be prompted to provide the TDI installation directory
as well as a solution directory (leave blank if we do not want to
specify solution folder) ) and a PMR number. Also, the following note
prompts the user to turn his log level to DEBUG if his problem is
easily re-creatable:
If your problem is easily
re-creatable and we use the default Log4J logging it is best if you
set your logging root category to DEBUG in etc\log4j.properties and
enable detailed log for your problematic components. Then we should
re-run your scenario and come back to this dialog to collect the logs
with detailed information for your problem.
The following files
are collected:
- ibmditk.bat(.sh)
- ibmdisrv.bat(.sh)
- derby.log
- ibmdiservice.props
- TDI_install_dir/etc/*.properties
- TDI_install_dir/etc/*.properties/*.xml
- TDI_install_dir/etc/*.properties/reconnect.rules
- TDI_install_dir/system_logs/*.log
- TDI_install_dir\win32_service\*.properties (on Windows)
- List of all .jar files
- Component version information
- Host, memory, and list of started services.
- AMC related issues
-
The following files are collected:
- amc.properties
- am_config.properties
- am_logging.properties
- tdimigam-log4j.properties
- All files inside the TDI_install_dir\lwi\runtime\isc\eclipse\plugins\AMC_7.1.0\WEB-INF folder.
- All the log files inside the TDI_install_dir\bin\amc\ActionManager\logs folder.
- All properties files inside the TDI_install_dir\bin\amc folder
- All properties files inside the TDI_install_dir\lwi\runtime\isc\eclipse\plugins\AMC_7.1.0\WEB-INF\classes folder
- Install related issues
- We will be prompted to provide the temp directory on the machine
that the installer has used to store the collected files (for example, corresponding to the TEMP environment variable on Windows) as well
as the TDI
installation directory, Common Solution Install directory and PMR
Number.
Note that on z/OS the
temp directory is /temp/InstallShield.
The
following files are collected:
- temp/tdiv71install.log
- temp/tdiv71uninstall.log
- temp/tdiSoldir.log
- temp/tdiSoldirERR.log
- temp/tdiMQeCreate.log
- temp/tdiMQeCreateERR.log
- common_solution_dir/logs/*/si_trace.log
- Information for installed components and fixpacks applied collected
using applyUpdates.bat(.sh) script and
saved in TDI_install_dir/TDIUpdateInstaller.txt
- Config editor related issues
- We will be prompted to provide the TDI
installation directory and PMR number.
The following files are collected:
- TDI_install_dir/ibmditk.bat(sh)
- TDI_install_dir/ce/eclipsece/configuration/config.ini
- workspace/.metadata/*.log
- TDI Plugin Related Issues
- We will need to specify the plugins installation directory
(which normally is TDI_install_dir/pwd_plugins)
and PMR number, and for each of the following plugins the files mentioned
below them will be collected.
- Domino Plug-in
-
- TDI_install_dir\pwd_plugins\domino\*.props
- TDI_install_dir\pwd_plugins\domino\*.log
- PAM Plug-in
-
- TDI_install_dir\pwd_plugins\pam\*.props
- TDI_install_dir\pwd_plugins\pam \*.log
- SunOne Plug-in
-
- TDI_install_dir\pwd_plugins\sun\*.props
- TDI_install_dir\pwd_plugins\sun \*.log
- TDS Plug-in
-
- TDI_install_dir\pwd_plugins\tds\*.props
- TDI_install_dir\pwd_plugins\tds \*.log
- Windows Plug-in
-
- TDI_install_dir\pwd_plugins\windows\*.props
- TDI_install_dir\pwd_plugins\windows \*.log
- TDI_install_dir\pwd_plugins\windows \*.reg
- A list of all jars present in the TDI_install_dir/jars folder
- Versions of all TDI components
- If we have selected AMC related issues - amc.property
files, all files in the WEB-INF folder and amc logs will be collected
- If the Solution Directory is different from the TDI_install_dir, then along with solution.properties all logs and property files as
mentioned above are collected from the solution directory
The TDI version of the ISA plugin has been instrumented
with the proper access information in order to support the process
of sending the collected files through HTTP or FTP.
These are the steps to use IBM Support
Assistant to generate problem records for TDI:
- Download ISA version 4.0, from http://www-306.ibm.com/software/support/isa/.
- Open ISA, select the Updater tab
and then select the New Products and Tools tab.
- Select IBM TDI 7.1 from the available plug-ins list and
install.
- Restart ISA to start using the tool for TDI.
- Or alternatively, if the plug-in and features folder
are available then drop the plug-in (com.ibm.esupport.client.product.SSCQGF71_4.0.0.20080815)
into the plugin and feature (com.ibm.esupport.client.product.SSCQGF71.feature_4.0.0.00) into features folder of ISA and restart ISA.