Sample Configuration Files for the ClearTrial Clinical Trial Management System Connector

The connector configuration process requires the following files:

• ctmsProtocolBaselinePlan.properties

  This file contains mappings between the Protocol ID in Siebel Clinical and the ClearTrial Baseline Plan ID in ClearTrial Track. You can create any number of mappings in this file. In each execution, the connector imports the actual data for all the Protocol IDs in this file into ClearTrial Track.

  The ClearTrial Baseline Plan ID is the ID of the plan that you select as the baseline plan for a study.The baseline plan is the modeled plan with acceptable milestones and a budget. Table A-3 shows an example of the mapping in this file.

Table A-3 Example of the Mapping in the File

Siebel Clinical	ClearTrial Track
88-3CDYK	56529
88-3CIEN	57830

• application.properties

  This file contains connection and communication parameters for the integration between Siebel Clinical and ClearTrial Track.

  Table A-4 describes the parameters that you must define in this file.

Table A-4 Parameters for application.propertie Files

Parameter	Description
proxy.server=myproxy.com	The proxy address that the server for the connector requires to access the internet. For a proxy server, this parameter is required.
proxy.port=80	The port on which the proxy listens. The default port is 80. For a proxy server, this parameter is required.
ctms.server=myCtmsServer .com	The fully qualified domain name of the middle-tier application server for Siebel Clinical. This parameter is required. You must specify this parameter even if the connector is installed and executed on the same server as Siebel Clinical.
ctms.port=80	The port on which the middle-tier application server for Siebel Clinical listens for the ASI SOAP (Application Service Interface Simple Object Application Protocol) Web services calls. The default port is 80. You must specify this parameter only if the Siebel Clinical listens on a different port.
ctms.protocol=http	A value that determines if the Siebel Clinical server is running in secure mode (https) or non secure mode (http). The default value is http.
ctms.environment=eai_enu	A value that determines the locale of the Siebel Clinical instance. The default value is eai_enu.
ctms.connection.timeout. millis=60000	The timeout (in milliseconds) after which the connector declares a connection failure to the middle-tier application server for Siebel Clinical. The default value is 60 seconds or 60,000 milliseconds. You can use this parameter if the network is slow. This parameter is not required.
ctms.read.timeout. millis=60000	The timeout (in milliseconds) after which the connector declares a read failure for the request to the middle-tier application server for Siebel Clinical. The default value is 60 seconds or 60,000 milliseconds. You can use this parameter if the network is slow. This parameter is not required.
ctms.page.size=10	The number of pages requested from Siebel Clinical in each request to the ASI SOAP Web services. The default value is 10. You can use this parameter if large data sets (SOAP XML content) are extracted in each request, which can lead to broken pipe type errors. This parameter is not required.
cleartrial.wsapi.connection .timeout.millis=60000	The timeout (in milliseconds) after which the connector declares a connection failure to the ClearTrial Web services API. The default value is 60 seconds or 60,000 milliseconds. You can use this parameter if the network is slow. This parameter is not required.
cleartrial.wsapi.read.timeout.millis=60000	The timeout (in milliseconds) after which the connector declares a read failure for a request to the ClearTrial Web services API. By default, the value is 60 seconds or 60,000 milliseconds. You can use this parameter if the network is slow. This parameter is not required.

• locationMap.properties

  This file provides mappings between the region names in Siebel Clinical and location names in ClearTrial Track. In ClearTrial Track, the location names are fixed. In Siebel Clinical, a few region names are provided at installation. However, you can create custom region names.

  The locationMap.properties file must contain the region-to-location mapping for every unique region across all protocols with data imported into ClearTrial Track.

  For example, Protocol 1 has region names of Switzerland, Swiss, BELGIUM, and US of A. Protocol 2 has region names of USA, Belgium, and Switzerland. The corresponding location names in ClearTrial Track are Switzerland, Belgium, and USA. In this example, the locationMap.properties file must contain the following information:

  Switzerland=Switzerland Swiss=Switzerland BELGIUM=Belgium Belgium=BelgiumUSA=USAUS\ of\ A=USA
  

  In this information, the left value is the region name in Siebel Clinical and the right value is the location name in the ClearTrial Track. Region and location names are case sensitive. If the region name contains spaces, then you must prefix the spaces with a backward slash (\). For example, if the region name is US of A, then it must appear as US\ of\ A.

  You do not have to configure the connector to recognize the following mappings:

  Australia=Australia Brazil=Brazil France=France Germany=Germany Japan=JapanUK=UKUSA=USA
  

• ctmsLabel.properties

  This file matches the status customization in Siebel Clinical. For example, the default status for the site initiation event is Initiated. However, you can customize this status to Approved. Both of the statuses can exist for the integrated protocols.

  In the this example, the ctmsLabel.properties file has the following content:

  site.approval.status=Initiated,Approved subject.enrollment.status=Enrolled
  

  The logic for the status of the initiation event also applies to the status of the subject enrollment.