Configuring Persistence and Recovery

The following sections describes persistence for WebLogic Integration business-to-business (B2B) integration applications:

• Persistence

• High Availability and Recovery

 

---

Persistence

The B2B engine can be configured to run in one of the following modes:

• Persistent mode
  In this mode, persistence is set to ON. The in-memory, dynamic state of B2B objects is saved to, and can be retrieved from, persistent storage in the database repository. Run-time states can be recovered in the event of an abnormal shutdown or crash. By default, WebLogic Integration is deployed in persistence mode.

• Nonpersistent mode
  In this mode, persistence is set to OFF. The in-memory, dynamic state of B2B objects is not saved. State information does not survive system restarts.

The persistence setting used by the B2B engine is determined by the configuration of the B2B startup EJB. (For instructions on configuring this class, see Configuring Persistence for B2B.) Thus, as soon as you start WebLogic Integration, as described in Getting Started in Starting, Stopping, and Customizing BEA WebLogic Integration, the B2B engine starts running in either persistent or nonpersistent mode.

Notes: We recommend that you use nonpersistent mode only when developing your WebLogic Integration B2B application, not in production. Persistence can only be turned off for the business-to-business (B2B) integration functionality of WebLogic Integration. Persistence is always on for the business process management and application integration functionality of WebLogic Integration.

Configuring Persistence for B2B

The configuration of the B2B startup EJB determines the persistence setting the B2B engine uses when you start WebLogic Integration. The following procedure describes how to view or modify the B2B startup configuration from the WebLogic Server Administration Console.

To view or modify the startup configuration:

1. Start the WebLogic Server Administration Console, as described in Starting the WebLogic Server Administration Console in Starting, Stopping, and Customizing BEA WebLogic Integration.

2. In the navigation tree, choose Deployments—>Applications —>WLI—>WLI-B2B Startup.

3. Select the Edit EJB Descriptor... link.

4. In the navigation tree, choose b2b-startup.jar—>EJB Jar —>Enterprise Beans—>Sessions—>B2BStartup—>Env Entries.

   In a new browser window, the b2b-startup.jar configuration is displayed.

5. In the navigation tree of the new browser window, click PERSISTENCE.

6. In the right pane, select the Optional tag.

   One of the following is displayed in the Env Entry Value text box:

   • ON
     The B2B engine is configured to start in persistent mode.

   • OFF
     The B2B engine is configured to start in nonpersistent mode.

7. To modify the current setting, edit as required and click Apply.

8. In the navigation tree, click b2b-startup.jar.

9. In the right pane, click Persist.

10. Close the WebLogic Server Administration Console.

11. To initiate the new settings, shut down and restart WebLogic Integration as follows:

    • Follow the shutdown instructions in Stopping WebLogic Integration in Starting, Stopping, and Customizing BEA WebLogic Integration.

    • Follow the restart instructions in Starting WebLogic Integration in Starting, Stopping, and Customizing BEA WebLogic Integration.

 

---

High Availability and Recovery

For more information about the benefits of deploying WebLogic Integration in persistence mode, see Configuring WebLogic Integration Clusters for High Availability in Deploying BEA WebLogic Integration Solutions.