Red Hat JBoss BPM Suite 6.1 IBM WebSphere Installation and Configuration Guide

Transcription

1 Red Hat JBoss BPM Suite 6.1 IBM WebSphere Installation and Configuration Guide For Red Hat JBoss BPM Suite Red Hat Content Services

2

3 Red Hat JBoss BPM Suite 6.1 IBM WebSphere Installation and Configuration Guide For Red Hat JBoss BPM Suite Red Hat Co ntent Services

4 Legal Notice Copyright 2015 Red Hat, Inc. This do cument is licensed by Red Hat under the Creative Co mmo ns Attributio n- ShareAlike 3.0 Unported License. If you distribute this document, or a modified version of it, you must provide attribution to Red Hat, Inc. and provide a link to the original. If the document is modified, all Red Hat trademarks must be remo ved. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, MetaMatrix, Fedora, the Infinity Logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other co untries. Linux is the registered trademark of Linus Torvalds in the United States and other countries. Java is a registered trademark o f Oracle and/o r its affiliates. XFS is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/o r o ther co untries. MySQL is a registered trademark of MySQL AB in the United States, the European Union and o ther co untries. Node.js is an official trademark of Joyent. Red Hat Software Collections is not formally related to or endorsed by the official Joyent Node.js open source or commercial project. The OpenStack Wo rd Mark and OpenStack Lo go are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not 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 A guide to installing and configuring Red Hat JBoss BPM Suite on IBM WebSphere

5 T able of Cont ent s Table of Contents. Chapt..... er Int... roduct ion Ab o ut Red Hat JBo ss BPM Suite Sup p o rted Platfo rms Use Case: Pro cess -b ased so lutio ns in the lo an ind ustry Ab o ut Red Hat JBo ss BPM Suite fo r IBM Web Sp here 8 3. Chapt..... er Download and... Ext... ract Do wnlo ad Red Hat JBo ss BPM Suite fo r IBM Web Sp here Extract Red Hat JBo ss BPM Suite fo r IBM Web Sp here 8 5. Chapt..... er Configure Increase JVM Heap Size Mo d ify Security Setting s Setup Dataso urce Setup JMS Reso urces Ad d Custo m JVM Pro p erties 12. Chapt..... er Inst.... all.. Red.... Hat.... JBoss BPM.... Suit.... e. on... IBM.... WebSphere Install Business Central Install Dashb uild er Install the Realtime Decisio n Server 17. Revision Hist... ory

6 Red Hat JBoss BPM Suit e 6.1 IBM WebSphere Inst allat ion and Configurat 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 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 with this release. Red Hat JBoss BPM Suite is supported for use with Red Hat Enterprise Linux 7 (RHEL7) 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.4 Red Hat JBoss Web Server 2.1 (Tomcat 7) on JDK 1.7 IBM WebSphere Application Server Oracle WebLogic Server (12c) 1.3. Use Case: Process -based solut ions in t he loan indust ry This section describes a use case of deploying JBoss BPM Suite to automate business processes (such as loan approval process) at a retail bank. This use case is a typical process-based specific deployment that might be the first step in a wider adoption of JBoss BPM Suite throughout an enterprise. It leverages features of both business rules and processes of JBoss BPM Suite. 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. The bank then processes the application in several steps, such as 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 has 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 Designer) in JBoss BPM Suite. Here is the process flow: 2

7 Chapt er 1. Int roduct ion Figure 1.1. High-level loan application process flow Business rules are developed with the rule authoring tools in JBoss 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 JBoss BPM Suite so that the entire loan application process can be automated. Figure 1.2. Loan Application Process Automation 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 About Red Hat JBoss BPM Suit e for IBM WebSphere 8 Red Hat JBoss BPM Suite for IBM WebSphere 8 is provided as two deployable web application archives: business-cental.war and dashbuilder.war. 3

8 Red Hat JBoss BPM Suit e 6.1 IBM WebSphere Inst allat ion and Configurat ion G uide Installation of JBoss BPM Suite on IBM WebSphere is supported from the version of JBoss BPM Suite. In this guide, you will explore how it can be installed on a full profile version of IBM WebSphere 8. Before installation, several configuration steps have to be performed to enable a successful setup. This guide will outline these steps. Before you proceed, ensure you have root access to the server on which IBM WebSphere 8 is installed and that you are able to successfully access IBM WebSphere' s administrative console via a web browser (Usually at As noted earlier, JBoss BPM Suite for IBM WebSphere is distributed as a WAR file. It is then deployed and configured as any other web application. 4

9 Chapt er 2. Download and Ext ract Chapter 2. Download and Extract 2.1. Download Red Hat JBoss BPM Suit e for IBM WebSphere 8 You can download the deployable Red Hat JBoss BPM Suite package file for WebSphere 8 from Red Hat Customer Portal: 1. Go to the Red Hat Customer Portal and log in. 2. Click Downloads. 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 In the table, navigate to R ed Hat JBo ss BP M Sui te 6. 1 D epl o yabl e fo r IBM WebSphere 8. 5 row and then click D o wnl o ad Ext ract Red Hat JBoss BPM Suit e for IBM WebSphere 8 The installation zip file for JBoss BPM Suite that you have just downloaded contains the Business Central WAR deployable (busi ness-central. war) and the D ashbuilder WAR deployable (d ashbui l d er. war) in un-exploded format. Extract the zip file so that you have access to the deployable WAR. 5

10 Red Hat JBoss BPM Suit e 6.1 IBM WebSphere Inst allat ion and Configurat ion G uide Chapter 3. Configure Before JBoss BPM Suite can be deployed as a web archive in IBM WebSphere 8, WebSphere server itself must be configured to accept the deployable. In this section, we will go through the different configuration steps that must be taken before deploying. Login to your WebSphere 8 console using an administrative login before performing any of these steps. The usual login URL is: Increase JVM Heap Siz e With the default JVM heap size, the WebSphere 8 server freezes and/or causes deployment errors when deploying Business Central. Increase the heap size by following these steps: 1. Click on Servers --> Server Types --> WebSphere Application Servers in your WebSphere administrative console. 2. In the list of application servers, click on the server on which you are going to deploy Business Central. This will open up the configuration page for that server. 3. Under Server Infrastructure, click on Java and Process Management and then Process Definition. This will open the JVM process definition page. 4. Click on Java Virtual Machine under the Additional Properties heading. This will open up the configuration properties for the JVM that is used to start WebSphere. 5. Enter a value of 1536 for the maximum heap size changing it from the default of Click Apply at the bottom. 6. You can choose to save these configuration settings to the master WebSphere configuration at this stage. 7. Restart WebSphere at this point or wait till other configuration changes have been made. Deployment Manager Heap Size At this stage, you may want to increase the heap size in the Deployment Manager, if installed and being used. To do so, click on System administration Deployment manager Java and process management Process definition Java virtual machine in your WebSphere administrative console. Enter the maximum heap size and restart the D eployment Manager Modify Securit y Set t ings Several security settings on IBM WebSphere 8 need to be changed and/or confirmed to be in place for the Business Central application to work on WebSphere 8. The following settings enable the container managed authentication mechanisms provided by the WebSphere server. 6

11 Chapt er 3. Configure 1. In WebSphere 8 administrative console, click on Security --> G lobal Security. Ensure that the option Enabl e Appl i cati o n securi ty is checked. This may already be checked and overridden at the server level. 2. Click on C usto m pro perti es and then New to enter a new custom property with the following details: Name: com.ibm.ws.security.web.logoutonhttpsessionexpire and Val ue: true. This property instructs the server to invalidate LTPA tokens on session invalidation, thereby making the logout process consistent across multiple users using the same browser. Click Appl y and then O K. 3. Next, click on Users and G roups --> Manage G roups and create 5 new groups: admin, analyst, developer, manager and user. Note Add the ki e-server group also if you will be installing the Realtime Decision Server. 4. Click on Users and G roups --> Manage Users and create a user (for example: businesscentral-admin) and assign it to the ad mi n user group that was created in the previous step. Note that you should not create users with usernames that are identical to group names. For example, do not create a user with the username of ad mi n. Note You may of course, assign this user to any of the groups that you have just created and in actual production systems you are likely to create separate users for separate groups that align with business roles. The admin group is all encompassing and is therefore useful for the purposes of this setup. 5. Set up session management cust om set t ings Next, click on Servers --> Server Types --> WebSphere Application Servers in your WebSphere administrative console and then select the server on which you are deploying Business Central. 6. Click on Session management --> Custom properties. Click NEW. 7. In the settings page, enter InvalidateOnUnauthorizedSessionRequestException and set its value to true. 8. Click Appl y and then O K Set up Dat asource 7

12 Red Hat JBoss BPM Suit e 6.1 IBM WebSphere Inst allat ion and Configurat ion G uide The Business Central application requires a datasource which must be created prior to the deployment of the actual WAR file. This also means that you must have access to an underlying database that the datasource connects to. Whatever your underlying database, make sure you have the datasource ready. The steps below will help you set this up. 1. Open up the JDBC providers panel by clicking on Resources --> JDBC --> JDBC Providers. 2. Select the scope of this JDBC provider to include your server and node. It cannot be Al l sco pes. Then click the New... button. This will bring up the C reate new JD BC pro vi d er form page. 3. Fill out the form based on the database driver that you have available. If your database is not listed, select O thers D atabase type selection box and provide the implementation class name. For example, for H2, Postgres or MySQL, the implementation class name will be org.h2.jdbcx.jdbcdatasource, org.postgresql.xa.pgxadatasource and com.mysql.jdbc.jdbc2.optional.mysqlconnectionpooldatasource respectively. 4. Make sure to give the JDBC Provider a name that is descriptive and click the Next button. You will be asked to provide the CLASSPATH for the JDBC driver class files that you have just defined. Enter this value and click the Next button to be taken to the summary screen. Click the Finish button to accept and add this new JDBC Provider. Using this new JDBC provider, you will now need to setup the actual datasource for Business Central. Before you create the datasource, however, open up the persi stence. xml file in the Business Central war file that you have downloaded. You will need to know the name of the datasource defined within this file. It is normally jdbc/jbpm. You will also need to change the hibernate.dialect to suit your actual database. For example, if your underlying database is DB2, you would change the this property from o rg. hi bernate. d i al ect. H2D i al ect to o rg. hi bernate. d i al ect. D B2D i al ect. Set t ing up a Dat asource 1. Open up the datasources panel by clicking on Resources --> JDBC --> Data sources in the WebSphere administrative panel. Click the N ew... button making sure the appropriate scope has been selected from the Scope drop-down. 2. Step 1 of the "Create a Data source" form is displayed. Enter a unique Data source name that you will use to refer to this datasource by. The JDBC provider is the one you created earlier in this section, and the JNDI name is the one you looked up from the persi stence. xml file. Click Next and select the JDBC provider created earlier from the drop-down menu. Click Next 2 more times and accept the default values. 3. Click the Finish button to save the changes and then click to save the changes in the master configuration. 4. You will now need to provide the basic meta properties for this datasource. Properties like servername, databasename, username and password must now be defined and vary for different databases. These properties can be defined by editing the datasource just created and then clicking on C usto m pro perti es link under the Additional properties menu. Some example database properties are shown below. For H2 databases, you will need to define the following custom properties: URL user 8

13 Chapt er 3. Configure password For MySQL databases, you will need to define the following custom properties: servername databasename port user password Finally for Postgres databases, you will need to define the following custom properties: servername databasename portnumber user password 5. Once all the connection properties have been defined, click the Test Connection to ensure the validity of the datasource Set up JMS Resources IBM WebSphere 8 must be configured to send and receive JMS messages via Red Hat JBoss BPM Suite. However, before you do this, a Service Bus must be present. Follow the steps below to create a Service Bus if one doesn't already exist. 1. In your IBM WebSphere 8 administrative console, click on Service integration and then the Buses link. All existing Service Buses will be listed. Click the New... button to create a new one. 2. Enter the name of the new Bus, and then uncheck Bus Securi ty. Click Next and then the Finish button to create this Service Bus. You must now add a new Bus member before proceeding ahead. A Bus member is a server or a cluster that has been added to this Service Bus. Add a Bus Member 1. Click on the Service Bus that you have just created. 2. Under the topology section, click on Bus members link. Follow the steps to add a server from a list of available servers within your setup. Creat e JMS Connect ion Fact ories 9

14 Red Hat JBoss BPM Suit e 6.1 IBM WebSphere Inst allat ion and Configurat ion G uide To send and receive messages from JBoss BPM Suite, you will need to create the JMS connection factories - one for receiving messages and one for sending them. Use the steps below twice to create these two factories with the respective JND I names: KIE.RESPONSE.ALL and KIE.INPUT. Note The factory names shown above are suggestions only and you can change them to suit your needs and company guidelines. 1. Open up the Connection factories panel by clicking on Resources --> JMS --> Connection factories. 2. Make sure the correct scope is selected and then click the New button. Select the Default messaging provider option and then click the O K button. 3. Enter the name and JNDI name of this factory and select the Service Bus that you created earlier. The rest of the options are not mandatory and can be left with default values. For example, when using these steps to create the factory for receiving messages, use name as KIE.RESPONSE.ALL and JND I name as jms/conn/kie.response.all. Installing the Realtime Decision Server? If you will be installing the Realtime Decision Server later, add the KIE.SERVER.REQUEST and KIE.SERVER.RESPONSE with the corresponding JND I names: jms/conn/kie.server.request and jms/conn/kie.server.response respectively. 4. Click the Apply button and then click to save to the master configuration. Creat e JMS Queues You will now need to create 4 JMS queues. These queues are your destination end points for pointto-point messaging. You will create: KIE.AUD IT: for asynchronous audit logs. KIE.RESPONSE.ALL: for JBoss BPM Suite responses. KIE.SESSION: for ksession based operations. KIE.TASK: for task based operations. KIE.SERVER.REQUEST: for Realtime D ecision Server requests. KIE.SERVER.RESPONSE: for Realtime D ecision Server responses. Follow the steps below 4 times to create these queues. 1. Click on Resources --> JMS --> Q ueues to open up the JMS Queue panel. Select the scope and then click the New button. 2. Accept the Default messaging provider and click O K. Enter the name (example: KIE.AUDIT), JND I name (example: jms/kie.audit) and the Service Bus created earlier. 10

15 Chapt er 3. Configure Note The deployment artifacts in the busi ness-central. war for WebSphere expect the following JND I names for the JMS queues since they are referenced specifically by configuration files. Make sure you use the following queue names only: jms/kie.task, jms/kie.session, jms/kie.aud IT (and jms/kie.server.request and jms/kie.server.response if installing the Realtime D ecision Server via the ki e- server. war file). 3. When you select the Q ueue name, make sure to select the Create Service Integration bus destination.. This will open up the form for creating a new service integration bus. In this form, you will need to select the Bus member that you created earlier in this section and enter a unique identifier. 4. Apply and then save to master configuration. Creat e JMS Act ivat ion Specificat ions A JMS activation specification is required to be the bridge between the two queues - one mandated by JMS and the other custom implementation provided by IBM' s System Integration Bus. For JBoss BPM Suite, you will need to create three specifications: KIE.AUD IT: for the asynchronous audit log. KIE.SESSION: for ksession based operations. KIE.TASK: for task based operations. KIE.SERVER.REQUEST: for Realtime D ecision Server requests. KIE.SERVER.RESPONSE: for Realtime D ecision Server responses. To create these specifications, follow these steps three times: 1. Click on Resources --> JMS --> Activation specifications to open up the Activation specifications page. 2. Click the New button in the correct scope and accept the Default messaging provider. 3. Enter the name (example: KIE.AUDIT) and the JND I name (jms/activation/kie.audit) and then making sure that Queue is selected as the Destination type, enter the corresponding queue you created in the previous step (example: jms/kie.audit). Installing the Realtime Decision Server? Use KIE.SERVER.REQUEST and KIE.SERVER.RESPONSE as the name and jms/activation/kie.server.request and KIE.SERVER.RESPONSE as the JND I name for installing the Realtime D ecision Server. 4. Select the Service Bus created earlier in the Bus name option, click O K at the bottom with the rest of the field values as default. Click to save to master configuration. You have now successfully completed the JMS configurations required for setting up JBoss BPM 11

16 Red Hat JBoss BPM Suit e 6.1 IBM WebSphere Inst allat ion and Configurat ion G uide Suite on IBM WebSphere Add Cust om JVM Propert ies At this point, you need to add three custom properties to the JVM that is used to start IBM WebSphere 8. These custom properties take into consideration the configuration changes you have made so far. 1. Click on Servers --> Server Types --> WebSphere Application Servers in your WebSphere administrative console. 2. In the list of application servers, click on the server on which you are going to deploy Business Central. This will open up the configuration page for that server. 3. Under Server Infrastructure, click on Java and Process Management and then Process Definition. This will open the JVM process definition page. 4. Click on Java Virtual Machine under the Additional Properties heading. This will open up the configuration properties for the JVM that is used to start WebSphere. 5. Click on Custom properties under Additional Properties. 6. Create the following properties by pressing the New... button. jbpm.ut.jndi.lookup=jta/usertransaction - used to look up user transactions from within non managed threads like timers. kie.services.jms.queues.response=jms/kie.response.all - This is the JND I name of the response queue for JMS remote API that we created earlier. You may have given this a different name then KIE.RESPONSE.ALL. Change if required. kie.services.rest.deploy.async=false - this argument on the command line instructs REST service to use synchronous mode to process deployments. This must be set for IBM WebSphere due to issues with CDI on WebSphere 8.5 and above only. kie.server.jms.queues.response=jms/conn/kie.server.response - For the Realtime D ecision Server. org.jboss.logging.provider=jdk - you only need to set this property if you have C A Si temi nd er T AI (SMT AI) installed in your environment. By setting this property you are forcing Hibernate within Dashbuilder to use JDK instead of log4j for logging. C A Si temi nd er T AI (SMT AI) contains an old version of log4j which causes conflicts. Note JBoss BPM Suite uses an embedded version of GIT for its artifact versioning. This version of GIT uses ports 9418 and 8003 for normal and SSH access, respectively. Make sure that these embedded GIT ports are not already in use in your version of IBM WebSphere. If these ports are being used and you need to change the default GIT ports, then change them by setting the org.uberfire.nio.git.daemon.port and org.uberfire.nio.git.ssh.port properties using the steps described here. 12

17 Chapt er 3. Configure 7. You can choose to save these configuration settings to the master WebSphere configuration at this stage. 8. Restart IBM WebSphere for these changes to take effect. 13

18 Red Hat JBoss BPM Suit e 6.1 IBM WebSphere Inst allat ion and Configurat ion G uide Chapter 4. Install Red Hat JBoss BPM Suite on IBM WebSphere 8 Now that the basic configuration is done and IBM WebSphere 8 is set to deploy JBoss BPM Suite, you can upload the WAR deployable that was extracted earlier. As noted earlier, the JBoss BPM Suite zip file for IBM WebSphere 8 contains the deployable WAR files for both Business Central and D ashbuilder. Let' s start with Business Central Inst all Business Cent ral Business Central is uploaded as a Web archive and then accessed by a familiar URL: Start this deployment by installing the Business Central WAR as a WebSphere Application. 1. In your IBM WebSphere 8 administrative console, open up Applications --> Application Types --> WebSphere enterprise applications. This will show you all the existing applications in the system and allow you to install a new one. 2. Click the Install button to start the process. 3. Upload the Business Central war file (busi ness-central. war) from the local file system. See Section 2.2, Extract Red Hat JBoss BPM Suite for IBM WebSphere 8. This process may take some time. 4. Accept the default choices for most of the options presented including choosing the Fast Pat h option. 5. Change Application name to be business-central in Step 1 and click Next. 6. In Step 2, map the Business Central modules to servers depending upon your requirements. 7. In Step 3, enter the JMS Activation JNDI names you created earlier for each of the three beans: For Ki esessi o nr eq uesmessag ebean, enter jms/acti vati o n/kie. SESSIO N for Target Resource JNDI Name For T askservi cer eq uesmessag ebean, enter jms/acti vati o n/kie. T ASK for Target Resource JNDI Name For JMSAud i tp ro cesso r, enter jms/acti vati o n/kie. AUD IT for Target Resource JNDI Name 8. In Step 4 where you have to map resource references to actual resources, you will be asked for the JNDI name for two beans: Ki esessi o nr eq uesmessag ebean and T askservi cer eq uesmessag ebean. Enter the JNDI name for the KIE. R ESP O NSE. ALL connection factory that you created earlier: jms/co nn/kie. R ESP O NSE. ALL. 9. Accept the default values for rest of the options and set the context root to: busi nesscentral. Click the Finish button to install Business Central at the Summary page. This process will take a while. Choose to save to the master configuration at the end of this process. 14

19 Chapt er 4. Inst all Red Hat JBoss BPM Suit e on IBM WebSphere You will be returned to the WebSphere enterprise applications page where businesscentral will be a new application listed. However, this application will be stopped at this stage. Before you start it, there are a few application configuration options that need to be done. 11. Map Groups t o Roles Click on the business-central application and open up this applications configuration page. Click on Security role to user/group mapping. Select the ad mi n role, click Map G ro ups..., search for the ad mi n group in the next screen (or just press the Search button) and move it from the Avai l abl e l i st to the Sel ected l i st. Click O K. Mapping this will give the admin user that we created earlier (busi nesscentral -ad mi n) access to the Business Central application. Do the same for the anal yst role and save the configuration. If you have other groups or users that should have access to Business Central, use the same steps to map them to the ad mi n or anal yst roles, or any other roles that you have (d evel o per, manag er or user). Note Give this user access to the ki e-server role if you are also installing the Realtime D ecision Server. 12. Classloading Configurat ion Ensure by going to the Class loading and update detection setting for your businesscentral application that the parameters C l asses l o ad ed wi th l o cal cl ass l o ad er fi rst (parent l ast) and Si ng l e cl ass l o ad er fo r appl i cati o n are checked. 13. Click the O K button, choose to save to master configuration and restart the WebSphere server. 14. Enable Bouncy Cast le Crypt o API To enable GIT SSH repository cloning and ki e-co nfi g -cl i from within Business Central, the Bouncy Castle Crypto API must be setup. Enable this API by following these steps: a. Set the org.apache.sshd.registerbouncycastle property to true and org.uberfire.domain property to WSLo g i n. These are custom properties so see Section 3.5, Add Custom JVM Properties for details on how to set them. b. Setup the Bouncy Castle API as a shared library referenced from Business Central using the appropriate version of Bouncy Castle: a. Navigate to Environment Shared Libraries, choose your scope and then click on the New button to create a new library. Give this library a name and set the classpath to the Bouncy Castle library (bcpro v-jd k jar). Click O k and save the configuration. b. Navigate to Applications Application Types. Open up WebSphere enterprise applications and then click the Business Central application that you have just installed. Click on Shared l i brary references, select 15

20 Red Hat JBoss BPM Suit e 6.1 IBM WebSphere Inst allat ion and Configurat ion G uide the web module, click on R eference shared l i brari es and select the Bouncy Castle library created in the previous step. Click the O k button and save the configuration. You have now successfully installed Business Central on IBM WebSphere 8. Start the application by going back to Applications --> WebSphere enterprise applications page and then selecting busi ness-central checkbox before clicking on the St art button. To access the application, navigate to Inst all Dashbuilder Dashbuilder for IBM WebSphere 8 is distributed as a deployable WAR file. To install it, please follow these steps: 1. Configure a Dat asource Follow the steps outlined in Section 3.3, Setup Datasource to install a datasource for Dashbuilder. In the step where you have to provide a datasource name, specify jd bc/d ashbui l d er. 2. Deploy Dashbuilder app Follow the steps outlined in Section 4.1, Install Business Central and use the datasource created in the previous step by uploading the dashbuilder.war file from your local file system extracted as part of the JBoss BPM Suite download. You will not need to specify any JMS settings. Make sure to setup the context path as d ashbui l d er. 3. Set up users and roles As with Business Central, D ashbuilder uses container managed authentication and authorization. To be able to login to Dashbuilder, you will need to create two user roles: ad mi n and user. 4. Creat e Users Click on Users and G roups and then Manage Users. Create a new user. If you create a user with the ro o t username, he will be granted all the permissions within the Dashbuilder application. 5. Map Dashbuilder Users t o WebShpere Users Click on Security role to user/group mapping within the Dashbuilder application. Select a role (ad mi n or user - which you would have created for Business Central) and then click on Map Users.. button. Map the users created in the previous steps to the roles that you want to assign them. 6. Save and rest art 16

21 Chapt er 4. Inst all Red Hat JBoss BPM Suit e on IBM WebSphere 8 Save the changes to the master configuration and restart the server. 7. Login t o Dashbuilder You can now login to D ashbuilder using this URL and the user that you have created in the above steps Inst all t he Realt ime Decision Server The Realtime Decision Server is distributed as a web application archive (WAR) file with the name of ki e-server. war and is present in your IBM WebSphere download. To install it, follow these steps: Note It is assumed here that you have followed the steps to create the role ki e-server, required by the D ecision Server when you were installing Business Central. Similarly, you have created the JMS connection factories, queues and activation specifications required by the D ecision Server. If you haven't done so, revisit the respective section in this guide. 1. In your IBM WebSphere 8 administrative console, open up Applications --> Application Types --> WebSphere enterprise applications. This will show you all the existing applications in the system and allow you to install a new one. 2. Click the Install button to start the process. 3. Upload the D ecision Server WAR file (ki e-server. war) from the local file system. 4. Accept the default choices for most of the options presented including choosing the Fast Pat h option. 5. Change Application name to kie-server in Step 1 and click Next. 6. In Step 2, map the KIE Server modules to servers depending upon your requirements. 7. In Step 3, enter the JMS Activation JNDI names you created earlier: Enter jms/acti vati o n/kie. SER VER. R EQ UEST for Target Resource JNDI Name 8. In Step 4 where you have to map resource references to actual resources, enter the JNDI name for the KIE. SER VER. R EQ UEST connection factory that you created earlier: jms/co nn/kie. SER VER. R EQ UEST. 9. Accept the default values for rest of the options and set the context root to: ki e-server. Click the Finish button to install the Decision Server. Choose to save to the master configuration at the end of this process. 10. Navigate to Applications --> Application Types --> WebSphere enterprise applications and then click on ki e-server (this should be in the stopped state). This will show you the specific application settings. Click on T arg et speci fi c appl i cati o n status and then server1 (or the server that you installed this on). In the properties, change ClassLoader Policy to Si ng l e and Class Loading Mode to "Classes loaded with local class loader first (parent last)". Save this configuration. 17

22 Red Hat JBoss BPM Suit e 6.1 IBM WebSphere Inst allat ion and Configurat ion G uide 11. If you have already mapped the ki e-server role to a user/group, you may ignore this step, otherwise, go back to the main configuration page for this newly installed server application. Click on Security role to user/group mapping. Select the ki e-server role, click Map G ro ups..., search for the ad mi n group in the next screen (or just press the Search button) and move it from the Avai l abl e l i st to the Sel ected l i st. Click O K. Mapping this will give the admin user that we created earlier (for example, busi ness-central -ad mi n) access to the Realtime D ecision Server 12. Save and start the ki e-server application. You can check whether the Realtime Decision Server REST API works by sending a GET request at 18

23 Revision Hist ory Revision History Revision Thu Apr Vikram G oyal Built from Content Specification: 22836, Revision: by vigoyal 19