Using a script to remove the Business Process Choreographer configuration

Use this task to remove the business process container, task container, and Business Process Choreographer Explorer configuration, and the associated resources.

Why and when to perform this task

Before you can remove the Business Process Choreographer configuration, you must stop all process and task templates, delete all process and task instances, then stop and remove the configuration for all enterprise applications that contain business processes or human tasks.

Steps for this task

  1. Change to the Business Process Choreographer sample directory:

    On Windows® platforms, enter the command:

    cd install_root\ProcessChoreographer\sample

    On UNIX® and Linux® platforms, enter:

    cd install_root/ProcessChoreographer/sample
  2. Run the script bpeunconfig.jacl. Use the appropriate command in the following table. In the following cases, also specify the appropriate options:
    • For stand-alone servers, stop the application server and use the -conntype NONE option. This step ensures that any Cloudscape databases are not locked and can be removed automatically.
    • In a Network Deployment (ND) environment, run the script, as follows:
      • If the deployment manager is not running, run the script on the deployment manager, using the -conntype NONE option.
      • If the deployment manager is running, stop the application server from which the configuration is to be removed, then run the script, omitting the -conntype NONE option.

        When the script is running on the application server node from which the Business Process Choreographer configuration is to be removed, the script can automatically delete any Cloudscape databases.

    • If WebSphere® security is enabled, specify also the user ID and password:
       -userid userID  -password password
    • If you are not configuring the default profile, specify also the profile name:
       -profileName profileName
    For a single server on Windows, use the command:
    install_root\bin\wsadmin.bat -f bpeunconfig.jacl 
        -server Server -node Node
        [-deleteDB deleteDatabase]
        [-conntype NONE]
    For a cluster on Windows, use the command:
    install_root\bin\wsadmin.bat -f bpeunconfig.jacl 
        -cluster Cluster 
        [-conntype NONE]
    For a single server on UNIX, use the command:
    install_root/bin/wsadmin.sh -f bpeunconfig.jacl  
        -server Server -node Node
        [-deleteDB deleteDatabase]
        [-conntype NONE]
    For a cluster on UNIX, use the command:
    install_root/bin/wsadmin.sh -f bpeunconfig.jacl 
        -cluster Cluster
        [-conntype NONE]
    Where:
    userID
    The user ID.
    password
    The password for the user ID.
    profileName
    The name of the profile that is being configured. If you are configuring the default profile, this option is optional.
    Server
    The name of the application server. If only one server exists, this parameter is optional.
    Node
    The name of the node. This is optional. If the node is omitted, the local node is used.
    Cluster
    The name of the cluster.
    deleteDatabase
    A Boolean value that specifies whether to delete Cloudscape databases:
    • yes
    • no
    If you omit a parameter, you are prompted for it.
  3. Optional: Delete the database used by Business Process Choreographer.

    For both the Business Process Choreographer database and the messaging database the following apply:

    • The bpeunconfig.jacl script lists the databases that were used by the configuration that has been removed. You can then more easily identify the databases that are to be removed.
    • When a Cloudscape database is used for the Business Process Choreographer database, the bpeunconfig.jacl script optionally removes the database, unless it is locked by a running application server. If the database is locked, stop the server, and use the -conntype NONE option.
  4. Optional: Check the log file install_root/profiles/profileName/logs/bpeunconfig.log.
  5. Required: Delete the database used by WebSphere default messaging. This database cannot be reused in a new configuration.

    For both the Business Process Choreographer database and the messaging database the following apply:

    • The bpeunconfig.jacl script displays a list of the databases that were used by the configuration that has been removed. The list of databases is also written to the install_root/profiles/profileName/logs/bpeunconfig.log log file. Use this information to identify the databases that are to be removed.
    • When Cloudscape is the messaging database, the bpeunconfig.jacl script optionally removes the database, unless it is locked by a running application server. If the database is locked, stop the server, and use the -conntype NONE option.
  6. Optional: For WebSphere MQ only, delete the queue manager used by Business Process Choreographer.
  7. Optional: Manually undo remaining settings that bpeunconfig.jacl does not undo. The following settings are not undone by the bpeunconfig.jacl script because it cannot determine whether the settings are still needed by other components:
    • enabling the WorkAreaService
    • enabling the ApplicationProfileService
    • enabling the ObjectPoolService
    • enabling the StartupBeansService
    • enabling the CompensationService
    • enabling the WorkareaPartitionService
    • enabling the WebSphere Security and Java 2 security
    • setting WebSphere variables
    • updates to the deployment manager's server.policy file in an ND environment
    • installing or adding target mappings for the SchedulerCalendars application

Result

The Business Process Choreographer applications and associated resources (such as scheduler, data sources, listener ports, connection factories, queue destinations, activation specs, work area partition, mail session, and authentication aliases) have been removed.

Terms of use |

Last updated: Tue Feb 21 17:47:13 2006

(c) Copyright IBM Corporation 2005.
This information center is powered by Eclipse technology (http://www.eclipse.org)