Chapter 1 Installing Netscape Application Server on Windows NT

This chapter explains how to install Netscape Application Server (NAS) on the NT platform. It includes the following topics:

• Checking Hardware and Software Requirements
• Planning Your Installation
• Installing Netscape Application Server
• Using the Sample Applications
• Post-Installation Notes
• Installing the Web Connector Plug-in
• Installing Netscape Application Server Administrator
• Uninstalling Netscape Application Server
• Installation Planning Worksheets

• This version represents a major upgrade of Netscape Application Server. Install on a machine where no earlier versions of this product have been installed.
• When you run the installation program, you install Netscape Application Server, Netscape Console, Netscape Administration Server, and Netscape Directory Server. Decide in advance which product or combination of products you want to install.

• Netscape Application Server includes Netscape Application Server, Netscape Application Server Administrator, the Web Connector plug-in used to communicate between NAS and the web server, and the Deployment Manager.
• Netscape Console provides the common user interfaces for all Netscape server products. From it you can perform common server administration functions such as stopping and starting servers, installing new server instances, and managing user and group information. Netscape Console can be installed stand-alone on any machine on your network and used to manage remote servers.
• Netscape Administration Server is a common front end to all Netscape servers. It receives communications from Netscape Console and passes those communications on the appropriate Netscape server. Your site will have at least one Administration Server for each server root in which you have installed a Netscape server.
• Netscape Directory Server is Netscape's LDAP implementation. The Directory Server runs as the slapd service on your machine. This is the server that manages the directory databases and responds to client requests.

The installation program asks whether you want to install Netscape Servers or Netscape Console. It is recommended that you select the Netscape Servers option, which includes Netscape Application Server, Netscape Console, and Netscape Directory Server. Netscape Console includes only the Netscape Console product.

• The default installation directory for Netscape Servers is c:\Netscape\Server4. If you use this path, the Netscape Application Server installation directory is set to c:\Netscape\Server4\nas. Decide if you'd rather install to a different directory. It is strongly recommended that you use the default installation directory.

• Before you run the installation program, read the Netscape Directory Server documentation, particularly the Netscape Directory Server 4.0 Installation Guide, for information about setting up Directory Server and details about the issues discussed in this section. All Directory Server documentation is located in the following places:

• In Netscape Server Family root directory\ manual\en\slapd
• At http://home.netscape.com/eng/server/directory/4.0/
• From the Help menu in Directory Server.
• If you install Directory Server with this installation of Netscape Application Server, you must designate this installation of Directory Server as the configuration directory, even if another installation of Directory Server already exists at your site.

The configuration directory contains the o=NetscapeRoot tree used by your Netscape servers. The o=NetscapeRoot tree is where all the configuration settings of your Netscape servers are stored.

• If you do not install Directory Server with this installation of NAS, you must designate an existing Directory Server as the configuration directory. Make sure that the Directory Server you designate as the configuration directory contains the o=NetscapeRoot tree.

The NAS installation program will prompt you for the following information about the existing Directory Server:

• The host name and port number for the machine where the existing Directory Server is installed.
• Login ID and password to connect to the existing Directory Server installation.
• Administrator login ID and password
• Multiple NAS installations can store their configuration settings on the configuration Directory Server. To avoid your settings being overwritten by another NAS installation's configuration settings, assign a unique global configuration name to your NAS installation's settings. This name appears in the o=NetscapeRoot tree along with the global configuration names of other NAS installations.

During installation, you are asked to provide the global configuration name for the configuration settings of the NAS you are currently installing. Note that if you want to share configuration settings with other NAS installations, simply enter the same global configuration name for each installation.

• If you install Directory Server with this installation of Netscape Application Server, you must designate this installation of Directory Server as the storage directory (as well as the configuration directory), even if another installation of Directory Server already exists at your site.
• If you do not install Directory Server with this installation of NAS, gather the following information about the existing storage Directory Server:

• The host name and port number for the machine where the existing Directory Server is installed
• Login ID and password for the existing Directory Server
• The top level domain name (suffix) of your Directory Server structure. This is the directory entry that represents the first entry in the directory tree. You will need at least one directory suffix for the tree that will contain your enterprise's data. It is recommended that you select a directory suffix that corresponds to the DNS host name used by your enterprise. For example, if your organization uses the DNS name of airius.com, then select a suffix of o=airius.com.
• The configuration directory contains an administration domain, which allows you to group Netscape servers together so that you can more easily distribute server administrative tasks across organizations while retaining centralized control. Decide if you want to use administration domains, and if so, select the name(s) you want to use. It is recommended that you use names that correspond to the organizations that will control the servers in each domain.
• The installation program asks you to specify a Directory Manager distinguished name (DN) and password. Directory Manager DN is the special directory entry to which access control does not apply. Think of directory manager as your directory's superuser.

The default Directory Manager DN is cn=Directory Manager. Because the Directory Manger DN is a special entry that is not stored in the directory tree (instead it is stored in slapd.conf), it does not have to conform to any suffix configured for your Directory Server. Also, you should not create an actual Directory Server entry to use with the Directory Manager DN.

The Directory Manager password must be at least 8 characters long.

