Configuring Business Central settings and properties

Procedure

1. In Business Central, select the Admin icon in the top-right corner of the screen and select Users.
2. Click New user, enter a user name, and then click Next.
3. To assign roles to the user, click the Roles tab, click Add Roles, select the desired roles, and click Add to selected roles.
4. Optionally, to assign groups to the user, click the Groups tab, click Add to groups, select the desired groups, and click Add to selected groups.
5. Click Create.
6. Click Yes to set a password for the user, enter a desired password, and click Change.

Procedure

1. In Business Central, select the Admin icon in the top-right corner of the screen and select Users.
2. From the All users list, click the user you want to edit. The user details display in the right pane.

3. Click Edit to perform any of the following tasks:

   • To change the groups of a user, click the Groups tab, click Add to groups, select the groups you want the user to be part of, click Add to selected groups, and click Save.
   • To change the roles of a user, click the Roles tab, click Add roles, select the roles you want to assign to the user, click Add to selected roles, and click Save.
   • To view the user permissions, click the Permissions tab and expand the attributes.
   • To change the password, click Change Password, enter the new password, and click Change.
   • To delete the user, click Delete and then click Yes to confirm removal.

Procedure

1. In Business Central, select the Admin icon in the top-right corner of the screen and select Groups.
2. Click New group, enter a group name, and then click Next.

3. Select the users that you want to add to this group, and then click Add selected users.

   The newly created group is listed under All groups.

Procedure

1. In Business Central, select the Admin icon in the top-right corner of the screen and select Groups.
2. From the All groups list, click the group that you want to edit. The user details display in the right pane.
3. Select the home page from the Home Page list.
4. Select the priority from the Priority list.

5. In the Permissions section, expand the resource attribute and change its permission.

   Note

   You can add exceptions to Pages, Editor, Spaces, and Projects permissions.

6. Click Save to apply the changes.

Procedure

1. In Business Central, select the Admin icon in the top-right corner of the screen and select Artifacts.
2. Click Open to view the artifact details.
3. Click Ok to go back to the Artifacts page.

Procedure

1. In Business Central, select the Admin icon in the top-right corner of the screen and select Artifacts.
2. Click Download.
3. Browse to the directory where you want to save the artifact.
4. Click Save.

Procedure

1. In Business Central, select the Admin icon in the top-right corner of the screen and select Artifacts.
2. Click Upload.
3. Click Choose File and browse to the directory from where you want to upload the artifact.

4. Click Upload.

   Note

   If you are using a non-Maven artifact, first deploy the artifact to the Maven repository using the mvn deploy command and then refresh the artifact list in Business Central.

Procedure

1. In Business Central, select the Admin icon in the top-right corner of the screen and select Data Sources.
2. In the DataSource Explorer pane, click Add Driver. The New driver window opens.
3. In the New driver window, enter the Name, Driver Class Name, Group Id, Artifact Id, and Version of the database driver.
4. Click Finish to add the driver to Business Central.

Procedure

1. In Business Central, select the Admin icon in the top-right corner of the screen and select Data Sources.
2. In the DataSource Explorer pane, select the driver you want to edit.
3. In the Driver Definition pane, make the necessary changes to the Name, Driver Class Name, Group Id, Artifact Id, and the Version fields.
4. Click Update.
5. Click Yes to save the changes to the driver.

Procedure

1. In Business Central, select the Admin icon in the top-right corner of the screen and select Data Sources.
2. In the DataSource Explorer pane, select the driver you want to delete.
3. Click Remove.
4. Click Delete to delete the driver.

Procedure

1. In Business Central, select the Admin icon in the top-right corner of the screen and select Data Sources.
2. In the DataSource Explorer pane, click Add DataSource. The New data source window opens.
3. In the New data source window, enter the data source Name, database Connection URL, User and Password, and Driver.
4. Click Test Connection to verify the connection to the database.
5. Click Finish to add the data source to Business Central.

Procedure

1. In Business Central, select the Admin icon in the top-right corner of the screen and select Data Sources.
2. In the DataSource Explorer pane, click the data source you want to edit.
3. In the Data Source Definition pane, make the necessary changes to the Name, Connection URL, User, Password, and the Driver fields.
4. Click Test Connection to verify the connection to the database.
5. Click Update.
6. Click Save to confirm the changes to the data source.

Procedure

1. In Business Central, select the Admin icon in the top-right corner of the screen and select Data Sources.
2. In the DataSource Explorer pane, click the data source you want to delete.
3. Click Remove.
4. Click Delete to confirm the deletion of the data source.

Procedure

1. In Business Central, go to Admin → Data Sets. The Data Set Explorer page opens.

2. Click New Data Set and select one of the following provider types:

   • Bean: Use to generate a data set from a Java class
   • CSV: Use to generate a data set from a remote or local CSV file
   • SQL: Use to generate a data set from an ANSI-SQL compliant database
   • Elastic Search: Use to generate a data set from Elastic Search nodes

   • Execution Server: Use to generate a data set using the custom query feature of an Execution Server

     Note

     KIE Server must be configured with this option.

3. Complete the Data Set Creation Wizard and click Test.

   Note

   The configuration steps differ based on the provider you chose.

4. Click Save.

Procedure

1. In Business Central, go to Admin → Data Sets. The Data Set Explorer page opens.
2. In the Data Set Explorer pane, search for the data set you want to edit and click Edit.

3. In the Data Set Editor pane, use the appropriate tab to edit the data as required. The tabs differ based on the data set provider type you chose.

   For example, the following changes are applicable for editing a CSV data provider:

   • CSV Configuration: Enables you to change the name of the data set definition, the source file, the separator, and other properties.

   • Preview: Enables you to preview the data. After you click Test in the CSV Configuration tab, the system executes the data set lookup call and if the data is available, a preview appears. Note that the Preview tab has two sub-tabs:

     • Data columns: Enables you to specify what columns are part of your data set definition.
     • Filter: Enables you to add a new filter.

   • Advanced: Enables you to manage the following configurations:

     • Caching: See Section 5.4, “Caching” for more information.
     • Cache life-cycle Enables you to specify an interval of time after which a data set (or data) is refreshed. The Refresh on stale data feature refreshes the cached data when the back-end data changes.
4. After making the required changes, click Validate.
5. Click Save.

Procedure

1. Open a command terminal on your system.

2. Run the ssh-keygen command to create the SSH key as shown in the following example, where <user_login> is your user name:

   ssh-keygen -t rsa -b 4096 -C "<user_login>"

   Note

   The SSH key formats supported by Business Central keystore are ssh-rsa, ssh-dss, ecdsa-sha2-nistp256, ecdsa-sha2-nistp384, and ecdsa-sha2-nistp521.

3. When prompted, press Enter and accept the default key file location as shown in the following example, where <user_login> is your user name:

   Enter a file in which to save the key (/home/<user_login>/.ssh/id_rsa): [Press enter]

4. At the command prompt, enter and confirm the passphrase:

   Enter passphrase (empty for no passphrase): [Type a passphrase]
   Enter same passphrase again: [Type passphrase again]

5. Start the ssh-agent:

   eval "$(ssh-agent -s)"
   Agent pid <any-number-here>

6. Add the new SSH private key to the ssh-agent. If you have used a different key name, replace id_rsa in that code:

   ssh-add ~/.ssh/id_rsa

Procedure

1. Open a command terminal on your system.

2. Run the cat command as shown in the following example, where id_rsa is your key name:

   cat ~/.ssh/id_rsa.pub

3. Copy the contents of your SSH public key.
4. In Business Central, select the Admin icon in the top-right corner of the screen and select SSH Keys.
5. On the SSH Keys page, click Add SSH Key.

6. In the Add SSH Key window, enter a name in the Name field and copy the contents of the SSH public key to the Key field.

   Note

   The Name and the Key fields are mandatory.

7. Click Add SSH Key to register the key.

Procedure

1. In Business Central, select the Admin icon in the top-right corner of the screen and select SSH Keys.
2. On the SSH Keys page, click the delete icon of the SSH key you want to delete.
3. Click Delete SSH Key to confirm the deletion.

Procedure

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

3. In the General Settings tab, perform any of the following tasks:

   • To enable other projects to have the same GAV, select the Disable GAV conflict check check box.
   • To enable child projects to have GAV edition, select the Allow child GAV edition check box.

4. Click Save.

   Note

   You can click Reset to undo all changes.

5. Click Save to confirm the changes.

Procedures

1. In Business Central, select the Admin icon in the top-right corner of the screen and select Projects. The Projects window opens.

2. In the Advanced GAV preferences tab, perform any of the following tasks:

   • To enable other projects to have the same GAV, select the Disable GAV conflict check check box.
   • To enable child projects to have GAV edition, select the Allow child GAV edition check box.
3. Click Save.

Procedure

1. In Business Central, go to Menu → Projects.
2. Select or create the space that you want to import the Git projects into.
3. Click on the right side of the screen and select Import Project.
4. In the Import Project window, enter the URL of your Git repository, for example, https://github.com/USERNAME/REPOSITORY_NAME.git, and the credentials for the Git repository.

5. Click Import.

   The project is added to the Business Central Git repository and is then available in the space.

   Important

   Use the HTTPS or Git protocol instead of a SCP-style SSH URL. Business Central does not support the basic SSH URL and an error appears if you use this URL.

   You must have your public ssh key configured in your Git provider.

   The Git repository must be a KJAR project, containing only a single KJAR that is compatible with the Red Hat Decision Manager version. The KJAR content must be in the root of the repository.

6. In a command terminal, navigate to the repository folder:

   cd JBOSS_HOME/bin/.niogit/<SPACE>/REPOSITORY_NAME.git

7. Create a post-commit file in a hooks folder with permissions set to rwxr—​r--. For example, JBOSS_HOME/bin/.niogit/<SPACE>/REPOSITORY_NAME.git/hooks/post-commit.

8. Add the following content to the post-commit file:

   #!/bin/sh
   git push origin +master

9. To check that the configuration was successful, create a guided rule in Business Central:

   1. In Business Central go to Menu → Projects → Add Asset → Guided Rule.
   2. On the Create new Guided Rule page, enter the required information.

   3. Click Ok.

      Business Central automatically pushes all changes to the remote repository.

Procedure

1. Create the *.properties file and add a line for each exit code with a corresponding message in the following format:

   <exit_code>=<display_message>

   The <exit_code> is the Git hook exit code and the <display_message> is the custom message that is displayed to a user.

   For example:

   0=Success! All working as expected.
   1=Warning! Please check the logs and advise your admin.
   .
   .
   31=Error! Please advise your admin immediately.

   Note

   It is not necessary to define all the possible exit codes in the *.properties file. Notifications appear only for the exit codes defined in the *.properties file.

   Important

   The notification service only supports the ISO 8859-1 (LATIN 1) character set in the properties file. If you want to use extended characters, please use their escaped Unicode character code sequences.

2. To enable Git hook notifications, specify the path to the file as the value of the appformer.git.hooks.bundle system property.

   See the following example of a standalone.xml file with the setting that points to a Messages.properties file:

   <system-properties>
     <property name="appformer.git.hooks.bundle" value="/opt/jboss-as/git-hooks-messages/Messages.properties">
     </property>
     ...
   </system-properties>