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 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.
1. A method, comprising:
configuring a repository-specific connector to support content management interoperability services (CMIS) documents, CMIS folders, CMIS primary types, and CMIS secondary types, the repository-specific connector particularly configured for a repository, the repository having categories as primary objects, the repository-specific connector operating on an integration services server at an integration tier between an application tier and a storage tier, the repository residing at the storage tier;
configuring an application operating at the application tier on a user device to add a secondary type object type, the user device communicatively connected to the integration services server over a network;
responsive to a request from a user of the application to access the repository, starting up the repository-specific connector to connect the application with the repository;
on startup, importing any category definition from the repository based on an account privilege of the user, the importing performed by the repository-specific connector, the category definition containing properties associated with a category 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, wherein the document is created using typed module instructions that obtain the properties from the category definition at run-time via the repository-specific connector and, responsive to the category being attached to the document, associating the document with the properties from the category definition;
generating a view of the document of the secondary type object type containing the properties from the category definition; and
displaying the view on the user device.
2. The method according to claim 1 , wherein the repository-specific connector is configured with a category object type having a category type identifier, the category object type inherited from a primary CMIS document type.
3. The method according to claim 2 , wherein the category has a category identifier, wherein the category is attached to the document, and wherein the document is associated with the properties from the category definition via the category type identifier and the category identifier.
4. The method according to claim 1 , wherein the application is further configured to add a CMIS item object type.
5. The method according to claim 4 , wherein the secondary type object type and the CMIS item object type for the application are primary object types such that CMIS secondary types are attachable to the secondary type object type and the CMIS item object type for the application.
6. The method according to claim 1 , wherein the category definition defines additional attributes that can be dynamically applied to or removed from an object managed by the repository.
7. A computer program product comprising at least one non-transitory computer readable medium storing instructions translatable by at least one processor to perform:
configuring a repository-specific connector to support content management interoperability services (CMIS) documents, CMIS folders, CMIS primary types, and CMIS secondary types, the repository-specific connector particularly configured for a repository, the repository having categories as primary objects, the repository-specific connector operating on an integration services server at an integration tier between an application tier and a storage tier, the repository residing at the storage tier;
configuring an application operating at the application tier on a user device to add a secondary type object type, the user device communicatively connected to the integration services server over a network;
responsive to a request from a user of the application to access the repository, starting up the repository-specific connector to connect the application with the repository;
on startup, importing any category definition from the repository based on an account privilege of the user, the importing performed by the repository-specific connector, the category definition containing properties associated with a category 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, wherein the document is created using typed module instructions that obtain the properties from the category definition at run-time via the repository-specific connector and, responsive to the category being attached to the document, associating the document with the properties from the category definition;
generating a view of the document of the secondary type object type containing the properties from the category definition; and
displaying the view on the user device.
8. The computer program product of claim 7 , wherein the repository-specific connector is configured with a category object type having a category type identifier, the category object type inherited from a primary CMIS document type.
9. The computer program product of claim 8 , wherein the category has a category identifier, wherein the category is attached to the document, and wherein the document is associated with the properties from the category definition via the category type identifier and the category identifier.
10. The computer program product of claim 7 , wherein the application is further configured to add a CMIS item object type.
11. The computer program product of claim 10 , wherein the secondary type object type and the CMIS item object type for the application are primary object types such that CMIS secondary types are attachable to the secondary type object type and the CMIS item object type for the application.
12. The computer program product of claim 7 , wherein the category definition defines additional attributes that can be dynamically applied to or removed from an object managed by the repository.
13. A system, comprising:
at least one processor;
at least one non-transitory computer readable medium; and
stored instructions translatable by the at least one processor to perform:
configuring a repository-specific connector to support content management interoperability services (CMIS) documents, CMIS folders, CMIS primary types, and CMIS secondary types, the repository-specific connector particularly configured for a repository, the repository having categories as primary objects, the repository-specific connector operating on an integration services server at an integration tier between an application tier and a storage tier, the repository residing at the storage tier;
configuring an application operating at the application tier on a user device to add a secondary type object type, the user device communicatively connected to the integration services server over a network;
responsive to a request from a user of the application to access the repository, starting up the repository-specific connector to connect the application with the repository;
on startup, importing any category definition from the repository based on an account privilege of the user, the importing performed by the repository-specific connector, the category definition containing properties associated with a category 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, wherein the document is created using typed module instructions that obtain the properties from the category definition at run-time via the repository-specific connector and, responsive to the category being attached to the document, associating the document with the properties from the category definition;
generating a view of the document of the secondary type object type containing the properties from the category definition; and
displaying the view on the user device.
14. The system of claim 13 , wherein the repository-specific connector is configured with a category object type having a category type identifier, the category object type inherited from a primary CMIS document type.
15. The system of claim 14 , wherein the category has a category identifier, wherein the category is attached to the document, and wherein the document is associated with the properties from the category definition via the category type identifier and the category identifier.
16. The system of claim 13 , wherein the application is further configured to add a CMIS item object type.
17. The system of claim 16 , wherein the secondary type object type and the CMIS item object type for the application are primary object types such that CMIS secondary types are attachable to the secondary type object type and the CMIS item object type for the application.