Introduction

Narendra Thota

The Enterprise Environment

Three key challenges faced by todays enterprises:
The need to integrate applications essential to the companys business
The need to analyze, streamline and improve business processes
The need to deliver agility and lower maintenance costs in IT

The Enterprise Environment

To address these challenges, Software AGs Integration
and Automation Platform: webMethods, is designed to
facilitate and deliver the convergence of:

Application Integration (ESB)

Business-To-Business (B2B) Trading Networks
Business Process Management(BPM)
Business Activity Monitoring (BAM)
Complex Event Processing(CEP)
Master Data Management (MDM)
Mobile Computing
SOA Infrastructure & Governance

Software AG Suite

webMethods 9.x

webMethods Suite

Integration Backbone

Integration Backbone (ESB)

The Enterprise Service Bus (ESB) is considered the
integration backbone of the webMethods product suite.
It provides
Central middleware and messaging infrastructure
Supports multiple communications protocols
Data transformation and mediation

The core of the ESB is the Integration Server(IS):

Runs in a Java Virtual Machine (JVM)
Listens for client requests on one or more ports. These can be
HTTPS,FTPS,email,etc..
Services execute within the IS JVM
Hosts packages that are containers for services and related files
Packages developed maintained by Software AG are prefixed with Wm
Custom Integration Solutions(services) are also developed within
packages(and ahould NOT be prefixed with Wm)
Packages can be installedconfigures on the IS to give it additional
capabilities. E.g If you want the IS to handle web service
mediation,you can install/configure the webMethods

Integration Backbone (ESB)-Continued

