iPlanet

iPlanet Deployment Guide

Contents

iPlanet Directory Server
iPlanet Web Server
iPlanet Portal Server
iPlanet Messaging Server
iPlanet Calendar Server
Certificate Management System
iPS:Instant Collaboration Pack
Unified Development Server-UDS
iPlanet Integration Server
iPlanet Message Queue
Preparing for Multiple Server Installations

iPlanet Directory Server

iPlanet Directory Server (iDS) is a scalable distributed directory server based on Lightweight Directory Access Protocol (LDAP). iDS creates a centralized and distributed data repository that can be used in an intranet, over the extranet with trading partners, or over the public internet to reach all customers.

System Requirements

Before you can install the iDS, make sure you have met the minimum hardware and operating system requirements. The basic minimum requirements are as follows:

Roughly 200 MB of disk space for a bare-bones installation. For production systems, you should plan at least 1 GB to support the product binaries, database, and log files; 2 GB and greater may be required for very large directories.

32 MB of RAM. However, you should plan from 256 MB to 1 GB of RAM for best performance on large production systems.

Installation

Type of Installation: Typical
The other forms of Installation are described in the Installation Guide
The setup script file will be available in /iDS/iDS416/DS416 under the name setup

Would you like to continue with installation? [Yes]:
Do you agree to the license terms? [No]: Type yes and Press Enter
Select the component you want to install [1]:
Choose an installation type [2]:
Install location [/usr/netscape/server4]: to accept the default server root directory. (If you are not installing as root, you will not have permission to create directories in /usr so you will have to choose another location.)
Specify the components you wish to install [All]:
Specify the components you wish to install [1, 2, 3]:
Specify the components you wish to install [1, 2]:
Specify the components you wish to install [1, 2]:
Computer name [myhost.mydomain.com]: to install on the local machine.
System User [nobody]: Enter the user that the configuration/user Directory Server process will run as. Where your system supports it, accept the default user, nobody, creating that user as necessary.
System Group [nobody]: Enter the group that the configuration/user Directory Server process will run as. Where your system supports it, accept the default group, nobody, creating that group as necessary.
Do you want to register this software with an existing Netscape configuration directory server? [No]: to install a new configuration directory.
Do you want to use another directory to store your data? [No]: to use the new configuration directory as your user/group directory.
Directory server network port [389]: to accept the default, 389 . If you are not installing as root or if 389 is in use, the default will be a random number; you may want to change this number to something easy to remember, such as 38989.
Directory server identifier [myhost]: Type configdir as the unique identifier for the configuration directory, and press Enter.
Netscape configuration directory server administrator ID [admin]: to accept the default, then enter the <admin password>.
Suffix [o=mydomain.com]: to accept the default.
Directory Manager DN [cn=Directory Manager]: to accept the default, then enter the <dir mgr password>.
Administration Domain [mydomain.com]: to accept the default.
Administration port [random #]: Type 4444 and press Enter.
Run Administration Server as [root]: to accept the default.

iPlanet Web Server

iPlanet Web Server (iWS) incorporates a modular architecture that integrates seamlessly with all of the products in the iPlanet family of servers. In addition, iWS includes an administration server interface for coordinating administrative functions across all of your web servers.
iPlanet Web Server Component Options - The following component options are available when you install iWS:

iPlanet Web Server Core
Java Runtime Environment
Java and Servlets
SNMP

System Requirements

The hardware and software requirements for iWS are:

Swap space at least as large as the amount of RAM on your system (twice the amount of RAM is recommended). Linux requires 256 MB swap space.

Netscape Communicator 4.72 or higher, or Microsoft Internet Explorer 5.0 or higher.

Java and cookies enabled in your browser.

A Java Development Kit (JDK), also known as a Java 2 Software Development Kit (SDK) installed on your system if you plan to use uncompiled Java Server Pages (JSPs).

iPlanet Web Server requires the following versions of the JDK:

Operating Environment JDK Version
Solaris JDK 1.2.2_07
Linux: JDK 1.2.2
HP-UX JDK 1.2.2_07
AIX JDK 1.2.2
Tru64 JDK 1.2.2-8

Installation

Type of Installation: Typical
The other forms of Installation are described in the Installation Guide.
The setup script file will be available in /iWS/enterprise under the name setup

Would you like to continue with installation? [Yes]:
Do you agree to the license terms? [No]: Type yes and
Choose an installation type [2]: Press Enter.
Install location [/usr/iplanet/servers]: to accept the default server root directory. (If you are not installing as root, you probably will not have permission to create directories in /usr so you will have to choose another location.)
Specify the components you wish to install [All]:
Specify the components you wish to install [1, 2, 3, 4, 5]: 1, 2, 3, 4, 5
Computer name [myhost.mydomain.com]: to install on the local machine.
System User [nobody]: Enter the user that the configuration/user Directory Server process will run as. Where your system supports it, accept the default user nobody, creating that user as necessary.
System Group [nobody]: Enter the group that the configuration/user Directory Server process will run as. Where your system supports it, accept the default group nobody, creating that group as necessary.
Run iWS Administration Server as [root]: Press Enter to accept default.
iWS Admin Server User Name [admin]: to accept default.
iWS Admin Server Password: Type password.
iWS Admin Server Password: Type password.
iWS Admin Server Port [8888]: Press Enter to accept default
Web Server Port [80]: Press Enter to accept default. If not logged as root, then give any number greater than 1024.
Web Server Content Root [/space/iws/docs]: to accept default
Do you want to use your own JDK [No]: Press Enter

For detailed documentation visit iPlanet Web Server page.

iPlanet Portal Server

A portal is a community-based web site that securely holds a collection of data related to different topics, including such things as news and stock quotes, applications, and services. The iPlanet Portal Server (iPS) is a full-service platform that provides the membership management, personalization, aggregation, security and integration services needed to quickly deploy today's most demanding e-commerce portals. With the iPS platform, companies can quickly roll out a highly scalable and reliable portal for customer, supplier, partner and employees. The available data content may be customized by users with write permission to change providers, display of data, and links to other allowable web sites from those available. Services can include the use of provider applications and utilities; for example email and file management and storage facilities. A corporate portal is a personalized web page that brings together data and productivity tools relevant to corporate users. Corporate users can include employees, vendors, marketing partners, customers, and allied business users.
Portal Server software has two main components:

The gateway component of the Portal Server product
The server component of the Portal Server product
For security reasons, the recommended installation is to put the gateway component of the Portal Server product on a computer separate from the server component. The server component and gateway component can, however, be installed on the same computer if you choose to do so.
System Requirements

The hardware and software requirments for iPS are:

Portal Server software runs in the Solaris^TM 2.6, 7, and 8 operating environments.

Portal Server software ideally uses two computers; one computer to function as a gateway between the Internet and your internal network (the gateway component of the Portal Server product) and one computer to function as a platform and applications server (the server component of the Portal Server product).

Computer Type - an E250 with 300 MHz processor is recommended for both the gateway component and server component of the Portal Server product.

Memory - the gateway component and the server component of the Portal Server product should each have a minimum of 128 Mbytes of memory.

Disk space - the gateway component of the Portal Server product should have a minimum of 100 Mbytes of free disk space; the server component of the Portal Server product should have a minimum of 500 Mbytes of free disk space.

Software - co-existence with other software is not supported.

Network Interfaces - if you choose to install the optional firewall on the gateway component of the Portal Server product, the computer on which you install the firewall should have more than one network interface.

Installation

Type of Installation: Typical
The other forms of Installation are described in the Installation Guide.
The setup file will be available in iPS/iPS under the name ipsinstall. This is a package and hence should be installed using the command pkgadd.
NOTE: It is necessary to install the patches before installing the Portal Server. The patches can be obtained from iPS/iPS/patches under the name install_cluster. This will install the required patches needed by the system. Once the patches are installed, the ipsinstall script can be run.

This product will run without a license. However, purchase a license from Sun Microsystems to use this product.
    Do you accept? [y]/n: Type y and
What is the iPS hostname of this machine? [hostname]:
What is the sub domain ("." for none)? [SubDomain]:
What is the domain? [MyOrganisation.Com]:
What is the ip address of Myhostname.Domain.com [xxx.xxx.xxx.xxx]: Type the correct ip address and Press Enter
Select which component to install:
1) Server
2) Gateway
3) Exit
Choice? [3]: Type 1 and
What directory to install in? [/opt]: to accept the default server root directory. (If you are not installing as root, you probably will not have permission to create directories in /opt so you will have to choose another location.)
Will this be an open portal install? y/[n]:
Are the servers using SSL protocol? y/[n]:
Is this a multiple server install? y/[n]:
The profile server will run on hostname.domain.com
On what port will the profile server run? [8080]:
What is the root of the profile role tree? [Organisation.COM]:
What is the user for the profile role tree? [root]:
On what port will the directory server run? [389]:
On what port will the gateways run? [443]:
Is this a multiple gateway install? y/[n]:
On what hostname will the gateway run? [MyGateway]:
What is the sub-domain name for hostname ("." for none)?:
What is the domain name for hostname? [Organisation.COM]:
Should the gateway(s) use a web proxy? y/[n]:
What is the administrator port for the web server? [8088]:
What is the pass phrase (8 characters minimum): password
Re-enter pass phrase : password
Start after installation completes? [y]/n:

For detailed documentation visit iPlanet Portal Server page.

iPlanet Messaging Server

iPlanet Messaging Services create an efficient and secure communication infrastructure to keep businesses in touch with their customers, suppliers, and partners. Information and ideas can be exchanged rapidly around the world, independent of time zones and geographical locations. The information contained in messages can also be encrypted and authenticated, providing for secure communications. Messaging Services also provide powerful capabilities for attracting customers to such services as webmail, unified messaging, and Intranet hosting. Messaging Services can be tightly integrated with Directory Services, so that users and their messaging accounts can be easily managed from a central location, independent of the server they actually use to process their messages.

System Requirements

The minimum hardware requirements for Messaging Server are:

Approximately 500 MB of disk space for a standard installation. For production systems, you should plan at least 1 GB to support the product binaries.

128 MB of RAM. For production systems, you should have a minimum of 256 MB of RAM.

Adequate space for your user mailboxes (message store), database, log files, and message queue directory. These can grow in size dramatically depending on the size of your site, so be sure to allocate space accordingly.

RAID (Redundant Array of Independent Disk) storage for fast access (optional).

Installation

Type of Installation: Typical
The other forms of Installation are described in the Installation Guide.
The setup script file will be available in iMS/iMS under the name setup

Would you like to continue with installation? [Yes]:
Do you agree to the license terms? [No]: Type yes and
Select the component you want to install [1] : Type 1
Choose an installation type [2]: Type 2
Install location [/usr/iplanet/server5]: to accept the default server root directory. (If you are not installing as root, you probably will not have permission to create directories in /usr so you will have to choose another location.)
Specify the components you wish to install [All]:
Specify the components you wish to install [1, 2, 3]:
Specify the components you wish to install [1, 2]:
Specify the components you wish to install [1, 2]:
Specify the components you wish to install [1, 2, 5]:
Computer name [myhost.mydomain.com]: to install on the local machine.
System User [nobody]: Enter the user that the configuration/user Directory Server process will run as. Where your system supports it, accept the default user, nobody, creating that user as necessary.
System Group [nobody]: Enter the group that the configuration/user Directory Server process will run as. Where your system supports it, accept the default group, nobody, creating that group as necessary.
Do you want to register this software with an existing Netscape configuration directory server? [No]: Press Enter to install a new configuration directory.
Do you want to use another directory to store your data? [No]: to use the new configuration directory as your user/group directory.
Directory server network port [389]: Press Enter if logged in as root. Else type any number greater than 1024.
Directory server identifier [hostname]:
iWS Admin Server User Name [admin]: to accept default.
iWS Admin Server Password: Type password.
iWS Admin Server Password: Type password.
Directory Manager DN [cn=Directory Manager]:
Password: Type password.
Password (again): Type password.
Administration Domain [Myorganisation.com]: Press Enter.
Administration port [random#]: Type a valid and available port.
Run Administration Server as [root]:
User Name [mailsrv]: Type nobody or any existing user.
Default Domain [MyOrganisation.MyDomain.com]:
Default Organization DN [o=india.sun.com, o=sun.com]:
Host Name [Hostname]:
Port [8080]:
Will the Messaging Server use a Smart Host [2]:
User ID [ServiceAdmin]: Press Enter or type a valid user name.
User Password: Type password.
Confirm Password: Repeat password.
Email Address [ims]: admin@hostname.domainname.com

For detailed documentation visit iPlanet Messaging Server page.

iPlanet Calendar Server

iPlanet Calendar Server is a readily deployable, LDAP-based solution that lets the ISP and Telecommunication service provider offer group scheduling features, as well as host personal event calendars, to their base of subscribed customers.
iPlanet Calendar Server 5.0 is a system of servers that can be configured to fit a variety of needs. It can stand in isolation as a stand-alone calendar server, or it can be configured with many instances, having the various services duplicated or split between them. It stores and manages calendars, calendar properties, access control information, events, to-dos, and alarms. It does not manage storage for user information. The minimal system requires a directory service. It makes use of plug-ins to obtain external services. It uses a directory service to perform operations such as authentication, and storage and retrieval of user preferences.
The iPlanet Calendar Server 5.0 system consists of several running processes that include multiple calendar server daemons, which can run on a single machine or be divided to run on multiple machines.
System Requirements:

The minimum hardware requirements for iPlanet Calendar Server 5.0 are:

Approximately 500 MB of disk space for a standard installation. For production systems, you should plan at least 1 GB to support the product binaries.

28 MB of RAM. For production systems, you should have between 256 MB to 1 GB of RAM for best performance.

RAID storage for fast access (optional).

Installation

Type of Installation: Typical
The other forms of Installation are described in the Installation Guide.
The setup script file will be available in iCS/iCS under the name setup. This installation supports both GUI based and command line based setup.

Do you agree to the license terms? [No]: Type yes and Press Next.
What is the hostname of this machine? [hostname]: Press Next.
What is the Domain name of the machine? [MyDomain]: Press Next
Please select the type of install to perform: [typical/custom]: Click Typical
iPlanet Calendar server components to be installed: Tick both components, Press Next.
- Calendar Server
- Calendar Server API
Directory to install Calendar Server components into: [/opt]: to accept the default server root directory. (If you are not installing as root, you probably will not have permission to create directories in /usr so you will have to choose another location.)
Web Port [80]: Press Next if logged as root. Otherwise choose any port number above 1024.
Enter UserID: [icsuser]: Press Next.
Enter GroupID: [icsgroup]: Press Next.
Calendar Administrator email Address [user@mailhost]: Type a valid email address.
SMTP Server Host Name [mailhost]: Type the server name and Press Next.
Directory to store Calendar Server database info: Type absolute path and Press Next.
Enter LDAP Configuration settings:
Host: Type host name.
Port: Type the LDAP port on which the directory server is running.
Base DN: Type the Base DN name.
Admin Bind DN: Type the admin bind DN.
Admin Password: Type the password.
Update LDAP with new schema.
Directory Manager DN: Type admin or dmanager
Directory Manager Password: Type password (minimum 8 characters)
Confirm Password: Type password (minimum 8 characters)
Directory to store schema files: Type absolute path and Press Next.
Enter LDAP UserID for authentication [calmaster]: Press Next.
User Password: Type password.
Confirm Password: Type password.
Start Calendar Server after successful installation: Tick box.
Start Calendar Server on system startup: Tick Box and Press Next.
Install Calendar Server now? : Press Install.

For detailed documentation visit iPlanet Calendar Server page.

Certificate Management System

iPlanet Certificate Management System (CMS) is a highly configurable set of software components and tools for creating, deploying, and managing certificates. Based on open standards for certificate management, CMS leverages iPlanet Directory Server and Netscape Console to provide a complete, scalable, high-performance certificate management solution for extranets and intranets.
With its support for open standards, Certificate Management System gives organizations confidence that they will be able to communicate within a heterogeneous computing environment.
System Requirements

The software and hardware requiremetnts for CMS are:

Solaris^TM 2.6, 2.7, or 2.8 (with relevant Java 2 patches)

Ultra 1 or faster

128 MB (required)

Total required is approximately 400 MB, broken down as follows:

Total transient space required during installation: 100 MB

Space required for setup, configuration, and running the server: 250 MB

Additional space to allow for database growth in pilot deployment: 50 MB (this may be reduced to 10 MB for default demo installation)

Total disk storage space for installation: 300 MB

Installation

Type of Installation: Typical
The other forms of Installation are described in the Installation Guide.
The setup script file will be available in CMS/CMS42SP2 under the name setup

Would you like to continue with setup? [Yes]:
Do you agree to the license terms? [No]: Type yes and press Enter.
Select the items you would like to install [1]:
Server root [/usr/netscape/server4]: to accept the default server root directory. (If you are not installing as root, you probably will not have permission to create directories in /usr so you will have to choose another location.)
Specify the components you wish to install [All]: to accept the default.
Specify the components you wish to install [1,2,3]: to accept the default server product components.
Specify the components you wish to install [1,2]: to accept the default Directory Suite components.
Specify the components you wish to install [1,2]: to accept the default Administration Services components.
Specify the components you wish to install [1, 2]: to accept the default CMS components.
Computer name [myhost.mydomain.com]: to install on the local machine.
System User [nobody]: Enter the user that the configuration/user Directory Server process will run as. Where your system supports it, accept the default user, nobody, creating that user as necessary.
System Group [nobody]: Enter the group that the configuration/user Directory Server process will run as. Where your system supports it, accept the default group, nobody, creating that group as necessary.
Do you want to register this software with an existing Netscape configuration directory server? [No]: Press Enter to install a new configuration directory.
Do you want to use another directory to store your data? [No]: to use the new configuration directory as your user/group directory.
Directory server network port [389]: to accept the default, 389 . If you are not installing as root or if 389 is in use, the default will be a random number; you may want to change this number to something easy to remember, such as 38989.
Directory server identifier [myhost]: Type configdir as the unique identifier for the configuration directory, and press Enter.
Netscape configuration directory server administrator ID [admin]: to accept the default, then enter the <admin password>.
Suffix [o=mydomain.com]: Press Enter to accept the default.
Directory Manager DN [cn=Directory Manager]: to accept the default, then enter the <dir mgr password>.
Administration Domain [mydomain.com]: to accept the default.
Administration port [random #]: Type 4444 and press Enter.
Run Administration Server as [root]: to accept the default.
Certificate Management System Server identifier [localhost]: Type demo CA and press Enter. After the script copies the files and updates the system, which may take a few minutes, press Enter to continue.

The first phase of the installation is now complete. The installation script has installed Netscape Console, installed and started an Administration Server and its configuration directory, and copied the files for Certificate Management System. You are now ready to configure the Certificate Management System instance by running the Installation Wizard.
For detailed documentation visit Certificate Management System page.

iPS:Instant Collaboration Pack

iPlanet Instant Messaging Server (iIM Server) enables web clients to participate in real-time messaging and automatically distributed information. With iIM Server, users partake in instant messaging and group chat sessions, share instant information through news channels, and view immediate alerts on important news. In addition, iIM Server is suitable for both intranets and the Internet.
You install and configure iPlanet Instant Messaging Server in one of two ways:

As part of the iPlanet Portal Server environment, so that iPlanet Instant Messenger is made available as an application in the iPlanet Portal Server Desktop Applications channel (Solaris platform only)

As a standalone server
Whether you install and configure iPlanet Instant Messaging Server with iPlanet Portal Server or as a standalone server, the iIM Server components are the same. These components include:

iPlanet Instant Messenger (iIM client)

iIM server

iIM multiplex

iIM client software/files

System Requirements

Before you install iPlanet Instant Messaging Server, make sure you have met the minimum hardware and operating system requirements. Installing iPlanet Instant Messaging Server in the iPlanet Portal Server requires that you use Solaris as the operating environment. iPlanet Portal Server currently runs only on Solaris. Additionally, though iPlanet Portal Server supports Solaris^TM 2.6, 7, and 8, iPlanet Instant Messaging Server supports just Solaris 2.6 and Solaris 8. If your portal is running Solaris 7, you cannot install iPlanet Instant Messaging Server. The requirements specific to iPlanet Portal Server can be obtained from the the Portal Server requirements section.
Installation

Type of Installation: Typical
The other forms of Installation are described in the Installation Guide available in the docs directory.
The setup script file will be available in iPS:ICP/iPS:ICP under the name setup. This installation supports both GUI based and command line based setup.

Welcome to iPlanet [TM] Portal Server:Instant Collaboration Pack 3.0: Press Next
Do you accept the terms of this license? Yes (Accept License)
What is the iPS host name of this machine? [jumbo]: jumbo
What is the DNA domain name [o=sun.com]:o=india.sun.com. Press Next
iPS Instant Collaboration Pack components showing a checked box will be installed: Press Next
iPlanet [TM] Instant Messenger 1.3 MB
iPlanet [TM] Instant Messaging Server 6.0 MB
What directory do you want to install the server in? [/opt]: /opt Press Next
Domain Name: India.Sun.Com
Server port accepting connections from multiplexors: 9999
Multiplexor port accepting connections from clients:9909
Remote Server Host name:jumbo.india.sun.com
Integration of iPlanet [TM] Instant Messenger in the Portal Desktop Enable iPlanet Instant Messenger in iPlanet Portal Server: Place a 'Tick' mark and Press Next
Selection of iPlanet [TM] Instant Messaging Server directory server. Use Portal's internal LDAP Directory: Place a 'Tick' mark and press Next
Host name: jumbo.india.sun.com
Port: 389
Base DN: o=India.Sun.Com
SMTP Server: blr-root
User ID: inetuser
Group ID: inetgroup
Directory to store iIM server runtime files into: /var/opt/SUNWiim and Press Next
Directory to store html, jar and Online Help files: /opt/SUNWiim/html and Press Next
Instant Messaging Services Startup: Press Next
Product: iPS:Instant Collaboration Pack: Press Install Now
iPlanet [TM] Instant Messenger 1.3 MB
iPlanet [TM] Instant Messaging Server 6.0 MB

Post Installation Procedure

In some cases due to network problems, the iimserver port is not set correctly. The workaround is to manually set the port to 9919 as against 9909. This will have to be set in the servlets.properties file which is present in the webserver path of Portal Server installation. /opt/netscape/server4/htts-hostname/config/servlets.properties

To authenticate the user while logging in, the IIM must be able to search the user in the LDAP and to do this search, the iim.conf file will have to be modified to enable this. The two additions that will go into the iim.conf file present in /opt/SUNWiim/config/iim.conf:

iim_ldap.usergroupbinddn="uid=ipsadmin, ou=Directory Administrators,o=sun.com"
iim_ldap.usergroupbindcred=admin1234

NOTE: No quotes for the password.
           These lines can be inserted anywhere in the file.
           Once this is done, go to /opt/SUNWiim/sbin and say iimadmin refresh.
           Go to the Portal Page and then start the Instant Messenger

Unified Development Server

iPlanet Unified Development Server (UDS) provides development tools for building advanced distributed applications. These tools enable developers to build integrated applications that are optimized for a distributed environment. It provides robust distributed application development environment that allows one to create manage and run iIS across various nodes in the UDS environment. UDS supports quick prototyping, collaboration my multiple developers and graphical user interface development.
Installation

The following procedure describes how to install iPlanet UDS software on a UNIX node. To accept any default values during the installation process, press Enter.

Set your current directory to the source of the installation files: If you are installing across a network, mount the iPlanet UDS installation directories containing the ALL_UNIX directory and the UNIX directory specific to your platform. If you are installing from the iPlanet UDS Platform CD, mount the CD as explained in "Mounting the Distribution CD" in the UDS documents section.
Execute the INSTALL.SH program: Located in the ALL_UNIX subdirectory of the iPlanet UDS Platform CD or in the designated directory of your server node, by typing ./install.sh
The installer prompts you for a target directory for your iPlanet UDS installation: If the target directory you specify does not exist, the installer creates it for you.
Choose type of Installation [2]: This is a Typical Install.
After selecting an installation option, the installer prompts you for additional information.

Installation path: /forte
Port ID for iPlanet UDS Name Service: 5000
iPlanet UDS NameService Address: none
Database pathnames: Do not specify a path to a database
Environment name: CentralEnv
Distributed repository name: CentralRepository
Example applications: install examples

Specify the iPlanet UDS installation path (default is /forte): /forte
iPlanet UDS Installation Menu
1) - Install & Setup for Central Server Node
2) - Install & Setup for Server Node
3) - Install & Setup for Client Only
4) - Install Files Only
q) - Exit Installation Program

