wls jms bridge destination

Overview

This resource allows you to manage a jms bridge destination in an WebLogic domain.

Here is an example on how you should use this:

wls_jms_bridge_destination { 'myBridgeDest':
  ensure                => 'present',
  adapter               => 'eis.jms.WLSConnectionFactoryJNDINoTX',
  classpath             => 'myClasspath',
  connectionfactoryjndi => 'myCFJndi',
  connectionurl         => 'myConnUrl',
  destinationjndi       => 'myDestJndi',
  destinationtype       => 'Queue',
  initialcontextfactory => 'weblogic.jndi.WLInitialContextFactory',
}

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

wls_jms_bridge_destination { 'my_domain/myBridgeDest':
  ensure                => 'present',
  adapter               => 'eis.jms.WLSConnectionFactoryJNDINoTX',
  classpath             => 'myClasspath',
  connectionfactoryjndi => 'myCFJndi',
  connectionurl         => 'myConnUrl',
  destinationjndi       => 'myDestJndi',
  destinationtype       => 'Queue',
  initialcontextfactory => 'weblogic.jndi.WLInitialContextFactory',
}

Here you can find more information about JMS bridge desitinations.

Experience the Power of Puppet for WebLogic

If you want to play and experiment with Puppet and WebLogic, please take a look at our playgrounds. At our playgrounds, we provide you with a pre-installed environment, where you experiment fast and easy.

For WebLogic   here at our playground...

Attributes

adapter

The JNDI name of the adapter used to communicate with the specified destination.

Valid values are eis.jms.WLSConnectionFactoryJNDINoTX, eis.jms.WLSConnectionFactoryJNDIXA.

Back to overview of wls_jms_bridge_destination

adapter_jndi_name

The JNDI name of the adapter used to communicate with the specified destination. This name is specified in the adapter’s deployment descriptor file and is used by the WebLogic Server Connector container to bind the adapter in WebLogic Server JNDI.

An example on how to use this:

wls_jms_bridge_destination {a_wls_jms_bridge_destination :
   ...
   adapter_jndi_name => 'eis.jms.WLSConnectionFactoryJNDIXA'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_jms_bridge_destination:adapter_jndi_name']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_jms_bridge_destination

bridge_destination_name

The bridge destination name

Back to overview of wls_jms_bridge_destination

classpath

The classpath for this bridge destination.

Back to overview of wls_jms_bridge_destination

connection_factory_jndi_name

The connection factory’s JNDI name for this JMS bridge destination.

An example on how to use this:

wls_jms_bridge_destination {a_wls_jms_bridge_destination :
   ...
   connection_factory_jndi_name => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_jms_bridge_destination:connection_factory_jndi_name']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_jms_bridge_destination

connection_url

The connection URL for this JMS bridge destination.

An example on how to use this:

wls_jms_bridge_destination {a_wls_jms_bridge_destination :
   ...
   connection_url => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_jms_bridge_destination:connection_url']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_jms_bridge_destination

connectionfactoryjndi

The connection factory’s JNDI name for this JMS bridge destination.

Back to overview of wls_jms_bridge_destination

connectionurl

The connectionurl.

Back to overview of wls_jms_bridge_destination

destination_jndi_name

The destination JNDI name for this JMS bridge destination.

An example on how to use this:

wls_jms_bridge_destination {a_wls_jms_bridge_destination :
   ...
   destination_jndi_name => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_jms_bridge_destination:destination_jndi_name']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_jms_bridge_destination

destination_type

The destination type (queue or topic) for this JMS bridge destination.

An example on how to use this:

wls_jms_bridge_destination {a_wls_jms_bridge_destination :
   ...
   destination_type => 'Queue'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_jms_bridge_destination:destination_type']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_jms_bridge_destination

destinationjndi

The destination JNDI name for this JMS bridge destination.

Back to overview of wls_jms_bridge_destination

destinationtype

The destination type (queue or topic) for this JMS bridge destination.

Valid values are Queue, Topic.

Back to overview of wls_jms_bridge_destination

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_jms_bridge_destination

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_jms_bridge_destination

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_jms_bridge_destination

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_jms_bridge_destination

ensure

The basic property that the resource should be in.

Valid values are present, absent.

Back to overview of wls_jms_bridge_destination

initial_context_factory

The initial context factory name for this JMS bridge destination.

An example on how to use this:

wls_jms_bridge_destination {a_wls_jms_bridge_destination :
   ...
   initial_context_factory => 'weblogic.jndi.WLInitialContextFactory'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_jms_bridge_destination:initial_context_factory']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_jms_bridge_destination

initialcontextfactory

The initial contextfactory.

Back to overview of wls_jms_bridge_destination

name

The name.

Back to overview of wls_jms_bridge_destination

notes

Optional information that you can include to describe this configuration. WebLogic Server saves this note in the domain’s configuration file (config.xml) as XML PCDATA. All left angle brackets (<) are converted to the XML entity <. Carriage returns/line feeds are preserved. <dl> <dt>Note:</dt> <dd> If you create or edit a note from the Administration Console, the Administration Console does not preserve carriage returns/line feeds. </dd> </dl>

An example on how to use this:

wls_jms_bridge_destination {a_wls_jms_bridge_destination :
   ...
   notes => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_jms_bridge_destination:notes']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_jms_bridge_destination

password

The bridge password.

Usage :

wls_jms_bridge_destination { ....:
  ...
  password => 'clear_text_password',
  ...
}

The password string is passed to WebLogic for encryption and then stored in the domain.

Back to overview of wls_jms_bridge_destination

provider

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

simple

Manage a JMS bridge destinaion in an WebLogic domain via regular WLST

Back to overview of wls_jms_bridge_destination

tags

Return all tags on this Configuration MBean

An example on how to use this:

wls_jms_bridge_destination {a_wls_jms_bridge_destination :
   ...
   tags => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_jms_bridge_destination:tags']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_jms_bridge_destination

user_name

The user name.

Back to overview of wls_jms_bridge_destination

user_password

The user password that the adapter uses to access the bridge destination. As of 8.1 sp4, when you get the value of this attribute, WebLogic Server does the following: <ol><li>Retrieves the value of the UserPasswordEncrypted attribute. <li>Decrypts the value and returns the unencrypted password as a String. </ol> When you set the value of this attribute, WebLogic Server does the following: <ol><li>Encrypts the value.</li> <li>Sets the value of the UserPasswordEncrypted attribute to the encrypted value.</li> </ol> Using this attribute (UserPassword) is a potential security risk because the String object (which contains the unencrypted password) remains in the JVM’s memory until garbage collection removes it and the memory is reallocated. Depending on how memory is allocated in the JVM, a significant amount of time could pass before this unencrypted data is removed from memory. Instead of using this attribute, use UserPasswordEncrypted.

An example on how to use this:

wls_jms_bridge_destination {a_wls_jms_bridge_destination :
   ...
   user_password => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_jms_bridge_destination:user_password']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_jms_bridge_destination