Skip navigation FileNet logo
Glossary  |  Help Directory  
  Help for Process Configuration Console
  Search  |  Index
Process Reference  
Process Configuration Console
Getting started
Isolated regions
  Initialize an isolated region
  Connect to an isolated region
  Disconnect from an isolated region
  Export to
IBM CrossWorlds®
  Copy an isolated region
  Remove an isolated region
  Modify isolated region properties
     Configure event logging options
     Enable or disable statistics collection
     Set performance parameters
     Set web application properties
     Configure step processors
     Specify step processor locations
Queues
Rosters
VWServices
Process Engines
Workflow database
Events and statistics
   

Copy an isolated region

NOTE This functionality is available only on systems that have multiple Process Routers/isolated regions.

Use this procedure to copy workflow roster, work queue, and event log definitions as well as isolated region properties from one isolated region to another. The destination region does not have to be on the same system as the source region; however, both regions must be accessible by a Process Router on the same Application Engine or web server.

To copy an isolated region

  1. If you are not already connected to both the source and destination isolated regions, do so.
  2. Select the icon of the isolated region you want to copy, then select Copy to... from the Action menu.
  3. Select the destination region from the Destination list. The list displays only those isolated regions you are currently connected to.

    NOTE If you are copying to a different service, the destination service must have the same or greater number of servers as the service you are copying from.

  4. Check Overwrite queues, rosters, and event logs to overwrite items on the destination region that have the same name as items on the source region. If you do not check this box, items with the same name are ignored.
  5. Click Copy to continue, or Cancel to cancel the action.
  6. Click Commit Changes on the toolbar to apply these changes to the destination isolated region. You can commit the changes immediately, or you can wait until you have finished all your changes.

    NOTE The commit process suspends all other database transactions within the isolated region until it finishes. We strongly recommend that you accumulate all changes and commit them once when you're done, or that you commit changes when the isolated region is relatively inactive. Avoid committing changes after every modification whenever possible.

   

NOTE When you perform this action, you make changes to the workflow database structures. If you currently have data in your workflow database, FileNet recommends backing up all the servers in your VWService prior to completing this change.

Related topics

Initialize an isolated region

About isolated regions

Remove an isolated region

Remove all isolated regions

Remove the workflow database