Configuring Weblogic in a cluster to work with Bizagi

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

Configuring Weblogic in a cluster to work with Bizagi

When using Weblogic to work with Bizagi in a cluster (use of more than 1 node for load balancing purposes), you need to have already set up your Weblogic for cluster support.

Therefore, before you move on, make sure you have carried out the steps described at Preconfiguring Weblogic for cluster support.

For more information about the procedure's overview, refer to Clustered Weblogic configuration.

This section focuses on the configuration needed in your Weblogic cluster so that your Bizagi project is set up.

 

 

What you need to do

Once you have achieved the previously mentioned, these steps are carried out as described further on in this section:

 

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 that these steps are required for each node making part of your cluster.

 

 

note_pin

Always use the names and information as presented below, keeping in mind that these are 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 -Dbizagi.cache.multicast.enabled=true -Dbizagi.cache.multicast.address=224.2.2.3 -Dbizagi.cache.multicast.port=7777 -Dbizagi.cache.multicast.type=UDP

 

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.

 

 

Weblogic12_cluster_envstart_nix

 

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, 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_envnixsap

 

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

 

Weblogic12_envpath_nix

 

 

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

 

In a 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 -Dbizagi.cache.multicast.enabled=true -Dbizagi.cache.multicast.address=224.2.2.3 -Dbizagi.cache.multicast.port=7777 -Dbizagi.cache.multicast.type=UDP

 

Weblogic12_cluster_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, access 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.

 

 

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 cluster configuration.

To do so, tick the cluster's checkbox and choose the All servers in the cluster so that the Target configuration considers your cluster setup.

Click Finish.

 

WLCluster_Data01

 

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 to process Asynchronous Activities.

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

 

WL_5_01

 

JMS Server

Regarding this type of resource, note that you will need to create one JMS Server (each with its own File Store), for each node of your Weblogic cluster.

 

To create a JMS Server, click on JMS Servers and then on 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), and select a Weblogic instance target (for the first one select AdminServer) and specify a valid and existing directory for the storage.

You may use the directory as predefined in step 2 by using the path at <BIZAGI_HOME> (where files used in runtime by Bizagi are allocated), however keep in mind that this folder needs to have proper access rights for your clustered setup.

Click Ok.

 

WL_5_032

 

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 instance of Weblogic for which this JMS Server will apply for.

For the first one you are creating AdminServer as the Target server instance and then click Finish.

 

WL_5_034

 

Keep in mind that you will need to repeat these steps so that at the end, you have created as many JMS Servers (and each with its own File store) as nodes for your cluster. In the last configuration screen of these definitions, you specify the instance for your resource (Target).

 

Note too that the names for such resources (JMS Servers and File Stores) must be unique. You may use this nomenclature forward on:

JMSServer-Bizagi2, JMSServer-BizagiN.

Once you are done, you will see the multiple JMS Servers and the File stores they use, in a list, including the one registered for the AdminServer instance:

 

WLCluster_JMS01

 

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

Set its value to 120 seconds.

 

WL_5_04

 

Click Save.

 

Make sure you repeat this configuration in all your JMS Servers and then ensure you save and activate 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

 

 

Make sure that you tick the cluster's checkbox and choose the All servers in the cluster so that the Target configuration considers and applies to your cluster setup.

 

 

WLCluster_Data01

 

Click Next and on Finish in the next step.

 

Connection factories and queues

In the list of JMS Modules, click on the newly created SystemModule-BizAgi to edit its properties,

Within its properties, we will create 6 new resources associated to this module (3 connection factories and 3 queues): a Connection Factory for an asynchronous queue, a Distributed Queue for it, a Connection factory for logging purposes, a Distributed Queue for it, a Connection Factory for a topic, and a Distributed Topic for it.

 

To create a resource for it, click New on the Summary of Resources table.

 

WL_7_01

 

 

For the first resource to handle asynchronous tasks in Bizagi, select Connection Factory as the type.

 

WL_7_02a

 

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

 

 

WLCluster_7_02b

 

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

 

For the second resource, create a queue for the asynchronous tasks handling in Bizagi.

Select Distributed Queue as the type.

 

WLCluster_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 Finish.

This resource should end up associated to the cluster as well.

 

For the third resource, create a Topic Connection factory.

Select Connection Factory as the type.

 

WL_7_02a

 

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

Click Next.

 

 

WLCluster_7_03b

 

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

 

WLCluster_JMS02

 

 

For the fourth create a distributed topic for the recently created Connection factory topic.

Select Distributed Topic as the type.

 

WLCluster_7_02a

 

 

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

Click Next.

 

WLCluster_7_03bTopic

 

Click Next and Finish.

This resource should end up associated to the cluster as well.

 

For the fifth resource for logging purposes in Bizagi, select Connection Factory as the type.

 

WL_7_02a

 

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

 

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

 

For the sixth and last resource, create a queue for the handling of logs in Bizagi.

Select Distributed Queue as the type.

 

WLCluster_7_03a

 

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

 

 

Click Next and Finish.

This resource should end up associated to the cluster as well.

 

Once you are done, you will see all resources listed in a table which shows that they apply to your Weblogic cluster:

 

 

In the list of Resources, click on the newly created AsyncController (the distributed 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 this way, having only 1 retry will rely on the retries definition set at the Process directly in Bizagi.

 

WLCluster_7_03e

 

Similary and back in the list of Resources, click on the created AsyncAuditController 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.

 

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 4 deployable libraries (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 which is <WEBLOGIC_HOME>\wlserver_12.1\common\deployable-libraries\ to mark the jsf-1.2.war library.

 

Weblogic12_cluster_deploylib1

 

Click Next.

Select the Install this deployment as library option.

 

 

WL_8_03

Click Next.

Make sure that you tick the cluster's checkbox and choose the All servers in the cluster so that the Target configuration considers and applies to your cluster setup.

 

 

WLCluster_Data01

Click Finish.

 

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

 

 

Weblogic12_deployable02

 

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

 

Weblogic12_deployable03

 

 

For the fourth one, repeat the Install steps but this time mark the eclipselink-2.X.X.jar library (still located at the deployable libraries folder).

 

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 automatically listed:

 

WLCluster_SharedLib01

 

Keep in mind 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.

At this point, you will need to restart your Weblogic server.

 

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 the default administrator 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.

 

Once you have completed these steps, make sure you configure the Scheduler service as described at Configuring the Scheduler in Weblogic.

 

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