Standard Weblogic configuration

<< 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 > Weblogic configuration >

Standard Weblogic configuration

Overview

When using Bizagi Engine in a JEE platform, your processes can be configured to run in different JEE Application servers, such as WebSphere, WebLogic, or JBoss.

The configuration procedure for each Application Server to work with Bizagi, may slightly vary according to each server's differences.

This section focuses in WebLogic configuration to work with Bizagi, meant for a Test or Production environment and as a standalone instance (no load balancing).

 

Bizagi_Weblogic_standard

 

 

 

If you wish to setup your WebLogic in a high availability schema and use load balancing, refer to Clustered Weblogic configuration.

 

 

Note that for the Development environment (Bizagi Studio), no configuration steps are required given that Bizagi JEE Edition installs a bundled JBoss Server which is automatically configured.

Using the bundled JBoss in the Development environment will promote agility in the project's implementation (given that JBoss is light-weight, it will start up or restart faster, and it will not require additional/manual configuration).

However, if your project strictly needs to use Weblogic in the Development environment, follow the steps described below as well.

 

Prerequisites

To configure your Weblogic Application Server in a Test or Production environment, the following are required:

Installed JAVA SE's JDK. It is strongly recommended to use JDK 7.

JAVA_HOME environment variable properly configured (it is recommended that this path contains no spaces):

 

JavaHome

 

Have at hand the configuration and deployment files delivered by Bizagi (BizAgi-ear-Weblogic-dist.zip).

It is required that this BizAgi-ear-Weblogic-dist.zip (provided when downloading Bizagi Engine JEE Weblogic) matches the version you used in your development environment (i.e Bizagi Studio's version and JEE Plugin).

Installed Weblogic Server version 12c R1.

The supported Weblogic version is 12.1.3.

Weblogic can be downloaded from the official Oracle site.

Make sure that you select the appropriate installer for your system, that your system meets the requirements recommended by Weblogic (or other best practices issued by Oracle as the vendor), and that you follow the guidelines presented in the next section (Weblogic requisites), such as creating a user domain and other general recommendations such as installing Weblogic into a directory which does not contain blank spaces or parenthesis.

 

 

Weblogic requisites

To install Weblogic (once its prerequisites are met), make sure you consider the following:

Installing all components of the Weblogic Server.

 

Weblogic12_install01

 

Note that the Oracle Coherence is not needed since this this procedure configures Weblogic for a standalone configuration, and not for a clustered setup).

 

Choosing your JDK home as previously set, to reference in the installation (using JDK 7).

Do NOT choose to install a bundled JDK from the list, in order to ensure that you use a version as supported by Bizagi.

 

Weblogic12_install02

 

Choosing to install the Windows Service (applicable if your operating system is Windows).

 

Weblogic12_install03

 

For a complete guide on how to install Weblogic, please refer to Oracle's documentation.

This installation path will be referenced as your <WEBLOGIC_HOME> from this point on.

 

 

Creating a user domain

Once Weblogic is installed, keep in mind you need to create a user domain for Bizagi's use.

For this, you may use the Run Quickstart option for Weblogic to assist you with this subject.

 

Within the Quickstart options, locate the Getting started with Weblogic Server option and select Create a new Weblogic domain.

 

Weblogic12_domain01

 

For further guide and information on this subject, refer to Weblogic's official documentation.

When creating the domain, acknowledge the name and path of your created domain.

Click Next.

 

Weblogic12_domain02

 

Configure the username and password for the administrator who will be able to start up the server and access the Administration Console.

In this example, the username is admin. Click Next.

 

weblogic_user

 

 

In the Configure Sever Start Mode and JDK window, select the option Production Mode in the panel called WebLogic Domain Startup Mode. For the JDK Selection, you may keep the selection for the available JDK.

Click on Next.

 

weblogic_ServerStartMode

 

In the configuration screen and for a standalone Weblogic instance,  make sure you choose the option Administration Server.

Recall that through this configuration you will set up a standalone Weblogic instance (not as a cluster).

Click on Next.

 

You will see the default Administration server's (AdminServer) configuration. Modify these settings according to your decisions, to configure your instance:

Name: AdminServer

Listen address: The IP address of the main server.

Listen port: The port number which will be used for this administration server. By default it will use 7001.

 

