Manual configuration of the operating environment

<< Click to Display Table of Contents >>

Navigation:  Bizagi Engine > Bizagi system administration > Bizagi server configuration > Bizagi Engine .NET platform configuration >

Manual configuration of the operating environment

 

Overview

This section describes how to manually configure Bizagi Engine for a Test or Production environment running in a .NET platform.

Keep in mind that this procedure is not needed when using the One-click Deployment feature in Bizagi.

For more information about when to configure Bizagi manually, refer to Bizagi Engine .NET platform configuration.

 

Before you start, it is important you make sure that your Authoring (Development) environment is already set.

The path where Bizagi is installed in your Development environment (by default at C:\Program Files\BizAgi\[Bizagi_edition]\) will be referred to as <BIZAGI_PATH> from this point on.

 

 

Prerequisites

Installing Bizagi Engine (via its installer), will include the required components.

Notice that Bizagi does not require additional components at the database server.

 

If you will be manually installing your Bizagi operating environment, you will need to make sure your server has these components previously installed:

 

1. Microsoft .NET Framework 4.0 full.

You may install this component as directly available from download at Microsoft Web sites:

http://www.microsoft.com/en-us/download/details.aspx?id=17718.

 

2. Internet Information Services components.

To make sure your server has a supported version of IIS and the necessary components, refer to: IIS Configuration.

 

3. Additional components according to your project's characteristics.

If you are using for your Process repository is an Oracle Database, or you use the Virtualization/Replication features to connect to an external Oracle Database, you will need to install the ODP.NET as described at Installing Oracle Data Provider for .NET.

If your project was created in previous versions of Bizagi 10.x and was then upgraded to Bizagi 10.x version (for instance, a project created initially in Bizagi 9.1.x), then you will also need to install the Microsoft Visual J# 2.0 SE.

If this same project from a previous version still uses letters, then you will need to additionally install the Microsoft Visual C++ (2008 SP1).

If your project integrates with SAP systems, through the use of Bizagi SAP connector, you will need Visual C++ 2010 redistributable.

 

For more information about system requirements, refer to Bizagi requirements.

 

note_pin

Some other components such as SQL Server 2005 components and Visual C++ 2008, are not needed in the operating environment mainly because these are used by Bizagi only in its Authoring / Development environment (by Bizagi Studio).

 

 

Before you start

Before you set up Bizagi's operating environment in a Production server, ensure:

 

1. Having purchased the proper Bizagi license.

This license should be at hand in order to activate it in the production server, otherwise Bizagi Work Portal will not work.

For further information about licenses, please contact sales@Bizagi.com.

 

note_pin

If you are setting up a clustered environment for Bizagi (multiple nodes to support load balancing capabilities), you may carry out the steps described below, but it is important to contact our support team to ensure you have activated your license in the clustered environment (for all Bizagi nodes).

 

2. Having acknowledged the implications of a manual installation.

When manually setting up the runtime of Bizagi Engine for your processes, note that you will need to carry out a similar procedure when upgrading your project to a newer Bizagi version.

Plan accordingly so that you acknowledge that you will need to upgrade Bizagi version with a previous assessments, replacing files and by running scripts.

Contact our support team if you wish to carry out this procedure.

Additionally, it is recommended to install as well Bizagi Management Console (in a machine having access to the database server), in order to be able to administer your project's parameters, as described in the Additional steps section.

 

 

What you need to do

Once you have met the prerequisites, in order to configure your Production or Test environment in Bizagi, these steps are taken (further detail is explained in the Procedure section):

 

1. Create your Production or Test Database.

In this step, you publish those processes which have been already implemented to a database different than the one used in the Development environment.

 

2. Create your project's folder structure

In this step, you create a directory in which you will place all relevant files and structure for your Bizagi project.

 

3. Install and configure the Work portal

In this step, you install your project's Work portal in the IIS.

 

4. Install and configure the Scheduler service.

In this step, you install your project's Scheduler as a Windows service (the Scheduler service is in charge of executing offline tasks).

 

5. Activate your license.

In this step, you activate the purchased license to support your Production or Test end users.

 

 

Procedure

Carry out the following:

 

