Puppet Class: wls_profile::basic_domain

Inherits:
wls_profile
Defined in:
manifests/basic_domain.pp

Summary

Overview

wls_profile::basic_domain

This is a highly customizable Puppet profile class to define a basic WebLogic (empty) domain on your system. At its core just adding:“‘contain wls_profile::basic_domain“`Is enough to get an empty WebLogic domain running on your system. But sometimes you have specific uses cases that are not handled well by the standard classes. This profile class allows you to add your own code to the execution.## StagesDefining and starting an empty basic WebLogic domain on you system goes through several stages(These are not puppet stages):- [`weblogic`](./weblogic.html) Install and patch the WebLogic software- [`wls_domain`](./wls_domain.html) Create an empty WebLogic domain- [`wls_startup`](./wls_startup.html) Make sure the domain restarts after a system reboot.All these stages have a default implementation. This implementation is suitable to get off to an easy start. These classed all have parameters you can customize through hiera values. The defaults are specified in the module’s ‘data/default.yaml` file. ## before classesBut sometimes this is not enough, and you would like to add some extra definitions, you can, for example, add a Puppet class to be executed after the `weblogic` stage is done and before the `wls_domain` is done. You can do this by adding the next line to your yaml data:“`yamlwls_profile::basic_domain::before_wls_domain: my_profile::my_extra_class“`## after classesYou can do the same when you want to add code after one of the stage classes:“`yamlwls_profile::basic_domain::after_wls_domain: my_profile::my_extra_class“`## SkippingSometimes organizations use different modules and mechanisms to implement a feature, and you want to skip the class:“`yamlwls_profile::basic_domain::wls_startup: skip“`## ReplacingOr provide your own implementation:“`yamlwls_profile::basic_domain::wls_domain: my_profile::my_own_implementation“`This mechanism can be used for all named stages and makes it easy to move from an easy setup with a running standard WebLogic installation to a fully customized setup using a lot of your own classes plugged in.Look at the description of the stages and their properties.

See the file “LICENSE” for the full license governing this code.

Parameters:

  • weblogic (Optional[String]) (defaults to: undef) —

    Use this value if you want to skip or use your own class for stage ‘weblogic`. ## Use your own class You can use hiera to set this value. Here is an example: “`yaml wls_profile::basic_domain::weblogic: my_module::my_class “` ## Skip You can use hiera to set this value. Here is an example: “`yaml wls_profile::basic_domain::weblogic: skip “`

  • wls_domain (Optional[String]) (defaults to: undef) —

    Use this value if you want to skip or use your own class for stage ‘wls_domain`. ## Use your own class You can use hiera to set this value. Here is an example: “`yaml wls_profile::basic_domain::wls_domain: my_module::my_class “` ## Skip You can use hiera to set this value. Here is an example: “`yaml wls_profile::basic_domain::wls_domain: skip “`

  • wls_startup (Optional[String]) (defaults to: undef) —

    Use this value if you want to skip or use your own class for stage ‘wls_startup`. ## Use your own class You can use hiera to set this value. Here is an example: “`yaml wls_profile::basic_domain::wls_startup: my_module::my_class “` ## Skip You can use hiera to set this value. Here is an example: “`yaml wls_profile::basic_domain::wls_startup: skip “`

  • before_weblogic (Optional[String]) (defaults to: undef) —

    The name of the class you want to execute directly before the ‘weblogic` class. You can use hiera to set this value. Here is an example: “`yaml wls_profile::basic_domain::before_weblogic: my_module::my_class “`

  • before_wls_domain (Optional[String]) (defaults to: undef) —

    The name of the class you want to execute directly before the ‘wls_domain` class. You can use hiera to set this value. Here is an example: “`yaml wls_profile::basic_domain::before_wls_domain: my_module::my_class “`

  • before_wls_startup (Optional[String]) (defaults to: undef) —

    The name of the class you want to execute directly before the ‘wls_startup` class. You can use hiera to set this value. Here is an example: “`yaml wls_profile::basic_domain::before_wls_startup: my_module::my_class “`

  • after_weblogic (Optional[String]) (defaults to: undef) —

    The name of the class you want to execute directly after the ‘weblogic` class. You can use hiera to set this value. Here is an example: “`yaml wls_profile::basic_domain::after_weblogic: my_module::my_class “`

  • after_wls_domain (Optional[String]) (defaults to: undef) —

    The name of the class you want to execute directly after the ‘wls_domain` class. You can use hiera to set this value. Here is an example: “`yaml wls_profile::basic_domain::after_wls_domain: my_module::my_class “`

  • after_wls_startup (Optional[String]) (defaults to: undef) —

    The name of the class you want to execute directly after the ‘wls_startup` class. You can use hiera to set this value. Here is an example: “`yaml wls_profile::basic_domain::after_wls_startup: my_module::my_class “`



91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
 
# File 'manifests/basic_domain.pp', line 91

class wls_profile::basic_domain (
  Optional[String] $after_weblogic = undef,
  Optional[String] $after_wls_domain = undef,
  Optional[String] $after_wls_startup = undef,
  Optional[String] $before_weblogic = undef,
  Optional[String] $before_wls_domain = undef,
  Optional[String] $before_wls_startup = undef,
  Optional[String] $weblogic = undef,
  Optional[String] $wls_domain = undef,
  Optional[String] $wls_startup = undef
) inherits wls_profile {
  easy_type::ordered_steps([
      'wls_profile::weblogic',
      'wls_profile::basic_domain::wls_domain',
      'wls_profile::basic_domain::wls_startup',
  ])
}