Method and apparatus for solution-template based deployment and management of an integration solution

CROSS REFERENCE TO RELATED APPLICATIONS

0001This application is related to U.S. patent application Ser. No. 10/682,800 filed Oct. 10, 2003 entitled “SYSTEM AND METHOD FOR GENERATING A BUSINESS PROCESS INTEGRATION AND MANAGEMENT (BPIM) SOLUTION”, which is commonly assigned with the present application and is incorporated herein by reference.

BACKGROUND OF THE INVENTION

00021. Field of the Invention

0003The present invention generally relates to a system and method of deployment and management of an integration solution and, in particular, to use of platform independent solution-template techniques for deployment and management of an integration solution.

00042. Background Description

0005Once developed, an integration solution must be deployed and managed. However, current approaches to deployment tend to be fragmented around the various components of the solution. Development tools provide integrated deployment and management capabilities within the tool, but a typical integration solution contains components developed separately or from different tools. Consequently, the tool-based integrated deployment and management capabilities do not have an overall view of the solution for all participating components and their relationships, and fail to capture deployment requirements prior to the deployment. Current management tools understand individual components, and can be taught about the dependencies amongst them, but lack the notion of an overall solution. The process of transferring the knowledge about deployment and management to a suitable management tool, so that the tool will have the details of the integration solution, is labor intensive and requires special skill. Therefore, the integration solution can't be effectively and efficiently deployed. Furthermore, effective and efficient deployment of an integration solution involving components developed separately or from different tools cannot be accomplished unless the deployment process can be executed by non-experts.

SUMMARY OF THE INVENTION

0006It is therefore an object of the present invention to provide an automated methodology for capturing knowledge about the details of deployment and management from the viewpoint of an overall integration solution.

0007A further object of the invention is to provide a solution-template based methodology for using the captured details of deployment and management of an integration solution to enable efficient and effective deployment.

0008Another object of the invention is to provide deployment solution templates developed by experts, so that non-experts can implement the deployment of integration solutions.

0009An aspect of the invention is a a method for automating the deployment and lifecycle management of an integration solution. The method uses a deployment solution template to gather information for deployment of the integration solution. This deployment information captures the computing environment topology into which the integration solution is being deployed and the resource requirements and non-functional requirements of the integration solution and its components. The method then automatically matches the components of the integration solution to the environment topology, the deployment solution template having been designed so that the captured deployment information is sufficient to enable said automatic matching.

0010The present invention extends the solution template concept of related U.S. patent application Ser. No. 10/682,800 to support the deployment and management of the integration solution. For the purposes of deployment, however, the template concept can be applied to an integration solution even where the template concept was not used in developing the integration solution itself. Whether or not the integration solution was developed using the template concept, the integration solution will be comprised of components. Under the solution template concept, as applied to deployment, the component definitions, platform requirements and performance characteristics of each component of the integration solution are gathered. Once the physical (i.e. environment) topology available to the user is provided (through automated discovery or otherwise), the deployment solution template can then be augmented to provide a deployment layout that matches the deployment requirements. The solution template can be enriched with component specific information to fine tune the deployment automation of each component, i.e. specific information can be provided about the configuration settings and performance parameters of each component. The deployment solution template provides a structure for gathering this information, thereby providing a framework and supporting data for automated analysis of deployment options, presentation of choices to users, and using responses to these user choices to refine automation of the deployment.

0011For example, a new version of an integration solution may provide additional capabilities for a particular component, requiring either that certain servers, being used for that component in the current deployment, be upgraded or that the component be moved to another server. These deployment options can be identified by automated analysis and presented to the user, with the answers of the user being used to automate the deployment. Through this mechanism, users who are not experts in deployment of an integration solution are able to manage the deployment.

0012The augmented solution template reflects the knowledge and experience of experts, and provides a place to put the information identified by those experts as being necessary or helpful in order to deploy and manage the integration solution. Sufficient information is gathered in this process to successfully manage the deployment from the point of view of the overall integration solution. The structure of the augmented solution template enables automated analysis, based on the information gathered and structured in accordance with the template, so that the deployment process can be optimized.

0013By extending the solution template concept to cover deployment, the solution template becomes the unifying artifact throughout the life cycle of the integration solution. The deployment solution template provides a comprehensive and systematic structure for recording all the information required to automate the deployment. It should be emphasized that the deployment solution template serves as a unifying artifact whether or not the solution template concept was used to develop the integration solution. This unifying artifact provides a structure for information usable for automated analysis of deployment options. Furthermore, this automation approach enables optimization of available IT resources based upon the requirements and performance characteristics of the deployment solution.

0014Also, as the template is enriched during deployment, the added information can be provided to the management phase, thereby allowing the management tools to provide a complete view of the integration solution. Solution upgrades can reuse this information, expediting the process of deployment for newer versions of the integration solution. In addition, the information collected for one deployment can be applied the next time around to a different configuration with similar requirements.

