WebLogic Server file review rules

Under the BEA Beehive to Apache Beehive category, the WebLogic Server rule set has rules to identify BEA Beehive control files.

Rule Name	Rule Description	Automated Fix
Do not use BEA Global.app files	This rule detects BEA Beehive Global.app application control files.	No
Do not use BEA Java Web Services (JWS) files	This rule detects BEA Beehive JWS files.	No
Do not use Java Control Extension (JCX) files	This rule detects BEA Beehive JCX files.	No
Do not use Java Page Flow (JPF) files	This rule detects BEA Beehive JPF files.	No

Under the MANIFEST.MF Review category, the WebLogic Server rule set has a rule to verify that the MANIFEST.MF class path is set up correctly.

Rule Name	Rule Description	Automated Fix
Use MANIFEST.MF for application class path	This rule detects any classes or libraries contained within an APP-INF directory of an EAR file. The quick fix adds an entry to the class path of each affected web module by updating the class path entry of the MANIFEST.MF file of the module.	No

Rule Name

Rule Description

Automated Fix

Use MANIFEST.MF for application class path

This rule detects any classes or libraries contained within an APP-INF directory of an EAR file.

The quick fix adds an entry to the class path of each affected web module by updating the class path entry of the MANIFEST.MF file of the module.

Under the Properties File Review category, the WebLogic Server rule set has a rule to analyze properties files.

Rule Name	Rule Description	Automated Fix
Do not use WebLogic-specific JNDI name values or the t3 protocol	This rule detects non-portable WebLogic Server JNDI lookup values or URLs with the t3 or t3s protocol in properties files.	No
WebLogic packages and classes are not supported in WebSphere	This rule detects the use of WebLogic string literals in Java code and property files. All string literals that include "weblogic" are flagged. Use packages, classes, and properties provided by Java EE or WebSphere Application Server instead.	No