What is the Publish-and-Subscribe Model?

• The publish-and-subscribe model is a specific type of message-based solution in which messages are exchanged anonymously through a message broker.

• Publishing Applications produce information that needs to be shared will make this information available in specific types of recognizable documents that they publish to the message broker.

• Subscribing Applications subscribe to the document types they need.

• At run time, the message broker receives documents from publishers and then distributes the documents to subscribers.

• The subscribing application processes or performs work using the document and may or may not send a response to the publishing application.

BROKER

Origin Of Broker

• The Broker originated from the webMethods/Active

Software merger and when most customers shifted their

focus from Business-to-Business (B2B) integration to EAI

integration initiatives. • Its primary responsibility was to provide a centralized

EAI messaging Server for the entire platform.• All transactions (documents) would traverse through

the Broker as it was the centralized ‘transaction router’ for

all Integration transactions.

Features Of Broker

• webMethods Broker provides the high-speed messaging

backbone for the webMethods Integration Platform. • It enables asynchronous, guaranteed message delivery

and routing in a highly efficient and scalable architecture.• House the flow,logic,code and orchestration of all

internal integration transactions.• Main Server for adapter connectivity and communication.• Centralized Server of all Internal Transactions.• Centralized Logging,Queuing of all Internal transactions.

Components

Broker Server: Client applications publish and subscribe to informationin the form of documents.The Broker Server manages theflow of documents among clients, Brokers, and variousapplications.

Broker: Each Broker Server has one or more entities,called Brokers, that reside on it. A Broker is where theclient programs connect, where document types are stored,and where client queues and subscriptions aremonitored and stored.

Components

Broker Clients:

A Broker client is a handle that is created and used

by client programs. It represents a connection to a particular

Broker.

Territory:

Brokers can share information about their document type

definitions and client groups by joining a territory. Brokers

within the same territory have knowledge of each other’s

document type definitions and client groups.

Components

Client State:

Describes a connection between a Broker client and a

Broker. It includes a client identifier, the client queue,the

client subscriptions.

Client Groups:

A configuration mechanism used in webMethods

Enterprise Server to configure and control the interaction

between Broker clients and a Broker. A client group defines

how queues are managed and document access permissions.

Components

Client Queue: An area of storage on a Broker used to hold documentsdestined for a specific client. A document is held in the clientqueue until it is retrieved by the client. Document type: Document types are the basis for establishing subscriptionsclient registers an interest in receiving documents of a specifictype.

Broker Management Tools

MWS provides functions to manage Broker Server,

• Start the My WebMethods Server.• Point your browser to the host and port where the MWS

is running with user name ‘Administrator’ and password ‘manage’.

• URL

http://hostname:8585/

Managing the Broker Server

Creating a webMethods Broker Server: The Broker Server installation software creates a defaultBroker Server that runs on port number 6849. To createadditional Broker Servers on the same Broker Server Host,use the server_config command-line program.

Adding a Broker Server to Broker Administrator:• Add known Broker Server option-specify the name

and port number of the broker.• Discover Broker Server option –To run multiple Broker

Servers on the same host.• Upload Broker Server List option- To populate the

Broker Server view with multiple Broker Servers all at once.

Managing the Broker Server

Removing a Broker Server:• In the Settings menu of Admin Page, click Known

Broker Servers.• On the Known Broker Server Settings page, click

Remove One or More Broker Servers.• In the Known Broker Servers list, select the check box

next to the Broker Server you want to remove.• Click Remove.

Creating and Configuring a Client Group

Creating a Client Group1 . Open the MWS Administration Messaging if it is not

already open.2. From the Navigation panel, under the appropriate Broker

Server and Broker,click Client Groups.3 .From the Client Groups page, click Create a New Client

Group.4 .In the Client Group Name field, enter the name of the client

group.5 .In the Client Group Description field, type a brief description

of the client group.6 .Select the lifecycle you want the Broker clients in the group to

have.7. Select the queue storage type from QueueStorage Type field 8 .Click Create.

Creating and Configuring a Client Group

Deleting a Client Group:1.Open MWS Administration Messaing if it is not

already open.2. From the Navigation panel, under the appropriate Broker

Server and Broker, click Client Groups.3. On the Client Groups page, click Delete Client groups.4. Select the client group you want to delete and then click

Delete.5. In the confirmation dialog box, click OK.

Territory

A facility by which two or more Brokers communicate and share document definitions.

Territories

• All Brokers in a territory share the same client groups and document types.

• Within a territory, documents published on one Broker can be sent to other Brokers because they are delivered there or a client on another Broker has a matching subscription.

• You cannot merge territories. To create a single territory where two existed before, the Brokers in one territory must leave it and then join the second territory .

• A territory cannot be empty.

Managing Territories

Creating a Territory:1.Open MWS Administration Messaging if it is not already

