IFIX Adapter Services v1.0

Overview

Ifix-Adapter is a system which works as mediator between ifix and its clients. This system will receive requests from client system and convert the data in the Ifix required format This document contains the details about how to setup ifix-adapter service and describes the functionalities it provides

Pre-requisites.

Before you proceed with the configuration, make sure the following pre-requisites are met -

• Java 8

• Kafka server is up and running

• PSQL server is running

• Redis

• Following services should be up and running:

  • Client Service Like mgramseva-ifix-adapter

  • Target service IFIX- fiscal-event-service

  • Target Service IFIX-keycloak

Key Functionalities

• 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. Deploy the latest version of ifix-reference-adapter

Configuration Details

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

Integration Benefits

Interaction Diagram

Reference Docs

Doc Links

API List