The core of the ESB is the Integration Server(IS):
Runs in a Java Virtual Machine (JVM)
Listens for client requests on one or more ports. These can be
HTTPS,FTPS,email,etc..
Services execute within the IS JVM
Hosts packages that are containers for services and related files
Packages developed maintained by Software AG are prefixed with Wm
Custom Integration Solutions(services) are also developed within
packages(and should NOT be prefixed with Wm)
Packages can be installed/configured on the IS to give it additional
capabilities. E.g. If you want the IS to handle web service mediation,
you can install/configure the webMethods Mediator(package
name=WmMediator). For B2B integration with Trading Partners, you
install webMethods Trading Networks(Mediator(package name=WmTN).

Integration Backbone (ESB)-Continued

The ESB consists of:
Integration Server(IS)- The IS includes many core capabilities
including caching ,logging,auditing,security,etc The IS can be
extended by installing the following as packages on the IS:
ActiveTransfer- for Managed File Transfers.Support for
HTTP,HTTPS,FTP,FTPS(SSL),SFTP(SSH),SCP and webDAV protocols
Adapters-pre-built for backend integration ( e.g.JDBC,Oracle Apps,SAP,
WebSphere MQ and many more)
CloudStreams for integration with SaaS/Cloud applications(e.g.
Salesforce)
Enterprise Gateway-provides the necessary DMZ-level infrastructure
needed by mobile and//or B2B applications to securely access services
hosted on IS
EntireX- for legacy (mainframe) integration
eStandards prebuilt solutions for specific standards and
industries(e.g.Chem,EDI,EDIINT, Fix,HIPAA,SWIFT,etc)
Mediator- for webservice mediation
Trading Networks- for B2B integrations
Etc..

Integration Backbone (ESB)-Continued

Messaging
Universal Messaging(UM)-supports messaging paradigms such as
publish/subscribe.Message Queues and Peer to Peer (AND More if you
have the fully featured license)
webMethods Broker is the Legacy messaging product. It is being
replaced by Universal Messaging

Universal Messaging (UM) & webMethods Broker

webMethods Broker is the legacy messaging product for
ESB. It offers many of the same messaging patterns
available in Universal Messaging

Features

Scalability
Multiple language APIs
Security
High Availability
Multiple messaging paradigms

BPMS(Business Process Management Suite)

Business Process Management

Business Process Management provides:
Design and automation of business processes
Business Rules
Benchmarking and analytics

Consists of:
Process Engine (hosted in the Integration Server)
Task Engine (hosted in My webMethods Server)
Infrastructure and Web Service Data Collectors
Rules engine (webMethods Rules or FICO Blaze)
Content Service Platform(for Enterprise Content Management
Integration)
Optimize for Process(for process analytics)
Custom Visualization with Component Application Framework(CAF) and
Open Presentation Layer(OPL)

Works together with:

ESB for integration with internal and external systems
CentraSite for SOA Governance

Lifecycle Management
Lifecycle Management provides:
Design and development of services,triggers,document types,process
models,rules, tasks and user interfaces
Unified installation,deployment and fixes
Common interfaces for startup/shutdown,monitoring,configuration
and management

Install products:Software AG Installer

Apply fixes:Software AG Update Manager(SUM)
Design and Development tools consist of:
Software AG Designer:
Built on Eclipse
Develop: Services,Triggers,Process models,Users Task Uis, Composite
Apps(CAF)

Deployment: webMethods Deployer

ESB Design and Development

Administration/Monitoring tools:
My webMethods Server(MWS)
Portal server that hosts browser-based User Interfaces(portlets) for
monitoring, configuring and user interaction for many webMethods
products, including ESB, BPMS,User Tasks and Optimize.

IS Administrator UI
Browser-based user interfaces(hosted in the IS) for administering,
configuring and managing the Integration Server(IS server settings,
Package Management,Port,Security,etc)

Command Central
Unified management tool for common tasks. Browser-based user interface,
Command-Line Interface(CLI) and APIs(REST and Java)

Mobile Administrator-used for administering the webMethods Mobile

suite
Universal Messaging (UM) Enterprise Manager-for managing/monitoring
the UM realms

Universal Messaging (UM)-Management API & Graphical Tool

Priniciples
Use UM to manage UM:Based on Java Client API,same
drivers/protocols,security,etc
Remote asynchronous monitoring information of multiple realms
Remote configuration management of multiple realms/clusters

Monitoring
Connections ,Threads, Memory,
Logs,Topics,Queues,Audits,Throughput,Data

Configuration/ Management
Configuration Parameters,Realm Security,
Topic/Queues,Interfaces,JNDI(JMS Bindings),Clusters,Scheduling
Graphical Tool- Universal Messaging Enterprise Manager
Developed using the nAdmin API
Every aspect of the tool has corresponding API
Monitor/Manage/Configure multiple realms and clusters from
anywhere

Command Central
Command Central is intended to be a unified,one-stop
interface for:
Viewing inventory of webMethods product installations, versions and
fixes
Comparing the versions of the products installed in different
installations
Comparing the fixes applied to products in different installations
Configuring ports, licenses, alerts and email settings of product
instances
Comparing the configuration settings of product instances running on
different installations
Performing lifecycle operations such as start ,
stop,restart,pause,resume and debug on runtime processes
Monitoring the health of product installations
Monitoring run time status,KPIs and alerts of product instances
Template based Provisioning- Create a template from an existing
managed installation and apply the template to another managed
installation to reproduce the same set of products, fixes and
configuration parameters

Command Central - continued

Command Central includes a unified web UI, CommandLine Interface(CLI) and APIs(REST and Java) for common
management tasks
Various products have their own admin/monitoring tools E.g. IS Admin
UI,MWS portal ,etc Command Central was introduced to unify and
centralize management/monitoring (etc..) of the various webMethods
products
Additional functionality is added to Command Central in each release
Product specific admin UIs and tools can still be used

Command Central - continued

Command Central can manage one or more
installations containing the following products

CentraSite
Command Central
EntireX
My webMethods Server
Platform Manager
webMethods Broker
webMethods Integration Server
Universal Messaging
More

Command Central

Command Central - Architecture

Command Central Architecture

Each Software AG Platform Manager (SPM) enables
Command Central to centrally administer the lifecycle
of managed products in an installation
The SPM provides a set of Services that are accessible via local and
remote APIs
An installation is a set of Software AG products and fixes installed in
the same installation directory". For example, if you have these
installation directories on a host machine:
C:\SoftwareAG_Dev\
C:\SoftwareAG_Sandbox\
The SPM in C:\SoftwareAG_Dev\profiles\SPM manages the products
installed under the C:\SoftwareAG_Dev\

Terracotta and Big Data

In May 2011,Software AG acquired a company called
Terracotta. Their products included : Enterprise
Ehcache,BigMemory,Quartz Scheduler, Terracotta Sever
Enterprise Ehcache for in memory caching:
Javas de facto standard caching API(javax.cache see JSR107)
Default cache for many popular frameworks E.g.
Hibernate,OpenJPA,Grails,Gag,Springsource,Atlassian,Jruby,Liferay
Uses a simple API honed by 100,000s of production deployments
Now baked in to many webMethods products tio improve
performance.For more details refer to the doc Getting Started with
the webmethods Product Suite and Terracotta. Available at the SAG
documentation site and in Empower

Terracotta and Big Data

Terracotta Server Array(TSA):
For clustering and distributed caches
Provides the platform for Terracotta products and the backbone for
Terracotta clusters
Can vary from a basic two-node tandem to a multi-node array
providing configurable scale, high performance and deep failover
coverage

webMethods Suite and Products

Questions?

webMethods Administration
Installation, Server startup/shutdown

Installation & Components

Installation
Please refer to ReadMe files and Installer documentation for sizing,
supported platforms, etc.
Download and Run webMethods Installer (install from image or
Internet)

SoftwareAGInstaller201402.exe

Choose Components to install

Software Startup & Shutdown

IS
Broker

webMethods Installer

webMethods Installer Components/ Configuration

webMethods Installer Components/Configuration

Installation Complete

Starting the Integration Server

Command prompt
Windows InstallDir\profiles\IS_default\bin\startup.bat
Unix InstallDir/profiles/IS_default/bin/startup.sh

Windows Programs
Start All Programs SoftwareAG
Start Servers Start IS 9.7

Stopping the Integration Server

Administrator (URL = http://host:port)

Starting the Broker Server

Command prompt
Windows/Unix Broker\bin\broker_start switch
server[:port]

server Name of the host (default = localhost)

port Broker Server listening port (default = 6849)
-switch can be:
-h Displays a usage message
Default Windows Service

Start MWS

Exercise

Start the Integration Server in Console Mode

Stop the Integration Server
Restart the Server using Administrator
Start MWS

Command Central

Command central
webMethods Command Central centralizes control of
webMethods implementations for on-premise and public
and private clouds
Software AG is the first integration and BPM software
vendor to provide this level of operational visibility and
control of products.

Need of command central

Command Central Drivers

Cloud Enablement

Large landscape management

Scalability

Reduce risk

Elastic expansion

Reduce effort

Automation

Increase agility

Architecture
Installation N
Installation 3
Installation 2
Installation 1

Command
Central Server

CC Web UI

CC Command

CC API

Architecture

Security
JAAS based authentication
Local user
LDAP
SSO from command central
to managed products
Role Based Authorization
Super admin (REW)
Read only admin (RE)
Viewer (Read)
HTTP only support

New Features added

Centralized repository management, including Web UI
Save and apply templates from Web UI
More IS configurations support including Web UI
IS instance management CLI/API
Web UI for license reports management
Log access from Web UI and CLI/API
HTTPS support and other security related
enhancements
Online HELP combining Web UI, CLI and REST API topics
Cloud Factory CLI/API (preview)
SPM footprint optimization

Centralized Repository Management

Central repositories are used by template-based
provisioning
Allows to configure access to SAG SDC and Empower in
one central place
Supports product and fix repository types
Product repos support multiple releases and locations
Adds ability to manage and transfer Installer and
Update Manager images to the target nodes
Provides Web UI and CLI/API

Centralized Repository Management CLI Basics

cc list repository products
cc add repository products name=<repoName>
location=<remote-repourl-or-image-file>
cc add repository products name=<name-for-this-repo>
--input<local-image-file> description=<description>
cc update repository products <repoName>
[[location=<installerimage-file-or-remote-repositoryuri>] [description=<description>]]]
cc update repository products -i <config-withcredentials.xml>
cc delete repository products <repoName>

Template-based Provisioning
Cloning/copying of servers
Creation of new (project) environments from standard
template
Composing more complex environment from a set of
product-specific templates
Creation of a repro-environment to troubleshoot
production issues
Fix and configuration promotion from staging to
production
Elastic scaling (cloud-bursting)

Template-based Provisioning
Web UI to create and apply templates
Relies on centrally configured repositories
Supports automatic image transfer from the central
repository to the target node
New simplified CLI/API

Template-based Provisioning

Save Installation as template

Applying the template

Select Repository

Install the products

Select Fix Repository

Install Fix Repository

Apply Template Sequence for Integration Server

IS Configuration

IS Configuration - example

Integration Sever Instance Management

Integration Server 9.6 supports multiple instances
Default instance can be created by the installer
Additional instances can be created using IS CLI locally
or CC CLI remotely
No CC Web UI yet
No CC Templates support yet
Integration Server license cannot be supplied during
instance creation.
The license file has to be added afterwards using Web
UI or CLI

Instance Management CLI

Log Access
Allows online access to product log files
Tail or head log file viewing, limited number of lines
Simple and regexp search
Full log download in plain text and zip formats
Download of multiple logs for a given component or
entire managed node
Supported for Integration Server, SPM, CCE, CTP
Web UI and CLI

Log Access CLI

How it works
URL

http://localhost:8090/cce/web

Build on Platform manager http://localhost:8092/spm

Web UI designed using Google web tool (GWT)

Use case scenarios

Monitoring

Repro cases

Config changes

Maintenance

Fix handlings

To easily detects problems in

Infrastructure, Installations and
usability
Reproduce the equal
production setup to check
identical production problems
Config changes to be carried
out by operation team
N/W Operators are replacing
routers so all servers and
installations need to be
shutdown proper.
Need to apply same fixes in
different installations

Product instances view

Installations view

Product instance details

Broker monitoring

Compare products and fixes

Platform manager

Questions