FCS Parameters

When you view a .doc, .docx, .xls, .xlsx, .ppt, and .pptx file using the View icon in IE, the file is opened inside the browser window. If this window remains open, you will not be able to view or download any other files because IE will bring you back to the window that is already open. This is a limitation in IE and the work-around is to change the mime type field for each file type. For example, for .xls files, change:

<mime-mapping id="MimeMapping_2">
   <extension>xls</extension>
   <mime-type>application/vnd.ms-excel</mime-type>
</mime-mapping>

To:

<mime-mapping id="MimeMapping_2">
   <extension>xls</extension>
   <mime-type>application/octet-stream</mime-type>
</mime-mapping>

This section describes FCS settings that allow you to configure ticket and receipt cleanup, and ticket expiration. Values are based on your usage patterns. If required, you can also change the URL used for communication between FCS and the MCS, and you can enable FCS to operate in two different domains with SSO.

To set how long a ticket is valid (i.e. the length of time between when a ticket is issued and when it reaches the FCS server), add the following setting on your FCS server:

<context-param id="ContextParam_19">
   <param-name>ematrix.max_ticket_age</param-name>
   <param-value>600</param-value>
</context-param>

For ticket expiration time-stamping, the receiver has the actual clock value of the sender. Prior to evaluating the validity of the ticket, the time-stamp on the receiver's end is adjusted to the sender's time, thus making time-stamping impervious to differences in time zones between a receiver and sender.

The default is 600 seconds (10 minutes). You should increase this time only if your network is very slow.

To set the number of tickets to process on your FCS server before deleting tickets from RAM:

<context-param id="ContextParam_19">
   <param-name>ematrix.ticket_cleanup_count</param-name>
   <param-value>1000</param-value>
</context-param>

The default is 1000. If your server is not very busy (e.g. processing approximately 100 documents per hour), you might decrease this number.

To set the number of receipts to process on your MCS before deleting receipts from RAM:

<context-param id="ContextParam_19">
   <param-name>ematrix.receipt_cleanup_count</param-name>
   <param-value>1000</param-value>
</context-param>

The default is 1000. If your server is not very busy (e.g. approximately 100 documents per/hour), you might decrease this number.

This URL value overrides the MCS URL.

To enable UTF8 file name encoding in zip files:

<context-param id="ContextParam_7">
   <param-name>MX_ZIPSTREAM_ENABLE_UTF8</param-name>
   <param-value>true</param-value>
</context-param>

You can also set this variable in the framework.properties file for each FCS:

MX_ZIPSTREAM_ENABLE_UTF8=true

The unzip software must also support UTF8 encoding.

MCS uses its own URL (which is used to request the JSP page producing the ticket) to compute the connect string for an FCS to communicate with the MCS. To change the URL for the MCS, for example, when an FCS needs to communicate with the MCS on a different port or with a different protocol (https vs. http):

<context-param id="ContextParam_19">
   <param-name>ematrix.mcs.contextConnect</param-name>
   <param-value>URL</param-value>
</context-param>

The following setting allows a cookie to be sent containing the login credential between two different domains in an FCS environment using SSO:

<context-param id="ContextParam_19">
   <param-name>ematrix.mcs.packageCookies</param-name>
   <param-value>TRUE</param-value>
</context-param>

The following parameters can be set to configure use of image caching in ENOVIA apps.

ematrix.maxImageCookieLength—Can be added to increase the total allowable cookie size, setting the threshold for when the system must use the MCS for delivering images instead of the faster FCS. For example, the parameter could be:

<context-param id="ContextParam_#">
   <param-name>ematrix.maxImageCookieLength</param-name>
   <param-value>1960</param-value>
</context-param>

BACKGROUND: The image URL encodes various information about the image, including any cookies that were presented by the browser to the MCS. If the session cookie string is too large, the resulting image URL will exceed the maximum URL length supported by the browser (2048 bytes on Internet Explorer). This is most likely to occur when a configuration involves many cookies for the session (SSO, web server proxies, etc.). If the total length of the cookie string exceeds this value, 3DSpace generates a URL that is addressed to the MCS for image delivery (omitting the cookies) rather than generating an image URL that exceeds 2048 bytes.

You can increase the total allowable cookie size by adding this setting to a web.xml.part file that will be built into the web.xml file for the MCS server. By default the maximum cookie length is 1960. With this setting in place, the system will send the image request to the MCS if the total length of all cookies is larger than 1960. The default should be fine in most circumstances, but you may want to increase it if you are in an environment that may have many cookies and Mozilla is the browser standard.

ematrix.isContentDispositionEnabledForImages—Can be added for WebLogic implementations to allow image files to be saved in the browser. For example, the parameter could be:

<context-param id="ContextParam_#">
   <param-name>ematrix.isContentDispositionEnabledForImages</param-name>
   <param-value>True</param-value>
</context-param>

BACKGROUND: By default, the image service sets both Cache-Control and Content-Disposition in its headers. The Cache-Control header is set to allow the browser to cache the image. The Context-Disposition header is set to allow the browser to save the image with the file name of the original file. WebLogic considers it an error to set both headers. Setting ematrix.isContentDispositionEnabledForImages to false on the FCS server suppresses the Content-Disposition header setting, which means that saved image files are named "DynamicImage".