Sun GlassFish Communications Server 2.0 Installation Guide

ProcedureTo Install Sun GlassFish Communications Server in GUI or CLI Mode

Before You Begin

Use this procedure if you are using the Graphic User Interface (GUI) or Command-Line Interface (CLI) mode of the file-based installer for Sun GlassFish Communications Server. Verify that your system meets the requirements specified in the Release Notes.

Solaris and Linux installations support both root and non-root user installations. Users of Windows installations should have Power User or Administrator access. If you are installing as a non-root user on Solaris or Linux, you must have read-write access to the following directories:

  1. Navigate to the directory where you downloaded the distribution file.

  2. If you have downloaded a .bin file, change the permission of the distribution file so that you have execute access:

    chmod +x distribution_filename

  3. Run the installation program.

    • If you are installing from a .bin file on Solaris or Linux, use the following command to run the installation program :


      Use the -console option to run the installation program in command-line mode. It is recommended that you use the -javahome option if you are running the installation program on Solaris x86 platform.

    • If you are installing from an .exe file on Windows, double-click the file.

    Note –

    If you are installing Sun GlassFish Communications Server on a 64–bit machine (running a 64–bit operating system), use a 32–bit JDK to install Sun GlassFish Communications Server on your 64–bit machine. You will need to use the following command: ./distribution_filename —javahome path to 32–bit JDK location

    After installation, download the 64–bit JDK from Edit the value of the AS_JAVA variable in the asenv.conf file to point to the 64–bit JDK installation, so that Sun GlassFish Communications Server uses the 64–bit JDK.

  4. Read and accept the license agreement.

  5. Choose the components you want to install.

    You can choose to install the Domain Administrative Server (DAS) or the node agent, or both.

  6. In the Administration Configuration page (or when prompted at the command line), enter the following fields and click Next.

    • Admin User Name – Name of the user who administers the server.

    • Password – Admin user’s password to access the Admin Server (8-character minimum).

    • Choose whether you want to be prompted for the Admin User Name and Password.

    • Admin Port – Administration port number for initial server instance. The default value is 4848.

    • HTTP Port - Port number to access the default server instance. The default is 8080

    • HTTPS Port - Secure port number to access the default server instance. The default is 8181

  7. In the SIP Configuration page, provide the following configuration information and click Next.

    • SIP Port – The port on which SIP listener listens for SIP requests. The default value is 5060.

    • SIPS Port – Secure SIP port. The default value is 5061.

    • Choose whether you want an installation with clustering capabilities or an installation without clustering capabilities.

      For more information on clustering, see the Clustering section in the High-Availability Administration guide.

    Note –

    The installation program automatically detects ports in use and suggests unused ports for the default settings.

    In addition, five other ports are automatically assigned. You can change the automatically assigned values after installation using the Admin Console. The ports are assigned with the following default values:

    • Message Queue – The default is 7676

    • IIOP – The default is 3700 for IIOP, and 3820 and 3890 for IIOP/SSL

    • JMXTM – The default is 8686

    If these default port numbers are in use, the installation program assigns random port numbers from the dynamic port range. This number may not be the next available port number.

  8. In the Installation Options page, select the options that you want. Click Next

    The following installation options are available:

    • Upgrade from a Previous Version – Select this option to upgrade from a previous version of Communications Server.

      The Upgrade Tool is launched if you choose this option.

    • Enable UpdateCenter Client – Select this option to enable Updatecenter to check for available updates and collect system data.

    • Create Desktop Shortcut to the AutoDeploy directory – Select this option to automatically deploy items dragged to this directory. You see this option only if you are using Windows.

    • Add bin Directory to PATH – Select this option to add as-install/bin to the PATH variable for simplifying the process of running the server and tools from the command line. You see this option only if you are using Windows.

    • Create Windows Service – Select this option to create a Windows service to start and stop Application Server,

      Note –

      To create a Windows service, the sc.exe utility must be available on the system. Windows 2000 users may need to install the Windows 2000 Resource Kit to get this utility. For other supported Windows versions, the utility is included in the operating system.

  9. On the Ready to Install page, click Install Now.

  10. After installation completes, use the Registration Options screen for registering your installation of application server. For instructions, see To Register Your Installation of Sun GlassFish Communications Server.

  11. Verify the installation by following the procedures in the Sun GlassFish Communications Server 2.0 Quick Start Guide, located in as-install/docs/QuickStart.html or on