Employee Rostering Optimization as a Service
Running on OpenShift Dedicated (paid edition)
Install the oc client tools
To copy-paste your command, go to the OpenShift Online web console and look for Help > Command line tools.
Login to OpenShift Dedicated from command line:
oc login https://api.YOUR_SERVER.openshift.com --token=<tokenId>
If you don’t know your
<tokenId>, log in at the OpenShift web console and look for Help > Command Line Tools.
Create, build and deploy the project.
./provision.sh setup --project-suffix mydemo
It should now be building the pod and running it on OpenShift. Go to the OpenShift Online web console to get the
*.openshiftapps.comURL to visit.
To build and deploy new changes, use:
To delete the OpenShift application and project, run:
Running on OpenShift Online (free edition)
This is not possible to due to resource limitations.
Running on a local OpenShift Origin
If you just installed oc client tools, follow the OpenShift Local Cluster Management docs to get
oc cluster (up|down)working.
oc cluster up
oc login, enter
developerfor both username and password when prompted
oc new-project optaweb-employee-rostering
oc new-app --image-stream="openshift/wildfly:10.1" https://github.com/kiegroup/optaweb-employee-rostering.git#master
To trigger a new build with the latest updates from the master branch, run
oc start-build optaweb-employee-rostering
To delete the OpenShift application and project, run
oc delete project optaweb-employee-rostering
Both IntelliJ and Eclipse formatters are available here: https://github.com/kiegroup/droolsjbpm-build-bootstrap/tree/master/ide-configuration
Building from source
mvn clean install
Under the covers, OpenShift builds activate the
To reproduce locally, add it explicitly (the
provision.sh script already does this):
mvn clean package -P openshift
IntelliJ IDEA Ultimate 2018.1
To run SuperDevMode and debug both backend and client code from IDEA you need to create two separate run configurations.
CodeServer run configuration
Create Maven configuration and set following parameters:
launcherDiris configured to point to
launcherDirproperty can be set in
pom.xmlor via system property.
AppServer run configuration
Add local JBoss Server configuration.
Configure the Application server field to point to a local WildFly 11 installation.
Click Fix button at the bottom of the dialogue and select
Remove any steps that were automatically added to the Before launch phase.
Check After launch and select Chrome browser.
Set start page to
Set both On Update action and On frame deactivation to Update classes and resources.
Run SuperDevMode in IDEA
Do a clean build:
mvn clean install -DskipTests
Run the CodeServer configuration in normal mode.
Run the AppServer configuration in debug mode.
If something goes wrong, do a clean build and click Maven Projects > Reimport All Maven Projects.
IntelliJ IDEA 2017.2 (and below) + CLI
The steps below make sure that the GWT Codeserver will recompile the application after files under
src/main/resources are saved.
Import the maven project by choosing the root
pom.xmlfile and selecting
Open as project
Restart IntelliJ (required after installing the plugin)
Other settings, go to the
Save Actionssubmenu and check either the first or the second options in the
Compile fileoption in the
After configuring the
Save Actions plugin, you should be able to start Wildfly and deploy the application from the CLI. Note that if you need to restart the GWT Code Server, it’s not mandatory to restart Wildfly.
mvn -N wildfly:start wildfly:deploy mvn gwt:codeserver
To stop the Wildfly server, use
mvn -N wildfly:shutdown.