Diff7 1vs6x PDF

EDUCATION SERVICES
webMethods
Knowledge Update 6 ->
>7
Revised 03-DEC-2007
Copyright
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
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…
Benefits
Please:
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
lecture,
e, we
we’ll
ll w
write
te itt o
on tthe
e boa
board
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
ROADMAP
Component Startup
Integration Server
Trading Networks
Broker
Page 9
Objectives
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

enterprises:
– The need to Integrate applications and partners essential to the
company’s
’ 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

71
Enterprise Service Bus.
The webMethods ESB provides:
– Central middleware and integration infrastructure
– Supports multiple communications protocols for connections to
various systems
y
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
7.1
1 offers complete end
end-to-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.
d
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
processes
– Monitor: for monitoring process and service activities and
performance
– My webMethods Server: centralized configuration,
configuration administration and
monitoring
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
f
– Optimize for Process
p
– 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

Analytics
y Enforcement
System Enterprise Legacy Roles and

Analytics B2B Service Bus Modernization Responsibilities
Service Lifecycle
Monitoring Management
Packaged
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
Reporting
CentraSite
Governance
Optimize for Enterprise Integration
Process X-Broker
Optimize for Integration Server Legacy

Infrastructure TN Broker Modernization Lifecycle
Management
Monitor
Packaged
Partners Apps Databases App Servers Mainframes
Page 18
webMethods 7 Architecture: Service Bus
Business Process Integration Solution

Packaged
Apps
Applications & Partners
Databases
Integration Rules Analytics Process Presentation
Mainframes
Service Bus
Partners
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
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
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
Service Bus
Page 22
Service Bus
Adapters
Accelerate development by providing a common interface to

disparate systems Packaged
Apps
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,
(HIPAA
UCCNet, EDIINT, RosettaNet, etc)
Service Bus
Page 23
webMethods 7 Architecture: Design and Development

Packaged
Apps
Databases
Mainframes
Service Bus
Partners

Web Services

3rd Parties

App Servers
Page 24
Design and Development
Developer
Development environment for

webMethods Integration Server services
Developer
Supports both codeless (Flow) &
coded development (Java
(Java, C)
Integrated with Version Control
webMethods Integration
Server
Systems (VCS)
Developer
webMethods VCS
Developer
Design &
Development
Page 25
Designer
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 &
Development
Page 26
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 &
execution
Standards-based
Standards based UI development
– Java Portlet Specification (JSR 168)
– Java Server Faces
– AJAX
Design &
Development
Page 27
Metadata Library
Common asset library for re-

re
use and faster development
Accessible from development
tools
l such
h as the
h Designer
– Allows drag and drop usage of
assets
Contains published assets
throughout the environment
Design &
Development
Page 28
webMethods 7 Architecture: Governance

Packaged
Apps
Databases
Mainframes
Service Bus
Partners

Web Services

3rd Parties

App Servers
Page 29
Governance
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
ti
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

Packaged
Apps
Databases
Mainframes
Service Bus
Partners

Web Services

3rd Parties

App Servers
Page 31
Management & Monitoring
My webMethods Server
Interconnected
I t t dddomains
i
– Services
My webMethods
– Tasks
– Processes
– Partner Interactions
Unified interface
Service Audit Process Audit Task Audit
Trading
Networks Audit
Management &
Monitoring
Page 32
Management & Monitoring
Optimize
Event data received from

My webMethods environment
Advanced monitoring and
analytics
l
– Infrastructure for systems
Analysis
Engine
– Process for business
Analysis DB processes
– B2B for partner interactions
IInfrastructure
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

Packaged
Apps
Databases
Mainframes
Service Bus
Partners

Web Services

3rd Parties

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
M
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
ROADMAP
Component Startup
Integration Server
Trading Networks
Broker
Page 37
Objectives

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
Starting
i the
h Web
W b Services
S i D
Data C
Collector
ll
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
line:
– /IntegrationServer/bin/server.sh | bat –switch –switch
Start as a Windows service:
Stop/restart from the Administrator
Page 41
Start/Stop My webMethods Server

– /MWS/bin/mws.sh | bat –s Default start
– /MWS/bin/mws.sh | 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
b
component.
Page 42
Start/Stop the Optimize Analytic engine

– /optimize/analysis/bin/startupAnalyticEngine.sh | bat
– /optimize/analysis/bin/shutdown.sh | 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/startupPredictionEngine.sh | bat
– /optimize/prediction/bin/shutdown.sh | bat
Windows:
Page 44
Start/Stop the Web Service Data Collector
Start/stop from the command line

– /optimize/dataCollector/bin/startupDataCollectorEngine.sh
| bat
– / ti i /d t C ll t /bi / h td
/optimize/dataCollector/bin/shutdown.sh
h | b
bat
t
Windows:
Page 45
Start/Stop the Infrastructure Data Collector
Start from the command line:

– /IntegrationServer/bin/server.sh | 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/ library.sh | bat
Or start and stop
p as a Windows Service
Page 47
Demo 1: Component Startup
Page 48
ROADMAP
Component Startup
Integration Server
Trading Networks
Broker
Page 49
Objectives

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
71
1 Enhanced web services support

1.
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
i
6. Centralized user management
7 Refined clustering
7.
8. Additional features
Page 52
1 Enhanced Web Services Support
1.
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
service
i
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
document
– Developer uses the consumer Web Service Descriptor to invoke and
use a remote Web Service similar to other IS Services
Page 55
Operations
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
Binders
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
element,
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
information
i
Page 57
Web Services Descriptor Nodes
1 Create WSD
1.
Provider
2. Create WSD
Consumer
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
WSD)
– Easier support for document/literal style messages
– Generate
Ge e ate Web SeService
v ce Co
Connectors
ecto s from
o WS
WSDL co
containing
ta g sc
schemas
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
WSDL
browsing
g
WS-I
check
Multiple
operations
SOAP
handlers
Multiple
bindings
Page 60
Developer Features
UDDI v3
browse/
publish
Easy
Deployment
Multiple
M lti l
transports
Use/Style
options
Page 61
Developer Features
Robust Web Services Support

– Provider and Consumer specific
definitions
– 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
p
– Drag/Drop web services from UDDI
registry
– 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
WS-Security
Security facility is a message
message-based
based implementation that
provides end-to-end network coverage
Transport-based implementation (ex. HTTPS) the credentials and
authentication
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
provider
Page 67
Outbound & Inbound Messages
1. When implementing
WS-Security you
WS-Security,
configure the security
settings for a Web
Service consumer or
provider’s inbound
and outbound
messages
Page 68
2 Interoperable Standards Support
2.
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
p
Publish to UDDI registry from WSD node
Page 70
3 Enhanced Protocol Support
3.
Upgraded HTTP stack

Upgraded SOAP stack
New C# broker client API
Page 71
Upgraded HTTP Stack
New HTTP 1
1.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
l
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
2. The SOAP M
Th Message
g
Handler Invokes
the Appropriate
SOAP Processor
3. The SOAP Processor

Performs Work and
Generates a
Response
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
passing
i it to
t an accounts-payable
t bl processor, th
the h
header
d could ld h
hold
ld
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
SOAP 1
1.1
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
documentt
Page 80
5 Native JMS Messaging
5.
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
WmPublic
P bli services
i
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
t
– ability to bypass JNDI for Broker configuration
– JMS extensions enable compression
p and message
g streaming
g
Page 81
Integration Server & Broker Sample Configuration
1. The Integration
Server and the Broker
share a fast, efficient
process for
exchanging
documents across the
entire webMethods
system.
Page 82
JMS Message Styles
1. JMS supports the

publish-subscribe
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

provider
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
– AUTO_ACKNOWLEDGE
– CLIENT_ACKNOWLEDGE
– DUPS_OK_ACKNOWLEDGE
Page 85
Demo 4: JMS Messaging
Page 86
6 Centralized User Management
6.
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
g
management
Centralized user store is selected, users can map IS ACLs to roles
defined in MWS
C
Centralized
li d user store will
ill allow
ll TN 7
7.1
1 to d
define
fi and
d use
credentials defined via MWS
Page 87
7 Refined Clustering
7.
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
environment
File polling listener now cluster aware
p v2 server is replaced
Repo p with a 3rd p
partyy OEM p
product
(Standalone Only)
– Guaranteed Delivery
– Key Cross Referencing
– Trigger Joins
– Client Certificate Mapping
Page 88
8 Additional Features
8.
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
Designer
i users will
ill h
have access to diff
different views
i which
hi h will
ill allow
ll
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
Log4J-based
based facilities logging
Page 91
ROADMAP
Component Startup
Integration Server
Trading Networks
Broker
Page 92
Objectives

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
Server.
Designed to provide partner management
– Profiles
– Document types
– Processing rules
Acts as a single point of entry for incoming documents
– XML
– EDI
Page 94
New in Trading Networks Version 7.1
71
1 Distribution of run-time
1. run time and design-time
design time activities
2. Role-based transaction monitoring
3. Role
Role-based
based partner administration
4. Improved search
Page 95
1 Distribution of Activities
1.
Run-time
Run time activities now through MWS
– Transaction monitoring
– Activity monitoring
– Task monitoring
Administration activities now through MWS
– Partner
P t profiles
fil
– 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…
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
than,
etc.)
– Implicit “AND” condition between fields
Page 97
…Role-based
Role based Transactions Monitoring…
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
t
– View related documents more clearly in a tree structure
Page 98
…Role-based
Role based Transactions Monitoring
Transactions Details View

– Save content to hard drive
– Edit and resubmit transaction
– Add/Edit comments for a
transaction
– Audit
ud t trail
t a l of
o changes
c a ges to
comments
– 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…
Administration
Monitor through My WebMethods (MWS) UI

– Profiles
– Profile Groups
– Public Queues
Role based access
– Screen level access
– Functional Permissions
– G
General
l ffunctional
ti l permissions
i i
Data level security
– Profiles
– Profile Groups
Keyword Search
Advanced Search
– Search on one or more fields
– Number and String operators (Equals, Not equals, Less than, Greater than, etc.)
Page 101
…Role
Role Based Partner Administration
Partner Certificate Search

– Search expired or about to expire certificates
Audit Trail of changes
g to partner
p p
profiles
Logged in Activity log
Suspend documents prior to
d li
delivery
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
Search
c using
us g p
pre-defined/custom
e de ed custo date ranges
a ges
Advanced Search
– Search on one or more values within a field
– Dynamic partner search criteria specification
– Search using pre
pre-defined/custom
defined/custom date ranges
– Query level customization of transaction results
Page 105
…Improved
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
Customize
t i column
l di
display,
l sortt order
d and
d number
b off ttransactions
ti
displayed
Page 106
Demo 7: Enhanced Search in TN
Page 107
ROADMAP
Component Startup
Integration Server
Trading Networks
Broker
Page 108
Objectives

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
Page 110
New in Broker Server Version 7.1
71
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
consultants
– 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
administrators
Page 113
Day 2
Page 114
ROADMAP
Optimize for Infrastructure

Optimize for Process
Optimize for B2B
BPM Components
SOA Components
Wrap Up
Page 115
Objectives

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?

– Monitors system components, such as the IS, Broker, Adapters
– Tracks operational data
– Alerts on errors and rule violations
– 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
processes
Optimize for B2B
– Monitors B2B documents (XML, EDI, etc.) and attributes
Page 118
New in Optimize for Infrastructure 7.1
71
1 Architecture
1.
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
Broker
Analytic engine Analytic engine
DB Prediction engine
My
y webMethods
Page 120
Infrastructure Data Collector…
Collector
Brokers
Integration
Servers
Infrastructure
Data Collector
Adapters
Web Service
Data Collector
Broker
SNMP Agents
DB P di ti
Prediction engine
i
My webMethods
Page 121
…Infrastructure
Infrastructure Data Collector
Infrastructure Data Collector
Broker Server Data Collector Module

Broker
Ser er
Server
Integration
Integration Server Data Collector Module
Server
Infrastructure Data Collector Module

