Centralized enterprise integration and services monitoring portal

Techniques are provided for centralized enterprise integration and services monitoring in computing environments. For example, a system comprises one or more processors operatively coupled to one or more memories to form a monitoring portal system, wherein the monitoring portal framework is configured to perform steps of: providing one or more graphical user interfaces; and enabling centralized enterprise integration and services monitoring through the one or more graphical user interfaces.

FIELD

The field relates generally to computing environments, and more particularly to techniques for providing centralized enterprise integration and services monitoring in such computing environments.

BACKGROUND

Tracking integrated enterprise, real-time service transactions, monitoring systems, forecast capacity usages, etc., across multiple heterogeneous information technology (IT) systems associated with an enterprise is important in today's fast-moving business climate in order to maintain advantages over competitors. To achieve such advantages, it would be desirable to be able to track data across an array of systems and applications used to monitor transactions and support requests across various databases. However, with existing systems, users have to check multiple locations to track a transaction from one endpoint to the next across an enterprise.

SUMMARY

Embodiments of the invention provide techniques for centralized enterprise integration and services monitoring in computing environments.

For example, in one illustrative embodiment, a system comprises one or more processors operatively coupled to one or more memories to form a monitoring portal framework, wherein the monitoring portal system is configured to perform steps of: providing one or more graphical user interfaces; and enabling centralized enterprise integration and services monitoring through the one or more graphical user interfaces.

Advantageously, in one or more illustrative embodiments, the centralized enterprise integration and services monitoring portal provides visibility that enables, for example, a sales representative insight into the status of a given customer order to keep track of its movement across the many heterogeneous systems and their interfaces.

These and other features and advantages of the invention will become more readily apparent from the accompanying drawings and the following description.

DETAILED DESCRIPTION

Illustrative embodiments will be described herein with reference to exemplary information processing systems and associated host devices, storage devices and other processing devices. It is to be appreciated, however, that embodiments are not restricted to use with the particular illustrative system and device configurations shown. Accordingly, the term “information processing system” as used herein is intended to be broadly construed, so as to encompass, for example, processing systems comprising cloud computing and storage systems, as well as other types of processing systems comprising various combinations of physical and virtual computing resources. An information processing system may therefore comprise, for example, a cloud infrastructure hosting multiple tenants that share cloud computing resources. Such systems are considered examples of what are more generally referred to herein as “computing network environments.” Environments that implement multiple cloud platforms are referred to as multi-cloud computing environments. As mentioned above, a multi-cloud computing environment employed by an enterprise may comprise a combination of private and public clouds. The term “enterprise” as used herein is intended to be broadly construed, and may comprise, for example, one or more businesses, one or more corporations or any other one or more entities, groups, or organizations. An “entity” as illustratively used herein may be a person or system.

As will be further explained herein, illustrative embodiments provide a framework that pulls together all integrated transaction data and their supported systems into a centralized view where business and support teams can see real-time transactions, operational metrics, monitoring systems, estimate capacity usages, etc., across multiple heterogeneous IT systems in a comprehensive dashboard (portal) that can service both executives and technical audiences. Examples of multiple heterogeneous IT systems that can be centrally monitored in accordance with illustrative embodiments include, but are not limited to, Enterprise Resource Planning (ERP) systems, Customer Relationship Management (CRM) systems, and Human Resources (HR) systems.

More particularly, in illustrative embodiments, a centralized enterprise integration and services monitoring portal system is built using an open source, virtualized, third platform technologies and enables the following features/advantages: micro services based approach; light weight and easily customizable; easy plug & play systems using one or more application programming interfaces (APIs); transaction search and save functionalities; data analytics and statistics functionalities; dashboard and reporting with any historic data; proactive service monitoring and alert functionalities; systems monitoring; chat and service integration; and mobile enabled functionalities.

