webMethods 10.5 and webMethods.io Integration: Everything You Must Know

Editor's Notes

• #3: Kellton Tech has been at the forefront of Digital Transformation for the past two decades. We are a global company with operations in the United States, United Kingdom, Ireland, and Asia Pacific. Our clients range in size from nimble Startups to Fortune 500 companies. Kellton Tech is a publicly traded company and with over 1,500 employees, we are large enough to deliver with excellence but still small enough to care.
• #6: Digital Transformation - is a journey to reach the ideal state of a Digital Enterprise. Kellton Tech’s Strategy and Architecture Services can help you define your digital goals and objectives and develop a strong digital strategy, roadmap and architecture. Analytics and Decisions - Digital noise needs to be matched with enterprise IP to deliver monetize-able insight for the business Process - Process Optimization, Automation and Business Activity Monitoring is fundamental to Digital Innovation feedback we help creating Case Management systems and Dynamic Applications with RPA. Integration - Integration is the Killer app of your future digital enterprise – it has been our core strength for more than 2 decades. Data Fabric and Cloud Enablement - Performance and scale of Data and Insight is fundamental for Digital Business
• #12: This Digital Business which is looking to deliver new Digital Services, Products and Experiences face a lot of challenges As more applications and data move to the cloud, application leaders face increasingly complex integration requirements: within the same cloud, across different clouds and with on-premises endpoints. Supporting these diverse topologies – a hybrid integration platform and strategy has become crucial because: 1. Established on-prem integration platforms are not able to address the new digital and cloud integration requirements 2. Although iPaaS, iSaaS and API tools support these new needs, they require new specialized skills and do not support integration content portability across each other in multi-cloud and on-prem scenarios 3. One-platform for all Integration scenarios remains sub-optimal - Although it is technically possible to achieve, it is not a realistic proposition for organizations with complex integration challenges Additionally application leaders in charge of integration are under pressure to integrate digital transformation projects involving the cloud, mobility, IoT, and APIs. About Platform Providers and Vendors: Many integration platform providers are trying to formulate a coherent integration platform capable of fully supporting multi-cloud service integration requirements. Several are still working hard to consolidate multiple generations of technologies, such as ESBs, data integration tools, B2B gateway software, MFT platforms, iPaaS offerings and API management platforms. They may not yet have reached the optimal combination of functionality and even maturity and production readiness for all the component parts, meaning that the one-vendor approach remains suboptimal. Application leaders in charge of integration are under pressure to reshape their integration infrastructure strategy in order to tackle the new "pervasive" integration challenges stemming from digital transformation projects that involve the cloud, mobility, the IoT and API integration. The hybrid integration platform (HIP) is a framework of on-premises and cloud-based integration and governance capabilities that enables differently skilled personas (integration specialists and nonspecialists) to support a wide range of integration use cases (see picture above). An organization's HIP is usually implemented by assembling a variety of technology building blocks, from one or more providers, which are managed as a cohesive, federated and integrated whole. Responsibility for HIP management is well-defined. Typical HIP building blocks include: • On-premises application and data integration platforms, such as ESBs, ETL tools, B2B Gateway Software, message oriented middleware and the likes. • integration platform as a service (iPaaS) • Full life cycle API management platforms (APIM) • integration software as a service (iSaaS) • other use case specific components, such as, managed file transfer, IoT platforms and mobile back-end services
• #13: As many enterprises move from on-premises only to cloud-based solutions and redefine who does the integration work (not just specialists within IT, but now line-of-business and casual integrators), the hybrid integration platform (HIP) is becoming more important in creating a robust, forward-looking capabilities model. A Hybrid Integration Platform (HIP) permits on-premise applications to seamlessly and securely integrate with cloud-based applications. This permits your IT Team to quick track development and improve efficiency and lower the risk factors in accomplishing Digital Integration. Why Hybrid Cloud Integration Organizations have re-defined their integration strategy to liaison between legacy systems and cloud technologies. Converting to an out and out cloud platform is not a viable solution for all enterprises, nor continuing the on-premise legacy systems. Hybrid Cloud Integration is a perfect pitch for businesses to integrate legacy on-premise systems with cloud data. It helps to resolve many of the challenges businesses face when moving to the Cloud. Hybrid Integration: Ensures Regulatory Compliance: Regulatory compliance prevents businesses from adopting full cloud Integration. Some country specific data protection laws forbid data from leaving its source and sometimes certain confidential data must remain behind the enterprise firewall. Hybrid integration provides the perfect solution by giving companies more control to how their data is handled. Security & Privacy: Organizations can determine the kind of data that should stay behind the firewall and which can be operated on the cloud. This also helps businesses segregate and track data movement. Fosters Innovation: Hybrid Integration provides an opportunity for businesses to incrementally deploy low-risk applications in small chunks to test the waters. This reduces the risk and grow the applications incrementally in cloud at their own pace. Maximize Investment: To maximize the investment, it is important for organizations to combine both on-premise and cloud systems. The Hybrid Integration Layer allows businesses to work with newer applications in cloud while continue to drive the value from legacy applications. What is Multi-Cloud? The term multi-cloud typically refers to using more than one of the public cloud hosting providers in a organization Eg: AWS, Azure, GCP Multi-Cloud vs Hybrid Cloud Multi-cloud applications rely on more than one cloud provider hybrid cloud is classified as an environment that uses a combination of different cloud and on-premises systems Extra ------ What is Multi-Cloud Application Integration? It is an Integration Strategy which enables integrating multiple public and private cloud environments via APIs leveraging iPaas Platforms Many Organizations that are having their applications on the different cloud also want to integrate into different cloud environments and with the availability of multi-cloud management platform, organizations can reduce their dependency on a single cloud provider Leveraging Kellton HIP strategy businesses can integrate to multi-cloud environments via API gateways. It is important not to confuse the term multi-cloud with hybrid cloud because these terms refer to two different aspects of cloud computing. Multi-Cloud use cases rely on more than one cloud provider, where as hybrid clouds are classified as an environment that uses a combination of different cloud and on-premise systems Increased Productivity and Efficiency: organizations can significantly improve their productivity, efficiency and their businesses by using multiple clouds.   Improved Flexibility: Multi-cloud integration is ideal for the flexibility required to effectively complete different tasks.   Dynamic Pricing: Organizations that use multi-cloud integration have the benefit of switching between cloud applications with different pricing models.   Avoid Vendor Lock-In: Multi-cloud integration helps avoid costly situations while keeping cloud providers honest.   Enable Failovers and Disaster Recovery: Multi-cloud deployments usually include failovers between cloud providers for this reason. If there’s downtime with one provider, organizations can quickly shift their resources to another for high availability. Service Grid Architecture Side Car Container Architecture
• #17: webMethods.io Integration is a powerful integration platform as a service (iPaaS) that provides a combination of capabilities offered by ESBs, data integration systems, API management tools, and B2B gateways. Industry's first Node.js-based, cloud-hosted integration Platform-as-a-Service (iPaaS) Easy to use Interface and Sophisticated orchestration Multi-tenant architecture On-premises connectivity Deploy on-premises or in the cloud Enables hybrid integration on-premises and in the cloud Has 300+ cloud and on-premises connectors maintained and updated around the clock Provides a B2B platform in the cloud Delivers next-generation integration architecture with microservices-backed APIs Combines low-code usability with high control to enable citizen integrators to build intuitive services quickly
• #18: Securely manage and expose your APIs to third-party developers, partners and other consumers for use in web, mobile and Internet of Things (IoT) applications. Create new business models and enrich your ecosystems with full lifecycle API management. Microgateway management API Portal : Publish your APIs Built-in usage analytics Integrated API testing Match your company's “look and feel” API Gateway : A secure API gateway A developer portal for collaboration A way to monetize your APIs Analytics to improve your APIs
• #19: Exchange B2B documents in the cloud—and avoid infrastructure headaches and costs. Built on the industry-leading webMethods Trading Networks, supporting purchase orders, invoices and shipping notices—electronically with customers, distributors and trading partners without any hardware investment, maintenance or upgrades. Secure transmission, total visibility Automated profile management Direct integration, real-time exchange Complete profile management Document creation, parsing & validation Reusable rules Security and encryption Back-end integration Real-time exchange Operational visibility Message repair & resubmit Activity logs
• #23: Move your workload to the cloud webMethods Integration cloud utilizes container technology including Docker to simplify deployment of hybrid solutions. It enables you to create new apps and solutions in the cloud using a low-code simplified UI which connect seamlessly to existing apps and solutions on premise.
• #24: CTOs are demanding that more and more integration workloads move to the cloud – taking advantage of productivity improvements and managed infrastructure Fueled by organizational demand for better agility and ease of use, webMethods Cloud deployment provides intuitive UIs for Integration Admins to deploy a fully managed Integration landscape into the SAG managed cloud. Via Designer, integration developers can now take existing services and via a couple clicks and built in CI/CD publish services directly to their cloud landscape .
• #27: The API Platform is made up of 4 components. The API Portal for … The API Gateway for … These are the two primary components. In some cases, these are the only pieces of the platform you need to sell. In fact, these provide a complete set of features to handle API Management scenarios. However, we also add two differentiating components. The API Catalog, which you probably know as CentraSite, offers much broader governance and lifecycle management capabilities than our gateway, and what our competitors provide. Especially important is CentraSite’s ability to track dependencies across assets. What this means is that if you change an API, you could potentially be breaking several other APIs without even knowing it. CentraSite helps protect you from these kinds of mistakes. It also provides more design time governance than our competitors do. In some organizations that value process and governance, such as government organizations just to name an example, CentraSite (or our API Catalog) can be the piece that makes all the difference in winning a deal. Finally, the API Consumption component is something you will not hear from other vendors. This component provides the ability to manage the consumption of APIs from other vendors. Consider, for example, that you are a company that is using Google Maps in one of your web products. Google Maps can be very expensive. How do you keep from accidentally building up a 7 figure bill from Google? You limit how many times you can call the API. You monitor it and you set thresholds on how much you consume the API. The product that supports this functionality is webMethods CloudStreams, which we typically sell as a means to connect to cloud-based APIs. Several customers and analysts have recognized this important differentiator for Software AG—one customer called it reverse monetization, meaning that it is preventing the company from losing money on other people’s APIs. Now let’s look at how the functionality fits into the DBP.
• #30: Need for microgateways: support for distributed microservices arch, Not to overload main gateways, Reduce impact from routing whole traffic though one gateway, Support east-west traffic and Smaller gateway footprint New – self contained java app with headless implementation using custom java profile Form factor: self contained java runtime or docker container with externalized config running on a micro linux host Deployment: standalone, side by side and side car options (microgateway runs close to the business logic, scales together with microservice)
• #31: These are application level problems that the current service mesh platform does not solve and these problems must be solved if microservices are to provide real business value. If we are able to bridge this gap between the technical and the business world by leveraging all the great benefits that service mesh brings to microservices management, and complement them with application awareness, then we are looking at the next logical evolution of service mesh which is “AppMesh” AppMesh symbolizes the convergence of Service Mesh, API Management and Integration technologies. AppMesh extends the service mesh platform by providing application awareness through “APIfication” of the microservices. “APIfication” really means providing an API face to these microservices. With this, you can enable reuse, governance, consumption, landscape management & importantly drives API led integration of these microservices.
• #33: Template Repository Import composite and micro templates from local repository or from the default SoftwareAG’s GitHub repository. Stacks and Layers Supports stacks and layers based on micro templates CRUD operations on the stacks and layers Control DB schema using DB layer in a stack Micro Template from UI Through UI can save an instance as template. Template can be directly used in stack and layers. Template can include all and custom configurations, with some filtering through CLI using an XML file. Saves Templates can be used in stacks and layers to create a new product installation. DB Fix handling With Composite template no additional needed for DB fixes Use function “Apply database fixes without composite template modification”. Encrypted password support CLI can be used to enter encrypted password in composite template or property files eg command : sagcc exec security encrypt password=MyPassword sharedsecret=manage
• #35: An Innovation Release may be a Major or Minor release and denotes a release with a much shorter duration of maintenance and support. An Innovation Release is intended for customers to start projects with new product features and innovations and requires them to upgrade to the next standard release within a few months of its release. An Innovation Release is clearly identified using the term Innovation Release in documentation, download and installation tooling. Standard maintenance Full support New fixes / SPs for issues Sustained maintenance Limited Support Existing fixes / SPs No new fixes Self service No support Self service access to knowledge base
• #36: Strategy Analyze the environment Define, Plan an upgrade path Deployment, Platform considerations Determine architecture - physical & logical Most cases, it is a Side by Side Install Methodology Install Standup, configure Migration components Rectify Deploy & Regression Test Cutover & Go-live And Rollback
• #37: Strategy Analyze the environment Define, Plan an upgrade path Deployment, Platform considerations Determine architecture - physical & logical Most cases, it is a Side by Side Install Methodology Install Standup, configure Migration components Rectify Deploy & Regression Test Cutover & Go-live And Rollback
• #38: Include some more details :
• #39: Advantage Portal : KT utility to generate a readable report of changed and deprecated SAG services and it’s impact on the current code and functionality. Environment Verification : This provides comprehensive end of end pattern test for all the different pattern in the upgrade lifecycle. Performance Monitor : Compares non-functional and SLA requirement between new and old setup.
• #41: 10.5 Current version is nearing EOS/EOM New features in the latest version API Management – Portal, Gateway, Engagement platform. Mature Command Central Hybrid Integration - Cloud Deployments with CI/CD Other features – IoT, AI and RPA integration Scheduled upgrade/maintenance strategy New version resolves issues/problems in the previous version We like new products and latest release Other drivers webMethods.io iPaaS, which combines low-code usability with high control of complex integrations and APIs Available on multiple cloud infrastructure platforms webMethods.io eliminates the need for you to perform upgrades, maintenance or fixes as you gain the cloud benefits of cost efficiency, speed, security and flexibility Enables hybrid integration on-premises and in the cloud Has 300+ cloud and on-premises connectors maintained and updated around the clock Provides a B2B platform in the cloud Delivers next-generation integration architecture with microservices-backed APIs Combines low-code usability with high control to enable citizen integrators to build intuitive services quickly