Mediation primitives have properties, and some of these
properties can be made visible to the runtime administrator by promoting
them. This section shows the properties you can promote.
Table of promotable properties
The follow
tables shows the properties you can promote and that, therefore, can
be dynamically overridden.
Table 1. The promotable properties
of mediation primitivesMediation primitive |
Promotable properties |
Custom Mediation |
Value (in User Properties) |
Database Lookup |
Search column |
Search location |
Table |
Target location |
Validate input |
Endpoint Lookup |
Classification |
Export |
Match policy |
Module |
Name |
Namespace |
Registry name |
Value (in User Properties) |
Version |
Event Emitter |
Enabled |
Transaction mode |
Fail |
Error message |
Fan In |
Count (decision type) |
Timeout |
XPath (decision type) |
Fan Out |
Batch Count |
HTTP Header Setter |
Validate input |
JMS Header Setter |
Validate input |
Message Element Setter |
Validate input |
Value (in Message Elements) |
Message Filter |
Distribution mode |
Enabled |
Pattern (in Filters) |
Message Logger |
Enabled |
Level |
Logging type |
Root |
Transaction mode |
MQ Header Setter |
Validate input |
Policy Resolution |
Classification |
Propagate to response flow |
Service Invoke |
Async timeout |
Retry count |
Retry delay |
Retry on |
Try alternate endpoints |
Use dynamic endpoint if set in the message header |
Set Message Type |
Validate |
SOAP Header Setter |
Validate input |
Type Filter |
(XPath) Element |
XSL Transformation |
Mapping file |
Root |
Validate input |
Table 2. Other promotable propertiesComponent |
Promotable properties |
Callout node |
Async timeout |
Invocation style |
Retry count |
Retry delay |
Retry on |
Try alternate endpoints |
Use dynamic endpoint if set in the message header |
Runtime considerations
The value of certain
promotable properties is displayed by WebSphere® Integration Developer as a text
value, but by the runtime administrative console as an integer. If
you update these properties from the administrative console, you must
specify the integer values.
Table 3. Runtime values of mediation
primitivesMediation Primitive |
Property |
Text Value |
Integer Value |
Endpoint Lookup |
Match policy |
Return all matching endpoints |
0 |
Return first matching endpoint and set routing
target |
1 |
Return all matching endpoints and set alternate
routing targets |
2 |
Return endpoint matching latest compatible service
version |
3 |
Event Emitter |
Enabled |
True |
true (Boolean) |
False |
false (Boolean) |
Transaction mode |
Default |
0 |
Existing |
1 |
New |
2 |
Fan Out |
Batch Count |
Check for asynchronous responses after all messages
have been fired |
0 |
Check for asynchronous responses after {n} messages
have been fired |
Integer value greater than 0 |
HTTP Header Setter |
Validate input |
True |
true (Boolean) |
False |
false (Boolean) |
JMS Header Setter |
Validate input |
True |
true (Boolean) |
False |
false (Boolean) |
Message Filter |
Distribution mode |
First |
0 |
All |
1 |
Enabled |
True |
true (Boolean) |
False |
false (Boolean) |
Message Logger |
Enabled |
True |
true (Boolean) |
False |
false (Boolean) |
Level |
Severe |
0 |
Warning |
1 |
Info |
2 |
Config |
3 |
Fine |
4 |
Finer |
5 |
Finest |
6 |
Logging type |
Database |
0 |
Custom |
1 |
Transaction mode |
Same |
0 |
New |
1 |
MQ Header Setter |
Validate input |
True |
true (Boolean) |
False |
false (Boolean) |
Policy Resolution |
Propagate to response flow |
False |
false (Boolean) |
Service Invoke |
Retry on |
Never |
0 |
Any fault |
1 |
Modeled fault |
2 |
Unmodeled fault |
3 |
SOAP Header Setter |
Validate input |
True |
true (Boolean) |
False |
false (Boolean) |
Table 4. Runtime values of the callout nodeComponent |
Property |
Text Value |
Integer Value |
Callout node |
Retry on |
Never |
0 |
Any fault |
1 |
Modeled fault |
2 |
Unmodeled fault |
3 |