FIG. 1illustrates an information processing system implementing a centralized enterprise integration and services monitoring framework, according to an illustrative embodiment. As shown in information processing system100, a plurality of users (USER1, USER2, . . . USER N)102-1,102-2, . . .102-N are operatively coupled (e.g., via their respective computing devices) to a centralized enterprise integration and services monitoring portal system110. The monitoring portal system110accumulates transaction data and other data from multiple heterogeneous IT systems associated with an enterprise and provides a centralized view for the users102-1,102-2, . . .102-N through one or more graphical user interfaces. The transaction data and other data is accumulated by the monitoring portal system110from cloud platform (public) services120and enterprise (private) services130that are executed on the heterogeneous IT systems associated with an enterprise. The services120and130are operatively coupled to monitoring portal system110.

FIG. 2illustrates a more detailed exemplary architecture for a centralized enterprise integration and services monitoring framework, according to an illustrative embodiment. More particularly, information processing system200illustrates examples of users102-1,102-2, . . .102-N and cloud platform services120and enterprise services130fromFIG. 1, as well as further details of the centralized enterprise integration and services monitoring portal system110.

As shown, users of the centralized enterprise integration and services monitoring portal system210may include, but are not limited to, enterprise personnel202-1, enterprise customer(s)202-2, and IT support202-3. Application & integration services230, data store services232, cloud platform services234, Platform-as-a-Service (PaaS) services236, and servers, virtual machines (VMs) & containers238are considered examples of cloud platform services120and/or enterprise services130.

Further, block210inFIG. 2illustrates further details of a centralized enterprise integration and services monitoring portal system (e.g., further details of system110inFIG. 1). As shown, system210comprises: a centralized monitoring portal212; a search & storage stage214; a collection, analysis & processing stage216; an operations monitoring, logs, system metrics & reporting stage218; authorization services222, notification services224; a rules engine226; and an application programming interface (API) gateway228, each operatively coupled to a centralized enterprise integration and services monitoring portal controller220.

Thus, in an illustrative operational flow example, transactions that are generated in accordance with one or more of application & integration services230, data store services232, cloud platform services234, PaaS services236, and servers, VMs & containers238, are provided to collection, analysis & processing stage216through API gateway228. The transactions can be provided in a push mode and/or a pull mode. The transaction data is provided to the search & store stage214. The data is stored in one or more storage arrays215. The stored data may comprise raw data collected directly from the cloud or enterprise services and/or data that is analyzed/processed by enterprise middleware (e.g., data filtering algorithm, data normalization algorithm, etc.) in stage216. Operations monitoring, logs, system metrics & reporting stage218is configured to further analyze the stored data. By way of example only, statistical analysis algorithms can be run on the data to generate customized reports and logs that are of respective interest to users such as enterprise personnel202-1, enterprise customer(s)202-2, and IT support202-3. The users are able to view the stored data and/or the results of the operations monitoring, logs, system metrics & reporting stage218through the centralized monitoring portal212. The portal212provides one or more graphical user interfaces that enable centralized enterprise integration and services monitoring for the users.

More particularly, in one or more illustrative embodiments, the portal212enables users access to view: one or more real-time transactions from across multiple heterogeneous systems associated with a given enterprise; one or more operational metrics from across multiple heterogeneous systems associated with a given enterprise; one or more monitoring systems from across multiple heterogeneous systems associated with a given enterprise; one or more estimated capacity usages from across multiple heterogeneous systems associated with a given enterprise; and monitoring data associated with one or more cloud computing platform services.

Authorization services222are configured to provide authentication of the users before allowing them to access the portal212and provide transaction queries (e.g., single sign on). Notification services224are configured to provide messages (emails, alerts, etc.) to users based on their searches and based on the status of any given transaction of interest. Rules engine226enables system administrators to load rules that the system210follows/executes with regard to various system operations, e.g., authorization, notification, storage, search, analysis, etc.

