Oracle® Health Sciences Mobile Clinical Research Associate Server

Installation and Configuration Guide

Release 2.0

E61215-01

November 2015

Oracle Health Sciences Mobile Clinical Research Associate Server Installation and Configuration Guide, Release 2.0

E61215-01

Copyright © 2012, 2015, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Contents

List of Figures

List of Tables

Preface

- Audience

- Documentation Accessibility

- Related Documents

- Conventions

1 Before you Begin

- 1.1 Technology Stack and System Requirements

- 1.1.1 Other Software Requirements

- 1.2 Prerequisites

- 1.3 Media Pack Contents

2 Installing the Database Tier

- 2.1 Creating Default Schema Users

- 2.2 Deploying Mobile Clinical Research Associate Server Schemas (With Clinical Development Analytics Install)

- 2.3 Deploying Mobile CRA Server Schemas (Without Clinical Development Analytics Install)

- 2.4 Installing Seed Data

- 2.4.1 Trip Report Seed Data

- 2.4.2 XSL Seed Data

- 2.5 Deploying Adaptive Site-at-a-Glance Server Schemas

3 Upgrading Database

- 3.1 Upgrading Database

4 Installing the OBIEE Tier

- 4.1 Creating Backup

- 4.2 Before Deploying Mobile Clinical Research Associate Server OBIEE Component

- 4.3 Configuring OBIEE Admin User

- 4.4 Configuring Mobile Clinical Research Associate Server Repository

- 4.5 Upgrading OCDA Repository to Add Mobile Clinical Research Associate Server Rule Engine Data Source (Required for Installation with OCDA)

- 4.6 Merging Repository

- 4.7 Deploying Updated OCDA Repository to OBIEE

- 4.8 Creating User to Access the New OCDA - Mobile Clinical Research Associate Server Repository

- 4.9 Deploying Mobile Clinical Research Associate Server Pre-defined Alert

- 4.10 Deploying Mobile Clinical Research Associate Server Reports Alert

- 4.11 Updating OCDA with Mobile Clinical Research Associate Server Rules Engine

- 4.11.1 Opening OCDA Repository

- 4.11.2 Adding Mobile Clinical Research Associate Server Rule Engine Data Source (Physical Layer)

- 4.11.3 Creating Joins Between Mobile Clinical Research Associate Server and OCDA Tables (Physical Layer)

- 4.11.4 Adding Mobile Clinical Research Associate Server Sources to OCDA Dimensions in the Business Model and Mapping Layer

- 4.11.5 Creating Presentation Tables for Mobile Clinical Research Associate Server (Presentation Layer)

- 4.11.6 Saving the Repository

- 4.12 Deploying Site-At-a-Glance Reports

5 Configuring the Oracle WebLogic Server for Mobile Clinical Research Associate Server

- 5.1 Configuring Oracle WebLogic Server

- 5.1.1 Configuring Data Source Mobile Server

- 5.1.2 Configuring Data Source Alert Engine

- 5.1.3 Configuring Data Source Server Advanced Queuing

- 5.1.4 Installing the Mobile CRA Server

- 5.1.4.1 Installing oracle.hs.Mobile CRA.cda.war on Oracle WebLogic Server

- 5.1.4.2 Installing oracle.hs.Mobile CRA.ctms.war on Oracle WebLogic Server

- 5.1.4.3 Installing oracle.hs.Mobile CRA.ear on Oracle WebLogic Server

- 5.1.5 Customizing the Configuration File

- 5.1.6 Configuring Data Source for Adaptive Site-at-a-Glance on Mobile CRA Server

- 5.2 Configuring Security Using Enterprise Manager

- 5.3 Setting Up Oracle Advanced Queuing

6 Deploying the Mobile CRA Configuration Utility

- 6.1 Verifying the Installation Package

- 6.2 Configuring Data Sources for Mobile CRA Configuration Utility

- 6.3 Configuring Security for Mobile CRA Configuration Utility

- 6.4 Using Single Sign On and Lightweight Directory Access Protocol for Mobile Clinical Research Associate Server

- 6.5 Deploying Mobile CRA Server Configuration Utility

- 6.6 Customizing the Configuration File for Mobile CRA Configuration Utility

- 6.7 Verifying Deployment

7 Mobile Clinical Research Associate Server Application Setup

- 7.1 Setting up Mobile Clinical Research Associate Server for iPad

- 7.1.1 Setting up the Server

- 7.1.2 Running and Logging to the Application

- 7.2 Setting up Mobile Clinical Research Associate Server for iPhone

- 7.2.1 Setting up the Server

- 7.2.2 Running and Logging to the Application

- 7.3 Setting up Mobile Clinical Research Associate Server for Tablet, Phablet, or Smartphone

A Sample Scripts

- A.1 Create_user.sql

- A.2 Create_queue_tables.sql

B Sample XML Files

- B.1 Config.xml

- B.2 Plan.xml

- B.3 config_adminui.xml

C Adding SDV Section to the Trip Report

- C.1 Creating Verified CRFs Checklist Trip Report Type

- C.2 Adding Attributes to the Verified CRFs Checklist

- C.3 Setting the Category Order of the Verified CRFs Checklist in the Trip Report

- C.4 Including Verified CRFs Checklist to the Trip Report

- C.5 Processing the Verified CRFs Checklist

List of Figures

- 3-1 Database Upgrade

- 4-1 OBIEE Administration Tool

- 4-2 Connection Pool Properties Screen 1

- 4-3 Connection Pool Window Screen 2

- 4-4 Testing Connections

- 4-5 Opening RPD

- 4-6 Selecting Merge Option

- 4-7 Selecting Repository

- 4-8 Selecting Input Files

- 4-9 Defining Merge Strategy

- 4-10 Coreapplication Screen

- 4-11 System Shutdown and Startup Screen

- 4-12 Settings for myrealms Screen

- 4-13 Users Tab

- 4-14 Select Subject Area Screen

- 4-15 Catalog Screen

- 4-16 Tasks Menu

- 4-17 Selecting the Mobile CRA.catalog File

- 4-18 Unarchive Window

- 4-19 List of Predefined Alert Imported

- 4-20 Catalog Screen

- 4-21 Tasks Menu

- 4-22 Unarchive Window

- 4-23 List of Predefined Alert Imported

- 4-24 Opening Administration Tool

- 4-25 Opening OCDA RPD

- 4-26 Loaded OCDA RPD

- 4-27 Selecting Import Metadata

- 4-28 Selecting Connection Type

- 4-29 Entering DB Connection Information

- 4-30 Selecting Views

- 4-31 Selecting Metadata Objects

- 4-32 Renaming Physical Schema

- 4-33 Selecting Files

- 4-34 View Menu

- 4-35 Creating Join

- 4-36 Physical Foreign Key Screen

- 4-37 Creating Join for HSM_OBI_STUDY_SITE _VW

- 4-38 Physical Foreign Key Screen

- 4-39 Selecting OCDA-DM

- 4-40 Selecting Dim - Study

- 4-41 Selecting Source

- 4-42 Drag and Drop

- 4-43 Creating Join

- 4-44 Selecting File

- 4-45 Selecting Dim-Study-Site

- 4-46 Drag and Drop

- 4-47 Creating Join

- 4-48 Selecting File

- 4-49 Updated Table

- 4-50 Adding New Column

- 4-51 Logical Column Screen

- 4-52 Update Logical Column

- 4-53 Update Logical Column

- 4-54 Selecting New Presentation Table

- 4-55 Entering Name

- 4-56 Navigating to Catalog

- 4-57 Selecting Site-At-A-Glance-.catalog File

- 5-1 Selecting Deployments

- 5-2 Browsing the Directory

- 5-3 Selecting the Targeting Style

- 5-4 Selecting the Default Settings

- 5-5 Selecting the Default Settings

- 5-6 Deployments Table

- 5-7 Changing the Deployment Plan Path

- 5-8 Specifying the Deployment Path

- 5-9 JMS Module Screen

- 5-10 Creating a New JMS Module

- 5-11 Selecting Target Server

- 5-12 Adding Resources to the JMS System Module

- 5-13 Selecting Type of Resource

- 5-14 Foreign Server Properties

- 5-15 Accepting Default Target

- 6-1 Server Administration Console

- 6-2 Summary of JDBC Data Sources Screen

- 6-3 Creating a New JDBC Data Source Screen

- 6-4 Selecting Database Driver

- 6-5 Selecting Default Settings

- 6-6 Configuring Connection Properties

- 6-7 Selecting Test Configuration

- 6-8 Selecting Deployments

- 6-9 Summary of Deployments Screen

- 6-10 Browsing the Directory

- 6-11 Selecting the Default File

- 6-12 Choosing the Targeting Style

- 6-13 Selecting the Default Settings

- 6-14 Selecting Finish

- 6-15 Validating the Application

- 6-16 Login Page

- 6-17 The Mobile CRA Configuration Utility Home Page

- C-1 Create Trip Report Type

- C-2 Verified CRFs Checklist Trip Report Type

- C-3 ActivityType Attribute

- C-4 Comment Attribute

- C-5 CreatedByName Attribute

- C-6 Description Attribute

- C-7 Display Attribute

- C-8 Status Attribute

- C-9 Setting the Order of the Verified CRFs Checklist

- C-10 Including Verified CRFs Checklist to the Trip Report

List of Tables

- 1-1 Media Pack Contents

- 2-1 Database Schema

Preface

This guide provides information about how to install Oracle Health Sciences Mobile Clinical Research Associate (Mobile CRA) Server application.

This preface contains the following topics:

- "Audience"

- "Documentation Accessibility"

- "Related Documents"

- "Conventions"

Audience

This guide is intended for the following job classifications:

- System Administrators

- Installation Professionals

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Related Documents

Oracle Database Documentation

- Oracle Database Concepts for a comprehensive introduction to the concepts and terminology used in this manual

- Oracle Database Administrator's Guide for information about administering the Oracle Database

- Oracle Database SQL Language Reference for information on Oracle's SQL commands and functions

- Oracle Database Advanced Application Developer's Guide for information about developing database applications within the Oracle Database

You can go directly to the documentation section of the OTN Web site at

http://www.oracle.com/technology/documentation

Oracle Business Intelligence Enterprise Edition Documentation

This is required only in installations that involve Oracle Clinical Development Analytics (OCDA). The Oracle Business Intelligence Suite Enterprise Edition (OBIEE) Online Documentation Library 11.1.1.7.0 documentation set includes:

- Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Enterprise Edition 11g Release 1 (11.1.1.7.0)

- Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition 11g Release 1 (11.1.1.7.0)

- Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition 11g Release 1 (11.1.1.7.0)

- Oracle Fusion Middleware Scheduling Jobs Guide for Oracle Business Intelligence Enterprise Edition 11g Release 1 (11.1.1.7.0)

- Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition 11g Release 1 (11.1.1.7.0)

- Oracle Fusion Middleware Developer's Guide for Oracle Business Intelligence Enterprise Edition 11g Release 1 (11.1.1.7.0)

- Oracle Fusion Middleware Integrator's Guide for Oracle Business Intelligence Enterprise Edition 11g Release 1 (11.1.1.7.0)

Oracle Health Sciences Clinical Development Analytics (OHSCDA) Documentation

This is required only in installations that involve OCDA.

- Oracle Health Sciences Clinical Development Analytics User's Guide

- Oracle Health Sciences Clinical Development Analytics Administrator's Guide

- Oracle Health Sciences Clinical Development Analytics Secure Installation and Configuration Guide

- Oracle Health Sciences Clinical Development Analytics Release Notes

- Oracle Health Sciences Clinical Development Analytics Release Content Document

Oracle Health Sciences Documentation

You can access Oracle Health Sciences Documentation at http://www.oracle.com/technetwork/documentation/hsgbu-clinical-407519.html.

Conventions

The following text conventions are used in this document:

Convention

Meaning

boldface

Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.

italic

Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.

monospace

Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.

1 Before you Begin

This section presents an overview of the Mobile Clinical Research Associate (CRA) Server requirements. It also describes the tasks that you must complete before you can install the Mobile CRA Server application. This section includes the following topics:

- Section 1.1, "Technology Stack and System Requirements"

- Section 1.2, "Prerequisites"

- Section 1.3, "Media Pack Contents"

Starting with Mobile CRA 1.2, installing OBIEE and OCDA are optional. To install Mobile CRA without OBIEE and OCDA, you must select the Adaptive Site-at-a-Glance (ASAAG) option (see Section 1.1).

To install with OBIEE and OCDA, you can either select ASAAG or OBIEE, but not both.

1.1 Technology Stack and System Requirements

The following is the technology stack for Oracle Health Sciences Mobile CRA Server:

- Oracle Database (DB) 12c Enterprise Edition Release 12.1.0.1.0 - 64 bit Production

- Oracle WebLogic Server (WLS) 10.3.6

- Oracle Application Development Framework (ADF) 11.1.1.2

- Oracle Internet Directory (OID) 11.1.1.5

The following products are optional and is required only in installations that involve OCDA.

- Oracle Business Intelligence Administration Tool 11.1.1.7.0

- Oracle Business Intelligence Enterprise Edition (OBIEE) 11.1.1.7.0

1.1.1 Other Software Requirements

The following are the software requirements:

- Oracle Enterprise Linux 6

- iOS 8.x and 9.x

- Android 4.4.x

- Java 1.6

1.2 Prerequisites

Before you install Mobile CRA Server:

- Install Lightweight Directory Access Protocol (LDAP)

- Configure Mobile CRA Server and CTMS with LDAP
For more information, see Oracle Fusion Middleware Oracle WebLogic Server Administration Console Online Help 11g Release 1 (10.3.6).

- Install Health Sciences Push Notification Service (HSPNS). For more information, see Oracle Health Sciences Mobile Clinical Research Associate Health Sciences Push Notification Service Installation and Configuration Guide

- Install Oracle Clinical Development Analytics (OCDA) 3.0
This is optional and is required only in installations that involve OCDA.

- Install Oracle Clinical Trial Management System (CTMS) IP 2015

- Install Oracle Health Sciences InForm 6.1

Note:
OCDA, CTMS, and InForm are not part of the Media Pack. You need to procure them separately.

1.3 Media Pack Contents

This media pack software section contains the following package:

Table 1-1 Media Pack Contents

File Name

Contains

MobileCRA_Server.zip

Mobile CRA Server files

mobilecra_server\jdev\deploy\ oracle.hs.mobilecra.ear

Mobile CRA Server EAR file.

MobileCRA_Server_CDA_Adapter.zip

Mobile CRA Server CDA Adapter files

mobilecra_server/jdev/ExtDependency/deploy/ oracle.hs.mobilecra.cda.war

Mobile CRA Server CDA Adapter war file

MobileCRA_Server_CTMS_Adapter.zip

Mobile CRA Server CTMS Adapter files

mobilecra_server/jdev/ExtDependency/deploy/ oracle.hs.mobilecra.ctms.war

Mobile CRA Server CDA Adapter war file

MobileCRA_AdminUI.zip

Mobile CRA Configuration Application

MobileCRA_AdminUI.ear

Mobile CRA Configuration Utility ear file

MobileCRA_Server_Database.zip

Zip file containing Mobile CRA Server schema creation scripts

HSM_SchemaCreation.sql

Control script to create Mobile CRA Server Schemas (without OCDA install)

HSM_SchemaCreation_CDA.sql

Control script to create Mobile CRA Server Schemas (with OCDA install)

adapter\cda\database

Folder structure for below files:

HSMRE_1.0_Schema_ddl.sql

Control script to create schema object for Mobile CRA Server Rules Engine (MCRE) schema

HSMRE_1.0_tables_ddl.sql

Script to create table

HSMRE_1.0_synonyms_ddl.sql

Script to create synonym

HSMRE_1.0_views_ddl.sql

Script to create view

HSMRE_1.0_indexes_ddl.sql

Script to create index

HSMRE_1.0_constraints_ddl.sql

Script to create constraint

HSMRE_1.0_sequences_ddl.sql

Script to create sequence

HSMRE_1.0_comments_ddl.sql

Script to create comments

MCRA_RulesEngine_Seed.sql

Script for Rule Engine Seed data

MCRA_OBIEE_Kpi_Seed.sql

Seed data for CDA KPIs

HSMRE_1.0_ResetSeq_ddl.sql

Script for reset sequence (drop and create new sequence objects)

HSMRE_1.0_schemadrop_ddl.sql

Script to drop schema objects

HSMRE_1.0_refresh_mvw.sql

Script to create materialized view scheduler

mobile-admin\database

Folder structure for below files:

HSCTMS_1.0_Schema_ddl.sql

Control script to create schema object for Mobile CRA Server Trip Report (MCTR) schema

HSCTMS_1.0_Tables_ddl.sql

Script to create table

HSCTMS_1.0_Indexes_ddl.sql

Script to create index

HSCTMS_1.0_Constraints_ddl.sql

Script to create constraint

HSCTMS_1.0_Sequences_ddl.sql

Script to create sequence

TripReport_SeedData.sql

Script for Trip Report Seed data

HSCTMS_1.0_ResetSeq_ddl.sql

Script for reset sequence (drop and create new sequence objects)

mobilecra_xsl.dmp

Dump file for Trip Report Seed data

mobilecra_server\database

Folder structure for below files:

HSMAQ_1.0_Schema_ddl.sql

Control script to create schema object for Mobile CRA Server Advance Queue (MCAQ) schema

HSMAQ_1.0_tables_ddl.sql

Script to create table

HSMAQ_1.0_constraints_ddl.sql

Script to create constraint

HSMAQ_1.0_sequences_ddl.sql

Script to create sequence

HSMAQ_1.0_CreateQ_ddl.sql

Script to create Advance Queue (AQ)

HSMAQ_1.0_PurgeQ_ddl.sql

Script to purge AQ

HSMAQ_1.0_index_ddl.sql

Script to create index

HSMAQ_1.0_schema_ddl.sql

Control script to create schema object

HSMAQ_1.0_tables_ddl.sql

Script to create table

HSMAQ_triggers.sql

AQ triggers

HSMSV_1.0_schema_ddl.sql

Control script to create schema object for Mobile CRA Server (MCSV) schema

HSMSV_1.0_tables_ddl.sql

Script to create table

HSMSV_1.0_index_ddl.sql

Script to create index

HSMSV_1.0_constraints_ddl.sql

Script to create constraint

HSMSV_1.0_sequence_ddl.sql

Script to create sequence

HSMSV_1.0_customtypes_ddl.sql

Script to create custom types

HSMSV_1.0_comments_ddl.sql

Script to create comments

HSMSV_1.0_ResetSeq_ddl.sql

Script for reset sequence (drop and create new sequence objects)

HSMSV_1.0_schemadrop_ddl.sql

Script to drop schema objects

MobileCRA_OBIEE.zip

Zip file containing Mobile CRA Server repository and catalogs

cda\RPD\

Folder structure for below files:

MobileCRA_Server_01.rpd

Mobile CRA server repository

dummy.rpd

Dummy repository (empty), which is required for merge process

Mobile CRA Operations.catalog

Mobile CRA Server Operations catalog

Mobile CRA.catalog

Mobile CRA Server catalog (Rules Engine)

Site-At-A-Glance.catalog

Site-at-a-Glance reports

ASAAG_Database.zip

Zip file containing database script files

HSOSS_Create_Schema_User

Control script to create ASAAG Schema

HSOSS_schema_ddl

Script to create table

ASAAG_CONFIG

Script to update Configuration

Config.zip

Contains config.xml and config_adminui.xml

config\Config.xml

Mobile CRA Server configuration

config\config_adminui.xml

Config file for Mobile CRA Configuration Utility (MobileCRA_AdminUI)

2 Installing the Database Tier

This chapter includes the following sections:

- Section 2.1, "Creating Default Schema Users"

- Section 2.2, "Deploying Mobile Clinical Research Associate Server Schemas (With Clinical Development Analytics Install)"

- Section 2.3, "Deploying Mobile CRA Server Schemas (Without Clinical Development Analytics Install)"

- Section 2.4, "Installing Seed Data"

- Section 2.5, "Deploying Adaptive Site-at-a-Glance Server Schemas"

2.1 Creating Default Schema Users

This section details the default schema users created by the script. For more details, see Section 2.2, Section 2.3, and Section 2.5.

Table 2-1 Database Schema

Schema

Recommended User Name

Mobile Clinical Research Associate (CRA) Server Rules Engine

MCRE_ADMIN

Mobile CRA Server Trip Report

MCTR_ADMIN

Mobile CRA Server

MCSV_ADMIN

Mobile CRA Server AQ

MCAQ_ADMIN

ASAAG

KPI_ADMIN

The script:

- Prompts to enter a password for each user

- Prompts for OCDA user name and password

- Assumes that schema user do not exist

Note:
The schema user names mentioned in the script are only for recommendation. However, you can modify the script and update schema users name as necessary.If you modify the user name, ensure to update the same in the MobileCRA_Server_Database\HSM_SchemaCreation.sql (for install without CDA installation) and MobileCRA_Server_Database\HSM_SchemaCreation_CDA.sql (for install with CDA installation) files.

2.2 Deploying Mobile Clinical Research Associate Server Schemas (With Clinical Development Analytics Install)

To deploy Mobile CRA Server schemas for customers with OCDA installation, perform the following steps:

1. Extract Mobile CRA_Server_Database.zip to a local folder.

2. Modify the value of the repeat_interval variable in the MobileCRA_Server_Database\adapter\cda\database\HSMRE_1.0_refresh_mvw.sql file to match the schedule of the Mobile CRA Server Rules Engine configured in Section 5.1.5, "Customizing the Configuration File".
You need to schedule this interval before the Mobile CRA Server Rules Engine runs. By default, the FREQ=MINUTELY;INTERVAL value is set to 30.

3. Using SQL*Plus, log in to the Oracle 11gR2 database as SYS user.

Note:
Ensure that the SQL*Plus is started from the folder where files are downloaded.

4. Execute the following SQL script using SQL*:
MobileCRA_Server_Database\HSM_SchemaCreation_CDA.sql

5. Enter the OCDA user name and password when prompted.

6. Enter the passwords for MCRE_ADMIN, MCSV_ADMIN, MCAQ_ADMIN, and MCTR_ADMIN schemas user when prompted.

The script creates database objects for MCRE_ADMIN, MCSV_ADMIN, MCAQ_ADMIN, and MCTR_ADMIN schemas.

Note:
Passwords will not echo on the screen.

2.3 Deploying Mobile CRA Server Schemas (Without Clinical Development Analytics Install)

To deploy Mobile CRA Server schemas for customers without OCDA installation, perform the following:

1. Extract Mobile CRA_Server_Database.zip to a local folder.

2. Using SQL*Plus, log in to the Oracle 11gR2 database as SYS user.

Note:
Ensure that the SQL*Plus is started from the folder where files are downloaded.

3. Execute the following SQL script using SQL*:
MobileCRA_Server_Database\HSM_SchemaCreation.sql

4. Enter the passwords for MCSV_ADMIN, MCAQ_ADMIN, and MCTR_ADMIN schemas when prompted.

The script creates database objects for MCSV_ADMIN, MCAQ_ADMIN, and MCTR_ADMIN schemas.

Note:
Passwords will not echo on the screen.

2.4 Installing Seed Data

2.4.1 Trip Report Seed Data

To install trip report seed data, perform the following:

1. From the MobileCRA_Server_Database/mobile-admin/database folder, execute the TripReport_SeedData.sql by connecting through a SQL session to the Mobile CRA Server trip report schema.
For example,

CMD>sqlplus

Enter user name and password when prompted, where user name is trip report schema user.

SQLPlus>@TripReport_SeedData.sql

2. Review to ensure that there are no errors.
If you want to spool the results, execute the spool command. For example,

SQL> spool abc.log

2.4.2 XSL Seed Data

To install XSL seed data, perform the following:

1. Set up the necessary environment so that you can run the Oracle utilities such as SQLPlus, imp, and so on.

2. Grant IMP_FULL_DATABASE role to the MCTR_ADMIN user.

3. Import the XSL seed data for the out-of-the-box trip reports by using the Oracle imp utility provided in step 5.

4. While importing the XSL seed data, you need to connect to the Mobile CRA Server trip report schema by executing the following command:
$>imp file=mobile-admin/database/mobilecra_xsl.dmp full=Y ignore=Y

Enter user name and password when prompted, where user name is trip report schema user.

5. After importing, revoke the IMP_FULL_DATABASE role.

6. After importing the XSL seed data in Mobile CRA Server CTMS trip report schema, perform the following:

1. Log in to the database using SQLPlus as MCTR_ADMIN schema user.

2. Execute HSCTMS_1.0_ResetSeq_ddl.sql (that is, MobileCRA_Server_Database\
mobile-admin\database\HSCTMS_1.0_ResetSeq_ddl.sql).

2.5 Deploying Adaptive Site-at-a-Glance Server Schemas

To deploy ASAAG schemas for customers, perform the following:

1. Extract ASAAG_Database.zip to a local folder.

2. Using SQL*Plus, log in to the Oracle 11gR2 database as system user.

Note:
Ensure that the SQL*Plus is started from the folder where files are downloaded.

3. Execute the following SQL script using SQL*:
HSOSS_Create_Schema_User.sql

4. Enter the passwords for KPI_ADMIN schemas when prompted.
The script creates database objects for KPI_ADMIN schemas.

5. Edit the following value in the ASAAG_CONFIG.sql file before executing in the KPI_ADMIN schema:

- NOTIFICATION_URL: HSPNS URL

6. Execute ASAAG_CONFIG.sql.

Note:
Passwords will not echo on the screen.

3 Upgrading Database

This chapter provides instructions on how to upgrade database.

3.1 Upgrading Database

To upgrade the database, perform the following:

1. Save and unzip the file on a local folder.

2. Enure you have access to sqlplus and to the database to be upgraded (tnsnames.ora is updated with database information).

3. Run the following upgrade install scripts:

1. To upgrade from v1.0 to v2.0, run Install_HSM_upg_v1.0_to_v2.0_CDA.sql. For installations without CDA, run Install_HSM_upg_v1.0_to_v2.0.sql.
For example, SQL> @Install_HSM_upg_v1.0_to_v2.0_CDA.sql.

2. To upgrade from v1.2 to v2.0, run Install_HSM_upg_v1.2_to_v2.0_CDA.sql. For installations without CDA, run Install_HSM_upg_v1.2_to_v2.0.sql.
For example, SQL> @Install_HSM_upg_v1.2_to_v2.0_CDA.sql.

3. To upgrade from v1.3 to v2.0, run Install_HSM_upg_v1.3_to_v2.0_CDA.sql. For installations without CDA, run Install_HSM_upg_v1.3_to_v2.0.sql.
For example, SQL> @Install_HSM_upg_v1.3_to_v2.0_CDA.sql.

After running the preceding script, the admin user has to perform the steps mentioned in Appendix C to add the SDV section.

4. Upgrade the database as follows:

1. Change to the server/database_upg folder.

2. Start SQLPlus and connect to the database using SYS user or SYSTEM user.

3. Run the upgrade install script.
For example, Install_HSM_upg_v1.0_to_v2.0_CDA.sql.

4. When prompted, enter user ID and password for each schema that has to be upgraded.
Following is a sample screen showing various prompts and messages during the execution of the script:

Figure 3-1 Database Upgrade

Note:
Monitor the screen for error reports, if any.

4 Installing the OBIEE Tier

This chapter details the deployment of Mobile CRA Server - OCDA OBIEE repository (RPD) in the Mobile CRA Server environment.

This chapter includes the following sections:

- Section 4.1, "Creating Backup"

- Section 4.2, "Before Deploying Mobile Clinical Research Associate Server OBIEE Component"

- Section 4.3, "Configuring OBIEE Admin User"

- Section 4.4, "Configuring Mobile Clinical Research Associate Server Repository"

- Section 4.5, "Upgrading OCDA Repository to Add Mobile Clinical Research Associate Server Rule Engine Data Source (Required for Installation with OCDA)"

- Section 4.6, "Merging Repository"

- Section 4.7, "Deploying Updated OCDA Repository to OBIEE"

- Section 4.8, "Creating User to Access the New OCDA - Mobile Clinical Research Associate Server Repository"

- Section 4.9, "Deploying Mobile Clinical Research Associate Server Pre-defined Alert"

- Section 4.10, "Deploying Mobile Clinical Research Associate Server Reports Alert"

- Section 4.11, "Updating OCDA with Mobile Clinical Research Associate Server Rules Engine"

- Section 4.12, "Deploying Site-At-a-Glance Reports"

For information about OBIEE and RPD in Oracle® Health Sciences Clinical Development Analytics (OHSCDA), see the following:

- http://download.oracle.com/docs/cd/E25587_01/index.htm (for Plus configuration)

- http://docs.oracle.com/cd/E50736_01/index.htm (for Standard configuration)

4.1 Creating Backup

Before deploying Mobile CRA Server OBIEE, back up all OBIEE catalogs, RPD, and security profiles.

4.2 Before Deploying Mobile Clinical Research Associate Server OBIEE Component

Before deploying Mobile CRA Server OBIEE component, ensure to collect the following files and DB user information:

- Required RPDs

- OCDA Repository: Ensure to make a note of the name, location, and the password for RPD (OCDA), which will be upgraded to include Mobile CRA Server Alert feature.

- Mobile CRA Server Repository (Mobile CRA_Server_01.rpd): This repository contains Mobile CRA Server data source. This is used for Mobile CRA Server operations reports and is provided by Oracle. The default password is Admin123.

- dummy.rpd: This is an empty RPD, which does not contain data source. This is required for merging process. The default password is Admin123.

- Database user name and password for the following schemas:

- Mobile CRA Server

- Mobile CRA Server Rules Engine (This is required only for installation with OCDA)

- OCDA (This is required only for installation with OCDA)

4.3 Configuring OBIEE Admin User

To configure OBIEE admin user, perform the following:

1. Log in to OBIEE server.

2. Log in to WLS Enterprise Manager as admin by entering the URL using the server address in Step 1 (for example, http://<server:port number>/console).

3. Click Security Realms.

4. Select myrealm from the list.
The Settings for myrealm screen is displayed in the right-side window panel.

5. Click Users and Groups.

6. Click Users tab and click New to create a user.

7. Enter the name.

8. Enter the description.

9. Retain the default value in the Provider field.

10. Enter a password of your choice.

11. Re-enter the password in the Confirm Password field.

12. Click OK to create the user.

13. Assign groups to the user as follows:

1. Click the user Mobile CRA-admin and select Groups.

2. Assign Administrator and BI Administrator groups to the user.

14. Click Save to save the user profile.

4.4 Configuring Mobile Clinical Research Associate Server Repository

To configure Mobile CRA Server RPD to point to Mobile CRA Server database, perform the following:

1. Open the OBIEE Administration tool.

Figure 4-1 OBIEE Administration Tool

2. Open MobileCRA_Server_01.rpd.

3. Enter the password.
Oracle recommends you to modify the password of the RPD provided by Oracle. To change the password, perform the following:

- From the File menu, select Change Password.

- Enter the old and new password in the respective fields.

4. To configure Mobile CRA Server, navigate to the Physical tab, right-click on Mobile CRA Server Connection Pool, and choose Properties.

Figure 4-2 Connection Pool Properties Screen 1

5. Modify the data source name, user name, and password to the database user created for the Mobile CRA Server data model.

- Enter the data source name in the following format:
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=<hostname>)(PORT=<port>))(CONNECT_DATA=(SID=<oracle db sid>)))

- Enter the user name and password for the Mobile CRA Server schema.

Figure 4-3 Connection Pool Window Screen 2

6. Save the RPD file.

7. Test your connections by viewing data on one of the tables in the datastore.

Figure 4-4 Testing Connections

For example, if you see data return, it indicates that your configuration is working.

8. Click OK to save.

4.5 Upgrading OCDA Repository to Add Mobile Clinical Research Associate Server Rule Engine Data Source (Required for Installation with OCDA)

To upgrade OCDA repository to add Mobile CRA Server Rule engine data source, perform the following:

1. Refer to Section 4.11, "Updating OCDA with Mobile Clinical Research Associate Server Rules Engine" for instructions.

2. Save the created RPD as OCDA_MCRA_01.rpd.

4.6 Merging Repository

To merge RPD, perform the following:

1. Take a backup of the following repository:

- Updated version of OCDA repository (updated with Mobile CRA Server Rules Engine data source) OCDA_MCRE_01.rpd.

- Mobile CRA Server Repository - MobileCRA_Server_01.rpd

2. Open the updated OCDA RPD, that is OCDA_MCRA_01.rpd.

Figure 4-5 Opening RPD

3. From the File menu, select Merge.

Figure 4-6 Selecting Merge Option

The Merge Repository Wizard is displayed.

4. Select dummy.rpd in the Original Master Repository.

Figure 4-7 Selecting Repository

5. Enter the repository password for the dummy repository.

6. Select MobileCRA_Server_01.rpd in the Modified Repository.

7. Enter the repository password for Mobile CRA Server repository.

8. Retain Save Merged Repository as is and note down the saved merged repository name and location.

9. Click Next.

Figure 4-8 Selecting Input Files

A screen is displayed which shows the conflicts.

10. Click the Decision column in the conflict row and select Current.

Figure 4-9 Defining Merge Strategy

11. Click Next.
The Merge Repository screen is displayed.

12. Click Finish.

13. Verify that the physical layer has Mobile CRA Server, Mobile CRA database, and OCDA data warehouse schemas available in the Physical section.

14. Verify that the Mobile CRA Server and OCDA-DM are available in the Business Model and Mapping section.

15. Open Dim - Study in OCDA-DM from the Business Model and Mapping section, and verify that the HSM_OBI_STUDY_VW is included in the source.

16. Open Dim - Study-site in OCDA-DM from the Business Model and Mapping section, and verify that the HSM_OBI_STUDY_SITE_VW is included in the source.

17. Verify that the Mobile CRA Server and OCDA are available in the Presentation section.

18. Verify that the Mobile CRA Alert Engine, -Study, and -Study-site presentation tables are available under OCDA.

19. Save the updated OCDA repository (for example as OCDA_MCRE_MCSV_01.rpd).

4.7 Deploying Updated OCDA Repository to OBIEE

To deploy updated OCDA RPD to OBIEE, perform the following:

1. Log in to Enterprise Manager (for example, http://<server:port number>/em).

2. Navigate to Business Intelligence and select Coreapplication.

3. Navigate to Deployment tab, and then to the Repository subtab.

Figure 4-10 Coreapplication Screen

4. Click Lock and Edit Configuration to lock the application.

5. In the Upload BI Server Repository pane, choose the RPD file that you want to upload, and load the updated OCDA repository (for example, OCDA_MCRE_MCSV_01.rpd).

6. Enter the password for updated OCDA repository.

7. Re-enter the password for the updated OCDA repository in the Confirm Password field.

8. Click Apply.

9. Click Activate Change.

10. Restart to apply recent changes.

11. Restart all BI components.

Figure 4-11 System Shutdown and Startup Screen

12. Click Yes in the Confirmation window.
Once the restart is complete, a message is displayed indicating that the RPD deployment is complete.

4.8 Creating User to Access the New OCDA - Mobile Clinical Research Associate Server Repository

To create a user to access the new OCDA - Mobile CRA Server RPD, perform the following:

1. Navigate to the Oracle WebLogic server (for example, http://<servername>/console/login/LoginForm.jsp).

2. Navigate to Security Realms and select myrealm.
The Settings for myrealms screen is displayed.

Figure 4-12 Settings for myrealms Screen

3. Click Users and Groups.

4. Click New in the Users subtab.

Figure 4-13 Users Tab

5. Enter the OBIEE user name (for example, Mobile CRA-admin).

6. Enter the OBIEE password.

7. Click OK to create user.

8. Assign groups to the user as follows:

1. Select the newly created user Mobile CRA-admin and navigate to Groups.

2. Assign groups to this user. For example, Administrator and BI Administrator.

9. Click Save to save the user profile.

10. Test the user by navigating to the OBIEE Analytics site (for example, http://<servername>/analytics).

11. Enter the user name and password.
You should be able to log in to OBIEE.

12. Create a new analysis.
If you see the following subject areas, it indicates that your RPD and user are configured and deployed correctly.

Figure 4-14 Select Subject Area Screen

4.9 Deploying Mobile Clinical Research Associate Server Pre-defined Alert

To deploy Mobile CRA Server pre-defined alert, perform the following:

1. Log in to the OBIEE Analytics.

2. Navigate to Catalog.
The Catalog Screen is displayed.

Figure 4-15 Catalog Screen

3. Select Shared Folders and click Unarchive in the bottom-left Tasks menu.

Figure 4-16 Tasks Menu

4. Click Browse and select the Mobile CRA.catalog file.

Figure 4-17 Selecting the Mobile CRA.catalog File

5. Click OK to unarchive the catalog.

Figure 4-18 Unarchive Window

6. Navigate to Shared Folders and select Mobile CRA to see the predefined alert imported.

Figure 4-19 List of Predefined Alert Imported

4.10 Deploying Mobile Clinical Research Associate Server Reports Alert

To deploy Mobile CRA Server Reports alert, perform the following:

1. Log in to the OBIEE Analytics.

2. Navigate to Catalog.
The Catalog Screen is displayed.

Figure 4-20 Catalog Screen

3. Select Shared Folders and click Unarchive in the bottom-left Task menu.

Figure 4-21 Tasks Menu

4. Click Browse and select the Mobile CRA.catalog file.

5. Click OK to unarchive the catalog.

Figure 4-22 Unarchive Window

6. Navigate to Shared Folders and select Mobile CRA to see the predefined alert imported.

Figure 4-23 List of Predefined Alert Imported

4.11 Updating OCDA with Mobile Clinical Research Associate Server Rules Engine

This section contains the following topics:

- Section 4.11.1, "Opening OCDA Repository"

- Section 4.11.2, "Adding Mobile Clinical Research Associate Server Rule Engine Data Source (Physical Layer)"

- Section 4.11.3, "Creating Joins Between Mobile Clinical Research Associate Server and OCDA Tables (Physical Layer)"

- Section 4.11.4, "Adding Mobile Clinical Research Associate Server Sources to OCDA Dimensions in the Business Model and Mapping Layer"

- Section 4.11.5, "Creating Presentation Tables for Mobile Clinical Research Associate Server (Presentation Layer)"

- Section 4.11.6, "Saving the Repository"

4.11.1 Opening OCDA Repository

To open OCDA RPD, perform the following:

1. Open the Oracle Business Intelligence Enterprise Edition Administration tool.

Figure 4-24 Opening Administration Tool

2. Open the OCDA repository (for example, OCDA_21_final.rpd).

Figure 4-25 Opening OCDA RPD

3. Enter the repository password when prompted.
OCDA RPD will be loaded in the OBIEE Administration tool.

Figure 4-26 Loaded OCDA RPD

4. Save this RPD and note down the file name (for example, OCDA_MCRE_01.rpd) and the location.

4.11.2 Adding Mobile Clinical Research Associate Server Rule Engine Data Source (Physical Layer)

1. From the File menu, select Import Metadata.

Figure 4-27 Selecting Import Metadata

2. Select OCI 10g/11g in the Connection type.

Figure 4-28 Selecting Connection Type

3. Enter complete data source name, database user name, and password in the respective fields. Oracle recommends the following data source name format:
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=<hostname>)(PORT=<port>))(CONNECT_DATA=(SID=<oracle db sid>)))

Figure 4-29 Entering DB Connection Information

4. Click Next.

5. Select Views from the Metadata types to be imported.

Figure 4-30 Selecting Views

6. Click Next.

7. Select the Mobile CRA Server Rule Engine Schema user from the list and select the following View object from the list:

- HSM_OBI_STUDY_VW

- HSM_OBI_STUDY_SITE_VW

Figure 4-31 Selecting Metadata Objects

8. Rename the data source to MobileCRA Database.

9. Rename the Physical schema to MobileCRA.

Figure 4-32 Renaming Physical Schema

10. Right-click HSM_OBI_STUDY_VW and select Update Row Count.

11. Right-click HSM_OBI_STUDY_SITE_VW and select Update Row Count.

4.11.3 Creating Joins Between Mobile Clinical Research Associate Server and OCDA Tables (Physical Layer)

To create joins between Mobile CRA Server and OCDA tables, perform the following:

1. Create Join for HSM_OBI_STUDY_VW.

1. Select HSM_OBI_STUDY_VW from MobileCRA schema in the MobileCRA Database and Dim _W_RXI_STUDY_D from RXI schema in the OCDA Data Warehouse.

Figure 4-33 Selecting Files