open.2. Navigate to the Broker Information page of the Broker for which

you will create a territory. 3. Click Create a New Territory.4. Type the name that is to belong to the territory in the New

Territory Name field.5. Click Create.

Leaving a Territory:1. Open the MWS Administration Messaging if it is not

already open.2. Navigate to the Broker Information page of the Broker who will

leave a territory.3. Click Leave Territory.

Territory Gateways

• A territory gateway is a connection between two territories, allowing the transfer of documents between the territories.

Territory GatewayCreating Gateways:• Create the gateway independently on each side of the territory.• Optionally, configure gateway security.• Configure the shared document types.• Synchronize changes to the definition of a shared document type

in one territory across the gateway to the territory.• Configure the document type permissions.• Optionally, set up the Gateway keep alive feature.

Removing a Territory Gateway• Open the MWS Administration Messaging if it is not

already open.• Open the Gateway Information page of the Gateway Broker. • Click Remove Gateway.• Select either Remove Both Sides of Gateway or Remove One

Side of Gateway.• Click Remove.

Publish-Subscribe Model

Basic Elements in the Publish-and-Subscribe Model

• Documents • Publishable Document Types• Triggers• Services• Adapter Notifications• Canonical Documents

Basic Elements in the Publish-and-Subscribe Model

Documents: An objects that the integration platform uses to

encapsulateand exchange data.Publishable Document Types:

A named schema-like definition that describes the structure of

a particular kind of document that can be published and subscribed.

Triggers:It establish subscriptions to publishable document types.

Basic Elements in the Publish-and-Subscribe Model Services

Services: They contain logic that the Integration Server executes.

Adapter Notifications: Adapter notifications notify the webMethods Integration Platformwhenever a specific event occurs on an adapter's resource.

Canonical Documents: A canonical document is a standardized representation that adocument might assume while it is passing through the webMethodsIntegration Platform. A canonical document acts as the intermediary data format betweenresources.

Steps for Building a Publish-and-Subscribe Solution

1. Research the Integration Problem and Determine Solution

2. Determine the Production Configuration 3. Create the Publishable Document Type 4. Make the Publishable Document Types Available 5. Create the Services that Publish the Documents6. Create the Services that Process the Documents7. Define the Triggers 8. Synchronize the Publishable Document Types

Steps for Building a Publish-and-Subscribe Solution

Research the Integration Problem and Determine

Solution: The first step to building an integration solution is to

define the problem and determine how to solve the problem using the publish-and-subscribe model.

Determine the Production Configuration: Determine the development environment to mirror

the production environment by finding theClusters,Broker etc.

Publishable Document Type creation

Making an Existing IS Document Type Publishable:

• Open the IS document.

• In the Properties panel, under Publication, set the Publishable property to True.

• Next to the Storage type property, select the storage method.

• When you make a document type publishable, the Integration Server adds an envelope field (_env) to the document type automatically.

Publishable Document Type creation

Creating Publishable Document from a Broker Document Type

• On the File menu, click New.• Select Document Type and click Next.• In the New Document Type dialog box,give the folder name and the

name of the document.• Select Broker Document Type, and click Next. Developer opens the

New Document Type dialog box,give the broker namespace.• When you make a document type publishable, the Integration Server

adds an envelope field (_env) to the document type automatically

Make the Publishable Document Types Available

One Integration Server:

• No need to take any action to make the publishable

document types available to other developers.

Multiple Integration Servers with a Broker:• Use Developer or Use package replication

Create the Services that Publish the Documents

The service which publishes the document uses any

one of the below services.pub.publish:deliver:

Delivers a document to a specified destination.

pub.publish:deliverAndWait: Delivers a document to a specified destination and waits for aresponse.

pub.publish:publish: Publishes a document locally or to a configured Broker.

Create the Services that Publish the Documents

pub.publish:publishAndWait:

Publishes a document locally or to a configured Broker and

waits for a response.

pub.publish:reply: Delivers a reply document in answer to a document receivedby the client.

pub.publish:waitForReply: Retrieves the reply document for a request published

asynchronously.

• Create a document reference to the publishable

document type that you want to publish.• Add content to the document reference.• Invoke any of the available publish services and set the

appropriate fields like documentTypeName,destID,

receiveDocumentTypeName etc

Create the Services that Publish the Documents

Creating a Trigger

• On the File menu, click New.• In the New dialog box, select Trigger, and click Next.• In the New Trigger dialog box,provide the folder andtrigger name. • In the editor, use the following procedure to build acondition.give the subscribing service name and also thedocument to be subscribed.• In the Properties panel, specify the join time-outperiod, trigger queue capacity,document processing mode,and document delivery attempts in case of error.• On the File menu, click Save to save the trigger.

Creating a Trigger

Thank You!!!!