IS Resource Module
ART Resource Module

API
TN Resource Module
MonA
Common Data Collector
SNMP
SNMP Data Collector Module
Agent
g
Page 122
2 Scalability and Reliability
2.
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
specifics
p of resource monitoring
g
Reliability Improvements
– Shared model with Optimize Analytic engine
– Addresses sync issues from previous releases
Page 123
3 Version Support
3.
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
7.1
1
– Mainframe
– Workflow 6.5
– DotNet
Coming soon (on or around SP1 release)
– Territory
– Territory Gateways
Page 124
4 Usability Features
4.
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
Assets
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
5.
Page 136
SNMP Data Collector Settings
Page 137
ROADMAP

Optimize for B2B
BPM Components
SOA Components
Wrap Up
Page 138
Objectives

Understand the new features in 7.1 Optimize for Process
Page 139
New in Optimize for Process 7.1
71
1 Architecture
1.
2. Support for multiple monitor instances
3. Service Level Agreements
4. Rule enhancements
5. Derived names usage
Page 140
1 Optimize For Process Architecture
1.
Web Service Web Service

Data Collector Data Collector
Broker
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
2.
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
3.
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
SLAs
– 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
customer(s)
Page 145
Demo 9: Service Level Agreements in Rules
Page 146
4 Rule Enhancements
4.
New alerts
– Reminder alerts: notification when a rule continues to stay out of
compliance
– 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
Severity
ty can
ca be set for
o rules
ules
– 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
Customer
SLA
Derived Name
Severity
Reminder
In Compliance
Page 149
Rule Features – Rule List Page
New Status Icons

Severity
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
5.
Derived names are extremely useful in uniquely identifying rule

instances.
– 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
character
character.
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
ROADMAP

Optimize for B2B
BPM Components
SOA Components
Wrap Up
Page 155
Objectives

Understand the new capabilities in 7.1 Optimize for B2B
Page 156
Optimize for B2B Overview
Real
Real-time
time business activity monitoring (BAM) solution continuously
monitors your EDI, XML, and Flat File transactions
Define, track and measure Key Performance Indicators to monitor
and
d enforce
f service level
l l agreements, and
d measure partner
performance
Directly integrated with webMethods Trading Networks
Automatically generates alerts based on thresholds, key data and
errors
Page 157
New in Optimize for B2B 7.1
71
1 Document type monitoring

1.
2. Standard Optimize activities
Page 158
1 Document type monitoring
1.
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
wm.b2b.editn:addAttributeTypeToBizDoc
Invoke a service to extract values and update the attributes in TN
database
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
2.
Define Event Maps

p
– 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…
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
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
t
etc.
– wants to evaluate what percentage of invoices are getting delivered
successfully
f ll by
b partner
t
– 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
ROADMAP

Optimize for B2B
BPM Components
SOA Components
Wrap Up
Page 165
Objectives

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
processes
– Monitor: for monitoring process performance and key business
metrics
– My webMethods Server: for access to monitoring and for user
interfaces to process tasks
Page 167
New in BPM 7.1
71
1 Simulation
1.
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
1.
Understand process behavior

behavior, bottlenecks
bottlenecks, costs and resource
requirements
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
systems.
C
Compare the
h b
behavior
h i ((performance,
f utilization,
ili i cost etc.)) off two
or more process models OR two or more versions of the same
process
Optimize processes
Visualize how processes actually work
Page 170
Simulation: Functionality…
Functionality
Fully integrated simulation (in Designer)

– No import/export
Activityy based costing
g
– Know projected costs aggregated by process, step, resource,
swimlane
– 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:
Simulation: Functionality
Reporting
– Detailed simulation statistics for further analysis
Animation with Playback
y
– 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
2.
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
3.
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
availability
l bl b before
f distributing
d b tasks
k
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
Server
– with
ith L
Lotus
t D Domino
i SServer
Page 178
Demo 13: Business and User Calendars
Page 179
4 Task Analytics
4.
Analyze task performance and people performance using