Select Option [1, 2, 3, 4, q (default is 4)]: Type 4 and Press Enter
Do you wish to continue the installation with these options? (y/n, default is y): Type y and Press Enter

After the installation is complete, proceed to "After Installing iPlanet UDS" in the udsinstall.pdf file in http://docs/iplanet.com

iPlanet Integration Server

iPlanet Integration Server is a suite of business integration tools for integrating and coordinating heterogeneous applications. The tools and software components provided with iIS let you develop newapplications, legacy applications and off the shelf products (including Web browsers) into business processes that are managed and controlled by a process engine. It is not a standalone system but is run from within an iPlanet UDS environment. With iMQ, processes running on different platforms and operating system can connect to common iMQ message service to send and receive information
System Requirements

iIS requires UDS to be installed first so that iIS can be installed over UDS.
Installation

To install iIS Enterprise Edition on a UNIX node

Start your iPlanet UDS environment, as described in "iPlanet UDS Installation"
Navigate to the ALL_UNIX directory of the installation files and execute the F_INSTAL.SH script by typing: ./F_INSTAL.SH
Do you agree to the license? y/[n]: Type y and Press Enter
Server Root [ /your_path/forte]. Please specify UDS installation path (y/n default y): Press Enter
Confirm version number and available disk space.
Current iIS version 3.0.0
Current Forte/UDS version: 5.0.1
Available disk space: 4614974 KB
iIS Option Menu:

