This document is for informational purposes only and is subject to change without notice. This document and its contents, including the viewpoints, dates and functional content expressed herein are believed to be accurate as of its date of publication. However, Epicor Software Corporation makes no guarantee, representations or warranties with regard to the enclosed information and specifically disclaims any applicable implied warranties, such as fitness for a particular purpose, merchantability, satisfactory quality or reasonable skill and care. As each user of Epicor software is likely to be unique in their requirements in the use of such software and their business processes, users of this document are always advised to discuss the content of this document with their Epicor account manager. All information contained herein is subject to change without notice and changes to this document since printing and other important information about the software product are made or published in release notes, and you are urged to obtain the current release notes for the software product. We welcome user comments and reserve the right to revise this publication and/or make improvements or changes to the products or programs described in this publication at any time, without notice. The usage of any Epicor software shall be pursuant to an Epicor end user license agreement and the performance of any consulting services by Epicor personnel shall be pursuant to Epicor's standard services terms and conditions. Usage of the solution(s) described in this document with other Epicor software or third party products may require the purchase of licenses for such other products. Where any software is expressed to be compliant with local laws or requirements in this document, such compliance is not a warranty and is based solely on Epicor's current understanding of such laws and requirements. All laws and requirements are subject to varying interpretations as well as to change and accordingly Epicor cannot guarantee that the software will be compliant and up to date with such changes. All statements of platform and product compatibility in this document shall be considered individually in relation to the products referred to in the relevant statement, i.e., where any Epicor software is stated to be compatible with one product and also stated to be compatible with another product, it should not be interpreted that such Epicor software is compatible with both of the products running at the same time on the same platform or environment. Additionally platform or product compatibility may require the application of Epicor or third-party updates, patches and/or service packs and Epicor has no responsibility for compatibility issues which may be caused by updates, patches and/or service packs released by third parties after the date of publication of this document. Epicor® is a registered trademark and/or
trademark of Epicor Software Corporation in the United States, certain other countries and/or the EU. All other trademarks mentioned are the property of their respective owners. Copyright © Epicor Software Corporation 2017.
All rights reserved. No part of this publication may be reproduced in any form without the prior written consent of Epicor Software Corporation.
New Installation of Epicor 10.1.500 Revision: May 03, 2017 4:14 p.m. Total pages: 145
Contents
Part I: Getting Started...9
Chapter 1: Review Epicor ERP Flows...9
1.1 Review Installation Flow...10
Chapter 2: Verify Prerequisites...12
2.1 Verify Access to EPICweb...12
2.2 Review Release Documents...12
2.3 Verify Windows Operating System Requirements...13
2.4 Verify SQL Server Install and Features...15
2.5 Configure Server Roles (Windows Server 2012 and 2008/R2)...17
2.6 Configure Server Roles (Windows Server 2016)...19
2.7 Verify SQL Server Reporting Services (SSRS) Prerequisites...22
2.8 Set Up Test Environment...23
Part II: Installation and Configuration...25
Chapter 3: Install the Epicor ERP 10.1 Application...25
3.1 Prepare SQL Server Login Account...25
3.2 Install Epicor ERP 10.1 Server...26
3.3 Install Epicor ERP 10.1.500.x Latest Update...30
Chapter 4: Configure Epicor Database...31
4.1 Add Epicor Database Server...31
4.2 Add Epicor Database...32
4.3 Configure Epicor ERP SQL Server Login Account...37
Chapter 5: Configure Epicor Server and Application Server...38
5.1 Determine Authentication Option (Endpoint Binding)...38
5.1.1 Generate Self-Signed SSL Security Certificate (If Using UserNameSSLChannel and HttpBinaryUsernameSslChannel)...38
5.2 Add Epicor Server...39
5.3 Add Epicor Application Server (New or Upgrading from 10.0)...40
Part III: Post-Installation...55
Chapter 6: Log In the First Time...55
6.1 Set Up System Agent...55
6.1.1 Create System Agent User Account...55
6.1.2 Create System Agent...56
6.2 Install and Configure Task Agent...57
6.3 Verify SQL Search Services for Full-Text Search...61
6.4 Test System and Repeat Installation...61
Chapter 7: Install Epicor ERP Extension Applications...63
7.1 Install Epicor Web Access...64
7.2 Install Epicor Mobile Access...66
7.3 Install Epicor Enterprise Search...68
7.4 Install Epicor Social Enterprise...70
7.5 Install Embedded Education Courses...71
7.6 Install Epicor Information Worker...73
7.7 Install Epicor Online Help System...74
7.8 Install Epicor SharePoint Publisher...77
Chapter 8: Configure Epicor ERP Extension Applications...78
8.1 Deploy and Configure Epicor Web Access...78
8.1.1 Assign EpicorWebAccess Folder Properties and Sharing...78
8.1.2 Assign Resources Folder Properties and Sharing...79
8.1.3 Deploy Epicor Web Access Forms...79
8.1.4 Set Up Initial Configuration of Epicor Web Access...80
8.1.5 Install Epicor Lightweight Client...81
8.1.6 Configure EWA Reporting URL Display Features...81
Configure PDF: Windows Server 2008 R2 Web Server...81
Configure XLS: Windows Server 2008 R2 Web Server...82
8.1.7 Generate Web Forms for User Dashboards...82
8.1.8 Generate Web Forms for Customized and Localized Application Forms...83
8.1.9 Review Supported Browsers and Configuration...84
8.1.10 Set Up EWA Compression (Windows Server 2008 R2 only)...84
8.1.11 Install Crystal Reports Embedded Server 2013 (optional)...85
8.2 Configure Epicor Mobile Access...86
8.2.1 Configure Epicor Mobile Access User...86
8.2.2 Assign Data Folder Properties and Sharing...86
8.3 Configure Epicor Enterprise Search...87
8.3.1 Register Enterprise Search Server...87
8.3.3 Scheduled Tasks...89
Use Pre-defined Schedule to Rebuild All Indexes...89
Schedule Search Index Rebuild Manually...89
8.3.4 Enable Search Index...90
8.3.5 Enable Epicor Search Anywhere for Users...91
8.3.6 Re-create Search Index Definition (If Needed)...92
8.4 Configure Epicor Social Enterprise...94
8.4.1 Log In to Epicor Social Enterprise...94
8.4.2 Create Notification Source...94
8.4.3 Configure Email Server...97
8.4.4 Configure Web Site URL...97
8.4.5 Configure Twitter Credentials (Optional)...98
8.4.6 Configure Message Editing (Optional)...98
8.4.7 Invite Users...99
8.5 Configure Epicor Education Module...99
8.5.1 Enable Education Module...99
8.6 Configure Epicor Information Worker...100
8.6.1 Generate Server Components for BAQs...100
8.6.2 Deploy Alternate Contact Data Source...101
8.6.3 Set Up Information Worker Clients...101
8.6.4 Troubleshooting Installation Errors...102
8.7 Configure Epicor Sharepoint Publisher...102
Chapter 9: Install Epicor ERP 10.1 Client on a Workstation...104
9.1 Install .NET Framework 4.6.1 or Later (Client)...104
9.2 Install Crystal .NET SDK Runtime (EWA Client optional)...104
9.3 Install Epicor ERP 10.1 Client Software...105
Part IV: Supplemental Installations...108
Chapter 10: Install Microsoft Service Bus 1.1...108
10.1 Install Service Bus in a Test Environment...108
10.2 Install Service Bus in a Production Environment...111
Chapter 11: Install Languages...112
11.1 Install Language File...112
11.2 Change Language Settings...112
Chapter 12: Configure Country Specific Functionality (CSF)...114
Chapter 13: Install Performance and Diagnostic Tool...116
Chapter 14: Configure Application Request Routing...118
14.1 Install and Configure Application Request Routing...118
14.2 Create Certificates...120
14.3 Set Up HttpsOffloadBinaryUserNameChannel Server...121
14.4 Set Up HttpsBinaryUserNameChannel Server...122
14.5 Configure Application Servers...123
14.6 Add Certificates...124
14.6.1 Add Certificate for Default Website...124
14.6.2 Add Self-Signed Certificates (Test Environment)...124
14.7 Manage Load Balance...127
14.7.1 Route Specific Calls to Server Farm...127
14.7.2 Test Load Balance...128
Part V: Appendices...130
Chapter 15: Manual Installation and Conversion Issues...130
15.1 Verify Temporary Files Do Not Exist...130
15.2 Manually Install Epicor Administration Console...130
15.3 Manually Set Up Information Worker Configuration...131
Chapter 16: Implement Single Sign On...133
16.1 Set Up Automatic Sign On (Epicor Account)...133
16.2 Set Up Single Sign On (Windows Account)...133
16.2.1 Set Up User Account...134
16.2.2 Configure the Server...134
16.2.3 Configure the Application Server...135
16.2.4 Configure the Client...136
Chapter 17: Changing or Uninstalling Epicor ERP 10.1 Application....137
17.1 Add or Remove Program Features...137
17.2 Uninstall Epicor ERP 10.1 Application...137
17.3 Uninstall Epicor ERP 10.1 Client...138
17.4 Uninstall Epicor ERP Application Extensions...138
Chapter 18: Troubleshooting...139
18.1 Review Error Message Resolutions...139
18.4 Change Free Memory Requirement...141 18.5 Manage LOB Data Replication...142
Part I: Getting Started
Welcome to the Epicor ERP 10.1 Installation Guide. This part of the guide explains how to verify the prerequisites and perform pre-installation steps prior to installing Epicor ERP 10.1.
Chapter 1: Review Epicor ERP Flows
1.1 Review Installation Flow
Use the following flow to review the process a new customer follows to install Epicor ERP 10.1 as the first Epicor ERP application installation.
Chapter 2: Verify Prerequisites
Use this chapter to verify the prerequisites prior to installing or upgrading your Epicor ERP 10.1 application.
2.1 Verify Access to EPICweb
Use these steps to verify you have appropriate permissions to access the EPICweb site.
1. Verify you have Internet access at your workstation.
2. Verify you have a valid User ID and Password for Epicor's Customer Portal (EPICweb). To create an account
go to: http://support.epicor.com
2.2 Review Release Documents
Use these steps to download and review the release documents that are available with this Epicor ERP 10.1 version. Each document has been updated specifically for this release.
1. Log on to EPICweb and go to the customer portal website. Navigate to Products > Epicor ERP version 10 > Downloads > Epicor ERP > Version 10.1.
You can use this link: https://epicweb.epicor.com/products/epicor-erp/downloads.
2. In the Available Downloads list, locate and download the following release documents. Note that the
installation guide is available in three versions and you only need to download one version.
Description Release Documentation
Includes detailed list of changes (fixes and enhancements) sorted by functional area. Also includes any late-breaking installation updates. Epicor ERP 10.1 Release Notes
Includes overview topics and conceptual information regarding the Epicor ERP 10.1 architecture and framework technology strategies. Epicor ERP 10.1 Architecture Guide
Note It is highly recommended that you read this guide and
understand the Epicor ERP 10.1 architecture prior to installing.
New customers should use this guide to install a new Epicor ERP 10.1 application for the first time. Guide includes instructions to install Epicor ERP 10.1 Installation Guide
Epicor ERP 10.1, and then configure the database, servers, and application severs, before logging in the first time.
Guide also includes steps for installing the extension applications such as Enterprise Search, Education Module, Mobile Access, Social Enterprise, Web Access, and Information Worker. The guides also include steps for installing supplemental components.
Description Release Documentation
Existing customers on Epicor 9.05 should use this guide to migrate their existing Epicor 9.05 version to ERP 10.1. Migration Guides are available based on your platform type:
Epicor ERP 10.1 Migration Guide
• Migration from SQL. Existing SQL customers should use this guide to migrate from an existing Epicor 9.05.702A - SQL application to Epicor ERP 10.1.
• Migration from Progress. Existing Progress customers should use this guide to migrate from an existing Epicor 9.05.702A -Progress application to Epicor ERP 10.1.
Guide includes instructions to backup your existing Epicor 9.05 application, install a new Epicor ERP 10.1 application, configure the database, migrate your existing database into an Epicor ERP 10.1 database, configure the servers, and then log in the first time. The guide also includes steps for installing the extension applications and supplemental components.
Existing customers on Epicor ERP 10.0 or 10.1.400 should use this guide to upgrade their existing Epicor ERP 10.0 or 10.1.400 to version to ERP 10.1. 500.
Epicor ERP 10.1 Release Upgrade Guide
3. If you previously downloaded any of the above release documents prior to following the steps in this section,
you must verify that you are using the latest version of the document. To do this:
a. On your release document locate the Disclaimer page, which is before the Table of Contents.
b. Verify that the Revision date on that page is the same as the Revision date on the file that is currently available from the EPICweb customer portal site.
c. If the Revision date is not the same, follow the above steps to download the release document from the EPICweb customer portal site.
2.3 Verify Windows Operating System Requirements
Use the steps to verify your operating system requirements for installing the Epicor ERP 10.1 application. These steps must be performed on the Epicor Application Server, and not on the machine where you will be running the Epicor Administration Console.
1. For your workstation, verify you have one of the following installed:
• Windows 7 (SP1) x86 / x64
• Windows 8 x86 / x64 Intel Architecture • Windows 8.1 x86 / x64 Intel Architecture • Windows 10 x86 / x64 Intel Architecture
2. For your server, verify that you have one of the following Microsoft Technology Stacks installed. Note
• Windows Server 2012 R2 with SQL Server 2014 • Windows Server 2012 R2 with SQL Server 2016
Important For your SQL Server, Epicor supports either the runtime, Standard or Enterprise versions.
The SQL Server Express editions are not supported due to constraints on the memory, CPU, and database size.
Note Certifying a platform for Epicor ERP 10.1 is an involved task due to the amount of environment
testing required. Therefore, not every combination of hardware, Windows operating system, and SQL Server version is formally certified to successfully run Epicor ERP 10.1. For example, Epicor ERP 10.1 is certified with SQL Server 2016 only if it is matched with Windows Server 2012 R2; but Epicor ERP 10.1 is not certified with SQL Server 2008 R2 when it is matched with Windows 2012 R2.
3. If you want to use the Epicor Administration Console to remotely administer machines, you need to enable
the IIS Management Service. To do this, in the Search field, enter "Windows Features" and select the
Turn Windows features on or off option to run the Windows Features program. In the Windows
Features window, navigate to Internet Information Services > Web Management Tools and select the
IIS Management Service check box. Click OK. Click Close.
Important If you install the .NET Framework 4.6 or later before you enable IIS, you must run the
ASP.NET IIS Registration tool in order to register the .NET Framework with IIS and create application pools that use the .NET Framework 4.x. The registration tool may be located in the following folder: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis -i. For more information, refer to Microsoft Development Network website.
4. For the Epicor Administration Console, verify that port 8172 is open in the firewall. To do this, if you are
using the built-in Windows firewall, navigate to Start > Control Panel > Administrative Tools > Windows
Firewall with Advanced Security.
5. For the Epicor Administration Console, verify that in the Windows Firewall, the inbound rule "Web
Management Server (HTTP Traffic-In)" is enabled. To do this, open your Windows Firewall. Locate the inbound rule named "Web Management Service (HTTP Traffic-in)". Right-click on the rule and select
Properties. Enter the following:
a. In the General tab, select Allow the connection in the Action group box.
b. In the Advanced tab, in the profiles section, clear the Public check box. This option should not be selected. c. Keep the Domain and the Private options enabled.
Note The inbound rule "Web Management Server (HTTP Traffic-In)" should be enabled, if it exists.
If that rule is not present, then create your own inbound rule that opens port 8172 for TCP traffic.
6. With Windows Server, a firewall is installed. The firewall must be disabled in order for connectivity from
other machines to allow for administering of the Epicor ERP 10.1 Application Servers. Based on your company practices, you can enable your firewall after the installation process is complete.
7. It is recommended that Windows Updates are not set to install automatically on your production server.
Based on your company practices, your system administrator should review the Windows Updates and install when necessary.
2.4 Verify SQL Server Install and Features
Use these steps to verify that a supported version of Microsoft SQL Server is installed on your database server and that the required Full-Text Search feature is installed on your SQL Server instance.
Note It is recommended that you review the SQL Books Online information in order to become familiar
with the SQL Server administration functionality. The documentation is typically installed with the SQL Server application. To access it, navigate to Start > All Programs > Microsoft SQL Server >
Documentation and Tutorials > SQL Server Books Online.
1. On your database server, verify that one of the following Microsoft Technology Stacks is installed. Note
the stack must be the exact combination of Windows Operating System and Microsoft SQL Server. • Windows Server 2008 R2 with SQL Server 2008 R2
• Windows Server 2012 with SQL Server 2012 • Windows Server 2012 R2 with SQL Server 2014 • Windows Server 2012 R2 with SQL Server 2016
Important If necessary, install SQL Server on your database server using the instructions that came
with your SQL installation. Be sure to install any Microsoft service pack and patch updates related to your SQL version. For your SQL Server, Epicor supports either the runtime, Standard or Enterprise versions. The SQL Server Express editions are not supported due to constraints on the memory, CPU, and database size.
Note Certifying a platform for Epicor ERP 10.1 is an involved task due to the amount of environment
testing required. Therefore, not every combination of hardware, Windows operating system, and SQL Server version is formally certified to successfully run Epicor ERP 10.1. For example, Epicor ERP 10.1 is certified with SQL Server 2016 only if it is matched with Windows Server 2012 R2; but Epicor ERP 10.1 is not certified with SQL Server 2008 R2 when it is matched with Windows 2012 R2.
2. If your SQL Server is hosted on a different machine than the Epicor ERP 10.1 Application Server, verify that
network connectivity exists between the servers. To do this, complete these steps on the two machines: a. For the Application Server, do the following:
• Add a domain account with Administrator permissions.
• Log into the Application Server using the domain account with Administrator permissions.
b. For the SQL Server, do the following:
• Add the domain account login (with Administrator permissions) to the Administrators group. • Verify the SQL Server service properties specifies "Log On As" that specific domain account. • In SQL Server Management Studio, create the domain account as a SQL login account with sysadmin
rights.
3. Verify that the Full-Text Search feature is installed on your SQL Server instance. Full-Text Search is required
in order to create databases using the Epicor ERP 10 application. To verify if the feature is installed: a. Open SQL Server Management Studio. Right-click on your server/instance and select New Query.
IF (1 =
FULLTEXTSERVICEPROPERTY('IsFullTextInstalled')) print 'INSTALLED' else print 'NOT INSTALLED'
b. Click Execute. If the query returns 1 or INSTALLED it means that Full-Text Search is installed. Your query results may look similar to the following:
c. If the query returns 0 or NOT INSTALLED, you must install the Full-Text Search component. To do this: • Select Start > Control Panel > Programs and Features. In the list of programs, right-click MS SQL
Server installation and select Uninstall/Change. Click Add. • Use you MS SQL Server installation media to run SQL setup wizard.
• In the Installation Type window, select the option to Add features to an existing instance of
SQL Server and specify the SQL Server instance you want to modify.
• In the Feature Selection window, select the Full-Text Search check box. Click Next several times, then click Complete to finish the component installation.
Note As an alternate method to verify if the Full-Text Search feature is enabled on your SQL Server,
you can review the list of services. To do this, on your SQL Server select Start > Control Panel >
Administrative Tools > Services. Verify that SQL Full-text Filter Daemon Launcher (SQL Server Instance Name) service is listed, for example (MSSQLSERVER). Note that if your SQL Server has multiple
instances, you must verify that the service is available for the specific SQL Server instance.
4. If you are using Enterprise Search, verify the following SQL Server requirements:
a. Verify that one of the following SQL Server versions is installed and running locally: • SQL Server 2008, SQL Server 2008 R2, or SQL Server 2008 Express
• SQL Server 2012 • SQL Server 2014 • SQL Server 2016
b. Verify that the SQL Server installation has SQL and Windows Authentication enabled.
c. Verify that the server where Enterprise Search is installed also has SQL Server installed as the named or primary instance. For example, if your server is named Candy, then SQL Server must be made available as Candy, and not as a sub or separate installation. Note that the Epicor application SQL database can be located on a remote server.
e. Starting with SQL Server 2012, the default System account used by many Windows Services is no longer granted Administration Rights in SQL Server. If you configured your Enterprise Search Database connectivity with Windows Authentication, and you use SQL Server 2012, 2014 or 2016, you must use the following steps to verify that the account you select for the Service account has the necessary System Admin rights to access to create and manage a new database on your SQL Server instance.
• Open SQL Server Management Studio and connect to your database.
• Expand Security > Logins. Right-click on NT AUTHORITY\SYSTEM and select Properties. • In the Login Properties dialog, select Server Roles. In the server roles list, verify that sysadmin is
selected. Click OK.
• Close SQL Server Management Studio.
2.5 Configure Server Roles (Windows Server 2012 and 2008/R2)
Use these steps to configure the required Server Roles, including both the Application Server and Web Server. If the roles already exist, you can still review the list of role features to verify that your roles are configured properly.
Note If you do not configure the server roles, you may be prompted with the error "Assembly binding
warning is turned OFF" when you are attempting to add an Epicor application server. To resolve the error, follow the steps in this section to configure your server roles.
Note Note that the steps are different based on your operating system.
For more information on roles, role services, and features on Windows Server 2012 and 2012 R2, use the following link: https://technet.microsoft.com/en-us/library/hh831809.aspx
For more information on roles and features on Windows Server 2008, use the following link: https://tech net.microsoft.com/en-us/library/cc732263.aspx#BKMK_add
1. On the server, open Server Manager. From the Manage menu, select Add Roles and Features. Your dialog
may look similar to the following:
3. In the Installation Type section, keep the default Role-Based or Feature-Based Installation option selected.
Click Next.
4. In the Server Selection section, verify your server is selected in the Server Pool list. Click Next. 5. In the Server Roles section, select the following roles and then click Next.
• Application Server • Web Server (IIS)
Note If you selected to install a role, a confirmation window appears. Click Add Features to confirm
the installation.
6. Verify that you selected the following Role Services to be installed for the Application Server role and the
Web Server role:
In the Web Server Role (IIS) > Web Server section: In the Application Server section:
• Common HTTP Features: • COM+ Network Access
• Distributed Transactions: • Default Document • Incoming Network Transactions • Directory Browsing
• HTTP Errors • Outgoing Network Transactions
• Static Content • TCP Port Sharing
• HTTP Redirection (If you are installing Epicor Social Enterprise)
• Web Server (IIS) Support and its features • Windows Process Activation Service Support:
• Health and Diagnostics: • HTTP Activation (not required for
Windows Server 2008) • HTTP Logging • Message Queuing Activation • Tracing
•
In the Web Server Role (IIS) > Web Server section: In the Application Server section:
• TCP Activation • Performance:
• Static Content Compression • Security: • Request Filtering • Windows Authentication • Application Development: • .NET Extensibility 4.6.1 • ASP.NET 4.6.1 • ISAPI Extensions • ISAPI Filters
• Server Side Includes (If you are installing ESE) • Management Tools (If you are installing Epicor Mobile
Access):
• IIS 6 Management Compatibility > IIS 6 Metabase Compatibility
7. In the Features section, select the following options and then click Next.
• .NET Framework 4.6.1
• Windows Search Service (If you are installing Epicor ERP Online Help System).
8. In the Add Roles and Features Wizard, confirm installation of the selected services. Click Next. 9. In the Confirmation section, click Install. The server roles and features are installed.
10. Close the Server Manager.
2.6 Configure Server Roles (Windows Server 2016)
Use these steps to configure the required Server Roles, including the File and Storage Services, and the Web Server (IIS). If the roles already exist, you can still review the list of role features to verify that your roles are configured properly.
Note If you do not configure the server roles, you may be prompted with the error "Assembly binding
warning is turned OFF" when you are attempting to add an Epicor application server. To resolve the error, follow the steps in this section to configure your server roles.
Note Note that the steps are different based on your operating system.
For more information on roles, role services, and features on Windows Server 2016 use the following link: http s://technet.microsoft.com/en-us/windows-server-docs/management/server-manager/install-or-uninstall-roles-role
1. On the server, open Server Manager. From the Manage menu, select Add Roles and Features. Your dialog
may look similar to the following:
2. The Add Roles and Features Wizard appears. In the Before You Begin section, review the information and
click Next.
3. In the Installation Type section, keep the default Role-Based or Feature-Based Installation option selected.
Click Next.
4. In the Server Selection section, verify your server is selected in the Server Pool list. Click Next. 5. In the Server Roles section, select the following roles and then click Next.
• File and Storage Services • Web Server (IIS)
Note If you selected to install a role, a confirmation window appears. Click Add Features to confirm
the installation.
6. Verify that you selected the following Role Services to be installed for the File and Storage Services role: In the File and Storage Services section
• File and iSCI Services > File Server • Storage Services
7. Verify that you selected the following Role Services to be installed for the Web Server (IIS) role: In the Management Tools section:
In the Web Server section:
• IIS Management Console (If you are installing Epicor Mobile Access)
• Common HTTP Features: • Default Document
In the Management Tools section: In the Web Server section:
• IIS 6 Management Compatibility (If you are installing Epicor Mobile Access)
• Directory Browsing • HTTP Errors
• > IIS 6 Metabase Compatibility • Static Content
• HTTP Redirection (If you are installing Epicor Social Enterprise)
• Health and Diagnostics: • HTTP Logging • Tracing
• Request Monitor (If you are installing ESE) • Performance:
• Static Content Compression • Security: • Request Filtering • Windows Authentication • Application Development: • .NET Extensibility 4.6 • ASP.NET 4.6 • ISAPI Extensions • ISAPI Filters
• Server Side Includes (If you are installing ESE)
8. In the Features section, select the following options and then click Next. In the Features section
• .NET Framework 4.6 Features • .NET Framework 4.6 • ASP.NET 4.6
• WCF Services (all) • Message Queuing
• Message Queuing Services > Message Queuing Server • SMB 1.0/CIFS File Sharing Support
• Windows Defender Features (all) • Windows Powershell
In the Features section
• Windows Powershell ISE
• Windows Process Activation Service (all)
• Windows Search Service (If you are installing Epicor ERP Online Help System). • WoW64 Support
9. In the Add Roles and Features Wizard, confirm installation of the selected services. Click Next. 10. In the Confirmation section, click Install. The server roles and features are installed.
11. Close the Server Manager.
12. If you have selected to install the Windows Search Service feature, you must now set it to be automatic. To
do this:
a. Click Start > Run > services.msc.
b. In the Services dialog, scroll to Windows Search. Double-click the item to open it.
c. In the Windows Search Properties dialog, for the Startup Type, click the drop-down arrow and select
Automatic.
d. Click OK.
e. Close the Windows Search dialog.
2.7 Verify SQL Server Reporting Services (SSRS) Prerequisites
Use these steps to verify that you have the required components and features installed and configured properly for using SQL Server Reporting Services (SSRS). With Epicor ERP 10.1, you use SSRS for reporting functionality.
1. Verify that you are using SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, or SQL Server 2016. 2. If you are using a SQL Server version prior to SQL Server 2014, in order to print reports using SSRS, you
must download and install a Microsoft SQL Server update package from the Microsoft Support site. It is a known Microsoft issue that installing the update is required for the rendering of PDF reports to be successful. For more information, refer to this Microsoft Support page: http://support.microsoft.com/kb/26 45648.
3. Verify that IIS is installed on the server where Epicor SQL Server Reporting will be installed.
4. Verify that .NET Framework 4.6.1 or later is installed on the server where Epicor SQL Server Reporting
will be installed.
5. Verify your Reporting Services configuration values using the Reporting Services Configuration Manager.
To do this:
a. Navigate to Start > All Programs > Microsoft SQL Server 20xx > Configurator Tools > Reporting
Services Configuration Manager.
c. In Current Report Server information displayed, verify that Report Server Mode is Native.
Note For more information on installing Reporting Services Native Mode Report Server, review
the Microsoft SQL Server Documentation Online. You can use this link: http://technet.microsoft.c om/en-us/library/ms143711.aspx
d. Verify that Report Server Status is Started.
e. On the left navigation pane, select Report Manager URL. In the Report Manager Site Identification section that displays, do the following:
• In the URLs field, click the URL to verify that it is valid. Your browser should open the SQL Server Reporting Services home page.
• Open a text editor, such as Notepad, and enter the URL exactly as it is displayed in the URLs field. For example, your URL may look similar to: http://ServerName:xx/Reports. Save the notepad file. Note that you will need to enter this URL later when you are adding an Epicor Application Server and configuring SSRS on the SSRS Configuration > SSRS Base URL field.
f. Click Exit to close the Reporting Services Configuration Manager.
6. The RsReportServer.Config file defines the settings used by the Report Server Web Service, the Report
Manager, and any report processes that run in the background. If you are encountering issues with SSRS reports timing out, you can adjust settings in this file to accommodate larger reports.
a. On your server, navigate to C:\Program Files\Microsoft SQL Server\<Instance>\Reporting
Services\ReportServer\ and locate the rsreportserver.config file. You can modify the following settings in the file:
• The CleanupCycleMinutes setting specifies how many minutes report sessions and report snapshots can exist before they are deleted from the report server database. You may want to increase this value, because it determines how long an intensive operation can run from SSRS.
• The DatabaseQueryTimeout setting defines how many seconds can pass before a connection to the report server database times out. You may need to increase this value to handle larger database queries.
The following table displays the recommended adjusted timeout values for these settings:
Adjusted Timeout Default Timeout Setting Attribute Setting 1440 (24 Hours) 180 (Minutes) Value <Add Key="CleanupCycleMinutes"/> 300 (Seconds) 120 (Seconds) Value <Add Key="DatabaseQueryTimeout"/>
2.8 Set Up Test Environment
Use this information to set up a test environment and test your system.
It is strongly recommended that you set up a separate test environment prior to installing a new Epicor ERP 10.1 application or upgrading from an existing Epicor version. You can use this test environment to test the new application or to test your current system files, such as custom tools. Custom tools such as personalizations,
need to be tested and maintained prior to upgrading. By using a separate testing environment, you will know what changes you have to make to your live system after the upgrade, which helps ensure a successful upgrade. Note that while it is possible to install multiple versions of the Epicor application on the same server for testing purposes, it is not recommended.
Important Do not upgrade to Epicor ERP 10.1 without first testing the installation in a separate test
Part II: Installation and Configuration
This part of the guide explains how to install and configure your Epicor ERP 10 application.Chapter 3: Install the Epicor ERP 10.1 Application
Use this chapter to install your Epicor ERP 10.1 application.
Note The installation process creates the application directory on your server, so you only need to install once.
You must install the application on the server before you install the client on any workstations.
Note Do not reference mapped drive letters in these instructions. Only use physical drive letters or UNC paths.
If you use mapped drive letters, the server installation will not work. For example, these instructions use C:\ drive but you can use any physical drive of your choice.
3.1 Prepare SQL Server Login Account
Use these steps to setup the SQL Server login account. Prior to installing Epicor ERP, you must determine how you access the Epicor ERP SQL Server database, either SQL Server Authentication or Windows Authentication. Note that both methods allow access to the Epicor ERP database using a single SQL Server login account.
Note After you have added your Epicor database, you will use the "Configure Epicor ERP SQL Server Login
Account" steps to configure security options for the SQL Server login account that you create.
Note If you choose SQL Server Authentication, within SQL you will need to grant the user account specified
in the Application Pool Username field during creation of the Application Server (on the Application Server Settings tab of the Application Server - Create Site dialog) at least Datareader and Datawriter permissions to the Reporting database. If possible, it is recommended that Windows Authentication is used with a dedicated domain user account in the Application Pool Username and that dedicated account has DBO permissions to the Epicor transactional and Reporting databases.
1. Determine your authentication method for accessing the Epicor SQL Server database, either using SQL Server
Authentication or Windows Authentication. If you need additional information to make your decision, refer to the "Authentication Options" information in the Epicor Architecture Guide.
2. Use SQL Server Management Studio to connect to the SQL Server instance where you will be installing the
Epicor ERP database.
4. Based on whether you decided to use SQL Server Authentication or Windows Authentication, do one of
the following:
• SQL Server Authentication. Select SQL Server authentication. For Login Name, enter an appropriate login name. For example, EpicorERP. Enter a Password and confirm the password. Click OK.
• Windows Authentication. Keep Windows authentication selected. For Login Name, click Search to select the Windows domain account to use for Epicor ERP access. If desired, create a Windows account just for Epicor ERP access. Click OK after you have selected the Windows account.
5. Click OK to close the dialog.
3.2 Install Epicor ERP 10.1 Server
Use these steps to install or upgrade your Epicor ERP 10.1 server framework. During the installation you are prompted to select the Epicor ERP 10.1 program features that you want installed to the server. To perform these steps, you must be logged in as a user with Administrator rights. Note that as of Epicor ERP 10.1, the release file is delivered as a compressed ZIP file that contains an ISO image file that must be mounted to open it.
1. On the server where you intend to install Epicor ERP 10.1, verify you have at least 25 GB space in order to
install the Epicor ERP application, extension applications, demonstration database, and one application server.
2. Verify you have virtual DVD drive functionality on your server. Based on your operating system, do one of
the following:
• Windows Server 2012 or 2012 R2. Virtual DVD drive functionality is already included in your operating system. You do not need to install additional software.
• Windows Server 2008 R2. Download and install virtual DVD drive software that will be used to mount the ISO file. For example, you can download and install Virtual CloneDrive (Freeware) from SlySoft from this link: http://www.slysoft.com/en/download.html. In the Download section, select Virtual CloneDrive (Freeware). When prompted, select to Save the file to your local. Run the file and follow the install instructions.
3. Locate your Epicor ERP 10.1 release. It is available as a download from EPICweb or as a DVD. Use one of
the following methods to access the release:
• EPICweb Downloads. The Epicor ERP version 10.1 release is available from EPICweb Downloads if you have completed the Release Approval process. For more information on the Release Approval process, contact your Customer Account Manager. To access the download, log on to EPICweb Customer portal website. Navigate to Products > Epicor ERP > Downloads > Epicor ERP > Releases. You can use this link: https://epicweb.epicor.com/products/epicor-erp/downloads.
• DVD. Locate your Epicor ERP version 10.1 DVD. Insert the DVD into your drive.
4. Locate the release file related to this installation. For example RL10.1.xxx.zip. Download the file to your
local machine. For verification purposes, you will be prompted to re-enter your EPICweb credentials when you attempt to download the Epicor ERP version 10.1 file from EPICweb Downloads.
5. Extract the file. If prompted for a password, enter the password provided by the Epicor Product Group. Click OK.
6. Right-click on the extracted RL10.1.xxx.x.iso file and select Mount or Mount (Virtual CloneDrive). The
7. Navigate to the mounted (virtual DVD) drive. Right-click on the *.exe file and select Run as administrator.
The install wizard verifies that the install executable is compatible with your environment and then prepares for your installation. This verification may take several minutes.
8. The Welcome window appears for installing the Epicor ERP 10.1 server software. Click Next.
9. The Select Components window appears. Select the program features you want to install, such as the
Application Server and Supplemental (Extension) Installs. In the Install Epicor ERP 10.1 to field accept the default location of C:\Epicor\ERP10 or click Change to browse and select a different location. Your dialog may look similar to the following:
Note If you want to install certain components later, you will need to re-run the Epicor installer.
11. The Completing the Epicor Install window appears. To begin the configuration of Epicor ERP 10.1, click Next. The installation begins. The process may take several minutes. Your dialog may look similar to the
following:
12. After the Epicor ERP 10.1 Server is installed, the following installations are processed:
• Expanding Epicor ERP 10.1 Client Installer
• Expanding Epicor ERP 10.1 Administration Console Installer • Expanding Epicor ERP 10.1 Education Courses
• Expanding Epicor ERP 10.1 Reporting Services
• Expanding Epicor ERP 10.1 Supplemental (Extension) Installs (Mobile Access, Information Worker, Social Enterprise, Enterprise Search, Web Access, and Task Agent)
• Installing Administration Console
13. The Install Complete window appears when the installation is complete. Based on the availability of an
Update release, do one of the following:
• If an Update release (10.1.500.x) is available, clear the Launch the Epicor Administration Console check box. You will need to install the Update release prior to launching the Epicor Administration Console.
• If an Update release (10.1.500.x) is not available, keep the Launch the Epicor Administration Console check box selected. You will now use the instructions in the following sections to complete the configuration using the Epicor Administration Console.
Your dialog may look similar to the following:
14. Click Finish. Your Epicor ERP 10.1 server framework is installed.
15. If you want to verify that your installation completed successfully, navigate to the folder where you installed
your Epicor ERP 10.1 application. For example, the default is C:\Epicor\ERP10 followed by the release version as a subfolder. Your folder structure may look similar to the following:
16. You can now unmount the DVD drive. To do this, in the left tree view, do one of the following based on
• Windows Server 2008 R2. Right-click on the DVD drive and select VCD (...) > Unmount.
3.3 Install Epicor ERP 10.1.500.x Latest Update
Use these steps to install the latest Epicor ERP 10.1 Update to your Epicor ERP 10.1 application, if an update is available. Updates are identified by the sequential number added to the end of the release number, for example 10.1.500.x.
1. Verify your environment is ready to start the installation. To do this:
• Verify the Epicor Administration Console is closed.
• Verify that there are no active Epicor Administration Console sessions on the server. • Verify all users are logged off the Epicor ERP application.
• Verify you have at least free 20 GB disk space available.
2. Log on to EPICweb Customer portal website to locate the latest Epicor ERP 10.1 update. Navigate to Products > Epicor ERP > Downloads > Epicor ERP > Version 10.1.500. You can use this link: https://epicweb.epi cor.com/products/epicor-erp/downloads.
3. Locate the latest release file related to this installation. For example UD10.1.xxx.x.zip. Download the file
to your local machine. Go to the directory where you downloaded the file. Extract the file.
4. Right-click on the extracted UD10.1.xxx.x.exe file and select Run as administrator. The install wizard
verifies that the install executable is compatible with your environment and then prepares for your installation. This verification may take several minutes.
5. The Welcome window appears for installing the Epicor ERP 10.1 Update. Click Next.
6. The Select Components window appears. Review the list of components that were installed with your base
Epicor ERP 10.1 installation. Click Next.
7. The Completing Epicor ERP 10 Update dialog appears. To begin the install of the update, click Next. The
install begins and status bars display the processing. The process may take a period of time.
8. The Epicor ERP 10.1 Update Complete window appears when the installation is complete. Keep the Launch the Epicor Administration Console check box selected to launch the console. Click Finish.
Your Epicor ERP 10.1 update is installed. You will now use the instructions in the following sections to complete the configuration using the Epicor Administration Console.
Chapter 4: Configure Epicor Database
Use this chapter to add an Epicor Database Server and Epicor database (new or demonstration) using the Epicor Administration Console. Note that your Epicor Database Server must be added prior to adding a new Epicor database.
4.1 Add Epicor Database Server
Use these steps to add an Epicor Database Server. The Epicor Database Server must be added prior to adding an Epicor database.
1. On the server where your Epicor application is installed, open the Epicor Administration Console, if it is not
already opened.
On the server where your Epicor application is installed, navigate to Start > All Programs > Epicor Software
> Epicor Administrative Tools > Epicor Administration Console.
2. In the left-hand Tree View, select the Database Server Management node. Your dialog may look similar
to the following:
3. Right-click on the Database Server Management node and select Add Epicor Database Server. Your
4. In the Server\Instance field, enter the SQL Server name and the SQL Instance ID. For example, enter your
local server or the network server to which you will be connecting.
5. Select the Authentication mode to connect to the SQL Server. For example, select Windows Authentication
or SQL Authentication. If you select SQL Authentication you must also enter your SQL User ID and Password.
Note The SQL User ID and Password you specify will be passed to the configuration when you add
a new Epicor database.
6. Click the Verify Server button to verify that your server name and connection details are valid. Click OK
to the message. Click OK again.
7. After the server is added, the server/instance is displayed as a node under Database Server Management in
the Tree View. Your dialog may look similar to the following:
After the Epicor Database Server is added, you are now ready to add your Epicor database. For example, you can add a new database (for production) or add the demo database (for training).
4.2 Add Epicor Database
Use these steps to add an Epicor database (new or demonstration) using the Epicor Administration Console. When this database is created it is empty and scripts are run to populate it with initial data, including tables and fields for menus, security and reports.
1. Prior to adding a database, verify that the Full-Text Search feature is installed on your SQL Server instance.
Full-Text Search is required in order to create databases using the Epicor ERP 10.1 application. Refer to the previous steps in the Getting Started > Verify Prerequisites > Verify SQL Server Install and Features section.
2. Open your Epicor Administration Console, if it is not already open.
On the server where your Epicor application is installed, navigate to Start > All Programs > Epicor Software
> Epicor Administrative Tools > Epicor Administration Console.
3. Expand Database Server Management. Right-click on your Server/Instance and select one of the options
to add an Epicor database:
• Add New Database - Use this option to launch the Database Migration tool to add a new database. The new database contains seed data only.
• Add Demo Database - Use this option to launch the Database Migration tool to add a new
Demonstration Database which is used for educational purposes along with the Epicor Education Module.
4. For either a New or Demo database, the Add New Database dialog opens. Your dialog may look similar to
the following:
Enter the following:
a. Enter a Name for your database.
Note Your database name cannot include a space. After the database is created you cannot
change the database name. If the database name already exists on the server, you will be prompted to confirm the name when the database creation process starts.
b. Enter the Deployment Server path to specify the deployment share location. This path is used by the Epicor Administration Console to verify that it has the required components to service the database. These components can then be downloaded from this location.
• If you are on the deployment server, enter a fully qualified path such as C:\Epicor\ERP10\ERP10.1.xxx.
5. The Create Database on Server dialog displays. If the database creation process does not start by default,
click the Start button. A status bar displays the creation process. This may take a few minutes. Your dialog may look similar to the following:
6. If you selected Add New Database, the database is ready to be created using the default values. If you
want to change the default values and configure the database properties before it is created, on the Create Database on Server dialog, from the Action menu , select Configuration. The Configuration dialog opens. Your dialog may look similar to the following:
7. If you want to use your default configuration settings, select the Use Existing Database check box. The
MDF and LDF sections become read-only.
8. For the Target database, verify the Master Database File (MDF) Information. Note that for more
information on MDF settings, refer to your Microsoft SQL Server user guides and online help. a. In the MDF Location field, verify the default path to the master database file.
b. Review the Initial MDF File Size in GB value. Epicor recommends to set this value close to the size of the future master database file.
c. Keep the Autogrowth check box selected if you want the file to increase automatically when new data is added. In the Autogrowth settings section, use the MDF File Growth fields to specify the file growth rate. Select the Restricted File Size Growth option and set the maximum size for the MDF file if you want to limit this value, or keep the Unrestricted File Size Growth option selected. If you use MDF
autogrowth and do not restrict the file size, the MDF file should be regularly monitored and managed by a database administrator.
9. For the Target database, verify the Log Database File (LDF) Information. Note that for more information
on LDF settings, refer to your Microsoft SQL Server user guides and online help. a. In the LDF Location field, verify the path to the log database file.
b. Specify the Initial LDF File Size in GB value. Epicor recommends to set this value close to the size of the future log database file.
c. Keep the Autogrowth check box selected if you want the file to increase automatically when new data is added. Define Autogrowth settings. Use the LDF File Growth fields to specify the file growth rate. Select the Restricted File Size Growth option and set the maximum size for the LDF file if you want to limit this value, or keep the Unrestricted File Size Growth option selected. If you use LDF autogrowth and do not restrict the file size, the LDF file should be regularly monitored and managed by a database administrator.
10. Click Test Connection to verify. Click OK to the validation message. 11. Click OK to save the configuration values. The Configuration dialog closes.
12. Back on the Create Database on Server dialog, click Start. The processing begins. This may take a bit of
time. If you want to view the processing messages, click the Show More button. If you want to hide the processing messages, click the Show Less button. Your dialog may look similar to the following:
Note If the database name already exists, you are prompted with a message to enter a password to
confirm that the existing database should be deleted in order for the new database to be created. Enter the password specified in the message and click OK to confirm.
13. During the creation of the database, progress is displayed using green check marks next to the task. Note
displayed next to each task. Verify that your tasks have all completed. Your dialog may look similar to the following:
14. After completion, click the Show Log button to display the DB Migration log. Review the information. Your
dialog may look similar to the following:
15. Click Close to close the log file.
16. Click Close to close the Create Database on Server dialog.
17. Verify that your new database displays under your Server in the tree node. Your dialog may look similar to
the following:
18. If you selected the option to Add Demo Database for educational use with the Epicor Education Module,
it is recommended that you create a back-up of this demonstration database. For example, create a backup and name it DEMO_ERP10. When you need to refresh (restore) the demonstration database, this backup database can be restored to the named demonstration database. Refer to the Appendices > Troubleshooting > Restore Demonstration Database section for more information.
4.3 Configure Epicor ERP SQL Server Login Account
Use these steps to allow the Epicor ERP SQL Server login account to access the Epicor ERP database. During these steps, you will select the SQL Server login account that you created in a previous section called "Install the Epicor ERP 10 Application > Prepare SQL Server Login Account".
1. Use SQL Server Management Studio to connect to the SQL Server instance that now hosts the Epicor ERP
database.
2. Navigate to Security > Logins.
3. Double-click the SQL Server login you previously created to access the Epicor ERP database. For example,
EpicorERP.
4. In the left pane, click User Mapping.
5. In the Map column, select the check box next to the EpicorERP database.
6. In the database role memberships list, in addition to public (which is selected), select the db_owner check
box.
Important After the install is complete, you can change the security settings for this SQL Login
account. For example, if you do not want the login user to have db_owner access, you can remove the ability by clearing (unselecting) that check box in the list of database role memberships. Note that if the db_owner access is removed, verify that both db_reader and db_writer access are granted.
Chapter 5: Configure Epicor Server and Application Server
Use this chapter to add an Epicor Server and Epicor Application Server using the Epicor Administration Console.
5.1 Determine Authentication Option (Endpoint Binding)
Use these steps to determine the authentication option (endpoint binding) you will select when you are adding your Epicor Application Server. The Epicor Application Server secures communication and authenticates users using different endpoint binding methods.
1. Locate the Epicor ERP 10 Architecture Guide. It is located on the EPICweb Customer portal under Products > Epicor ERP version 10 > Documentation.
2. In the Technology Strategies section, review the "Authentication Options" information. Options include:
• UsernameWindowsChannel • UsernameSSLChannel • Windows • HttpBinaryUsernameSslChannel • HttpsBinaryUsernameChannel • HttpsBinaryWindowsChannel • HttpsOffloadbinaryUserNameChannel
3. Determine your authentication option based on your company's best practice method for security.
Note If you select to use the UserNameSSLChannel and HttpBinaryUsernameSslChannel endpoint
binding, you must use the steps in the next section to generate an SSL security certificate.
5.1.1 Generate Self-Signed SSL Security Certificate (If Using UserNameSSLChannel and
HttpBinaryUsernameSslChannel)
Use these steps to generate a Self-Signed SSL security certificate, if you have determined that you are going to use the UserNameSSLChannel or HttpBinaryUsernameSslChannel endpoint binding.
If you have determined that you are going to use the UserNameSSLChannel or HttpBinaryUsernameSslChannel endpoint binding, you will need a SSL security certificate. You can use these steps as an example of how to generate a self-signed SSL Security Certificate. Review the Epicor ERP 10 Architecture Guide for information on using authentication options and security certificates, if needed. Note that you must complete these steps prior to adding an Epicor Application Server.
1. Create a Self-Signed SSL Security Certificate:
a. Navigate to Start > Administrative Tools > Internet Information Services (IIS) Manager. Select your server name.
b. Double-click the Server Certificates icon in the IIS section of the middle pane. c. In the Actions menu, click Create Self-Signed Certificate.
d. Enter a name for the new certificate, for example, enter the fully qualified domain name. Select Personal certificate store from the drop-down list and click OK. The certificate displays in the Server Certificates list.
2. Modify the certificate security properties:
a. Navigate to the MachineKeys folder. By default the path is C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys.
b. In the MachineKeys folder, right-click the file with the latest Date modified and select Properties. c. In the Properties window, click the Security tab. Click the Edit button.
d. In the Permissions for <file name> window, click the Add button.
e. In the Enter the object names to select field, enter Everyone. Click OK.
f. Click Everyone in the Group or user names list. In the Permissions for Everyone pane, select the Allow check box against the Full control permission. Click OK.
g. Click OK in the Properties window and exit the MachineKeys folder.
3. Add the HTTPS protocol to the Self-Signed SSL Security Certificate:
a. In IIS Manager tree view, expand the Sites node and select Default Web Site. b. In the Actions pane, click Bindings.
c. In the Site Bindings dialog, click Add.
d. Set Type value to HTTPS. The Port value defaults to 443.
e. Click the Select button next to the SSL certificate field and select the certificate you have just created. Click OK.
f. Click OK in the Add Site Binding window.
5.2 Add Epicor Server
Use these steps to add your Epicor Server using the Epicor Administration Console. You must add the Epicor Server prior to adding the Epicor Application Server.
2. In the left-hand Tree View, select the Server Management node. Right-click and select Add Epicor Server.
Your dialog may look similar to the following:
3. The server Name defaults for you using its fully qualified domain name. Click Ping Server to verify the
server name. A message displays that it is successful. Click OK.
4. Verify that your Epicor Server is added under the Server Management node. You can now add an Epicor
Application Server to this Epicor Server.
5.3 Add Epicor Application Server (New or Upgrading from 10.0)
Use these steps to add your Epicor Application Server using the Epicor Administration Console. Note that prior to adding an Epicor Application Server, you must add your Epicor Server.
Note Use these steps if you are installing your Epicor ERP 10.1 application for the first time, or you are
upgrading from a previous installation of Epicor ERP 10.0 (600 or 700). If you are upgrading from a previous installation of Epicor ERP 10.1.400 you use the "Upgrade Epicor Application Server" steps instead.
1. In the Epicor Administration Console tree view, expand the Server Management node. Verify that the
2. Right-click on the Epicor server and select Add Application Server. If prompted to select a Snap-In Version,
select the version of the application server you want to add and click OK. The Application Server - Create Site dialog opens. Your dialog may look similar to the following:
3. On the Application Server Settings tab, define the following:
a. Review or enter the Application Name to identify the name that Internet Information Services (IIS) uses to create the application. This value is also added to the URL address which the client installation uses to connect to the application server. For example, the name ERP101500 means the application server URL will be net.tcp://<servername>/ERP101500. You can directly enter the name or click the Browse
(...) button to find and select it.
Note Several fields default based on the Application Name: Web Site Directory and Application Pool Name on this same tab, and Display Name on the Admin Console Settings tab. This feature
prevents a site that already exists from being overwritten by the name change.
b. Review or enter the Deployment Directory that contains the Epicor server installation. For example: \\EpicorServer\Epicor\ERP10\ERP10.1.500.0. You must be a member of the Administrators group on the server specified.
c. If available, use the Deployment Version drop-down to select your update version from the list of updates that are available on your server. If a release update is not available, select Base. If a release update is available, it is recommended that you select the update release. For example, select 10.1.500.x.
Important If a release update is available, you would have installed it using the previous steps in
the Install Epicor ERP 10 Update (10.1.500.x) section. It is recommended that you select that update version to update your Epicor ERP version to the latest version, for example 10.1.500.x. Note that when you click OK, the application server updates the Epicor ERP 10.1 application to the selected version. If prompted that all users will be disconnected while the system is being updated, verify that all users have logged out of the system and then click Yes to continue.
d. The Web Site Directory identifies the server machine that will contain the application server. The application server is installed in this location. Verify that the path includes the Application Name that you just entered. For example: C:\Inetpub\wwwroot\EpicorERP101500.
e. Use the drop-down menu to select your Endpoint Binding to define how this application server checks for authentication certificates through Internet Information Services (IIS). When a user logs into the application, the selected method verifies the communications are encrypted and checks whether the user can access the Epicor application. Options include:
• UsernameWindowsChannel - This NET.TCP binding authenticates transactions through an Epicor Username and Password. Windows checks for existing Epicor user accounts to authenticate logins. • UsernameSSLChannel - This NET.TCP binding authenticates transactions using a Secure Sockets
Layer (SSL) X509 certificate. Leverage this method for application servers that handle smart client installations when users reside in different domains. By using an SSL certificate, users from these different domains can log into the Epicor application. When you select this option, the following fields become available:
• SSL Certificate Subject Name. Click the Browse (...) button to open the Windows Security list. Select your certificate. Click OK
• DNS Endpoint Identity. Enter the Domain Name System (DNS) identity of the server. When the system runs X509 SSL Certificate authentication, it uses this identity value to validate the server. • Windows - This NET.TCP binding authenticates transactions using a Windows Username and Password.
Any user with a Windows Username and Password within this domain can successfully log into the Epicor application.
• HttpBinaryUsernameSslChannel - This HTTP binding protocol authenticates using a Secure Sockets Layer (SSL) X509 certificate. The data transfers between the client and server using Hypertext Transfer Protocol (HTTP). Instead of the transport, the message which contains the data transfer is encrypted. Because this binding does not use Hypertext Transfer Protocol Secure (HTTPS), it tends to be slower than bindings which use HTTPS.
Use this method for application servers that handle smart client installations when users reside in different domains. By using an SSL certificate, users from these different domains can log into the Epicor ERP application. When you select this option, the following fields become available:
• SSL Certificate Subject Name. Click the Browse (...) button to open the Windows Security list. Select your certificate. Click OK
• DNS Endpoint Identity. Enter the Domain Name System (DNS) identity of the server. When the system runs X509 SSL Certificate authentication, it uses this identity value to validate the server. • HttpsBinaryUsernameChannel - This HTTPS binding authenticates transactions using an Epicor
Username and Password. The data transfers between the client and server using Hypertext Transfer Protocol Secure (HTTPS). HTTPS encrypts the data transfer.