wls deployment

Overview

This resource allows you to manage a cluster in an WebLogic domain.

Here is an example on how you should use this:

# 'jersey-bundle' will use default as wls_setting identifier
wls_deployment{'jersey-bundle':
  ensure            => 'present',
  deploymenttype    => 'Library',
  stagingmode       => 'nostage',
  remote            => "1",
  upload            => "1",
  target            => ['AdminServer', 'WebCluster'],
  targettype        => ['Server', 'Cluster'],
  versionidentifier => '1.18@1.18.0.0',
}

In this example you are managing a deployment in the default domain. When you want to manage a deployment in a specific domain, you can use:

wls_deployment{'my_domain/webapp':
  ensure            => 'present',
  deploymenttype    => 'AppDeployment',
  stagingmode       => 'nostage',
  remote            => "1",
  upload            => "1",
  target            => ['WebCluster'],
  targettype        => ['Cluster'],
  versionidentifier => '1.1@1.1.0.0',
  require           => Wls_deployment['jersey-bundle']
}

Check the WebLogic documentation for more information about application deployment.

Attributes

deployment_name

The deployment name

Back to overview of wls_deployment

deployment_order

An integer value that indicates when this unit is deployed, relative to other deployable units on a server, during startup. Units with lower values are deployed before those with higher values.

Back to overview of wls_deployment

deploymenttype

The deployment type

Valid values are Library, AppDeployment.

Back to overview of wls_deployment

disable_autorequire

Puppet supports automatic ordering of resources by autorequire. Sometimes, however, this causes issues. Setting this parameter to true, disables autorequiring for this specific resource.

USE WITH CAUTION!!

Here is an example on hopw to use this:

...{'domain_name/...':
  disableautorequire => true,
  ...
}

Back to overview of wls_deployment

disable_corrective_change

Disable the modification of a resource when Puppet® decides it is a corrective change.

(requires easy_type V2.11.0 or higher)

When using a Puppet® Server, Puppet® knows about adaptive and corrective changes. A corrective change is when Puppet® notices that the resource has changed, but the catalog has not changed. This can occur for example, when a user, by accident or willingly, changed something on the system that Puppet® is managing. The normal Puppet® process then repairs this and puts the resource back in the state as defined in the catalog. This process is precisely what you want most of the time, but not always. This can sometimes also occur when a hardware or network error occurs. Then Puppet® cannot correctly determine the current state of the system and thinks the resource is changed, while in fact, it is not. Letting Puppet recreate remove or change the resource in these cases, is NOT wat you want.

Using the disable_corrective_change parameter, you can disable corrective changes on the current resource.

Here is an example of this:

crucial_resource {'be_carefull':
  ...
  disable_corrective_change => true,
  ...
}

When a corrective ensure does happen on the resource Puppet® will not modify the resource and signal an error:

    Error: Corrective change present requested by catalog, but disabled by parameter disable_corrective_change
    Error: /Stage[main]/Main/Crucial_resource[be_carefull]/parameter: change from '10' to '20' failed: Corrective change present requested by catalog, but disabled by parameter disable_corrective_change. (corrective)

Back to overview of wls_deployment

disable_corrective_ensure

Disable the creation or removal of a resource when Puppet® decides is a corrective change.

(requires easy_type V2.11.0 or higher)

When using a Puppet® Server, Puppet® knows about adaptive and corrective changes. A corrective change is when Puppet® notices that the resource has changed, but the catalog has not changed. This can occur for example, when a user, by accident or willingly, changed something on the system that Puppet® is managing. The normal Puppet® process then repairs this and puts the resource back in the state as defined in the catalog. This process is precisely what you want most of the time, but not always. This can sometimes also occur when a hardware or network error occurs. Then Puppet® cannot correctly determine the current state of the system and thinks the resource is changed, while in fact, it is not. Letting Puppet recreate remove or change the resource in these cases, is NOT wat you want.

Using the disable_corrective_ensure parameter, you can disable corrective ensure present or ensure absent actions on the current resource.

Here is an example of this:

crucial_resource {'be_carefull':
  ensure                    => 'present',
  ...
  disable_corrective_ensure => true,
  ...
}

When a corrective ensure does happen on the resource Puppet® will not create or remove the resource and signal an error:

    Error: Corrective ensure present requested by catalog, but disabled by parameter disable_corrective_ensure.
    Error: /Stage[main]/Main/Crucial_resource[be_carefull]/ensure: change from 'absent' to 'present' failed: Corrective ensure present requested by catalog, but disabled by parameter disable_corrective_ensure. (corrective)

Back to overview of wls_deployment

domain

With this parameter, you identify the domain, where your objects is in.

The domain name is part of the full qualified name of any WebLogic object on a system. Let’s say we want to describe a WebLogic server. The full qualified name is:

wls_server{'domain_name/server_name':
  ensure => present,
  ...
}

When you don’t specify a domain name, Puppet® will use default as domain name. For every domain you want to manage, you’ll have to put a wls_settings in your manifest.

Back to overview of wls_deployment

ensure

The basic property that the resource should be in.

Valid values are present, absent.

Back to overview of wls_deployment

localpath

The local path of the artifact

Back to overview of wls_deployment

name

The name.

Back to overview of wls_deployment

planpath

The path of the deploymentplan

Back to overview of wls_deployment

provider

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

simple

Manage a deployment in an WebLogic domain via regular WLST

Back to overview of wls_deployment

refreshonly

The deployment should only be deployed or redeployed as a refresh mechanism for when a dependent object is changed.

right now refreshonly only works on the versionidentifier property of a deployment.

It only makes sense to use this option when this command depends on some other object; it is useful for triggering an action:

Note that only subscribe and notify can trigger actions, not require, so it only makes sense to use refreshonly with subscribe or notify.

Valid values are true, false.

Back to overview of wls_deployment

remote

remote option for deployment.

Valid values are absent, 1, 0.

Back to overview of wls_deployment

stagingmode

The staging type

Valid values are callback-polling, nostage, stage, external_stage.

Back to overview of wls_deployment

target

The target name

Back to overview of wls_deployment

targettype

The type of the target

Back to overview of wls_deployment

timeout

Timeout for deploying and undeploying a deployment

With this parameter, you can specify the length of the timeout. The value is specified in seconds. In this example, the timeout is set to 600 seconds.

wls_deployment{'my_deployment':
  ...
  timeout => 600,
}

The default value for timeout is 120 seconds.

Back to overview of wls_deployment

upload

Upload option for deployment.

Valid values are absent, 1, 0.

Back to overview of wls_deployment

versionidentifier

The version identifier.

Back to overview of wls_deployment