2. From the View menu, select Physical Diagram, and then Selected Object(s) only.

Figure 4-34 View Menu

3. Click New Join.

4. Click HSM_OBI_STUDY_VW and drag the cursor (hold the mouse) to Dim_W_RXI_STUDY_D and release the cursor (release the mouse).

Figure 4-35 Creating Join

5. Select INTEGRATION_ID column from the Dim_W_RXI_STUDY_D table and STUDY_ID column from the HSM_OBI_STUDY_VW table (view).

Figure 4-36 Physical Foreign Key Screen

6. Click OK.

7. Close the window.

2. Create Join for HSM_OBI_STUDY_SITE_VW.
The following steps are similar to creating join for HSM_OBI_STUDY_VW in step 1.

1. Select HSM_OBI_STUDY_SITE_VW from the MobileCRA schema in the MobileCRA Database and Dim _W_RXI_STUDY_SITE_D from the RXI schema in the OCDA Data Warehouse.

2. From the View menu, select Physical Diagram, and then select Selected Object(s) only.

3. Click New Join.

4. Click HSM_OBI_STUDY_SITE _VW and drag the cursor (hold the mouse button) to Dim_W_RXI_STUDY_SITE _D and release the cursor (release the mouse button).

Figure 4-37 Creating Join for HSM_OBI_STUDY_SITE _VW

5. Select INTEGRATION_ID column from the Dim_W_RXI_STUDY_SITE_D table and STUDY_SITE_ID column from the HSM_OBI_STUDY_SITE_VW table (view).

Figure 4-38 Physical Foreign Key Screen

6. Click OK.

7. Close the window.

4.11.4 Adding Mobile Clinical Research Associate Server Sources to OCDA Dimensions in the Business Model and Mapping Layer

To add Mobile CRA Server sources to OCDA Dimensions in the Business Model and Mapping Layer, perform the following:

1. Update Dim - Study.

1. Select OCDA-DM and expand by clicking +.

Figure 4-39 Selecting OCDA-DM

2. Select Dim - Study and expand by clicking +.

Figure 4-40 Selecting Dim - Study

3. Click Sources and expand by clicking +.

Figure 4-41 Selecting Source

4. Drag HSM_OBI_STUDY_VW from the Physical section and drop on Dim - Study in the Business Model and Mapping section.

Figure 4-42 Drag and Drop

5. Select HSM_OBI_STUDY_VW in Sources under Dim - Study.

6. From the Edit menu, select Properties to open property window.

7. Click Add to create join with Dim - Study.

Figure 4-43 Creating Join

8. Click Dim_W_RXI_STUDY_D from the right side and then click Select.

Figure 4-44 Selecting File

9. Click OK.

2. Update Dim - Study-Site.

1. Select Dim - Study-Site and expand by clicking +.

Figure 4-45 Selecting Dim-Study-Site

2. Click Sources and expand by clicking +.

3. Drag HSM_OBI_STUDY_SITE_VW from the Physical section and drop on Dim - Study-Site in the Business Model and Mapping section.

Figure 4-46 Drag and Drop

4. Select HSM_OBI_STUDY_SITE_VW in Sources under Dim-Study-Site.

5. From the Edit menu, select Properties to open property window.

6. Click Add to create join with Dim - Study-Site.

Figure 4-47 Creating Join

7. Click Dim_W_RXI_STUDY_SITE_D from the right side and then click Select.

Figure 4-48 Selecting File

8. Click OK to close the window.
The created join is displayed.

Figure 4-49 Updated Table

3. Create Custom Columns for HSM_OBI_STUDY_VW.

1. Create four new columns as follows:
SUBSCRIPTION LAST_UPDATED_BY

SUBSCRIPTION LAST_UPDATE_DATE

SUBSCRIPTION CREATION_DATE

SUBSCRIPTION CREATED_BY

2. Map these columns to LAST_UPDATED_BY, LAST_UPDATE_DATE, CREATION_DATE, and CREATED_BY respectively from HSM_OBI_STUDY_VW.

4. Add new columns as follows:

1. Right-click HSM_OBI_STYDY_VW, navigate to Properties, and then select the Column Mapping tab.

2. Click Add New Column.

Figure 4-50 Adding New Column

3. Enter the column name, for example, SUBSCRIPTION LAST_CREATED_BY, and update the column mapping to select the correct source.

Figure 4-51 Logical Column Screen

4. Update the Physical Table as HSM_OBI_STUDY_VW and Expression as CREATED_BY.

5. Repeat Step 5 for LAST_UPDATE_DATE, LAST_UPDATED_BY, and CREATED_BY columns as shown in the Figure 4-52.

Figure 4-52 Update Logical Column

6. Click OK.

5. Create Custom Columns for HSM_OBI_STUDY_SITE_VW.

1. Create custom columns for LAST_UPDATED_BY, LAST_UPDATE_DATE, CREATION_DATE and CREATED_BY columns as shown in Figure 4-53.

2. Map these columns to LAST_UPDATED_BY, LAST_UPDATE_DATE, CREATION_DATE, and CREATED_BY respectively from HSM_OBI_STUDY_VW.

3. Add a new column INTEGRATION_ID mapped to INTEGRATION_ID of Dim_W_RXI_STUDY_SITE_D.

4. Follow similar steps defined in Step 3 (Create Custom Columns for HSM_OBI_STUDY_VW).

Figure 4-53 Update Logical Column

4.11.5 Creating Presentation Tables for Mobile Clinical Research Associate Server (Presentation Layer)

To create presentation tables for Mobile CRA Server (presentation layer), perform the following:

1. Create New Presentation Table for Grouping Purpose.

1. Right-click OCDA in the Presentation section and then click New Presentation Table.

Figure 4-54 Selecting New Presentation Table

2. Enter Mobile CRA Alert Engine in the Name field and click OK.

Figure 4-55 Entering Name

3. Locate the newly created presentation table (that is, Mobile CRA Alert Engine) in the Presentation section, and then locate Fact for Presentation Folder.

4. Drag and drop it on the Mobile CRA Alert Engine table in the presentation section.

2. Create New Presentation Table for Study.

1. Right-click OCDA in the Presentation section and then click the New Presentation table.

2. Enter - Study in the Name field and click OK.

3. Select the following columns from Dim - Study in the Business Model and Mapping section and drop on - Study presentation table in the Presentation section.
HSM_RULE_SBSCRTIONS_ID

USER_ID

HSM_RULES_ID

HSM_RULES_NAME

HSM_RULES_DESCR

HSM_RULES_FNCTN

STUDY_ID

ACTV_STUS

FIRED_STUS

THRESH_DT1

THRESH_DT1_NM

THRESH_DT2

THRESH_DT2_NM

THRESH_DT3

THRESH_DT3_NM

THRESH_DT4

THRESH_DT4_NM

THRESH_DT5

THRESH_DT5_NM

THRESH_NUM1

THRESH_NUM1_NM

THRESH_NUM2

THRESH_NUM2_NM

THRESH_NUM3

THRESH_NUM3_NM

THRESH_NUM4

THRESH_NUM4_NM

THRESH_NUM5

THRESH_NUM5_NM

THRESH_STR1

THRESH_STR1_NM

THRESH_STR2

THRESH_STR2_NM

THRESH_STR3

THRESH_STR3_NM

THRESH_STR4

THRESH_STR4_NM

THRESH_STR5

THRESH_STR5_NM

SUBSCRIPTION LAST_UPDATED_BY

SUBSCRIPTION LAST_UPDATE_DATE

SUBSCRIPTION CREATION_DATE

SUBSCRIPTION CREATED_BY

3. Create New Presentation Table for Study-Site.

1. Right-click OCDA in the Presentation section and then click New Presentation Table.

2. Enter - Study Site in the Name field and click OK.

3. Select the following columns from Dim - Study-Site in the Business Model and Mapping section and drop on - Study Site presentation table in the Presentation section.
HSM_RULE_SBSCRTIONS_ID

USER_ID

HSM_RULES_ID

HSM_RULES_NAME

HSM_RULES_DESCR

HSM_RULES_FNCTN

STUDY_SITE_ID

ACTV_STUS

FIRED_STUS

THRESH_DT1

THRESH_DT1_NM

THRESH_DT2

THRESH_DT2_NM

THRESH_DT3

THRESH_DT3_NM

THRESH_DT4

THRESH_DT4_NM

THRESH_DT5

THRESH_DT5_NM

THRESH_NUM1

THRESH_NUM1_NM

THRESH_NUM2

THRESH_NUM2_NM

THRESH_NUM3

THRESH_NUM3_NM

THRESH_NUM4

THRESH_NUM4_NM

THRESH_NUM5

THRESH_NUM5_NM

THRESH_STR1

THRESH_STR1_NM

THRESH_STR2

THRESH_STR2_NM

THRESH_STR3

THRESH_STR3_NM

THRESH_STR4

THRESH_STR4_NM

THRESH_STR5

THRESH_STR5_NM

SUBSCRIPTION LAST_UPDATED_BY

SUBSCRIPTION LAST_UPDATE_DATE

SUBSCRIPTION CREATION_DATE

SUBSCRIPTION CREATED_BY

4. Create a new column Src Unique Site ID in Study-Site, which is mapped to logical column INTEGRATION_ID of Dim_Study Site created in Section 4.11.4, "Adding Mobile Clinical Research Associate Server Sources to OCDA Dimensions in the Business Model and Mapping Layer"(Step 4).

4.11.6 Saving the Repository

To save the RPD, perform the following:

1. From the File menu, select Save.

4.12 Deploying Site-At-a-Glance Reports

To deploy site-at-a-glance reports, perform the following:

1. Log in to OBIEE analytics.

2. Navigate to Catalog.

Figure 4-56 Navigating to Catalog

3. Select Shared folders and click Unarchive in the bottom-left Task menu.

4. Click Browse and choose the Site-At-A-Glance-.catalog file.

Figure 4-57 Selecting Site-At-A-Glance-.catalog File

5. Click OK to unarchive the catalog.

6. Navigate to the Shared folder and select Site-At-A-Glance.
A list of predefined reports that are imported is displayed which will be deployed.

5 Configuring the Oracle WebLogic Server for Mobile Clinical Research Associate Server

This chapter includes the following sections:

- Section 5.1, "Configuring Oracle WebLogic Server"

- Section 5.2, "Configuring Security Using Enterprise Manager"

- Section 5.3, "Setting Up Oracle Advanced Queuing"

Note:
For information about installing Oracle WebLogic Server, see http://docs.oracle.com/cd/E23943_01/doc.1111/e14142/toc.htm.

5.1 Configuring Oracle WebLogic Server

You need to define a data source to point the WebLogic Server (WLS) to the database where the Mobile CRA Server database component is installed.

This section contains the following topics:

- Section 5.1.1, "Configuring Data Source Mobile Server"

- Section 5.1.2, "Configuring Data Source Alert Engine"

- Section 5.1.3, "Configuring Data Source Server Advanced Queuing"

- Section 5.1.4, "Installing the Mobile CRA Server"

- Section 5.1.5, "Customizing the Configuration File"

- Section 5.1.6, "Configuring Data Source for Adaptive Site-at-a-Glance on Mobile CRA Server"

5.1.1 Configuring Data Source Mobile Server

To configure data source mobile server, perform the following:

