Troubleshooting PTC Arbortext Content Delivery
The following sections describe tools available for troubleshooting and debugging in the Task Manager and the Publication Manager.
Task Manager Tools
After transformation, use the following resources to help troubleshoot and debug any issues:
• Task Manager Flow Monitoring
• Log files
Most logs are located in the HOME/Log/System/Log directory. The following logs are available:
◦ Configurator_logs – Folder containing logs for the Configurator.
◦ sce.log – Logs related to SDK Queries and results.
◦ enigma.log – Flow and business logic logs.
◦ coreServer.log – Core Specific logs.
◦ coreCMIServer.log – CMI Server specific logs (for core debug purposes).
◦ Trace.log
The Task Manager log is located at HOME/Data/Work/Applications/TaskManager/Work/TaskReport.
In order to understand what was loaded to the repository, navigate to the following directory:
Data\Data\Titles
Copy the repository to a different directory, and then run a check of the repository.
 |
You should never run checks on the real repository that is serving an installation.
|
Fake Path of Descriptor File Selected when Creating New Task
When a new task is created in the Task Manager, a fake path of the descriptor file gets selected and an error message occurs. To resolve this issue, use one of the following methods:
• From Internet Explorer, navigate to > > > . Find the Include local directory path when uploading files to a server setting and select Enable.
OR
• Add your site to the list of trusted sites in Internet Explorer. Navigate to > > . Click Trusted Sites and click Sites. In the Trusted Sites window, enter the name of the site and click Add.
|
|
If there is an HTTPS validation error, deselect the Require server verification (https:) for all sites in this zone checkbox.
|
Task Manager Data Loading Failure
If you have an issue loading data using the Task Manager, you might need to change the Java heap size for JBoss. For the Publisher server, it is recommended to set the heap size to a minimum of 4 GB and a maximum of 12 GB. For the Viewer servers it is recommended to set the heap size to a minimum of 4 GB and a maximum of 8 GB.
Task Manager Data Loading Failure with Microsoft SQL Server Database
If you have an issue loading data using the Task Manager and you are using the Microsoft SQL Server database, check the Task Manager log for an error similar to the following:
com.microsoft.sqlserver.jdbc.SQLServerException: Snapshot isolation transaction failed in database 'testdb' because the object accessed by the statement has been modified by a DDL statement in another concurrent transaction since the start of this transaction. It is disallowed because the metadata is not versioned. A concurrent update to metadata can lead to inconsistency if mixed with snapshot isolation.
In this case, database indexing running in parallel caused the issue. You should resume the data loading task.
Task Failure
When tasks fail, it does not abort successfully due to server shutdown, networking issues or any other server failure during publishing or loading a bundle. Complete the following steps:
1. Let all task that are running for other segments complete, then restart all the services on Publisher and Viewer machine, like:
a. Core CMI Server
b. CoreServer
c. JBoss Server
|
|
Restart the services to let the automated server start the recovery process, recover the failed task and the remainings from system.
|
2. When the system is restarted, navigate to <enigma.log.home>/System/Log/enigma.log and search for the following line Action RollbackTasksCommand has finished successfully. If found, the automatic server startup recovery is successful.
3. Navigate to <engima.work.home>/DCTM_Output folder and delete the contents of the folder.
4. Navigate to <enigma.work.home>/DCTM_Output folder and delete the contents of the folder.
5. Navigate to <data.home>/Titles/<Segment_Name>/Data/Core/Tr folder. If you see any remainings after aborting the task in these two <data.home>/Titles/<Segment <data.home>/Titles/<Segment_Name>/Data/Core/Tr folders, then complete the following steps:
a. Stop the CoreServer, CoreCMIServer and JBoss Server services again.
b. If there is no delta file in <data.home>/Titles/<Segment.Name>/Data/Core/Delta but there is a Tr present in the <data.home>/Tiles/<Segment.Name>/Data/Core/TR folder, then take a backup of the Tr file and restart the publishing task.
c. If there is a delta file present in <data.home>/Titles/<Segment.Name>/Data/Core/Delta folder, but if no Tr file is present in <data.home>/Tiles/<Segment.Name>/Data/Core/TR folder, no need to take any backup. You can delete the delta file and restart the failed publishing task.
d. Navigate to <enigma.config.home>/System/Config/Core/corePublications.xml file. The Preload attribute value for all the repositories must be YES. If the Preload=NO, change it to Preload=YES. The value for MaxDeltaLevel property is 1.
6. Navigate to <enigma.config.home>/System/Config/Core/coreCMIPublications.xml file, thePreload attribute value for all repositories should be Preload=NO except for CoreUtils.
7. Navigate to <enigma.config.home>/Titles/<Segment_Name>/Config/BusinessLogic/runtimeProperties.conf.xml
file. The contents of the file should have the values as shown in the below image:
| | Repeat this for all the segments present in <enigma.config.home>/Titles file. |
8. Navigate to <enigma.config>/Tiles/<Segment_Name>Config/Presentation/runtimeProperties.conf file. The contents of the file should have the values as shown in the below image:
| | Repeat this for all the segments present in <enigma.config.home>/Titles file. |
9. Start the following services in the following order:
a. Core
b. CoreCMI
c. JBoss