DESCRIPTION
    This operation undeploys the following modified artifacts.

    1. Life cycle operations for JEE.

    This operation assumes that the patch is not installed in the
    Oracle Home. So, 'ph' option needs to be used to specify the patch
    location for undeployment.
    
    Please refer the following instructions for life cycle deployment.

    The -domain <DOMAIN_NAME> option has to be specified along with the
    -auto option for automated rollout to the Fusion Middleware domain.
    If only a single domain has been created out of the Oracle Home
    you can omit specifying the domain name. Only certain patches which
    have been certified by Oracle Product Support can be rolled out using
    this command.

    OPatch will pose questions to query for information necessary for 
    accessing the Fusion Middleware domain. They are Admin Server URL, 
    Admin Server User, Admin Server Password, Node Manager User and Node
    Manager password.


SYNTAX
opatch undeploy -ph <Patch Location>
                [-domain <DOMAIN_NAME>] [-auto ]
                [-invPtrLoc <Patch to oraInst.loc file ] 
                [-jre <JRE location> ]
                [-mw_home <Middlware Home> ]
                [-oh <Oracle Home Path> ] 
                [-report ]
                [-silent ] [-property_file <Path to custom property file>]            
 
OPTIONS

       -domain
              The name of the Fusion Middleware domain to which the
              artifacts affected by the patch will be redeployed.
 
       -auto
              This option is deprecated and is no-op for 'undeploy'.
 
       -jre
              This option tells OPatch to use JRE (java) from the
              specified location instead of the default location
              under Oracle Home.
 
       -property_file
              The user defined property file for OPatch to use. The
              path to the property file should be absolute. This
              property file takes precedence over the one that is
              supplied with OPatch.

              For life cycle deployment, the following keys are required
              with the necessary values.
 
              'AdminConfigFile' - Encrypted file for Admin Server user.
              'AdminKeyFile' - Encrypted file for Admin Server password.
              'AdminServerURL - Admin Server URL.
              'NodeManagerConfigFile' - Encrypted file for Node Manager user.
              'NodeManagerKeyFile' - Encrypted file for Node Manager password.

              For encryption files, Please check 'storeUserConfig' WLST
              command for details.

              The Key, value pair is of the format 'x=y' where 'x' is OPatch 
              understood key and each pair is separated by newline in the 
              property file. This option is typically used for silent
              operations.
 
       -invptrloc
              Used to locate the oraInst.loc file. Needed when the
              installation uses the -invPtrLoc flag. This should be
              the path to the oraInst.loc file.

       -mw_home
              The Middleware Home for the Fusion Middleware install. This
              takes precedence over the environment variable MW_HOME. 

       -oh
              The Oracle Home of the Fusion Middleware product which is to be
              used for the deploy operations. This takes precedence over the
              environment variable ORACLE_HOME.

       -report
              Just prints out the actions without execution.

       -silent
              Invoke the operation in silent mode. Path to custom property
              file may be provided which will have required inputs as
              name-value pairs. If required inputs are not found, OPatch willl
              error out with missing key values. Please check 'property_file'
              option for more details.

PARAMETERS
   The 'ph' option should be used and it mandates that patch is not installed in the
Oracle Home.
