JR44202: CROSS-CELL ENABLEMENT FOR FEDERATED REST API

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Cross-cell enablement for federated REST API
    Enable registering of REST endpoints from another cell to be
    used by the federated REST API.
    

Local fix

Problem summary

  • 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 443
    -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]')
    ----------------------------------------------------------------
    -----------------------------------
    

Problem conclusion

  • Problem fixed
    
    iFix available on top of V800 GA
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR44202

  • Reported component name

    BPM ADVANCED

  • Reported component ID

    5725C9400

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-09-26

  • Closed date

    2013-01-23

  • Last modified date

    2013-01-23

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    BPM ADVANCED

  • Fixed component ID

    5725C9400

Applicable component levels

  • R800 PSY

       UP



Rate this page:

(0 users)Average rating

Document information


More support for:

IBM Business Process Manager Advanced

Software version:

8.0

Reference #:

JR44202

Modified date:

2013-01-23

Translate my page

Machine Translation

Content navigation