Menu Close
Settings Close

Language and Page Formatting Options

8.2. Business Central Console and BRMS Integration

8.2.1. Business Central Console and BRMS Integration

The Business Central Console is integrated with the JBoss BRMS repository. The console will retrieve artifacts from all available packages in the repository (please note this does not include packages in the Global Area). Packages must be built in BRMS before they will be visible in the console. When a package has been updated and rebuilt, the updated package can be accessed in the console by pressing the refresh button.
The console will attempt to retrieve all available packages from the BRMS repository, and, as such, all packages must have been successfully built in BRMS. It is possible to limit the packages the console will attempt to retrieve, please see Section 8.2.2, “Configuring the Business Central Console” for details.
To build all packages in BRMS at once, from the navigation menu select Knowledge BasesCreate NewRebuild all package binaries.

8.2.2. Configuring the Business Central Console

The management console is configured with the jbpm.console.properties file, which is located in the jboss-as/server/profile/deploy/business-central-server.war/WEB-INF/classes/ directory. This file configures the following properties:

Note

Not all of the properties listed below are included in the jbpm.console.properties file by default.
  • jbpm.console.server.host (default localhost)
  • jbpm.console.server.port (default 8080)
  • jbpm.console.task.service.host (default localhost) host where Task Server is deployed applies to all transports
  • jbpm.console.tmp.dir: An optional property that is used to set the location of the jbpmSessionId.ser file, which stores the session ID of the most recently used persisted session.
  • jbpm.console.task.service.port: The port where the task server is deployed (5446 when using HornetQ)
  • jbpm.console.task.service.strategy (default HornetQ)
  • JMSTaskClient.connectionFactory (no default) JNDI name of connection factory only for JMS
  • JMSTaskClient.acknowledgeMode (no default) acknowledgment mode only for JMS
  • JMSTaskClient.transactedQueue (no default) transacted queue name only for JMS
  • JMSTaskClient.queueName (no default) queue name only for JMS
  • JMSTaskClient.responseQueueName (no default) response queue name only for JMS
  • guvnor.protocol (default http)
  • guvnor.host (default localhost:8080)
  • guvnor.subdomain (default drools-guvnor)
  • guvnor.usr (default admin)
  • guvnor.pwd (default admin)
  • guvnor.packages (comma separated list of packages to load from Guvnor. When no packages have been specified, all packages will be visible. When specifying packages that should be visible, it is important to remember only the specified packages be visible.)
  • guvnor.connect.timeout (default 10000)
  • guvnor.read.timeout (default 10000)
  • guvnor.snapshot.name (default LATEST) This is an optional property that specifies the name of the snapshot to use.

Note

The password and username contained in this file must match the credentials set in jboss-as/server/production/deploy/jboss-brms.war/WEB-INF/components.xml. If the credentials are changed in one place, they must be changed in both locations.
The Business Central console can be clustered so that multiple instances of the console and the process engine attached to the console can share the same data in a persisted database. Clustering the console makes it possible to spread the available processes across the cluster, and also ensures failover if a node in the cluster fails. See the BRMS Getting Start Guide for details.

8.2.3. User and Group Management

The human task service requires users to be defined as group members so that group members can claim tasks that are assigned to that group. The console uses username / group associations; when using the JBoss BRMS 5.3 standalone installation, the group assignments are specified in the brms-roles.properties file in the server/profile/conf/props/ directory.
Alternative login modules can be configured; for details, please refer to the BRMS Administrator Guide about Security Authentication.