Chapter 2 Installing Netscape Application Server on Unix

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

• Checking Hardware and Software Requirements
• Planning Your Installation
• Installing Netscape Application Server
• Using the Sample Applications
• Post-Installation and Troubleshooting 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 ns-slapd process 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 /Netscape/Server4. If you use this path, the Netscape Application Server installation directory is set to /Netscape/Server4/nas. 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).
• 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 (1025 to 32768) and must be unique (not used by any other applications on your system).

The default port numbers are as follows:

• 10817 for the Administrative Server (KAS)
• 10818 for the Executive Server (KXS)
• 10819 for the CGI to Executive Server (KXS) communication
• 10820 for the Java Server (KJS). You can configure multiple Java Servers.
• 10821 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.

• Decide if you want to install Netscape Application Server so that it starts up automatically when you boot your system. If you decide yes, then log on to the system as the root user before installing Netscape Application Server.

• 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.



• Know the full path location of the web server.
• If you are performing a webless installation of Netscape Application Server, 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 74 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.
• Install Netscape Application Server as the same user or as a member of the same group that installed the web server with which your Netscape Application Server will interface.
• For automatic configuration of the connector plug-in for Netscape Enterprise Server (version 3.6), know the instance directory (the directory where web server configuration and start/stop scripts are stored) of the installed web server.

• gxlib
• APPS
• registry
• kdb

• 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
Informix CLI 2.83	Informix Server 7.3

• Install and configure all database servers before installing Netscape Application Server.
• Know the directory paths of the different database client libraries installed on your system. You are asked during the installation if you want to configure Netscape Application Server with connectivity to supported databases. For each Yes response, you are prompted to provide the home directory for the database client and the database library name.

• 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 is nas install directory/CCS0/ TXNMGR_MIRROR/.

Note that this is the same path that is used to store the restart file. It is recommended that you store restart.bak in a different location than restart. Consider using a pointer to the different physical disk drive.

• 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 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

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 the Netscape Application Server Administrator tool without installing Netscape Application Server.
• Installs sample applications
• Installs and configures the Web Connector plug-in for Netscape Enterprise Server 3.6. 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 JRE 1.1.6 under the installation directory

1. Insert the Netscape Application Server Install CD-ROM into the CD-ROM drive.
2. Mount the CD-ROM on, for example, /cdrom/cdrom0.
3. At the shell prompt, run the following command:

/cdrom/cdrom0/solaris/setup

4. Follow the instructions of the installation program.

During installation, press:

CTL+B to back up to the previous screen within an installation section. An installation section is defined by the title at the top of the screen. For example, "Netscape Server Products," "Netscape Directory," and "Application" are names of sections within the installation program. You cannot use CTL+B to go back to a screen in a different section than the one you are currently in.

CTL+C if you need to exit the installation. This results in an incomplete installation. If you want to install again, you must run the installation program from the beginning, starting at Step 1 of this procedure.

5. When prompted, press Enter or specify 1 to select "Netscape Servers" as the item to install.
6. Specify 2 to select an installation type of Typical.
7. Specify a target installation directory as the base directory within which all components are installed. Do not include spaces in the path name.
8. When prompted for the components you want to install, do one of the following:

To install Netscape Application Server along with Directory Server, press Enter. This selects all of the following components.

• Netscape Server Family Core Components
• Netscape Directory Suite
• Administration Services
  This installs the Administration Services and Console, allowing you to administer your Netscape servers from the same machine as the Console.
• Netscape Application Server 4.0
  This installs Netscape Application Server, Netscape Application Server Administrator, the Web Connector plug-in used to communicate between NAS and the web server, and Deployment Manager.

The first three components (Netscape Server Family Core Components, Netscape Directory Suite, Administration Services) install Directory Server software. The last component installs Netscape Application Server and its associated components.

To install Netscape Application Server without Directory Server, type 4 (a NAS-only installation), and go to Step 12.

