Page Comparison

...

• Ifix client requests pushed to IFIX

• Auth token is fetched from keycloak and cached. Token will be re fetched 5 minutes before expiry

• Every push to Ifix is recoded with http status

  • status series 200 series considered success

  • status 400 are marked client error and reported back to client

  • status 500 resubmitted by scheduler

Deployment Details

1. update the keycloak credentials client-id and secrets in environment file

2. Map the coa in HeadCodeToCoaMapping.yml

3. Map project in ProjectMapping.yml

4. Deploy the latest version of ifix-reference-adapter

...

1. Update Key cloak credentials in dev.yaml,qa.yaml,prod.yaml according to environment update the keycloak credentials “client-id” and “secrets” in environment file https://github.com/egovernments/iFix-DevOps/blob/27c67ad236f06ad2e6a139c4d59111db184f8705/deploy-as-code/helm/environments/mgramseva-qa.yaml#L224 ,https://github.com/egovernments/iFix-DevOps/blob/27c67ad236f06ad2e6a139c4d59111db184f8705/deploy-as-code/helm/environments/mgramseva-qa-secrets.yaml#L65

2. Map clientcode, ifixcoacode, ifixid in ifix_adapter_coa_map table

3. If client “project code” and IFIX project code are different then map clientprojectcode, ifixprojectid in ifix_adapter_project_map table

Integration

Integration Scope

...