Broker

WebMethods Integration Server (IS) is mainly used to support the integration of diverse services
and communication between systems.
But to do the same we need multiple Integration servers to do the complete job (Not compulsory,
depends on business requirements and server load). And this is the area where Broker will come into
the picture, which acts as "message backbone" which helps the IS's to communicate with each other
using a model called as "Publish and Subscribe Model". We will look into more details about this
model in another section.
When the IS's received the documents from the external applications, the IS publishes the document
to the the respective configured Broker which in turn the configured subscriber (another IS or
another application) will subscribe those documents for the further process. So this inturn indicates
that the IS interactions are in de-coupled format, meaning they do not interact directly. Instead, the
interactions will happen through Broker.
When the IS's received the documents from the external applications, the IS publishes the
document to the the respective configured Broker which in turn the configured subscriber (another
IS or another application) will subscribe those documents for the further process. So this inturn
indicates that the IS interactions are in de-coupled format, meaning they do not interact directly.
Instead, the interactions will happen through Broker.

By default, port 6849 is the Broker Server base port.

How Integration Server communicate with Broker?

The Integration Server uses "dispatcher.cnf" config files to communicate with Broker. This
config will store all the information about the Broker to which IS wants to communicates
like broker server name, broker server port, status of the Broker. The dispatcher will also
take care of the connection pool monitoring which helps to connectivity between IS and
Broker.
How the Storage will be handling in the Brokers?

The broker Storage will be handling through the concept called "Queue". When the broker
receives the documents from the IS, the Broker will place the documents that matches the
client's subscription in the client's queue.Each client has it's own queue.
The Queue will be either in "Locked" or "Unlocked" state. During the "Lock" state all the
published documents will be keep piling up in the queue which we can be used to verify
the documents structure by downloading the same. And during the "Unlock" state the
documents will be subcribed by the respective subscribing clients.

Note: When there are no subscriptions for the respective documents, then the documents will be
moved to queue called "DeadLetter" queue.

Note: We use another concept of queue called "Forward queue", this is mainly used in the
Territories to store the documents between the brokers configured in territories.
What about Storage Type of Documents?

Documents published to Broker can be stored as volatile documents or guaranteed

documents. Volatile documents are stored only in memory and are lost if the host machine
loses power or the Broker Server is otherwise re-started. Guaranteed documents are
persisted to disk so that they can be recovered in case of a power failure or a restart.

As we know that, the broker communicates between Publisher and subscriber through
documents. But how will the Broker knows, whether to accept or discard the incoming
document when it is notified with the incoming document. To achieve this the Broker uses
the "Document Type" as filter technique, which mean that when the Broker receives the
document the Broker will check whether the respective Document type is configured in
the broker to accept the Document if it is then it will accept by the respective broker.

Each document is an instance of a document type. A document type is a schema-like

definition that describes the structure of a document that publishers and subscribers can
exchange using the Broker. A document type has a unique name, a structure that consists
of named fields, and a set of properties that determines how the Broker handles instances
of that document type at run time.

We can create these Document Types either in the following ways.

1. We can use Developer to define a document type and mark it as publishable.

Repeat: Repeat is a conditional based flow step. The execution of child steps will be depends on "REPEAT
ON" value (SUCESS / FAILURE in property panel).
Loop: You should perform a loop operation on array of items(String list/Document list/Object list). Loop
operation process each and every array element in the array. you have to give the input array value.

2) What is scope?
Ans. Scope Property is used to restrict flow step to access only the elements of a IData
Object. For Example if document x has elements x1,x2,x3,lets say for flow Map step we
set the scope as X when the control is in map step we can do Operations only on x1, x2,
x3.

PUB-SUB model
Publisher publishes a document broker then the subscriber receive the document from broker.you
should make document as publishable at publisher side.

Subscriber should subscribe to that particular document by creating a trigger. The trigger monitors
that document. If a subscribed document got published then trigger invokes a service which
associates with trigger to handle the document.
 Introduction to EAI (webmethods)

webMethods

I)Introduction:

The company pioneered the use of web services to connect software applications together within a single organization and
across the Internet.

II)Focused On:

1)Application Integration.

2)Business Process Integration.

3)B2B Partner integration.

III)Basis:

It is based on the idea to use the new standards of the Web such as HTTP and XML to allow software applications to
communicate with one another in a real time.

Series of development consist of:

1)Web Automation Server.

2)Web Methods B2B Integration Server.

IV)Basic Function of this software:

It is basically an engine for running services .A service can be viewed as a black box which performs some computational
function. It takes in required data, required messages and generates the output as required by the required computation.

The Web method integration server is a service engine therefore to IS, everything is viewed as a service.

V)Other Components of it are as follows:

1)Integration Servers:

It is the engine for running services .Many other modules are used as an add on the integration server on the top of the IS.
Some of the examples are Trading Networks, Flat File Handler and Business Process

Modeler as well as the administrative GUIs for other modules.

Features of the Integration Server is as follows:

a) An engine for running local services, distributed services, web services.

b) A client enabler to invoke local services, distributed services, web services.

c) To bind two disparate systems.

d) An XML parser and generator.

It uses the Web method Flow Procedural Statements which are :

1) MAP(assignment statement).

2) BRANCH(decision statement).

3) LOOP(iteration statement).

In addition the flow language has the following extra 4 statements:

4) INVOKE (subroutine call).

5) SEQUENCE(compound statement)

6) EXIT

7) REPEAT(another iteration)

2) Trading Networks:

It is a service that acts as an interface between the internet and the Webmethod . It tracks down data between the multiple
external partners and an integration server.It performs task such as

a)Authentication

b)Authorization

c)Document Identification

d)Logging and activity monitoring.

It can be viewed as a generalized document router, but in reality it acts as simply another service running with the integration
server. It can be invoked via a variety of mechanisms such as HTTP, FTP, SMTP, Web Services ,java client or via
publish/subscribe.

3)Broker:

It acts as separate server which helps to pass data between the multiple instances of the integration Server. In it a service
publishes a document to the broker and the broker delivers the document to all services that subscribe to the document. The
Broker performs routing of messages in a reliable and efficient manner.

4)JAVA Service:

Java is used to write for all the services except the running services. The cases when java should not be used to write services
are as follows :

1)The Webmethod developer does not provide an IDE for java.

2)Java program cannot easily manipulate the pipeline which is used by integration server to pass data among services.

3)Java is harder to implement in comparision to the flow language.

VI)Webmethods Installation:

Its products are not free and the cost goes up high to have it. The products can be installed from the internet if you have an
access to the appropriate license key.

An installer program WebmethodsInstaller651.exe is needed to access the installation files.

The installation choices are as follows:

a)We can deploy the products online on a single machine kust by opting out for the prompts interactively or via a script file.

b)We can download products to a image file which can be later used for the local deployments,by answering prompts
interactively or via a script file.

VII)Hardware Configuration requirements:

a)2-3 GHz CPU.

b)1-2 GB RAM

c)40-80 GB HDD.

d)Compatible with both Unix and Windows OS(Unix is favored for the production system but windows is better for an
experimental purpose).

e)A Database(For example Oracle or SQL Server)

VIII)webMethods Products :

It produces a lot of the products that focuses on

a)Enterprise Application Integration Market(EAI):

It is concerned with integrating disparate systems such as application servers (SAP, Seibel, Peoplesoft ),

Database management systems(Oracle, SQL Server, DB2),mainframe and custom applications(J2EE).

b)Business-to-Business market(B2B):

It is concerned with enabling separate companies to exchange electronic documents , such as purchase orders ,invoices, etc .