Skip Headers
Siebel CRM Siebel Clinical Trial Management System Guide
Siebel Innovation Pack 2015, Rev. A
E52416-01
  Go to Documentation Home
Home		 Go To Table Of Contents
Contents		 Go To Index
Index
Previous
Previous 		 Next
Next		     View PDF

Process of Setting Up Clinical Data Management System Integration

To set up clinical data management system integration for Siebel Clinical, perform the following tasks:

Configuring Siebel Tools for Clinical Data Management System Integration

This task describes how to configure Siebel Tools to activate the fields that are required for clinical data management system integration.


Note:

This Siebel Tools configuration task is not required in version 8.1.1.10 and later.

This task is a step in "Process of Setting Up Clinical Data Management System Integration".

To configure Siebel Tools for clinical data management system integration 

  1. In Siebel Tools, lock the following projects:

    • LS Clinical Protocol

    • LS Clinical Protocol Site

  2. Lock the following objects:

    • Clinical Protocol Admin Form Applet

    • Clinical Protocol Form Applet

    • Clinical Protocol Site Entry Applet

  3. Complete the following steps to configure the Clinical Protocol Admin Form Applet:

    1. Right click Clinical Protocol Admin Form Applet and select Edit Weblayout.

    2. Right click Integration and select View Properties.

    3. Set the Visible option to True for each of the following:

      • CDMS Study ID

      • Synchronize Active Study Sites

  4. Complete the following steps to configure the Clinical Protocol Form Applet:

    1. Right click Clinical Protocol Form Applet and select Edit Weblayout.

    2. Right click Integration and select View Properties.

    3. Set the Visible option to True for each of the following:

      • CDMS Study ID

      • Synchronize Active Study Sites

  5. Complete the following steps to configure the Clinical Protocol Site Entry Applet:

    1. Right click Clinical Protocol Site Entry Applet and select Edit Weblayout.

    2. Right click Integration and select View Properties.

    3. Set the Visible option to True for each of the following:

      • Integration

      • Activate for Synchronization

      • Primary Site Address

  6. Compile the locked projects.

Activating Workflows for Clinical Data Management System Integration

This task describes how to activate the workflows that are required for clinical data management system integration. You can use Siebel Business Process Designer to modify the workflows to suit your own business model. For more information, see Siebel Business Process Framework: Workflow Guide.

This task is a step in "Process of Setting Up Clinical Data Management System Integration".

To activate workflows for clinical data management system integration 

  1. Navigate to the Administration - Business Process screen, then the Workflow Deployment view.

  2. Query for and activate each of the following workflows:

    • LS Clinical Protocol Site New

    • LS Clinical Protocol Site Update

    • SWI LS Clinical Subject Inbound - Subject

    • SWI LS Clinical Subject Inbound - Activity

    • SWI - Protocol Number Lookup

    • LS Clinical - DeleteNonAppVisits Process

  3. Verify that each activated workflow is added to the Active Workflow Processes view at the bottom of the screen.

Setting Up the LS Clinical Integration Workflow Monitor Agent for Clinical Data Management System Integration

This topic describes how to set up the LS Clinical Integration workflow monitor agent for clinical data management system integration.

This task is a step in "Process of Setting Up Clinical Data Management System Integration".

To set up the LS Clinical Integration workflow monitor agent for clinical data management system integration 

  1. Navigate to the Administration - Server Configuration screen, then the Enterprises view.

  2. Navigate to the Component Definitions view, and query for Workflow* in the Component field.

  3. Make a copy of the Workflow Monitor Agent component definition, and complete the following steps:

    1. Change the Component field to LS Clinical Integration.

    2. Change the Alias field to LSClinicalInteg.

    3. Set the Component Group field to Workflow Management.

  4. In the Component Parameters list, complete the following steps:

    1. Change the value of the Group Name parameter to LS Clinical Site Integration.

    2. Change the value of the Action Interval parameter to 5.

    3. Click Advanced, change the value of the Sleep Time parameter to 15, and change the value of the Default Tasks parameter to 1.

  5. Click Activate to change the status of the new component to Active.

  6. Synchronize the components.

  7. Restart the Siebel server.

