- Release notes
- Getting started
- Installation
- Configuration
- Integrations
- Authentication
- Working with Apps and Discovery Accelerators
- AppOne menus and dashboards
- AppOne setup
- TemplateOne 1.0.0 menus and dashboards
- TemplateOne 1.0.0 setup
- TemplateOne menus and fashboards
- TemplateOne 2021.4.0 setup
- Purchase to Pay Discovery Accelerator menus and dashboards
- Purchase to Pay Discovery Accelerator Setup
- Order to Cash Discovery Accelerator menus and dashboards
- Order to Cash Discovery Accelerator Setup
- Basic Connector for AppOne
- SAP Connectors
- Introduction to SAP Connector
- SAP input
- Checking the data in the SAP Connector
- Adding process specific tags to the SAP Connector for AppOne
- Adding process specific Due dates to the SAP Connector for AppOne
- Adding automation estimates to the SAP Connector for AppOne
- Adding attributes to the SAP Connector for AppOne
- Adding activities to the SAP Connector for AppOne
- Adding entities to the SAP Connector for AppOne
- SAP Order to Cash Connector for AppOne
- SAP Purchase to Pay Connector for AppOne
- SAP Connector for Purchase to Pay Discovery Accelerator
- SAP Connector for Order-to-Cash Discovery Accelerator
- Superadmin
- Dashboards and charts
- Tables and table items
- Application integrity
- How to ....
- Working with SQL connectors
- Introduction to SQL connectors
- Setting up a SQL connector
- CData Sync extractions
- Running a SQL connector
- Editing transformations
- Releasing a SQL Connector
- Scheduling data extraction
- Structure of transformations
- Using SQL connectors for released apps
- Generating a cache with scripts
- Setting up a local test environment
- Separate development and production environments
- Useful resources
Server installation
It is recommended to use a clean installation of Windows Server.
See Hardware and Software Requirements for the supported ve:rsions.
For production environments, it is recommended to use CPUs with high single-threaded performance, an SSD for storage, and enough RAM.
A supported web browser must be installed on the server on which you want to install UiPath Process Mining. See Hardware and Software Requirements for the supported versions.
Before you can install UiPath Process Mining you must copy the installation package to your server.
Follow these steps to create the installation folder.
Step |
Action |
---|---|
1 |
Download the UiPath Process Mining installation package. |
2 |
On the server, create a folder for UiPath Process Mining. For instance,
D:\processmining .
In the rest of this guide, we will refer to this directory as
<PLATFORMDIR> .
Note: For multiple installations on the same server, you must create a different folder for each installation.
|
3 |
Create the folder
<PLATFORMDIR>\builds .
|
4 |
Place the installation package in the
<PLATFORMDIR>\builds folder.
• Right click on the installation package. • Select Extract All…. A sub folder is now created automatically. In the rest of this guide, we will refer to this directory as
<EXTRACTDIR> .
|
You have downloaded the installation package and copied it to your server. The package can now be installed.
Cache files use a lot of disk space. To save disk space, it is strongly recommended to set the Compress contents to save disk space option for the UiPath Process Mining server installation folder.
Follow these steps to set the Compress contents to save disk space option.
Step |
Action |
---|---|
1 |
In Windows Explorer, right click on the UiPath Process Mining installation folder
<PLATFORMDIR> and select Properties....
|
2 |
On the Generaltab, click on Advanced.... |
3 |
Enable the Compress contents to save disk space option and click on OK (2x). |
You must enable IIS on the server on which you want to install UiPath Process Mining. Follow these steps to enable IIS.
Step |
Action |
---|---|
1 |
Login on the server and open the Server Manager. |
2 |
Go to the Manage menu and select Add Roles and Features. Click on Next. |
3 |
Click through the wizard and keep the default settings. • In the Server Roles step, enable Web Server (IIS). • Continue clicking through the wizard and reboot the server if necessary. |
Follow these steps to grant permissions to IIS users.
Step |
Action |
---|---|
1 |
In Windows Explorer, right-click on the UiPath Process Mining installation folder
<PLATFORMDIR> and select Properties....
|
2 |
In the Security tab, click on Edit…, and then on Add…. |
3 |
Click on Locations…, select your local machine as the Location, and click on OK. |
4 |
Enter IIS_IUSRS in the Enter the object names to select text box. |
5 |
• Click on Check Names. Verify that
IIS_IUSRS is prefixed with the hostname.
• Click on OK. Note: For multiple installations with different users, use the users for that group instead of
IIS_IUSRS .
|
6 |
In the Group or user names list, select IIS_IUSRS. Note: For multiple installations with different users, use the users for that group instead of
IIS_IUSRS .
|
7 |
In the list below find the Full control row, check Allow. |
8 |
Click several times on OK to apply all changes and close all windows. Note:
If you are installing on any other drive than the C drive, make sure
IIS_IUSRS also has access to the parent folders/drive.
|
By default, Process Mining is only accessible externally through HTTPS. This requires that a port must be opened for external communication to enable end-users to access the platform using a web browser. Usually, port 443 is used for external communication.
If external access is needed, then a CA Certificate is required. The IT department may already have wildcard SSL certificates for your company domain name.
You have downloaded the installation package and copied it to your server. The package can now be installed.
Follow these steps to install UiPath Process Mining on the server.
Step |
Action |
---|---|
1 |
Run the following batch file:
<EXTRACTDIR>\install\activate-build\activate-build.bat .
|
2 |
Copy the file
<EXTRACTDIR>\install\processgold.lic to
<PLATFORMDIR> .
|
3 |
Copy the directory
<EXTRACTDIR>\install\databases to
<PLATFORMDIR> .
|
4 |
From the install directory in the installation package, install the following packages: •
iisnode-full-v0.2.18-x64-mv0.msi ,
•
rewrite_amd64.msi ,
•
vc_redist.x64.exe (for UiPath Process Mining 20.4 and earlier versions).
Note: For multiple installations on the same server, these packages need to be installed on the server only once.
|
5 |
Reboot the server, and verify that http://localhost shows an IIS test site. |
IIS is enabled in Windows Server, and the prerequisites are installed. http://localhost shows the IIS test site.
See illustration below.
Follow these steps to configure IIS.
Step |
Action |
---|---|
1 |
Open Internet Information Services (IIS) Manager. In the rest of this document, we will refer to this as IIS Manager. |
2 |
In IIS Manager, select your server. • Double click on Feature Delegation. Note: For multiple installations on the
same server, you need to do this only once.
|
3 |
• In this list select Handler Mappings. • In the panel on the right, click on Read/Write. Note: For multiple installations on the
same server, you need to do this only once.
|
4 |
In IIS Manager, select your server again, and in the panel on the right, click on Restart. |
5 |
In IIS Manager right click on Application Pools and click on Add Application Pool…. • Enter a name, e.g. processmining and click on OK. |
6 |
For a single installation go to Step 7. For multiple installations with different users: In the panel on the right, click on Advanced Settings…. • Go to Identity and click on … next to ApplicationPoolIdentity. • Select the Custom account option. • Click on Set... and enter the credentials for the User. • Click on OK (2x). |
7 |
In the panel on the right, click on Recycling…. • Uncheck the Regular time intervals checkbox. • Check the Specific time(s) checkbox. • In the text box, enter 02:00. Other times will also do, but keep in mind that all users that are logged in, will be logged out at that time. • Click on Next, and Finish. |
8 |
In IIS Manager, right click on Sites and click on Add Website…. • Enter a name, e.g. processmining. • Select the application pool created in Step 5. • Enter
<PLATFORMDIR>\builds as the physical path.
• Enter 8080 as the port number (any unused port number will do). Note: When you have multiple installations on the same server, you must use a different (unused) port for each installation.
• Click OK to create the site. Note: Leave the localhost binding intact. The initial login is only possible on localhost.
|
http://localhost:PORT/?page=superadmin
.
sa
and default password sa
.
superadmin
in the URL must be all lowercase!
Making the platform available to the users over the internet is done by making the site in IIS available.
- you have an HTTPS binding for the platform in IIS;
- the domain name points to the UiPath Process Mining server;
- HTTPS traffic to and from the UiPath Process Mining server is allowed.
Follow these steps to give end-users access to Process Mining.
Step |
Action |
---|---|
1 |
Obtain an SSL certificate for that domain name and install it on the UiPath Process Mining server. Refer to the documentation of the supplier of your SSL certificate for information on how to request and install an SSL certificate for your specific IIS version. |
2 |
Create a new binding for HTTPS (Port 443) • Go to IIS Manager and Click on the Process Mining Site. • Click on Bindings... in the Actions panel. • Click on Add to add a new binding, • Select https as the Type. This automatically enables Port 443. • Select the SSL Certificate installed in Step 1 from the SSL certificate list. • Click on OK. • Click on Close. |
For a detailed description on how to create an SSL binding, visit the official Microsoft documentation.
Step |
Details |
---|---|
Activate the Process Mining license | |
Set up authentication |
- Before you begin
- Windows Server
- Web browser
- Part 1: Create the installation folder
- Folder compression
- Part 2: Enable IIS on the server
- Grant permissions to IIS users
- Requirements for external access
- Part 3: Install Process Mining
- Part 4: Configuring IIS
- Part 5: Make the UiPath Process Mining platform available to end-users
- Next steps