update backend-integration.md file

After having restructured the client & server stubs and developing minimal server-side & client-side logic for the new feature using the [development guide](./development-guide.md), move the code files into AdvantEDGE repository or its fork using the following guidelines:

- [Server side](./development-guide.md#server-side) code contained in a separate folder named `meep-<mec-identifier>` will go under `AdvantEDGE/go-apps/` directory

- [Server side (For multiple APIs)](./development-guide.md#server-side-for-multiple-apis) code contained in a separate folder named `meep-<mec-identifier>` will go under `AdvantEDGE/go-apps/` directory

- [Client side](./development-guide.md#client-side) code contained in a folder named `meep-<mec-identifier>-client` will be placed under `AdvantEDGE/go-packages/` directory

- [Testing](./development-guide.md#unit-tests-for-the-new-micro-service) code... (**TODO** _Info about test files to be added later._)

### Changes in AdvantEDGE `.meepctl-repocfg.yaml`

The changes that need to be made to `.meepctl-repocfg.yaml` file are:

- Add the new service in `repo.sandbox.go-apps` section

- Add the new service in `repo.sandbox.go-apps` section. In case if a service contains multiple APIs, then rest of the lines will be same. Just add the corresponding APIs information under _api_ tag, as mentioned below:

  ```

  api:

  - name: 'AdvantEDGE MEC <api_name_1>'

    file: go-apps/meep-<mec-identifier>/api/<api_tag_1>/swagger.yaml 

  - name: 'AdvantEDGE MEC <api_name_2>'

    file: go-apps/meep-<mec-identifier>/api/<api_tag_2>/swagger.yaml

  ...

  ... 

  ```

- To allow the `meep-virt-engine` service to deploy the new service's pod, the service should be added to the following sections:

  - `repo.sandbox.go-apps.meep-virt-engine.docker-data`

  - `repo.sandbox.go-apps.meep-virt-engine.sandbox-pods`

Additionally for making the Swagger UI available in the Sandbox frontend for the new service, these steps need to be taken:

1. Copy the Swagger or OpenAPI specifications of the new MEC Service from backend (available under `mec-sandbox/go-apps/meep-<mec-identifier>/api/swagger.yaml`) to `mec-sandbox/config/api/` folder and rename the file from `swagger.yaml` to `<mec-identifier>-api.yaml`. Additionally

1. Copy the Swagger or OpenAPI specifications of the new MEC Service from backend (available under `mec-sandbox/go-apps/meep-<mec-identifier>/api/swagger.yaml`) to `mec-sandbox/config/api/` folder and rename the file from `swagger.yaml` to `<mec-identifier>-api.yaml`. 

* **Note:** In case multiple APIs, copy each Swagger or OpenAPI specifications of the new MEC Service from backend (available under `mec-sandbox/go-apps/meep-<mec-identifier>/api/<api_tag_i>/swagger.yaml`) to `mec-sandbox/config/api/<api_tag_i>/` subfolders.

3. After performing the above, do the following:

    - Customize the YAML to hide unnecessary endpoints in the UI

    - Add necessary license description in the `info` section

2. Add this location of OAS yaml in the `repo.sandbox.go-apps.<mec-identifier>.user-api` section of `.meepctl-repocfg.yaml` file

4. Add this location of OAS yaml in the `repo.sandbox.go-apps.<mec-identifier>.user-api` section of `.meepctl-repocfg.yaml` file

In addition to `.meepctl-repocfg.yaml` file, the following files will need to be updated when creating a new micro-service:

- `mec-sandbox/config/long-term-storage-repocfg.yaml`

All the Helm charts for multiple services are available under the `AdvantEDGE/charts` folder. Once a new service is added, its Helm chart needs to be added in this folder under the name `meep-<mec-identifier>`.

The template for the Helm chart for the new service can be obtained from any other micro-service like `meep-rnis`, `meep-wais` etc. The service name in each of the files for the template will need to be changed to reflect the name of the new service.

The template for the Helm chart for the new service can be obtained from any other micro-service like `meep-rnis`, `meep-wais` etc. The service name in each of the files for the template will need to be changed to reflect the name of the new service. In case of multiple APIs scenario, `meep-tm` charts can be consulted.

## _meep-applications_ Configuration