9. When prompted to install the Netscape Server Family Core Components, press Enter to select all of the components listed.
10. When prompted to install the Directory Suite components, press Enter to select all of the components listed.
11. When prompted to install the Administration Services components, press Enter to select all of the components listed.
12. When prompted to install Netscape Application Server components, press Enter if you want to install all the listed components.

1. NAS Web Connector Component
2. Core Server Component (NAS without the Web Connector plug-in)
3. Administrator Component (Netscape Application Server Administrator)
4. Deployment Manager

If you want to install NAS without the Web Connector plug-in, specify 2 (Core Server Component) and 3 (Administrator Component) and proceed to Step 13.

If you want to install only the NAS Web Connector, specify 1 only and proceed to the section "Installing the Web Connector Plug-in."

If you want to install only the Administrator (Netscape Application Server Administrator), specify 3 only and proceed to the section "Installing Netscape Application Server Administrator."

If you want to install only the Deployment Manager, specify 4 only and press Enter to complete the installation process.

13. Specify the domain name of your machine. Press Enter to accept the default value provided here by the installation program.
14. Specify the Unix user and group name under which your Netscape Application Server and Directory Server installations will run.

You should have already set up this user and group prior to running the installation program. Specify a user that has no privileges elsewhere on the system, so as to avoid access to restricted servers, such as the configuration Directory Server, from NAS.

15. If you specified in Step 8 that you do not want to install Directory Server, enter the URL of the configuration Directory Server for this installation of NAS, and then go to Step 23.

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

16. If you are installing Directory Server with this installation of NAS, specify this Directory Server as the configuration Directory Server. Only specify an existing Directory Server as the configuration Directory Server if you are not installing Directory Server with this installation of NAS.
17. If you are installing Directory Server with this installation of NAS, specify this Directory Server as the storage server. Only specify an existing Directory Server as the storage server if you are not installing Directory Server with this installation of NAS.

If you specify an existing installation as the storage Directory Server, enter the following information:

• 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
18. Enter the port number to be used by the Directory Server you are installing. The default value is 389.
19. When prompted for the Directory Server identifier, enter the host name of the Directory Server machine.
20. Enter the administrator ID and password for the configuration Directory Server.

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.

21. When prompted for the suffix, enter the top level domain name.
22. Enter the Directory Manager distinguished name (DN) and password. The default value for the distinguished name is cn=Directory Manager
23. Enter the name of the Administration Domain where Netscape software information is stored on Directory Server.
24. Enter the port number for the Directory Server Administration Server. This is required for using the Console to administer the Directory Server.
25. Confirm the user which the Administration Server will run as.

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

26. Enter the host name of the current machine on which you are installing Netscape Application Server.
27. If you installed Directory Server earlier during this installation process (Step 13 through Step 25), indicate that you want NAS to be configured with this Directory Server.

If you did not install Directory Server earlier during this installation process, provide the following information about the already existing Directory Server that you want NAS to be configured with:

• Server identifier
• Host name
• Port number
• Username (same value you entered in Step 22)
• User password (same value you entered in Step 22)
28. 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.
29. Enter the product key of Netscape Application Server. The product key is available in the Welcome letter you received with the product.
30. When prompted, enter port numbers for the Administrative Server (KAS), the Executive Server (KXS), and the web server (CGI to KXS).

All port numbers you specify are for listener ports, must be within the acceptable range (1025 to 32768), and must be unique (not used by any other services on your system). In most cases, the default port numbers supplied by the installation program are adequate.

31. Enter the number of Java Servers (KJS) that you intend to use to process applications with this installation of Netscape Application Server, and the port number(s) for the Java Server(s).

All Java Server port numbers you specify are for listener ports and must be within the acceptable range of 1025 to 32768. Port numbers must be unique (not used by any other services on your system). In most cases, the default port numbers supplied by the installation program are adequate.

32. Enter the number of C++ Servers (KCS) that you intend to use to process applications with this installation of Netscape Application Server, and the port number(s) for the C++ Server(s).