• The Netscape Administration Server is a common front end to all Netscape servers. It receives communications from Netscape Console and passes those communications on to the appropriate Netscape server. Your site will have at least one Administration Server for each server root in which you have installed a Netscape server. During installation you are prompted for an Administration Server port number. This is the port number that your system administrator must specify to access the Administration Server.

Make sure the port number you select for the Administration Server is unique and has not been assigned earlier during the installation process to the non-SSL port number for the configuration server. Be sure to use the "Installation Planning Worksheets" at the end of this chapter to write down all the different port numbers and ensure that you do not inadvertently assign ones that are already in use by other products such as Directory Server.

• Decide which NAS components you are installing on your machine. Then determine if you have previously installed one of the following on this machine:

• Netscape Application Server
• Netscape Application Server Administrator
• Web Connector plug-in
• Deployment Manager

If an earlier version of any of these components already exists on your machine, uninstall the earlier version before installing the current NAS 4.0 version. The installation program does not upgrade earlier versions or releases.

• Decide how many Netscape Application Server instances you want to run. An instance of Netscape Application Server is defined as one installation of Netscape Application Server with one Executive Server (KXS).
• Only one instance of Netscape Application Server should run per machine. You should not install multiple Netscape Application Servers on the same machine.
• When you install Netscape Application Server, you must specify a product key. The product key is available on the Welcome letter you received with the Netscape Application Server that you purchased.
• Know the number of Java Servers (KJS) you want to run for each instance of a Netscape Application Server. For information about Java Servers, see the Overview Guide.
• Know the number of C++ Servers (KCS) you want to run for each instance of a Netscape Application Server. For information about C++ Servers, see the Overview Guide.

Know the available port numbers on your machine so that you can assign ports to the Administrative, Executive, Java, and C++ Servers. All ports you specify are listener ports. Valid port numbers must be within the acceptable range (1 to 65535) and must be unique (not used by any other applications on your system). Be sure to use the "Installation Planning Worksheets" at the end of this chapter to write down all the different port numbers and ensure that you do not inadvertently assign ones that are already in use by other products such as Directory Server or the Netscape Administration Server.

The default port numbers are as follows:

• 10817 for the Administrative Server (KAS)
• 10818 for the Executive Server (KXS)
• 10819 for the Java Server (KJS). You can configure multiple Java Servers.
• 10820 for the C++ Server (KCS). You can configure multiple C++ Servers.

In most cases, the default port numbers suggested by the installation program are adequate, unless you are configuring multiple Java and C++ Servers, in which case you assign a unique number to each additional Java and C++ engine.

• Know whether your web server runs on the machine where you are about to install Netscape Application Server or whether it resides on another machine. If it is on another machine, you perform what is referred to as a "webless" installation of Netscape Application Server.

The following diagram illustrates a webless installation, where the web server and Netscape Application Server reside on separate machines.



The following diagram illustrates a non-webless installation, where Netscape Application Server and the web server reside on the same machine.



• If you are performing a webless installation of Netscape Application Server, know the type of web server you have and remember to install the Web Connector plug-in on the web server after you finish installing Netscape Application Server. See "Checking Hardware and Software Requirements" on page 14 for information about supported web server versions and types.
• Consider security issues related to your firewall setup. In a webless install of Netscape Application Server, if a firewall will exist between the Netscape Application Server machine and the web server machine, before installing Netscape Application Server, consult with your security administrator to ensure that the necessary ports on the firewall are open so that the Executive Server (KXS) and the Web Connector plug-in can communicate. For information about the Executive Server, see the Overview Guide. For more information about firewall configuration, see Chapter 2, "Planning Your Environment," in the Deployment Guide.
• Install and configure the web server and web browser before installing Netscape Application Server.
• If you use one of the supported web servers on the same machine as the Netscape Application Server, the connector plug-in configuration is automatic. For installations of Netscape Application Server, understand the difference between the following two directories and know their locations:

• The web server document directory is the directory where the web server gets the files it serves to a web browser, such as HTML, GIF, and JPEG. The installation program will detect the HTML directory for all supported web servers.

• Determine the database connectivity configuration for this installation of Netscape Application Server. During installation of Netscape Application Server, you are asked to rank the client databases in priority order. Sample applications installed with Netscape Application Server will be configured to connect to the database that is assigned the top priority.

In addition, when you create your own applications, you can elect not to specify the particular database you want the application to use. In this case, the application attempts connecting to the configured databases in the priority order you specify during installation.

Note that Netscape Application Server supports a variety of database client versions, with each one interfacing with a variety of database servers. The following table lists Netscape Application Server database compatibility information:

DB Client	DB Server
Oracle 8.05	Oracle 8.05
Sybase 11.1.1	Sybase 11.9.2
DB2 5.2	DB2 5.2
ODBC 3	Microsoft SQL Server 6.5
Informix CLI 2.83	Informix Server 7.3

• Install and configure all database servers before installing Netscape Application Server.

• Update a database using one or more Enterprise Java Beans (EJB) running concurrently for the same global transaction, from within one or more KJS processes. This occurs when an EJB triggers another EJB to run and they both participate in the same transaction.
• Update multiple databases that are distributed over different geographic locations.
• Update multiple databases of different types (Oracle, Sybase, and so on).

