PQ49459: WASSECK - XMLCONFIG IMPORT ADDING CLONED EJBS DOESN'T DIFFERENTIATE BETWEEN EJBS ON DIFFERENT APP SERVERS,CLONES,NODES


APAR

APAR status
Closed as program error.

Error description
Environment:
WebSphere Application Server (WAS) 3.0.2.x and 3.5.x
.
Description:Environment:WebSphere Application Server (WAS) 3.0.2.x and 3.5.x.
The WAS XMLConfig tag <ejb name> which is a child of<enterprise-application> and <ejb-security> doesn't describe the full location (node, application server/clone) of the EJB. As a result, the following things happen when multiple application servers/clones have EJBs with the same name:Description: The WAS XMLConfig tag, which is a child of, and, doesn't describe thefull location (node, application server/clone) of the EJB. As aresult, the following things happen when multiple application
. 1. There is no way to specify which EJB to add to or remove from an enterprise application or to secure or unsecure a specific EJB using XMLConfig import 2. There is no way to add or remove all cloned EJBs to/from an enterprise application or secure/unsecure all the EJBs on all clones using XMLConfig import . This needs to be resolved as soon as possible because we have customers who have a huge number of EJBs and using the admin console to secure them and unsecure them is not a viable option.
servers/clones have EJBs with the same name:.1. There is no way to specify which EJB to add to or remove froman enterprise application or to secure or unsecure a specificEJB using XMLConfig import2. There is no way to add or remove all cloned EJBs to/from anenterprise application or secure/unsecure all the EJBs on allclones using XMLConfig import.This needs to be resolved as soon as possible because we havecustomers who have a huge number of EJBs and using the adminconsole to secure them and unsecure them is not a viable option.
Local fix
No viable workaround for customer with a large number of EJBs
Problem summary
Throught the admin console, the user may specify
security on a specific EJB clone.  When using
the task menu in 3.5.4, select Configure Resource
Security, then when hovering over the clone,
you will see the "ejb full name" and be able to
select the correct clone.
The xmlconfig does not allow you to do this
as indicated in the defect.  This is the current
xmlconfig syntax for EJB security:<ejb-security>
    <ejb name="EJBName"/></ejb-security>
To specify which particular clone, I'm utilizing the dtd
flag added as part of defect 89591 (which is scheduled to
make it into 3.5.5):xmlconfig syntax for EJB security:To specify which particular clone, I'm utilizing the dtdflag added as part of defect 89591 (which is scheduled to
<ejb-security> <ejb name="EJBName"> <ejb-full-name> NodeName/ServerName/ContainerName/EJBName</ejb-full-name> </ejb></ejb-security> If one does not use the ejb-full-name.. the security will be set for the first clone, as it did before. 89591 fixes the issue of adding/removing a specific ejb from the enterprise app utilizing the <ejb-full-name> tag for <ejb>. As far as adding/removing/securing bulk ejbs, this is not supported in the console and is not a defect but a functionality request.
make it into 3.5.5):NodeName/ServerName/ContainerName/EJBNameIf one does not use the ejb-full-name.. the security will beset for the first clone, as it did before.89591 fixes the issue of adding/removing a specific, ejb from the enterprise app utilizing the, tag for.As far as adding/removing/securing bulk ejbs, this is notsupported in the console and is not a defect but afunctionality request.
Problem conclusion
See above summary
Temporary fix
ZE FIX ERROR PQ52036 01/09/13
Comments
APAR information
APAR numberPQ49459
Reported component nameWAS STANDARD SU
Reported component ID5648C8302
Reported release350
StatusCLOSED PER
PENoPE
HIPERNoHIPER
Submitted date2001-06-07
Closed date2001-06-29
Last modified date2001-09-14

APAR is sysrouted FROM one or more of the following:

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


Modules/Macros

Fix information
Fixed component nameWAS STANDARD SU
Fixed component ID5648C8302
APAR is sysrouted TO one or more of the following:Modules/Macros

Applicable component levels
R350 PSYUP











Document Information

Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, General
Software version: 350
Reference #: PQ49459
IBM Group: Software Group
Modified date: 2001-09-14