Chapter 2. Project deployment in Business Central

Procedure

1. In your Red Hat Process Automation Manager installation directory, navigate to the standalone-full.xml file. For example, if you use a Red Hat JBoss EAP installation for Red Hat Process Automation Manager, go to $EAP_HOME/standalone/configuration/standalone-full.xml.

2. Open standalone-full.xml and under the <system-properties> tag, set the following properties:

   • org.kie.server.controller.user: The user name of a user who can log in to the Business Central.
   • org.kie.server.controller.pwd: The password of the user who can log in to the Business Central.
   • org.kie.server.controller: The URL for connecting to the API of Business Central. Normally, the URL is http://<centralhost>:<centralport>/business-central/rest/controller, where <centralhost> and <centralport> are the host name and port for Business Central. If Business Central is deployed on OpenShift, remove business-central/ from the URL.
   • org.kie.server.location: The URL for connecting to the API of Process Server. Normally, the URL is http://<serverhost>:<serverport>/kie-server/services/rest/server, where <serverhost> and <serverport> are the host name and port for Process Server.
   • org.kie.server.id: The name of a server configuration. If this server configuration does not exist in Business Central, it is created automatically when Process Server connects to Business Central.

   Example:

   <property name="org.kie.server.controller.user" value="central_user"/>
   <property name="org.kie.server.controller.pwd" value="central_password"/>
   <property name="org.kie.server.controller" value="http://central.example.com:8080/business-central/rest/controller"/>
   <property name="org.kie.server.location" value="http://kieserver.example.com:8080/kie-server/services/rest/server"/>
   <property name="org.kie.server.id" value="production-servers"/>

3. Start or restart the Process Server.

Procedure

1. Create a Maven settings.xml file with connection and access details for your external repository. For details about the settings.xml file, see the Maven Settings Reference.
2. Save the file in a known location, for example, /opt/custom-config/settings.xml.
3. In your Red Hat Process Automation Manager installation directory, navigate to the standalone-full.xml file. For example, if you use a Red Hat JBoss EAP installation for Red Hat Process Automation Manager, go to $EAP_HOME/standalone/configuration/standalone-full.xml.

4. Open standalone-full.xml and under the <system-properties> tag, set the kie.maven.settings.custom property to the full path name of the settings.xml file.

   For example:

   <property name="kie.maven.settings.custom" value="/opt/custom-config/settings.xml"/>

5. Start or restart Business Central and Process Server.

Procedure

1. In Business Central, go to Menu → Design → Projects, click the project name, and select any asset in the project.
2. In the Project Explorer menu on the left side of the screen, click the Customize View gear icon and select Repository View → pom.xml.

3. Add the following settings at the end of the project pom.xml file (before the </project> closing tag). The values must correspond to the settings that you defined in your settings.xml file.

   <distributionManagement>
   <repository>
   <id>${maven-repo-id}</id>
   <url>${maven-repo-url}</url>
   <layout>default</layout>
   </repository>
   </distributionManagement>

4. Click Save to save the pom.xml file changes.

Procedure

1. In Business Central, go to Menu → Design → Projects and click the project name.

2. In the upper-right corner, click Deploy to build and deploy the project.

   Note

   To compile the project without deploying it to Process Server, click Build.

   If only one Process Server is connected to Business Central, or if all connected Process Servers are in the same server configuration, the services in the project are started automatically in a deployment unit (KIE container).

   If multiple server configurations are available, a deployment dialog is displayed in Business Central, prompting you to specify server and deployment details.

3. If the deployment dialog appears, verify or set the following values:

   • Deployment Unit Id / Deployment Unit Alias: Verify the name and alias of the deployment unit (KIE container) running the service within the Process Server. You normally do not need to change these settings.
   • Server Configuration: Select the server configuration for deploying this project. You can later deploy it to other configured servers without rebuilding the project.
   • Start Deployment Unit?: Verify that this box is selected to start the deployment unit (KIE container). If you clear this box, the service is deployed onto the server but not started.

Procedure

1. In Business Central, go to Menu → Design → Projects and click the project name.
2. Click the project Settings tab.

3. In General Settings, modify the Group ID, Artifact ID, or Version fields as necessary. If you have deployed the project and are developing a new version, usually you need to increase the version number.

   Note

   For development purposes only, you can add the SNAPSHOT suffix in the project version to instruct Maven to get a new snapshot update according to the Maven policy. Do not use the SNAPSHOT suffix for a production environment.

4. Click Save to finish.