CN101488099A - Method and apparatus for centralized user information management - Google Patents

Abstract

The invention relates to the field of user information management, in particular to the unified management technology of multi-system user information. A method for unified management of user information, comprising steps: an application program for managing user information obtains changed user information and starts a transaction for managing user information; the transaction calls each A COM+ component of an application system; after the COM+ component of each application system is invoked, the user information of the corresponding application system is changed according to the changed user information. The invention also provides a device for unified management of user information. The present invention realizes the change of the user information of each system through the COM+ components, and by calling these COM+ components in the same transaction, using the atomicity and consistency attributes of the transaction, it ensures the consistency of changing the user information of each system through the COM+ components It realizes low-cost and convenient unified management of user information.

Description

A method and device for unified management of user information

technical field

The invention relates to the field of user information management, in particular to a unified management technology of user information in a multi-application system.

Background technique

With the rapid development of information technology and network technology, there are more and more application systems in enterprises. For example, in the media industry, common application systems include editing application systems, typesetting application systems, printing application systems, advertising management application systems, financial application systems, office automation application systems, decision support application systems, customer relationship management application systems and website publishing. application system, etc. Since these application systems are independent of each other, the user must log in according to the corresponding application system identity before using each application system, so the user must remember the user name and password of each application system, which brings a lot of trouble to the user. Especially with the increase of the application system, the possibility of error will increase.

Generally speaking, each application system has an independent user information management function, and the format, naming and storage methods of user information are also various. When a user needs to use multiple application systems, it will bring user information synchronization problems. User information synchronization will increase the complexity of the application system and increase the cost of management.

For example, if user X needs to use application system A and application system B at the same time, user X must be created in application system A and application system B, so that user X’s information must be synchronized after being changed in either application system A or B to another application system. If user X needs to use 10 application systems at the same time, user information must be synchronized to the other 9 application systems after making changes in any application system. If an accident occurs in the application system when synchronizing user information, data integrity must be guaranteed, so the procedure for synchronizing user information may be very complicated.

In the prior art, user information is synchronized by establishing a unified user management system (UUMS). UUMS stores user information of all application systems in a unified manner, and all relevant operations of application systems on users are completed through UUMS, while authorization and other operations are completed by each application system, that is, unified storage and distributed authorization. UUMS should have the following basic functions:

1. User information is named and stored uniformly, and the user ID is globally unique. User ID is like an ID card, distinguishing and identifying different individuals.

2. UUMS provides user attribute lists to each application system, such as name, phone number, address, email and other attributes, and each application system can select some or all of the attributes required by the application system.

3. The application system's request for adding, modifying, deleting and querying the user's basic information is processed by UUMS.

4. The application system retains user management functions, such as user grouping and user authorization.

UUMS adopts SSO (Single Sign-on, single sign-on) technology to facilitate users to access multiple application systems. Users only need to register once when logging in, and they can freely shuttle between multiple application systems without having to repeatedly enter user names and passwords. Identify.

At present, many products in the industry support UUMS for SSO, such as IBM's WebSphere and BEA's WebLogic. However, the price of these commercial software is relatively expensive, and there are also requirements for the application system. Generally, some modifications must be made to the application system to be integrated, such as installing AGENT software on the application system to be integrated.

Contents of the invention

The embodiment of the present invention provides a method for unified management of user information, so as to realize low-cost and convenient unified management of user information.

The embodiment of the present invention provides a device for unified management of user information, which is used to realize low-cost and convenient unified management of user information.

A method for unified management of user information, comprising the steps of:

An application for managing user information obtains changed user information and starts a transaction for managing user information;

According to the changed user information, the transaction calls the COM+ component of each application system for managing user information from the operating system;

After the user information management COM+ component of each application system is invoked, the user information of the corresponding application system is changed according to the changed user information.

A device for unified management of user information, including:

Change information acquisition module, used to obtain changed user information;

The transaction calling component module is used to start the transaction of managing user information, and the transaction calls the user information management COM+ component of each application system from the operating system according to the changed user information; the user information management of each application system After the COM+ component is invoked, the user information of the corresponding application system is changed respectively according to the changed user information.

