Configure custom properties for WebSphere MQ messaging provider JMS resources
In addition to the standard properties that we can define for WebSphere MQ messaging provider JMS resources, we can configure further WebSphere MQ properties as custom properties. We can configure custom properties for activation specifications, connection factories, and JMS destinations for the WebSphere MQ messaging provider.
WebSphere Application Server supports the use of custom properties to define WebSphere MQ properties. This is useful because it enables WebSphere Application Server to work with later versions of WebSphere MQ that might have properties that are not exposed in WebSphere Application Server.
We can use this task to set custom properties for JMS destinations, connection factories, and activation specifications for the WebSphere MQ messaging provider. For example, you would use this task to set the custom property WAS_EndpointInitialState for an activation specification. WAS_EndpointInitialState determines whether or not message consumption begins from the JMS destination as soon as the activation specification is used for a message-driven bean to connect with the destination.
To specify custom properties for WebSphere MQ messaging provider JMS resources, use the console to complete the following steps:
- In the navigation pane, click Resources > JMS.
- Select the type of JMS resource for which we want create custom properties (JMS destinations, connection factories, or activation specifications).
- Optional: Change the Scope setting to the level at which the resource definition is visible to applications.
- In the contents pane, select the specific WebSphere MQ messaging provider JMS resource name for which to specify the custom property. This displays information about the resource.
- To create a custom property, select [Additional Properties] Custom properties.
- Click New in the content pane.
- Specify the following attributes for the new custom property:
- Name
- The name of the custom property. A property name is required.
- Value
- The value for the custom property.
- Type
- The type of the custom property. Select the custom property type from the list.
- Click Apply. This defines the custom property to WebSphere Application Server, and enables you to browse or change additional properties.
- Save any changes to the master configuration.
- To have the changed configuration take effect, stop then restart the application server.
Example
To set the custom property WAS_EndpointInitialState for an activation specification, specify the following attributes:
- For Name, specify WAS_EndpointInitialState.
- For Value, specify one of the following options:
- ACTIVE
- Specify a value of ACTIVE if message consumption is to begin as soon as the message-driven bean connects with the JMS destination.
- INACTIVE
- Specify a value of INACTIVE if message consumption is not to begin until you use wsadmin.sh or the console to activate message consumption for the message-driven bean.
- For Type, select String.
Related concepts
WebSphere MQ custom properties
Related tasks
Manage messages with message endpoints Configure an activation specification for the WebSphere MQ messaging provider Configure a unified connection factory for the WebSphere MQ messaging provider Configure a queue connection factory for the WebSphere MQ messaging provider Configure a topic connection factory for the WebSphere MQ messaging provider Configure custom properties for the WebSphere MQ resource adapter
WebSphere MQ resource custom properties settings WebSphere MQ resource custom properties settings WebSphere MQ messaging provider custom properties