DIAGRAM02_JANUS_CTR-TargetStateDiagram.pdf

PDF 194 KB Posted

Attached to
JReview Support
Solicitation number
FDA-SOL-15-3282
Issued by

About this file

DIAGRAM02

View the file

Other files

Show all 14

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

C lie nt

W or ks ta tio n

Pr es en ta tio n

Zo ne

Target State Diagram Janus Clinical Trials Repository (CTR) – PROD Environment

Description

Communications & Dependencies

Enterprise Services

Key Contacts Security Bucket Receives from

Sends to Version: 8 Last Modified: 7/21/2015

External Dependencies

Application Zone

D at a Zo ne A pp lic at io n Zo ne

Web Browser Reviewers, System Admin

WODC Internal

Web Server 01 Windows Server 1 Processor

8 GB RAM

100 GB Disk Space/SAN

1 FDA user web access to Presentation load balancer for Janus CTR

Application Server to External Enterprise Vocabulary Service (EVS) API (for code list look-up) (Configurable, HTTP: 80) (EXTERNAL)

Application Server to Database Server (Configurable: 1531)

M an ag em en t D

M Z

M an ag em en t S ha re d To ol s

Database Server 02 Red Hat Linux 4 Processor

128 GB RAM

500 TB Disk/SAN

Software: Database Oracle

Version: 11g

CTR Warehouse

Analysis Ready SDTM Database

7 8

Application Server to Analysis Ready Database (1531)

Database Server 01 Red Hat Linux 4 Processor

128 GB RAM

500 TB Disk/SAN

Software: Database Oracle

Version: 11g

FDA Single Sign-On ()

EVS at NCI Via API

The Janus Clinical Trials Repository (CTR) supports the validation, loading, and management of clinical study data in a warehouse repository and the creation of an analysis-ready extract database of enhanced SDTM views and custom views (shown in item #8 below).

CTR enhanced SDTM views can be accessed by reviewers using a variety of analytical tools (e.g., SAS, JMP, JReview). TSDs for SAS/ JMP and JReview access to the CTR views are shown in separate TSDs.

The CTR application architecture also will include:

▪ A web-based Admin Module for use by data managers/system administrators that is accessed via web browser

▪ A web interface that allows users to access custom views and create custom extracts through an ad hoc query tool

Software: IRServer Version: 9.1.4

JReview Windows Server to iRServer (Configurable: 22302)

JReview Windows Server (Prod)

Software: Oracle OHS Version: 11.1.1.7.0

Web Server to Application Server (HTTP: 5575) [OHS – WebLogic]

System Administrator connects to Portes to copies datasets from Portes to CTR (via API)

Load Balancer

Developer

Citrix Servers

10a

10b

10a

10b Developer access to database(s) using TOAD (not sure we need or can get this access in Prod)

Shared directory

5 Application server to prod fileshare \\cdsnas

App Server Web Server

Portes

4a WODC Prod Server to ADC App on 389

WODC Prod Server to CHDC App on 55754b

4c WODC Prod Web Server to CHDC App on 5575

Application Server 01 Red Hat Linux 2 Processors

16 GB RAM

500 GB Disk Space/SAN

Software: Java (JDK) Version: 6

Software: Pentaho Version: 4.1.0

Software: JBPM Version: 5.x

Software: Ant Version: 1.8.4

Software: Oracle WebLogic Server 11gR1

Version: 10.3.6

Located at CHDC

4a 4b

4c

File details come from the government source that posted it. Updated .