Using the administrative console to remove part or all of the business process container configuration

Use this task to remove part of the business process container configuration. The database and queue manager will not be deleted.

Before you begin

Why and when to perform this task

Before you can uninstall the business process container, you must stop all process templates, delete all process instances, then stop and uninstall all enterprise applications that contain business processes.

Steps for this task

  1. Ensure that all the stand-alone servers, the database, and the application server (or at least one application server per cluster) are running.
  2. For each enterprise application that contains business processes, stop all process templates:
    1. For V5.0-style processes , select Enterprise Applications> Application Name> Business Process Modules.
      Then for each process archive (.far file), click Templates> Select All> Stop> Save> Save
    2. Wait for any running instances to finish.

      Note: To see if any instances are running, you can log on to the Web client as administrator, and view the processes that are "Administered By Me". If the list is empty, no instances exist.

    3. If there are any instances that have the autoDelete flag set to false, or that cannot be completed for some other reason, you must delete them manually.
    4. Stop and uninstall the application.
    5. If there are any more applications that contain business processes, repeat step 2.
  3. In the administrative console, select Applications > Enterprise Applications > BPEContainer_identifier.
    Where identifier depends on where you installed the business process container.
    Installed the business process container on BPEContainer_identifier
    Application server BPEContainer_nodeName_serverName
    Cluster BPEContainer_clusterName


  4. Click Stop.
  5. Click Uninstall > Save > Save.
  6. If the uninstall fails, make sure that all business process applications have been stopped and uninstalled.
  7. Using the administrative console, find and remove all or any of the following resources that you do not want to reuse:
    1. Find the process choreographer data source (usually named BPEDataSourcedbType) and note its associated authentication data alias (if any) and JNDI name (usually, jdbc/BPEDB) before removing it. If using Oracle there is a second data source named BPEDataSourceOracleNonXA which you must remove as well.
    2. If the above data source had an authentication data alias, remove it. Usually, it is named cellName/BPEAuthDataAliasdbType_identifier. Where cellName is the name of the cell, dbType is the database type, and identifier is one of the values given in the previous table.
    3. Remove the JDBC provider of the above data source unless it contains further data sources that you still need.
    4. Remove the process choreographer CMP connector factory, usually named BPEDataSourcedbType_CF.
    5. Find the scheduler configuration for the data source JNDI name that you noted in step 7a and remove it as well as the associated work manager.
    6. On the process container configuration page, note the listener port names of the following:
      • inputListenerPort - normally has the value BPEInternalListenerPort
      • externalRequestListenerPort - normally has the value BPEApiListenerPort
      • holdListenerPort - normally has the value BPEHoldListenerPort
    7. In the application server configuration, locate and note their queue and queue connection factory JNDI names, these are normally:
      • jms/BPEIntQueue
      • jms/BPEApiQueue
      • jms/BPEHldQueue
      • jms/BPECF
      • jms/BPECFC
    8. Remove the three listener ports.
    9. On the process container configuration page, note the retention queue factory name (normally jms/BPECF).
    10. In the following, note the associated authentication data aliases (if any) before removing the queue connection factories:
      1. When using WebSphere MQ, remove all queues and queue connection factories in the WebSphere MQ JMS provider whose JNDI names match the ones noted in the previous steps.
      2. When using embedded messaging, note the associated queue names of all queues before removing them, they are normally:
        • BPEIntQueue_serverName
        • BPEApiQueue_serverName
        • BPEHldQueue_serverName
        • BPERetQueue_serverName
    11. Remove any authentication data aliases noted in the previous step.
    12. In a cluster, repeat the removal of any other server level resources.
    13. Save your configuration changes.
    14. Restart the application server.

Results

The business process container has been uninstalled, but the process choreographer database and queue manager have not been removed. Resources related to the business process container (such as scheduler, data sources, listener ports, connection factories, and queue destinations) that you have not removed can either be uninstalled separately, or reused.

Related tasks
Managing processes



Searchable topic ID:   t2demanual
Last updated: Jun 21, 2007 8:07:48 PM CDT    WebSphere Business Integration Server Foundation, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.wasee.doc/info/ee/workflow/tasks/t2demanual.html

Library | Support | Terms of Use | Feedback