Using the administrative console to remove the Business Process Choreographer configuration

Use this task to remove part or all of 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 tasks and process instances, then stop and uninstall all enterprise applications that contain business processes or human tasks.

Steps for this task

  1. Uninstall the Business Process Choreographer enterprise applications.
    1. Display the enterprise applications.

      In the administrative console, select Applications > Enterprise Applications.

    2. Identify the scope of the Business Process Choreographer installation.
      Look for applications with the following names:
      • BPEContainer_scope is the business process container application.
      • TaskContainer_scope is the human task container application.
      • BPCExplorer_scope is the Business Process Choreographer Explorer application.
      • BPCObserver_scope is the Business Process Choreographer Observer application.
      • BPCECollector_scope is the event collector application that is required by the Business Process Choreographer Observer.
      Where the value of scope depends on your configuration:
      • If Business Process Choreographer was configured on an application server, scope has the value nodeName_serverName.
      • If Business Process Choreographer was configured on a cluster, scope has the value clusterName.
    3. Optional: If you installed the business process container, uninstall it. Select BPEContainer_Scope, then click Uninstall > OK > Save > Save.
    4. Optional: If you installed the human task container, uninstall it.
      1. Select TaskContainer_Scope, then click Stop.
      2. Select the application again, then click Uninstall > OK > Save > Save.
    5. Optional: If you installed Business Process Choreographer Explorer, uninstall it.
      1. Select BPCExplorer_Scope, then click Stop.
      2. Select the application again, then click Uninstall > OK > Save > Save.
    6. Optional: If you installed Business Process Choreographer Observer, uninstall it and the Business Process Choreographer Common Event Infrastructure consumer.
      1. Select bpcobserver_Scope and bpcobservereventconsumer_Scope, then click Stop.
      2. Select the applications again, then click Uninstall > OK > Save > Save.
  2. Remove all or any of the following resources that you do not want to reuse:
    1. Optional: Find the Business Process Choreographer data source (the default name is BPEDataSourcedbType) and note its associated authentication data alias (if any) and Java Naming and Directory Interface (JNDI) name before removing it (for a single server, the default name is jdbc/BPEDB).

      To find the data sources:

      1. Click Resources > JDBC Providers.
      2. If Business Process Choreographer was installed on an application server, select Server.
      3. If Business Process Choreographer was installed on a cluster, select the cluster.
      4. Click Apply.
      5. Select the appropriate JDBC provider, then click Data sources.
      6. If you are using an Oracle database management system, remove also a second data source: BPEDataSourceOracleNonXA.
    2. Optional: For a database other than a Cloudscape database, remove the JDBC provider of the data source identified in step 2, unless it contains further data sources that you still need.
    3. Optional: Remove the appropriate connection factories and queues.
      • For default messaging, before you remove the connection factories, note their associated authentication data aliases. Then remove the JMS connection factories and JMS queues.
        1. Click Resources > JMS Providers > Default messaging.
        2. On the Default messaging provider pane perform one of the following:
          • If you configured Business Process Choreographer on a cluster, select Cluster then click Apply.
          • If you configured Business Process Choreographer on a server, select Server then click Apply.
      • For WebSphere MQ, remove the JMS queue connection factories and JMS queue destinations.
        1. Click Resources > JMS Providers > WebSphere MQ.
        2. On the WebSphere MQ messaging provider pane, select Server. Then click Apply.
        If you configured Business Process Choreographer on a cluster, you must repeat this for each server that is a member of the cluster.

      For the business process container the JNDI names are normally as follows:

      • jms/BPECF
      • jms/BPECFC
      • jms/BPEIntQueue
      • jms/BPERetQueue
      • jms/BPEHldQueue
      For the human task container the JNDI names are normally as follows:
      • jms/HTMCF
      • jms/HTMIntQueue
      • jms/HTMHldQueue
    4. Optional: If you are using WebSphere default messaging as the JMS provider, remove the activation specifications.
      1. Click Resources > JMS Providers > Default messaging > JMS activation specification.
      2. Remove the following activation specifications:
        • BPEInternalActivationSpec
        • HTMInternalActivationSpec
    5. Optional: If you are using WebSphere MQ as the JMS provider, remove the listener ports.
      1. Click Servers > Application servers > serverName.
      2. Under Communications, click Messaging > Message Listener Service > Listener Ports.
      3. On the Application servers pane, remove the following listener ports:
        • BPEInternalListenerPort
        • BPEApiListenerPort
        • BPEHoldListenerPort
        • HTMInternalListenerPort
    6. Optional: Delete the authentication data aliases.
      • If the data source identified in step 2 had an authentication data alias, remove that alias.

        Usually, the alias for the database is named cellName/BPEAuthDataAliasdbType_Scope, where:

        cellName
        The name of the cell
        dbType
        The database type
        Scope
        One of the values given in step 1.b
      • If any of the connection factories identified in step 2.c have an authentication data alias, remove the alias.

        Usually, the alias for the database is named cellName/BPEAuthDataAliasJMS_Scope, where:

        cellName
        The name of the cell
        Scope
        One of the values given in step 1.b

      The authentication data alias is in Security > Global security > JAAS Configuration > J2C Authentication data.

    7. Optional: Remove the scheduler configuration for the data source JNDI name.
      1. Click Resources > Schedulers.
      2. Select the scope of the Business Process Choreographer configuration; either Server or cluster. Then click Apply.
      3. On the Schedulers pane, note the work manager name, then select and delete the scheduler BPEScheduler.
    8. Optional: Remove the work manager.
      1. Click Resources > Asynchronous beans > Work managers.
      2. Select the scope of the Business Process Choreographer configuration; either Server or cluster. Then click Apply.
      3. On the Work managers pane, select and delete the work manager whose name you noted in step 2.g.
    9. Optional: Remove the work area partition.
      1. Click Servers > Application servers > serverName.
      2. Under Business Process Services, click Work area partition service.
      3. On the Application servers pane, select and delete the work area partition BPECompensation.
    10. Optional: Remove the mail session.
      1. Click Resources > Mail Providers.
      2. On the Mail Providers pane, select Cell. Then click Apply.
      3. Click Built-in Mail Provider.
      4. Under Additional Properties, select Mail sessions.
      5. Select and delete HTMMailSession_Scope, where Scope is the scope identified in step 1.b
    11. In a cluster, repeat the removal of any server level resources for each cluster member.
    12. Save your configuration changes.
    13. Restart the application server.
  3. Optional: If you use WebSphere default messaging for Business Process Choreographer, you can delete the bus member, bus, and data source:
    1. Click Service integration > Buses > BPC.cellName.Bus > Messaging engines.
    2. Select the messaging engine:
      • nodeName.serverName-BPC.cellName.Bus if you configured Business Process Choreographer on a server.
      • clusterName-BPC.cellName.Bus if you configured Business Process Choreographer in a cluster.
        Note: If you configured Business Process Choreographer to use a remote messaging engine, clusterName might not match the name of the cluster where you configured Business Process Choreographer.
    3. In Additional Properties, select Data store, and note the JNDI name for the data source.
    4. Go to Service integration > Buses > BPC.cellName.Bus > Bus members and remove the bus member identified by one of the following:
      • Node=nodeName, Server=serverName if you configured Business Process Choreographer on a server.
      • Cluster=clusterName if you configured Business Process Choreographer on a cluster.
    5. Optional: If you removed the last member of the bus BPC.cellName.Bus, you can also remove the bus.
    6. Optional: Remove the data source. Click Resources > JDBC Providers > Server > Apply > Cloudscape JDBC Provider > Data Sources, then delete the data source that you noted in step 3.c.
  4. Optional: If you configured Business Process Choreographer on a cluster, delete the BPC_REMOTE_DESTINATION_LOCATION variable: Click Environment > WebSphere Variables > Cluster > Apply. Select the variable named BPC_REMOTE_DESTINATION_LOCATION, then click Delete.
  5. Click Save to save all your deletions in the master configuration.
  6. Optional: Delete the Business Process Choreographer database.
  7. Optional: If you are using WebSphere MQ, delete the queue manager used by Business Process Choreographer.
  8. If you use WebSphere default messaging for Business Process Choreographer, delete the datastore for the message engine. If you use the default data store, you can delete the data store by deleting the following directory:
    • On Windows systems, delete install_root\profiles\profileName\databases\com.ibm.ws.sib\nodeName.serverName-BPC.cellName.Bus
    • On UNIX and Linux systems, delete install_root/profiles/profileName/databases/com.ibm.ws.sib/nodeName.serverName-BPC.cellName.Bus
  9. Optional: If you configured the Business Process Choreographer Observer perform the following:
    1. Using the administrative console to remove the Business Process Choreographer event collector for each event collector.
    2. Using the administrative console to remove Business Process Choreographer Observer.

Result

The Business Process Choreographer configuration has been removed.

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