edocs Home > BEA WebLogic Server 10.0 Documentation > Administration Console Online Help > Configure a Singleton Service

Administration Console Online Help

    Previous Next  Open TOC in new window 
Content starts here

Configure a Singleton Service

Before you begin

Ensure that you have defined a singleton service using the Administration Console. See Define a New Singleton Service.


A singleton service is a service running on a managed server that is available on only one member of a cluster at a time. WebLogic Server provides allows you to automatically monitor and migrate singleton services from one server to another.

The following procedures show you how to configure the migration behavior of a singleton service.

  1. If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit (see Use the Change Center).
  2. In the Domain Structure tree, expand Environment > Clusters.
  3. Select the cluster where you want to define the new singleton service, then select Singleton Services.
  4. Click General.
    1. Ensure that you have defined a value for the Class Name field. This field must contain the fully qualified name to the class. The class must also be contained in the server classpath.

      The class specified in Class Name must implement the SingletonService interface in order to function as a migratable singleton service. See Service-Level Migration.

    2. Enter information for the following fields:

      Additional Migration Attempts:

      Sleep Time Between Attempts:

  5. Click Migration.
    1. Specify a value for the User Preferred Server field.
    2. Specify a list of Constrained Candidate Servers.
  6. Click Save.
  7. To activate these changes, in the Change Center of the Administration Console, click Activate Changes.
    Not all changes take effect immediately—some require a restart (see Use the Change Center).

Result

After you finish

The singleton service created using these procedures uses the default behavior for determining the list of candidate servers for migration. The default is to iterate through all of the servers in the cluster. To configure the list of candidate servers and other aspects of automatic server migration, see Configure server migration in a cluster.


  Back to Top