Single access to common user/application information

• US 5,897,635 A
• Filed: 06/07/1995
• Issued: 04/27/1999
• Est. Priority Date: 06/07/1995
• Status: Expired due to Term

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Collins, Michael, Torres, Robert J.
• Primary Examiner(s): Lintz, Paul R.
• Assistant Examiner(s): Corrielus, Jean M.
• Application Number:
  US08/474,396
• Time in Patent Office: 1,420 Days
• Field of Search: 395/600, 395/200.3, 395/701, 707/10, 707/104, 711/147
• US Class Current: 1/1
• CPC Class Codes: G06F 9/451 Execution arrangements for user interfaces
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing

Abstract

The present invention is directed of a method for centralized storage of user and application information where user and application information can be added, deleted, modified, updated, and enhanced to customize user compute environments and to improve overall system administration and oversight. The information is stored in a database file which is interfaced with the user and/or system administrator through a customization user interface (CUI). The CUI includes windowing functionality and allows the user to invoke the method steps for adding, deleting, and updating user information and for adding, deleting, and updating application information.

Claims

1. A method for centrally storing user and application information and automatically distributing such information to and from heterogeneous applications requiring directory and enrollment information, the applications installed in a distributed computer environment running a windowing type operating system, the method comprising the steps of:

a. installing a localized user and application information procedure (LUAIP) comprising a central datafile, a customization user interface (CUI ), and a plurality of data entries manipulation user invocable procedures designed to modify the information contained in the datafile and in the installed applications;

b. monitoring data entry devices for user input from a series of menus or icons associated with a CUI display window designed to select an invocable procedure associated with the LUAIP;

c. executing the selected LUAIP procedure to accomplish the user modification of one or more datafile entries and/or the information associated with one or more installed applications, thereby automatically synchronizing the directory and enrolment information in the central datafile and the installed applications; and

d. returning to the monitoring step (b) for further user input.

2. The method of claim 1, wherein the procedures comprise an add user procedure, a delete user procedure, an update user procedure, and an update self procedure.

3. The method of claim 1, wherein the CUI comprises a plurality of profiles including at least a user profile and at least one application profile displayed in a profile display area of the CUI window where each profile is represented by a tab associated with an active profile.

4. The method of claim 3, wherein the CUI further comprises tabs associated with an active profile window in the profile display area where the tabs are designed to designate profile specific information.

5. The method of claim 2, wherein the add user procedure comprises the steps of:

a. adding a user to the address book;

b. analyzing the transaction;

c. checking the transaction in an application enrollment conditional branch step;

d. branching to a yes path due to a successful enrollment check;

e. generating an enrollment request from the yes branch;

f. sending the enrollment request to the application;

g. waiting for a response from the application;

h. checking a status of the application response in a check status conditional branch;

i. branching to an error handling logic unit in response to an error status;

j. branching to a send next step in response to a successful status;

k. jumping back to step (e) to complete any additional add user requests in a send nest step;

l. branching to a no path due to an unsuccessful enrollment check;

m. committing all changes to the datafile; and

n. returning to the monitor events step.

6. The method of claim 2, wherein the delete user procedure comprises the steps of:

a. deleting a user from the address book;

b. analyzing the transaction;

c. checking the transaction in an application delete conditional branch step;

d. branching to a yes path due to a successful delete check;

e. generating a delete request from the yes branch;

f. sending the delete request to the application;

g. waiting for a response from the application;

h. checking a status of the application response in a check status conditional branch;

i. branching to an error handling logic unit in response to an error status;

j. branching to a send next step in response to a successful status;

k. jumping back to step (e) to complete any additional delete user requests in a send next step;

l. branching to a no path due to an unsuccessful delete check;

m. committing all changes to the datafile; and

n. returning to the monitor events step.

7. The method of claim 2, wherein the update user procedure comprises the steps of:

a. locking the record in the datafile;

b. updating information associated with a user;

c. analyzing the transaction;

d. checking the transaction in an update datafile conditional branch step;

e. branching to a yes path due to an update datafile check and updating the datafile in accordance with the inputted update and continuing to an add or update enrollment check;

f. continuing through a no path to the add or update enrollment check;

g. checking the transaction for an add or update enrollment request in the add or update enrollment conditional branch step;

h. branching to a yes path due to a successful enrollment check;

i. generating an enrollment request from the yes branch;

j. sending the enrollment request to the application;

k. waiting for a response from the application;

l. checking a status of the application response in a check status conditional branch;

m. branching to an error handling logic unit in response to an error status;

n. branching to a send next step in response to a successful status;

o. jumping back to step (e) to complete any additional enrollment requests in a send next step;

p. branching to a no path due to an unsuccessful enrollment check;

q. committing all changes to the datafile; and

r. returning to the monitor events step.

8. The method of claim 2, wherein the update self procedure comprises the steps of:

a. locking the record in the datafile;

b. updating information associated with a user;

c. analyzing the transaction;

d. checking the transaction in an update datafile conditional branch step;

e. branching to a yes path due to an update datafile check and updating the datafile in accordance with the inputted update and continuing to an add or update enrollment check;

f. continuing through a no path to the add or update enrollment check;

g. checking the transaction for an add or update enrollment request in the add or update enrollment conditional branch step;

h. branching to a yes path due to a successful enrollment check;

i. generating an enrollment request from the yes branch;

j. sending the enrollment request to the application;

k. waiting for a response from the application;

l. checking a status of the application response in a check status conditional branch;

m. branching to an error handling logic unit in response to an error status;

n. branching to a send next step in response to a successful status;

o. jumping back to step (e) to complete any additional enrollment requests in a send next step;

p. branching to a no path due to an unsuccessful enrollment check;

q. committing all changes to the datafile; and

r. returning to the monitor events step.

9. Apparatus for centrally storing user and application information and automatically distributing such information to and from heterogeneous applications requiring directory and enrollment information, the applications installed in a distributed computer environment running a windowing type operating system comprising the steps of:

a. means for installing a localized user and application information procedure (LUAIP) comprising a central datafile, a customization user interface (CUI), and a plurality of data entries manipulation user invocable procedures designed to modify the information contained in the datafile and in the installed applications;

b. means for monitoring data entry devices for user input from a series of menus or icons associated with a CUI display window designed to select an invocable procedures associated with the LUAIP;

c. means for executing the selected LUAIP procedure to accomplish the user modification of one or more datafile entries and/or the information associated with one or more installed applications, thereby automatically synchronizing the directory and enrollment information in the central datafile and the installed applications; and

d. means for returning to the monitoring step (b) for further user input.