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:
receiving, by a content management interoperability services (CMIS)-compliant server, a request from an application on a user device to access a repository, the application adapted to support a secondary type object type as a CMIS primary object type such that CMIS secondary object types are attachable to the secondary type object type in the application;
in response to the request from the application to access the repository, establishing, by the CMIS-compliant server using a repository-specific connector, a CMIS connection between the application with the repository, the repository-specific connector specific to the repository and adapted for mapping a repository-supported object type to a CMIS primary object type or a CMIS secondary object type, the repository-supported object type being a primary object type in the repository and having a definition specifying a set of dynamically manipulatable attributes;
on startup of the repository-specific connector, importing or retrieving, by the repository-specific connector from the repository, the definition of the repository-supported object type;
responsive to a document having the secondary type object type being created within the application, determining whether the repository-supported object type is attached to the document as a CMIS secondary object type;
responsive to the repository-supported object type being attached to the document as a CMIS secondary object type, automatically associating the document created in the application on the user device with the set of dynamically manipulatable attributes from the definition of the repository-supported object type imported or retrieved from the repository;
generating a view of the document having the secondary type object type, the view containing the set of dynamically manipulatable attributes; and
displaying the view of the document with the set of dynamically manipulatable attributes on the user device.
2. The method according to claim 1 , wherein the application is further adapted to support a CMIS item object type as a CMIS primary object type and wherein the CMIS secondary object types are attachable to the CMIS item object type in the application.
3. The method according to claim 1 , further comprising:
displaying, by the CMIS-compliant server through a user interface, a set of dynamically manipulatable properties defined by a CMIS secondary object type, the set of dynamically manipulatable properties comprising a property for associating the repository-supported object type through an object type identifier.
4. The method according to claim 3 , wherein, through the object type identifier, the set of dynamically manipulatable attributes from the definition of the repository-supported object type is viewable on the user interface of the CMIS-compliant server.
5. The method according to claim 1 , wherein the CMIS primary object type has a predefined set of fixed properties for an CMIS object and wherein the CMIS secondary object type defines a set of dynamically manipulatable properties applicable to the CMIS object at creation time of the CMIS object.
6. The method according to claim 1 , wherein the importing or retrieving is performed using a repository-specific application programming interface based on an account privilege of a user of the CMIS-compliant server.
7. The method according to claim 1 , wherein the application is one of a plurality of client applications of the CMIS-compliant server, the plurality of client applications operating independently of the repository.
8. A content management interoperability services (CMIS)-compliant system, comprising:
a processor;
a non-transitory computer-readable medium; and
stored instructions translatable by the processor for:
receiving a request from an application on a user device to access a repository, the application adapted to support a secondary type object type as a CMIS primary object type such that CMIS secondary object types are attachable to the secondary type object type in the application;
in response to the request from the application to access the repository, establishing, using a repository-specific connector, a CMIS connection between the application with the repository, the repository-specific connector specific to the repository and adapted for mapping a repository-supported object type to a CMIS primary object type or a CMIS secondary object type, the repository-supported object type being a primary object type in the repository and having a definition specifying a set of dynamically manipulatable attributes;
on startup of the repository-specific connector, importing or retrieving, from the repository, the definition of the repository-supported object type;
responsive to a document having the secondary type object type being created within the application, determining whether the repository-supported object type is attached to the document as a CMIS secondary object type;
responsive to the repository-supported object type being attached to the document as a CMIS secondary object type, automatically associating the document created in the application on the user device with the set of dynamically manipulatable attributes from the definition of the repository-supported object type imported or retrieved from the repository;
generating a view of the document having the secondary type object type, the view containing the set of dynamically manipulatable attributes; and
displaying the view of the document with the set of dynamically manipulatable attributes on the user device.
9. The CMIS-compliant system of claim 8 , wherein the application is further adapted to support a CMIS item object type as a CMIS primary object type and wherein the CMIS secondary object types are attachable to the CMIS item object type in the application.
10. The CMIS-compliant system of claim 8 , wherein the stored instructions are further translatable by the processor for:
displaying, through a user interface, a set of dynamically manipulatable properties defined by a CMIS secondary object type, the set of dynamically manipulatable properties comprising a property for associating the repository-supported object type through an object type identifier.
11. The CMIS-compliant system of claim 10 , wherein, through the object type identifier, the set of dynamically manipulatable attributes from the definition of the repository-supported object type is viewable on the user interface.
12. The CMIS-compliant system of claim 8 , wherein the CMIS primary object type has a predefined set of fixed properties for an CMIS object and wherein the CMIS secondary object type defines a set of dynamically manipulatable properties applicable to the CMIS object at creation time of the CMIS object.
13. The CMIS-compliant system of claim 8 , wherein the importing or retrieving is performed using a repository-specific application programming interface based on an account privilege of a user of the CMIS-compliant server.
14. The CMIS-compliant system of claim 8 , wherein the application is one of a plurality of client applications of the CMIS-compliant server, the plurality of client applications operating independently of the repository.
15. A computer program product comprising a non-transitory computer-readable medium storing instructions translatable by a processor of a content management interoperability services (CMIS)-compliant system for:
receiving a request from an application on a user device to access a repository, the application adapted to support a secondary type object type as a CMIS primary object type such that CMIS secondary object types are attachable to the secondary type object type in the application;
in response to the request from the application to access the repository, establishing, using a repository-specific connector, a CMIS connection between the application with the repository, the repository-specific connector specific to the repository and adapted for mapping a repository-supported object type to a CMIS primary object type or a CMIS secondary object type, the repository-supported object type being a primary object type in the repository and having a definition specifying a set of dynamically manipulatable attributes;
on startup of the repository-specific connector, importing or retrieving, from the repository, the definition of the repository-supported object type;
responsive to a document having the secondary type object type being created within the application, determining whether the repository-supported object type is attached to the document as a CMIS secondary object type;
responsive to the repository-supported object type being attached to the document as a CMIS secondary object type, automatically associating the document created in the application on the user device with the set of dynamically manipulatable attributes from the definition of the repository-supported object type imported or retrieved from the repository;
generating a view of the document having the secondary type object type, the view containing the set of dynamically manipulatable attributes; and
displaying the view of the document with the set of dynamically manipulatable attributes on the user device.
16. The computer program product of claim 15 , wherein the application is further adapted to support a CMIS item object type as a CMIS primary object type and wherein the CMIS secondary object types are attachable to the CMIS item object type in the application.
17. The computer program product of claim 15 , wherein the instructions are further translatable by the processor for:
displaying, through a user interface, a set of dynamically manipulatable properties defined by a CMIS secondary object type, the set of dynamically manipulatable properties comprising a property for associating the repository-supported object type through an object type identifier.
18. The computer program product of claim 17 , wherein, through the object type identifier, the set of dynamically manipulatable attributes from the definition of the repository-supported object type is viewable on the user interface.
19. The computer program product of claim 15 , wherein the CMIS primary object type has a predefined set of fixed properties for an CMIS object and wherein the CMIS secondary object type defines a set of dynamically manipulatable properties applicable to the CMIS object at creation time of the CMIS object.
20. The computer program product of claim 15 , wherein the importing or retrieving is performed using a repository-specific application programming interface based on an account privilege of a user of the CMIS-compliant server.