• A mirror directory for storing the restart.bak file of each KJS process.

The default directory, nas install directory\CCS0\ TXNMGR_MIRROR\, resides on the same disk as the NAS installation directory, which is the same disk used to store the restart file.

It is recommended that you specify a different physical drive at installation time so that the restart.bak file is stored in a different physical location than restart, in case restart ever becomes unavailable. If you decide to specify a different drive path, make sure you create the directory on that drive prior to running the installation program.

For example, assuming that the Netscape Application Server installation directory is on the c: drive, instead of specifying c:\nas install directory\CCS0\TXNMGR_MIRROR at installation time, create the same path on your d: drive and specify d:\nas install directory\CCS0\ TXNMGR_MIRROR.

• For each KJS process, a log volume disk name for storing the log file.

The default name is nas install directory\CCS0\TXNMGR\ ENGnumber\logVol, where logVol is the file name, not the raw device name.

For each KJS process, ENGnumber changes to match the process number. So, for KJS1, the directory is nas install directory\CCS0\ TXNMGR\ENG1; for KJS2, the directory is nas install directory\CCS0\ TXNMGR\ENG2, and so on.

It is recommended that you do the following:

• Create a raw partition on a physical drive prior to running the installation program and then, at installation, specify the path for this partition, including the raw device name. Refer to your operating system documentation for information on how to create a raw device.
• If you intend to specify a file name, use the default drive and log volume disk name provided by the installation program.
• If you specify the name of a log volume disk that is a raw partition, make sure to indicate during installation that it is a raw partition.
• If you specify a raw partition, you must specify a starting page number (Offset value) during the installation. You must also specify the number of the pages (Size value) in the log file. Make sure that the size allocated for the log file is greater than 4MB; in other words, the file should be greater than or equal to 1000 pages, at a size of roughly 4KB per page.
• If you do not create a raw partition on a disk drive, and do not want to use the default drive and file name because you'd rather store the log file elsewhere, create a directory and file on a different disk drive, specify this directory name at installation time, and make sure you do not specify that it is a raw partition. Note that the file must be greater than 4MB, so make sure you have sufficient disk space wherever you create the directory and file. Refer to your operating system documentation for information on how to create a directory and file on a different disk drive.

The following list contains the database types you can specify for a resource manager:

• Oracle
• Sybase
• DB2
• Microsoft SQL

The following table provides the open string formats for the different types of database back ends:

• Decide if this NAS machine will participate in distributed data synchronization, also referred to as clustering. Distributed data synchronization maintains the integrity of shared information across multiple Netscape Application Servers. This is crucial for partitioned and distributed applications that are hosted on multiple Netscape Application Servers.

For more information about distributed data synchronization, see Chapter 14, "Managing Distributed Data Synchronization," in the Administration Guide.

• If this or any other NAS machine you install will participate in distributed data synchronization, carefully plan your clusters and the role of each server in the cluster before installation.

A cluster is a group of Netscape Application Servers, installed on separate machines, that can participate as a group in synchronization of state and session data. Each server within a cluster can assume one of several roles. Most important for this installation discussion is the category of Sync Server, which includes the Sync Primary, Sync Backup, and Sync Alternate servers.

The Sync Primary is the primary data store, to which all other servers in a cluster communicate for the latest distributed data information.

A Sync Backup mirrors the information on the Sync Primary and takes over the role of the Sync Primary if the original Sync Primary fails.

A Sync Alternate is eligible to become a Sync Backup. If the number of Sync Backups falls below the set maximum, the Sync Alternate with the highest priority relative to other Sync Alternates is promoted to Sync Backup.

Note: If your configuration consists of only one instance of Netscape Application Server, then cluster planning is not necessary.

• Decide how many Sync Servers are in the cluster, in other words how many servers have the potential to become the Sync Primary. At most, this can be equal to the number of Netscape Application Servers installed on your network.
• Know the IP address of the machine that each Sync Server in the cluster resides on and the Executive Server (KXS) port number of each Netscape Application Server.
• Decide in advance the priority order, or rating, of the Sync Servers. Note that the Sync Primary is not determined by which machine has the highest priority assignment, but rather by which machine you start up first after all servers are installed.
• Make sure to note the priority rating you assign to the Netscape Application Servers in the cluster. For each installation of a Netscape Application Server in the cluster, you must re-enter the IP address-KXS port number-priority number combination for every the server in the cluster.
• It is recommended that you assign the highest priority to the Netscape Application Server you prefer to be the Sync Primary, and that you start that machine up first; assign the next highest priority to the Sync Backup, and to the remaining Sync Alternates in the desired order of promotion.
• You do not have to install the servers in the same order as the priority you assign, as long as the priority rating and Application Server identification information is consistent across each installation.

• Installs Netscape Application Server.
• Installs Netscape Application Server Administrator. You can choose to install Netscape Application Server Administrator without installing Netscape Application Server.
• Installs sample applications.
• Installs and configures the Web Connector plug-in for supported web servers. You can choose to install the Web Connector plug-in separately, on a different machine than the one where you install Netscape Application Server.
• Installs Netscape Directory Server
• Installs Netscape Console
• Installs Netscape Administration Server
• Installs the Java JRE under the installation directory.

1. Insert the Netscape Application Server Install CD-ROM into the CD-ROM drive.
2. Click Start on the Windows NT taskbar and click Run, or choose File - Run from the Windows NT Program Manager and click Run.
3. Click Browse and go to the CD-ROM drive (for example, d:\).
4. Open the NT folder and run the file setup.exe.
5. Follow the instructions of the installation program.
6. When prompted for the installation, click Netscape Servers. This gives you the choice to install Netscape Application Server, Netscape Directory Server, Netscape Console, Netscape Application Server Administrator, and the Web connector plug-in.

(Selecting Netscape Console installs Netscape Console as a standalone application.)

7. When prompted for the installation type, click Typical.
8. Select the installation directory. The default directory is c:\Netscape\Server4. Note that if you use the default, Netscape Application Server is installed in c:\Netscape\Server4\NAS.

You cannot use a directory name that includes spaces.

9. Do one of the following:

To install Netscape Application Server along with Directory Server, select all of the following components (these are the default selections), and proceed to Step 10 before continuing to the next screen in the installation program:

• Netscape Server Family Core Components
• Netscape Directory Suite
• Administration Services
• Netscape Application Server 4.0

The first three components (Netscape Server Family Core Components, Netscape Directory Suite, Administration Services) install Directory Server software. Although listed on the screen, do not select Netscape Directory Server 4.0 Synch Service.

To install Netscape Application Server without Directory Server, select only Netscape Application Server 4.0 and proceed to Step 10 before continuing to the next screen in the installation program:

10. Click Change to select subcomponents and then choose the Netscape Application Server component(s) you wish to install:

• Web Connector Component (Web Connector)
• Core Server Component (NAS, without the Web Connector plug-in)
• Administrator Component (Netscape Application Server Administrator)
• Deployment Manager Component

If you want to install NAS without the Web Connector plug-in, select Core Server Component, and proceed to Step 11.

If you want to install NAS with the Web Connector plug-in, select both Web Connector Component (Web Connector) and Core Server Component (Webless), and proceed to Step 11.

If you want to install only the Web Connector plug-in, select Web Connector Component (Web Connector) and go to the section "Installing the Web Connector Plug-in" on page 46.

If you want to install only the Administrator (Netscape Application Server Administrator), select Administrator Component, and go to the section "Installing Netscape Application Server Administrator" on page 52.

If you select only Deployment Manager Component, proceed with the installation process until it is complete.

11. If you specified in Step 9 that you want to install Directory Server, continue to the next step.

Otherwise, if you do not want to install Directory Server, do the following:

1. Enter the following information for the configuration Directory Server that you want this NAS installation to be configured with:
   Host name and port number of the machine where the existing installation of Directory Server resides
   Login ID to the machine where Directory Server is installed in "Bind As" (the default value is cn=Directory Manager)
   Password to the machine where Directory Server is installed
2. Click "Store data in an existing directory server" and then enter the following information for the storage Directory Server that you want this NAS installation to be configured with:
   Host name and port number of the machine where Directory Server is installed
   Login ID to the machine where Directory Server is installed in "Bind As"
   Password to the machine where Directory Server is installed
   Top level domain name in Suffix
3. Go to Step 15 to enter the Administration Domain where Netscape software is stored on Directory Server.
4. Then go to Step 18 to proceed to the NAS portion of the installation process.
12. If you are installing Directory Server with this installation of NAS, you must click the following options:

• This instance will be the configuration directory server
• Store data in this directory server
13. Enter the settings to be used by the Directory Server you are installing:

• Host name of the machine in Server Identifier
• Server Port number
• Top level domain name in Suffix
14. Enter the Administrator ID and password to the configuration directory.

Important: This is the Administrator ID and password required to uninstall NAS and Directory Server. Make a note of this information, as you will need it if you uninstall either of these products.

15. Enter the name of the Administration Domain where Netscape software information is stored on Directory Server.
16. Enter the Directory Manager distinguished name (DN) and password. The default value for the distinguished name is cn=Directory Manager.
17. Enter the port number for the Directory Server Administration Server. This is required for using the Console to administer the Directory Server.

This is the last step of the Directory Server portion of the installation process. The steps that follow install NAS.

18. Enter the unique global configuration name of the configuration settings for this installation of NAS. The name you assign is stored on the configuration Directory Server, under the o=NetscapeRoot tree along with the global configuration names of other NAS installations
19. Enter the product key of Netscape Application Server. See the Welcome letter you received with the product for the correct key.
20. When prompted for the type of web server to be used with this installation of Netscape Application Server, click one of the supported web server types and, if you clicked Netscape Enterprise Server, enter the web server instance name.
21. Enter the number of Java Servers (KJS) and C++ Servers (KCS) used to process applications. The default value is 1; increase this to handle high processing loads.
22. Enter the port numbers for the Administrative Server (KAS), the Executive Server (KXS), the Java Servers (KJS), and C++ Servers (KCS). All port numbers you specify are for listener ports, must be within the acceptable range (1 to 65535), and must be unique (not used by any other applications on your system).

Note that the default port number is always suggested by the installation program, whether or not the port number is already being used by another service. If it is already in use, make sure you change the value to a unique port number. Otherwise, the service you are assigning a port number to will not start up when you run NAS.

23. When prompted for the Administration Server user ID and password, enter the user ID and password that will be required to log on to the Administration Server through the Administrator tool (Netscape Application Server Administrator).

Make sure this user ID and password account has been created in Directory Server.

24. Rank the installed databases in priority order.

The installation program lists all supported database client types. The clients are required for your applications to connect to your database back ends. You must rank the clients in order of connectivity priority, whether you've installed the clients or not. You can always install the client software after running the NAS installation program. Note that sample applications are configured for the highest priority database.

25. Enter the mirror directory path where the transaction manager restart.bak file for each KJS engine process gets stored.

The default disk drive is the drive on which you are installing NAS. It is strongly recommended that you specify a path on a separate disk drive. If you do, make sure you create the directory on that drive, prior to running the installation program.

26. Enter the log volume disk name where the transaction manager log file gets stored for each Java Server.

It is strongly recommended that you create a raw partition on disk prior to running the installation program and that you specify the name of the raw device here.

27. Indicate if the specified disk name is a raw partition. If you indicate that it is, make sure that the name you specify in Step 26 is that of a raw device.
28. If the log volume is a raw partition, indicate the number of pages (Size) in the raw partition and the starting page number (the Offset value). Make sure that the size allocated for the log file is greater than 4MB; in other words, the file should be greater than or equal to 1000 pages, at a size of roughly 4KB per page.
29. Indicate whether or not you want to configure Netscape Application Server with resource manager.
30. If you indicate Yes in Step 29, specify the number of resource managers you want to use.
31. If you indicate Yes in Step 29, specify the following information for each resource manager:

• Resource manager name (user-defined)
• Database type
• Open string
  (See "Resource Manager Issues" on page 25 for information about open string formats.)
• Whether or not the resource manager is enabled.
32. When prompted whether the server will synchronize data across servers, click Yes if you intend to synchronize session and state information across multiple servers for failover and fault tolerance.

If you click No, go to Step 37.

For more information about data synchronization, see Chapter 14, "Managing Distributed Data Synchronization," in the Administration Guide.

33. If you answered Yes in Step 32, enter the name of the cluster that this Netscape Application Server will participate in.
34. Indicate if you are currently installing a Sync Server or a Sync Local. If you are installing a Sync Local, then this server will use data synchronization services, but is not eligible to become a Sync Primary or the Sync Backup.
35. Enter the total number of Sync Servers that you plan to have in the cluster.
36. For each Sync Server in the cluster, specify the following information:

• IP address
• Executive Server port number
• Priority rating
  Choose which Sync Server has the highest priority for taking over as Sync Primary and rate all other servers in the cluster in order of priority.
37. Review the summary provided by the installation program of the configuration you have selected. If necessary, go back and make changes.
38. When the installation is complete, reboot the computer so that the new settings take effect.

version.bat

• setup_ora.bat
• setup_syb.bat
• setup_db2.bat
• setup_mssql.bat

[Database setup file name] [DataSource] [Database] [DB User] [DB 
Password] [Resource manager name]

Note that if you configure the sample application to run with DB2, you can browse the catalog and search for books but you cannot check out items into your shopping cart. If you want to use the checkout feature, configure the sample application with one of the other database types.

For Microsoft SQL Server:

• Before you run setup_mssql.bat, open the file and set the value of the GUID in the open string to equal the ResourceMgrID entry in your NAS registry.
• Use the following syntax when you run setup_mssql.bat:

[Database batch file name] [DataSource] [Database] [DB User] [DB 
Password] [DB Server] [Resource manager name]

It is strongly recommended that you specify the same user-defined resource manager name you specified during installation (Step 31 on page 34).

For Oracle, use SQL*PLUS to troubleshoot any errors that may be generated when you run setup_ora.bat.

For Sybase, make sure you enable row level locking before using the sample application. This avoids application deadlocking. Refer to your Sybase documentation for details about how to enable row level locking.

[DRIVERS] 

;libtli.so=tcp unused ; This is the non-threaded tli driver. 

libtli_r.so=tcp unused ; This is the threaded tli driver.

nmake /f bookstore.mak

1. From the DOS prompt, run the following command to go to the custom directory:

cd custom

2. From the DOS prompt to run the following command to invoke the .mak file in the custom directory:

nmake /f custom.mak

1. Click Start on the Windows NT taskbar and click Programs - Netscape Server Family - Netscape Console.
2. Enter the Console Administrator user ID and password.
3. Click the "Users and Groups" tab.
4. Choose New User in the drop-down list on the lower right portion of the panel and click Create.
5. In the "Select Organizational Unit" dialog, select People and click OK.
6. Enter the name, user ID, and password for the user you want to create and click OK.
7. Click the "Users and Groups" tab.
8. Choose New Group in the drop-down list on the lower right portion of the panel and click Create.
9. In the "Select Organizational Unit" dialog, select Groups and click OK.
10. Under Create Group, enter the name of the Group you want to create, for example: BookAdmin. If the group already exists, go to Step 11.
11. Click the Members tab and then click Add.
12. Click Users and then click Search.
13. Choose the name of the user you created in Step 6 and click OK.
14. If you created a new group in Step 10, do the following:

1. Open the file nas install directory/APPS/GXApp/ldap/ldapInfo.properties
2. Add the following line in the file: ADMIN_GROUP_DN = cn=name of group created in Step 10, ou=Group, o=mcom.com
3. Save the file.

• setup_ora.bat
• setup_syb.bat
• setup_db2.bat
• setup_mssql.bat

[Database batch file name] [DataSource] [Database] [DB User] [DB 
Password]

• Log_ora.sql
• Log_syb.sql
• Log_db2.sql
• Log_mssql.sql

For Microsoft SQL Server use the following syntax when you run setup_mssql.bat:

[Database batch file name] [DataSource] [Database] [DB User] [DB 
Password] [DB Server] 

For Oracle, use SQL*PLUS to troubleshoot any errors that may be generated when you run setup_ora.bat.

For Sybase, make sure you enable row level locking before using the sample application. This avoids application deadlocking. Refer to your Sybase documentation for details about how to enable row level locking.

[DRIVERS] 

;libtli.so=tcp unused ; This is the non-threaded tli driver. 

libtli_r.so=tcp unused ; This is the threaded tli driver.

nmake /f bank.mak

1. From the DOS prompt, run the following command to go to the custom directory:

cd customer

2. From the DOS prompt to run the following command to invoke the .mak file in the custom directory:

nmake /f customer.mak

1. Start running NAS.

Verify that an active KXS process and KJS process is running.

2. Open Netscape Navigator, enter the following URL, and press Enter:

http://yourwebserver:portnumber/GXApp/index.html

3. Click the link for one of the following sample applications:

• C++ Fortune & Lottery
• C++ Online Bank
• Java Fortune
• Java Online Bookstore
• Java Online Bank (2.1)
• Java Online Bank (4.0)
4. If you are running the Online Bookstore application:

• Click the Bookstore image on the left portion of the page to enter the book store area of the application.
• Click the Book Administrator image on the right portion of the page to enter administration area of the application.

SHELL=%systemroot%\system32\command.com /e:2048

Variable: DSQUERY

Value: sybase server name

Variable: ORACLE_SID

Value: oracle server ID

Variable: ORACLE_HOME

Value: oracle install directory

Variable: DB2INSTANCE

Value: db2 instance name

Variable: INFORMIXSERVER

Value: informix server

[DRIVERS] 

;libtli.so=tcp unused ; This is the non-threaded tli driver. 

libtli_r.so=tcp unused ; This is the threaded tli driver.

nas install directory\bin\kcs

nas install directory\bin\kxs

• Netscape Enterprise Server
• Microsoft Internet Information Server

• Check whether or not the NAS 4.0 Web Connector plug-in has already been installed. If it has, the web server instance is already configured for your Netscape Application Server and you do not need to re-install the plug-in.
• Stop running your web server instance.

1. Insert the Netscape Application Server Install CD-ROM into the CD-ROM drive.
2. Click Start on the Windows NT taskbar and click Run, or choose File - Run from the Windows NT Program Manager and click Run.
3. Click Browse and go to the CD-ROM drive (for example, d:\).
4. Open the NT folder and run the file setup.exe.
5. Follow the instructions of the installation program.
6. When prompted for the installation, click Netscape Servers.
7. When prompted for the installation type, click Typical.
8. Select the installation directory. The default directory is c:\Netscape\Server4. Note that if you use the default, Netscape Application Server is installed in c:\Netscape\Server4\NAS.

You cannot use a directory name that includes spaces.

9. Choose Netscape Application Server 4.0 and click Change to select subcomponents.
10. Choose Web Connector Component (Web Connector).
11. Enter the host name and non-SSL port number for the configuration Directory Server that you want this Web Connector plug-in and the corresponding NAS installation to be configured with.
12. When prompted for the type of web server to be used with this installation of Netscape Application Server, click one of the supported web server types.
13. If you click Netscape Enterprise Server, enter the web server instance name.
14. Enter the domain name of the current machine.
15. Enter the IP address of the machine where Netscape Application Server is installed. This is a separate machine from the one where you are currently installing the Web Connector plug-in.
16. Enter the Executive Server (KXS) port number of the Netscape Application Server that the Web Connector plug-in will work with.
17. Review the Web Connector plug-in configuration list.
18. When the installation program finishes running, reboot the web server machine.

1. Enable CGI, if it is not already enabled:

1. Go to the Netscape program group and click Administer Netscape Servers.
2. Enter the administrator ID and password, and click OK.
3. On the Netscape Server Selector screen, click on the web server instance you want to configure.
4. On the main menu bar across the top of the page, click Programs.
5. On the CGI directory screen under URL prefix, type cgi-bin.
6. Under the CGI directory, enter the cgi-bin path.

drive letter:/Netscape/SuiteSpot/docs/cgi-bin 

Now, you are ready to configure the Web Connector plug-in.

2. Make a copy of the obj.conf file before modifying it and place the copy in the following directory:

drive_letter:\Netscape\SuiteSpot\https-machinename\conf_bk

