Interaction manager template

• US 20030229884A1
• Filed: 03/27/2003
• Published: 12/11/2003
• Est. Priority Date: 05/21/2002
• Status: Abandoned Application

• Current Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Original Assignee: Hewlett-Packard Development Co. (HP Inc.)
• Inventors: Carr, Steven R., Muthuswamy, Venkatakrishnan, Gentilozzi, Harry V., Har, Tudor I.
• Application Number:
  US10/402,482
• Publication Number:
  US 20030229884A1
• Time in Patent Office: Days
• US Class Current: 717/101
• CPC Class Codes: G06F 16/217 Database tuning G06F16/2282 takes precedence; database performance monitoring G06F11/3409
• CPC Class Codes: G06F 16/2465 Query processing support for facilitating data mining operations in structured databases
• CPC Class Codes: G06Q 30/02 Marketing; Price estimation or determination; Fundraising

Abstract

A template for deployment of enterprise applications one example of which is an interaction manager. For deployment of the interaction manager, the template is configured with a class framework for building source code of the interaction manager and a test driver. The template is further configured with wizards. An application wizard provides for building a base class portion of the class framework. Interaction and attribute wizards provide for extending or modifying the class framework once the base class portion is built so as to provide for enterprise-specific deployment of the interaction manager along with the test driver. In addition, test driver script is provided through which the test driver is to be used for validating and measuring the performance of the interaction manager once their source code is converted to executable code.

Claims

1. A template fashioning a deployment framework, comprising:

an application sub-framework;

a business logic sub-framework; and

a test driver sub-framework,

wherein the template is adaptable with wizards for deployment that is enterprise-specific, and wherein the application, business logic and test driver sub-frameworks provide a mechanism for deploying an application along with a test driver for validating and measuring the performance of the application.

2. A template as in claim 1, wherein the application is an enterprise application, and wherein the template is a set of programming tools for developing and deploying enterprise applications.

3. A template as in claim 2, wherein the application is an interaction manager (IM) which is one of the enterprise applications and wherein the template is an IM template.

4. A template as in claim 3, wherein the deployment framework is a mechanism for deployment of the IM as a server along with deployment of a test driver as a client or for deployment of the IM along with the test driver as a standalone test application.

5. A template as in claim 4, wherein the deployed server and client are CORBA or Tuxedo-based.

6. A template as in claim 4, wherein the deployed test driver is platform independent, designed for performing functional testing and debugging and performance testing.

7. A template as in claim 4, wherein the deployed test driver is designed to test various enterprise-specific operation cases or code paths and generate a large volume of activity for large-scale performance testing of the IM.

8. A template as in claim 4, wherein the deployed test driver works off of a script and is instrumented for performance measurements.

9. A template as in claim 2, wherein the set of programming tools is included in a zero latency enterprise (ZLE) development kit (ZDK).

10. A template as in claim 3, wherein the deployed IM is designed to provide a way for initiating and resuming a session in which a guest is identified via a cookie if anonymous browsing is supported, and wherein the template is configured for deployment of the IM that omits a cookie table for associating the session with the cookie if the anonymous browsing is not supported.

11. A template as in claim 1, wherein the wizards provide for customized deployment of the IM in that they include

an application wizard to be invoked for generating an IM source,

an interaction wizard to be invoked for defining a data object or an interaction type, wherein each time the interaction wizard is invoked a defined data object or an interaction type is added to the IM source, and

an attribute wizard to be invoked for defining each attribute of one of the defined data objects or interaction types.

12. A template as in claim 1, wherein the wizards are configured for maintaining application interface for either one of CORBA and Tuxedo related information.

13. A template as in claim 1, wherein the wizards are implemented with Perl scripts to be invoked via a batch file or manually via a command lines.

14. A template as in claim 1, wherein the wizards are designed for invocation by a Perl command along with parameters.

15. A template as in claim 11, wherein a data object represents a table, the interaction type references the table and each attribute associated therewith represents a column in the table.

16. A template as in claim 15, wherein the table is located at an operation data store (ODS) within a ZLE infrastructure.

17. A template as in claim 11, wherein the application is an IM deployed with business logic and designed for leveraging a rules engine designed to process business rules, wherein the data objects are relevant to the business rules or to the business logic.

