Overview

This resource allows you to manage opatch patches on a specific middleware home.

wls_opatch {‘/opt/oracle/middleware12c:16175470’: ensure => “present”, jdk_home_dir => “/usr/java/jdk1.7.0_45”, os_user => “oracle”, source => “/vagrant/p16175470_121200_Generic.zip”, }

Attributes

Attribute Name Short Description
ensure The basic property that the resource should be in.
jdk_home_dir The JDK home folder.
name The name.
oracle_product_home_dir The oracle product home folder.
orainst_dir The orainst folder.
os_user The weblogic operating system user.
patch_id The patchId of the OPatch.
provider resource.
source The source of the patch.
tmp_dir The tmp extract directory of the patch.

ensure

The basic property that the resource should be in.

Valid values are present, absent. Back to overview of wls_opatch

jdk_home_dir

The JDK home folder.

Back to overview of wls_opatch

name

The name.

Back to overview of wls_opatch

oracle_product_home_dir

The oracle product home folder.

Back to overview of wls_opatch

orainst_dir

The orainst folder.

Back to overview of wls_opatch

os_user

The weblogic operating system user.

Back to overview of wls_opatch

patch_id

The patchId of the OPatch.

Back to overview of wls_opatch

provider

The specific backend to use for this wls_opatch resource. You will seldom need to specify this — Puppet will usually discover the appropriate provider for your platform.Available providers are:

prefetching
Apply Oracle OPatches

Back to overview of wls_opatch

source

The source of the patch. Can be either an extracted folder or the raw zip file.

Back to overview of wls_opatch

tmp_dir

The tmp extract directory of the patch.

Back to overview of wls_opatch