iPlanet Application Builder

Installation Instructions

Release 6.0 Service Pack 1

Contents
Before You Begin
System Requirements
Installing the iPlanet Application Builder
Configuring Database Access
Running the Tutorial
Uninstalling
Related Documentation

Before You Begin
Before you install the Application Builder tool, you need to:

Uninstall previous versions of the Application Builder (version 3.0 or older).
Uninstall previous versions of the Application Server (version 4.0 or older).
Read the Release 6.0 Service Pack 1 Release Notes.

System Requirements
The hardware and software requirements for installing and running the Application Builder are as follows:

NT Machine Solaris Machine

Operating System: Intel Pentium microprocessor running Microsoft Windows NT version 4.0 with Service Pack 5 Solaris 2.6 or 8.0

Memory: 128 MB minimum; 256 MB recommended 128 MB minimum; 256 MB recommended

Available disk space: 220 MB, plus 120 MB temporary space 220 MB, plus 120 MB temporary space

Network software: TCP/IP TCP/IP

Web server: iPlanet Web Server (Enterprise Edition) version 4.1 iPlanet Web Server (Enterprise Edition) version 4.0 or 4.1

Application server: ¹ iPlanet Application Server Version 6.0 SP 1 iPlanet Application Server Version 6.0 SP 1

Database connectivity: (optional)

Database Client Database Server

Oracle 8.1.5 and 8i Oracle 8i and 7.3.4

ODBC 3.5.1 and 3.6.0 MS SQL Server 7.0, OBDC 3.5.1 and 3.6.0

Sybase Open/Client System 11.1.1 Sybase 11.9.2, 12

Informix 2.4 Informix 9.1.4

DB2 5.2 DB2 5.2, 6.1

Database Client Database Server

Oracle 8.1.5 and 8i Oracle 8i and 7.3.4

Sybase Open/Client System 11.1.1 Sybase 11.9.2, 12

Informix 2.4 Informix 9.1.4

DB2 5.2 DB2 5.2, 6.1

¹ It is assumed that you are installing the Application Server along with the installation of the Application Builder.

Installing the iPlanet Application Builder
If you have the iPlanet Application Server and Builder versions 2.0 or 3.0 installed on your machine, you must uninstall these previous versions and reboot your machine before installing this 6.0 Service Pack 1 release. However, if you have the Application Server and Builder version 6.0 installed, you DON'T need to uninstall before upgrading to this Service Pack 1 release.
You must install iPlanet Web Server locally on your machine before installing the Application server. The Web Server is included in your Application Builder bundle. If you are installing the iPlanet Web Server (Enterprise Edition) 4.x on a system that has an earlier version (2.01 or 3.x) of Enterprise Server or FastTrack Server, please read the iPlanet Web Server 4.x Migration Guide before you begin the installation.
You must turn off any web publishing services before installing the Application Builder.
To install the Application Builder on a Windows NT system:

Double-click on the Setup.exe in the iPlanet Application Builder subdirectory on the CD-ROM.
Follow the steps in each window to customize your installation.
When prompted to enter the Product Key, enter the number provided in your Welcome letter.
Select Next or OK to proceed to the window; or Cancel to quit the installation process.

