Browse Prior Art Database

Wrapping a Command Invocation in a Process

IP.com Disclosure Number: IPCOM000174981D
Original Publication Date: 2008-Sep-30
Included in the Prior Art Database: 2008-Sep-30
Document File: 1 page(s) / 19K

Publishing Venue

IBM

Abstract

A framework design that supports a Command Invocation to be placed within a Process that is under Change Control and be executed in an automated fashion.

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

Page 1 of 1

Wrapping a Command Invocation in a Process

A framework design is disclosed that supports a Command Invocation to be placed within a Process that is under Change Control and be executed in an automated fashion. By supporting a command object as part of a Change Process and as part of the remote invocation, this allows for the inputs and outputs of the invocation to be retained for historical/audit purposes.

In data centers, Change Management is a key ITIL (Information Technology Infrastructure Library)

process in implementing changes. Today, the precision in communication between the

approver and the actual task implementer is not complete. The approver goes by what has been described at a high level and the implementer then translates it into actual invocations, including specific parameters that make up the invocation. The approver doesn't approve parameter level descriptions of intended changes. This new design tightens the linkage between the intention of a change approver and actual implementer of the change

The design supports the creation and persistence of a command object that can be used to drive the execution of an operation on a remote application, for example, a change request object can initiate the implementation of a software patch on a server. The object allows operators to identify the necessary commands during an approval process. Once approved, the automatic invocation takes place using the commands supp...