You are on page 1of 228


Knowledge Update 6 ->

Revised 03-DEC-2007

This publication is protected by international copyright law.

law All rights
reserved. No part of this publication may be reproduced, translated, stored
in a retrieval system, or transmitted in any form or by any means,
electronic, mechanical, photocopying, recording or otherwise, without the
prior permission of Software AG. webMethods, webMethods Administrator,
webMethods Broker, webMethods Dashboard, webMethods Developer,
webMethods Glue, webMethods Fabric, webMethods Installer, webMethods
Integration Server
Server, webMethods Mainframe
Mainframe, webMethods Manager
webMethods Mobile, webMethods Modeler, webMethods Monitor,
webMethods Optimize, webMethods Trading Networks, webMethods
Workflow, and the webMethods logo are trademarks of Software AG. All
other marks are the property of their respective owners.

Page 2
Welcome to Software AG Training!

Housekeeping Items
ƒ Class hours
ƒ Refreshments
ƒ Smoking
ƒ Restrooms
ƒ Emergency exits
ƒ Sign-in sheets

Page 3
So Everyone Benefits…

ƒ Turn off/silence cell phones and pagers
ƒ Check e-mail only at breaks
ƒ Refrain from side discussions – we all want to hear what you have to say!
ƒ Feel free to ask questions during the lecture – if your question is off-topic
or will
o w ll be covered
cove ed late
later in tthe
e lectu
e, we
ll w
te itt o
on tthe
e boa
d to be
sure we cover it

Page 4
Course Agenda – Day 1

ƒ Architecture Overview
ƒ Component Startup
ƒ Integration Server
ƒ Trading Networks
ƒ Broker

Page 5
Course Agenda – Day 2

ƒ BPM Components
ƒ BAM Components
ƒ SOA Components
ƒ Wrap Up

Page 6
Workshop Structure

Structure (for each module): If you are going

i tto struggle,
t l we
want you to struggle here in class,
ƒ Lecture not back on your project!

ƒ Demo led by the instructor Tryy things

g out in class – ask yyour
instructor or fellow students if you
– Feel free to follow along… get stuck.
– Time limit will be adhered to!
ƒ Software AG provides comprehensive documentation
documentation, online help
help, and
samples. Please use these resources during the workshop.

Page 7
Day 1

Page 8

Architecture Overview
Component Startup
Integration Server
Trading Networks

Page 9

At the end of this lesson

lesson, you will be able to:
ƒ Explain the webMethods product suite for version 7.1
ƒ Understand how the various components relate to each other
ƒ Define how webMethods components solve enterprise challenges
ƒ Relate older versions and names to current versions and names

Page 10
The Enterprise Environment

ƒ Software AG recognizes key challenges faced by today’s

– The need to Integrate applications and partners essential to the
’ business
b i (ESB)
– The need to deliver agility and lower maintenance costs by exploiting
Service-Oriented Architecture (SOA)
– The need to streamline and improve business processes through
Business Process Management (BPM)
ƒ To address these challenges, the Software AG webMethods suite
7.1 is designed to facilitate and deliver the convergence of ESB,
BPM, and SOA – all monitored by a unified Business Activity
Monitoring (BAM) environment!

Page 11
Software AG webMethods Business Integration Platform

Page 12
Enterprise Integration and B2B

ƒ Enterprise Integration and B2B are part of the webMethods 7.1

Enterprise Service Bus.
ƒ The webMethods ESB provides:
– Central middleware and integration infrastructure
– Supports multiple communications protocols for connections to
various systems
ƒ ESB consists of:
– Integration Server
– Trading Networks
– Broker
– Adapters,
p , Industryy Adapters
p & Solutions
– Interfaces for process management, monitoring, rules & presentation

Page 13
Service Oriented Architecture

ƒ webMethods 7
1 offers complete end
to end life-cycle
life cycle
management: from design-time to run-time to change-time.
– Messaging
– Management
– Registry
– Security
– User interaction
ƒ SOA permeates all of the webMethods 7.1 architecture
– ESB hosts and proxies services
– CentraSite provides registry, repository, and governance

Page 14
Business Process Management

ƒ BPM automates end-to-end

end to end business transactions
transactions, coordinating
people and systems in formalized interactions.
– People interactions include tasks such as approval, review, exception
h dli
handling, and
d manuall procedures.
ƒ The following webMethods components implement BPM:
– Designer:
g for designing
g g processes,
p , tasks,, and user interfaces
– Process Engine: for executing automated processes
– Task Engine: for implementing task interaction between users and
– Monitor: for monitoring process and service activities and
– My webMethods Server: centralized configuration,
configuration administration and

Page 15
Business Activity Monitoring

ƒ BAM analyzes real-time

real time information and provides actionable data
and insight. This is done through:
– Key Performance Indicators to define vital information to gather
– Analysis to learn normal behavior and correlate data
– Rules to represent conditions, alerting, and corrective action
– Prediction to find potential problems before they happen
ƒ These capabilities are offered in webMethods 7.1 through the
Optimize products:
– Optimize
O for
f Infrastructure
– Optimize for Process
– Optimize for SAP
– Optimize for B2B

Page 16
webMethods Suite Capabilities

Business Business Process Management and Applications SOA

Activity Governance
Monitoring Process Application
Design & Execution Composition

Business Registry &

Analytics Repository

Process Enterprise Integration Policy Design and

y Enforcement

System Enterprise Legacy Roles and

Analytics B2B Service Bus Modernization Responsibilities

Service Lifecycle
Monitoring Management

Partners Apps Databases App Servers Mainframes

Page 17
webMethods Suite Components

Business Business Process Management and Applications SOA

Activity Governance
Monitoring Process Engine / Task Engine Enterprise Application Composer

Optimize for Enterprise Integration
Process X-Broker

Optimize for Integration Server Legacy

Infrastructure TN Broker Modernization Lifecycle


Partners Apps Databases App Servers Mainframes

Page 18
webMethods 7 Architecture: Service Bus

Business Process Integration Solution

Applications & Partners


Integration Rules Analytics Process Presentation


Service Bus


Design & Management &

Web Services

Development Governance Monitoring

3rd Parties

Metadata Registry/ Event

Library Repository Data

App Servers

Page 19
Service Bus

ƒ The Enterprise Service Bus (ESB),

(ESB) provides:
– Central middleware infrastructure
– Supports multiple communications protocols
ƒ Consists of:
– Integration Server
– Trading
T di Networks
N t k
– Broker
– Adapters, Industry Adapters & Solutions
– Interfaces for process management, monitoring, rules & presentation

Integration Rules Analytics Process Presentation

Service Bus

Page 20
Service Bus
Integration Server

ƒ Primary service execution runtime component of the webMethods

Service Bus
ƒ Hosts:
– Adapters (JDBC, JMS, WebSphere MQ, etc)
– Process Engine for process execution
– Monitor package for Service
Service, Document & Process auditing
– Industry Adapters & Solutions packages (EDI, RosettaNet, etc)
– Runtime environment for Fair Isaac Blaze business rules engine
– Data collector for Optimize analysis engine

Integration Rules Analytics Process Presentation

Service Bus

Page 21
Service Bus
Trading Networks

ƒ Trading Networks
– Simplified B2B integration via Trading Partner profiles, document
recognition, processing rules
– Central gateway for both XML & flat-file formats, including EDI
– Transaction auditing
ƒ Broker
– Scalable, high-speed messaging backbone for webMethods Suite
– Asynchronous, guaranteed message delivery & routing
– Built-in JMS provider for standards-based messaging

Integration Rules Analytics Process Presentation

Service Bus

Page 22
Service Bus

ƒ Accelerate development by providing a common interface to

disparate systems Packaged

ƒ Isolate resources from change, provide error detection and

recovery, support end-to-end
d d transactionality
l Databases

ƒ Available for most major Enterprise Resource Planning (ERP),

Customer Relationship Management (CRM), Messaging & Mainframes

Integration systems
ƒ Industry Adapters & Solutions Partners

– Simplified integration with industry-specific

industry specific standards (HIPAA,
UCCNet, EDIINT, RosettaNet, etc)

Integration Rules Analytics Process Presentation

Service Bus

Page 23
webMethods 7 Architecture: Design and Development

Business Process Integration Solution

Applications & Partners


Integration Rules Analytics Process Presentation


Service Bus


Design & Management &

Web Services

Development Governance Monitoring

3rd Parties

Metadata Registry/ Event

Library Repository Data

App Servers

Page 24
Design and Development

ƒ Development environment for

webMethods Integration Server services
ƒ Supports both codeless (Flow) &
coded development (Java
(Java, C)
ƒ Integrated with Version Control
webMethods Integration
Systems (VCS)

webMethods VCS

Design &

Page 25
Design and Development

ƒ Unified Eclipse-based
Eclipse based development environment for:
– Business Process models
– User-centric workflow Tasks
– User Interfaces (UIs), including those for Tasks
ƒ Perspectives for Business Analysts, Process Developers,
Process Debuggers & My webMethods Task & UI developers
ƒ Provides a single interface for the full business process application
development lifecycle

Design &

Page 26
Design and Development
My webMethods Server

ƒ Unified presentation layer for webMethods Suite

– Monitor Processes, Tasks, Integrations & Documents
– View system & business analytics
ƒ Integrated task engine for user-centric Task distribution &
ƒ Standards-based
Standards based UI development
– Java Portlet Specification (JSR 168)
– Java Server Faces

Design &

Page 27
Design and Development
Metadata Library

ƒ Common asset library for re-

use and faster development
ƒ Accessible from development
l such
h as the
h Designer
– Allows drag and drop usage of
ƒ Contains published assets
throughout the environment

Design &

Page 28
webMethods 7 Architecture: Governance

Business Process Integration Solution

Applications & Partners


Integration Rules Analytics Process Presentation


Service Bus


Design & Management &

Web Services

Development Governance Monitoring

3rd Parties

Metadata Registry/ Event

Library Repository Data

App Servers

Page 29
CentraSite Editions and X-Broker

Enterprise Edition Governance Edition X-Broker

ƒ Service
S i lif lifecycle
l & ƒ SOA lifecycle
lif l ƒ Integrated
I t g t d run-time
meta data management governance enforcement

ƒ Extensible data model ƒ Powerful Active ƒ Service virtualization

ƒ Native XML support policies
li i and
d mediation
di ti

ƒ Artifact life cycle ƒ Design, change & run ƒ Run-time policy

management time policy enforcement
management ƒ WS-Security
ƒ Pluggable AJAX UI
ƒ Service Contracts ƒ Monitoring & Logging
ƒ Graphical impact
analysis ƒ Comprehensive UDDI ƒ SLA Enforcement
v2, v3 registry support
ƒ Flexible &
customizable reporting ƒ B2B SOA

ƒ Eclipse Support Governance

Page 30
webMethods 7 Architecture: Management & Monitoring

Business Process Integration Solution

Applications & Partners


Integration Rules Analytics Process Presentation


Service Bus


Design & Management &

Web Services

Development Governance Monitoring

3rd Parties

Metadata Registry/ Event

Library Repository Data

App Servers

Page 31
Management & Monitoring
My webMethods Server

ƒ Interconnected
I t t dddomains
– Services
My webMethods
– Tasks
– Processes
– Partner Interactions
ƒ Unified interface

Service Audit Process Audit Task Audit

Networks Audit

Management &

Page 32
Management & Monitoring

ƒ Event data received from

My webMethods environment
ƒ Advanced monitoring and
– Infrastructure for systems
– Process for business
Analysis DB processes
– B2B for partner interactions

f t t
ƒ Monitoring
g interaction
Data Collector Broker WS Data
Collector – Rules
– Prediction
webMethods webMethods External – Alerts
System Agents Processes Processes and
– Web service actions
Management &
Systems Monitoring

Page 33
webMethods 7 Architecture: Unified Solution

Business Process Integration Solution

Applications & Partners


Integration Rules Analytics Process Presentation


Service Bus


Design & Management &

Web Services

Development Governance Monitoring

3rd Parties

Metadata Registry/ Event

Library Repository Data

App Servers

Page 34
webMethods Version Overview

Current Previous

ƒ Developer 7.1 ƒ Developer 6.5

ƒ Trading Networks Console 7.1 ƒ Trading Networks Console 6.5
ƒ Designer 7.1 ƒ Designer 7 / Modeler / Workflow
Designer / Portal Designer

ƒ Administrator 7.1
71 ƒ Administrator 6.5

ƒ MWS Console 7.1 ƒ MWS Console 7

Page 35
webMethods Version Overview

Current Previous

ƒ Integration Server 7.1 ƒ Integration Server 6.5

ƒ Trading Networks 7.1 ƒ Trading Networks 6.5
ƒ Broker 7.1 ƒ Broker 6.5
ƒ My webMethods Server 7.1 ƒ My webMethods Server 7
ƒ Metadata Library 7.1
71 ƒ Metadata Library 7
ƒ Optimize for Process 7.1 ƒ Optimize for Process 7
ƒ Optimize for Infrastructure 7.1 ƒ Optimize for Infrastructure 7 (also
Manager 6)

ƒ Optimize for B2B 7.1 ƒ N/A

ƒ CentraSite Governance Edition 7.1 ƒ Infravio X-Registry 6.6

ƒ X-Broker 7.1 ƒ Infravio X-Broker 6.6

Page 36

Architecture Overview
Component Startup
Integration Server
Trading Networks

Page 37

At the end of this lesson

lesson, you will be able to:
ƒ Start and stop the various components of the webMethods 7 Suite

Page 38
Starting webMethods Components

Starting non-webMethods
non webMethods Components
ƒ Starting the Broker Server
ƒ Starting the Integration Server
ƒ Starting My webMethods Server
ƒ Starting the Optimize Analytic Engine
ƒ Starting the Optimize Prediction Engine
ƒ Starting the Infrastructure Data Collector
ƒ S
i the
h Web
W b Services
S i D
Data C
ƒ Starting the MetaData Library
Open tools to verify

Page 39
Start/Stop the Broker Server

ƒ Start and stop from the command line:

– /Broker/bin/broker_start –switch server[:port]
– /Broker/bin/broker_stop –switch server[:port]

ƒ Start and stop as a Windows service:

ƒ Start / stop / restart from My webMethods

Page 40
Start/Stop the Integration Server

ƒ Start
St t from
f th
the command
d li
– /IntegrationServer/bin/ | bat –switch –switch

ƒ Start as a Windows service:

ƒ Stop/restart from the Administrator

Page 41
Start/Stop My webMethods Server

ƒ Start and stop from the command line:

– /MWS/bin/ | bat –s Default start
– /MWS/bin/ | bat –s Default stop

ƒ Or start and stop as a Windows Service

ƒ MWS is
i ddependent
d on the
h completed
l d startup off the
h ddatabase

Page 42
Start/Stop the Optimize Analytic engine

ƒ Start and stop from the command line:

– /optimize/analysis/bin/ | bat
– /optimize/analysis/bin/ | bat

ƒ Or in Windows:
– Via Services (will start in background)
– Start Menu icons (will start in foreground)

Page 43
Start/Stop the Optimize Prediction Engine

ƒ Start/stop from the command line:

– /optimize/prediction/bin/ | bat
– /optimize/prediction/bin/ | bat

ƒ Windows:
– Via Services (will start in background)
– Start Menu icons (will start in foreground)

Page 44
Start/Stop the Web Service Data Collector

ƒ Start/stop from the command line

– /optimize/dataCollector/bin/
| bat
– / ti i /d t C ll t /bi / h td
h | b

ƒ Windows:
– Via Services (will start in background)
– Start Menu icons (will start in foreground)

Page 45
Start/Stop the Infrastructure Data Collector

ƒ Start from the command line:

– /IntegrationServer/bin/ | bat –switch –switch

ƒ Stop and restart from the Administrator

ƒ IDC is a highly modified version of the IS
– Default port of 5555
– Default
D f lt diagnostic
di ti portt off 9999
ƒ Modify the above if starting the IDC on a physical host with an
installation of the Integration Server

Page 46
Start/Stop the Metadata Library

ƒ Start from the command line:

– /MetadataLibrary/library/bin/ | bat
ƒ Or start and stop
p as a Windows Service

Page 47
Demo 1: Component Startup

Page 48

Architecture Overview
Component Startup
Integration Server
Trading Networks

Page 49

At the end of this lesson

lesson, you will be able to:
ƒ Understand the new features in the 7.1 Integration Server

Page 50
Integration Server Overview

ƒ Integration Server is the central run-time

run time component of the
Enterprise Server Bus.
ƒ Robust, standards-compliant platform
ƒ Responsible for:
– Run-time execution of flow and java services
– Supporting data transfer between systems via hosted adapters
– Hosting process engine for BPM
ƒ Previous version: 6.5

Page 51
New in Integration Server Version 7.1

1 Enhanced web services support

2. Interoperable standards support (WS-I, SOAP 1.2, MTOM/XOP,
WS-Security 1.0)
3. Enhanced protocol support
4. Improved XML schema support
5 Native
5. N i JMS messaging
6. Centralized user management
7 Refined clustering
8. Additional features

Page 52
1 Enhanced Web Services Support

ƒ Web service descriptors

ƒ Developer features
ƒ Web services security

Page 53
Web Service Descriptor

ƒ Web service descriptor (WSD) defines a Web service in IS terms

– Two basic types of web service descriptor
ƒ Provider WSD defines a web service for external consumers
ƒ Consumer WSD defines an external web service and is used to
create a web service connector (WSC) for each operation in the
web service
ƒ A WSC is like any other IS flow service
– when a connector is invoked it calls a specific operation of a Web

Page 54
Creating Web Service Descriptors

ƒ Provider Web Service Descriptors

– Created from one or more IS services or a WSDL document.
– Developer uses the provider Web service descriptor to publish these
IS services to a UDDI registry as a single Web service.
– External users (requesters or consumers of the service) can then find
the Web service on the registry and invoke the IS services remotely
ƒ Consumer Web Service Descriptors
– Created from a Web Service (published to a registry) or from a WSDL
– Developer uses the consumer Web Service Descriptor to invoke and
use a remote Web Service similar to other IS Services

Page 55

ƒ Each operation contains a single request and response

ƒ Each request and response contains a single, read-only body element
and one or more header elements
ƒ A response can also contain fault elements
ƒ Add one to many operation(s) to a provider WSD
ƒ Consumer
C WSD is
i ddefined
fi d bby th
the WSDL and
d can nott b
be edited
dit d

Page 56

ƒ A binder is a collection of related definitions and specifications for

a particular port
ƒ The binder is a container for the endpoint address, WSDL binding
l transport protocol,l and
d communication protocoll
ƒ Developer creates at least one binder when it generates the Web
service descriptor based on the data in the WSDL or service
ƒ New binder definitions can be added to a provider Web Service
Descriptor created from an IS service
ƒ New binders can *not* be added to a consumer or provider Web
Service Descriptor created from a WSDL URL or a UDDI Registry
ƒ Separate binders can be defined for endpoint address and protocol
i f

Page 57
Web Services Descriptor Nodes

1 Create WSD

2. Create WSD

Page 58
WSD Node Summary

ƒ Web service descriptor (WSD) node

– Define more than a single operation within each WSD
– Provide a URL to acquire WSDL for an IS WS (unique end point for a
– Easier support for document/literal style messages
– Generate
Ge e ate Web SeService
v ce Co
ecto s from
o WS
ta g sc
e as
with recursive definitions and other schema constructs
– Support Dynamic Endpoints for Web Service Connectors
ƒ Define “Aliases”
Aliases to be used with Dynamic endpoint addressing for both
outbound WSC and during WSDL generation of Provider WSD’s
ƒ Additional standards support through WSD
– Support for WS-Security
WS Security on WS invocations (Inbound and Outbound)
– Embedded WS-I compliance tool
Page 59
Developer Features





Page 60
Developer Features


M lti l


Page 61
Developer Features

ƒ Robust Web Services Support

– Provider and Consumer specific
– Enforce WS-I compliance
– Support for custom headers and faults
– WSDL-first development (generate
service stubs complete with signatures)
– Multiple invocation options
ƒ Focus on Ease of Use
– Wizard driven WSD creation
– Drag/Drop
g p existing
g services as operations
– Drag/Drop web services from UDDI
– Out of box selection of security policies
ƒ Designed for Easy Deployment
– Alias based dynamic end point definition

Page 62
Demo 2: Create Producer and Consumer WSD

Page 63
Web Services Security

ƒ The WS
Security facility is a message
based implementation that
provides end-to-end network coverage
ƒ Transport-based implementation (ex. HTTPS) the credentials and
h information
f secure the
h endpoints
d off a connection
ƒ Message-based implementation (ex. WS-Security) the signing and
encryption are implemented at the individual message level

Page 64
Web Service Security Standards

ƒ The Integration Server WS-Security

WS Security facility follows the guidelines
of the WS-Security, version 1.0 standards for: SOAP Message
– Security
– Username Token Profile
– X.509 Certificate Token Profile

Page 65
Message Direction

ƒ Configuring message-level
message level security must be categorized as either
inbound or outbound
ƒ Authorization properties can only be applied to messages flowing
in inbound
b d or outbound
b d

Page 66
Securing Web Service Providers and Consumers

1. The Web service

consumer constructs
an outbound request
and sends it to a Web
service provider

2. The provider receives

the inbound request

3. The provider
constructs an
outbound response
and sends it back to
the consumer

4. The consumer
receives the inbound
response from the

Page 67
Outbound & Inbound Messages

1. When implementing
WS-Security you
configure the security
settings for a Web
Service consumer or
provider’s inbound
and outbound

Page 68
2 Interoperable Standards Support

ƒ Interoperability (WS-I)
(WS I)
– Basic Profile (BP) 1.1
– Simple Soap Binding Profile (SSBP) 1.0
ƒ Security (WS-Security 1.0)
ƒ Invocation (SOAP 1.2)
ƒ Registry (UDDI v3 browse/publish)
ƒ Attachments (MTOM/XOP in SOAP 1.2)
ƒ Header Handlers (JAX-RPC
(JAX RPC header support)
ƒ Application Server Interoperability (JMS JCA)

Page 69
UDDI v3 Publish / Subscribe

ƒ Developer UDDI v3 Registry publish and browse

ƒ Developer integrates with the X-Registry
ƒ Search for web services in registry from developer
ƒ 3rd Party UDDI v3 registry (preliminary testing w/CentraSite)
ƒ Generate WS connectors for web services that are in a UDDI v3
g y via Wizard and/or drag
registry g & drop
ƒ Publish to UDDI registry from WSD node

Page 70
3 Enhanced Protocol Support

ƒ Upgraded HTTP stack

ƒ Upgraded SOAP stack
ƒ New C# broker client API

Page 71
Upgraded HTTP Stack

ƒ New HTTP 1
1 support provides 2 key features
– Persistent Connections
– Streaming Support
ƒ The Reverse Invoke Server is now called the Reverse HTTP
Gateway and will provide streaming support for documents sent
thru this gateway
ƒ The proprietary SOCK/SSLSOCK protocol will be replaced with
HTTP/HTTPS 1.1 protocol
ƒ Advanced port configuration options will allow users to:
– Suspend/Resume ports
– Configure a backlog queue for suspended ports
– Throttle the rate of acceptance of new connections
– Optionally define a private thread pool per port
Page 72
Upgraded SOAP Stack

ƒ New SOAP processor

– SOAP 1.1 and 1.2
– Custom SOAP faults supported (inbound and outbound)
– Custom SOAP headers supported

Page 73
SOAP Processor

ƒ The SOAP processor is a service that acts upon SOAP messages

ƒ Integration Server receives a SOAP message, it invokes the SOAP
processor based on the process directive specified in the URL
requesteddbby the
h client
ƒ The SOAP processor routes messages to services based on a
qualified name (QName).
ƒ If the SOAP message includes an HTTP header, the QName is
derived from the SOAPAction (SOAP 1.1) or ActionHTTP (SOAP 1.2)
ƒ If the SOAP message does not include an HTTP header
header, the QName
is derived from the first element in the SOAP body.

Page 74
SOAP Messages with the Integration Server

1. The HTTP Client

Posts a SOAP
Document to the
Integration Server

2. The SOAP M
Th Message
Handler Invokes
the Appropriate
SOAP Processor

3. The SOAP Processor

Performs Work and
Generates a

4. The Message
Handler Returns
the Response to
the Client

Page 75
Web Services Fault Handling

ƒ The SOAP specification defines one body element named Fault

ƒ Recipient must return the Fault element if it cannot process a
SOAP message successfully
ƒ Integration Server can add a document to the fault message

Page 76
Web Services Header Handling

ƒ SOAP message can include an optional header component to store

additional information
– Example: Routing invoices through one or more approval steps before
i it to
t an accounts-payable
t bl processor, th
the h
d could ld h
the document’s routing information.
ƒ Integration Server provides services to register header handler
ƒ Two main types: Provider and Consumer header handlers

Page 77
Web Services Header Handling

1 Header Attributes:
ƒ actor
ƒ mustUnderstand

SOAP 1.2 Header Attributes:

ƒ encodingStyle
ƒ role
ƒ mustUnderstand
ƒ relay

Page 78
Demo 3: SOAP Fault Document

Page 79
4 Improved XML Schema 1.0
4. 1 0 Support

ƒ Recursive Complex Types

– Expanding on current support
ƒ Redefines
– New XML schema can be derived from an existing schema by
selectively redefining components in the original schema
ƒ Chameleon Includes
– This XML Schema feature allows an XSD with no target namespace to
be included by an XSD that has a target namespace
ƒ Substitution
S b i i G Groups
– Allows elements from a substitution group to be substituted for a
declared element (the head of the substitution group) in an XML
i t
instance d

Page 80
5 Native JMS Messaging

ƒ Native JMS messaging allows IS to directly

– publish JMS documents
– subscribe to JMS queues and topics
ƒ JMS publish
bli h will
ill b
be d
done via
i new W
P bli services
ƒ JMS subscribe will be done via new JMS triggers
ƒ Broker JMS provider and WebSphere MQ will be certified out of
the box
– Certifications for JBOSS, WebLogic, and Sonic planned
ƒ Broker
B k JMS ffriendly
i dl ffeatures
– ability to bypass JNDI for Broker configuration
– JMS extensions enable compression
p and message
g streaming

Page 81
Integration Server & Broker Sample Configuration

1. The Integration
Server and the Broker
share a fast, efficient
process for
documents across the
entire webMethods

Page 82
JMS Message Styles

1. JMS supports the

Point-to-Point: Queue (pub-sub) and
point-to-point (PTP)
messaging styles

Pub/Sub: Topic

Page 83
Sending a JMS Message

1. Integration Server
public services for
sending JMS messages

Page 84
Receiving a JMS Message

ƒ JMS trigger specifies the destination (queue or topic) on a JMS

ƒ JMS trigger contains routing rules, which specify the service that
Integration Server invokes
k to process a message
ƒ JMS trigger contains filtering rules
ƒ JMS trigger contains joins
ƒ JMS trigger contains different Acknowledgment Modes

Page 85
Demo 4: JMS Messaging

Page 86
6 Centralized User Management

ƒ Centralized user store that IS, MWS, BPMS runtimes can

authenticate requests from a single directory service
ƒ Integration Server can use LDAP, local, or CDS for user
ƒ Centralized user store is selected, users can map IS ACLs to roles
defined in MWS
ƒ C
li d user store will
ill allow
ll TN 7
1 to d
fi and
d use
credentials defined via MWS

Page 87
7 Refined Clustering

ƒ All Persistent storage to a DB (Oracle, MS SQL, etc.)

ƒ All in memory storage managed by Tangosol
ƒ IS Scheduler re-factoring to improve performance in a clustered
ƒ File polling listener now cluster aware
p v2 server is replaced
ƒ Repo p with a 3rd p
partyy OEM p
(Standalone Only)
– Guaranteed Delivery
– Key Cross Referencing
– Trigger Joins
– Client Certificate Mapping

Page 88
8 Additional Features

ƒ Metadata Library access

ƒ Version Control
ƒ Logging

Page 89
Metadata Library Access

ƒ Configure location/access of Library

ƒ Select and Deploy assets to be extracted from Integration Server
to the Metadata library
ƒ Sync up of changes since last extraction
ƒ Enforce IS security model on assets viewed thru Library
ƒ D
i users will
ill h
have access to diff
different views
i which
hi h will
ill allow
different tasks to be performed

Page 90
Version Control and Logging

ƒ Version Control
– ClearCase support added to VCS
– Visual Source Safe already supported
ƒ Log4J-Based Journal Logging
– Journal logging (server.log) in webMethods Integration Server 7.1 has
been enhanced to support Log4J
based facilities logging

Page 91

Architecture Overview
Component Startup
Integration Server
Trading Networks

Page 92

At the end of this lesson

lesson, you will be able to:
ƒ Understand the new features in 7.1 Trading Networks

Page 93
Trading Networks Overview

ƒ Trading Networks is an add-on

add on component to the Integration
ƒ Designed to provide partner management
– Profiles
– Document types
– Processing rules
ƒ Acts as a single point of entry for incoming documents
ƒ Previous version: 6.5

Page 94
New in Trading Networks Version 7.1

1 Distribution of run-time
1. run time and design-time
design time activities
2. Role-based transaction monitoring
3. Role
based partner administration
4. Improved search

Page 95
1 Distribution of Activities

ƒ Run-time
Run time activities now through MWS
– Transaction monitoring
– Activity monitoring
– Task monitoring
ƒ Administration activities now through MWS
– Partner
P t profiles
– Profile groups
– Queue management
ƒ Development activities remain in TN Console
– Document Types
– Processing
P i Rules
R l
– TPAs
Page 96
2 Role
2. Role-based
based Transactions Monitoring…

ƒ Monitor through My WebMethods (MWS)

– Transactions
– Tasks
– Activities
ƒ Role based access
– Screen level access
– Functional Permissions
– General functional permissions
ƒ Data level security
– Profiles
– Profile Groups
– Document Types
ƒ Basic Search
– Number and String operators (Equals,
(Equals Not equals
equals, Less than
than, Greater than
– Implicit “AND” condition between fields
Page 97
Role based Transactions Monitoring…

ƒ Advanced Search
– Search on one or more values within a field
– Apply “AND” or “OR” condition between fields
– Dynamic partner search criteria specification
– Query level customization of transaction results
ƒ Saved Searches
– Public and Private searches
ƒ User level customization of transaction search results
– Column display
– S t order
Sort d
– # of transactions
ƒ Transactions View
– C t l number
Control b off ttransactions
ti resubmitted/reprocessed
b itt d/ d att any iinstance
– View related documents more clearly in a tree structure

Page 98
Role based Transactions Monitoring

ƒ Transactions Details View

– Save content to hard drive
– Edit and resubmit transaction
– Add/Edit comments for a
– Audit
ud t trail
t a l of
o changes
c a ges to
– Edit User Status
– Send link to the transaction

Page 99
Demo 5: Partner User Role

Page 100
3 Role
3. Role-based
based Partner Administration…

ƒ Monitor through My WebMethods (MWS) UI

– Profiles
– Profile Groups
– Public Queues
ƒ Role based access
– Screen level access
– Functional Permissions
– G
l ffunctional
ti l permissions
i i
ƒ Data level security
– Profiles
– Profile Groups
ƒ Keyword Search
ƒ Advanced Search
– Search on one or more fields
– Apply “AND” or “OR” condition between fields
– Number and String operators (Equals, Not equals, Less than, Greater than, etc.)

Page 101
Role Based Partner Administration

ƒ Partner Certificate Search

– Search expired or about to expire certificates
ƒ Audit Trail of changes
g to partner
p p
ƒ Logged in Activity log
ƒ Suspend documents prior to
d li
ƒ Flexible partner/user mapping

Page 102
Role Based Access Summary

ƒ Role based access enables:

– Which screens does a user have access to?
– What functions can a user perform within the screens they have
access to?
– What other general functions can a user perform?
ƒ Data level security enables:
– Which partner transactions are visible to the user?
– What types of transactions (Invoices, Purchase orders, etc.) are
visible to the user?

Page 103
Demo 6: Admin Role

Page 104
4 Improved Search
4. Search…

ƒ Basic Search
– Type ahead for quick field selection
– Number and String operators (Equals, Not equals, Less than, Greater
than, etc.)
– Implicit “AND” condition between fields
– Sea
c using
us g p
e de ed custo date ranges
a ges
ƒ Advanced Search
– Search on one or more values within a field
– Apply “AND” or “OR” condition between fields
– Dynamic partner search criteria specification
– Search using pre
defined/custom date ranges
– Query level customization of transaction results

Page 105
Improved Search

ƒ Saved Searches
– Public searches visible to all users
– Private searches only available to users who created them
ƒ Transaction search results display
– User driven customization
– C
t i column
l di
l sortt order
d and
d number
b off ttransactions

Page 106
Demo 7: Enhanced Search in TN

Page 107

Architecture Overview
Component Startup
Integration Server
Trading Networks

Page 108

At the end of this lesson

lesson, you will be able to:
ƒ Understand the new features in the 7.1 Broker Server and Broker

Page 109
Broker Server Overview

ƒ Broker Server hosts the primary mechanism for messaging

between webMethods components.
– Broker messaging via publish and subscribe
– JMS messaging via JMS publish and subscribe
ƒ Broker servers:
– Host brokers
– Are started by broker monitors
ƒ Previous version: 6.5

Page 110
New in Broker Server Version 7.1

ƒ Auditing
– Enhanced auditing capabilities that enable administrators to manage and log Broker
configuration changes
ƒ SSL Upgrade
– Entrust (for Java)
– Open SSL (for C)
– MS Crypto (for C#) (provides SHA256 and FIPS encryption and open standards)
ƒ Configuration
– Configurable remote Broker Server batch size
– Manually configurable monitor and server IP address and port
ƒ Java Connector Architecture ((JCA)) support
pp to access the Broker JMS
ƒ Suspend Publish
– Refuses any new documents to be published while keeping subscribers connected
ƒ Client features
– New C# Broker client API
– Access Labels extended support for JMS and C# clients

Page 111
Configurable During Installation

Page 112
Broker High Availability

ƒ New scripts and procedures

– Simple approach to start, stop, and monitor application
ƒ Same Active/Passive approach
– Store the application
application’ss state information and data on a shared disk
– Survive a crash and restart/rollover to a known state
– Resolve host name dependencies
ƒ There are three task categories when setting up webMethods Broker to
run in an HA cluster environment:
– Cluster hardware and software (for example, Veritas, HP ServiceGuard, IBM
HACMP or Sun Cluster)) installation p
performed byy cluster installation
– webMethods Broker and HA script installation performed by a Software AG
Professional Services representative
– System and network administration tasks performed by the user’s system

Page 113
Day 2

Page 114

Optimize for Infrastructure

Optimize for Process
Optimize for B2B
BPM Components
SOA Components
Wrap Up

Page 115

At the end of this lesson

lesson, you will be able to:
ƒ Understand the new features in 7.1 Optimize for Infrastructure

Page 116
Optimize Overview

ƒ webMethods 7 7.1
1 Optimize provides the Business Activity
Monitoring (BAM) capability of the webMethods 7 platform.
– Optimize for Process
– Optimize for Infrastructure
– Optimize for SAP
– Optimize for B2B
ƒ Optimize runs within, monitors, and interacts with the entire
webMethods 7 platform.
ƒ Previous versions:
– 6.5 Manager
– 7.0 Optimize
p for Process

Page 117
What are the Optimize Differences?

ƒ Optimize for Infrastructure

– Monitors system components, such as the IS, Broker, Adapters
– Tracks operational data
– Alerts on errors and rule violations
ƒ Optimize for Process
– Monitors
M it b i
business process instances
i t
– Track business key performance indicators
– Alerts on errors and rule violations
– Enables the use of Six Sigma by measuring defects in business
ƒ Optimize for B2B
– Monitors B2B documents (XML, EDI, etc.) and attributes
Page 118
New in Optimize for Infrastructure 7.1

1 Architecture
2. Scalability and Reliability
3. Version Support
4. Usability Features
5. Updated Administrator

Page 119
1 Optimize 7.1
1. 7 1 Architecture

Web Service Infrastructure

Data Collector Data Collector


Analytic engine Analytic engine

DB Prediction engine

y webMethods

Page 120
Infrastructure Data Collector…


Data Collector

Web Service
Data Collector

SNMP Agents
Analytic engine Analytic engine

DB P di ti
Prediction engine

My webMethods

Page 121
Infrastructure Data Collector

Infrastructure Data Collector

Broker Server Data Collector Module

Ser er

Integration Server Data Collector Module

Infrastructure Data Collector Module

IS Resource Module

ART Resource Module


TN Resource Module

Common Data Collector

SNMP Data Collector Module

Page 122
2 Scalability and Reliability

ƒ Scalability
– From 3500 managed objects in Manager, now…
– Single InfraDC instance and single Analytic Engine Instance able to
monitor 5000 Components/16k KPIs
– Single InfraDC instance and cluster of two Analytic Engines able to
monitor 7500 Components/23K KPIs
ƒ Extensibility and Maintenance Improvements
– Common data collector component abstracts data collection from
p of resource monitoring
ƒ Reliability Improvements
– Shared model with Optimize Analytic engine
– Addresses sync issues from previous releases

Page 123
3 Version Support

ƒ Out of the box monitoring (no fixes required)

– IS 7.1
– All supported versions of the Broker
ƒ New monitoring packages required (WmISExtDC, WmARTExtDC)
– IS 6.5 and 6.1 require a fix containing the packages
ƒ Not
N yet supported
d ffor monitoring
i i iin 7
– Mainframe
– Workflow 6.5
– DotNet
ƒ Coming soon (on or around SP1 release)
– Territory
– Territory Gateways
Page 124
4 Usability Features

ƒ Discovery UI moved to My webMethods Server

ƒ Better search capability

Page 125
Discovery of Resources
Navigate to MWS > Administration > Analytics > Monitored Components. Select Add Asset

Page 126
Add Asset Discovery
Used to Discover a specific resource for which you know connection parameters

Page 127
Add Network Discovery
Used to discover resources in a range of IP addresses

Page 128
List of discovered assets

Page 129
Monitored Components
Select components and KPIs for monitoring.

Page 130
View Monitored Components configuration
Editing Component Type shows user what components and KPIs are currently selected for monitoring

Page 131
Add Components for Monitoring

Page 132
Add KPIs for monitoring

Page 133
System Overview

Page 134
Demo 8: Discovery, Built-In KPIs and Rules

Page 135
5 Updated Administrator Settings

Page 136
SNMP Data Collector Settings

Page 137

Optimize for Infrastructure

Optimize for Process
Optimize for B2B
BPM Components
SOA Components
Wrap Up

Page 138

At the end of this lesson

lesson, you will be able to:
ƒ Understand the new features in 7.1 Optimize for Process

Page 139
New in Optimize for Process 7.1

1 Architecture
2. Support for multiple monitor instances
3. Service Level Agreements
4. Rule enhancements
5. Derived names usage

Page 140
1 Optimize For Process Architecture

Web Service Web Service

Data Collector Data Collector


Analytic engine Analytic engine

DB Prediction engine

My webMethods

Page 141
Optimize Data Flow Through the Architecture

ƒ External Business processes and applications send data to web

service data collectors
ƒ The data collectors publish their data to the Broker
ƒ Internal Business Processes send data directly to the Broker
ƒ The analytic engines pull data from the Broker, process it and
store it in the database
ƒ The prediction engine analyzes the data from the database,
consults with the rules engine for alerts, and predicts trends
toward alerts
ƒ My webMethods Server displays all Optimize data and provides
administration interfaces for configuring the Optimize components

Page 142
Architecture Features

ƒ Monitor API Enhancements

– Various modifications and enhancements to support the
Infrastructure Data Collector as well as other webMethods products
ƒ Common Directory Services
– Standardized on a common authentication model used by
webMethods product line
ƒ Database Optimization

Page 143
2 Support for Multiple Monitor Instances

ƒ Support for Multiple Monitor Instances

– Monitor multiple Integration Servers from one MWS instance
– Most requested feature for Monitor
ƒ Prior to 7.1 this was a one to one relationship between a monitor
instance and a My WebMethods instance.
– In order to access multiple Monitor instances a user would have to
log into multiple My WebMethods server instances
– 7.1 users can use one instance of My WebMethods Server to monitor
multiple Monitor instances

Page 144
3 Service Level Agreements

ƒ Service Level Agreement (SLA) additions to Rules

– Ability to tag a rule as an SLA
– Provides context to the rule
ƒ Implementation:
– A rule can now be designated as “SLA” along with a customer
– Rule
R l List
Li t can b
be searched
h d ffor SLA
– Rule List can be searched for rules associated with a certain customer
– All rules pages provide an indication of rules with an SLA
– SLA information is included with email alerts including the

Page 145
Demo 9: Service Level Agreements in Rules

Page 146
4 Rule Enhancements

ƒ New alerts
– Reminder alerts: notification when a rule continues to stay out of
– In-Compliance alerts: notified when rule goes back into compliance
ƒ Uses derived instance names
– allows users to provide custom rule instance names including access
to the Dimensions and attributes associated with the KPI being
evaluated by the rule
ƒ Seve
ty can
ca be set for
o rules
– allows the user to associate a custom severity that is searchable and
available to actions and alerts

Page 147
Email Alert – In Compliance

Page 148
Rule Features – Rule Edit Page

Derived Name


In Compliance

Page 149
Rule Features – Rule List Page

New Status Icons


Rollover – Type
yp and Customer

Page 150
Rule Features – Problems Listing

Severity SLA Icon

Derived Rule Names

Rollover – SLA plus Customer

Page 151
5 Derived names usage

ƒ Derived names are extremely useful in uniquely identifying rule

– If the derived name field is left empty, all instances will use the
d f lt rule
default l name
– Causes confusion when there is more than one instance
ƒ Variables can be used to make the derived name distinctive. The
syntax for using variables in derived names is:
– $DimensionName.AttributeName
– where DimensionName is the first in a KPI hierarchy pair
pair, and
AttributeName is the second in the pair.
ƒ Multiple pairs can be used, each separated by a space or other

Page 152
Variables in derived names

ƒ The actual variables that can be used in a derived name depend

on the KPI evaluated by the rule.
ƒ To determine what variables you can use, do the following:
– Locate the KPI evaluated by the rule in the System Data or Business
Data page.
– Identifyy the KPI Hierarchyy associated with this KPI,, and locate the
hierarchy on the KPI Hierarchies page.
– Open the hierarchy, make a note of any pairs you might want to use
in the derived name, and enter those pairs following the syntax
described below in the Derived Name field on the Edit Rule page.

Example: Memory allocated to $AnalyticEngine.LogicalServerName

Page 153
Demo 10: Rule Features, Derived Names

Page 154

Optimize for Infrastructure

Optimize for Process
Optimize for B2B
BPM Components
SOA Components
Wrap Up

Page 155

At the end of this lesson

lesson, you will be able to:
ƒ Understand the new capabilities in 7.1 Optimize for B2B

Page 156
Optimize for B2B Overview

ƒ Real
time business activity monitoring (BAM) solution continuously
monitors your EDI, XML, and Flat File transactions
ƒ Define, track and measure Key Performance Indicators to monitor
d enforce
f service level
l l agreements, and
d measure partner
ƒ Directly integrated with webMethods Trading Networks
ƒ Automatically generates alerts based on thresholds, key data and

Page 157
New in Optimize for B2B 7.1

1 Document type monitoring

2. Standard Optimize activities

Page 158
1 Document type monitoring

ƒ As before, define a document type

ƒ As before, define and extract business attributes
– Can define custom attributes in TN console
ƒ Extraction behavior by document type:
– XML Docs
ƒ Extract business information and associate with custom attributes for
each document type
– EDI and Flat files
ƒ Associate attribute with doc type using
ƒ Invoke a service to extract values and update the attributes in TN

Page 159
Document Type Monitoring

ƒ Once defined
defined, select document types or attributes to monitor
– Monitor any B2B document (XML, EDI, etc.)
– Monitor System attributes
– Monitor Custom attributes
ƒ Finally, specify when to send event to BAM

Page 160
2 Standard Optimize activities

ƒ Define Event Maps

– Map metrics related document attributes to Facts (For example,
amounts, counts, etc.)
– Map
p “slicing”
g data byy document attributes to Dimensions ((For
example, Partner, Customer, Processing Status, etc.)
ƒ Add KPIs
– Associate Fact
– Specify collection interval (5min, 10min, 1 hour, etc.)
– Associate Dimension for slicing/dicing of KPIs
ƒ Associate KPIs to Process Tree
ƒ Define rules for problem notification
– KPI Rules evaluate KPIs
– Threshold rules evaluate a single datapoint
– Send notification emails
Page 161
Use Cases: BAM for B2B…

ƒ Business administrator:
– selects the system and business attributes within the purchase order
and invoice document types to monitor
– defines KPIs to analyze and monitor metrics
ƒ average purchase order amount by partner
ƒ average invoice amount by partner
ƒ Etc.
– defines trigger alert rules to identify problems in real-time

Page 162
Use Cases: BAM for B2B

ƒ Business analyst:
– analyzes KPIs to resolve potential problems
ƒ Average invoice amount by partner
ƒ Purchase
P h order
d volume
l b
by partner
ƒ etc.
– wants to evaluate what percentage of invoices are getting delivered
f ll by
b partner
– wants to evaluate how many attempts were made by the partner in
sending a document

Page 163
Demo 11: Monitor Attribute from Document

Page 164

Optimize for Infrastructure

Optimize for Process
Optimize for B2B
BPM Components
SOA Components
Wrap Up

Page 165

At the end of this lesson

lesson, you will be able to:
ƒ Understand the new capabilities in 7.1 Business Process Management

Page 166
webMethods BPM Overview

ƒ webMethods BPM 7.1

7 1 enables the modeling and execution of
automated business processes
ƒ The following components implement BPM:
– Designer: for designing processes, tasks, and user interfaces
– Process Engine: for executing automated processes
– Task Engine: for implementing task interaction between users and
– Monitor: for monitoring process performance and key business
– My webMethods Server: for access to monitoring and for user
interfaces to process tasks

Page 167
New in BPM 7.1

1 Simulation
2. Business calendars
3. User calendar integration
4. Task analytics
5. Task visualization
6. Simplified task editing
7. Enhanced visual editing
8 Custom
8. C categorizations
i i
9. Asset dependency visualization
10 Design-time
10.Design time KPI definitions
11.Debugger enhancements
Page 168
1 Simulation

ƒ Understand process behavior

behavior, bottlenecks
bottlenecks, costs and resource
ƒ Implemented as part of the Designer
ƒ Simulation activities happen at design-time
– Before beginning process implementation

Page 169
Simulation: Value Proposition

ƒ Learn about bottlenecks in the process

ƒ Understand the behavior of the process under various scenarios
ƒ Learn about the total cost of the process
ƒ Understand how processes utilize resources, such as people, or
ƒ C
Compare the
h b
h i ((performance,
f utilization,
ili i cost etc.)) off two
or more process models OR two or more versions of the same
ƒ Optimize processes
ƒ Visualize how processes actually work

Page 170
Simulation: Functionality…

ƒ Fully integrated simulation (in Designer)

– No import/export
ƒ Activityy based costing
– Know projected costs aggregated by process, step, resource,
– Understand the total costs of the project
ƒ Bottleneck analysis
– Recognize steps and resources that could be potential bottlenecks
ƒ Multi-process simulation
– Know how the process behaves in the context of other processes
– Simulation Perspective in Designer

Page 171
Simulation: Functionality

ƒ Reporting
– Detailed simulation statistics for further analysis
ƒ Animation with Playback
– See how the process(es) behave visually;
playback for further analysis
ƒ Scenario management
– Run various simulation scenarios
ƒ Simulation Perspective

Page 172
Demo 12: Basic Simulation

Page 173
2 Business Calendars

ƒ Scheduling and timeouts based on business time

– Process level
– Task level
ƒ Configurable business calendar based event-actions
– Escalate task five business days before expiration date
ƒ Simple
Si l calendar
l d d definition
fi i i user iinterface
f ffor administrators
d i i
ƒ Supports:
– Work days
– Holidays
– Business hours
– Time zones
– Etc.
Page 174
Business Calendars: Value Proposition

ƒ Eliminating the disconnect between business expectations and

BPM infrastructure
ƒ The disconnect that existed BEFORE this feature:
– Reality
ƒ Most businesses operate in business time
ƒ Process participants operate in business time
ƒ Service level agreements are in business time
– BPM Infrastructure
ƒ Assumes timeouts are in absolute time
ƒ Assumes schedules are in absolute time

Page 175
3 User Calendar Integration

ƒ Understand user availability before assigning work to them!

ƒ Check user availability
– Assigning
g g tasks
– Delegating tasks etc
ƒ Distribution management
– Task distribution management takes into account user availability
ƒ Calendar integration
– with Exchange
– with Domino

Page 176
User Calendar Integration: Value Proposition

ƒ Allow task owners and people managers to check for process

participant availability before re-assigning or delegating tasks
ƒ Allow automated distribution of tasks to factor-in participant
l bl b before
f distributing
d b tasks

Page 177
User Calendar Integration: Functionality

ƒ Check user availability from Task List Management (TLM)

– Principal Picker shows a calendar icon – clicking on it shows the
actual user calendar
ƒ Distribution management (in Designer)
– Task distribution management takes into account user availability
ƒ Calendar integration
– with Microsoft Exchange
– with
ith L
t D Domino
i SServer

Page 178
Demo 13: Business and User Calendars

Page 179
4 Task Analytics

ƒ Analyze task performance and people performance using

ƒ Task Key Performance Indicators (KPIs)
– Task reassignments, completions, queue time, processing time etc.
– Dimension based on task type, assignee etc.
ƒ People Analytics
– Understand average behavior
ƒ What’s average task completion count/time?
– Detect deviations
ƒ How is the task completion count/time trending?
– Take corrective action
ƒ Employee might need training on specific types of activities

Page 180
Task Analytics: Value Proposition

ƒ Same value proposition as that of Process Analytics,

Analytics except that this is
more granular
Existed in 7.0
Process Analytics Æ
Step Analytics Æ
New in 7.1
Task Analytics Æ
People Analytics
ƒ Understand average performance of tasks and people
– Joe completes 10 tasks per day
– Review tasks generally get re-assigned once in a blue moon
ƒ Detect deviations
– Joe seems to be completing 4 tasks per day
– Review tasks are getting re-assigned like crazy
ƒ Take corrective actions
– Assign the right tasks to Joe; re-train Joe etc.
– Review task distribution rules need to be revisited
Page 181
Task Analytics: Functionality

ƒ Out-of-the-box
Out of the box Intrinsic Task KPIs
– Includes user/assignee dimensions
ƒ Enabling
g Task Analytics
y thru Myy webMethods
– One click to task analytics
ƒ Fully embedded into Process Analytics (Optimize)
– Seamless user experience

Page 182
5 Task Visualization

ƒ Visual status of your Inbox and Task Lists!

– No need to sift and search thru rows and columns
ƒ Inbox visualization for task participants
p p
– Clickable charts that show the status of your inbox visually
– Easier inbox navigation
ƒ T
k Li
List M
Management (TLM) visualization
i li i for f task
k owners and
– Clickable charts that show how your tasks are distributed among
various task participants
– See the status of tasks
ƒ Point-and-click creation and configuration
g of custom charts

Page 183
Task Visualization: Value Proposition

ƒ Process participants spend more time executing tasks,

tasks not
searching for them
ƒ One glance status at the overall status of tasks (across various
b ffor Task
k Owners and
d Peoplel Managers
ƒ One glance status of the Inbox for process participants

Page 184
Task Visualization: Functionality

ƒ Configurable task charts

– View: Multiple charting options – Pie, Bar, Line etc.
– Source: Data comes from saved searches
– Clickable: Charts are clickable!; when clicked, redirect to
appropriate saved search results in TLM/Inbox
ƒ Task Charts are just portlets
– Add them anywhere – including to
your Inbox or TLM
– Add as many as you want

Page 185
Demo 14: Task Visualization

Page 186
6 Simplified Task Editing

ƒ Task editing made easy…

ƒ Intuitive and simple point-and-click interface for defining
– Task User Interfaces
– Task Assignments
– Task Events
– Task
T k Data
D t
ƒ One unified view of the task components
– Know everything
y g about the task in one g
ƒ Create Task Views, Inbox Views and Notification Views by simply
selecting business data fields
ƒ New
N ttask
k di
t ib ti methods
th d
– Round-robin, queue-length based and user-availability
Page 187
Simplified Task Editing: Value Proposition

ƒ Unified view of what constitutes a task

– None existed in 7.0
ƒ Intuitive task definition and editing
– Much simplified user experience (compared to 7.0)
ƒ Powerful “human-centric” capabilities
– More Powerful Task Routing
ƒ Distributing tasks based on queue lengths, round-robin, on availability
– Explicit Processes
ƒ Making modeling of task routing in processes easy

Page 188
Enhanced Task Editing: Functionality…

ƒ Task Summary View

… Know everything about the task implementation in ONE unified view
– Business Data
– Assignment Rules
– Events
– User Interfaces
ƒ Assignment Rules
… Task distribution made simple and more powerful
– Who is the assignee?
– When should the rule be evaluated?
– What are the conditions under which this assignment should take
– How should the tasks be distributed among various members of a
Page 189
Enhanced Task Editing: Functionality

ƒ Events
… Which events does the task respond to or generate?
– What is the event?
– What is the event configuration?
– What are the actions?
ƒ Rule Sets
… Making task assignments more explicit in the process model
– One UI implementation – and multiple Assignment & Event sets
– Multiple
p task stepsp with the same task implementation
p – but
configured with different rule sets
ƒ Configurable Views
… UI Creation made even more easier
– Simply select business data and add to task view, inbox etc.
– Custom inbox creation made easy!
Page 190
7 Enhanced Visual Editing

ƒ More drag-and-drop
drag and drop & point-and-click…
point and click
ƒ Closer to WYSIWIG
ƒ Preview User Interfaces from Designer
ƒ Point-and-click CSS definition
ƒ Preview Server
ƒ New UI Controls

Page 191
Enhanced Visual Editing: Value Proposition

ƒ Maximize developer productivity

– No need to deploy to test
– No need to deploy to preview
– No need to code up CSS styles

Page 192
Enhanced Visual Editing: Functionality

ƒ Preview User Interfaces from Designer

– How does the UI look in a browser?
ƒ Closer to WYSIWIG
– Cleaner looking canvas
ƒ Point-and-click CSS definition
– Create and apply styles
ƒ Preview Server
– Preview task and composite application execution right from
– No need to deploy; Test your task as you develop
ƒ New UI Controls

Page 193
8 Custom Categorizations

ƒ Because a standard asset taxonomy is too rigid…

ƒ Classify assets the way you see them
– Classification examples:
ƒ Classify by project stage (Development, Design etc.)
ƒ Classify by stakeholder (Finance group, HR etc.)
– Asset types include
ƒ Processes
ƒ Services
ƒ Documents
ƒ Tasks
ƒ Rules etc.
ƒ Search for assets using custom categories
– Find
Fi d all
ll process assets
t iin “D
i ” phase
ƒ Visualize asset dependencies in terms of custom categories
Page 194
Custom Categorization: Value Proposition

ƒ Allow users to categorize assets the way they see them

– Static categorization (processes, tasks, rules etc.) is not flexible
– Customers want to organize and see assets in many different angles
ƒ Based on the phase of development an asset is in (Deployed,
Development, Testing etc.)
ƒ Based on the asset ownership (HR, Finance etc.)

Page 195
Custom Categorizations: Functionality

ƒ User Interface to create custom categories and values

– Category: Project Stage
– Value: Development, Design, Testing, Deployed etc.
ƒ Categorizations in
– Workspace
– Metadata
M t d t Lib
ƒ Enhanced search includes custom category based search
ƒ Asset dependency viewer includes custom category nodes

Page 196
9 Asset Dependency Visualization

ƒ Re-using
Re using a service? Modifying a rule? What are the implications?
ƒ Visualize impact analysis thru asset dependency visualization
– Explore
p dependency
p y chain byy p

Page 197
Asset Dependency Viewer: Value Proposition

ƒ Impact analysis
– Know the impact of changes
ƒ Visualize dependencies
– As opposed to looking at dependencies in a list

Page 198
Asset Dependency Viewer: Functionality

ƒ New Eclipse View

ƒ Drag-and-drop assets into the view from
– Solutions View
– Metadata Library View
– Search View
ƒ Expand capability to drill
down into dependencies
ƒ Filter capability to only look at dependencies of selected types
ƒ Asset chaining to selectively view assets
ƒ Generate asset dependency report
ƒ Hover over Node to get asset information
ƒ Hover over Link to get type of relationship
ƒ Zoom in and out
Page 199
10 KPI Definitions at Design Time

ƒ Define KPIs at design-time?

design time? Now deploy them too!
ƒ Design-time definition of Key Performance Indicators (KPIs)
– Defined byy Business Analysts
y or Developers
p in Designer
ƒ Automatic KPI deployment to Optimize

Page 200
Design time KPI Upload: Value Proposition

ƒ KPIs defined along with the process are deployed to Optimize

automatically when the process is deployed

Page 201
Design time KPI Upload: Functionality

ƒ New Designer Preference

– Configure Optimize
ƒ Automatic deployment
p y of design-time
g defined KPIs
– Enhanced “Build and Upload for Execution”
ƒ Selective/Manual deployment of design-time defined KPIs
– “Upload KPIs” option
ƒ Designer uploaded KPIs overwrite existing KPIs
– Unless they’ve
they ve been modified in My webMethods

Page 202
Demo 15: Design Time KPIs

Page 203
11 Debugger Enhancements

ƒ Debug more in the Designer!

ƒ Debug support now available for:
– Sub-Processes
– Referenced Processes
– Web Service Receive
– JMS Receive
R i
ƒ Trace step outputs

Page 204

Optimize for Infrastructure

Optimize for Process
Optimize for B2B
BPM Components
SOA Components
Wrap Up

Page 205

At the end of this lesson

lesson, you will be able to:
ƒ Understand the new capabilities of the 7.1 SOA Components
– CentraSite Governance Edition
– X-Broker

Page 206
webMethods SOA Overview

Enterprise Edition Governance Edition X-Broker

ƒ Software
S ft AG original
igi l ƒ Formerly
F l Infravio
I f i X X- ƒ Formerly
F l Infravio
I f i X X-
product Registry 6.6 Broker 6.6

Page 207
webMethods SOA Overview

Enterprise Edition Governance Edition X-Broker

ƒ Service
S i lif lifecycle
l & ƒ SOA lifecycle
lif l ƒ Integrated
I t g t d run-time
meta data management governance enforcement

ƒ Extensible data model ƒ Powerful Active policies ƒ Service virtualization and

ƒ Native XML support ƒ Design, change & run time mediation
di ti

ƒ Artifact life cycle policy management ƒ Run-time policy

management ƒ Service Contracts enforcement

ƒ Pluggable AJAX UI ƒ Comprehensive UDDI v2

v2, v3 ƒ WS-Security

ƒ Graphical impact analysis registry support ƒ Monitoring & Logging

ƒ Flexible & customizable ƒ B2B SOA ƒ SLA Enforcement

ƒ Eclipse Support

Page 208
New in CentraSite Governance 7.1

1 Enhanced usability
2. Revamped UI
3. New terminology
4. Open metadata model
5. Flexible policy scope
6. Profile level access control
7. Enhanced impact analysis

Page 209
1 Enhanced Usability

ƒ New Look

ƒ New Navigation

ƒ Web 2.0/AJAX technology

ƒ Easy to use & scalable interaction patterns:

– Browse

– Asset Details •Accelerate roll out of g

– Policies •Reduce training requirements
•Promote SOA adoption
ƒ In-line help
p text •Ensure user productivity

Page 210
2 Revamped UI

ƒ Home
H ƒ Policy
P li
– Approval Inbox/History – New terminology

ƒ Catalog – Main page

– My Assets – Create/Edit Policy

– Browse – Action templates

– Search ƒ Administration
– Asset Details

Page 211
New UI Features

ƒ New WSDL editor UI

ƒ New Performance profile UI in Asset Details

ƒ New Runtime Events UI in Asset Details

ƒ New Guest user UI

ƒ Reports UI

ƒ Operations UI

– Single location for managing run-time infrastructure

– Manage Target
types, targets and consumer applications

– View events across services

Page 212
3 New Terminology

Old Term
New T

Policy Instance Policy

Assertion Instance Action

Assertion Template Action Template

Policy Template Action Category

Templates Action Templates

Parameter Instance Parameter

Parameter Template Parameter Template

Page 213
4 Open Meta-data
4. Meta data Model

ƒ New data types •Model SOA assets to meet unique

requirements of your organization.
– Classification
•Provide complete flexibility over
– Relationship composition and organization of SOA
meta data.
– Rich Text •Unify governance of all SOA assets
ƒ Extensible Attributes within
ithi th
the enterprise
t i

ƒ Extensible Profiles

ƒ Extensible Asset Types

ƒ Custom Meta-data extractors

ƒ View meta-model bottom-up and top-down

Page 214
5 Flexible Policy Scope

ƒ Apply policies to specific asset types

ƒ Apply policies to all Assets

ƒ Apply policies to all Objects

•Unify governance of all SOA entities

within the enterprise
f unique policies
l ffor each
asset type to define its behavior in
SOA processes

Page 215
6 Profile
6. Profile-level
level Access Control

ƒ Secure individual assets

ƒ Secure profiles within an asset

ƒ Use policy actions to automate profile level access control

•Customize CentraSite GE for

different stakeholders by creating
different views of the same asset.

Page 216
Profile level Access Control Features

ƒ Permissions are always granted on an asset by asset basis.

ƒ Optionally, permissions can also be granted within an asset at a
profile level.
ƒ Permissions granted at a profile level effectively override
permissions at the asset level
ƒ If permissions have not been explicitly specified for a profile,
profile it
simply assumes the permission definition of the asset.
ƒ The Permissions profile will allow a user to have specific
ƒ Permission specification can also be automated via a policy

Page 217

ƒ Scenario 1
– John D is granted view permissions on WebService1
– Within WebService1, John D is granted edit permission on the
Technical Support
Support’ profile.
– Within WebService1, John D has no permissions for the ‘Development
Costs’ profile.
– Effectively, John D can view WebService1. Within WebService1, John
D can view all profiles except ‘Development Costs’. John D can only
edit ‘Technical Support’ profile.
ƒ Scenario 2
– User Bob has view permission on ‘Technical Support’ profile for
StockQuoteService, but does not have view permission on ‘Technical
Support’ profile for CalculatorService.
– This
Thi would ld nott b
be possible
ibl in
i 6.6,
6 6 where
h permissions
i i are d
fi d
along with the attribute definition and then enforced the same way
for all services.
Page 218
Changes to Cross-Org
Cross Org Permissions

ƒ No one (not even a POA or a Super Admin) can create a group that
contains users outside of their organization.
– In 6.6, anyone with Super Admin privileges could create a group that
t i d users ffrom any org on th
the server.
ƒ When you grant permissions to an object, you can select:
– anyy individual user from yyour own organization
g or
– any group that is defined on the server
– Since you can’t create a group that contains users from different
organizations, you ask the administrator of the other organization to
create the group for you.
– Letting the requestor set up the group retains flexibility and control
within the Consumer Org g and avoid creating
g bottle-necks.

Page 219
7 Enhanced Impact Analysis

ƒ Contract tab in Policy details

ƒ Contract tab in Asset Details
ƒ Graphical Impact Analysis

•Provides relationship and

dependency information regarding
various SOA entities.
•Provides insight into how change
should be managed.

Page 220
8 Improved Documentation

ƒ New Users Guide

ƒ In-line help text
ƒ More samples and examples

Page 221
And other features…

ƒ Access control for reports

ƒ One-click contract creation and contract update
ƒ Support for X
Path to identify consumer applications
ƒ Support for X-509 certificate for use by 3rd party PEPs (still not
supported by X-Broker)

Page 222

Optimize for Infrastructure

Optimize for Process
Optimize for B2B
BPM Components
SOA Components
Wrap Up

Page 223
What Should I Take Next?

Now that you have completed the webMethods Knowledge Update 6 ->
7 course, there are a number of other classes you can take:

– Interested in Integration Server service development or administration?

ƒ Integration Workshop
ƒ Advanced Integration Workshop
– Interested in Business Process Development?
ƒ BPMS for Developers
ƒ Optimize for Process

Check out

Page 224

Our certification programs establish standards for knowledge and skills

necessary to successfully implement mission-critical IT systems using
Software AG technology.

– Software AG
/d f l

– webMethods Suite

Page 225
Further Information

ƒ Software AG Advantage
Supporting the webMethods Community

ƒ webMethods Customer Care Group

– Toll-free in US: 1-888-222-8215
– Europe: +800-963-84-637
– Asia-Pacific: +612-8913-1151

Page 226
ti and

Thank you!

Please don’t forget to complete a course evaluation.

Page 227

The End