PM75926: ALLOW EJB 3.0 JNDIS AND JNDI NAMES FOR EJB REFERENCES TO BE SET THROUGH A CUSTOM DEFAULT BINDINGS STRATEGY FILE

Fixes are available

APAR status

Closed as program error.

Error description

When a custom default bindings strategy file is used during
application deployment, allows EJB 3.0 JNDIs and JNDIs for ejb
reference from an EE5 module to be set.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server.                                     *
****************************************************************
* PROBLEM DESCRIPTION: Any JNDI values specified in the        *
*                      default bindings custom strategy file   *
*                      for EJB 3.x beans and EJB 3.x           *
*                      references are not honored during       *
*                      application deployment.                 *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Any JNDI values specified in the default bindings custom
strategy file for EJB 3.x beans and EJB 3.x references are not
honored during application deployment.

Problem conclusion

The code has been modified to allow you to set the custom
property
com.ibm.websphere.management.application.client.customStrategy.a
llowEJB3xDefaultBindings on the JVM to true/false to override
the default settings.

1) To enable the System Property in the Administrative Console:

a) In a Network Deployment environment, the system property
needs to be set on the DMGR. System administration -->
Deployment manager --> Java and Process Management --> Process
Definition --> Java Virtual Machine --> Custom Properties
Name:
com.ibm.websphere.management.application.client.customStrategy.a
llowEJB3xDefaultBindings Value : true/false

b) In a Base environment, the system property is set on
server1. Servers --> Application Servers --> server1 --> Java
and Process Management --> Process Definition --> Java Virtual
Machine --> Custom Properties Name :
com.ibm.websphere.management.application.client.customStrategy.a
llowEJB3xDefaultBindings Value : true/false

2) To enable the System Property in wsadmin it must be set as
an option when starting wsadmin or in the wsadmin.properties
file.

a) To set the System Property when starting wsadmin do the
following: wsadmin -javaoption
"-Dcom.ibm.websphere.management.application.client.customStrateg
y.allowEJB3xDefaultBindings="

b) To set the System Property in the wsadmin.properties file,
found at /profiles//properties, add the following line (value
can be false or true):
com.ibm.websphere.management.application.client.customStrategy.a
llowEJB3xDefaultBindings=false

The fix for this APAR is currently targeted for inclusion in
fixpacks 7.0.0.29, 8.0.0.6 and 8.5.0.2.  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
PM75926
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-10-26
Closed date
2012-12-13
Last modified date
2012-12-13

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
WEBS APP SERV N
Fixed component ID
5724H8800

Applicable component levels

R700 PSY
UP
R800 PSY
UP
R850 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 October 2021

Tips

PM75926: ALLOW EJB 3.0 JNDIS AND JNDI NAMES FOR EJB REFERENCES TO BE SET THROUGH A CUSTOM DEFAULT BINDINGS STRATEGY FILE

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R700 PSY

R800 PSY

R850 PSY

Document Information

Share your feedback

Need support?