TECHED USER CONFERENCE MAY 3-4, 2016

Transcription

1 TECHED USER CONFERENCE MAY 3-4, 2016 Jithesh Melepurackal

2 AGENDA webmethods Architecture Component View Event Driven Architecture and a Use case High Availability and Use cases High Availability Options in Various Products 2

3 WEBMETHODS ARCHITECTURE wm Optimize wm Process Performance Manager USERS Browser Browser wm PPM Dashboard PRESENTATION wm AgileApps wm Enterprise Gateway My webmethods Server MWS CAF Mashzone NextGen PROCESS wm Integration Server wm Process Run Time (PRT) wm Business Rules APAMA (CEP) Capital Markets Foundation API s INTEGRATION wm Integration Cloud CloudStreams wm Integration Server Trading Networks Adapter Run Time wm Mediator CentraSite MESSAGING wm Active Transfer wm Universal Messaging IT-SYSTEMS APPLICATIONS Cloud & SaaS Partner, B2B & EDI ERP CRM CORE SYSTEM 3

4 EVENT DRIVEN ARCHITECTURE Event is a significant change in state Example - Shipment status changed from In-Transit to Delivered Event may signify a problem or an opportunity within or outside your business Three parties involved Event Producers Channels (Message oriented middleware) Event Consumers Loose Coupling - Producer of event need not know consumers of the event Very useful in cases of X clients consuming a message now, x+n clients expected to consume in future 4

5 EVENT DRIVEN ARCHITECTURE USE CASE Requirements Analyze performance of assembly line process Compare performance of processes between various business units Identify why certain products take more time while going through assembly line Message will be consumed by other Software AG products in the environment in the future Identify common defect codes quickly, to help with inventory planning Minimize lookup on core database tables Metrics Dashboards Products used Integration Server, Terracotta Big Memory, Universal Messaging, Event Driven Architecture, PPM (Process Performance Manager) 5

6 DETAILED ARCHITECTURE AND FLOW 6

7 BUSINESS VALUE AND TECHNICAL BENEFITS Business Value Able to identify process bottlenecks A specific assembly unit was under performing compared with others Able to apply best practices from best performing units to under performing unit Easy to extend the implementation to include dashboards and alerts Technical Benefits EDA implementation lays the foundations for messages to be consumed easily by other SAG products in future Apama or Optimize for Monitoring and Alerting Big Memory used to cache approximately 20 GB of data thus avoiding resource consuming DB lookup and retrieving data in milliseconds 7

8 ARCHITECTURE AND HIGH AVAILABILITY USE CASE Requirements Identify the root cause of Production outages that happened in a month Recommend best architecture Out of the Multiple webmethods environments world wide, problem detected in one of their environment Products 9.5 version in production Integration Server, Broker, Trading Networks, BPMS, My WebMethods Server, Optimize, Enterprise Gateway Additional Factors to consider Have hardware limitations on expanding to use VMs Upgrade to a latest version in progress 8

9 CURRENT ARCHITECTURE IS1 IS1 IS2 IS2 IS3 IS3 IS4 IS4 IS5 IS5 IS6 IS6 IS7 IS7 IS8 IS8 BRK1 BRK1 BRK2 BRK2 Multiple Integration Servers on same VM Multiple Broker Servers on same VM Servers sharing same resources on the VM Segregation of IS based on business domains Fairly large volume in 3 clusters Integration Servers clustered across VMs 9 VM - 1 VM - 2 DB Schema

10 NEW ARCHITECTURE IS1 IS2 IS3 IS4 IS5 IS6 IS7 IS8 VM - 1 Schema1 Schema2 Schema3 Schema4 Schema5 Schema6 Schema7 Schema8 IS1 IS2 IS3 IS4 IS5 IS6 IS7 IS8 VM - 2 Split Single Schema into multiple DB schemas Helps DB Archival process to run cleaner and faster Removed broker from these hosts Batch transactions and Real-time transactions to separate servers Change to Stateless IS Cluster, which doesn t require Terracotta 10

11 INTEGRATION SERVER CLUSTERING RECOMMENDATIONS Frequently used Functions Stateful Cluster Stateless Cluster Scheduled Tasks Supports only Any or a Specific Node. All not supported File Polling Adapter Notifications* Triggers/Subscriptions Service Result Caching Session Not Supported * Notifications when configured to use scheduler 11

12 ARCHITECTURE CLOUD USE CASE Requirements Get better visibility into business leads from 150+ partners Integrate partners systems to company s Salesforce by using various data exchange mechanisms including FTP/SFTP, Webservices and Saas APIs Keep overall cost low Easy Development/Mapping High Availability Products Integration Cloud, Integration Server 12

13 PROPOSED ARCHITECTURE Acme On-premise wm Integration Server Acme Salesforce instance Partner Salesforce instance webmethods Integration Cloud Firewall Integration Agent Custom App Database Microsoft Dynamics CRM 3 rd party Middleware Other CRM Web FTP Server Service File based Integration Partner A Partner B Partner C Partner D 13

14 HIGH LIGHTS OF THE ARCHITECTURE Easy cloud integration with other SaaS providers like Salesforce No complex software/hardware installed at On Premise Management of Integration cloud server by Software AG team Development in Integration Cloud Server by Customer team Use of FTP other than HTTP High Availability provided by the Cloud 14

15 MULTI-TENANT CLOUD ARCHITECTURE On-premise server Universal Messaging connectivity layer wm IS farm Live Stage Scheduler Development Stage Git Repository Web Browser webmethods Integration Cloud wm IS farm Tomcat App Server Tenant Database SaaS / PaaS Intelligent Routing Layer Cache Layer Firewall Multi-tenant and managed Multiple tenants share a development execution instance Each tenants gets a separate Live stage instance All elements are in the architecture are managed by Software AG Secure Universal Messaging is used as the communication layer between on-premise and cloud Intelligent Routing Layer Routes request coming from the user / SaaS application to the correct tenant execution instance. The outside world does not need to know it s ip address. Dynamically add additional capacity to a tenant without impacting operations 15

16 HIGH AVAILABILITY OPTIONS Product Integration Server Universal Messaging Broker Centrasite Mediator My WebMethods server HA Options Stateful Cluster(using Terracotta) or Stateless Cluster Active/Active Cluster Minimum of three servers for the Quorum (At least 2 servers online) Cluster Using Sites Across Data Centers Active/Passive set up. Passive server will be down. Requires third party clustering software for automatic failover Load Balancer not recommended Active/Passive set up. Passive server will be down. Requires third party clustering software for automatic failover GUI Multiple GUI servers can be up and running Repository - Active/Passive Set up. Passive Repo will be down. Requires third party clustering software for automatic failover Stateful Cluster(using Terracotta), Stateless Cluster Active/Active Cluster. Applicable to Task Engine as well 16

17 HIGH AVAILABILITY OPTIONS - CONTINUED Product Terracotta Analytical Engine Infrastructure Data Collector Trading Networks Integration Cloud HA Options Active/Passive Set up. Both Servers will be up and running, active processing get /put data, management etc Active/Active set up using Terracotta to share cache information Only one Data Collector used generally. But can have multiple of them Similar to IntegrationServer Available in cloud 17

18 18