IBM Support

PK77768: PROVIDER ENDPOINTS PROPERTY ON ACTIVATION SPECIFICATION NOT AVAILABLE WITH V6.0/6.1

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • In WAS v7.0 Provider endpoints property is available on
    activation spec.This property allows an MDB to connect to
    a messaging engine in a remote cell.This feature is not
    available in WAS v6.0/6.1.
    

Local fix

  • fix required
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of the default messaging provider     *
    *                  for WebSphere Application Server V6.0 and   *
    *                  V6.1, with message driven beans connecting  *
    *                  to a service integration bus via an         *
    *                  activation specification.                   *
    ****************************************************************
    * PROBLEM DESCRIPTION: WebSphere Application Server V6.0 and   *
    *                      V6.1 activation specifications for      *
    *                      the default messaging provider do not   *
    *                      have a configuration option to specify  *
    *                      provider endpoints.                     *
    *                                                              *
    *                      These are required if an MDB is         *
    *                      connects to a bus located in another    *
    *                      Cell. Provider endpoints need to        *
    *                      be defined on the activation            *
    *                      specification to locate a bootstrap     *
    *                      server (with the SIB Service running)   *
    *                      in the other cell, so that a suitable   *
    *                      messaging engine can be located.        *
    ****************************************************************
    * RECOMMENDATION:  Apply the fix for this APAR, or create a    *
    *                  core group bridge between the two cells     *
    *                  and enable the SIB Service on the server    *
    *                  hosting the MDB.                            *
    ****************************************************************
    Without the ability to specify provider endpoints on a
    activation specification it wasn't possible to connect a MDB
    deployed in one cell with a messaging engine running in
    another, unless the two cells were bridged and the SIB Service
    was active on the server hosting the MDB.
    
    If a bridge has been configured, then the SIB Service of
    servers in the local cell will receive knowledge of the
    messaging engines running in the bus in the remote cell.
    

Problem conclusion

  • The fix for this APAR allows provider endpoints to be specified
    on a default messaging provider activation specification.
    
    A new profile must be created after applying this APAR, before
    provider endpoints can be specified.
    
    Once a new profile has been created with this APAR applied,
    a new entry in the "J2C activation specification custom
    properties" will be available for all activation specifications
    created within that profile.
    
    To view and edit these in the administration console:
    - Select "Resources"
    - Select "Resource Adapters"
    - Choose the scope at which the activation specification
    was defined.
    - Select "SIB JMS Resource Adapter"
    - Select "J2C Activation specifications"
    - Choose the activation specification from the list
    - Select "J2C activation specification custom properties"
    
    The new property is as follows:
    "providerEndpoints"
    
    The fix for this APAR is currently targeted for inclusion in
    fixpack 6.0.2.35 and 6.1.0.25.  Please refer to the Recommended
    Updates page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK77768

  • Reported component name

    PLAT MSG COM

  • Reported component ID

    620600101

  • Reported release

    200

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-12-19

  • Closed date

    2009-02-24

  • Last modified date

    2009-05-12

  • 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

    PLAT MSG COM

  • Fixed component ID

    620600101

Applicable component levels

  • R200 PSY

       UP



Document information

More support for: WebSphere Application Server
Service Integration Technology

Software version: 6.1

Reference #: PK77768

Modified date: 12 May 2009


Translate this page: