Chapter 3. ConfigureBefore JBoss BPM Suite can be deployed as a web archive in IBM WebSphere 8, WebSphere serveritself must be configured to accept the deployable. In this section, we will go through the differentconfiguration steps that must be taken before deploying.Login to your WebSphere 8 console using an administrative login before performing any of thesesteps. The usual login URL is: http://target-server:9060/ibm/console.

3.1. Increase JVM Heap SizeWith the default JVM heap size, the WebSphere 8 server freezes and/or causes deployment errorswhen deploying Business Central. Increase the heap size by following these steps:1. Click on Servers --> Server T yp es --> Web Sp h ere Ap p licat io n Servers in yourWebSphere administrative console.2. In the list of application servers, click on the server on which you are going to deployBusiness Central. This will open up the configuration page for that server.3. Under Server In f rast ru ct u re, click on Java an d Pro cess Man ag emen t and thenPro cess Def in it io n . This will open the JVM process definition page.4. Click on Java Virt u al Mach in e under the Additional Properties heading. This will open upthe 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 1024. ClickApply at the bottom.

6. You can choose to save these configuration settings to the master WebSphere configurationat this stage.7. Restart WebSphere at this point or wait till other configuration changes have been made.

Deployment Manager Heap SizeAt this stage, you may want to increase the heap size in the D eployment Manager, if installedand being used. To do so, click on Syst em ad min ist rat io n → Dep lo ymen t man ag er →Java an d p ro cess man ag emen t → Pro cess d ef in it io n → Java virt u al mach in e in yourWebSphere administrative console. Enter the maximum heap size and restart the D eploymentManager.

3.2. Modify Securit y Set t ingsSeveral security settings on IBM WebSphere 8 need to be changed and/or confirmed to be in placefor the Business Central application to work on WebSphere 8. The following settings enable thecontainer managed authentication mechanisms provided by the WebSphere server.Red Hat JBoss BPM Suit e 6 .1 IBM WebSphere Inst allat ion and Configurat ion G uide61. In WebSphere 8 administrative console, click on Secu rit y --> G lo b al Secu rit y. Ensure thatthe option Enabl e Appl i cati o n securi ty is checked. This may already be checked andoverridden at the server level.

2. Click on C usto m pro perti es and then New to enter a new custom property with thefollowing details: Name: com.ibm.ws.security.web.logoutOnHTTPSessionExpireand Val ue: true. This property instructs the server to invalidate LTPA tokens on sessioninvalidation, thereby making the logout process consistent across multiple users using thesame browser.

Click Appl y and then O K.3. Next, click on Users an d G ro u p s --> Man ag e G ro u p s and create 5 new groups: admin,analyst, developer, manager and user.

Add the ki e-server group also if you will be installing the Realtime D ecision Server.4. Click on Users an d G ro u p s --> Man ag e 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. Forexample, 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 createdand in actual production systems you are likely to create separate users for separategroups that align with business roles. The admin group is all encompassing and istherefore useful for the purposes of this setup.5. Set up session management cust om set t ingsNext, click on Servers --> Server T yp es --> Web Sp h ere Ap p licat io n Servers in yourWebSphere administrative console and then select the server on which you are deployingBusiness Central.6. Click on Sessio n man ag emen t --> Cu st o m p ro p ert ies. Click NEW.7. In the settings page, enter InvalidateOnUnauthorizedSessionRequestException andset its value to true.

8. Click Appl y and then O K.

3.3. Set up Dat asourceChapt er 3. Configure7The Business Central application requires a datasource which must be created prior to thedeployment of the actual WAR file. This also means that you must have access to an underlyingdatabase that the datasource connects to. Whatever your underlying database, make sure you havethe datasource ready. The steps below will help you set this up.1. Open up the JD BC providers panel by clicking on Reso u rces --> JDBC --> JDBCPro vid ers.2. Select the scope of this JD BC provider to include your server and node. It cannot be Al lsco pes. Then click the New... button. This will bring up the C reate new JD BC pro vi d erform page.

3. Fill out the form based on the database driver that you have available. If your database is notlisted, select O thers D atabase type selection box and provide the implementation classname. For example, for H2, Postgres or MySQL, the implementation class name will beorg.h2.jdbcx.JdbcDataSource, org.postgresql.xa.PGXADataSource andcom.mysql.jdbc.jdbc2.optional.MysqlConnectionPoolDataSource respectively.4. Make sure to give the JD BC Provider a name that is descriptive and click the Next button.You will be asked to provide the CLASSPATH for the JD BC driver class files that you havejust defined. Enter this value and click the Next button to be taken to the summary screen.Click the Fin ish button to accept and add this new JD BC Provider.Using this new JD BC provider, you will now need to setup the actual datasource for BusinessCentral. Before you create the datasource, however, open up the persi stence. xml file in theBusiness Central war file that you have downloaded. You will need to know the name of thedatasource 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 yourunderlying database is D B2, you would change the this property fromo 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 asource1. Open up the datasources panel by clicking on Reso u rces --> JDBC --> Dat a so u rces inthe WebSphere administrative panel. Click the New... button making sure the appropriatescope has been selected from the Scope drop-down.2. Step 1 of the " Create a D ata source" form is displayed. Enter a unique D ata source name thatyou will use to refer to this datasource by. The JD BC provider is the one you created earlier inthis section, and the JND I name is the one you looked up from the persi stence. xml file.

Click Next and select the JD BC provider created earlier from the drop-down menu. Click Next2 more times and accept the default values.

3. Click the Fin ish button to save the changes and then click to save the changes in the masterconfiguration.4. You will now need to provide the basic meta properties for this datasource. Properties likeservername, databasename, username and password must now be defined and vary fordifferent databases. These properties can be defined by editing the datasource just createdand then clicking on C usto m pro perti es link under the Ad d it io n al p ro p ert ies menu.Some example database properties are shown below.

For H2 databases, you will need to define the following custom properties:URLuserRed Hat JBoss BPM Suit e 6 .1 IBM WebSphere Inst allat ion and Configurat ion G uide8passwordFor MySQL databases, you will need to define the following custom properties:serverNamedatabaseNameportuserpasswordFinally for Postgres databases, you will need to define the following custom properties:serverNamedatabaseNameportNumberuserpassword5. Once all the connection properties have been defined, click the T est Co n n ect io n to ensurethe validity of the datasource.

3.4 . Set up JMS ResourcesIBM WebSphere 8 must be configured to send and receive JMS messages via Red Hat JBoss BPMSuite. However, before you do this, a Service Bus must be present. Follow the steps below to create aService Bus if one doesn't already exist.1. In your IBM WebSphere 8 administrative console, click on Service in t eg rat io n and then theBu ses link. All existing Service Buses will be listed. Click the New... button to create a newone.2. Enter the name of the new Bus, and then uncheck Bus Securi ty. Click Next and then theFin ish button to create this Service Bus.

You must now add a new Bus member before proceeding ahead. A Bus member is a server or acluster that has been added to this Service Bus.

Add a Bus Member1. Click on the Service Bus that you have just created.2. Under the topology section, click on Bu s memb ers link. Follow the steps to add a serverfrom a list of available servers within your setup.

Creat e JMS Connect ion Fact oriesChapt er 3. Configure9To send and receive messages from JBoss BPM Suite, you will need to create the JMS connectionfactories - one for receiving messages and one for sending them. Use the steps below twice to createthese two factories with the respective JND I names: KIE.RESPONSE.ALL and KIE.INPUT.NoteThe factory names shown above are suggestions only and you can change them to suit yourneeds and company guidelines.1. Open up the Connection factories panel by clicking on Reso u rces --> JMS -->Co n n ect io n f act o ries.2. Make sure the correct scope is selected and then click the New button. Select the Def au ltmessag in g p ro vid er option and then click the O K button.3. Enter the name and JND I name of this factory and select the Service Bus that you createdearlier. The rest of the options are not mandatory and can be left with default values. Forexample, when using these steps to create the factory for receiving messages, use name asKIE.RESPONSE.ALL and JND I name as jms/conn/KIE.RESPONSE.ALL.Installing the Realtime Decision Server?If you will be installing the Realtime D ecision Server later, add theKIE.SERVER.REQUEST and KIE.SERVER.RESPONSE with the corresponding JND Inames: jms/conn/KIE.SERVER.REQUEST and jms/conn/KIE.SERVER.RESPONSErespectively.

4. Click the Ap p ly button and then click to save to the master configuration.

Creat e JMS QueuesYou 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 Reso u rces --> JMS --> Q u eu es to open up the JMS Queue panel. Select thescope and then click the New button.2. Accept the Def au lt messag in g p ro vid er and click O K. Enter the name (example:KIE.AUDIT), JND I name (example: jms/KIE.AUDIT) and the Service Bus created earlier.Red Hat JBoss BPM Suit e 6 .1 IBM WebSphere Inst allat ion and Configurat ion G uide10NoteThe deployment artifacts in the busi ness-central . war for WebSphere expect thefollowing JND I names for the JMS queues since they are referenced specifically byconfiguration 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 andjms/KIE.SERVER.RESPONSE if installing the Realtime D ecision Server via the ki eserver.

war file).3. When you select the Q u eu e n ame, make sure to select the Creat e Service In t eg rat io nb u s d est in at io n .. This will open up the form for creating a new service integration bus. Inthis form, you will need to select the Bus member that you created earlier in this section andenter a unique identifier.

4. Apply and then save to master configuration.Creat e JMS Act ivat ion Specificat ionsA JMS activation specification is required to be the bridge between the two queues - one mandatedby JMS and the other custom implementation provided by IBM's System Integration Bus. For JBossBPM 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 Reso u rces --> JMS --> Act ivat io n sp ecif icat io n s to open up the Activationspecifications page.2. Click the New button in the correct scope and accept the Def au lt messag in g p ro vid er.3. Enter the name (example: KIE.AUDIT) and the JND I name (jms/activation/KIE.AUDIT) and thenmaking sure that Queue is selected as the Dest in at io n t yp e, enter the corresponding queueyou 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 forinstalling the Realtime D ecision Server.4. Select the Service Bus created earlier in the Bu s n ame option, click O K at the bottom withthe 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 BPMSuite on IBM WebSphere 8.

3.5. Add Cust om JVM Propert iesAt this point, you need to add three custom properties to the JVM that is used to start IBM WebSphere8. These custom properties take into consideration the configuration changes you have made so far.1. Click on Servers --> Server T yp es --> Web Sp h ere Ap p licat io n Servers in yourWebSphere administrative console.2. In the list of application servers, click on the server on which you are going to deployBusiness Central. This will open up the configuration page for that server.3. Under Server In f rast ru ct u re, click on Java an d Pro cess Man ag emen t and thenPro cess Def in it io n . This will open the JVM process definition page.4. Click on Java Virt u al Mach in e under the Additional Properties heading. This will open upthe configuration properties for the JVM that is used to start WebSphere.5. Click on Cu st o m p ro p ert ies 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 withinnon managed threads like timers.

kie.services.jms.queues.response=jms/KIE.RESPONSE.ALL - This is the JND I name of theresponse queue for JMS remote API that we created earlier. You may have given this adifferent name then KIE.RESPONSE.ALL. Change if required.

kie.services.rest.deploy.async=false - this argument on the command line instructs RESTservice to use synchronous mode to process deployments. This must be set for IBM

WebSphere due to issues with CD I on WebSphere 8.5 and above only.

kie.server.jms.queues.response=jms/conn/KIE.SERVER.RESPONSE - For the RealtimeD ecision Server.

org.jboss.logging.provider=jdk - you only need to set this property if you have C ASi teMi nd er T AI (SMT AI) installed in your environment. By setting this property youare forcing Hibernate within D ashbuilder to use JD K instead of log4j for logging. C ASi teMi nd er T AI (SMT AI) contains an old version of log4j which causes conflicts.

7. You can choose to save these configuration settings to the master WebSphere configurationat this stage.8. Restart IBM WebSphere for these changes to take effect.

Chapter 4. Install Red Hat JBoss BPM Suite on IBM WebSphere8Now 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 filesfor both Business Central and D ashbuilder.Let's start with Business Central.

4 .1. Inst all Business CentralBusiness Central is uploaded as a Web archive and then accessed by a familiar URL: http://targetserver/business-central. Start this deployment by installing the Business Central WAR as a

WebSphere Application.1. In your IBM WebSphere 8 administrative console, open up Ap p licat io n s --> Ap p licat io nT yp es --> Web Sp h ere en t erp rise ap p licat io n s. This will show you all the existingapplications in the system and allow you to install a new one.2. Click the In st all 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 maytake some time.

Getting error in logs-Failed to create trmporary file in system defined temporary location (java.io.tmpdir) [ /tmp ]

Got this error while deploying-

bm.ws.ffdc.impl.FfdcProvider@b3afe9e9 aborted, Exception follows[6/15/15 17:48:26:681 IST] 00000081 ServletWrappe E com.ibm.ws.webcontainer.servlet.ServletWrapper service Uncaught service() exception thrown by servlet action: java.lang.NoClassDefFoundError: org/eclipse/hyades/logging/events/cbe/util/EventHelpers at org.eclipse.hyades.logging.java.CommonBaseEventLogRecord.setThrown(CommonBaseEventLogRecord.java:1660) at com.ibm.ws.logging.object.CBEWsLogRecordAdapter.setThrown(CBEWsLogRecordAdapter.java:155) at com.ibm.ws.logging.object.WsLogRecordFactory.createWsLogRecord(WsLogRecordFactory.java:558) at com.ibm.ws.logging.WsLogger.createLogRecord(WsLogger.java:447) at com.ibm.ws.logging.WsLogger.logp(WsLogger.java:624) at com.ibm.ffdc.impl.Ffdc.setFailsafeProvider(Ffdc.java:142) at com.ibm.ffdc.impl.Ffdc.log(Ffdc.java:227) at com.ibm.ws.management.util.RasUtils.logException(RasUtils.java:163) at com.ibm.ws.management.util.RasUtils.logException(RasUtils.java:73)

at com.ibm.ws.management.application.client.AppInstallHelper.createEarWrapper(AppInstallHelper.java:1056) at com.ibm.ws.management.application.client.AppInstallHelper.createEarWrapper(AppInstallHelper.java:853) at com.ibm.ws.management.application.client.AppInstallHelper.createEarWrapper(AppInstallHelper.java:798) at com.ibm.ws.console.appmanagement.action.UploadAction.formUpload(UploadAction.java:470) at com.ibm.ws.console.appmanagement.action.UploadAction.execute(UploadAction.java:140) at org.apache.struts.action.RequestProcessor.processActionPerform(Unknown Source) at org.apache.struts.action.RequestProcessor.process(Unknown Source) at org.apache.struts.action.ActionServlet.process(Unknown Source) at org.apache.struts.action.ActionServlet.doPost(Unknown Source) at javax.servlet.http.HttpServlet.service(HttpServlet.java:595) at javax.servlet.http.HttpServlet.service(HttpServlet.java:668) at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1230) at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:779) at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:478) at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:178) at com.ibm.ws.webcontainer.filter.WebAppFilterChain.invokeTarget(WebAppFilterChain.java:136) at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:97) at com.ibm.ws.console.core.servlet.WSCUrlFilter.setUpCommandAssistance(WSCUrlFilter.java:955) at com.ibm.ws.console.core.servlet.WSCUrlFilter.continueStoringTaskState(WSCUrlFilter.java:504) at com.ibm.ws.console.core.servlet.WSCUrlFilter.doFilter(WSCUrlFilter.java:325) at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:195) at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:91) at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:960) at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:1064) at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3878) at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:304) at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:981) at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1662) at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:200) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:461) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:528) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:314) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:285)

at com.ibm.ws.ssl.channel.impl.SSLConnectionLink.determineNextChannel(SSLConnectionLink.java:1049) at com.ibm.ws.ssl.channel.impl.SSLConnectionLink$MyReadCompletedCallback.complete(SSLConnectionLink.java:643) at com.ibm.ws.ssl.channel.impl.SSLReadServiceContext$SSLReadCompletedCallback.complete(SSLReadServiceContext.java:1818) at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:175) at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217) at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161) at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138) at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204) at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775) at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1864)

[6/15/15 17:48:26:847 IST] 00000081 SystemOut O WSCUrlFilter exception using CSRFResponseWrapper: com.ibm.websphere.servlet.error.ServletErrorReport: java.lang.NoClassDefFoundError: org/eclipse/hyades/logging/events/cbe/util/EventHelpers[6/15/15 17:48:26:809 IST] 00000081 FfdcProvider W com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted on /clasctl/was85/IBM/WebSphere/AppServer/profiles/APPSERVBPMS6/logs/ffdc/server1_2885ec91_15.06.15_17.48.26.6863164298315441885258.txt com.ibm.ws.webcontainer.servlet.ServletInstance.service 290[6/15/15 17:48:26:845 IST] 00000081 FfdcProvider W com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted on /clasctl/was85/IBM/WebSphere/AppServer/profiles/APPSERVBPMS6/logs/ffdc/server1_2885ec91_15.06.15_17.48.26.8122542667150834120327.txt com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter 82

On deploying next time after clearing cache and log files, it gets deployed but this error used to come in logs[6/15/15 19:08:46:551 IST] 0000007e wtp E org.eclipse.jst.j2ee.commonarchivecore.internal.impl.CommonarchiveFactoryImpl createTempZipFileStrategyIfPossible Failed to create temporary file in system defined temporary location (java.io.tmpdir) [ /tmp ].Failed to create temporary file.A nested strategy will be used, but this usually slows performance dramatically.

4. Accept the default choices for most of the options presented including choosing the FastPat 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 JND I names you created earlier for each of the threebeans:For Ki eSessi o nR eq uesMessag eBean, enter jms/acti vati o n/KIE. SESSIO N forTarget Resource JNDI NameFor T askServi ceR eq uesMessag eBean, enter jms/acti vati o n/KIE. T ASK forTarget Resource JNDI NameFor JMSAud i tP ro cesso r, enter jms/acti vati o n/KIE. AUD IT for Target ResourceJNDI Name

8. In Step 4 where you have to map resource references to actual resources, you will be askedfor the JND I name for two beans: Ki eSessi o nR eq uesMessag eBean andT askServi ceR eq uesMessag eBean. Enter the JND I name for the KIE. R ESP O NSE. ALLconnection 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 Fin ish button to install Business Central at the Summary page. Thisprocess will take a while. Choose to save to the master configuration at the end of thisprocess.

Red Hat JBoss BPM Suit e 6 .1 IBM WebSphere Inst allat ion and Configurat ion G uide1410. You will be returned to the Web Sp h ere en t erp rise ap p licat io n s page where businesscentralwill 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 RolesClick on the business-central application and open up this applications configuration page.

Click on Secu rit y ro le t o u ser/g ro u p map p in g .

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 ectedl 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.

D o 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 samesteps 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).

Give this user access to the ki e-server role if you are also installing the RealtimeD ecision Server.12. Classloading Configurat ionEnsure by going to the Class lo ad in g an d u p d at e d et ect io n setting for your businesscentralapplication that the parameters C l asses l o ad ed wi th l o cal cl ass l o ad erfi 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 WebSphereserver.14. Enable Bouncy Cast le Crypt o APITo 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 andorg.uberfire.domain property to WSLo g i n. These are custom properties so seeSection 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 Centralusing the appropriate version of Bouncy Castle:a. Navigate to En viro n men t → Sh ared Lib raries, choose your scope andthen click on the New button to create a new library. Give this library a nameand set the classpath to the Bouncy Castle library (bcpro v-jd k16 -

1. 4 6 . jar). Click O k and save the configuration.

b. Navigate to Ap p licat io n s → Ap p licat io n T yp es. Open up Web Sp h ereen t erp rise ap p licat io n s and then click the Business Central applicationthat you have just installed. Click on Shared l i brary references, selectthe web module, click on R eference shared l i brari es and select theBouncy Castle library created in the previous step. Click the O k button andsave the configuration.

You have now successfully installed Business Central on IBM WebSphere 8. Start the application bygoing back to Ap p licat io n s --> Web Sp h ere en t erp rise ap p licat io n s page and then selectingbusi ness-central checkbox before clicking on the St art button.

Error-[6/15/15 18:58:08:946 IST] 00000090 EJBMDOrchestr E CNTR0126E: The KieSessionRequesMessageBean message-driven bean (MDB) class does not define a message listener interface.[6/15/15 18:58:08:994 IST] 00000090 DeployedAppli W WSVR0206E: Module, business-central.war, of application, business-central.ear/deployments/business-central, failed to start[6/15/15 18:58:09:002 IST] 00000090 ApplicationMg W WSVR0101W: An error occurred starting, business-central[6/15/15 18:58:09:004 IST] 00000090 ApplicationMg A WSVR0217I: Stopping application: business-central[6/15/15 18:58:09:160 IST] 00000090 ApplicationMg A WSVR0220I: Application stopped: business-central[6/15/15 18:58:09:169 IST] 00000090 CompositionUn E WSVR0194E: Composition unit WebSphere:cuname=business-central in BLA WebSphere:blaname=business-central failed to start.[6/15/15 18:58:09:218 IST] 00000090 FfdcProvider W com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted on /clasctl/was85/IBM/WebSphere/AppServer/profiles/APPSERVBPMS6/logs/ffdc/server1_9a2c6ff4_15.06.15_18.58.09.1724241233134874507775.txt com.ibm.ws.runtime.component.CompositionUnitMgrImpl 679[6/15/15 18:58:09:315 IST] 00000090 FfdcProvider W com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted on

/clasctl/was85/IBM/WebSphere/AppServer/profiles/APPSERVBPMS6/logs/ffdc/server1_9a2c6ff4_15.06.15_18.58.09.2202188169733989674880.txt com.ibm.ws.management.AdminServiceImpl.invoke 679[6/15/15 18:58:09:323 IST] 00000090 MBeanHelper E Could not invoke an operation on object: WebSphere:name=ApplicationManager,process=server1,platform=proxy,node=indekgg4grm-1Node01,version=8.5.5.3,type=ApplicationManager,mbeanIdentifier=ApplicationManager,cell=indekgg4grm-1Node01Cell,spec=1.0 because of an mbean exception: com.ibm.ws.exception.RuntimeWarning: Error while processing references for EJB-in-WAR: com.ibm.ejs.container.EJBConfigurationException: The KieSessionRequesMessageBean message-driven bean (MDB) class does not define a message listener interface.[6/15/15 18:58:09:783 IST] 00000090 ServletWrappe I com.ibm.ws.webcontainer.servlet.ServletWrapper init SRVE0242I: [isclite] [/ibm/console] [/secure/javascriptToSession.jsp]: Initialization successful.To access the application, navigate to http://target-server/business-central.