> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/public-finance/v2.3/platform/configuration/promotion-docs/mgramseva-ifix-adapter.md).

# mGramSeva iFIX Adapter

The mGramSeva iFIX Adapter receives multiple event requests from the mGramSeva service and helps in attributes conversion to map with fix-fiscal-event-service request data.

## Setup Steps

1. Environment variable

   Configure "fiscal-event-service", "adapter-master-data-service" and "ifix-department-entity-service" in egov-service-host in respective environment yaml file ([<img src="https://github.com/fluidicon.png" alt="" data-size="line">iFix-DevOps/mgramseva-qa.yaml at mgramseva · misdwss/iFix-DevOps](https://github.com/misdwss/iFix-DevOps/blob/mgramseva/deploy-as-code/helm/environments/mgramseva-qa.yaml) ).
2. Redis data clean up

   Execute the below commands on redis-cli before doing any activity on the mgramseva iFix adapter while performing the deployment first time.

   * Connecting Redis Client:&#x20;

     `kubectl exec -it <redis-pod> -n mgramseva -- /bin/bash`

     `redis-cli`

     *e.g.*

     `kubectl exec -it redis-647449f6b9-gg4gw -n mgramseva -- /bin/bash`

     `redis-cli`

     `keys *  (check all keys)`
   * Redis cleanup command

     `del <key>`

     *e.g.*

     `del "10101" "10102" "10201" "20101" "20201" "20301" "20401"`

     `keys * (check all keys)`

   ***Note:** Make sure all client codes, which have been mentioned in the "ifix\_adapter\_coa\_map" table, are listed in the redis "DEL" command list and recheck those are removed using "keys \*" command.*&#x20;

## Steps To Use mGramSeva iFIX Adapter Service

Use the postman tool to verify mGramSeva iFix adapter API end. It is open-end and therefore does not require any access token.

## &#x20;**Technical Doc**

[MGramSeva IFIX Adapter Services v2.0](/public-finance/v2.3/exemplar/ifix-adapter/adapter-service-documents/mgramseva-ifix-adapter-service.md)

> [![Creative Commons License](https://i.creativecommons.org/l/by/4.0/80x15.png)*​*](http://creativecommons.org/licenses/by/4.0/)*All content on this page by* [*eGov Foundation*](https://egov.org.in/) *is licensed under a* [*Creative Commons Attribution 4.0 International License*](http://creativecommons.org/licenses/by/4.0/)*.*

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.digit.org/public-finance/v2.3/platform/configuration/promotion-docs/mgramseva-ifix-adapter.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.