Configuration templates for different use cases for a system

[0001] Embodiments of the invention generally relate to the field of computer systems and, more particularly, to a method and apparatus for configuration templates for different use cases for a system.

[0002] In complex computer systems, the development of a configuration for each particular computer environment can be difficult, and is often a matter of experimentation and guesswork to develop a working model. Because a complex system may include many disparate environments, this generally requires repeating the development process numerous times as various systems in different locations are configured.

[0003] If a configuration is developed for a system and is found to operate effectively, this generally is of little help for other systems. In a conventional operation, a developer or user may wish to copy a configuration over to another system or to develop a configuration for use in multiple systems, but this is generally not possible because of system dependencies built into the configuration. Certain elements of the configuration will depend on the characteristics of the individual computer systems that are configured, and such characteristics will generally be different for each system that is encountered.

[0004] A conventional system configuration is static, and thus is not adaptable to new environments. If a developer or user wishes to copy a working configuration for one system to another system or to develop a configuration for use in multiple computer systems, it is necessary to identify all system dependent configuration elements, to determine how the system dependent configuration elements need to be set to operate in each system, and then to set these configuration elements. Thus, the transfer of a configuration from one system to another is a time-consuming process, and the effort required to correct problems severely limits any advantage that might be gained in copying system configurations or attempting to a common configuration for multiple different systems.

[0005] In addition to other issues, a conventional configuration is not adapted for a particular use of a system. Each conventional configuration is designed for a particular computer system, and thus cannot be designed to address a particular use for multiple systems. For this reason, each use requires a configuration designed for the system, rather than a configuration for a use being usable in multiple systems.

[0006] A method and apparatus for configuration templates for different use cases for a system are described. In one aspect of the invention, a method includes receiving an abstract configuration for a system, the abstract configuration including a setting. The configuration setting is modified with a template, the template being designed for a particular use of the system

[0007] Embodiments of the invention are illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings in which like reference numerals refer to similar elements.

[0008] FIG. 1 is an illustration of the transfer of a configuration in an embodiment of the invention;

[0009] FIG. 2 is an illustration of an embodiment of a system for generation of a configuration;

[0010] FIG. 3 is an illustration of an embodiment of configuration development;

[0011] FIG. 4 is an illustration of an embodiment of configuration development;

[0012] FIG. 5 is a flowchart to illustrate an embodiment of configuration generation; and

[0013] FIG. 6 is an illustration of an embodiment of configuration generation using templates.

[0014] Embodiments of the invention are generally directed to a method and apparatus for templates for different use cases for a system.

[0015] As used herein, a “configuration” describes the manner in which a computer system, device, component, or other element, including any hardware, software, or both, is set up. A configuration may include, but is not limited to, the system name, the amount of memory available, the number of CPUs (central processing units) available, and other related information. A configuration may be described in various different ways in different settings, and may have a different name or designation in certain environments. To reduce repetitiveness in this description, a computer system, device, component, or other element may be referred to generally as a computer system or system. In this description, the computer system that receives a configuration may also be referred to as a configuration recipient or configuration consumer.

[0016] As used herein, a “template” is a form, pattern, set of defaults, or other similar device to establish values. In an embodiment of the invention, a template includes a set of values for a configuration, where a particular set of values may correspond to a certain use case for a system. A template may include, but is not limited to, settings to enable or disable hardware or software elements, settings for memory usages, and other configuration settings.

[0017] In an embodiment of the invention, a configuration may be transferred between computer systems. For example, when a configuration has been developed for a system that works well for a certain use, that same configuration may be exported to another system that is different than the first system. In an embodiment, a configuration may be developed or generated for multiple different systems that have differing characteristics. In an embodiment of the invention, a configuration is virtualized for the elements of each system and is adaptable to each system. For example, a software vendor may utilize an embodiment of the invention to develop a self-adapting configuration together with a software product. In this example, the self-adapting configuration may be shipped together with the product in order to minimize configuration overhead for the customer.

[0018] In an embodiment of the invention, a system configuration utilizes abstract elements that are not dependent on the characteristics of any particular system. In an embodiment, the abstract elements of a configuration are resolved at run-time to generate values that apply to a particular computer system. As used herein, “abstract” means that an element has a value to be determined that is not tied to a particular system, use, or setting. The value of the element is thus expressed in an abstract fashion, with the value resolvable to a specific value in relation to a particular system that is assigned to the configuration.

[0019] In an embodiment of the invention, a system configuration is dynamic, and the determination of the settings for the configuration is based on the nature of each computer system and changes that may occur in a system. A dynamic configuration contrasts with a static configuration in a conventional system, in which the configuration elements need to be modified to work in a particular system. The elements of a dynamic configuration change as the configuration is applied to a system, and may be modified dynamically as the system is modified in order to reflect current values. Thus, in addition to providing for mobility of a configuration, the dynamic values provide for ease in maintenance of the configuration because the elements adapt to reflect the current state of the system.

[0020] In a conventional system, it is not generally possible to copy a configuration from one system to another or to generate a configuration that is usable for multiple different computer systems because of system dependencies. A conventional system will utilize a static configuration having set elements, and a static configuration will not transfer from one system to another system in the same form as was used in the original system. In conventional operations, it is necessary to manually modify each of the system dependent configuration elements to make such elements match the new system. Further, because of the system dependencies and the need to create new values for each configuration, there is no assurance in a conventional process that the same configuration will work in the same way in two systems after all of the elements have been set.

[0021] In an embodiment of the invention, a configuration is abstracted to eliminate the system dependencies in the configuration. In an embodiment, any system environment dependent settings are removed from a configuration database. Instead of static configuration values, a configuration introduces dynamic elements to reflect any current system. The dynamic elements may include parameters that characterize each system that receives the configuration. Parameters may include, but are not limited to, host names, instance names, the number of CPUs, the amount of available memory, and other hardware and software elements. In an embodiment of the invention, a configuration is dynamic and adapts itself to the system environment, thereby enabling the movement of the configuration from one system environment to another. In an embodiment, the only static settings that may exist in a configuration are non-system dependent settings that thus are not tied to any particular system.

[0022] In an embodiment, a configuration element or agent will evaluate abstract configuration elements and substitute the needed values into the configuration to reflect the characteristics of the system that is receiving the configuration. In one embodiment of the invention, a configuration machine or configuration manager will evaluate the abstract configuration elements and determine the values of the configuration elements for the relevant computer system. A configuration machine or manager may be, for example, an API (application program interface) that operates on top of a database for a system. In an embodiment, the configuration manager transparently evaluates the configuration values at run-time to adapt the configuration to the system. However, embodiments of the invention are not limited to any particular component, device, or process for the resolution of configuration elements, but rather include any internal or external agent that can process the configuration elements for a computer system.

[0023] In an embodiment of the invention, an abstract configuration may be created using various different processes. In one embodiment, API methods of a configuration manager may be used directly to generate the abstract configuration. In another embodiment a specially tagged property file, such as a JavaProperty file, may be imported into the configuration manager. For example, an enhanced property file may be imported as a property sheet into a configuration database. Other methods of generating the abstract configuration may be utilized, and embodiments of the invention are not limited to any particular generation process.

[0024] In an embodiment, system dependencies may include any characteristic of a system that may be found in a configuration. Dependencies may include system identification data, system information such as heap size and number of nodes, and hardware availability such as number of CPUs. Each system dependency is expressed in an abstract form in the virtualized configuration in a manner that does not refer to any particular system. The form of the elements in a virtualized configuration may vary in different embodiments. For example, system dependencies may include parameters that are substituted, parameters that require calculation, parameters that rely on or refer to other values, or other types of direct or indirect values.