Optimize!
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
71
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
5.
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
Task
k Li
List M
Management (TLM) visualization
i li i for f task
k owners and
d
managers
– 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
inboxes)
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
6.
Task editing made easy…

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
glance
Create Task Views, Inbox Views and Notification Views by simply
selecting business data fields
New
N ttask
k di
distribution
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
g
– 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
etc.
– Explicit Processes
Making modeling of task routing in processes easy
Page 188
Enhanced Task Editing: Functionality…
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?
g
– When should the rule be evaluated?
– What are the conditions under which this assignment should take
place?
– How should the tasks be distributed among various members of a
role?
Page 189
…Enhanced
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
7.
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
Designer
– No need to deploy; Test your task as you develop
New UI Controls
Page 193
8 Custom Categorizations
8.
Because a standard asset taxonomy is too rigid…

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
“Design”
i ” phase
h
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
Library
Enhanced search includes custom category based search
Asset dependency viewer includes custom category nodes
Page 196
9 Asset Dependency Visualization
9.
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
point-and-click
Page 197
Asset Dependency Viewer: Value Proposition
Impact analysis
– Know the impact of changes
Visualize dependencies
p
– 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
drill-down
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
10.
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
g
Automatic KPI deployment to Optimize
Page 200
Design time KPI Upload: Value Proposition
Design-time
KPIs defined along with the process are deployed to Optimize

automatically when the process is deployed
Page 201
Design time KPI Upload: Functionality
Design-time
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
11.
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
ROADMAP

Optimize for B2B
BPM Components
SOA Components
Wrap Up
Page 205
Objectives

Understand the new capabilities of the 7.1 SOA Components
– CentraSite Governance Edition
– X-Broker
Page 206
webMethods SOA Overview
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
Service
S i lif lifecycle
l & SOA lifecycle
lif l Integrated
I t g t d run-time
ti
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

reporting
Eclipse Support
Page 208
New in CentraSite Governance 7.1
71
1 Enhanced usability
1.
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
1.
New Look
New Navigation
Web 2.0/AJAX technology
Easy to use & scalable interaction patterns:
– Browse
– Asset Details •Accelerate roll out of g

governance
– Policies •Reduce training requirements
•Promote SOA adoption
In-line help
p text •Ensure user productivity
Page 210
2 Revamped UI
2.
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
Target-types
types, targets and consumer applications
– View events across services

Page 212
3 New Terminology
3.
Old Term
T N
New T
Term
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
5.
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
•Define
f unique policies
l ffor each
h
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
Profile-level
Permissions are always granted on an asset by asset basis.

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
permissions.
permissions
Permission specification can also be automated via a policy
action.
Page 217
Examples
Scenario 1
– John D is granted view permissions on WebService1
– Within WebService1, John D is granted edit permission on the
‘Technical
Technical Support
Support’ profile.
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
defined
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
contained
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
7.
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
8.
New Users Guide

In-line help text
More samples and examples
Page 221
And other features…
features
Access control for reports

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

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
Check out www.webmethods.com/education
Page 224
Certification
Our certification programs establish standards for knowledge and skills

necessary to successfully implement mission-critical IT systems using
Software AG technology.
– Software AG
http://www.softwareag.com/Corporate/service/training/certification
/d f l
/default.asp
– webMethods Suite
http://www.webmethods.com/Services/Education/Certification
Page 225
Further Information
Software AG Advantage
Supporting the webMethods Community
http://advantage.webMethods.com
webMethods Customer Care Group

– Toll-free in US: 1-888-222-8215
– Europe: +800-963-84-637
– Asia-Pacific: +612-8913-1151
– support@webMethods.com
Page 226
Q
Questions
ti and
dCComments
t
Thank you!
Please don’t forget to complete a course evaluation.
Page 227
EDUCATION SERVICES
The End

Diff7 1vs6x PDF

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Diff7 1vs6x PDF

Enviado por

Direitos autorais:

Formatos disponíveis

EDUCATION SERVICES

This publication is protected by international copyright law.

Structure (for each module): If you are going

 Demo led by the instructor Tryy things

