# US 10,503,878 B2 · Integration services systems, methods and computer program products for ECM-independent ETL tools > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 10,503,878 B2 - Document ID: US10503878B2 - Status: Granted - Kind: B2 - Application number: 16/012,087 - Filed: 2018-06-19 - Published: 2018-12-13 - Granted: 2019-12-10 - Earliest claimed: 2013-03-14 - Assignees: Open Text SA ULC - Applicants: Open Text SA Ulc - Inventors: Alexander Lilko; Martin Brousseau - Web page: https://patentgrep.com/patent/US10503878B2 ## CPC - G06F 21/10: Protecting distributed programs or content, e.g. vending or licensing of copyrighted material (protection in video systems or pay television H04N7/16) {; Digital rights management [DRM]} - G06F 16/254: {Extract, transform and load [ETL] procedures, e.g. ETL data flows in data warehouses} - G06F 21/604: {Tools and structures for managing or administering access control systems} - G06F 21/6218: {to a system of files or objects, e.g. local or distributed file system or database} - G06F 2221/2113: Multi-level security, e.g. mandatory access control - H04L 63/101: {Access control lists [ACL]} - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract 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 particular 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. ## Claims ### Claim 1 A method, comprising: responsive to a request from a user of an application at an application tier to access a repository at a storage tier, starting up a repository-specific connector on an integration services server at an integration tier between the application tier and the storage tier to connect the application at the application tier with the repository at the storage tier by way of the integration tier, the repository-specific connector specific to a repository and configured for supporting content management interoperability services (CMIS) documents, CMIS folders, CMIS primary types, and CMIS secondary types, the repository having a repository feature for managing objects, the application running on a user device and configured with a secondary type object type of the CMIS secondary types; on startup of the repository-specific connector on the integration services server importing any repository feature definition from the repository based on an account privilege of the user, the repository feature definition containing properties associated with a repository object type in the repository; responsive to an instruction from the user of the application to create a document of the secondary type object type, creating the document of the secondary type object type and, responsive to the repository object type attached to the document, associating the document with the properties from the repository feature definition; generating a view of the document of the secondary type object type containing the properties from the repository feature definition; and displaying, in the application on the user device, the view of the document of the secondary type object type containing the properties from the repository feature definition. ### Claim 2 (depends on 1) The method according to claim 1, wherein the objects stored in the repository are managed by a backend system utilizing the repository feature, the backend system operating in an enterprise computing environment. ### Claim 3 (depends on 2) The method according to claim 2, wherein the application at the application tier is part of an extract, transform, and load (ETL) tool and wherein the ETL tool operates independently of the backend system that manages the objects stored in the repository. ### Claim 4 (depends on 3) The method according to claim 3, wherein the backend system comprises an enterprise content management (ECM) system or a content server (CS). ### Claim 5 (depends on 3) The method according to claim 3, wherein the repository-specific connector is operable to map the repository object type, which is specific to the backend system, to the secondary type object type of the document created through the application at the application tier, wherein the secondary type object type is one of the CMIS secondary types. ### Claim 6 (depends on 1) The method according to claim 1, further comprising: adding an additional secondary type object type to the document created through the application at the application tier. ### Claim 7 (depends on 6) The method according to claim 6, wherein the additional secondary type object type added to the document indicates a records management hold. ### Claim 8 A system, comprising: a processor; a non-transitory computer-readable medium; and stored instructions translatable by the processor for: responsive to a request from a user of an application at an application tier to access a repository at a storage tier, starting up a repository-specific connector on an integration services server at an integration tier between the application tier and the storage tier to connect the application at the application tier with the repository at the storage tier by way of the integration tier, the repository-specific connector specific to a repository and configured for supporting content management interoperability services (CMIS) documents, CMIS folders, CMIS primary types, and CMIS secondary types, the repository having a repository feature for managing objects, the application running on a user device and configured with a secondary type object type of the CMIS secondary types; on startup of the repository-specific connector on the integration services server, importing any repository feature definition from the repository based on an account privilege of the user, the repository feature definition containing properties associated with a repository object type in the repository; responsive to an instruction from the user of the application to create a document of the secondary type object type, creating the document of the secondary type object type and, responsive to the repository object type attached to the document, associating the document with the properties from the repository feature definition; generating a view of the document of the secondary type object type containing the properties from the repository feature definition; and displaying, in the application on the user device, the view of the document of the secondary type object type containing the properties from the repository feature definition. ### Claim 9 (depends on 8) The system of claim 8, wherein the objects stored in the repository are managed by a backend system utilizing the repository feature, the backend system operating in an enterprise computing environment. ### Claim 10 (depends on 9) The system of claim 9, wherein the application at the application tier is part of an extract, transform, and load (ETL) tool and wherein the ETL tool operates independently of the backend system that manages the objects stored in the repository. ### Claim 11 (depends on 10) The system of claim 10, wherein the backend system comprises an enterprise content management (ECM) system or a content server (CS). ### Claim 12 (depends on 10) The system of claim 10, wherein the repository-specific connector is operable to map the repository object type, which is specific to the backend system, to the secondary type object type of the document created through the application at the application tier, wherein the secondary type object type is one of the CMIS secondary types. ### Claim 13 (depends on 8) The system of claim 8, wherein the stored instructions are further translatable by the processor for: adding an additional secondary type object type to the document created through the application at the application tier. ### Claim 14 (depends on 8) The system of claim 8, wherein the additional secondary type object type added to the document indicates a records management hold. ### Claim 15 A computer program product comprising a non-transitory computer-readable medium storing instructions translatable by a processor for: responsive to a request from a user of an application at an application tier to access a repository at a storage tier, starting up a repository-specific connector on an integration services server at an integration tier between the application tier and the storage tier to connect the application at the application tier with the repository at the storage tier by way of the integration tier, the repository-specific connector specific to a repository and configured for supporting content management interoperability services (CMIS) documents, CMIS folders, CMIS primary types, and CMIS secondary types, the repository having a repository feature for managing objects, the application running on a user device and configured with a secondary type object type of the CMIS secondary types; on startup of the repository-specific connector on the integration services server, importing any repository feature definition from the repository based on an account privilege of the user, the repository feature definition containing properties associated with a repository object type in the repository; responsive to an instruction from the user of the application to create a document of the secondary type object type, creating the document of the secondary type object type and, responsive to the repository object type attached to the document, associating the document with the properties from the repository feature definition; generating a view of the document of the secondary type object type containing the properties from the repository feature definition; and displaying, in the application on the user device, the view of the document of the secondary type object type containing the properties from the repository feature definition. ### Claim 16 (depends on 15) The computer program product of claim 15, wherein the objects stored in the repository are managed by a backend system utilizing the repository feature, the backend system operating in an enterprise computing environment. ### Claim 17 (depends on 15) The computer program product of claim 15, wherein the application at the application tier is part of an extract, transform, and load (ETL) tool and wherein the ETL tool operates independently of the backend system that manages the objects stored in the repository. ### Claim 18 (depends on 17) The computer program product of claim 17, wherein the repository-specific connector is operable to map the repository object type, which is specific to the backend system, to the secondary type object type of the document created through the application at the application tier, wherein the secondary type object type is one of the CMIS secondary types. ### Claim 19 (depends on 15) The computer program product of claim 15, wherein the instructions are further translatable by the processor for: adding an additional secondary type object type to the document created through the application at the application tier. ### Claim 20 (depends on 19) The computer program product of claim 19, wherein the additional secondary type object type added to the document indicates a records management hold.