Oshyn has implemented a synchronization tool for RedDot environments. We realize about the importance of synchronization jobs between different environments without using the import/export built in tool of the CMS. This kind of synchronization is very common in projects when you just have to push small changes from one environment to another.

The sync tool allows synchronizing CMS servers in different scenarios:
- · Source and Target Servers are located in the same server but are different projects, CMS servers are not located in the same network of the sync tool, the second scenario is when the entire architecture is installed in the same network.
- · Source Server, Target Server and the sync tool are located in different networks, in this case is possible to establish a VPN connection to execute the tool if it requires.
RedDot CMS provides different web services to manage different types of queries (RQL):
- · PageService: provide methods to manage process related to content, for example create/edit pages, content elements, structural elements, metadata, etc.
- · SessionService: provide methods to manage user session from an external application, this is one of the most important services because it provides data to execute almost all the types of RQL queries
- · RqlService: provides methods to execute queries, it needs session data to execute queries.
Tool Features
In this first version of the Sync Tool we have implemented the following futures:
- · Categories/Keywords Synchronization: with the categories synchronization you can move the entire set of categories/keywords at once or you can move only the new keywords of a category. * This process does not present dependencies with the CMS elements
- · Authorization Packages: users can synchronize authorization packages but this process presents some dependencies like users/groups dependencies, this means that as previous step users/groups synchronization should be executed.
- · Workflows Synchronization: maybe this can be the most complex functionality of the tool, this implies a lot of data load, as the same way of Authorization packages this requires a previous synchronization of users/groups and project variants.
- · Content Classes Synchronization: this feature allows users to move new structural changes between environments, this should be the most useful feature because it allows users to edit/create templates and this process can merge a lot of data. This process has folder dependencies so folders should be synchronized before Content Classes.

In a second version of the tool we want to add all the dependencies synchronization and as a plus Oshyn is working to implement a generic migration tool that can work with different types of Content Managements Systems, this will allows users to change the software technology between different CMS without having to spend too much time in the data and site structure migration.





blog comments powered by Disqus