1.2 Introduction To Webmethods

Introduction to webMethods
Integration Suite
Confidential | Copyright © Larsen & Toubro Infotech Ltd.

Course Objectives
This module will give you an introduction of

webMethods overview and details of each
components in webMethods suite.
Confidential | Copyright © Larsen & Toubro Infotech Ltd. 2

Course Agenda
1
Overview of
Integration
Scenarios 2
Functions and
Components of
3 wM
2 Design time &
Run time
Architecture
of wM

1
Overview of
Integration
Scenarios

Objectives
After this session you must be able to :

• Understand the various integration patterns with
examples

Integration scenarios
Integration scenarios are patterns of interaction Systems

between people (users, customers, partners),
applications, and businesses. webMethods
Application
supports many integration scenarios, including Integration
those summarized below:
Application Integration Single

Extended
Integration between software applications and
Self-Service View Enterprise
systems within the enterprise Integration
Extended Enterprise People Businesses

Integration between businesses
Collaboration
Managed interaction between end-users and systems
Access Integration
Integration of end-user access to back-end applications and data sources
Self-Service
Interactions between external users and a business’s processes. On the following
pages, each type of application scenario described above will be illustrated.
Application Integration
Application Integration
Propagation
Synchronization
Aggregation
Sequential Process
Invocation

Propagation
Source: Image from reference from wM 6.5 Integration Patterns Overview.ppt
Propagation of similar business objects from one system to other multiple systems
 One-to-many
 Real-time or batch (bulk transfer)
Examples
 Order status change

 Product/price change replication
 Unidirectional customer sync

Synchronization
Synchronization of similar business objects between two or more systems
 Bi-directional
 Many-to-many
Examples
 Single view of the customer (bi-directional sync)

 Master file sync

Aggregation
 Aggregation of information from multiple sources into a common destination

system
 Many-to-one
 Real-time or batch
 Examples
 Operational data store
 Consolidated reporting

Sequential Process
 Automated business process that steps sequentially across multiple

systems
Example
 Quote to order (front-office to back-office integration).

Managed Process
 Business process involving multiple systems where process logic (business rules,
routing rules) exists external to the applications.
Example
 Order management process with optional credit approval step

Innovation
 Invocation of a remote service that performs a required business function

Internal or external Query or transactional as service provider or invoker
Examples
 Lookup
 Web services
 Mainframe transaction integration
Extended Enterprise
Extended Enterprise
Document Exchange
Direct Integration
Shared Process

Document Exchange
 Exchange of a business document between two organizations

 Point-to-point or store-and-forward
 Neutral or proprietary format
Examples
 Document exchange via e-mail, FTP, or HTTP
 EDI

Direct Integration
 Integration between two organizations through a common integration

infrastructure.
Examples
 ERP-to-ERP
 Web services

Shared Process
 Implementation of a common business process agreed to between two or

more organizations
 Example: Rosetta Net order management

Collaboration
Collaboration
Integrated Workflow
 Integrated Workflow
 Integration of tasks performed by people within business process automation
Examples
 Integration process exception handling
 Bridging functional gaps between applications

Access Integration
Access Integration
Information Gateway
Composite Application
 Information Gateway
 Real-time access to enterprise data through a uniform query interface
Examples:
 Order status query

 Mainframe query
 Composite Application
 Transactional access to enterprise applications through a personalized user
interface
 Example: Composite CSR application

Summary
Integration scenarios are patterns of

interaction between people (users,
customers, partners), applications, and
businesses.

2
2
Overview of
Functions and
Integrationof
Components
Scenarios
webMethods

Objectives
After this session you must be able to :

• Implement a typical Integration
scenario using webMethods suite of
products
• Understand the dataflow between
various webMethods components

webMethods Introduction
Software AG who owns and has built the webMethods platform is a software company that
specializes in integration server software for enterprises.
webMethods integration platform is set of different components used to design, execute and
manage integration solutions
• Design – Business process can be designed by using webMethods Design time
components
• Execute – Designed business process can be executed by webMethods run time
components
• Manage- The developed business solutions can be managed by using webMethods
monitoring components
• webMethods architecture is based on Hub

and spoke model.
• webMethods can be leveraged for
exchanging documents with business
partners and Synchronizing the
information across the enterprise.
• webMethods can also be leveraged for
automating a multistep business process

webMethods Components
webMethods components can be broadly categorized under the below 3 criteria’s

Run time components :
• WebMethods Integration Server (IS)
• WebMethods Broker
• WebMethods Adapters
• WebMethods Workflow
• WebMethods Mainframe
• WebMethods Trading Networks (TN) and eStandard Modules
Design-Time Components:
• WebMethods Designer
• WebMethods Developer
Administrative and Monitoring Components:

• WebMethods Administrator
• WebMethods Monitor
• My webMethods Server (MWS)

IS - Integration Server
webMethods integration server is the platform’s central run-time

component. It serves as the entry point for the systems and applications
that you want to integrate and is the platform’s primary engine for the
execution of integration logic.
Integration servers:
• Hosts adapters
• Serves as a business-to- business gateway
• Execute integration logic.
• Hosts platform utilities and admin tools

Broker
• Broker is high-speed message router.

• It enables asynchronous, message based solutions that are built on the publish
subscribe model.
• The broker performs role of routing documents between information producers
(publishers) and information consumers(subscribers).
• Provides content based filtering.
• Provides Topic and as well as Queue types of messaging models.
Working with Broker:
• Message based solutions are developed based on Publish and Subscribe model.
• Broker maintains a list of subscribers for each message.
• It routes the messages to the subscribers for the message thus facilitates the
information exchange.
Broker-Supported Messaging Methods
Broker
Point-to-Point: The role of the document

is to route documents between information
producers(senders) and information
consumers(receivers).
Publish-Subscribe: The role of the document

is to route documents between information
producers(publishers) and information
consumers(subscribers).

Adapter
• Adapters run on the integration Server. They connect the
back-end resources in your enterprise(such as SAP, Ariba,
databases, etc.) to the integration platform.
• An adapter allows you to incorporate the resource in an
integration solution without having to build complex low-
level details of the resource or its transport protocol.
• Connects back end resources in the enterprise.
• Adapters runs on Integration server.
• Some of Adapters available:
• JDBC Adapter
• Siebel Adapter
• EJB Adapter
• JMS Adapter
• Define an appropriate connection to the back end resource.
• Using that connection define the required type of adapter
service.
• Different types of adapter service that can be defined for
JDBC Adapter connection are :
 Select
 Insert
 Delete
Confidential | Copyright © Larsen & Toubro Infotech Ltd.  Update 28
Trading Network
• webMethods Trading Networks is an optional add-on component that runs on the

integration server.
• You use Trading Networks to build, manage, and analyze your network of trading
partners in a document- oriented exchange scenario.
• A trading partner can be any system, within or outside your enterprise, that
produce to consumes business documents.

Developer
• webMethods Developer is a graphical

development tool that you will use to build,
edit, and test integration logic.
• Developer tool provides an integrated
development environment in which we
develop the logic and supporting elements
that carry out the work of an integration
solution. This also provides testing and
debugging tools for the solutions you create.
• Developer lets you rapidly construct
integration logic with an easy-to-use
implementation language called the
webMethods Flow Language, or flow.
• webMethods Flow provides a set of simple
but powerful constructs that you
use to specify a sequence of actions (steps)
that are executed at run time by the IS
• Developer provides Editors for creating
various elements such as Documents,
Schemas etc.
Working with Developer
Developer window contains
• Navigation Panel
• Recent elements panel
• Editor
• Properties panel
• Results panel
Login into the Developer with userid and password. Elements Provided by Developer
• Package
• Folder
• Flow Service
• Java Service
• Documents
• Schemas
• Adapter Services
• Web Service Connector
• Trigger
Services: T he actual work of receiving data from one resource and delivering it to another is
accomplished through the execution of integration logic on the integration server. Integration
logic is housed in units of work called services that run on the integration server. In an
integration solution, services are used to retrieve data from the resources, execute calculations, apply
business rules perform data transformation and pass data to other resources,systems and processes. 31
Workflow
With almost any automated process, your business inevitable has transactions that require
human intervention(for example, an order needing approval or credit issues needing
resolution). webMethods workflow integrates these human interactions into the
webMethods integration platform.
• Directs the Execution of workflows
• Work flow is a series of tasks performed by participants at execution time
• webMethods Workflow :
WorkFlow Server
WorkFlow Client
• WorkFlow Server orchestrates the execution of workflows
• WorkFlow Client is used to view and complete the pending tasks.

 webMethods Workflow directs the execution of workflows. A workflow is a series of
