HR Integration App¶
This page gives an overview of the HR Integration App, describing its current status, where and how it's developed and deployed, and who is responsible for maintaining it.
Danger
The HR Integration App uses technology, coding standards, and deployment methodologies which are not endorsed by the TDA and not standard practice for the DevOps team.
Service Description¶
The HR Integration App provides functionality to integrate and expose data from the CHRIS datastore (the central University HR system), as well as a management interface to review how data has been synchronized and notify on data transfer errors.
Service Status¶
The HR Integration App is currently live.
Note
Work is currently (Q2-2024) being completed to migrate the existing deployment to GCP.
Contact¶
Technical queries and support should be directed to hr-systems-development@uis.cam.ac.uk and will be picked up by a member of the team working on the service. To ensure that you receive a response, always direct requests to hr-systems-development@uis.cam.ac.uk rather than reaching out to team members directly.
Issues discovered in the service or new feature requests should be reported to servicedesk@uis.cam.ac.uk
Issues related to the Oracle Database which serves as the primary data store for the application should be raised with the DBA Team.
Environments¶
The HR Integration App is currently deployed to the following environments:
| Name | URL |
|---|---|
| Production | https://hrsystems.admin.cam.ac.uk/integration-ui/ |
| Staging | https://staging.hrsystems.admin.cam.ac.uk/integration-ui/ |
| Development | https://dev.hrsystems.admin.cam.ac.uk/integration-ui/ |
Source Code¶
The source code for the HR Integration App is spread over the following repositories:
| Repository | Description |
|---|---|
| Application Server | The source code for the main application server |
| Infrastructure Deployment | The Terraform infrastructure code for deploying the application server to GCP |
The source code for the HR Integration App has not been fully audited and does not follow existing DevOps practices, therefore it is only available to DevOps team members actively working on the project.
Technologies Used¶
The following gives an overview of the technologies the service is built on.
| Category | Language | Framework(s) |
|---|---|---|
| Server | Java | Spring |
| Database | Oracle 19c | Hibernate |
| Frontend | JavaScript | JQuery / Bootstrap |
Operational documentation¶
Note
Information about the operation of the existing on-prem deployment is contained within the README.md of the web application.
The following gives an overview of how the HR Integration App will be deployed and maintained within GCP:
Deployment¶
Deployment to the GCP environment is via our standard terraform deployment CI pipeline.
Monitoring¶
Monitoring is configured as per our standard Google Cloud Run application module.
Access Management¶
Access management is managed internally within the application, with the application holding a list of users who are able to access the admin UI within the Oracle database.
Service Management¶
The service owner for the service is Nick Stocks
The service manager for the service is Andrew Crook
The tech lead for the service is Abubakar Zubair
The following engineers have operational experience with the HR Integration App and are able to respond to support requests or incidents: