...
Deployment Location:
- Host computer /user/webapps/wfa , which is virtual mount of docker container’s tomcat/webapps. When we deploy updates of WFA App, we need to unzip the app file into this location.DWS Config Settings:
Target login Dhis2 server:
In ‘ws_v2@CMN@replica', we need to properly set ‘dhis2LoginUrl’ & ‘dhis2CountryLevel’.
For ‘dhis2LoginUrl’ set to ‘dev.psh.org.zw’, the ‘dhis2CountryLevel’ is set to '1'.
However, this might/might not be same for the production Dhis2 server.In DWS, reaching other tomcat hosted services, use http://localhost:8080
In DWS, reaching node.js services, use http://node_container:3000
Dhis2 Server Setup
‘OrgUnit’ needs to be populated for login user code & pin.
‘OrgUnitGroup’ needs to be populated for login user roles.
Services WFA App Uses:
Dynamic Web Service (DWS):
- Dynamic Web Service that is a service layer middle ware. Most of the requests go through the DWS for WFA App.
- Located in tomcat webapps folder as ‘dws’. It is an java service application.MongoDB Setup:
- Main collections: ‘client’, ‘log’, and ‘vouchers’. Indexes need to be populated.
- The data needs to be extracted from current production database for Zim data only. And need to be restored.Other Services WFA App Uses:
VoucherCode Service (vcGen):
- VoucherCode Service handles generating voucher codes, store them in queue, and provides these voucher codes from queue to users in WFA App.
- This is a node.js service with storing data (voucherCode Queue) in mongoDb. The node.js service (vcGen) is running in nodeJs docker container.
- WFA App goes through DWS to access services of VoucherCode.
MongoDB Service:
- Located in mongoDB docker container.
- Main collections: ‘client’, ‘log’, and ‘vouchers’. Indexes need to be populated.