Content Server Developer Tools are the latest and the first ever supported tools from Oracle (Fatwire) which provides plugin to eclipse and command line utility to help manage Fatwire artefacts in a file system. Once the artefacts are in file system, it opens a whole new doors to managing them. I covered about CSDT in my previous post and this is extention to the original post.
CSDT has been designed keeping in my the new development as the priority with not much thought around the projects upgrading to CS 761. But in my view the focus should have been other way around as there will be lot more upgrades than new implementations as the initial use case for CSDT.
If you are planning to use CSDT across developers setup, here are some pointers to be aware:
- CSDT V1 has a limitation that it expects the work space name to be cs_workspace at the location
/export/envision. So, one option to make csdt work is to create a project with the same name at expected location.
- CSDT expects the same folder structure within workspace, src/_metadata and src/jsp. So it is important that if you are trying to manage CSDT export within CVS, setup the same project structure
- When you have all the artefacts you want to manage within CVS, make sure everyone sync their local instances with the CVS export so that everyone are at the same code level before starting any development
- Word ‘Exception’ causes CSDT import to fail. Make sure that during development, do not specify name/ description fields with it. Or use Excaption
If you are upgrading to CS761, there are number of issues which you need to be aware of:
- Fw_uids need to be same across all the upgraded environments otherwise csdt deployments will fail
- As part of best practice, if you have extracted element as cselement to make code go through the publishing process, make sure that all such dependencies are changed manually in Meta information. (.main.XML) file else the import will fail
General CSDT issues:
- Workflows can not be exported and imported through CSDT so there is need to either mirror to server the workflows or use catalog mover to move them
- Categories can not be exported using CSDT
- If Treetabs or start menus or any other artefact is enabled for any site, it is not exported out when we export artefacts for specific site, though they are part of the at site
- modified date command line parameter doesn’t work as expected
- Not applicable for no asset tables. A classic example is usage of SystemLocateString.
- Incremental deployments are tough to achieve and its more manual work to arrive at the dependency set. Full deployment is the easiest way to achieve code drop.
- CSDT doesn’t check if the asset has actually modified and updates all the assets which are part of workspace. So, if you carry out full deployment everytime, one drawback is that it will invalidate whole of the cache.
Even though there are number of issues with the current version of CSDT, it is a good to start using it as it will provide a platform which is going to improve over time. And hopefully version 2 of CSDT is not far which will definitely address some of the above issues, it not all.
Happy CSDTing !