a. Production architecture
Dynasys application is composed of two separate PROD environments, one by company.
SCo : 1 backend server ACEW1PDSCPAPPS5 + 1 frontend server ACEW1PDSCPTSES5
- DSCP instances : DP1, DP2, DP3, DiP1, DiP3, DSCP2
- 2 DataHub databases : one for DSCP2, one for other instances
- Services
- A Task scheduler to execute batches
- A third DataHub named ITF_SHARED to collect data from all ECo/SCo DH databases
ECo : 1 backend server ACEW1PDSCPAPPE5 + 1 frontend server ACEW1PDSCPTSEE5
- DSCP instances : DP4, DP5, DiP4, DiP, DSCP1
- 2 DataHub databases : one for DSCP1, one for other instances
- Services
- A Task scheduler to execute batches
b. Non-Production architecture
Non-Prod Dynasys architecture is made of two environments : DEV and TEST.
Test SCo : 1 backend server ACEW1TDSCPAPPS3 + 1 frontend server ACEW1TDSCPTSES3
- DSCP instances : DP1, DP2, DP3, DiP1, DiP3, DSCP2
- 2 DataHub databases : one for DSCP2, one for other instances
- Services
- A Task scheduler to execute batches
- A third DataHub named ITF_SHARED to collect data from all ECo/SCo DH databases
Test ECo : 1 backend server ACEW1TDSCPAPPE3 + 1 frontend server ACEW1TDSCPTSEE3
- DSCP instances : DP4, DP5, DiP4, DiP, DSCP1
- 2 DataHub databases : one for DSCP1, one for other instances
- Services
- A Task scheduler to execute batches
Dev SCo : 1 backend server ACEW1DDSCPAPPS1 + 1 frontend server ACEW1DDSCPTSES1
- DSCP instances : DP1, DP2, DP3, DiP1, DiP3, DSCP2
- 2 DataHub databases : one for DSCP2, one for other instances
- Services
- A Task scheduler to execute batches
- A third DataHub named ITF_SHARED to collect data from all ECo/SCo DH databases
Dev ECo : 1 backend server ACEW1DDSCPAPPE1 + 1 frontend server ACEW1DDSCPTSEE1
- DSCP instances : DP4, DP5, DiP4, DiP, DSCP1
- 2 DataHub databases : one for DSCP1, one for other instances
- Services
- A Task scheduler to execute batches
A jump server (ACEW1PAPPJRDP01) allows administrators to log on all Dev/Test/Prod servers. Direct connection to servers is not possible.