WebSphere brand IBM WebSphere Telecom Web Services Server, Version 7.1

JMX Notification

Used to emit Java Management Extensions (JMX) notifications by means of the WebSphere Application JMX infrastructure.

Description

The JMX Notification mediation primitive is used to emit Java Management Extensions (JMX) notifications via the WebSphere Application JMX infrastructure. WebSphere® Application Server provides plug-points with which software products (IBM and non-IBM) can receive the notifications and gather management-related information. The JMX Notification mediation primitive gathers information about Access Gateway processing faults from the service message object (SMO) headers according to the SMO schema.

SMO headers

The headers used by other Access Gateway mediation primitives are described in the property table:

SMO header (represented by XPath) Content
ServiceMessageObject/context/failInfo/failureString The full message text that represents the fault situation with substituted variables. For example, SOAC4025E: Error occurred.
ServiceMessageObject/context/failInfo/origin The name of the mediation primitive class that originates the fault.
ServiceMessageObject/SOAPFaultInfo/faultcode The TWSS message code that represents the fault situation. For example, SOAC4025E.
ServiceMessageObject/SOAPFaultInfo/faultstring The full message text that represents the fault situation with substituted variables. For example, SOAC4025E: Error occurred.
ServiceMessageObject/context/transient/exceptionType The exception type element under the transient context may contain one of two values: service or policy. These values represent the context of the fault: indicating whether it was caused by the operation of the service or a policy-related action.

The notification contains the detailed fault string with the origin element used as the originating class for the JMX notification.

When running in a secured environment, the JMX Notification mediation primitive must have access to the administrative user name and password to have sufficient privileges to emit notification events. These credentials can be configured as part of the mediation primitive configuration properties.

Policy configuration

This mediation primitive uses the following policies for runtime configuration:

None

Mediation primitive properties

This mediation primitive uses the following configuration properties. These properties can be modified using WebSphere Integration Developer (WID) tooling. Properties that are promoted can be configured using the Integrated Solutions Console.
Property Type Promoted? Description
adminUserName string yes The administrative user name used to run as the administrative user principal when emitting JMX notifications. This user name is needed only when security is enabled.

Default: (blank)

adminPassword string yes The administrative user password used to run as the administrative principal when emitting JMX notifications. Encrypt the password with the AdminTool provided with TWSS: java -jar AdminTool.jar encryptpassword

Default: (blank)

Upstream SOAP headers

The following SOAP header elements are expected from upstream mediation primitives:

None

Added SOAP headers

The following SOAP header elements are added or modified for downstream mediation primitives:

None

Message handling

Messages that are successfully processed by the JMX Notification mediation primitive are passed to the output terminal of the mediation primitive. If an error occurs while processing the message, the error is logged for tracing.



Terms of use
(C) Copyright IBM Corporation 2009. All Rights Reserved.