Thursday, 13 November 2014

WebMethods -2: Messaging & Triggers Explained

There are two types of message styles popular in Software AG

·   Point to Point: In this style of messaging, message is sent between message provider and consumer. Both provider and consumer are known. The destination is represented as queue. Exactly one consumer will receive a single message. If there are no consumers available at the time the message is sent it will be kept until a consumer is available that can process the message. If a consumer receives a message and does not acknowledge it before closing then the message will be redelivered to another consumer. The producer and consumer are knows as senders and receivers.

· Publish-Subscribe: This messaging style enable message producer to publish message, which is subscribed by various interested consumers. When you publish a message it goes to all the subscribers who are interested - so zero to many subscribers will receive a copy of the message. Only subscribers who had an active subscription at the time the broker receives the message will get a copy of the message.

Note: The publishers and subscribers never communicate with each other directly. Instead, they communicate by exchanging messages through a message Broker

Triggers play vital role in messaging aspect of Webmethods. It is required to subscribe the message/document.

Properties of Triggers

 Processing Mode is of two type

Serial: Subscribe one document at a time. It is single thread operated.
Concurrent:  Subscribe multiple documents in parallel. It is multiple thread operated.


Transient error handling parameter is important in case of error handling. Max retry attempts indicate how many times a request can be retried in case of failure.

Exactly once helps identifying duplicate, new, in doubt aspect of request.

Trigger setting for below is done in order to connect and routes.

Note:- The above notes has been prepared based on my experience on the technology as well as various reference available on internet. 

Thank You!
Satender Kumar Mall

Twitter: satenderiiit

Sunday, 2 November 2014

WebMethods -1: Audit Explained

The Integration server (IS) has a feature, which helps to tracks the execution of services invoked in journey from starts to end in web-services call.

It is set at 2 level.

1.      IS level

It has 3 level

·         PerSvc: It indicated that Auditing is enabled and logging will be based on audit properties set in individual flows of the service.

·         Brief: - It indicated logging is always enabled. It is logged on error, success and start of the flows. It ignores the audit properties set on individual flows.

·         Verbose: It facilitates the complete functionality indicated brief. In addition it also includes pipeline for each flows logged.

2.      In individual flow of a service.

The Audit properties of flow have 3 parameter: -

·         Enable auditing
Never: Audit is turned off for current flow.
When top-level service only: If the flow is the entry point of a service invoke
Always: Audit is turned ON for current flow

·         Log on
Error only: flow is logged when only error/exception occurred/
Error and success: flow is logged in both success scenario & also during error/exception.
Error, Success and start: flow is logged in all scenarios.

·         Include pipeline
Never: Do include data structure when flow is logged.
On error only: Included data in flow only in case of error.
Always: Data in flow should be logged always when flow is logged.

Keys takeaways: -

·         Flows are logged in database, which is displayed on MyWebmethods server.
·         Flow logged with pipeline can be retrieved and used for debug of same flow or proceeding       flows.
·         Log wisely - Too much audit logging cost performance and no logging you end up blind in       case of error in production.
·         Audit logging gives indication of flows invokes when call is made to service.
·         There is more than 8 type of logging mechanism in Webmethods. All by default are                    logged to files. We need to configure in order to point the heavy logging to Database else        IS  will crash. See below

Note:- The above notes has been prepared based on my experience on the technology as well as various reference available on internet. 

Thank You!
Satender Kumar Mall

Twitter: satenderiiit