### Java DIP Tester
Version 4.4.0

I. Introduction

The DIP Tester Script for was originally developed as a unix korn shell script in an effort to automate formatting and executing the ldap tools, dipassistant commands, log viewing, etc when setting up, testing, and debugging a DIP synchronization connector.

This is a VOLUNTEER EFFORT written by: Jerry Smith, OID Advanced Resolution Engineer, Orlando, FL

*******************************************************************************************
Disclaimer
Please note that DIP Tester is NOT supported by Oracle Support and is
only available as an alternative to the OID Administrator to configure
Oracle Directory Integration and Provisioning Platform.
Oracle development does not support the use of DIP Tester and you may be
required to abandon its use if a problem arises.
*******************************************************************************************

Comments and/or suggestions are welcome and should be directed to jerry.smith@oracle.com

II. About Java DIP Tester

If you are new to DIP Tester (you have never run the character based version) you may ignore the references to diptester.ini as they are not required for this new java version.

The character based version of DIP Tester, up to and including version 3.4.1 used a diptester.ini file located in the $ORACLE_HOME. The .ini file was a set of unix environment variables that were used to control the behavior of DIP Tester.

This new version starting at 4.1 uses a diptester.properties file that must reside within the new DIP Tester file structure at $ORACLE_HOME/ldap/odi/diptester. It is the equivalent of the old diptester.ini file. Since environment variables would differ from operating system to operating system, we now use a standard formatted java "properties" file that is used by the JVM to create a runtime "resource bundle". This allows the diptester properties file to be the same format regardless of the operating system.

As in the previous character version, the properties file MUST begin with 'diptester'. The install script creates the default diptester.properties file in $ORACLE_HOME/ldap/odi/diptester.

II. Contents of DIP Tester Distribution

DIP Tester distribution contains the following files:

    README.html                   - this file viewable in a web browser

    install.bat                    - installation script for Windows platforms

    install.sh                     - installation script for Unix platforms

    activechg.map                  - a known working Active Directory import mapping file

    activeexp.map                  - a known working Active Directory export mapping file

    ad2oid.properties              - a known working Active Directory bootstrap config file

    cdiptester                      - the character based Korn shell version of diptester

    diptester.hpux                 - unix shell script for launching diptester.jar

    diptester.linux                - unix shell script for launching diptester.jar

    diptester.solaris              - unix shell script for launching diptester.jar

    diptester.bat                  - dos batch file for launching diptester.jar

    diptester.jar                  - java diptester executable

    diptester.properties           - an initial diptester.properties file

    diptester.properties.master    - template for creating diptester-xxx.properties files

    diptester.log                   - diptester log file is located in $OH/ldap/odi/log directory

    diptesterUSERGUIDE.doc          - a MS Word document DIP Tester User Guide

    ipl2oid.properties             - a known working Active Directory bootstrap config file

    iplanetexp.map                 - a known working Active Directory import mapping file

    iplanetimp.map                 - a known working Active Directory export mapping file

    ldapcheck_for_HPUX              - a corrected version of ldapcheck for HPUX

    prop2ini.sh                     - a shell script that will convert a properties file to an ini file

    unix_install                    - main script for unix installations that is called by install.sh

    w                               - DEBUG = 0 value needed by DOS Install

    x                               - SSLAUTH = 0 value needed by DOS Install

    y                               - INSTANCE = 2 value needed by DOS Install

    z                               - CONFIGSET = 1 value needed by DOS Install

    create_DB_profile.sh            - creates an Oracle Database Connector

    create_DBtable.sql              - creates a database table for synchronizing

    DBImport.cfg                    - database connector configuration file used by create_DB_profile.sh

    DBImport.map                    - database connector mapping file

    DBImport.properties             - database connector properties file sued by create_DB_profile.sh

III. Installation

1. The ORACLE_HOME and ORACLE_SID should be set

2. The database, listener, and oidldapd must be running.

3. Run the install.sh to install on a unix environment. It will check to see if you have a previous java diptester installed and either do a complete install or upgrade the diptester.jar file. (for patches)

4. If installing on HPUX, rename the $ORACLE_HOME/ldap/bin/ldapcheck and copy the ldapcheck_for_HPUX in its place(ldapcheck is used to display the current status of all OID processes).

5. If installing on windows, you need to run the install.bat from a DOS command prompt

The installation script will create the necessary file structure for DIP Tester and copy a known working set of mapping files and bootstrap config files. The DIP Tester executable is a simple shell script that launches the diptester.jar using java. The install.sh will determine your OS and copy the corresponding diptester.xxxx to $OH/bin. The script also copies the character based version of the DIP Tester tool (cdiptester).

If you want to do a manual installation do the following:

1. create the following directories:

$ORACLE_HOME/ldap/odi/diptester
$ORACLE_HOME/ldap/odi/diptester/adsync
$ORACLE_HOME/ldap/odi/diptester/iplsync
$ORACLE_HOME/ldap/odi/diptester/edirsync
$ORACLE_HOME/ldap/odi/diptester/dbsync
2. if you have previously installed the character based DIP Tester the installer will rename your default diptester.ini located in $ORACLE_HOME before generating a new one that matches the java version diptester.properties file.

3. on Unix copy the appropriate script file; diptester. to $ORACLE_HOME/bin as diptester

for example: cp diptester.linux $ORACLE_HOME/bin/diptester

on Windows copy the batch file "diptester.bat" to %ORACLE_HOME%\bin

