SERVICE-ORIENTED ARCHITECTURE (SOA) MANAGEMENT OF DATA REPOSITORY

• US 20090193057A1
• Filed: 01/24/2008
• Published: 07/30/2009
• Est. Priority Date: 01/24/2008
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: MAES, Stephane H.
• Granted Patent: US 8,589,338 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: H04L 67/306 User profiles
• CPC Class Codes: H04L 67/567 Integrating service provisioning from a plurality of service providers

Abstract

A data repository includes information for multiple data systems, which can each control data in this and a number of other domains. A business process can be launched by one of the data systems to update the target data and any related data in the repository or any other related repository. Any request to update data is intercepted and the business process can launch workflows and apply policies as needed to process the request. Workflows can be associated with the fields being updated or process being executed, such that any update to the target data is also accurately reflected in any other related system. Further, launching a workflow allows processes to be run before the data is updated, such that the data can be modified, added to, rejected, or otherwise processed before being added to the appropriate repositories.

Claims

1. A method of managing data in a data system, comprising:

providing a repository storing data for at least one data system;

receiving a request to update target data in the repository, the target data being owned by one of the data systems; and

launching a business process in response to receiving the request, the business process being programmed to trigger at least one condition or action, or combination thereof, needed to update the target data in the repository and any related data as a result of the request.

2. A method according to claim 1, wherein the request to update target data is further able result in at least one of triggering a workflow or policy that updates the data in the repository, updating data and having a workflow triggered as a result, and causing a workflow or policy to be triggered that does not update the data in the repository.

3. A method according to claim 1, wherein:

the first repository is able to store data for multiple data systems; and

the target data in the repository is owned by one of the multiple data systems.

4. A method according to claim 3, wherein:

the business process is programmed to trigger at least one condition or action, or combination thereof, for any of the multiple data systems needed to update the target data and any related data in the first repository and any second repository in order to process the request.

5. A method according to claim 1, further comprising:

generating a notification when the target data and any related data is updated in response to the request.

6. A method according to claim 5, wherein:

generating a notification includes displaying a message at the source of the request.

7. A method according to claim 1, further comprising:

starting a workflow to coordinate processing.

8. A method according to claim 1, further comprising:

storing data in one of a distributed cache and a replicated cache for processing.

9. A method according to claim 1, wherein:

generating a notification is controlled by a policy.

10. A method according to claim 1, wherein:

launching a business process includes kicking off a workflow selected the workflow is a service-oriented architecture (SOA)-based workflow.

11. A method according to claim 1, further comprising:

obtaining access to each of the multiple data systems using a user profile enabling the mapping or management of identities across the multiple data systems.

12. A method according to claim 1, wherein:

a timing of an update of any related data relative to the updating of the target data is determined by a policy.

13. A method according to claim 1, wherein:

launching a business process further includes applying a policy to reconcile the target data with related data stored elsewhere.

14. A method according to claim 1, wherein:

the business process is operable to kick off a workflow that is a service-oriented architecture (SOA)-based workflow.

15. A method according to claim 1, further comprising:

maintaining policies defining which operations and updates are executed by the business process.

16. A method according to claim 1, wherein:

the multiple data systems include at least one of a business support system (BSS), operations support system (OSS), billing system, and subscription system.

17. A method according to claim 16, wherein:

the data is related to a subscription; and

the data is viewed in the first repository as aggregated from the BSS and OSS systems.

18. A method according to claim 17, wherein:

requests to change the data related to the subscription are consistent with related data in the BSS and OSS systems.

19. A method according to claim 18, further comprising:

executing at least one SOA workflow to delegate to the BSS and OSS systems to update the relevant data to ensure consistency.

20. A method according to claim 1, wherein:

any update to the target data and any related data occur in real time.

21. A system for managing data across multiple data systems, comprising:

a plurality of data systems; and

an data management tool operable to provide a shared view of data from the plurality of data systems, the data management tool operable to receive a request to update target data in the first repository, the data management tool being programmed to launch a business process in response to receiving the request, the business process being programmed to trigger an action for any of the plurality of data systems needed to update the target data and any related data in the first repository and any second repository in order to process the request.

22. A method of providing subscription management, comprising:

providing a unified user profile for a user providing access for the user to multiple data systems;

receiving a request from a user to manage a subscription;

accessing a repository to determine the unified user profile for the user;

launching a business process in response to the request, the business process executing actions for any of the multiple data systems using the unified user profile in order to manage the subscription, the business process being programmed to update target data and any related data in any of a number of repositories for any of the multiple data systems.

23. A computer program product embedded in a computer-readable medium for managing data across multiple data systems, comprising:

program code for providing a first repository storing data for at least one of the multiple data systems;

program code for receiving a request to update target data in the first repository, the target data being owned by one of the data systems; and

program code for launching a business process in response to receiving the request, the business process being programmed to trigger an action for any of the multiple data systems needed to update the target data and any related data in the first repository and any second repository in order to process the request.