Configuring Web Services for Clinical Data Management System Integration

This task describes how to configure the Web services that are required for clinical data management system integration. For more information about configuring Web services, see Integration Platform Technologies: Siebel Enterprise Application Integration.


Note:

It is recommended that you use HTTPS authentication. For information about configuring Secure Sockets Layer (SSL) for HTTPS authentication, see Siebel Security Guide.

This task is a step in "Process of Setting Up Clinical Data Management System Integration".

To configure Web services for clinical data management system integration 

  1. Navigate to the Administration - Web Services screen, then the Inbound Web Services view.

  2. Query for each of the following Web services, and update the language and address variables:

    • ClinicalSubject Inbound Web service.

    • LS Clinical Protocol Site Interface Service

  3. Click Clear Cache on the Inbound Web Services applet.

Creating Directory Structure on Siebel Server for Clinical Data Management System Integration

This task describes how to set up the directory structure that is required for JMS (Java Message Service) communication with the Oracle WebLogic Server.

This task is a step in "Process of Setting Up Clinical Data Management System Integration".

To create the directory structure on the Siebel Server for clinical data management system integration 

  1. Create the following directory for storing the JNDI (Java Naming and Directory Interface) properties file and JAR (Java Archive) files on the Siebel Server: D:\WLSJMS.

  2. Create the following directory for storing the log file on the Siebel Server: D:\WLSJMS\log.

  3. Copy Siebel.jar and SiebelJI_enu.jar from the Siebel installation directory to D:\WLSJMS.

Creating Oracle WebLogic Full Client JAR for Clinical Data Management System Integration

This task describes how to create the Oracle WebLogic full client JAR (Java Archive) that is required for clinical data management system integration. You use the Oracle WebLogic JarBuilder tool to generate the full client JAR. You then add the JAR file to the classpath.

This task is a step in "Process of Setting Up Clinical Data Management System Integration".

To create the Oracle WebLogic full client JAR for clinical data management system integration 

  1. Log on to the Oracle WebLogic server.

  2. Change the directory to the server/lib directory, using the following command:

    cd WL_HOME/server/lib

  3. Create wlfullclient.jar in the server/lib directory, using one of the commands in the following table.

    JDK Version Command
    Version 1.5 
    java -jar wljarbuilder.jar -profile wlfullclient5
    Version 1.6 
    ava -jar wljarbuilder.jar

  4. To add the Oracle WebLogic full client JAR to the classpath, copy it to the D:\WLSJMS directory on the Siebel Server.

Creating JNDI Properties File for Clinical Data Management System Integration

This task describes how to create the JNDI (Java Naming and Directory Interface) properties file that is required for clinical data management system integration.

This task is a step in "Process of Setting Up Clinical Data Management System Integration".

To create the JNDI properties file for clinical data management system integration 

  1. Create the D:\WLSJMS\jndi.properties file on the Siebel Server.

  2. Add the following JNDI properties to the file:

    java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory
java.naming.provider.url=t3://Host IP Address:Port

    where:

    Host IP Address is the IP address of the AIA server.

    Port is the port where the Web server instance listens for connections.


    Note:

    Make sure there are no spaces at the end of the lines in the jndi.properties file. Spaces cause the connection to fail.

Configuring JVM Subsystem for Clinical Data Management System Integration

This task describes how to configure the JVM (Java Virtual Machine) subsystem that is required for clinical data management system integration.

This task is a step in "Process of Setting Up Clinical Data Management System Integration".

