Skip to content

Runtime Topology & Configuration Capture

Overview

  • Services in scope: Spring Boot cis-api (Jetty on ${SERVER_PORT:8089}) and the Angular frontend bundles (cis-external, cis-internal, cis-workflow-studio) to be published behind nginx.
  • Execution model: cis-api runs as a single JVM with ShedLock, Redis-backed caching, SMTP, LDAP, and multiple HTTP(S)/FTP integrations. Frontend artifacts are static Angular builds served via nginx with SPA rewrites.

cis-api Runtime Inputs

  • Process basics: Bootable jar launched with JAVA_OPTS="-XX:+UnlockExperimentalVMOptions -XX:+UseCGroupMemoryLimitForHeap -XX:+UseG1GC" (see Dockerfile). HTTP port supplied via SERVER_PORT.
  • Core configuration: .env.example enumerates datasource, Redis, SMTP, LDAP, workflow, stamping, FTP, and DigitalOcean Spaces values. Spring profiles map to application-*.yaml (dev, uat, dalrrd) with Oracle + Redis defaults and LDAP credentials.
  • Secrets location: Local keystores (jwt.jks, /cis-api/src/main/resources/keystore/) and LDAP bind details already live under src/main/resources; production secrets must be injected at runtime (env vars or mounted files) rather than committed.
  • File system touch points:
  • /data/uploads ↔ APP_STORAGE_LOCATION
  • /app/logs for Logback appenders
  • Optional keystores/public keys bound into /app/config (documented in docs/docker/cis-api.md)
  • External dependencies: Oracle DB, Redis (7.x), OpenLDAP / Active Directory, RustFS S3 Object Storage (:9000), SMTP gateway (Mailpit in dev), FTP server, workflow/stamping HTTP APIs. ShedLock currently uses Redis via net.javacrumbs.shedlock-provider-redis-spring.

Angular + nginx Notes

  • Source located in CIS-WEB-ANGULAR/CIS/cis-web/ with Angular CLI projects per sub-app (cis-external, cis-internal, cis-workflow-studio).
  • Legacy nginx added compression, caching headers, and SPA fallback; exact rules pending infra export. Build artifacts land in dist/<app> after npm ci && npm run build --prod.

Outstanding Information Needed

  1. nginx configuration: need the current /etc/nginx/conf.d/*.conf or equivalent to port existing headers, caching, and proxy rules.
  2. Production environment variables: confirm authoritative values for Oracle/Redis/LDAP, plus non-standard JVM flags (heap sizing, GC logging) if different from defaults.
  3. Secrets management process: clarify whether Docker secrets, Vault, or Kubernetes secrets will supply sensitive values.
  4. Inbound networking: document load balancer ports, TLS termination points, and any mutual TLS/whitelisting requirements for the cis-api container.