...
Info |
---|
May be able to replace information with this document when it is completed: https://docs.google.com/a/kuali.org/document/d/1pbtM4y5aC-4rB_mY44FeArwmTWVu7fhP47FbpF6JPWo/edit#heading=h.a7io9c9blj32 |
System Architecture Diagram
System Architecture Diagram | Latest Dev Branch Deployment |
---|---|
|
...
), |
...
|
...
includes |
...
the |
...
three |
...
environments |
...
for |
...
DEV, |
...
TST |
...
and |
...
DEMO. |
...
Each environment includes at the least:
1. OLE/FS
...
server
...
2.
...
DocStore
...
Server
...
3.
...
And
...
backend
...
database
...
For
...
DEV
...
and
...
TST
...
environment,
...
there
...
are
...
two
...
applications
...
deployed
...
on
...
OLE/FS
...
server,
...
one
...
is
...
OLE/FS
...
on
...
Rice
...
1.x
...
framework,
...
the
...
another
...
is
...
OLE
...
on
...
Rice
...
2.0
...
framework.
...
For
...
DEMO
...
environment,
...
there
...
is
...
only
...
OLE/
...
FS on
...
Rice
...
1.x
...
framework
...
deployed
...
on
...
the
...
server.
...
DEMO
...
release
...
version
...
is
...
OLE
...
0.6.
...
The
...
DocStore
...
on
...
each
...
environment uses Apache Jackrabbit 2.0
...
for
...
content
...
storage
...
and
...
...
...
...
for
...
indexing
...
and
...
searching.
...
On
...
the
...
cloud
...
environment,
...
we
...
configure
...
the
...
Jackrabbit
...
with
...
ORACLE
...
Database.
...
Server Configuration:
Environment | Server Name | Amazon Instance Type | Description |
DEV Env | Ole-dev | C1.medium | OLE/FS DEV site |
ole-docstore-dev |
...
M1.large |
...
DocStore |
...
DEV |
...
site |
...
TST |
...
Env |
...
Ole-tst |
...
M1.medium |
...
OLE/FS |
...
TST |
...
site |
...
ole-docstore-tst |
...
M1.large |
...
DocStore |
...
TST |
...
site |
...
DEMO |
...
Env |
...
Ole-demo |
...
M1.large |
...
OLE/FS |
...
Demo |
...
site |
...
Ole-docstore-demo |
...
M1.large |
...
DocStore |
...
demo |
...
site |
Reference:
Small Instance – default*
1.7 GB memory
1 EC2 Compute Unit (1 virtual core with 1 EC2 compute Unit)
160 GB instance storage 32-bit or 64-bit platform
I/O Performance: Moderate
API name: m1.small
Medium Instance
3.75 GB memory
2 EC2 Compute Units (1 virtual core with 2 EC2 compute Units)
410 GB instance storage 32-bit or 64-bit platform
I/O Performance: Moderate
API name: m1.medium
Large Instance
7.5 GB memory
4 EC2 Compute Unit (2 virtual cores with 2 EC2 Compute Units each)
850 GB instance storage 64-bit platform
I/O Performance: High
API name: m1.large
ORACLE Database instance/schemas
we have three ORACLE database instances setup on the cloud:
- OLE-ORACLE-2, 7.5GB RAM, 160GB storage, including schemas as following:
- OLEDBA (we keep our OLE schema here)
- OLEDEV (schema comes from OLEDBA, setup for OLE DEV site)
- OLETST (schema comes from OLEDBA, setup for OLE TST site)
- OLEDM (playground for data modeler, do we need now???)
- OLELOCAL (the playground for data modeler or developer to play with the schema, refreshed from OLEDBA every morning at 4am)
- OLECI (playground for unit test)
- OLERICE_DEV (schema setup for OLE/Rice 2 for DEV site)
- OLERICE_TST (schema setup for OLE/Rice 2 for TST site)
- DocStore/JCR tables for DEV
- DocStore/JCR tables for TST
- OLE-DEMO-ORACLE-2,
...
- 7.5GB
...
- RAM,
...
- 80GB
...
- storage,
...
- only
...
- has
...
- one
...
- schema:
...
- OLEDEMO
- DocStore/JCR
...
- tables
...
- for
...
- DEMO
...
- OLE-DEV-2
...
- Not
...
- sure
...
- what
...
- kinds
...
- of
...
- schema
...
- on
...
- this,
...
- should
...
- be
...
- just
...
- for
...
- dev
...
- site
Backup for DEMO, we have two jobs on the cloud to take snapshots for the databases and DocStore file system. The snapshots for OLE-DEMO-ORACLE-2
...
instance
...
keep
...
on
...
RDS
...
(in
...
the
...
Amazon
...
cloud).
...
But
...
it
...
is
...
only
...
run
...
when
...
loading
...
new
...
data
...
as
...
the
...
baseline.
...
Amazon
...
backup
...
the
...
data
...
for
...
us
...
automatically.
...
The
...
backup
...
data
...
only
...
can
...
be
...
accessed
...
through
...
aws
...
console.
...
Access Databases: you should have Aqua Data Studio, SQL Plus/Developer or other database client to access the databases on the cloud. The configuration of each schema for the client setup is as following:
- OLEDEV
- UserName – oledev
- Hostname – ole-oracle.ole.kuali.org
...
- Port – 1521
- SID – ole
- OLETST
- UserName – oletst
- Hostname – ole-oracle.ole.kuali.org
...
- Port – 1521
- SID – ole
- OLEDEMO
- UserName – olefs
- Hostname – demo-oracle.ole.kuali.org
...
- Port – 1521
- SID – oledemo
- OLERICE_DEV
- UserName - olerice_dev
- Hostname – ole-oracle.ole.kuai.org
...
- Port
...
- -
...
- 1521
...
- SID
...
- -
...
- ole
...
- OLERICE_TST
...
- UserName - olerice_tst
...
- Hostname – ole-oracle.ole.kuai.org
...
- Port
...
- -
...
- 1521
...
- SID – ole
- OLEDBA
- UserName - oledba
- Hostname – ole-oracle.ole.kuai.org
...
- Port
...
- -
...
- 1521
...
- SID
...
- -
...
- ole
...
- OLELOCAL
- UserName - olelocal
- Hostname – ole-oracle.ole.kuai.org
...
- Port
...
- -
...
- 1521
...
- SID
...
- -
...
- ole
File/folder
...
structure
...
for
...
miscellaneous
...
files
...
There
...
is
...
one
...
upload
...
folder
...
for
...
each
...
DocStore
...
server.
...
You have to secure ftp to the server as following:
- FTP sites
- DEV – sftp://upload@docstore.dev.ole.kuali.org
...
- TST – sftp://upload@docstore.tst.ole.kuali.org
...
- DEMO – sftp://demo@docstore.demo.ole.kuali.org
...
- The
...
- files
...
- are
...
- using
...
- for
...
- the
...
- following
...
- purpose:
...
- files
...
- to
...
- be
...
- processed
...
- by Vendors
- Support files for information contained/displayed
...
- in
...
- Load
...
- Reports
...
- XML
...
- file
...
- for
...
- YBP
...
- Loading
...
- sample
...
- data
...
- for
...
- instance,
...
- bib…
- Folder locates at /opt/docstore/upload,
...
- for
...
- example
Steps for refresh DEMO environment:
- stop tomcat instances for OLE DEMO and OLE DEMO DocStore
- Reference for how to stop and start tomcat (jobs on ci):
- Server Stop
- Server Start
- Each job will need to be ran twice. Build the job and you will be given an option. For one run select demo and the other run docstore-demo from the pull down menu.
- Run Stop before the refresh jobs and Start at the end of the refresh jobs
- Reference for how to stop and start tomcat (jobs on ci):
- Refresh Demo DocStore Filesystem , this will refresh the filsystem portion on docstore demo
- Refresh Demo Oracle, this will refresh the oracle for both the docstore and OLE.
- Restart tomcat instances for OLE DEMO and OLE DEMO DocStore