Configuring the Scheduler in WebSphere

<< Click to Display Table of Contents >>

Navigation:  Bizagi Engine > Bizagi system administration > Bizagi server configuration > Bizagi Engine JEE platform configuration > Configuring a JEE application server to work with Bizagi > WebSphere configuration > Clustered WebSphere configuration >

Configuring the Scheduler in WebSphere

Overview

In environments with high availability is demanded, and where the solution is set up in a cluster, Bizagi offers the possibility of a manual Scheduler service configuration in order to:

Have this service rely on fault tolerance (so that the service can be executed on any node of the cluster).

Have management options to start, stop or restart the service in an independent manner (possible anytime).

 

 

Prerequisites

To configure the Scheduler service in WebSphere, ensure you meet the following prerequisites:

Have already configured Bizagi in WebSphere.

For more information about this, refer to Clustered WebSphere configuration.

Have at hand the configuration files (used to deploy Bizagi) which are required for the JEE edition (BizAgi-ear-Websphere-dist.zip). These files need to be unzipped in a local path, as referred to in the steps describing how to configure WebSphere to work with Bizagi. This path will be referenced as <CONFIGURATION_INPUTS> from this point on.

 

 

Configuration

Locate the <CONFIGURATION_INPUTS>/BizagiSchedulerService/ path in which configuration files where configured.

 

1. In this path, and inside the bin folder, configure the following properties file scheduler_configuration.properties

For this, consider:

 

bizagi.scheduler.timer: Property used to indicate timer the time interval in which the scheduler should run in Bizagi. The default value is 30 seconds.

bizagi.scheduler.connection.port: The port number assigned to the service by which requests are received. By default the value assigned is 5681.

bizagi.scheduler.remote.connection.retries: property that defines the maximum number of retries to establish communication with the application server ,in case of a connection problem. By default the assigned value is 3.

 

2. Copy EJB client libraries in the path <CONFIGURATION_INPUTS>/BizagiSchedulerService/lib/ext/

These are found in the installation path of the application server:

 

<WAS_HOME>/runtimes/com.ibm.ws.ejb.thinclient_<VERSION>.jar

<WAS_HOME>/runtimes/com.ibm.ws.orb_<VERSION>.jar

 

3. Configure the properties file custom_jndi.properties.

 

java.naming.factory.initial: property for Bizagi exclusive use that defines the client component context that will be used to communicate with WebSphere Application Server. The value of this property is:
com.ibm.websphere.naming.WsnInitialContextFactory

java.naming.provider.url: configurable property to specify the name or IP address of the application server. The value must satisfy the following format:

oConfiguration for a distributed environment, in a horizontal cluster: Defining the list of servers that are part of the cluster with their own port: corbaloc:iiop:[SERVER_NAME]:[PORT1],:[SERVER_NAME]:[PORT2],:[SERVER_NAME]:[PORT3]

oConfiguration for a distributed environment in a vertical cluster: uses the same server name and changes the port number assigned to each virtual node:
corbaloc:iiop:[SERVER_NAME]:[PORT1],:[SERVER_NAME]:[PORT2],:[SERVER_NAME]:[PORT3]

java.naming.security.principal: This property is disabled by default (#). If the application server has application-level security configured for communication with external components, specify the name for the user created.

java.naming.security.credentials: This property is disabled by default (#). If the application server has application-level security configured for communication with external components, specify the password for the user created.

ejb.remote.jndi: property for Bizagi exclusive use which specifies the address (JNDI) used to access remote Scheduler service found in the WebSphere Application Server. The value of this property is: Noice you should change [CLUSTER_NAME] for the value assigned when creating the cluster in:
cell/clusters/[CLUSTER_NAME]/BizAgiSchedulerBean#com.vision.bizagi.scheduler.BizAgiSchedulerRemote

 

 

Service operation

Keep in mind that for the Scheduler's execution, you need to have previously defined these required environment variables: bizagi.cache.multicast.enabled, bizagi.cache.multicast.address, bizagi.cache.multicast.port, and bizagi.cache.multicast.type (as described under the environment variable configuration section when configuring WebSphere to work with Bizagi in a cluster).

 

To start the service, run the start-service as an administrator.

 

In a Unix-like OS such as Linux, this file is located as:

<CONFIGURATION_INPUTS>/BizagiSchedulerService/bin/start-service.sh

In a Windows OS, this file is located as:

<CONFIGURATION_INPUTS>\BizagiSchedulerService\bin\start-service.bat

 

This operation creates a javaw.exe process which keeps running using the port (by default 5681), as configured in the scheduler_configuration.properties.

 

 

To stop the service, run the shutdown-service as an administrator.

 

In a Unix-like OS such as Linux, this file is located as:

<CONFIGURATION_INPUTS>/BizagiSchedulerService/bin/shutdown-service.sh

 

In a Windows OS, this file is located as:

<CONFIGURATION_INPUTS>\BizagiSchedulerService\bin\shutdown-service.bat