BRIEF DESCRIPTION OF THE DRAWINGS

0015The foregoing and other objects, aspects and advantages will be better understood from the following detailed description of a preferred embodiment of the invention with reference to the drawings, in which:

0016<figref idref="DRAWINGS">FIG. 1</figref> is a diagram showing a deployment methodology in accordance with the invention.

0017<figref idref="DRAWINGS">FIG. 2</figref> is a diagram showing an XML schema for a solution deployment template.

DETAILED DESCRIPTION OF A PREFERRED EMBODIMENT OF THE INVENTION

0018Referring now to the drawings, and more particularly to <figref idref="DRAWINGS">FIG. 1</figref>, there is shown a methodology for implementation of the invention. The invention assumes development <b>105</b> of an integration solution <b>110</b> comprised of components separately developed, often using different tools. The integration solution <b>110</b> will provide descriptive information about the components and their inter-relationships within the solution, including component definitions. There will also be developed solution deployment requirements <b>115</b> (such as the resource requirements of each component and platform requirements), and solution non-functional requirements <b>120</b> (such as performance characteristics). This information will be entered into an appropriate solution deployment template <b>160</b>. The solution deployment template <b>160</b> is a structure reflecting the expertise of those experienced in deployment, and may therefore require, for example, particular details of information regarding component resource requirements, such as usage patterns over time as well as data storage requirements, depending upon the nature of the integration solution application.

0019The organization and structure of these particulars may vary with the size and complexity of the integration solution <b>110</b>, the particulars of solution deployment requirements <b>115</b> and non-functional requirements <b>120</b>, and the environment topology <b>125</b> of the computing resources on which the integration solution is to be deployed. Consequently, it may be appropriate to develop a variety of deployment templates <b>160</b>.

0020The invention is implemented through a deployment process <b>100</b> (further detailed in a metamodel described in <figref idref="DRAWINGS">FIG. 2</figref>) using solution deployment templates <b>160</b> to capture deployment requirements <b>115</b> and non-functional requirements <b>120</b> for deploying the integration solution <b>110</b>, and for describing the environment topology <b>125</b> where the integration solution <b>110</b> would be deployed and subsequently executed and managed. The deployment process <b>100</b> provides for matching <b>130</b> the integration solution <b>110</b> to the environment topology <b>125</b> and, optionally, provides an algorithm <b>140</b> for optimizing usage of available IT resources (identified in the environment topology <b>125</b>) based on the solution deployment requirements <b>115</b> and the solution non-functional requirements <b>120</b>. The deployment template <b>160</b> selected and used in this process may be customized <b>150</b>, and is then used to implement the deployed solution <b>170</b>. In addition, these customized solution deployment templates <b>150</b> can be stored in the deployment template repository <b>160</b> for later use.

0021<figref idref="DRAWINGS">FIG. 2</figref> shows an XML solution deployment template schema <b>210</b> for structuring the deployment templates <b>160</b>. The schema <b>210</b> contains a preamble <b>215</b> and a solution deployment model <b>220</b>, which includes a model <b>230</b> of the integration solution <b>110</b>, a model <b>240</b> of the deployment topology <b>125</b>, and a model <b>250</b> of the deployed solution <b>170</b>. Within a requirements section <b>235</b> there are models <b>260</b> and <b>270</b>, respectively, of solution deployment requirements <b>115</b> and non-functional requirements <b>120</b>.

0022Returning again to <figref idref="DRAWINGS">FIG. 1</figref>, the optimal matching algorithm <b>140</b> may be responsive to a variety of objectives. For example, the objective may be to deploy the integration solution <b>110</b> on a minimum number of servers. Or, alternatively, the objective may be to achieve the fastest performance of integration solution <b>110</b>. The information required to execute an optimizing algorithm is gathered by using a selected one of the solution deployment templates in the repository <b>160</b>. This information will include the resource constraints applicable to the servers identified in the available deployment topology <b>125</b> as well as the resource constraints applicable to the components of the integration solution <b>110</b>. For example, for variables X_ij=0 or 1, where 1 indicates component i of integration solution <b>110</b> is being deployed on server j, 0 otherwise, the algorithm

0023<maths id="MATH-US-00001" num="00001"><math overflow="scroll"><mrow><mrow><munderover><mo>∑</mo><mrow><mi>j</mi><mo>=</mo><mn>1</mn></mrow><mi>n</mi></munderover><mo>⁢</mo><msub><mi>X</mi><mi>aj</mi></msub></mrow><mo>=</mo><mn>1</mn></mrow></math></maths><br /> indicates that component a should be deployed on one and only one server.

0024While the invention has been described in terms of a single preferred embodiment, those skilled in the art will recognize that the invention can be practiced with modification within the spirit and scope of the appended claims.