4. copy the diptester.jar to $ORACLE_HOME/ldap/odi/jlib

5. copy the diptester.properties to $ORACLE_HOME/ldap/odi/diptester

6. copy the Active Dir mapping and bootstrap files to $ORACLE_HOME/ldap/odi/diptester/adsync

7. copy the Iplanet mapping and bootstrap files to $ORACLE_HOME/ldap/odi/diptester/iplsync

8. copy the DBImport connector mapping and config files to $ORACLE_HOME/ldap/odi/diptester/dbsync

9. no current files exist yet for the Novell eDirectory as it is not yet released.

10. manually edit the file $ORACLE_HOME/ldap/odi/diptester/diptester.properties

IV. Using DIP Tester

An Oracle Web Conference shows a sample DIP Tester session complete with audio and can be viewed at:

https://conference.oracle.com/imtapp/app/arc_pb_hub.uix?mID=20233566&src=app/arc_pub&action=pb

Known issues and differences between this version and character based DIP Tester:

Generic

1. It is suggested to use the DIP Tester log purge or log rename option to first condense the logs.
Note: also that the odisrv should be stopped prior to doing this.

2. Under the Logs menu a list log directory option is provided to check the size of log files before viewing them. This was added as a result of the Windows limitation (see below).

3. You can dynamically change the number of lines that tail will use to display log files. For example: to check for successful synchronization, set the tail lines to 20. Then if you see an error set it to 500 or 1000 or (as many as necessary) so that you are able to scroll backwards in the log window to view the entire synchronization details.

4. This version now does NOT automatically load the mapping file after editing it.

5. DIP Tester now validates the orcladmin password at launch and again when switching to different connectors.

6. There is a new option to initialize a connector profile using the information already known in the diptester.properties file.

7. There is a DN counter to count the # of entries in the default container in OID. This is useful after running a bootstrap operation.

8. By default, DIP Tester logging is turned off. If you are getting an unexpected error or DIP Tester does not seem to be doing what you expect, enable debugging by setting the DEBUG = 1 in the diptester.properties file. DIP Tester commands will be appended to the diptester.log located in $ORACLE_HOME/ldap/odi/log. file in the location shown above. If you want to disable logging set the DEBUG = 0 and restart DIP Tester.

9. This version also provides extensive help. In addition to HELP menu choice under each Main category, anytime a popup requires input a help button is provided that gives syntax and/or example of exactly what input is expected.

10. If you do not get a login window immediately upon launching DIP Tester, check your diptester.properties file and make sure you have a fully qualified hostname defined for OIDHOST.

11. If dipassistant is not found make sure you have set your $ORACLE_HOME or %ORACLE_HOME% environment variable and that ORACLE_HOME/bin is in your path.

12. You must be running 9.0.4 or later for DIP Tester to be fully functional as it relies on dipassistant commands. You may be able to use DIP Tester on prior versions but certain updates, such as load mapping file will not work.

13. Any test users added will be created with a default password of welcome1.

Unix Only
If you need to run DIP Tester are over a dialup or DSL line where the X windows performance precludes using java diptester, you can still use the character based DIP Tester (version 3.4.1) by typing 'diptester -char' at the command prompt.

To implement this feature do the following:

- if this is your first installation of java DIP Tester and you had previously installed the character version, the install.sh will detect it and rename the existing $ORACLE_HOME/diptester to cdiptester, no further action by you is required

- if you do NOT have the character based version of DIP Tester, the install will install it in $ORACLE_HOME/bin.

By default, typing 'diptester' will launch the new java based GUI version.

To run the character based version type 'diptester -char' >p> Windows Only

1. If running on Windows you must change to your drive letter where the oracle home is located before running "DIP Tester" (diptester.bat).

2. The default log viewer, DOS 'type.exe' is used to view the log files, but because of files in use, DIP Tester must first copy the log file to C:\winnt\temp and then TYPE it to the screen. If your log files are large, this can take considerable time. Using the type.exe command severely limits the usability of DIP Tester when viewing log files to check if sync is successful.

Therefore, it is HIGHLY RECOMMENDED that you download one of several DOS tail.exe utilities and set this to be used as the LOGVIEWER in the diptester.properties file. You may obtain a copy of tail.exe at the following locations:

http://www.rhazes.com/download/tail/tail.zip

http://unxutils.sourceforge.net/UnxUtils.html
Not only tail.exe but a complete unix suite of tools

Microsoft Windows Server Resource Kit for XP and Server 2003 can be obtained at:
http://www.microsoft.com/downloads/details.aspx?FamilyID=9d467a69-57ff-4ae7-96ee-b18c4790cffd&DisplayLang=en
tail.exe is NOT included in prior versions of the Microsoft Resource Kits

After obtaining your copy of tail.exe you must place it in your windows command folder...eg..C:\winnt\system32, and change your diptester.properties file setting LOGVIEWER = tail.exe

3. Since LDAPCHECK is not implemented on windows the Odi Server/ status option does not work for windows platforms.

4. When using 'tail' to view log files somethimes it seems to interfere with the running odisrv resulting in the odisrv0x.log returning 'Access denied'. Stopping the entire Oracle stack an rebooting the process will correct the problem.

V. The DIP Tester change history is provided here for additional info:

                                   DIP Tester CHANGE HISTORY

Version 4.3.9

-------------

Corrected a problem with the Windows install.bat.

Corrected syntax for odiprovtool to disable a provisioning profile, operation=modify does not work,

changed to operation=enable / disable