Dieser Inhalt ist in der von Ihnen ausgewählten Sprache nicht verfügbar.
Chapter 5. Red Hat Decision Manager Spring Boot configuration
After you create your Spring Boot project, you can configure several components to customize your application.
5.1. Configuring REST endpoints for Spring Boot applications Link kopierenLink in die Zwischenablage kopiert!
After you create your Spring Boot project, you can configure the host, port, and path for the REST endpoint for your Spring Boot application.
Prerequisites
- You have a ZIP file that you created using the business application website.
Procedure
-
Extract the Spring Boot project ZIP file and navigate to the
<BUSINESS-APPLICATION>/<BUSINESS-APPLICATION>-service/src/main/resourcesfolder, where<BUSINESS-APPLICATION>is the name of your Spring Boot project. -
Open the
application.propertiesfile in a text editor. Configure the host, port, and path for the REST endpoints, where
<ADDRESS>is the server address and<PORT>is the server port:server.address=<ADDRESS> server.port=<PORT> cxf.path=/rest
server.address=<ADDRESS> server.port=<PORT> cxf.path=/restCopy to Clipboard Copied! Toggle word wrap Toggle overflow The following example adds the REST endpoint to the address
localhoston port8090.server.address=localhost server.port=8090 cxf.path=/rest
server.address=localhost server.port=8090 cxf.path=/restCopy to Clipboard Copied! Toggle word wrap Toggle overflow
5.2. Configuring the KIE Server identity Link kopierenLink in die Zwischenablage kopiert!
After you create your Spring Boot project, you can configure KIE Server so that it can be easily identified.
Prerequisites
- You have a Spring Boot business application ZIP file that you created using the business application website.
Procedure
-
Extract the Spring Boot project ZIP file and navigate to the
<BUSINESS-APPLICATION>/<BUSINESS-APPLICATION>-service/src/main/resourcesfolder, where<BUSINESS-APPLICATION>is the name of your Spring Boot project. -
Open the
application.propertiesfile in a text editor. Configure the KIE Server parameters as shown in the following example:
kieserver.serverId=<BUSINESS-APPLICATION>-service kieserver.serverName=<BUSINESS-APPLICATION>-service kieserver.location=http://localhost:8090/rest/server kieserver.controllers=http://localhost:8080/decision-central/rest/controller
kieserver.serverId=<BUSINESS-APPLICATION>-service kieserver.serverName=<BUSINESS-APPLICATION>-service kieserver.location=http://localhost:8090/rest/server kieserver.controllers=http://localhost:8080/decision-central/rest/controllerCopy to Clipboard Copied! Toggle word wrap Toggle overflow The following table describes the KIE Server parameters that you can configure in your business project:
Expand Table 5.1. kieserver parameters Parameter Values Description kieserver.serverIdstring
The ID used to identify the business application when connecting to the Decision Manager controller.
kieserver.serverNamestring
The name used to identify the business application when it connects to the Decision Manager controller. Can be the same string used for the
kieserver.serverIdparameter.kieserver.locationURL
Used by other components that use the REST API to identify the location of this server. Do not use the location as defined by
server.addressandserver.port.kieserver.controllersURLs
A comma-separated list of controller URLs.
5.3. Configuring KIE Server components to start at runtime Link kopierenLink in die Zwischenablage kopiert!
If you selected Business Automation when you created your Spring Boot business application, you can specify which KIE Server components must start at runtime.
Prerequisites
- You have a Spring Boot business application ZIP file that you created using the business application website.
Procedure
-
Extract the Spring Boot project ZIP file and navigate to the
<BUSINESS-APPLICATION>/<BUSINESS-APPLICATION>-service/src/main/resourcesfolder, where<BUSINESS-APPLICATION>is the name of your Spring Boot project. -
Open the
application.propertiesfile in a text editor. To set a component to start at runtime, set the value of the component to
true.The following table lists the components that you can set to start at runtime:
Expand Table 5.2. kieserver capabilities parameters Parameter Values Description kieserver.drools.enabledtrue, falseEnables or disables the Decision Manager component.
kieserver.dmn.enabledtrue, falseEnables or disables the Decision Model and Notation (DMN) component.
5.4. Configuring business application user group providers Link kopierenLink in die Zwischenablage kopiert!
With Red Hat Decision Manager, you can manage human-centric activities. To provide integration with user and group repositories, you can use two KIE API entry points:
-
UserGroupCallback: Responsible for verifying whether a user or group exists and for collecting groups for a specific user -
UserInfo: Responsible for collecting additional information about users and groups, for example email addresses and preferred language
You can configure both of these components by providing alternative code, either code provided out of the box or custom developed code.
For the UserGroupCallback component, retain the default implementation because it is based on the security context of the application. For this reason, it does not matter which backend store is used for authentication and authorisation (for example, RH-SSO). It will be automatically used as a source of information for collecting user and group information.
The UserInfo component is a separate component because it collects more advanced information.
Prerequisites
- You have a ZIP file that you created using the business application website and that contains a business automation project.
Procedure
To provide an alternative implementation of
UserGroupCallback, add the following code to the Application class or a separate class annotated with@Configuration:@Bean(name = "userGroupCallback") public UserGroupCallback userGroupCallback(IdentityProvider identityProvider) throws IOException { return new MyCustomUserGroupCallback(identityProvider); }@Bean(name = "userGroupCallback") public UserGroupCallback userGroupCallback(IdentityProvider identityProvider) throws IOException { return new MyCustomUserGroupCallback(identityProvider); }Copy to Clipboard Copied! Toggle word wrap Toggle overflow To provide an alternative implementation of
UserInfo, add the following code to the Application class or a separate class annotated with@Configuration:@Bean(name = "userInfo") public UserInfo userInfo() throws IOException { return new MyCustomUserInfo(); }@Bean(name = "userInfo") public UserInfo userInfo() throws IOException { return new MyCustomUserInfo(); }Copy to Clipboard Copied! Toggle word wrap Toggle overflow
5.5. Enabling Swagger documentation Link kopierenLink in die Zwischenablage kopiert!
You can enable Swagger-based documentation for all endpoints available in the service project of your Red Hat Decision Manager business application.
Prerequisites
- You have a Spring Boot application ZIP file that you created using the business applications website.
Procedure
-
Extract the
<BUSINESS-APPLICATION>.zipfile and navigate to the<BUSINESS-APPLICATION>/<BUSINESS-APPLICATION>-servicefolder, where<BUSINESS-APPLICATION>is the name of your Spring Boot project. -
Open the service project
pom.xmlfile in a text editor. Add the following dependencies to the service project
pom.xmlfile and save the file.Copy to Clipboard Copied! Toggle word wrap Toggle overflow To enable the Swagger UI (optional), add the following dependency to the
pom.xmlfile and save the file.<dependency> <groupId>org.webjars</groupId> <artifactId>swagger-ui</artifactId> <version>2.2.10</version> </dependency>
<dependency> <groupId>org.webjars</groupId> <artifactId>swagger-ui</artifactId> <version>2.2.10</version> </dependency>Copy to Clipboard Copied! Toggle word wrap Toggle overflow -
Open the
<BUSINESS-APPLICATION>/<BUSINESS-APPLICATION>-service/src/main/resources/application.propertiesfile in a text editor. Add the following line to the
application.propertiesfile to enable Swagger support:kieserver.swagger.enabled=true
kieserver.swagger.enabled=trueCopy to Clipboard Copied! Toggle word wrap Toggle overflow
After you start the business application, you can view the Swagger document at http://localhost:8090/rest/swagger.json. The complete set of endpoints is available at http://localhost:8090/rest/api-docs?url=http://localhost:8090/rest/swagger.json.