webmethods_97

7/24/2019 webMethods_97

1/76

Narendra Thota

Introduction


2/76

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


3/76

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


4/76

Software AG Suite


5/76

webMethods 9.x


6/76

webMethods Suite


7/76

Integration Backbone


8/76

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

=


9/76

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 beHTTPS,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 withinpackages(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).

kb d


10/76


The ESB consists of: Integration Server(IS)- The IS includes many core capabilities

including caching ,logging,auditing,security,etc The IS can beextended 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 andindustries(e.g.Chem,EDI,EDIINT, Fix,HIPAA,SWIFT,etc)

Mediator- for webservice mediation

Trading Networks- for B2B integrations

Etc..

I i B kb (ESB) C i d


11/76


Messaging Universal Messaging(UM)-supports messaging paradigms such as

publish/subscribe.Message Queues and Peer to Peer (AND More if youhave the fully featured license)

webMethods Broker is the Legacy messaging product. It is being

replaced by Universal Messaging

U i l M i (UM) & bM h d B k


12/76

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

F t


13/76

Features

Scalability

Multiple language APIs

Security

High Availability

Multiple messaging paradigms

BPMS(B i P M t S it )


14/76

BPMS(Business Process Management Suite)

B i P M t


15/76

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

Lif l M t


16/76

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 D i d D l t


17/76

ESB Design and Development

Administration/Monitoring tools: My webMethods Server(MWS)

Portal server that hosts browser-based User Interfaces(portlets) formonitoring, 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

U i l M i (UM) M t API & G hi l T l


18/76

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


19/76

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 productinstances

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


20/76

Command Central - continued

Command Central includes a unified web UI, Command-

Line 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


21/76

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


22/76

Command Central

Command Central Architecture


23/76

Command Central - Architecture



24/76


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


25/76


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



26/76


Terracotta Server Array(TSA): For clustering and distributed caches

Provides the platform for Terracotta products and the backbone forTerracotta 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


27/76

webMethods Suite and Products

Questions?


28/76

Questions?


29/76

webMethods Administration

Installation, Server startup/shutdown

Installation & Components


30/76

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


31/76

webMethods Installer

webMethods Installer Components/ Configuration


32/76

webMethods Installer Components/ Configuration

webMethods Installer Components/Configuration


33/76

webMethods Installer Components/Configuration

Installation Complete


34/76

Installation Complete

Starting the Integration Server


35/76

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


36/76

Stopping the Integration Server

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

Starting the Broker Server


37/76

Starting the Broker Server

Command prompt

Windows/Unix Broker\bin\broker_start

switchserver[: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


38/76

Start MWS

Exercise


39/76

Exercise

Start the Integration Server in Console Mode

Stop the Integration Server

Restart the Server using Administrator

Start MWS


40/76

Command Central

Command central


41/76

Command central

webMethods Command Central centralizes control of

webMethods implementations for on-premise and publicand private clouds

Software AG is the first integration and BPM software

vendor to provide this level of operational visibility andcontrol of products.


42/76

Architecture


43/76

c tectu e

Installation 3

Installation 2

Command

Central Server

CC Web UI CC Command CC API

Installation N

Installation 1

Architecture


44/76

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


45/76

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


46/76

p y g

Central repositories are used by template-based

provisioning

Allows to configure access to SAG SDC and Empower inone central place

Supports product and fix repository types

Product repos support multiple releases and locations

Adds ability to manage and transfer Installer andUpdate Manager images to the target nodes

Provides Web UI and CLI/API


47/76

Centralized Repository Management CLI Basics


48/76

p y g

cc list repository products

cc add repository products name=

location= cc add repository products name=

--input description=

cc update repository products

[[location=] [description=]]]

cc update repository products -i

cc delete repository products

Template-based Provisioning


49/76

p g

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)



50/76

p g

Web UI to create and apply templates

Relies on centrally configured repositories

Supports automatic image transfer from the centralrepository to the target node

New simplified CLI/API



51/76

p g

Save Installation as template


52/76

p

Applying the template


53/76

pp y g p

Select Repository


54/76

Install the products


55/76

Select Fix Repository


56/76

Install Fix Repository


57/76


58/76

Apply Template Sequence for Integration Server


59/76

IS Configuration


60/76

IS Configuration - example


61/76

Integration Sever Instance Management


62/76

Integration Server 9.6 supports multiple instances

Default instance can be created by the installer

Additional instances can be created using IS CLI locallyor 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


63/76

Log Access


64/76

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


65/76


66/76

Log Access CLI


67/76

How it works


68/76

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
http://localhost:8090/cce/webhttp://localhost:8090/cce/webhttp://localhost:8090/cce/webhttp://localhost:8090/cce/web


69/76

Monitoring : To easily detects problems in

Infrastructure, Installations and

usability Repro cases : Reproduce the equal

production setup to check

identical production problems

Config changes : Config changes to be carriedout by operation team

Maintenance : N/W Operators are replacing

routers so all servers and

installations need to beshutdown proper.

Fix handlings : Need to apply same fixes in

different installations

Product instances view


70/76

Installations view


71/76


72/76

Broker monitoring


73/76

Compare products and fixes


74/76

Platform manager


75/76

Questions


76/76

webmethods_97

Documents