Tours Open Days Implementation Plan 1.2x - Project

mountainromeInternet and Web Development

Oct 31, 2013 (3 years and 11 months ago)

96 views

University of
Edinburgh

_______________________________________________________________________________________________________



___________________________________________________________________________________


Information Ser
vices
-

Template Revised June
20
12














Stage: Build


Implementation Plan




Open Days and Tours Migration




STU233







Document Version:
1.2


Date:
12
/09/2013


B
uild: Implementation Plan


STU233


Open Day and Tours Migration

Version: 1.0

_______________________________________________________________________________________________________




___________________________________________________________________________________


Page
2

of
7


Contents


1

DOCUMENT MANAGEMENT

................................
................................
..........
3

1.1

Contributors

................................
................................
................................
.....

3

1.2

Version Control

................................
................................
................................

3

2

IMPLEMENTATION TASKS

................................
................................
.............
4

2.1

Infrastructure Components

................................
................................
............

4

2.2

Application Components

................................
................................
.................

4

2.
3

Application Setup

................................
................................
.............................

5

2.4

Integration Components
................................
.....

Error! Bookmark not defined.

2.5

Data Population
................................
...................

Error! Bookmark not defined.

2.6

Data Migration

................................
................................
................................
.

5

2.7

Implem
entation Validation

................................
................................
.............

6

3

ROLLOUT STEPS

................................
................................
..............................
7


B
uild: Implementation Plan


STU233


Open Day and Tours Migration

Version: 1.0

_______________________________________________________________________________________________________




___________________________________________________________________________________


Page
3

of
7

1

Document Management


1.1

Contributors


Please provide details of all contributors to this document.


Role

Unit

Name

Systems Analyst Designer
(
Owner
)

Development
Services

Ross Nicoll

Technical Architect (O
wner
)



Developer



Development Technology
Administrator




Production Management
Coordinator



Project Manager



Other document contributors




1.2

Version Control


Please document all changes made to this document since
initial distribution.


Date

Version

Author

Section

Amendment

28/03/13

1.0

RN

All

Creation

04/09/13

1.1

MM

All

Changes for correct server/db details.

12/09/13

1.2

RN

2.2

Changed deployment to be based on source
code archives




























B
uild: Implementation Plan


STU233


Open Day and Tours Migration

Version: 1.0

_______________________________________________________________________________________________________




___________________________________________________________________________________


Page
4

of
7

2

Implementation

T
asks



T
he steps necessary to implement the appli
cation or components

should be drawn together in this
document.


Please note any exceptions between implementation in the
TEST

and
LIVE

environments.


2.1

Infrastructure C
omponents


D
etails
of database and application server set
-
up requirements. Include a link to the Technical
Architecture Document

(TAD)

which is the primary source of information for the technical
infrastructure set
-
up and configuration.


The developer should liaise with the
technical architect to ensure that relevant details are updated in
the TAD and any application specific information is added. This includes confirmation of machine[s],
UNIX accounts, database users and roles, database links, database configuration require
m
ents,
application server set
-
up (
including technology, confirmation of settings e.g. timeout
)
, firewall
requirements and any specific software installation components.


This section should be completed by the developer in collaboration with the technical
architect.


Requires:




Web server (tested against Apache 2.2.x)



PHP 5.3 with LDAP and "mysqli" extensions installed.



MySQL 5.1 or better with InnoDB support.



Yii framework 1.1.13

2.2

Application C
omponents


Details

of application components


include database objects: tables, views, sequences, packages,
procedures, functions, triggers; Cold Fusion files; java classes; Business Objects universes/reports;
Oracle Forms/Reports; Unix scripts, etc.


This section should
be completed by the developer.


The tours & open day booking system is considered as two separate applications;
the public facing front
-
end and the administration tools. The two applications share a
common database, but are otherwise independent.


2.2.1

Front En
d

Copy
the source code

archive

from
K:
\
ISAPPS
\
dsg
\
Projects
\
STU233
\
public_srarec.tar.gz

to the
folder
/u01/software/smsproxy/public/htdocs/web
-
proxy

on the lamp
-
db
-
kb1{|t} server as
per section 4 of the TAD
. Unpack the archive

(“tar

xzf

public_srarec.tar.gz”) in that
directory
.


The archive contains all of its files under a single folder “srarec”, such that it should
end up at the path “
/u01/software/smsproxy/public/htdocs/web
-
proxy
/srarec

“.


The directories "assets" and "protected/runt
ime" must

be writeable by the web
server; permissions are set accordingly in the archive and should be therefore set
automatically on unpacking.