tasks performed by one or more people (participants) at execution time. Approval and
review processes are examples of work that is commonly implemented through
workflows.
 Workflows are also often used for exception handling in otherwise automated
processes.
 A workflow is a message-driven process. When a participant is required to perform a

task, the Workflow component issues a message to that participant.
 When the participant completes the task, the Workflow component issues a message
to the next participant in the workflow. A workflow can contain complex sequences
whose flow of execution is directed by routing decisions, timers, and join conditions.

Designer
Designer is a graphical tool to design

and implement business processes
Business process is sequence of steps
to be performed. Business processes
can be implemented in two ways
• Top down Approach
• Bottom up Approach
Process model is composed of :
• Steps
• Transitions
• Documents
Working with Designer: Open the
Designer User interface
Modes of operation
• Offline
• Online
Create a process model. Deploy the
process model into the Integration
server.

Administrator
webMethods Administrator allows you to

configure and administer all the
webMethods servers on your platform
with a single, browser-based interface.
It functions as a portal to the platform’s

Administrative interfaces (for example,
the administrative interfaces for the
Integration Server, the webMethods
Mainframe component, and the Broker).
Browser based interface used to

configure and Administer all
webMethods servers on your Platform
It can be accessed by
http://HostName:PortNumber\WmAdmi
n

webMethods Monitor
 Monitor is a real-time web-based monitoring

tool, presented in My webMethods.
 Monitor enables you to examine running and
Completed Business Processes, services,
Integrations and documents.
 Monitor allows to control your processes and
Integration solutions by suspending and
resuming Processes ,editing and re-submitting
documents.
 Monitor retrieves information about services ,
processes, documents by querying the audit
logs.
The audit logs maintain a permanent record of
certain types Of activities on the integration
platform.
Working with webMethod server :

Wm Monitor can be accessed with browser
http:\\Hostname:portNumber\WmMonitor

My webMethods Server(MWS)
 My webMethods Server is
both the primary runtime
component for webMethods
administrative and
monitoring capabilities.
 The My webMethods
framework provides a
unified ,task based user
interface for management
of webMethods components.
 Provides a role based,
secure environment which
ensures that user will
receive the information
they need ,when they need
it.
 MWS provides an
environment for building
applications (portals)using
Composite Application
Framework(CAF).
webMethods Optimize
 Optimize for Infrastructure

allows monitoring the resource
utilizations and various system
and operational metrics related to
the webMethods eco-system.
 Optimize for Process
provides the capability to View
and track of the transactions
related to Business Processes and
guides towards process
improvement.
 Optimize tor B2B provides the
capability to Monitor the data
flowing through the B2B gateway
to Trading Partners and measure
performance metrics for the
purpose of analysis.
 Optimize for SAP is a real-
time process monitoring software
solution for SAP business
processes.
wM Deployer

Automating a multistep business process
by using webMethods

3
Design time and

run time
Architecture

Objectives
After this session you must be able to
• Understand the design time architecture

• Understand the run time architecture

Runtime Architecture
Source: Image from webMethods_Modeler_User's_Guide_6_5_1.pdf

Runtime Architecture
The run-time components execute the integration solutions that you develop. They:
 Transform and validate data

 Execute integration logic
 Invoke processes on target systems
Clustering allows a group of Integration Servers to act as a single entity. A clustered

configuration provides redundancy, increases throughput and also improves performance
by distributing requests among a group of servers.
To increase the geographical or functional capabilities of the platform’s messaging

facility, you deploy multiple Brokers in a distributed configuration called a territory. A
document published to any Broker in a territory goes to all Brokers in that territory.

Development Architecture

Unit Summary
• The Architecture Overview module gave you an

overview of integration scenarios, design architecture,
and run-time architecture.
• Concepts and terms related to the webMethods

integration architecture and applications.
• Introduction to the functions and purpose of

