a. Non-Production architecture
Dynasys application is composed of two non-prod environments : DEV and TEST.
The DEV is hosted on two backend servers :
ACEW1DDSCP01
- DP1, DP2, DP3 and DSCP2 instances
- 2 DataHub databases : main DH, DSCP2 DH
- Services
- A Task scheduler to execute batches
ACEW1DDSCP02
- DiP1, DiP2, DiP3 and DSCP1 instances
- 1 DataHub database : DSCP1 DH
- Services
- A Task scheduler to execute batches
ACEW1DTSCPTSE01 is the frontend server to manage access to each application.
The Test environment has the same structure with two backend servers (ACEW1TDSCP11 and ACEW1TDSCP12) and one frontend server (ACEW1TDSCPTSE11).
A jump server (ACEW1PAPPJRDP01) allows administrators to log on to all servers, including production ones.
b. Production architecture
Dynasys PROD is hosted on two backend servers :
ACEW1PDSCP21
- DP1, DP2, DP3 and DSCP2 instances
- 2 DataHub databases : main DH, DSCP2 DH
- Services
- A Task scheduler to execute batches
ACEW1PDSCP22
- DiP1, DiP2, DiP3 and DSCP1 instances
- 1 DataHub database : DSCP1 DH
- Services
- A Task scheduler to execute batches
ACEW1PTSCPTSE21 is the frontend server to manage access to each application.
c. Groups & Admin members
d. Batch DynaSys alert DP / Batch DynaSys alert DiP / Batch DynaSys alert DSCP
To register a ticket in Service One to do Google Groups Createion / Deletion / Modification.
Now we have 3 groups by applicaion, People within the groups will received the email regarding batch Dynasys alert by application.
batch.dynasys.alert@solvay.com
batch.dynasys.alert.DiP@solvay.com
batch.dynasys.alert.DSCP@solvay.com (to be created)