jhflow

This application was generated using JHipster 4.6.2, you can find documentation and help at https://jhipster.github.io/documentation-archive/v4.6.2.

Development

Before you can build this project, you must install and configure the following dependencies on your machine:

1. Node.js: We use Node to run a development web server and build the project. Depending on your system, you can install Node either from source or as a pre-packaged bundle.

After installing Node, you should be able to run the following command to install development tools. You will only need to run this command when dependencies change in package.json.

npm install

We use npm scripts and Webpack as our build system.

Run the following commands in two separate terminals to create a blissful development experience where your browser auto-refreshes when files change on your hard drive.

./mvnw
npm start

[Npm][] is also used to manage CSS and JavaScript dependencies used in this application. You can upgrade dependencies by specifying a newer version in package.json. You can also run npm update and npm install to manage dependencies. Add the help flag on any command to see how you can use it. For example, npm help update.

The npm run command will list all of the scripts available to run for this project.

Service workers

Service workers are commented by default, to enable them please uncomment the following code.

• The service worker registering script in index.html

<script>
    if ('serviceWorker' in navigator) {
        navigator.serviceWorker
        .register('./sw.js')
        .then(function() { console.log('Service Worker Registered'); });
    }
</script>

• The copy file option in webpack-common.js

{ from: './src/main/webapp/sw.js', to: 'sw.js' },

Note: Add the respective scripts/assets in sw.js that is needed to be cached.

Managing dependencies

For example, to add Leaflet library as a runtime dependency of your application, you would run following command:

npm install --save --save-exact leaflet

To benefit from TypeScript type definitions from DefinitelyTyped repository in development, you would run following command:

npm install --save-dev --save-exact @types/leaflet

Then you would import the JS and CSS files specified in library's installation instructions so that Webpack knows about them:

Edit src/main/webapp/app/vendor.ts file:

import 'leaflet/dist/leaflet.js';

Edit src/main/webapp/content/css/vendor.css file:

@import '~leaflet/dist/leaflet.css';

Note: there are still few other things remaining to do for Leaflet that we won't detail here.

For further instructions on how to develop with JHipster, have a look at Using JHipster in development.

Using angular-cli

You can also use Angular CLI to generate some custom client code.

For example, the following command:

ng generate component my-component

will generate few files:

create src/main/webapp/app/my-component/my-component.component.html
create src/main/webapp/app/my-component/my-component.component.ts
update src/main/webapp/app/app.module.ts

Building for production

To optimize the jhflow application for production, run:

./mvnw -Pprod clean package

This will concatenate and minify the client CSS and JavaScript files. It will also modify index.html so it references these new files. To ensure everything worked, run:

java -jar target/*.war

Then navigate to http://localhost:8080 in your browser.

Refer to Using JHipster in production for more details.

Testing

To launch your application's tests, run:

./mvnw clean test

Client tests

Unit tests are run by Karma and written with Jasmine. They're located in src/test/javascript/ and can be run with:

npm test

For more information, refer to the Running tests page.

Using Docker to simplify development (optional)

You can use Docker to improve your JHipster development experience. A number of docker-compose configuration are available in the src/main/docker folder to launch required third party services. For example, to start a postgresql database in a docker container, run:

docker-compose -f src/main/docker/postgresql.yml up -d

To stop it and remove the container, run:

docker-compose -f src/main/docker/postgresql.yml down

You can also fully dockerize your application and all the services that it depends on. To achieve this, first build a docker image of your app by running:

./mvnw package -Pprod docker:build

Then run:

docker-compose -f src/main/docker/app.yml up -d

For more information refer to Using Docker and Docker-Compose, this page also contains information on the docker-compose sub-generator (jhipster docker-compose), which is able to generate docker configurations for one or several JHipster applications.

Continuous Integration (optional)

To configure CI for your project, run the ci-cd sub-generator (jhipster ci-cd), this will let you generate configuration files for a number of Continuous Integration systems. Consult the Setting up Continuous Integration page for more information.

Flowable Integration

1. Create standard JHipster application

2. Update pom.xml to add the following dependency to pom.xml: org.flowable flowable-spring-boot-starter-rest-api 6.1.0

3. Update the main application class to exclude the flowable SecurityAutoConfiguration

@ComponentScan @EnableAutoConfiguration(exclude = {MetricFilterAutoConfiguration.class, MetricRepositoryAutoConfiguration.class, org.flowable.spring.boot.SecurityAutoConfiguration.class}) @EnableConfigurationProperties({LiquibaseProperties.class, ApplicationProperties.class}) public class JhflowApp { 4. Create a “processes” directory under /resources and add a sample bpm process.

5. This is necessary as the autodeploy will fail otherwise and the engine will not start.

6. There will be an overlap in the userResource bean so update the Hipster app ReST Resource UserResource definition in /web/rest/UserResource. This name is not actually called by anything so a simple rename/refactor is all that is required. I renamed it to “JHserResource"

7. Update the Swagger default-include-path path in /resources/config/application.yml to look like: default-include-pattern: /(api|runtime|query|repository/process-definitions|repository/deployments|history)/.

8. The above swagger update includes the flowable ReST endpoints. This includes the most important API’s but doesn’t include management and other less obscure API’s.

9. Override the “default” auto-deployment strategy with a custom ProcessEngineConfigurationConfigurer class.

10. Override the Identity Service implementation of Flowable to use the JHipster user and group tables. This allows us to retain the AuthenticationProvider for JHipster. This will be pulled into the Process Engine Configuration in the “ProcessEngineConfigurationConfigurer” class using: processEnginerConfiguration.setIdmProcessEngineConfigurator(customIdmConfiguration). Refer : https://github.com/flowable/flowable-engine/tree/master/modules/flowable-ldap-configurator/src/main/java/org/flowable/ldap