All C++ port numbers you specify are for listener ports and must be within the acceptable range of 1025 to 32768. Port numbers must be unique (not used by any other services on your system). In most cases, the default port numbers supplied by the installation program are adequate.

33. When prompted for the Server Administrator username and password, enter the username and password to log on to the NAS Administrator tool.
34. Provide all the necessary database connectivity information.

The installation program lists the database clients supported by Netscape Application Server. The clients are required for your NAS applications to process data. You must indicate if you want to configure this instance of Netscape Application Server to connect with each of the supported database clients. For each client that you specify Yes, you must provide the installation program with the client's home directory and library name.

For more information about prioritizing and configuring databases, see "Database Configuration Issues" on page 82.

35. If you specified at least one database in Step 34, rank the installed databases in priority order. Specify the top priority database first. (If you only specified one database in Step 34, then list that one here as the top priority database).
36. Enter the mirror directory path where the transaction manager restart.bak file of each KJS process gets stored.

The default directory is nas install directory/CCS0/ TXNMGR_MIRROR/. This is the same path that is used to store the restart file. It is recommended that you store restart.bak in a different location than restart. Consider using a pointer to the different physical disk drive.

37. For each Java Server specified in Step 31, specify the following information:

• Log volume disk name where the transaction manager log file gets stored. The default name is nas install directory/CCS0/TXNMGR/ENGnumber, where number represents the KJS engine process number.
• Whether or not the log volume disk is a raw partition. If you specify Yes, make sure that the name you enter here is that of a raw device.
• If the log volume disk 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 4KB per page.
38. When prompted, indicate if you want to enable resource manger.
39. If you answer Yes in Step 38, specify the number of resource managers you want to enable.
40. If you answer Yes in Step 38, specify the following information for each resource manager:

• User-defined resource manager name
• Database type
• Open string (See "Resource Manager Open String Information" on page 85 for information about open string formats)
• Whether or not the resource manager is enabled
41. When prompted whether the server will synchronize data across servers (Dsync), specify Yes if you intend to synchronize session and state information across multiple servers for failover and fault tolerance. If you specify No, then proceed to Step 47.

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

To proceed with data synchronization, also referred to as cluster configuration, you must plan your clusters ahead of time. For information about planning clusters, see "Clustering and Data Synchronization Issues" on page 86.

42. When prompted for the cluster name, enter the name of the cluster that this Netscape Application Server will belong to.

The cluster you specify may already exist, or this installation of Netscape Application Server may be the first server assigned to the cluster.

43. Indicate if this instance of Netscape Application Server is a Sync Server or a Sync Local.
44. Enter the number of Sync Servers that you plan to have in the cluster.
45. For each Sync Server in the cluster, specify the following information:

• IP address
• Sync Server priority-You are asked to start by specifying the highest priority Sync Server in the cluster, that is, the server that is first in line to take over for the Sync Primary if it fails. Next, you are asked to specify the next highest priority Sync Server, and so on, until you have ranked all the Sync Servers you specified in Step 44.

For each installation of a Netscape Application Server within the cluster you specified in Step 42, specify the same set of IP addresses and port numbers. The addresses and port number configurations must match across installations for the cluster to function properly.

46. Specify the number of Sync Backup servers that should be active while the cluster is running.
47. Indicate whether or not you want to run Netscape Application Server automatically when you reboot the machine. You can only complete this step if you are logged on as root.

version

[Database shell script file name] [DataSource] [Database] [DB User] 
[DB Password] [Resource manager name] 

• setup_ora.sh
• setup_syb.sh
• setup_db2.sh

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 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.

make -f makefile

1. Start the 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.

[Database shell script file name] [DataSource] [Database]
[DB User] [DB Password]

• setup_ora.sh
• setup_syb.sh
• setup_db2.sh

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

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.

make -f makefile

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.

• The Netscape Application Server user and the web server user must either be the same or from the same group. If the web server is installed as a regular user and the Netscape Application Server user is installed as the root user, a file permission problem will exist. The web server won't start because it won't have access to the registry file reg.dat.
• If Netscape Enterprise Server 3.6 has been installed as root, the user must have root access to start it.
• After installing Netscape Application Server, make sure that the NAS gxlib directory (nas install directory/nas/gxlib) and the registry directory (nas install directory/nas/registry) are accessible by the web server owner and user.

