JP2004259066A - Data source integrating program, system and method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To efficiently manage data by unifying contents of a plurality of data sources. <P>SOLUTION: In this data source integrated program 6a, a reception function 7 receiving a data operating command from a command source and a generation function generating data from a plurality of data sources A-C of different classes recorded in recording means 27A-27C in advance according to the operating instructions received by the reception function 7 are realized in a computer, and the data sources A-C comprise information on managed data and a management form. <P>COPYRIGHT: (C)2004,JPO&NCIPI

Description

【０１６０】
表２は、企業エントリｅ２の例である。
【０１６１】
【表２】

【０１６２】
表３は、組織エントリｅ３の例である。
【０１６３】
【表３】

【０１６４】
表４は、組織エントリｅ４の例である。
【０１６５】
【表４】

【０１６６】
表５は、社員エントリｅ５の例である。
【０１６７】
【表５】

【０１６８】
表６は、社員エントリｅ６の例である。
【０１６９】
【表６】

【０１７０】
表７は、社員エントリｅ７の例である。
【０１７１】
【表７】

【０１７２】
表８は、社員エントリｅ８の例である。
【０１７３】
【表８】

次に、データソースＢについて説明する。
【０１７４】
このデータソースＢは、企業テーブルｔ１、組織テーブルｔ２、社員テーブルｔ３という３種類のテーブルを管理するとする。
【０１７５】
表９は、企業テーブルｔ１の例である。
【０１７６】
【表９】

【０１７７】
表１０は、組織テーブルｔ２の例である。
【０１７８】
【表１０】

【０１７９】
表１１は、社員テーブルｔ３の例である。
【０１８０】
【表１１】

【０１８１】
次に、定義データ１４について説明する。
【０１８２】
定義データ１４は、例えばデータソース接続定義データ１４ａ、データソースアクセス方法定義データ１４ｂ、各データソースＡ、Ｂに関するデータソース定義データ１４ｃ、１４ｄなどのようなデータソース自体についてのデータと、マッピング定義データ１４ｅを具備する。
【０１８３】
データソース接続定義データ１４ａの例を表１２に示す。
【０１８４】
【表１２】

データソース接続定義データ１４ａには、データソース名、データソースの種別、ホスト名、ポート、Ｂｉｎｄ Ｕｓｅｒ、Ｐａｓｓｗｏｒｄなどの各データソースＡ、Ｂに接続するために必要な情報が定義される。
【０１８５】
データソースアクセス方法定義データ１４ｂの例を表１３に示す。
【０１８６】
【表１３】

データソースアクセス方法定義データ１４ｂには、各データソースＡ、Ｂを検索、登録、更新、削除するためのコマンドが定義される。
【０１８７】
データソース定義データ１４ｃ、１４ｄには、各データソースＡ、Ｂに記録されるデータの内容が定義される。例えば、データソース定義データ１４ｃ、１４ｄでは、対応するデータソースＡ、Ｂに記録されているデータのデータ名（例えば、ＬＤＡＰの属性、ＲＤＢの列名）が定義される。
【０１８８】
本実施例では、ＬＤＡＰ及びＲＤＢの２つのデータソースＡ、Ｂがあるため、定義データ１４は２つのデータソース定義データ１４ｃ、１４ｄを具備する。
【０１８９】
データソースＡに係るデータソース定義データ１４ｃの例を表１４に示す。
【０１９０】
【表１４】

データソース定義データ１４ｃには、データソースＡのオブジェクトクラス名、属性名、型、必須、主キーが定義される。
【０１９１】
一方、データソースＢに係るデータソース定義データ１４ｄの例を表１５に示す。
【０１９２】
【表１５】

データソース定義データ１４ｄには、データソースＢのテーブル名、列名、型、必須、主キーが定義される。
【０１９３】
マッピング定義データ１４ｅの例を表１６に示す。
【０１９４】
【表１６】

マッピング定義データ１４ｅには、統合クラスとこの統合クラスの属性の定義、及び統合クラスとこの統合クラスの属性と上記データソース定義データ１４ｃ、１４ｄで定義されているデータとのマッピング関係を定義している。
【０１９５】
統合クラスの属性としては、データソースＡ、Ｂのいずれかに記録されたデータ、参照関係にあるクラス、関数の３種類が用いられ、それぞれ定義内容が異なる。
【０１９６】
まず、マッピング定義データ１４ｅについて、統合クラスの属性の種別がデータの場合について説明する。
【０１９７】
統合クラスの属性の種別がデータでありこの統合クラスの属性の属性値となるデータがＬＤＡＰのデータソースＡに格納されている場合、マッピング定義データ１４ｅには、統合クラスの属性名、型、必須となる属性、主キーとなる属性と、統合クラスで属性値となるデータの格納されているデータソース名、クラス、属性名とが関係付けられ、定義される。
【０１９８】
一方、統合クラスの属性の種別がデータでありこの統合クラスの属性の属性値となるデータがＲＤＢのデータソースＢに格納されている場合、マッピング定義データ１４ｅには、統合クラスの属性名、型、必須となる属性、主キーとなる属性と、統合クラスで属性値となるデータの格納されているデータソース名、テーブル名、列名とが関係付けられ、定義される。
【０１９９】
マッピング定義データ１４ｅにおいて、異なるデータソースＡ、Ｂ間で同じ値を持つ属性は、共通キーとして定義される。共通キーとして定義される統合クラスの属性名には、データソースＡの属性名及びデータソースＢの列名が関係付けされる。
【０２００】
共通キーは、例えば、データソースＡの属性の値をキーとして、データソースＢの列の値を取得するとき、共通キーである旨の印の付されているデータソースＡの属性の値を、関連するデータソースＢの列の値として代入し、この代入された値をキーとしてデータソースＢ内の列の値を取得する場合に使用される。
【０２０１】
例えば、ＳｙａｉｎＣｌａｓｓにおいて、共通キーは「ＳＹＡＩＮ＿ＮＵＭ」であり、データソースＡは「ｕｉｄ」、データソースＢは「ＮＵＭＢＥＲ」に対応付けられている。ここで、データソースＡの「ｃｎ」の属性値をキーとして、データソースＢにある「ＴＥＬ」の属性値を取得する場合、まず「ｃｎ」をキーとしてデータソースＡを検索することにより、共通キーである「ｕｉｄ」の属性値を取得することができる。続いて、得られた「ｕｉｄ」の属性値を「ＮＵＭＢＥＲ」の属性値としてデータソースＢを検索することにより、目的とする「ＴＥＬ」の属性値を取得することができる。
【０２０２】
マッピング定義データ１４ｅにおけるＲｅａｄ、Ｗｒｉｔｅは、データソース統合システム３において統合オブジェクトの属性値に対するＲｅａｄ、Ｗｒｉｔｅの操作が行われたときに、実際にどのデータソースＡ、Ｂの属性値又は列の値に対してＲｅａｄ、Ｗｒｉｔｅ操作を行うか定義している。
【０２０３】
例えば、共通キーであるＳｙａｉｎＣｌａｓｓの「ＳＹＡＩＮ＿ＮＵＭ」の属性値を取得する場合、データソースＡの「ｕｉｄ」、データソースＢの「ＮＵＭＢＥＲ」のどちらを参照すればよいかを特定できないため、どのデータソースから値を参照するかをＲｅａｄから判断する。表１６の例では、「ｕｉｄ」から参照することになっている。
【０２０４】
次に、マッピング定義データ１４ｅについて、統合クラスの属性の種別が参照関係の場合について説明する。
【０２０５】
統合クラスの属性の種別が参照関係の場合、この統合クラスの属性名、参照元対応属性名、参照先クラス名、参照先対応属性名、参照対応数が定義される。参照関係の属性に対する取得操作は、参照先クラスの参照先対応属性に、参照元対応属性の値を持つ参照先クラスの統合オブジェクトを取得する操作に変換される。
【０２０６】
例えば、ＳｙａｉｎＣｌａｓｓにおいて、参照関係の属性である「ＳＹＯＺＯＫＵ＿ＳＯＳＩＫＩ」に対する取得操作が要求された場合、ＳｏｓｉｋｉＣｌａｓｓの「ＳＯＳＩＫＩ＿ＣＯＤＥ」にＳｙａｉｎＣｌａｓｓの「ＳＹＯＺＯＫＵ＿ＣＯＤＥ」の値が入ったＳｏｓｉｋｉＣｌａｓｓを取得することになる。
【０２０７】
次に、マッピング定義データ１４ｅについて、統合クラスの属性の種別が関数の場合について説明する。
【０２０８】
統合クラスの属性の種別が関数の場合、統合クラスの属性名、型、処理内容が定義される。例えば、関数の属性名として「年齢」を考えた場合、処理内容には、関数［現在の年月日−誕生年月日］が定義される。
【０２０９】
次に、アクセス制御データ１５について説明する。
【０２１０】
アクセス制御データ１５は、ロール定義データ１５ａとアクセス制御定義データ１５ｂ、１５ｃとを具備する。
【０２１１】
表１７に、ロール定義データ１５ａの例を示す。
【０２１２】
【表１７】

ロール定義データ１５ａでは、複数の権限をまとめたロールと、そのロールに対応付けられるアプリケーションが定義される。この例では、アプリケーション４ａについての権限がまとめられてロール「ＲＯＬＥ０１」とされ、アプリケーション４ｂについての権限がまとめられてロール「ＲＯＬＥ０２」とされる。
【０２１３】
表１８に、ロール「ＲＯＬＥ０１」についてのアクセス制御定義データ１５ｂの例を示す。
【０２１４】
【表１８】

【０２１５】
表１９に、ロール「ＲＯＬＥ０２」についてのアクセス制御定義データ１５ｃの例を示す。
【０２１６】
【表１９】

