Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

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. 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

Configuration Details

  1. Update Key cloak credentials in dev.yaml,qa.yaml,prod.yaml according to environment

Integration

Integration Scope

Integration Benefits

Interaction Diagram

Reference Docs

API List

  • No labels