SS
RCKMS Shared Service
Last updated
RCKMS Shared Service
Last updated
The RCKMS Shared Service (SS) serves as the primary entrypoint for the reportability environment, utilizing jurisdiction records stored in the Document Database to appropriately invoke other services to generate an RCKMS output payload.
Refer to for further details.
Workload performs the following interactions:
In the reportability environment, the Shared Service accepts incoming RCKMS payloads from Mirth channels, and serves as the transaction broker for the main reportability event loop, communicating with the Document Database, VCS, DSS, and ultimately responding back to Mirth with an RCKMS output payload.
In the authoring environment, the Shared Service accepts test submissions from CAT, the primary user interface for the RCKMS platform. This operation is primarily performed by HLN business analysts to validate authoring changes, and to certify new releases.
Workload should be deployed to both the and environments.
Name
shared-service
Restart Policy
Always
Termination Grace Period (seconds)
60
Tolerations (optional for AIMS environments)
N/A
Provision workload as a Kubernetes Deployment resource, with RollingUpdate strategy and the following attributes for nominal operation state:
Replicas
24
Minimum Ready Seconds
15
Maximum Surge
12
Maximum Unavailable
0
Provision workload as a Kubernetes Deployment resource, with RollingUpdate strategy and the following attributes for nominal operation state:
Replicas
1
Minimum Ready Seconds
15
Maximum Surge
1
Maximum Unavailable
0
A Kubernetes Service Account named shared-service should be associated with this workload, for bindings specified in .