Background
If you are reviewing this document, your organization is evaluating one or more of Recurrency’s ERP automation products. During your evaluation process, we give you the option to see your data in Recurrency by establishing a read-only connection to your ERP.
The instructions below walk through the steps to establish the secure connection between Recurrency’s systems and your ERP’s database.
💡 Note: This guide assumes you are using Epicor P21 Cloud. Epicor provides access to a read-only database for all cloud customers.
You should be able to find the URL for the database, username and password within your Prophet21 account settings. Epicor does keep this database behind an IP allowlist and should have configured it to allow you to access from your corporate network.
If you are not using Epicor hosted P21 cloud, there is another version of this guide that is better suited for you. Additionally, if you are using a public or private cloud to host your Prophet 21 instance, there may be alternative ways to establish a secure connection between our systems. Reach out to [email protected] if you have questions.
System Architecture
Components of the Recurrency system:
Epicor Prophet 21 MSSQL Database: behind every Prophet 21 deployment, there is a Microsoft SQL database that holds all of the data. Recurrency works by establishing a direct connection with this database.
Recurrency web application: hosted at https://app.recurrency.com, this is the website that users will interact with to use Recurrency’s features and capabilities
Recurrency production environment: this is our cloud based environment which hosts all of your data and the systems necessary to push/pull data to/from the Prophet 21 database. It also includes all of the systems which support the web application.
Integration Steps
High-level steps for setting up the integration with Recurrency:
Log into EpiCare and find your replicated read-only DB credentials (see steps below).
Email your server URL and port to your Recurrency Solutions Consultant.
Your Recurrency Solutions Consultant will set up a Recurrency account for you and email you a link to set up a password. This account provides access to our integration portal.
Submit DB credentials to Recurrency via our integration portal.
Recurrency Engineering will finalize the initial sync during offline hours*
*If your business has abnormal operating hours, please let us know.
Finding the Epicor Cloud Read-Replica Database Details
Epicor provides a read-replica database and its details can be found inside your P21 instance. To find the details you’ll need later in this guide.
Go to the Main Home Screen, navigate to the top right, hover over your name, and select "Account Administration".
Choose the Production Configuration Profile on your left then select the account name associated with your live production environment.
Look for the following fields:
Replicated Database Name (e.g. az_yourname_live)
Replication DB User (e.g. readonly_yourname_live)
Replicated DB Password
Replicated SQL server and ECC URL ( (e.g. p21us-read03.epicordistribution.com, 50135)
Initial Configuration Questions
The Recurrency team will send you this question via email. Your answers here help us do the upfront work to enable the network connectivity to your replicated database. You can
Questions:
What are the details Epicor provided you for accessing the read-only database? This should include:
Server URL: usually in the format “p21-us03.epicordistribution.com”
ECC URL: default is 50135
Creating your Admin Account
Within the Recurrency web application, we provide these same instructions along with useful tools to help you verify your configuration along the way.
You will receive an email from Recurrency to “Join your team on Recurrency.” The email will be sent from [email protected].
Open the email and click on the Activate Account button.
This will take you to the Recurrency Integration Portal where you will set a password for your account.
Next, you will be asked to log in using the password you just created.
You will then be taken to a Database Connection Setup page that will walk you through establishing the network connection and creating a database user with read/write access.
You’ll reference this page a few more times during the setup process.
Submitting Database Credentials
Recurrency’s Integration Portal provides a secure form to submit your database user credentials to us so we can connect your database. The username and password should be located in the same place you found the database name and URL earlier.
Log in to the Recurrency Integration Portal (see previous section)
Click on “Step 3: Database Credentials”
This page will provide some details on how to create a net-new user, which we do not have to do for P21 cloud. You already have the user details provided by Epicor.
Instead, click on Submit Credentials and supply the following details:
Database Name: Epicor provides this to you and should be in the format “az_yourcompanyname_live”
Username: the name of the user Epicor provided. Usually in the format “readonly_12345_live”
Password: also provided by Epcior and should be accessible in your P21 admin settings
Press Submit
This updates the configuration data within Recurrency and our team will review and verify the connection is working properly. We will reach out with confirmation or questions if there are any issues.
Waiting for the Initial Sync
Within a few days of confirming that the Recurrency service and database user are properly configured, Recurrency will run an initial sync after hours to sync your database with our system. Following the initial sync, we continue to pull incremental changes from your database to keep your ERP database in sync with Recurrency’s systems.
Frequently Asked Questions
1. How does the Recurrency service securely communicate with your services?
Recurrency encrypts all data in transit and at rest. In transit, we use HTTPS with at least TLSv1.2 to communicate with the Recurrency service. Any users interacting with our web-based application will also use HTTPS with at least TLSv1.2 . At rest, data is encrypted using AES-256.
2. What are the resource requirements for the Recurrency service? Should we be worried about it impacting the performance of our ERP?
The Recurrency service is designed to be lightweight and consumes few resources. Most issues we see are due to the server the agent is on losing connection to the internet or being taken offline. We also implement rate limiting within our services to ensure we do not overload your ERP.
3. I don’t feel comfortable giving Recurrency write access, can I proceed with read permission only?
Yes. We can begin with just read access. If you want to use the full suite of Recurrency’s features, we will need to add write access.
If you have any questions, please reach out to your dedicated Account Executive, [email protected], or [email protected].
4. Epicor asked for Recurrency’s public IP address so they can allowlist your system through their firewall. What should I tell them?
You can provide Epicor with the following IP: 18.206.113.117