Browse Prior Art Database

Early Detection of Potential Long Running Jobs in a Cloud Environment

IP.com Disclosure Number: IPCOM000246661D
Publication Date: 2016-Jun-24
Document File: 4 page(s) / 68K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed is a method to pre-determine that a job is a long-running job in an orchestration on a cloud environment, and then provide suggestions to avoid said long-running job.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 38% of the total text.

Page 01 of 4

Early Detection of Potential Long Running Jobs in a Cloud Environment

Cloud computing is a business evolution that impacts all facets of business including sales, marketing, human capital management, supply chain, finance, manufacturing, quoting, ordering, service, support, email, and so on. Each of these functions requires migration and integration as it moves to the cloud. Additionally, each vendor that provides a cloud solution creates a dedicated interface to the application. This creates a challenge in information technology (IT) organizations in companies of all sizes and across global locations that attempt to understand and then manage these unique application interfaces and integrate applications from cloud-to-cloud and cloud-to-on- premise.

Current platforms are available that meet the challenge of integrating cloud applications with on-premise systems, cloud applications-to-cloud applications, and on-premise-to- on-premise applications. One existing environment focuses on the business requirements, the applications, and the business user requirements. It removes the daunting complexity of integration.

Following the orchestration build, a live function of the integration platform provides the runtime engine for the orchestration to execute the jobs. The job runs on the runtime engine and it is completed with the end of the orchestration flow. However, if the orchestration does not complete, then the job continues running for a longer period, occasionally greater than 24 hours. The main cause is an incorrect orchestration design. The operations team then manually checks the orchestration to determine the exact source of the fault in the design, correct the fault, and end the job.

This practice requires that the operations team manually intervene and research the orchestration in order to correct it. Another problem is that the job has run for more than 24 hours, resulting in no thru put work being done during this time.

The novel contribution is a method to pre-determine that a job is a long-running job in an orchestration on a cloud environment, and then provide suggestions to avoid said long-running job. The method is applicable to many types of application workbenches.

The method provides automatic detection of potential long-running jobs prior to job submission (at an early stage). It eliminates wasted time caused by a long-running job count.

One system that provides an approach to integrating applications does not require any programming knowledge; this is the basis for the following discussion and example embodiments of the proposed method. Integration flows can be built in the application studio , which is a graphical development environment that is installed to a personal computing device. The studio enables a user to create an integration project containing one or more orchestrations. Each orchestration is built with a number of activities that define the flow of data. The details of an activity can be defined f...