• Check for required Solaris patches. See the readme file for information about how to determine what patches you need.
• Ensure that "CGI file type" is enabled on your web server. For Netscape Enterprise Server, go to the Server Administrator page, and under the Programs folder, click Yes for CGI file type.
• When running applications, if the NAS Class Loader is unable to find the AppLogic class file through the SYSTEM_JAVA parameter (the registry parameter that contains both the CLASSPATH and GX_CLASSPATH settings), NAS hands the request over to the JAVA Class Loader, which in turn reads the CLASSPATH environment variable to find the class file. This allows AppLogics and servlets to execute even if the user classpath is not specified.

• For Bourne Shell:

DSQUERY=sybase servername; export DSQUERY

• For C Shell:

setenv DSQUERY sybase servername 

• For Bourne Shell:

ORACLE_SID=oracle SID export ORACLE_SID

ORACLE_HOME=oracle install directory; export ORACLE_HOME

• For C Shell

setenv ORACLE_SID oracle SID

setenv ORACLE_HOME oracle install directory

• For Bourne Shell:

DB2INSTANCE= db2instance; export DB2INSTANCE

• For C Shell

setenv DB2INSTANCE db2instance

• For Bourne Shell:

INFORMIXSERVER=informixserver; export INFORMIXSERVER

• For C Shell

setenv INFORMIXSERVER informixserver 

