Several troubleshooting aids are available to help evaluate Content Server pages as they are used. This section discusses three broad types of troubleshooting aids:
Syntax errors and other mistakes in component files or dynamic server pages can cause errors in the Content Server. If the Content Server fails, it reports the error in the following locations:
If you run the Content Server from a command prompt, you can view the error in the console window.
If you can log in to the Content Server and display the Admin Server page, you can view the Content Server log by selecting the Content Server and then clicking the View Server Output link.
You can view the Content Server log files in the DomainHome/ucm/cs/weblayout/groups/secure/logs/ directory.
The IsJava setting displays the local data of a Content Server Web page.
In a Web browser, add the following code in the Address box to the end of the page's URL:
&IsJava=1
On a template page or in an include, use the following code:
<$IsJava=1$>
The IsDebugTrace setting displays a tree structure view of all includes being called on a Content Server Web page. The debug trace appears at the bottom of the Web page.
In a Web browser, add the following code in the Address box to the end of the page's URL:
&IsDebugTrace=1
On a template page or in an include, use the following code:
<$IsDebugTrace=1$>
To place a marker in the script debug trace, place the following code at the point where you want to see a value or perform a step:
<$trace(marker code)$>
For example, you can use the following code to insert the current user name in the debug trace (the eval function must be used to evaluate Idoc Script):
<$trace(eval("The user name is "<$UserName$>)$>
IsJava and IsDebugTrace are discussed in detail in the Oracle Fusion Middleware Idoc Script Reference Guide.
Three configuration settings enable you to view the loading of resources when you run the Content Server from a command line. Set any of these variables equal to 1 in the IntradocDir/config/config.cfg file:
TraceResourceLoad logs all resources loaded, resource overrides, resource conflicts, and resource merges.
TraceResourceOverride logs when a system resource is overridden by a component resource or a component resource is loaded twice.
TraceResourceConflict logs when a system resource is overridden twice by component resources.
These configuration settings are discussed in detail in the Oracle Fusion Middleware Idoc Script Reference Guide.
The following is an example of the command line output when TraceResourceLoad=1.
Loading Java Resources Loading ConflictTester Component Loading ConflictTester2 Component Loading Compression Component Merging into Filters *MERGE* [validateStandard, compression.ConversionParamsFilter, null, 1] Loading Html Resources Loading System Resource c:/intradoc/shared/config/resources/upper_clmns_map.htm ColumnTranslation Loading System Resource c:/intradoc/shared/config/resources/indexer.htm IndexerQueryTable IndexerStatesTable IndexerTransitionsTable DefaultIndexerCycles Loading System Resource c:/intradoc/shared/config/resources/std_page.idoc std_html_head_declarations std_definitions std_html_head_definition_declarations std_page_variable_definitions … Loading System Resource c:/intradoc/shared/config/resources/std_docrefinery.htm AdditionalRenditionsSource DocumentConversions ConversionSteps Loading ConflictTester Component c:/intradoc/custom/ConflictTester/resources/conflicttester_resource.htm conflict_tester_include ConflictTester_Table Loading ConflictTester2 Component c:/intradoc/custom/ConflictTester2/resources/conflicttester_resource.htm *OVERRIDE* conflict_tester_include ***CONFLICT*** ConflictTester_Table Loading Compression Component c:/intradoc/custom/Compression/Compression_resource.htm *OVERRIDE* searchapi_result_definitions *OVERRIDE* searchapi_thumbnail_result_doc_href_start *OVERRIDE* searchapi_result_table_content_begin compression_thumbnail_img Loading Compression Component c:/intradoc/custom/Compression/Compression_handlers.htm CompressionHandlers Merging ConflictTester_Templates into IntradocTemplates *MERGE* HOME_PAGE Merging ConflictTester_Templates into IntradocTemplates *MERGE* HOME_PAGE Merging CompressionIntradocTemplates into IntradocTemplates *MERGE* COMPRESSION_IMAGE_INFO Merging CompressionHandlers into ServiceHandlers *MERGE* [FileService, compression.CompressionFileServiceHandler, 100] *MERGE* [FileService, DocCommonHandler, 100] *MERGE* [DocService, compression.CompressionFileServiceHandler, 100] …