The centralized enterprise integration and services monitoring portal controller220is configured to control the operations of each of the other components of system210. In one illustrative embodiment, the controller220loads from memory and executes software instructions that are configured to provide the functionalities described herein. The controller can also be in the form of software code which calls other software code that executes the functionalities described herein. In some embodiments, the controller is a combination of hardware and software components. Examples of processing platforms that are able to implement the components shown inFIGS. 1 and 2are described below in the context ofFIGS. 4 and 5.

Given the above-described illustrative embodiments of the centralized enterprise integration and services monitoring framework, an illustrative use case is now described from the perspective of companies that are merging and have a need to enable customers of both companies, and internal personnel of both companies, to access transaction data across the newly formed enterprise.

Tracking business and service transactions across multiple IT systems is important in today's fast-moving business climate. Being able to track them across two major IT companies that recently merged to form one of the largest technology companies in the world is absolutely vital. Accordingly, the centralized enterprise integration and services monitoring framework (e.g.,FIGS. 1 and 2) provides a visualization tool that lets business and IT support teams monitor transactions on a single dashboard. This is a critical step in the integration of merging companies. The monitoring framework brings together all transaction data into a single place where business and support people can see transactions across multiple systems in a comprehensive dashboard.

In one embodiment, the monitoring framework provides access via single sign on, allowing consolidation of different tracking applications that existed in the two companies prior to merging into one application.

Further, assume that each of the companies prior to merger had amassed an array of systems and applications used to monitor transactions and support requests across various databases. Prior to the monitoring framework described herein, business and support users would have to check multiple locations to track a transaction from one phase to the next across the organization.

For example, prior to the monitoring framework, IT personnel might get a call from a business user asking for insights into what is happening with a given sales order. Maybe they already confirmed the transaction data had been processed from the SAP® (SAP America Inc., Newtown Square, Pa.) database but did not know if it ever reached TradeSphere® (Livingston International, Chicago, Ill.), an open-source application used to ensure transactions conform to trade compliance regulations. Further, the business user may be looking for the transaction's status in Salesforce.com® (Salesforce.com Inc., San Francisco, Calif.), a third-party customer relationship management (CRM) application.

With the monitoring framework described herein, such sales representatives, as well as numerous other business users and support providers, can enter the transaction number (into portal212) and find out (search stage214) exactly where their sales order, service request, security enablement process, or manufacturing invoice is in the process. The transaction data is received by the system (210) from the various cloud and enterprise services (230through238).

In one illustrative embodiment, the centralized enterprise integration and services monitoring framework (e.g.,FIGS. 1 and 2) is implemented on Pivotal Spring Framework® (Pivotal Software, Palo Alto, Calif.), which is an open-source application development framework. The search stage (214) includes the enterprise search engine ElasticSearch® (Elasticsearch, Mountain View, Calif.). The monitoring framework, in one illustrative embodiment, may be implemented with Google Material Design® (Google, Mountain View, Calif.) to maximize user experience for visual data presentation; Pivotal Cloud Foundry and Pivotal Gemfire® (Pivotal Software, Palo Alto, Calif.); AngularJS, D3JS & JQuery; Spring Boot and Spring Cloud Microservices® (Pivotal Software, Palo Alto, Calif.); and Slack® (Slack Technologies, Vancouver, Canada).

The result is a single dashboard that is customizable and offers better insights into integrated transaction data, which is also easily maintained. Users can search for transactions faster and see their status all in one place. Replacing a plurality of tracking applications with one results in cost and resource savings.

FIG. 3illustrates a methodology300for providing centralized enterprise integration and services monitoring, according to an illustrative embodiment.

Step302obtains transaction data from cloud (public) services and private services across heterogeneous IT systems of a given enterprise.

Step304analyzes and/or processes the obtained transaction data and stores the raw and initially-analyzed/processed transaction data in one or more data storage arrays.

Step306executes one or more system metrics and monitoring/logging operations on the stored data to generate subsequently-analyzed/processed transaction data and reporting data.

