PK67741: PROCESSEMBEDDCONFIG FLAG THAT WILL HELP DEPLOYING A ENHANCED EAR FILE.

Fixes are available

APAR status

Closed as program error.

Error description

A system property is provided to indicate ProcessEmbeddedConfig
to fix the deletion of installedApps folder problem while
deploying enhanced ear files.

ProcessEmbededConfig (true/false) flag would work for all the
EARs

--> if the flag is set to false then no matter what is passed
while installation all the EAR's are considered to be normal
EAR's during deployment

--> if the flag is set to true but the EAR is still a normal EAR
then flag wouldnt have any effect

--> if the flag is set to false but the EAR is still a normal
EAR the installation would be same as earlier

--> if the flag is set to false but EAR is EnhancedEAR then the
EAR would be treated as normal EAR and installed.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All IBM WebSphere Application Server        *
*                  version 6.0.2 and 6.1 users                 *
****************************************************************
* PROBLEM DESCRIPTION: The current behavior of Application     *
*                      Server with respect to Enhanced         *
*                      Enterprise Archive files (EARs)         *
*                      makes it difficult to use enhanced      *
*                      EARs exported from one environment      *
*                      to be imported into another             *
*                      environment. Importing such Enhanced    *
*                      Ear's causes the contents of the        *
*                      <PROFILE-HOME>/installedApps            *
*                      directory to be deleted. Also an        *
*                      option to control the processing of     *
*                      the Enhanced Ear's at the global level  *
*                      is missing.                             *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When using Enhanced EARs, if an EAR exported from one
environment is imported into a different environment then it
causes the entire contents of the <PROFILE-HOME>/installedApps
directory to be deleted.  This impacts your environment to a
large extent. Also you do not have the flexibility of
controlling the  processing of the Enhanced Ear's at a global
level. A flag at a global level would help manage the Enhanced
EAR's better.

Problem conclusion

The code has been modified to address this issue by providing
a system property which you have to set to enable and disable
processing of the embedded configuration of the enhanced EARs.

1) To enable the system property edit the wsadmin.properties
file .Please add the following line:

com.ibm.websphere.management.processEmbeddedConfigGlobal= false

2) From the administrative console:
a) For WebSphere Application Server Network Deployment
edition, it has to be set in deployment manager.
The property needs to be defined as a JVM property in
Deployment manager. In the administrative console, navigate to:
System administration --> Deployment manager --> Process
Definition --> Java Virtual Machine --> Custom Properties
Name : com.ibm.websphere.management.processEmbeddedConfigGlobal
Value : false

b) For WebSphere Application Server Base edition the
value has to be set for Server1 instead of deployment manager.

Once the property is set when you deploy an Enhanced EAR then
the embedded configuration of the Enhanced Ear is not
taken into account while deploying .

With the property set the following behavior will occur:

1) If the flag is set to false then unless explicitly set
while deploying via wsadmin (that is, unless deployed with an
option -processEmbededConfig) all the EAR's are considered to
be normal EAR's during deployment

2) if the flag is set to true but the EAR is still a normal
EAR then the flag will not have any effect

3) if the flag is set to false but the EAR is still a normal
EAR the installation would be the same as it was prior
to this fix.

The fix for this APAR is currently targeted for inclusion in
cumulative fix packs 6.0.2.31 and 6.1.0.21.
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
PK67741
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
60I
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-06-17
Closed date
2008-07-23
Last modified date
2008-07-23

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

R60A PSY
UP
R60H PSY
UP
R60I PSY
UP
R60P PSY
UP
R60S PSY
UP
R60W PSY
UP
R60Z PSY
UP
R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z 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":"6.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 December 2021

Tips

PK67741: PROCESSEMBEDDCONFIG FLAG THAT WILL HELP DEPLOYING A ENHANCED EAR 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

R60A PSY

R60H PSY

R60I PSY

R60P PSY

R60S PSY

R60W PSY

R60Z PSY

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

Document Information

Share your feedback

Need support?