At the end of this lesson

 Software AG recognizes key challenges faced by today’s

 Enterprise Integration and B2B are part of the webMethods 7.1

 BPM automates end-to-end

 BAM analyzes real-time

Business Business Process Management and Applications SOA

Business Registry &

Process Enterprise Integration Policy Design and

System Enterprise Legacy Roles and

Business Business Process Management and Applications SOA

Optimize for Integration Server Legacy

Business Process Integration Solution

Integration Rules Analytics Process Presentation

Design & Management &

Development Governance Monitoring

Metadata Registry/ Event

 The Enterprise Service Bus (ESB),

Integration Rules Analytics Process Presentation

 Primary service execution runtime component of the webMethods

Integration Rules Analytics Process Presentation

Integration Rules Analytics Process Presentation

 Accelerate development by providing a common interface to

 Isolate resources from change, provide error detection and

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

– Simplified integration with industry-specific

Integration Rules Analytics Process Presentation

Business Process Integration Solution

Integration Rules Analytics Process Presentation

Design & Management &

Development Governance Monitoring

Metadata Registry/ Event

 Development environment for

 Unified presentation layer for webMethods Suite

 Common asset library for re-

Business Process Integration Solution

Integration Rules Analytics Process Presentation

Design & Management &

Development Governance Monitoring

Metadata Registry/ Event

Enterprise Edition Governance Edition X-Broker

 Extensible data model  Powerful Active  Service virtualization

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

 Eclipse Support Governance

Business Process Integration Solution

Integration Rules Analytics Process Presentation

Design & Management &

Development Governance Monitoring

Metadata Registry/ Event

Service Audit Process Audit Task Audit

 Event data received from

Business Process Integration Solution

Integration Rules Analytics Process Presentation

Design & Management &

Development Governance Monitoring

Metadata Registry/ Event

 Developer 7.1  Developer 6.5

 MWS Console 7.1  MWS Console 7

 Integration Server 7.1  Integration Server 6.5

 Optimize for B2B 7.1  N/A

Demo led by the instructor Tryy things

Software AG recognizes key challenges faced by today’s

Enterprise Integration and B2B are part of the webMethods 7.1

BPM automates end-to-end

BAM analyzes real-time

The Enterprise Service Bus (ESB),

Primary service execution runtime component of the webMethods

Accelerate development by providing a common interface to

Isolate resources from change, provide error detection and

Available for most major Enterprise Resource Planning (ERP),

Development environment for

Unified presentation layer for webMethods Suite

Common asset library for re-

Extensible data model Powerful Active Service virtualization

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

Eclipse Support Governance

Event data received from

Developer 7.1 Developer 6.5

MWS Console 7.1 MWS Console 7

Integration Server 7.1 Integration Server 6.5

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

Start and stop from the command line:

Start and stop as a Windows service:

Start / stop / restart from My webMethods

Start as a Windows service:

Stop/restart from the Administrator

Start and stop from the command line:

Or start and stop as a Windows Service

Start and stop from the command line:

Start/stop from the command line:

Start/stop from the command line

Start from the command line:

Stop and restart from the Administrator

Start from the command line:

Integration Server is the central run-time

Web service descriptors

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

Provider Web Service Descriptors

Each operation contains a single request and response

A binder is a collection of related definitions and specifications for

Web service descriptor (WSD) node

Robust Web Services Support

The Integration Server WS-Security

Developer UDDI v3 Registry publish and browse

Upgraded HTTP stack

New SOAP processor

The SOAP processor is a service that acts upon SOAP messages

The SOAP specification defines one body element named Fault

SOAP message can include an optional header component to store

Recursive Complex Types

Native JMS messaging allows IS to directly

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

Centralized user store that IS, MWS, BPMS runtimes can

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

Metadata Library access

Configure location/access of Library

Trading Networks is an add-on

Monitor through My WebMethods (MWS)

Transactions Details View

Monitor through My WebMethods (MWS) UI

Partner Certificate Search

Role based access enables:

Broker Server hosts the primary mechanism for messaging

New scripts and procedures

Optimize for Infrastructure

Out of the box monitoring (no fixes required)

Discovery UI moved to My webMethods Server