FCS Settings for C2D Files

On FCS server, ensure the folders markup and xref with their content are present.

The folders and thier content is present in the <Application server Loc>\webapps\<Application>\integrations\c3d folder. The folders are available on the MCS server machine after C2D is installed.

If they are not already present in the FCS application, these folders and their content can be copied from the ENOVIA installation on MCS server machine from the following locations:

<ENOVIA Live Collaboration Server Install Location>\STAGING\ematrix\integrations\c3d\markup
<ENOVIA Live Collaboration Server Install Location>\STAGING\ematrix\integrations\c3d\scripts
<ENOVIA Live Collaboration Server Install Location>\STAGING\ematrix\integrations\c3d\xref

Ensure the following JAR files are present in the application's WEB-INF\lib folder on the FCS:

The JAR files are available on the MCS server machine after C2D is installed.

```
framework.jar
```
```
avjnlpservlet.jar
```
```
ENOC3DConnector.jar
```
```
log4j-api.jar
```
```
log4j-core.jar
```
```
log4j-web.jar
```
```
vuelinkcore.jar
```
```
vuerdvservlet.jar
```
```
vueservlet.jar
```
```
ENOViewerIntegrationFramework.jar
```
```
ENOCoreIntegrationFramework.jar
```
```
owasp-esapi-2.1.0.jar
```
```
commons-fileupload-1.2.2.jar
```
```
commons-io-1.3.2.jar
```

If they are not already present in the FCS application, you have to copy them from the ENOVIA installation on MCS server machine from the following location, <ENOVIA Live Collaboration Server Install Location>\STAGING\ematrix\classes.

Ensure the following property files are present in the application's WEB-INF\classes folder on the FCS:

These property files are available on the MCS server computer after C2D is installed.

```
ESAPI.properties
```
```
AvESAPI.properties
```

c3dIntegrationStringResource_deNative.properties

c3dIntegrationStringResource_de.properties

c3dIntegrationStringResource_en.properties

c3dIntegrationStringResource_frNative.properties

c3dIntegrationStringResource_fr.properties

c3dIntegrationStringResource_itNative.properties

c3dIntegrationStringResource_it.properties

c3dIntegrationStringResource_jaNative.properties

c3dIntegrationStringResource_ja.properties

```
c3dIntegrationStringResource.properties
```

c3dIntegrationStringResource_zh_CNNative.properties

c3dIntegrationStringResource_zh_CN.properties

If they are not already present in the FCS application, you have to copy the property files from the ENOVIA installation on MCS server machine from the following location, <ENOVIA Live Collaboration Server Install Location>\STAGING\ematrix\properties.

The following servlet and servlet mappings should be added at the appropriate location in the web.xml file on the FCS:

<servlet id="c3dVueServlet"> 
<servlet-name>VueServlet</servlet-name> 
<servlet-class>com.cimmetry.servlet.VueServlet</servlet-class>
<init-param>
<param-name>JVueServer</param-name>
<param-value><AutoVue server name/AutoVue server IP>:<AutoVue server port></param-value> 
</init-param> 
</servlet> 
<servlet id="c3dVueJNLPServlet">
	<servlet-name>VueJNLPServlet</servlet-name>
	<servlet-class>com.cimmetry.servlet.VueJNLPServlet</servlet-class>
	<init-param>
		<param-name>URL-Dir</param-name>
		<param-value>/integrations/c3d/scripts</param-value>
	</init-param>
	<init-param>
		<param-name>Cookies</param-name>
		<param-value>JSESSIONID;</param-value>
	</init-param>
</servlet>
<servlet id="c3dVueRDVServlet">
      <servlet-name>VueRDVServlet</servlet-name>
      <servlet-class>com.cimmetry.servlet.VueRDVServlet</servlet-class>
</servlet>
<servlet id="c3dconnectorservlet">
	<servlet-name>C3DControllerServlet</servlet-name>
	<servlet-class>com.ds.enovia.c3d.controller.C3DControllerServlet</servlet-class>
		 <init-param>
		 	<param-name>DecryptionAlgorithm</param-name>
		 	<param-value>AES</param-value>
		 </init-param>
		 <init-param>
		 	<param-name>KeyAgreementAlgorithm</param-name>
		 	<param-value>EC</param-value>
		 </init-param> 
