Administration Console Online Help

    Previous Next  Open TOC in new window 
Content starts here

Configure Jolt startup and shutdown classes


On each WebLogic Server instance that hosts a Jolt connection pool, you must configure Jolt classes to run as server startup up and shutdown classes. The classes establish and terminate the connection between Tuxedo and WebLogic Server.

To configure the Jolt startup and shutdown classes:

  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 Administration Console, expand Environment and select Startup and Shutdown Classes.
  3. To configure the startup class:
    1. On the Startup and Shutdown Classes page, click New.
    2. On the Configure a New Startup or Shutdown Class: Class Type page, choose Startup Class. Then click Next.
    3. On the Startup Class Properties page, enter a name that you will use the identify this configuration of your Java class. For example, MyJoltStartupClass.
    4. In the ClassName field, enter the following: bea.jolt.pool.servlet.weblogic.PoolManagerStartUp
    5. Check Failure is Fatal.
    6. Click Save.
    7. Select the Target and Deploy tab.
    8. Select the servers or clusters that host Jolt connection pools and click Save.
  4. To configure the startup class:
    1. On the Startup and Shutdown Classes page, click New.
    2. On the Configure a New Startup or Shutdown Class: Class Type page, choose Shutdown Class. Then click Next.
    3. On the Shutdown Class Properties page, enter a name that you will use the identify this configuration of your Java class. For example, MyJoltShutdownClass.
    4. In the ClassName field, enter the following: bea.jolt.pool.servlet.weblogic.PoolManagerShutDown
    5. Click Save.
    6. Select the Target and Deploy tab.
    7. Select the servers or clusters that host Jolt connection pools and click Save.
  5. 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).

After you finish

  1. Add startup and shutdown classes to the classpath.
  2. Restart each server instance on which you have deployed the classes.

  Back to Top