NOC Management engine connection factory
This connection factory is used by the NOC Management engine to process messaging requests.
| Property | Value | Description |
|---|---|---|
| Scope | Cell | Scope specifies the level at which the resource definition is visible. For a
stand-alone server installation, the JMS connection factory is to be configured at the cell level. For
example, For a cluster installation, the JMS connection factory is to be
configured at the cluster level. For example, |
| Provider | The IBM® MQ messaging provider. | The name of the messaging provider. |
| Name | NOC MQ Connection Factory | The name of the connection factory. |
| JNDI Name | jms/noc/NocQCF | The Java™ Naming and Directory Interface (JNDI)
name. Note: The value for this entry must be exactly as shown.
|
| Container-managed authentication alias | NOC Queue Manager JAAS Alias | The name of the NOC Management queue manager JAAS alias. |
| Mapping-configuration alias | DefaultPrincipalMapping | The JAAS configuration maps an authentication alias to its user ID and password. |
| Queue manager | Customer specified | The name of the IBM MQ queue manager for this connection factory. |
| Host | Customer specified | The name of the host on which the IBM MQ queue manager runs. |
| Port | Customer specified | The TCP/IP port number used to connect to the IBM MQ queue manager. |
| Transport type | Client | Specifies to use the IBM MQ client connection to connect to the queue manager. |
| Retain messages, even if no matching consumer is available | Selected | Specifies whether unwanted messages are left on the queue. |
| Support two phase commit protocol | Selected | Specifies whether the connection factory is for XA or non-XA coordination of messages. |
| Fail JMS method calls if the WebSphere® MQ queue manager is quiescing | Selected | Indicates whether selected JMS operations fail if they are called while the queue manager is quiescing. |