アクセス制御定義データ１５ｂ、１５ｃでは、各ロールの内容が定義され、クラスに対する操作（検索、登録、更新、削除）と、属性に対する操作（Ｒｅａｄ、Ｗｒｉｔｅ）の権限が定義される。
【０２１７】
図１４は、本実施例におけるデータソース統合システム３の処理フローの第１例を示すブロック図である。
【０２１８】
この図１４では、アプリケーション４ａが、名前「ＴＴＴ」の社員オブジェクト２４を検索する操作を行う。
【０２１９】
前提条件として、操作対象となる名前「ＴＴＴ」の社員オブジェクト２４は記録装置１３ｃに記録されていないとする。
【０２２０】
ステップＨ１において、データソース統合システム３の操作内容解析部７は、アプリケーション４ａから検索要求を表すデータ操作命令「ＳＥＬＥＣＴ ＊ ＦＲＯＭ ＳｙａｉｎＣｌａｓｓ ＷＨＥＲＥ ＮＡＭＥ＝ＴＴＴ」を受け付け、操作内容を解析し、操作内容をアクセス制御部８に提供する。具体的には、まず「アプリケーション４ａからの要求」であり、操作が「検索」であり、操作対象オブジェクトのクラスが「ＳｙａｉｎＣｌａｓｓ」である旨の情報を抽出する。更に操作対象オブジェクトを特定するためのキーが「ＮＡＭＥ＝ＴＴＴ」であり、操作対象の属性が「全ての属性」である旨（上記操作命令の「＊」の部分）の情報を抽出し、これらの情報をアクセス制御部８に提供する。
【０２２１】
ステップＨ２において、アクセス制御部８は、上記表１７〜１９に例示するアクセス制御データ１５を参照し、アプリケーション４ａの権限情報を取得する。
【０２２２】
具体的には、アクセス制御部８は、上記表１７のロール定義データ１５ａに基づいて、アプリケーション４ａの権限情報はＲＯＬＥ０１に対応することを抽出する。そして、操作対象オブジェクトのクラスが「ＳｙａｉｎＣｌａｓｓ」であることから、上記表１８の「ＲＯＬＥ０１」のアクセス制御定義データ１５ｂに基づいて、「ＳｙａｉｎＣｌａｓｓ」に対する権限情報を抽出する。表１８の例では「ＳｙａｉｎＣｌａｓｓ」を検索可能であり、「ＢＩＲＴＨＤＡＴＥ」「ＫＥＩＴＡＩ」「ＡＧＥ」属性を除く属性に対して、Ｒｅａｄ権限が与えられていることを認識可能である。したがって、アクセス制御部８は、「ＳｙａｉｎＣｌａｓｓ」で定義され、「ＮＡＭＥ＝ＴＴＴ」のオブジェクトの「ＢＩＲＴＨＤＡＴＥ、ＫＥＩＴＡＩ、ＡＧＥを除く全ての属性」に対する「検索」である旨の情報をオブジェクト処理部９の検索部９ｂに出力する。
【０２２３】
ステップＨ３において、オブジェクト処理部９の検索部９ｂは、アクセス制御部８からの情報を受け付けると、検索対象の「ＮＡＭＥ＝ＴＴＴ」の社員オブジェクト２４について記録装置１３ｃに対して検索を行う。
【０２２４】
検索の結果、記録装置１３ｃに検索対象の社員オブジェクト２４が存在しないため、ステップＨ４において、オブジェクト処理部９の生成部９ｃは、データソースＡ、Ｂに関する情報を得るために、オブジェクト処理部９の定義データ読込部９ａを通して、定義データ１４に含まれる上記表１４及び表１５の示すデータソース定義データ１４ｃ、１４ｄを参照する。また、生成部９ｃは、統合クラスの属性とデータソースＡ、Ｂとのマッピング関係を表す上記表１６に示すマッピング定義データ１４ｅを参照する。
【０２２５】
マッピング定義データ１４ｅでは、統合クラス「ＳｙａｉｎＣｌａｓｓ」の属性「ＮＡＭＥ」が、データソースＡのオブジェクトクラス「ｉｎｅｔＯｒｇＰｅｒｓｏｎ」の属性「ｃｎ」に関係付けされている。したがって、統合クラス「ＳｙａｉｎＣｌａｓｓ」に対する検索キー「ＮＡＭＥ＝ＴＴＴ」を、データソースＡに対する検索キー「ｃｎ＝ＴＴＴ」としてデータソースＡ内を検索すれば、データソースＡに格納された名前「ＴＴＴ」のデータを取得可能である。また、データソースＢに格納された名前「ＴＴＴ」のデータも取得するために、上記表１６のマッピング定義データ１４ｅの共通キーを参照し、データソースＡとデータソースＢで同じ値を持つ属性を調べる。マッピング定義データ１４ｅでは、データソースＡのオブジェクトクラス「ｉｎｅｔＯｒｇＰｅｒｓｏｎ」の属性「ｕｉｄ」と、データソースＢのテーブル「ＳＹＡＩＮ」の列名「ＮＵＭＢＥＲ」とが同じ値を持つと記されている。したがって、データソースＡの検索の結果得られる「ｕｉｄ」の値を、データソースＢのテーブル「ＳＹＡＩＮ」の列名「ＮＵＭＢＥＲ」の値として、データソースＢに対する検索キー「ＮＵＭＢＥＲ＝＜ｕｉｄの属性値＞」を作成し検索すれば、データソースＢに格納された名前「ＴＴＴ」のデータを取得できる。
【０２２６】
そこで、生成部９ｃは、ステップＨ５において、「ｃｎ＝ＴＴＴ」をキーとする検索要求、「ＮＵＭＢＥＲ＝＜ｕｉｄの属性値＞」をキーとする検索要求をトランザクション管理部１１に提供する。
【０２２７】
ステップＨ６において、トランザクション管理部１１は、マッピング定義データ１４ｅを参照することにより、「ｃｎ」属性がデータソースＡに格納されていることを認識し、「ｃｎ＝ＴＴＴ」をキーとする検索要求をデータソースＡに対応したデータソースアクセス部１２ａに提供する。
【０２２８】
ステップＨ７において、データソースアクセス部１２ａは、上記表１２のデータソース接続定義データ１４ａを参照し、データソースＡに接続するための情報を取得した後、上記表１３のデータソースアクセス方法定義データ１４ｂを参照し、データソースＡから「ｃｎ＝ＴＴＴ」をキーとする検索を行うためのコマンドを作成する。
【０２２９】
具体的には、ホスト名がｌｄａｐｈｏｓｔの３８９ポートにｃｎ＝Ｄｉｒｅｃｔｏｒｙ Ｍａｎａｇｅｒで接続し、「ｌｄａｐｓｅａｒｃｈ ｃｎ＝ＴＴＴ “ｏｂｊｅｃｔｃｌａｓｓ＝ｉｎｅｔＯｒｇＰｅｒｓｏｎ”」というコマンドを用いて検索を行う。
【０２３０】
検索の結果、統合クラスの「ＳＹＡＩＮ＿ＮＵＭ」「ＭＡＩＬ＿ＡＤＤＲＥＳＳ」「ＳＹＯＺＯＫＵ＿ＣＯＤＥ」属性に対応付けられたデータソースＡの「ｕｉｄ」「ｍａｉｌ」「ｏｕ」属性の属性値「１００００１」「ＴＴＴ＠ＴＴＴ．ｃｏ．ｊｐ」「２０１」を取得し、トランザクション管理部１１に提供する。
【０２３１】
このとき、統合クラスの「ＫＥＩＴＡＩ」に対応する「ｍｏｂｉｌｅ」の属性値についてはアクセス権限がないため取得されない。また、属性種別が参照関係の属性については、その属性に対して直接取得操作がない限り取得されない。
【０２３２】
続いて、ステップＨ８において、トランザクション管理部１１は、マッピング定義データ１４ｅを参照することにより、「ＮＵＭＢＥＲ」がデータソースＢに格納されていることを認識し、データソースＡの検索で得られた「ｕｉｄ」の値「１００００１」を「ＮＵＭＢＥＲ」の値として、「ＮＵＭＢＥＲ＝１００００１」をキーとする検索要求をデータソースＢに対応したデータソースアクセス部１２ｂに提供する。
【０２３３】
ステップＨ９において、データソースアクセス部１２ｂは、上記表１２のデータソース接続定義データ１４ａを参照し、データソースＢに接続するための情報を取得した後、上記表１３のデータソースアクセス方法定義データ１４ｂを参照し、「ＮＵＭＢＥＲ＝１００００１」をキーとする検索を行うためのコマンドを作成する。
【０２３４】
具体的には、ホスト名がｒｄｂｈｏｓｔの１５２１ポートにＡｄｍｉｎで接続し、「ＳＥＬＥＣＴ ＊ ＦＲＯＭ ＳＹＡＩＮ ＷＨＥＲＥ ＮＵＭＢＥＲ＝１００００１」を用いて検索を行う。
【０２３５】
検索の結果、統合クラスの「ＴＥＬＥＰＨＯＮＥ」「ＹＡＫＵＳＹＯＫＵ」属性に対応付けられたデータソースＢの「ＴＥＬ」「ＳＹＯＫＵＩ」属性の属性値「０１１−２２２−３４５６」「Ｓ」を取得し、トランザクション管理部１１に提供する。
【０２３６】
このとき、統合クラスの属性「ＢＩＲＴＨＤＡＴＥ」に対応する「ＢＩＲＴＨ」の属性値についてはアクセス権限がないため取得されない。
【０２３７】
ステップＨ１０において、トランザクション管理部１１は、データソースＡ、Ｂの検索結果を生成部９ｃに提供する。
【０２３８】
なお、上記処理において、データソースＡに対するデータの検索とデータソースＢに対するデータの検索の順序は、統合クラスに対する検索キーに使われる属性がどのデータソースに格納されているかによる。本実施例では、統合クラスの「ＮＡＭＥ」属性がデータソースＡの「ｃｎ」属性に関係付けられているため、データソースＡから検索される。並列で検索が可能な場合は並列に行われてもよい。
【０２３９】
ステップＨ１１において、生成部９ｃは、データソースＡとデータソースＢのデータを統合した名前「ＴＴＴ」の社員オブジェクト２４を生成する。
【０２４０】
ステップＨ１２において、生成部９ｃは、生成された名前「ＴＴＴ」の社員オブジェクトを記録装置１３ｃに記録するとともに、アクセス制御部８、操作内容解析部７経由でアプリケーション４ａに提供する。
【０２４１】
図１５は、本実施例におけるデータソース統合システムの処理フローの第２例を示すブロック図である。なお、この図１５では、上記図１４と同様にアプリケーション４ａが、名前「ＴＴＴ」の社員オブジェクト２４を検索する操作を行う。また、この図１５では、操作対象となる社員オブジェクト２４は記録装置１３ｃに記録されているとする。
【０２４２】
ステップＩ１、Ｉ２は、上記図１４のステップＨ１、Ｈ２と同様である。
【０２４３】
ステップＩ３において、オブジェクト処理部９の検索部９ｂは、検索対象の「ＮＡＭＥ＝ＴＴＴ」の社員オブジェクト２４の検索を記録装置１３ｃに対して行う。
【０２４４】
検索の結果、記録装置１３ｃに検索対象の社員オブジェクト２４が存在するため、ステップＩ４において、検索部９ｂは、検索された名前「ＴＴＴ」の社員オブジェクト２４をアクセス制御部８、操作内容解析部７経由でアプリケーション４ａに提供する。
【０２４５】
このように、データソース統合システム３の記録装置１３ｃに、種類の異なるデータソースの内容を反映し統合した統合オブジェクトを記録することにより、データの検索が要求された場合であってもデータソースをアクセスしなくてもよい場合がある。これにより、データの検索処理が高速化される。
【０２４６】
なお、異なるアプリケーションから同じ検索要求が複数回行われた場合であっても、１回目の検索要求時に統合オブジェクトが作成され、記録されるため、２回目以降ではデータソースを実際にアクセスする必要がなく処理を高速化できる。
【０２４７】
（第２の実施例）
本実施例では、上記第１の実施例と同様の条件において、アプリケーション４ｂが、社員番号「１００００１」の社員オブジェクト２４の属性「電話番号（ＴＥＬＥＰＨＯＮＥ）」の属性値と属性「役職（ＹＡＫＵＳＹＯＫＵ）」の属性値をそれぞれ「０１１−２２２−７８９０」、「ＳＳ」に更新する操作を行う場合について説明する。
【０２４８】
本実施例において、操作対象となる社員オブジェクト２４はデータソース統合システム３の記録装置１３ｃに記録されているとし、データソースへの書き込みタイミングはアプリケーションからデータソースに書き込みを行う旨を示す書込要求を受け付けたときとする。
【０２４９】
図１６は、本実施例におけるデータソース統合システム３の処理フローの例を示すブロック図である。
【０２５０】
ステップＪ１において、データソース統合システム３の操作内容解析部７は、アプリケーション４ｂから更新要求を表すデータ操作命令「ＵＰＤＡＴＥ ＳｙａｉｎＣｌａｓｓ ＳＥＴ ＴＥＬＥＰＨＯＮＥ ＝ ０１１−２２２−７８９０， ＹＡＫＵＳＹＯＫＵ＝ＳＳ ＷＨＥＲＥ ＳＹＡＩＮ＿ＮＵＭ＝１００００１」を受け付け、操作内容を解析し、操作内容をアクセス制御部８に提供する。具体的には、「アプリケーション４ｂからの要求」であり、操作が「更新」であり、操作対象オブジェクトのクラスが「ＳｙａｉｎＣｌａｓｓ」である旨の情報を抽出する。更に、操作対象オブジェクトを特定するためのキーが「ＳＹＡＩＮ＿ＮＵＭ＝１００００１」であり、更新内容が「ＴＥＬＥＰＨＯＮＥ＝０１１−２２２−７８９０、ＹＡＫＵＳＹＯＫＵ＝ＳＳ」である旨の情報を抽出し、これらの情報をアクセス制御部８に提供する。
【０２５１】
ステップＪ２において、アクセス制御部８は、上記表１７〜１９に例示するアクセス制御データ１５を参照し、アプリケーション４ｂの権限情報を取得する。
【０２５２】
具体的には、アクセス制御部８は、上記表１７のロール定義データ１５ａに基づいて、アプリケーション４ｂの権限情報はＲＯＬＥ０２に対応することを抽出する。そして、操作対象オブジェクトのクラスが「ＳｙａｉｎＣｌａｓｓ」であることから、上記表１９のＲＯＬＥ０２のアクセス制御定義データ１５ｃに基づいて、「ＳｙａｉｎＣｌａｓｓ」に対する権限情報を抽出する。表１９の例では「ＳｙａｉｎＣｌａｓｓ」の検索、登録、更新、削除が可能であり、全ての属性に対してＲｅａｄ、Ｗｒｉｔｅの権限が与えられていることを認識可能である。したがって、アクセス制御部８は、「ＳｙａｉｎＣｌａｓｓ」で定義され、「ＳＹＡＩＮ＿ＮＵＭ＝１００００１」のオブジェクトの「ＴＥＬＥＰＨＯＮＥ」「ＹＡＫＵＳＹＯＫＵ」属性の属性値を「０１１−２２２−７８９０」「ＳＳ」に「更新」する旨の情報をオブジェクト処理部９の更新部９ｄに出力する。
【０２５３】
ステップＪ３において、オブジェクト処理部９の更新部９ｄは、アクセス制御部からの情報を受け付けると、更新対象の「ＳＹＡＩＮ＿ＮＵＭ＝１００００１」の社員オブジェクト２４の検索を記録装置１３ｃに対して行う。
【０２５４】
検索の結果、記録装置１３ｃに更新対象の社員オブジェクト２４が存在するため、ステップＪ４において、更新部９ｄは、属性「ＴＥＬＥＰＨＯＮＥ」の属性値を「０１１−２２２−７８９０」に更新し、属性「ＹＡＫＵＳＹＯＫＵ」の属性値を「ＳＳ」に更新する。
【０２５５】
このとき、ステップＪ５において、オブジェクト処理部９の排他制御部９ｇは、この更新対象の社員オブジェクト２４をロックしており、他のデータ操作命令（例えば他のアプリケーションからの更新要求）があった場合に、この他のデータ操作命令を拒否する。
【０２５６】
ステップＪ６において、更新部９ｄは、社員オブジェクト２４の更新が終わった後、更新完了メッセージをアクセス制御部８、操作内容解析部７経由でアプリケーション４ｂに提供する。
【０２５７】
ここで、アプリケーション４ｂは、社員オブジェクト２４の内容をデータソースに反映する旨の書込命令をデータソース統合システム３に提供したとする。
【０２５８】
ステップＪ７において、操作内容解析部７は、アプリケーション４ｂから書込命令を受け付け、アクセス制御部８によるアクセス権限の確認を経て書込管理部１０に提供する。
【０２５９】
ステップＪ８において、書込管理部１０は、書込命令を受け付けた場合に、オブジェクト処理部９の書込部９ｈ経由で社員オブジェクト２４を取得し、この社員オブジェクト２４の内容にしたがってデータソースを更新するためのデータソース操作命令をトランザクション管理部１１に提供する。
【０２６０】
ステップＪ９において、トランザクション管理部１１は、社員オブジェクト２４の更新要求を、それぞれデータソースに対する更新要求に変換する。
【０２６１】
具体的には、上記表１６のマッピング定義データ１４ｅを参照し、更新される社員オブジェクト２４の「ＴＥＬＥＰＨＯＮＥ」「ＹＡＫＵＳＹＯＫＵ」属性は、共にデータソースＢに格納されており、「ＳＹＡＩＮ」テーブルの「ＴＥＬ」「ＳＹＯＫＵＩ」属性に対応付けられていることを認識し、データソースＢに対応するデータソースアクセス部１２ｂに更新要求を出す。
【０２６２】
ステップＪ１０において、データソースアクセス部１２ｂは、上記表１２のデータソース接続定義データ１４ａに基づいてデータソースＢにアクセスし、上記表１３のデータソースアクセス方法定義データ１４ｂに基づいて、データソースＢに対する更新コマンド「ＵＰＤＡＴＥ」を用いたデータソースＢに対する更新要求を作成し、データソースＢを更新する。
【０２６３】
具体的には、ホスト名がｒｄｂｈｏｓｔの１５２１ポートにＡｄｍｉｎで接続し、「ＵＰＤＡＴＥ ＳＹＡＩＮ ＳＥＴ ＴＥＬ＝０１１−２２２−７８９０ ， ＳＹＯＫＵＩ＝ＳＳ ＷＨＥＲＥ ＳＹＡＩＮ＿ＮＵＭ＝１００００１」を用いて更新を行う。
【０２６４】
なお、本実施例では、アプリケーションからの書込要求にしたがってデータソースへの書き込みが行われるが、例えば時刻指定など、所定のデータソースへの書き込みタイミング毎に、バッチ処理によりデータソースへの書き込みが行われてもよい。
【０２６５】
（第３の実施例）
本実施例では、アプリケーション４ｂからの操作によって、組織コード「２０１」の組織に属する社員の社員オブジェクトが取得され、取得された社員オブジェクトに含まれる電話番号を更新する。
【０２６６】
本実施例では、操作対象となる組織オブジェクト、社員オブジェクトは記録装置１３ｃに記録されていないとする。
【０２６７】
本実施例において、アプリケーション４ｂは、上記第１の実施例と同様の条件において、第１段階で、組織コード「２０１」の組織オブジェクト２５を参照し、第２段階で、参照した組織オブジェクト２５に属する社員の社員オブジェクト２４ａ〜２４ｃを検索し、第３段階で、検索された社員オブジェクト２４ａ〜２４ｃの電話番号を「０１１−５５５−５５５５」に更新する。
【０２６８】
図１７は、本実施例におけるデータソース統合システム３の第１段階の処理フローの例を示すブロック図である。この図１７では、組織オブジェクト２５の検索までの処理が表されている。
【０２６９】
ステップＫ１において、データソース統合システム３の操作内容解析部７は、アプリケーション４ｂから組織コード「２０１」の組織オブジェクト２５の検索要求を表すデータ操作命令「ＳＥＬＥＣＴ ＊ ＦＲＯＭ ＳｏｓｉｋｉＣｌａｓｓ ＷＨＥＲＥ ＳＯＳＩＫＩ＿ＣＯＤＥ＝２０１」を受け付け、操作内容を解析し、操作内容をアクセス制御部８に提供する。具体的には、「アプリケーション４ｂからの要求」であり、操作が「検索」であり、操作対象オブジェクトのクラスが「ＳｏｓｉｋｉＣｌａｓｓ」である旨の情報を抽出する。更に操作対象オブジェクトを特定するためのキーが「ＳＯＳＩＫＩ＿ＣＯＤＥ＝２０１」であり、操作対象の属性が「全ての属性」である旨（上記操作命令の「＊」の部分）の情報を抽出し、これらの情報をアクセス制御部８に提供する。
【０２７０】
ステップＫ２において、アクセス制御部８は、上記表１７のロール定義データ１５ａ及び上記表１９のアクセス制御定義データ１５ｃを参照し、アプリケーション４ｂの権限情報を取得する。
【０２７１】
具体的には、アクセス制御部８は、上記表１７のロール定義データ１５ａに基づいて、アプリケーション４ｂの権限情報はＲＯＬＥ０２に対応することを抽出する。そして、操作対象オブジェクトのクラスが「ＳｏｓｉｋｉＣｌａｓｓ」であることから、上記表１９のＲＯＬＥ０２のアクセス制御定義データ１５ｂに基づいて、「ＳｏｓｉｋｉＣｌａｓｓ」に対する権限情報を抽出する。表１９の例では「ＳｏｓｉｋｉＣｌａｓｓ」の検索、登録、更新、削除が可能であり、全ての属性に対してＲｅａｄ、Ｗｒｉｔｅの権限が与えられていることを認識可能である。したがって、アクセス制御部８は、「ＳｏｓｉｋｉＣｌａｓｓ」で定義され、「ＳＯＳＩＫＩ＿ＣＯＤＥ＝２０１」のオブジェクトの「全ての属性」に対する「検索」である旨の情報をオブジェクト処理部９の検索部９ｂに出力する。
【０２７２】
ステップＫ３において、オブジェクト処理部９の検索部９ｂは、検索対象の「ＳＯＳＩＫＩ＿ＣＯＤＥ＝２０１」の組織オブジェクト２５について記録装置１３ｃに対して検索を行う。
【０２７３】
検索の結果、記録装置１３ｃに検索対象の組織オブジェクト２５が存在しないため、ステップＫ４において、オブジェクト処理部９の生成部９ｃは、データソースＡ、Ｂに関する情報を得るために、オブジェクト処理部９の定義データ読込部９ａを通して、定義データ１４に含まれる上記表１４及び表１５の示すデータソース定義データ１４ｃ、１４ｄを参照する。また、生成部９ｃは、統合クラスの属性とデータソースＡ、Ｂとのマッピング関係を表す上記表１６に示すマッピング定義データ１４ｅを参照する。
【０２７４】
マッピング定義データ１４ｅでは、統合クラス「ＳｏｓｉｋｉＣｌａｓｓ」の属性「ＳＯＳＩＫＩ＿ＣＯＤＥ」が、データソースＡのオブジェクトクラス「ｌｄａｐＳｏｓｉｋｉ」の属性「ｓｏｓｉｋｉＣｏｄｅ」と、データソースＢのテーブル「ＳＯＳＩＫＩ」の列名「Ｓ＿ＣＯＤＥ」に関係付けされている。したがって、統合クラス「ＳｏｓｉｋｉＣｌａｓｓ」に対する検索キー「ＳＯＳＩＫＩ＿ＣＯＤＥ＝２０１」を、データソースＡに対する検索キー「ｓｏｓｉｋｉＣｏｄｅ＝２０１」としてデータソースＡ内を検索するとともに、データソースＢに対する検索キー「Ｓ＿ＣＯＤＥ＝２０１」としてデータソースＢ内を検索すれば、目的とする組織オブジェクト２５のデータを取得可能である。
【０２７５】
そこで、生成部９ｃは、ステップＫ５において、「ｓｏｓｉｋｉＣｏｄｅ＝２０１」をキーとする検索要求、「Ｓ＿ＣＯＤＥ＝２０１」をキーとする検索要求をトランザクション管理部１１に提供する。
【０２７６】
ステップＫ６ａ、Ｋ６ｂにおいて、トランザクション管理部１１は、マッピング定義データ１４ｅを参照することにより、「ｓｏｓｉｋｉＣｏｄｅ」がデータソースＡに格納され、「Ｓ＿ＣＯＤＥ」がデータソースＢに格納されていることを認識し、「ｓｏｓｉｋｉＣｏｄｅ＝２０１」をキーとする検索要求をデータソースアクセス部１２ａに、「Ｓ＿ＣＯＤＥ＝２０１」をキーとする検索要求を１２ｂに提供する。
【０２７７】
ステップＫ７において、データソースアクセス部１２ａは、上記表１２のデータソース接続定義データ１４ａを参照し、データソースＡに接続するための情報を取得した後、上記表１３のデータソースアクセス方法定義データ１４ｂを参照し、データソースＡから「ｓｏｓｉｋｉＣｏｄｅ＝２０１」をキーとする検索を行うためのコマンドを作成する。
【０２７８】
具体的には、ホスト名がｌｄａｐｈｏｓｔの３８９ポートにｃｎ＝Ｄｉｒｅｃｔｏｒｙ Ｍａｎａｇｅｒで接続し、「ｌｄａｐｓｅａｒｃｈ ｓｏｓｉｋｉＣｏｄｅ＝２０１ “ｏｂｊｅｃｔｃｌａｓｓ＝ｌｄａｐＳｏｓｉｋｉ”」というコマンドを用いて検索を行う。
【０２７９】
検索の結果、統合クラスの「ＳＯＳＩＫＩＭＥＩ」「ＪＹＯＩ＿ＳＯＳＩＫＩ＿ＣＯＤＥ」属性に対応付けられたデータソースＡの「ｏｕ」「ｊｙｏｉＳｏｓｉｋｉＣｏｄｅ」属性の属性値「ｓｏｍｕ」「−（上位組織なし）」を取得し、トランザクション管理部１１に提供する。
【０２８０】
また、ステップＫ８において、データソースアクセス部１２ｂは、上記表１２のデータソース接続定義データ１４ａを参照し、データソースＢに接続するための情報を取得した後、上記表１３のデータソースアクセス方法定義データ１４ｂを参照し、データソースＢから「Ｓ＿ＣＯＤＥ＝２０１」をキーとする検索を行うためのコマンドを作成する。
【０２８１】
具体的には、ホスト名がｒｄｂｈｏｓｔの１５２１ポートにＡｄｍｉｎで接続し、「ＳＥＬＥＣＴ ＊ ＦＲＯＭ ＳＯＳＩＫＩ ＷＨＥＲＥ Ｓ＿ＣＯＤＥ＝２０１」というコマンドを用いて検索を行う。
【０２８２】
検索の結果、統合クラスの「ＳＯＳＩＫＩ＿ＴＥＬ」属性に対応付けられたデータソースＢの「ＴＥＬ」属性の属性値「０１２−３４５−１１１１」を取得し、トランザクション管理部１１に提供する。
【０２８３】
なお、上記処理において、データソースＡに対するデータの検索とデータソースＢに対するデータの検索は並列に行われてもよい。
【０２８４】
ステップＫ９において、トランザクション管理部１１は、データソースＡ、Ｂの検索結果を生成部９ｃに提供する。
【０２８５】
上記処理において、属性種別が参照関係の属性は、その属性に対する取得操作があった場合に取得される。
【０２８６】
ステップＫ１０において、生成部９ｃは、データソースＡとデータソースＢのデータを統合した組織コード「２０１」の組織オブジェクト２５を生成する。
【０２８７】
ステップＫ１１において、生成部９ｃは、組織コード「２０１」の組織オブジェクト２５を記録装置１３ｃに記録するとともに、アクセス制御部８、操作内容解析部７経由でアプリケーション４ｂに提供する。
【０２８８】
図１８は、本実施例におけるデータソース統合システム３の第２段階の処理フローの例を示すブロック図である。この図１８では、組織コード「２０１」の組織オブジェクト２５に属する社員の社員オブジェクト２４ａ〜２４ｃの検索までの処理が表されている。
【０２８９】
ステップＬ１において、データソース統合システム３の操作内容解析部７は、アプリケーション４ｂから組織コード「２０１」の組織に属する社員の社員オブジェクト２４ａ〜２４ｃの検索要求を表すデータ操作命令「ＧＥＴ ＳＯＳＩＫＩ＿ＭＥＭＢＥＲ」を受け付け、操作内容を解析し、操作内容をアクセス制御部８に提供する。具体的には、「アプリケーション４ｂからの要求」であり、操作が「検索」であり、操作対象の属性が「ＳＯＳＩＫＩ＿ＭＥＭＢＥＲ」である旨の情報を抽出し、これらの情報をアクセス制御部８に提供する。このとき、操作対象オブジェクトに関する情報は、第１段階における組織オブジェクトの検索によって、組織コード「２０１」の組織オブジェクトであると特定されている。
【０２９０】
ステップＬ２において、アクセス制御部８は、上記表１７〜１９に例示するアクセス制御データ１５を参照し、アプリケーション４ｂの権限情報を取得する。具体的には、アクセス制御部８は、上記表１７のロール定義データ１５ａに基づいて、アプリケーション４ｂの権限情報はＲＯＬＥ０２に対応することを抽出する。そして、操作対象オブジェクトのクラスが「ＳｏｓｉｋｉＣｌａｓｓ」であることから、上記表１９のＲＯＬＥ０２のアクセス制御定義データ１５ｃに基づいて、ＳｏｓｉｋｉＣｌａｓｓに対する権限情報を抽出する。表１９の例では、「ＳｏｓｉｋｉＣｌａｓｓ」の検索、登録、更新、削除が可能であり、全ての属性に対してＲｅａｄ、Ｗｒｉｔｅ権限が与えられていることを認識可能である。したがって、アクセス制御部８は、「ＳｏｓｉｋｉＣｌａｓｓ」で定義され、組織コード「２０１」のオブジェクトの「ＳＯＳＩＫＩ＿ＭＥＭＢＥＲ」に対する「検索」である旨の情報をオブジェクト処理部９の検索部９ｂに出力する。
【０２９１】
ステップＬ３において、オブジェクト処理部９の検索部９ｂは、マッピング定義データ１４ｅを参照することにより、先で検索された組織コード「２０１」の組織オブジェクト２５の属性「ＳＯＳＩＫＩ＿ＭＥＭＢＥＲ」の種別は参照関係であることを認識可能である。
【０２９２】
ステップＬ４において、検索部９ｂは、参照関係の属性の場合、参照先クラスの参照先対応属性に参照元対応属性の値を入れて参照先クラスのオブジェクトを検索する。
【０２９３】
ここでは、検索部９ｂは、定義データ１４を参照し、「ＳＯＳＩＫＩ＿ＭＥＭＢＥＲ」の検索要求を所属コード「２０１」の社員オブジェクト２４ａ〜２４ｃの検索要求に変換し、検索を行う。この例では、「ＳｙａｉｎＣｌａｓｓ」の「ＳＹＯＺＯＫＵ＿ＣＯＤＥ」属性の属性値が「２０１」である社員オブジェクト２４ａ〜２４ｃが検索される。
【０２９４】
検索の結果、社員オブジェクト２４ａ〜２４ｃは、記録装置１３ｃに記録されていないため、ステップＬ５において、オブジェクト処理部９の生成部９ｃは、定義データ１４に含まれる上記表１４及び表１５の示すデータソース定義データ１４ｃ、１４ｄ、マッピング定義データ１４ｅを参照する。
【０２９５】
マッピング定義データ１４ｅにおいて、統合クラス「ＳｙａｉｎＣｌａｓｓ」の属性「ＳＹＯＺＯＫＵ＿ＣＯＤＥ」はデータソースＡのオブジェクトクラス「ｉｎｅｔＯｒｇＰｅｒｓｏｎ」の属性「ｏｕ」に関係付けされている。したがって、統合クラス「ＳｙａｉｎＣｌａｓｓ」に対する検索キー「ＳＹＯＺＯＫＵ＿ＣＯＤＥ＝２０１」を、データソースＡに対する検索キー「ｏｕ＝２０１」としてデータソースＡ内のデータを検索すれば、データソースＡに格納された所属コード「２０１」のデータを取得可能である。また、データソースＢに格納された所属コード「２０１」のデータも取得するために、上記表１６のマッピング定義データ１４ｅの共通キーを参照し、データソースＡとデータソースＢで同じ値を持つ属性を調べる。マッピング定義データ１４ｅでは、データソースＡのオブジェクトクラス「ｉｎｅｔＯｒｇＰｅｒｓｏｎ」の属性「ｕｉｄ」とデータソースＢのテーブル「ＳＹＡＩＮ」の列名「ＮＵＭＢＥＲ」が同じ値を持つと記されている。したがって、データソースＡの検索の結果得られる「ｕｉｄ」の値を、データソースＢのテーブル「ＳＹＡＩＮ」の列名「ＮＵＭＢＥＲ」の値として、データソースＢに対する検索キー「ＮＵＭＢＥＲ＝＜ｕｉｄの属性値＞」として検索すれば、データソースＢに格納された所属コード「２０１」のデータを取得できる。
【０２９６】
そこで、生成部９ｃは、ステップＬ６において、「ｏｕ＝２０１」をキーとする検索要求、「ＮＵＭＢＥＲ＝＜ｕｉｄの属性値＞」をキーとする検索要求をトランザクション管理部１１に提供する。
【０２９７】
ステップＬ７において、トランザクション管理部１１は、マッピング定義データ１４ｅを参照することにより、「ｏｕ」属性がデータソースＡに格納されていることを認識し、「ｏｕ＝２０１」をキーとする検索要求をデータソースアクセス部１２ａに提供する。
【０２９８】
ステップＬ８において、データソースアクセス部１２ａは、上記表１２のデータソース接続定義データ１４ａを参照し、データソースＡに接続するための情報を取得した後、上記表１３のデータソースアクセス方法定義データ１４ｂを参照し、データソースＡから「ｏｕ＝２０１」をキーとする検索を行うためのコマンドを作成し、検索を行う。
【０２９９】
検索の結果、統合クラスの「ＳＹＡＩＮ＿ＮＵＭ」「ＭＡＩＬ＿ＡＤＤＲＥＳＳ」「ＫＥＴＩＡＩ」に対応付けられたデータソースＡの「ｕｉｄ」「ｍａｉｌ」「ｍｏｂｉｌｅ」属性の属性値を取得し、トランザクション管理部１１に提供する。
【０３００】
具体的には、［「ｕｉｄ＝１００００１」「ｍｉａｌ＝ＴＴＴ＠ＴＴＴ．ｃｏ．ｊｐ」「ｍｏｂｉｌｅ＝０１−１１１１−１１１１」］、［「ｕｉｄ＝１００００２」「ｍｉａｌ＝ＪＪＪ＠ＪＪＪ．ｃｏ．ｊｐ」「ｍｏｂｉｌｅ＝０１−２２２２−２２２２」］、［「ｕｉｄ＝１００００３」「ｍｉａｌ＝ＳＳＳ＠ＳＳＳ．ｃｏ．ｊｐ」「ｍｏｂｉｌｅ＝０１−３３３３−３３３３」］の３人分のデータがトランザクション管理部１１に提供される。
【０３０１】
続いて、ステップＬ９において、トランザクション管理部１１は、マッピング定義データ１４ｅを参照することにより、「ＮＵＭＢＥＲ」がデータソースＢに格納されていることを認識し、データソースＡの検索で得られた「ｕｉｄ」の値「１００００１」「１００００２」「１００００３」を「ＮＵＭＢＥＲ」の値として、「ＮＵＭＢＥＲ＝１００００１」「ＮＵＭＢＥＲ＝１００００２」「ＮＵＭＢＥＲ＝１００００３」をキーとする３つの検索要求をデータソースＢに対応したデータソースアクセス部１２ｂに提供する。
【０３０２】
ステップＬ１０において、データソースアクセス部１２ｂは、上記表１２のデータソース接続定義データ１４ａを参照し、データソースＢに接続するための情報を取得した後、上記表１３のデータソースアクセス方法定義データ１４ｂを参照し、「ＮＵＭＢＥＲ＝１００００１」「ＮＵＭＢＥＲ＝１００００２」「ＮＵＭＢＥＲ＝１００００３」をキーとする検索を行うためのコマンドをそれぞれ作成し、検索を行う。
【０３０３】
検索の結果、統合クラスの「ＴＥＬＥＰＨＯＮＥ」「ＹＡＫＵＳＹＯＫＵ」「ＢＩＲＴＨＤＡＴＥ」に対応付けられたデータソースＢの「ＴＥＬ」「ＳＹＯＫＵＩ」「ＢＩＲＴＨ」属性の属性値を取得し、トランザクション管理部１１に提供する。
【０３０４】
具体的には、［「ＴＥＬ＝０１１−２２２−３４５６」「ＳＹＯＫＵＩ＝Ｓ」「ＢＩＲＴＨ＝１９６５／０１／０１」］、［「ＴＥＬ＝０１１−２２２−３４５６」「ＳＹＯＫＵＩ＝Ｅ」「ＢＩＲＴＨ＝１９７０／０５／１２」］、［「ＴＥＬ＝０１１−２２２−３４５６」「ＳＹＯＫＵＩ＝Ｅ」「ＢＩＲＴＨ＝１９７１／０３／０７」］の３人分のデータがトランザクション管理部１１に提供される。
【０３０５】
ステップＬ１１において、トランザクション管理部１１は、データソースＡ、Ｂの検索結果を生成部９ｃに提供する。
【０３０６】
ステップＬ１２において、データソース統合システム３の生成部９ｃは、所属コード「２０１」の社員オブジェクト２４ａ〜２４ｃの集合を生成する。このとき、属性種別が関数である「ＡＧＥ」属性が計算され、社員オブジェクトに含められる。
【０３０７】
ステップＬ１３において、社員オブジェクト２４ａ〜２４ｃをアプリケーション４ｂに返すとともに、記録装置１３ｃに記録する。
【０３０８】
図１９は、本実施例におけるデータソース統合システム３の第３段階の処理フローの例を示すブロック図である。この図１９では、検索された社員オブジェクト２４ａ〜２４ｃの電話番号が「０１１−５５５−５５５５」に更新されるまでの処理が表されている。
【０３０９】
ステップＭ１において、操作内容解析部７は、アプリケーション４ｂから、組織コード「２０１」の組織に属する社員の社員オブジェクト２４ａ〜２４ｃの電話番号を「０１１−５５５−５５５５」に更新するデータ操作命令「ＳＥＴ ＴＥＬＥＰＨＯＮＥ＝０１１−５５５−５５５５」を受け付け、アクセス制御部８に提供する。具体的には、「アプリケーション４ｂからの要求」であり、操作が「更新」であり、操作対象の属性が「ＴＥＬＥＰＨＯＮＥ」である旨の情報を抽出し、これらの情報をアクセス制御部８に提供する。このとき、操作対象オブジェクトに関する情報は、第２段階における組織コード「２０１」の組織に属する社員オブジェクトの検索によって、所属コードが「２０１」である社員オブジェクトであると特定されている。
【０３１０】
ステップＭ２において、アクセス制御部８は、上記表１７〜１９に例示するアクセス制御データ１５を参照し、アプリケーション４ｂの権限情報を取得する。具体的には、アクセス制御部８は、上記表１７のロール定義データ１５ａに基づいて、アプリケーション４ｂの権限情報はＲＯＬＥ０２に対応することを抽出する。そして、操作対象オブジェクトのクラスが「ＳｙａｉｎＣｌａｓｓ」であることから、上記表１９のＲＯＬＥ０２のアクセス制御定義データ１５ｃに基づいて、ＳｙａｉｎＣｌａｓｓに対する権限情報を抽出する。表１９の例では、「ＳｙａｉｎＣｌａｓｓ」の検索、登録、更新、削除が可能であり、全ての属性に対してＲｅａｄ、Ｗｒｉｔｅ権限が与えられていることを認識可能である。したがって、アクセス制御部８は、「ＳｙａｉｎＣｌａｓｓ」で定義され、所属コード「２０１」の社員オブジェクトの「ＴＥＬＥＰＨＯＮＥ」に対する「更新」である旨の情報をオブジェクト処理部９の更新部９ｄに出力する。
【０３１１】
ステップＭ３において、オブジェクト処理部９の更新部９ｄは、記録装置１３ｃに対して所属コード「２０１」の社員オブジェクト２４ａ〜２４ｃの属性「ＴＥＬＥＰＨＯＮＥ」の属性値を「０１１−５５５−５５５５」に更新する。
【０３１２】
【発明の効果】
以上詳記したように本発明においては、複数のデータソースの内容が統一して管理され、効率的にデータを管理できる。
【図面の簡単な説明】
【図１】本発明の第１の実施の形態に係るデータソース統合システムの構成の一例を示すブロック図。
【図２】同実施の形態に係るオブジェクト処理部の詳細例を示すブロック図。
【図３】同実施の形態におけるデータソースの内容と統合クラスとの関係の一例を示す図。
【図４】同実施の形態における複数のクラス間の参照関係の定義された統合クラスの一例を示す図。
【図５】同実施の形態に係るデータソース統合システムの動作概念の第１例を示すブロック図。
【図６】同実施の形態に係るデータソース統合システムの動作概念の第２例を示すブロック図。
【図７】同実施の形態に係るデータソース統合システムの動作概念の第３例を示すブロック図。
【図８】同実施の形態に係るデータソース統合システムの動作概念の第４例を示すブロック図。
【図９】同実施の形態に係るデータソース統合システムの動作概念の第５例を示すブロック図。
【図１０】同実施の形態に係るデータソース統合システムの処理の例を示すフローチャート。
【図１１】本発明の第２の実施の形態に係るデータソース統合システムの構成の一例を示すブロック図。
【図１２】同実施の形態に係るデータソース統合システムの処理の例を示すフローチャート。
【図１３】本発明の第１の実施例で用いられるデータソースのツリー構成の例を示すブロック図。
【図１４】同実施例に係るデータソース統合システムの処理フローの第１例を示すブロック図。
【図１５】同実施例に係るデータソース統合システムの処理フローの第２例を示すブロック図。
【図１６】本発明の第２の実施例に係るデータソース統合システムの処理フローの例を示すブロック図。
【図１７】本発明の第３の実施例に係るデータソース統合システムの第１段階の処理フローの例を示すブロック図。
【図１８】同実施例に係るデータソース統合システムの第２段階の処理フローの例を示すブロック図。
【図１９】同実施例に係るデータソース統合システムの第３段階の処理フローの例を示すブロック図。
【図２０】データソースの内容をオブジェクトに変換した図。
【符号の説明】
３、２０…データソース統合システム、４ａ〜４ｃ…アプリケーション、６…記録媒体、６ａ，６ｂ…データソース統合プログラム、７…操作内容解析部、８…アクセス制御部、９…オブジェクト処理部、１０…書込管理部、１１…トランザクション管理部、１２ａ〜１２ｃ…データソースアクセス部、１３ａ〜１３ｃ…記録装置、１４…定義データ、１５…アクセス制御データ、Ａ〜Ｃ…データソース、９ａ…定義データ読込部、９ｂ…検索部、９ｃ…生成部、９ｄ…更新部、９ｅ…登録部、９ｆ…削除部、９ｇ…排他制御部、９ｈ…書込部[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention relates to a program, a system, and a method for realizing sharing, management, and effective utilization of various data.
[0002]
[Prior art]
Many data sources exist for the purpose of sharing, managing, and effectively utilizing data. Examples of the data source include various databases such as an LDAP (Lightweight Directory Access Protocol) directory, an object-oriented database, an RDB (Relational Database), an XML (Extensible Markup Language) database, a text file, a CSV file (CSVComm), a CSV file (CSVComm), and the like. There are various types such as various files and file systems, and data is managed by various methods.
[0003]
As shown in FIG. 20, a technique for converting data in a certain data source 1a recorded in a certain recording device 28a into an object 2a and managing the data has already been proposed. By using this technique, data can be individually objectized and managed for each of the data sources 1a to 1c recorded in each of the recording devices 28a to 28c.
[0004]
[Patent Document 1]
JP 2000-242542 A
[0005]
[Patent Document 2]
JP-A-2000-242541
[0006]
[Problems to be solved by the invention]
Systems that handle multiple different types of data sources are increasing. Data management in such a system has the following problems, making it difficult to manage data efficiently.
[0007]
First, when handling a plurality of types of data sources, the system has a problem that it is necessary to always know the type of target data and the storage location of the data.
[0008]
Secondly, the system needs to separately perform update processing for all data sources related to this data each time an update of certain data occurs, which increases the number of processing and reduces the processing speed. .
[0009]
Third, the system needs to separately manage transactions and control access to a plurality of different types of data sources.
[0010]
For example, as shown in FIG. 20 described above, when data is individually converted into objects for a plurality of different data sources 1a to 1c, the system stores target data in an object generated from any data source. It is necessary to always keep track of Further, when an update of a certain data is requested, the system relates to the data to be updated among the objects 2a to 2c generated from the plurality of types of data sources 1a to 1c at the requested update timing. Update processing is performed on all objects. For this reason, many processes are concentrated and the processing speed may be reduced.
[0011]
The present invention has been made in view of the above circumstances, and has as its object to provide a data source integration program, a system, and a method for unifying and managing the contents of a plurality of data sources and improving the efficiency of data management. And
[0012]
[Means for Solving the Problems]
Specific means taken for realizing the present invention will be described below.
[0013]
According to the present invention, there is provided a receiving function for receiving a data operation command from a command source, generating data from a plurality of different types of data sources recorded in advance in a recording unit in accordance with an operation command received by the receiving function. The data source is a data source integration program that realizes a function and is characterized by including data to be managed and information of a management form.
[0014]
In the present invention, integrated data in which the contents of a plurality of data sources are integrated is generated, and data operation is performed on the integrated data. Thereby, the contents of a plurality of data sources are unified and managed, and data management can be made more efficient.
[0015]
It should be noted that means for implementing the above functions may be provided in the computer system.
[0016]
By implementing the data management method implemented by the data source integration program, a similar effect can be obtained.
[0017]
BEST MODE FOR CARRYING OUT THE INVENTION
Hereinafter, embodiments of the present invention will be described with reference to the drawings.
[0018]
(First Embodiment)
In the present embodiment, a data source integration system that converts data scattered in a plurality of data sources of different types into integrated objects of a predetermined format and manages them unifiedly will be described.
[0019]
FIG. 1 is a block diagram showing an example of the configuration of the data source integration system according to the present embodiment. FIG. 2 is a block diagram illustrating a detailed example of the object processing unit.
[0020]
The data source integration system 3 operates between the applications 4a to 4c and the recording devices 27A to 27C that record the data sources A to C. The applications 4a to 4c are command sources, but for example, a user or the like may be the command source.
[0021]
In the present embodiment, a case will be described in which there are three applications 4a to 4c and three data sources A to C. However, the number of applications may be one or more and the number of data sources may be plural.
[0022]
Here, the data source refers to information on actual data to be managed and a management form thereof. As described above, for example, an LDAP (Lightweight Directory Access Protocol) directory, an object-oriented database, an RDB (Relational Database), and an XML (Extensible Markup). There are various types such as various databases such as a language database, various files such as a text file, a CSV (Comma Separated Value) file, and a binary file. Further, the information on the management form refers to information on association of managed data and information necessary for data acquisition and writing (information necessary for data management). For example, in LDAP, association between object classes is referred to. There is information and information on association between an object class and an attribute included in the class. In the latter example, in the inetOrgPerson class, information on association between the class and attributes such as cn, uid, and ou included in the class is included. is there. Further, in the RDB, there is information on association between tables and information on association between tables and columns included in the tables. In Table 11 and the like, in the latter example, information on association between employee tables and NUMBER, TEL and the like included in the employee table is included. is there.
[0023]
The data source integration system 3 reads the data source integration program 6a recorded on the recording medium 6 and executes the data source integration program 6a, so that the operation content analysis unit 7, the access control unit 8, the object processing unit 9, the write management unit 10, The functions as the transaction management unit 11 and the data source access units 12a to 12c are realized. The data source integration system 3 includes recording devices 13a to 13c.
[0024]
The processing mode of the data source integration system 3 is of an interpreter type that receives a data operation command and executes processing while referring to the definition data 14 recorded in the recording device 13b as necessary.
[0025]
The operation content analysis unit 7 receives a data operation command from the command source, analyzes the operation content indicated by the data operation command, and provides the operation content to the access control unit 8.
[0026]
Further, the operation content analysis unit 7 provides various data or messages received from the object processing unit 9 via the access control unit 8 to the command source.
[0027]
The access control unit 8 refers to the access control data 15 recorded in the recording device 13a and determines whether or not the command source has authority for the operation content analyzed by the operation content analysis unit 7.
[0028]
When determining that the access control unit 8 has the authority, the access control unit 8 provides the operation content to the object processing unit 9, receives a result corresponding to the operation content from the object processing unit 9, and provides the result to the operation content analysis unit 7.
[0029]
On the other hand, if the access control unit 8 determines that the user does not have the right, the access control unit 8 provides a message indicating that the user does not have the right to the command source via the operation content analysis unit 7.
[0030]
As shown in FIG. 2, the object processing unit 9 includes a definition data reading unit 9a, a searching unit 9b, a generating unit 9c, an updating unit 9d, a registering unit 9e, a deleting unit 9f, an exclusive control unit 9g, and a writing unit 9h. I do.
[0031]
The definition data reading unit 9a reads the definition data 14 recorded in the recording device 13b in response to a request from another part of the object processing unit 9, and returns the read definition data 14 to the request destination.
[0032]
When the operation content received from the operation content analysis unit 7 via the access control unit 8 represents a data search request, the search unit 9b searches the recording device 13c for an integrated object including the search target data.
[0033]
When the integrated unit including the search target data can be searched from the recording device 13c, the search unit 9b provides the searched integrated object to the command source via the access control unit 8 and the operation content analysis unit 7.
[0034]
On the other hand, if the integrated object including the data to be searched is not recorded in the recording device 13c and cannot be searched, the search unit 9b provides the operation content to the generation unit 9c.
[0035]
When the integrated object including the search target data is not recorded in the recording device 13c, the generation unit 9c reads the definition data 14 recorded in the recording device 13b via the definition data reading unit 9a, and reads the definition data 14 from the transaction management unit 11 and The data sources A to C are searched via the data source access units 12a to 12c.
[0036]
Further, the generation unit 9c generates an integrated object including data to be searched based on the integrated class defined by the definition data 14 and the search results of the data sources A to C, and accesses the generated integrated object. The information is provided to the command source via the control unit 8 and the operation content analysis unit 7 and is recorded in the recording device 13c.
[0037]
When the operation content indicates a request for updating the integrated object, the update unit 9d updates the content of the integrated object of the recording device 13c according to the update content specified by the data operation instruction.
[0038]
The update unit 9d provides a message indicating the result of the update process to the command source via the access control unit 8 and the operation content analysis unit 7.
[0039]
When the operation content indicates a request for registration of an integrated object, the registration unit 9e records the integrated object including the data specified by the data operation instruction in the recording device 13c.
[0040]
The registration unit 9e provides a message indicating the result of the registration process to the command source via the access control unit 8 and the operation content analysis unit 7.
[0041]
When the operation content indicates a data deletion request, the deletion unit 9f deletes the data to be deleted from the recording device 13c by the data operation command.
[0042]
Further, the deletion unit 9f provides a message indicating the result of the deletion process to the command source via the access control unit 8 and the operation content analysis unit 7.
[0043]
The exclusive control unit 9g executes exclusive control for ensuring data consistency when an operation is performed on the integrated object recorded in the recording device 13c.
[0044]
That is, when the search unit 9b, the generating unit 9c, the updating unit 9d, the registering unit 9e, and the deleting unit 9f perform an operation on the integrated object recorded on the recording device 13c, the exclusive control unit 9g Prohibit (lock) work from.
[0045]
When the writing unit 9h receives a command from the writing management unit 10 at the time when the content of the integrated object recorded in the recording device 13c is reflected on the data sources A to C, the writing unit 9h records the integrated object recorded in the recording device 13c. The object is read and returned to the write management unit 10.
[0046]
When a predetermined event occurs, the writing management unit 10 provides an instruction to the writing unit 9h of the object processing unit 9, receives an integrated object recorded in the recording device 13c as a response, and receives the received integrated object. An operation instruction for reflecting the contents of the object in the data sources A to C is provided to the transaction management unit 11.
[0047]
The occurrence of the predetermined event includes, for example, a case where a predetermined time has elapsed, a case where a predetermined time has elapsed, and a case where a write request to the data sources A to C has been received from the application.
[0048]
The transaction management unit 11 receives a data source operation command such as a search command from the generation unit 9c of the object processing unit 9 and an operation command from the write management unit 10, and based on the definition data 14 recorded in the recording device 13b. , Which data source is recorded in which data source, and distributes the data source operation instruction to the data source access units 12a to 12c.
[0049]
When receiving the search result for the search command from the data source access units 12a to 12c, the transaction management unit 11 provides the search result to the generation unit 9c.
[0050]
When each of the data source access units 12a to 12c receives the data source operation command from the transaction management unit 11, the data source access units 12a to 12c read the definition data 14 of the recording device 13b.
[0051]
Each of the data source access units 12a to 12c converts a data source operation instruction into an operation instruction corresponding to the data source A to C corresponding to the data source based on the definition data 14, and converts the converted operation instruction to each data source. Provide to sources AC.
[0052]
In each of the data sources A to C, a process corresponding to the converted operation command is performed, and the result is returned to each of the data source access units 12a to 12c.
[0053]
FIG. 3 is a diagram illustrating an example of the relationship between the data sources A to C and the integrated class.
[0054]
Data source A records "employee number", "name", and "affiliation", and data source B records "employee number", "birth date", and "telephone number". In the data source C, “name”, “hobby”, and “license information” are recorded.
[0055]
In order to integrate the contents of the data sources A to C, an employee class 16 is defined as an integrated class. The attributes of the employee class 16 include “employee number”, “name”, “affiliation”, “employee number”, “birth date”, “telephone number”, “hobby”, “hobby” included in the data sources A to C. License information "is defined.
[0056]
It should be noted that a reference relationship for referring to another class may be defined as an attribute of the integrated class. Further, a function for calculating an attribute value from a value recorded in the data source may be defined as an attribute of the integrated class.
[0057]
The employee object 17 which is an integrated object is generated based on the integrated class.
[0058]
FIG. 4 is a diagram illustrating an example of an integrated class in which a reference relationship between a plurality of integrated classes is defined.
[0059]
As an integrated class, an organization class 18 and an employee class 16 are defined. The organization class 18 refers to the organization class 18. Thereby, the hierarchical relationship of the organization can be represented. Each organization class 18 refers to the employee class 16. Thereby, the employees belonging to each organization can be represented.
[0060]
In this example, 0 (no superior organization) or one organization class generated based on the organization class 18 is defined in the attribute “super organization” of the organization class 18.
[0061]
Further, 0 or more employee classes generated based on the employee class 16 are defined in the attribute “organization member” of the organization class.
[0062]
FIG. 5 is a block diagram showing a first example of the operation concept of the data source integration system 3.
[0063]
FIG. 5 shows an outline of an operation when a search for data not recorded in the recording device 13c is requested. Although FIG. 5 shows a case where a search for the same integrated object is requested from different applications 4a and 4b, the same applies to a case where a search for the same integrated object is requested a plurality of times from the same application.
[0064]
In step A1, the operation content analysis unit 7 of the data source integration system 3 receives a search request for the employee object 17a of the employee number "123" from the application 4a.
[0065]
In step A2, the search unit 9b of the data source integration system 3 searches the recording device 13c for the employee object 17a of the employee number "123".
[0066]
Here, in the example of FIG. 5, it is assumed that the employee object of the employee number “123” has not been recorded in the recording device 13c at this time.
[0067]
In step A3, the generation unit 9c of the data source integration system 3 searches data required for generating the employee object 17a of the employee number "123" for the plurality of data sources A to C based on the employee class, The employee object 17a of the employee number "123" is generated.
[0068]
In step A4, the generation unit 9c of the data source integration system 3 returns the generated employee object 17a of the employee number "123" to the application 4a via the access control unit 8 and the operation content analysis unit 7, and sends the generated employee object 17a to the recording device 13c. Record.
[0069]
In step A5, the operation content analysis unit 7 of the data source integration system 3 receives a search request for the employee object 17a with the employee number "123" from the application 4b.
[0070]
In step A6, the search unit 9b of the data source integration system 3 searches the recording device 13c for the employee object 17a of the employee number "123".
[0071]
At this point, since the employee object 17a with the employee number "123" is recorded in the recording device 13c in step A4, the search unit 9b can retrieve the employee object 17a with the employee number "123" from the recording device 13c.
[0072]
In step A7, the search unit 9b of the data source integration system 3 returns the searched employee object 17a of the employee number "123" to the application 4b.
[0073]
As described above, the search can be performed at high speed by returning the integrated object in the data source integration system 3 to the application 4b without accessing the data sources A to C.
[0074]
FIG. 6 is a block diagram showing a second example of the operation concept of the data source integration system 3.
[0075]
FIG. 6 shows an outline of the operation when a reference relationship between classes is defined in the integrated class.
[0076]
In step B1, the operation content analysis unit 7 of the data source integration system 3 receives from the application 4a a search request for “superordinate organization” in the organization object 19a with the organization name “general affairs section”.
[0077]
Here, in the example of FIG. 6, it is assumed that the organization object 19a of the organization name “General Affairs Division” is recorded in the recording device 13c at this time. Further, it is assumed that “general affairs department” is defined as an upper organization in the organization object 19a of the organization name “general affairs section”.
[0078]
In step B2, the search unit 9b of the data source integration system 3 searches the recording device 13c for the organization object 19a of the organization name "General Affairs Section" and acquires the organization object 19a of the organization name "General Affairs Section".
[0079]
In step B3, the search unit 9b searches for the organization object 19b of the “general affairs department” specified by “superordinate organization” of the organization object 19a of the organization name “general affairs section”.
[0080]
Here, in the example of FIG. 6, it is assumed that the organization object 19b of the organization name “general affairs department” is not recorded in the recording device 13c at this time.
[0081]
In step B4, the generation unit 9c of the data source integration system 3 searches a plurality of data sources A to C, and generates an organization object 19b having an organization name of “general affairs department”.
[0082]
In step B5, the generation unit 9c of the data source integration system 3 returns the generated organization object 19b of the organization name “general affairs department” to the application 4a and records it on the recording device 13c.
[0083]
FIG. 7 is a block diagram showing a third example of the operation concept of the data source integration system 3.
[0084]
FIG. 7 shows an outline of the operation when exclusive control of the operation on the integrated object is performed.
[0085]
The exclusion levels include search prohibition, update prohibition, registration prohibition, and deletion prohibition. Here, a case where an update of the employee object 17a is requested will be described as an example, but the same applies to a case where a search, registration, deletion, or the like of an integrated object is requested.
[0086]
In step C1, the operation content analysis unit 7 of the data source integration system 3 receives a first update request for the employee object 17a with the employee number "123" from the application 4a.
[0087]
In step C2, the exclusive control unit 9g of the data source integration system 3 occupies the employee object 17a of the employee number "123" only for the first update request.
[0088]
In step C3, the updating unit 9d of the data source integration system 3 updates the employee object 17a of the employee number “123” recorded in the recording device 13c according to the first update instruction.
[0089]
Here, in the example of FIG. 7, during the update of the employee object 17a of the employee number "123" based on the first update instruction, a second update request of the employee object 17a of the employee number "123" is transmitted from the application 4b. Suppose.
[0090]
In step C4, the operation content analysis unit 7 of the data source integration system 3 receives a second update request for the employee object 17a with the employee number "123" from the application 4b.
[0091]
In step C5, the exclusive control unit 9g of the data source integration system 3 rejects the second update request in order to occupy the employee object 17a of the employee number "123" for only the first update request.
[0092]
In step C6, the updating unit 9d of the data source integration system 3 provides an error message to the application 4b.
[0093]
Note that the exclusive control unit 9g also locks in units of data operation instructions when receiving a plurality of data operation instructions for the same integrated object from the same application.
[0094]
In addition, operation requests from different integrated objects for data of the same data source are rejected. For example, an integration class is not defined so that the “license” data stored in the data source C can be operated from both the employee object and the qualification object, or data used by the employee object when the employee object is locked. There are also methods such as locking the source data.
[0095]
FIG. 8 is a block diagram showing a fourth example of the operation concept of the data source integration system 3.
[0096]
In FIG. 8, a case will be described as an example where after the registration of the employee object 17a is requested, the contents of the employee object 17a are reflected on the data sources A to C. However, the update and deletion of the employee object 17a are requested. The same applies to the case where
[0097]
In step D1, the operation content analysis unit 7 of the data source integration system 3 receives a registration request for the employee object 17a with the employee number "123" from the application 4a.
[0098]
In step D2, the registration unit 9e of the data source integration system 3 records the employee object 17a of the employee number "123" on the recording device 13a.
[0099]
In step D3, the write management unit 10 of the data source integration system 3 sends a registration request for the employee object 17a with the employee number "123" at a different timing from the registration of the employee object 17a with the recording device 13c. To be reflected in the contents of the data sources A to C.
[0100]
For example, when a write command is received from the application 4a, the write management unit 10 reads the employee object 17a recorded in the recording device 13c via the writing unit 9h of the object processing unit 9, and reads the employee object 17a. May be provided to the data sources A to C via the transaction management unit 11 and the data source access units 12a to 12c to reflect the contents of the data sources A to C to the contents of the data sources A to C. Further, the writing management unit 10 reads out the employee object 17a recorded in the recording device 13c via the writing unit 9h of the object processing unit 9 by a batch process based on time designation, and writes the contents of the employee object 17a to each data. Operation instructions for reflecting the contents of the sources A to C may be provided to the data sources A to C via the transaction management unit 11 and the data source access units 12a to 12c.
[0101]
As described above, by changing the data sources A to C at a different timing from the change (registration, update, deletion) of the recording device 13c, when the number of processes in the data source integration system 3 is small or when the data sources A to C When the number of data operations to the data sources is small, the data operation to the data sources A to C can be performed from the data source integration system 3. Thereby, the apparent processing speed can be improved. Note that the meaning of “a timing different from the data operation instruction” includes a change in the recording device 13c and a change at a different timing.
[0102]
Instead of changing all the data sources A to C at the same timing, the change timing may be changed for each data source.
[0103]
For example, for data sources that are frequently accessed, object changes are reflected in real time, and for data sources that are accessed once a day at a specified time, the changes are reflected once a day in batch processing. For example, by setting the change timing for each data source, useless access to the data source can be reduced.
[0104]
FIG. 9 is a block diagram showing a fifth example of the operation concept of the data source integration system 3.
[0105]
In FIG. 9, a case will be described in which the update processing of the data sources A to C is collectively performed by the transaction management unit 11 and the data source access units 12a to 12c.
[0106]
The recording device 13c of the data source integration system 3 records an employee object 17a with an employee number “123”. The attribute "telephone number" of the employee object 17a having the employee number "123" has an attribute value "123-456-7890", and the attribute "affiliation" has an attribute value "accounting department".
[0107]
In step E1, the operation content analysis unit 7 of the data source integration system 3 receives an update request for the employee object 17a with the employee number "123" from the application 4a.
[0108]
Here, it is assumed that the update request is a request for updating the telephone number of the employee number “123” to “111-222-3456” and updating the affiliation of the employee number “123” to “General Affairs Department”.
[0109]
In step E2, the update unit of the data source integration system 3 reads the employee object 17a of the employee number "123" from the recording device 13c, updates the employee object 17a to the content specified by the update request, and updates the updated employee number "123". Is recorded in the recording device 13c.
[0110]
In step E3, the writing management unit 10 of the data source integration system 3 acquires the employee object 17a via the writing unit 9h of the object processing unit 9 at a different timing from the update of the integrated object in the recording device 13c. The operation content is provided to the transaction management unit 11.
[0111]
In step E4, the transaction management unit 11 of the data source integration system 3 provides a data source operation command to each of the data source access units 12a to 12c according to the operation content and the definition data 14.
[0112]
In step E5, each of the data source access units 12a to 12c of the data source integration system 3 converts the data source operation instruction based on the definition data 14, and converts the converted data source operation instruction to the data source A, B.
[0113]
As a result of the conversion, an operation command for converting the affiliation of the employee number "123" in the data source A to the "general affairs department" is obtained by the data source access unit 12a, and the telephone number of the employee number "123" is obtained by the data source access unit 12b. An operation command for converting the number into “111-222-3456” is obtained.
[0114]
FIG. 10 is a flowchart illustrating an example of processing of the data source integration system 3. FIG. 10 illustrates a case where a search is requested.
[0115]
In step F1, the operation content analysis unit 7 receives a data operation command from a command source and analyzes the operation content.
[0116]
In step F2, the access control unit 8 refers to the access control data 15 and determines whether to restrict the operation requested by the command source. If the operation is to be restricted, the process ends.
[0117]
If the operation is permitted, in step F3, the search unit 9b of the object processing unit 9 searches the recording device 13c for an integrated object to be searched.
[0118]
In step F4, the search unit 9b of the object processing unit 9 determines whether the integrated object to be searched has been searched. If it is determined that the search has been performed, the search unit 9b provides the searched integrated object to the request source, and step F8 is executed.
[0119]
If it is determined that the search is not performed, in step F5, the definition data reading unit 9a reads the definition data 14, and in step F6, the generation unit 9c transmits the data sources A to D via the data source access units 12a to 12c. Read the contents of C.
[0120]
In step F7, the generation unit 9c determines, based on the definition data 14 read by the definition data reading unit 9a and the contents of the data sources A to C read by the transaction management unit 11 and the data source access units 12a to 12c. An integrated object to be searched is generated, recorded in the recording device 13c, and provided to the request source.
[0121]
In FIG. 10 described above, when another operation such as update, registration, or deletion is requested instead of the search, update processing, registration processing, and deletion processing are performed in place of the processing in steps F3 to F7, respectively. Is executed.
[0122]
For example, when the operation content is an update of the integrated object, the update unit 9d updates the integrated object to be updated recorded in the recording device 13c.
[0123]
When the operation content is registration of an integrated object, the registration unit 9e registers the integrated object to be registered in the recording device 13c.
[0124]
When the operation content is the deletion of the integrated object, the deletion unit 9f deletes the data to be deleted from the integrated object of the recording device 13c.
[0125]
In the process of registration, update, and deletion, in step F8, the write management unit 10 determines whether to write the changed content of the recording device 13c to the data sources A to C.
[0126]
When writing to the data sources A to C, in step F9, the write management unit 10 changes the contents of the data sources A to C via the transaction management unit 11 and the data source access units 12a to 12c.
[0127]
In the present embodiment described above, an integrated object is generated by integrating the contents of a plurality of different types of data sources A to C. Thereby, the following effects can be obtained.
[0128]
First, by performing various data operations on the integrated object, there is no need to be aware of which data source A to C the data is actually stored in, and data can be managed efficiently.
[0129]
Secondly, the difference between the types of the data sources A to C can be absorbed, the data can be operated without being conscious of the types of the data sources A to C, and the format of the data operation command received from the command source can be unified.
[0130]
Third, a plurality of transactions for a plurality of data sources A to C can be managed in a unified manner.
[0131]
Fourth, access control for a plurality of data sources A to C can be unified.
[0132]
Fifth, since an integrated object obtained by integrating the contents of a plurality of data sources A to C is held in the data source integration system 3, the number of accesses to the data sources A to C can be reduced, and the data operation can be performed at high speed. And efficiency.
[0133]
Sixth, it is possible to control the timing of reflecting the contents of the integrated object to the data sources A to C. Then, by accessing the data sources A to C at a timing when the number of accesses to the data sources A to C is small or at a timing when the data source integration system 3 can perform high-speed processing, data operation can be speeded up and data can be efficiently saved. Can manage.
[0134]
Seventh, when a reference relationship between classes is defined in the integrated class, retrieval of the integrated object becomes easy, and high-speed and efficient data manipulation can be performed.
[0135]
(Second embodiment)
In the present embodiment, a data source integration system having a compiler type processing mode in which the contents of the definition data 14 are pre-installed in a data source integration program will be described.
[0136]
FIG. 11 is a block diagram illustrating an example of a configuration of the data source integration system according to the present embodiment. In FIG. 11, the same parts as those in FIG. 1 are denoted by the same reference numerals, and the description thereof will be omitted. Here, only the different parts will be described in detail.
[0137]
The definition data 14 is incorporated in the data source integration program 6b recorded on the recording medium.
[0138]
The data source integration system 20 includes a compiler 21 (processing program creation unit).
[0139]
The data source integration program 6b is compiled by the compiler 21 and operates on the data source integration system 20.
[0140]
In the present embodiment, since the definition data 14 is incorporated in the data source integration program 6b in advance, the recording device 13b in FIG. 1 and the definition data reading unit 9a in FIG. 2 are omitted.
[0141]
For example, in the first embodiment, the data source access units 12a to 12c refer to the definition data 14 for information such as a host name and a port number necessary for connecting to the data sources A to C. In the form, such information is written in the program.
[0142]
Therefore, the object processing unit 22, the transaction management unit 26, and the data source access units 23a to 23c do not need to separately access the definition data 14.
[0143]
FIG. 12 is a flowchart illustrating an example of processing of the data source integration system 20.
[0144]
In step G1, the compiler 21 of the data source integration system 20 compiles the data source integration program 6b.
[0145]
Subsequent steps G2 to G9 are the same as steps F1 to F4 and F6 to F9 in FIG. 10 described above, and step F5 is omitted.
[0146]
Since the data source integration system 20 does not need to refer to the recording device to obtain the contents of the definition data 14, the processing can be speeded up.
[0147]
In each of the above embodiments, each component of the data source integration systems 3 and 20 may be realized by hardware in a portion realized by a program.
[0148]
The components included in the data source integration systems 3 and 20 according to the above embodiments may be changed in arrangement as long as the same operation can be realized, and the components may be freely combined. Alternatively, each component may be freely divided.
[0149]
In addition, the data source integration systems 3 and 20 according to each of the above-described embodiments are configured by a plurality of computers, and the respective data source integration programs 6a and 6b are distributed and arranged in the plurality of computers, and perform processing while cooperating with each other. It may be executed.
[0150]
For example, an internal memory, a hard disk, or the like is applied to each of the recording devices. Each of the above recording devices may be an element constituting a database.
[0151]
As the recording medium 6 for recording the data source integration programs 6a and 6b and the recording devices 27A to 27C for recording the data sources A to C, for example, a magnetic disk (flexible disk, hard disk, etc.), an optical disk (CD-ROM, DVD, etc.) ), Semiconductor memory and the like. Further, the data source integration programs 6a and 6b can be transmitted to a communication medium and applied to a computer. Also in this case, the computer realizes the above functions by reading the program and controlling the operation by the program.
[0152]
【Example】
Hereinafter, a specific example of the data source integration system 3 according to the first embodiment will be described. The same applies to the data source integration system 20 according to the second embodiment.
[0153]
(First embodiment)
In the present embodiment, the type of the data source A is LDAP and the type of the data source B is RDB, and the data source integration system 3 integrates the two data sources A and B.
[0154]
First, the data source A will be described.
[0155]
FIG. 13 is a block diagram illustrating an example of a tree configuration of the data source A.
[0156]
The data source A includes four types of entries: a country entry, a company entry, an organization entry, and an employee entry. Each entry has a hierarchical relationship from the top, in the order of country entry, company entry, organization entry, and employee entry.
[0157]
In the example of FIG. 13, a company entry e2 is located below the country entry e1. Below the company entry e2 are organization entries e3 and e4. Below the organization entry e3 are employee entries e5 to e7. An employee entry e8 is located below the organization entry e4.
[0158]
Table 1 is an example of the country entry e1.
[0159]
[Table 1]

[0160]
Table 2 is an example of the company entry e2.
[0161]
[Table 2]

[0162]
Table 3 is an example of the organization entry e3.
[0163]
[Table 3]

[0164]
Table 4 is an example of the organization entry e4.
[0165]
[Table 4]

[0166]
Table 5 is an example of the employee entry e5.
[0167]
[Table 5]

[0168]
Table 6 is an example of the employee entry e6.
[0169]
[Table 6]

[0170]
Table 7 is an example of the employee entry e7.
[0171]
[Table 7]

[0172]
Table 8 is an example of the employee entry e8.
[0173]
[Table 8]

Next, the data source B will be described.
[0174]
It is assumed that this data source B manages three types of tables: a company table t1, an organization table t2, and an employee table t3.
[0175]
Table 9 is an example of the company table t1.
[0176]
[Table 9]

[0177]
Table 10 is an example of the organization table t2.
[0178]
[Table 10]

[0179]
Table 11 is an example of the employee table t3.
[0180]
[Table 11]

[0181]
Next, the definition data 14 will be described.
[0182]
The definition data 14 includes data about the data source itself such as data source connection definition data 14a, data source access method definition data 14b, data source definition data 14c and 14d for each data source A and B, and mapping definition data. 14e.
[0183]
Table 12 shows an example of the data source connection definition data 14a.
[0184]
[Table 12]

The data source connection definition data 14a defines information necessary for connecting to each of the data sources A and B, such as a data source name, a data source type, a host name, a port, a Bind User, and a Password.
[0185]
Table 13 shows an example of the data source access method definition data 14b.
[0186]
[Table 13]

Commands for searching, registering, updating, and deleting the data sources A and B are defined in the data source access method definition data 14b.
[0187]
The data source definition data 14c and 14d define the content of data recorded in each of the data sources A and B. For example, in the data source definition data 14c and 14d, data names (for example, LDAP attributes and RDB column names) of data recorded in the corresponding data sources A and B are defined.
[0188]
In this embodiment, since there are two data sources A and B of LDAP and RDB, the definition data 14 has two data source definition data 14c and 14d.
[0189]
Table 14 shows an example of the data source definition data 14c for the data source A.
[0190]
[Table 14]

In the data source definition data 14c, the object class name, attribute name, type, required, and primary key of the data source A are defined.
[0191]
On the other hand, Table 15 shows an example of the data source definition data 14d relating to the data source B.
[0192]
[Table 15]

In the data source definition data 14d, the table name, column name, type, required, and primary key of the data source B are defined.
[0193]
Table 16 shows an example of the mapping definition data 14e.
[0194]
[Table 16]

The mapping definition data 14e defines the definition of the integration class and the attribute of the integration class, and the mapping relationship between the integration class, the attribute of the integration class, and the data defined by the data source definition data 14c and 14d. I have.
[0195]
As the attributes of the integrated class, three types of data recorded in one of the data sources A and B, a class having a reference relationship, and a function are used, and the definitions are different.
[0196]
First, a case where the type of the attribute of the integration class is data in the mapping definition data 14e will be described.
[0197]
When the type of the attribute of the integration class is data and the data which is the attribute value of the attribute of the integration class is stored in the data source A of the LDAP, the mapping definition data 14e includes the attribute name, type, and mandatory , A primary key attribute, and a data source name, a class, and an attribute name in which data serving as an attribute value in the integrated class are stored and defined.
[0198]
On the other hand, when the type of the attribute of the integration class is data and the data that is the attribute value of the attribute of the integration class is stored in the data source B of the RDB, the mapping definition data 14e includes the attribute name and type of the integration class. An essential attribute, an attribute serving as a primary key, and a data source name, a table name, and a column name storing data serving as attribute values in the integration class are defined.
[0199]
In the mapping definition data 14e, attributes having the same value between different data sources A and B are defined as a common key. The attribute name of the data source A and the column name of the data source B are associated with the attribute name of the integrated class defined as the common key.
[0200]
For example, when the value of the column of the data source B is acquired using the value of the attribute of the data source A as a key, the value of the attribute of the data source A marked as a common key is It is used when a value of a column in the data source B is acquired by substituting the value as a column value of the related data source B and using the substituted value as a key.
[0201]
For example, in SyainClass, the common key is “SYAIN_NUM”, the data source A is associated with “uid”, and the data source B is associated with “NUMBER”. Here, when the attribute value of “TEL” in the data source B is acquired by using the attribute value of “cn” of the data source A as a key, the data source A is first searched by using “cn” as a key, thereby The attribute value of the key “uid” can be obtained. Subsequently, by searching the data source B using the obtained attribute value of “uid” as the attribute value of “NUMBER”, the target attribute value of “TEL” can be obtained.
[0202]
Read and Write in the mapping definition data 14e are set to the attribute values or column values of any of the data sources A and B when the Read and Write operations on the attribute values of the integrated object are performed in the data source integration system 3. It is defined whether a Read or Write operation is performed.
[0203]
For example, when acquiring the attribute value of “SYAIN_NUM” of SyainClass which is a common key, it is not possible to specify which one of “uid” of data source A and “NUMBER” of data source B should be referred to. It is determined from Read whether to refer to the value from. In the example of Table 16, reference is made from “uid”.
[0204]
Next, a case where the type of the attribute of the integration class is a reference relation in the mapping definition data 14e will be described.
[0205]
If the type of the attribute of the integrated class is a reference relationship, the attribute name, reference source corresponding attribute name, reference destination class name, reference destination corresponding attribute name, and reference correspondence number of this integrated class are defined. The acquisition operation for the attribute of the reference relationship is converted into an operation of acquiring the integrated object of the reference destination class having the value of the reference source correspondence attribute in the reference destination correspondence attribute of the reference destination class.
[0206]
For example, in SyainClass, when an acquisition operation for “SYOZOKU_SOSIKI”, which is the attribute of the reference relationship, is requested, a SosikiClass in which the value of “SYOZOKU_CODE” of SyainClass is included in “SOSIKI_CODE” of SoshikiClass.
[0207]
Next, a case where the type of the attribute of the integration class is a function in the mapping definition data 14e will be described.
[0208]
When the type of the attribute of the integrated class is a function, the attribute name, type, and processing content of the integrated class are defined. For example, when "age" is considered as the attribute name of the function, the function [current date / birth date / birth date] is defined as the processing content.
[0209]
Next, the access control data 15 will be described.
[0210]
The access control data 15 includes role definition data 15a and access control definition data 15b and 15c.
[0211]
Table 17 shows an example of the role definition data 15a.
[0212]
[Table 17]