B
uild: Implementation Plan


STU233


Open Day and Tours Migration

Version: 1.0

_______________________________________________________________________________________________________




___________________________________________________________________________________


Page
5

of
7

2.2.2

Administration

Copy
the source code

archive

from
K:
\
ISAPPS
\
dsg
\
Projects
\
STU233
\
admin
_srarec.tar.gz

to the
folder
/

u01/software/smsproxy/admin/htdocs/admin

on the lamp
-
db
-
kb1{|t} server as per
section 4 of the TAD
. Unpack the archive (“tar

xzf admin_srarec.tar.gz”) in that
directory
.


The archive contains all of its files under a single folder “srarec”, such
that it should
end up at the path “
/u01/software/smsproxy/admin/htdocs/admin
/
srarec”.


The directories "assets" and "protected/runtime" must

be writeable by the web
server; permissions are
set accordingly

in the archive and should be therefore set
automatically on unpacking.

2.3

Application S
etup


Details of
authorisation and authentication

requirements

-

i
nclude
user creation,
access control
and
any functional set
-
up tasks that need to be carried out after im
plementation
of

the infrastructure and
application components.

Set
-
up of EASE test cases and/or integration with the portal should be
included.


This section will be completed by the Project Manager in conjunction with the business test co
-
ordinator.




The

provided configuration files should be correct for Test/Live and require no
modification.



Data migration & population is required and is covered in detail later in this
document.



Once the Implementation Plan has been completed, Polopoly configuration
will

be required (likel
y by SAR) to proxy the pages.


2.4

Data Migration


Specifically for upgrades, re
-
implementations, any data migration requirements and the steps to follow.


This section should be completed by the developer.


There is a
multi
-
stage process fo
r migrating data from the existing database
.
Database migration scripts are provided in


K:
\
ISAPPS
\
dsg
\
Projects
\
STU233
\
Code
\
db



1.

Take a database dump of the two source databases (edinfo
_bookings
and edinfo_visitingday
) from the server “praline”. Due to the

size of the
database dumps, compressing the resulting files before copying them
to other servers is recommended.

2.

Restore both database dumps to the single schema “
srarec
” on the
new server.

3.

Migrate the da
ta into its new table structure, by running the scr
ipt
“deploy.sql” on the “
srarec
” schema. Note that the migration process is
complex, and likely to take 1
-
2 minutes.

4.

Drop ta
bles which are no longer needed by running the script
“clean.sql”.

B
uild: Implementation Plan


STU233


Open Day and Tours Migration

Version: 1.0

_______________________________________________________________________________________________________




___________________________________________________________________________________


Page
6

of
7

5.

Create a cross
-
schema view of the p
ostgraduate prospectus databas
e
.
This requires

a user with access to both the “smspg” and “
srarec

schemas.

The script “deploy_as_root.sql” contains the SQL in
question.

6.

Create
initial user accounts as needed by running:



Test: "boo
t
strap_users_dev_test.sql"



Live: "boo
t
strap_users_live.sql"

2.5

Implementation V
alidation


This is used to document that implementation has been successful and that the basic steps of being able
to authenticate
to the

system is possible and whatever authorisation level assigned to the initial user

base is in place.

F
or deployments involving several servers (like SOA and MyEd), detail the checks to
be performed to validate the deployment to all servers



This section should be completed by the support analyst.


B
uild: Implementation Plan


STU233


Open Day and Tours Migration

Version: 1.0

_______________________________________________________________________________________________________




___________________________________________________________________________________


Page
7

of
7

3

Rollout S
teps


Please indicate the
order in wh
ich tasks need to be carried out. Refer to sub
-
sections in section 2 where
necessary.


Please note any exceptions between implementation in the test and production environments.


3.1

Differences Between Live & Dev/Test


Please note that there are di
fferent SQL scripts for creating users on dev/test, and on
live. The dev/test version provides user accounts for developers for testing, which
live does not:



Dev/test: db/bootstrap_users_dev_test.sql



Live: db/bootstrap_users_live.sql


3.2

Rollout Steps


1.

Perfor
m schema checks (standard task for all TEST to LIVE implementations)

2.

Copy and unpack the archives

from
K:
\
ISAPPS
\
dsg
\
Projects
\
STU233
\

to the
display and admin folders (2)

3.

Perform the migration of data from current database (5)

4.

Run the schema update and use
r population scripts (5)

5.

Test applications are available (6)

6.

Project Manager should arrange for
SAR

to set
-
up Polopoly proxy pages.