A Java EE 8 web application for managing system readiness at Jefferson Lab built with the Smoothness web template.
The System Readiness application allows machine operators and management to determine machine readiness. The app inventories all systems of the machine and organizes systems into a hierarchy of categories. Further, systems are assigned individual components to increase readiness specificity. To aid in answering the more common question of where can beam be sent, each component is associated with zero or more beam destinations. Component readiness is determined by System Responsible Groups, and each component has an ordered set assigned. Each Responsible Group is associated with a set of group leaders, who are authorized to mark final readiness.
- Grab project
git clone https://github.com/JeffersonLab/srm
cd srm
- Launch Compose
docker compose up
- Navigate to page
http://localhost:8080/srm
Note: Login with demo username "tbrown" and password "password".
This application requires a Java 11+ JVM and standard library to run, plus a Java EE 8+ application server (developed with Wildfly).
- Install service dependencies
- Download Wildfly 26.1.3
- Configure Wildfly and start it
- Download srm.war and deploy it to Wildfly
- Navigate your web browser to localhost:8080/srm
Wildfly must be pre-configured before the first deployment of the app. The wildfly bash scripts can be used to accomplish this. See the Dockerfile for an example.
Uses the Smoothness Environment Variables.
Additionally, the scheme, host name and port of the CEBAF Element Database (CED) server is configured with environment variable CED_SERVER_URL.
There are some Settings in the database as well.
This application requires an Oracle 18+ database with the following schema installed. The application server hosting this app must also be configured with a JNDI datasource.
This project is built with Java 17 (compiled to Java 11 bytecode), and uses the Gradle 7 build tool to automatically download dependencies and build the project from source:
git clone https://github.com/JeffersonLab/srm
cd srm
gradlew build
Note: If you do not already have Gradle installed, it will be installed automatically by the wrapper script included in the source
Note for JLab On-Site Users: Jefferson Lab has an intercepting proxy
See: Docker Development Quick Reference
In order to iterate rapidly when making changes it's often useful to run the app directly on the local workstation, perhaps leveraging an IDE. In this scenario run the service dependencies with:
docker compose -f deps.yaml up
Note: The local install of Wildfly should be configured to proxy connections to services via localhost and therefore the environment variables should contain:
KEYCLOAK_BACKEND_SERVER_URL=http://localhost:8081
FRONTEND_SERVER_URL=https://localhost:8443
Further, the local DataSource must also leverage localhost port forwarding so the standalone.xml connection-url field should be: jdbc:oracle:thin:@//localhost:1521/xepdb1.
The server and app setup scripts can be used to setup a local instance of Wildfly.
- Bump the version number in the VERSION file and commit and push to GitHub (using Semantic Versioning).
- The CD GitHub Action should run automatically invoking:
- The Create release GitHub Action to tag the source and create release notes summarizing any pull requests. Edit the release notes to add any missing details. A war file artifact is attached to the release.
- The Publish docker image GitHub Action to create a new demo Docker image.
- The Deploy to JLab GitHub Action to deploy to the JLab test environment.
The deploy to JLab's acctest is handled automatically via the release workflow.
At JLab this app is found at ace.jlab.org/srm and internally at acctest.acc.jlab.org/srm. However, those servers are proxies for wildfly5.acc.jlab.org and wildflytest5.acc.jlab.org respectively. A deploy script is provided on each server to automate wget and deploy. Example:
/root/setup/deploy.sh srm v1.2.3
JLab Internal Docs: InstallGuideWildflyRHEL9