[0025] In an embodiment of the invention, system configurations may include various default values that are substituted as the values are resolved for a particular computer system. In addition, configuration may be dependent on the intended use of a computer system. Various defaults or settings may be established for different types of uses. The different use cases may be addressed in various ways. In one example, templates, forms, or similar devices may be provided to establish certain parameter values for a configuration.

[0026] In an embodiment of the invention, configurations may be structured or developed in multiple levels, with, for example, “higher” levels providing default and abstract elements, which are shippable across system boundaries. In this example, an upper configuration level is applicable to all systems, but may, for instance, be overridden by lower level configuration levels in certain cases.

[0027] In one embodiment, below an upper configuration level may be a usage defined level, or template level, that provides configuration elements designed for particular use cases. In an embodiment of the invention a system provides for predefined configurations, which may include the use of templates, forms, or similar devices. The usage defined level may override upper level defaults. In an embodiment, the usage defined level is based on the system usage and not the particular system and thus the elements remain abstract for purposes of evaluation in conjunction with the characteristics of the receiving system. The different use cases may, for example, enable and disable components as needed for the particular use case. In one possible example, a developer may wish to turn off much of a system, minimizing the number of nodes, to maximize the system power available to the developer. In another example, a usage case may require enablement of all server nodes to enable the use of a portal that will carry a large amount of traffic.

[0028] In an embodiment of the invention, below the usage defined level may be a system level, which is based on the individual system instance. The system level includes defining the actual system instances belonging to the system. In an embodiment, each system instance derives its configuration from the template level. The settings received from the template level are abstract and dynamically resolved during runtime according to the given system context, which is attached to the system. Thus, in an embodiment of the invention a configuration is self-adapting to the particular system environment. In an embodiment, on the system level customizations might be made that are system specific and thus could be done in a generic or abstract manner on the template level. The system level defines the actual system instances belonging to the system. Each system instance derives its configuration from the template level. These derived settings will still be abstract and dynamically resolved during runtime according to the given system context, which is attached to the system. Thus, the configuration is self-adapting to the particular system environment. On the system level customizations might be done which are system specific and which could not be done in a generic (or abstract) way on the system or template level

[0029] The system level may further include a custom level above the individual instance, with the custom level providing customization of the configuration for application to a particular site. In an embodiment, an additional modification may exist between the default level and the usage case level to provide customization that affects all use cases. Thus, customization may be done either for all instances at a higher level, or at the individual instance level.

[0030] In an embodiment of the invention, templates are used to provide different features for different uses for a system. In an embodiment, a template only provides values that are non-system dependent. After a template has been applied, a configuration remains abstract for the purposes of the system that will receive the configuration. A template may include default values for parameters. In certain instances, settings established by template may be overridden in the resolution of a configuration for a particular system if necessary. In an embodiment, a template that is well designed may require little or no overwriting. In an embodiment of the invention, it is normally not necessary to overwrite the template settings, except in certain special cases, because the settings are abstracted from any particular system environment and thus are valid across different systems.

[0031] In system development, there is an incentive to provide a complete configuration to a customer. In an embodiment of the invention, a customer is only required to provide a use case in order to receive a complete configuration. The designation of the use case determines a template for the configuration. The template then establishes the necessary settings and defaults for the intended use, with the resulting configuration being an abstract structure that adapts to the recipient system. Thus, a configuration template is system independent and may be moved between systems. In an embodiment, a configuration template is derived from a default configuration and may overwrite default settings according to the specific usage to which the template is assigned.

[0032] In an embodiment of the invention, a customer attaches a particular use to a configuration machine. The configuration machine includes a component, such as configuration resolver, that recognizes the used case and finds the correct abstract configuration for the used case, which may referred to as a template for the uses case. The abstract configuration is obtained from a database of abstract configuration elements. In one example, the database contains templates for multiple different usages.

[0033] In operation, a number of instances may be created. Each instance then may be assigned to a particular template, depending on the usage. In one possible example, a JMS (Java messaging service) instance may be assigned to a template that is limited to JMS instances, while other instances are assigned to one or more other templates.

