Installing and configuring Process Server on IBM WebSphere Application 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 master configuration.

   Figure 4.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>

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

Procedure

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

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

5. 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.)
6. 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.

7. Optionally, 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.

8. 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 Process Server.

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

   Figure 4.2. WebSphere configuration page

   

4. Under Additional Properties, click Java Virtual Machine.

   Figure 4.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. Process 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 Process Server.
6. Under Additional Properties, click Custom Properties.

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

   Table 4.4. System properties for Process Server

   Name	Value	Description
   kie.server.jms.queues.response	jms/queue/KIE.SERVER.RESPONSE	The JNDI name of JMS queue for responses used by Process 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 Process 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/queue/KIE.SERVER.EXECUTOR	Job executor JMS queue for Process Server.
   org.kie.executor.jms.cf	jms/cf/KIE.SERVER.EXECUTOR	Job executor JMS connection factory for Process Server.
   org.kie.server.router	Example: http://localhost:9000	(Optional) Specifies one or more URLs for one or more Process Server routers (Smart Routers) that the application server is part of in a clustered Process 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 master configuration.

Procedure

1. In the WebSphere Integrated Solutions Console, click Users and Groups → Manage Groups.
2. In the Manage Groups screen, click Create.
3. In the Create a Group screen, enter kie-server in the Group name box, then click Create.
4. To create a user to add to the kie-server group, click Users and Groups → Manage Users.
5. In the Create a User screen, complete the required information.
6. Click Group Membership.
7. In the Group Membership screen, click kie-server, move it to Mapped To, and click Close.
8. On the Create a User screen click Create.

Procedure

1. In the WebSphere Integrated Solutions Console, navigate to Applications → Application Types → WebSphere Enterprise Applications and select the newly installed kie-server application.
2. Under Detail Properties, click Security Role to User/Group Mapping.
3. Select the kie-server role and click Map Groups to search for the kie-server group.

4. Move the kie-server group from the Available list to the Selected list and click OK.

   This mapping gives users in the IBM WebSphere Application Server kie-server group access to Process Server.

5. Click Save to complete the mapping.

Procedure

1. Navigate to Applications → Application Types → WebSphere Enterprise Applications and click kie-server.
2. Click Class Loading and Update Detection under the Detail Properties heading on the left.
3. In the properties, change Class Loader Order to Classes loaded with local class loader first (parent last) and WAR Class Loader Policy to Single class loader for application.
4. Save the changes to the master configuration.

Procedure

1. Navigate to Applications → Application Types → WebSphere Enterprise Applications and click kie-server.
2. Click Class Loading and Update Detection under the Detail Properties heading on the left.
3. In the properties, change Class Loader Order to Classes loaded with local class loader first (parent last) and WAR Class Loader Policy to Single class loader for application.
4. Save the changes to the master configuration.

Procedure

1. Specify the following JVM property values on the application server instance where the headless Process Automation Manager controller is installed:

   Table 6.1. Required properties for the headless Process Automation Manager controller

   Name	Requirement
   org.kie.server.user	A user with the kie-server role
   org.kie.server.pwd	The password for the user specified in the org.kie.server.user property

2. Specify the following JVM property values on the application server instance where Process Server is installed:

   Table 6.2. Required properties for Process Server when headless Process Automation Manager controller is installed

   Name	Requirement
   org.kie.server.controller.user	A user with the kie-server role
   org.kie.server.controller.pwd	The password for the user specified for the org.kie.server.controller.user property
   org.kie.server.id	The ID or name of the Process Server installation, such as rhdm700-decision-server-1
   org.kie.server.location	The URL of the Process Server, http://<HOST>:<PORT>/kie-server/services/rest/server
   org.kie.server.controller	The URL of the headless Process Automation Manager controller, http://<HOST>:<PORT>/controller/rest/controller

   <HOST> is the ID or name of the Process Server host, for example, localhost or 192.7.8.9.

   <PORT> is the port of the Process Server host, for example, 7001.

Procedure

1. In the WebSphere Integrated Solutions Console, create the kie-server group and a user for that group, as described in Creating the Process Server group and role.
2. Navigate to Applications → Application Types → WebSphere Enterprise Applications and select the newly installed headless Process Automation Manager controller.
3. Under Detail Properties, click Security Role to User/Group Mapping.
4. Select the kie-server role and click Map Groups to search for the kie-server group.

5. Move the kie-server group from the Available list to the Selected list and click OK.

   This mapping gives the previously created administrator user access to Process Automation Manager.

6. Click Save to complete the mapping.