Adding a Local Server Instance

The iPlanet Application Server Integration tool enables you to deploy to your application to one or more iPlanet Application Server instance. Setup a local or remote server instance prior to performing local or remote debugging.

To create a local server instance:

From the Explorer window Runtime tab, select the iPlanet Application Server Instance node.
If the iPlanet Application Server node is not displayed, then the iPlanet integration tool is not installed or it is not enabled.
Right click to select Add an iPlanet Application Server Instance menu option.
When the iPlanet Application Server Properties window appears, select each field to enter the appropriate information.
Admin Port Number Enter the port number of the local Administrative Server. During installation of the iPlanet Application Server this is set by default to port number 10817.
If you are unsure of the port number, perform the following steps:
1. From a command tool, type kregedit, to launch the iPlanet Application Server Registration Editor.
  A treeview of the iPlanet Application Server directory structure appears.
2. Locate the SOFTWARE\iPlanet\Application Server\6.0\Admin\Port<PortNumber>
3. Enter the port number you just located in the Properties window Admin Port Number field.
Admin User name Enter the username you specified during the iPlanet Application Server installation. The default settings displayed are for the registered local server.
Admin User Password Enter the password for the local iPlanet Administrative KAS Server. The default settings displayed are for the registered local server.
If you registered the Application Server instance through the AdminTool, the Integration Tool polls the AdminTool registration to obtain the password and displays it here as the default entry for you. If you haven't registered the local server, a message appears in the status bar prompting you to identify the Admin user name and password.
Connector URL Accept the default URL setting.
Host Name Accept the default host name setting.
Close the Properties window.
A node representing your local server appears under the iPlanet Application Server Instances node.
Select the local server node and right click to display the context menu.
Either the Start Server Engines or Stop Server Engines menu item is enabled depending on whether your server engines (KJS and KXS) are running or not.
Use the Start Server Engines and Stop Server Engines menu options to start/stop the KJS and KXS engines on the local server. These menu options are only functional if the Administration KAS server is running on the local server.
On an NT machine, start the KAS engine through the Control Panel Services interface.
On a Solaris machine, start KAS using the iascontrol start command.
For more information on how to use the iascontrol command see the iPlanet Application Server Version 6.0 Service Pack 2 Release Notes.
A red arrow on the instance node icon indicates that the Administrative server (KAS) is not running. A green arrow indicates the Administrative server (KAS) is running.
If your KJS/KXS engines is not running, and your KAS administration engine is running, select Start Server Engine to launch the KJS/KXS.
When the local server is stopped and started, there is a delay for Forte to detect it. Also, Forte does not poll the server, so the server instance node display does not change until the next time the node is selected.
The Set as Default menu option is disabled if the server is already set as the default. The iPlanet Application Server Instances node changes to identify which server is set as the default.

See also
	Adding a Remote Server Instance About the iPlanet Application Server Engines

Legal Notices