<init-param> 
<param-name>log4jInitFile</param-name> 
<param-value>F:/Tomcat/apache-tomcat-6.0.24/webapps/enovia/WEB-INF/lib/log4j.properties</param-value> 
</init-param> 
<init-param>
<param-name>dms.context</param-name>
<param-value>com.ds.enovia.c3d.controller.C3DControllerContext</param-value> 
</init-param>
<init-param>
<param-name>dms.action.Open</param-name> 
<param-value>com.ds.enovia.c3d.controller.actions.C3DOpenAction</param-value> 
</init-param> 
<init-param>
<param-name>dms.action.GetProperties</param-name>
<param-value>com.ds.enovia.c3d.controller.actions.C3DGetPropActionManager</param-value>
</init-param>
<init-param>
<param-name>dms.action.Download</param-name> 
<param-value>com.ds.enovia.c3d.controller.actions.C3DDownloadAction</param-value> 
</init-param> 
<init-param> 
<param-name>dms.action.Save</param-name> 
<param-value>com.ds.enovia.c3d.controller.actions.C3DSaveAction</param-value>
</init-param>
<init-param> 
<param-name>dms.action.Delete</param-name>
<param-value>com.ds.enovia.c3d.controller.actions.C3DDeleteAction</param-value>
</init-param> 
<init-param>
<param-name>dms.action.SetProperties</param-name>
<param-value>com.ds.enovia.c3d.controller.actions.C3DSetPropAction</param-value>
</init-param> 
<init-param> 
<param-name>dms.getprops.PK</param-name> 
<param-value>com.cimmetry.vuelink.propsaction.GetPropPK</param-value>
</init-param>
<init-param>
<param-name>dms.getprops.CSI_DocDateLastModified</param-name> 
<param-value>com.ds.enovia.c3d.controller.actions.handlers.C3DGetDocLastModDatePropHandler</param-value>
</init-param> 
<init-param> 
<param-name>dms.getprops.CSI_Renditions</param-name> 
<param-value>com.ds.enovia.c3d.controller.actions.handlers.C3DGetDocCSIRenditionsPropHandler</param-value>
</init-param>
<init-param> 
<param-name>dms.getprops.CSI_DocSize</param-name>
<param-value>com.ds.enovia.c3d.controller.actions.handlers.C3DGetDocSizePropHandler</param-value> 
</init-param> 
<init-param>
<param-name>dms.getprops.CSI_DocName</param-name>
<param-value>com.ds.enovia.c3d.controller.actions.handlers.C3DGetDocNamePropHandler</param-value>
</init-param>
<init-param>
<param-name>dms.getprops.CSI_ListItems</param-name>
<param-value>com.ds.enovia.c3d.controller.actions.handlers.C3DListItemsPropHandler</param-value>
</init-param> 
<init-param> 
<param-name>dms.getprops.GUI</param-name>
<param-value>com.ds.enovia.c3d.controller.actions.handlers.C3DGetGUIPropHandler</param-value> 
</init-param>
<init-param> 
<param-name>dms.getprops.CSI_Search</param-name>
<param-value>com.ds.enovia.c3d.controller.actions.handlers.C3DGetPropCSI_Search</param-value> 
</init-param> 
<init-param>
<param-name>dms.getprops.CSI_Markups</param-name>
<param-value>com.ds.enovia.c3d.controller.actions.handlers.C3DMarkupHandler</param-value> 
</init-param>
<init-param> 
<param-name>dms.getprops.CSI_XREFS</param-name> 
<param-value>com.ds.enovia.c3d.controller.actions.handlers.C3DGetPropCSI_XREFS</param-value> 
</init-param> 
<init-param> 
<param-name>dms.getprops.CSI_ListAllProperties</param-name>
<param-value>com.ds.enovia.c3d.controller.actions.handlers.C3DListAllPropertiesHandler</param-value> 
</init-param>
<init-param>
<param-name>dms.getprops.Default</param-name> 
<param-value>com.ds.enovia.c3d.controller.actions.C3DGetPropActionManager</param-value> 
</init-param>
<init-param>
<param-name>dms.getprops.CSI_Versions</param-name>
<param-value>com.ds.enovia.c3d.controller.actions.handlers.C3DCSI_VersionsHandler</param-value>
</init-param> 
<init-param> 
<param-name>dms.getprops.CSI_MarkupPolicy</param-name> 
<param-value>com.ds.enovia.c3d.controller.actions.handlers.C3DCSI_MarkupPolicy</param-value>
</init-param> 
<init-param> 
<param-name>RenditionFormats</param-name>
<param-value>PCRS_TIF;PCRS_GP4;PCRS_EPS;PCRS_PCL;PCRS_PCX;PCVC_PDF;PCRS_RLC;PCRS_BMP;CSI_META</param-value> 
</init-param> 
<init-param> 
<param-name>StreamingFileCheckin</param-name> 
<param-value>true</param-value> 
</init-param> 
<init-param>
<param-name>ValidateStreamingFile</param-name> 
<param-value>true</param-value> 
</init-param> 
<init-param> 
<param-name>properties</param-name>
<param-value>/WEB-INF/classes/csiLaunch.properties</param-value> 
</init-param> 
<init-param> 
<param-name>dms.getprops.CSI_IsMultiContent</param-name>
<param-value>com.ds.enovia.c3d.controller.actions.handlers.C3DGetDocIsMultiContentPropHandler</param-value>
</init-param> 
<init-param> 
<param-name>dms.backend</param-name> 
<param-value>com.ds.enovia.c3d.controller.C3DBackendImp</param-value>
</init-param>
<init-param>
<param-name>CSI_MarkupPolicyDefLocation</param-name>
<param-value>/integrations/c3d/markup/MarkupPolicy.xml</param-value> 
</init-param>
<init-param>
<param-name>CSI_IntellistampDefLocation</param-name>
<param-value>/integrations/c3d/markup/dmstamps.ini</param-value> 
</init-param> 
<init-param>
<param-name>CSI_BlankMarkupLocation</param-name> 
<param-value>/integrations/c3d/markup/BlankMarkup.mrk</param-value>
</init-param> 
<load-on-startup>1</load-on-startup> 
</servlet>
<servlet-mapping id="c3dVueServletmapping"> 
<servlet-name>VueServlet</servlet-name> 
<url-pattern>/VueServlet</url-pattern> 
</servlet-mapping>
<servlet-mapping id="c3dVueJNLPServletmapping">
	<servlet-name>VueJNLPServlet</servlet-name>
	<url-pattern>/VueJNLPServlet</url-pattern>
