process-mining
2023.10
false
- Release notes
- Before you begin
- Getting started
- Integrations
- Working with process apps
- Working with dashboards and charts
- Working with process graphs
- Working with Discover process models and Import BPMN models
- Showing or hiding the menu
- Context information
- Export
- Filters
- Sending automation ideas to UiPath® Automation Hub
- Tags
- Due dates
- Compare
- Conformance checking
- Root cause analysis
- Simulating automation potential
- Triggering an automation from a process app
- Viewing Process data
- Creating apps
- Loading data
- Customizing process apps
- App templates
- Additional resources
- Out-of-the-box Tags and Due dates
- Editing data transformations in a local environment
- Setting up a local test environment
- Designing an event log
- Extending the SAP Ariba extraction tool
- Performance characteristics
- How to cancel a data run from the database
- How to add an IP table rule to use SQL Server port 1433
- When creating a process app the status stays in Creating app
- Configuring Dapr with Redis in cluster mode
- Data transformations
- Uploading data
- CData Sync
Process Mining
Last updated Jun 11, 2025
How to add an IP table rule to use SQL Server port 1433
Only the default SQL Server port 1433 can be used for the Airflow metadata SQL
server database
AutomationSuite_ProcessMining_Metadata. If your
organization policies or firewall rules do not allow using port 1433, you can redirect
incoming traffic directed at port 1433 of the SQL Server IP address to a new SQL Server
IP and port.
Use the following Linux command to add a
nat rule in the IP tables
PREROUTING chain:
iptables -t nat -A PREROUTING -d <sql server IP> -dport 1433 -j DNAT --to-destination <sql server ip>:<sql server port>iptables -t nat -A PREROUTING -d <sql server IP> -dport 1433 -j DNAT --to-destination <sql server ip>:<sql server port>Replace
<sql server IP> and <sql server
port> with your respective SQL Server IP address and port number.
Note:
This command should be run as a root user or a sudo user.
To make the connectivity available from node level as well, an additional rule in the output chain is required:
iptables -t nat -A OUTPUT -p tcp -d <sql server IP> --dport 1433 -j DNAT --to-destination <sql server ip>:<sql server port>iptables -t nat -A OUTPUT -p tcp -d <sql server IP> --dport 1433 -j DNAT --to-destination <sql server ip>:<sql server port>The
iptables commands needs to be executed on all the nodes of the
cluster.
To make the IP table rules persistent, run the following command:
iptables-save > /etc/sysconfig/iptables
systemctl enable iptablesiptables-save > /etc/sysconfig/iptables
systemctl enable iptables
