IBM BPM, V8.0.1, All platforms > Install IBM BPM > Uninstalling IBM BPM > Remove the Business Process Choreographer configuration

Use the administrative console to remove the Business Process Choreographer configuration

Use this task to remove part or all of the Business Process Choreographer configuration, including the Business Process Choreographer Explorer, Business Process Archive Manager, Business Process Archive Explorer, and the associated resources.

Before you can remove the Business Process Choreographer configuration, you must undeploy all enterprise applications that contain BPEL processes or human tasks.


Procedure

  1. Undeploy the Business Process Choreographer enterprise applications.

    1. Display the enterprise applications.

      In the administrative console, select Applications > Application Types > WebSphere enterprise applications.

    2. Identify which of the following Business Process Choreographer applications are installed, and their original deployment scopes.

      Business Process Choreographer application names
      Application Application names
      Business Flow Manager BPEContainer_ scope
      Human Task Manager TaskContainer_ scope
      Business Process Choreographer Explorer BPCExplorer_ scope
      Business Process Choreographer Business Space predefined tasks HTM_PredefinedTasks_V nnn_ scope and HTM_PredefinedTaskMsg_V nnn_ scope
      Business Process Archive Manager BPArchiveMgr_ scope and TaskArchiveMgr_ scope
      Business Process Archive Explorer BPCArchiveExplorer_ scope
      Where nnn is the version number, and the value of scope depends on your configuration:

      • If the application was originally configured on an application server, scope has the value nodeName_ serverName – even if the server was later promoted to a cluster.

      • If the application was configured on a cluster, scope has the value clusterName.

    3. If you configured Business Process Choreographer, undeploy the predefined tasks, Business Flow Manager, and Human Task Manager applications.

      1. Select HTM_PredefinedTasks_V nnn_ scope and HTM_PredefinedTaskMsg_V nnn_ scope.

      2. Click Undeploy > OK > Save.

      3. Select BPEContainer_ scope, and TaskContainer_ scope.

      4. Click Undeploy > OK > Save.

    4. If you configured the Business Process Choreographer Explorer, undeploy all instances that you configured.

      1. Select the Business Process Choreographer Explorer application instances:

        • Instances that use the default context root, /bpc, are named BPCExplorer_ scope.

        • Instances that use a nondefault context root, context_root, are named BPCExplorer_ scope_ context_root.

      2. Click Undeploy > OK > Save.

    5. If you configured Business Process Archive Manager, undeploy its applications.

      1. Select BPArchiveMgr_ scope and TaskArchiveMgr_ scope.

      2. Click Undeploy > OK > Save.

    6. If you configured the Business Process Archive Explorer, undeploy all instances that you configured.

      1. Select the Business Process Archive Explorer application instances:

        • Instances that use the default context root, /bpcarchive, are named BPCArchiveExplorer_ scope.

        • Instances that use a nondefault context root, context_root, are named BPCArchiveExplorer_ scope_ context_root.

      2. Click Undeploy > OK > Save.
  2. Remove all or any of the following resources that you do not want to reuse:

    1. Optional: Find the data source for Business Process Choreographer or Business Process Archive Manager (the default name for both is BPEDataSource dbType) and make a note of its name and the associated authentication data alias (if any) and Java™ Naming and Directory Interface (JNDI) name, and then remove it (the default name is jdbc/BPEDB).

      To find the data source:

      1. Click Resources > JDBC > Data sources.

      2. For Scope, select the server or cluster where Business Process Choreographer or Business Process Archive Manager was configured.

    2. Optional: Remove the JDBC provider of the data source identified in step 2, unless it contains further data sources that you still need. Click Resources > JDBC > JDBC Providers, select the JDBC driver for your database and click Delete.

    3. Optional: Remove the connection factories and queues. Business Process Choreographer configurations and Business Process Archive Manager configurations normally have the same JNDI names for the connection factories and queues:

      Connection factories for the Business Flow Manager:

      • jms/BPECF
      • jms/BPECFC
      • jms/BFMJMSReplyCF

      Queues for the Business Flow Manager:

      • jms/BPEIntQueue
      • jms/BPERetQueue
      • jms/BPEHldQueue
      • jms/BFMJMSAPIQueue
      • jms/BFMJMSCallbackQueue
      • jms/BFMJMSReplyQueue

      Connection factory for the Human Task Manager:

      • jms/HTMCF

      Queues for the Human Task Manager:

      • jms/HTMIntQueue
      • jms/HTMHldQueue

      How you delete the connection factories and queues depends on the JMS messaging provider that you use.

      • 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 > Connection factories. For Scope, select the server or cluster where Business Process Choreographer or Business Process Archive Manager was configured. Then select the connection factory, and click Delete.

        2. Click Resources > JMS > Queues. For Scope, select the server or cluster where Business Process Choreographer or Business Process Archive Manager was configured. Then select the queues, and click Delete.

      • For WebSphere MQ, remove the JMS queue connection factories and JMS queues.

        1. Click Resources > JMS > Queue connection factories. For Scope, select the server or cluster where Business Process Choreographer or Business Process Archive Manager was configured. Then select the connection factory, and click Delete.

        2. Click Resources > JMS > Queues. For Scope, select the server or cluster where Business Process Choreographer or Business Process Archive Manager was configured. Then select the queues, and click Delete.

    4. If you are using WebSphere default messaging as the JMS provider, remove the activation specifications.

      1. Click Resources > JMS > Activation specifications. For Scope, select the server or cluster where Business Process Choreographer or Business Process Archive Manager was configured.
      2. Remove the following activation specifications:

        • BPEInternalActivationSpec
        • BFMJMSAS
        • HTMInternalActivationSpec

    5. If you are using WebSphere MQ as the JMS provider, remove the listener ports for the server.

      1. Click Servers > Server Types > WebSphere application servers > server_name.
      2. Under Communications, click Messaging > Message Listener Service > Listener Ports.

      3. On the Application servers pane, remove the following listener ports:

        • BPEInternalListenerPort
        • BPEHoldListenerPort
        • HTMInternalListenerPort

      If you configured Business Process Choreographer on a cluster, repeat this step for each member of the cluster.

    6. Optional: Delete the authentication data aliases.

      1. Click Security > Global security then in the Authentication section, expand Java Authentication and Authorization Service , click J2C authentication data.

      2. If the data source identified in step 2 had an authentication data alias, remove that alias. The name depends on the deployment target in the following manner:

        • When Business Process Choreographer is configured on a server named serverName, on a node named nodeName, the name is usually BPCDB_ nodeName. serverName_Auth_Alias.

        • When Business Process Choreographer is configured on a cluster named clusterName, the name is usually BPCDB_ clusterName_Auth_Alias

      3. If any of the connection factories identified in step 2.c have an authentication data alias, remove the alias with great care:

        • If you did not create your Business Process Choreographer configuration on Version 6.0.x, the name is BPC_Auth_Alias and it is shared between all Business Process Choreographer configurations in a ND environment.

          Attention: Only remove this authentication alias if you are removing the last Business Process Choreographer configuration, otherwise the remaining Business Process Choreographer configurations will stop working.

        • If you created your Business Process Choreographer configuration on Version 6.0.x, the name is normally cellName/BPEAuthDataAliasJMS_ scope, where cellName is the name of the cell, and scope identifies the deployment target. You can remove this authentication alias without affecting other Business Process Choreographer configurations.

    7. Optional: Remove the scheduler configuration for the data source JNDI name.

      1. Click Resources > Schedulers.

      2. For Scope, select the server or cluster where Business Process Choreographer or Business Process Archive Manager was configured.

      3. On the Schedulers pane, note the JNDI name of the work manager, then select and delete the scheduler named BPEScheduler.

    8. Optional: Remove the work manager.

      1. Click Resources > Asynchronous beans > Work managers.

      2. For Scope, select the server or cluster where Business Process Choreographer or Business Process Archive Manager was configured.

      3. On the Work managers pane, select and delete the work manager whose JNDI name you noted in step 2.g.

      4. Also delete the work manager with the JNDI name wm/BPENavigationWorkManager.

    9. Optional: Remove the work area partition.

      1. Click Servers > Server Types > WebSphere application servers > server_name, then in the Container Settings section, expand Business Process Services, and click Work area partition service.

      2. On the Application servers pane, select and delete the work area partition BPECompensation.

      If you configured Business Process Choreographer on a cluster, repeat this step for each member of the cluster.

    10. Optional: Remove the mail session.

      1. Click Resources > Mail > Mail providers.

      2. For Scope, select the Cell= cellName, where cellName is the name of the cell.

      3. Click Built-in Mail Provider.
      4. Under the Additional Properties section, select Mail sessions.

      5. Select and delete HTMMailSession_ scope, where scope is the scope identified in step 1.b

  3. 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, then in the Topology section, click 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.

        If you configured Business Process Choreographer to use a remote messaging engine, nodeName. serverName or clusterName will not match the name of the deployment target where you configured Business Process Choreographer.

    3. Under Additional Properties, select Message store.

      • If the JNDI name for the data source. On a server the JNDI name of the data source is usually jdbc/com.ibm.ws.sib/ nodeName. serverName-BPC. cellName.Bus. On a cluster the JNDI name of the data source is usually jdbc/com.ibm.ws.sib/ clusterName-BPC. cellName.Bus.

    4. Click Service integration > Buses > BPC. cellName.BUS, then in the Topology section, click Bus members and remove the bus member identified by one of the following names:

      • nodeName: serverName if you configured Business Process Choreographer on a server.
      • 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. Click Resources > JDBC > Data sources. The scope of the messaging engine might not be the same as the deployment target where you configured Business Process Choreographer.

      If necessary, trying different scopes, look for the JNDI name that you noted in step 3.c. If you configured Business Process Choreographer on a cluster, repeat this step for each member of the cluster.

  4. Delete the BPC_REMOTE_DESTINATION_LOCATION variable. Click Environment > WebSphere variables, for Scope select the deployment target where Business Process Choreographer was configured, then select and delete the variable BPC_REMOTE_DESTINATION_LOCATION variable.

  5. Click Save to save all your deletions in the master configuration.
  6. Restart the application server or cluster.

  7. Optional: Delete the Business Process Choreographer database.

  8. Optional: Delete the Business Process Archive database.

  9. If you are using WebSphere MQ, delete the queue manager used by Business Process Choreographer.

  10. If you use WebSphere default messaging for Business Process Choreographer, delete the messaging database that was used as the message store for the message engine; because it cannot be reused. This is the database pointed to by the data source JNDI name that you noted in step 3.c.


Results

The Business Process Choreographer configuration has been removed.

: Remove the Business Process Choreographer configuration