18. A template as in claim 11, wherein the application wizard is designed for creating a number of base classes of the IM source and the interaction wizard is designed for creating additional classes each time it is invoked such that the additional classes are respectively connected to the base classes via hooks in such base classes.

19. A template as in claim 11, wherein the attribute wizard adds lines of code to or updates a previously created class.

20. A template as in claim 11, wherein the interaction wizard is designed to create classes associated with the interaction type being defined thereby, and wherein the attribute wizard is designed to touch each class associated with that interaction type when its invocation specifies that interaction type.

21. A template as in claim 1, wherein for each instance of the application being deployed there is a project file located in a directory in which all source files related to the project file are located.

22. A template as in claim 1, wherein the application is deployed with business logic specific to the enterprise via the wizards.

23. A template as in claim 21, wherein there are build targets defined within the project file including

a first library containing modules for composing and/or extending the business logic sub-framework,

a second library containing modules for composing or extending the test driver sub-framework,

a standalone test modules associated with the modules of both the first and second libraries,

server modules associated with the modules of the first library, and

client modules associated with the modules of the second library.

24. A template as in claim 23, wherein the first and second libraries are first to be built among the build targets.

25. A method for deploying an interaction manager (IM), comprising:

producing a template adaptable with wizards for enterprise-specific deployment of an IM along with a test driver, the wizards including

an application wizard,

an interaction wizard, and

an attribute wizard;

invoking the application wizard which invocation instantiates a project file with a set of base classes that define build targets of which a first target include common and business logic library, a second target includes a test driver library and a third target includes a stand alone test program with modules linked to the first and second targets;

invoking the interaction wizard once for each enterprise-specific interaction type and data object which invocation creates classes and connects them to any of the base classes that are named in the interaction wizard invocation;

invoking the attribute wizard once for each attribute of the enterprise-specific interaction type and data object which invocation adds lines of code to or modifies any of the classes that are named in the attribute wizard invocation; and

compiling and linking the classes and base classes and creating therefrom the IM in the form of an executable file.

26. A method for deploying an IM as in claim 25, further comprising:

building a fourth target that fashions a CORBA server with modules linked to the first target; and

building a fifth target that fashions a CORBA client with modules linked to the second target.

27. A method for deploying an IM as in claim 25, further comprising:

building a fourth target that fashions a Tuxedo server with modules linked to the first target; and

building a fifth target that fashions a Tuxedo client with modules linked to the second target.

28. A system for deploying an interaction manager (IM), comprising:

means for providing a template adaptable with wizards for enterprise-specific deployment of the IM along with a test driver, the wizards including

an application wizard,

an interaction wizard, and

an attribute wizard;

means for invoking the application wizard which invocation instantiates a project file with a set of base classes that define build targets of which a first target include common and business logic library, a second target includes a test driver library and a third target includes a stand alone test program with modules linked to the first and second targets;

means for invoking the interaction wizard once for each enterprise-specific interaction type and data object which invocation creates classes and connects them to any of the base classes that are named in the interaction wizard invocation;

means for invoking the attribute wizard once for each attribute of the enterprise-specific interaction type and data object which invocation adds lines of code to or modifies any of the classes that are named in the attribute wizard invocation; and

means for compiling and linking the classes and base classes and for creating therefrom the IM in the form of an executable file.

29. A system for deploying an IM as in claim 28, further comprising:

means for building a fourth target that fashions a CORBA server with modules linked to the first target; and

means for building a fifth target that fashions a CORBA client with modules linked to the second target.

30. A system for deploying an IM as in claim 28, further comprising:

means for building a fourth target that fashions a Tuxedo server with modules linked to the first target; and

means for building a fifth target that fashions a Tuxedo client with modules linked to the second target.

31. An interaction manager (IM) template, comprising:

a class framework for building source code of an interaction manager and a test driver;

wizards including

an application wizard for building a base class portion of the class framework, and

interaction and attribute wizards for extending or modifying the class framework once the base class portion is built so as to provide for enterprise-specific deployment of the interaction manager along with the test driver;

test driver script through which the test driver is to be used for validating and measuring the performance of the interaction manager once their source code is converted to executable code.

32. An IM template as in claim 31, wherein the base class portion created via the application wizard fashions objects that are always part of the class framework, including session, customer and offer objects, and wherein the attribute wizard adds to or modifies attributes of these objects.