</servlet-mapping>
<servlet-mapping id="c3dVueRDVServletmapping">
	<servlet-name>VueRDVServlet</servlet-name>
	<url-pattern>/VueRDVServlet</url-pattern>
</servlet-mapping>
<servlet-mapping id="c3dconnectorservletmapping">
<servlet-name>C3DControllerServlet</servlet-name>
<url-pattern>/servlet/C3DControllerServlet</url-pattern> 
</servlet-mapping>

Specify the value of <AutoVue server name/AutoVue server IP> as either the name or the IP of the machine on which AutoVue server is running.

Specify the value of <AutoVue server port> as the port of the AutoVue server on the above mentioned machine.

Ensure the following for modifications in the web.xml for multiple FCS-MCS combinations:


Setup	Configuration Settings
FCS URL and MCS URL are the same. (MCS FCS)	The web.xml on the MCS machine is considered.
FCS URL and MCS URL are different. (MCS FCS)	The web.xml on the FCS machine is considered. If MCS FCS, there can be a common AutoVue server, if both MCS and FCS are in the same network. If MCS and FCS are not in the same network, then you must install AutoVue server on the FCS computer network. Install the AutoVue Server either on a dedicated machine or on the MCS/FCS machine the server will connect to.

To validate and troubleshoot CD integration in an FCS setup:

When MCS = FCS and both (MCS and FCS) are using the same Oracle AutoVue server, run the following URL from a web browser:
http://<ENOVIA MCS Server Name OR ENOVIA MCS Server IP>:<Application Server port>/<ENOVIA MCS application name>/VueServlet
When MCS FCS and the FCS is pointing to an Oracle AutoVue server in its LAN, run the following URL from a web browser:
http://<ENOVIA FCS Server Name OR ENOVIA FCS Server IP>:<Application Server port>/<ENOVIA FCS application name>/VueServlet

The details about the Oracle AutoVue server such as, AutoVue server version, build and other details are displayed.