Options Description Minimum Disk Space Required
1) iIS Professional Edition 50838 KB
2) iIS Enterprise Edition
q) Exit Installation Program

Enter installation option [1, 2, q (default is 1) ]: Type 2 and Press Enter
The following table summarizes the Enterprise Edition installation options. For more information on iIS installation options, refer to Planning an iIS Installation. You can also refer to the iIS Process System Guide and the iIS Backbone System Guide.
iIS Enterprise Edition Option Menu:

Options Description Minimum Disk Space Required
1) Central Server Node 108484 KB
2) Server Node 59604 KB
3) Runtime Client Node 44956 KB
q) Exit Installation Program

Enter installation option [1-3, q (default is 3): Type 2 and Press Enter
iIS Server Node Option Menu:

Options Description Minimum Disk Space Required
1) Backbone System 50838 KB
2) Process Engine 58448 KB
3) Both Backbone and Process Engine 65486 KB
q) Exit

Enter installation option [1-3, q (default is 3): Type 2 and Press Enter
Do you want the installation to create a iIS development repository for this node? (y/n, default is n): Press y
Please specify a name for your iIS development repository: (default is f_repos) Press Enter
Enter name of the repository. If you are installing a central server node, the installer prompts you for platformsfor distribution. The installer prompts you to choose the platforms you intend to use for distribution. Select theplatforms to which you intend to distribute applications.
iIS Worshop Option Menu:

Options Description
1) XML/XSLT Workshop
2) Process Development Workshop
3) Both workshop
4) No Workshops to be installed
q) Exit Installation Program

