Red Hat Summit 红帽全球峰会支持控制台（Console）开发人员开始试用联系人

此内容没有您所选择的语言版本。

Chapter 3. Installation options

Red Hat JBoss BPM Suite comes in two versions:
  • Executable jar installer for installation on Red Hat JBoss Enterprise Application Platform (EAP) 6.1.1.
  • Zip file install which itself comes in two versions:
    • jboss-bpms-6.MINOR_VERSION-redhat-x-deployable-eap6.x.zip: version adapted for deployment on Red Hat JBoss Enterprise Application Platform (EAP 6.1.1).
    • jboss-bpms-6.MINOR_VERSION-redhat-x-deployable-generic.zip: the deployable version with additional libraries adapted for deployment on Red Hat JBoss Web Server (WS), Apache Tomcat 6, and Apache Tomcat 7.
Depending on your environment, you may choose the installation option best suited for your project needs.

Note

Red Hat JBoss BPM Suite is designed to work with UTF-8 encoding. If a different encoding system is used by the underlying JVM, unexpected errors might occur. To ensure UTF-8 is used by the JVM, use the following system property "-Dfile.encoding=UTF-8".
Report a bug

3.1. The EAP6 bundle installation
复制链接

This section describes installing the Red Hat JBoss BPM Suite package deployable for Red Hat JBoss Enterprise Application Platform (EAP).

Note

The minimum supported configuration of Red Hat JBoss EAP for Red Hat JBoss BPM Suite installation is 6.1.1 and not 6.1.0.
Report a bug

3.1.1. Downloading the EAP6 package
复制链接

To download the deployable Red Hat JBoss BPM Suite package for JBoss Enterprise Application Platform, do the following:
  1. Go to the Red Hat Customer Portal and log in.
  2. Click Downloads Products Downloads.
  3. In the Product Downloads page that opens, click Red Hat JBoss BPM Suite.
  4. From the Version drop-down menu, select version 6.0.3.
  5. On the Software Downloads page that opens, navigate to the Red Hat JBoss BPM Suite 6.0.3 Deployable for EAP 6.1.1 row and click Download.
Report a bug

3.1.2. Installing the EAP6 package
复制链接

Installation on a fresh EAP instance

To install the deployable package for an EAP that has yet to be configured, do the following:
  1. Extract the zip package deployable for EAP you downloaded from the Red Hat Customer Portal.
  2. Merge the extracted zip package deployable for EAP into the EAP SERVER_HOME directory.

    Warning

    This step must be performed by the same user account that was used to install EAP. This account must not be a superuser account.
  3. In this process, multiple files in the EAP SERVER_HOME directory will be overwritten and you must let the unzip process overwrite these files. An example of a file that is overwritten is the SERVER_HOME/bin/product.conf file. After a successful merge, this file must contain the string slot=bpms. You can open this file to verify that the files have been overwritten successfully.
In Red Hat Enterprise Linux, you can use the following command to extract the BPMS zip file and merge it into your server directory correctly in one step, if you execute this command in the directory where you have downloaded the zip file: 
unzip -u jboss-bpms-VERSION-TYPE.zip -d SERVER_HOME_PARENT_DIR
Copy to Clipboard Toggle word wrap

Example 3.1. The unzip command

unzip -u jboss-bpms-6.0.3-redhat-7-deployable-eap6.x.zip -d /home/john/myServers/
Copy to Clipboard Toggle word wrap
On server start-up, Red Hat JBoss BPM Suite will be deployed.

Installation on an existing EAP configuration

Warning

