Chapter 4. Configuring and starting KIE Server You can configure your KIE Server location, user name, password, and other related properties by defining the necessary configurations when you start KIE Server. Procedure Navigate to the Red Hat Decision Manager 7.13 bin directory and start the new KIE Server with the following properties. Adjust the specific properties according to your environment. 1 Start command with standalone-full.xml server profile 2 Server ID that must match the server configuration name defined in Business Central 3 User name to connect with KIE Server from the Process Automation Manager controller 4 Password to connect with KIE Server from the Process Automation Manager controller 5 Process Automation Manager controller location, Business Central URL with /rest/controller suffix 6 User name to connect to the Process Automation Manager controller REST API 7 Password to connect to the Process Automation Manager controller REST API 8 KIE Server location (on the same instance as Business Central in this example) Note If Business Central and KIE Server are installed on separate application server instances (Red Hat JBoss EAP or other), use a separate port for the KIE Server location to avoid port conflicts with Business Central. If a separate KIE Server port has not already been configured, you can add a port offset and adjust the KIE Server port value accordingly in the KIE Server properties. Example: If the Business Central port is 8080, as in this example, then the KIE Server port, with a defined offset of 150, is 8230. KIE Server connects to the new Business Central and collects the list of deployment units (KIE containers) to be deployed. Note When you use a class inside a dependency JAR file to access KIE Server from KIE Server client, you get the ConversionException and ForbiddenClassException in Business Central. To avoid generating these exceptions in Business Central, do one of the following: If the exceptions are generated on the client-side, add following system property to the kie-server client: If the exceptions are generated on the server-side, open standalone-full.xml from the Red Hat Decision Manager installation directory, set the following property under the <system-properties> tag: Set the following JVM property: It is expected that you do not configure the classes that exists in KJAR using these system property. Ensure that only known classes are used in the system property to avoid any vulnerabilities. The org.example is an example package, you can define any package that you want to use. You can specify multiple packages separated by comma , for example, org.example1.* * , org.example2.* * , org.example3.* * . You can also add specific classes , for example, org.example1.Mydata1, org.example2.Mydata2 .

Commands:
~/EAP_HOME/bin/standalone.sh --server-config=standalone-full.xml 1 -Dorg.kie.server.id=myserver 2 -Dorg.kie.server.user=kie_server_username 3 -Dorg.kie.server.pwd=kie_server_password 4 -Dorg.kie.server.controller=http://localhost:8080/business-central/rest/controller 5 -Dorg.kie.server.controller.user=controller_username 6 -Dorg.kie.server.controller.pwd=controller_password 7 -Dorg.kie.server.location=http://localhost:8080/kie-server/services/rest/server 8
-Djboss.socket.binding.port-offset=150 -Dorg.kie.server.location=http://localhost:8230/kie-server/services/rest/server
System.setProperty("org.kie.server.xstream.enabled.packages", "org.example.**");
<property name="org.kie.server.xstream.enabled.packages" value="org.example.**"/>
-Dorg.kie.server.xstream.enabled.packages=org.example.**