To install the Application Builder on a Solaris system:
Insert the Application Builder CD in the CD-ROM drive.
Run setup from CDROM located under /cdrom/solaris/iAS60 to install iAS 6.0 Service Pack 1 ( only if you haven't already installed the Application Server).
Copy the iAB_60opt.tar.gz file to a temporary directory on your system.
Change directory to the location containing the just-copied iAB_60opt.tar.gz file.
unzip the file by typing: gzip -d iAB_60opt.tar.gz in your console window.
Untar the file by typing tar -xvf iAB_60opt.tar in your console window.
The set of Application Builder files appear.

Locate the install script in the same directory.
Run the install script by typing /install.
Follow the directions as prompted.

The installation script detects the location of the application server. Press enter to install using the detected location of the application server.
If you have multiple application servers installed, enter the path to the Application Server you wish to use with the Application Builder.

The installation script also attempts to locate the installation of your Netscape Browser. When prompted, press enter to accept the detected location as default. Otherwise, enter the path to the browser you wish to be the default browser.
The installation script attempts to detect the location of the web server to be used with the Application Builder. Press enter to install using the detected location of the web server.
If you have multiple web servers installed, enter the path of the Web Server you wish to use with the Application Builder.
You should install the Application Builder with the same user and privileges as you provided when you installed the Application Server.
At the end of the installation process, you are prompted to make changes to your login shell script to ensure that the Application Builder startup script is available in you CLASSPATH.
BASEDIR=/usr/iplanet/ias6
IAB_PKGNAM=iAB60
IAS_HOME=${BASEDIR}/ias
IAS_BIN=${IAS_HOME}/bin
IAS_CLASSES=${IAS_HOME}/classes/java
IAS_APPS=${IAS_HOME}/APPS
IAB_HOME=${BASEDIR}/${IAB_PKGNAM}
IAB_BIN=${IAB_HOME}/bin
IAB_LIB=${IAB_HOME}/lib
JAVA_HOME=${IAS_HOME}/usr/java
JRE=${JAVA_HOME}/jre
JAVALIB=${JAVA_HOME}/lib
JAVABIN=${JAVA_HOME}/bin
JRELIB=${JRE}/lib
JREBIN=${JAVA_HOME}/bin/sparc
GX_ROOTDIR=${IAS_HOME}
Additionally, you are prompted to edit the following lines to enable database access.
# Uncomment the corresponding line in the LD_LIBRARY_PATH and CLASSPATH sections
#ORACLE_HOME=oracle-home-dir
#SYBASE_HOME=sybase-home-dir
#DB2_HOME=db2-home-dir
#INFORMIX_HOME=informix-home-dir
#INFORMIXSERVER=informix-server-name
if [ $INFORMIX_HOME ]
then
        INFORMIXDIR=$INFORMIX_HOME
        IFMXCLI=$INFORMIX_HOME/lib/cli
        IFMXESQL=$INFORMIX_HOME/lib/esql
        IFMXLIB=$INFORMIX_HOME/lib
        export INFORMIXDIR INFORMIXSERVER IFMXLIB IFMXESQL IFMXCLI
fi
if [ $DB2_HOME ]
then
        DB2DIR=$DB2_HOME
        DB2INSTANCE=db2-instance
        DB2LIB=$DB2_HOME/lib
        export DB2DIR DB2LIB DB2INSTANCE
fi
LANG=C
CLASSPATH=${IAS_CLASSES}/kfcjdk11.jar
CLASSPATH=${IAS_CLASSES}/ktjdk11.jar:${CLASSPATH}
CLASSPATH=${IAS_CLASSES}/ldapjdk.jar:${CLASSPATH}
CLASSPATH=${IAS_CLASSES}/kadmin.jar:${CLASSPATH}
CLASSPATH=${IAS_CLASSES}/naf.jar:${CLASSPATH}
CLASSPATH=${IAS_CLASSES}/jdbc20.jar:${CLASSPATH}
CLASSPATH=${IAS_CLASSES}/javax.jar:${CLASSPATH}
CLASSPATH=${IAS_CLASSES}/xml.jar:${CLASSPATH}
CLASSPATH=${IAS_CLASSES}/servlet.jar:${CLASSPATH}
CLASSPATH=${IAS_CLASSES}/toolutil.jar:${CLASSPATH}
CLASSPATH=${IAB_HOME}/lib/iAB60.jar:${CLASSPATH}
CLASSPATH=${JAVALIB}/tools.jar:${CLASSPATH}
CLASSPATH=${JAVALIB}/dt.jar:${CLASSPATH}
CLASSPATH=${JRELIB}/ext/jndi.jar:${CLASSPATH}
CLASSPATH=${JRELIB}/rt.jar:${CLASSPATH}
# Nobody's needed these in their classpath yet, but just in case...
#CLASSPATH=${CLASSPATH}:${JRELIB}/ext/providerutil.jar
#CLASSPATH=${CLASSPATH}:${JRELIB}/ext/jbroker.jar
#CLASSPATH=${CLASSPATH}:${JRELIB}/ext/cosnaming.jar
OLD_LD_LIBRARY_PATH=$LD_LIBRARY_PATH
LD_LIBRARY_PATH=/lib
LD_LIBRARY_PATH=${IAB_BIN}:${LD_LIBRARY_PATH}
LD_LIBRARY_PATH=${IAS_APPS}/bin:${LD_LIBRARY_PATH}
LD_LIBRARY_PATH=${JRELIB}/sparc:${LD_LIBRARY_PATH}
LD_LIBRARY_PATH=${JRELIB}/ext/sparc:${LD_LIBRARY_PATH}
LD_LIBRARY_PATH=${GX_ROOTDIR}/gxlib:${LD_LIBRARY_PATH}
#LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${ORACLE_HOME}/lib
#LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${SYBASE_HOME}/lib
#LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${DB2LIB}
#LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${INFORMIX_HOME}/lib:${INFORMIX_HOME}/lib/cli:$IFMXCLI:$IFMXESQL:$IFMXLIB
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$OLD_LD_LIBRARY_PATH
PATH=${JAVABIN}:/usr/bin:${JAVABIN}/sparc/native_threads:${IAB_BIN}:${IAS_BIN}:.
#PATH=${PATH}:${ORACLE_HOME}/bin
#PATH=${PATH}:${SYBASE_HOME}/bin
#PATH=${PATH}:${DB2DIR}/bin
#PATH=${PATH}:${INFORMIX_HOME}/bin
export GX_ROOTDIR LD_LIBRARY_PATH PATH CLASSPATH
if [ ! -f "$HOME/.netscape/Application Builder/6.0.pp" ]
then
     mkdir -p "$HOME/.netscape/Application Builder"
     cp ${IAB_BIN}/6.0.pp "$HOME/.netscape/Application Builder"
fi
java -classpath ${CLASSPATH} -Xms16m -Xmx256m netscape.blizzard.Main &
Configuring the Database Access
If you haven't already done so, you must configure the database access.

To configure the database access:

Locate the db_setup script located in the ias6/ias/bin directory.
Run the db_setup script by typing: db_setup.sh on solaris and dbsetup.exe on NT.
Your database access should now be properly configured.

Running the Tutorial
Before you can run the tutorial, you must setup the database to recognize the application tutorial. We have provided database setup scripts to assist you in this process. The scripts are located in the iab60\tutorial\db directory.
To setup the database on a Solaris machine:

Create a database with the name nsample in your database server.
Create a database user that has administrator privileges and with a username and password of netscape.
Execute the load_ora.sql script to create the tables under an Oracle database.
Login to your database.
Verify that the cdxinventory and cdxusers tables exist.

To setup the database on an NT machine:
Create a database with the name nsample in your database server.
Create a database user that has administrator privileges and with a username and password of netscape.
Execute the load_mssql.sql script to create the tables under an MS SQL database, or execute the load_ora.sql script to create the tables under an Oracle database.
Verify that your %HOME% system environment variable is set properly; otherwise, messages will not be logged properly.
The following messages will be written to your %HOME%\dbconn.cfg file:
	DATASOURCE = nsample
	DATABASE = %DBNAME%
	USERNAME = %USER%
	PASSWORD = %PSWD%
	
To create tables in an MS SQL database:

Execute the load_mssql.bat script from the command line by typing:
load_mssql [database] [db_user] [db_password]
For example, load_mssql nsample iPlanet iPlanet

Login to your database.
Verify that the cdxinventory and cdxusers tables exist.

To create tables in an Oracle database:

Execute the load_ora.bat script from the command line by typing:
load_ora [database] [db_user] [db_password]
For example, if you are using an Oracle Native Driver, the command would be:
load_ora nsample netscape netscape
For an Oracle ODBC Driver, the command would be:
load_ora odbc:nsample netscape netscape

Login to your database.
Verify that the cdxinventory and cdxusers tables exist.

Uninstalling the Application Builder

To uninstall version 4.0:
The application server and the Application Builder must both be uninstalled.

Select Uninstaller from Netscape Application Server 4.0 program group in the Start menu.
Follow the messages as prompted.

To Uninstall version 3.0:
To preserve your applications, you must copy any projects and application files located in the Apps subdirectory.

Select Uninstaller from the Netscape Application Builder 3.0 program group in the Start menu.
Follow the messages as prompted.
Remove NAB entries from your PATH environment variable using the System control panel.
Restart your computer.

To uninstall version 2.x:
To preserve your applications, you must copy any projects and application files located in the KIVA Apps subdirectory.
Select Uninstaller from the KIVA Application Builder 3.0 program group in the Start menu.
Follow the messages as prompted.
Run the Registry Editor by typing regedt32 or regedit at the Run command.
Under the HKEY_LOCAL_MACHINE\SOFTWARE, delete the KIVA key.
Delete the KIVA directory.
Right click on the Start menu and select Properties.
Select Program tab, select Advanced, and select the Programs folder at the bottom of the window.
Remove the folder 'KIVA .....'.
From the Control Panel, select Environment.
From the PATH, delete the set of the directories that includes "KIVA":
	C:\KIVA\KDS\BIN;
        C:\KIVA\KDS\ORB\ORBIX\BIN;
        C:\KIVA\KDS\APPS\BIN;
        C:\KIVA\KES\BIN;
        C:\KIVA\KES\ORB\ORBIX\BIN;
        C:\KIVA\KES\APPS\BIN;
	
If you do not delete the KIVA directory set from the PATH, when you install your new software the new path is appended. You may receive an error message stating:"PATH is too Long"
Delete all KIVA-related entries from the following environment variables:
	BASE_CLASSPATH
        CLASSPATH
        IT_CONFIG_PATH
        GX_INCLUDE
        GX_KDSROOTDIR
        INCLUDE
        KDS_CLASSPATH
        LIB
    
Reboot your computer.
Related Documentation
The iPlanet Application Builder documentation can be found at: http://docs/iplanet.com/docs/manuals
Select the Application Builder link to access the latest documentation including the most up-to-date Release Notes.

Sun, Sun Microsystems, the Sun logo, Java, iPlanet, and the Sun, Java, and iPlanet-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries.

Netscape and the Netscape N logo are registered trademarks of Netscape Communications Corporation in the U.S. and other countries. Other Netscape logos, product names, and service names are also trademarks of Netscape Communications Corporation, which may be registered to other countries.