Browse Prior Art Database

Method of common reusable process flow node to integrate with IT resource lifecycle management software from IT service management process layer

IP.com Disclosure Number: IPCOM000216732D
Publication Date: 2012-Apr-16
Document File: 3 page(s) / 53K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed is a new design method for the integration between a runbook process flow with an IT resource lifecycle management server and, potentially, any task automation or external system. It uses of a general and reusable sub-process that is parameterized/customized by an external and previous workflow action.

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

Page 01 of 3

Method of common reusable process flow node to integrate with IT resource lifecycle management software from IT service management process layer

This invention disclosure addresses the issues of integrating IT resource lifecycle management software tasks/workflows for datacenter automation into IT service management processes. The current solution for integrating with the provisioning process via the IT service management is to expose provisioning functions as IT process actions and then build the process workflow by adding this action as one of the steps. This approach provides the basic building block of integrating the provisioning function (task level automation) with process level automation (e.g., Run Book Automation (RBA)). The smallest unit of the building block to talk to IT resource lifecycle management software from the runbook process flow is to define an action to make a provisioning manager task invocation, a step of monitoring the provisioning status, and a step of retrieving the output parameters or error details from the provisioning engine. This solution has the following limitations:


• It is not flexible in the way input/output parameters are passed and retrieved to the provisioning manager action


• It is visually/graphically complex, as it requires a sequence of workflow steps for running a simple process management function. A system could encapsulate these building blocks into a sub-process to hide this complexity.


• Reusing the same action in several process flows is difficult

The disclosed invention addresses these previous limitations and provides a general integration approach that is applicable to provisioning management as well as other task execution tools integration use cases. It does not depend on any specific implementation from any external application; thus, the same integration method is applicable to several tools.

This approach also needs to consider that the provisioning engine or task execution tool may be residing in a remote system, so this integration encapsulation layer can handle remote integration with the provisioning function.

Some existing products provide a specific approach to invoking provisioning tasks; however, they might rely on their specific data model (e.g., management plan module, service topology) to integrate with provisioning manager tasks from the process level. This integration does not work with a general approach when an automation manager product is not present. Additionally, an automation manager integration module does not support the use cases where the provisioning system is on a remote server, and all assumptions within the provisioning integration prevents the integrat...