Enter installation option [1-4, q (default is 3): Type 3 and Press Enter
After making your selection, the installer asks you to confirm your installation options.
Specify y to begin the installation, or n to abort the installation: Type y and Press Enter
If all checks pass, the installation proceeds.
Depending on the options you selected, during the appropriate time in the installation you are asked to confirm the following:

All options: confirm that the iPlanet UDS environment manager is running.
Server node and runtime client: confirm that the node manager is running.
All options except runtime client: confirm that the iPlanet UDS repository server is running.
Depending on the options you selected, you may also need to supply the name of your iPlanet UDS environment. You can verify the name of your iPlanet UDS environment by issuing the ShowAgent Escript command.
The installation proceeds to completion.

For detailed documentation visit iPlanet Integration Server page.

iPlanet Message Queue

The iMQ product is a standards-based solution to the problem of inter application communication and reliable message delivery. iMQ is an enterprise messaging system that implements the Java Message Service (JMS) open standard.
System Requirements

The Service Pack requires about 8 megabytes of free space to store backups. The Solaris patch mechanism checks to see if there is sufficient space.

Installation

Type of Installation: Typical
The other forms of Installation are described in the Installation Guide.
The setup file will be available in iMQ/2.0 under the name SUNWjqrun. This is a package and hence should be installed using the command pkgadd

Install the broker to start automatically [y]/n? y and Press Enter
iMQ/sp1/111858-01]$ ./installpatch `pwd`

