Red Hat JBoss BPM Suite 6.0 Installation Guide

Red Hat JBoss BPM Suite 6.0 Installation Guide
Red Hat JBoss BPM Suite 6.0
Installation Guide
For Red Hat JBoss Administrators
Red Hat Content Services
Red Hat JBoss BPM Suite 6.0 Installation Guide
For Red Hat JBoss Administrators
Red Hat Co ntent Services
Legal Notice
Co pyright © 20 15 Red Hat, Inc.
This do cument is licensed by Red Hat under the Creative Co mmo ns Attributio n-ShareAlike 3.0
Unpo rted License. If yo u distribute this do cument, o r a mo dified versio n o f it, yo u must pro vide
attributio n to Red Hat, Inc. and pro vide a link to the o riginal. If the do cument is mo dified, all Red
Hat trademarks must be remo ved.
Red Hat, as the licenso r o f this do cument, waives the right to enfo rce, and agrees no t to assert,
Sectio n 4 d o f CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shado wman lo go , JBo ss, MetaMatrix, Fedo ra, the Infinity
Lo go , and RHCE are trademarks o f Red Hat, Inc., registered in the United States and o ther
co untries.
Linux ® is the registered trademark o f Linus To rvalds in the United States and o ther co untries.
Java ® is a registered trademark o f Oracle and/o r its affiliates.
XFS ® is a trademark o f Silico n Graphics Internatio nal Co rp. o r its subsidiaries in the United
States and/o r o ther co untries.
MySQL ® is a registered trademark o f MySQL AB in the United States, the Euro pean Unio n and
o ther co untries.
No de.js ® is an o fficial trademark o f Jo yent. Red Hat So ftware Co llectio ns is no t fo rmally
related to o r endo rsed by the o fficial Jo yent No de.js o pen so urce o r co mmercial pro ject.
The OpenStack ® Wo rd Mark and OpenStack Lo go are either registered trademarks/service
marks o r trademarks/service marks o f the OpenStack Fo undatio n, in the United States and o ther
co untries and are used with the OpenStack Fo undatio n's permissio n. We are no t affiliated with,
endo rsed o r spo nso red by the OpenStack Fo undatio n, o r the OpenStack co mmunity.
All o ther trademarks are the pro perty o f their respective o wners.
Abstract
This guide pro vides the steps necessary fo r administrato rs to install Red Hat JBo ss Enterprise
BPM Suite Platfo rm, the plug-ins fo r Red Hat JBo ss Develo per Studio , and pro vides instructio ns
fo r running example pro jects.
T able of Cont ent s
T able of Contents
. .hapt
⁠C
. . . .er
. .1. .. Int
. . .roduct
. . . . . .ion
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2. . . . . . . . . .
⁠1.1. Ab o ut Red Hat JBo s s BPM Suite
2
⁠1.2. Sup p o rted p latfo rms
2
⁠1.3. Us e Cas e: Pro c es s ​-b as ed s o lutio ns in the lo an ind us try
2
. .art
⁠P
. . .I.. Red
. . . . Hat
. . . .JBoss
. . . . . .Ent
. . .erprise
. . . . . . BPM
. . . . .Suit
...e
. .inst
. . . allat
. . . . ion
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4. . . . . . . . . .
. .hapt
⁠C
. . . .er
. .2. .. Inst
. . . .allat
. . . ion
. . . .opt
. . .ions
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5. . . . . . . . . .
⁠2 .1. The Red Hat JBo s s BPM Suite Ins taller ins tallatio n
5
⁠2 .2. The EAP6 b und le ins tallatio n
15
⁠2 .3. The g eneric d ep lo yab le b und le ins tallatio n
19
. .hapt
⁠C
. . . .er
. .3.
. .Special
. . . . . . .set
. . .ups
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2. 9. . . . . . . . . .
⁠3 .1. Setting up Pers is tenc e fo r Bus ines s Central
29
⁠3 .2. Setting up Pers is tenc e fo r Das hb uild er
⁠3 .3. Sp ec ial s etup fo r IBM DB2 d atab as e
30
30
. .hapt
⁠C
. . . .er
. .4. .. Roles
. . . . . .and
. . . Users
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
...........
⁠4 .1. Defining Ro les
32
⁠4 .2. Creating us ers
32
. .hapt
⁠C
. . . .er
. .5.
. .T. est
. . . ing
. . . t. he
. . .inst
. . . allat
. . . . ion
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
...........
⁠5 .1. Starting the s erver
34
⁠5 .2. Java Sec urity Manag er and p erfo rmanc e manag ement
35
⁠5 .3. Lo g g ing o n to Bus ines s Central
35
. .hapt
⁠C
. . . .er
. .6. .. Clust
. . . . .ering
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
...........
⁠ G IT rep o s ito ry c lus tering mec hanis m
36
⁠ Clus tering Maven Rep o s ito ries
37
⁠6 .1. Setting up a c lus ter
38
⁠6 .2. Setting up Q uartz
39
⁠6 .3. Co nfig uring c lus tering o n Red Hat JBo s s EAP
41
. .hapt
⁠C
. . . .er
. .7. .. Maven
. . . . . . Reposit
. . . . . . . ories
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4. 5. . . . . . . . . .
⁠7 .1. Ab o ut Maven
45
⁠7 .2. Ab o ut The Pro vid ed Maven Rep o s ito ries
45
⁠7 .3. Co nfig uring Maven to Us e the File Sys tem Rep o s ito ries
45
⁠7 .4. Co nfig uring Maven to Us e the O nline Rep o s ito ries
50
⁠7 .5. Dep end enc y Manag ement
54
. .hapt
⁠C
. . . .er
. .8. .. Red
. . . . Hat
. . . .JBoss
. . . . . .Developer
. . . . . . . . .St
. .udio
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
...........
⁠8 .1. Red Hat JBo s s Develo p er Stud io
56
⁠8 .2. Ins talling the JBo s s Develo p er Stud io Plug -ins
56
⁠8 .3. Setting the Dro o ls runtime
56
⁠8 .4. Co nfig uring the JBo s s BPM Suite Server
57
⁠8 .5. Imp o rting Pro jec ts fro m a G it Rep o s ito ry into JBo s s Develo p er Stud io
57
. . . . . . . . .Hist
Revision
. . . ory
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6. 2. . . . . . . . . .
1
Red Hat JBoss BPM Suit e 6 .0 Inst allat ion G uide
Chapter 1. Introduction
1.1. About Red Hat JBoss BPM Suit e
Red Hat JBoss BPM Suite is an open source business process management suite that combines
Business Process Management and Business Rules Management and enables business and IT
users to create, manage, validate, and deploy Business Processes and Rules.
Red Hat JBoss BRMS and Red Hat JBoss BPM Suite use a centralized repository where all resources
are stored. This ensures consistency, transparency, and the ability to audit across the business.
Business users can modify business logic and business processes without requiring assistance
from IT personnel.
To accommodate Business Rules component, Red Hat JBoss BPM Suite includes integrated Red Hat
JBoss BRMS.
Business Resource Planner is included as a technical preview with this release.
Report a bug
1.2. Support ed plat forms
Red Hat JBoss BPM Suite and Red Hat JBoss BRMS are supported on the following containers:
Red Hat JBoss Enterprise Application Platform 6.1.1
Red Hat JBoss Web Server 2.0 (Tomcat 7)
IBM WebSphere Application Server 8
Report a bug
1.3. Use Case: Process​- based solut ions in t he loan indust ry
Red Hat JBoss BPM Suite (BPMS) can be deployed to automate business processes, such as
automating the loan approval process at a retail bank. This is a typical 'Specific Process-Based'
deployment that might be the first step in a wider adoption of BPM throughout an enterprise. It
leverages both the BPM and business rules features of BPMS.
A retail bank offers several types of loan products each with varying terms and eligibility
requirements. Customers requiring a loan must file a loan application with the bank, which then
processes the application in several steps, verifying eligibility, determining terms, checking for
fraudulent activity, and determining the most appropriate loan product. Once approved, the bank
creates and funds a loan account for the applicant, who can then access funds. The bank must be
sure to comply with all relevant banking regulations at each step of the process, and needs to
manage its loan portfolio to maximize profitability. Policies are in place to aid in decision making at
each step, and those policies are actively managed to optimize outcomes for the bank.
Business analysts at the bank model the loan application processes using the BPMN2 authoring
tools (Process D esigner) in BPM Suite:
2
⁠Chapt er 1 . Int roduct ion
Fig u re 1.1. H ig h - level lo an ap p licat io n p ro cess f lo w
Business rules are developed with the rule authoring tools in BPM Suite to enforce policies and make
decisions. Rules are linked with the process models to enforce the correct policies at each process
step.
The bank's IT organization deploys the BPM Suite so that the entire loan application process can be
automated.
Fig u re 1.2. Lo an Ap p licat io n Pro cess Au t o mat io n
The entire loan process and rules can be modified at any time by the bank's business analysts. The
bank is able to maintain constant compliance with changing regulations, and is able to quickly
introduce new loan products and improve loan policies in order to compete effectively and drive
profitability.
Report a bug
3
Red Hat JBoss BPM Suit e 6 .0 Inst allat ion G uide
⁠Part I. Red Hat JBoss Enterprise BPM Suite installation
4
⁠Chapt er 2 . Inst allat ion opt ions
Chapter 2. 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.
Z ip file install which itself comes in two versions:
jbo ss-bpms-6 . MINOR_VERSION-red hat-x-d epl o yabl e-eap6 . x. zi p: version
adapted for deployment on Red Hat JBoss Enterprise Application Platform (EAP 6.1.1).
jbo ss-bpms-6 . MINOR_VERSION-red hat-x-d epl o yabl e-g eneri c. zi p: the
deployable version with additional libraries adapted for deployment on Red Hat JBoss Web
Server (WS), Apache Tomcat 6, and Apache Tomcat 7.
D epending 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 "-D fi l e. enco d i ng = UT F-8".
Report a bug
2.1. T he Red Hat JBoss BPM Suit e Inst aller inst allat ion
This section describes the steps required to install Red Hat JBoss BPM Suite using the jar file
installer installation method. The jar file is an executable file that installs EAP6 if you do not already
have it, or you can use it to install BPMS on an existing EAP6 installation.
Installation on IBM JDK
D ue to IBM JD K not being able to use keystores generated on other JD Ks, it is not possible to
install JBoss BPM Suite into an existing JBoss EAP running on IBM JD K with a keystore
generated on another JD K.
Report a bug
2.1.1. Downloading Red Hat JBoss BPM Suit e Inst aller
1. Go to the Red Hat Customer Portal and log in.
2. Click D o wn lo ad s → Pro d u ct s D o wn lo ad s.
3. In the P ro d uct D o wnl o ad s page that opens, click R ed Hat JBo ss BP M Sui te.
4. From the Versi o n drop-down menu, select version 6.0.3.
5
Red Hat JBoss BPM Suit e 6 .0 Inst allat ion G uide
5. Select R ed Hat JBo ss BP M Sui te 6 . 0 . 3 Instal l er fo r EAP 6 . 1. 1 and then
click D o wnl o ad .
Report a bug
2.1.2. Inst alling Red Hat JBoss BPM Suit e using t he Inst aller
The installer for Red Hat JBoss BPM Suite is an executable Java jar file. You can use it to install
BPMS on an existing EAP 6.1.1 installation or a brand new one. The installer gives you the option to
install EAP 6.1.1 if you do not already have it.
Note
For security reasons, you should run the installer as a no n-ro o t user.
1. ⁠ Se t up Lo cat io n and Use rs
Navigate to the folder where you downloaded the installer file in a command prompt and
execute the following command (replace the VERSION number and x with the actual file
name).
java -jar jbo ss-bpms-i nstal l er-VER SIO N. G A-red hat-x. jar
Note
When running the installer on Windows, you may be prompted to provide administrator
credentials during the installation. To prevent this, add the
i zpack. mo d e= pri vi l eg ed option to the installation command: java D i zpack. mo d e= pri vi l eg ed -jar jbo ss-bpms-i nstal l er-VER SIO N. G Ared hat-x. jar
2. The graphical installer will execute and display a splash screen and a license agreement
page. Accept the license to proceed.
3. In the next screen, provide the parent location of an existing EAP where BPMS needs to be
installed. If you instead prefer to install BPMS in a brand new EAP, then point this location to
a parent directory where there is no existing EAP. BPMS will then be installed on top of a
fresh EAP server bundled with the installer. The screenshot below depicts an example
directory path:
6
⁠Chapt er 2 . Inst allat ion opt ions
Fig u re 2.1. B PM Su it e In st aller D irect o ry Pat h
4. In the next two screens, create two users: the first one for the management console of the EAP
(ManagementRealm) and the second one for managing BPMS itself (ApplicationRealm).
Make a note of these usernames and passwords as you will need them to access the EAP
server and the BPMS application respectively.
Note
The passwords that you create must have at least 8 characters and must contain
atleast one number and one alphanumeric character.
D epicted below is a screenshot of the username and password page:
7
Red Hat JBoss BPM Suit e 6 .0 Inst allat ion G uide
Fig u re 2.2. B PM Su it e In st aller U sern ame an d Passwo rd Screen
Note
The application role assigned to the second user that you create is the admin role.
This is the only role that can be assigned to this newly created user. You can create
more users with narrow roles afterwards by using the command line.
5. ⁠ Se t up Se curit y Enviro nm e nt
Next, you will setup the security environment of your new BPMS install. D ecide to enable or
disable the Java Security Manager in this step by clicking on the checkbox. The Java
Security Manager makes your system more secure but may downgrade performance. You
need to make a decision based on your environment.
6. Next, configure the passwords for the SSL Keystores for both server and client side for JMS
messages. This is to make sure that the messages sent to BPMS via JMS can be encrypted as
it may contain sensitive information.
8
⁠Chapt er 2 . Inst allat ion opt ions
7. ⁠ Final Co nfigurat io n St e ps
Choose whether you want to setup pure IPv6 configuration on the server that the installation
is taking place. This will allow you to setup runtime IPv6 specific configurations later.
8. Choose default configuration for the runtime environment in the next step and click next to
review the installation details. If you are happy with the details, click next to start the actual
installation or click previous to go back and make changes.
9. The installer will go through the steps to install BPMS and will perform post installation
configuration steps when you click next. The installer will also start the BPMS server and
connect to it to validate the installation. Click next to get to the last screen where you can
generate the installation script and properties file. Click done to quit the installer.
You have successfully installed Red Hat JBoss BPM Suite using the installer.
Report a bug
2.1.3. Inst alling Red Hat JBoss BPM Suit e using t he Inst aller in CLI Mode
The installer for Red Hat JBoss BPMS can also be executed through the command-line interface
(CLI). The procedure below demonstrates the steps that you are likely to encounter using this option
to install BPMS.
1. Navigate to the folder where you downloaded the installer file in a command prompt and
execute the following command (replace the VERSION number and x with the actual file
name).
java -jar jboss-bpms-installer-VERSION.GA-redhat-x.jar -console
9
Red Hat JBoss BPM Suit e 6 .0 Inst allat ion G uide
2. The command-line interactive process will start and display the End-User license agreement.
You will be prompted to select an option at the end of this license:
press 1 to continue, 2 to quit, 3 to redisplay.
3. Enter 1 to begin the installation and type in the parent directory of an existing EAP
installation. If you specify a directory where EAP does not exist, the installer will install a new
version of EAP for you.
If you wish to install on an existing EAP installation, the parent
directory of that EAP installation should be specified.
[/home/user]
If you decide to create a new folder for the installation to take place, you will be prompted to
select the following:
press 1 to continue, 2 to quit, 3 to redisplay.
4. Create a user for the management console of EAP (Management Realm):
Create an administrative user
This user will be added to the host container's management realm
for administrative purposes. It can be used to access the
management console, the management CLI or other applications
secured in this realm.
Admin username: [admin]
5. Create and confirm a password for the user of the EAP management console:
The password must have at least 8 characters, and contain at least
one number and one non-alphanumeric symbol.
Admin password: []
Confirm admin password: [******************************]
6. After the passwords have been entered, choose an option from the prompt below:
press 1 to continue, 2 to quit, 3 to redisplay.
7. Enter 1 then create a BPMS user:
Create a Business Process Management Suite User
Create a BPM Suite user. The user will be added to the
ApplicationRealm, and can be used to access the Business Central
Console. The User will be assigned the 'admin' application roles.
The BPMS username cannot be any of the following: 'admin',
10
⁠Chapt er 2 . Inst allat ion opt ions
'analyst', 'user', 'manager' or 'developer'.
BPMS username: [bpmsAdmin]
8. Create and confirm a password for the BPMS user:
The password must have at least 8 characters, and contain at least
one number and one non-alphanumeric symbol.
BPMS password: []
Confirm BPMS password: [****************]
9. After the passwords have been entered, choose an option from the prompt below:
press 1 to continue, 2 to quit, 3 to redisplay.
10. Configure the Java Security Manager by either pressing 1 to select it or 0 to deselect it.
Configure the Java Security Manager
A Java security manager offers JVM level security beyond what is
provided by the application container. It enforces access rules at
the JVM runtime based on one or more security policies.
This installer will place two security policies in the installation
directory with the filenames 'security.policy' and 'kie.policy'
regardless of choice. Those policies will be enabled at runtime if
the option below is selected.
Please note that a security manager imposes a significant
performance overhead when enabled. It is suggested the included
policies be applied in production if user requirements call for a
stronger measure than what is already provided by the application
container's authentication and authorization mechanism.
Please see the JBoss Business Process Management Suite
administrative documentation for further details and consideration.
[x] Enable the Java security manager
Input 1 to select, 0 to deselect:
11. After the Java Security Manager choice, choose an option from the prompt below:
press 1 to continue, 2 to quit, 3 to redisplay.
12. The Configure JMS SSL keystores will display on the CLI:
Configure JMS SSL keystores
Some JMS messages sent to BPMS can contain password information. In
order to make sure that this information is sent safely, SSL must be
used, which uses public/private key encryption to set up an
11
Red Hat JBoss BPM Suit e 6 .0 Inst allat ion G uide
encrypted connection between the client and the server.
Please supply the private passwords to use with BPMS. These
passwords should not be shared with others.
If multiple distinct clients are necessary, the number of distinct
client keystores can also be indicated. The server's keystore
certificate will automatically be imported into the client
keystores.
Passwords to use for the generated keystores. They must have at
least 6 characters.
13. Enter the server keystore password:
Server keystore password: []
Re-enter server keystore password: [**********]
14. Enter the client keystores password:
Client keystores password: [**********]
Re-enter client keystores password: [**********]
15. Enter the number of client keystores to generate:
Number of client keystores to generate: [1]
16. After the keystores configuration, choose an option from the prompt below:
press 1 to continue, 2 to quit, 3 to redisplay.
17. Next, select whether to enable the IPv6 configuration.
IPv6 configuration
If this computer is using a pure IPv6 configuration, please check
the box below. A pure IPv6 setup requires additional configuration
at runtime to ensure the proper bindings of the management and http
interfaces.
[ ] Enable pure IPv6 configuration
Input 1 to select, 0 to deselect:
18. After the IPv6 configuration choice, choose an option from the prompt below:
press 1 to continue, 2 to quit, 3 to redisplay.
12
⁠Chapt er 2 . Inst allat ion opt ions
19. Configure the runtime environment by either choosing the default configuration or inputting
advanced options.
Configure runtime environment
Red Hat JBoss Business Process Management Suite can be further
customized at this time.
0 [x] Perform default configuration
1 [ ] Perform advanced configuration
Input Selection:
If you select 1, " Perform advanced configuration," complete the following configurations:
[ ] Install password vault
Input 1 to select, 0 to deselect:
[ ] Enable SSL security
Input 1 to select, 0 to deselect:
[ ] Enable LDAP authentication
Input 1 to select, 0 to deselect:
[ ] Add a security-domain
Input 1 to select, 0 to deselect:
20. Next, choose an option from the prompt below:
press 1 to continue, 2 to quit, 3 to redisplay.
21. Configure the password vault by creating a password and pressing 1 to continue:
Configure password vault
A password vault encrypts sensitive strings and stores them in an
encrypted keystore. The vault mechanism manages decrypting the
strings for use with security domains, security realms, or other
verification systems.
Please make note of your entry below in order to mask any
subsequent passwords. See EAP 6 documentation for further details.
The password must have no fewer than 6 characters.
Vault keystore password: []
Re-enter vault keystore password: [**********]
press 1 to continue, 2 to quit, 3 to redisplay.
22. The .jar file will begin to upack and configure.
23. After a successful installation, the command-line will ask you if you would like to generate an
automatic installation script and properties file.
13
Red Hat JBoss BPM Suit e 6 .0 Inst allat ion G uide
Installation has completed successfully.
Application installed on /home/user/Documents/BPMS_Installer
Would you like to generate an automatic intallation script and
properties file?
(y/n) [n]:
24. If you select [ y ], provide a path for the automatic installation script:
Select path for the automatic installation script:
[/home/user/Documents/BPMS_Installer/<auto script filename>]
This generated script will allow the user to run the installer in the following way for future
installations:
java -jar jboss-bpms-installer.jar <auto script filename>
Note
Running the installer in this way will result in an installation identical to the installation
from which the auto script was generated. Note that sensitive values, such as
passwords, will need to be provided from an external file or provided at auto
installation time. The optional argument below allows the user to provide these values
automatically:
-variablefile <variable filename>
Sensitive values can also be provided using the following argument:
-variables key1=value1,key2=value2
25. The command-line will provide the following message upon a successful auto script creation
and/or console installation:
XML written successfully.
[ Console installation done ]
[BPMS_Installer]$
26. Start JBoss EAP by running stand al o ne. sh in the jbo ss-eap-[VER SIO N]/bi n
directory.
./standalone.sh
27. Navigate to http://localhost:8080/business-central in a web browser.
28. Login with the correct username/password as given to the BPMS user in the " Create and
confirm a password for the BPMS user" step.
Report a bug
14
⁠Chapt er 2 . Inst allat ion opt ions
2.2. T he EAP6 bundle inst allat ion
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
2.2.1. Downloading t he 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 D o wn lo ad s → Pro d u ct s D o wn lo ad s.
3. In the P ro d uct D o wnl o ad s page that opens, click R ed Hat JBo ss BP M Sui te.
4. From the Versi o n drop-down menu, select version 6.0.3.
5. On the So ftware D o wnl o ad s page that opens, navigate to the R ed Hat JBo ss BP M
Sui te 6 . 0 . 3 D epl o yabl e fo r EAP 6 . 1. 1 row and click D o wnl o ad .
Report a bug
2.2.2. Inst alling t he EAP6 package
Inst allat io n o n a fre sh EAP inst ance
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/bi n/pro d uct. co nf file. After a successful merge, this file must contain the
string sl o t= bpms. You can open this file to verify that the files have been overwritten
successfully.
15
Red Hat JBoss BPM Suit e 6 .0 Inst allat ion G uide
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
Examp le 2.1. T h e u n z ip co mman d
unzip -u jboss-bpms-6.0.3-redhat-7-deployable-eap6.x.zip -d
/home/john/myServers/
On server start-up, Red Hat JBoss BPM Suite will be deployed.
Inst allat io n o n an e xist ing EAP co nfigurat io n
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.
jbo ss-eap-6 . 1/d o mai n/co nfi g urati o n/* - (please be aware that BPMS requires
JMS, so JMS is added by default into all profiles in d o mai n. xml provided by BPMS
distribution.)
jbo ss-eap-6 . 1/stand al o ne/co nfi g urati o n/* - (please be aware that BPMS
requires JMS, so JMS is added by default into all profiles config files (especially into
stand al o ne. xml and stand al o ne-ha. xml ) provided by BPMS distribution.)
jbo ss-eap-6 . 1/mo d ul es/l ayers. co nf
jbo ss-eap-6 . 1/bi n/pro d uct. co nf
3. Ensure the target EAP does not include a deployment with a colliding name. Copy the folder
jbo ss-eap-6 . 1/stand al o ne/d epl o yments into the EAP_HOME directory from the
BPMS distribution.
4. Make sure no EAP module layer is already called BPMS and copy the folder jbo ss-eap6 . 1/mo d ul es/system/l ayers/bpms into the EAP 6.1.1 folder.
Report a bug
2.2.3. Inst alling BPM Suit e in t he Domain Mode
To install the deployable package for an EAP in the domain mode, do the following steps:
16
⁠Chapt er 2 . Inst allat ion opt ions
1. Extract the downloaded EAP D eployable Z IP file from Red Hat Customer Portal and copy the
following directories into your local installation of EAP 6.1:
bi n
d o mai n
mo d ul es
Skip the stand al o ne directory.
2. On the command line, move to the /d o mai n directory and start the domain:
In a Unix environment, run:
./domain.sh
In a Windows environment, run:
./domain.bat
3. D eploy the archive either via ${jbo ss-eap-ho me}/bi n/jbo ss-cl i . sh / ${jbo sseap-ho me}/bi n/jbo ss-cl i . bat, or via management web UI (localhost:9990/):
Note
The web applications business-central.war and dashbuilder.war supplied in the EAP
deployable binaries are directories, but for deployment into the domain, you have to
use WAR archives. To create them, simply zip the content of the business-central.war
and the dashbuilder.war directories.
a. To deploy the archive via ${jbo ss-eap-ho me}/bi n/jbo ss-cl i . sh or
${jbo ss-eap-ho me}/bi n/jbo ss-cl i . bat, move into the ${jbo ss-eapho me}/bi n d i recto ry and deploy the WAR file:
In a Unix environment, run:
./jboss-cli.sh
In a Windows environment, run:
./jboss-cli.bat
b. To deploy the archive via management web UI (localhost:9990/):
log in using your EAP management account
select D o mai n -> Manag e D epl o yments -> C o ntent R epo si to ry -> Ad d
select the web archive from the file system, upload the web archive
select the deployment, click the Assi g n button
select the server group
17
Red Hat JBoss BPM Suit e 6 .0 Inst allat ion G uide
Note
In order to log in to Business Central deployed on Host Controller (HC) machines, the user
created on the D omain Controller Machine has to be created on the Host Controller machines
as well, by following the steps in the Section 4.2, “ Creating users” section.
Inst alling Mult iple BPMS Se rve r Inst ance s
In many situations, users may want to group together a set of EAP 6 nodes on the same machine and
give them a meaningful name for easy maintenance. Unique values need to be incorporated for the
system properties for each server instance. Listed below are the common properties that can be
specified with a single BPMS node to change the default configuration; however, they should be
specified for multiple nodes running on a single machine so every node can point to a different
directory:
o rg . uberfi re. ni o . g i t. d i r
o rg . uberfi re. metad ata. i nd ex. d i r
o rg . uberfi re. ni o . g i t. ssh. cert. d i r
When multiple BPMS nodes are used on a single machine, the below properties need to be specified:
o rg . uberfi re. ni o . g i t. d aemo n. ho st - can be left on default to bind to localhost.
o rg . uberfi re. ni o . g i t. d aemo n. po rt
o rg . uberfi re. ni o . g i t. ssh. ho st - can be left on default to bind to localhost.
o rg . uberfi re. ni o . g i t. ssh. po rt
Note
Both the o rg . uberfi re. ni o . g i t. d aemo n. po rt and the
o rg . uberfi re. ni o . g i t. ssh. po rt require different port values in order to avoid port
conflicts.
Incorporate the previous properties in the $EAP _HO ME/d o mai n/co nfi g urati o n/ho st. xml file
as illustrated in the two nodes below:
Node A:
<system-properties>
<property name="org.uberfire.nio.git.dir" value="/valid/path/.."
boot-time="false"/>
<property name="org.uberfire.metadata.index.dir"
value="/valid/path/.." boot-time="false"/>
<property name="org.uberfire.nio.git.ssh.cert.dir"
value="/valid/path/.." boot-time="false"/>
<property name="org.uberfire.nio.git.daemon.host" value="10.10.10.10"
boot-time="false"/>
<property name="org.uberfire.nio.git.daemon.port" value="9417" boot-
18
⁠Chapt er 2 . Inst allat ion opt ions
time="false"/>
<property name="org.uberfire.nio.git.ssh.host" value="10.10.10.10"
boot-time="false"/>
<property name="org.uberfire.nio.git.ssh.port" value="8002" boottime="false"/>
</system-properties>
Node B:
<system-properties>
<property name="org.uberfire.nio.git.dir" value="/valid/path/.."
boot-time="false"/>
<property name="org.uberfire.metadata.index.dir"
value="/valid/path/.." boot-time="false"/>
<property name="org.uberfire.nio.git.ssh.cert.dir"
value="/valid/path/.." boot-time="false"/>
<property name="org.uberfire.nio.git.daemon.host" value="10.10.10.10"
boot-time="false"/>
<property name="org.uberfire.nio.git.daemon.port" value="9418" boottime="false"/>
<property name="org.uberfire.nio.git.ssh.host" value="10.10.10.10"
boot-time="false"/>
<property name="org.uberfire.nio.git.ssh.port" value="8003" boottime="false"/>
</system-properties>
The system properties depicted above should indicate the host, port, or location of the . i nd ex or
. ni o g i t files. These files, which should be used by a respective node, would then be grouped in a
particular domain.
Report a bug
2.3. T he generic deployable bundle inst allat ion
To install Red Hat JBoss BPM Suite on Red Hat JBoss Web Server (WS) , you need to use the
generic deployable package of the product.
For installation on WS, the generic deployable package contains additional transaction manager
and security libraries that are not part of Red Hat JBoss WS.
Note that the generic deployable package contains the following zip archives:
jbo ss-bpms-eng i ne. zi p: supported execution engine libraries needed if you are embedding
the engine into your application
jbo ss-bpms-manag er. zi p: the busi ness-central . war and d ashbui l d er. war web
applications
Report a bug
2.3.1. Downloading t he generic deployable package
To download the generic deployable Red Hat JBoss BPM Suite package for JBoss Web Server, do
the following:
19
Red Hat JBoss BPM Suit e 6 .0 Inst allat ion G uide
1. Go to the Red Hat Customer Portal and log in.
2. Select D o wn lo ad s → Pro d u ct D o wn lo ad s.
3. From the list of products click on R ed Hat JBo ss BP M Sui te.
4. From the Versi o n drop-down menu, select version 6.0.3.
5. In the Software D ownloads section that comes up, navigate to the R ed Hat JBo ss BP M
Sui te 6 . 0 . 3 D epl o yabl e fo r al l suppo rted co ntai ners row and then click
D o wnl o ad .
Report a bug
2.3.2. Inst alling t he generic deployable package
To install the generic deployable package, you need to set up the following after you have installed
the underlying platform (Red Hat JBoss WS):
Set up the database driver and the transaction manager (Bitronix) (refer to Section 2.3.2.1,
“ Setting up transaction manager for Red Hat JBoss Web Server 2.0 (Tomcat 7)” ).
Set up the Business Central application: set up users and roles and set up persistence (refer to
Section 2.3.2.2, “ Setting up Business Central for Red Hat JBoss Web Server 2.0 (Tomcat 7)” ).
Set up the D ashbuilder application: set up users and roles and set up persistence (refer to
Section 2.3.2.3, “ Setting up D ashbuilder for Red Hat JBoss Web Server 2.0 (Tomcat 7)” ).
Report a bug
2 .3.2 .1 . Se t t ing up t ransact io n m anage r fo r Re d Hat JBo ss We b Se rve r 2 .0 (T o m cat
7)
1. Extract the generic deployable zip package you downloaded from Red Hat Customer Portal.
This zip package contains two more zip files: jbo ss-bpms-eng i ne. zi p and jbo ssbpms-manag er. zi p.
2. Extract the contents of the jbo ss-bpms-manag er. zi p file to a temporary location. This zip
file contains two web application archive folders: busi ness-central . war and
d ashbui l d er. war in exploded formats and these are now in your temporary location.
Rename these folders to remove the . war extension.
Copy both these folders directly under the $TOMCAT_DIR/webapps folder.
You should end up with two folders in exploded format:
$TOMCAT_DIR/webapps/busi ness-central and
$TOMCAT_DIR/webapps/d ashbui l d er.
Note
$TOMCAT_DIR stands for the home directory where your web server is located.
Replace it with the actual path to your web server home directory, for example:
/ho me/jo hn/jbo ss-ews-2. 0 /to mcat7/
20
⁠Chapt er 2 . Inst allat ion opt ions
3. Extract the jbo ss-bpms-eng i ne folder from the jbo ss-bpms-eng i ne. zi p archive to a
temporary location from where you can copy the required libraries. This folder now contains
all the core BPMS libraries under the extracted folder and a l i b folder.
4. ⁠ In st all t h e t ran sact io n man ag er.
Warning
Please note that the following section describes the setup of a transaction manager,
Bitronix that is not officially supported by Red Hat.
Copy the following transaction manager jar libraries from the l i b folder where you just
extracted the jbo ss-bpms-eng i ne libraries to $TOMCAT_DIR/l i b/ directory:
btm-VERSION.jar
btm-tomcat55-lifecycle-VERSION.jar
jta-VERSION.jar
slf4j-api-VERSION.jar
slf4j-ext-VERSION.jar
In addition, download the following library and copy it into the $TOMCAT_DIR/l i b/ folder
as well:
javax.security.jacc-api.jar
5. Install the driver to your database: copy the jar file with the relevant database driver to
$TOMCAT_DIR/l i b/.
Driver to the embedded H2 database
If using the embedded H2 database, the driver is available in busi nesscentral /WEB-INF/l i b/.
6. Create the transaction manager configuration files in $TOMCAT_DIR/co nf/:
btm-config.properties
bitronix.tm.serverId=tomcat-btm-node0
bitronix.tm.journal.disk.logPart1Filename=${btm.root}/work/btm1.t
log
bitronix.tm.journal.disk.logPart2Filename=${btm.root}/work/btm2.
tlog
bitronix.tm.resource.configuration=${btm.root}/conf/resources.pro
perties
resources.properties (the resource.ds1.uniqueName defines the datasource name used in
tomcat resource definition later - make a note of this value).
Make sure to change the values in the following definitions to match your environment.
21
Red Hat JBoss BPM Suit e 6 .0 Inst allat ion G uide
Examp le 2.2. H 2 d at aso u rce d ef in it io n
resource.ds1.className=bitronix.tm.resource.jdbc.lrc.LrcXADataS
ource
resource.ds1.uniqueName=jdbc/jbpm
resource.ds1.minPoolSize=10
resource.ds1.maxPoolSize=20
resource.ds1.driverProperties.driverClassName=org.h2.Driver
resource.ds1.driverProperties.url=jdbc:h2:file:~/jbpm
resource.ds1.driverProperties.user=sa
resource.ds1.driverProperties.password=
resource.ds1.allowLocalTransactions=true
Examp le 2.3. MySQ L 5.5 d at aso u rce d ef in it io n
resource.ds1.className=com.mysql.jdbc.jdbc2.optional.MysqlXADat
aSource
resource.ds1.uniqueName=jdbc/jbpm
resource.ds1.minPoolSize=0
resource.ds1.maxPoolSize=10
resource.ds1.driverProperties.URL=jdbc:mysql://localhost:3306/s
ampledb
resource.ds1.driverProperties.user=dbuser
resource.ds1.driverProperties.password=dbpassword
resource.ds1.allowLocalTransactions=true
Examp le 2.4 . D B 2 T yp e 4 d at aso u rce d ef in it io n
resource.ds1.className=com.ibm.db2.jcc.DB2Driver
resource.ds1.uniqueName=jdbc/jbpm
resource.ds1.minPoolSize=0
resource.ds1.maxPoolSize=10
resource.ds1.driverProperties.URL=jdbc:db2://localhost:50000/sa
mpledb
resource.ds1.driverProperties.user=dbuser
resource.ds1.driverProperties.password=dbpassword
resource.ds1.allowLocalTransactions=true
Examp le 2.5. O racle d at aso u rce d ef in it io n
resource.ds1.className=oracle.jdbc.xa.client.OracleXADataSource
resource.ds1.uniqueName=jdbc/jbpm
resource.ds1.minPoolSize=0
resource.ds1.maxPoolSize=10
resource.ds1.driverProperties.URL=jdbc:oracle:thin:@ //localhost
:1521/bpms
resource.ds1.driverProperties.user=dbuser
resource.ds1.driverProperties.password=dbpassword
resource.ds1.allowLocalTransactions=true
22
⁠Chapt er 2 . Inst allat ion opt ions
Examp le 2.6 . Micro so f t SQ L Server d at aso u rce d ef in it io n
resource.ds1.className=com.microsoft.sqlserver.jdbc.SQLServerDr
iver
resource.ds1.uniqueName=jdbc/jbpm
resource.ds1.minPoolSize=0
resource.ds1.maxPoolSize=10
resource.ds1.driverProperties.URL=jdbc:sqlserver://localhost:14
33;databaseName=bpms;
resource.ds1.driverProperties.user=dbuser
resource.ds1.driverProperties.password=dbpassword
resource.ds1.allowLocalTransactions=true
7. Set up the transaction manager listener in $TOMCAT_DIR/co nf/server. xml to start and
stop Bitronix on container startup and shutdown:
Add the following element as the last <Listener> element into the <Server> element:
<Listener
className="bitronix.tm.integration.tomcat55.BTMLifecycleListener"
/>
8. D efine the btm.root system property and location where bitronix config file is placed:
In $TOMCAT_DIR/bi n/, create the setenv. sh file with the following content:
CATALINA_OPTS="-Xmx512M -XX:MaxPermSize=512m Dbtm.root=$CATALINA_HOME Dbitronix.tm.configuration=$CATALINA_HOME/conf/btmconfig.properties -Dorg.jbpm.designer.perspective=RuleFlow Djbpm.tsr.jndi.lookup=java:comp/env/TransactionSynchronizationRegis
try"
The property o rg . jbpm. d esi g ner. perspecti ve is set to R ul eFl o w to allow the default
perspective for the designer to be R ul eFl o w rather than Ful l . Grant the file execute
permissions if applicable.
T omcat on Microsoft Windows systems
On Microsoft Windows systems, replace the $C AT ALINA_HO ME value in the content of
the file with the equivalent environment variable name or use the absolute path and
add the values in setenv. bat file as shown here in the following example:
set "CATALINA_OPTS=-Xmx512M -XX:MaxPermSize=512m Dbtm.root=C:/Tomcat Dbitronix.tm.configuration=C:/Tomcat/conf/btmconfig.properties -Dorg.jbpm.designer.perspective=RuleFlow"
Report a bug
2 .3.2 .2 . Se t t ing up Busine ss Ce nt ral fo r Re d Hat JBo ss We b Se rve r 2 .0 (T o m cat 7 )
23
Red Hat JBoss BPM Suit e 6 .0 Inst allat ion G uide
To set up Business Central, do the following:
1. Set up a Val ve so that the Business Central web application can load the users set up in
Tomcat:
a. D efine users and roles in $TOMCAT_DIR/co nf/to mcat-users. xml . Note that
Business Central requires users to have the roles specified as ad mi n and/or
anal yst (for more information about user and role definitions, refer to the Tomcat 7
documentation).
The program listing below shows an example of how these two roles would be added
and how a user named bpmsad mi n will be assigned these roles.
<role rolename="admin"/>
<role rolename="analyst" />
<user username="bpmsadmin" password="[email protected] ssw0rd"
roles="admin,analyst"/>
b. Copy ki e-to mcat-i nteg rati o n-VERSION. jar from
$TOMCAT_DIR/webapps/busi ness-central /WEB-INF/l i b/ to
$TOMCAT_DIR/l i b/.
c. Copy jaxb-api -VERSION. jar from $TOMCAT_DIR/webapps/busi nesscentral /WEB-INF/l i b/ to $TOMCAT_DIR/l i b/.
d. In $TOMCAT_DIR/co nf/server. xml , add the Tomcat Valve declaration in the
relevant <host> element:
<Valve className="org.kie.integration.tomcat.JACCValve" />
e. In $TOMCAT_DIR/webapps/busi ness-central /WEB-INF/web. xml , uncomment
entries marked with the T O MC AT -JEE-SEC UR IT Y comments.
f. Set up the tomcat authentication source: in the $TOMCAT_DIR/webapps/busi nesscentral /WEB-INF/cl asses/MET A-INF/servi ces/ directory, rename the
following files: o rg . uberfi re. securi ty. auth. Authenti cati o nSo urce to
o rg . uberfi re. securi ty. auth. Authenti cati o nSo urce-O R IG IN and
o rg . uberfi re. securi ty. auth. Authenti cati o nSo urce-T O MC AT -JEESEC UR IT Y to o rg . uberfi re. securi ty. auth. Authenti cati o nSo urce:
# Example command if you run this from $TOMCAT_DIR/webapps
directory
$ mv business-central/WEB-INF/classes/METAINF/services/org.uberfire.security.auth.AuthenticationSource
business-central/WEB-INF/classes/METAINF/services/org.uberfire.security.auth.AuthenticationSourceORIGIN
$ mv business-central/WEB-INF/classes/METAINF/services/org.uberfire.security.auth.AuthenticationSourceTOMCAT-JEE-SECURITY business-central/WEB-INF/classes/METAINF/services/org.uberfire.security.auth.AuthenticationSource
g. In $TOMCAT_DIR/webapps/busi ness-central /WEB-INF/beans. xml ,
uncomment JAASUserG ro upInfo P ro d ucer and comment
o rg . jbpm. ki e. servi ces. cd i . pro d ucer. D efaul tUserG ro upInfo P ro d uce
r (optional). The al ternati ves part of this file should now look like this:
24
⁠Chapt er 2 . Inst allat ion opt ions
<alternatives>
<!-<class>org.jbpm.kie.services.cdi.producer.DefaultUserGroupInfo
Producer</class> -->
<!-- uncomment JAASUserGroupInfoProducer when using JEE
security on Tomcat -->
<class>org.jbpm.kie.services.cdi.producer.JAASUserGroupInfoPro
ducer</class>
</alternatives>
2. If you are using a datasource other than the default provided by the underlying H2 database,
you will need to setup persistence. If you are using the default H2 database, then you can
ignore the rest of the steps in this procedure.
In this procedure, you configure a datasource with the JND I name jd bc/myD ataso urce as
defined in uniqueName=jdbc/jbpm in the bitronix reso urces. pro perti es file earlier (for the
MySQL option).
a. In busi ness-central /MET A-INF/co ntext. xml , replace the datasource JND I
name in the <Resource> element. The uniqueName attribute refers to the
resource.ds1.uniqueName property set in reso urces. pro perti es:
<Resource name="jdbc/myDatasource" uniqueName="jdbc/jbpm"
auth="Container" removeAbandoned="true"
factory="bitronix.tm.resource.ResourceObjectFactory"
type="javax.sql.DataSource"/>
b. In busi ness-central /WEB-INF/web. xml , replace the datasource JND I name in
the <res-ref-name> element with your datasource name:
<resource-ref>
<description>Console DS</description>
<res-ref-name>jdbc/myDatasource</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
c. Change busi ness-central /WEB-INF/cl asses/MET A-INF/persi stence. xml .
In this file, change the name of the hibernate dialect used for your database, if using a
different database other than H2. The code below demonstrates the original database
information for persi stence. xml :
<property name="hibernate.dialect"
value="org.hibernate.dialect.H2Dialect"/>
This information can be updated in the following manner (as demonstrated with
MySQL database below):
<property name="hibernate.dialect"
value="org.hibernate.dialect.MySQLDialect"/>
25
Red Hat JBoss BPM Suit e 6 .0 Inst allat ion G uide
Note
The dialect for D B2 is o rg . hi bernate. d i al ect. D B2D i al ect, for D B2 on
AS/400 is o rg . hi bernate. d i al ect. D B24 0 0 D i al ect, for Oracle is
o rg . hi bernate. d i al ect. O racl e10 g D i al ect and for Microsoft SQL
Server is o rg . hi bernate. d i al ect. SQ LServerD i al ect
d. Change busi ness-central /WEB-INF/cl asses/MET A-INF/persi stence. xml
file so that BPMS process engine can use the new database.
The code below demonstrates the original datasource information for
persi stence. xml :
<jta-data-source>java:comp/env/jdbc/jbpm</jta-data-source>
Change this value to the datasource defined earlier:
<jta-data-source>java:comp/env/jdbc/myDatasource</jta-datasource>
3. You can now start the JBoss Web Server to login to Business Central.
a. Run startup. sh in the $TOMCAT_HOME/bi n directory.
./startup.sh
b. Navigate to http://localhost:8080/business-central in a web browser.
c. Login with the correct username/password as given in the to mcat-users. xml file
where you defined user roles.
Report a bug
2 .3.2 .3. Se t t ing up Dashbuilde r fo r Re d Hat JBo ss We b Se rve r 2 .0 (T o m cat 7 )
Note
Before setting up D ashbuilder on Red Hat JBoss Web Server, you must ensure that you have
correctly installed and started Business Central as described in Section 2.3.2.2, “ Setting up
Business Central for Red Hat JBoss Web Server 2.0 (Tomcat 7)” . D ashbuilder requires the
history log database tables to exist, which are only provided by Business Central. If these
tables are not present in the database before attempting the steps below, you may get
initialization errors.
To set up D ashbuilder on Red Hat JBoss Web Server, do the following:
1. D efine users and roles in $TOMCAT_DIR/co nf/to mcat-users. xml . Note that D ashbuilder
requires users to have the role specified as ad mi n and/or anal yst. If you have already
defined these users earlier for Business-Central, you don't need to define them again.
2. Enable single sign-on between D ashbuilder and Business Central by uncommenting the
following lines in $TOMCAT_DIR/co nf/server. xml file:
26
⁠Chapt er 2 . Inst allat ion opt ions
<Valve className="org.apache.catalina.authenticator.SingleSignOn"
/>
3. As with Business Central setup, if you are using a database other than the default and
integrated H2 database, you will need to setup persistence.
In this procedure, you configure a datasource with the JND I name jd bc/d ashbui l d erD S
as defined in uniqueName=jdbc/jbpm in the bitronix reso urces. pro perti es file:
a. In d ashbui l d er/MET A-INF/co ntext. xml , replace the datasource JND I name in
the <Resource> element. The uniqueName attribute refers to the
resource.ds1.uniqueName property set in reso urces. pro perti es:
<Resource name="jdbc/dashbuilderDS" uniqueName="jdbc/jbpm"
auth="Container" removeAbandoned="true"
factory="bitronix.tm.resource.ResourceObjectFactory"
type="javax.sql.DataSource"/>
Note
D epending upon your database, you may need to define some other properties
here as well. For example, in an Oracle environment, this entry may look like
the following listing.
<Resource name="jdbc/jbpm" uniqueName="jdbc/jbpm"
auth="Container" removeAbandoned="true"
factory="bitronix.tm.resource.ResourceObjectFactory"
type="javax.sql.DataSource" username="username"
password="password"
driverClassName="oracle.jdbc.xa.client.OracleXADataSourc
e" url="jdbc:oracle:thin:YOUR-URL:1521:YOUR-DB"
maxActive="8" />
b. In d ashbui l d er/WEB-INF/web. xml , add the datasource JND I name in the <resref-name> element with your datasource name:
<resource-ref>
<description>Dashboard Builder Datasource</description>
<res-ref-name>jdbc/dashbuilderDS</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
c. In d ashbui l d er/MET A-INF/co ntext. xml , define the transaction factory:
<Transaction
factory="bitronix.tm.BitronixUserTransactionObjectFactory"/>
d. Update the datasource JND I name in d ashbui l d er/WEBINF/etc/hi bernate. cfg . xml in the <session-factory> element:
27
Red Hat JBoss BPM Suit e 6 .0 Inst allat ion G uide
<property
name="connection.datasource">java:/comp/env/jdbc/dashbuilderD
S</property>
4. Restart Java Web server for these changes to take effect. Once restarted, you can navigate to
D ashbuilder from within Business Central or directly via:
http: //l o cal ho st: 80 80 /d ashbui l d er.
Report a bug
28
⁠Chapt er 3. Special set ups
Chapter 3. Special setups
3.1. Set t ing up Persist ence for Business Cent ral
BPM Suite is configured to use an example datasource with Java Naming and D irectory Interface
(JND I) name java: jbo ss/d ataso urces/Exampl eD S. For Business Central, this example
datasource is located in the file busi ness-central . war/WEB-INF/cl asses/MET AINF/persi stence. xml .
If you want to configure BPM Suite to use an external database, make the following changes. For file
busi ness-central . war/WEB-INF/cl asses/MET A-INF/persi stence. xml :
1. Install the respective Java D atabase Connectivity (JD BC) driver using modular approach for
easy subsequent configuration (see EAP 6 documentation).
2. Create a new datasource according to the example in EAP 6 documentation, section 6.7.1.
Example PostgreSQL D atasource. This is the default used H2 database specific datasource
configuration:
<subsystem xmlns="urn:jboss:domain:datasources:1.1">
<datasources>
<datasource jndiname="java:jboss/datasources/ExampleDS" pool-name="ExampleDS"
enabled="true" use-java-context="true">
<connection-url>jdbc:h2:mem:test;DB_CLOSE_DELAY=1</connection-url>
<driver>h2</driver>
<security>
<user-name>sa</user-name>
<password>sa</password>
</security>
</datasource>
<drivers>
<driver name="h2" module="com.h2database.h2">
<xa-datasourceclass>org.h2.jdbcx.JdbcDataSource</xa-datasource-class>
</driver>
</drivers>
</datasources>
3. Use the JND I name of the datasource to update the following entry inside the
persi stence. xml file, which is by default set to this entry.
<jta-data-source>java:jboss/datasources/ExampleDS</jta-data-source>
Important
When configuring your datasource, make sure to enable JTA (typically, by adding
jta= "true" to the d ataso urce tag).
4. Replace the following text with the appropriate database specific hibernate dialect name.
29
Red Hat JBoss BPM Suit e 6 .0 Inst allat ion G uide
<property name="hibernate.dialect"
value="org.hibernate.dialect.H2Dialect" />
For example, for an Oracle D atabase Express Edition 11g, it would be:
<property name="hibernate.dialect"
value="org.hibernate.dialect.Oracle10gDialect" />
Report a bug
3.2. Set t ing up Persist ence for Dashbuilder
As D ashbuilder is dependent on the configuration of Business Central, ensure Business Central is
configured according to Section 3.1, “ Setting up Persistence for Business Central” . BPMS 6 is
configured to use a datasource with Java Naming and D irectory Interface (JND I) name
java: jbo ss/d ataso urces/Exampl eD S. If you want to make the application work with a
database different from H2, for example O racl e, MySQ L, P o stg res, or MS SQ L Server, follow
these steps.
1. Install the database driver and create a new datasource according to the example in EAP 6
D ocumentation in section 6.7.1. Example PostgreSQL D atasource. Use modular approach to
the installation of JD BC driver for easy subsequent configuration.
2. Create an empty database.
3. Modify file d ashbui l d er. war/WEB-INF/jbo ss-web. xml whose default entry is:
<jboss-web>
<context-root>/dashbuilder</context-root>
<resource-ref>
<res-ref-name>jdbc/dashbuilder</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<jndi-name>java:jboss/datasources/ExampleDS</jndi-name>
</resource-ref>
4. Modify also files WEB-INF/jbo ss-d epl o yment-structure. xml from both the
busi ness-central . war and d ashbui l d er. war applications, and add a dependency
under the dependencies section on the JBD C driver module created earlier during
datasource creation. The following snippet shows a sample configuration where
jd bcD ri verMo d ul eName is the name of the JBoss EAP 6 JD BC driver module.
<dependencies>
...
<module name="jdbcDriverModuleName" />
...
</dependencies>
Report a bug
3.3. Special set up for IBM DB2 dat abase
30
⁠Chapt er 3. Special set ups
If you want to use an IBM D B2 database as the underlying data source for Business Central, you will
need to increase the page size for the database. The default page size of 4 kB is not sufficient for the
D ashbuilder table columns size.
When creating the database, force the page size to 16384 as in the example below:
Examp le 3.1. Ad ju st in g p ag e siz e
CREATE DATABASE dashb PAGESIZE 16384
This increase in page size for the underlying database must be performed before the BPM Suite has
been run for the first time.
Report a bug
31
Red Hat JBoss BPM Suit e 6 .0 Inst allat ion G uide
Chapter 4. Roles and Users
4 .1. 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 D eveloper 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, Au t h o rin g → Ad min ist rat io n access is unavailable to users with the analyst role.
Certain lower-level features targeted towards developers, like the D ep lo ymen t → Art if act
R ep o sit o ry view are not accessible for this role. However, the Bui l d & D epl o y 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
4 .2. Creat ing users
To start adding new users, you will need to run the add-user.sh script on a Unix system or the adduser.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: hel l o wo rl d user.
5. Create the user's password at the password prompt and reenter the password. For example:
Hel l o wo rl d @ 123.
32
⁠Chapt er 4 . Roles and Users
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 4.1,
“ D efining Roles” ).
Business Central users need to have at least the anal yst role, and dashbuilder users need
to have the ad mi n 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
33
Red Hat JBoss BPM Suit e 6 .0 Inst allat ion G uide
Chapter 5. Testing the installation
5.1. St art ing t he server
If you have installed BPMS using either the Installer or via the EAP6 bundle install, you can now start
your server in one of two modes.
Note
If you installed BPMS using the generic deployable version on Red Hat Java Web Server, the
instructions for download and install also contain the instructions for starting the server. You
can ignore the following discussion.
The default startup script, stand al o ne. sh that Red Hat JBoss BPM Suite ships with is optimized
for performance. To run your server in the performance mode, do the following:
1. On the command line, move into the $SERVER_HOME/bi n/ directory.
2. In a Unix environment run:
./standalone.sh
In a Windows environment run:
./standalone.bat
Red Hat JBoss BPM Suite also ships with a separate script, stand al o ne-secure. sh that is
optimized for security. This script applies a security policy by default that protects against a known
security vulnerability.
Note
It is recommended that production environments use stand al o ne-secure. sh script.
Warning
The use of a security manager imposes a significant performance penalty that you should be
aware of. The tradeoff between security and performance must be made by taking into
consideration individual circumstances. See Section 5.2, “ Java Security Manager and
performance management” .
To run your server in the secure mode with this script, do the following:
1. On the command line, move into the $SERVER_HOME/bi n/ directory.
2. In a Unix environment run:
./standalone-secure.sh
34
⁠Chapt er 5. T est ing t he inst allat ion
In a Windows environment run:
./standalone-secure.bat
Report a bug
5.2. Java Securit y Manager and performance management
As noted earlier, enabling the Java Security Manager (JSM) to sandbox the evaluation of MVEL
scripts in BPMS introduces a performance hit in high load environments. Environments and
performance markers must be kept in mind when deploying a BPMS application. Use the following
guidelines to deploy secure and high performance BPMS applications.
In high load environments where performance is critical it is recommended to only deploy
applications that have been developed on other systems and properly reviewed. It is also
recommended not to create any users with Analyst role on such systems. If these safeguards are
followed, it is safe to leave JSM disabled on these systems so it does not introduce any
performance degradation.
In testing and development environments without high loads, or in environments where rule and
process authoring is exposed to external networks, it is recommended to have JSM enabled in
order to achieve security benefits of properly sandboxed evaluation of MVEL.
Allowing users with Analyst role to log in to the Business Central console with JSM disabled is not
secure and not recommended.
Report a bug
5.3. Logging on t o Business Cent ral
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 l o cal ho st 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 =
hel l o wo rl d user and password = Hel l o wo rl d @ 123.
Report a bug
35
Red Hat JBoss BPM Suit e 6 .0 Inst allat ion G uide
Chapter 6. Clustering
When clustering Red Hat JBoss BPM Suite, consider which components need to be clustered. You
can cluster the following:
GIT repository: virtual-file-system (VFS) repository that holds the business assets so that all
cluster nodes use the same repository
Execution Server and Web applications: the runtime server that resides in the container (such as,
Red Hat JBoss EAP) along with BRMS and BPM Suite web applications so that nodes share the
same runtime data.
For instructions on clustering the application, refer to the container clustering documentation.
Back-end database: database with the state data, such as, process instances, KIE sessions,
history log, etc., for fail-over purposes
Fig u re 6 .1. Sch ema o f B PMS syst em wit h in d ivid u al syst em co mp o n en t s
GIT reposit ory clust ering mechanism
To cluster the GIT repository the following is used:
Apache Z ookeeper brings all parts together.
Apache Helix is the cluster management component that registers all cluster details (the cluster
itself, nodes, resources).
36
⁠Chapt er 6 . Clust ering
The runtime environment, that is the Execution Server, utilizes the following to provide the clustering
capabilities:
kie-commons provides VFS implementation and clustering
uber fire framework provides backbone of the web applications
Fig u re 6 .2. C lu st erin g sch ema wit h H elix an d Z o o keep er
A typical clustering setup involves the following:
Setting up the cluster itself using Z ookeeper and Helix
Setting up the back-end database with Quartz tables and configuration
Configuring clustering on your container (this documentation provides only clustering
instructions for Red Hat JBoss EAP 6)
Clust ering Maven Reposit ories
Various operations within the Business Central publish JARs to the Business Central's internal
Maven Repository.
This repository exists on the application server's file-system as regular files and is not cluster aware.
This folder is not synchronized across the various nodes in the cluster and must be synchronized
using external tools like rsync.
37
Red Hat JBoss BPM Suit e 6 .0 Inst allat ion G uide
An alternate to the use of an external synchronization tool is to set the system property
org.guvnor.m2repo.dir on each cluster node to point to a SAN or NAS. In this case clustering of the
Maven repository folder is not needed.
Report a bug
6.1. Set t ing up a clust er
To cluster your GIT (VFS) repository in Business Central, do the following (If you don't use Business
Central, you may skip this section):
1. D ownload the jbo ss-bpms-brms-VERSION-red hat-suppl ementary-to o l s. zi p,
which contains Apache Z ookeeper, Apache Helix, and quartz D D L scripts. After
downloading, unzip the archive: the Zo o keeper directory ($ZO O KEEP ER _HO ME) and the
Hel i x directory ($HELIX_HO ME) are created.
2. Now Configure Z ookeeper:
a. In the Z ookeeper directory, go to co nf directory and do the following:
cp zoo_sample.cfg zoo.cfg
b. Open zo o . cfg for editing and adjust the settings including the following:
# the directory where the snapshot is stored.
dataDir=$ZOOKEEPER_HOME/tmp/
# the port at which the clients connects
clientPort=2181
Make sure the dataD ir location exists and is accessible.
3. Set up Z ookeeper, so you can use it when creating the cluster with Helix:
a. Go to the $ZOOKEEPER_HOME/bi n/ directory and start Z ookeeper:
./zkServer.sh start
You can check the Z ookeeper log in the $ZOOKEEPER_HOME/bi n/zo o keeper. o ut
file.
4. Set up the cluster with the Z ookeeper server as the master of the configuration:
a. Create the cluster:
$HELIX_HOME/bin/helix-admin.sh --zkSvr
ZOOKEEPER_HOST:ZOOKEEPER_PORT --addCluster CLUSTER_NAME
b. Add your nodes to the cluster:
$HELIX_HOME/bin/helix-admin.sh --zkSvr
ZOOKEEPER_HOST:ZOOKEEPER_PORT --addNode CLUSTER_NAME
NODE_NAMEUNIQUE_ID
Examp le 6 .1. Ad d in g t wo clu st er n o d es
38
⁠Chapt er 6 . Clust ering
./helix-admin.sh --zkSvr localhost:2181 --addNode bpmscluster nodeOne:12345
./helix-admin.sh --zkSvr localhost:2181 --addNode bpmscluster nodeTwo:12346
5. Add resources to the cluster.
Examp le 6 .2. Ad d in g vf s- rep o as reso u rce
./helix-admin.sh --zkSvr localhost:2181 --addResource bpmscluster vfs-repo 1 LeaderStandby AUTO_REBALANCE
6. Rebalance the cluster.
Examp le 6 .3. R eb alan cin g t h e b p ms- clu st er
./helix-admin.sh --zkSvr localhost:2181 --rebalance bpms-cluster
vfs-repo 2
7. Start the Helix controller.
Examp le 6 .4 . St art in g t h e H elix co n t ro ller
./run-helix-controller.sh --zkSvr localhost:2181 --cluster bpmscluster 2>& 1 > /tmp/controller.log &
Report a bug
6.2. Set t ing up Quart z
Before you can configure the database on your application server, you need to prepare the database
for Quartz to create Quartz tables, which will hold the timer data, and the Quartz definition file.
Of course, if you are not using Quartz (timers) in your business processes, or if you are not using the
Execution Server at all, you can skip this section completely. Please note that if you want to replicate
timers in your business process, you need to use the Quartz component.
Warning
Please keep in mind that due to a bug in the implementation of the Quartz API in the current
version of Red Hat JBoss BPM Suite, a cluster with EAP 6 nodes and D B2 as the backend
database that attempts to create and then deploy a process dealing with timers or deadlines
will fail with an error. To get around this issue, remove the constraints on blob size in Quartz
D D L for D B2.
39
Red Hat JBoss BPM Suit e 6 .0 Inst allat ion G uide
To set this up, do the following:
1. Set up the database. Make sure to use one of the supported non-JTA data source. Note, that
since Quartz need a non-JTA data source, you cannot use the Business Central data source.
In the example code, PostgreSQL with the user bpms and password bpms is used. This
database will need to be connected to your application server, so make sure to keep a note
on the database information and credentials.
2. Create Quartz tables on your database to allow timer events synchronization. To do so, use
the D LL script for your database, which is available in the extracted supplementary zip
archive in QUARTZ _HOME/docs/dbTables.
3. Create the Quartz configuration file q uartz-d efi ni ti o n. pro perti es in
$JBOSS_HOME/PROFILE/co nfi g urati o n/ directory and define the Quartz properties.
Examp le 6 .5. Q u art z co n f ig u rat io n f ile f o r a Po st g reSQ L d at ab ase
#==============================================================
==============
# Configure Main Scheduler Properties
#===============================================================
=============
org.quartz.scheduler.instanceName = jBPMClusteredScheduler
org.quartz.scheduler.instanceId = AUTO
#===============================================================
=============
# Configure ThreadPool
#===============================================================
=============
org.quartz.threadPool.class = org.quartz.simpl.SimpleThreadPool
org.quartz.threadPool.threadCount = 5
org.quartz.threadPool.threadPriority = 5
#===============================================================
=============
# Configure JobStore
#===============================================================
=============
org.quartz.jobStore.misfireThreshold = 60000
org.quartz.jobStore.class=org.quartz.impl.jdbcjobstore.JobStoreCM
T
org.quartz.jobStore.driverDelegateClass=org.quartz.impl.jdbcjobst
ore.PostgreSQLDelegate
org.quartz.jobStore.useProperties=false
org.quartz.jobStore.dataSource=managedDS
org.quartz.jobStore.nonManagedTXDataSource=notManagedDS
org.quartz.jobStore.tablePrefix=QRTZ_
org.quartz.jobStore.isClustered=true
org.quartz.jobStore.clusterCheckinInterval = 20000
#===============================================================
40
⁠Chapt er 6 . Clust ering
=============
# Configure Datasources
#===============================================================
=============
org.quartz.dataSource.managedDS.jndiURL=jboss/datasources/psbpmsD
S
org.quartz.dataSource.notManagedDS.jndiURL=jboss/datasources/quar
tzNotManagedDS
Note the configured datasources that will accommodate the two Quartz schemes at the very
end of the file.
Cluster node check interval
The recommended interval for cluster discovery is 20 seconds and is set in the
org.quartz.jobStore.clusterCheckinInterval of the q uartzd efi ni ti o n. pro perti es file. D epending on your set up consider the performance
impact and modify the setting as necessary.
Also note the org.quartz.jobStore.driverD elegateClass property that defines the D B dialect to
be used when communicating with the set database (in this example,
o rg . q uartz. i mpl . jd bcjo bsto re. P o stg reSQ LD el eg ate).
Report a bug
6.3. Configuring clust ering on Red Hat JBoss EAP
The information provided in this section is a simple clustering recipe. For additional information on
clustering refer to Red Hat JBoss EAP documentation.
To configure clustering on Red Hat JBoss EAP 6, do the following:
1. Install your JD BC driver as a core module: copy the driver jar to
$EAP_HOME/mo d ul es/system/l ayers/base/ and create a mo d ul e. xml file in the
directory.
2. Edit the mo d ul e. xml file as of the respective module XSD .
Examp le 6 .6 . T h e mo d u le.xml f ile co n t en t f o r a Po st g reSQ L d at aso u rce
<module xmlns="urn:jboss:module:1.0" name="org.postgresql">
<resources>
<resource-root path="postgresql-jdbc.jar"/>
</resources>
<dependencies>
<module name="javax.api"/>
<module name="javax.transaction.api"/>
</dependencies>
</module>
41
Red Hat JBoss BPM Suit e 6 .0 Inst allat ion G uide
3. Configure individual server nodes in the mai n-server-g ro up element in the
$EAP_HOME/domain/co nfi g urati o n/ho st. xml file with properties defined in Table 6.1,
“ Cluster node properties” :
T ab le 6 .1. C lu st er n o d e p ro p ert ies
Pro p ert y n ame
Valu e
D escrip t io n
o rg . uberfi re. ni o . g i t
.dir
o rg . q uartz. pro perti es
/ho me/jbpm/no d e[N]/re
po
/bpms/q uartzd efi ni ti o n. pro perti es
no d eO ne
bpms-cl uster
GIT (VFS) repository location
on node[N]
absolute path to the quartz
configuration file
node name unique within the
cluster
Helix cluster name
l o cal ho st: 2181
Z ookeeper location
no d eO ne_1234 5
unique ID of the Helix cluster
node
jbo ss. no d e. name
o rg . uberfi re. cl uster.
id
o rg . uberfi re. cl uster.
zk
o rg . uberfi re. cl uster.
l o cal . i d
Note that : is replaced with
_.
o rg . uberfi re. cl uster.
vfs. l o ck
o rg . uberfi re. ni o . g i t
. d aemo n. po rt
vfs-repo
9 4 18
name of the resource defined
on the Helix cluster
port used by the VFS repo to
accept client connections
The port must be unique for
each cluster member.
o rg . uberfi re. metad ata
. i nd ex. d i r
/ho me/jbpm/no d e[N]/i n
d ex
o rg . uberfi re. cl uster.
auto start
fal se
o rg . uberfi re. ni o . g i t
. ssh. po rt
80 0 3
o rg . uberfi re. ni o . g i t
. d aemo n. ho st
no d eO ne
o rg . uberfi re. ni o . g i t
. ssh. ho st
no d eO ne
Examp le 6 .7. C lu st er n o d eO n e co n f ig u rat io n
42
location where the index for
search is to be created
(maintained by Apache
Lucene)
This value delays VFS
clustering until the
application is fully initialized
to avoid conficts when all
cluster members create local
clones.
the unique port number for
ssh access to the GIT repo
for a cluster running on
physical machines.
the name of the daemon host
machine in a physical
cluster.
the name of the SSH host
machine in a physical
cluster.
⁠Chapt er 6 . Clust ering
<system-properties>
<property name="org.uberfire.nio.git.dir"
value="/tmp/bpms/nodeone" boot-time="false"/>
<property name="jboss.node.name" value="nodeOne" boottime="false"/>
<property name="org.uberfire.cluster.id" value="bpms-cluster"
boot-time="false"/>
<property name="org.uberfire.cluster.zk" value="localhost:2181"
boot-time="false"/>
<property name="org.uberfire.cluster.local.id"
value="nodeOne_12345" boot-time="false"/>
<property name="org.uberfire.cluster.vfs.lock" value="vfs-repo"
boot-time="false"/>
<property name="org.uberfire.nio.git.daemon.port" value="9418"
boot-time="false"/>
<property name="org.uberfire.metadata.index.dir"
value="/tmp/jbpm/nodeone" boot-time="false"/>
<property name="org.uberfire.cluster.autostart" value="false"
boot-time="false"/>
<property name="org.uberfire.nio.git.ssh.port" value="8003"
boot-time="false"/>
<property name="org.uberfire.nio.git.daemon.host"
value="nodeOne" />
<property name="org.uberfire.nio.git.ssh.host" value="nodeOne"
/>
<property name="org.quartz.properties"
value="/tmp/jbpm/quartz/quartz-db-postgres.properties" boottime="false"/>
</system-properties>
Examp le 6 .8. C lu st er n o d eT wo co n f ig u rat io n
<system-properties>
<property name="org.uberfire.nio.git.dir"
value="/tmp/bpms/nodetwo" boot-time="false"/>
<property name="jboss.node.name" value="nodeTwo" boottime="false"/>
<property name="org.uberfire.cluster.id" value="bpms-cluster"
boot-time="false"/>
<property name="org.uberfire.cluster.zk" value="localhost:2181"
boot-time="false"/>
<property name="org.uberfire.cluster.local.id"
value="nodeTwo_12346" boot-time="false"/>
<property name="org.uberfire.cluster.vfs.lock" value="vfs-repo"
boot-time="false"/>
<property name="org.uberfire.nio.git.daemon.port" value="9418"
boot-time="false"/>
<property name="org.uberfire.metadata.index.dir"
value="/tmp/jbpm/nodetwo" boot-time="false"/>
<property name="org.uberfire.cluster.autostart" value="false"
boot-time="false"/>
43
Red Hat JBoss BPM Suit e 6 .0 Inst allat ion G uide
<property name="org.uberfire.nio.git.ssh.port" value="8003"
boot-time="false"/>
<property name="org.uberfire.nio.git.daemon.host"
value="nodeTwo" />
<property name="org.uberfire.nio.git.ssh.host" value="nodeTwo"
/>
<property name="org.quartz.properties"
value="/tmp/jbpm/quartz/quartz-db-postgres.properties" boottime="false"/>
</system-properties>
4. Add management users as instructed in the Administration and Configuration Guide for Red Hat
JBoss EAP and application users as instructed in Red Hat JBoss BPM Suite Administration and
Configuration Guide.
5. Start the application server:
]$ $JBOSS_HOME/bin/domain.sh
6. Check that the nodes are available.
D eploy the Business Central application to your servers:
1. Change the predefined persistence of the application to the required data base (PostgreSQL):
in persi stence. xml change the following:
a. jta-data-source name to the source defined on the application server
(java: jbo ss/d ataso urces/psbpmsD S)
b. hibernate dialect to be match the data source dialect
(o rg . hi bernate. d i al ect. P o stg reSQ LD i al ect)
2. Log on as the management user to the server Administration console of your domain and add
the new deployments using the Runtime view of the console. Once the deployment is added to
the domain, assign it to the correct server group (mai n-server-g ro up).
Report a bug
44
⁠Chapt er 7 . Maven Reposit ories
Chapter 7. Maven Repositories
7.1. About Maven
Apache Maven is a distributed build automation tool used in Java application development to build
and manage software projects. Maven uses configuration XML files called POM (Project Object
Model) to define project properties and manage the build process. POM files describe the project's
module and component dependencies, build order, and targets for the resulting project packaging
and output. This ensures that projects are built in a correct and uniform manner.
Maven uses repositories to store Java libraries, plug-ins, and other build artifacts. Repositories can
be either local or remote. A local repository is a download of artifacts from a remote repository
cached on a local machine. A remote repository is any other repository accessed using common
protocols, such as http: // when located on an HTTP server, or fi l e: // when located on a file
server. The default repository is the public remote Maven 2 Central Repository.
Configuration of Maven is performed by modifying the setti ng s. xml file. You can either configure
global Maven settings in the M2_HOME/co nf/setti ng s. xml file, or user-level settings in the
USER_HOME/. m2/setti ng s. xml file.
For more information about Maven, see Welcome to Apache Maven.
For more information about Maven repositories, see Apache Maven Project - Introduction to
Repositories.
For more information about Maven POM files, see the Apache Maven Project POM Reference.
Report a bug
7.2. About T he Provided Maven Reposit ories
A set of repositories containing artifacts required to build applications based on Red Hat
JBoss BPM Suite is provided with this release. Maven must be configured to use these repositories
and the Maven Central Repository in order to provide correct build functionality.
Two interchangeable sets of repositories ensuring the same functionality are provided. The first set is
available for download and storage in a local file system, the second set is hosted online for use as
remote repositories. You can configure Maven to use the repositories following the procedure in
Section 7.4, “ Configuring Maven to Use the Online Repositories” or Section 7.3, “ Configuring Maven
to Use the File System Repositories” .
Important
The set of online remote repositories is a technology preview source of components. As such,
it is not in scope of patching and is supported only for use in development environment. Using
the set of online repositories in production environment is a potential source of security
vulnerabilities and is therefore not a supported use case. For more information see
https://access.redhat.com/site/maven-repository.
Report a bug
7.3. Configuring Maven t o Use t he File Syst em Reposit ories
45
Red Hat JBoss BPM Suit e 6 .0 Inst allat ion G uide
O verview
In situations where you cannot use the online repositories, you will have to download and configure
the required repositories locally.
Pro ced u re 7.1.
1. D ownload the following Z IP archives containing the required repositories:
http://maven.repository.redhat.com/techpreview/brms6/6.0.3/jboss-bpms-brms-6.0.3.GAredhat-1-maven-repository.zip
http://maven.repository.redhat.com/techpreview/eap6/6.1.1/jboss-eap-6.1.1-mavenrepository.zip
Note
Alternatively, the Z IP archives can be downloaded from
http://access.redhat.com/jbossnetwork/.
2. Unzip the downloaded Z IP files into an arbitrary location in a local file system.
3. Add entries for the unzipped repositories to Maven's setti ng s. xml file. The following code
sample contains a profile with the repositories, configuration of authentication for access to
the repositories, and an activation entry for the profile:
​< ?xml version="1.0" encoding="UTF-8" standalone="no"?>
​< settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/xsd/settings1.0.0.xsd">
​ <localRepository/>
​ <profiles>
​
<!-- Profile with local repositories required by BRMS/BPMS -->
​
<profile>
​
<id>brms-bpms-local-profile</id>
​
<repositories>
​
<repository>
​
<id>jboss-bpms-brms-6.0.3.GA-redhat-1-mavenrepository</id>
​
<name>BRMS/BPMS 6.0.3 GA Repository</name>
​
<url>file://<!-- path to the repository -->/jboss-bpmsbrms-6.0.3.GA-redhat-1-maven-repository</url>
​
<layout>default</layout>
​
<releases>
​
<enabled>true</enabled>
​
<updatePolicy>never</updatePolicy>
​
</releases>
​
<snapshots>
​
<enabled>false</enabled>
​
<updatePolicy>never</updatePolicy>
​
</snapshots>
​
</repository>
​
<repository>
​
<id>jboss-eap-6.1.1.GA-maven-repository</id>
46
⁠Chapt er 7 . Maven Reposit ories
​
<name>EAP 6.1.1 GA Repository</name>
<url>file://<!-- path to the repository -->/jboss-eap6.1.1.GA-maven-repository</url>
​
<layout>default</layout>
​
<releases>
​
<enabled>true</enabled>
​
<updatePolicy>never</updatePolicy>
​
</releases>
​
<snapshots>
​
<enabled>false</enabled>
​
<updatePolicy>never</updatePolicy>
​
</snapshots>
​
</repository>
​
<repository>
​
<id>jboss-public-repository</id>
​
​
<url>http://repository.jboss.org/nexus/content/repositories/public/
</url>
​
<releases>
​
<enabled>true</enabled>
​
</releases>
​
<snapshots>
​
<enabled>false</enabled>
​
</snapshots>
​
</repository>
​
</repositories>
​
<pluginRepositories>
​
<pluginRepository>
​
<id>jboss-bpms-brms-6.0.3.GA-redhat-1-mavenrepository</id>
​
<name>BRMS/BPMS 6.0.3 GA Repository</name>
​
<url>file://<!-- path to the repository -->/jboss-bpmsbrms-6.0.3.GA-redhat-1-maven-repository</url>
​
<layout>default</layout>
​
<releases>
​
<enabled>true</enabled>
​
<updatePolicy>never</updatePolicy>
​
</releases>
​
<snapshots>
​
<enabled>false</enabled>
​
<updatePolicy>never</updatePolicy>
​
</snapshots>
​
</pluginRepository>
​
<pluginRepository>
​
<id>jboss-eap-6.1.1.GA-maven-repository</id>
​
<name>EAP 6.1.1 GA Repository</name>
​
<url>file://<!-- path to the repository -->/jboss-eap6.1.1.GA-maven-repository</url>
​
<layout>default</layout>
​
<releases>
​
<enabled>true</enabled>
​
<updatePolicy>never</updatePolicy>
​
</releases>
​
<snapshots>
​
<enabled>false</enabled>
​
<updatePolicy>never</updatePolicy>
47
Red Hat JBoss BPM Suit e 6 .0 Inst allat ion G uide
​
</snapshots>
</pluginRepository>
<pluginRepository>
<id>jboss-public-plugin-repository</id>
​
​
​
​
<url>http://repository.jboss.org/nexus/content/repositories/public/
</url>
​
<releases>
​
<enabled>true</enabled>
​
</releases>
​
<snapshots>
​
<enabled>false</enabled>
​
</snapshots>
​
</pluginRepository>
​
</pluginRepositories>
​
</profile>
​ </profiles>
​
<!-- Configuring pre-emptive authentication for the repository
server -->
​ <server>
​
<id>brms-bpms-m2-repo</id>
​
<username>admin</username>
​
<password>admin</password>
​
<configuration>
​
<wagonProvider>httpclient</wagonProvider>
​
<httpConfiguration>
​
<all>
​
<usePreemptive>true</usePreemptive>
​
</all>
​
</httpConfiguration>
​
</configuration>
​ </server>
​
​
<!-- Alternative to enabling pre-emptive authentication configuring
​
the Authorization HTTP header with Base64-encoded
credentials
​ <server>
​
<id>brms-bpms-m2-repo</id>
​
<configuration>
​
<httpHeaders>
​
<property>
​
<name>Authorization</name>
​
<value>Basic YWRtaW46YWRtaW4=</value>
​
</property>
​
</httpHeaders>
​
</configuration>
​ </server>
​ -->
​
​
<activeProfiles>
​
<!-- Activation of the BRMS/BPMS profile -->
​
<activeProfile>brms-bpms-local-profile</activeProfile>
​ </activeProfiles>
​< /settings>
48
⁠Chapt er 7 . Maven Reposit ories
Important
The bpm-servi ce quickstart application will not build without two additional repositories. If
you want to build this application, download the following repositories and add them to your
setti ng . xml file in the same way as that shown above.
http://maven.repository.redhat.com/techpreview/eap6/6.0.1/jboss-eap-6.0.1-mavenrepository.zip
http://maven.repository.redhat.com/techpreview/wfk2/2.5.0/jboss-wfk-2.5.0-mavenrepository.zip
R esu lt
The Maven repositories are downloaded, unzipped in a local file system, registered in Maven's
setti ng s. xml file, and ready to be used when performing Maven builds.
T ro u b lesh o o t in g
Q:
Wh y d o I st ill g et erro rs wh en b u ild in g o r d ep lo yin g my ap p licat io n s?
A:
Issu e
When you build or deploy a project, it fails with one or both of the following errors:
[ER R O R ] Fai l ed to execute g o al o n pro ject PROJECT_NAME
C o ul d no t fi nd arti fact ARTIFACT_NAME
C au se
Your cached local Maven repository might contain outdated artifacts.
R eso lu t io n
To resolve the issue, delete the cached local repository – the ~ /. m2/repo si to ry/ directory
on Linux or the %SystemDrive%\Users\USERNAME\. m2\repo si to ry\ directory on
Windows – and run mvn cl ean i nstal l -U. This will force Maven to download correct
versions of required artifacts when performing the next build.
Q:
Wh y is JB o ss D evelo p er St u d io u sin g my o ld Maven co n f ig u rat io n ?
A:
Issu e
You have updated your Maven configuration, but this configuration is not reflected in JBoss
D eveloper Studio.
C au se
49
Red Hat JBoss BPM Suit e 6 .0 Inst allat ion G uide
If JBoss D eveloper Studio is running when you modify your Maven setti ng s. xml file, this
configuration will not be reflected in JBoss D eveloper Studio.
R eso lu t io n
Refresh the Maven settings in the ID E. From the menu, choose Win d o w → Pref eren ces. In the
P references Window, expand Maven and choose User Setti ng s. Click the Upd ate
Setti ng s button to refresh the Maven user settings in JBoss D eveloper Studio.
Fig u re 7.1. U p d at e Maven U ser Set t in g s
Report a bug
7.4 . Configuring Maven t o Use t he Online Reposit ories
50
⁠Chapt er 7 . Maven Reposit ories
The online repositories required for Red Hat JBoss BPM Suite applications are located at
http://maven.repository.redhat.com/techpreview/all/ and
http://repository.jboss.org/nexus/content/repositories/public/.
If you did not configure the Maven repository during installation, you can configure it using the
following procedure. (It is also possible to do this using the project's POM file, but this is not
recommended.)
Pro ced u re 7.2. C o n f ig u rin g Maven t o U se t h e O n lin e R ep o sit o ries
1. Add entries for the online repositories and configuration of authentication for accessing them
to Maven's setti ng s. xml file as in the code sample below:
​
​< settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
​
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
​
xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
http://maven.apache.org/xsd/settings-1.0.0.xsd">
<profiles>
<!-- Profile with online repositories required by BRMS/BPMS -->
<profile>
<id>brms-bpms-online-profile</id>
<repositories>
<repository>
<id>jboss-ga-repository</id>
​
​
​
​
​
​
​
<url>http://maven.repository.redhat.com/techpreview/all</url>
​
<releases>
​
<enabled>true</enabled>
​
</releases>
​
<snapshots>
​
<enabled>false</enabled>
​
</snapshots>
​
</repository>
​
<repository>
​
<id>jboss-public-repository</id>
​
<url>http://repository.jboss.org/nexus/content/repositories/public/
</url>
​
<releases>
​
<enabled>true</enabled>
​
</releases>
​
<snapshots>
​
<enabled>false</enabled>
​
</snapshots>
​
</repository>
​
</repositories>
​
<pluginRepositories>
​
<pluginRepository>
​
<id>jboss-ga-plugin-repository</id>
​
<url>http://maven.repository.redhat.com/techpreview/all</url>
​
<releases>
​
<enabled>true</enabled>
​
</releases>
​
<snapshots>
51
Red Hat JBoss BPM Suit e 6 .0 Inst allat ion G uide
​
<enabled>false</enabled>
</snapshots>
</pluginRepository>
<pluginRepository>
<id>jboss-public-plugin-repository</id>
​
​
​
​
​
<url>http://repository.jboss.org/nexus/content/repositories/public/
</url>
​
<releases>
​
<enabled>true</enabled>
​
</releases>
​
<snapshots>
​
<enabled>false</enabled>
​
</snapshots>
​
</pluginRepository>
​
</pluginRepositories>
​
</profile>
​ </profiles>
​
​
<!-- Configuring pre-emptive authentication for the repository
server -->
​ <server>
​
<id>brms-bpms-m2-repo</id>
​
<username>admin</username>
​
<password>admin</password>
​
<configuration>
​
<wagonProvider>httpclient</wagonProvider>
​
<httpConfiguration>
​
<all>
​
<usePreemptive>true</usePreemptive>
​
</all>
​
</httpConfiguration>
​
</configuration>
​ </server>
​
​
<!-- Alternative to enabling pre-emptive authentication configuring
​
the Authorization HTTP header with Base64-encoded
credentials
​ <server>
​
<id>brms-bpms-m2-repo</id>
​
<configuration>
​
<httpHeaders>
​
<property>
​
<name>Authorization</name>
​
<value>Basic YWRtaW46YWRtaW4=</value>
​
</property>
​
</httpHeaders>
​
</configuration>
​ </server>
​ -->
​
​
52
<activeProfiles>
<!-- Activation of the BRMS/BPMS profile -->
⁠Chapt er 7 . Maven Reposit ories
​
<activeProfile>brms-bpms-online-profile</activeProfile>
</activeProfiles>
​
​< /settings>
2. If you modified the setti ng s. xml file while JBoss D eveloper Studio was running, you must
refresh Maven settings in the ID E. From the menu, choose Win d o w → Pref eren ces. In the
P references Window, expand Maven and choose User Setti ng s. Click the Upd ate
Setti ng s button to refresh the Maven user settings in JBoss D eveloper Studio.
Fig u re 7.2. U p d at e Maven U ser Set t in g s
R esu lt
Maven has been configured to use the online repositories provided for Red Hat JBoss BPM Suite.
53
Red Hat JBoss BPM Suit e 6 .0 Inst allat ion G uide
Important
If your cached local Maven repository contains outdated artifacts, you may encounter one of
the following Maven errors when you build or deploy your project:
Missing artifact ARTIFACT_NAME
[ERROR] Failed to execute goal on project PROJECT_NAME; Could not resolve
dependencies for PROJECT_NAME
To resolve the issue, delete the cached local repository – the ~ /. m2/repo si to ry/ directory
on Linux or the %SystemDrive%\Users\USERNAME\. m2\repo si to ry\ directory on
Windows. This will force Maven to download correct versions of required artifacts during the
next build.
Report a bug
7.5. Dependency Management
In order to use correct Maven dependencies in your Red Hat JBoss BPM Suite project, relevant Bill Of
Materials (BOM) and parent POM files must be added to the project's po m. xml file. Adding the BOM
and parent will ensure that correct versions of plugins and transitive dependencies from the provided
Maven repositories are included in the project.
To ensure correct dependency usage in your project, declare the following parent in the project's
po m. xml file:
o rg . jbo ss. i p. co mpo nent. manag ement: i p-parent: 1. 2. 1-red hat-2
and add the following two BOM files as dependencies in the d epend encyManag ement section:
o rg . jbo ss. i p. co mpo nent. manag ement: i p-d epend ency-manag ement-al l : 1. 2. 1red hat-2
o rg . jbo ss. co mpo nent. manag ement: jbo ss-d epend ency-manag emental l : 6 . 1. 2. Fi nal -red hat-5
Use the entries from the code sample below for this purpose.
​< parent>
​ <groupId>org.jboss.ip.component.management</groupId>
​ <artifactId>ip-parent</artifactId>
​ <version>1.2.1-redhat-2</version>
​< /parent>
​. ..
​< dependencyManagement>
​ <dependencies>
​
<dependency>
​
<groupId>org.jboss.ip.component.management</groupId>
​
<artifactId>ip-dependency-management-all</artifactId>
​
<type>pom</type>
​
<version>1.2.1-redhat-2</version>
​
<scope>import</scope>
54
⁠Chapt er 7 . Maven Reposit ories
​
</dependency>
<dependency>
​
<groupId>org.jboss.component.management</groupId>
​
<artifactId>jboss-dependency-management-all</artifactId>
​
<type>pom</type>
​
<version>6.1.2.Final-redhat-5</version>
​
<scope>import</scope>
​
</dependency>
​ </dependencies>
​< /dependencyManagement>
​
Report a bug
55
Red Hat JBoss BPM Suit e 6 .0 Inst allat ion G uide
Chapter 8. Red Hat JBoss Developer Studio
8.1. Red Hat JBoss Developer St udio
Red Hat JBoss D eveloper Studio is the JBoss integrated development environment (ID E) based on
Eclipse and available from the Red Hat customer support portal at https://access.redhat.com.
JBoss D eveloper Studio provides plug-ins with tools and interfaces for Red Hat JBoss BRMS and
Red Hat JBoss BPM Suite. These plugins are based on the community version of these products. So,
the BRMS plugin is called the D rools plugin and the BPM Suite plugin is called the jBPM plugin.
Refer to the Red Hat JBoss Developer Studio documentation for installation and set-up instructions.
Warning
D ue to an issue in the way multi-byte rule names are handled, you need to ensure that the
instance of JBD S is started with the file encoding set to UT F-8. You can do this by editing the
$JBD S_HO ME/stud i o /jbd evstud i o . i ni file and adding the following property: "D fi l e. enco d i ng = UT F-8"
Report a bug
8.2. Inst alling t he JBoss Developer St udio Plug-ins
The D rools and jBPM plug-ins for JBoss D eveloper Studio are available via the update site.
Pro ced u re 8.1. In st all t h e D ro o ls an d jB PM JB o ss D evelo p er St u d io Plu g - in
1. Start JBoss D eveloper Studio.
2. Select H elp → In st all N ew So f t ware.
3. Click Ad d to enter the Ad d R epo si to ry menu.
4. Give the software site a name next to Name field and add the following url in the Lo cati o n
field: https://devstudio.jboss.com/updates/7.0/integration-stack/
5. Click O K
6. Select the JBo ss Busi ness P ro cess and R ul e D evel o pment feature from the
available options and click Next and then Next again.
7. Read the license and accept it by selecting the appropriate radio button, and click Fi ni sh.
8. After installation of the plug-ins has completed, restart JBoss D eveloper Studio.
Report a bug
8.3. Set t ing t he Drools runt ime
In order to use the JBoss BRMS plug-in with Red Hat JBoss D eveloper Studio, it is necessary to set
up the runtime.
56
⁠Chapt er 8 . Red Hat JBoss Developer St udio
A runtime is a collection of jar files that represent a specific release of the software and provides
libraries needed for compilation and running of your business assets.
Pro ced u re 8.2. C o n f ig u re B R MS R u n t ime
1. Extract the runtime jar files located in the jbo ss-brms-eng i ne. zi p archive of the JBoss
BRMS Generic D eployable zip archive (not the EAP6 deployable zip archive) available from
Red Hat Customer Portal.
2. From the JBoss D eveloper Studio menu, select Wi nd o w and click P references.
3. Select D ro o ls → In st alled D ro o ls R u n t imes.
4. Click Ad d . . . ; provide a name for the new runtime, and click Bro wse to navigate to the
directory where you extracted the runtime files in step 1. Click OK to register the selected
runtime in JBD S.
5. Mark the runtime you have created as the default D rools runtime by clicking on the check box
next to it.
6. Click O K. If you have existing projects, a dialog box will indicate that you have to restart
JBoss D eveloper Studio to update the Runtime.
Report a bug
8.4 . Configuring t he JBoss BPM Suit e Server
JBoss D eveloper Studio can be configured to run the Red Hat JBoss BPM Suite Server.
Pro ced u re 8.3. C o n f ig u re t h e Server
1. Open the jBPM view by selecting Win d o w → O p en Persp ect ive → O t h er and select jBP M
and click O K.
2. Add the server view by selecting Win d o w → Sh o w View → O t h er... and select Server →
Servers.
3. Open the server menu by right clicking the Servers panel and select N ew → Server.
4. D efine the server by selecting JB o ss En t erp rise Mid d leware → JB o ss En t erp rise
Ap p licat io n Plat f o rm 6 .1+ and clicking Next.
5. Set the home directory by clicking the Bro wse button. Navigate to and select the installation
directory for JBoss EAP 6.1.1 which has JBoss BPM Suite installed.
6. Provide a name for the server in the Name field, make sure that the configuration file is set,
and click Fi ni sh.
Report a bug
8.5. Import ing Project s from a Git Reposit ory int o JBoss Developer
St udio
JBoss D eveloper Studio can be configured to connect to a central Git asset repository. The
repository is the space where versions of rules, models, functions and processes are stored. This Git
repository must already be defined by the KIE Workbench.
57
Red Hat JBoss BPM Suit e 6 .0 Inst allat ion G uide
Users can either clone a remote Git repository or import a local Git repository.
Pro ced u re 8.4 . C lo n in g a R emo t e G it R ep o sit o ry
1. Start the Red Hat JBoss BPM Suite server (if not already running) by selecting the server from
the server tab and click the start icon.
2. Simultaneously, start the Secure Shell server, if not running already, by using the following
command. The command is Linux and Mac specific only. On these platforms, if sshd has
already been started, this command will fail and you may safely ignore this step.
/sbin/service sshd start
3. In JBoss D eveloper Studio, select File → Imp o rt ... and navigate to the Git folder. Open the
Git folder to select Pro ject s f ro m G it and click Next.
4. Select the repository source as C lo n e U R I and click Next.
5. Enter the details of the Git repository in the next window and click Next.
58
⁠Chapt er 8 . Red Hat JBoss Developer St udio
Fig u re 8.1. G it R ep o sit o ry D et ails
6. Select which branch you want to import in the following window and click Next.
7. You will be presented with the option to define the local storage for this project. Enter (or
select) a non-empty directory, make any configuration changes and click Next.
8. Import the project as a general project in the following window and click Next. Name the
project and click Fi ni sh.
Pro ced u re 8.5. Imp o rt in g a Lo cal G it R ep o sit o ry
1. Start the Red Hat JBoss BPM Suite server (if not already running) by selecting the server from
the server tab and click the start icon.
2. In JBoss D eveloper Studio, select File → Imp o rt ... and navigate to the Git folder. Open the
Git folder to select Pro ject s f ro m G it and click Next.
59
Red Hat JBoss BPM Suit e 6 .0 Inst allat ion G uide
3. Select the repository source as Exist in g lo cal rep o sit o ry and click Next.
Fig u re 8.2. G it R ep o sit o ry D et ails
4. Select the repository that is to be configured from the list of available repositories and click
Next.
5. In the dialog that opens, select the radio button Imp o rt as g en eral p ro ject from the
Wiz ard f o r p ro ject imp o rt g ro u p and click N ext . Name the project and click Fin ish .
60
⁠Chapt er 8 . Red Hat JBoss Developer St udio
Fig u re 8.3. Wiz ard f o r Pro ject Imp o rt
Report a bug
61
Red Hat JBoss BPM Suit e 6 .0 Inst allat ion G uide
Revision History
R evisio n 1.0.0- 6 0
T h u Mar 12 2015
Vikram G o yal
Built from Content Specification: 22689, Revision: 746986 by vigoyal
62
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement