Detecting language please wait for.......
FICO will soon be upgrading from LiveContent Architect 11.1.3 to the latest version of Tridion Docs. Tridion Docs no longer supports the old version of the DITA-OT that we run our PDF output through (version 1.5.2), so part of the project will involve porting our PDF customizations to a newer version of the OT. Because the structure of the OT has changed significantly, this will not be an easy task.
Can anyone share any lessons they learned when doing this? Best practices? Things to watch out for? Any advice at all? Thank you in advance!
You should be able to get your plugin running with just a few tweaks, but I think it's always a good idea to refactor using the new templates in the default plugins. So you might think about doing the change in two phases: phase 1, update the old plugin working in the new version of the OT; phase 2, create a new plugin and refactor your old style sheet piece by piece to work in the new OT.
Hi Elizabeth. It's always great to plan ahead. That said, SDL Professional Services can try and hook up your existing DITA-OT to the upgraded product and see if we can get your PDFs building. DITA 1.5.2 is a pretty old Tookkit version so it's not a bad idea to think about upgrading it.
I did same thing last year. I migrated our stylesheets from DITA-OT 1.7.5 to 2.5.4. It's not best practice, but I recommend following process to achieve successful migration.
1. Survey differences between LCA and TD14
There are many changes regarding the DITA-OT related implementation of Content Manager. For example,
a) How to launch DITA-OTLCA uses batch command, but TD14 uses powershell command
b) Preprocess and postprocess for publishingLCA uses vb scripts to control preprocess and postprocess for publishing. In TD14, preprocess and postprocess are described in XML Publishing Plug-in Settings.
c) Output metadata controlIf your PDF stylesheets read metadata output from Content Manager, you should change the method to designate required metadata. LCA uses 'ReqMetaDataExportForPublication.xml' and 'ReqMetaDataExportForPublicationXMLForPubObject.xml' files. In TD14, the required metadata are specified in XML Publishing Plug-in Settings. In addition, though 'ishjobticket.xml' file is generated for compatibility purpose, it not possible to control metadata output as same as LCA.
I recommend that installing TD14 OOB in your environment and confirm these changes.
2. Verify DITA-OT compatibility
The versions of base software of DITA-OT are different between DITA-OT 1.5 in LCA and DITA-OT 2.X/3.X in TD14. And these affect stylesheet compatibility.
- Versions of SAXON- JRE- Ant
I ran into following compatibility issues:
- Some Ant codes did not work properly. I had to modify those codes.- Some stylesheets were not able to launch using Ant. I used the 'dita.bat' to launch them.- Some stylesheets did not work with AdoptOpenJDK. In our site, both AdoptOpenJDK and JDK8 are installed.
3. Modify stylesheets codes to adapt them to latest DITA-OT
In general, preprocess order and its outcome are different depending on versions of DITA-OT. If your styleseets have customized DITA-OT preprocess, you may have to be modify the codes to adapt it to new DITA-OT.
Hope this will help your project.
Naoki Hirai thank you very much! This is indeed very helpful.