Implementation Tasks

Qliksense

1. Infrastructure Components

Servers built for DEV, TEST & LIVE by ITI, Alister Webb & Simon Minifie

ADFS deploy to LIVE

ADFS already configured in DEV and TEST Qliksense environments

ADFS implementation steps:

1] QlikIT - Simon Minifie - supply Qliksense proxy metadata file

( can only be provided as a file )

2] ITI - Neil Cooper - Create new ADFS service provider / configure the new ADFS service for Qliksense

3] IS Service Management - Andrew McFarlane - Enable users to grant access to Qliksense

Steps 1] and 2] can be done in advance - the new Qliksense service is not available until step 3] is done.

It is proposed that Qliksense will only be rolled out to a small number of  Pilot users in GASP - as first step of LIVE rollout

Data sources:

Qliksense - access to local file shares . All the file shares should be available via the login to the remote Terminal services server - same user login

Qliksense access to EDW

1. Application Components

Determined by IS Service Management via permissions set in AD groups and within QMC ( Qlik Management Console) 

1. Application Setup

Determined by IS Service Management via permissions set in AD groups and within QMC ( Qlik Management Console) 

1. Integration Components

2. Data Population

3. Data Migration

4. Implementation Validation

Qlikview

1. Infrastructure Components

Windows 2016

Qlikview server

Qlikview remote Terminal services VDI service - Qlik-dash-remote - already installed by QlikIT ( Simon Minifie) - now needs testing

Qlikview - access to local file shares . All the file shares should be available via the login to the remote Terminal services server - same user login

Qlikview access to EDW

1. Application Components

2. Application Setup

3. Integration Components

4. Data Population

5. Data Migration

6. Implementation Validation