Step308presents the transaction data and results of analysis/processing to one or more authorized users via one or more graphical user interfaces.

Cloud infrastructure as disclosed herein can include cloud-based systems such as AWS, GCP and Microsoft Azure. Virtual machines provided in such systems can be used to implement at least portions of information processing systems in illustrative embodiments. These and other cloud-based systems in illustrative embodiments can include object stores such as AWS S3, GCP Cloud Storage, and Microsoft Azure Blob Storage.

Illustrative embodiments of processing platforms will now be described in greater detail with reference toFIGS. 4 and 5. Although described in the context of systems100and200, these platforms may also be used to implement at least portions of other information processing systems in other embodiments.

FIG. 4shows an example processing platform comprising cloud infrastructure400. The cloud infrastructure400comprises a combination of physical and virtual processing resources that may be utilized to implement at least a portion of the information processing system100. The cloud infrastructure400comprises virtual machines (VMs)402-1,402-2, . . . ,402-L implemented using a hypervisor404. The hypervisor404runs on physical infrastructure405. The cloud infrastructure400further comprises sets of applications410-1,410-2, . . . ,410-L running on respective ones of the virtual machines402-1,402-2, . . . ,402-L under the control of the hypervisor404.

Although only a single hypervisor404is shown in the embodiment ofFIG. 4, the system100may of course include multiple hypervisors each providing a set of virtual machines using at least one underlying physical machine. Different sets of virtual machines provided by one or more hypervisors may be utilized in configuring multiple instances of various components of the systems100and200.

An example of a commercially available hypervisor platform that may be used to implement hypervisor404and possibly other portions of the information processing systems100and200in one or more embodiments is the VMware® vSphere® which may have an associated virtual infrastructure management system such as the VMware® vCenter™. The underlying physical machines may comprise one or more distributed processing platforms that include one or more storage systems.

As is apparent from the above, one or more of the processing modules or other components of systems100and200may each run on a computer, server, storage device or other processing platform element. A given such element may be viewed as an example of what is more generally referred to herein as a “processing device.” The cloud infrastructure400shown inFIG. 4may represent at least a portion of one processing platform. Another example of such a processing platform is processing platform500shown inFIG. 5.

The processing platform500in this embodiment comprises a portion of systems100and200, and includes a plurality of processing devices, denoted502-1,502-2,502-3, . . . ,502-N, which communicate with one another over a network504.

The processing device502-1in the processing platform500comprises a processor510coupled to a memory512.

The memory512may comprise random access memory (RAM), read-only memory (ROM) or other types of memory, in any combination. The memory512and other memories disclosed herein should be viewed as illustrative examples of what are more generally referred to as “processor-readable storage media” storing executable program code of one or more software programs.

Also included in the processing device502-1is network interface circuitry514, which is used to interface the processing device with the network504and other system components, and may comprise conventional transceivers.

The other processing devices502of the processing platform500are assumed to be configured in a manner similar to that shown for processing device502-1in the figure.

As another example, portions of a given processing platform in some embodiments can comprise converged infrastructure such as VxRail™, VxRack™, VxRack™ FLEX, VxBlock™ or Vblock® converged infrastructure from VCE, the Virtual Computing Environment Company, now the Converged Platform and Solutions Division of Dell EMC.

Also, numerous other arrangements of computers, servers, storage devices or other components are possible in the information processing systems100and200. Such components can communicate with other elements of the information processing systems100and200over any type of network or other communication media.

It should again be emphasized that the above-described embodiments of the invention are presented for purposes of illustration only. Many variations may be made in the particular arrangements shown. For example, although described in the context of particular network and device configurations, the techniques are applicable to a wide variety of other types of computer networks and processing device configurations. Moreover, the assumptions made herein in the context of describing some illustrative embodiments should not be construed as limitations or requirements of the invention, and need not apply in other embodiments. Numerous other alternative embodiments within the scope of the appended claims will be readily apparent to those skilled in the art.