1. Log in to Oracle WebLogic Server (WLS) as admin by entering the URL (for example, http://<server:port number>/console).

2. Click Lock and Edit in the Change Center panel on the left side.

3. Click Services in the Domain Structure window.

4. Select Data Sources.
The Summary of JDBC data sources is displayed on the right-side window panel.

5. Click New and select Generic Data Source from the list.

6. In the JDBC Data Source Properties screen, perform the following:

1. Enter the name.
Oracle recommends that the name should match the JNDI name.

2. Enter jdbc/mobilecra as the name and JNDI name to connect to MCSV_ADMIN schema.

3. Enter Oracle as the database type.

4. Click Next.

5. In the Database Driver field, select the default value, that is, Oracle's Driver (Thin XA) for instance connections (versions: 9.0.1 and above).

6. Click Next.

7. Click Next on the Transaction Options screen.

8. In the Connection Properties screen, perform the following:

1. Enter the SID in the Database Name field.

2. Enter the server where mobile server database is hosted.

3. Enter the port number for the database.

4. Enter the Mobile CRA server database user name where it is hosted.

5. Enter password for the database user.

6. Re-enter the password in the Confirm password field.

7. Click Next.
The Properties, System Properties, and Test Table Name fields are displayed on the screen.

8. Click Test Configuration.
If the test is successful, the message Connection test succeeded is displayed on the screen.

9. Click Next.
The Select Targets screen is displayed with the list of servers.

9. Select the server where the Mobile CRA Server is installed.

10. Click Finish.

11. After creating jdbc/mobilecra, click Activate Changes in the Change Center panel.

5.1.2 Configuring Data Source Alert Engine

To configure data source alert engine, perform the following:

1. Log in to WLS as admin by entering the URL (for example, http://<server:port number>/console).

2. Click Lock and Edit in the Change Center panel on the left side.

3. Click Services in the Domain Structure window.

4. Select Data Sources.
The Summary of JDBC Data Sources is displayed on the right-side window panel.

5. Click New and select Generic Data Source from the list.

6. In the JDBC Data Source Properties screen, perform the following:

1. Enter the name.
Oracle recommends that the name should match the JNDI name.

2. Enter jdbc/ae as the name and JNDI name to connect to MCRE_ADMIN schema.

3. Enter Oracle as the database type.

4. Click Next.

5. In the Database Driver field, select the default value, that is, Oracle's Driver (Thin XA) for instance connections (versions: 9.0.1 and above).

6. Click Next.

7. Click Next on the Transaction Options screen.

8. In the Connection Properties screen, perform the following:

1. Enter the SID in the Database Name field.

2. Enter the server where alert engine database is hosted.

3. Enter the port number for database.

4. Enter the alert engine database user name where it is hosted.

5. Enter password for the database user.

6. Re-enter the password in the Confirm password field.

7. Click Next.
The Properties, System Properties, and Test Table Name fields are displayed on the screen.

8. Click Test Configuration.
If the test is successful, the message Connection test succeeded is displayed on the screen.

9. Click Next.
The Select Targets screen is displayed with the list of servers.

9. Select the server where the Mobile CRA Server is installed.

10. Click Finish.

11. After creating jdbc/ae, click Activate Changes in the Change Center panel.

12. Exit the Oracle WebLogic server.

5.1.3 Configuring Data Source Server Advanced Queuing

To configure data source Server AQ, perform the following:

1. Log in to WLS as admin by entering the URL (for example, http://<server:port number>/console).

2. Click Lock and Edit in the Change Center panel on the left side.

3. Click Services in the Domain Structure window.

4. Select Data Sources.
The Summary of JDBC Data Sources is displayed on the right-side window panel.

5. Click New and select Generic Data Source from the list.

6. In the JDBC Data Source Properties screen, perform the following:

1. Enter the name.
Oracle recommends that the name should match the JNDI name.

2. Enter jdbc/mobileaq as the name and JNDI name to connect to MCAQ_ADMIN schema.

3. Enter Oracle as the database type.

4. Click Next.

5. In the Database Driver field, select the default value, that is, Oracle's Driver (Thin XA) for instance connections (versions: 9.0.1 and above).

6. Click Next.

7. Click Next on the Transaction Options screen.

8. In the Connection Properties screen, perform the following:

1. Enter the SID in the Database Name field.

2. Enter the server where AQ database is hosted.

3. Enter the port number for database.

4. Enter the AQ database user name where it is hosted.

5. Enter password for the database user.

6. Re-enter the password in the Confirm password field.

7. Click Next.
The Properties, System Properties, and Test Table Name fields are displayed on the screen.

8. Click Test Configuration.
If the test is successful, the message Connection test succeeded is displayed on the screen.

9. Click Next.
The Select Targets screen is displayed with the list of servers.

9. Select the server where the Mobile CRA Server is installed.

10. Click Finish.

11. After creating jdbc//mobileaq, click Activate Changes in the Change Center panel.

12. Exit the Oracle WebLogic server.

5.1.4 Installing the Mobile CRA Server

5.1.4.1 Installing oracle.hs.Mobile CRA.cda.war on Oracle WebLogic Server

To install oracle.hs.Mobile CRA.cda.war on WebLogic server, perform the following:

1. Download Mobile CRA_Server_CDA_Adapter.zip to a local folder and unzip it to extract the oracle.hs.Mobile CRA.cda.war file.

2. Log in to the Oracle WebLogic Server Administration Console.

3. Within Server Administration, select Deployments.

Figure 5-1 Selecting Deployments

The Summary of Deployments screen is displayed.

4. Select Install to install the application.

5. Browse the directory where the install package is located.

Figure 5-2 Browsing the Directory

6. Select the oracle.hs.Mobile CRA.cda.war file.

7. Select the Install this deployment as a library option.

Figure 5-3 Selecting the Targeting Style

8. Select default settings as displayed in Figure 5-4.

Figure 5-4 Selecting the Default Settings

9. Select Finish to complete installation.

10. Click Activate Changes.

5.1.4.2 Installing oracle.hs.Mobile CRA.ctms.war on Oracle WebLogic Server

To install oracle.hs.Mobile CRA.ctms.war on WLS, follow the similar steps in Section 5.1.4.1, "Installing oracle.hs.Mobile CRA.cda.war on Oracle WebLogic Server".

5.1.4.3 Installing oracle.hs.Mobile CRA.ear on Oracle WebLogic Server

Note:
Before you install oracle.hs.Mobile CRA.ear, you must define notificationService.credential.
For more information about defining notificationService.credential, see the Oracle Health Sciences Mobile Clinical Research Associate Server Security Guide.

To install oracle.hs.Mobile CRA.ear on WLS, perform the following:

1. Log in to the Oracle WebLogic Server Administration Console.

2. Within Server Administration, select Deployments.
The Summary of Deployments screen is displayed.

3. Select Install to install the application.

4. Browse the directory where the install package is located.

5. Select the oracle.hs.Mobile CRA.ear file.

6. Select the Install this deployment as an application option.

7. Select default settings as displayed in Figure 5-5.
Specify the name as oracle.hs.mobilecra.

Figure 5-5 Selecting the Default Settings

8. Select Finish to complete installation.

9. Click Activate Changes.

5.1.5 Customizing the Configuration File

To customize the configuration file, perform the following:

1. From the Config folder of the media pack, select Config.xml
This is a template file where you have to update values for customization.

2. Create a copy of Config.xml and save it as Plan.xml.
For examples of Config.xml and Plan.xml files, see Appendix B.

3. Modify configuration values for your environment.
The plan.xml file lets you configure your Mobile CRA Server application to point to the right CTMS and OCDA server, push notification schedule, alert engine schedule, and so on.

Some of the basic configurations such as CTMS server information has to be setup for the application to work but the advanced configuration such as push notification configurations may be modified to suit your schedule and performance needs.

Following are the basic settings to change in the Plan.xml file:

- ctmsApdater.hostname - The name of the CTMS host to which the mobile instance should connect for accessing and manipulating data. For example, server.domain.com.

Note:
If you use CTMS IP 2015, enter the IP address instead of host name.

- ctmsAdpater.port - The CTMS port host. For example, 8080. If the default port is used, enter a value 0 instead of null.

- useCDA - Use this parameter to select or deselect the OCDA option. The valid values are True and False.
If the parameter is set to True, the system uses the value for the KPIs for SAAG, subscriptions, and alerts from OCDA configurations.

If the parameter is set to False, the system uses the value for the KPIs for SAAG, subscriptions, and alerts from ASAAG configurations.

- pushNotificationEngine.timeUnit - The time-out unit of the notification engine on the push notification server. For example, seconds.

- notificationEngineScheduler.timeUnit - The time-out unit of scheduler on the push notification server. For example, seconds.

- cdaAdapter.wsdlLocation - This is the URL of the OBIEE Web service wsdl location. Mobile CRA Server uses the OBIEE server for alerts and notifications. For example, http://<ocdaserver>/analytics/saw.dll?WSDL.

- pushNotificationService.url - If you are using alerts and notifications, use this to set the URL of the push notification service. This is the URL of the hosted service provided by Oracle. For example, pushNotificationserver.domain.com:port (if port number is given).

- notificationEngineScheduler.period and notificationEngineScheduler.timeUnit - If you are using alerts and notifications, use this to set the schedule for the notification engine.
notificationEngineScheduler.period along with notificationEngineScheduler.timeUnit defines the schedule for the notification scheduler. A value of 300 for notificationEngineScheduler.period along with a value of seconds for notificationEngineScheduler.timeUnit specifies a schedule of 300 seconds. Valid values for notificationEngineScheduler.timeUnit are seconds, minutes, and hours.

- informAPIService.url - If source data verification is being used, this value should be set to http://<mobilecraserverhost>:<mobilecraserverport>/mobilecraservices/rest/ias, where mobilecraserverhost and mobilecraserverport are values of the host and port that you use in Mobile CRA client application on iOS or Android for logging in.

Note:
Enter the IP address instead of host name.

- mfv.maxRetries - Set this value to the maximum number of tries Mobile CRA client application should poll for a multi-field validation check to complete.

Advanced settings:

- pushNotificationEngine.maximumPoolSize - The maximum number of threads in the pool for the push notification engine. The valid values are integer values.

- pushNotificationEngine.engineLockTimeout - The duration the service should wait for the push notification engine to respond.

- notificationEngineScheduler.initialDelay - The initial delay after which the notification starts after each WLS restart.

- mobilecraLog.Level - Set this parameter to set up log levels. For example, INFO.
The following are levels in descending order:

SEVERE (highest value)

WARNING

INFO

CONFIG

FINE

FINER

FINEST (lowest value)

- tripReport.maxBeanPoolSize - The maximum bean pool size of the trip report.

- tripReport.initialBeanPoolSize - The initial bean pool size of the trip report.

Note:
The same settings are applicable for Alert Engine Scheduler.

4. Save Plan.xml to the machine where Oracle WebLogic is installed.

5. Upload Plan.xml file on the server as follows:

1. In the Deployments table, select oracle.hs.Mobile CRA.

2. Click Update.

Figure 5-6 Deployments Table

3. In the Update Application Assistant wizard, select Update this application in place with new deployment plan changes, and click Change Path.

Figure 5-7 Changing the Deployment Plan Path

4. In the Path field, specify the deployment path of your environment specific Plan.xml file to upload it to the server.

Figure 5-8 Specifying the Deployment Path

5. Click Finish.

5.1.6 Configuring Data Source for Adaptive Site-at-a-Glance on Mobile CRA Server

To configure data source mobile server, perform the following:

1. Log in to Oracle WebLogic Server (WLS) as administrator by entering the URL.
For example, http://<server:port number>/console

2. Click Lock & Edit in the Change Center panel on the left side.

3. Click Services in the Domain Structure window

4. Select Data Sources.
The Summary of JDBC data sources is displayed on the right side window panel.

5. Click New and select Generic Data Source from the list.

6. In the JDBC Data Source Properties screen, perform the following:

1. Enter the name.
Oracle recommends that the name should match the JNDI name.

2. Enter jdbc/ossdb as the name and JNDI name to connect to KPI_ ADMIN schema.

3. Enter Oracle as the database type.

4. Click Next.

5. In the Database Driver field, select the default value, that is, Oracle's Driver (Thin XA) for instance connections (versions: 9.0.1 and above).

6. Click Next.

7. Click Next on the Transaction Options screen.

8. In the Connection Properties screen, perform the following:

1. Enter the SID in the Database Name field.

2. Enter the server where mobile server database is hosted.

3. Enter the port number for the database.

4. Enter the Mobile CRA server database user name where it is hosted.

5. Enter password for the database user.

6. Re-enter the password in the Confirm password field.

7. Click Next.
The Properties, System Properties, and Test Table Name fields are displayed on the screen.

8. Click Test Configuration.
If the test is successful, the message Connection test succeeded is displayed on the screen.

9. Click Next.
The Select Targets screen is displayed with the list of servers.

9. Select the server where the Mobile CRA Server will be installed.

10. Click Finish.

11. After creating jdbc/ossdb, click Activate Changes in the Change Center panel.

5.2 Configuring Security Using Enterprise Manager

For information about configuring security using Enterprise Manager, see Oracle Health Sciences Mobile Clinical Research Associate Server Security Guide.

5.3 Setting Up Oracle Advanced Queuing

The Mobile CRA Server uses Oracle AQ to send and receive asynchronous messages. Complete the following setup to configure Mobile CRA Server to use Oracle AQ.

1. Navigate to Services, select Messaging, and then select JMS Modules.
The JMS Module screen is displayed.

Figure 5-9 JMS Module Screen

2. Click Lock and Edit.

3. Click New to create a new JMS module.
The Create JMS System Module screen is displayed.

4. Enter McraJmsSysMod as the name of your system module.

Figure 5-10 Creating a New JMS Module

5. Enter a descriptor file name (optional).
If you do not provide the descriptor file name, a default file name is assigned.

6. Specify the location where you may want to place the descriptor of this system module (optional).

7. Click Next.

8. In the Targets section, select the server or cluster on which you want to deploy this JMS system module.

Figure 5-11 Selecting Target Server

9. Click Next.

10. Select Would you like to add resources to this JMS system module? if you want to add resources.

Figure 5-12 Adding Resources to the JMS System Module

11. Click Next.

12. Click Finish.
The list of resources type is displayed.

13. Click New.

14. Select Foreign Server as the resource.

Figure 5-13 Selecting Type of Resource

The Foreign Server Properties screen is displayed.

15. Enter OracleAQFS as the foreign server name.

Figure 5-14 Foreign Server Properties

16. Click Next.
The Targets screen is displayed. Accept the default targets where the JMS resource is targeted.

Figure 5-15 Accepting Default Target

The foreign server is created successfully.

17. Click Finish.

18. Click OracleAQFS.

19. In the Setting for OracleAQFS screen, select the Configuration tab.

20. Select the General subtab and enter the JNDI initial context factory name as oracle.jms.AQjmsInitialContextFactory.

21. Remove value from JNDI Connection URL and JNDI Properties Credential.

22. Enter JNDI Properties as datasource=jdbc/mobileaq.

23. Click Save to save the settings.
A message is displayed indicating that the settings are updated.

24. Select the Destinations subtab, click New, and enter the foreign destination properties in the Create a New Foreign JMS Destination screen.
Name: /jms/aq/tripReportQueue

JNDI Name: /jms/aq/tripReportQueue

Remote JNDI Name: Queues/<schema>.trip_report_queue, in which mobileaq is installed. See Section 2.2.

mobileaq.trip_report_queue is the queue that queues the trip report schema.

mobileaq is the schema in which the MCAQ_ADMIN is installed. See Section 2.2.

trip_report_queue is the queue in that schema, which the installer creates.

25. Select Connection Factories subtab, click New, and enter the foreign connection factory properties in the Create a New Foreign JMS Connection Factory screen.
Name: /jms/aq/mobileQueueCF

Local JNDI Name: /jms/aq/mobileQueueCF

Remote JNDI Name: XAQueueConnectionFactory

26. Click OK.

27. Click Activate Changes.

28. Restart the server for changes to take effect.

6 Deploying the Mobile CRA Configuration Utility

This chapter details the deployment of the Mobile CRA Configuration Utility. It includes the following sections:

- Section 6.1, "Verifying the Installation Package"

- Section 6.2, "Configuring Data Sources for Mobile CRA Configuration Utility"

- Section 6.3, "Configuring Security for Mobile CRA Configuration Utility"

- Section 6.4, "Using Single Sign On and Lightweight Directory Access Protocol for Mobile Clinical Research Associate Server"

- Section 6.5, "Deploying Mobile CRA Server Configuration Utility"

- Section 6.6, "Customizing the Configuration File for Mobile CRA Configuration Utility"

- Section 6.7, "Verifying Deployment"

6.1 Verifying the Installation Package

You must validate the installation package before deploying. To validate, ensure that:

- The Install package is deployed as an Enterprise Archive file called Mobile CRA_AdminUI.ear.

- The EAR file contains ADF related application files.

- The EAR file also includes the WAR file, which contains the actual web application.

- The file name contains the build version as mentioned in the Release Notes.

Note:
For deploying the Mobile CRA Configuration Utility, see Oracle WebLogic Administration Guide.

6.2 Configuring Data Sources for Mobile CRA Configuration Utility

You need to configure the following data sources for the Mobile CRA Configuration Utility:

- jdbc/ae - Connects to the alerts schema and handles the alert generation.

- jdbc/mobileaq - Connects to the Oracle AQ schema and handles the asynchronous message handling of trip report.

- jdbc/mobilecda - Connects to the CDA schema and handles the CDA adapter related functionality.

- jdbc/mobilecra - Connects to the Mobile CRA server schema and handles the Mobile CRA server functionality.

- jdbc/mobilectms - Connects to the Mobile CRA Trip Report schema and handles the trip report configuration and other Mobile CRA Configuration Utility related functionality.

The following steps explain how to create jdbc/mobilecda data source:

1. Within the Server Administration Console, select Data Sources under Services.

Figure 6-1 Server Administration Console

The Summary of JDBC Data Sources screen is displayed.

2. Select New and then select Generic Data Source from the drop-down list.

Figure 6-2 Summary of JDBC Data Sources Screen

The Create a New JDBC Data Source screen is displayed.

3. Enter jdbc/mobilecda as the name and JNDI name to connect to MCRE_ADMIN schema.

Figure 6-3 Creating a New JDBC Data Source Screen

4. Select database driver as Oracle Driver (Thin XA) (versions: 9.0.1 and later).

Note:
In case the WebLogic Server version is 10.3.6.0 (the default is 10.3.5.0), for jdbc/mobilecda, you should select Database Driver as Oracle's Driver (Thin) during the installation.

Figure 6-4 Selecting Database Driver

5. Select default settings as displayed in Figure 6-5.

Figure 6-5 Selecting Default Settings

6. Configure connection properties as displayed in Figure 6-6.

Figure 6-6 Configuring Connection Properties

7. Upon completion, select Test Configuration to validate the connection.

Figure 6-7 Selecting Test Configuration

The Connection test succeeded message is displayed.

8. Repeat Step 3 to 7 to create jdbc/ae, jdbc/mobileaq, jdbc/mobilecra, and jdbc/mobilectms.

Note:
For jdbc/mobilectms, you should select Database Driver as Oracle's Driver (Thin) instead of (Thin XA) during the installation.

Note:
For information about the NS_ADMIN data source, see the Oracle Health Sciences Mobile Clinical Research Associate Health Sciences Push Notification Service Installation and Configuration Guide.

6.3 Configuring Security for Mobile CRA Configuration Utility

For information about configuring security for Mobile CRA Server, see Oracle Health Sciences Mobile Clinical Research Associate Server Security Guide.

6.4 Using Single Sign On and Lightweight Directory Access Protocol for Mobile Clinical Research Associate Server

To use Single Sign On (SSO) and Lightweight Directory Access Protocol (LDAP), see the following documents:

- http://docs.oracle.com/cd/E29306_01/index.htm

- http://docs.oracle.com/cd/E27559_01/index.htm

6.5 Deploying Mobile CRA Server Configuration Utility

To deploy Mobile CRA Server Configuration Utility, perform the following:

1. Log in to the Oracle WebLogic Server Administration Console.

2. Within Server Administration, select Deployments.

Figure 6-8 Selecting Deployments

The Summary of Deployments screen is displayed.

3. Select Install to deploy application.

Figure 6-9 Summary of Deployments Screen

4. Browse the directory where the install package is located.

Figure 6-10 Browsing the Directory

5. Select the Mobile CRA_AdminUI_v1.3.ear file.

Figure 6-11 Selecting the Default File

6. Select the Install this deployment as an application option.

Figure 6-12 Choosing the Targeting Style

7. Select default settings as displayed in Figure 6-13.

Figure 6-13 Selecting the Default Settings

8. Select Finish to complete installation.

Figure 6-14 Selecting Finish

9. Validate that the installed application is listed on the Deployments screen.

Figure 6-15 Validating the Application

6.6 Customizing the Configuration File for Mobile CRA Configuration Utility

To customize the configuration file config_adminui.xml for Mobile CRA Configuration Utility, perform the following:

1. From the Config folder of the media pack, select config_adminui.xml.
This is a template file where you have to update values for customization.

2. Create a copy of config_adminui.xml and save it as adminui_plan.xml.
For an example of config_adminui.xml, see Appendix B.

3. Modify configuration values for your environment.
The adminui_plan.xml file lets you configure your Mobile CRA Configuration Application to point to the right CTMS and ASAAG servers.

4. Change the following basic settings in the adminui_plan.xml file:

Note:
The ctmsAdapter.hostname, ctmsAdapter.port, and adaptiveSaag.url properties in the adminui_plan.xml file should match the respective values defined in the plan.xml file for MobileCRA Server Application. For more information, see Section 5.1.5.

- ctmsAdapter.hostname - The name of the CTMS host to which the mobile instance should connect for accessing and manipulating data. For example, server.domain.com.

Note:
If you use CTMS IP 2015, enter the IP address instead of host name.

- ctmsAdapter.port - The CTMS port host. For example, 8080. If the default port is used, enter a value 0 instead of null.

- adaptiveSaag.url - Host name of the ASAAG server. For example, server.domain.com.

6.7 Verifying Deployment

To verify deployment, perform the following:

1. Enter the following URL for the Mobile CRAConfiguration Utility:
http://<server:port>/MobileAdminCRA/faces/login.jspx?

The Login page is displayed.

2. Figure 6-16 Login Page

3. Enter the user name and password.
The Mobile CRA Configutation Utility Home Page is displayed.

Figure 6-17 The Mobile CRA Configuration Utility Home Page

7 Mobile Clinical Research Associate Server Application Setup

You must download and install the Mobile application for iPad or iPhone from the App store. This chapter details the set up of Mobile CRA Server. It includes the following sections:

- Section 7.1, "Setting up Mobile Clinical Research Associate Server for iPad"

- Section 7.2, "Setting up Mobile Clinical Research Associate Server for iPhone"

- Section 7.3, "Setting up Mobile Clinical Research Associate Server for Tablet, Phablet, or Smartphone"

7.1 Setting up Mobile Clinical Research Associate Server for iPad

7.1.1 Setting up the Server

To set up the Mobile CRA server, perform the following:

1. Navigate to the iPad Home screen.

2. Tap Settings.

3. Tap Mobile CRA.
The Mobile CRA screen is displayed.

4. Set the idle time for a session in the Time out field. Once this specified amount of time has passed, you will be logged off from your Mobile CRA Server session.

5. Enter the server address in the format, http://hostname:port or https://hostname:port.

7.1.2 Running and Logging to the Application

To run and log in to the application, perform the following:

1. Click Home.

2. Tap Mobile CRA.

3. On the Login screen, enter the user ID and password.

4. Tap Login.

7.2 Setting up Mobile Clinical Research Associate Server for iPhone

7.2.1 Setting up the Server

To set up the Mobile CRA Server, perform the following:

1. Navigate to the iPhone Home screen.

2. Tap Settings.

3. Tap Mobile CRA.
The Mobile CRA screen is displayed.

4. Set the idle time for a session in the Time out field. Once this specified amount of time has passed, you will be logged off from your Mobile CRA Server session.

5. Enter the Mobile CRA server address in the format http://hostname:port or https://hostname:port.

6. Tap Back.

7.2.2 Running and Logging to the Application

To run and log in to the application, perform the following:

1. Navigate to the Home screen.

2. Tap Mobile CRA.

3. On the Login screen, enter the user ID and password.

4. Tap Login.

7.3 Setting up Mobile Clinical Research Associate Server for Tablet, Phablet, or Smartphone

To log in or set up the Mobile CRA server, perform the following:

1. Navigate to the Tablet, Phablet, or Smartphone Home screen.

2. Tap Mobile CRA. The Mobile CRA Login screen is displayed.

3. Enter the server address, user ID, and password. The format of the server address is:
http://hostname:port or https://hostname:port.

4. Tap Login.

5. Tap Settings on the navigation bar.

6. Tap Application Time out.

7. Set the idle time for a session. Once this specified time has passed, you are logged out of the Mobile CRA Server session.

A Sample Scripts

This appendix provides the following sample SQL scripts:

- Appendix A, "Create_user.sql"

- Appendix A, "Create_queue_tables.sql"

A.1 Create_user.sql

Use the following script to create the user. The script prompts for the password.

create user mobileaq identified by &&mobileaq_pwd;

grant connect, resource to mobileaq;

grant aq_user_role to mobileaq;

Grant execute ON sys.dbms_aqadm TO mobileaq;

Grant execute ON sys.dbms_aq TO mobileaq;

Grant execute ON sys.dbms_aqin TO mobileaq;

Grant execute ON sys.dbms_aqjms TO mobileaq;

A.2 Create_queue_tables.sql

DECLARE
po dbms_aqadm.aq$_purge_options_t;
BEGIN
po.block := FALSE;
DBMS_AQADM.PURGE_QUEUE_TABLE(
queue_table => 'TRIP_REPORT_QT',
purge_condition => NULL,
purge_options => po);
END;

BEGIN

dbms_aqadm.drop_queue_table('TRIP_REPORT_QT', TRUE, FALSE);

dbms_aqadm.create_queue_table(
queue_table=>'TRIP_REPORT_QT',
queue_payload_type=>'sys.aq$_jms_text_message');

DBMS_AQADM.CREATE_QUEUE (
queue_name => 'trip_report_queue'
, queue_table => 'mobileaq.trip_report_qt'
, queue_type => DBMS_AQADM.NORMAL_QUEUE
, max_retries => 5
, retry_delay => 0
, retention_time => 1800
, dependency_tracking => FALSE
, comment => 'queue for mobile trip report'
, auto_commit => FALSE);

DBMS_AQADM.START_QUEUE('trip_report_queue');

END;

CREATE TABLE "TRIP_REPORT_TRACKING"
(
"TRACKING_ID"     NUMBER(10,0),
"USER_ID"        VARCHAR2(80 BYTE),
"TRIP_REPORT_ID" VARCHAR2(80 BYTE),
"TEMPLATE_ID"    VARCHAR2(80 BYTE),
"CTMS_TRIP_REPORT_QRY_REQUEST" CLOB,
"QUERIED_CANONICAL_TRIP_REPORT" CLOB,
"CTMS_TRIP_REPORT_UPD_REQUEST" CLOB,
"TO_UPD_CANONICAL_TRIP_REPORT" CLOB,
"STATUS"     VARCHAR2(20 BYTE),
"ERROR_CODE" VARCHAR2(80 BYTE),
"ERROR_TEXT" VARCHAR2(2000 BYTE),
"CREATED_BY" VARCHAR2(80 BYTE),
"CREATION_TS" DATE,
"MODIFIED_BY" VARCHAR2(80 BYTE),
"MODIFICATION_TS" DATE,
"LAST_REQ_OPERATION" VARCHAR2(15 BYTE),
PRIMARY KEY ("TRACKING_ID")
);

create sequence TRIP_REPORT_TRACKING_SEQ start with 1 increment by 1;

B Sample XML Files

This appendix provides the following sample XML files, which you may use to customizing the configuration file:

- Appendix B, "Config.xml"

- Appendix B, "Plan.xml"

- Appendix B, "config_adminui.xml"

B.1 Config.xml

<?xml version='1.0' encoding='UTF-8'?>
<deployment-plan xmlns="http://xmlns.oracle.com/weblogic/deployment-plan"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://xmlns.oracle.com/weblogic/deployment-plan http://xmlns.oracle.com/weblogic/deployment-plan/1.0/deployment-plan.xsd"
global-variables="false">
<application-name>oracle.hs.mobilecra.ear</application-name>
<variable-definition>
<variable>
<name>ctmsAdapter.hostname</name>
<value></value>
</variable>
<!-- If port is not defined then default it to 0 -->
<variable>
<name>ctmsAdapter.port</name>
<value></value>
</variable>
<variable>
<name>useCDA</name>
<value></value>
</variable>
<variable>
<name>adaptiveSaag.version</name>
<value></value>
</variable>
<variable>
<name>adaptiveSaag.url</name>
<value></value>
</variable>
<variable>
<name>adaptiveSaag.usekpi</name>
<value></value>
</variable>
<variable>
<name>pushNotificationEngine.maximumPoolSize</name>
<value></value>
</variable>
<variable>
<name>pushNotificationEngine.timeUnit</name>
<value></value>
</variable>
<variable>
<name>pushNotificationEngine.engineLockTimeout</name>
<value></value>
</variable>
<variable>
<name>notificationEngineScheduler.initialDelay</name>
<value></value>
</variable>
<variable>
<name>notificationEngineScheduler.period</name>
<value></value>
</variable>
<variable>
<name>notificationEngineScheduler.timeUnit</name>
<value></value>
</variable>
<variable>
<name>cdaAdapter.wsdlLocation</name>
<value></value>
</variable>
<variable>
<name>pushNotificationService.url</name>
<value></value>
</variable>
<variable>
<name>mobilecraLog.Level</name>
<value>INFO</value>
</variable>
<variable>
<name>tripReport.maxBeanPoolSize</name>
<value></value>
</variable>
<variable>
<name>tripReport.initialBeanPoolSize</name>
<value></value>
</variable>
</variable-definition>
<module-override>
<module-name>oracle.hs.mobilecra.war</module-name>
<module-type>war</module-type>
<module-descriptor external="false">
<root-element>web-app</root-element>
<uri>WEB-INF/web.xml</uri>
<variable-assignment>
<name>ctmsAdapter.hostname</name>
<xpath>/web-app/context-param/[param-name="ctmsAdapter.hostname"]/param-value</xpath>
<operation>replace</operation>
</variable-assignment>
<variable-assignment>
<name>ctmsAdapter.port</name>
<xpath>/web-app/context-param/[param-name="ctmsAdapter.port"]/param-value</xpath>
<operation>replace</operation>
</variable-assignment>
<variable-assignment>
<name>useCDA</name>
<xpath>/web-app/context-param/[param-name="useCDA"]/param-value</xpath>
<operation>replace</operation>
</variable-assignment>
<variable-assignment>
<name>adaptiveSaag.version</name>
<xpath>/web-app/context-param/[param-name="adaptiveSaag.version"]/param-value</xpath>
<operation>replace</operation>
</variable-assignment>
<variable-assignment>
<name>adaptiveSaag.url</name>
<xpath>/web-app/context-param/[param-name="adaptiveSaag.url"]/param-value</xpath>
<operation>replace</operation>
</variable-assignment>
<variable-assignment>
<name>adaptiveSaag.usekpi</name>
<xpath>/web-app/context-param/[param-name="adaptiveSaag.usekpi"]/param-value</xpath>
<operation>replace</operation>
</variable-assignment>
<variable-assignment>
<name>pushNotificationEngine.maximumPoolSize</name>
<xpath>/web-app/context-param/[param-name="pushNotificationEngine.maximumPoolSize"]/param-value</xpath>
<operation>replace</operation>
</variable-assignment>
<variable-assignment>
<name>pushNotificationEngine.timeUnit</name>
<xpath>/web-app/context-param/[param-name="pushNotificationEngine.timeUnit"]/param-value</xpath>
<operation>replace</operation>
</variable-assignment>
<variable-assignment>
<name>pushNotificationEngine.engineLockTimeout</name>
<xpath>/web-app/context-param/[param-name="pushNotificationEngine.engineLockTimeout"]/param-value</xpath>
<operation>replace</operation>
</variable-assignment>
<variable-assignment>
<name>notificationEngineScheduler.initialDelay</name>
<xpath>/web-app/context-param/[param-name="notificationEngineScheduler.initialDelay"]/param-value</xpath>
<operation>replace</operation>
</variable-assignment>
<variable-assignment>
<name>notificationEngineScheduler.period</name>
<xpath>/web-app/context-param/[param-name="notificationEngineScheduler.period"]/param-value</xpath>
<operation>replace</operation>
</variable-assignment>
<variable-assignment>
<name>notificationEngineScheduler.timeUnit</name>
<xpath>/web-app/context-param/[param-name="notificationEngineScheduler.timeUnit"]/param-value</xpath>
<operation>replace</operation>
</variable-assignment>
<variable-assignment>
<name>cdaAdapter.wsdlLocation</name>
<xpath>/web-app/context-param/[param-name="cdaAdapter.wsdlLocation"]/param-value</xpath>
<operation>replace</operation>
</variable-assignment>
<variable-assignment>
<name>pushNotificationService.url</name>
<xpath>/web-app/context-param/[param-name="pushNotificationService.url"]/param-value</xpath>
<operation>replace</operation>
</variable-assignment>
<variable-assignment>
<name>mobilecraLog.Level</name>
<xpath>/web-app/context-param/[param-name="mobilecraLog.Level"]/param-value</xpath>
<operation>replace</operation>
</variable-assignment>
</module-descriptor>
</module-override>
<module-override>
<module-name>tripreport_messaging.jar</module-name>
<module-type>ejb</module-type>
<module-descriptor external="false">
<root-element>weblogic-ejb-jar</root-element>
<uri>META-INF/weblogic-ejb-jar.xml</uri>
<variable-assignment>
<name>tripReport.maxBeanPoolSize</name>
<xpath>/weblogic-ejb-jar/weblogic-enterprise-bean/[ejb-name="TripReportAQMDBBeanBean"]/message-driven-descriptor/pool/max-beans-in-free-pool</xpath>
<operation>replace</operation>
</variable-assignment>
<variable-assignment>
<name>tripReport.initialBeanPoolSize</name>
<xpath>/weblogic-ejb-jar/weblogic-enterprise-bean/[ejb-name="TripReportAQMDBBeanBean"]/message-driven-descriptor/pool/initial-beans-in-free-pool</xpath>
<operation>replace</operation>
</variable-assignment>
</module-descriptor>
</module-override>
<config-root></config-root>
</deployment-plan>

B.2 Plan.xml

<?xml version='1.0' encoding='UTF-8'?>
<deployment-plan xmlns="http://xmlns.oracle.com/weblogic/deployment-plan"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://xmlns.oracle.com/weblogic/deployment-plan http://xmlns.oracle.com/weblogic/deployment-plan/1.0/deployment-plan.xsd"
global-variables="false">
<application-name>oracle.hs.mobilecra.ear</application-name>
<variable-definition>
<variable>
<name>informAPIService.url</name>
<value>http://<host>:<port>/mobilecraservices/ias/rest
where, host and port are same as that of Mobile CRA.
Enter the IP address instead of host name.
</variable>
<variable>
<name>ctmsAdapter.hostname</name>
<value>servername.domain.com</value>
</variable>
<!-- If port is not defined then default it to 0 -->
<variable>
<name>ctmsAdapter.port</name>
<value><0></value>
</variable>
<variable>
<name>useCDA</name>
<value>true</value>
</variable>
<variable>
<name>pushNotificationEngine.maximumPoolSize</name>
<value>5</value>
</variable>
<variable>
<name>pushNotificationEngine.timeUnit</name>
<value>seconds</value>
</variable>
<variable>
<name>pushNotificationEngine.engineLockTimeout</name>
<value>10</value>
</variable>
<variable>
<name>notificationEngineScheduler.initialDelay</name>
<value>40</value>
</variable>
<variable>
<name>notificationEngineScheduler.period</name>
<value>300</value>
</variable>
<variable>
<name>notificationEngineScheduler.timeUnit</name>
<value>seconds</value>
</variable>
<variable>
<name>cdaAdapter.wsdlLocation</name>
<value>http://<servername>/analytics/saw.dll?WSDL</value>
</variable>
<variable>
<name>pushNotificationService.url</name>
<value><notificationservername.domain.com></value>
</variable>
<variable>
<name>mobilecraLog.Level</name>
<value></value>
</variable>
<variable>
<name>tripReport.maxBeanPoolSize</name>
<value>10</value>
</variable>
<variable>
<name>tripReport.initialBeanPoolSize</name>
<value>10</value>
</variable>
</variable-definition>
<module-override>
<module-name>oracle.hs.mobilecra.war</module-name>
<module-type>war</module-type>
<module-descriptor external="false">
<root-element>web-app</root-element>
<uri>WEB-INF/web.xml</uri>
<variable-assignment>
<name>informAPIService.url</name>
<xpath>/web-app/context-param/[param-name="informAPIService.url"]/
param-value</xpath>
<operation>replace</operation>
</variable-assignment>
<variable-assignment>
<name>ctmsAdapter.hostname</name>
<xpath>/web-app/context-param/[param-name="ctmsAdapter.hostname"]/
param-value</xpath>
<operation>replace</operation>
</variable-assignment>
<variable-assignment>
<name>ctmsAdapter.port</name>
<xpath>/web-app/context-param/[param-name="ctmsAdapter.port"]/
param-value</xpath>
<operation>replace</operation>
</variable-assignment>
<variable-assignment>
<name>useCDA</name>
<xpath>/web-app/context-param/[param-name="useCDA"]/
param-value</xpath>
<operation>replace</operation>
</variable-assignment>
<variable-assignment>
<name>pushNotificationEngine.maximumPoolSize</name>
<xpath>/web-app/context-param/[param-name=
"pushNotificationEngine.maximumPoolSize"]/param-value</xpath>
<operation>replace</operation>
</variable-assignment>
<variable-assignment>
<name>pushNotificationEngine.timeUnit</name>
<xpath>/web-app/context-param/[param-name=
"pushNotificationEngine.timeUnit"]/param-value</xpath>
<operation>replace</operation>
</variable-assignment>
<variable-assignment>
<name>pushNotificationEngine.engineLockTimeout</name>
<xpath>/web-app/context-param/[param-name=
"pushNotificationEngine.engineLockTimeout"]/param-value</xpath>
<operation>replace</operation>
</variable-assignment>
<variable-assignment>
<name>SimpleScheduler.initialDelay</name>
<xpath>/web-app/context-param/[param-name=
"notificationEngineScheduler.initialDelay"]/param-value</xpath>
<operation>replace</operation>
</variable-assignment>
<variable-assignment>
<name>SimpleScheduler.period</name>
<xpath>/web-app/context-param/[param-name=
"notificationEngineScheduler.period"]/param-value</xpath>
<operation>replace</operation>
</variable-assignment>
<variable-assignment>
<name>notificationEngineScheduler.timeUnit</name>
<xpath>/web-app/context-param/[param-name=
"notificationEngineScheduler.timeUnit"]/param-value</xpath>
<operation>replace</operation>
</variable-assignment>
<variable-assignment>
<name>cdaAdapter.wsdlLocation</name>
<xpath>/web-app/context-param/[param-name=
"cdaAdapter.wsdlLocation"]/param-value</xpath>
<operation>replace</operation>
</variable-assignment>
<variable-assignment>
<name>pushNotificationService.url</name>
<xpath>/web-app/context-param/[param-name=
"pushNotificationService.url"]/param-value</xpath>
<operation>replace</operation>
</variable-assignment>
<variable-assignment>
<name>mobilecraLog.Level</name>
<xpath>/web-app/context-param/[param-name="
mobilecraLog.Level"]/param-value</xpath>
<operation>replace</operation>
</variable-assignment>
</module-descriptor>
</module-override>
<module-override>
<module-name>tripreport_messaging.jar</module-name>
<module-type>ejb</module-type>
<module-descriptor external="false">
<root-element>weblogic-ejb-jar</root-element>
<uri>META-INF/weblogic-ejb-jar.xml</uri>
<variable-assignment>
<name>tripReport.maxBeanPoolSize</name>
<xpath>/weblogic-ejb-jar/weblogic-enterprise-bean/
[ejb-name="TripReportAQMDBBeanBean"]/message-driven-descriptor/
pool/max-beans-in-free-pool</xpath>
<operation>replace</operation>
</variable-assignment>
<variable-assignment>
<name>tripReport.initialBeanPoolSize</name>
<xpath>/weblogic-ejb-jar/weblogic-enterprise-bean/[ejb-name=
"TripReportAQMDBBeanBean"]/message-driven-descriptor/pool/
initial-beans-in-free-pool</xpath>
<operation>replace</operation>
</variable-assignment>
</module-descriptor>
</module-override>
<config-root></config-root>
</deployment-plan>

B.3 config_adminui.xml

<?xml version='1.0' encoding='UTF-8'?>
<deployment-plan xmlns="http://xmlns.oracle.com/weblogic/deployment-plan"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

xsi:schemaLocation="http://xmlns.oracle.com/weblogic/depl
oyment-plan http://xmlns.oracle.com/weblogic/deployment-
plan/1.0/deployment-plan.xsd"
global-variables="false">
<application-name>MobileCRA_AdminUI.ear</application-name>
<variable-definition>
<variable>
<name>ctmsAdapter.hostname</name>
<value></value>
</variable>
<!-- If port is not defined then default it to 0 -->
<variable>
<name>ctmsAdapter.port</name>
<value></value>
</variable>
<variable>
<name>useCDA</name>
<value></value>
</variable>
<variable>
<name>adaptiveSaag.version</name>
<value></value>
</variable>
<variable>
<name>adaptiveSaag.url</name>
<value></value>
</variable>
<variable>
<name>adaptiveSaag.usekpi</name>
<value></value>
</variable>
<variable>
<name>pushNotificationEngine.maximumPoolSize</name>
<value></value>
</variable>
<variable>
<name>pushNotificationEngine.timeUnit</name>
<value></value>
</variable>
<variable>
<name>pushNotificationEngine.engineLockTimeout</name>
<value></value>
</variable>
<variable>
<name>notificationEngineScheduler.initialDelay</name>
<value></value>
</variable>
<variable>
<name>notificationEngineScheduler.period</name>
<value></value>
</variable>
<variable>
<name>notificationEngineScheduler.timeUnit</name>
<value></value>
</variable>
<variable>
<name>notification.provider</name>
<value>GCM</value>
</variable>
<variable>
<name>cdaAdapter.wsdlLocation</name>
<value></value>
</variable>
<variable>
<name>pushNotificationService.url</name>
<value></value>
</variable>
<variable>
<name>mobilecraLog.Level</name>
<value></value>
</variable>
<variable>
<name>tripReport.maxBeanPoolSize</name>
<value></value>
</variable>
<variable>
<name>tripReport.initialBeanPoolSize</name>
<value></value>
</variable>
</variable-definition>
<module-override>
<module-name>MobileAdminApp.war</module-name>
<module-type>war</module-type>
<module-descriptor external="false">
<root-element>web-app</root-element>
<uri>WEB-INF/web.xml</uri>
<variable-assignment>
<name>ctmsAdapter.hostname</name
<xpath>/web-app/context-param/[param-name="ctmsAdapter.hostname"]/param-
value</xpath>
<operation>replace</operation>
</variable-assignment>
<variable-assignment>
<name>ctmsAdapter.port</name>
<xpath>/web-app/context-param/[param-
name="ctmsAdapter.port"]/param-value</xpath>
<operation>replace</operation>
</variable-assignment>
<variable-assignment>
<name>useCDA</name>
<xpath>/web-app/context-param/[param-name="useCDA"]/param-
value</xpath>
<operation>replace</operation>
</variable-assignment>
<variable-assignment>
<name>adaptiveSaag.version</name>
<xpath>/web-app/context-param/[param-
name="adaptiveSaag.version"]/param-value</xpath>
<operation>replace</operation>
</variable-assignment>
<variable-assignment>
<name>adaptiveSaag.url</name>
<xpath>/web-app/context-param/[param-
name="adaptiveSaag.url"]/param-value</xpath>
<operation>replace</operation>
</variable-assignment>
<variable-assignment>
<name>adaptiveSaag.usekpi</name>
<xpath>/web-app/context-param/[param-
name="adaptiveSaag.usekpi"]/param-value</xpath>
<operation>replace</operation>
</variable-assignment>
<variable-assignment>
<name>pushNotificationEngine.maximumPoolSize</name>
<xpath>/web-app/context-param/[param-
name="pushNotificationEngine.maximumPoolSize"]/param-
value</xpath>
<operation>replace</operation>
</variable-assignment>
<variable-assignment>
<name>pushNotificationEngine.timeUnit</name>
<xpath>/web-app/context-param/[param-
name="pushNotificationEngine.timeUnit"]/param-
value</xpath>
<operation>replace</operation>
</variable-assignment>
<variable-assignment>
<name>pushNotificationEngine.engineLockTimeout</name>
<xpath>/web-app/context-param/[param-
name="pushNotificationEngine.engineLockTimeout"]/param-
value</xpath>
<operation>replace</operation>
</variable-assignment>
<variable-assignment>
<name>notificationEngineScheduler.initialDelay</name>
<xpath>/web-app/context-param/[param-
name="notificationEngineScheduler.initialDelay"]/param-
value</xpath>
<operation>replace</operation>
</variable-assignment>
<variable-assignment>
<name>notificationEngineScheduler.period</name>
<xpath>/web-app/context-param/[param-
name="notificationEngineScheduler.period"]/param-
value</xpath>
<operation>replace</operation>
</variable-assignment>
<variable-assignment>
<name>notificationEngineScheduler.timeUnit</name>
<xpath>/web-app/context-param/[param-
name="notificationEngineScheduler.timeUnit"]/param-
value</xpath>
<operation>replace</operation>
</variable-assignment>
<variable-assignment>
<name>cdaAdapter.wsdlLocation</name>
<xpath>/web-app/context-param/[param-
name="cdaAdapter.wsdlLocation"]/param-
value</xpath>
<operation>replace</operation>
</variable-assignment>
<variable-assignment>
<name>pushNotificationService.url</name>
<xpath>/web-app/context-param/[param-
name="pushNotificationService.url"]/param-
value</xpath>
<operation>replace</operation>
</variable-assignment>
<variable-assignment>
<name>mobilecraLog.Level</name>
<xpath>/web-app/context-param/[param-
name="mobilecraLog.Level"]/param-
value</xpath>
<operation>replace</operation>
</variable-assignment>
</module-descriptor>
</module-override>
<module-override>
<module-name>tripreport_messaging.jar</module-name>
<module-type>ejb</module-type>
<module-descriptor external="false">
<root-element>weblogic-ejb-jar</root-element>
<uri>META-INF/weblogic-ejb-jar.xml</uri>
<variable-assignment>
<name>tripReport.maxBeanPoolSize</name>
<xpath>/weblogic-ejb-jar/weblogic-enterprise-bean/[ejb-
name="TripReportAQMDBBeanBean"]/message-driven-
descriptor/pool/max-beans-in-free-pool</xpath>
<operation>replace</operation>
</variable-assignment>
<variable-assignment>
<name>tripReport.initialBeanPoolSize</name>
<xpath>/weblogic-ejb-jar/weblogic-enterprise-bean/[ejb-
name="TripReportAQMDBBeanBean"]/message-driven-
descriptor/pool/initial-beans-in-free-pool</xpath>
<operation>replace</operation>
</variable-assignment>
</module-descriptor>
</module-override>
<config-root></config-root>
</deployment-plan>

C Adding SDV Section to the Trip Report

This appendix provides procedures to add SDV section to the Verified CRFs Checklist Type Trip Report.

This appendix includes the following sections:

- Section C.1, "Creating Verified CRFs Checklist Trip Report Type"

- Section C.2, "Adding Attributes to the Verified CRFs Checklist"

- Section C.3, "Setting the Category Order of the Verified CRFs Checklist in the Trip Report"

- Section C.4, "Including Verified CRFs Checklist to the Trip Report"

- Section C.5, "Processing the Verified CRFs Checklist"

C.1 Creating Verified CRFs Checklist Trip Report Type

To create Verified CRFs Checklist trip report type, perform the following:

1. On the Mobile Trip Report Configuration screen, click Create in the Trip Report Types pane.
The Create Trip Report Type window appears.

2. Enter Verified CRFs Checklist in the Type Name field.

3. Enter SDV Section in the Description field.

4. Enter the details in the remaining fields as applicable and click OK.

Figure C-1 Create Trip Report Type

The Verified CRFs Checklist trip report type is created.

Figure C-2 Verified CRFs Checklist Trip Report Type

C.2 Adding Attributes to the Verified CRFs Checklist

To add attributes to the Verified CRFs Checklist, perform the following:

1. Select the Verified CRFs Checklist trip report type in the Trip Report Types pane.

2. Click Add in the Selected Type: Verified CRFs Checklist pane to add the attributes.
The Add Type Attribute window appears.

3. Enter the values in the required fields as follows:

- Attribute Name: ActivityType

- Caption: Activity Type

- Category: Verified CRFs Checklist

4. Select CHECKLIST_ACTIVITY from the Picklist Field drop-down list.

5. Enter the details in the remaining fields as applicable and click OK.

Figure C-3 ActivityType Attribute

The ActivityType attribute is added to the Verified CRFs Checklist.

6. Similarly, add the following attributes to the Verified CRFs Checklist:

Figure C-4 Comment Attribute

Figure C-5 CreatedByName Attribute

Figure C-6 Description Attribute

Figure C-7 Display Attribute

Figure C-8 Status Attribute

C.3 Setting the Category Order of the Verified CRFs Checklist in the Trip Report

To set the category order of the Verified CRFs Checklist in the Trip Report, perform the following:

1. Select Trip Report in the Trip Report Types pane and click Edit.
The Edit Trip Report Type window appears.

2. Enter Verified CRFs Checklist in the required order in the Category Order field and click OK.
In this example, the Verified CRFs Checklist is entered in the last and so it is displayed as the last row in the Trip Report.

Figure C-9 Setting the Order of the Verified CRFs Checklist

C.4 Including Verified CRFs Checklist to the Trip Report

To include Verified CRFs Checklist to the Trip Report, perform the following:

1. Select Trip Report in the Trip Report Types pane.

2. Click Subitems in the Selected Type: Trip Report pane.

Figure C-10 Including Verified CRFs Checklist to the Trip Report

3. Select Add Item against Verified CRFs Checklist and click Save.

C.5 Processing the Verified CRFs Checklist

Update the CANONICAL_TO_CTMS_UPDATE trip report style to process the Verified CRFs Checklist in the canonical trip report and save it as a Checklist Item type in the trip report, as follows:

Note:
In the following code, the logic to save as Checklist Item type is from <xsl:for-each select="$canonicalDoc//can:Item[(not (@id) or @id='' or starts-with (@id, 'NEWITEM')) and @type='Verified CRFs Checklist']"> to </xsl:for-each>.

<xsl:template match="tns:ListOfClinicalChecklist">
<xsl:element name="tns:ListOfClinicalChecklist">
<xsl:apply-templates/>
<xsl:for-
each select="$canonicalDoc//can:Item[(not (@id) or @id='' or starts-
with (@id, 'NEWITEM')) and @type='Checklist Item']">
<xsl:element name="tns:ClinicalChecklist">
<xsl:element name="tns:Id">
<xsl:value-
of select="count(preceding::can:Attribute[@name='ActivityType'] | ancestor:
:can:Attribute[@name='ActivityType']) +1"/>
</xsl:element>
<xsl:element name="tns:Category">
<xsl:text>Check List</xsl:text>
</xsl:element>
<xsl:element name="tns:Type">
<xsl:value-
of select="can:Attribute[@name='ActivityType']/can:Value"/>
</xsl:element>
<xsl:element name="tns:CreatedByName">
<xsl:choose>
<xsl:when test="can:Attribute[@name='CreatedByName']/can:Value != ''">
<xsl:value-
of select="can:Attribute[@name='CreatedByName']/can:Value"/>
</xsl:when>
<xsl:otherwise>
<xsl:value-of select="$currentUser"/>
</xsl:otherwise>
</xsl:choose>
</xsl:element>
<xsl:element name="tns:Description">
<xsl:value-
of select="can:Attribute[@name='Description']/can:Value"/>
</xsl:element>
<xsl:element name="tns:Display">
<xsl:value-of select="can:Attribute[@name='Display']/can:Value"/>
</xsl:element>
<xsl:element name="tns:ShortComment">
<xsl:value-
of select="can:Attribute[@name='Comment']/can:Value"/>
</xsl:element>
</xsl:element>
<xsl:element name="tns:Status">
<xsl:value-of select="can:Attribute[@name='Status']/can:Value"/>
</xsl:element>
<xsl:element name="tns:ParentActivityId">
<xsl:value-of select="$tripReportId"/>
</xsl:element>
<xsl:element name="tns:ListOfLsClinicalChecklistAssignee">
<xsl:for-each select="can:Item[@type='Assignee']">
<xsl:element name="tns:LsClinicalChecklistAssignee">
<xsl:element name="tns:ActivityId">
<xsl:value-
of select="can:Attribute[@name='ActivityId']/can:Value"/>
</xsl:element>
<xsl:element name="tns:EmpId">
<xsl:value-of select="can:Attribute[@name='EmpID']/can:Value"/>
</xsl:element>
</xsl:element>
</xsl:for-each>
</xsl:element>
</xsl:element>
</xsl:for-each>

<xsl:for-
each select="$canonicalDoc//can:Item[(not (@id) or @id='' or starts-
with (@id, 'NEWITEM')) and @type='Verified CRFs Checklist']">
<xsl:element name="tns:ClinicalChecklist">
<xsl:element name="tns:Id">
<xsl:value-
of select="count(preceding::can:Attribute[@name='ActivityType'] | ancestor:
:can:Attribute[@name='ActivityType']) +1"/>
</xsl:element>
<xsl:element name="tns:Category">
<xsl:text>Check List</xsl:text>
</xsl:element>
<xsl:element name="tns:Type">
<xsl:value-
of select="can:Attribute[@name='ActivityType']/can:Value"/>
</xsl:element>
<xsl:element name="tns:CreatedByName">
<xsl:choose>
<xsl:when test="can:Attribute[@name='CreatedByName']/can:Value != ''">
<xsl:value-
of select="can:Attribute[@name='CreatedByName']/can:Value"/>
</xsl:when>
<xsl:otherwise>
<xsl:value-of select="$currentUser"/>
</xsl:otherwise>
</xsl:choose>
</xsl:element>
<xsl:element name="tns:Description">
<xsl:value-
of select="can:Attribute[@name='Description']/can:Value"/>
</xsl:element>
<xsl:element name="tns:Display">
<xsl:value-of select="can:Attribute[@name='Display']/can:Value"/>
</xsl:element>
<xsl:element name="tns:ShortComment">
<xsl:value-
of select="can:Attribute[@name='Comment']/can:Value"/>
</xsl:element>
<xsl:element name="tns:Status">
<xsl:value-of select="can:Attribute[@name='Status']/can:Value"/>
</xsl:element>
<xsl:element name="tns:ParentActivityId">
<xsl:value-of select="$tripReportId"/>
</xsl:element>
<xsl:element name="tns:ListOfLsClinicalChecklistAssignee">
<xsl:for-each select="can:Item[@type='Assignee']">
<xsl:element name="tns:LsClinicalChecklistAssignee">
<xsl:element name="tns:ActivityId">
<xsl:value-
of select="can:Attribute[@name='ActivityId']/can:Value"/>
</xsl:element>
<xsl:element name="tns:EmpId">
<xsl:value-
of select="can:Attribute[@name='EmpID']/can:Value"/>
</xsl:element>
</xsl:element>
</xsl:for-each>
</xsl:element>
</xsl:element>
</xsl:for-each>
</xsl:element>
</xsl:template>

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2015, Oracle and/or its affiliates. All rights reserved.

Trademark Notice

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

License Restrictions Warranty/Consequential Damages Disclaimer

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

Warranty Disclaimer

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

Restricted Rights Notice

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

Hazardous Applications Notice

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Third-Party Content, Products, and Services Disclaimer

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Alpha and Beta Draft Documentation Notice

If this document is in preproduction status:

This documentation is in preproduction status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.