[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

set strmsgsz=0

• 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.
• Log on as the root user, or as a user from the same group as the root user, who installed Netscape Application Server before installing the Web Connector plug-in

1. After you finish installing Netscape Application Server as a webless installation, take the installation CD-ROM to the machine or machines that host the web server.
2. Mount the CD-ROM on, for example, /cdrom/cdrom0.
3. At the shell prompt, run the following command:

/cdrom/cdrom0/solaris/setup

4. Follow the instructions of the installation program.
5. When prompted, press Enter or specify 1 to select "Netscape Servers" as an installation.
6. Specify 2 to select an installation type of Typical.
7. Specify a target installation directory. Do not include spaces in the path name.
8. When prompted for the components you want to install, specify 4 to select a NAS-only installation.
9. When prompted to install the Netscape Application Server components, specify 1 to select the NAS Web Connector Component.
10. Specify the domain name of your machine. Press Enter to accept the default value provided here by the installation program.
11. Specify the Unix user and group name under which your Netscape Application Server and Directory Server installations will run.

You should have already set up this user and group prior to running the installation program. Specify a user that has no privileges elsewhere on the system, so as to avoid access to restricted servers, such as the configuration Directory Server, from NAS.

12. Enter the URL of the configuration Directory Server that your NAS installation was configured with. This is the same URL you entered in Step 15 on page 91 of "Installing Netscape Application Server."
13. Enter the name of the Administration Domain where Netscape software information is stored on Directory Server. You must enter the same name you entered in Step 23 on page 92 of "Installing Netscape Application Server."
14. Enter the administrator ID and password for the configuration Directory Server. You must enter the same ID and password you entered in Step 20 on page 92 of "Installing Netscape Application Server."

Important: This is the Administrator ID and password required to uninstall the Web Connector plug-in. Make a note of this information, as you will need it if you uninstall the Web Connector plug-in.

15. Enter the host name of the current machine on which you are installing the Web Connector plug-in.
16. Provide the following information about the Directory Server you configured NAS with (you must enter the same information you entered in Step 27 on page 92):

• Server identifier
• Host name
• Port number
• Username
• User password
17. Enter the path of the web server instance, or enter `cgi,' if you are using CGI.
18. Enter the IP address of the machine where NAS is installed.
19. Enter the port number for the web server to Executive Server (KXS) communication, specified earlier (Step 30 on page 93) when you installed NAS without the Web Connector plug-in.

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.

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:

netscape home dir/https-machinename/conf_bk

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

For example:

Netscape home dir/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 root/gxlib/libgxnsapi30.so" 

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:

netscape home dir/https-machinename/conf_bk

10. Modify the web server's start and stop scripts as follows:

In the start script:

• Set GX_ROOTDIR to the directory in which Netscape Application Server is installed. For example:

GX_ROOTDIR=nas install directory; export GX_ROOTDIR

• Set LD_LIBRARY_PATH to gxlib under the Netscape Application Server installation directory. For example:

LD_LIBRARY_PATH=nas install directory/gxlib:$LD_LIBRARY_PATH;

export LD_LIBRARY_PATH

1. Restart the web server.

1. After you finish installing Netscape Application Server, insert the installation CD-ROM into the CD-ROM drive of the machine where you want to install Netscape Application Server Administrator.
2. Mount the CD-ROM on, for example, /cdrom/cdrom0.
3. At the shell prompt, run the following command:

/cdrom/cdrom0/solaris/setup

4. Follow the instructions of the installation program.
5. When prompted, enter 1 to specify "Netscape Servers."
6. Specify 2 to select an installation type of Typical.
7. Enter a target installation directory. Do not include spaces in the path name.
8. When prompted for the components you want to install, specify 4 to select a NAS-only installation.
9. When prompted to install the Netscape Application Server components, specify 3 to select the NAS Administrator Component.
10. Enter the domain name of your machine. Press Enter to accept the default value provided here by the installation program.
11. Enter the Unix user and group name under which your Netscape Application Server and Directory Server installations will run.

You should have already set up this user and group prior to running the installation program. Specify a user that has no privileges elsewhere on the system, so as to avoid access to restricted servers, such as the configuration Directory Server, from NAS.

12. Enter the host name of the current machine on which you are installing the Netscape Application Server Administrator.
13. 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.

• 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
• The nas install directory/APPS directory, which is moved by the uninstallation program to NAS server root/nas_APPS/.

After uninstalling NAS, decide if you want to remove these directories, particularly the APPS directory 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.
• The uninstall program overwrites the web server configuration file (obj.conf) with a version of the same file that existed before you installed Netscape Application Server and the Web Connector plug-in. Therefore, all changes you made to the web server's obj.conf file after installing Netscape Application Server and the Web Connector plug-in are lost.
• Some Netscape Application Server files may remain after running the uninstall program due to locks that the operating system or NFS might have. Remove such files manually.

1. From the Netscape installation directory (the default is /usr/netscape/server4), type uninstall and press Enter.
2. Follow the uninstall instructions.
3. Specify the components you want to uninstall.
4. Enter a user ID and password that has administrator privileges on 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 20, page 92) enter another user name and password, as long as it has administrator privileges on the configuration Directory Server.

• Table 2.1 Basic installation information
• Table 2.2 Directory Server installation information
• Table 2.3 Netscape Application Server installation information

Table 2.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: /Netscape/Server4 See "Basic Installation Issues" on page 75 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 8 on page 89 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 79 for details.
5	Domain name for this machine		The domain name of the machine on which you are installing NAS
6	User and group name under which your NAS and Directory Server installations will run	User name: ___________ Group name: _________	The user and group name under which your NAS and Directory Server installations will run. These should already be set up prior to running the NAS installation. See Step 14 on page 91 for details.

Table 2.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 76 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 76 for details.
3	Configuration Directory Server information	Host Name: _______________ Non-SSL Port:_________________ Login ID (Bind As): _____________ Password: _____________________	The host name, non-SSL port number, login ID, password, and URL of the configuration Directory Server. If you are installing Directory Server as part of this NAS installation, you must designate this Directory Server as the configuration Directory Server. See "Directory Server Issues" on page 76 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 76 and Step 20 on page 92 for details.
5	Storage Directory Server information	Host Name: _____________________ Login ID (Bind As): _____________________ Password: _____________________ Top-level domain name (Suffix): _____________________	See "Directory Server Issues" on page 76 for details.
6	Settings for the Directory Server you are installing with this installation of NAS.	Host Name (Server Identifier): _____________________ Port number: _____________________ Top-level domain name (Suffix): _____________________	See "Directory Server Issues" on page 76 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 76 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 76 for details.
9	Directory Server Administration Server Port Number		Required for using the Console to administer Directory Server. See "Basic Installation Issues" on page 75 and "Directory Server Issues" on page 76 for details.
10	Administration Server User		The user which the Administration Server will run as. See Step 25 on page 92 for details.

Table 2.3 Netscape Application Server installation information

No.	Data	Enter your value	Description
1	Machine host name		The host name of the current machine on which you are installing NAS. See Step 26 on page 92.
2	Global Configuration Name		The unique global configuration name of the configuration settings for this installation of NAS. See "Directory Server Issues" on page 76 for details.
3	Product key		The product key for this installation of NAS. See "Basic Netscape Application Server Configuration Issues" on page 79 for details.
4	Webless installation	Yes No	Decide if you are installing NAS on a machine where the web server is also installed or if NAS is on a separate machine (webless).
5	Web server	NES 3.6 None (webless) Other	The kind of web server this installation of NAS will use. See "Web Server Configuration Issues" on page 80 for details.
6	Web server path and instance name		The path for the web server and the web server instance name. If you are using CGI, enter "cgi." See "Web Server Configuration Issues" on page 80 for details.
7	Number of Java Servers (KJS)		The number of Java Servers to be used to process applications. See "Basic Netscape Application Server Configuration Issues" on page 79 for details.
8	Number of C++ Servers (KCS)		The number of C++ Servers to be used to process applications. See "Basic Netscape Application Server Configuration Issues" on page 79 for details.
9	Administrative Server (KAS) port number		The port number on this machine for your Administrative Server. See "Basic Netscape Application Server Configuration Issues" on page 79 for details.
10	Executive Server (KXS) port number		The port number on this machine for your Executive Server. See "Basic Netscape Application Server Configuration Issues" on page 79 for details.
11	Web server port number		Specifies the CGI to KXS connection. Only required if using CGI. See "Basic Netscape Application Server Configuration Issues" on page 79 for details.
12	Java Server (KJS) port number(s)		The port number(s) on this machine for your Java Server(s). See "Basic Netscape Application Server Configuration Issues" on page 79 for details.
13	C++ Server (KCS) port number(s)		The port number(s) on this machine for your C++ Server(s) See "Basic Netscape Application Server Configuration Issues" on page 79 for details.
14	Administration Server user ID and password	User ID: _____________ Password: ____________	User ID and password to log on to the Administration Server via the Netscape Application Server Administrator tool. Account must already exist on Directory Server. See Step 33 on page 93 for details.
15	Database client directory, library, and priority	Oracle: Yes / No Home directory: Library: Priority: Informix: Yes / No Home directory: Library: Priority: Sybase: Yes / No Home directory: Library: Priority: IBM DB2: Yes / No Home directory: Library: Priority:	The databases this server will connect to, the home directory of each database, the library name, and the priority rating for attempting the connection. See "Database Configuration Issues" on page 82 and Step 34 on page 94 for details.
16	Mirror directory path		The location of the transaction manager restart.bak file for each Java Server (KJS). See "Transaction Manager Issues" on page 83 for details.
17	Log volume disk name	KJS1:________________ KJS2:________________ KJS3:________________ KJS4:________________	The name of the disk where the transaction manager log file is stored for each Java Server (KJS). See "Transaction Manager Issues" on page 83 for details.
18	Is the log volume disk a raw partition?	Yes No	It is strongly recommended that you create a raw partition prior to running the installation program, for dedicated storage of the transaction manager log file of each Java Server (KJS). See "Transaction Manager Issues" on page 83 for details.
19	If the log volume disk is a raw partition, number of pages and starting page number	Size (No. of pages): _____ Offset value (Starting page number): _________	During installation, you must specify the number of pages (total must be greater than 4 MB) and a starting page number for the log volume disk. See "Transaction Manager Issues" on page 83 for details.
20	Do you want to configure this installation of NAS with resource manager?	Yes No	Resource manager lets you connect to a database back end for global transactions. See "Resource Manager Issues" on page 85 for details.
21	Number of resource managers		You can configure multiple resource managers, one for each database back end you want to connect to with a global transaction. See "Resource Manager Issues" on page 85 for details.
22	For the first resource manager, provide the following details: Resource Manager user-defined name Database type Open string Is the resource manager enabled?	User-defined name:________________ Database type: Oracle Sybase DB2 Open string: ___________ _____________________ _____________________ _____________________ _____________________ Enabled: Yes No	For each resource manager you configure, provide this set of information. Configure one resource manager per database back end that you want to connect to. This worksheet lets you write down information for up to four resource managers, but you are not limited to this number. See "Resource Manager Issues" on page 85 for details.
23	If you want to use a second resource manager, provide the following details: Resource manager user-defined name Database type Open string format Is the resource manager enabled?	User-defined name:________________ Database type: Oracle Sybase DB2 Open string: ___________ _____________________ _____________________ _____________________ _____________________ Enabled: Yes No	For each resource manager you configure, provide this set of information. Configure one resource manager per database back end that you want to connect to. This worksheet lets you write down information for up to four resource managers, but you are not limited to this number. See "Resource Manager Issues" on page 85 for details.
24	If you want to use a third resource manager, provide the following details: Resource manager user-defined name Database type Open string format Is the resource manager enabled?	User-defined name:________________ Database type: Oracle Sybase DB2 Open string: ___________ _____________________ _____________________ _____________________ _____________________ Enabled: Yes No	For each resource manager you configure, provide this set of information. Configure one resource manager per database back end that you want to connect to. This worksheet lets you write down information for up to four resource managers, but you are not limited to this number. See "Resource Manager Issues" on page 85 for details.
25	If you want to use a fourth resource manager, provide the following details: Resource manager user-defined name Database type Open string format Is the resource manager enabled?	User-defined name:________________ Database type: Oracle Sybase DB2 Open string: ___________ _____________________ _____________________ _____________________ _____________________ Enabled: Yes No	For each resource manager you configure, provide this set of information. Configure one resource manager per database back end that you want to connect to. This worksheet lets you write down information for up to four resource managers, but you are not limited to this number. See "Resource Manager Issues" on page 85 for details.
26	Will this installation of NAS participate in data synchronization?	Yes No	Distributed data synchronization also referred to as clustering, maintains the integrity of multiple Netscape Application Servers. See "Clustering and Data Synchronization Issues" on page 86 for details.
27	Cluster name (Applies only to data synchronization)		The name of the cluster that this server will belong to. See "Clustering and Data Synchronization Issues" on page 86 for details.
28	Sync Server Status (Applies only to data synchronization)	Sync Server Sync Local	Is this installation a Sync Server (eligible to become a Sync Primary) or a Sync Local (not eligible to become a Sync Primary, Sync Backup, or Sync Alternate)? See "Clustering and Data Synchronization Issues" on page 86 for details.
29	Number of Sync Servers (Applies only to data synchronization)		How many additional Sync Servers will exist in the cluster that this installation belongs to? See "Clustering and Data Synchronization Issues" on page 86 for details.
30	Sync Server machine addresses, port numbers, and priority (Applies only to data synchronization)	Address: Port number: Priority: Address: Port number: Priority: Address: Port number: Priority: Address: Port number: Priority:	What are the IP addresses of each Sync Server in the cluster, their corresponding port numbers, and their priority rating? See "Clustering and Data Synchronization Issues" on page 86 for details.
31	Number of Sync Backups		The number of Sync Backups in the cluster. See "Clustering and Data Synchronization Issues" on page 86 for details.
32	Run NAS automatically when you reboot machine	Yes No	Indicate if you want NAS to start up automatically whenever this machine reboots. See Step 47 on page page 96.