Chapter 47. Configuring IBM WebSphere Application Server for KIE Server

Procedure

1. In the WebSphere Integrated Solutions Console, click Security → Global Security and ensure that the option Enable Application Security is selected. This may already be selected and overridden at the server level.
2. Click Security Configuration Wizard and click Next.
3. Select the repository that contains the user information. For example, select Federated repositories for local configurations.
4. Click Next
5. Enter the Primary administrative user name and Password.
6. Click Next and then click Finish.

7. Click Save in the Messages window to save your changes to the primary configuration.

   Figure 47.1. Save security changes

   

8. In your command terminal, navigate to the IBM WebSphere Application Server /bin directory location that you specified during installation, and run the following commands to stop and restart IBM WebSphere to apply the security changes:

   sudo ./stopServer.sh <SERVER_NAME>

   sudo ./startServer.sh <SERVER_NAME>

   Replace <SERVER_NAME> with the IBM WebSphere Application Server name defined in Servers → Server Types → IBM WebSphere Application Servers of the WebSphere Integrated Solutions Console.

Procedure

1. Navigate to the Software Downloads page in the Red Hat Customer Portal (login required), and select the product and version from the drop-down options:

   • Product: Process Automation Manager
   • Version: 7.12
2. Download Red Hat Process Automation Manager 7.12.0 Add-Ons.

3. Complete the following steps to prepare your database:

   1. Extract rhpam-7.12.0-add-ons.zip in a temporary directory, for example TEMP_DIR.
   2. Extract TEMP_DIR/rhpam-7.12.0-migration-tool.zip.
   3. Change your current directory to the TEMP_DIR/rhpam-7.12.0-migration-tool/ddl-scripts directory. This directory contains DDL scripts for several database types.

   4. Import the DDL script for your database type into the database that you want to use, for example:

      psql jbpm < /ddl-scripts/postgresql/postgresql-jbpm-schema.sql

      Note

      If you are using PostgreSQL or Oracle in conjunction with Spring Boot, you must import the respective Spring Boot DDL script, for example /ddl-scripts/oracle/oracle-springboot-jbpm-schema.sql or /ddl-scripts/postgresql/postgresql-springboot-jbpm-schema.sql.

4. In the WebSphere Integrated Solutions Console, navigate to Resources → JDBC → Data sources.
5. Select the scope at which applications can use the data source. You can choose a cell, node, cluster, or server.
6. Click New to open the Create a data source wizard.

7. Enter a unique name in the Data source name field and a Java Naming and Directory Interface (JNDI) name in the JNDI name field. The application server uses the JNDI name to bind resource references for an application to this data source.

   Do not assign duplicate JNDI names across different resource types, such as data sources versus J2C connection factories or JMS connection factories.

   Do not assign duplicate JNDI names for multiple resources of the same type in the same scope.

8. Click Next and choose Select an existing JDBC provider if the provider has been created, or choose Create new JDBC provider to define details for a new provider. (Creating the JDBC provider before this point is recommended, as a prerequisite to adding data sources.)
9. On the Enter database specific properties for the data source panel, click Use this data source in container managed persistence (CMP) if container managed persistence (CMP) enterprise beans must access this data source. Then fill in any other database-specific properties.

10. Optional: Configure the security aliases for the data source. You can select None for any of the authentication methods, or choose one of the following types:

    • Component-managed authentication alias: Specifies an authentication alias to use when the component resource reference res-auth value is Application. To define a new alias, navigate to Related Items → J2EE Connector Architecture (J2C) authentication data entries. A component-managed alias represents a combination of ID and password that is specified in an application for data source authentication. Therefore, the alias that you set on the data source must be identical to the alias in the application code.
    • Mapping-configuration alias: Used only in the absence of a login configuration on the component resource reference. The specification of a login configuration and the associated properties on the component resource reference is the preferred way to define the authentication strategy when the res-auth value is set to Container. If you specify the DefaultPrincipalMapping login configuration, the associated property is a JAAS - J2C authentication data entry alias.
    • Container-managed authentication alias: Used only in the absence of a login configuration on the component resource reference. The specification of a login configuration and the associated properties on the component resource reference determines the container-managed authentication strategy when the res-auth value is set to Container.

11. Click Next, review the information for the data source, and click Finish to save the configuration and exit the wizard.

    The Data sources panel displays your new configuration in a table along with any other data sources that are configured for the same scope.

Procedure

1. In the WebSphere Integrated Solutions Console, navigate to Servers → Server Types → IBM WebSphere Application Servers.
2. In the list of application servers, choose the server on which you are going to deploy KIE Server.

3. Under the Server Infrastructure, click Java and Process Management → Process Definition.

   Figure 47.2. WebSphere configuration page

   

4. Under Additional Properties, click Java Virtual Machine.

   Figure 47.3. Process definition configuration page

   

   This opens the configuration properties for the JVM that is used to start IBM WebSphere.

5. Set both the Initial heap size and Maximum heap size to 2048 and click Apply to increase the Java Virtual Machine (JVM) memory size. KIE Server has been tested with these values. If you do not increase the JVM memory size, IBM WebSphere Application Server freezes or causes deployment errors when deploying KIE Server.
6. Under Additional Properties, click Custom Properties.

7. Click New → Custom JVM Properties and add the following properties to IBM WebSphere:

   Table 47.4. System properties for KIE Server

   Name	Value	Description
   kie.server.jms.queues.response	jms/KIE.SERVER.RESPONSE	The JNDI name of JMS queue for responses used by KIE Server.
   org.kie.server.domain	WSLogin	JAAS LoginContext domain used to authenticate users when using JMS.
   org.kie.server.persistence.ds	jdbc/jbpm	Data source JNDI name for KIE Server.
   org.kie.server.persistence.tm	org.hibernate.engine.transaction.jta.platform.internal.WebSphereJtaPlatform	Transaction manager platform for setting Hibernate properties.
   org.kie.server.persistence.dialect	Example: org.hibernate.dialect.H2Dialect	Specifies the Hibernate dialect to be used. Set according to data source.
   org.kie.executor.jms.queue	jms/KIE.SERVER.EXECUTOR	Job executor JMS queue for KIE Server.
   org.kie.executor.jms.cf	jms/cf/KIE.SERVER.EXECUTOR	Job executor JMS connection factory for KIE Server.
   org.kie.server.router	Example: http://localhost:9000	(Optional) Specifies one or more URLs for one or more KIE Server routers (Smart Routers) that the application server is a part of in a clustered KIE Server environment.
   org.jboss.logging.provider	jdk	This property is only required where a CA SiteMinder TAI (SMTAI) is installed in the environment. Using this property forces Hibernate to use JDK instead of log4j for logging within Dashbuilder. CA SiteMinder TAI (SMTAI) contains an old version of log4j, which causes conflicts.

8. Click Save to save the changes to the primary configuration.