The embodiment of the present invention implements the change of the user information of each application system through the COM+ components, and by calling these COM+ components in the same transaction, using the atomicity and consistency attributes of the transaction, thereby ensuring the change of each application system by calling the COM+ components. The consistency of application system user information realizes the unified management of user information of each application system. Since the use of expensive UUMS is avoided, the cost of unified management of user information is reduced; and there is no need to modify each application system, so that unified management of user information can be realized more conveniently.

Description of drawings

1a to 1c are schematic diagrams of a user information database of a multi-application system according to an embodiment of the present invention;

FIG. 2 is a flow chart of a method for generating an application program for unified management of user information according to an embodiment of the present invention;

3 is a flowchart of a method for unified management of user information according to an embodiment of the present invention;

FIG. 4 is a structural diagram of a device for unified management of user information according to an embodiment of the present invention.

Detailed ways

The embodiment of the present invention realizes the change to the user information of each application system in the COM (Component Object Model, Component Object Model)+component of each application system, by calling these COM+ components in a transaction, utilizing the atomicity of the transaction and Consistency attributes, thus ensuring the consistency of changing the user information of each application system by calling COM+ components, and realizing the unified management of user information of each application system.

Here we first introduce the concepts of COM+ components and affairs. Microsoft proposed the COM (Component Object Model, Component Object Model) concept as another way to build applications. Generally speaking, an application is composed of a single binary file. If you need to make some improvements to the application, you need to modify the source code of the application, and then compile it to generate a new file to replace the original file. Now, we use a new perspective to look at the problem: divide the original entire executable binary file (EXE) file into several relatively independent components with different functions, and assemble them to form a program and software. After the application program is released, if a certain part of the application program needs to be modified, it is only necessary to replace the problematic components or the components that need to be upgraded. It is even possible to replace components in it without affecting the normal operation of the program.

COM is a specification that describes how to build dynamically interchangable components. This specification provides some binary and network standards that clients and components should follow to ensure interoperability. Through this standard, communication can be carried out between any two components regardless of whether their operating environments are the same, whether the development languages used are consistent, and whether they run on the same computer.

COM+ is not a simple upgrade of COM. The underlying structure of COM+ is still based on COM. It contains almost all the content of COM. It promotes the COM component software to the application layer instead of the underlying software structure. All kinds of support enable the component object model to be established on the application layer, leaving the underlying details of all components to the operating system. Therefore, the combination of COM+ and the operating system is closer.

In order to complete operations on data, concurrent access to data shared among multiple components is often required. In this case, it may be required that a set of operations on a (distributed) resource be treated as a unit of work. In a unit of work, all parts of the operation succeed or fail together and recover. A unit of work is implemented by a set of distributed components that access data from multiple resources, and the data operations of the unit of work on (distributed) resources either all succeed or all fail. In the event of a unit of work failure, the unit of work returns the data state of all resources to the previous state.

A transaction maintains data integrity within a unit of work and has the following properties:

1. ATOMICITY: A transaction must be completed or undone completely without ambiguity. In the event of an error in any operation, the effects of all operations constituting the transaction must be undone, and the data should be restored to its previous state.

2. Consistency (CONSISTENCY): A transaction should protect all invariant attributes defined on the data (such as integrity constraints). After completing a successful transaction, the data should be in a consistent state. In other words, a transaction should transition the system from one consistent state to another. For example, in the case of relational databases, a consistent transaction will protect all integrity constraints defined on the data.

3. Isolation (ISOLATION): There may be multiple transactions executing concurrently in the same environment, and each transaction should appear to be executed independently.

4. DURABILITY: The effect of a completed transaction should be persistent.

The embodiment of the present invention utilizes the above-mentioned attributes of transactions to maintain the consistency of user information when operating and managing user information of a multi-application system.

Assume that the user uses three application systems: A, B, and C application systems. In these three application systems, user information is the same. Then, when changing the user information in one of the application systems, it is also necessary to change the user information in the other two application systems synchronously, as shown in Figure 1a to Figure 1c:

The application system A has a user information database A for storing user information of the application system A, which may include user information of multiple users. For example, user information of users such as John and Tom. The user information may also include user names, passwords, and the like.

Similarly, there is a user information database B in the application system B to store the user information of the application system B; and a user information database C in the application system C is used to store the user information of the application system C.

The technical solutions of the embodiments of the present invention will be described below by taking synchronizing user information in application systems A, B, and C as an example.

The embodiment of the present invention provides a method for generating an application program for unified management of user information, the flow chart of which is shown in Figure 2, specifically including the following steps:

Step S201: Define a COM+ component corresponding to each application system for managing user information of the corresponding application system.

For each application system with user information, the user information stored in the user information database of the application system is consistent. Corresponding to each application system, a COM+ component is defined—the user information management COM+ component. Each defined COM+ component is used to operate on the user information of the corresponding application system. These operations may include: adding, modifying or deleting user information. For example, the COM+ component can add the user "Sam" and the password "000" of the user "Sam" in the user information database of the corresponding application system; or, the COM+ component can add the user "John" in the user information database of the corresponding application system. "Password changed to "333". Since the implementation method is well known to those skilled in the art, the specific programming method for realizing the operation of each COM+ component on the user information in the user information database of the corresponding application system will not be repeated here.

During specific implementation, those skilled in the art may have various technical means to realize the operation of the user information management COM+ component on the user information of the corresponding application system. Among them, as a better method, a class of user information management interface common to user information databases of all application systems can be defined first. The user information management interface class is used to provide an interface for receiving changed user information for COM+ components inheriting the user information management interface class. Some basic operations on user information in the user information database can be realized, such as adding, modifying or deleting user information. Since each defined COM+ component inherits the user information management interface class, it has the same interface for receiving changed user information, and transactions can uniformly transmit changed user information to COM+ components through the interfaces of these COM+ components. The COM+ component then changes the user information in the user information database of the corresponding application system according to the incoming changed user information. For example, the changed user information "increase, user AA, password 555" is passed to these COM+ components as a string parameter. Then the COM+ component that inherits the user information management interface class can uniformly perform the corresponding operation of adding users according to the parameters passed in by the interface.

Step S202: Register all defined COM+ components to the operating application system.

After these user information management COM+ components are registered in the operating application system, these defined user information management COM+ components can be called. The method of registration is well known to those skilled in the art, either by manually inputting a command line to register the user information management COM+ component, or by calling a script from a program.

Step S203: Call all user information management COM+ components in a transaction.

In one transaction, call all user information management COM+ components through parameters, so that all user information management COM+ components perform the same operations on the user information in the user information database of their corresponding application systems. For example, when it is necessary to modify the password information of the user "Tom" to "999" for the application systems A, B, and C, the COM+ components are uniformly called in the transaction, so that the corresponding COM+ components of the application systems A, B, and C are all executed. The operation of modifying user information. Of course, the user information management COM+ component is used to modify the user information by passing parameters to the user information management COM+ component so that the user information management COM+ component can specifically decide what operation to perform and which user to perform according to the incoming parameters. operation, and why the specific changed user information. Passing parameters to the user information management COM+ component and calling the user information management COM+ component to complete the operation of the user information in the user information database of the corresponding application system are well known to those skilled in the art, so details are not repeated here.

Due to the atomicity and consistency attributes of the transaction described above, if a user information management COM+ component fails to operate on the user information in the user information database of the corresponding application system during execution, the transaction will Restore the user information in the user information database of the application system corresponding to all user information management COM+ components to the user information before modification. Only when the operations of modifying the user information in the user information database of all user information management COM+ components are successful, the user information in the user information database of all application systems will be changed. This ensures that during the process of modifying user information, the user information in the user information databases of all application systems are consistently modified, and their modifications are all synchronized—either the modification is successful or the modification fails.

Step S204: Encapsulate the COM+ components defined in the above step S201 and the programs for performing the operations of the above steps S202 and S203 to generate an application program for unified management of user information.

The embodiment of the present invention provides a method for unified management of user information, as shown in Figure 3, including the following steps:

Step S301: Obtain changed user information.

When the user needs to change the user information of the application system, for example, the password information of the user "Tom" in the application systems A, B, and C needs to be changed to "999", and the changed user information that the application program needs to obtain for unified management of user information Including: the change operation is to modify the user password, the changed user is "Tom", and the changed password is "999".

Step S302: Start a transaction for managing user information, and the transaction uniformly calls the user information management COM+ component defined corresponding to each application system according to the changed user information.

The unified management user information application program starts a transaction for managing user information, and the transaction uniformly calls the user information management COM+ component defined corresponding to each application system with user information according to the changed user information. As described in the aforementioned step S201, a COM+ component—the user information management COM+ component is defined corresponding to each application system with user information, and each COM+ component is used to update the user information of the corresponding application system according to the changed user information Make changes. Because the user information management COM+ component realizes the operation on the user information of the corresponding application system, these operations include: adding, deleting or modifying user information, so the user information management COM+ component can make corresponding operations according to the obtained changed user information. For example, the changed user information obtained includes: the change operation is to modify the user password, the changed user is "Tom", and the changed password is "999", then each user information management COM+ component executes the user information of the corresponding application system Modify the operation, and specifically change the password of the "Tom" user to "999".

Or the changed user information obtained is: add a new user "Sam", and the password of "Sam" is "000", then each user information management COM+ component performs the user operation of adding user information to the corresponding application system, and specifically Add user "Sam" and its password "000".

Specifically, a better method may be used to implement the user information management COM+ component to perform corresponding modification operations on the user information of the corresponding application system according to the obtained modified user information. First define a class of user information management interface common to user information databases of all application systems. The user information management interface class is used to provide an interface for receiving changed user information for COM+ components inheriting the user information management interface class. Some basic operations on user information in the user information database can be realized, such as adding, modifying or deleting user information. Since each defined COM+ component inherits the user information management interface class, it has the same interface for receiving changed user information, and transactions can uniformly transmit changed user information to COM+ components through the interfaces of these COM+ components. The COM+ component then changes the user information in the user information database of the corresponding application system according to the incoming changed user information.

Due to the atomicity and consistency properties of transactions in the unified calling process, all operations of user information management COM+ components either all succeed or all fail, which ensures the consistency of user information changes.

Before calling the user information management COM+ components, these COM+ components need to be pre-registered in the operating system. The method of registration can be either by manually entering the command line to register the user information management COM+ component, or by calling the script through the program.

As shown in FIG. 4 , the embodiment of the present invention also provides a device for unified management of user information, including: a modification information obtaining module 401 and a transaction calling component module 403 .

The modification information obtaining module 401 is configured to obtain modified user information.

The transaction calling component module 403 is used to start a transaction, and uniformly call the user information management COM+ component corresponding to each application system with user information according to the changed user information in a transaction.

Corresponding to each application system having user information, a user information management COM+ component is defined, and the COM+ component is used to change the user information of the corresponding application system according to the changed user information. Since the user information management COM+ component realizes the operation on the user information of the corresponding application system, including: adding, deleting or modifying user information, the user information management COM+ component can make corresponding operations according to the obtained changed user information.

Specifically, a better method may be used to implement the user information management COM+ component to perform corresponding modification operations on the user information of the corresponding application system according to the obtained modified user information. First define a class of user information management interface common to user information databases of all application systems. The user information management interface class is used to provide an interface for user information operations of the application system. After each defined COM+ component inherits the user information management interface class, it operates on the user information in the user information database of the corresponding application system through the inherited user information management interface class. In this way, each user information management COM+ component can be conveniently and uniformly called through this user information management interface class.

In the transaction calling component module 403, including:

A unit for calling COM+ components used by each application system to manage user information from the operating system.

Further, it also includes:

A unit for controlling all user information management COM+ components to restore the user information of the corresponding application system to the user information before modification when at least one user information management COM+ component fails to change the user information of the corresponding application system.

Due to the atomicity and consistency of transactions in the unified calling process, the operations of all user information management COM+ components either all succeed or all fail, which ensures the consistency of user information changes.

Since the above-mentioned COM+ components need to be registered in the operating application system before being called, the registration method can be registered by manually inputting a command line, or by calling a script from a program.

Then further, the device for unified management of user information may also include:

The component registration module 402 is used for registering the user information management COM+ component in the operation application system by calling the script through the program. Before the transaction calling component module 403 calls various user information management COM+ components, these COM+ components need to be registered in the operating application system. After each user information management COM+ component is registered in the operating application system, the transaction calling component module 403 does not need to register each time before calling these COM+ components.

The embodiment of the present invention implements the change of the user information of each application system through the COM+ components, and by calling these COM+ components in a transaction, the atomicity and consistency properties of the transaction are used to ensure that the changes of each application system are made by calling the COM+ components. The consistency of application system user information realizes the unified management of user information of each application system. Compared with the method of unified management of user information in the prior art, the embodiment of the present invention avoids the use of expensive UUMS, thus reducing the cost of unified management of user information; and the technical solution of the embodiment of the present invention does not need to modify each application system , so that the unified management of user information can be realized more conveniently.

Those of ordinary skill in the art can understand that all or part of the steps in the method of the above-mentioned embodiments can be completed by instructing related hardware through a program, and the program can be stored in a computer-readable storage medium, such as: ROM/RAM, Diskettes, CDs, etc.

The above is only a preferred embodiment of the present invention, it should be pointed out that for those of ordinary skill in the art, without departing from the principle of the present invention, some improvements and modifications can also be made, and these improvements and modifications should also be It is regarded as the protection scope of the present invention.

Claims (10)

1, a kind of method of unified management user profile is characterized in that, comprises the steps:

The application program that is used for managing user information obtains the user profile of change and starts the affairs that are used for managing user information;

Described affairs are called the COM+ assembly that each application system is used for managing user information according to the user profile of described change from operating system;

After the subscriber information management COM+ assembly of each application system is called, change the user profile of corresponding application system respectively according to the user profile of described change.

2, the method for claim 1, it is characterized in that, the subscriber information management interface class of the subscriber information management COM+ assembly of described each application system is identical, and described subscriber information management interface class is used to subscriber information management COM+ assembly that the interface of the user profile that receives described change is provided.

3, method as claimed in claim 1 or 2 is characterized in that, the subscriber information management COM+ assembly of described each application system is registered in the described operating system by input command is capable.

4, method as claimed in claim 1 or 2 is characterized in that, the subscriber information management COM+ assembly of described each application system is that the mode by the routine call script is registered in the described operating system.

5, as the arbitrary described method of claim 1-4, it is characterized in that, also comprise: if there is at least one subscriber information management COM+ assembly to change the user profile failure of corresponding application system, then described affairs are controlled all subscriber information management COM+ assemblies the user profile of corresponding application system are reverted to user profile before the change.

6, a kind of device of unified management user profile is characterized in that, comprising:

Changed information obtains module, is used to the user profile that obtains to change;

Affairs invocation component module is used to start the affairs of managing user information, and described affairs are called the subscriber information management COM+ assembly of each application system according to the user profile of described change from operating system; After the subscriber information management COM+ assembly of described each application system is called, change the user profile of corresponding application system respectively according to the user profile of described change.

7, device as claimed in claim 6, it is characterized in that, the subscriber information management interface class of described each subscriber information management COM+ assembly is identical, and described unified subscriber information management interface class is used to each subscriber information management COM+ assembly that the unified interface of the user profile that receives described change is provided.

8, as claim 6 or 7 described devices, it is characterized in that, also comprise:

The component register module is used for each subscriber information management COM+ assembly is registered to the operational applications system respectively.

As claim 6 or 7 described devices, it is characterized in that 9, described affairs invocation component module comprises:

Be used for calling the unit that each application system is used for the COM+ assembly of managing user information from operating system.

10, device as claimed in claim 9 is characterized in that, described affairs invocation component module also comprises:

Be used for when at least one subscriber information management COM+ assembly is changed the failure of user profile of corresponding application system, control the unit that all subscriber information management COM+ assemblies revert to the user profile of corresponding application system user profile before the change.

Images