[0034] In an embodiment of the invention, central administration may be used in the formation of configurations. Central administration is a tool that runs within the J2EE engine. The central configuration manages the configuration of system landscapes via corresponding configuration templates. The scope of a configuration template managed by the central configuration is not limited to groups of instances of one system, but rather provides a landscape of several systems. For J2EE configurations within the J2EE engine, central configuration templates are accorded to a particular usage or use case. 100351 During the installation of an application instance, the usage of the instance is not known. For this reason, during installation the application instances are configured via a “minimal instance” configuration template. The minimal instance configuration is sufficient to run the central configuration.

[0035] In an embodiment of the invention, a central configuration is started in order to configure the instances for the specific usage to which each one is attached. During the central configuration, the custom layer configuration from which all instance configurations are derived is assigned to the J2EE configuration according to the particular usage of the system. The custom configuration is derived from the selected configuration template, and the instance configuration of all application instances is derived from the custom configuration.

[0036] In an embodiment of the invention, configuration templates provided (such as within the J2EE engine) are system independent, with any system dependent settings being abstract (via, for example, parameterization and arithmetic expressions). Thus, most of the settings are already correct for a receiving system and do not need be addressed during instance configuration. However, in some embodiments a process may provide for customizing additional engine components.

[0037] The central configuration may be handled in various different ways for configuring settings. For example, if a configuration setting should be modified for all application instances, then the central configuration may access a “custom” configuration in order to modify the setting. If a configuration setting should be changed for only a particular instance, then the setting may be changed on the level of the instance configuration.

[0038] In an embodiment of the invention, templates may be divided into sets that apply to particular processes or other system distinctions. For example, a first set of templates may apply to a first type of process and a second set of templates may apply to a second type of process. In one possible example, one or more templates may apply to a JMS instance and one more templates may apply to any other process. JMS is an API for accessing enterprise messaging systems from Java program. Other embodiments of the invention may divide templates in other ways such that templates in a first set are applicable to a first system and templates in a second set are applicable to a second system.

