PK07276: USING A PRE-DEFINED BINDINGS FILE TO SPECIFY EJB REFERENCE BINDINGS (EJB-REF-BINDING) DURING DEPLOYMENT HAS NO EFFECT.

 A fix is available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
Giving pre-defined EJB reference bindings during deployment
(on the 'Preparing for application installation' step) has
no effect on the final deployment bindings.  This is a retrofit
of v6 botp defect 213792.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V5.0 for z/OS                                *
****************************************************************
* PROBLEM DESCRIPTION: During application installation, it is  *
*                      not possible to use a custom strategy   *
*                      (or pre-defined bindings file) to       *
*                      alter the jndi-name bound to an ejb     *
*                      reference.                              *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
WebSphere can generate default bindings and mappings during
application installation and also provides the ability to
extend the default bindings so you need only customize those
areas where the default strategy is insufficient.  However,
it is not possible to use such custom strategies to override
the default jndi-name bindings for ejb references.  Attempts
to do so will generate a series of messages similar to the
following in the DeploymentManager/AppServer servant joblog:
/WebSphere/V5R0M0/DeploymentManager/wstemp/-1953207853/upload/
   my.bindings.xml
 Error  :7:25: Element type "ejb-ref-bindings" must be declared.
 Error  :8:26: Element type "ejb-ref-binding" must be declared.
 Error  :9:25: Element type "ejb-ref-name" must be declared.
 Error  :13:23: The content of element type "ejb-jar-binding"
   must match "(jar-name,data-source?,connection-factory?,
   ejb-bindings?,resource-ref-bindings?,
   resource-env-ref-bindings?)".
Problem conclusion
Support was added for ejb reference bindings in custom
strategies.  An updated version of the properties/dfltbndngs.dtd
file is shipped with this fix and includes xml code examples of
how to exploit this capability in pre-defined bindings files.

APAR PK07276 is associated with SERVICE LEVEL W502031 of
WebSphere Application Server V5.0 for z/OS.
Temporary fix Comments
APAR information
APAR number PK07276
Reported component name WEBSPHERE FOR Z
Reported component ID 5655I3500
Reported release 500
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2005-06-14
Closed date 2005-06-20
Last modified date 2005-07-01

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

APAR is sysrouted TO one or more of the following:

Modules/Macros
BBOUBINF          

Publications Referenced

Fix information
Fixed component name WEBSPHERE FOR Z
Fixed component ID 5655I3500

Applicable component levels
R500 PSY UK04679    UP05/06/28 P F506

  Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.


Document Information


Current web document: swg1PK07276.html
Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS
Operating system(s):
Software version: 500
Software edition:
Reference #: PK07276
IBM Group: Software Group
Modified date: Jul 1, 2005