In the role definition data 15a, a role in which a plurality of authorities are put together and an application associated with the role are defined. In this example, the authority for the application 4a is grouped into a role “ROLE01”, and the authority for the application 4b is grouped into a role “ROLE02”.
[0213]
Table 18 shows an example of the access control definition data 15b for the role “ROLE01”.
[0214]
[Table 18]

[0215]
Table 19 shows an example of the access control definition data 15c for the role “ROLE02”.
[0216]
[Table 19]

In the access control definition data 15b and 15c, the contents of each role are defined, and the authority for the operation (search, registration, update, and delete) for the class and the operation (Read, Write) for the attribute is defined.
[0219]
FIG. 14 is a block diagram illustrating a first example of a processing flow of the data source integration system 3 in the present embodiment.
[0218]
In FIG. 14, the application 4a performs an operation of searching for the employee object 24 with the name “TTT”.
[0219]
As a precondition, it is assumed that the employee object 24 having the name “TTT” to be operated is not recorded in the recording device 13c.
[0220]
In step H1, the operation content analysis unit 7 of the data source integration system 3 receives a data operation instruction “SELECT * FROM SyainClass WHERE NAME = TTT” representing a search request from the application 4a, analyzes the operation content, and accesses the operation content. Provided to the control unit 8. Specifically, first, information is extracted that is “request from application 4a”, the operation is “search”, and the class of the operation target object is “SyainClass”. Further, information that the key for specifying the operation target object is “NAME = TTT” and the attribute of the operation target is “all attributes” (“*” part of the operation command) is extracted. Is provided to the access control unit 8.
[0221]
In step H2, the access control unit 8 acquires the authority information of the application 4a by referring to the access control data 15 illustrated in Tables 17 to 19 above.
[0222]
Specifically, the access control unit 8 extracts that the authority information of the application 4a corresponds to ROLE01 based on the role definition data 15a in Table 17 above. Then, since the class of the operation target object is “SyainClass”, the authority information for “SyainClass” is extracted based on the access control definition data 15b of “ROLE01” in Table 18 above. In the example of Table 18, “SyainClass” can be searched, and it can be recognized that the Read authority has been given to attributes other than the “BIRTHDATE”, “KEITAI”, and “AGE” attributes. Therefore, the access control unit 8 sends the information of “search” for “all attributes except BIRTHDATE, KEITAI, and AGE” of the object of “NAME = TTT” defined by “SyainClass” to the object processing unit 9. Output to the search unit 9b.
[0223]
In step H3, upon receiving the information from the access control unit 8, the search unit 9b of the object processing unit 9 searches the recording device 13c for the employee object 24 of "NAME = TTT" to be searched.
[0224]
As a result of the search, since the employee object 24 to be searched does not exist in the recording device 13c, in step H4, the generation unit 9c of the object processing unit 9 checks the object processing unit 9 to obtain information on the data sources A and B. The data source definition data 14c and 14d shown in Tables 14 and 15 included in the definition data 14 are referred to through the definition data reading unit 9a. Further, the generation unit 9c refers to the mapping definition data 14e shown in Table 16 above, which shows the mapping relationship between the attributes of the integrated class and the data sources A and B.
[0225]
In the mapping definition data 14e, the attribute "NAME" of the integrated class "SyainClass" is associated with the attribute "cn" of the object class "inetOrgPerson" of the data source A. Therefore, if the search key “NAME = TTT” for the integrated class “SyainClass” is searched in the data source A using the search key “cn = TTT” for the data source A, the name “TTT” stored in the data source A is obtained. Data can be obtained. In addition, in order to obtain the data of the name “TTT” stored in the data source B, the attribute having the same value in the data source A and the data source B is referred to by referring to the common key of the mapping definition data 14e in Table 16 above. Find out. The mapping definition data 14e describes that the attribute "uid" of the object class "inetOrgPerson" of the data source A has the same value as the column name "NUMBER" of the table "SYAIN" of the data source B. Therefore, the value of “uid” obtained as a result of the search of the data source A is used as the value of the column name “NUMBER” of the table “SYAIN” of the data source B, and the search key “NUMBER = <uid attribute value” for the data source B is used. If ">" is created and searched, data with the name "TTT" stored in the data source B can be obtained.
[0226]
Therefore, in step H5, the generation unit 9c provides the transaction management unit 11 with a search request using “cn = TTT” as a key and a search request using “NUMBER = <attribute value of uid>” as a key.
[0227]
In step H6, the transaction management unit 11 recognizes that the “cn” attribute is stored in the data source A by referring to the mapping definition data 14e, and issues a search request using “cn = TTT” as a key. The data is provided to the data source access unit 12a corresponding to the data source A.
[0228]
In step H7, the data source access unit 12a refers to the data source connection definition data 14a in Table 12 above, acquires information for connecting to the data source A, and then acquires the data source access method definition data 14b in Table 13 above. , A command for performing a search using “cn = TTT” as a key is created from the data source A.
[0229]
Specifically, the host is connected to the 389 port having the host name of ldaphost by cn = Directory Manager, and the search is performed using the command “ldapsearch cn = TTT“ objectclass = inetOrgPerson ””.
[0230]
As a result of the search, the attribute values “100001” “TTT@TTT.co.jp” of the “uid”, “mail” and “ou” attributes of the data source A associated with the “SYAIN_NUM”, “MAIL_ADDRESS”, and “SYOZOKU_CODE” attributes of the integrated class "201" and provide it to the transaction management unit 11.
[0231]
At this time, the attribute value of “mobile” corresponding to “KEITAI” of the integrated class is not acquired because there is no access right. Further, an attribute whose attribute type is a reference relation is not acquired unless there is a direct acquisition operation on the attribute.
[0232]
Subsequently, in step H8, the transaction management unit 11 recognizes that “NUMBER” is stored in the data source B by referring to the mapping definition data 14e, and obtains “NUMBER” obtained by searching the data source A. With the value “100001” of “uid” as the value of “NUMBER”, a search request using “NUMBER = 100001” as a key is provided to the data source access unit 12b corresponding to the data source B.
[0233]
In step H9, the data source access unit 12b refers to the data source connection definition data 14a in Table 12 above, acquires information for connecting to the data source B, and then acquires the data source access method definition data 14b in Table 13 above. To create a command for performing a search using “NUMBER = 100001” as a key.
[0234]
More specifically, the host name is connected to port 1521 of rdbhost by Admin, and a search is performed using “SELECT * FROM SYNINE WHERE NUMBER = 100001”.
[0235]
As a result of the search, the transaction management unit acquires the attribute values “011-222-3456” and “S” of the “TEL” and “SYOKUI” attributes of the data source B associated with the “TELEPHONE” and “YAKUSYOKU” attributes of the integrated class, and 11 to provide.
[0236]
At this time, the attribute value of "BIRTH" corresponding to the attribute of the integrated class "BIRTHDATE" is not acquired because there is no access right.
[0237]
In step H10, the transaction management unit 11 provides the search results of the data sources A and B to the generation unit 9c.
[0238]
In the above processing, the order of the data search for the data source A and the data search for the data source B depends on which data source stores the attribute used as the search key for the integrated class. In this embodiment, since the “NAME” attribute of the integrated class is related to the “cn” attribute of the data source A, the data source A is searched. If the search can be performed in parallel, the search may be performed in parallel.
[0239]
In step H11, the generation unit 9c generates the employee object 24 having the name “TTT” by integrating the data of the data source A and the data source B.
[0240]
In step H12, the generation unit 9c records the generated employee object having the name “TTT” in the recording device 13c and provides the employee object to the application 4a via the access control unit 8 and the operation content analysis unit 7.
[0241]
FIG. 15 is a block diagram illustrating a second example of the processing flow of the data source integration system according to the present embodiment. In FIG. 15, similarly to FIG. 14, the application 4a performs an operation of searching for the employee object 24 with the name “TTT”. In FIG. 15, it is assumed that the employee object 24 to be operated is recorded on the recording device 13c.
[0242]
Steps I1 and I2 are the same as steps H1 and H2 in FIG.
[0243]
In step I3, the search unit 9b of the object processing unit 9 searches the recording device 13c for the employee object 24 of "NAME = TTT" to be searched.
[0244]
As a result of the search, the employee object 24 to be searched exists in the recording device 13c. Therefore, in step I4, the search unit 9b compares the searched employee object 24 with the name "TTT" with the access control unit 8, the operation content analysis unit 7 To the application 4a via
[0245]
As described above, by recording the integrated object reflecting and integrating the contents of the different types of data sources in the recording device 13c of the data source integration system 3, even if a data search is requested, the data source can be changed. Access may not be required. This speeds up the data search process.
[0246]
Even if the same search request is made a plurality of times from different applications, an integrated object is created and recorded at the first search request, so it is necessary to actually access the data source from the second time. Processing speed.
[0247]
(Second embodiment)
In the present embodiment, under the same conditions as those in the first embodiment, the application 4b determines the attribute value of the attribute “telephone number” and the attribute “YAKUSYOKU” of the employee object 24 with the employee number “100001”. The operation for updating the attribute values of “011-222-7890” and “SS” respectively will be described.
[0248]
In the present embodiment, it is assumed that the employee object 24 to be operated is recorded in the recording device 13c of the data source integration system 3, and the write timing to the data source is a write request indicating that the application writes to the data source. And when it is accepted.
[0249]
FIG. 16 is a block diagram illustrating an example of a processing flow of the data source integration system 3 in the present embodiment.
[0250]
In step J1, the operation content analysis unit 7 of the data source integration system 3 receives the data operation instruction “UPDATE SineClass SET TELEPHONE = 011-222-7890, YAKUSYOKU = SS WHERE SYAIN_NUM = 100001” representing the update request from the application 4b. The contents of the operation are analyzed, and the contents of the operation are provided to the access control unit 8. Specifically, it extracts information indicating that the request is “request from the application 4b”, the operation is “update”, and the class of the operation target object is “SyainClass”. Further, the information for identifying that the key for specifying the operation target object is “SYAIN_NUM = 100001” and the update content is “TELEPHONE = 011-222-7890, YAKUSYOKU = SS” is extracted, and the information is accessed. Provided to the control unit 8.
[0251]
In step J2, the access control unit 8 acquires the authority information of the application 4b with reference to the access control data 15 exemplified in the above Tables 17 to 19.
[0252]
Specifically, the access control unit 8 extracts that the authority information of the application 4b corresponds to ROLE02 based on the role definition data 15a in Table 17 above. Then, since the class of the operation target object is “SyainClass”, the authority information for “SyainClass” is extracted based on the access control definition data 15c of ROLE02 in Table 19 above. In the example of Table 19, search, registration, update, and deletion of “SyainClass” can be performed, and it can be recognized that Read and Write authority is given to all attributes. Therefore, the access control unit 8 updates the attribute values of the “TELEPHONE” and “YAKUSYOKU” attributes of the object “SYAIN_NUM = 100001” defined by “SyainClass” to “011-222-7890” and “SS”. Is output to the updating unit 9d of the object processing unit 9.
[0253]
In step J3, when the update unit 9d of the object processing unit 9 receives the information from the access control unit, the update unit 9d searches the recording device 13c for the employee object 24 of "SYAIN_NUM = 100001" to be updated.
[0254]
As a result of the search, since the employee object 24 to be updated exists in the recording device 13c, in step J4, the updating unit 9d updates the attribute value of the attribute “TELEPHONE” to “011-222-7890”, and updates the attribute “YAKUSYOKU”. Is updated to “SS”.
[0255]
At this time, in step J5, the exclusive control unit 9g of the object processing unit 9 locks the employee object 24 to be updated and receives another data operation instruction (for example, an update request from another application). Refuse other data manipulation instructions.
[0256]
In step J6, after the update of the employee object 24 is completed, the update unit 9d provides an update completion message to the application 4b via the access control unit 8 and the operation content analysis unit 7.
[0257]
Here, it is assumed that the application 4b has provided the data source integration system 3 with a write command to reflect the contents of the employee object 24 to the data source.
[0258]
In step J7, the operation content analysis unit 7 receives the write command from the application 4b, and provides the write control unit 10 with the access control unit 8 confirming the access right.
[0259]
In step J8, when receiving the write command, the write management unit 10 acquires the employee object 24 via the write unit 9h of the object processing unit 9, and updates the data source according to the contents of the employee object 24. The transaction management unit 11 is provided with a data source operation instruction for performing the operation.
[0260]
In step J9, the transaction management unit 11 converts the update request for the employee object 24 into an update request for the data source.
[0261]
Specifically, the "TELEPHONE" and "YAKUSYOKU" attributes of the employee object 24 to be updated are stored in the data source B with reference to the mapping definition data 14e in the above Table 16, and the "TELIN" in the "SYAIN" table is stored. Recognizing that it is associated with the "SYOKUI" attribute, it issues an update request to the data source access unit 12b corresponding to the data source B.
[0262]
In step J10, the data source access unit 12b accesses the data source B based on the data source connection definition data 14a in Table 12, and accesses the data source B based on the data source access method definition data 14b in Table 13 above. An update request for the data source B using the update command “UPDATE” is created, and the data source B is updated.
[0263]
Specifically, the host name is connected to the 1521 port having the host name of rdbhost by Admin, and the update is performed using “UPDATE SYAIN SET TEL = 011-222-7890, SYOKUI = SS WHERE SYAIN_NUM = 100001”.
[0264]
In the present embodiment, writing to the data source is performed according to a writing request from the application. However, writing to the data source is performed by batch processing at each writing timing to a predetermined data source, for example, at a specified time. May be performed.
[0265]
(Third embodiment)
In the present embodiment, the employee object of the employee belonging to the organization with the organization code "201" is acquired by the operation from the application 4b, and the telephone number included in the acquired employee object is updated.
[0266]
In this embodiment, it is assumed that the organization object and the employee object to be operated are not recorded in the recording device 13c.
[0267]
In the present embodiment, the application 4b refers to the organization object 25 of the organization code “201” in the first stage under the same conditions as the first embodiment, and to the referenced organization object 25 in the second stage. The employee objects 24a to 24c of the belonging employee are searched, and in the third stage, the telephone numbers of the searched employee objects 24a to 24c are updated to "011-555-5555".
[0268]
FIG. 17 is a block diagram illustrating an example of a first-stage processing flow of the data source integration system 3 in the present embodiment. FIG. 17 shows the processing up to the search for the organization object 25.
[0269]
In step K1, the operation content analysis unit 7 of the data source integration system 3 receives the data operation instruction “SELECT * FROM SoshikiClass WHERE SOSIKI_CODE = 201” representing a search request for the organization object 25 of the organization code “201” from the application 4b. The contents of the operation are analyzed, and the contents of the operation are provided to the access control unit 8. Specifically, it extracts “information from the application 4b”, extracts information indicating that the operation is “search”, and the class of the operation target object is “SosikiClass”. Further, a key for specifying the operation target object is “SOSIKI_CODE = 201”, and information indicating that the attribute of the operation target is “all attributes” (“*” part of the operation instruction) is extracted. Is provided to the access control unit 8.
[0270]
In step K2, the access control unit 8 refers to the role definition data 15a in Table 17 and the access control definition data 15c in Table 19 to acquire the authority information of the application 4b.
[0271]
Specifically, the access control unit 8 extracts that the authority information of the application 4b corresponds to ROLE02 based on the role definition data 15a in Table 17 above. Then, since the class of the operation target object is “SosikiClass”, the authority information for “SosikiClass” is extracted based on the access control definition data 15b of ROLE02 in Table 19 above. In the example of Table 19, "SosikiClass" can be searched, registered, updated, and deleted, and it can be recognized that Read and Write authority is given to all attributes. Therefore, the access control unit 8 outputs to the search unit 9b of the object processing unit 9 information that is defined as “SosikiClass” and that is “search” for “all attributes” of the object of “SOSIKI_CODE = 201”.
[0272]
In step K3, the search unit 9b of the object processing unit 9 searches the recording device 13c for the organization object 25 of “SOSIKI_CODE = 201” to be searched.
[0273]
As a result of the search, since the organization object 25 to be searched does not exist in the recording device 13c, in step K4, the generation unit 9c of the object processing unit 9 checks the object processing unit 9 to obtain information on the data sources A and B. The data source definition data 14c and 14d shown in Tables 14 and 15 included in the definition data 14 are referred to through the definition data reading unit 9a. Further, the generation unit 9c refers to the mapping definition data 14e shown in Table 16 above, which shows the mapping relationship between the attributes of the integrated class and the data sources A and B.
[0274]
In the mapping definition data 14e, the attribute "SOSIKI_CODE" of the integrated class "SosikiClass" is related to the attribute "soshikiCode" of the object class "ldapSosiki" of the data source A and the column name "S_CODE" of the table "SOSIKI" of the data source B. Is attached. Therefore, the search key “SOSIKI_CODE = 201” for the integration class “SosikiClass” is searched in the data source A as the search key “soshikiCode = 201” for the data source A, and the search key “S_CODE = 201” for the data source B is searched. By searching the data source B, the data of the target organization object 25 can be obtained.
[0275]
Therefore, the generation unit 9c provides the transaction management unit 11 with a search request using “soshikiCode = 201” as a key and a search request using “S_CODE = 201” as a key in step K5.
[0276]
In steps K6a and K6b, the transaction management unit 11 recognizes that “soshikiCode” is stored in the data source A and “S_CODE” is stored in the data source B by referring to the mapping definition data 14e. A search request using “soshikiCode = 201” as a key is provided to the data source access unit 12a, and a search request using “S_CODE = 201” as a key is provided to 12b.
[0277]
In step K7, the data source access unit 12a refers to the data source connection definition data 14a in Table 12 above, acquires information for connecting to the data source A, and then acquires the data source access method definition data 14b in Table 13 above. To create a command for performing a search from the data source A using “soshikiCode = 201” as a key.
[0278]
Specifically, the host is connected to the 389 port having the host name of ldaphost by cn = Directory Manager, and the search is performed using the command “ldsearchsearch soikicode = 201“ objectclass = ldapSoshiki ””.
[0279]
As a result of the search, the attribute values "somu" and "-(no upper organization)" of the "ou" and "jyoiSoshikiCode" attributes of the data source A associated with the "SOSIKIMEI" and "JYOI_SOSIKI_CODE" attributes of the integrated class are acquired, and the transaction management is performed. Provided to the section 11.
[0280]
Also, in step K8, the data source access unit 12b refers to the data source connection definition data 14a in Table 12 above, acquires information for connecting to the data source B, and then acquires the data source access method definition in Table 13 above. With reference to the data 14b, a command for performing a search from the data source B using “S_CODE = 201” as a key is created.
[0281]
Specifically, the host name is connected to the 1521 port having the host name rdbhost by Admin, and the search is performed using the command “SELECT * FROM SOSIKI WHERE S_CODE = 201”.
[0282]
As a result of the search, the attribute value “012-345-1111” of the “TEL” attribute of the data source B associated with the “SOSIKI_TEL” attribute of the integrated class is acquired and provided to the transaction management unit 11.
[0283]
In the above process, the data search for the data source A and the data search for the data source B may be performed in parallel.
[0284]
In step K9, the transaction management unit 11 provides the search results of the data sources A and B to the generation unit 9c.
[0285]
In the above process, the attribute whose attribute type is the reference relationship is acquired when an acquisition operation is performed on the attribute.
[0286]
In Step K10, the generation unit 9c generates the organization object 25 of the organization code “201” obtained by integrating the data of the data source A and the data source B.
[0287]
In step K11, the generation unit 9c records the organization object 25 of the organization code "201" in the recording device 13c, and provides the organization object 25 to the application 4b via the access control unit 8 and the operation content analysis unit 7.
[0288]
FIG. 18 is a block diagram illustrating an example of a processing flow of the second stage of the data source integration system 3 in the present embodiment. FIG. 18 shows the processing up to the search for the employee objects 24a to 24c of the employees belonging to the organization object 25 of the organization code "201".
[0289]
In step L1, the operation content analysis unit 7 of the data source integration system 3 receives a data operation instruction “GET SOSIKI_MEMBER” representing a search request for the employee objects 24a to 24c of the employees belonging to the organization with the organization code “201” from the application 4b. , Analyzing the operation contents and providing the operation contents to the access control unit 8. Specifically, it extracts information indicating that the request is “request from the application 4b”, the operation is “search”, and the attribute of the operation target is “SOSIKI_MEMBER”, and the information is provided to the access control unit 8. I do. At this time, the information on the operation target object is specified as the organization object of the organization code “201” by the search for the organization object in the first stage.
[0290]
In step L2, the access control unit 8 acquires the authority information of the application 4b with reference to the access control data 15 illustrated in Tables 17 to 19 above. Specifically, the access control unit 8 extracts that the authority information of the application 4b corresponds to ROLE02 based on the role definition data 15a in Table 17 above. Then, since the class of the operation target object is “SosikiClass”, the authority information for the SoshikiClass is extracted based on the access control definition data 15c of ROLE02 in Table 19 above. In the example of Table 19, "SosikiClass" can be searched, registered, updated, and deleted, and it can be recognized that Read and Write permissions have been granted to all attributes. Therefore, the access control unit 8 outputs to the search unit 9b of the object processing unit 9 information that is defined as “SosikiClass” and is “search” for “SOSIKI_MEMBER” of the object with the organization code “201”.
[0291]
In step L3, the search unit 9b of the object processing unit 9 refers to the mapping definition data 14e, and the type of the attribute “SOSIKI_MEMBER” of the organization object 25 of the organization code “201” searched earlier has a reference relationship. It is recognizable.
[0292]
In step L4, in the case of the attribute of the reference relationship, the search unit 9b searches the object of the reference destination class by putting the value of the reference source corresponding attribute in the reference destination corresponding attribute of the reference class.
[0293]
Here, the search unit 9b refers to the definition data 14, converts the search request of "SOSIKI_MEMBER" into a search request of the employee objects 24a to 24c of the affiliation code "201", and performs a search. In this example, the employee objects 24a to 24c whose attribute value of the "SYOZOKU_CODE" attribute of "SyainClass" is "201" are searched.
[0294]
As a result of the search, since the employee objects 24a to 24c are not recorded in the recording device 13c, in step L5, the generation unit 9c of the object processing unit 9 sets the data shown in Tables 14 and 15 included in the definition data 14 The source definition data 14c and 14d and the mapping definition data 14e are referred to.
[0295]
In the mapping definition data 14e, the attribute "SYOZOKU_CODE" of the integrated class "SyainClass" is related to the attribute "ou" of the object class "inetOrgPerson" of the data source A. Therefore, if data in the data source A is searched using the search key “SYOZOKU_CODE = 201” for the integrated class “SyainClass” and the search key “ou = 201” for the data source A, the affiliation code “ 201 "can be obtained. Further, in order to acquire the data of the belonging code “201” stored in the data source B, the attribute having the same value in the data source A and the data source B is referred to by referring to the common key of the mapping definition data 14e in Table 16 above. Find out. In the mapping definition data 14e, the attribute "uid" of the object class "inetOrgPerson" of the data source A and the column name "NUMBER" of the table "SYAIN" of the data source B have the same value. Therefore, the value of “uid” obtained as a result of the search of the data source A is used as the value of the column name “NUMBER” of the table “SYAIN” of the data source B, and the search key “NUMBER = <uid attribute value” for the data source B If ">" is retrieved, the data of the belonging code "201" stored in the data source B can be obtained.
[0296]
Therefore, in step L6, the generation unit 9c provides the transaction management unit 11 with a search request using “ou = 201” as a key and a search request using “NUMBER = <attribute value of uid>” as a key.
[0297]
In step L7, the transaction management unit 11 recognizes that the “ou” attribute is stored in the data source A by referring to the mapping definition data 14e, and issues a search request using “ou = 201” as a key. It is provided to the data source access unit 12a.
[0298]
In step L8, the data source access unit 12a refers to the data source connection definition data 14a in Table 12 above, acquires information for connecting to the data source A, and then acquires the data source access method definition data 14b in Table 13 above. , A command for performing a search using “ou = 201” as a key is created from the data source A, and the search is performed.
[0299]
As a result of the search, the attribute values of the “uid”, “mail”, and “mobile” attributes of the data source A associated with “SYAIN_NUM”, “MAIL_ADDRESS”, and “KETIAI” of the integrated class are obtained, and provided to the transaction management unit 11.
[0300]
Specifically, [“uid = 100001”, “mial=TTT@TTT.co.jp”, “mobile = 01-11111-1111”], [“uid = 100002”, “mial=JJJ@JJJ.co.jp” The data of “mobile = 01-2222-2222”], [“uid = 100003”, “mial=SSS@SSS.co.jp”, “mobile = 01-3333-3333”] are sent to the transaction management unit 11. Provided.
[0301]
Subsequently, in Step L9, the transaction management unit 11 recognizes that “NUMBER” is stored in the data source B by referring to the mapping definition data 14e, and obtains “NUMBER” obtained by searching the data source A. UUID "values" 100001 "," 100002 "," 100003 "as" NUMBER "values, and three search requests with" NUMBER = 100001 "," NUMBER = 100002 ", and" NUMBER = 100003 "as keys correspond to data source B. It is provided to the data source access unit 12b.
[0302]
In step L10, the data source access unit 12b refers to the data source connection definition data 14a in Table 12 above, acquires information for connecting to the data source B, and then acquires the data source access method definition data 14b in Table 13 above. , A command for performing a search using “NUMBER = 100001”, “NUMBER = 100002”, and “NUMBER = 100003” as keys is created, and the search is performed.
[0303]
As a result of the search, the attribute values of the “TEL”, “SYOKUI”, and “BIRTH” attributes of the data source B associated with the integrated classes “TELEPHONE”, “YAKUSYOKU”, and “BIRTHDATE” are acquired and provided to the transaction management unit 11.
[0304]
Specifically, ["TEL = 011-222-3456", "SYOKUI = S", "BIRTH = 1965/1/01/01"], ["TEL = 011-222-3456", "SYOKUI = E", "BIRTH = 1970" 05/12 "], [" TEL = 011-222-3456 "," SYOKUI = E "," BIRTH = 1973/03/07 "] are provided to the transaction management unit 11.
[0305]
In step L11, the transaction management unit 11 provides the search results of the data sources A and B to the generation unit 9c.
[0306]
In step L12, the generation unit 9c of the data source integration system 3 generates a set of the employee objects 24a to 24c having the belonging code “201”. At this time, an “AGE” attribute whose attribute type is a function is calculated and included in the employee object.
[0307]
In step L13, the employee objects 24a to 24c are returned to the application 4b and recorded on the recording device 13c.
[0308]
FIG. 19 is a block diagram illustrating an example of a processing flow of the third stage of the data source integration system 3 in the present embodiment. FIG. 19 shows the processing until the telephone numbers of the found employee objects 24a to 24c are updated to “011-555-5555”.
[0309]
In step M1, the operation content analysis unit 7 uses the application 4b to update the telephone numbers of the employee objects 24a to 24c of the employees belonging to the organization with the organization code "201" to "011-555-5555". "TELEPHONE = 011-555-5555" is accepted and provided to the access control unit 8. Specifically, it extracts information indicating that the request is “request from the application 4b”, the operation is “update”, and the attribute of the operation target is “TELEPHONE”, and the information is provided to the access control unit 8. I do. At this time, the information on the operation target object has been identified as an employee object whose affiliation code is “201” by searching for an employee object belonging to the organization with the organization code “201” in the second stage.
[0310]
In step M2, the access control unit 8 acquires the authority information of the application 4b by referring to the access control data 15 exemplified in the above Tables 17 to 19. Specifically, the access control unit 8 extracts that the authority information of the application 4b corresponds to ROLE02 based on the role definition data 15a in Table 17 above. Then, since the class of the operation target object is “SyainClass”, the authority information for SyainClass is extracted based on the access control definition data 15c of ROLE02 in Table 19 above. In the example of Table 19, “SyainClass” can be searched, registered, updated, and deleted, and it can be recognized that Read and Write permissions have been granted to all attributes. Therefore, the access control unit 8 outputs to the updating unit 9d of the object processing unit 9 information that is defined as “SyainClass” and is “update” for “TELEPHONE” of the employee object with the belonging code “201”.
[0311]
In step M3, the updating unit 9d of the object processing unit 9 updates the attribute value of the attribute "TELEPHONE" of the employee objects 24a to 24c having the belonging code "201" to "011-555-5555" for the recording device 13c. .
[0312]
【The invention's effect】
As described in detail above, in the present invention, the contents of a plurality of data sources are unified and managed, and data can be managed efficiently.
[Brief description of the drawings]
FIG. 1 is a block diagram showing an example of a configuration of a data source integration system according to a first embodiment of the present invention.
FIG. 2 is an exemplary block diagram showing a detailed example of an object processing unit according to the embodiment;
FIG. 3 is an exemplary view showing an example of the relationship between the contents of a data source and an integrated class according to the embodiment;
FIG. 4 is an exemplary view showing an example of an integrated class in which a reference relationship between a plurality of classes is defined in the embodiment;
FIG. 5 is an exemplary block diagram showing a first example of an operation concept of the data source integration system according to the embodiment;
FIG. 6 is an exemplary block diagram showing a second example of the operation concept of the data source integration system according to the embodiment;
FIG. 7 is an exemplary block diagram showing a third example of the operation concept of the data source integration system according to the embodiment;
FIG. 8 is a block diagram showing a fourth example of the operation concept of the data source integration system according to the embodiment;
FIG. 9 is an exemplary block diagram showing a fifth example of the operation concept of the data source integration system according to the embodiment;
FIG. 10 is an exemplary flowchart illustrating an example of processing of the data source integration system according to the embodiment;
FIG. 11 is a block diagram showing an example of a configuration of a data source integration system according to a second embodiment of the present invention.
FIG. 12 is an exemplary flowchart illustrating an example of processing of the data source integration system according to the embodiment;
FIG. 13 is a block diagram showing an example of a tree configuration of a data source used in the first embodiment of the present invention.
FIG. 14 is an exemplary block diagram showing a first example of the processing flow of the data source integration system according to the embodiment;
FIG. 15 is an exemplary block diagram showing a second example of the processing flow of the data source integration system according to the embodiment;
FIG. 16 is a block diagram showing an example of a processing flow of the data source integration system according to the second embodiment of the present invention.
FIG. 17 is a block diagram showing an example of a first-stage processing flow of the data source integration system according to the third embodiment of the present invention;
FIG. 18 is an exemplary block diagram illustrating an example of a process flow of a second stage of the data source integration system according to the embodiment.
FIG. 19 is an exemplary block diagram illustrating an example of a processing flow of a third stage of the data source integration system according to the embodiment;
FIG. 20 is a diagram in which the contents of a data source are converted into objects.
[Explanation of symbols]
3, 20: data source integration system, 4a to 4c: application, 6: recording medium, 6a, 6b: data source integration program, 7: operation content analysis unit, 8: access control unit, 9: object processing unit, 10 ... Write management unit, 11: Transaction management unit, 12a to 12c: Data source access unit, 13a to 13c: Recording device, 14: Definition data, 15: Access control data, A to C: Data source, 9a: Definition data read Section, 9b ... search section, 9c ... generation section, 9d ... update section, 9e ... registration section, 9f ... deletion section, 9g ... exclusive control section, 9h ... writing section

Claims (13)

On the computer,
A reception function for receiving data operation commands from the command source,
According to the operation command received by the receiving function, a generation function of generating data from a plurality of different types of data sources recorded in advance in the recording unit,
The data source integration program, wherein the data source includes data to be managed and information of a management form. On the computer,
A reception function for receiving data operation commands from the command source,
When a search is requested by the data operation command, data to be searched specified by the data operation command is selected from integrated data generated according to a plurality of different types of data sources and recorded in the recording unit. A search function for searching integrated data including, when integrated data including the search target data is searched, providing the searched integrated data to the command source,
When the integrated data including the search target data is not searched, the integrated data is generated based on the plurality of different types of data sources, the generated integrated data is recorded in the recording unit, and the command source is generated. Generation function provided to
To realize
The data source integration program, wherein the data source includes data to be managed and information of a management form. The program according to claim 2,
On the computer,
When an update is requested by the data operation instruction, an update function of updating the contents of the integrated data recorded in the recording unit according to the update content specified by the data operation instruction is realized. And a data source integration program. In the program according to claim 2 or 3,
On the computer,
A data source integration program for realizing a registration function of recording integrated data including data specified by the data operation instruction in the recording unit when registration is requested by the data operation instruction. The program according to any one of claims 2 to 4,
On the computer,
A data source integration program for realizing a deletion function of deleting data specified by the data operation instruction from the recording unit when deletion is requested by the data operation instruction. The program according to any one of claims 2 to 5,
On the computer,
A data source integration program for realizing a transaction management function of providing a data source operation instruction corresponding to the data operation instruction to the plurality of data sources. The program according to claim 6,
On the computer,
A data source integration program for realizing a writing function of providing the data operation instruction to the transaction management function at a timing different from the data operation instruction. The program according to any one of claims 2 to 7,
On the computer,
A data source integration program for realizing an exclusive control function of performing exclusive control on integrated data recorded in the recording means. The program according to any one of claims 2 to 8,
The format of the integrated data is defined by an integrated class representing the integrated content of the plurality of data sources,
The integrated data is an integrated object generated based on the integrated class. The program according to claim 9,
The data source integration program according to claim 1, wherein the integration class includes definition contents of a reference relationship between a plurality of classes. In the program according to claim 9 or 10,
The data source integration program according to claim 1, wherein the integration class includes a definition of a function for calculating integrated content based on the content of the plurality of data sources. Receiving means for receiving a data operation command from a command source; recording means for recording integrated data generated according to a plurality of different types of data sources;
When a search is requested by the data operation instruction, integrated data including search target data specified by the data operation instruction is searched from the integrated data recorded in the recording unit, and the search is performed. When integrated data including target data is searched, a search unit that provides the searched integrated data to the command source,
When the integrated data including the search target data is not searched, the integrated data is generated based on the plurality of different types of data sources, the generated integrated data is recorded in the recording unit, and the command source is generated. Generating means for providing
The data source integration system, wherein the data source includes data to be managed and information of a management form. A method of managing data from a plurality of data sources by a computer,
Receiving a data operation command from the command source,
When a search is requested by the data operation command, data to be searched specified by the data operation command is selected from integrated data generated according to a plurality of different types of data sources and recorded in the recording unit. Execute the process of searching for integrated data including
When the integrated data including the search target data is searched, the searched integrated data is provided to the command source, and when the integrated data including the search target data is not searched, the plurality of different A method for generating integrated data based on a data source of a type, recording the generated integrated data in the recording unit, and providing the generated integrated data to the command source.

Images