[0039] In a particular embodiment of the invention for a Java process, templates may apply to use cases and scenarios such as Portal+KM (Knowledge Management) (which may include providing a configuration that is appropriate for operation of a portal), Minimal Instance (to provide a configuration using minimal resources, J2EE Developer (to provide a configuration that is appropriate for development efforts), and other uses.

[0040] In an embodiment of the invention, the technical configuration of a Java system is simplified through the use of virtualized and adaptive configuration. Embodiments of the invention may be described herein in terms of Java objects and processes. However, embodiments of the invention are not limited to any particular system environment. Embodiments of the invention may be applied to any computer environment which includes the use of a configuration or similar structure with one or more system dependent elements.

[0041] The architectures and methodologies discussed above may be implemented with various types of computing systems such as an application server that includes a Java 2 Enterprise Edition (“J2EE”) server that supports Enterprise Java Bean (“EJB”) components and EJB containers (at the business layer) and/or Servlets and Java Server Pages (“JSP”) (at the presentation layer). Other embodiments may be implemented in the context of various different software platforms including, by way of example, Microsoft .NET, Windows/NT, Microsoft Transaction Server (MTS), the Advanced Business Application Programming (“ABAP”) platforms developed by SAP AG, and other computer platforms.

[0042] FIG. 1 is an illustration of the transfer of a configuration in an embodiment of the invention. In this illustration, a first computer system (system 1 105) has a particular configuration 115 that is based at least in part on the system context 120, which includes such elements as the system name, the instance host name, the number of CPUs, the amount of memory available, and other related system factors.

[0043] A second computer system (system 2 110) also contains a configuration 125 that is based at least in part on the system context 130 of the second system 110. If the configuration 115 of the first system 105 has been developed and would be useful in the second system, then there is an incentive to transfer the configuration 135 and thus to re-use the development efforts that went into generating the configuration 115. However, in a conventional process, a configuration generally cannot not be easily copied or transferred because the elements of the configuration are based on the specific system context 120 of the first system 105. In order to perform the transfer of the configuration, the resulting configuration 125 for the second system 110 would have to be modified and corrected to match the system context 130 of the second system 110, which may be a very time consuming process.

[0044] In an embodiment of the invention, a configuration is developed as a virtualized, adaptable configuration that is based on abstract configuration data, and that does not contain any system dependent elements. In this embodiment, the abstract configuration may be provided to the second system 110. The elements of the abstract configuration would be resolved based on the system context 130 of the second system 130 to form the configuration 125 for the second system 110. In an embodiment, it is possible to transfer 135 an adaptable configuration 115 of the first system 105 to the second system 110, or to develop a configuration that is usable in both systems. The abstract and adaptable nature of such virtualized configuration allows for transfer without first making corrections and modifications to the configuration.

[0045] In an embodiment of the invention, the transferred configuration 125 will be automatically resolved, such as through use of a configuration machine or engine. The automatic resolution process may include the transformation of any indirect references, calculated references, and other parameters as needed to match the system context 130 of the second system 110.

[0046] FIG. 2 is an illustration of an embodiment of a system for generation of a configuration. In this illustration, a configuration machine 205 is used to provide a configuration to a consumer of the configuration 215. The consumer may be any component, device, or system that requires a configuration for a particular use. In an embodiment of the invention, a database includes abstract configuration data 220, the abstract data being configuration elements that are not tied to any particular system, but rather are adaptable to a system that receives the configuration. For example, the same abstract configuration data may be used in multiple different systems even though the systems have different system characteristics that require different configuration elements.

[0047] In an embodiment of the invention, a configuration machine 205 includes a configuration resolver 210. The configuration machine 205 receives the abstract configuration data 220 and the configuration resolver 210 resolves the elements of the abstract configuration data to apply to a particular system, in this case including the configuration consumer 215. The configuration is resolved based at least in part on the system context 225 of the relevant system, which includes relevant data regarding the particular system 215 that is to receive the configuration.

[0048] In an embodiment of the invention, a configuration may also be based on the particular use case intended for the system 230. Thus, the configuration may be formed based at least in part on the particular use case of the configuration consumer 215. The use case may provide certain system default elements that are designed for particular uses of a system.

[0049] FIG. 3 is an illustration of an embodiment of configuration development. In an embodiment of the invention, a configuration may be developed in levels, with upper levels providing defaults that may be overridden in lower levels. In an embodiment of the invention, a configuration may inherit elements from upper levels. In one example, an engine level configuration 305 may represent a basic default configuration that is not designed for any particular use or system. The configuration may include abstract elements that are structured as required for a configuration engine or machine that will resolve the elements for a particular system.

[0050] In this example, a use-based (or template) configuration level 310 then defines configurations that are based at least in part on an intended use for a system. This level may provide settings that are appropriate for a particular purpose, which may then be modified as appropriate. In one example, the use-based configuration level may provide that a certain number of nodes be turned on for the purpose of a particular use case.

[0051] A system level configuration 315 inherits a configuration from the use-based configuration level. In some instances, the configuration may be further customized at the system level. The system level defines the actual system instances belonging to the system, with each system instance deriving its configuration from the template level. The derived settings remain abstract and are dynamically resolved during runtime according to the given system context attached to the system. In this manner, a configuration is self-adapting to the particular system environment. On the system level, customizations may be implemented that are system specific, and that could not be accomplished in a generic or abstract manner in an engine level or template level configuration.

[0052] FIG. 4 is an illustration of an embodiment of configuration development. In FIG. 4 a particular example of configuration development is described, but embodiments of the invention are not limited to this particular structure.

[0053] In this illustration, an engine configuration level 405 is illustrated. At this level a configuration engine default configuration is formed 420, which provides a basic instance of the configuration. The basic instance is a virtualized configuration that is abstract and is not tied to any particular system or used case. In one example, a customization of the basic instance 425 may be provided, such customization providing a possible modification of all configuration instances for a system regardless of the particular use of the system.

[0054] Also illustrated in FIG. 4 is a use case configuration, the use case providing the configuration for various different uses of a system, which are illustrated here as Use Case A 430, Use Case B 435, and Use Case C 440. Each use case provides a template or form for a configuration for a particular use of a system. The use case configuration remains an abstract level that is not tied to a particular system.

[0055] A system configuration is also illustrated, including one or more different configuration instances, such as Instance A 450 and Instance B 455. In an embodiment of the invention, the context information for the configuration instances will be accessed in the system context. In an embodiment, the system configurations contain information about the instances that are part of the system, and may further include customizations that could not be defined on an abstract level. In this illustration, the system configuration may also include a customized instance 445, which provides customization for instances received for various different use cases. In other embodiments, there may be multiple customized instances, depending on the particular type of configuration being established.

[0056] FIG. 5 is a flowchart to illustrate an embodiment of configuration generation. In this illustration, a virtualized configuration is developed 505, the virtualized configuration including one or more abstract elements that are not tied to any particular computer system. In an embodiment, the virtualized configuration is adaptable, with the abstract elements intended to be resolved to reflect appropriate values for a system that is receiving a configuration.

[0057] In this illustration, the abstract elements may be stored in a database 510, although the process of building up a configuration may vary in different embodiments of the invention. A recipient system for the configuration is identified 515, and an abstract configuration is provided for the recipient system 520. A configuration engine or other agent may be responsible for generating the configuration and resolving the abstract elements of the configuration. As a part of this process, the system context is identified for the recipient system 525, which thus provides the characteristics of the system for purposes of resolving the configuration elements. A use case may also be identified 530, which may be applicable if a form or template is available to establish a customized configuration.

[0058] A virtualized configuration instance is then generated 535. The configuration engine resolves the abstract elements of the configuration instance for the recipient system 540. In this manner, the configuration adapts to the recipient system, with resolution taking place during runtime within the recipient system.

[0059] FIG. 6 is an illustration of an embodiment of configuration generation using templates. In this illustration, a use case or template configuration 605 may include multiple different templates. There may be initially a minimal instance template 610 used during installation to generate a minimal or default configuration. For the configuration process, there are various templates for specific use case, including a J2EE developer template 615 and Portal KM template 620. There is also a JMS instance template for the special case of JMS instances 625. Also illustrated is the system configuration level 630, which works with the use case templates. In this example, there are multiple relevant instances 640, shown as Instance 1 650 through Instance n 655, and JMS instances, shown as JMS Instance 1 665 through JMS Instance n 670, assigned to a system 635. There may also be a system customization process, which is illustrated as a custom application instance 675 and custom JMS instance 680.

[0060] In an embodiment of the invention, the illustrated templates may be used to establish configurations that are appropriate for a particular use of a system. In an embodiment, the templates provide settings that establish needed system settings for the designated use. In an embodiment, the templates remain abstract and system independent, and thus can be used for multiple different computer systems.

[0061] It should be appreciated that reference throughout this specification to “one embodiment” or “an embodiment” means that a particular feature, structure or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Therefore, it is emphasized and should be appreciated that two or more references to “an embodiment” or “one embodiment” or “an alternative embodiment” in various portions of this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures or characteristics may be combined as suitable in one or more embodiments of the invention.

[0062] Similarly, it should be appreciated that in the foregoing description of exemplary embodiments of the invention, various features of the invention are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the disclosure aiding in the understanding of one or more of the various inventive aspects. This method of disclosure, however, is not to be interpreted as reflecting an intention that the claimed invention requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the detailed description are hereby expressly incorporated into this detailed description, with each claim standing on its own as a separate embodiment of this invention.