3. Open the obj.conf file in the web server configuration directory to begin editing.

For example:

Netscape Enterprise Server

drive letter:\Netscape\SuiteSpot\https-machinename\config

4. At the end of the Init section of the obj.conf file, add the following as two separate lines:

Init fn="load-modules" funcs= 
"nas_name_trans,gxrequest,gxlog,gxinit,gxredirect,gxhtmlrequest" 
shlib="nas install directory/bin/example: gxnsapi351.dll" 

Init fn="gxinit"

5. In the Object name=default section, just before the line NameTrans fn=document-root root="drive_letter:/netscape home directory/SuiteSpot/docs", add the following as two separate lines:

NameTrans fn="pfx2dir" from="/cgi-bin" dir="drive_letter:/netscape 
home directory/SuiteSpot/docs/cgi-bin" name="cgi" 

NameTrans from="/" fn="nas_name_trans"

6. In the Object name=default section, just after the line ObjectType fn=force-type type=text/plain, also add the following line:

Service fn="gxredirect" fnname="imagemap" method="(GET|HEAD)" type= 
"magnus-internal/imagemap"

7. In the Objectname=cgi section(s), insert the following line immediately before the line Service fn="send-cgi":

Service fn="gxrequest" 

And then insert the following line immediately after the line Service fn="send-cgi":

AddLog fn="gxlog" 

8. After the Objectname=cgi section(s), add the following sections:

<Object name="nassspl"> 

ObjectType fn="force-type" type="magnus-internal/cgi" 

Service fn="gxrequest" 

AddLog fn="gxlog" 

</Object> 

<Object name="nashtml"> 

Service fn="gxhtmlrequest" 

AddLog fn="flex-log" name="access" 

</Object>

9. Make a copy of the current version of the file obj.conf and copy it to the back up version (so that the backup is consistent with the current version) in the following directory:

drive_letter:\Netscape\SuiteSpot\https-machinename\conf_bk

10. Restart the web server.

• Rename the gxisapi.dll library to gx.dll and leave it in the cgi-bin directory of the IIS wwwroot (inetput/wwwroot/cgi-bin/).
• Configure the ISAPI filter file, gx.dll, in the following registry entry:

My Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ 
W3SVC\Parameters\

Under Parameters, add string key, Filter DLLs, with the following value:

c:\inetpub\wwwroot\cgi-bin\gx.dll

1. Insert the Netscape Application Server Install CD-ROM into the CD-ROM drive.
2. Click Start on the Windows NT taskbar and click Run, or choose File - Run from the Windows NT Program Manager and click Run.
3. Click Browse and go to the CD-ROM drive (for example, d:\).
4. Open the NT folder and run the file setup.exe.
5. Follow the instructions of the installation program.
6. When prompted for the installation, click Netscape Servers.
7. When prompted for the installation type, click Typical.
8. Select the installation directory. The default directory is c:\Netscape\Server4. Note that if you use the default, Netscape Application Server is installed in c:\Netscape\Server4\nas.

You cannot use a directory name that includes spaces.

9. Choose Netscape Application Server 4.0 and click Change to select subcomponents.
10. Choose Administrator Component (Netscape Application Server Administrator) as the component you wish to install.
11. Review the Netscape Application Server Administrator configuration list.
12. When prompted for the Server Administrator user name and password, enter the user name and password to log on to the NAS Administrator tool.

You must specify one of the following:

• A user name and password combination that already exists on Directory Server
• A new user name and password combination, making sure that the user name is unique and does not already exist as part of a user name and password account on Directory Server.
13. After the installation program finishes running, reboot your machine.

• When uninstalling NAS, use the procedure described in this section. Do not uninstall NAS by deleting directories or modifying parameters in the registry.
• This procedure is for uninstalling NAS and its subcomponents only. If you installed Directory Server along with NAS, other servers may also have since been configured with that Directory Server. Uninstalling the Directory Server could cause problems for these other servers. Therefore, you should not uninstall Directory Server with NAS, unless you are absolutely certain that the only system configured with this installation of Directory Server is the NAS you are uninstalling.
• The following directories remain after you uninstall Netscape Application Server:

• Netscape Application Server root directory
• Any custom directories you created under the NAS directory
• nas install directory\APPS directory

After uninstalling NAS, decide if you want to remove these directories, particularly the custom and APPS directories which may contain applications you've developed and files you wish to keep.

• Before running the Netscape Application Server uninstallation program, make sure that Directory Server is running. Do not uninstall Directory Server before you uninstall NAS.
• During the uninstallation process, you are prompted to provide a username and password with administrator access to the configuration Directory Server. If you do not want to use the user name and password you entered at the beginning of the installation process, enter another user name and password, as long as it has administrator privileges on the configuration Directory Server.
• Some Netscape Application Server files remain in the installation directory after uninstalling. These files are marked by your machine's operating system for deletion and are removed when you reboot your machine. You must reboot immediately after you uninstall Netscape Application Server.
• If you do not reboot the machine after uninstalling Netscape Application Server and if you re-install Netscape Application Server immediately, you might receive missing file messages such as 'Cannot find gxutil.dll', and so on. Such errors occur if a file was unable to be removed during the uninstall process and hence it was marked for removal after system reboot. To prevent this behavior, reboot after uninstall and before re-installing the product.