1. Create your Production or Test Database.

When the One-click Deployment feature is not used, you will need to create a Database for your Production or Test environments.

You create this Database with your published processes by using the Advanced Deployment tool.

For more information refer to the Advanced Deployment.

 

Once this step has been completed, make sure that you end up having the details of the connection to your Production or Test Database (these will be needed to configure the Work portal and the Scheduler service).

 

2. Create your project structure

Before you install the components for the operating environment of Bizagi, make sure you create a local directory at the server, in which you will place all relevant files and structure for your Bizagi project.

Keep in mind:

 

The path on which this directory is created, will be addressed from now on as <PROJECT_PATH>.

Name the directory after the name of your project.

Inside of the created directory, you will need to create the following sub-directories:

Backups, ComponentLibrary, Database, Docs, Domains, EntityManager, Resources, SOA, Temporary, Tools, and Trace.

 

Your <PROJECT_PATH>\[Your_project_name] structure should have at this point:

 

ManualInst_projectstructBefore

 

 

3. Install and configure the Work portal

To install Bizagi Work portal, you will need to copy Bizagi web folder and files into <PROJECT_PATH>\[Your_project_name].

 

note_pin

These set of steps for the Work portal should be done in any number of servers, if your solution considers more than one in a clustered environment that supports load balancing capabilities.

Therefore and for a cluster configuration, make sure you install and configure the Work portal in each of your cluster nodes.

 

 

3.1. Copy the Web application folder.

Take a copy of the WebApp folder found at the Bizagi's Project Model files (located at <BIZAGI_PATH>\ProjectModel\WebApp\), and place it into the server's local path of your project (inside of <PROJECT_PATH>\[Your_project_name]).

 

 

3.2 Review the Work portal folder’s access rights.

Once you have copied the WebApp folder into the new path, make sure it is not marked as read-only content.

 

To review this, you may right-click that folder to select its properties and ensure that the Read-only checkbox is unselected.

 

ManualInst_Webapp01

 

Then, ensure that you also grant Full control rights.