Review the configuration settings of your domain before the Configuration Wizard creates the domain. When done, click Create.

 

Weblogic options

For information about how to start, stop or access the administration console in Weblogic, refer to the information below.

 

Starting the Server (domain)

To start Weblogic services, execute the following file in a command prompt:

 

In a Unix-like OS such as Linux:

<WEBLOGIC_HOME>/user_projects/domains/[USER_DOMAIN]/bin/startWebLogic.sh

 

In a Windows OS:

<WEBLOGIC_HOME>\user_projects\domains\[USER_DOMAIN]\bin\startWebLogic.cmd

 

note_pin

In Windows OS, you may also use the direct access from the Start menu (e.g. Oracle Weblogic > User Projects > [user_domain] > Start Admin Server).

 

 

Weblogic12_startup01

 

Make sure you enter the username and password (as it was defined when the domain was created).

 

Weblogic12_startup02

 

 

Stopping the Server (domain)

To stop Weblogic services, execute the following file in a command prompt:

 

In a Unix-like OS such as Linux:

<WEBLOGIC_HOME>/user_projects/domains/[USER_DOMAIN]/bin/stopWebLogic.sh

 

In a Windows OS:

<WEBLOGIC_HOME>\user_projects\domains\[USER_DOMAIN]\bin\stopWebLogic.cmd

 

note_pin

In Windows OS, you may also use the direct access from the Start menu (e.g. Oracle Weblogic > User Projects > [user_domain] > Start Admin Server).

 

Weblogic12_stop

 

Make sure you enter the username and password (as it was defined when the domain was created).

 

 

Accessing the Administration Console

To access the Administration Console of Weblogic, enter the following address in the browser of your choice.

http://localhost:7001/console/login/LoginForm.jsp

 

Consider the port number involved in the service, according to any modifications you may have configured.

Then, enter the username and password (as it was defined when the domain was created).

 

Weblogic12_adminconsole

 

 

 

What you need to do

To configure Weblogic to work with Bizagi, the procedure is carried out:

 

1. Install Bizagi libraries and drivers into Weblogic.

2. Configure files for Bizagi's runtime.

3. Set environment variables.

4. Configure the following modules in Weblogic:

Authentication

Data access

Messaging service (JMS)

Shared libraries (JSTL, JSF)

Others such as JTA's timeout and the Bizagi system user

 

These modules are configured by using Weblogic's administration console and by making use of the Bizagi libraries and drivers installed in the first step.

After these steps, your Weblogic installation will be configured for Bizagi processes to be deployed into a JEE application (Work Portal).

 

 

Procedure

The following steps describe in detail how to configure and modify settings of the default Weblogic installation in order to work with Bizagi.

 

note_pin

Use the names involved in references and configuration exactly as presented below, keeping in mind that such configuration is case-sensitive.

 

1. Install Bizagi libraries and drivers into Weblogic

For Weblogic to work with Bizagi, you will need to install libraries and drivers that Bizagi uses into your Weblogic installation.

Such libraries and drivers are not shipped in a Weblogic installation by default.

 

To do this, you will need to have at hand the configuration and deployment files delivered by Bizagi (BizAgi-ear-Weblogic-dist.zip).

Once having this .zip file, extract its contents into a local path of your choice.

This path, including its immediate subfolder called BizagiBPMJEE, will be referenced as <CONFIGURATION_INPUTS> from this moment on.

In this image, <CONFIGURATION_INPUTS> references C:\ROOT\BizAgi-ear-Weblogic-dist\BizagiBPMJEE\:

 

Weblogic12_copyfiles00

 

1.1 Install Authentication libraries

Installing the libraries is simply done by copying those libraries used by Bizagi's Authentication module provided in the Configuration inputs (bizagi-security-provider-[version].jar, bizagi-remote-[version].jar, bizagi-security-common-[version].jar), from this path:

<CONFIGURATION_INPUTS>\security\

And into Weblogic server libraries repository at:

<WEBLOGIC_HOME>\wlserver_12.1\server\lib\mbeantypes\

 

Weblogic12_copyfiles01

 

1.2 Install Data access drivers

Installing the data access drivers is simply done by copying those libraries that will be needed for Bizagi to connect to your database.

