Custom Properties for improving application startup in WebSphere Application Server

http://www-01.ibm.com/support/docview.wss?uid=swg21983564

Problem(Abstract)

In WebSphere Application Server traditional V9.0, Contexts and Dependency Injection (CDI) 1.2 is enabled by default. Enablement of CDI 1.2 might increase unnecessary performance overhead if the application does not use CDI.

Symptom

The application starts slowly.

Resolving the problem

Disable CDI processing steps for applications or archives that do not contain CDI content, and for which the steps are unnecessary. The following Java custom properties and manifest attributes are introduced to disable CDI processing steps:

Name: com.ibm.ws.cdi.enableImplicitBeanArchives
Allowed Values: true, false
Default Value: true
Description: By setting the com.ibm.ws.cdi.enableImplicitBeanArchives custom property to false, CDI-related annotation scanning steps are disabled for archives that do not contain a bean descriptor, for example, the beans.xml file.

Name: com.ibm.ws.cdi.enableCDI
Allowed Values: true, false
Default Value: true
Description: By setting the com.ibm.ws.cdi.enableCDI custom property to false, all CDI steps are disabled. Set the value to false if no CDI is needed on the server level.

In addition to these Java custom properties that impact all applications that are deployed to the target server, the following properties can be set in the server-wide amm.filter.properties file and as manifest attributes of application archive files.

System Property Name: com.ibm.ws.cdi.enableImplicitBeanArchives
Property and Manifest Attribute Name: Enable-Implicit-Bean-Archive

System Property Name: com.ibm.ws.cdi.enableCDI
Property and Manifest Attribute Name: Enable-CDI

Note:

• The amm.filter.properties file is located at WAS_HOME/properties/amm.filter.properties.
• Manifest attributes are set as main manifest attributes in Java EE-related application archive files, such as EAR, WAR, RAR, and JAR files.
• The Enable-CDI property affects an entire application. Set this property on the Manifest.mf file of the application. Setting this property only for a module archive has no effect.

In this way, the property value from the least enclosing scope is used. An attribute value on a module manifest takes precedence over the attribute value on the application. The attribute value on the application takes precedence over a java custom property value. The java custom property value takes precedence over a property value set in the amm.filter.properties file.

For more information about similar properties, see Reducing annotation searches during application deployment in IBM Knowledge Center.

http://www-01.ibm.com/support/docview.wss?uid=swg21983564

PM85864: SYMBOLIC LINK UNDER INSTALLEDAPPS DIRECTORY DOES NOT GET RETAINED AFTER APPLICATION UNINSTALL AND RE-INSTALL

PM85864: SYMBOLIC LINK UNDER INSTALLEDAPPS DIRECTORY DOES NOT GET RETAINED AFTER APPLICATION UNINSTALL AND RE-INSTALL
http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg1PM85864

Any symbolic links that exist in the application installation directory will be deleted when the application is uninstalled or updated.

Problem conclusion

The code has been modified to allow you to set the custom property

com.ibm.websphere.management.application.sync.deleteSymbolicLinks 

on the JVM to false to override the default setting of true.

1) To enable the System Property in the administrative

console: a) In a Network Deployment edition, the system

property needs to be set on the nodeagent. System

administration --> Node agents --> nodeagent --> Java and

Process Management --> Process definition --> Java Virtual

Machine --> Custom properties Name:

com.ibm.websphere.management.application.sync.deleteSymbolicLinks 

Value: true/false

*** both node agent and application server must restart to take effect 

b) In a Base edition, the system property is set on the

server. Servers --> Application Servers --> server1 --> Java

and Process Management --> Process Definition --> Java Virtual

Machine --> Custom Properties Name:

com.ibm.websphere.management.application.sync.deleteSymbolicLinks 

Value: true/false

*** Restrictions: ***

Do not use symbolic links on Microsoft Windows operating systems as they are not supported.

The fix for this APAR is currently targeted for inclusion in

fix pack 8.0.0.7 and fix pack 8.5.5.1.