These instructions are for installing, and NOT for updating an existing BPMS instance. Make sure that there is no existing BPMS install in the target EAP.
To install the deployable package for a previously configured EAP, do the following:
  1. Extract the zip package deployable for EAP you downloaded from the Red Hat Customer Portal.
  2. Unzip the downloaded zip archive; however, do not overwrite all of the files. Manually merge the following files into the SERVER_HOME directory.
    • jboss-eap-6.1/domain/configuration/* - (please be aware that BPMS requires JMS, so JMS is added by default into all profiles in domain.xml provided by BPMS distribution.)
    • jboss-eap-6.1/standalone/configuration/* - (please be aware that BPMS requires JMS, so JMS is added by default into all profiles config files (especially into standalone.xml and standalone-ha.xml) provided by BPMS distribution.)
    • jboss-eap-6.1/modules/layers.conf
    • jboss-eap-6.1/bin/product.conf
  3. Ensure the target EAP does not include a deployment with a colliding name. Copy the folder jboss-eap-6.1/standalone/deployments into the EAP_HOME directory from the BPMS distribution.
  4. Make sure no EAP module layer is already called BPMS and copy the folder jboss-eap-6.1/modules/system/layers/bpms into the EAP 6.1.1 folder.
Report a bug

3.1.3. Defining Roles
复制链接

Before starting the server and logging onto Business Central, you will need to create some user accounts. This section describes the different user roles that are used in Red Hat JBoss BPM Suite :
  • admin: The users with admin role are the administrators of the application. Administrators can manage users, manage the repositories (create and clone) and have full access to make the required changes in the application. Admins have access to all areas within the system.
  • developer: A developer has access to almost all features and can manage rules, models, process flows, forms and dashboards. They can manage the asset repository, they can create, build and deploy projects and they can even use Red Hat JBoss Developer Studio to view processes. Only certain administrative functions like creating and cloning a new repository are hidden for the developer role.
  • analyst: An analyst role has access to all high-level features to model and execute their projects. However, Authoring Administration access is unavailable to users with the analyst role. Certain lower-level features targeted towards developers, like the Deployment Artifact Repository view are not accessible for this role. However, the Build & Deploy button is available for the analyst role while using the Project Editor.
  • user: User or a business user work on the business task lists that are used to operate a certain process. A user with this role can access the dashboard and manage processes.
  • manager: A manager is a viewer of the system and is interested in statistics around the business processes and their performance, business indicators, and other reporting of the system. A user with this role has access to the BAM only.

Note

Enter the above mentioned roles during the user creation process.
Report a bug

3.1.4. Creating users
复制链接

To start adding new users, you will need to run the add-user.sh script on a Unix system or the add-user.bat file on a Windows system from the EAP bin directory.
  1. Run ./add-user.sh on a Unix system or add-user.bat on a Windows system from the bin directory.
  2. Enter b to select an Application User at the type of user prompt and press Enter.
  3. Accept the default Realm (ApplicationRealm): by pressing Enter.
  4. At the username prompt, enter a user name and confirm. For example: helloworlduser.
  5. Create the user's password at the password prompt and reenter the password. For example: Helloworld@123.

    Note

    The password should be at least 8 characters in length and should contain upper and lower case alphabetic characters (e.g. A-Z, a-z), at least one numerical character (e.g. 0-9) and at least one special character (e.g. ~ ! @ # $ % ^ * ( ) - _ + =).
  6. Enter a comma separate list of roles the user will need at the roles prompt (refer to Section 3.1.3, “Defining Roles”).
    Business Central users need to have at least the analyst role, and dashbuilder users need to have the admin role. Roles should be entered as a comma-separated list.
  7. Confirm you want to add the user.
  8. Enter yes at the next prompt (this is to enable clustering in the future if required).
Report a bug
返回顶部
Red Hat logoGithubredditYoutubeTwitter

学习

尝试、购买和销售

社区

关于红帽文档

通过我们的产品和服务，以及可以信赖的内容，帮助红帽用户创新并实现他们的目标。 了解我们当前的更新.

让开源更具包容性

红帽致力于替换我们的代码、文档和 Web 属性中存在问题的语言。欲了解更多详情，请参阅红帽博客.

關於紅帽

我们提供强化的解决方案，使企业能够更轻松地跨平台和环境（从核心数据中心到网络边缘）工作。

Theme

© 2025 Red Hat