6.3. Logging into Business Central
Log into Business Central after the server has successfully started.
http://localhost:8080/business-centralin a web browser. If the user interface has been configured to run from a domain name, substitute
localhostfor the domain name. For example
Log in with the user credentials that were created during installation. For example, user:
- 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:
ErraiService.propertiesfile, which contains:
Copy the file to
- Create an
You can create two types of Red Hat JBoss BRMS 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 BRMS 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 BRMS:
- Git repository: virtual-file-system (VFS) repository that holds the business assets.
RealTime Decision Server, or Web applications: the web application nodes must share runtime data.
For instructions on clustering the RealTime Decision Server, see Section 6.5.5, “Clustering the Realtime Decision Server”, or the clustering documentation of your container.