Business Central 是微软提供的一款全面的业务管理软件解决方案，旨在帮助中小型企业实现数字化转型

Business Central（一般介绍）

Business Central 是微软提供的一款全面的业务管理软件解决方案，旨在帮助中小型企业实现数字化转型，提高业务效率和竞争力。以下是关于 Business Central 的一般介绍：

一、核心特点

1. 一体化管理：

   • Business Central 集成了财务、供应链、库存、销售、客户关系管理（CRM）等功能，实现了企业业务的全面覆盖。
   • 通过一体化的设计，Business Central 消除了信息孤岛，使得各部门之间的数据能够实时共享和协同工作。

2. 灵活性和可扩展性：

   • Business Central 支持根据企业的实际需求进行定制和扩展，满足企业的个性化管理需求。
   • 提供了丰富的API接口，方便与其他系统和服务进行集成。

3. 云端部署：

   • Business Central 支持云端部署，企业无需担心硬件和基础设施的维护，降低了IT成本。
   • 云端部署还使得企业可以随时随地访问业务数据，提高了工作效率。

4. 智能化分析：

   • 内置了强大的数据分析工具，帮助企业挖掘数据价值，优化业务流程。
   • 提供了直观的报表和仪表盘，方便企业实时监控业务运营情况。

二、主要功能

1. 财务管理：

   • 支持总账、应收账款、应付账款、现金管理等核心财务功能。
   • 提供了自动化的财务流程，减少了人工错误，提高了财务工作效率。

2. 供应链管理：

   • 支持采购、销售、库存管理等供应链功能。
   • 提供了实时的库存监控和预警功能，帮助企业优化库存管理，减少库存成本。

3. 客户关系管理（CRM）：

   • 支持客户信息管理、销售机会管理、客户服务等功能。
   • 提供了全方位的客户视图，帮助企业更好地了解客户需求，提高客户满意度。

4. 项目管理：

   • 支持项目计划、资源分配、进度跟踪等功能。
   • 提供了实时的项目监控和报告功能，帮助企业确保项目按时交付。

三、应用场景

Business Central 适用于各种类型的中小型企业，特别是那些希望实现数字化转型、提高业务效率和竞争力的企业。具体应用场景包括但不限于：

• 制造业：帮助制造企业实现生产、采购、销售等环节的全面协同，提高生产效率。
• 批发和零售业：帮助批发和零售企业优化库存管理，提高销售效率。
• 服务业：帮助服务企业提升客户满意度，优化服务流程。
• 专业服务业：如会计师事务所、律师事务所等，帮助企业实现项目管理和客户关系管理的自动化。

四、优势

1. 成本效益：

   • Business Central 提供了全面的业务管理功能，降低了企业购买多个独立系统的成本。
   • 云端部署减少了企业的IT基础设施投资和维护成本。

2. 易用性：

   • Business Central 提供了直观的用户界面和操作流程，降低了员工的培训成本。
   • 提供了丰富的在线帮助和社区支持，方便用户解决使用过程中遇到的问题。

3. 安全性：

   • Business Central 采用了严格的数据加密和访问控制机制，确保企业数据的安全性。
   • 提供了定期的数据备份和恢复功能，防止数据丢失。

五、总结

Business Central 是一款功能全面、灵活可扩展、云端部署的业务管理软件解决方案。它帮助中小型企业实现数字化转型，提高业务效率和竞争力。通过一体化的设计、丰富的功能和灵活的部署方式，Business Central 满足了企业的个性化管理需求，为企业的持续发展提供了有力支持。
11. Business Central (General)
11.1. Installation
11.1.1. War installation

Use the war from the Business Central distribution zip that corresponds to your application server. The differences between these war files are mainly superficial. For example, some JARs might be excluded if the application server already supplies them.

eap7: tailored for Red Hat JBoss Enterprise Application Platform 7

wildfly14: tailored for Wildfly 14

11.1.2. Business Central data

Business Central stores its data, by default in the directory $WORKING_DIRECTORY/.niogit, for example wildfly-14.0.1.Final/bin/.niogit, but it can be overridden with the system property-Dorg.uberfire.nio.git.dir.

In production, make sure to back up the Business Central data directory.
11.1.3. System properties

Here’s a list of all system properties:

org.kie.workbench.profile: Selects the Business Central profile. Possible values are FULL or PLANNER_AND_RULES. A prefix FULL_ will set the profile and hide the profile preferences from the admin preferences. Default: FULL.

kie.maven.offline.force: Forces Maven to behave as offline. If true, disable online dependency resolution. Default: false.
	

Use this property for Business Central only. If you share a runtime environment with any other component, isolate the configuration and apply it only to Business Central.

org.appformer.m2repo.url: Location of the default Maven repository Business Central uses when looking for dependencies. Usually this points to the Maven repository inside the Workbench for example http://localhost:8080/business-central/maven2. Please set this before starting up the Workbench. Default: File path to the inner m2 repository.

org.uberfire.nio.git.dir: Location of the directory .niogit. Default: working directory

org.uberfire.nio.git.dirname: Name of the git directory. Default: .niogit

org.uberfire.nio.git.proxy.ssh.over.http: Defines that SSH should use an HTTP Proxy. Default: false

http.proxyHost: Defines the host name of the HTTP Proxy. Default: null

http.proxyPort: Defines the host port (integer value) of the HTTP Proxy. Default: null

org.uberfire.nio.git.proxy.ssh.over.https: Defines that SSH should use an HTTPS Proxy. Default: false

https.proxyHost: Defines the host name of the HTTPS Proxy. Default: null

https.proxyPort: Defines the host port (integer value) of the HTTPS Proxy. Default: null

org.uberfire.nio.git.http.enabled: Enables or disables the HTTP daemon. Default: true

org.uberfire.nio.git.http.host: If the HTTP daemon is enabled, it uses this property as the host identifier. This is an informative property that is used to display how to access the Git repository over HTTP. The HTTP still relies on the servlet container. Default: localhost

org.uberfire.nio.git.http.hostname: If the HTTP daemon is enabled, it uses this property as the host name identifier. This is an informative property that is used to display how to access the Git repository over HTTP. The HTTP still relies on the servlet container. Default: localhost

org.uberfire.nio.git.http.port: If the HTTP daemon is enabled, it uses this property as the port number. This is an informative property that is used to display how to access the Git repository over HTTP. The HTTP still relies on the servlet container. Default: 8080

org.uberfire.nio.git.https.enabled: Enables or disables the HTTPS daemon. Default: false

org.uberfire.nio.git.https.host: If the HTTPS daemon is enabled, it uses this property as the host identifier. This is an informative property that is used to display how to access the Git repository over HTTPS. The HTTPS still relies on the servlet container. Default: localhost

org.uberfire.nio.git.https.hostname: If the HTTPS daemon is enabled, it uses this property as the host name identifier. This is an informative property that is used to display how to access the Git repository over HTTPS. The HTTPS still relies on the servlet container. Default: localhost

org.uberfire.nio.git.https.port: If the HTTPS daemon is enabled, it uses this property as the port number. This is an informative property that is used to display how to access the Git repository over HTTPS. The HTTPS still relies on the servlet container. Default: 8080

org.uberfire.nio.git.daemon.enabled: Enables/disables git daemon. Default: true

org.uberfire.nio.git.daemon.host: If git daemon enabled, uses this property as local host identifier. Default: localhost

org.uberfire.nio.git.daemon.hostname: If the git daemon is enabled, uses this property as the local host name identifier. Default: localhost

org.uberfire.nio.git.daemon.port: If git daemon enabled, uses this property as port number. Default: 9418

org.uberfire.nio.git.http.sslVerify: Enables or disables SSL certificate checking for Git repositories. Default: true
	

If the default or assigned port is already in use, a new port is automatically selected. Ensure that the ports are available and check the log for more information.

org.uberfire.nio.git.ssh.enabled: Enables/disables ssh daemon. Default: true

org.uberfire.nio.git.ssh.host: If ssh daemon enabled, uses this property as local host identifier. Default: localhost

org.uberfire.nio.git.ssh.hostname: If the SSH daemon is enabled, uses this property as local host name identifier. Default: localhost

org.uberfire.nio.git.ssh.port: If ssh daemon enabled, uses this property as port number. Default: 8001

org.uberfire.nio.git.ssh.ciphers: A comma-separated string of ciphers. The available ciphers are aes128-ctr, aes192-ctr, aes256-ctr, arcfour128, arcfour256, aes192-cbc, aes256-cbc. If the property is not used, all available ciphers are loaded.

org.uberfire.nio.git.ssh.macs: A comma-separated string of message authentication codes (MACs). The available MACs are hmac-md5, hmac-md5-96, hmac-sha1, hmac-sha1-96, hmac-sha2-256, hmac-sha2-512. If the property is not used, all available MACs are loaded.
	

If the default or assigned port is already in use, a new port is automatically selected. Ensure that the ports are available and check the log for more information.

org.uberfire.nio.git.ssh.cert.dir: Location of the directory .security where local certificates will be stored. Default: working directory

org.uberfire.nio.git.ssh.passphrase: Passphrase to access your Operating Systems public keystore when cloning git repositories with scp style URLs; e.g. git@github.com:user/repository.git.

org.uberfire.nio.git.ssh.algorithm: Algorithm used by SSH. Default: DSA
	

If you plan to use RSA or any algorithm other than DSA, make sure you setup properly your Application Server to use Bouncy Castle JCE library.

appformer.ssh.keystore: Defines the custom SSH keystore to be used with Business Central by specifying a class name. If the property is not available the default SSH keystore is used.

appformer.ssh.keys.storage.folder: When using the default SSH keystore, this parameter defines the storage folder for the user’s SSH public keys. If the property is not available the keys are stored in the Workbench .security folder.

org.uberfire.metadata.index.dir: Place where Lucene .index folder will be stored. Default: working directory

org.uberfire.ldap.regex.role_mapper: Regex pattern used to map LDAP principal names to application role name. Note that the variable role must be part of the pattern as it is substited by the application role name when matching a principal value to role name. Default: Not used.

org.uberfire.sys.repo.monitor.disabled: Disable configuration monitor (do not disable unless you know what you’re doing). Default: false

org.uberfire.secure.key: Secret password used by password encryption. Default: org.uberfire.admin

org.uberfire.secure.alg: Crypto algorithm used by password encryption. Default: PBEWithMD5AndDES

org.uberfire.domain: security-domain name used by uberfire. Default: ApplicationRealm

appformer.experimental.features: enables the Experimental Features Framework

org.guvnor.m2repo.dir: Place where Maven repository folder will be stored. Default: working-directory/repositories/kie

org.guvnor.project.gav.check.disabled: Disable GAV checks. Default: false

org.kie.demo: Enables external clone of a demo application from GitHub.

org.kie.build.disable-project-explorer: Disable automatic build of selected Project in Project Explorer. Default: false

org.kie.verification.disable-dtable-realtime-verification: Disables the realtime validation and verification of decision tables. Default: false

org.kie.workbench.controller: URL for connecting with a jBPM controller, for example: ws://localhost:8080/kie-server-controller/websocket/controller.

org.uberfire.gzip.enable: Enables or disables Gzip compression on GzipFilter. Default: true

Only Web Socket protocol is supported for connecting with a headless jBPM controller. When specifying this property, Business Central will automatically disable all the features related to running the embedded jBPM controller.

org.kie.workbench.controller.user: User name for connecting with a jBPM controller. Default: kieserver

org.kie.workbench.controller.pwd: Password for connecting with a jBPM controller. Default: kieserver1!

org.kie.workbench.controller.token: Token string for connecting with a jBPM controller.

Please refer to Using token based authentication for more details about how to use token based authentication.

kie.keystore.keyStoreURL: URL to a keystore which should be used for connecting with a headless jBPM controller.

kie.keystore.keyStorePwd: Password to a keystore.

kie.keystore.key.ctrl.alias: Alias of the key where password is stored.

kie.keystore.key.ctrl.pwd: Password of an alias with stored password.

Please refer to Securing password using key store for more details about how to use a key store for securing your passwords.

org.jbpm.wb.forms.renderer.ext: Switch form rendering between Business Central and Kie Server rendered forms. By default, form rendering is done by Business Central. Default: false.

org.jbpm.wb.forms.renderer.name: Allows to switch between Business Central or Kie Server rendered forms. Kie server includes two renderers, bootstrap and patternfly in addition to the default renderer, workbench. Default: workbench.

To change one of these system properties in a WildFly or JBoss EAP cluster:

Edit the file $JBOSS_HOME/domain/configuration/host.xml.

Locate the XML elements server that belong to the main-server-group and add a system property, for example:

<system-properties>
  <property name="org.uberfire.nio.git.dir" value="..." boot-time="false"/>
  ...
</system-properties>