For detailed documentation visit iPlanet Message Queue page.

Preparing for Multiple Server Installations

The multiple server installations deal with installations of a set of products that will be commonly or most frequently used by an end user. Based on this, a couple of multiple server scenarios have been identified and the various issues that crop up on account of such installations have beenidentified. These issues are mentioned below and this will help to avoid problems like server root clashes, port clashes, etc. and help in achieving an error freeinstallation.
iDS+iWS+iPS+iMS+iCS+CMS+iPS:ICP+iPS:MAP+iIS+UDS

In this scenario, the above products are installed on a single machine. To proceed with this scenario, there are quite a few points to be noted down in order to achieve a successful installation of all the mentioned products.
13.1.1 Identified Issues

iDS and CMS have the same default server root and hence care must be taken that they don't clash. The best way to avoid a server root clash would be to install both the products on unique server root paths

iPSs uses port 8080 and while installing iMS, the port assigned to Delegated Admin (iDA) is also 8080. Hence this must be taken care off, lest it should create a problem while installing iDA in future. Since the port 8080 in iDA is an optional port( meaning, this port will be used only if iDA is installed), it would be better to assign another port number to avoid a clash with the portal server.

Since iPS, iMS, iCS and CMS uses web port 80 as default apart from iWS, care must be taken that each of these products are given different web ports.

