Previous     Contents     Index     DocHome     Next     
iPlanet Application Server Administrator's Guide



Chapter 14   Setting Up iPlanet Application Server for Development


This chapter describes the tasks you need to perform, to set up iPlanet Application Server for development purposes.

The following subjects are described in this chapter:



Setting Up Class Paths

You may need to manually set up the iPlanet Application Server class path when you want to do one of the following:

  • when you enable RMI/IIOP access to EJBs.

  • when you make a set of helper or framework classes available to all applications deployed to a server.

To change the iPlanet Application Server class path, perform the following tasks:


On Solaris

  1. Navigate to the <iasinstall>/ias/env path and edit the Common Environment script, iasenv.ksh. You can use a text editor to edit this file.

  2. Search for and locate the ClassPath entry. You can either change the default classpath or add a new classpath.

  3. Restart the server for the change to take effect.


On Windows

  1. Open iPlanet Registry Editor.

    (See About iPlanet Registry Editor)

  2. Open the following key:

    SOFTWARE\iPlanet\Application Server\6.0\Java\

  3. Modify the class path and restart the server for the change to take effect.



Changing Heap Size For Java Engines

Default heap size for KJS is specified in the KJS script. If you want to enable KJS to store more objects, you can change the heap size manually. To do so, perform the following tasks:


On Solaris

  1. Go to <iasinstall>/ias/env and edit the KJS (Java Engine) startup script, iasenv.ksh.

    Locate the JAVA_ARGS entry and modify the existing minimum(-Xms) and maximum (-Xmx) heap size specifications, as required.

  2. Close all KJS processes and restart them, for the change in heap size to take effect.


On Windows

  1. Start iPlanet Registry Editor.

    (See About iPlanet Registry Editor)

  2. Open the following key:

    SOFTWARE\iPlanet\Application Server\6.0\Java\

  3. Modify the JavaArgs value and set the minimum heap size (-Xms <number>m) and the maximum heap size (-Xmx<number>m) for Java engines.

    Your heap size specification must look like this:

    JavaArgs=-Xms16m -Xmx32m

  4. Restart all kjs processes for the change to take effect.

    Note that on Windows, the heap size for Java engines does not exist by default.



Changing The Default Application Path

Your applications are stored in the default application path, from where they are picked up by DeployTool, to be deployed. You may want to change this path if, for example, you want to store your applications in your server's home directory. You can change the default application through kregedit.

Before changing the default application path, you need to:

  • create the new path on your machine or network and

  • manually copy your application's class files to this location.

After you create the path, you need to change the default class path in Iplanet Registry. To do so, perform the following tasks:

  1. Start iPlanet Registry Editor.

    (See About iPlanet Registry Editor)

  2. Open the following key:

    SOFTWARE\iPlanet\Application Server\6.0\

  3. Edit the AppPath value and change the default application class path. See Setting Up Class Paths.

  4. Restart the server for the change to take effect.



Enabling Dynamic Servlet Reloading

By default, dynamic servlet reloading is disabled in iPlanet Application Server. You can enable it, by performing the following tasks:

  1. Start iPlanet Registry Editor.

    (See About iPlanet Registry Editor)

  2. Open the following key:

    SOFTWARE\iPlanet\Application Server\6.0\CCSO\SYSTEM_JAVA\Versioning

  3. Set Disable=0. The default value is 1 which indicates that dynamic servlet reloading has not been enabled.

  4. Restart iPlanet Application Server for the change to take effect.

This change will enable dynamic reloading of servlet classes and registered JSPs (those JSPs that have been assigned GUIDs and are listed as servlets in web.xml files). By default, unregistered JSPs are dynamically reloaded by iPlanet Application Server.



Specifying Session And Cache Timeout Values For J2EE Components


When you deploy an application, session timeout values are set for the applications's J2EE components, such as JSPs, servlets and EJBs. These values apply to all the J2EE components that run on your Web Server and Application Servers.

You can specify session timeout values for individual J2EE components for each application, on a need-basis. The value that you specify for an individual J2EE component will override the default value set during deployment.

Cache timeout values can be specified for servlets and JSPs. These are set to 0 by default when an application is deployed.

You can use DeployTool to set these values too. See the Online Help that has been provided for DeployTool.

This section describes the following topics:


To Set Session Timeout Value For JSPs And Servlets

For JSPs and Servlets, session timeout value can be set for each application. These values are set by default during deployment. You can modify the session timeout value, by performing the following tasks:

  1. Start iPlanet Registry Editor.

    (See About iPlanet Registry Editor)

  2. Open the following key:

    SOFTWARE\iPlanet\Application Server\6.0\J2EE-Module\<module name>\

    If session timeout value has been specified already, you will see a key that looks like this: session-timeout=(). If session timeout value has not been specified, you can add it to the module.

  3. Select the module for which you want to specify session timeout value.

  4. Click Edit>Add Value.

  5. In the Name field, specify a name, for example, Session-timeout.

  6. In the Value field, specify a value, for example, 10. Note that the timeout value is specified in seconds.

  7. Set the type of the value to Integer.

  8. Click OK to save your changes.

The session timeout value is set for the Servlets and JSPs that belong to your application.


To Set Session Timeout Value For EJBs

For EJBs, session timeout value is globally set using iASAT. See To Specify EJB Container Parameters for Run Time for more information. The value that is set through iASAT is applicable to all the EJBs that are deployed.

However, you can customize the session timeout value for each individual EJB, in iPlanet Registry. To specify the session timeout value for an EJB, perform the following tasks:

  1. Start iPlanet Registry Editor.

    (See About iPlanet Registry Editor)

  2. Open the following key:

    SOFTWARE\iPlanet\Application Server\6.0\J2EE-Module\<module name>\ejbs

    You will see a string that looks like this:

    <Beanhomename>=(18c06cf0-21dd-11d2094b6-0060083a5082)

    The string within brackets is the GUID (Global Unique Identifier) that identifies the EJB used in the selected application module. Make a note of this GUID.

  3. Navigate to SOFTWARE\iPlanet\Application Server\ClassDef\

    This folder lists all the GUIDS that are attached to deployed applications. Locate the GUID you want.

  4. Expand the GUID key into its hierarchal tree.

  5. Open the SessionDescriptor key. This key contains session timeout, passivation timeout and other values that have been set for the EJB.

  6. Modify the session timeout value and restart the server for the change to take effect.


To Set Cache Timeout Settings For JSPs And Servlets

The default cache timeout is the period for which servlets and JSPs are kept in the cache before they are purged by the Web Server. The default cache time is set at the time of deployment.

You can change the default cache timeout settings for JSPs and Servlets, per GUID. To do so, perform the following tasks:

  1. Start iPlanet Registry Editor.

    (See About iPlanet Registry Editor)

  2. Open the following key:

    SOFTWARE\iPlanet\Application Server\6.0\J2EE-Module\<module name>\servlets\

    You will see a GUID, which looks like this:

    <module name>servlet=(1a488137-7510-1941-bae5-080020b90148)

    Make a note of this GUID.

  3. Navigate to SOFTWARE\iPlanet\Application Server\ClassDef\

    This folder lists all the GUIDS that are attached to deployed applications. Locate the GUID you want.

  4. Select the GUID and click Edit>Add Key.

  5. In the Name field, type Caching.

  6. Create the following values under this key:

    • Cache-Size (value in KB, type Integer)

    • Cache-Timeout (value in seconds, type Integer)

    • Cache-Option (value can be set as either Timeout-Create or Timeout-Lastaccess, type String).

    • Cache-Criteria (value that specifies appropriate cache criteria, type String). See the Java Developer's Guide for more information on cache criteria.

  7. Restart the server for the changes to take effect.

If your application uses JSPs, you will find the relevant GUID in the path described in Step 2.



Enabling RMI/IIOP Support


iPlanet Application Server does not enable support for RMI/IIOP access to EJBs, during installation. However, you can add an RMI/IIOP bridge process to the iPlanet Application Server environment through iASAT.

To add an RMI/IIOP bridge process to the iPlanet Application Server environment through iASAT, perform the following tasks:

  1. Start iASAT.

    • On Solaris, go to <iASinstall>/ias/bin/ and type ksvradmin.

    • On Windows, from the Start menu, choose Programs>iPlanet Application Server and choose iAS Administration Tool.

  2. Select the server for which you want to add a new RMI/IIOP process. Expand the server to view the processes under it.

    You should see at least one kjs and one kxs process. You need to now add a cxs process, to enable RMI/IIOP process.

  3. Click File>New. Choose Process.

  4. Select cxs from the Process drop down list.

  5. In the Port text field, enter a port number that is different from the port numbers being used by the other processes.

  6. In the IIOP Port text field, specify a port number for the IIOP bridge process. The default IIOP port number is 9010. You can retain this port number if it does not conflict with the other port numbers already in your system environment.

  7. Click OK to register the cxs process. The cxs process is added to the iPlanet Application Server machine.

  8. Restart the server to activate the cxs process.

On Solaris, you can also check for the existence of the IIOP bridge process from the command line. For example:

ps - ef |grep iiop

root 1153 1 0 17:00:15 ? 0:00 /bin/sh/usr/iPlanet/iAS6/bin/kjs -cset CCSO - eng 3 - iiop - DORBinsPOrt=9010



Setting Environment Variables for Databases


Although system environment variables for databases are set during installation, verify that they have not changed.

On Solaris, you can type env at the prompt, to verify the environment variables. Review the list of environment variables. If a any variable in the system environment is not set according to the guidelines provided here, change it to the proper setting.


Sybase

  • For Bourne Shell:

    DSQUERY=<sybase servername>; export DSQUERY

  • For C Shell:

    setenv DSQUERY <sybase servername>

    Replace sybase servername with the name of the user's Sybase server.


Oracle

  • For Bourne Shell:

    ORACLE_HOME=<oracle install directory>; export ORACLE_HOME

  • For C Shell

    setenv ORACLE_SID <oracle SID>

    setenv ORACLE_HOME <oracle install directory>


DB2

  • For Bourne Shell:

    DB2INSTANCE=<db2instance>; export DB2INSTANCE

  • For C Shell

    setenv DB2INSTANCE <db2instance>


INFORMIX

  • For Bourne Shell:

    INFORMIXSERVER=<informixserver>; export INFORMIXSERVER

  • For C Shell

    setenv INFORMIXSERVER <informixserver>


Adjusting Environment Size

After installation, if you notice any Administrative Server processes consuming 100% of your system resources, increase the size of the environment space on your NT machine. Edit the file Config.nt, found in the System32 directory of your system root (normally C:\Winnt or C:\Winnt4) by adding the following line, and then restart your machine:

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

If you still experience the problem after restarting your machine, try increasing the environment size further by specifying /e:4096, instead of /e:2048, in the line above.


Previous     Contents     Index     DocHome     Next     
Copyright © 2001 Sun Microsystems, Inc. Some preexisting portions Copyright © 2001 Netscape Communications Corp. All rights reserved.

Last Updated June 25, 2001