Siebel Correspondence, Proposals, and Presentations Guide > Document Server >

Configuring the Document Server

To configure the Document Server, perform the following optional tasks:

• Enabling HTML Generation for Correspondence
• Configuring Application Recycle Period
• Routing Requests to One Document Server
• Enabling Additional Logging

Enabling HTML Generation for Correspondence

By default, correspondence is saved only in document format, not in HTML format. In the My Correspondence Requests view, the View HTML command is unavailable, and the user cannot view the correspondence in HTML format.

The DocumentServerViewHTML server parameter specifies if the Document Server generates HTML versions of documents. The default value is FALSE. By default, the Document Server generates documents only in their native format, and not in HTML. To enable the user to display correspondence in HTML format, you must edit the DocumentServerViewHTML parameter to the value TRUE instead of FALSE. Any documents generated after you enable the parameter are saved in both formats.

When you generate an HTML document, a copy of the generated document is created in HTML and stored in the Siebel File System. This process can affect performance, and it increases the storage space required in the Siebel File System. The clarity of the HTML document depends on the ability of your Microsoft Office application to translate its native format into HTML.

To enable HTML generation for correspondence

1. Start the Server Manager.
2. Enter the following command:

   srvrmgr> change param DocumentServerViewHTML=True for comp DocServer

   NOTE:  You can also change parameters in the Administration - Server Configuration screen. For more information, see Siebel System Administration Guide.

Configuring Application Recycle Period

You use the MSWordLiveCount parameter to control how often the Microsoft Office applications are restarted.

You can set each parameter to a positive integer that specifies the number of documents to be processed before the corresponding Microsoft Office application is shut down and restarted. A value of 0 (the default) indicates that the applications are not shut down. If you set the parameter value to any integer other than 0, and the Document Server fails to launch, the corresponding application is shut down and then restarted again.

To configure the application recycle period

1. Start the Server Manager.
2. To change the application recycling period for Microsoft Word, which is used for correspondence and proposals, enter the following command:

   srvrmgr> change param MSWordLiveCount=5 for comp DocServer

3. To change the application recycling period for Microsoft PowerPoint, which is used for presentations, enter the following command:

   srvrmgr> change param MSPPLiveCount=5 for comp DocServer

Routing Requests to One Document Server

If you run multiple Document Servers within the same enterprise, then the server infrastructure routes document requests to different Document Servers to achieve load balancing.

However, you can specify that all requests are routed to one Document Server. For example, you can specify one Document Server to help diagnose a server problem.

To route all requests to one Document Server

1. Start the Server Manager.
2. Enter the following command:

   srvrmgr> change param DocumentServerName=DocSrvr1

Enabling Additional Logging

You can enable additional logging for debugging purposes.

Event logging writes events to the log file using the log level for each event type. The number you specify indicates the filtering level for logging. The default value is 3. This value means that events with a level of 1, 2, or 3 are logged, while events with a level of 4 or 5 are suppressed. Setting the filtering level to 5 means that all events are logged. For more information about event logging, see Siebel System Monitoring and Diagnostics Guide.

To enable additional logging

1. Start the Server Manager.
2. Enter the following command for each event type for which you want to enable additional logging:

   srvrmgr> change evtloglvl event_alias_name=level for component Docserver

   where:

   • event_alias_name is one of the following event types:
     • eDocDocServerEvent. The Document Server business service is the high-level entry point for document generation. This business service passes document generation requests to the code that handles correspondence, proposals, or presentations. Set the logging to eDocDocServerEvent to provide high-level information about the incoming document generation request.
     • eDocDocEngineEvent. Because a proposal can have many components, the proposal generation code can be called many times. The Document Engine component calls the proposal generation code as often as necessary to generate each of these components, and then merges them together. Set the logging to eDocDocEngineEvent to trace events related to calling the proposal generation code and to collating the final proposal document.
     • eDocCorrespEvent. Correspondence generation is the process of performing the mail merge from the Siebel CRM application into the predefined Microsoft Word document. Set the logging to eDocCorrespEvent to trace the mail merge process between Siebel CRM and Microsoft Word.
     • eDocProposalEvent. Proposal generation is the process of merging fields from the Siebel CRM application into the predefined Microsoft Word document. Set the logging to eDocProposalEvent to trace the merge process between Siebel CRM and Microsoft Word.
     • eDocPresentationEvent. Presentation generation is the process of merging fields from the Siebel CRM application into the predefined Microsoft PowerPoint presentation. Set the logging to eDocPresentationEvent to trace the merge process between Siebel CRM and Microsoft PowerPoint.
   • level is a number that indicates the log level for the event type.