Integration services systems, methods and computer program products for ECM-independent ETL tools
To resolve a conflict between CMIS secondary types and certain ECM features such as content server categories and allow the underlying ECM system to be fully CMIS-compliant, an ECM-independent ETL tool comprising a CMIS-compliant, repository-specific connector is provided. Operating on an integration services server at an integration tier between an application tier and a storage tier where the repository resides, the connector is particularly configured to support CMIS secondary types and specific to the repository. On startup, the connector can import any category definition from the repository. The category definition contains properties associated with a category in the repository. When the category is attached to a document, the properties are viewable via a special category object type and a category identifier for the category. Any application can be adapted to leverage the ECM-independent ETL tool disclosed herein.
1. A method, comprising:
responsive to a request from a user of an application operating at an application tier to access a repository operating at a storage tier and storing objects of repository-specific types, starting up, by a server operating at an integration tier between the application tier and the storage tier, a repository-specific connector to connect the application with the repository, wherein the starting up comprises importing, from the repository based on an account privilege of the user, a definition of a repository feature of the repository as a secondary type definition, wherein the secondary type definition defines a set of properties that can be dynamically added to or removed from content management interoperability services (CMIS) objects; and
sending, by the server operating at the integration tier, the secondary type definition to the application operating at the application tier, wherein the application, responsive to an instruction from the user to create a document of a secondary type object type defined in the application:
obtains the set of properties from the secondary type definition;
associates the document of the secondary type object type with the set of properties from the secondary type definition;
generates a view of the document; and
displays the view on a user device.
2. The method according to claim 1 , wherein the starting up further comprises displaying the set of properties through a user interface of the server operating at the integration tier.
3. The method according to claim 1 , wherein each instance of the repository feature, which is of a primary type in a repository object tree, has a definition that is viewable, through a user interface of the server operating at the integration tier, as a CMIS secondary type in a CMIS type definition tree.
4. The method according to claim 1 , wherein the repository-specific connector is configured for establishing a CMIS-compliant connection between the application with the repository and for supporting CMIS documents, CMIS folders, CMIS primary types, and CMIS secondary types and operations.
5. The method according to claim 1 , wherein the repository-specific connector is configured for mapping the repository-specific types to CMIS types defined in a CMIS data model.
6. The method according to claim 5 , wherein the application follows the CMIS data model.
7. The method according to claim 1 , further comprising:
adding the secondary type object type to the application; and
configuring the repository-specific connector to support CMIS secondary types defined in a CMIS data model.
8. A system, comprising:
a processor;
a non-transitory computer-readable medium; and
instructions stored on the non-transitory computer-readable medium and translatable by the processor for:
responsive to a request from a user of an application operating on a user device to access a repository storing objects of repository-specific types, starting up a repository-specific connector to connect the application with the repository, wherein the starting up comprises importing, from the repository based on an account privilege of the user, a definition of a repository feature of the repository as a secondary type definition, wherein the secondary type definition defines a set of properties that can be dynamically added to or removed from content management interoperability services (CMIS) objects; and
sending the secondary type definition to the application operating on the user device, wherein the application, responsive to an instruction from the user to create a document of a secondary type object type defined in the application:
obtains the set of properties from the secondary type definition;
associates the document of the secondary type object type with the set of properties from the secondary type definition;
generates a view of the document; and
displays the view on the user device.
9. The system of claim 8 , wherein the starting up further comprises displaying the set of properties through a user interface.
10. The system of claim 8 , wherein each instance of the repository feature, which is of a primary type in a repository object tree, has a definition that is viewable, through a user interface, as a CMIS secondary type in a CMIS type definition tree.
11. The system of claim 8 , wherein the repository-specific connector is configured for establishing a CMIS-compliant connection between the application with the repository and for supporting CMIS documents, CMIS folders, CMIS primary types, and CMIS secondary types and operations.
12. The system of claim 8 , wherein the repository-specific connector is configured for mapping the repository-specific types to CMIS types defined in a CMIS data model.
13. The system of claim 12 , wherein the application follows the CMIS data model.
14. The system of claim 8 , wherein the instructions are further translatable by the processor for:
adding the secondary type object type to the application; and
configuring the repository-specific connector to support CMIS secondary types defined in a CMIS data model.
15. A computer program product comprising a non-transitory computer-readable medium storing instructions translatable by an integration server computer for:
responsive to a request from a user of an application operating on a user device to access a repository storing objects of repository-specific types, starting up a repository-specific connector to connect the application with the repository, wherein the starting up comprises importing, from the repository based on an account privilege of the user, a definition of a repository feature of the repository as a secondary type definition, wherein the secondary type definition defines a set of properties that can be dynamically added to or removed from content management interoperability services (CMIS) objects; and
sending the secondary type definition to the application operating on the user device, wherein the application, responsive to an instruction from the user to create a document of a secondary type object type defined in the application:
obtains the set of properties from the secondary type definition;
associates the document of the secondary type object type with the set of properties from the secondary type definition;
generates a view of the document; and
displays the view on the user device.
16. The computer program product of claim 15 , wherein the starting up further comprises displaying the set of properties through a user interface.
17. The computer program product of claim 15 , wherein each instance of the repository feature, which is of a primary type in a repository object tree, has a definition that is viewable, through a user interface, as a CMIS secondary type in a CMIS type definition tree.
18. The computer program product of claim 15 , wherein the repository-specific connector is configured for establishing a CMIS-compliant connection between the application with the repository and for supporting CMIS documents, CMIS folders, CMIS primary types, and CMIS secondary types and operations.
19. The computer program product of claim 15 , wherein the repository-specific connector is configured for mapping the repository-specific types to CMIS types defined in a CMIS data model.
20. The computer program product of claim 19 , wherein the application follows the CMIS data model.