To configure the JVM Subsystem for clinical data management system integration 

  1. Navigate to the Administration - Server Configuration screen, then the Enterprises view.

  2. Select the Enterprise Server that you want to configure.

  3. Navigate to the Profile Configuration view.

  4. Create a new component profile.

  5. Set the parameters in the following table.

    Name Value
    Profile JAVA
    Alias JAVA
    Subsystem Type JVMSubsys

  6. Set the parameters in the following table in the Profile Parameters list.

    Name Alias Data Type Value
    JVM Classpath CLASSPATH String Set the classpath value as follows:

    • Windows. The files in the classpath must be separated by semicolons (;) and end with a semicolon and period (;.), for example:

      D:\WLSJMS;D:\WLSJMS\Siebel.jar;D:\WLSJMS\SiebelJI_enu.jar;D:\WLSJMS\wlfullclient.jar;.

    • UNIX. The files in the classpath must be separated by colons (:) and end with a colon and period (:.), for example:

      /usr/wlsjms:/usr/wlsjms/Siebel.jar:/usr/wlsjms/SiebelJI_enu.jar:/usr/wlsjms:.
    JVM DLL Name DLL String Set the path to the JVM library file, for example:

    • Windows:

      <JAVA_HOME>/jdk/jre/bin/server/jvm.dll

    • UNIX:

      <JAVA_HOME>/jre/lib/sparc/client/libjvm.so
    JVM Options VMOPTIONS String Set the JVM-specific options for the log file, for example:

    • Windows:

      -Djms.log=D:\WLSJMS\log\jms.log

    • UNIX:

      -Xusealtsigs -Xrs -Djms.log=/usr/wlsjms/log/jms.log

Configuring Java Message Service Parameters for Clinical Data Management System Integration

This task describes how to configure Java Message Service parameters that are required for clinical data management system integration.

This task is a step in "Process of Setting Up Clinical Data Management System Integration".

To configure Java Message Service parameters for clinical data management system integration 

  1. Navigate to the Administration - Server Configuration screen, then the Enterprises view.

  2. Select the Enterprise Server that you want to configure.

  3. Navigate to the Profile Configuration view.

  4. Create a new component profile.

  5. Set the parameters in the following table.

    Name Value
    Profile JMSParameters_study
    Alias JMSParameters_study
    Subsystem Type JMSSubsys

  6. In the Profile Parameters list, set the parameters in the following table.

    Name Value
    ConnectionFactory jms/aia/AIA_SiebelClinical_ClinicalStudyJMSQueueCF
    SendQueue jms/aia/AIA_SiebelClinical_ClinicalStudyJMSQueue
    SendUsername Set the value to the Oracle WebLogic server user name.

    Note: The Oracle WebLogic user must have access to the JMS (Java Message Service) queue.
    SendPassword Set the value to the Oracle WebLogic server user password.

    The password is visible in plain text until you save and refresh the profile.

  7. Restart the Siebel Server.

Populating Domain Value Maps

This topic describes how to configure domain value maps that are required for clinical data management system integration.

You must populate the domain value maps (DVMs) before integrating Siebel Clinical with Oracle Clinical. Siebel Clinical provides a list of values for states and countries that each company can customize.

Domain value maps are a standard feature of the Oracle SOA Suite, and enable you to map equivalent entities in different applications. Domain value maps are static. Administrators can add additional domain value maps as required. Transactional business processes never update domain value maps. They only read from them. The domain value maps are stored in XML files and cached in memory at run time.

You must update domain value maps before synchronizing data between Siebel Clinical and Oracle Clinical. Table 16-1 describes the domain value mappings for integrating Siebel Clinical with Oracle Clinical. Administrators can extend the list of mapped values by adding more domain value maps. To add, modify, or delete a domain value map, use the Oracle Enterprise Service Bus Control DVM user interface. For more information about domain value maps (DVMs), see Oracle Enterprise Service Bus Developer's Guide 10g on My Oracle Support.

This task is a step in "Process of Setting Up Clinical Data Management System Integration".

Table 16-1 Domain Value Maps for Integrating Siebel Clinical with Oracle Clinical

DVM Type Enterprise Service Bus DVM Column Name Description

Country

COMMON, SEBLCLIN_01, OC_O1

This DVM maps the country codes between Siebel Clinical and Oracle Clinical.

State

COMMON, SEBLCLIN_01, OC_O1

This DVM maps the state codes between Siebel Clinical and Oracle Clinical.

ClinicalStudySubject_Status

COMMON, SEBLCLIN_01, OC_01

This DVM maps the patient statuses that customers define in Oracle Clinical to subject statuses in Siebel Clinical.

  Previous
Previous 		 Next
Next
  Go to Documentation Home
Home		 Go To Table Of Contents
Contents		 Go To Index
Index