Complete Contents
Introduction
Chapter 1 About Netscape Application Server Extensions
Chapter 2 About the Netscape Extension Builder
Chapter 3 Introduction to Netscape's Interface Definition Language
Chapter 4 Designing a Netscape Extension
Chapter 5 Generating Output Files
Chapter 6 Completing Method Stubs
Chapter 7 Using Template Streaming
Chapter 8 Managing State and Session Information
Chapter 9 Using Object Pools
Chapter 10 Compiling the Extension Source Code
Chapter 11 Deploying and Managing a Netscape Extension
Chapter 12 Example Extension: HelloWorld
Appendix A C++ Helper Functions
Appendix B Java Helper Static Methods
Appendix C Java Class Decorations
Appendix D Reserved Words
Appendix E The ConnManager.cpp File
Glossary
Previous Next Contents Index


Deploying and Managing a Netscape Extension

This chapter describes the process of deploying a Netscape extension, including deploying the Netscape Extension Builder Runtime Layer, the extension classes and libraries, and the Netscape Application Server application that will use the extension.

The following topics are included in this chapter:


Deploying a Netscape Extension
Before you can deploy an extension, you must first register the server(s) to which you want to deploy. During this process you must provide a username and password that is authorized by that server to perform both Administration and Deployment. In preparation for deployment, you must first setup this username using the NAS Administrator.

To setup a username in NAS Administration and NAS Deployment to use when deploying an extension, perform the following steps:

  1. From the Start menu choose Programs and then Netscape Application Server 4.0.

    2. The NAS Administrator opens.

  2. In the left navigation pane, highlight the server to which you want to deploy and click the Security button.

    3. The following window opens:



  3. Highlight NAS Administration and click Modify near the bottom of the window.

    4. The Modify Access Control List dialog box appears.

  4. Click Add User or Group.

  5. In the text box highlight the username "admin21" and click OK.

  6. In the Modify Access Control List dialog, click the checkbox for user admin21.

    7. This grants this user ADMIN privileges for NAS Administration.

  7. Click OK.

  8. Repeat steps 3-6 to grant user admin21 ADMIN privileges for NAS Deployment.

    9. You can now deploy an extension to this server.

You deploy an extension from the project file (.gxp) that corresponds to the extension project. To generate the .gxp file, you must first compile the extension source code. For more information about compiling the extension, see Compiling the Extension Source Code.

To deploy a Netscape extension, perform the following steps:

  1. Open the extension .gxp file in Netscape Extension Builder Designer.

  2. Choose Tools - Deploy or click the Deploy Extension tool-bar icon.

    3.

    The Deploy Extension dialog box appears:

  3. In the Deploy Extension dialog box, select the server or servers that you will deploy the extension to, then click the right arrow button.

    4. The selected servers appear in the "Servers to deploy to:" box.

  4. If you need to make more Netscape Application Servers available, click Register and specify the information necessary to connect and add those servers.

    5. The Register Server dialog appears, prompting you for the name of the server, a username, and a password.

  5. Enter the name of the server, the username "admin21" (without the quotes) and the admin password used to logon to the server.

  6. In the Deploy Extension dialog box, click Deploy.

    7. The Deploy dialog box appears:



  7. If you are deploying this extension to a Netscape Application Server that does not already host an extension, you must first enable the Netscape Extension Builder Runtime Layer by selecting the "Enable NEB runtime on target servers" checkbox.

    8. The Runtime Layer consists of the files associated with the Netscape Extension Builder Runtime Features. These files need be enabled only once for each Netscape Application Server.

  8. Click OK.

    9. A log dialog box appears, displaying the deployment process of the extension. Read the log to verify proper deployment of the extension.

  9. When finished reading the log, click Close.

    10. Deployment of the extension is complete.


Verifying Extension Configuration
Once you have completed the deployment process, you can verify that the extension is properly configured using Netscape Application Server Administrator. This is particularly useful for servers that have multiple extensions installed on them and for extensions that use many services.

Netscape Application Server Administrator displays each extension hosted on the server as well as the service or services that compose each extension, and the engines in which those services are run. This allows you to verify that a C++ service is properly hosted in the C++ Server, a Java service is hosted in the Java Server, and a C++ service with a Java access layer is hosted in the C++ Server and the Java Server.

As the extension developer and deployer, you must coordinate with the server administrator to verify extension configuration using Netscape Application Server Administrator.

To verify extension configuration

  1. Open Netscape Application Server Administrator.

  2. Select the server to which you deployed.

  3. Click View Extensions.

    4. The View Extensions dialog box appears.

  4. Under Extension Name, find the extension you deployed.

  5. Under Extension In, verify that each service of the extension is hosted in the appropriate Netscape Application Server process, as described by the following table:
    6. Extension In
    		Description
    C++ Server
    		Extension services written in C++ must be hosted by the C++ Server.
    Java Server
    		Extension services written in Java must be hosted by the Java Server.
    C++ Server/Java Server
    		Extension services written in C++ with a Java access layer are hosted in the C++ Server and Java Server.

  6. When you are finished, click OK.

Disabling an Extension
You might have to disable an extension for a variety of reasons. Using the Netscape Application Server registry, you can disable an extension whenever necessary.

To disable an extension

  1. Open the Netscape Application Server registry editor by typing kregedit at the command or shell prompt.

    2. The Netscape Application Server registry editor opens and displays the keys and values that apploy to the Netscape Application Server.

    For Windows NT, use regedit and start at
    HKEY_LOCAL_MACHINE\\SOFTWARE\\KIVA.

  2. Open the following key:
    3. KIVA\\Enterprise\\4.0\\CCSO\\EXTENSIONS\\<ExtensionName>\\ServiceName

  3. Double-click the enabled DWORD value.

    4. The DWORD editor dialog box appears.

  4. Change the value data to 0 and click OK.

Adjusting Object Pooling Configurations
If your extension is pooling objects, there are performance-optimizing configurations the server administrator can make. Currently, these settings must be made in the Netscape Application Server registry for each machine on which Netscape Application Server is running an extension.

To adjust object pooling configurations

  1. Open the Netscape Application Server registry editor by typing kregedit at the command or shell prompt.

    2. The Netscape Application Server registry editor opens and displays the keys and values that apply to the Netscape Application Server.

    For Windows NT, use regedit and start at HKEY_LOCAL_MACHINE\\SOFTWARE\\KIVA.

  2. Open the following key:

    3. KIVA\\Enterprise\\2.1\\CCSO\\POOLS

  3. Adjust the pooling configurations as described in the following table:
    4. Object Pooling Values
    		Description
    MaxPoolSize
    		The maximum number of objects allowed in the pool. For example, if the pooled objects are CICS connections, set this number to the peak number of connections available to the server.
    If the number of objects is less than MaxPoolSize but exceeds SteadyPoolSize, objects are destroyed immediately after they are returned to the pool.
    SteadyPoolSize
    		The number of unused objects that are kept in the pool until they time out. For example, if the pooled objects are CICS connections, set SteadyPoolSize to the steady state (RMS) number of connections available from the CICS server.
    MaxWait
    		The maximum time, in seconds, a request for a physical object is held in the queue before the request times out and is destroyed.
    UnusedMaxLife
    		The maximum time, in seconds, that a physical object remains unused in the pool. After this time, the physical object is destroyed.
    MonitorInterval
    		(Optional) The time, in seconds, that a thread is spawned to monitor the current status of the pool. Default is 30 seconds. Typically, setting this number too low degrades performance, but it should be set to a number less than UnusedMaxLife.
    DebugLevel
    		(Optional) Determines type of message logging, as described by the following choices:
    0: Logging turned off.
    1: Logs only callback messages.
    2: Logs all messages.

    These values can also be set at the engine level (CCS0\\ENG\\<eng #>). Settings made for an engine override the settings made in the POOLS key only for that engine. This allows you to fine tune, on an engine by engine bases, extensions running on multiple engines.

  4. When finished, close the Netscape Application Server registry editor.
 

Copyright © 2000 Sun Microsystems, Inc. Some preexisting portions Copyright © 2000 Netscape Communications Corp. All rights reserved.