webMethods components, including: Integration
Server Administrator, webMethods Developer,
webMethods Modeler, webMethods Monitor,
webMethods Workflow, webMethods Integration
Server, webMethods Broker, webMethods Manager,
webMethods Trading Networks Adapters and services .

Thank You
Our Business Knowledge,

Your Winning Edge.
Confidential | Copyright © Larsen & Toubro Infotech Ltd.

1.2 Introduction To Webmethods

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

1.2 Introduction To Webmethods

Caricato da

Copyright:

Formati disponibili

Introduction to webMethods

Confidential | Copyright © Larsen & Toubro Infotech Ltd.

This module will give you an introduction of

Confidential | Copyright © Larsen & Toubro Infotech Ltd. 2

Confidential | Copyright © Larsen & Toubro Infotech Ltd. 3

Confidential | Copyright © Larsen & Toubro Infotech Ltd. 4

After this session you must be able to :

Confidential | Copyright © Larsen & Toubro Infotech Ltd. 5

Integration scenarios are patterns of interaction Systems

Application Integration Single

Extended Enterprise People Businesses

Confidential | Copyright © Larsen & Toubro Infotech Ltd. 7

Source: Image from reference from wM 6.5 Integration Patterns Overview.ppt

 Order status change

Confidential | Copyright © Larsen & Toubro Infotech Ltd. 8

Source: Image from reference from wM 6.5 Integration Patterns Overview.ppt

Synchronization of similar business objects between two or more systems

 Single view of the customer (bi-directional sync)

Confidential | Copyright © Larsen & Toubro Infotech Ltd. 9

Source: Image from reference from wM 6.5 Integration Patterns Overview.ppt

 Aggregation of information from multiple sources into a common destination

Confidential | Copyright © Larsen & Toubro Infotech Ltd. 10

Source: Image from reference from wM 6.5 Integration Patterns Overview.ppt

 Automated business process that steps sequentially across multiple

Confidential | Copyright © Larsen & Toubro Infotech Ltd. 11

Source: Image from reference from wM 6.5 Integration Patterns Overview.ppt

 Order management process with optional credit approval step

Confidential | Copyright © Larsen & Toubro Infotech Ltd. 12

Source: Image from reference from wM 6.5 Integration Patterns Overview.ppt

 Invocation of a remote service that performs a required business function

Confidential | Copyright © Larsen & Toubro Infotech Ltd. 14

Source: Image from reference from wM 6.5 Integration Patterns Overview.ppt

 Exchange of a business document between two organizations

Confidential | Copyright © Larsen & Toubro Infotech Ltd. 15

Source: Image from reference from wM 6.5 Integration Patterns Overview.ppt

 Integration between two organizations through a common integration

Confidential | Copyright © Larsen & Toubro Infotech Ltd. 16

Source: Image from reference from wM 6.5 Integration Patterns Overview.ppt

 Implementation of a common business process agreed to between two or

 Example: Rosetta Net order management

Confidential | Copyright © Larsen & Toubro Infotech Ltd. 17

Confidential | Copyright © Larsen & Toubro Infotech Ltd. 18

 Order status query

Confidential | Copyright © Larsen & Toubro Infotech Ltd. 19

Integration scenarios are patterns of

Confidential | Copyright © Larsen & Toubro Infotech Ltd. 20

Confidential | Copyright © Larsen & Toubro Infotech Ltd. 21

After this session you must be able to :

Confidential | Copyright © Larsen & Toubro Infotech Ltd. 22

• webMethods architecture is based on Hub

Confidential | Copyright © Larsen & Toubro Infotech Ltd. 23

webMethods components can be broadly categorized under the below 3 criteria’s

Administrative and Monitoring Components:

Confidential | Copyright © Larsen & Toubro Infotech Ltd. 24

webMethods integration server is the platform’s central run-time

Confidential | Copyright © Larsen & Toubro Infotech Ltd. 25

• Broker is high-speed message router.

Working with Broker:

Point-to-Point: The role of the document

Publish-Subscribe: The role of the document

Confidential | Copyright © Larsen & Toubro Infotech Ltd. 27

• webMethods Trading Networks is an optional add-on component that runs on the

Confidential | Copyright © Larsen & Toubro Infotech Ltd. 29