1. Click the Uninstall icon in the Netscape Application Server 4.0 program group.
2. Follow the uninstall instructions.
3. Choose the components you wish to uninstall.

Note: During the uninstall of Netscape Application Server, you may be prompted by the following message to remove some shared libraries:

"Setup has determined that this is a shared file, but it is not being used by any other applications. Do you want to remove this file?"

Select "No to All" to indicate that you do not want to remove the shared libraries.

4. When prompted, enter a user name and password with administrator access to the configuration Directory Server. If you do not want to use the user name and password you entered at the beginning of the installation process (Step 14 on page 32), enter another user name and password, as long as it has administrator privileges on the configuration Directory Server.
5. Re-enter the configuration Directory Server information you entered in Step 4.
6. Reboot your system after you uninstall Netscape Application Server.
7. Remove the Netscape Application Server root directory.
8. Remove the Netscape Application Server item from the Start menu. To do so:

1. Click Start - Settings - Taskbar.
2. Click the Start Menu Programs tab.
3. Click Advanced.
4. Click Winnt - Profiles - All Users - Start Menu - Programs.
5. Remove the following items:

• Netscape Application Server 4.0
• Netscape Server Family

1. Click Start - Settings - Control Panel.
2. Click the Services icon.
3. Verify whether or not Netscape Application Server 4.0 is still listed as a service in the Services dialog box.
4. If Netscape Application Server 4.0 is still listed as a service, remove the Netscape key from the registry by running regedit. Search the following locations for the key:

• HKEY_LOCAL_MACHINE\Software\Netscape\Application Server\
• HKEY_LOCAL_MACHINE\System\CONTROLSET001
• HKEY_LOCAL_MACHINE\System\CONTROLSET002

• Table 1.1 Basic installation information
• Table 1.2 Directory Server installation information
• Table 1.3 Netscape Application Server installation information

Table 1.1 Basic installation information

No.	Data	Enter your value	Description
1	Machine IP address		The IP address of the machine on which you are installing Netscape Application Server (NAS)
2	Target installation /server root directory		The name of the directory where you want this installation to store files. The default is: c:\Netscape\Server4 See "Basic Installation Issues" on page 15 for details.
3	Netscape Server components	Netscape Server Family Core Components Netscape Directory Suite Administration Services Netscape Application Server	The Netscape server software you are installing. The first three items—Netscape Server Family Core Components, Netscape Directory Suite, and Administration Services—install Directory Server. The last item installs Netscape Application Server. See Step 9 on page 30 for details.
4	Netscape Application Server components	Web Connector plug-in component Netscape Application Server, without the Web Connector plug-in and without Netscape Application Server Administrator Netscape Application Server Administrator component Deployment Manager component	The Netscape Application Server component(s) you are installing. See "Basic Netscape Application Server Configuration Issues" on page 19 for details.

Table 1.2 Directory Server installation information

No.	Data	Enter your value	Description
1	Is Directory Server already installed at your site?	Yes No	Even if you decide to install Directory Server with this installation of NAS, another Directory Server may already be installed at your site. See "Directory Server Issues" on page 16 for details.
2	Do you want to install Directory Server as part of this installation?	Yes No	You can elect to install or not install Directory Server with this installation. See "Directory Server Issues" on page 16 for details.
3	Configuration Directory Server information	Host Name: ______________ Non-SSL Port:________________ Login ID (Bind As): ____________ Password: ____________________	The Host Name and Non-SSL Port Number of the configuration Directory Server. If you are installing Directory Server along with this installation of NAS, you must designate this Directory Server as the configuration Directory Server. See "Directory Server Issues" on page 16 for details.
4	Configuration Directory Server Administrator ID and Password	Administrator ID: ______________________ Password: ______________________	This is the Administrator ID and password to uninstall NAS and Directory Server. See "Directory Server Issues" on page 16 for details.
5	Storage Directory Server information	Host Name: ____________________ Login ID (Bind As): ____________________ Password: ____________________ Top-level domain name (Suffix): ____________________	If you are installing Directory Server as part of this installation, indicate that you want this Directory Server to be the storage directory. See "Directory Server Issues" on page 16 for details.
6	Settings for your existing Directory Server	Host Name (Server Identifier): ____________________ Port number: ____________________ Top-level domain name (Suffix): ____________________	If you are not installing Directory Server as part of this NAS installation, gather the information of the Directory Server that is already installed at your site. See "Directory Server Issues" on page 16 for details.
7	Administration Domain		The name of the Administration Domain where Netscape software information is stored on Directory Server. See "Directory Server Issues" on page 16 for details.
8	Directory Manager Distinguished Name and Password	Distinguished Name (DN): _____________________ Password: _____________________	Default value for the distinguished name is cn=Directory Manager. See "Directory Server Issues" on page 16 for details.
9	Directory Server Administration Server Port Number		Required for using the Console to administer Directory Server. See "Basic Installation Issues" on page 15 and "Directory Server Issues" on page 16 for details.
10	Global Configuration Name		The unique global configuration name of the configuration settings for this installation of NAS. See "Directory Server Issues" on page 16 for details.