Action: wve_common_configure_work_classes

Summary:
   Manages Work Classes inside IBM WebSphere Virtual Enterprise.
   
Required Data:
   This action is executed at the cell or node scope and uses configuration
   data in the workClass section of the workClasses.xml file at the cell or
   node scope.[1][2][3]
      
   Augment mode uses the configuration data in the 
   augment/workClasses.xml file.[1][2][3][4]
      
   The configuration data for Work Class is stored in the
   workClasses.xml file. For example configuration data, see the 
   workClass section in the samples:      
   RAFW_HOME/samples/xml/wve/61/workClasses.xml       
       
Supported Modes:
   import, execute, compare, augment
   
Supported Scopes:
   cell, node
   
Notes:
   [1] The workClasses_augment.xml and workClasses.xml are automation 
       framework for WebSphere files.  

   [2] Use the -c [CELL_NAME] or [-n NODE_NAME] option to run this action at
          the cell scope or node containing the on-demand router (ODR) server.
          
   [3] The scope is relative to the environment tree path: 
       RAFW_HOME/user/environments.
                                  
       cell path:    ENV_NAME/cells/CELL_NAME 
       cluster path: <cell path>/clusters/CLUSTER_NAME 
       node path:    <cell path>/nodes/NODE_NAME 
       server path:  <node path>/servers/SERVER_NAME           
 
   [4] When the mode is execute: The default work classes for systemApps is 
       modified to match what is contained in the workClasses.xml file. All 
       other WorkClasses are deleted and re-created based on what is specified 
       in the workClasses.xml file.
         
   [5] If the mode is augment: If a WorkClass entry is found with the same 
       'name' it is not updated, only WorkClass entries which are not found 
       by 'name' in the existing configuration are added.      
   
   [6] The augment mode directory defaults to "augment". To override the 
       augment mode directory supply: -opt augmentDir=<dir>

   [7] To promote entries in an augment file, specify the option 
       -opt augmentDir=<dir> and the rules_augment.xml in <dir>  
       will be used during promotion.
             
   [8] Refer to the Rational Automation Framework for WebSphere 
       Information Center for more information on promote mode filters.

Related actions:
    wve_common_configure_health_policies
    wve_common_configure_service_policies
    wve_common_configure_odr_routing_rules