Wednesday, December 28, 2011

Running wls_basic_audit.py - Weblogic BASIC license compliance

This script will help with verifying that WebLogic Server is being used in accordance with the WebLogic Server "Basic" license.

Reference: MOS note "WebLogic Server Basic License Audit Script [ID 885587.1]"

1. Set the environment from WL_SERVER_HOME/server/bin. Make sure to use below command to avoid "Exception in thread "main" java.lang.NoClassDefFoundError: weblogic/WLST"

Two dots are important in case the "." is not specified in PATH variable.

. ./setWLSEnv.sh

2. java weblogic.WLST wls_basic_audit.py
$ java weblogic.WLST wls_basic_audit.py

Initializing WebLogic Scripting Tool (WLST) ...

Welcome to WebLogic Server Administration Scripting Shell

Type help() for help on available commands

===============
WLS Basic Audit
===============
12/28/11 4:31 PM
Please enter your username :weblogic
Please enter your password :
Please enter your server URL [t3://localhost:7001] :
Connecting to t3://localhost:7001 with userid weblogic ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain 'INB'.

Warning: An insecure protocol was used to connect to the
server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.

===========
Domain Info
===========
Checking for administration port enabled: 
Checking for service migration: 
No errors detected
============
Cluster Info
============
Checking cluster type and overload actions: 
No errors detected
===========
Server Info
===========
Checking server mode and overload actions: 
No errors detected
======================
Singleton Service Info
======================
Checking for singleton services: 
No errors detected
======================
Service Migration Info
======================
Checking for service migration: 
No errors detected
========================
Global Work Manager Info
========================
Checking for global Work Managers: 
No errors detected
=============================
Application Work Manager Info
=============================
Checking for application-scoped Work Managers: 
No errors detected
===============
Deployment Info
===============
Checking for application versioning and ordering: 
License compliance failure:  Application reports version 11.1.1.2.0 uses version 11.1.1.2.0
License compliance failure:  Application formsapp version 11.1.1 uses version 11.1.1
Production redeployment strategy involves deploying a new version of an updated application alongside an older version of the same application. WebLogic Server automatically manages client connections so that only new client requests are directed to the new version. Clients already connected to the application during the redeployment continue to use the older version of the application until they complete their work, at which point WebLogic Server automatically retires the older application. This capability is supported by deploying the application in Administration mode, which makes it available only via a configured Administration channel.
In the license for WebLogic Server Basic, deploying any application that uses a version identifier is not permitted.
See the documentation:  http://download.oracle.com/docs/cd/E12839_01/web.1111/e13702/redeploy.htm#DEPGD281
2 error(s) detected
=========================
Application FastSwap Info
=========================
Checking whether FastSwap is enabled in an application: 
No errors detected
========
JMS Info
========
Checking for non-default Unit-of-Work Message Handling Policy: 
Checking for non-default Message Unit-of-Order: 
Checking for Message Store-and-Forward agents: 
No errors detected
=====================
Tuxedo Connector Info
=====================
Checking for WebLogic Tuxedo Connectors: 
No errors detected
=========
SNMP Info
=========
Checking for SNMP agents: 
No errors detected
=====================
Application Mode Info
=====================
Checking for application in Administration mode: 
Location changed to domainRuntime tree. This is a read-only tree with DomainMBean as the root.
For more help, use help(domainRuntime)

Location changed to serverRuntime tree. This is a read-only tree with ServerRuntimeMBean as the root.
For more help, use help(serverRuntime)

No errors detected
======================
Module Deployment Info
======================
Checking for deployment of standalone JMS, JDBC, or WLDF modules: 
No errors detected
===========================
HTTP Publish-Subscribe Info
===========================
Checking for HTTP Publish-Subscribe Server usage: 
No errors detected
==========================
Diagnostics Framework Info
==========================
Checking for WebLogic Diagnostics Framework usage: 
License compliance failure:  Diagnostics framework system resource is being used:  Module-FMWDFW
The WebLogic Diagnostic Framework (WLDF) is a monitoring and diagnostic framework that defines and implements a set of services that run within WebLogic Server processes and participate in the standard server life cycle. Using WLDF, you can create, collect, analyze, archive, and access diagnostic data generated by a running server and the applications deployed within its containers. This data provides insight into the run-time performance of servers and applications and enables you to isolate and diagnose faults when they occur.
In the license for WebLogic Server Basic, the use of WLDF is not permitted.
See the documentation:  http://download.oracle.com/docs/cd/E12839_01/web.1111/e13714/intro.htm#WLDFC108
1 error(s) detected
=======
Summary
=======
3 error(s) detected


Exiting WebLogic Scripting Tool.






I will post more posts on how to take care of these errors reported by compliance script.

No comments:

Post a Comment