Copy the Data Access drivers according to your Database engine (provided in the Configuration inputs) from this path:

<CONFIGURATION_INPUTS>\configuration\

Into Weblogic libraries at.

<WEBLOGIC_HOME>\wlserver_12.1\server\lib\

 

If you are using Oracle, you will not need to copy the driver.

Ojdbc6 is usually included by default within the files shipped in with Weblogic (you will need to ensure it is there).

 

If you are using Microsoft SQL Server, copy the sqljdbc-4.0.jar file.

 

Weblogic12_copyfiles02

 

1.3 Install the logger library.

Installing the logger library is simply done by copying the jar file used for this purpose, called log4j-[version].jar (provided too in the Configuration inputs), from this path:

<CONFIGURATION_INPUTS>\configuration\

Into your Weblogic domain libraries at:

<WEBLOGIC_HOME>\user_projects\domains\[your_domain]\lib\

 

Weblogic12_copyfiles03

 

1.4. Install the shared libraries.

Installing shared libraries is done so that Bizagi can use them when carrying out an application deployment at Weblogic (generating the Bizagi Work Portal).

This is simply done by copying the files called: jsf-myfaces-[version].war, and eclipselink-[version].jar provided in the Configuration inputs, from this path:

<CONFIGURATION_INPUTS>\configuration\

Into Weblogic libraries at:

<WEBLOGIC_HOME>\wlserver_12.1\common\deployable-libraries\

 

Weblogic12_copyfiles04

 

 

Two additional shared libraries are used as well for application deployment, but you do not need to install them since they are already shipped with a default Weblogic installation.

These 2 libraries are jsf-1.2.war and jstl-1.2.war:

 

Weblogic12_copyfiles05

 

 

2. Configure files for Bizagi's runtime

There are certain configuration files that Bizagi will internally use and will look up for, when executing the processes, such as: A JiNET module and a set of properties files holding special settings in your specific project.

You need to initially define where you will have these files so that referencing them is configured when setting the environment variables that Weblogic will use in its startup.

 

