Browse Prior Art Database

Organizing Solution Deployment Software Into Multiple Modules

IP.com Disclosure Number: IPCOM000237489D
Publication Date: 2014-Jun-19
Document File: 3 page(s) / 55K

Publishing Venue

The IP.com Prior Art Database

Abstract

A method is disclosed for organizing solution deployment software into multiple modules. The multiple modules may be deployment handlers. The deployment handlers are configured for deploying changes for one artifact or an item or group of items in an artifact.

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

Page 01 of 3

Organizing Solution Deployment Software Into Multiple Modules

Disclosed is a method for organizing solution deployment software into multiple modules. The multiple modules may be deployment handlers. The deployment handlers are configured for deploying changes for one artifact or an item or group of items in an artifact.

In accordance with the disclosed method, the group of items in the artifact may include metadata that defines new classes of objects in a Content Management Repository. The Content Management Repository may include classes of case objects that represent customer cases. The customer cases define custom user defined properties for classes of objects. The group of artifacts in a solution may also include definitions of workflow processes that drive the worker based activities of the solution. The group of items may further include resources that are used to build a web based application such as templates for various pages that build a User Interface (UI), and custom client-side Java Script* classes. The group of items may additionally include supporting resources that are added to the Content Management Repository wherein the resources may be form templates.

The deployment handlers are decoupled from a repository specific batching Application Programming Interface (API), with constraints on maximum number of changes.

Additionally, the deployment handlers may submit changes to a batch collector. Such changes are not submitted to an actual repository until all changes have been submitted to the batch collector. The batch collector then executes this batch upon submitting one or several actual batches of changes to the Content Management Repository.

The disclosed method breaks the deployment process into several phases. For example a first phase may be dedicated to deploying metadata changes to the Content Management Repository. A second phase may be dedicated to deploying process definitions to a process repository. The second phase may be dependent on completion of the first phase because some of the processes may require that the metadata already exist in the Content Management Repository. A third phase may be responsible for applying further content repository changes that depends on changes that have been already applied to the process repository.

In an exemplary embodiment of the disclosed method and system, the deployment process for a single phase is illustrated in Figure 1:

1


Page 02 of 3

Figure 1

Each of the deployment handler modules understands the batching characteristics of the single phase. For example, the single phase may deploy metadata changes to the Content Management Repository and may include a single Batch Collector object. Each deployment handler submits changes to the Batch Collector object when asked to deploy the changes for a particular batch.

Moving on, the disclosed method submits an item representing a change to the Batch Collector in a form that may be submitted as part of an actual batc...