6.3. Logging into Business Central

Log into Business Central after the server has successfully started.

  1. Navigate to http://localhost:8080/business-central in a web browser. If the user interface has been configured to run from a domain name, substitute localhost for the domain name. For example http://www.example.com:8080/business-central.
  2. Log in with the user credentials that were created during installation. For example, user: helloworlduser and password: Helloworld@123.
Loading…​ screen does not disappear

When you log into Business Central, it is possible that the Loading…​ screen does not disappear. This can be caused by your firewall interfering with Server Sent Events (SSE) used by Business Central.

To work around the problem, disable SSE usage by the Business Central:

  1. Create an ErraiService.properties file, which contains: errai.bus.enable_sse_support=false.
  2. Copy the file to INSTALL_PATH/standalone/deployments/business-central.war/WEB-INF/classes/.
  3. Redeploy business-central.war.

You can create two types of Red Hat JBoss BPM Suite clusters:

Design-Time Clustering

Enables you to share assets in the Git repository, such as processes, rules, data objects, and others, with all the Red Hat JBoss BPM Suite nodes in your cluster. It is suitable in case of concerns about a single point of failure and high availability during the development process. Design-time clustering makes use of Apache Helix and Apache ZooKeeper.

Design-time clustering is not required for runtime execution.

Runtime Clustering
Enables you to use the clustering capabilities of your container, such as Red Hat JBoss EAP. Runtime clustering does not require you to manage any Apache Helix or Apache ZooKeeper nodes. Quartz Enterprise Job Scheduler is supported if you use timers in your application.

If you use the Websphere Application Server, Quartz setup is not necessary. Instead, use clustered EJB Timers. For more information, see the How to setup BPM Suite Timers to work in Websphere Application Server clustering support article.

You can cluster the following components of Red Hat JBoss BPM Suite:

  • Design-time cluster

    • Git repository: virtual-file-system (VFS) repository that holds the business assets.
  • Runtime cluster

    • Intelligent Process Server, or web applications: the web application nodes must share runtime data.

      For instructions on clustering the Intelligent Process Server, see Section 6.5.5, “Clustering the Intelligent Process Server”, or the clustering documentation of your container.

    • Back-end database: database with the state data, such as process instances, KIE sessions, history log, and similar.