VRTSwls.4.0.00.2-P2 for Solaris
================================

CONTENTS
--------
1.  OVERVIEW
   - Symptom of the Problem
   - Resolution
2. APPLYING THE PATCH
3. DISCLAIMER

OVERVIEW
========

The VRTSwls.4.0.00.2-P2 is a bundled patch which contains 4 fixes reported in 
the following 4 ETRACK incidents.

 ==============================================================================
| 371633 | Weblogic agent does not support user's default shell as csh |
| 371634 | Parsing of ps command output fails in GetLongProcessListHash|
| 379323 | While onlining SecondLevelMonitor uses negative value for Timeout.
| 379324 | SecondLEvelMonitor fails for User with default shell - csh.
 ==============================================================================

Symptoms of the Problems
=========================
1. Incident 371633
==================

Problem
--------
Weblogic agent does not support user's default shell as csh.

When the WebLogic Agent issues the start command, it issues it under a
particular USER context by doing a "su USER ". This operation assumes that the
user shell is a sh derived shell ( sh, ksh, bash etc). Hence it does the 
redirection of output and the execution of the command in the background 
based on sh syntax.

Resolution
-----------
Added support for csh. Instead of setting seperate redirection and background 
for the different shells ( sh derived , csh etc ) , now their is a generic 
implementation of the redirection and command execution in the background.

2. Incident 371634
==================
Parsing of ps command output fails in GetLongProcessListHash.

Problem
-------
The Agent uses a framework routine, GetLongProcessListHash(), to parse the 
output of the ps command ( /usr/ucb/ps ) and then splits the fields for UID, 
PID, PPID etc fields. The framework routine assumes the first field  as numeric
and hence the routine fails to split the output correctly.

Resolution
----------
Added the check for alphanumeric characters in the routine by changing the
first search pattern from [0-9] to [0-9a-z] .

3. Incident 379323 
==================

Problem
--------
While onlining SecondLevelMonitor uses negative value for Timeout.

Resolution
-----------
Fixed the calculation of the Timeout value for SecondLevelMonitor.

4. Incident 379324 
==================
SecondLEvelMonitor fails for User with default shell - csh.

When the WebLogic Agent invokes SecondLevelMonitor , it issues it under a 
particular USER context by doing a "su USER ". This operation assumes that the
user shell is a sh derived shell ( sh, ksh, bash etc). Hence it does the 
execution of the command based on sh syntax. 

Resolution
-----------
Added support for csh. 


Applying patch VRTSwls.4.0.00.2-P2 on Solaris
===================================================

The patch is provided as a compressed tar file. This tar file contains 2 perl 
modules

- VProProc.pm
- VProWeblogic.pm


To install the patch follow the steps below

1) Offline the Weblogic resources on all the nodes.

# hares -offline <res-name> -sys <sysname>

2) Stop the Weblogic Agent on all the nodes

# haagent -stop VProWebLogic -sys <sysname>

3) Save the original perl modules as follows on all the nodes

# cd /opt/VRTSvcs/lib/perl5/.VCSagntfw/lib/
# cp -pr VProProc.pm  VProProc.pm.pre230-071-782
# cp -pr VProWebLogic.pm VProWebLogic.pm.pre280-432-101

4) Change directory to the location where the file VRTSwls.4.0.00.2-P2.sol.CD.tar.Z was extracted.

5) Copy the perl module from the working directory to the right location on 
both the nodes.

# cp VProProc.pm   /opt/VRTSvcs/lib/perl5/.VCSagntfw/lib/.
# cp VProWebLogic.pm /opt/VRTSvcs/lib/perl5/.VCSagntfw/lib/.

6) Start the agent  and online the WebLogic resources

# haagent -start VProWebLogic -sys <sysname>
# hares -online <res-name> -sys <sysname>


DISCLAIMER
----------
This patch is a supported fix that has not been fully regression tested
and must be applied only to systems that are severely affected by the
problem.For other situations, we recommend that you wait for the next 
Maintenance Pack that will contain this fix.
Contact VERITAS Technical Support for more information.