For a secure connection, the standard SSL port being used is 443. Since both iPSgw and CMS requires SSL connection, there is a possibility of a port clash in such a scenario. This will have to be avoided and a different port number will have to be assigned to either iPSgw or to CMS

iPSs requires the use of LDAP service but it cannot use an external LDAP. Hence the embedded LDAP will have to be used in iPSs. The same is the case with iMS.

iCS requires iDS to be installed first which becomes a pre-requisite for iCS.

iDS+iPS+iPS:ICP+iMS

13.2.1 Identified Issues

iDS as a standalone product will take port number 389 to run LDAP and hence care must be taken to ensure that iPS and iMS uses a different port numbers to run their respective LDAP.

Both iPS and iMS cannot use the standalone iDS unless they are manually configured to support iPS and iMS and hence will have to use the embedded directory server.

iPS uses port 8080 for Desktop Login and hence the iDA port in iMS which has its default port as 8080 will now have to use a different port. This will not be checked during installation and hence will have to be taken care by the user.

iDS+CMS+iMS

13.3.1 Identified Issues

iMS with external iDS crashes while installation. To have a successful installation, the iDS will have to be edited manually to work with iMS. Otherwise, iMS will have to use the embedded iDS.

CMS iDS have the same default server roots and hence care must be taken that they are installed in different server roots to avoid directory clashes.

Port conflict for CMS and iDS since both of them require 389 to run LDAP. Hence a different port number will have to be assigned for both. The same is the case with iMS and iDS and hence will have to have different port numbers for running LDAP.

Web Port conflict for iMS and CMS and hence they will have to use different port numbers.

Back

Operating Environment	JDK Version
Solaris	JDK 1.2.2_07
Linux:	JDK 1.2.2
HP-UX	JDK 1.2.2_07
AIX	JDK 1.2.2
Tru64	JDK 1.2.2-8

Installation path:	/forte
Port ID for iPlanet UDS Name Service:	5000
iPlanet UDS NameService Address:	none
Database pathnames:	Do not specify a path to a database
Environment name:	CentralEnv
Distributed repository name:	CentralRepository
Example applications:	install examples

Options	Description	Minimum Disk Space Required
1)	iIS Professional Edition	50838 KB
2)	iIS Enterprise Edition
q)	Exit Installation Program

Options	Description
1)	XML/XSLT Workshop
2)	Process Development Workshop
3)	Both workshop
4)	No Workshops to be installed
q)	Exit Installation Program