EP1652115A2 - Moteur logique et pilotes de transformation commerciale - Google Patents

Moteur logique et pilotes de transformation commerciale

Info

Publication number
EP1652115A2
EP1652115A2 EP04777931A EP04777931A EP1652115A2 EP 1652115 A2 EP1652115 A2 EP 1652115A2 EP 04777931 A EP04777931 A EP 04777931A EP 04777931 A EP04777931 A EP 04777931A EP 1652115 A2 EP1652115 A2 EP 1652115A2
Authority
EP
European Patent Office
Prior art keywords
data
user
handler
business
application
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Withdrawn
Application number
EP04777931A
Other languages
German (de)
English (en)
Inventor
Jesus Fernandez
Catherine Elizabeth Sullivan
Kejian Qui
Ronald Jacobson
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
CA Inc
Original Assignee
FERNANDEZ Jesus
QUI Kejian
Computer Associates Think Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by FERNANDEZ Jesus, QUI Kejian, Computer Associates Think Inc filed Critical FERNANDEZ Jesus
Publication of EP1652115A2 publication Critical patent/EP1652115A2/fr
Withdrawn legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/30—Information retrieval; Database structures therefor; File system structures therefor of unstructured textual data
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/25—Integrating or interfacing systems involving database management systems
    • G06F16/258—Data format conversion from or to a database
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/80—Information retrieval; Database structures therefor; File system structures therefor of semi-structured data, e.g. markup language structured data such as SGML, XML or HTML
    • G06F16/84—Mapping; Conversion
    • G06F16/88—Mark-up to mark-up conversion

Definitions

  • a business transformation logic (BTL) engine transforms data from a source application, through a series of transformation handlers, into a format usable by a target application.
  • role-based user provisioning enables the administrators to automatically provide users with a set of userids based on their business functions and ensures consistent user access policies are applied across a wide range of system types and directories.
  • a system and method for managing user data in a plurality of databases extracts user data from a source application, repository or database, transforms the user data into global user data, and sends the global user data to a target application capable of managing the global user data across various environments.
  • a business transformation logic engine for integrating data from a source application to a target application comprising a receiving module for receiving data from the source application in a first predetermined format; and at least one transformation handler for transforming the received data into a second predetermined format usable by the target application.
  • the business transformation logic engine may comprise a template handler for developing application-specific handlers; a XSL (Extensible Stylesheet Language) files handler for transforming the received data with a chain of XSL files; a business rules handler for defining and executing a series of business rules; a mapping handler for associating data from the source application to data in the target application; or a generic component handler for transforming the source data into a workflow request for integrating the source data to the target application.
  • a method for integrating data from a source application to a target application is provided.
  • the method comprises the steps of receiving, decoding and uncompressing an XML message including the source data; creating a message context object from the uncompressed XML message; transforming the message context object into a workflow request for integrating the source data to the target application.
  • a program storage device readable by a machine, tangibly embodying a program of instructions executable by the machine to perform method steps for integrating data from a source application to a target application is provided, the method steps comprising receiving, decoding and uncompressing an XML message including the source data; creating a message context object from the uncompressed XML message; transforming the message context object using user- configured XSL entries; applying business rules to the message context object; mapping source data elements to target data elements; and transforming the XSL-transformed data into a workflow request for integrating the source data to the target application.
  • FIG. 1 is a block diagram of an exemplary system for managing user data in a plurality of databases in accordance with an embodiment of the present invention
  • FIG. 2 is a block diagram of an interface module in accordance with an embodiment of the present invention
  • FIG. 3 is a block diagram of a business transfonnation logic (BTL) engine in accordance with an embodiment of the present invention
  • FIG. 4 is a flow diagram illustrating a method for managing user data in a plurality of databases in accordance with an embodiment of the present invention.
  • FIG. 5 is an overall flow diagram illustrating a system and method for managing user data in a plurality of databases, where a source application or repository is a PeopleSoftTM application and a target application or repository is eTrustTM Admin.
  • a source application or repository is a PeopleSoftTM application
  • a target application or repository is eTrustTM Admin.
  • DETAILED DESCRIPTION Preferred embodiments of the present invention will be described hereinbelow with reference to the accompanying drawings. In the following description, well-known functions or constructions are not described in detail to avoid obscuring the invention in unnecessary detail.
  • a system and method for managing user data in a plurality of databases is provided. The system and method extracts user data from a source application, repository or database, transforms the user data into global user data, and sends the global user data to a target application capable of managing the global user data across various environments.
  • the system 100 includes an interface module 102 for extracting user data from a source application 104 and a business transformation logic (BTL) engine 106 for transforming the user data into a format usable by a target application 108.
  • the interface module 102 includes a publisher 110 for extracting user data, e.g., employee data, from the source application 104.
  • the publisher 110 publishes an XML message from the extracted user data and sends it to a subscriber 112.
  • the subscriber 112 receives, decodes, and uncompresses the XML message.
  • the subscriber 112 then sends the data to the BTL engine 106 that creates a MessageContext object with XML messages and sends it through a chain of BTL handlers, which will be described in detail below.
  • the object is sent to a workflow engine 114 where a request is created and sent to the target application 108.
  • the target application 108 creates, modifies, or deletes global users, their accounts, or changes the roles associated with a global user.
  • a configuration GUI (graphical user interface) 116 is provided for a user, e.g., an administrator, to define the information to be transformed from the source application 104 to the target application 108.
  • the present invention may be implemented in various forms of hardware, software, firmware, special purpose processors, or a combination thereof.
  • the present invention may be implemented in software as an application program tangibly embodied on a program storage device.
  • the application program may be uploaded to, and executed by, a machine comprising any suitable architecture.
  • the machine is implemented on a computer platform having hardware such as one or more central processing units (CPU), a random access memory (RAM), a read only memory (ROM) and input/output (I/O) interface(s) such as a keyboard, cursor control device (e.g., a mouse or joystick) and display device.
  • the computer platform also includes an operating system and micro instruction code.
  • the various processes and functions described herein may either be part of the micro instruction code or part of the application program (or a combination thereof) which is executed via the operating system.
  • various other peripheral devices may be connected to the computer platform such as an additional data storage device and a printing device.
  • the system and method may be implemented on several machines coupled together over a network, e.g., a local area network (LAN), a Wide Area Network (WAN), the Internet, etc..
  • the interface module maybe implemented on a first machine while the business transformation logic engine may be implemented on a second machine.
  • FIG. 2 is a graphical representation of a PeopleSoftTM eTrustTM Admin Interface (PETAI) module 202 and FIG.
  • PETAI PeopleSoftTM eTrustTM Admin Interface
  • PETAI module 202 is to interface with PeopleSoftTM and to feed the PeopleSoftTM data onto the BTL Engine 306.
  • the feed process will take place using two different mechanisms: Full Data Replication and Incremental Updates.
  • the Full Data Replication process will be used to seed, or initially populate or repopulate, a copy of the entire sub-set of PeopleSoftTM records and fields exported onto eTrustTM Admin.
  • the Incremental Updates mechanism will keep eTrustTM Admin current, with changes made on the master PeopleSoftTM data.
  • the PETAI module 202 will be implemented using PeopleSoftTM Enterprise Integration technology, specifically using Application Messaging 211 and will be loaded into the PeopleSoftTM application. PeopleSoftTM Application Messaging is based on a "publish-and-subscribe" model that enables a third party external system to integrate with PeopleSoftTM applications via XML/HTTP(S) messages.
  • the PETAI module 202 includes a publisher 210 and a subscriber 212. The publisher mechanism 210 will be deployed onto PeopleSoftTM and will publish and deliver the XML messages to eTrustTM Admin subscriber 212.
  • the PETAI module 202 will comprise two separate publisher mechanisms, one for implementing the Full Data Replication 210-1 and one for the Incremental Updates 210-2.
  • the eTrustTM Admin subscriber mechanism 212 will be deployed onto the PeopleSoftTM Application Messaging Gateway 211 and will capture, transform and pass the XML messages onto the BTL engine 306.
  • the Incremental Updates Publisher mechanism 210-2 will subscribe to internal application messages that synchronize PeoplesoftTM database components when changes are being made to the PeopleSoftTM records and fields. Then, it will build the PeopleSoftTM
  • the Full Data Replication Publisher mechanism 210-1 will query all the defined PeopleSoftTM records and fields to get a full copy of data, then it will build the PeopleSoftTM XML message(s) and populate it (them) with the data, and finally publish it (them) onto the eTrustTM Admin subscriber 212.
  • Many PeopleSoftTM application tables are effective-dated, meaning that historical and future-date rows may be present on the table.
  • eTrustTM Admin does not use effective dating so the PETAI module 202 will need to filter and provide only the current or active information before feeding it onto eTrustTM Admin.
  • the PETAI module 202 will define a sub-set of PeopleSoftTM records and fields that will be published and delivered to the eTrustTM Admin subscriber 212. This definition will be taken from the PeopleSoftTM Message definitions(s) that will carry on the data to eTrustTM Admin. Separate PeopleSoftTM message definitions will be created for the full data replication and incremental updates publishers.
  • the subscriber 212 e.g., a Java subscriber, will be deployed and registered into the PeopleSoftTM Application Messaging Gateway Servlet.
  • the Java subscriber 212 will also integrate with the PeopleSoftTM Application Messaging Config Servlet.
  • the Config servlet will allow the administrator to load/unload the PETAI Java subscriber 212 as well as configuring PeopleSoftTM Nodes to be subscribed from. Integration code will interface with the Config servlet APIs including a HTML graphical user interface for the Java subscriber configuration.
  • a separated thread will process the full data replication messages while the Java subscriber thread will process incremental updates messages.
  • This separate thread is implemented by an EDI (Electronic Data Interchange) engine.
  • EDI Electronic Data Interchange
  • the subscriber 212 transforms the user data from the source application, the data is passed to the BTL engine 306.
  • the purpose of the BTL engine 306 is to provide a means to transform the input PeopleSoftTM data coming from the PETAI module 202 into Workflow request(s). This request(s) will lead towards the provisioning, modification or de- provisioning of an eTrustTM Admin Global user and all associated accounts.
  • the transformation will be performed by a series of BTL handlers that will be invoked by the BTL engine 306, as shown in FIG. 3.
  • the invocation process will follow a pre-determined order previously specified in the configuration GUI.
  • Each BTL handler will receive, apply its transformation and pass onto the next handler a MessageContext Object.
  • the MessageContext object is a structure, which will contain the PeopleSoftTM data in an XML format among other parts.
  • the BTL engine 306 will enable the administrator to determine and assign Roles to
  • the BTL engine 306 will comprise a chain of handlers including a sample template handler 330, XSL files handler 332, business rules handler 334, mapping handler 336, and generic component handler (Dirsync Handler) 338.
  • the template handler 330 will serve as a starting point for the end user to develop custom BTL handlers for transforming data.
  • the XSL handler 332 will allow the end user to transform the input XML message based on a chain of XSL (Extensible Stylesheet Language) files.
  • the stylesheet must be provided a separated file containing the XSL Transformation code (no need to re-compile
  • a PSCAMA PeopleSoftTM Common Application Message Attributes
  • a PSCAMA handler may have an entry as follows: ⁇ xsl-entry> ⁇ stylesheet-id>pscama ⁇ /stylesheet-id> ⁇ stylesheet-filename>pscama.xsl ⁇ /stylesheet-filename> ⁇ stylesheet-order>l ⁇ /stylesheet-order> ⁇ /xsl-entry> ⁇ xsl-entry> ⁇ stylesheet-id>sample ⁇ /stylesheet-id> ⁇ stylesheet-filename>sample.xsl ⁇ /stylesheet-filename> ⁇ stylesheet-order>2 ⁇ /stylesheet-order> ⁇ /xsl-entry> The PSCAMA XSL program will provide the functionality to filter PSCAMA and data
  • the data record will be included in the output if PSCAMA record not present for a specific data record PSCAMA record is present and AUDIT_ACTN is set to 'A' or 'C or 'N' or A sample XSL program will also be provided. It will serve as a starting point for the end user, e.g. adininistrator, to develop custom XSL programs.
  • the business rules (BR) handler 334 enables the user to create a set of decision tables that match their specific needs.
  • a decision table is a set of business rules that determine the assignments of special Global User attributes required in the user provisioning process. Special Global User attributes can be roles, profiles, groups, or any other attribute requiring special treatment to determine its value.
  • Decision tables present a sophisticated mechanism to set special attributes without having to write any code. For each special Global User attribute an administrator may want to assign, the administrator will create one decision table. Each decision table needs to specify a set of input parameters to be used in the calculation of the attribute value.
  • a decision table header enables the administrator to provide this information.
  • the header's first column is where the output field name is to be placed. Nalid output field names are considered any field name on the ETRUST_ADIV ⁇ T ⁇ record.
  • the rest of the header columns are where the input parameters are to be placed.
  • Valid input parameters are considered any field on the XML message and must be defined using XPath standard syntax.
  • the decision table rows are where the business rules are defined. Each row specifies the output value, the combination of comparison values, and operators for assigning the value.
  • the first column on each row is where the output value is placed.
  • the rest of the row columns are where the comparison values and the operators are placed.
  • the following decision table example assigns the Global User Role attribute (Role- Name) and uses three input parameters to calculate the value (Country, Department ID, and Company).
  • the sample defines two business rules for assigning two different role values.
  • the business rules handler 334 then sends the message to the mapping handler 336.
  • the BTL mapping handler 336 associates one PeopleSoftTM data field or a custom record field to a Global User attribute of the eTrustTM Admin application.
  • the mapping supports the association of any element and any non-element within the XML message to a Global User Attribute using XPath standard syntax.
  • the mapping of attributes will be defined by XML data stored in the configuration file. The end user can customize the XML data to fit their specific needs using the configuration GUI.
  • the configuration file will use XPath standard syntax to define the mappings having the root element as the context for all definitions.
  • the following XML data represents a sample PeopleSoftTM XML message:
  • mapping definitions for "EMPLID” and “DEPTID” elements will be represented using XPath standard syntax as:
  • the generic component handler 338 will be the end point in the BTL engine chain and ultimately will transform the PeopleSoftTM data into Workflow requests.
  • the generic component handler 338 takes the input data from the mapping handler 336 and transform it onto Workflow requests.
  • a Workflow request is a record within the Workflow repositoiy or engine 114 representing a group of action tasks that will take place as a result of the execution of the request. Sample action tasks are: Create Global User, Modify Global User, Delete Global User, Add Role to Global user, etc.
  • the configuration GUI 116 will be employed to configure the various BTL handlers.
  • the purpose of the configuration GUI 116 is to provide a means for a system administrator to easily define the information that is needed to transform a PeopleSoftTM User Entry into an eTrustTM Admin Global User Entry. This information will include the resulting eTrustTM Admin Global User attributes and the means that is used to produce them.
  • the BTL configuration GUI 116 will be comprised of the following interfaces:
  • BTL Handlers Registration This interface will allow the end user to register BTL handlers on the BTL engine and define their invocation order.
  • This interface will allow the end user to set all remaining configuration parameters.
  • the configuration GUI 116 will additionally enable the administrator to set any necessary configuration parameters. These configuration parameters will be held in the XML configuration file mentioned above. Below is an exemplary Ust of parameters included in the configuration file:
  • This meta-data will be needed for both eTrustTM Admin and PeopleSoftTM.
  • PeopleSoftTM it will consist of the attributes that can be used as parameters to the Decision Table Definitions.
  • eTrustTM Admin this data will consist of a list of all supported Global User attributes.
  • PeopleSoftTM Extract From an existing extract, the BTL configuration GUI will be able to obtain the required meta-data. At any time, the system administrator will be able to add to and modify this meta-data.
  • eTrustTM Admin meta-data a listing of the attributes that exist will be readily available from the configuration GUI.
  • the eTrustTM Admin meta-data may be modified as well.
  • the PETAI module 502 will interface with PeopleSoftTM system 504 (step 402) and will feed PeopleSoftTM data onto the BTL engine 506 through its Java Subscriber 512 (step 404).
  • the BTL engine 506 will generate a MessageContext object containing the PeopleSoftTM data and it will pass it on to the first BTL handler defined in the configuration file that in this case is the sample template handler 530 (step 406).
  • the template handler 530 will process and transform the MessageContext object and it will pass it on to next handler in the chain.
  • the XSL files handler 532 receives the MessageContext and applies a chain of XSL Transformations, e.g., PSCAMA.XSL and sample.XSL (step 408).
  • the business rules handler 534 receives the MessageContext object and transforms it executing any decision tables defined in the configuration file (step 410), via the configuration GUI 516. Then, it will pass it on to the mapping handler 536.
  • the mapping handler 536 receives the MessageContext object and transforms it assigning PeopleSoftTM data fields and custom fields to Global User attributes based on the mapping information in the configuration file (step 412). Then, it will pass it on to the generic component handler
  • the generic component handler or end point handler (Dirsync Handler) will ultimately generate eTrustTM Admin Workflow requests (step 414), via the workflow engine 514. This request(s) will lead towards the provisioning, modification or de-provisioning of Global user and all associated accounts in the eTrustTM Admin application 508.
  • the system and method according to embodiments of the present invention provides organizations the ability to capture changes to a source application, e.g., a PeopleSoftTM application, in real time. The system and method transforms the data into "intelligible" user provisioning requests based on business rules associated with specific values in the source application data.
  • a workflow engine e.g., a target application, which ultimately sends (create, delete, or modify) requests to managed security systems.
  • a user provisioning engine e.g., a target application
  • embodiments of the present invention automate the user provisioning process from a source application to the heterogeneous security systems making up the orgamzations IT infrastructure.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Data Mining & Analysis (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Stored Programmes (AREA)

Abstract

La présente invention se rapporte à un moteur logique de transformation commerciale qui permet d'intégrer des données en provenance d'une application source dans une application cible, et à un procédé associé. Le moteur logique de transformation commerciale de l'invention comprend un module de réception qui reçoit des données en provenance de l'application source dans un premier format prédéterminé ; et au moins un pilote de transformation qui transforme les données reçues en un second format prédéterminé pouvant être utilisé par l'application cible. Le procédé de l'invention consiste à recevoir un message XML renfermant les données sources ; à créer un objet de contexte de message à partir du message XML ; à transformer l'objet de contexte de message en utilisant les entrées XSL configurées par l'utilisateur ; à appliquer des règles commerciales à l'objet de contexte de message transformé ; à mettre en correspondance les éléments de données sources de l'objet de contexte de message transformé avec les éléments de données cibles ; et à transformer en une demande de flux de travaux les données transformées en XSL afin d'intégrer les données sources dans l'application cible.
EP04777931A 2003-07-11 2004-07-09 Moteur logique et pilotes de transformation commerciale Withdrawn EP1652115A2 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US48651203P 2003-07-11 2003-07-11
PCT/US2004/022152 WO2005008540A2 (fr) 2003-07-11 2004-07-09 Moteur logique et pilotes de transformation commerciale

Publications (1)

Publication Number Publication Date
EP1652115A2 true EP1652115A2 (fr) 2006-05-03

Family

ID=34079240

Family Applications (1)

Application Number Title Priority Date Filing Date
EP04777931A Withdrawn EP1652115A2 (fr) 2003-07-11 2004-07-09 Moteur logique et pilotes de transformation commerciale

Country Status (2)

Country Link
EP (1) EP1652115A2 (fr)
WO (1) WO2005008540A2 (fr)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2492674A1 (fr) 2011-02-28 2012-08-29 Lexogen GmbH Réseaux de biocapteurs formé par jonctions d'électrodes fonctionnalisées

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
None *

Also Published As

Publication number Publication date
WO2005008540A3 (fr) 2005-03-31
WO2005008540A2 (fr) 2005-01-27

Similar Documents

Publication Publication Date Title
US7926064B2 (en) Business transformation logic engine and handlers
US7788214B2 (en) XML configuration technique and graphical user interface (GUI) for managing user data in a plurality of databases
US11138023B2 (en) Method and apparatus for composite user interface creation
US10402424B1 (en) Dynamic tree determination for data processing
US6806890B2 (en) Generating a graphical user interface from a command syntax for managing multiple computer systems as one computer system
US7484219B2 (en) Synchronizing centralized data store from distributed independent data stores using fixed application programming interfaces
US7167874B2 (en) System and method for command line administration of project spaces using XML objects
US7870157B2 (en) System and method for implementing a management component that exposes attributes
US6810429B1 (en) Enterprise integration system
DE69404647T2 (de) Verfahren und vorrichtung zum verwalten von tischcomputern eines unternehmens
US7370335B1 (en) System and method for providing a public application program interface
US7596550B2 (en) System and method for query planning and execution
US8606816B2 (en) Management of collections of websites
US20150046555A1 (en) Message broker system and method
US7512941B2 (en) Method and system for distributing and updating heterogeneous resources
US7640238B2 (en) Query planning for execution using conditional operators
US11550785B2 (en) Bidirectional mapping of hierarchical data to database object types
US9317570B2 (en) System and method for managing user data in a plurality of databases
US20110289041A1 (en) Systems and methods for managing assignment templates
EP1652115A2 (fr) Moteur logique et pilotes de transformation commerciale
WO2005008539A1 (fr) Systeme et procede de gestion de donnees d'utilisateur dans une pluralite de bases de donnees
US20220188335A1 (en) Distributing tables in a distributed database using consolidated grouping sources
EP1649391A2 (fr) Technique de configuration xml et interface graphique utilisateur (gui) pour la gestion de donnees d'utilisateur dans une pluralite de bases de donnees
US6996602B2 (en) Server-side page table framework for client application definition and execution
Piprani et al. A metamodel for orchestrating service requirements in an SQL-environment

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20060206

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LI LU MC NL PL PT RO SE SI SK TR

17Q First examination report despatched

Effective date: 20060828

DAX Request for extension of the european patent (deleted)
RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: COMPUTER ASSOCIATES THINK, INC.

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION HAS BEEN WITHDRAWN

18W Application withdrawn

Effective date: 20181128