JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle GlassFish Server 3.1 Administration Guide
search filter icon
search icon

Document Information


1.  Overview of GlassFish Server Administration

Default Settings and Locations

Configuration Tasks

Administration Tools

Instructions for Administering GlassFish Server

Part I Runtime Administration

2.  General Administration

3.  Administering Domains

About Administering Domains

GlassFish Server Instances

Domains for Administering GlassFish Server

Domain Administration Server (DAS)

Creating, Logging In To, and Deleting a Domain

To Create a Domain

To Create a Domain From a Custom Template

To List Domains

To Log In to a Domain

To Delete a Domain

Starting and Stopping a Domain

To Start a Domain

To Stop a Domain

To Restart a Domain

Configuring a DAS or a GlassFish Server Instance for Automatic Restart

To Configure a DAS or an Instance for Automatic Restart on Windows

To Configure a DAS or an Instance for Automatic Restart on Linux

To Configure a DAS or an Instance for Automatic Restart on Oracle Solaris

To Prevent Service Shutdown When a User Logs Out on Windows

Suspending and Resuming a Domain

To Suspend a Domain

To Resume a Domain

Setting Up Automatic Backups of a Domain

To Create a Backup Configuration

To List Backup Configurations

To Enable a Backup Configuration

To Disable a Backup Configuration

To Delete a Backup Configuration

To Create a Schedule

To List Schedules

To Delete a Schedule

Backing Up and Restoring a Domain

To Back Up a Domain

To Restore a Domain

To List Domain Backups

Re-Creating the Domain Administration Server (DAS)

To Migrate the DAS

Additional Domain Tasks

To Display Domain Uptime

To Switch a Domain to Another Supported Java Version

To Change the Administration Port of a Domain

4.  Administering the Virtual Machine for the Java Platform

5.  Administering Thread Pools

6.  Administering Web Applications

7.  Administering the Logging Service

8.  Administering the Monitoring Service

9.  Writing and Running JavaScript Clients to Monitor GlassFish Server

10.  Administering Life Cycle Modules

11.  Extending and Updating GlassFish Server

Part II Resources and Services Administration

12.  Administering Database Connectivity

13.  Administering EIS Connectivity

14.  Administering Internet Connectivity

15.  Administering the Object Request Broker (ORB)

16.  Administering the JavaMail Service

17.  Administering the Java Message Service (JMS)

18.  Administering the Java Naming and Directory Interface (JNDI) Service

19.  Administering Transactions

Part III Appendixes

A.  Subcommands for the asadmin Utility


Re-Creating the Domain Administration Server (DAS)

For mirroring purposes, and to provide a working copy of the DAS, you must have:

Note - You must maintain a backup of the DAS from the first host using the backup-domain(1) subcommand as described in To Back Up a Domain. You can automatically maintain a backup of the DAS using the automatic backups feature of Oracle GlassFish Server.

To Migrate the DAS

The following steps are required to migrate the DAS from the first host (olddashost) to the third host (newdashost).

  1. Install GlassFish Server on newdashost just as it was installed on olddashost.

    This is required so that the DAS can be properly restored on newdashost without causing path conflicts.

  2. Use the restore-domain subcommand to restore the latest backup file onto newdashost.

    For example:

    asadmin> restore-domain --backupdir /net/

    This example assumes that backups are stored in a network-accessible location. If this is not the case, manually copy the latest backup file from offline storage to a directory on newdashost.

    If you have both configuration-only and full backups, restore the latest full backup first. Then, restore the latest configuration-only backup if it is newer than the latest full backup. Use the --backupconfig option of the restore-domain subcommand to specify the appropriate full and configuration-only backups.

    You can backup any domain. However, while re-creating the domain, the domain name should be same as the original.

  3. Stop the domain on olddashost, if it is running.
  4. Start the domain on newdashost by using the start-domain(1) subcommand.

    For example:

    asadmin> start-domain domain1
  5. If the domain on olddashost was centrally administered, set up centralized administration on newdashost.

    See Chapter 2, Setting Up SSH for Centralized Administration, in Oracle GlassFish Server 3.1-3.1.1 High Availability Administration Guide for instructions.

  6. Verify that instances on other hosts are visible to the new DAS on newdashost:
    asadmin> list-instances --long
  7. Update instances on apphost to communicate with the new DAS.

    If the domain uses centralized administration, use the update-admin-server-coordinates subcommand on newdashost:

    asadmin> update-admin-server-coordinates

    If the domain does not use centralized administration, use the update-admin-server-local-coordinates subcommand on apphost:

    asadmin> update-admin-server-local-coordinates
    --adminhost host3 --adminport port-number node-name
  8. Use the new DAS to restart clusters and standalone instances on apphost:

    Restarting the clustered and standalone instances on apphost triggers their recognition of the new DAS on newdashost.

    1. Use the list-clusters subcommand to list the clusters in the domain.
    2. Use the stop-cluster subcommand to stop each cluster.
    3. Use the list-instances subcommand to list the instances in the domain.
    4. Use the restart-instance subcommand to restart each standalone instance.
    5. Use the start-cluster subcommand to start each cluster.

      If the domain does not use centralized administration, use the start-local-instance subcommand to start the cluster instances on apphost.

  9. Verify that instances on apphost are running:
    asadmin> list-instances --long
  10. Decommission and discontinue use of the DAS on olddashost.