To ensure you can manage the configuration involved for Bizagi to work (i.e creating backups for the system's configuration), we recommend copying these configuration files into a separate path.

This path will be referred to as <BIZAGI_HOME> from this point on.

 

 

note_pin

It is recommended that your <BIZAGI_HOME> path is contained inside of the Weblogic installation directory and that the owner of this folder is the same user running Weblogic.

This way, you can ensure proper access rights (this path should have at least read and write rights).

It is also recommended to place inside of <BIZAGI_HOME>, the JEE Console Manager for your process deployments.

 

To configure the files used by Bizagi, first copy:

The JiNET folder (located at <CONFIGURATION_INPUTS>) into <BIZAGI_HOME>

The bizagi-config folder (located at <CONFIGURATION_INPUTS>) into <BIZAGI_HOME>

The connectors folder (located at <CONFIGURATION_INPUTS>) into <BIZAGI_HOME>

 

In this image, <BIZAGI_HOME> is created referencing C:\ROOT\BizagiWeblogic\:

 

Weblogic12_bizagifiles01

 

 

Additionally, you will need a path to store the files of a JMS File Store dedicated for Bizagi's purpose.

 

note_pin

You may create such path inside of <BIZAGI_HOME>, however the most important, usual and recommended aspect is that this folder is set inside of the Weblogic's installation directory in order to avoid issues regarding the access rights (read and write rights as minimum; preferably having ownership set to the user running Weblogic).

 

 

Weblogic12_bizagifiles02

 

Notice that in the image above, the path in which we will be storing such files is C:\ROOT\BizagiWeblogic\JMSFileStores\FileStore0\. This path will be used in the configuration treated further on when setting the JMS resources.

 

 

note_pin

If your processes use Bizagi's built-in integration with SAP systems, you will need to configure the libraries involved in the connection to SAP throughout the connector for JEE platforms.

 

The SAP connector for JEE platforms  (called JCo) consists of a .jar file and an additional native library for the operating system (a .so file for a Unix-like OS such as Linux, or a .dll for a WIndows OS).

All JCo required files are requested and downloaded from the same official SAP link at http://service.sap.com/connectors (authorized access by using your valid SAP credentials required).

Make sure you obtain the library that corresponds to your system architecture bits specification (i.e, 64-bit or 32-bit).

 

Once you have the JCo library, make sure you:

1. Place the sapjco-3.x.jar library in your JEE Application server's repository of libraries, at <WEBLOGIC_HOME>\user_projects\domains\[your_domain]\lib\.

2. Place the sapjco3.so (for a Unix-like OS such as Linux) or the sapjco3.dll (for a Windows OS) in Bizagi's files, at <BIZAGI_HOME>/connectors/SAP/jco3.

 

In the next section (set environment variables) you will need to include this path as a starting parameter of the environment variables.

 

3. Set environment variables

To set environment variables, first ensure your Weblogic Server is in a stopped status (NOT currently running).

Then, edit the server's start-up file to ensure that you include reference to the environment variables.

 

In Unix-like OS:

Edit the <WEBLOGIC_HOME>/user_projects/domains/<USER_DOMAIN>/bin/startWebLogic.sh file by locating the line having

JAVA_OPTIONS="${SAVE_JAVA_OPTIONS}", and adding these lines at the end, but included within the closing quotes:

-DiNET_HOME=<BIZAGI_HOME>/JiNET -Duser.language=en -Duser.country=us -Dfile.encoding=UTF-8 -DAPP_SERV=WEBLOGIC -Dbizagi-config=<BIZAGI_HOME>/bizagi-config -Dcom.sun.xml.ws.spi.db.BindingContextFactory=com.sun.xml.ws.db.glassfish.JAXBRIContextFactory -Djavax.xml.bind.JAXBContext=com.sun.xml.bind.v2.ContextFactory

 

Weblogic12_envstart_nix

 

Consider that you need to replace <BIZAGI_HOME> with the actual path of the files Bizagi will use in its runtime, while making sure you will use "/" as the path for folder separation.

 

 

note_pin

If your processes use Bizagi's built-in integration with SAP systems, recall that the libraries involved in the connection to SAP throughout the connector for JEE platforms needs to be configured, as mentioned in the above section.

 

Once you have placed the JCo libraries in your corresponding server paths, include the following part as an additional last variable into the JAVA_OPTIONS modifications at <WEBLOGIC_HOME>/user_projects/domains/<USER_DOMAIN>/bin/startWebLogic.sh:

-Djava.library.path=<BIZAGI_HOME>/connectors/SAP/jco3

 

Weblogic12_envstart_nixsap

 

Additionally, it is recommended that you manage the assigned memory to be used by the default startup parameters (according to your hardware characteristics), so that you enhance your application performance and promote a better deployment response from the server.

To do this, make use of the USER_MEM_ARGS= command to assign these type of values.

It is recommended to use (nonetheless you may tune these values according to your hardware and vendor's recommendations):

USER_MEM_ARGS="-Xms512m -Xmx1024m -XX:PermSize=512m -XX:MaxPermSize=1024m"

 

 

note_pin

If you are using a SQL Server database, you will need to make an additional modification to the common Environment parameters to include the sqljdbc into Weblogic's CLASSPATH (by using the exact's jar name and version, such as sqljdbc-4.0.jar).

To do so, locate the line starting with WEBLOGIC_CLASSPATH="${JAVA_HOME} and add the ${WL_HOME}/server/lib/sqljdbc-4.0.jar dependency to the <WEBLOGIC_HOME>/wlserver_12.1/common/bin/commEnv.sh file (using the proper $ separator character for multiple dependencies, and at the end but inside the quotes).

 

Weblogic12_envpath_nix

 

Save changes in this file and start up your Weblogic Server.

 

 
In Windows OS:

Edit the <WEBLOGIC_HOME>\user_projects\domains\<USER_DOMAIN>\bin\startWebLogic.cmd file by locating the line having

set JAVA_OPTIONS=%SAVE_JAVA_OPTIONS%, and adding these lines at the very end:

-DiNET_HOME=<BIZAGI_HOME>\JiNET -Duser.language=en -Duser.country=us -Dfile.encoding=UTF-8 -DAPP_SERV=WEBLOGIC -Dbizagi-config=<BIZAGI_HOME>\bizagi-config -Dcom.sun.xml.ws.spi.db.BindingContextFactory=com.sun.xml.ws.db.glassfish.JAXBRIContextFactory -Djavax.xml.bind.JAXBContext=com.sun.xml.bind.v2.ContextFactory

 

Weblogic12_envstart_win

 

Consider that you need to replace <BIZAGI_HOME> with the actual path of the files Bizagi will use in its runtime, while making sure you will use "\" as the path for folder separation.

 

 

note_pin

If your processes use Bizagi's built-in integration with SAP systems, recall that the libraries involved in the connection to SAP throughout the connector for JEE platforms needs to be configured, as mentioned in the above section.

 

Once you have placed the JCo libraries in your corresponding server paths, include the following part as an additional last variable into the JAVA_OPTIONS modifications at <WEBLOGIC_HOME>\user_projects\domains\<USER_DOMAIN>\bin\startWebLogic.sh:

-Djava.library.path=<BIZAGI_HOME>\connectors\SAP\jco3

 

Weblogic12_cluster_envwinsap

 

Additionally, it is recommended that you manage the assigned memory to be used by the default startup parameters (according to your hardware characteristics), so that you enhance your application performance and promote a better deployment response from the server.

To do this, make use of the set USER_MEM_ARGS= command to assign these type of values.

It is recommended to use (nonetheless you may tune these values according to your hardware and vendor's recommendations):

set USER_MEM_ARGS=-Xms512m -Xmx1024m -XX:PermSize=512m -XX:MaxPermSize=1024m

 

 

note_pin

If you are using a SQL Server database, you will need to make an additional modification to the common Environment parameters to include the sqljdbc driver into Weblogic's CLASSPATH (by using the exact's jar name and version, such as sqljdbc-4.0.jar).

To do so, locate the line starting with set WEBLOGIC_CLASSPATH=%JAVA_HOME% and add the ;%WL_HOME%\server\lib\sqljdbc-4.0.jar dependency to the <WEBLOGIC_HOME>\wlserver_12.1\common\bin\commEnv.cmd file (using the proper ; separator character  for multiple dependencies).

 

Weblogic12_envpath_win

 

Save changes in this file and start up your Weblogic Server.

 

 

4. Configure Weblogic modules

You will need to configure Weblogic modules to use the libraries and drivers as previously installed.

The configuration for this as described in detail below, is mainly set through Weblogic's administration console.

 

note_pin

Notice that in order to edit these settings, you may need to first click the Lock & Edit button at the upper left corner.

Make sure you confirm and apply these modifications (by clicking on Activate changes), or choose to discard them if they were not appropriately (by clicking on Release configuration).

At the end of each of the steps, it is recommended to activate changes so that can apply changes incrementally. If you do activate changes for each step, consider that you will need to use the Lock & Edit button option repeatedly as well.

 

Right after some steps, Weblogic may show a message indicating that a server restart is necessary.

 

 

4.1 Authentication configuration

Access the administration console, and go to the SecurityRealms section and select the myrealm item.

 

WL_3_02

 

Select the Providers tab and then the Authentication tab.

Create a new item by click on the New button.

 

WL_3_03

 

Enter BizagiAuthenticator for the new Provider's name and select BizagiAuthenticator for its type.

 

WL_3_04

 

 

Click OK. Back in the Providers list, make sure you select the BizAgiAuthenticator as the first item in it.

This is required because the newly created Provider operates in a shared context.

Click on Reorder to do this and ensure BizAgiAuthenticator is at the top.

 

WL_3_05

 

 

Back in the list of Providers, click on BizAgiAuthenticator to modify its settings.

Change the Control Flag to SUFFICIENT from the drop-down list and click on Save.

 

WL_3_06

 

 

Finally, activate the changes.

 

4.2 Data access configuration

Before moving on, take into account that if you are using a SQL Server Database, you will require that its service is not started under a dynamic port.

It is required that this TCP/IP port is set explicitly (i.e its default 1433 port).

 

SQLServer_explicitPort

 

For the following configuration, use the administration console and perform the described steps.

Notice that in some of them, there will be input according to your Database Engine (Oracle or SQL Server).

 

Go into the Services section and into Data Sources.

 

WL_4_01

 

Create a Data Source, by clicking on New and specifying that it is a Generic Data Source.

 

WL_4_02

 

To configure this Data Source, specify the following:

 

First, enter BizAgiJava for both the Name and JNDI Name.

 

WL_4_03aMAIN

 

For Oracle, choose Oracle as the Database type. Click Next and select Oracle’s Driver (Thin) for instance connections; Versions: 9.0.1 and later for the Database Driver.

 

WL_4_03aORA

 

 

WL_4_03bORA

Click Next.

 

For SQL Server, choose MS SQL Server as the Database type. Click Next and select Microsoft's MS SQL Server Driver (Type 4) Versions:2005 and later for the Database Driver.

 

 

WL_4_03aSQL

 

WL_4_03bSQL

 

Click Next.

 

In the Transaction Options, ensure that Supports Global Transactions is marked and select Emulate Two-Phase Commit.

 

Click Next and specify the Connection details to your Database. Click Next.

 

Test your connection by using the Test Configuration button. Notice you may also review the URL of your connection string.

Make sure this test is successful and click Next.

 

WL_4_05

 

 

Review and make sure that this data source is applied to your Server in the Target configuration (e.g AdminServer).

Click Finish.

 

Finally, make sure you activate the changes.

 

4.3 Messaging service configuration (JMS)

In these steps we will configure a JMS Server used by Bizagi mainly to process Asynchronous Activities.

To do this, in the administration console go into the Services section and into Messaging.

 

WL_5_01

 

JMS Server

Click on JMS Servers and click New.

Through the New JMS option, click on Create a New Store to define a Persistent Store.

 

 

WL_5_02

 

For the store type, select File Store. Click Next.

 

WL_5_031

 

In its properties, enter its Name (FileStore-BizAgi), select your server instance --the AdminServer as target--.

Specify the directory for the storage, as predefined in step 2 by using the path at <BIZAGI_HOME> (where files used in runtime by Bizagi are allocated).

Click Ok.

 

Weblogic12_FileStorePath

 

Back in the new JMS Server information (having created the File store successfully), enter JMSServer-BizAgi for the JMS Name and select the newly created persistent store from the drop-down list. Click Next.

 

 

WL_5_033

 

Finally, select the AdminServer as the Target server instance. Click Finish.

 

WL_5_034

 

In the list of JMS Servers, click on the newly created JMSServer-BizAgi to edit its Expiration Scan Interval property.

Set its value to 120 seconds.

 

WL_5_04

 

Click Save and make sure you activate the changes.

 

JMS Module

Browse into the Services section and expand the Messaging item to click on the JMS Modules option.

Click New to create a new JMS Module.

 

WL_6_01

 

Enter SystemModule-BizAgi for the JMS Module Name.

Additional information is not required. Click Next.

 

WL_6_02

 

Mark the checkbox for the AdminServer.

 

WL_6_03

Click Next and on Finish in the next step.

 

In the list of JMS Modules, click on the newly created JMS module to edit its properties and create the necessary associated resources.

 

Within its properties, we will create 4 new resources associated to this module: 2 connection factories (one to handle asynchronous tasks in Bizagi and another for logging purposes).

To do this, click on SystemModule-BizAgi.

 

WL_7_01

 

 

Connection factories.

To create and associate the first resource, a connection factory, click New from the Summary of Resources table.

 

For the first resource to be used for asynchronous tasks, select Connection Factory as the type.

 

WL_7_02a

 

Click Next and enter AsyncControllerFactory for its Name and JNDI Name.

Ensure that XA Connection Factory Enabled is marked and click Finish.

 

 

WL_7_02b

 

Create a second resource of the type connection factory type, this time for logging purposes.

For this, click New from the table of Summary of Resources.

Select Connection Factory again as the type.

 

WL_7_02a

 

Click Next and enter AsyncAuditControllerFactory for its Name, and its JNDI Name.

Ensure that XA Connection Factory Enabled is marked and click Finish.

 

 

Queues

Back in the view of the table of Summary of Resources, click New to create and associate a first queue (meant to handle asynchronous tasks).

 

For the first queue, select Queue as the type.

 

WL_7_03a

 

Click Next and enter AsyncController for its Name. Enter jms/AsyncController for its JNDI Name. Click Next.

 

WL_7_03b

Click Next and click Create a New Subdeployment for the Subdeployments option.

For the Subdeployment, enter AsyncController for its Name and click Ok.

 

WL_7_03c

Ensure that the newly created Subdeployment is selected and mark the existing JMSServer-BizAgi as the JMS Server target

Click Finish.

 

WL_7_03d

 

In the list of Resources, click on the newly created AsyncController Queue to edit its properties,

Click on the Delivery Failure tab to configure how to manage retries when message delivery fails.

Specify 1 as the Redelivery Limit and click Save.

 

WL_7_03e

 

 

 

For the second queue, back in the view of the table of Summary of Resources, click New to create and associate the queue to be used for logging purposes.

Select Queue as the type:

 

WL_7_03a

 

Click Next and enter AsyncAuditController for its Name. Enter jms/AsyncAuditController for its JNDI Name. Click Next.

 

 

Click Next and click Create a New Subdeployment for the Subdeployments option.

For the Subdeployment, enter AsyncAuditController for its Name and click Ok.

 

 

Ensure that the newly created Subdeployment is selected and mark the existing JMSServer-BizAgi as the JMS Server target

Click Finish.

 

 

In the list of Resources, click on the newly created AsyncController Queue to edit its properties,

Click on the Delivery Failure tab to configure how to manage retries when message delivery fails.

Specify 1 as the Redelivery Limit and click Save.

 

 

In the end, you should be able to see the list of all 4 resources we created (2 connection factories, 2 queues).

Make sure you activate the changes.

 

4.4 Shared libraries configuration

Access the administration console, and go to the Deployments section.

Within this module, we will install the 4 shared libraries as deployable for Bizagi (jstl-1.2.war, jsf-1.2.war, jsf-myfaces-1.2.8.war, eclipselink-2.X.X.jar).

 

WL_8_01

 

For the first one, click Install and browse into the deployable libraries folder (at <WEBLOGIC_HOME>\wlserver_12.1\common\deployable-libraries\).

Mark the jsf-1.2.war library:

 

Weblogic12_deployable01

 

Click Next.

Select the Install this deployment as library option. Click Next and then Finish.

 

WL_8_03

 

For the second one, repeat the Install steps but this time mark the jsf-myfaces-1.2.8.war library (located too at the same deployable libraries folder).

 

Weblogic12_deployable02

 

For the third one, repeat the Install steps but this time mark the jstl-1.2.war library (located too at the same deployable libraries folder).

 

 

Weblogic12_deployable03

 

 

For the fourth one, mark the eclipselink-2.X.X.jar library (located too at the same deployable libraries folder).

Click Next.

 

Weblogic12_deployable04

 

It is recommended to edit the name of the installed deployable library so that you do not use minor version detail for this library.

Edit the name to eclipselink-2, and click Finish.

 

Weblogic12_deployable05

 

Once you have installed these 4 deployable libraries, these will be listed:

 

WLCluster_SharedLib01

 

Keep in mind you need to activate the changes.

 

 

4.5 JTA and the Bizagi system user

For JTA (Java Transaction API) we will only modify its default timeout time.

To do this, access the administration console and go to the Services section.

Select JTA and edit the Timeout seconds property to set it to 120.

 

 

WL_9

 

 

Click Save and activate the changes.

 

Bizagi system user

Configuring the internal system user for Bizagi is strictly required and it needs to be done for the user called admon from the domain called domain.

To configure this user, access the administration console and go to the Security realms section, and into myrealm.

 

Locate the Users and Groups tab, and create a new user by clicking on New.

 

WL_10_01

 

Enter the following information for the new user (needs to be specifically the information below):

Name: admon.

Provider: DefaultAuthenticator

Password: bizagi$91

 

WL_10_02

 

 

Click Ok.

 

What is next?

After finishing these steps, your Weblogic installation is configured to work with Bizagi Processes!

You may now startup you server and generate Bizagi Work portal to have your Bizagi Processes be deployed as a Weblogic application.

 

note_pin

Recall that now that your Weblogic server has been set up to work with Bizagi, the path and files located at <BIZAGI_HOME> should not be deleted nor modified (unless when upgrading your Bizagi version in which case, some specific modifications to such files may apply).

Other input files not used in the above steps such as BizAgiConsoleManager-JEE-dist will be employed specifically by the Processes deployment procedure and you may as well uncompress the JEE Console folder inside of <BIZAGI_HOME> (recommended).

 

For more information about this option, refer to deploying the application into Weblogic Application Server.