WFA App is an web application that is deployed in ‘Tomcat’ docker container.
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’, ‘cws_dws_pwa_name’, and ‘cws_dws_pwa_pwd’.
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.
...
On this page:
WFA is a web application deployed on Tomcat. It integrates with services such as 'Dhis2 login', 'voucherCodeService', and 'message scheduling/sending', all of which are orchestrated through the DWS service.
WFA Deployment
The WFA app file will be provided as a zip file. Initial deployment or update deployment can be done by unpacking this zip file in tomcat webapps folder.
Use FTP to transfer the WFA zip file named ‘wfa.zip’.
(In this example, the FPT file transfer destination is ‘/home/ktt’.)Connect to the server and execute the below command.
Code Block sudo tar --overwrite -xvf /home/ktt/wfa.zip -C /home/ktt/zw-vmmc-docker/tomcat/webapps
WFA DWS Configurations
DWS operates by endpoint configurations. By setting up a proper operation configuration for a given endpoint, DWS performs a proper operation.
Setup