此内容没有您所选择的语言版本。
Chapter 11. Maven settings and repositories for Red Hat Decision Manager
You can use an external Maven repository to deploy a project. When you create a project, Decision Central uses the Maven repositories that are configured for Decision Central. You can use the Maven global or user settings to direct all Red Hat Decision Manager projects to retrieve dependencies from the public Red Hat Decision Manager repository by modifying the following files:
-
The Maven
settings.xmlfile. -
The Maven project object model (POM) file (
pom.xml).
For more information, see Packaging and deploying a Red Hat Decision Manager project.
To use the correct Maven dependencies in your Red Hat Decision Manager project, add the Red Hat Business Automation bill of materials (BOM) files to the project’s pom.xml file. The Red Hat Business Automation BOM applies to both Red Hat Decision Manager and Red Hat Process Automation Manager. When you add the BOM files, the correct versions of transitive dependencies from the provided Maven repositories are included in the project.
For more information about the Red Hat Business Automation BOM, see What is the mapping between Red Hat Decision Manager and the Maven library version?.
Procedure
Declare the Red Hat Business Automation BOM in the
pom.xmlfile:Copy to Clipboard Copied! Toggle word wrap Toggle overflow -
Declare dependencies required for your project in the
<dependencies>tag. After you import the product BOM into your project, the versions of the user-facing product dependencies are defined so you do not need to specify the<version>sub-element of these<dependency>elements. However, you must use the<dependency>element to declare dependencies which you want to use in your project. For standalone projects that are not authored in Decision Central, specify all dependencies required for your projects. In projects that you author in Decision Central, the basic decision engine dependencies are provided automatically by Decision Central.
- For a basic Red Hat Decision Manager project, declare the following dependencies, depending on the features that you want to use:
For a basic Red Hat Decision Manager project, declare the following dependencies:
Embedded decision engine dependencies
Copy to Clipboard Copied! Toggle word wrap Toggle overflow To use the Decision Server, declare the following dependencies:
Client application Decision Server dependencies
<dependency> <groupId>org.kie.server</groupId> <artifactId>kie-server-client</artifactId> </dependency>
<dependency> <groupId>org.kie.server</groupId> <artifactId>kie-server-client</artifactId> </dependency>Copy to Clipboard Copied! Toggle word wrap Toggle overflow To create a remote client for Red Hat Decision Manager, declare the following dependency:
Client dependency
<dependency> <groupId>org.uberfire</groupId> </dependency>
<dependency> <groupId>org.uberfire</groupId> </dependency>Copy to Clipboard Copied! Toggle word wrap Toggle overflow When creating a JAR file that includes assets, such as rules and process definitions, specify the packaging type for your Maven project as
kjarand useorg.kie:kie-maven-pluginto process thekjarpackaging type located under the<project>element. In the following example,${kie.version}is the Maven library version listed in What is the mapping between Red Hat Decision Manager and the Maven library version?:Copy to Clipboard Copied! Toggle word wrap Toggle overflow
You can configure Decision Central and Decision Server to use an external Maven repository, such as Nexus or Artifactory, instead of the built-in repository. This enables Decision Central and Decision Server to access and download artifacts that are maintained in the external Maven repository.
"Artifacts in the repository do not receive automated security patches as Maven requires that artifacts be immutable. As a result, artifacts that are missing patches for known security flaws will remain in the repository to avoid breaking builds that depend on them. Patched artifacts have their version number incremented". For more information, see JBoss Enterprise Maven Repository.
For information about configuring an external Maven repository for an authoring environment on Red Hat OpenShift Container Platform, see Deploying a Red Hat Decision Manager authoring or managed server environment on Red Hat OpenShift Container Platform.
Prerequisite
Decision Central and Decision Server are installed. For installation options, see Planning a Red Hat Decision Manager installation.
Procedure
-
Create a Maven
settings.xmlfile with connection and access details for your external repository. For details about thesettings.xmlfile, see the Maven Settings Reference. -
Save the file in a known location, for example,
/opt/custom-config/settings.xml. -
In your Red Hat Decision Manager installation directory, navigate to the
standalone-full.xmlfile. For example, if you use a Red Hat JBoss EAP installation for Red Hat Decision Manager, go to$EAP_HOME/standalone/configuration/standalone-full.xml. Open
standalone-full.xmland under the<system-properties>tag, set thekie.maven.settings.customproperty to the full path name of thesettings.xmlfile.For example:
<property name="kie.maven.settings.custom" value="/opt/custom-config/settings.xml"/>
<property name="kie.maven.settings.custom" value="/opt/custom-config/settings.xml"/>Copy to Clipboard Copied! Toggle word wrap Toggle overflow - Start or restart Decision Central and Decision Server.
Next steps
For each Decision Central project that you want to export or push as a KJAR artifact to the external Maven repository, you must add the repository information in the project pom.xml file. For instructions, see Packaging and deploying a Red Hat Decision Manager project.