Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The scheduled message forwarding processor is a message processor that consumes messages in a message store and sends them to an endpoint . If a message is successfully delivered to the endpoint, the processor deletes the message from the message store. In case of a failure, it will retry after a specified interval. 

...

Parameter Name

Description

Required

NameThe name of the scheduled message forwarding processor.Yes
Endpoint nameThe endpoint to which the scheduled message forwarding processor should forward messages.Yes
Message StoreThe message store from which the scheduled message forwarding processor consumes messages.Yes
Processor state (is.active)Activate (true) or Deactivate (false)Yes
Forwarding interval (interval)

Interval in milliseconds in which processor consumes messages.

If both Cron Expression and Forwarding Interval are specified in the configuration, Cron Expression will precede the Forwarding Interval.

No (The default value is 1000)

Retry interval (client.retry.interval)

Message retry interval in milliseconds.

No (The default is value is 1000)

Non retry http status codes (non.retry.status.codes)

The parameter based on which the message processor decides if it needs to retry. If the HTTP status code of the response is specified as a non retry http status code, it will not retry. 

No

Maximum redelivery attempts (max.delivery.attempts)

Maximum redelivery attempts before deactivating the processor. This is used when the backend server is inactive and the ESB tries to resend the message.

No (The default value is 4)

Drop message after maximum delivery attempts (max.delivery.drop)

If this parameter is set to Enabled, the message will be dropped from the message store after the maximum number of delivery attempts are made, and the message processor will remain activated. This parameter would have no effect when no value is specified for the Maximum Delivery Attempts parameter.

The Maximum Delivery Attempts parameter can be used when the backend is inactive and the message is resent.

If this parameter is disabled, the undeliverable message will not be dropped and the message processor will be deactivated.

No (The default value is Disabled)

Axis2 Client repository (axis2.repo)

The location path of the Axis2 Client repository path. This repository is the location where services and modules reside.Noused when it is needed to process messages prior to sending them to the endpoint.

No (The default value is /repository/deployment/client )

Axis2 Configuration (axis2.config)

The location path of the Axis2 Configuration file to be used to send messagesprocess messages prior to sending them to the endpoint.

No (The default value is repository/conf/axis2/axis2_blocking_client.xml )

Reply sequence name (message.processor.reply.sequence)

The name of the sequence where the message reply should be sent.

No

Fault sequence name (message.processor.fault.sequence)

The name of the sequence where the fault message should be sent to in case of a SOAP fault.

No

Deactivate sequence name (message.processor.deactivate.sequence)

The deactivate sequence that will be executed when the processor is deactivated automatically. Automatic deactivation occurs when the maximum delivery attempts is exceeded and the Drop message after maximum delivery attempts parameter is disabled.

No

Quartz configuration file path (quartz.conf)

The Quartz configuration file path. This properties file contains the Quartz configuration
parameters for fine tuning the Quartz engine. More details of the configuration can be
found at http://quartz-scheduler.org/documentation/quartz-2.x/configuration/ConfigMain.

No

Cron Expression (cronExpression)

Interval in milliseconds in which processor consumes messages.

If both Cron Expression and Forwarding Interval are specified in the configuration, Cron Expression will precede the Forwarding Interval.

No

Task Count (Cluster Modemember.count)

 

The

required

number of

worker nodes when you

tasks that need to

run the processor in more than 1 worker node.

be created for this message processor.

Specifying this will not guarantee that the processor will run

on

in each worker node. There can be instances where the processor will not run in some workers nodes.

No (The default value is 1)

...