Custom policy

A custom policy allows you to define when message transmission occurs and which messages to send in the message transmission.

When creating custom policy rules for your application, it is recommended that you include a default all-inclusive rule so that messages are not accidentally overlooked by other rules. For example, this rule synchronizes messages that are at least one day old,

auto=DATEADD( day, 1, ias_StatusTime ) < ias_CurrentTimestamp

The following is a list of factors that impact the effectiveness of synchronization and should be considered when creating your own custom policy rules.

Message sizes
Synchronization frequency
Bandwidth and network reliability
Priority messaging
Data transfer costs

The custom policy is defined by a set of transmission rules.

Each rule is of the following form:

schedule = condition

where schedule defines when condition is evaluated. For more information, see Rule syntax.

All messages satisfying condition are transmitted. In particular, if schedule is automatic, the condition is evaluated when any of the following conditions occurs:

PutMessage() is called. See:
- .NET: PutMessage method
- C++: putMessage method
- Java: putMessage method
- SQL: ml_qa_putmessage
A message status change has occurred. This typically occurs when a message is acknowledged by the application. See:
- .NET: AcknowledgementMode enumeration
- C++: AcknowledgementMode class
- Java: AcknowledgementMode interface
- SQL: all messaging using the SQL API is transactional
A Push Notification is received.

See Using push notifications.
A Network Status Change Notification is received.
TriggerSendReceive ( ) is called. See:
- .NET: TriggerSendReceive method
- C++: triggerSendReceive method
- Java: triggerSendReceive method
- SQL: ml_qa_triggersendreceive

Discuss this page in DocCommentXchange.