TMF Service
Purpose
mvp3-tmf-service is the backend service for TMF-related workflows.
Local runtime facts
- default local port:
3004 - swagger docs:
/tmf/docs - metrics endpoint:
/tmf/metrics - env template:
.env.example
Owned modules
redissockettmf
Dependencies
- MariaDB
- Redis
- RabbitMQ credentials are part of the template
CAMELIA_SOCKET_BASE_URI- socket and TMF-related integrations
- shared storage volume appears in
docker-compose.yml
Required config groups
PORTDB_*TOKEN_EXPIRED_PER_SECONDS,JWT_ISSUER,JWT_ALGORITHMREDIS_*RABBITMQ_*CAMELIA_SOCKET_BASE_URI
Upstream and downstream
- upstream callers: portal or mobile flows that need TMF-related context or actions
- downstream systems: MariaDB, Redis, sockets, TMF domain modules
- queue publishing confirmed from code:
- sends TMF update patterns to
intt_ctt_queue
- sends TMF update patterns to
- team clarification:
- this service is part of the Antrix system of record
- it exposes endpoints for external sources
- cross-service integration should happen through endpoints, not direct table writes
Confirmed module mapping
- technical host module:
TmfModule - routing module registers the service directly rather than mounting a nested path like
/ngossor/nocgrid
Local commands
Install:
git submodule update --init --recursive
cd share-entity
git checkout development
cd ..
pnpm install
Run locally:
pnpm run start:dev
Build and run production mode:
pnpm run build
pnpm run start:prod
Test:
pnpm run test
pnpm run test:e2e
pnpm run test:cov
Local testing
- unit tests:
pnpm run test - e2e tests:
pnpm run test:e2e - coverage:
pnpm run test:cov