Fix (APAR): JR44202 Status: Fix Product: IBM Business Process Manager Release: 8.0.0.0 Operating System: All operating systems Supersedes Fixes: Pre-requisite Fixes: Exclusive-requisite Fixes: Defect: JR44202 Byte size of APAR: 192172 Date: 2012-10-05 Abstract: CROSS-CELL ENABLEMENT FOR FEDERATED REST API Problem Description: Add support to add endpoints form another cell to the federated REST API. Problem Summary: You can use the federated REST API to provide a single, federated user experience for interacting with processes and tasks from multiple IBM® Business Process Manager systems, or across multiple process servers. Federation with IBM Case Manager solutions is also supported. The Federation API allows you to display processes and tasks created in Process Designer and Integration Designer in the same task list. If your environment has multiple clusters in the same cell or includes multiple cells, you must manually configure the federation domains using commands. Endpoints for REST APIs in the same cell are automatically registered during the initial configuration. Endpoints for other cells must be added manually using wsadmin commands. More information about the federated REST API can be found in the infocenter: http://pic.dhe.ibm.com/infocenter/dmndhelp/v8r0mx/topic/com.ibm.wbpm.bpc.doc/topics/cbsp_restapis_federation.html http://pic.dhe.ibm.com/infocenter/dmndhelp/v8r0mx/topic/com.ibm.wbpm.bspace.imuc.doc/topics/tcfg_bsp_enable_federation.html Problem Conclusion: Two new admin commands are added: --------------------------------------------------------------------------------------------------- addBPMSystem Description: Adds an BPM (BPEL or BPD engine) system to the local BPM federated API. Target object: None Arguments: *bpmCellName - The name of the cell where the BPM system is configured. bpmNodeName - The name of the node where the BPM system is configured. If this parameter is specified, then the bpmServerName parameter must be specified. Do not specify this parameter if the bpmClusterName parameter is specified. bpmServerName - The name of the server where the BPM system is configured. If this parameter is specified, then the bpmNodeName parameter must also be specified. Do not specify this parameter if the bpmClusterName parameter is specified. bpmClusterName - The name of the cluster where the BPM system is configured. Do not specify this parameter if the bpmNodeName or bpmServerName parametesr are specified. *bpmSystemType - The type of the BPM system. Either specify BPEL or BPD. *bpmHostName - The host name of the BPM system. *bpmPort - The port of the BPM system. *bpmTransportType - The transport type used by the REST calls. Either specify http or https. processServicesContextRoot - The context root for the process services endpoint. Specify a value here if the context root for the bfmrestapi.war of the BPEContainer application or the context root for the bpmrest.war of the IBM_BPM_Teamworks application was changed. taskServicesContextRoot - The context root for the task services endpoint. Specify a value here if the context root for the taskrestapi.war of the TaskContainer application or the context root for the bpmrest.war of the IBM_BPM_Teamworks application was changed. Example: AdminTask.addBPMSystem('[-bpmCellName remoteCell -bpmClusterName RemoteCell.AppCluster -bpmSystemType BPEL -bpmHostName remoteHostname -bpmPort 80 -bpmTransportType https]') --------------------------------------------------------------------------------------------------- removeBPMSystem Description: Removes an BPM (BPEL or BPD engine) system from the local BPM federated API. Target object: None Arguments: *bpmCellName - The name of the cell where the BPM system is configured. bpmNodeName - The name of the node where the BPM system is configured. If this parameter is specified, then the bpmServerName parameter must be specified. Do not specify this parameter if the bpmClusterName parameter is specified. bpmServerName - The name of the server where the BPM system is configured. If this parameter is specified, then the bpmNodeName parameter must also be specified. Do not specify this parameter if the bpmClusterName parameter is specified. bpmClusterName - The name of the cluster where the BPM system is configured. Do not specify this parameter if the bpmNodeName or bpmServerName parametesr are specified. *bpmSystemType - The type of the BPM system. Either specify BPEL or BPD. Example: AdminTask.removePMSystem('[-bpmCellName remoteCell -bpmClusterName RemoteCell.AppCluster -bpmSystemType BPEL]') --------------------------------------------------------------------------------------------------- Directions to apply fix: 1) Shutdown WebSphere. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix. 2) Extract the .zip file to a directory. For example, extract to C:\temp. 3) Add the fix pack repository location in IBM Installation Manager: a. Start IBM Installation Manager. b. In Installation Manager, click File > Preferences > Repositories. c. Click Add Repository. d. Browse to or enter the file path to the repository.config file. The repository.config file is located in the directory where you extracted the compressed files. For example, enter C:\temp\repository.config, and then click OK. 4) On the main page of the Installation Manager, click Update. 5) Restart WebSphere Directions to remove fix: NOTE: FIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED. DO NOT REMOVE A FIX UNLESS ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED. YOU MAY REAPPLY ANY REMOVED FIX. Example: If your system has fix1, fix2, and fix3 applied in that order and fix2 is to be removed, fix3 must be removed first, then fix2 may be removed 1) Shutdown WebSphere. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix. 2) Start IBM Installation Manager. 3) On the main page of the Installation Manager, click Unistall. 4) Select the package to uninstall and follow the prompts on screen. 5) Restart WebSphere Directions to re-apply fix: 1) Shutdown WebSphere. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix. 2) Extract the .zip file to a directory. For example, extract to C:\temp. 3) Add the fix pack repository location in IBM Installation Manager: a. Start IBM Installation Manager. b. In Installation Manager, click File > Preferences > Repositories. c. Click Add Repository. d. Browse to or enter the file path to the repository.config file. The repository.config file is located in the directory where you extracted the compressed files. For example, enter C:\temp\repository.config, and then click OK. 4) On the main page of the Installation Manager, click Update. 5) Restart WebSphere. Additional Information: