Parameters for the Service Facade to WebSphere MQ: one-way with acknowledgment pattern

Service information
Pattern parameter M C Default Description
Service WSDL Yes No Not applicable This pattern parameter identifies a deployable WSDL file, which you can select from the workspace.

To navigate to the required WSDL, click Browse.

Validation of SOAP request No Yes None This pattern parameter identifies the level of validation required for requests. Valid values are:
  • None
  • Content and value

Incoming service requests are validated as required by this pattern parameter.

Provider information
Pattern parameter M C Default Description
Provider queue manager No Yes   This pattern parameter identifies the queue on which the provider application receives requests from the broker message flow.

If left blank, the default is the broker queue manager.

Provider request queue Yes Yes PROVIDER This pattern parameter identifies the queue on which the provider application receives requests from the broker message flow.
Logging
Pattern parameter M C Default Description
Logging required No No Cleared

This pattern parameter determines whether the pattern instance includes the code for logging.

If Logging required is cleared, the Log subflow is not included.

If Logging required is selected, a Log subflow is included in the message flow and values must be set for Log queue manager and Log queue.

Log queue manager No Yes

This pattern parameter defines the queue manager for logging. It can be left blank if the broker queue manager is used for logging.

This parameter is required only if Logging required is selected.

Log queue No Yes LOG

This pattern parameter defines the queue for logging.

This parameter is required only if Logging required is selected.

Error handling
Pattern parameter M C Default Description
Error message required No No Selected

This pattern parameter defines whether the pattern application creates the message flow elements to create error messages.

If Error message required is selected, values must be set for Error queue manager and Error queue.

Error queue manager No Yes  

This pattern parameter defines the queue manager for error messages. It can be left blank if the broker queue manager is used for logging.

Error queue No Yes ERROR

This pattern parameter defines the queue for error messages.

This parameter is required only if Error message required is selected.

General
Pattern parameter M C Default Description
Broker schema No No mqsi If set, all message flows and ESQL files are created in the named broker schema. If not set, the default schema is used.
Flow prefix No No   If set, this prefix is added to the beginning of all message flow names.
Flow suffix No No   If set, this suffix is added to the end of all message flow names.
Queue prefix No No   If set, this prefix is added to the beginning of all queue names.

If default queue names are used, the prefix, suffix, or both, must be set to identify queue names for each pattern instance.

Queue suffix No No   If set, this suffix is added to the end of all queue names.
Short description No No   This description is added to the Short description property of all message flows that are generated.
Long description No No   This description is added to the Long description property of all message flows that are generated.

All the pattern parameters are listed with their default values.

The column headed M indicates whether the property is mandatory. The column headed C indicates whether the property is configurable, meaning that you can change the value when you add the message flow to the broker archive (BAR) file.

Where no default is indicated the default value is an empty string.

Back to Service Facade to WebSphere MQ: one-way with acknowledgment pattern specification