IBM BPM, V8.0.1, All platforms > Install IBM BPM > Uninstalling IBM BPM > Remove the Business Process Choreographer configuration
Use a script to remove the Business Process Choreographer configuration
Remove the Business Flow Manager, Human Task Manager, Business Process Choreographer Explorer, and the associated resources from a server or cluster.
Before you can remove the Business Process Choreographer configuration, the following conditions must be met:
- You must delete any BPEL process and human task instances, then undeploy all enterprise applications that contain BPEL processes or human tasks.
- If WebSphere administrative security is enabled, and your user ID does not have operator or administrator authority, include the wsadmin -user and -password options to specify a user ID that has operator or administrator authority.
If you are not working with the default profile, use the wsadmin -profileName profile option to specify the profile.
- For stand-alone servers, stop the application server and use the -conntype NONE option.
- In a ND environment, run the script, as follows:
- If the dmgr is not running, run the script on the dmgr, using the -conntype NONE option.
- If the dmgr is running, stop the application server from which the configuration is to be removed, then run the script, omitting the -conntype NONE option.
Procedure
- Change to the Business Process Choreographer config directory:
INSTALL_ROOT/ProcessChoreographer/config
![]()
INSTALL_ROOT/ProcessChoreographer/config
INSTALL_ROOT\ProcessChoreographer\config
- Run the script bpeunconfig.jacl.
For a single server on a Linux or UNIX platform, enter the command:
INSTALL_ROOT/bin/wsadmin.sh -f bpeunconfig.jacl -server Server -node Node [-forcePredefTasks yes|no]For a cluster on a Linux or UNIX platform, enter the command:
INSTALL_ROOT/bin/wsadmin.sh -f bpeunconfig.jacl -cluster Cluster [-forcePredefTasks yes|no]For a single server on a Windows platform, enter the command:
INSTALL_ROOT\bin\wsadmin.bat -f bpeunconfig.jacl -server Server -node Node [-forcePredefTasks yes|no]For a cluster on the Windows platform, enter the command:
INSTALL_ROOT\bin\wsadmin.bat -f bpeunconfig.jacl -cluster Cluster [-forcePredefTasks yes|no]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.
- forcePredefTasks yes | no
- This specifies whether to force the removal of the predefined Human Tasks enterprise application:
If you select yes, the predefined Human Tasks application is removed from the WebSphere configuration repository, but the corresponding entries remain in the Business Process Choreographer database. When removing the configuration for a single server with WebSphere security enabled, enter the command:
INSTALL_ROOT/bin/wsadmin.sh -f bpeunconfig.jacl -server Server -node Node -userid userID -password passwordWhen removing the configuration for a single server with WebSphere security disabled, enter the command:
INSTALL_ROOT/bin/wsadmin.sh -f bpeunconfig.jacl -server Server -node NodeWhen removing the configuration for a cluster with WebSphere security enabled, enter the command:
INSTALL_ROOT/bin/wsadmin.sh -f bpeunconfig.jacl -cluster Cluster -userid userID -password passwordWhen removing the configuration for a cluster with WebSphere security disabled, enter the command:
INSTALL_ROOT/bin/wsadmin.sh -f bpeunconfig.jacl -cluster ClusterWhere:
- 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.
If you omit a required parameter, you are prompted for it.
- Optional: Delete the databases 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. The list of databases is also written to the INSTALL_ROOT/profiles/ profileName/logs/bpeunconfig.log log file. You can use this list to identify which databases you might want to delete manually.
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.
- Optional: Check the bpeunconfig.log log file. It is located in the logs subdirectory of the profile_root directory.
- If you used WebSphere MQ, delete the queue manager used by Business Process Choreographer.
- 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:
- Installing the BusinessCalendar system application
- Enabling the WorkAreaService
- Enabling the ApplicationProfileService
- Enabling the ObjectPoolService
- Enabling the StartupBeansService
- Enabling the CompensationService
- Enabling the WorkareaPartitionService
- Setting WebSphere variables
Results
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.