DITA CMS Release 4.0: Detailed Release Notes

Transcription

1 DITA CMS Release 4.0: Detailed Release Notes / DITACMS v. 4.0, Build / Copyright 2015 IXIASOFT Technologies. All rights reserved. Last revised: April 22, 2015

2 2 DITA CMS Release 4.0: Detailed Release Notes Table of contents About this document Release notes Update relative path to the mathml3.dtd file 4 Update the path in the DITA CMS configuration 4 Update the path in the Output Generator 5 Update the path in the Web Author 5 Update the index definition for assigned roles and performance issues 6 Fix incorrect trigger name in RemoveProcInsTriggers.xml 7 New feature: Specify a debug address for the Scheduler 8

3 About this document 3 About this document This document describes the new features and bug fixes introduced in this build of DITA CMS Release 4.0.

4 4 DITA CMS Release 4.0: Detailed Release Notes Release notes Update relative path to the mathml3.dtd file The relative path to the mathml3.dtd file was incorrect in the Mathml Domain plugin (org.oasis-open.dita.mathml.doctypes). The path is "../../org.w3c.mathml3/mathml3.dtd" and it should be "../../org.w3c.mathml3/dtd/mathml3.dtd". To fix this issue, you need to update the file in the following three locations: DITA CMS configuration Output Generator Web Author The procedures are provided below. Update the path in the DITA CMS configuration This procedure describes how to update the path to the mathml3.dtd file in the Content Store. 1. Open the TEXTML Administration view. 2. Connect to your server and Content Store. 3. In the repository's /system/plugins/org.oasis-open.dita.mathml.doctypes/dtd/ collection, check out the mathmldomain.mod file and open it with a text editor. 4. Locate the following two lines: PUBLIC "-//W3C//DTD MathML 3.0//EN" "../../org.w3c.mathml3/mathml3.dtd" 5. Change the path in the second line as follows: "../../org.w3c.mathml3/dtd/mathml3.dtd" 6. Save and check in the file. 7. Synchronize the configuration.

5 Release notes 5 Update the path in the Output Generator This procedure describes how to update the path to the mathml3.dtd file in the Output Generator. 1. Open the %OutputGenDir%/data/DITA-OT1.8.5/plugins/org.oasis-open.dita.mathml.doctypes/ dtd/mathmldomain.mod file. 2. Locate the following two lines: PUBLIC "-//W3C//DTD MathML 3.0//EN" "../../org.w3c.mathml3/mathml3.dtd" 3. Change the path in the second line as follows: "../../org.w3c.mathml3/dtd/mathml3.dtd" 4. Save the file. 5. In the %OutputGenDir%/data/%OT_Dir%/ directory, double-click startcmd.bat (Windows) or run startcmd.sh (Linux). 6. At the command prompt, enter: ant -f integrator.xml The integration build runs and you should soon see BUILD SUCCESSFUL. Note: If a message similar to the following is displayed, you can safely ignore it: Unable to locate tools.jar. Expected to find it in C:\Program Files\Java\jre6\lib\tools.jar This message means that you are using a JRE instead of a JDK to run the Output Generator. 7. Close the command window. Update the path in the Web Author This procedure describes how to update the path to the mathml3.dtd file in the Web Author. Note: Perform this procedure only if you are using MathML equations in the Web Author. 1. Open the TEXTML Administration view. 2. Connect to your server and Content Store. 3. In the repository's /system/cms.webauthor/frameworks/ collection, check out the frameworks.zip file. 4. In the frameworks.zip file, open the following file:

6 6 DITA CMS Release 4.0: Detailed Release Notes dita/dita-ot/plugins/org.oasis-open.dita.mathml.doctypes/dtd/mathmldomain.mod 5. Locate the following two lines: PUBLIC "-//W3C//DTD MathML 3.0//EN" "../../org.w3c.mathml3/mathml3.dtd" 6. Change the path in the second line as follows: "../../org.w3c.mathml3/dtd/mathml3.dtd" 7. Save the file. 8. Check in the updated frameworks.zip file. Update the index definition for assigned roles and performance issues You need to update the index definition to solve the following two issues: Active assignments were not showing when assigned to multiple users. A performance issue was reported when indexing large documents (over 12 MB). To solve this issue, you need to update two indexes in the Index Definition document. Updating these indexes will have a major impact on the indexing process, so IXIASOFT recommends that you change the Index Definition document during off hours only. This operation will require a reindexing of the TEXTML Server, which will reduce the performance of the TEXTML Server and may impede user actions (for example, newly created topics will only be searchable using the Advanced Search). To update the indexes: 1. Open the TEXTML Administration perspective. 2. Connect to your server and Content Store. 3. Expand the Content Store node to display the Index Definition branch. 4. Right-click Index Definition and select Check out. 5. Open the Index Definition Document in an XML editor. 6. Look for the following index: <index CUSTOMPROPERTY="True" NAME="assigned_roles" SYNC="True">... </index>

7 Release notes 7 7. Change the contents of the index to the following: <index CUSTOMPROPERTY="True" NAME="assigned_roles" SYNC="True"> <!-- System index required by the DITA CMS --> <stringindex KEEPEXTRACTEDVALUES="True"> <elements> <element DEPTH="INFINITE" XPATH="for $e in //assignment return concat($e/@role, ' ; ', $e, ' ; ', //status)"/> </elements> </stringindex> </index> 8. Look for the following index: <index NAME="tags">... </index> 9. Change the contents of the index to the following: <index NAME="tags"> <stringindex KEEPEXTRACTEDVALUES="True"> <elements> <element DEPTH="INFINITE" XPATH="if (/*[contains(@class, ' project/project ') or contains(@class, ' imagemeta/imagemeta ') or contains(@class, ' formatted/formatted ') or contains(@class, ' resourcemeta/resourcemeta ') or contains(@class, ' multistream/multistream ') or contains(@class, ' resourcepkg/map ')]) then ('') else distinct-values(for $e in (//*) return local-name($e))"/> </elements> </stringindex> </index> 10. Save, close, and check in the index definition document. Fix incorrect trigger name in RemoveProcInsTriggers.xml An incorrect trigger name in the RemoveProcInsTriggers.xml file prevents processing instructions from being removed. To solve this issue: 1. Open the TEXTML Administration view. 2. Connect to your server and Content Store. 3. In the repository's /system/conf/ collection, check out the RemoveProcInsTriggers.xml file and open it with a text editor. 4. Locate the following line: <trigger name="xmetalchangetracking"> 5. Change the trigger name to "Clean Processing Instructions".

8 8 DITA CMS Release 4.0: Detailed Release Notes For example: <trigger name="clean Processing Instructions"> Note: The trigger name must match the name assigned to the com.ixiasoft.cms.triggers.removeprocins trigger in the /system/conf/triggers.xml file. By default, this name is "Clean Processing Instructions". If you changed the name of this trigger in the /system/conf/triggers.xml file, specify this name instead. 6. Save and check in the file. 7. Synchronize the configuration. New feature: Specify a debug address for the Scheduler You can specify a debug address when configuring the Scheduler. This allows you to send all notification s to this debug address until you are satisfied with your configuration. To specify a debug address: 1. Open the %SchedulerDir%/conf/wrapper.conf file. 2. In the Java Additional Parameters section, add the following parameter after the Kerberos parameters: wrapper.java.additional.3=-dixia.postmaster.debug. =your @acme.com Where your @acme.com is the where notifications should be sent during your configuration testing. When you specify this parameter, notifications are not sent to real users. For example: # Java Additional Parameters wrapper.java.additional.1=-djava.security.krb5.conf=../conf/krb5.ini wrapper.java.additional.2=-djava.security.auth.login.config=../conf/login.conf wrapper.java.additional.3=-dixia.postmaster.debug. =test_ @ixiasoft.com 3. Save and close the file. 4. Restart the Scheduler.