Loosely coupled product install and configuration

• US 8,589,912 B2
• Filed: 06/29/2007
• Issued: 11/19/2013
• Est. Priority Date: 06/29/2007
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Hinton, Heather M., Milman, Ivan M., Wardrop, Patrick R.
• Primary Examiner(s): Dao, Thuy
• Assistant Examiner(s): Luu, Cuong V
• Application Number:
  US11/770,860
• Publication Number:
  US 20090007094A1
• Time in Patent Office: 2,335 Days
• Field of Search: 717/178
• US Class Current: 717/174
• CPC Class Codes: G06F 8/60 Software deployment

Abstract

A method, system and program are provided for managing the installation and configuration of a software product by using a proxy service to loosely couple the installation and/or configuration of constituent modules within the installation/configuration flow of the software product. The proxy service invokes the installation/configuration processing of an existing software component, thereby reducing the complexity associated with installing new component installation processes every time a component is to be supported, especially where the software products and new component(s) do not share the same installation/configuration platforms.

Claims

1. A process-implemented method for installing a software product within a data processing system, the method comprising:

identifying, for a software product, one or more prerequisite components during an installation process flow for the software product;

building, for one or more of the prerequisite components, a list of a plurality of provider options comprising a first provider option that identifies a re-usable component that has previously been installed;

displaying information identifying a first prerequisite component along with a corresponding list of the plurality of provider options for the first prerequisite component comprising the first provider option that identifies the re-usable component that has previously been installed for the first prerequisite component;

receiving a user selection of the first provider option; and

invoking, within the installation process flow for the software product, a component configuration process flow for the re-usable component identified by the first provider option.

2. The method of claim 1, where building a list of a plurality of provider options comprises accessing a deployed product itemization data store which stores information identifying provider options for the plurality of previously deployed components in a distributed data processing system.

3. The method of claim 1, where receiving a user selection of the first provider option comprises receiving a selection for a specific re-usable component, selected from the list of available components.

4. The method of claim 1, where building a list of a plurality of provider options comprises excluding from the list any provider option for a component that is not available for re-use.

5. The method of claim 1, further comprising:

collecting required configuration information for the re-usable component; and

configuring the re-usable component using the required configuration information.

6. The method of claim 5, where collecting required configuration information comprises accessing configuration data for the re-usable component by accessing a configuration management data store.

7. The method of claim 6, where collecting required configuration information comprises collecting configuration information from the user that is used to provide additional runtime configuration of the re-usable component.

8. A non-transitory computer-usable medium embodying computer program code, the computer program code comprising computer executable instructions configured for installing and configuring one or more prerequisite components in a data processing system by:

identifying, for a software product, one or more prerequisite components during an installation process flow for the software product;

building, for one or more of the prerequisite components, a list of a plurality of provider options comprising a first provider option that identifies a re-usable component that has previously been installed;

receiving a user selection of the first provider option; and

invoking, within the installation process flow for the software product, a component configuration process flow for the re-usable component identified by the first provider option.

9. The non-transitory computer-usable medium of claim 8, where building a list of a plurality of provider options comprises accessing a deployed product itemization data store which stores information identifying provider options for the plurality of previously deployed components in a distributed data processing system.

10. The non-transitory computer-usable medium of claim 8, where receiving a user selection of the first provider option comprises receiving a selection for a specific re-usable component, selected from the list of available components.

11. The non-transitory computer-usable medium of claim 8, where building a list of a plurality of provider options comprises excluding from the list any provider option for a component that is not available for re-use.

12. The non-transitory computer-usable medium of claim 8, wherein the embodied computer program code further comprises computer executable instructions configured for:

collecting required configuration information for the re-usable component; and

configuring the re-usable component using the required configuration information.

13. The non-transitory computer-usable medium of claim 12, where collecting required configuration information comprises accessing configuration data for the re-usable component by accessing a configuration management data store.

14. A data processing system comprising:

a processor;

a data bus coupled to the processor; and

a computer-usable medium embodying computer program code, the computer-usable medium being coupled to the data bus, the computer program code comprising instructions executable by the processor and configured for installing and configuring one or more prerequisite components in the data processing system by;

identifying, for a software product, one or more prerequisite components during an installation process flow for the software product;

building, for one or more of the prerequisite components, a list of a plurality of provider options comprising a first provider option that identifies a re-usable component that has previously been installed;

receiving a user selection of the first provider option; and

invoking, within the installation process flow for the software product, a component configuration process flow for the re-usable component identified by the first provider option.

15. The data processing system of claim 14, where building a list of a plurality of provider options comprises accessing a deployed product itemization data store which stores information identifying provider options for the plurality of previously deployed components in a distributed data processing system.

16. The data processing system of claim 14, where receiving a user selection of the first provider option comprises receiving a selection for a specific re-usable component, selected from the list of available components.

17. The data processing system of claim 14, where building a list of a plurality of provider options comprises excluding from the list any provider option for a component that is not available for re-use.

18. The data processing system of claim 14, wherein the embodied computer program code further comprises computer executable instructions configured for:

collecting required configuration information for the re-usable component; and

configuring the re-usable component using the required configuration information.

19. The data processing system of claim 18, where collecting required configuration information comprises accessing configuration data for the re-usable component by accessing a configuration management data store.

20. The data processing system of claim 19, where collecting required configuration information comprises collecting configuration information from the user that is used to provide additional runtime configuration of the re-usable component.