DIAGRAM03_JReview-TargetStateDiagram.pdf

PDF 129 KB Posted

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

About this file

DIAGRAM 03

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

Client Workstation

Web Zone

Application Zone

C lie nt

W or ks ta tio n

W eb

Z on e A pp lic at io n Zo ne

Data Zone

D at a Zo ne

CDER [0116]: Jreview Migration Group: CDER-A Bundle:

CDER jReview

This app serves sponsor’s data as spreadsheet like views, accomplishing subsets/sorts/merges in the background as the user directs. Future service levels include running SAS analysis jobs on the server, and in the present these views can be exported as data tables for SAS analysis.

New hardware was purchased to support the SAS engine as follows:

- Production: One M4000

- Training: One M3000

- Test: One M3000

The Sun cluster is currently in place to provide for high availability. There is a shared mount point to both servers in the cluster so the application can failover if one node should fail. However, clustering is not required moving forward into the new environment.

The Cluster currently has 2.2 TB of storage.

External connectivity via VPN received for vendor support.

jReview uptime requirements are from Monday to Friday, 6am to 6pm.

Acceptable downtime for the migration effort is once a weekend per month.

Description

Communications & Dependencies

Enterprise Services

Key Contacts

External Dependencies

Receives from

Sends to

Security Bucket

Version: 2 Last Modified: July 21, 2015

Standalone Components

App Instance: jReview Server for CDER/PORTES/

JANUS

64-bit; 2GB RAM

Software: Microsoft IIS

All servers are deployed to WODC, except for the File Share containing EDR data and the Portes Data. Fileshare containing EDR data is in CHDC.

Modification Tasks

Additional Upgrades Needed To Meet Standards

M od ifi ca tio n

Ta sk s D ur in g M ig ra tio n

Modification Tasks

Current State Diagram

End User Workstation

1 End user workstation to Web Tier Load Balancer(TCP/80 – HTTP)

Web Tier Load Balancer to Citrix Web Interface (TCP/443 – HTTPS)2

CHDC Internal

Fileshare containing EDR data

Software: SAS with SAS Share Version: 9.2

App Instance: SAS/ IRServer

Solaris 10

9 Standalone Components

Load Balancer

CBER Jreview Application Server to SAS Server (TCP/22300)

Citrix Web Interface to Citrix Core Server (TCP/443 – HTTPS)

Citrix Core Server to XenApp Application Server (TCP/443 - HTTPS)

SAS (UNIX) initiates connection to Windows fileshare containing EDR data (TCP/135-139,445 – CIFS/SMB) for copying data

Jreview Application Server to SAS Server (TCP/22300)

SAS Standard API calls for IRServer to reach Portes Data (TCP/22300) Jreview Application Server to Linux Server (Oracle Client for access to Janus database) (TCP/22300)

11 XenApp Server to SAS Server for application support (TCP/22 – SSH)

F5 BigIP Load Balancer to IIS (HTTP/80)

F5 BigIP Load Balancer to IIS (HTTP/80)

3 F5 Load Balancer to F5 Load Balancer (TCP/80 – HTTP)

Software: Microsoft IIS Version: 6

Citrix Web Interface (Mngt)

Software: Citrix

Software: Microsoft IIS

Citrix Core Server and backup zone data collector (Mngt)

Software: Citrix XenApp

Citrix Application Server (Mngt)

Software: Java

Software: Jreview Admin Version: 9.0

End user workstation to Web Tier Load Balancer(TCP/443 – HTTPS)

App Instance: jReview Server for CBER

Standalone Components

Software: Microsoft IIS

64-bit; 2GB RAM Windows Server 2008 (VM)

Portes Data (Remote to White Oak)

Unknown Linux ServerM

App Instance: Oracle Client/IRServer

Janus Data (Oracle Database)

Load Balancer

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