PQ54810: SETTING A JNDI NAME IN A WSCP (TCL) SCRIPT DOES NOT WORK FOR APPSERVER (WAS) 4.0.

APAR status
Closed as program error.

Error description
It appears that to set the jndi name
in the tcl script (with wscp) there needs to be a
jndi name already configured.  Using AAT it was
possible to set a jndi name on his jar file and then
install with the jndi name from the tcl script.
There is a bug the way wscp handles the jndi name.
Local fix
Using AAT, one can set the jndi name on the jar file
before installing with the jndi name from the tcl script.
Problem summary
****************************************************************
* USERS AFFECTED: All WebSphere Application Server AE 4.0      *
*                 users of wscp's EnterpriseApp install        *
*                 function.                                    *
****************************************************************
* PROBLEM DESCRIPTION: Wscp EnterpriseApp install function's   *
*                      -ejbnames option does not work if       *
*                      there is no existing mapping.           *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The wscp EnterpriseApp install command has a -ejbnames option
that can be used to set up a mapping between EJBs and JNDI
names.  This does not not work if the binding information for
a given EJB has no existing JNDI name mapping.  In this case,
wscp silently fails to create the mapping.  This lack of
binding information is visible from the Admin Console -- there
is an EJB tab for the property sheet for EJB Modules.  Under
this tab, the "JNDI Name" will be blank in the case of this
failure.
Problem conclusion
WSCP code is fixed so that EJB-to-JNDIName mappings are created
even in the case where no such mapping exists in the bindings.
Temporary fix
I built an e-fix for this apar and placed it on wasdoc0/apars
in directory pq54810.
Comments
APAR information
APAR number PQ54810
Reported component name WEBSPHERE AES N
Reported component ID 5630A2301
Reported release 400
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2001-11-14
Closed date 2001-12-03
Last modified date 2001-12-04

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
WSCP          

Fix information
Fixed component name WEBSPHERE AES N
Fixed component ID 5630A2301

Applicable component levels
R400 PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ54810
IBM Group: Software Group
Modified date: Dec 4, 2001