BEA Logo BEA Collaborate Release 2.0

  BEA Home  |  Events  |  Solutions  |  Partners  |  Products  |  Services  |  Download  |  Developer Center  |  WebSUPPORT

   http://www.oracle.com/technology/documentation/index.html   |   Site Map   |   Search   |   PDF Files   |   Contact   |   Glossary

 

   Collaborate Documentation   |   Administering   |   Previous Topic   |   Next Topic   |   Contents

Configuring Persistence and Recovery

 

The following sections describe persistence and recovery:

 

Understanding Persistent Mode

In persistent mode, all state records are read from and written to persistent storage and are not cached in memory. In persistent mode, WebLogic Collaborate stores the states of the following types of run-time objects in persistent storage:

Persistent storage consists of a database that WebLogic Collaborate accesses by means of a connection pool. The same database is used by both persistent storage and the repository. WebLogic Collaborate creates a state record for each run-time component that it creates during processing. A state record is a row in a database table; the row represents an object state.

Multiple objects can change state during the time that a message passes through WebLogic Collaborate. WebLogic Collaborate updates the persistent storage for these objects as a group. If a message passes through WebLogic Collaborate successfully, then the recorded changes are retained. If the message processing fails in any part of WebLogic Collaborate, then WebLogic Collaborate can retry some operations. When an operation fails, WebLogic Collaborate discards the changes that the operation caused. To maintain and update a set of objects states as a group, WebLogic Collaborate uses transactions.

WebLogic Collaborate performs special processing for messages. WebLogic Collaborate uses the message size and the large message support configuration to determine how to save the message, as follows:

For information about the large message threshold and large message support, see Configuring WebLogic Collaborate in BEA WebLogic Collaborate Administration Console Online Help.

 

Understanding Nonpersistent Mode

In nonpersistent mode, all state records other than the repository are maintained in memory and recovery is disabled. In nonpersistent mode, WebLogic Collaborate stores the states of run-time objects to in-memory tables. The only difference between persistent mode and nonpersistent mode is that in nonpersistent mode WebLogic Collaborate does not save states in persistent storage. This means that states cannot be retrieved when the system is shut down and therefore state information does not survive system restarts.

Note: It is recommended that you use this option only when you are developing your WebLogic Collaborate system, not during run time.

Note: If you migrated a Java messaging application that was written using the WebLogic Collaborate C-Enabler API to WebLogic Collaborate Release 2.0, the migrated application must be run in a separate JVM in nonpersistent mode.

 

Understanding Recovery

The following list describes the WebLogic Collaborate phases that affect recovery:

  1. Startup

    WebLogic Collaborate starts in either persistent mode or nonpersistent mode. You cannot change the persistence mode while WebLogic Collaborate is running. For information about configuring the persistence mode, see Configuring Persistence and Recovery.

  2. Shutdown

    WebLogic Collaborate shuts down in one of the following modes:

  3. Restart

    When WebLogic Collaborate restarts after a shutdown, its behavior depends on whether it is running in persistent mode or nonpersistent mode:

 

Configuring Persistence and Recovery

The following table describes how to set the persistence mode when you start WebLogic Collaborate.

Table 9-1 Setting the Persistence Mode

When you start WebLogic Collaborate with the following method . . .

Do the following to start WebLogic Collaborate in persistent mode . . .

Or do the following to start WebLogic Collaborate in nonpersistent mode . . .

WebLogic Collaborate Administration Console

For information about starting WebLogic Collaborate from the WebLogic Collaborate Administration Console, see Starting, Stopping, and Customizing WebLogic Collaborate.

  1. Go to the Monitoring —> General tab in the WebLogic Collaborate Administration Console.

  2. Click Start this server.

  3. The resulting dialog box presents a checkbox labeled Persistence On. Select the checkbox if it is not already selected.

  4. Click Yes.

  1. Go to the Monitoring —> General tab in the WebLogic Collaborate Administration Console.

  2. Click Start this server.

  3. The resulting dialog box presents a checkbox labeled Persistence On. De-select the checkbox if it is not already de-selected.

  4. Click Yes.

Note: It is recommended that you run in nonpersistent mode only when you are developing your WebLogic Collaborate system, not during run time.

Start menu

In the Start menu, select the Start Server command for WebLogic Collaborate. For details about how to do this, see Starting, Stopping, and Customizing WebLogic Collaborate.

  1. Add the PERSISTENCE value to the config.xml file. PERSISTENCE is one of the possible values for the StartupClass's Arguments attribute. For example: 
    <StartupClass
        ClassName=
                "com.bea.b2b.
                server.Startup"
        Name=
                "WLCStartup"
        Arguments=
                "PERSISTENCE=OFF"
        Targets=
                "myserver"
    />

  2. In the Start menu, choose the Start Server command for WebLogic Collaborate. For details about how to do this, see Starting, Stopping, and Customizing WebLogic Collaborate.

Command line

Issue the command to start WebLogic Collaborate. For instructions, see Starting, Stopping, and Customizing WebLogic Collaborate.

  1. Add the PERSISTENCE value to the config.xml file. PERSISTENCE is one of the possible values for the StartupClass's Arguments attribute. For example: 
    <StartupClass
        ClassName=
                "com.bea.b2b.
                server.Startup"
        Name=
                "WLCStartup"
        Arguments=
                "PERSISTENCE=OFF"
        Targets=
                "myserver"
    />

  2. Issue the command to start WebLogic Collaborate. For instructions, see Starting, Stopping, and Customizing WebLogic Collaborate.

 
 

 

back to top previous page next page

 

Copyright © 2001 BEA Systems, Inc. All rights reserved.
Required browser: Netscape 4.0 or higher, or Microsoft Internet Explorer 4.0 or higher.