We recommend you use one account that has such access rights and that is valid within your domain (a dedicated network's service account).

 

ManualInst_Webapp02

 

Click Ok to save changes.

 

3.3 Preconfigure the Work portal.

Edit the Work portal configuration file so that it includes the connection details to your project's database.

 

To do this, locate the <PROJECT_PATH>\[Your_project_name]\WebApp\web.config file and edit its DSNDB, PROVIDERTYPE and PROJECT keys according to the detail of the connection to your Test or Production database. Follow the detail provided below.

 

If you are using SQL Server:

<add key="DSNDB" value="Persist Security Info=True;User ID=[login_account];Password=[login_password];Data Source=[db_server_instance];Initial Catalog=[project_database];" />

 

<add key="PROVIDERTYPE" value="MSSqlClient" />

<add key="Project" value="[project_name]"/>

 

For this consider:

o[db_server_instance]: The Database server, including the instance name if explicitly defined.

o[project_database]: The name of your project's Database.

o[login_account]: The user login used to connect to that Database instance.

o[login_password]: The password for the user login. This information can be included as encrypted.

o[project_name]: The name of your Bizagi project for this environment.

Notice that this detail should refer to the database created with the Advanced Deployment procedure.

 

If you are using Oracle:

<add key="DSNDB" value="Data Source=[db_server]:[port_number]/[service_name];User ID=[user_schema];Password=[schema_password];Unicode=True;" />

 

<add key="PROVIDERTYPE" value="Oracle" />

<add key="Project" value="[project_name]"/>

 

For this consider:

o[db_server]: The Database server.

o[port_number]: The port in which the Database service listens to.

o[service_name]: The Database service identifier.

o[user_schema]: The name of your Bizagi project (seen as the user schema).

o[schema_password]: The password for that user schema.

o[project_name]: The name of your Bizagi project for this environment.

Notice that this detail should refer to the database created with the Advanced Deployment procedure.

 

 

The following image illustrates the Work portal configuration file connecting to a SQL Server database:

 

ManualInst_Webapp03

 

note_pin

It is important to ensure that the value for the Project key (<add key="Project" value="[your_project_name]"/>) matches the name of your project which should match the folder' name at <PROJECT_PATH>\[Your_project_name]

 

note_pin

If your server uses IIS 7 or higher, keep in mind that you need the HTTP compression feature enabled for performance enhancements in Bizagi (as mentioned at the IIS required configuration).

You may want to review that your web.config contains the <httpCompression> use (specified inside of <system.webServer>) :

Webconfig_compression

 

 

Save the changes and close the file.

 

3.4 Create the Work portal's Web application

To create the Work portal as a Web application, first ensure you have a proper application pool for the Work portal.

To do this open the IIS Manager (inetmgr).

 

Under the application pools, use the Add application pool... option to create one having:

Name: Give a unique name to this pool.

If you are using a 64-bit installation, it is suggested naming the pool as Bizagi 64-Bit ASP.NET v4.0.

Otherwise, for a 32-bit installation you may name the pool as Bizagi 32-Bit ASP.NET v4.0.

.NET Framework version: 4.0.

Manage pipeline mode: Integrated.

 

ManualInst_Webapp06

 

Click Ok.

Then edit its advanced settings to ensure the following values on its properties:

Enable 32-Bit Applications: False (if you are using a 64-bit installation).

For 32-bit installations, select True.

Identity: [your domain\service account]

Make sure you select the service account you configured for step 3 having rights over:

The project's Work portal path: <PROJECT_PATH>\[Your_project_name]\WebApp

Temporary folders used by the .NET Framework, such as C:\Windows\Temp or C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\

 

We recommend you use one account that has such access rights and that is valid within your domain (a dedicated network's service account).

 

ManualInst_Webapp07

 

Click Ok.

Once the application pool is set, add a new Web application for Bizagi's Work portal by using the Add application... option:

 

ManualInst_Webapp04

 

Notice that by default and most commonly, the Application is set to the Default Web site.

Though, you may use different Web site and consider its port number setting if different than the default port 80.

For more information about this setting, refer to Configuration of the Work portal outside of the default web site.

 

Make sure you set:

An Alias for its location.

Use the Application pool defined previously.

Reference as the physical path the WebApp folder located at <WEB_PATH>\WebApp

 

ManualInst_Webapp05

 

Click Ok.

 

note_pin

By default, the Web application's Authentication settings are created having Anonymous authentication enabled and Windows authentication disabled.

It is required that Anonymous authentication is enabled regardless of the authentication used by your project.

 

You will need to review the Windows authentication setting only if you will be using integrated Windows authentication in your project.

 

Finally, run the following commands in a command prompt:

%systemroot%\system32\inetsrv\APPCMD unlock config -section:system.webServer/httpCompression

%systemroot%\system32\inetsrv\APPCMD unlock config -section:system.webServer/serverRuntime

 

At this point, the Work portal has been set for your Bizagi operating environment.

To set up additional security measures (recommended), refer to Additional security configurations.

 

4. Install and configure the Scheduler service.

To install this service, you will need to copy Bizagi Scheduler folder and files into <PROJECT_PATH>\[Your_project_name].

 

 

4.1. Copy the Scheduler folder.

Take a copy of the Scheduler folder found at the Bizagi's Project Model files (located at <BIZAGI_PATH>\ProjectModel\Scheduler\), and place it into the server's local path of your project (inside of <PROJECT_PATH>\[Your_project_name]).

 

 

4.2 Review the Scheduler folder’s access rights.

Once you have copied the Scheduler folder into the new path, make sure it is not marked as read-only content.

 

To review this, you may right-click that folder to select its properties and ensure that the Read-only checkbox is unselected.

 

ManualInst_Scheduler01

 

Then, ensure that you also grant the proper access rights to the following users:

 

USER

RIGHTS

ASPNET

Modify, Write

[your domain\service account]

Modify, Write

SYSTEM user

Full control

 

ManualInst_Scheduler02

 

Click Ok to save changes.

 

4.3 Preconfigure the Scheduler.

Edit the Scheduler's configuration file so that it includes the connection details to your project's database.

 

To do this, locate the <PROJECT_PATH>\[Your_project_name]\Scheduler\BizAgi.Scheduler.Services.exe.config file and edit its DSNDB, PROVIDERTYPE and PROJECT keys according to the detail of the connection to your Test or Production database. Follow the detail provided below.

 

If you are using SQL Server:

<add key="DSNDB" value="Persist Security Info=True;User ID=[login_account];Password=[login_password];Data Source=[db_server_instance];Initial Catalog=[project_database];" />

 

<add key="PROVIDERTYPE" value="MSSqlClient" />

<add key="Project" value="[project_name]"/>

 

For this consider:

o[db_server_instance]: The Database server, including the instance name if explicitly defined.

o[project_database]: The name of your project's Database.

o[login_account]: The user login used to connect to that Database instance.

o[login_password]: The password for the user login. This information can be included as encrypted.

o[project_name]: The name of your Bizagi project for this environment.

Notice that this detail should refer to the database created with the Advanced Deployment procedure.

 

If you are using Oracle:

<add key="DSNDB" value="Data Source=[db_server]:[port_number]/[service_name];User ID=[user_schema];Password=[schema_password];Unicode=True;" />

 

<add key="PROVIDERTYPE" value="Oracle" />

<add key="Project" value="[project_name]"/>

 

For this consider:

o[db_server]: The Database server.

o[port_number]: The port in which the Database service listens to.

o[service_name]: The Database service identifier.

o[user_schema]: The name of your Bizagi project (seen as the user schema).

o[schema_password]: The password for that user schema.

o[project_name]: The name of your Bizagi project for this environment.

Notice that this detail should refer to the database created with the Advanced Deployment procedure.

 

 

The following image illustrates the Scheduler's configuration file connecting to a SQL Server database:

 

ManualInst_Scheduler03

 

note_pin

It is important to ensure that the value for the Project key (<add key="Project" value="[your_project_name]"/>) matches the name of your project which should match the folder' name at <PROJECT_PATH>\[Your_project_name]

 

Save the changes and close the file.

 

Your <PROJECT_PATH>\[Your_project_name] structure should finally look like:

 

ManualInst_projectstruct

 

 

4.4 Install the Scheduler service.

To install the Scheduler as a Windows service, create a file called BizAgi_[Project_name]_Scheduler_Service_Install.bat with the following content:

 

CD /D "%~dp0"

C:\WINDOWS\Microsoft.NET\[framework_version]\v4.0.30319\installutil /name=BizAgi[project_name]SchedulerService BizAgi.Scheduler.Services.exe

NET START "BizAgi[project_name]SchedulerService"

pause

 

Consider:

[project_name]: Is the name of your project.

[framework_version]: Should be defined as framework64 or framework according to your Bizagi installation (32 or 64 bits).

 

Once you have created this file, run it with an administrator account to install the service. You may want to review the log and the machine’s services to ensure that the service has been successfully created and that it appears listed as available.

 

ManualInst_Scheduler04

 

 

Right click on the Scheduler to select its properties and make sure it is started under the same identity and account used by the IIS application pool:

 

ManualInst_Scheduler05

 

Notice that at the end, the service called BizAgi[project_name]SchedulerService will need to be started.

 

5. Activate your license.

Activate your purchased license by following the steps described at Activate licenses, in which for this specific setup, you may activate licenses through a Bizagi which is installed in a server within the same network as your test/production server.

 

note_pin

If you are setting up a clustered environment, please contact our support team.

 

At this point, you will be set with your Bizagi operating environment.

 

 

Additional steps

To administer your operating environment, keep in mind that you may use Bizagi Management Console.

By using Bizagi Management Console you may configure active parameters in production such as: the SMTP server, URLs and systems involved in external Web services, ECM and Virtualized systems, among others (for more information about these options refer to Bizagi Management Console).

 

To use the Management Console, keep in mind you need to install it in a server with network access to the project's database.

 

note_pin

When defining the documents repository of your project (where case attachments are stored), note that if you are using a file server's shared folder then you will need to make sure that the service account described above (used to startup the application pool and Scheduler), have read and write access to that folder.

Recall that if you are using a clustered setup having more than one node, then each node should be able to access this shared folder with the required rights.