Epicor905 InstallGuide 90560x Progress

Epicor 9.
05 Installation Guide
Progress Version
Disclaimer
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 2011.
All rights reserved. No part of this publication may be reproduced in any form without the prior written consent of
Epicor Software Corporation.
Progress Version
Revision: November 17, 2011 9:59 a.m.
Total pages: 113
install_prog.ditaval
Epicor 9.05 Installation Guide Contents
Contents
Introduction.......................................................................................................9
Part I: Getting Started....................................................................................10
Chapter 1: Verify Release Documentation..............................................10

1.1 Verify Revision Date..........................................................................................................................10
1.2 Review Revision History.....................................................................................................................10
Chapter 2: Perform Required Upgrades...................................................12

2.1 Verify Access to EPICweb..................................................................................................................12
2.2 Verify Latest 9.04.507x Version Installed...........................................................................................12
2.3 Verify Financial Groups are Posted....................................................................................................13
Chapter 3: Set Up Test Environment........................................................14

3.1 Set Up Test Environment Process......................................................................................................14
Chapter 4: Create Back Ups......................................................................14

4.1 Back Up Database and System..........................................................................................................14
4.2 Back Up Customized Reports............................................................................................................15
4.3 Back Up Custom Client MFGSYS Files...............................................................................................15
Part II: Pre-Installation....................................................................................16
Chapter 5: Pre-Installation Steps..............................................................16

5.1 Review Epicor Application Dependencies..........................................................................................16
5.2 Review Software Requirements.........................................................................................................16
5.3 Review Hardware Requirements........................................................................................................16
5.4 Verify Windows Server 2008 Compatibility........................................................................................16
5.5 Determine Web Service Type: WSE or WCF.......................................................................................17
5.6 Review Epicor 9.05 Functionality.......................................................................................................17
5.7 Disable Error Reporting.....................................................................................................................17
5.7.1 Using Windows 7...................................................................................................................17
5.7.2 Using Windows Vista or Windows Server 2008.......................................................................18
5.7.3 Using Windows Server 2008 R2..............................................................................................18
5.8 Download Latest Updates.................................................................................................................18
Progress Version 3
Contents Epicor 9.05 Installation Guide
5.9 Download Latest OpenEdge Updates................................................................................................19

5.10 Setup Progress OpenEdge Explorer Tool..........................................................................................19
Part III: Installation.........................................................................................21
Chapter 6: Install the Epicor 9.05 Server..................................................21

6.1 Install Microsoft Tools: .NET 3.5 and WSE or WCF Runtime (Server)...................................................21
6.2 Stop Appservers and Database..........................................................................................................22
6.3 Start Server Installation.....................................................................................................................22
6.4 Install Progress OpenEdge 10.2A......................................................................................................22
6.4.1 If you selected the Typical/Automatic Install option.................................................................23
6.4.2 If you selected the Advanced/Manual Install option.................................................................23
6.5 Install Progress OpenEdge 10.2A SP..................................................................................................24
6.6 Install Progress OpenEdge 10.2A SP Hot Fix......................................................................................25
6.7 Share the Epicor Folders....................................................................................................................25
6.8 Install Epicor 9.05 Server Software....................................................................................................26
Chapter 7: Install Latest Updates.............................................................28

7.1 Verify Specific Folders are Not Read-Only..........................................................................................28
7.2 Install Epicor 9.05 Service Pack on the Server....................................................................................28
7.3 Install Epicor 9.05 Patch on the Server..............................................................................................29
7.4 Install Epicor 9.05 Help Content Pack................................................................................................29
Chapter 8: Install Epicor Administration Functionality...........................31

8.1 Install Epicor Administration Console................................................................................................31
Chapter 9: Install the Epicor 9.05 Client...................................................32

9.1 Before You Start...............................................................................................................................32
9.2 Install Microsoft Tools .NET 3.5 and WSE or WCF Runtime (Client)....................................................32
9.3 Install Epicor 9.05 Client Software....................................................................................................32
9.4 Install Crystal Reports 2008 Runtime (Client).....................................................................................33
9.5 Copy Shortcuts for All Users.............................................................................................................34
Part IV: Post-Installation.................................................................................35
Chapter 10: Post-Installation Steps on the Server..................................35

10.1 Verify Parameter File Settings..........................................................................................................35
10.2 Establish Security for Progress AppServer........................................................................................37
10.2.1 Establishing an administrative account..................................................................................37
10.2.2 Establishing Local Security Policy...........................................................................................37
10.2.3 Establishing the AdminService Setting...................................................................................37
4 Progress Version
10.3 Upgrade to Service Connect 9.05...................................................................................................38

10.4 Upgrade to Epicor Portal 9.05.........................................................................................................38
Chapter 11: Prepare Your Database.........................................................39

11.1 Convert Your Database...................................................................................................................39
11.1.1 Pre-Conversion Tasks............................................................................................................39
11.1.2 Restore Schema Holders.......................................................................................................40
11.1.3 Run Schema Change............................................................................................................40
11.2 Add Epicor and Application Server Connections..............................................................................41
11.3 Import License Codes......................................................................................................................41
11.4 Add Company................................................................................................................................42
11.5 Run Data Conversions.....................................................................................................................42
11.5.1 Set Epicor Admin Tools PROPATH.........................................................................................42
11.5.2 Run Conversions Using Epicor Admin Tools..........................................................................43
11.6 Stop and Start Database and App Servers.......................................................................................43
Chapter 12: Log in the First Time.............................................................45

12.1 Import Posting (Booking) Rules for Extended Rules..........................................................................45
12.2 Review Blocked Standard Posting Rules (if any)...............................................................................46
12.3 Set Up System Agent for Printing (First Time Login).........................................................................46
12.4 Maintain Your Customizations and Personalizations........................................................................47
12.5 Test Business Activity Query (BAQ) Calculations...............................................................................48
12.6 Test Business Activity Manager (BAM) Upgrades.............................................................................48
12.7 Update and Test Business Process Management (BPM) Directives....................................................49
12.8 Test Custom Code Programs...........................................................................................................49
12.9 Test System and Repeat Installation................................................................................................49
Chapter 13: Restore Demonstration Database........................................50

13.1 Download Demonstration Database File..........................................................................................50
13.2 Verify Prerequisites.........................................................................................................................50
13.3 Restore the Demonstration Database - Progress..............................................................................50
13.4 Import Product Licenses and Enable Modules..................................................................................51
13.5 Start Database and Main Appserver................................................................................................51
13.6 Run Manual Conversion..................................................................................................................52
13.7 Set Up System Agent for Printing (Demo Database).........................................................................52
13.8 Restart Remaining Appservers.........................................................................................................53
13.9 Test Demonstration Database Update.............................................................................................53
Chapter 14: Configure Windows Admin Workstation (Optional)..........54

14.1 Install ODBC Driver (Native Client 10)..............................................................................................54
14.2 Install Progress OpenEdge...............................................................................................................54
14.3 Install Epicor 9.05 Client.................................................................................................................54
Progress Version 5
Part V: Appendices.........................................................................................56
Appendix A: Configure 64-Bit Environment (Windows 2008)...............56

A.1 Enable ASP .NET 2.0 Application (64-bit only)...................................................................................56
Appendix B: Install Embedded Education Courses.................................58

B.1 Install Embedded Education Courses Process.....................................................................................58
B.2 Configure Embedded Education Courses Client................................................................................59
B.3 License Embedded Education Courses...............................................................................................60
Appendix C: Install Epicor Administration Console................................61

C.1 Uninstall Epicor Administration Console...........................................................................................61
C.2 Install Epicor Administration Console................................................................................................61
Appendix D: Install and Deploy Epicor Web Access...............................62

D.1 Install Crystal Reports Runtime and Embedded Server.......................................................................62
D.1.1 Uninstall Previous Versions of Crystal Reports Runtime and Embedded Server.........................62
D.1.2 Install Crystal Reports 2008 Runtime (Web Access).................................................................62
D.1.3 Install Crystal Reports Embedded Server.................................................................................63
D.2 Configure Forms and Components...................................................................................................64
D.3 Install Epicor Web Access.................................................................................................................64
D.4 Deploy Epicor Web Access................................................................................................................68
D.5 Configure Epicor Web Access...........................................................................................................69
D.6 Assign Resource Folder Properties and Sharing.................................................................................69
D.7 Install Full Adobe Reader on Epicor Web Access Client......................................................................70
D.8 Update Epicor Lightweight Client Installer File...................................................................................70
D.9 Configure EWA Reporting URL Display Features................................................................................71
D.9.1 Configure: Windows 2008 64-bit Web Server - PDF...............................................................71
D.9.2 Configure: Windows 2008 32- or 64-bit Web Server - XLS.....................................................71
D.10 Generate Web Forms for Customized Epicor 9.05 Forms................................................................72
D.11 Generate Web Forms for User Dashboards.....................................................................................72
D.12 Review Supported Browsers and Configuration..............................................................................72
D.13 Set Up Compression for Performance Tuning.................................................................................73
D.13.1 Compression for Windows 2008 or Vista (IIS7).....................................................................73
D.14 Set EWA Server Timeout.................................................................................................................74
Appendix E: Install Epicor DB Replication...............................................75
Appendix F: Install Epicor SQL Server Reporting (SSRS)........................76

F.1 Verify SSRS Prerequisites...................................................................................................................76
6 Progress Version
F.2 Enable IIS 6 Management Compatibility............................................................................................76

F.2.1 Using Vista and Windows 7....................................................................................................76
F.2.2 Using Server 2008...................................................................................................................77
F.3 Install Custom Assembly DLL File (Report Server)................................................................................77
F.4 Install Microsoft Report Viewer 2010 Redistributable Package...........................................................78
F.5 Configure Epicor SQL Report Monitor...............................................................................................78
F.6 Maintain Epicor SQL Report Monitor Configuration...........................................................................81
Appendix G: Install Epicor Enterprise Search..........................................82

G.1 Verify SQL Server Prerequisites..........................................................................................................82
G.2 Create Back Ups (if Previous Version Installed)..................................................................................82
G.3 Uninstall Epicor Enterprise Search (if Previous Version)......................................................................82
G.4 Install Epicor Enterprise Search Process.............................................................................................82
G.5 Configure Replication Server for Epicor Enterprise Search.................................................................83
G.6 Configure Epicor Enterprise Search...................................................................................................84
G.7 Uninstall Information........................................................................................................................85
Appendix H: Install Epicor Mobile Access................................................86

H.1 Enable IIS 6 Management Compatibility...........................................................................................86
H.1.1 Using Vista and Windows 7....................................................................................................86
H.1.2 Using Server 2008..................................................................................................................86
H.2 Install Epicor Mobile Access Process..................................................................................................86
H.3 Configure Epicor Mobile Access.......................................................................................................87
Appendix I: Install Epicor Information Worker.......................................88
Appendix J: Install Epicor Sharepoint Publisher.....................................89
Appendix K: Configure Your Help System..............................................90

K.1 Host Help System in a Web Site........................................................................................................90
K.2 Implement Server-Side Help Search (Windows Server 2008)..............................................................91
Appendix L: Upgrade to Infragistics NetAdvantage...............................92
Appendix M: Install SonicMQ...................................................................93

M.1 Determine Your Security..................................................................................................................93
M.2 Install SonicMQ With Security Enabled.............................................................................................93
M.3 Install SonicMQ Without Security Enabled........................................................................................94
M.4 Install SonicMQ Updates..................................................................................................................95
M.4.1 Download Latest Update File.................................................................................................95
M.4.2 Install Sonic SP for Windows..................................................................................................95
Progress Version 7
M.5 Set Up Sonic Test Environment........................................................................................................96

M.6 Review Possible Installation Messages..............................................................................................96
M.6.1 Adapter .jms error in the AppServer log.................................................................................96
M.6.2 Javax.jms Exception error in the AppServer log......................................................................96
M.6.3 Javax.jms Security error in the AppServer log.........................................................................96
M.6.4 General Error Message..........................................................................................................97
Appendix N: Set Up Multi-Company Functionality.................................98

N.1 Verify Multi-Site Management License..............................................................................................98
N.2 Verify SonicMQ Broker Status...........................................................................................................98
N.3 Configure an External System Record...............................................................................................99
N.4 Configure an External Company Record.........................................................................................100
N.5 Verify Your Startup Schedule..........................................................................................................101
N.6 Schedule the Multi-Company Server Process...................................................................................102
N.7 Start the Multi-Company Process....................................................................................................102
N.8 Review Multi-Company Log File......................................................................................................103
N.9 Test the Communication................................................................................................................104
N.10 Review Sonic Container Information.............................................................................................105
N.11 Review Validation Errors...............................................................................................................105
N.12 Review Automatic Data Translations.............................................................................................106
N.13 Review Integrated Workbench......................................................................................................107
N.14 Review Multi-Company Functionality............................................................................................107
Appendix O: Review Configuration File Settings.................................109
Appendix P: Uninstall Options...............................................................112
8 Progress Version
Epicor 9.05 Installation Guide
Introduction
Welcome to the Epicor 9.05 Installation Guide - Version 9.05.600. This guide explains how to install the Epicor
9.05 application system for new or existing customers. Use the following process flow to determine your path
through this comprehensive installation guide:
Progress Version 9
Getting Started Epicor 9.05 Installation Guide
Part I: Getting Started

This part of the guide explains how to get started with your Epicor 9.05 installation.
Chapter 1: Verify Release Documentation
Use these instructions to review and verify the release documentation prior to starting the installation.
1.1 Verify Revision Date

Use these steps to verify that you have the latest version of the installation guide.
1. Log on to EPICweb and go to the Customer Portal Page. Navigate to Support > Epicor 9 > Downloads.
Note You can use this link:https://epicweb.epicor.com/Support/epicor9/Downloads
2. Navigate to Epicor 9 > Version 9.05.600.
3. In the Available Downloads list, locate and download the appropriate installation guide for your platform,
either SQL, Progress, or Linux/ UNIX.
4. Open the file. On the Disclaimer page, verify that the Revision date is the same as the Revision date on the
installation guide you are using.
Note Be sure to always use the installation guide with the latest Revision date.
1.2 Review Revision History
Use this section to review the revision history of this document. This list includes major revisions that impact
customers, such as the additions, deletions or changes to a section or set of steps. It does not include any minor
revisions of text or formatting. The revision history is sorted by Service Pack.
Release Section Description

607 Post-Install SQL only: Changed "Setup Full-Text Searching on Ms SQL Server" for
compliance with SQL Server 2008.
606 All Removed references and support for Windows Server 2003
606 Getting Started Add "Verify Financial Groups are Posted" to Perform Required
Upgrades section
606 Getting Started Add "Verify Release Documentation"
606 Installation Remove "Create ODBC Connection" from Install Latest Updates
section; Move "Configure Windows Admin Workstation" from Install
Epicor Administration Functionality section to Appendix section (for
SQL only)
10 Progress Version
Epicor 9.05 Installation Guide Getting Started
Release Section Description

606 Pre-Install Add "Setup Progress OpenEdge Explorer Tool"
606 Post-Install Changed "Verify Parameter File Settings"; Changed "Restore
Demonstration Database" Security Manager login to epicor / epicor
Progress Version 11
Chapter 2: Perform Required Upgrades
For existing customers, use these instructions to perform required upgrades before you start the installation. Specific
upgrades are required based on your current system.
2.1 Verify Access to EPICweb
Use the following instructions 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
3. If you are new to EPICweb, review the following links available on the EPICweb home page:
• An Overview of the New EPICweb
• Change or Reset Your Password
2.2 Verify Latest 9.04.507x Version Installed
Use this section to verify you have the latest version of Epicor 9.04.507x installed prior to upgrading to 9.05.
• If you are an existing customer on Vantage 8.03x, use this section to upgrade to Epicor 9.04 and then install
the latest 9.04.507 service pack and 9.04.507x patch.
• If you are an existing customer on Epicor 9.04, use this section to install the latest 9.04.507 service pack and
9.04.507x patch.
Note Prior to installing Epicor 9.05, your Epicor application must be upgraded to 9.04.507x.
1. If your Epicor application is at version 8.03.40x or earlier, use these steps to upgrade to Epicor 9.04. Contact
your Epicor consultant for assistance if necessary.
a. Log on to EPICweb and go to the Documentation website. Click this link to access the website: https://
epicweb.epicor.com/doc/Pages/Epicor9.aspx
b. From the 9.04 section, download the Epicor 9 Installation 9.04 guide for either Progress, SQL or
Linux/UNIX, based on your database.
c. Use the installation instructions to upgrade your Epicor application from 8.03.40x to 9.04.
d. Verify you have completed the required steps in the Run Additional Conversions section. Additional
conversions include:
• 10080 - Creating TranGLC for posted PartTran. If you want to convert or create links from GL Journal
detail to historical source documents, it is recommended that you manually run Conversion 10080
prior to installing Epicor 9.05. Conversion 100080 must be run against the Epicor 9.04 database. Be
sure to save a copy of your Epicor 9.04 database if you want to be able to create links from the GL
Journal detail to historical source documents after you upgrade to Epicor 9.05.
• 10012 - Setting BitFlag Field
12 Progress Version
• 9880 or 9890 - Set Unique ID; SysRow ID (For Progress Only). It is very important that you manually
run one of these conversions prior to installing 9.05.
2. After you have upgraded your system to 9.04, use the following steps to upgrade to the latest 9.04.507
Service Pack and 9.04.507x Patch.
a. Log on to EPICweb and go to the Support website. Click this link to access the website: https://epicweb
.epicor.com/Support/epicor9/downloads/Pages/default.aspx
b. Download and install the latest Service Pack onto your 9.04 system. For example, download and install
the 9.04.507 Service Pack. Use the Service Pack Installation Guide, available on that same site, for
instructions.
c. Download and install the latest Patch onto your 9.04.507 system. For example, download and install the
9.04.507A Patch. Use the Patch Installation Guide, available on that same site, for instructions.
3. If you are a Progress customer, verify you have run one of the following:
• If you are on version 9.04.506 or prior, you must manually run Conversion 9890 - Set Unique ID Part 2;
SysRow ID. The conversion can only be run once. If the conversion is not listed, it means it has already
been run.
• If you are on version 9.04.506A or higher, you must manually run Conversion 9880 - Set Unique ID;
SysRow ID. If needed, this conversion can be run multiple times.
Note Do not skip this step. It is very important that you manually run one of these conversions prior
to installing 9.05. You cannot run this conversion after you have upgraded to 9.05.
2.3 Verify Financial Groups are Posted
Use the following instructions to verify that your financial groups have been posted prior to upgrading.
1. In your Epicor application, verify that the following financial groups have been posted:
• AR Cash Receipt Entry groups
• AR Invoice groups
• GL Journal Entry groups
• Payroll Check Entry groups
• AP Payment Entry groups
• AP Invoice groups
2. In your Epicor application, go to Job Management and open the Capture COS/WIP Activity Process.
Run this task to capture and execute the calculation process for work-in-process (WIP) and/or cost of sales
(COS) for standard jobs, project jobs, inventory, receipts, and adjustment transactions.
Progress Version 13
Chapter 3: Set Up Test Environment
It is strongly recommended that you set up a test environment where you can test your current system files, such as
custom tools, prior to upgrading to Epicor 9.05.
Custom tools such as personalizations, customizations, global alerts, Business Activity Queries (BAQs), Business Activity
Manager (BAM) events and Business Process Management (BPM) methods 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 Do not upgrade to Epicor 9.05 without first testing the upgrade in a separate test environment.
3.1 Set Up Test Environment Process
1. Create a test environment of your system. For reference, use the instructions for setting up a new installation.
2. Copy your database into your test environment.
3. Verify your test environment is separate from your live system.
Chapter 4: Create Back Ups
Create the following back ups prior to continuing with your installation.
4.1 Back Up Database and System
Database and system backups are very important. Do not skip this step.
1. Verify your database is stopped.
2. Create a backup of all your database files.
3. Create a backup of your other database files, such as test, train and pilot.
4. It is required that you truncate the BI (Before Image) on each database. To do this:
a. Navigate to Start > Programs > OpenEdge 10.1c > Proenv.
b. Go to the folder where your database is located.
c. At the prompt type: proutil mfgsys -C truncate bi
d. Exit the ProEnv Utility.
5. Create a backup of your manufacturing software. In a standard installation, the files are located in the
\oe101c and \epicor directories.
14 Progress Version
6. Verify that your backups are valid and can be restored if needed. To test that your backup is valid, restore
your backup to a test area, not your production area.
4.2 Back Up Customized Reports
If you are using customized Crystal Reports, the report files must be backed up. These backups are very important.
Do not skip this step.
1. Go to your Crystal Reports directory.
2. Save the reports as file names different from the standard report names.
4.3 Back Up Custom Client MFGSYS Files
Use the following instructions to backup your custom MFGSYS files.
1. Go to the location of the .mfgsys files on your client workstation.
2. Create a backup of all the .mfgsys files. For example, back up the default, train, test, and pilot files.
At the end of the service pack installation, the ClientZipInstaller program will automatically run and replace any
client-side .mfgsys files, such as default, train, and test with the .mfgsys files that currently reside on the server.
The program unpacks the client files, updates the current mfgsys files and then repackages the zip file with the
updated mfgsys files. This ensures that the mfgsys files are ready for the service pack installation. After the
installation, you can run the ClientZipInstaller program anytime you need it.
Progress Version 15
Pre-Installation Epicor 9.05 Installation Guide
Part II: Pre-Installation

This part of the guide lists the steps to perform before installing or upgrading Epicor 9.05.
Chapter 5: Pre-Installation Steps
Use these steps prior to installing or upgrading the Epicor 9.05 application.
5.1 Review Epicor Application Dependencies
Use the following information to review the dependencies within the Epicor application components and modules.
• If you have SQL installed and you are using that SQL database for your transactional database, and you plan
to use Epicor Enterprise Search, you do not need to install Replication Server because you can use your SQL
database. See more detail in the Replication Server appendix.
• If you use Progress for your Epicor 9.05 application database, and you plan to install Epicor Enterprise Search,
you must also have Epicor Replication Server installed.
5.2 Review Software Requirements
Software requirements have been updated for this release. Use the following information to update your system.
• Windows Server 2008 or Windows Server 2008 R2 must be installed on the server.
• If you use a Windows XP workstation, you must have Windows XP Service Pack 2 installed.
• You must have the Microsoft Internet Information Services (IIS) installed in order to use several features of
the Epicor application, including Embedded Education Courses, and Epicor Web Access. If you do not have
IIS installed, refer to your operating system documentation for instructions.
• If you are hosting an Epicor Web Access site on the Epicor application server, the IIS Server name must not
include the underscore character. If the IIS Server name has an underscore character, the user will not be able
to log in.
• To run the Epicor Administration Console, you must have the latest Microsoft Management Console (MMC)
3.0 or later installed. See the Microsoft MMC 3.0 download site for download information.
• If you have Customer Connect, the service pack for that product must be installed on your system.
5.3 Review Hardware Requirements
Hardware requirements may have changed for this release. For a complete list of requirements, review the Epicor
9.05 Hardware Sizing and Configuration Guide on the EPICWeb Support website.
5.4 Verify Windows Server 2008 Compatibility
If you have Windows Server 2008 installed on your server, use the following steps to verify the compatibility with
the Epicor Application.
1. If you use Windows Server 2008, note that to open an executable file, you do not double-click the file.
Instead, you right-click and select the Run as an Administrator option.
16 Progress Version
Epicor 9.05 Installation Guide Pre-Installation
2. If you use Windows Server 2008, you also need to install Application Server and IIS with V6 compatibility.
3. With Windows Server 2008, a firewall is installed. The firewall needs to be disabled in order for connectivity
from other machines to allow for administering of the Epicor 9.05 Appservers. Based on your company
practices, you can enable your firewall after the installation process is complete.
5.5 Determine Web Service Type: WSE or WCF
Use this information to determine which type of Web Service you will install later in the installation process.
Epicor 9.05 is compatible with two types of Web Services: WSE (Web Service Enhancements) and WCF (Windows
Communication Foundation). Based on Microsoft development, WSE will be replaced with WCF.
• If you are a new customer, you can choose to start using WSE or WCF. It is recommended you use the WCF
version. Note that WCF is included as part of the base .NET 3.5 framework.
• If you are an existing customer using WSE, and you have already invested resources and time in Epicor Service
Connect workflows or custom coding that use WSE, you can choose to continue with WSE and start
transitioning over to the WCF version.
For more information on WCF, click this link to read the article What is WCF:
http://msdn.microsoft.com/en-us/library/ms731082(VS.85).aspx
5.6 Review Epicor 9.05 Functionality
It is recommended that you become familiar with the features available in the Epicor 9.05 release prior to installing
the Epicor 9.05 application.
1. Review the Epicor 9.05 Feature Summary to learn about the features available in the Epicor 9.05 release.
To access the 9.05 Feature Summary, log onto the EPICWeb Documentation site and click the link for Feature
Summaries.
Note You can also view the Feature Summary using the online help system.
2. If desired, contact the Services group to learn more about upgrading or migration to Epicor 9.05.
Note To request assistance from Services, fill out theServices Request Form. The form is available on
the EPICWeb Services site. You can use the following link:
https://epicweb.epicor.com/services/Pages/default.aspx.
5.7 Disable Error Reporting
Use the following steps to disable error reporting on your workstation. This step is recommended in order to
save processing time by not automatically reporting software issues during installations. Based on your company
practices, you can enable error reporting after the installation process is complete. Note that the steps differ
based on your operating system.
5.7.1 Using Windows 7
1. Verify that you have administrator privileges.
2. Open the Local Group Policy Editor. To do this, open Start > Search. Type gpedit and press Enter.
Progress Version 17
3. Navigate to Computer Configuration > Administrative Templates > System > Internet Communication
Management > Internet Communication Settings.
4. From the main window, select Turn Off Windows Error Reporting.
5. On the dialog, select the Enabled check box. Click OK. The change takes place immediately.
5.7.2 Using Windows Vista or Windows Server 2008
1. Right-click on Control Panel.
2. If you do not view your Control Panel by classic view, click on System Maintenance.
3. Click Problem Reports and Solutions.
4. Click on Change Settings in the left sidebar.
5. Click the Advanced Settings button.
6. Turn off Problem reporting.
5.7.3 Using Windows Server 2008 R2
1. Navigate to Start > Control Panel > System and Security.
2. Select Action Center. Select the Change Action Center Settings link.
3. Select the Problem reporting settings link.
4. Select Never check for solutions button. Click OK.
5.8 Download Latest Updates
Use these steps to download the latest service pack and patch files that will be installed later in the installation
process.
Note You can use this link:https://epicweb.epicor.com/Support/epicor9/Downloads
3. Download the latest Epicor 9.05 application service pack related to this installation. For example, select one
of the following files, based on your environment:
• Progress on Windows (32 bit): SP90560x-P.EXE
• Progress on Windows (64 bit): SP90560x-P64.EXE
18 Progress Version
Epicor 9.05 Installation Guide Pre-Installation
4. Download the latest Epicor 9.05 application patch related to this installation, if one is available. For example,
select one of the following files, based on your environment:
• Progress on Windows (32 bit): PA90560xx-P32.EXE
• Progress on Windows (64 bit): PA90560xx-P64.EXE
5. Download the latest Epicor 9.05 help content pack related to this installation. For example, download the
HELP90560x.EXE file.
5.9 Download Latest OpenEdge Updates
Use these steps to download the latest Open Edge service pack and service pack hot fix files.
Note You can use this link: https://epicweb.epicor.com/Support/epicor9/Downloads
2. Navigate to Epicor 9 > Version 9.05.600 > Third Party Products > OpenEdge > 10.2A.
3. Based on your environment, go to the appropriate folder. Download the latest OpenEdge service pack file
onto your machine, if it is not already installed. For example, select one of the following files:
• For Windows 32: 102ASP3.exe
• For Windows 64: 102ASP3x64.exe
4. Based on your environment, go to the appropriate folder. Download the latest OpenEdge service pack hot
fix file onto your machine, if it is not already installed. For example, select one of the following files:
• For Windows 32: Rl102asp0323hf.exe
• For Windows 64: Rl102asp0323hf-64.exe
5. If you want to use the OpenEdge Explorer tool instead of the Progress Explorer Tool, you can access the files
from the Epicor 9.05 DVD or download them from EPICweb. To download the files, based on your
environment, go to the appropriate folder. Download the latest OpenEdge Management file onto your
machine. For example, select one of the following files:
• For Windows 32: OEM102A_nt.exe
• For Windows 64: OEM102A_nt64.exe
Note From the OpenEdge > 10.2A folder, you must also download the OpenEdge Management
Guide file(OpenEdgeManagement_Guide.pdf).
5.10 Setup Progress OpenEdge Explorer Tool

If you want to use the OpenEdge Explorer tool instead of the Progress Explorer Tool, use these steps to setup
the OpenEdge Explorer tool.
1. Verify that your OpenEdge admin services are not running.
Progress Version 19
2. Go to the OpenEdge Management Guide that you previously downloaded. The file is called
OpenEdgeManagement_Guide.pdf.
3. Use the guide for instructions on setting up the OpenEdge Explorer tool.
Note You can use the OpenEdge Management files you previously downloaded from EPICweb, or
you can access the files from the Epicor 9.05 DVD in the OEManage folder.
4. After being installed, you can access the OpenEdge Explorer tool from Start > Programs > OpenEdge
Explorer.
20 Progress Version
Epicor 9.05 Installation Guide Installation
Part III: Installation

This part of the guide explains how to install or upgrade the Epicor 9.05 application.
Chapter 6: Install the Epicor 9.05 Server
This installation 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.
6.1 Install Microsoft Tools: .NET 3.5 and WSE or WCF Runtime (Server)
Use the following steps to download and install Microsoft tools, such as .NET and either WSE (Web Services
Enhancements) or WCF (Windows Communication Foundation) from the Microsoft Download Center website.
Note that WCF is included as part of the base .NET 3.5 framework.
Note Review your decision to install either WSE or WCF which you determined during a Pre-Installation
step.
1. Click the following link to go to the Microsoft Download Center to Download Microsoft .NET 3.5: http://w
ww.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=ab99342f-5d1a-413d-8319-81da47
9ab0d7
a. Download the latest version of Microsoft .NET 3.5 to your server.
b. Use the instructions provided on the website to guide you through the installation process.
Note The .NET 3.5 installation includes the .NET Service Pack when you download.NET 3.5 from the
Microsoft Download Center website.
2. If you want to install WSE, click the following link to go to the Microsoft Download Center toDownload
Web Services Enhancements (WSE) 3.0 Runtime: http://www.microsoft.com/downloads/details.aspx?Famil
yID=1F445589-818A-4E7B-B49B-FFE9393E4D0A&displaylang=en
a. Download the latest version of Microsoft Web Services Enhancements (WSE) 3.0 Runtime to your server
and/or Windows Admin workstation.
Progress Version 21
Installation Epicor 9.05 Installation Guide
6.2 Stop Appservers and Database
If you have OpenEdge already installed, use the following steps to stop the appservers and database prior to
starting the installation.
1. Sign on to the server and/or Windows Admin workstation as Administrator or Administrator equivalent.
2. Existing customers (Epicor 9/Vantage/Vista) need to use the Progress Explorer Tool or OpenEdge Explorer
Tool to stop the following functions in order:
• Stop the Appservers.
• Stop the OpenEdge database.
3. Select Start > Settings > Control Panel > Administrative Tools > Services. The Services window appears.
4. Right-click on AdminService for OpenEdge 10.1C, and select Properties. The AdminService dialog box
appears. On the General tab, click Stop. Click OK.
5. Close all applications except Windows.
6.3 Start Server Installation
Use the following steps to start the server installation.
1. Insert your Epicor 9.05 DVD in the server's DVD-ROM drive (D:\). The autorun feature should launch the
Epicor 9.05 Installation program. If not, choose Start > Run and enter the command: D:\setup.exe.
2. The Welcome dialog box appears. Click Next.
3. The Check Customer Center on the Web option appears. Click Next.
4. The Select the Software to Install window appears. Select the Install Epicor 9.05 Server option. Click
Next.
6.4 Install Progress OpenEdge 10.2A
Use these instructions to install Progress OpenEdge 10.2A on your server and/or Windows Admin workstation.
You will need to reboot the server after completing this section.
Note If you are using Windows Server 2008, the Progress Explorer Tool is not available. Instead, you must
set up a workstation to act as the Windows Admin Workstation. A remote Progress Explorer Tool connection
must be made from this Windows Admin Workstation to the server running Windows Server 2008 in order
to monitor appservers and database status.
1. Review the 10.2A OpenEdge Getting Started: Installation and Configuration Guide (on the Progress
Software Developers Network website) if you plan to select the Advanced/Manual type installation of
OpenEdge. If you plan to select the Typical/Automatic installation, you do not need to review this guide.
2. Launch the installation program and proceed to the Select the Software to Install window. Click Install
Epicor 9.05 Server. Click Next.
22 Progress Version
3. On the Epicor 9.05 Server Setup menu, click Install OpenEdge 10.2A.
4. The Welcome window appears. Click Next.
5. The Progress OpenEdge Type of Install window appears. Select the type of installation based on your
current system:
• OpenEdge Typical/Automatic Install -- Select if the OpenEdge software should automatically specify
web server settings and permissions. This is a preferred method of installation for systems that have
never had OpenEdge installed. The installation runs and displays a minimized icon in the task bar.
• OpenEdge Advanced/Manual Install -- Select if you want to customize how OpenEdge is installed.
This includes manually specifying the software and working paths, web server settings, and permissions.
This is the preferred method of installation for existing systems that have a version of OpenEdge previously
installed.
6. For either selection, click Next.
7. Depending of which install you selected, use one of the following sets of steps: Typical/Automatic or
Advanced/Manual.
6.4.1 If you selected the Typical/Automatic Install option
1. Select the OpenEdge folder location for the Progress software directory. Even though the default directory
is C:\Program Files\Epicor\oe102a, it is recommended you select a shorter path, such as C:\Epicor\oe102a.
2. If you need to install files for the web service, select the Install Web Service Files check box. Click Next.
3. The Ready to Install window appears. Click Install.
4. You may be prompted with registry warnings if the following file extensions have already been registered
as configuration file types: .CFG, .DB. When prompted, select Y.
5. A status meter appears indicating the progress of the installation. When the installation is finished, you are
returned to the desktop.
6. Reboot your server.
6.4.2 If you selected the Advanced/Manual Install option
1. The OpenEdge 10.2A window appears. Click Install.
3. Enter the serial numbers for the products that you will be using. Click Next.
4. On the Before You Start window, click Next.
5. On the Select Server Engines window, click Both. Click Next.
6. On the Previous Installation Settings, click No.
Progress Version 23
7. On the Destination and Working Path Directories window, select the destination and working path
directories. Recommended paths are \Epicor\oe102A and \Epicor\oe102A_wrk. Click Next.
8. On the Setup Type window, click Complete. Click Next.
9. On the Configuring/Installing Components window, clear the Sonic ESB option. Click Next. If you leave
the settings blank, click OK at the alert message.
10. On the Program Folder window, select the OpenEdge 10.2A group. Click Next.
11. On the Web Server Type window, select the Microsoft Web Server (IIS) or ISAPI - compatible check
box. Browse and select the Web Server Script directory and the Web Server Document Root directory.
Recommended paths are C:\InetPub\adminscripts and C:\InetPub\wwwroot. If these are unknown, for each
directory select C:\Epicor. Clear the Copy static HTML files to Document Root directory check box. Click
Next.
12. On the Language window, select the default language. Click Next.
13. On the International Settings window, select your settings. Click Next.
14. If you have configured the web server, configure the web services adapter settings. If not, accept the defaults.
Click Next.
15. On the Admin Server Authorization Options window, select the security options for the Admin Server.
Click Next.
16. On the Summary window, click Next. The installation begins. The installation can take up to 45 minutes
on older machines.
17. Click Finish. The Commit Shared Files window appears.
6.5 Install Progress OpenEdge 10.2A SP
Use the following instructions to install the latest Progress OpenEdge service pack file on your server and Windows
Admin workstation.
Important Do not skip this step.
1. For existing users, use the Progress Explorer Tool or OpenEdge Explorer Tool to stop any OpenEdge App
Servers or databases that may be currently running.
2. Select Start > Control Panel > Administrative Tools > Services. The Services window appears.
3. Right-click on AdminService for OpenEdge 10.2A, and select Properties. The AdminService dialog box
appears. On the General tab, click Stop. Click OK.
4. Go to the OpenEdge service pack file that you downloaded to your machine during a Pre-Installation step.
5. Double-click the OpenEdge service pack file. The installation program opens.
24 Progress Version
7. Click Next to confirm you have backed up your system files.
8. Click Next to confirm the summary information. The installation proceeds.

Note You may be prompted with registry warnings if the following file extensions have already been
registered as file types: .I, .DB, .UDF, .CLS. When prompted to overwrite the registry entry and register
this file extension as a Progress file, select Y
9. Click Finish. The Service Pack installation is now complete.
6.6 Install Progress OpenEdge 10.2A SP Hot Fix
Use the following instructions to install the latest Progress OpenEdge service pack hot fix file on your server and
Windows Admin workstation.
Important Do not skip this step.
1. Go to the OpenEdge service pack hot fix file that you downloaded to your machine during a Pre-Installation
step.
2. Double-click the file. The installation program opens.
4. Click OK to confirm you have stopped the OpenEdge related functions.

Note If you have not stopped the AppServer, database and AdminServices functions, click No and
then stop the functions before continuing.
5. Select the OpenEdge 10.2A directory as your Destination directory. For example, select C:\Epicor\oe102A.
Click Next.
6. The Ready to Install window appears. Click Next. The installation proceeds.
7. Click Finish. Depending on your selection, the files appear for review.
6.7 Share the Epicor Folders
Use the following steps to share the Epicor folders.

Note If you are using Windows Server 2008, the steps may be slightly different.
1. On the C: drive, create the C:\Program Files\Epicor Software\Epicor905 folder if it does not already exist.
a. Right-click on the \Epicor Software\Epicor905 folder and select Sharing and Security.
b. Select the option to Share this Folder. Epicor905 displays as the default share name. Do not change
the name. The folder must be named Epicor905.
Progress Version 25
c. Click the Permissions button. It is recommended that you assign Full Control to the Everyone group.
Click OK to accept the permissions.
d. Click the Security tab. It is recommended that you assign read-only permissions to Users. Read-only
includes Read & Execute, List Folder Contents, and Read. Add an Administrator and assign the
Administrator Full Control. Click OK.
2. On the C: drive, create the C:\Program Files\Epicor Software\EpicorData folder.
a. Right-click on the folder icon and select Sharing and Security.
b. Select the option to Share this Folder. EpicorData displays as the default share name.
c. Click the Permissions button. It is recommended that you assign Full Control to each user folder. Click
OK.
d. Click OK to accept the share options.
6.8 Install Epicor 9.05 Server Software
Use the following steps to install the server software.
1. Launch the installation program and click Next to proceed to the Select the Software to Install window.
Select the Install Epicor 9.05 Server button. Click Next.
2. On the Epicor 9.05 Server Setup window, select the Epicor 9.05 Server Software option.
3. Select the Server platform option you want to run:
a. OpenEdge on Windows
After selecting your platform option, the InstallAware Wizard verifies that your software environment is
compatible with your selection. This may take several minutes.
4. The Welcome window appears for installing the server software. Click Next.
5. The Destination Location window appears, prompting for the destination path for the software and for the
printer work path. Enter the paths of the installation directory and the printer work directory. Click Next
after specifying the locations.
• The default installation directory for a 32-bit Epicor application on a 32-bit Windows install or a 64-bit
Epicor application on a 64-bit Windows install is C:\Program Files\Epicor Software\Epicor905 or specify
a different drive location.
• The default installation directory for a 32-bit Epicor application on a 64-bit Windows install is C:\Program
Files (X86)\Epicor Software\Epicor905 or specify a different drive location.
• The default printer work directory for a 32-bit Epicor application on a 32-bit Windows install or a 64-bit
Epicor application on a 64-bit Windows install is C:\Program Files\Epicor Software\EpicorData or specify
a different drive location.
• The default printer work directory for a 32-bit Epicor application on a 64-bit Windows install is C:\Program
Files (X86)\Epicor Software\EpicorData or specify a different drive location.
26 Progress Version
6. The Server Setup window appears, prompting for the UNC path name for the Share directory for clients.
The default is \\<servername>\Epicor905\, where \\<servername> equals the machine name of the server.
Click Next.
7. The Start Installation window appears. Click Next. Processing messages appear. This may take several
minutes.
8. On the Server Setup window, click Finish. If prompted to confirm exiting the setup program, click OK.
The server software installation is complete.
Progress Version 27
Chapter 7: Install Latest Updates
Use these steps to install the latest Epicor 9.05 service pack, patch and help system patch on your system.
In these instructions, drive C: refers to a local hard drive. If your local hard drive is assigned to a different letter, substitute
that letter during these instructions.
Some of the instructions are based on using Windows Server 2008. If you use a different operating system you may
need to make slight adjustments to the instructions.
7.1 Verify Specific Folders are Not Read-Only
Use these steps to verify that the Client, ClientServer and Server folders are not read-only. These folders need to
have write access so that files can be added to them during the installation.
1. Go to the location where your Epicor 9.05 application is installed. For example, go to C:\Program Files\Epicor
Software\Epicor905.
2. Right-click on the Client folder.
3. Select Properties.
4. On the General tab, unselect the Read Only check box.
5. Click Apply.
6. The Confirm Attribute Changes dialog appears. The Apply changes to this folder, subfolders and
files option is selected by default. Click OK.
7. Click OK to exit the Client Properties folder.
8. Repeat the previous steps for the ClientServer folder.
9. Repeat the previous steps for the Server folder.
7.2 Install Epicor 9.05 Service Pack on the Server
Use these instructions to install the Epicor 9.05 service pack on the server.
1. Go to the directory where you downloaded the latest service pack file.
2. Double-click on the file to run it.
3. The InstallAware Wizard window appears. A status bar shows the progress of verifying the contents of the
Service Pack setup package. This verification may take several minutes.
4. A Welcome window appears. Click Next.
5. The Application Requirements window appears. Review the upgrade status for each required component.
Possible statuses include:
• If all components have a Pass status, all components are valid.
28 Progress Version
• If any components have a Fail status, click the Details button to review additional information. After
reviewing the details, click Close. Resolve the issues and click Check Again. Continue to resolve the
issues until all components have a Pass as an Upgrade Status.
6. Review the default directory that is displayed. This is the directory where your Epicor application program
files are located. Click Change and select a different directory if the installation you want to update is not
the one listed. Click Next.
7. If you use Country Specific Functionality (CSF), review the notification regarding licensing. Click Next.
8. The Start Installation window appears. Click Next. The installation begins.
Note If prompted with a message that your Properties file is being modified, click Restart After.
The installation continues as normal.
9. When the installation is complete, click Finished.. The Epicor application service pack is now installed.
7.3 Install Epicor 9.05 Patch on the Server
Use these instructions to install the Epicor 9.05 patch on the server, if a patch is available.
1. Go to the directory where you downloaded the patch file.
4. A confirmation window appears. Click Yes to proceed.
5. Enter the directory where your program files are located. Click Next.
6. Enter the directory where your OpenEdge files are located. Click Next.
7. You may be prompted to verify your server name, operating system or database type. If prompted, select
the appropriate option and click Next. Note that this prompt is only displayed if your mfgsys.ver file is
incomplete.
8. The Start Installation window appears. Click Next.
9. A message appears, stating that the application patch installation is complete. Click Finished.
The Epicor application patch is now installed.
7.4 Install Epicor 9.05 Help Content Pack
Use these steps to install the Epicor Help Content Pack on your system. The Help Content Pack contains the
updated online help system available with this release. Typically, Help Content Packs are available with Service
Pack releases, not Patch releases.
1. Go to the directory where you download the latest Epicor 9.05 Help Content pack file.
Progress Version 29
4. Enter the directory where your program files are located. Click Next.
5. The Start Installation window appears. Click Next.
6. A completion message appears. Click Finish.
The Help Content Pack is now installed.
30 Progress Version
Chapter 8: Install Epicor Administration Functionality
Use these instructions to install Epicor administration functionality.
8.1 Install Epicor Administration Console
Use these steps to install the Epicor Administration Console on your server and/or on your Windows Admin
Workstation.
1. Go to the directory where your Epicor application is installed.

Example Go to C:\Program Files\Epicor Software\Epicor905.
2. Double-click on the EpicorUtilities.exe file.
3. On the Welcome to the Epicor Utilities Setup wizard, click Next.
4. On the Epicor Utilities Setup dialog, click the Install Administration Console button to start the installation.
5. On the Welcome dialog, click Next.
6. On the Confirm Installation dialog, click Next. The files are installed.
7. When the installation is complete, click Close.
The Epicor Administration Console is now installed.
Progress Version 31
Chapter 9: Install the Epicor 9.05 Client
Use the following instructions to install the Epicor 9.05 client on your workstation.
9.1 Before You Start
Use the following instructions before you install the client.
1. Verify you have Internet Explorer version 6 (or greater) installed on each workstation.
2. Be sure to log in as the Local Administrator on the client workstation.
9.2 Install Microsoft Tools .NET 3.5 and WSE or WCF Runtime (Client)
Use the following steps to download and install Microsoft tools, such as .NET and either WSE (Web Services
Enhancements) or WCF (Windows Communication Foundation) from the Microsoft Download Center website.
Note that WCF is included as part of the base .NET 3.5 framework.
Note Review your decision to install either WSE or WCF which you determined during a Pre-Installation
step.
1. Click the following link to go to the Microsoft Download Center to Download Microsoft.NET 3.5: http://w
ww.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=ab99342f-5d1a-413d-8319-81da47
9ab0d7
a. Download the latest version of Microsoft .NET 3.5 to your workstation.
Note The .NET 3.5 installation includes the .NET Service Pack when you download .NET 3.5 from
the Microsoft Download Center website.
2. If you want to install WSE, click the following link to go to the Microsoft Download Center to Download
Web Services Enhancements (WSE) 3.0 Runtime:
http://www.microsoft.com/downloads/details.aspx?FamilyID=1F445589-818A-4E7B-B49B-FFE9393E4D0A&displaylang=en.
a. Download the latest version of Microsoft Web Services Enhancements (WSE) 3.0 Runtime to your server
and/or Windows Admin workstation.
9.3 Install Epicor 9.05 Client Software
Use the following instructions to start the client installation. New customers or existing customers who are adding
a new client workstation should use the following instructions to install the Epicor 9.05 Client.
1. On the client workstation, use Windows Explorer to navigate to the server where Epicor 9.05 was just
installed.
32 Progress Version
2. Go to the Epicor905 folder. Double-click to run the Epicor9Client.exe file.
3. The Epicor 9.05 Client Setup menu opens. Click Install Epicor 9.05 Client Software.
4. The Welcome window appears for installing the client software. Click Next.
5. The Destination Folder window appears. Specify the Client Destination and the Server Share Location path.
a. For the Client Destination, click Browse to navigate to a destination folder. For example, you can use
C:\Program Files\Epicor Software\Epicor905.
b. For the Server Share Location, use \\<servername>\Epicor905, where <servername> is the machine name
where the server installation was done.
c. Click Next.
6. The Shortcut Creation window appears. Select the Create Desktop Icons check box to create the following
shortcut icons on your client desktop.
a. Epicor 9.05: Select this checkbox to run your Epicor 9.05 database from this workstation.
b. Epicor 9.05 MES: Select this checkbox to run the Data Collection programs from this workstation.
7. On that same window, you can also select the following check boxes to create icons in your program menu:
• Create Training Icons: Select this checkbox for training icons that can access the training database.
• Create Test Icons: Select this checkbox for test icons that can access the test database.
• Create Pilot Icons: Select this checkbox for pilot icons that can access the pilot database.
8. Click Next.
9. The Ready to Install the Application window appears. Click Next.
10. When finished, click Finish to complete.
11. If prompted, reboot the workstation at this time.
9.4 Install Crystal Reports 2008 Runtime (Client)
Use the following steps to install Crystal Reports 2008 Runtime on your client. You can also use these steps to
install Crystal Reports 2008 Runtime on your server or Windows Admin workstation if you plan to print Crystal
Reports forms from your server or Windows Admin workstation.
Note You cannot install both Crystal Reports 2008 Runtime and Crystal Reports 2008 Developer on the
same client.
1. If you have a previous version of Crystal Reports .Net Runtime installed on your client, use the following to
uninstall the previous version:
a. Navigate to Start > Control Panel > Add or Remove Programs.
b. Select Crystal Reports .Net Runtime and click Remove.
c. Verify the uninstallation was completed successfully.
Progress Version 33
2. Log on to EPICweb and go to the Customer Portal Page. Navigate to Support > Epicor 9 > Downloads..
3. Navigate to Epicor 9 > Version 9.05.600 > Third Party Products > Crystal.
4. Download the latest Crystal 2008 Runtime file. For example, download Crystal_2008_03_Runtime.zip.
5. Navigate to the downloaded file. Open the .zip file and extract the contents.
6. Double-click to run the EXE file. For example, run the CRRuntime_12_3_mlb.exe file.
7. The Welcome window appears for Crystal Reports 2008 Runtime. Click Next.
8. Review the license agreement information. Select I accept the License Agreement. Click Next.
9. Specify the folder for the installation of Crystal Reports 2008 .Net Runtime, and select Everyone as the user
of the computer. Click Next.
10. When prompted for the Product ID, do the following:
a. Using a text editor, open the License Key.txt file that was extracted in a previous step.
b. Copy the text and paste it into the Product ID field.
c. Click Next.
11. If prompted, confirm the installation. Click Next.
12. The installation proceeds. When it is finished, click Finish.
9.5 Copy Shortcuts for All Users
Use these steps to make the shortcuts available on the Start menu for all users.
1. Go to the location where your system is installed. For example: C:\Documents and Settings\<user>\Start
Menu\Programs\Epicor Software.
2. Copy the Epicor905 folder.
3. Go to the Epicor Software folder. For example: Users\Public\Start Menu\Programs\Epicor Software
4. Paste the Epicor905 folder.
34 Progress Version
Epicor 9.05 Installation Guide Post-Installation
Part IV: Post-Installation

The following procedures explain the steps you perform after installing or upgrading Epicor 9.05, right up to
logging into the application client.
Chapter 10: Post-Installation Steps on the Server
Use the following instructions to set up your server after installation.
10.1 Verify Parameter File Settings
Use these steps to verify the parameter settings that are defined in the *.pf files. Several parameter settings are
required in order for your appservers to start and for your system to run properly. The parameter settings may
differ based on your database type, either Progress or SQL.
Note If the required parameters are not included in the *.pf file, your appservers will not start.
1. On the server where your Epicor application is installed, navigate to the Server\Config folder.
2. With a text editor, open the parameter file for the database you want to configure. For example, parameter
files include: Mfgsys.pf, MfgTrain.pf, MfgTest.pf, MfgPilot.pf.
3. For both SQL and Progress databases, use the following to verify the required parameters in the .pf file.
Parameter Description Required Value

-disabledeltrig Disable delete trigger to allow replication logic to run properly. -disabledeltrig
Even if you do not use replication, this parameter is required.
This parameter must not be the last line in the .pf file.
-rereadnolock changes read-only record retrieval to get consistent results -rereadnolock
-ttmarshal Improve performance -ttmarshal 5
-tmpbsize Improve performance by allowing appserver agent to hold -tmpbsize 8
more temporary table records before paging them out to the
temporary disk file. If the value is not 8, a warning message
is displayed but the appservers are allowed to start.
4. For SQL databases only, use the following to verify the required parameters in the .pf file.
Parameter Required Value

PRGRS_NOWAIT_OVERRIDE PRGRS_NOWAIT_OVERRIDE,1
TXN_ISOLATION TXN_ISOLATION,1
PRGRS_NATIVE_LOCKWAIT PRGRS_NATIVE_LOCKWAIT,30000
Progress Version 35
Post-Installation Epicor 9.05 Installation Guide
5. For both SQL and Progress databases, use the following to verify the optional parameters in the .pf file.
Parameter Description Optional Value

-Bt Improve appserver performance in dealing with temporary tables. -Bt 4096
Increase the value based on the amount of memory on the server
where the Epicor application is installed. For example, for 4 GB of
RAM, increase value to 4096; for 8 GB of RAM increase to 8192.
6. If needed, review the parameter values in the following example .pf files.
• Example: Progress
• Example: SQL
• Example: SQL Unicode
36 Progress Version
7. Later, when you start your appserver, if the appserver does not start due to parameter validation issues,
review the appserver log file. In a standard installation, the log file is located in the Server\Logs folder.
10.2 Establish Security for Progress AppServer
Use the following instructions to setup security and allow necessary privileges for the Progress AppServer software.
These instructions can be used anytime, not just after installation, to keep your company's security requirements
current.
10.2.1 Establishing an administrative account
1. Create an account, or use an existing account, as an administrator. The account can be local (only to the
server) or a domain account (usable anywhere).
2. Verify that the account has administrative rights on the server where Progress OpenEdge 10 is installed.
10.2.2 Establishing Local Security Policy
Use the following instructions to establish the local security policy.
1. Using the admin logon account specified above, select Control Panel > Administrative Tools > Local
Security Policy.
2. On the left pane, select Local Policy > User Rights Assignment.
3. In the right panel, double-click each of the following Policies, and add the domain User Account of the
user or group with system administrative rights for the server. You will connect these accounts through
Progress Explorer.
• Act as part of the operating system
• Adjust memory of quotas for a process
• Create a token object
• Create permanent shared objects
• Log on as a batch job
• Log on as a service
• Replace a process level token
10.2.3 Establishing the AdminService Setting
Use the following instructions to establish the AdminService setting.
1. Use the Progress Explorer Tool or OpenEdge Explorer Tool to verify that your appservers and databases are
not running.
2. Using the admin logon account specified above, select Control Panel > Administrative Tools > Services.
3. Verify that the AdminService is stopped. To do this, right-click AdminService for OpenEdge 10.2A and
select Stop if the service is running.
Progress Version 37
4. To set up the service account, right-click AdminService for OpenEdge 10.2A and select Properties.
5. In the Log On section, click This Account, and specify the same user or group as with the Local Security
Policy settings. Again, the user or group must have administrative rights for the whole server.
6. Click OK. Then exit the Services window.
7. Click Start to start the service.
10.3 Upgrade to Service Connect 9.05
If you use Epicor Service Connect, you must upgrade to the latest version. Use the following instructions to
upgrade to the latest version of Service Connect, such as Service Connect 9.05.
1. Go to the directory where your system is installed.
2. Run the runtime version of Service Connect 9.05.
3. Test your system to verify that Service Connect works successfully.
10.4 Upgrade to Epicor Portal 9.05
If you use Epicor Portal, you must upgrade to the latest version. Use the following instructions to upgrade to the
latest Epicor Portal version, such as Epicor Portal 9.05.
1. Locate the Epicor Portal 9.05 Installation Guide. Click this link to access EPICweb:
https://epicweb.epicor.com/Support/epicor9/Downloads
2. Complete the instructions to upgrade your portal installation. Be sure to install any Epicor Portal service
packs after the portal installation.
3. Test your system to verify that Epicor Portal works successfully.
38 Progress Version
Chapter 11: Prepare Your Database
Use the following instructions to prepare your database prior to logging in the first time. If you are an existing Epicor
9/Vantage/Vista customer, you must complete this entire section.
Note If you are an existing customer upgrading from a 32-bit platform to a 64-bit platform, no special database
preparation is necessary. As with a normal upgrade, you must complete this entire Prepare Your Database
section.
If you use Progress and you are a new customer installing the Epicor 9.05 application for the first time, you must
complete the following sub-sections:
• Add Epicor and Application Server Connections, Import License Codes, Add Company
11.1 Convert Your Database
Use these instructions to convert your database for compatibility with the Epicor 9.05 application.
11.1.1 Pre-Conversion Tasks
1. If your database and Appservers are running, use the Progress Explorer Tool or OpenEdge Explorer Tool to
stop the following functions in order:
2. It is required that you backup and restore the database. To do this:
a. Navigate to Start > Programs >OpenEdge 10.2A > Proenv.
c. At the prompt type: probkup mfgsys mfgsys.bak
d. Copy the mfgsys.bak file to the \Epicor\Epicor905\DB folder
e. In ProEnv, go to the \Epicor\Epicor905\DB folder
f. At the prompt type: prorest mfgsys mfgsys.bak
g. Exit the ProEnv Utility.
3. It is required that you truncate the BI (before image) file. To do this:
a. Navigate to Start > Programs > OpenEdge 10.2A > Proenv.
c. At the prompt type: proutil mfgsys -C truncate bi
d. Exit the ProEnv Utility.
Progress Version 39
11.1.2 Restore Schema Holders
If you are a SQL customer, use the following steps to restore your schema holders. New customers and customers
upgrading from an existing Epicor application installation must complete these steps in order to be compatible
with the current OpenEdge version.
1. If your database and Appservers are running, use the Progress Explorer Tool or OpenEdge Explorer Tool to
stop the OpenEdge database.
2. Make a backup copy of your current schema holder files. To do this, do the following:
a. Go to the folder where your schema holder is located. For example, go to \Epicor905\db\newdb.
b. Make a copy of your current schema holder files. The schema holder files are mfgsyssh.*
3. Navigate to Start > Programs > OpenEdge 10.2A > Proenv.
4. Go to the folder where your schema holder is located. For example, go to \Epicor905\db\newdb.
5. To restore the schema holder backup file, at the prompt type one of the following commands, based on
your environment:
• SQL (32 bit): prorest mfgsyssh mfgsyssh32.bkup
• SQL (64 bit): prorest mfgsyssh mfgsyssh64.bkup
• SQL Unicode (32 bit): prorest mfgsyssh mfgsyssh32U.bkup
• SQL Unicode (64 bit): prorest mfgsyssh mfgsyssh64U.bkup
6. Exit the ProEnv Utility.
7. If you use Extended UD Table functionality, use Epicor Admin Tools to rerun your Schema Changes for the
extended UD tables.
11.1.3 Run Schema Change
Use these steps to run the schema change.
1. Use the Progress Explorer Tool or OpenEdge Explorer Tool to start the databases which you will be converting
to the Epicor 9.05 level.
2. Open the Epicor Schema Change program. To do this, navigate to Start > Programs > Epicor Software
> Epicor 9.05 > Epicor Schema Change icon for the appropriate database.
Note If prompted with a message that it is unable to open message file: PROMSGS, click OK to the
message. Then, you need to edit the Shortcut properties. To do this, right-click on the icon and select
Properties. In the Target field, locate the part of the path that says server\config\epicor905.ini
and add a "\" character before that part of the path. For example, it should look like:
\server\config\epicor905.ini. Note that there needs to be a "\" before the word server. Do not
change the rest of the target path.
3. The Schema Change Required window appears. In the Password field, enter CHANGESCHEMA. Click
Continue.
40 Progress Version
4. The Finish window appears. Click OK.
11.2 Add Epicor and Application Server Connections
Use the following steps to use the Epicor Administration Console to add and then connect to the Epicor and
application servers.
1. Use the Progress Explorer Tool or OpenEdge Explorer Tool to verify that your Epicor database and main
AppServer are running.
2. Login to the Epicor Administration Console. To do this, select Start > Programs > Epicor Software >
Epicor Administrative Tools > Epicor Administration Console.
Note You may be prompted to update your Microsoft Management Console (MMC) to version 3.0
or later. See the Microsoft MMC 3.0 download site for more information.
3. Right-click on the Server Management node. Select Add Epicor Server.
4. Enter the Name of the server.
5. Click Ping Server. Click OK to confirm that the server was located.
6. Click OK to add the Epicor Server.
7. Right-click the Epicor Server you just added. Select Add Application Server.
8. Select New Application Server Properties, including the following:
a. Name. Enter the name of the application server.
b. Port Number. Enter the identifier of the port to which you are connecting.
c. User Name. Enter a valid user name to log into the Epicor database.
d. Password. Enter a valid password to login to the Epicor database.
9. Click Test Connection. Click OK to confirm the connection.
10. Right-click on the Application Server you just added. Select Connect to Application Server.
Note If you are a new customer, a User Name called Manager is created when you connect to the
Application server for the first time.
The Epicor and application servers should now be configured.
11.3 Import License Codes
Use the following steps to import your Epicor 9.05 application license codes.
1. In the Epicor Administration Console, right-click on the Licensing node. Select Import License File.
2. Browse to the location where you previously downloaded the license code file. Select the file and click Open
to import the file.
Progress Version 41
3. Double-click on the licensing code to open it. The Properties dialog opens.
4. Click the Modules tab. Select the check box for each module you want enabled.
Note It is recommended that you carefully review the modules that you have selected to enable.
Failure to enable your modules may result in possible data corruption. Also, if you enable a new module
at this time, you are committing to basic configuration and implementation steps within the application.
5. Click OK.
11.4 Add Company
If you are a new customer, you must create a company. If you are an existing Vantage/Vista customer, you have
already configured your companies and you do not need to complete this step, unless you want to add a new
company.
1. In the Epicor Administration Console, right-click the Companies node. Select Add Company.
2. In the Add Company dialog, specify your company information.
3. To assign a Serial Number to the new company, click the browse button to search for a list of serial numbers.
Highlight the appropriate serial number to select it. Click OK.
4. Click OK to save the information.
5. Repeat these steps for additional companies, if desired.
11.5 Run Data Conversions
Use these steps to run the data conversions on your Epicor 9.05 application.
11.5.1 Set Epicor Admin Tools PROPATH
Use these steps to set the Epicor Admin Tools PROPATH prior to running the conversions.
1. Locate the Epicor905.ini file. In a standard installation, it is located in the following directory:
...\Epicor905\Server\Config.
2. Using Notepad, open the Epicor905.ini file. Locate the line that starts with PROPATH=.
3. In the PROPATH line, locate \BPMExec. Immediately following \BPMExec, add one of the following folders,
based on your databfase: \LiveBPM, \PilotBPM, \TestBPM or \TrainingBPM.
For example, here is the line before you make the change:
PROPATH=.,C:\Program Files\Epicor
Software\Epicor905\Clientserver,C:\Program Files\Epicor
Software\Epicor905\Server,C:\Program Files\Epicor
Software\Epicor905\BPMExec,C:\Program Files\Epicor
Software\Epicor905,c:\program files\epicor\oe102a\gui,c:\program
files\epicor\oe102a,c:\program files\epicor\oe102a\bin
42 Progress Version
And here is the line after you make the change:

PROPATH=.,C:\Program Files\Epicor
Software\Epicor905\Clientserver,C:\Program Files\Epicor
Software\Epicor905\Server,C:\Program Files\Epicor
Software\Epicor905\BPMExec\LiveBPM,C:\Program Files\Epicor
Software\Epicor905,c:\program files\epicor\oe102a\gui,c:\program
files\epicor\oe102a,c:\program files\epicor\oe102a\bin
4. Save the Epicor905.ini file.
11.5.2 Run Conversions Using Epicor Admin Tools
Use these steps to run the conversions using Epicor Admin Tools.
1. On the server, open the Epicor Admin Tools program. To do this, navigate to Start > Programs > Epicor
Software > Epicor 9.05 > Epicor Admin Tools.
Note If prompted with a message that it is unable to open message file: PROMSGS, click OK to the
message. Then, you need to edit the Shortcut properties. To do this, right-click on the icon and select
Properties. In the Target field, locate the part of the path that says server\config\epicor905.ini
and add a "\" character before that part of the path. For example, it should look like:
\server\config\epicor905.ini. Verify that there is a "\" character before the word server. Do not
change the rest of the target path.
2. Login with a valid User Id and Password. Note that the user must have Security Manager rights.
3. At the prompt for automatic mandatory conversions, click Yes. Mandatory conversion programs run.
Note If you use posting rules, the conversion process may block posting rules that are invalid. If any
rules cannot be activated, you are prompted with an informational message listing the blocked standard
rules. It is recommended that you take a screen capture of this message to be used later to review
the blocked rules.
4. To verify that the mandatory conversions completed successfully, make sure the database conversion date
is the correct date. To do this:
a. Select the Run Conversion Program option.
b. Review the list of conversions that were run. If necessary, scroll to the right to see the Date the conversion
was run.
5. When the conversions are completed, close Epicor Admin Tools.
11.6 Stop and Start Database and App Servers
Use these steps to stop and start the database and App servers. It is strongly recommended that you complete
these steps after running the automatic data conversions.
1. Use the Progress Explorer Tool or OpenEdge Explorer Tool to stop the following functions in order:
Progress Version 43
2. Use the Progress Explorer Tool or OpenEdge Explorer Tool to start the following functions in order:
• Start the OpenEdge database.
• Start the Appservers.
44 Progress Version
Chapter 12: Log in the First Time
Use the following steps to verify and test your Epicor 9.05 application upgrades the first time you log in.
Note If you are a new customer, you only complete the Set Up System Agent for Printing steps. All other
steps can be ignored.
12.1 Import Posting (Booking) Rules for Extended Rules
Use these steps to import your posting rules if you use Extended Rules. If you only use standard rules, this step
has already been automatically completed for you when you converted your data.
1. Open the Epicor 9.05 application.
2. Select Financial Management > General Ledger >Setup > GL Transaction Type.
3. From the Actions menu, select Import ACT Type.
4. Click the Input File Name button. Navigate to the Extended posting rules folder. For example, go to the
following:
• Extended rules: \\<servername>\Epicor905\server\PostingRules\Extended
5. Select one or more .XML files. You can select multiple files by pressing the Shift key while you highlight
the files. Click Open to select the highlighted files.
6. Select the Import All check box to specify that you want to import all the selected XML files. To specify
individual XML files instead, you can select the Selected check box for each file.
7. If this is not the first time you are importing posting rule files, you can select the Replace All check box to
replace your existing revision with the same name. To specify to replace individual XML files instead, you
can select the Replace Existing check box for each file.
8. Select the Change All Revision Statuses To Active check box if you want to change the revision from a
draft to active for all transaction types being imported. To specify to activate individual XML files instead,
you can select the Activate check box for each file.
9. Select the Import into all companies check box if you want to import the posting rules into each company.
Note Newly created revisions are automatically set to Active in the current company only. In other
companies, you need to update the status manually. In order to make changes, your User Id must
have access to the company.
10. Click OK to begin the import.
11. You may be prompted with the Book Mapping dialog. Select the book identifier you previously defined
from the Map Book selection list. If you want to map the selected book identifier to all transaction types,
select the Use for all transaction types check box. Click OK.
12. Click Save to save your imported financial data.
Progress Version 45
Note To copy the rules from one book to another, you can use GL Transaction Type Maintenance.
You create a revision, and then copy both the header and detail rules one at a time into a new book.
Then activate the revision.
12.2 Review Blocked Standard Posting Rules (if any)
Use the following steps to review any standard posting rules that were not updated during the conversion. If you
were not prompted with an Information message during the conversion, you can skip this step.
1. Get the screen capture of the Information message that you took during the conversion process.
2. Select Financial Management > General Ledger > Setup > GL Transaction Type.
3. Search and select a transaction type that is listed on the Information message.
4. In the Tree View area, select a revision. From the Actions menu, select Change Log Menu. Review the list
of revisions that were added and blocked during the last conversion process.
5. If a Revision you want is listed as Blocked, you can change it to Active. To do this:
a. Click on the Revision to select it.
b. From the Status drop-down list, select Active.
c. Click Save from the standard toolbar.
6. Repeat the above step for each Revision listed on the Information message.
Note If you have multiple companies, the Information message may list the same blocked transaction
type for each company. You must review the blocked posting rules for each company where you have
access.
12.3 Set Up System Agent for Printing (First Time Login)
Use the following steps to set up the System Agent for your system to enable printing.
1. Review the paths you specified during the server software installation for the following locations:
• Destination Location
• Print Folder Destination Location
• Server Share Location
2. Launch your Epicor 9.05 application.
3. Navigate to System Management > Utilities > System Agent.
4. Click Agent ID to search for the system agent identifier.
5. The identifiers are listed. Select SystemTaskAgent. Click OK.
6. In the SystemAppServer section, enter your directory paths. For example:
46 Progress Version
Directory Description Examples

Server File specifies the local path on the server to c:\Program Files\Epicor
the print directory Software\EpicorData/usr/epicor/epicordata
Client File specifies the unc path to the print \\<servername>\EpicorData
directory
Client Program specifies the unc path to the server \\<servername>\Epicor905\Server
directory
12.4 Maintain Your Customizations and Personalizations
Use the following steps to verify and maintain your customizations and personalizations. Note that the
Customization / Personalization Maintenance program attempts to automatically correct any problems that it
encounters during the verification process.
The verification process checks that each customization includes the following: a valid customization script, valid
custom properties, valid control keys, valid controls that are located on the form and properly docked, and
user-defined controls are added to the form. It also deletes customization properties that are no longer applied,
and cleans up the grid layout to remove obsolete fields.
2. Navigate to System Management > Utilities > Customization Maintenance.
3. Click the Search icon (binoculars) from the tool bar.
4. Select Customization as the Type and All as the Status.
5. Click Search. The customizations are displayed. Click Select All and then click OK to select all.
6. Click on the Actions menu.
7. Select the Verify All command.
8. You are warned that this process may take several minutes. Click Yes.
9. The verification process reviews the selected personalizations and customizations. When complete, you are
returned to the Customization/Personalization Maintenance window.
10. Select a customization/personalization you want to review.
11. Click the Warnings tab to review any elements that were not validated. Usually warnings are caused by
properties stored in the customization data that cannot be applied. Common warnings that you might see
include:
a. Cannot locate control on form. The key used for the customization is no longer on the form. This could
result from a renamed control or changed EpiGuid.
b. Could not set the property. No code exists that sets this property.
c. EpiBinding is not valid. Identifies the database field that should be used.
d. Invalid Parent Type. Custom control was added to an invalid parent.
Progress Version 47
12. Use the Run, Modify, and Show Custom Data features from the Actions menu to correct the warnings.
13. After fixing a warning, select the row and click Remove Selected Item.
14. Click the Errors tab to review error messages generated by the selected program. Usually errors are caused
by problems with the customization script.
15. Use the Run, Modify, and Show Custom Data features from the Actions menu to correct the errors.
16. After fixing the errors, from the Actions menus, select Verify Customization.
17. Click the Detail tab to verify that the customization has passed validation. If it is valid, the current
manufacturing version is Valid For and Pass is the Status.
18. Repeat these instructions and select Personalization as the Type to verify and maintain your personalizations,
if necessary.
12.5 Test Business Activity Query (BAQ) Calculations
During the Epicor 9.05 installation, unused obsolete fields are automatically deleted. Obsolete fields that are used
in calculations within BAQ are not deleted, but calculations with obsolete fields no longer work.
1. Review your calculations within any BAQs you want to continue using after upgrading your system.
2. Launch the online help system.
3. Review the Schema Change topic to see which fields have been changed or removed.
4. Change each BAQ calculation so that it uses current fields.
After you upgrade, your BAQ reports should work since your fields are valid.
12.6 Test Business Activity Manager (BAM) Upgrades
If you use any global alerts that activate procedure (.p) programs, use these steps to compile these programs
using the newly installed Progress 10.2A.
1. Review each BAM event that has a procedure program on your system. Verify that it still has a valid business
reason for being upgraded to the next version.
2. Add Comments within your procedure program, explaining your changes.
3. Save each BAM event, including the procedure files, in an archive location.
4. Move these BAM events and their procedure files to a new location.
5. If any Epicor 9.05 schema changes affect the procedure program, update the .p program to reflect the new
schema.
6. Compile each procedure program using Progress 10.2A.
7. Test each procedure program for issues.
48 Progress Version
12.7 Update and Test Business Process Management (BPM) Directives
Use these instructions to update your outdated BPM directives after upgrading and to identify any that need
special attention due to schema changes or other factors.
Note You must use these steps to properly upgrade your BPM directives. You can not just copy the BPM
directives in the Epicor905\BPM\bo directory to another directory. You also cannot keep the BPM directives
in the current folder, they must be properly upgraded to a new location.
1. Navigate to System Management > Business Process Management > General Operations > Directive
Update.
2. From the Actions menu, select Recompile All Outdated Directives. As the directives are converted and
re-compiled, an hour glass is displayed.
3. Upon completion, the compile results are displayed. Any Method Directives that failed to compile after the
conversion are listed.
4. Navigate to System Management > Business Process Management > Setup > Method Search.
5. Use the Method Directives program to search for any Outdated Directives.
6. Open an outdated directive.
7. Click on the Actions menu and select Validate Method.
8. If a directive is outdated, the Pre-Processing, Base Processing and/or Post Processing sheets display the
Outdated icon on each directive's Detail sheet. Research how to update each outdated directive to make it
compatible with Epicor 9.05. This may involve updating your custom 4GL code to reflect the new schema.
9. Repeat these steps for all the outdated directives that you find.
12.8 Test Custom Code Programs
Use these steps to test any custom code programs that were created and updated for you by the Epicor Custom
Solutions Group.
1. Test your custom code programs.
2. Contact the Epicor Custom Solutions Group if you need other custom code upgraded. Note that the Epicor
Custom Solutions Group requires time to review, estimate, schedule, and complete the custom solution for
you.
12.9 Test System and Repeat Installation
Based on your installation process, you are at one of the following points:
• If you completed the Epicor 9.05 installation in a test environment, you are now ready to test the installed
Epicor 9.05 application in that environment. After your testing is complete, you must repeat the entire
installation in your production environment.
• If you completed the Epicor 9.05 installation in your production environment, you are now ready to use the
installed Epicor 9.05 application in that environment.
Progress Version 49
Chapter 13: Restore Demonstration Database
Use the following instructions to restore the Epicor 9.05 Demonstration Database, if desired. The Epicor 9.05
Demonstration Database is released with every Service Pack and is used with the Embedded Education Courses.
13.1 Download Demonstration Database File
Use the following instructions to download the appropriate Demonstration Database file based on your database
platform. Each *.zip file includes a copy of the Demonstration Database that can be restored to replace the
existing Demonstration Database.
You can click this link: https://epicweb.epicor.com/Support/epicor9/Downloads
2. Navigate to Epicor 9 > Version 9.05.600 > Demonstration Database.
3. Download the latest Epicor 9.05 Demonstration Database related to this installation. For example, download
the necessary files, based on your environment:
• Progress (32): Epicor9_Database_90560xx_Vx_Win32Progress.zip
• Progress (64): Epicor9_Database_90560xx_Vx_Win64Progress.zip
13.2 Verify Prerequisites
Use the following instructions to verify the prerequisite steps have been completed.
1. All Appservers and OpenEdge Databases are stopped.
2. Epicor 9.05 Service Pack or Patch has been installed, if available.
3. Epicor 9.05 Post-Installation steps have been completed.
13.3 Restore the Demonstration Database - Progress
Use the following instructions to restore the Demonstration Database using the Progress ProRestore command.
These instructions assume the Epicor 9.05 Demonstration Database is installed in: C:\Program Files\Epicor
Software\Epicor905\db\Training.
1. Go to the location where you downloaded the zipped file.
2. Open the .zip file. For example, extract the Epicor9_Database_90560x_Vx_WinxxProgress.ed file directly
into the C:\Program Files\Epicor Software\Epicor905\db\Training folder.
3. Navigate to Start > Program > OpenEdge 10.2A > ProEnv. A DOS window opens.
4. At the proenv> prompt, type: Prompt and press Enter.
5. Type: cd\ and press Enter.
50 Progress Version
6. At the c:\> prompt, type: cd Program Files\Epicor Software\Epicor905\db\Training and press Enter.
7. At the C:\Program Files\Epicor Software\Epicor905\db\Training> prompt, run the Prorest command. For
example, type: prorest mfgsys Epicor9_Database_90560x_Vx_WinxxProgress.ed and press Enter.
8. At the overwrite message, type Y and press Enter.
9. When the restore is completed, you are returned to the C:\Programs Files\Epicor
Software\Epicor905\db\Training> prompt. Type exit to close the DOS window.
13.4 Import Product Licenses and Enable Modules
Use the following instructions to import the product licenses and enable the modules.
1. Open the Epicor Admin Console. To do this, navigate to Start > Programs > Epicor Software > Epicor
Administrative Tools > Epicor Administration Console.
2. Login with a valid User ID and Password. Note that the user must have Security Manager rights. For example,
login as manager / manager or epicor / epicor.
3. Connect to the location of your training environment, such as EpicorTrain905.
4. Specify the imported license file for each company. To do this:
a. Right-click on Company, such as Epic01, and select Properties.
b. Browse and select the license serial number to the imported license file. Click OK. The file is imported.
c. Repeat for each of the other companies, such as Epic02 and Epic03.
5. Enable the modules attached to the imported licenses. To do this:
a. From the list, select Licensing.
b. Right-click on the license serial number and select Properties.
c. Click the Modules tab.
d. Select the individual modules to activate, or click Enable all Licensed to select all the modules. The
Enabled check box should be selected for the modules you want to activate.
e. Click OK.
6. When finished, exit the Epicor Administration Console.
13.5 Start Database and Main Appserver
Use the following instructions to start the database and main Appserver.
1. Use the Progress Explorer Tool or OpenEdge Explorer Tool to start the following functions in order:
• Start the Database: EpicorTrain905
• Start the Appserver: EpicorTrain905
Progress Version 51
2. Minimize the Progress Explorer Tool or OpenEdge Explorer Tool. Do not start the other Appservers yet.
13.6 Run Manual Conversion
Use the following instructions to run the required manual conversion to reset the sequence table. Your main
appserver must be stopped prior to running the conversions, and then restarted after the conversion has finished.
1. If your main appserver is started, you must stop it prior to running the conversions. For example, use the
Progress Explorer Tool to stop the EpicorTrain905 appserver.
2. Open the Epicor Admin Tools program. To do this, navigate to Start > Programs > Epicor Software >
Epicor 9.05 > Epicor Admin Tools.
3. Login with a valid User ID and Password. Note that the user must have Security Manager rights. For example,
login as manager / manager.
4. Select Run Database Conversion.
5. Scroll down the list of programs to number 5460 called Re-set DB Sequences. Highlight the program to
select it.
6. From the Conversion menu, select Run Conversion Program. Click Yes to confirm.
7. After the conversion finishes, exit Epicor Admin Tools.
8. Start your main appserver. For example, use the Progress Explorer Tool to start the EpicorTrain905 appserver.
13.7 Set Up System Agent for Printing (Demo Database)
Use the following instructions to set up your system agent. The paths for the System Agent, which control report
printing, must be reset after a database restore.
These instructions assume your database is set to be the Mfgsys database directly located in this folder: C:\Programs
Files\Epicor Software\Epicor905\db\Training.
1. Review the paths you specified during the server software installation for the following locations:
• Destination Location
• Print Folder Destination Location
• Server Share Location
3. Navigate to System Management > Utilities > System Agent.
4. Click Agent ID to search for the system agent identifier.
5. The identifiers are listed. Select SystemTaskAgent. Click OK.
6. In the Task AppServer section, change the AppServer URL to AppServerDC://localhost:9413.
7. In the System AppServer section, change the AppServer URL to AppServerDC://localhost:9411.
52 Progress Version
8. The Username defaults to print. Enter the Password as print.
9. In the SystemAppServer section, enter your directory paths. For example:
Directory Description Examples

Server File specifies the local path on the server to c:\Program Files\Epicor
the print directory Software\EpicorData/usr/epicor/epicordata
Client File specifies the unc path to the print \\<servername>\EpicorData
directory
Client Program specifies the unc path to the server \\<servername>\Epicor905\Server
directory
10. Save the System Agent changes. Exit System Agent Maintenance.
11. Close the Epicor 9.05 application.
13.8 Restart Remaining Appservers
Use the following instructions to start the remaining Appservers.
1. Open the Progress Explorer Tool or OpenEdge Explorer Tool. Start the following Appservers in order:
• EpicorTrain905TaskAgent
• EpicorTrain905ProcessServer
2. Exit the Progress Explorer Tool or OpenEdge Explorer Tool.
13.9 Test Demonstration Database Update
Use the following instructions to verify that the Demonstration Database was properly updated.
2. Log on using your Username and Password.
3. From the Help menu, select About Epicor 9.
4. Verify that the version has changed to the correct version you installed.
Progress Version 53
Chapter 14: Configure Windows Admin Workstation

(Optional)
Use these steps to configure a Windows Admin Workstation, if one is needed. These steps can be run on a client or
server machine, but they cannot be run on a server that has a 64-bit version of OpenEdge installed. The 32-bit and
64-bit OpenEdge Software cannot be located on the same machine.
Note For a Windows installation, this is an optional step needed only if you want to configure a workstation as
a super-client.
14.1 Install ODBC Driver (Native Client 10)
If you use SQL, use these steps to download and install the 32-bit Native Client 10 ODBC driver.
1. Go to the Microsoft Download website. You can download the 32-bit SQL Native Client 10 from the Microsoft
Download Center. The 32-bit SQL Native Client is in a Feature Pack for Microsoft SQL Server 2008. The link
is: http://www.microsoft.com/downloads/details.aspx?FamilyId=C6C3E9EF-BA29-4A43-8D69-A2BED18FE7
3C&displaylang=en
2. In the Feature Pack for Microsoft SQL Server 2008, scroll to the download link for Microsoft 32-bit SQL
Server Native Client.
3. Download the 32-bit SQL Native Client 10.
4. Install the 32-bit SQL Native Client 10. Verify that it is installed correctly.
14.2 Install Progress OpenEdge
1. Verify that your machine does not have a 64-bit version of OpenEdge installed.
2. Install the 32-bit version of Progress OpenEdge 10.2.A. See the Install Progress OpenEdge 10.2A section
of this document for instructions.
3. Apply the 32-bit version of Progress OpenEdge 10.2.A Service Pack. See the Install Progress OpenEdge
10.2A Service Pack section of this document for instructions.
4. Apply the 32-bit version of Progress OpenEdge 10.2.A Hot Fix. See the Install Progress OpenEdge 10.2A
Hot Fix section of this document for instructions.
14.3 Install Epicor 9.05 Client
1. Install the Epicor 9.05 Client. See the Install the Epicor 9.05 Client section of this document for instructions.
You must complete all the steps in that section.
Note During the installation, if this Windows Admin Workstation machine is where you plan to run
the Epicor Admin Tools and Epicor Schema Changes, be sure to select the following check boxes to
create the shortcuts: Epicor Admin Console and Epicor Schema Change.
54 Progress Version
Note During the installation, if this Windows Admin Workstation machine will also be used as a
normal Epicor 9.05 client machine, you have the option of also selecting the following check boxes
to create additional shortcuts: Epicor 9.05 and Epicor 9.05 MES.
Progress Version 55
Appendices Epicor 9.05 Installation Guide
Part V: Appendices
Use the following information to help complete your Epicor 9.05 environment set up. Complete the sections
appropriate for the components you intend to use.
For Service Pack and Patch upgrades, review the Release Notes for more information on which sections need to
be completed after installing the upgrade.
Appendix A: Configure 64-Bit Environment (Windows 2008)
If you have installed a Windows 2008 (64-bit version) environment, use these steps to enable the 32-bit version of
ASP.NET 2.0 in a Windows 2008 64-bit environment. This version must be enabled in order to install and deploy web
based products, such as Epicor Web Access and the Embedded Education courses.
Note When using a 64-bit server, you may encounter login issues when using Internet Explorer 64-bit. Epicor
Web Access allows users to enter login credentials, but the application may not start. To resolve this security
issue, use Internet Explorer to add the Epicor Web Access site to the server’s trusted site list.
A.1 Enable ASP .NET 2.0 Application (64-bit only)
Use these steps to enable the 32-bit version of ASP.NET 2.0 in a Windows 2008 64-bit environment.
1. Go to Internet Information Services (IIS) Manager.
2. From the Application Pools node, select DefaultAppPool.
3. From the Action menu, select Advanced Settings.
4. Select the Enable 32-Bit Application check box.
5. Restart the Application Pool.
6. Expand the Default Web Site node.
7. In the middle column, click Handler Mappings.
8. If these extensions are not mapped, you must manually add each one separately. To add the .htm extension,
do the following:
a. In the right column, click Add Script Map
b. Request path: *.htm
c. Executable: C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll
d. Name: htm.
e. Click OK.
9. To add the .html extension, do the following:
56 Progress Version
Epicor 9.05 Installation Guide Appendices
a. In the right column, click Add Script Map
b. Request path: *.html
c. Executable: C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll
d. Name: html.
e. Click OK.
10. Within IIS, right-click on Default Website and select Manage Web Site > Restart.
Progress Version 57
Appendix B: Install Embedded Education Courses
Use these steps to install and license the embedded Education courses. Using the embedded courses requires a Windows
Server operating system and Microsoft Internet Information Services (IIS 6 or IIS 7).
Note Embedded Education Courses must be installed in your training environment, not in your live production
environment.
B.1 Install Embedded Education Courses Process
Use these steps to install the embedded education courses using the Epicor Education Course Installer.
1. Go to the directory where your Epicor application is installed. For example, go to \Epicor Software\Epicor905.
4. On the Epicor Utilities Setup dialog, click Install Epicor Education Courses to open the Epicor Education
Course Installer.
Note You can also open the Epicor Education Course Installer by navigating to the Epicor Education
folder and running the EduCourseInstaller.exe file.
5. Verify that the Epicor 9.05 Education Course Installer program opens. The user interface looks different
based on your operating system.
6. Select the Web Site where you want to install the Education courses. It is recommended that you select
the DefaultWebSite.
7. Select the App Pool to use for the Education courses. It is recommended that you select the DefaultAppPool
and then verify that it is set to 32-bit and Integrated. To verify the settings:
a. Open the Internet Information Services Manager (IIS 7).
b. In the Connections tree view, select Application Pools.
c. In the Application Pools list, select the application pool used by the Epicor Education virtual directory.
For example, select DefaultAppPool.
d. In the Action panel, click on Advanced Settings.
e. Verify that Integrated is selected as the Managed Pipeline Mode.
f. Verify that Enable 32-Bit Applications is set to True, if your system is a 64-bit server.
g. Click OK to close the dialog and save your changes.
h. Close the IIS Management panel.
8. Enter the Alias you want to use to gain access to the courses. The alias is used as part of the course server
URL. Do not use spaces. The default is EpicorEducation.
58 Progress Version
Note It is recommended that you record the Alias that you enter. In the next section, you are required
to configure the client by editing the .mfgsys configuration file. To edit this file, you will need to enter
the Alias and the course server URL.
9. Enter the Directory. The directory can be any folder on the server. For example, if you have a folder on your
server where you host Web content, such as C:\Inetpub\wwwroot, you can install the courses to that folder.
If the directory does not exist, the installer creates it. You can install a new batch of courses to an existing
directory by using the browse button.
10. For the Server Name enter the name of the server where your Epicor application is installed.
11. Enter the Port used by the AppServer. To find your port number:
a. Go to the Config folder on the server where your Epicor application is installed. For example, go to the
Epicor905\client\config folder.
b. Open your train.mfgsys file and look at the AppServer node. The port number should be listed. For
example, the default port for the training database is 9411.
Note The Server Name and Port must point to a training database and not a live database within
your production environment.
12. Enter a valid Epicor application User ID and Password. The course web site uses this User ID and Password
to login to the Training AppServer to verify licensing information. The default User ID and Password for the
Epicor Education database is manager / manager.
13. Click Create.

Note If any entries were not valid, a warning icon appears next to the invalid field. Enter a valid entry
in the field and click Create again.
14. After a message displays that the site has been created, close the Epicor Education Course Installer.
B.2 Configure Embedded Education Courses Client
Use these steps to configure the embedded education course client.
1. On your client workstation, navigate to the client\config folder.
2. Open the train.mfgsys file in a text editor, such as Notepad.
3. In the <helpSettings> node, edit the following lines:
a. Edit the <courseServer uri="" /> line to specify the location where the education courses are installed.
For example, if the courses are installed on a server named Company1 and the alias is set to
EpicorEducation, the line would be: <courseServer uri="http://Company1/EpicorEducation/" />.
Note Be sure to use the Alias that you entered and recorded in a previous step when you ran the
EduCourseInstaller program.
Progress Version 59
b. Edit the <helpServer uri="" /> line to specify the location where the help files are installed. For example,
if the help files are installed on a server named Company1, the line would be: <helpServer
uri="//Company1/Help/" />.
Note If the help files are installed on the deployment server, it is not necessary to edit the
<helpServer uri="" /> line.
For example, the <helpSettings> node with the edited lines would look similar to the following:
<helpSettings>
 <helpServer uri="http://Company1/Help/
"
/> <courseServer uri="http://Company1/EpicorEducation/" />
<E9EducationKeysServer uri="" />
...
</helpSettings>
B.3 License Embedded Education Courses
Use these steps to license the embedded education courses. License keys are specified by Education Course
module, not Epicor 9.05 modules.
Note You must retrieve your license information for your embedded courses when you access the embedded
education courses for the first time, and each time a Service Pack is applied.
2. On the Standard toolbar, click the Education Course button (student with a graduation cap). The Education
Course program opens.
3. From the Actions menu, select one of the following options:
a. Load License from file. Choose this option to enter the name of the license file.
b. Enter License Keys. Choose this option to manually enter the key if you were sent a file that contains
your license keys. At the prompt, browse to the file and open it. Manually copy the license key details
from the file into your database. This step only has to be completed once and it is saved in the database.
c. Retrieve the key from EPICweb. Choose this option to download and install license key information
from EPICweb. Log on to EPICweb by entering your User Id and Password. Click OK. Your EPICweb login
information is verified and then your embedded education course license keys are automatically installed
on your system.
Note When a Service Pack is applied, the Education database is updated and the license key
information must be re-imported. If courses are delivered with the service pack, reinstall them in
the same location on the server.
4. Click OK to complete the embedded education course setup.
5. To view the Embedded Education Courses, click the Refresh button from the toolbar in the application. If
the refreshed Embedded Education Courses do not display, you should close and reopen the application.
60 Progress Version
Appendix C: Install Epicor Administration Console
Use these steps to install Epicor Administration Console on your server. The upgrade process includes uninstalling and
then reinstalling your Epicor Administration Console. These steps must be completed at each Service Pack or Patch
release.
C.1 Uninstall Epicor Administration Console
If you have a previous version of Epicor Administration Console installed on your server, use these steps to uninstall
Epicor Administration Console.
1. Uninstall the Epicor Administration Console. To do this, select Start > Control Panel > Add or Remove
Programs.
2. Select Epicor Administration Console and click Remove.
C.2 Install Epicor Administration Console
Use these steps to install the Epicor Administration Console on your server and/or on your Windows Admin
Workstation.
1. Go to the directory where your Epicor application is installed.

Example Go to C:\Program Files\Epicor Software\Epicor905.
4. On the Epicor Utilities Setup dialog, click the Install Administration Console button to start the installation.
The Epicor Administration Console is now installed.
Progress Version 61
Appendix D: Install and Deploy Epicor Web Access
Use these steps to install and deploy Epicor Web Access using a Windows 2008 based Internet Information Server (IIS).
The Epicor Web Access forms and components are an optional installation and are required only if Browser-based
access to your Epicor 9.05 environment is desired.
Note While it is possible to deploy the Epicor Web Access forms on your Windows based Epicor 9.05 Server, it
is not recommended. For optimal performance and ease of maintenance, a separate Internet Information Server
is recommended.
D.1 Install Crystal Reports Runtime and Embedded Server
If you use report generation from Epicor Web Access, you must install Crystal Reports 2008 Runtime and Crystal
Reports 2008 Embedded Server.
D.1.1 Uninstall Previous Versions of Crystal Reports Runtime and Embedded Server
Use the following steps to uninstall any previous version of Crystal Reports Runtime and Crystal Reports Embedded
Server. Do not skip this step.
1. Navigate to Start > Control Panel > Add or Remove Programs.
2. Select Crystal Reports .NET Runtime and click Remove.
3. Select Crystal Reports .NET Embedded Server and click Remove.
4. Verify the uninstallations were completed successfully.
D.1.2 Install Crystal Reports 2008 Runtime (Web Access)
Use the following steps to install the latest version of Crystal 2008 Runtime. This component must be installed
on the web server that is hosting Epicor Web Access. Crystal Reports 2008 .Net Runtime can be installed on
Windows Server 2008.
3. Download the latest Crystal Reports Runtime file from EPICweb to your workstation. For example:
Crystal_2008_03_Runtime.zip.
5. Double-click to run the EXE file. For example, run the CRRuntime_12_3_mlb.exe file.
6. The Welcome window appears for Crystal Reports 2008 Runtime. Click Next.
62 Progress Version
7. Review the license agreement, and select the I accept the License Agreement check box. Click Next.
8. Specify the folder for the installation of Crystal Reports 2008 .NET Runtime, and select Everyone as the
user of the computer. Click Next.
9. When prompted for the Product ID, do the following:
a. Using a text editor, open the License Key.txt file that was extracted in a previous step.
b. Copy the text and paste it into the Product ID field.
c. Click Next.
10. A confirmation window appears. Click Next to confirm.
11. The installation proceeds. When it is finished, click Finish.
D.1.3 Install Crystal Reports Embedded Server
Use these steps to install the latest version of the Crystal Reports 2008 Embedded Server on your server.
This component can be installed either on the same server as the Epicor Web Access forms, if Windows 2008 is
being used for both Epicor Web Access and Crystal Reports, or on another server within the trusted domain.
Note As of the Epicor 9.05.606 and later releases, the Crystal 2008 Embedded Server license is included
in the installer. The license no longer needs to be entered manually during the installation.
3. Download the latest Crystal Reports Embedded Server file from EPICweb to your workstation. For example:
Crystal Reports 2008 Embedded Server SP3.zip.
5. Move the extracted files to the report server where the file are to be installed.
6. Navigate to the extracted file folder. Double-click the Setup.exe file.
7. The Crystal wizard Welcome window appears. Select the installation language in the wizard, and review
the Installation Guide and Release Notes located in the extracted files folder.
8. On the Crystal Reports 2008 Embedded Server Edition Setup form, click Next.
9. Review the license statement and select to accept it. Click Next.
10. Specify the installation folder. Click Next.
11. For the Install Type, select the New checkbox.
12. Click Next to confirm to start the installation. A meter displays the progress.
Progress Version 63
13. When completed, click Close.
14. You need to set the Report Directory of the Cental Configuration Manager. To do this, do the following:
a. Navigate to Start > BusinessObject XI 3.1 > Crystal Report Embedded Server 2008 > Central
Configuration Manager.
b. Stop the Report Application Server 12.
c. Right-click on Report Application Server 12 and select Properties.
d. In the Report Application Server 12 Properties window, select Parameter.
e. In Option Type, select Server.
f. For the Report Directory enter the value: C:\.
g. Restart the Report Application Server 12.
The installation of the Crystal Reports 2008 Embedded Server is complete.
D.2 Configure Forms and Components
The Epicor Web Access forms and components are delivered as part of the Epicor application server installation.
The files are located in the /Epicor Web Access folder on your server. Use the following steps to configure those
forms and components.
1. Go to the /Epicor Web Access folder on your server. It is located at the same folder level as
Administration/Client/Server/Help.
2. Move the entire folder to the Windows 2008 Internet Information Server (IIS) that will host your Epicor Web
Access web site.
3. Go to the /Epicor Web Access Utilities 9.0 folder.
4. Double-click the Epicor Web Access Utilities.msi file to run the pre-installation configuration process.
D.3 Install Epicor Web Access
Use the following steps to complete the installation of your Epicor Web Access Forms.
1. Navigate to Start > Programs > Epicor Software > Epicor Administrative Tools > Epicor Web Access
Utilities > Epicor Web Access Installer.
Note To run the Epicor Web Access installer on Server 2008 or Windows 7, you must launch the
installer as an Administrator. To do this, right-click on the Epicor Web Access Installer icon, and
select Run as Administrator from the menu.
2. The Epicor Web Access Installer windows appears. Click Next.
3. The Basic Installer Settings dialog opens. It looks similar to the following:
64 Progress Version
Enter the following information:
a. Web Forms Package: Enter EpicorWebAccessForms.zip which stores the files that related to web
forms such aspx, js, and css.
b. Web Services Package: Enter EpicorWebAccessServices.zip which stores the files that are related
web services such as asmx, and dll.
c. Click Next.
4. The Site Settings dialog opens. It looks similar to the following:
a. Epicor Web Access Site: Enter your site name.
b. Install Path: Enter the directory path where the EWA files will be located. The final installation directory
uses both the Install Path and the Epicor Web Access Site values. For example, if you enter "EWATest"
as your Epicor Web Access Site, and "C:\temp" as your Install Path, then the final installation path would
be "C:\temp\EWATest". The Install Path is available for entry for both IIS 6 and IIS7 environments.
Progress Version 65
c. Web Site: Select the IIS web site where the application will get created. For example, in IIS, the web site
Default Web Site is always available. If you want to select a different web site, you can create one using
the IIS Admin Console. The Web Site is available only when installing in an IIS 7 environment.
d. App Pool: Select the Application Pool that will be used by the Epicor Web Access application. The
drop-down list displays only the application pools that are set to use Integrated Pipeline mode. If the list
is empty, click the New button to create a new application pool that uses an Integrated pipeline. The
App Pool is available only when installing in an IIS 7 environment.
e. Progress Server: Enter the name of your Epicor Progress Application Server (AppServer).
f. AppServer Port: The AppServer port number defaults to 3090. Change this number to identify your
AppServer port. For example, the Appserver port for the live database is 9001.
g. Enable Single Sign On: Select this check box to use Windows authentication for a single sign on. If it
is not successful, it prompts for an EpicorWeb login.
h. Click Next.
5. The Reporting Settings dialog opens. It looks similar to the following:
a. Enable Reporting: Select this check box if you have Crystal 2008 Embedded Server installed on the
same server or on the network. Selection enables the Report Setting section. Note that this check box is
only enabled when a Crystal 2008 Runtime is installed on the server.
b. Report Appserver. The Report Appserver defaults to the name of the webserver. If the Crystal 2008
Embedded Server is installed on a different server, change this name to identify the name of the server
where it is installed.
c. Report Monitor Polling for Server (ms): Select the number of milliseconds for report polling from the
web server.
d. High Priority Interval For Client (ms): Select the number of milliseconds the process waits immediately
after the report is submitted. When the time is greater than High Priority Duration for Client time, the
process shifts it to Low Priority Interval for Client.
e. Low Priority Interval For Client (ms): Select the number of milliseconds the process waits between
process after the time specified for the High Priority Duration for Client is done.
66 Progress Version
f. Auto Purge Older Reports For Server (days): Select the number of days the report is available before
it is automatically delete from the server.
g. High Priority Duration for Client (ms): Select the number of milliseconds for the duration time that
the reports check for new reports. This setting is similar to the System Monitor in the Win Client. When
the duration times out, it sets it to Low Priority Interval For Client.
h. NLB Report Repository: Specify the NLB (Network Load Balancing) report repository location. This
location is a shared repository that can be accessed by other EWA installations. This is an optional field.
i. Click Next.
6. The Summary dialog opens. Review the information. Click Finish. The Epicor Web Access installation
proceeds.
7. If you entered an Epicor Web Access Site name that already exists, the Install Options dialog opens. Review
the options and click the button that specifies your desired installation option. Options include:
• Install New Site. Select this button to install a new Epicor Web Access site using the name you specified.
The installation will remove all the web forms and assemblies that were previously installed in the site,
and it will install new web forms and new assemblies.
• Upgrade Site. Select this button to keep the existing Epicor Web Access site in place. The installation
will overwrite all Epicor web forms and replace any changed assemblies. Custom forms will be kept in
place.
• Cancel. Select this button to cancel the installation.
8. To verify that the installation was successful, in Windows Explorer enter the Epicor Web Access URL.
For example, enter http://<your server>/<your site name>/default.aspx where <your server> is the name
you specified as your Progress server and <your site name> is the name you specified as your Epicor Web
Access Site.
9. If your Epicor Web Access installed successfully, a window similar to the following should appear:
10. Enter a valid User ID and Password that you use to log into your Epicor application. This sign-in consumes
a user license.
Note If you want to use a Time and Expense (TE) or Customer Relationship Management (CRM)
license, go to the login page using the following URLs respectively: http://<your server>/<your site
name>/default.aspx?LicenseType=TE or http://<your server>/<your site
name>/default.aspx?LicenseType=CRM. During deployment of EWA, direct users of TE and CRM
license types to set up browser Favorites using the appropriate style of URL.
Progress Version 67
11. Click Login.
D.4 Deploy Epicor Web Access
Use these steps to deploy Epicor Web Access. The delivered web forms are generated at the same version as the
Epicor application software deployed in the release. The Web Menu includes the forms that are available for
Epicor Web Access.
1. Epicor Web Access includes the majority of the Epicor application forms, with a few exceptions of the
drag-and-drop scheduling forms and most of the system setup forms. Review the form exceptions, which
include:
• Job Scheduling Board
• Multi Resource Scheduling Board
• Resource Scheduling Board
• Business Activity Query Designer
• BPM Method and Data Directive Maintenance
• Financial Report Designer
• Menu and Security Maintenance
• Mobile, Customer and Supplier Connect Maintenance
• Translation Maintenance
• System Agent
• W2 Processing
2. Determine if you need further control over web forms that you need to exclude from Epicor Web Access.
To exclude a form, use Menu Maintenance (using the Epicor Smart Client) and on the Security sheet,
select the Exclude Epicor Web Access check box associated with each menu option.
Note Epicor Web form supports group access security so this exclusion is only required when a form
should be available to users from the Epicor Smart client but not the Epicor Web Client.
3. Determine if you need to customize any forms or create any user dashboards since these must be specially
generated for Epicor Web Access.
Note A prerequisite for generation is that any customization script must be supported in C# rather
than VB.Net code. This is due to the fact that the process converts customization code from C# into
Java Script for Browser deployment. This process is not possible from VB.Net code. Although VB.Net
is supported for backward compatibility with the Epicor 9.05 application, it is not recommended that
new customizations are created using VB.Net with the Epicor 9.05 application since they do not
generate for Web Access without conversion to C#.
4. Determine how to process the customizations and dashboards containing customization code in VB.Net
that were created prior to upgrading to the Epicor 9.05 application. You must either recreate those
customizations using C#, or manually convert code either by hand or using a commercially available VB.Net
to C# conversion routine. Instructions are available in a the document entitled Guidelines for Conversion
of VB.Net to C# Customization Code in Epicor 9.05. Contact Epicor Support for this documentation.
5. If you want certain users to use a Time and Expense (TE) or Customer Relationship Management (CRM)
license, direct them to use the following URL style to get to the login page: http://<your server>/<your site
68 Progress Version
name>/default.aspx?LicenseType=TE or http://<your server>/<your site name>/default.aspx?LicenseType=CRM.

Direct users of TE and CRM license types to set up browser Favorites using the appropriate URL.
D.5 Configure Epicor Web Access
Use these steps to configure Epicor Web Access within your Epicor application.
1. Navigate to System Management > Company Maintenance and open the Company program.
2. Click the System > Epicor Everywhere tab.
3. Enter your Epicor Everywhere URL. For example, enter http://<your server>/<your site name>.
4. Enter your Metadata Output Path. This is from the perspective of a client PC that might be generating
Epicor Web Access forms.
For example, enter: \\<your server>\<shared site name> where <your server> is the name of your web server
and <shared site name> is a share on that server to your Web Access site name. Example:
c:\inetpub\wwwroot\<your site name>.
5. Click Save on the Standard toolbar.
D.6 Assign Resource Folder Properties and Sharing
Use the following steps to assign required properties and sharing to the Resource folder.
1. Navigate to the Epicor Web Access virtual directory. For example, if your Epicor Web Access was installed
to IIS, the default directory would be: :\inetpub\wwwroot\EWA\Resources
2. Right-click on the Resources folder and select Properties.
3. Click the Security tab. Select the IIS_WPG group from the Group or user names list.
4. Click the Edit button.
5. Re-select the IIS_WPG group.
6. In the Permissions for IIS_WPG list, select the Modify and Write check boxes in the Allow column.
Note The IIS_WPG group now has Allow selected for Modify, Read & Execute, List Folder Contents,
Read, and Write.
7. Click OK until you exit.
8. Right-click on the Resources folder and select Sharing and Security.
9. Select the Share this folder check box. Click OK.
Progress Version 69
D.7 Install Full Adobe Reader on Epicor Web Access Client
Use the following steps to install Adobe Reader on your Epicor Web Access client. Installing the full Adobe Reader
installs the appropriate browser add-on that is required to render and view report .pdf files (from IIS).
1. Go to the Adobe Reader website. The link is: http://get.adobe.com/reader
2. Download the latest version of Adobe Reader.
D.8 Update Epicor Lightweight Client Installer File
Use the following steps to update the lightweight Epicor Web Access client installer .msi file. A lightweight
client allows a local smart client to work in conjunction with the EWA browser client to provide functionality not
available from EWA forms.
1. Verify that your Epicor Web Access site has been created.
2. Open the Epicor Web Access Utilities. To do this, navigate to Start > Programs > Epicor Software > Epicor
Administrative Tools > Epicor Web Access Utilities.
3. Select the Epicor Lightweight Client Install Updater program.
4. Enter or browse for the Installer File Name. The file is called SmartClientInstall.msi file and it is located
in the following folder: C:\inetpub\wwwroot\<EWA site>\SmartClientInstaller.
5. Enter the Deployment server URL. To find the value, do the following:
a. On the smart client, go to the \config directory.
b. Open the configuration file for that smart client. For example, open the default.mfgsys file.
c. Locate the line: <Deployment server uri = [value]>.
d. Copy the value and paste it into the Deployment server URL field.
6. Enter your Configuration file name. For example, enter the configuration file used by your smart client,
such as default.mfgsys.
7. Click OK.
8. When the installation is finished, click OK.
9. To test that the Epicor Lightweight Client Installer file was updated, do the following:
a. Open Epicor Web Access.
b. Click on the Download Smart Client Installer icon that is located in the toolbar.
c. The Epicor Lightweight Client Installer is downloaded to your machine.
70 Progress Version
D.9 Configure EWA Reporting URL Display Features
If you use Windows Server 2008 (32 or 64) for your web server you must use these steps to configure the Epicor
Web Access report display feature. You need to configure both PDF and XLS report formats.
D.9.1 Configure: Windows 2008 64-bit Web Server - PDF
If you use Windows Server 2008 64-bit web services, use the following steps to set up a PDF configuration.
1. After creating an Epicor Web Access site, open Internet Information Server.
2. Expand the Sites and Default Web Sites nodes.
3. Locate the Epicor Web Site and single-click to enable the Feature view pane.
4. Under IIS section, double-click to open Handler Mappings.
5. In the Actions section, select Add Script Map.
a. For the Request path, enter *.pdf.
b. For the Executable, browse and select the file:

C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll
c. For the Name, enter AboMapperCustom PDF 32.
d. Click Request Restrictions.
e. Go to the Verbs tab. Select the One of the following verbs checkbox.
f. Manually enter GET,HEAD,POST,DEBUG.
g. Click OK.
h. Review the Edit Script Map setup form. The values should be the same as you previously entered. Click
OK.
i. A message appears asking if you want to allow the ISAPI extension. Click Yes.
D.9.2 Configure: Windows 2008 32- or 64-bit Web Server - XLS
If you use Windows Server 2008 32-bit or 64-bit web services, use the following steps to set up a XLS configuration.
1. Under IIS section, double-click to open Handler Mappings.
2. In the Actions section, select Add Script Map.
a. For the Request path, enter *.xls.
b. For the Executable, browse and select the file:

C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll
c. For the Name, enter xlsMappingCustom XLS 32.
d. Click Request Restrictions.
Progress Version 71
e. Go to the Verbs tab. Select the One of the following verbs checkbox.
f. Manually enter GET,HEAD,POST,DEBUG.
g. Click OK.
h. Review the Edit Script Map setup form. The values should be the same as you previously entered. Click
OK.
i. A message appears asking if you want to allow the ISAPI extension. Click Yes.
D.10 Generate Web Forms for Customized Epicor 9.05 Forms
Use these steps to generate Web Forms for customized Epicor 9.05 application forms.
1. Click on the User Security tab. Verify that the Customization Privileges check box is selected.
2. From the Options menu, select the Developer Mode check box.
3. Run the Customized form under the customization that you wish to Generate.
4. From the Tools menu of the customized form, select Generate Web Form.
5. Click OK. The customized form is generated to the Epicor Web Access site.
D.11 Generate Web Forms for User Dashboards
Use these steps to generate Web Forms for user Dashboards:
1. Click on the User Security tab. Verify that the Customization Privileges check box is selected.
2. Open the Dashboard that you wish to generate a web form.
3. From the Tools menu, select Developer.
4. From the Tools menu, select Application Builder > Deploy UI Application. This deploys the dashboard
as a UI form.
5. Select Application Builder > Generate Web Form. This deploys the UI Dashboard to the Epicor Web
Access site
D.12 Review Supported Browsers and Configuration
Use these steps to review the browsers and browser configurations that are supported with Epicor Web Access.
1. Verify that one of the following browser versions is installed on your system:
• Internet Explorer - Internet Explorer 7
• Mozilla Firefox - FireFox 3.0.4
• Apple Safari - Safari 3.2
72 Progress Version
Note Microsoft Silverlight cannot be used in browsers running in 64-bit mode.
2. If you use Firefox, complete the following steps to change your security settings to support Java popups
such as the search dialog box:
a. In the Navigation bar, type about:config.
b. In the Filter text box, type signed.applets.codebase_principal_support.
c. Double-click on the entry. The value changes from false to true.
d. Restart Firefox.
3. If you use Firefox, complete the following steps to access some Microsoft plug-in files to support Window
Authentication:
a. In Firefox, browse to the following: http://www.microsoft.com/genuine/diag/default.aspx?displayLang=en
b. Click the Start Diagnostics button.
c. Follow the online instructions to add the plug-in files.
D.13 Set Up Compression for Performance Tuning
If you use Windows Server 2008, use the following steps to set up compression. With IIS 7, compression is enabled
at the site level. Mime types are enabled globally and are applied to the applicationHost.config.
D.13.1 Compression for Windows 2008 or Vista (IIS7)
If you use Windows Server 2008, use the following steps to set up compression. With IIS 7, compression is enabled
at the site level. Mime types are enabled globally and are applied to the applicationHost.config.
1. Create a backup of the metabase. To do this:
a. To create the backup, run this command: %windir%\system32\inetsrv\appcmd.exe add backup

"My Backup Name"
b. To restore the backup, run this command: %windir%\system32\inetsrv\appcmd.exe restore backup

"My Backup Name"
c. To delete the backup, run this command: %windir%\system32\inetsrv\appcmd.exe delete backup

"My Backup Name"
2. Enable Compression in IIS. To do this:
a. In IIS, under Default Web Site, select the web site to be enabled.
b. From the available IIS features, open the Compression feature.
c. Select the Enable dynamic content compression and Enable static content compression check
boxes.
d. Click Apply. Exit from IIS, and save settings.
Progress Version 73
3. The EWA extensions do not need to be modified. However, if you want to apply compression to specific
extensions, you can do the following:
a. Open the file: C:\Windows\System32\Inetsrv\Config\applicationHost.config
b. Locate the httpCompression section.
c. Edit the dynamicTypes and staticTypes sections to control which content gets compressed. IIS6 controls
by file extension, IIS7 controls by mimeType. The "*" character is a wildcard and can be used in any
combination. The easiest setup is to enable all with types */*.
Here are some examples of enabling selective mimetype(s):

dynamicTypes:
<mimetype="text/*" enabled="true">
<mimetype="message/*" enabled="true">
<mimetype="application/x-javascript" enabled="true">
<mimetype="*/*" enabled="false">
staticTypes
<mimetype="text/*" enabled="true">
<mimetype="message/*" enabled="true">
<mimetype="application/x-javascript" enabled="true">
<mimetype="*/*" enabled="false">
D.14 Set EWA Server Timeout
Use these steps to set the session timeout values for the server. The timeout values are entered in minutes.
1. Using a text editor, such as Notepad, open the web.config file located in the root of the EWA web site.
2. Locate the <sessionState> line. For example, the line may look similar to the following: <sessionState
mode="InProc" stateConnectionString="tcpip=127.0.0.1:42424" sqlConnectionString="data
source=127.0.0.1;Trusted_Connection=yes" cookieless="false" timeout="20" />
3. Edit the timeout string portion that is in quotes. For example, change timeout = "20" to timeout = "60"
to increase the timeout value from 20 minutes to 60 minutes.
4. Save and close the file.
74 Progress Version
Appendix E: Install Epicor DB Replication
Use these steps to install Epicor DB Replication.

Note Based on the release, you may have to also install an Epicor DB Replication Hot Fix after installing Epicor
DB Replication.
1. Log on to EPICweb and go to the Customer Portal Page. Navigate to Documentation > Epicor 9.
Note You can use this link: https://epicweb.epicor.com/doc/Pages/Epicor9.aspx
2. Expand the release. For example, expand Release 9.05.
3. Download the Epicor Replication Server Install Guide to your workstation.
4. Use the instructions in the Epicor Replication Server Install Guide to install and configure Epicor DB Replication.
Progress Version 75
Appendix F: Install Epicor SQL Server Reporting (SSRS)
Use these steps to install Epicor SQL Server Reporting Service (SSRS). During the installation, the report portal and
Report Service Monitor Service are created. Epicor SQL Server Reporting Services (SSRS) is a reporting technology that
provides additional functionality not currently available with the current Crystal Reports client runtime. The installation
of SSRS is optional.
F.1 Verify SSRS Prerequisites
Use these steps to verify the requirements before you begin the installation of SSRS.
1. Verify that you are using SQL Server 2008.
2. Verify that your SQL Server 2008 installation has Reporting Services enabled. Reporting Services must be
installed in Native mode. To do this:
a. Navigate to Start > All Programs > Microsoft SQL Server 2008 > Configurator Tools > Reporting
Services Configuration Manager.
b. Connect to the Reporting Services.
c. In Current Report Server information, verify that Report Server Mode = Native.
3. Set SSRS as an allowed reporting style in your Epicor application. To do this:
a. Open the Epicor 9.05 application. Select System Management > Company Maintenance > Company.
b. Select the System sheet. In the Allowed Report Style field, select Crystal and SSRS or SSRS Only.
Save the record.
F.2 Enable IIS 6 Management Compatibility
If you are running IIS 7, use these steps to enable IIS 6 Management Compatibility. The steps are different based
on your operating system.
F.2.1 Using Vista and Windows 7
1. Open the Control Panel. Click Programs or Programs and Features.
2. Select the Turn Windows features on or off option
3. Expand Internet Information Services > Web Management Tools > IIS 6 Management Compatibility.
4. Verify that IIS Metabase and IIS 6 configuration compatibility is selected.
5. Exit the Control Panel.
76 Progress Version
F.2.2 Using Server 2008
1. Run Server Manager.
2. From Roles > Web Services (IIS), right-click and select Add Role Services. Note that this node is only
present when IIS is already installed.
3. Expand Management Tools > IIS 6 Management Compatibility.
4. Verify that IIS 6 Metabase Compatibility is installed.
5. Exit the Server Manager.
F.3 Install Custom Assembly DLL File (Report Server)
Use these steps to install custom assembly DLL file. Installation includes copying the .dll file and editing the .config
file.
1. Go to the Assembly folder on the server where SSRS is installed. For example, go to C:\Program Files\Epicor
Software\Epicor905\SSRS\Epicor SSRS Assembly.
2. Copy the CLSEpicor.dll file to the location where your Microsoft SQL Server Reporting Server files are
installed. For example, copy the file to: C:\Program Files\Microsoft SQL Server\<Instance Name>\Reporting
Services\ReportServer\bin folder.
Note The name of your <Instance Name> folder depends on your installation location or other Epicor
tools that have already been installed.
3. Go to the C:\Program Files\Microsoft SQL Server\<Instance Name>\Reporting Services\ReportServer folder.
4. Locate the rssrvpolicy.config file. Create a backup copy of the file.
5. Open the rssrvpolicy.config file with a text editor. In the config file, locate the following code:
<CodeGroup class="FirstMatchCodeGroup" version="1"
PermissionSetName="Nothing">
<IMembershipCondition class="AllMembershipCondition"
version="1"/>
6. Paste the following code right below the code you located in the previous step:
<CodeGroup
class="UnionCodeGroup"
version="1"
PermissionSetName="FullTrust"
Name="MyCodeGroup"
Description="Code group for my data processing extension">
<IMembershipCondition
class="UrlMembershipCondition"
version="1"
Url="C:\Program Files\Microsoft SQL Server\MSRS10.MSSQLSERVER\Reporting Ser
vices\ReportServer\bin\CLSEpicor.dll"/>
</CodeGroup>
Note You may need to change the URL based on the location where the ReportServer\bin folder
is located on your server.
Progress Version 77
7. In the code, locate the description:

Description="This code group grants default permissions for code in report
expressions and Code element."
8. In the line above this description, change PermissionsSetName = Execution to PermissionSetName =

FullTrust. This enables the expressions in the report to access the configuration file and call the .dll file.
F.4 Install Microsoft Report Viewer 2010 Redistributable Package
Use the following steps to download and install the latest Microsoft Report Viewer 2010 Redistributable Package
from the Microsoft Download Center website.
1. Go to the Microsoft Download Center to download the Microsoft Report Viewer 2010 Redistributable
Package. You can use this link: http://www.microsoft.com/downloads/en/confirmation.aspx?familyId=a941
c6b2-64dd-4d03-9ca7-4017a0d164fd&displayLang=en
2. Download the latest version of the Microsoft Report Viewer 2010 Redistributable Package to your server.
3. Use the instructions provided on the website to guide you through the installation process.
F.5 Configure Epicor SQL Report Monitor
Use these steps to configure the Epicor SQL Report Monitor.
1. Go to the SSRS directory on the server where your Epicor application is installed. Example: C:\Program
Files\Epicor Software\Epicor905\SSRS.
2. Copy the EpiSSRS.msi file to the server where your Microsoft SQL Server 2008 is located.
3. Double-click the EpiSSRS.msi file on the server where your Microsoft SQL Server 2008 is located.
5. On the Select Installation Address dialog, enter the following:
a. Site. Enter the web location site to install Epicor SQL Report Monitor. The default is Default Web Site.
b. Virtual Directory. Enter the virtual directory. For example, EpiSSRSPortal. The virtual directory is created
under inetpub/wwwroot, unless a specific path is specified.
c. Application Pool. From the drop-down list, select your application pool. Note that only integrated .NET
AppPool types are displayed. For IIS 7 and above, if the drop-down is empty, use your IIS Manager to
create an integrated . NET application pool.
d. Click Next. The web location is created.
7. The Configuration Utility opens to begin the SSRS configuration. On the Set up the Epicor SQL Report
Monitor Service User Account dialog, select Local System Account or This Account. If you select This
Account, you must define the user name, domain, and password. For example, create a user name such
as Administrator. Click Next.
78 Progress Version
8. On the Configure the SQL Server Report Portal dialog, enter the following:
a. Epi SSRS site. Enter a site that is a valid URL. For example, http://localhost/EpiSSRSPortal.
b. Epi SSRS path. Enter a path that already exists and contains a web.config file. For example,
C:\inetpub\wwwroot\EpiSSRSPortal\.
c. Click Next.
9. On the Configure the SQL Report Server dialog, enter the following information:
a. SSRS ReportServer site. This site was created when you installed Microsoft SQL Server with Reporting
Services enabled (SSRS). For example, enter a URL such as: http://localhost/reportserver.
b. User name. Enter a user name that has administrative rights.
c. Domain. Enter your domain identifier. For example, localhost.
d. Password. Enter a password and confirmation password for the user.
e. Show Report Parameters. Select this check box if you want the report parameters to display on the
report. Note that you can also modify this setting by editing the "IsShowRptParameters" parameter in
the web.config file, which is located in the root of the EWA web site.
f. Developer mode. Select this check box if you want to run SSRS in developer mode.
g. Click Next.
10. On the Enter the application server information dialog, enter the following:
a. Application Server. Enter the URL for the Epicor application. For example,
AppServerDC://Epicor9servername
b. Port. Enter the port for the application server.
c. User name. Enter a user name for logging into the Epicor application.
d. Password. Enter a password and confirmation password for the user.
e. Click Next.
11. On the Enter the mail configuration information dialog, enter your company's SMTP values. If you do not
know your this information, use your Epicor application to open Company Configuration and review the
System values.
a. SMTP server. Enter the name of the SMTP server.
b. SMTP port. Enter your port number. The port value is >0 and < 65536.
c. Email from. Enter the originating email address.
d. Click Next.
12. To configure the Windows Service, you can accept the defaults, or enter your own values. The defaults
include:
a. Concurrent agents. Specifies the number of agents allowed to run simultaneously. Default is 5. Value
is > 0 and <=20.
Progress Version 79
b. Polling interval. Specifies the number of seconds to wait between listening for activity. Default is 3.
Values are >0 and <1200 seconds, or 20 minutes.
c. Login interval. Specifies the number of seconds to wait before checking on the Appserver, if it is not
started. Default is 100. Values are >0 and <1200 seconds, or 20 minutes.
d. Purge interval. Specifies the number of days to wait before the system automatically deletes the data.
Default is 10. Values are >1 and <99 days.
e. Click Next.
13. To configure the server printers, do the following:
a. Click on the printer button (paper and green plus sign) on the right.
b. Enter the print identifier. For example, enter \\servername\printername
c. Click OK.
d. Click Next.
14. On the Configure the Windows Service dialog, enter the following:
a. SSRS Script Location. Enter the server location where your script file, such as the RS Scripter Load All
Items.cmd, is located. For example, enter C:\Program Files\Epicor Software\Epicor905\SSRS\.
b. RS.EXE Location. Enter the location where the report service file (RS.EXE) is located. For example, enter
C:\Program Files\Microsoft SQL Server\100\Tools\Binn\RS.EXE
c. To deploy all the reports that are in the SSRS Script location, select the Deploy Epicor SSRS Reports
Now check box.
d. Click Finish.
15. If you selected the Deploy Epicor SSRS Reports Now check box, you are prompted with the message
stating that deploying the Epicor SSRS Report to Microsoft SQL Service Report Service may take a long
time.You are asked whether you want to run this process in a separate thread and not display the log file.
a. Yes. Click Yes to run the process now in a separate thread. After clicking Yes, the process exits and the
Epicor SSRS reports are deployed on a separate thread. To verify the report deployment, review the RS
Scripter Load Log file. This log file is located in the same location as the RS Scripter Load All Items.cmd
file, for example C:\Program Files\Epicor Software\Epicor905\SSRS.
b. No. Click No to wait until the deployment of the Epior SSRS reports is complete. After clicking No, the
process waits for the reports to complete and then the RS Scripter Load Log fle is displayed.
16. If prompted, click Close to exit the Epicor SQL Report Monitor installation.
17. To verify the installation was successful, start the Epicor SQL Report Monitor Service. To do this:
a. Navigate to Start > Control Panel > Administrative Tools > Services.
b. Select Epicor SQL Report Monitor Service.
c. Click Start this Service.
d. Navigate to Start > Control Panel > Administrative Tools > Event Viewer.
80 Progress Version
e. Expand the Applications node.
f. Verify that EpiSSRS is available.
18. To verify that your reports open correctly, open a report. To do this:
a. Go to your Reports site. For example, http://localhost/Reports
b. Click on the Reports folder. This folder was populated with all the reports located in SSRS\Reports folder.
c. Select a report to open. Verify it opens correctly.
F.6 Maintain Epicor SQL Report Monitor Configuration
After the installation, if you need to make additional changes to the Epicor SQL Report Monitor configuration
settings, you can use the Epi SSRS Service utility.
1. Verify that you have Administrator rights. If you run the utility with UAC turned on, you are prompted to
login as an Administrator to run the application
2. Go to Start > Programs > Epicor Software > Epicor SQL Report Monitor. Select the Configure Epi
SSRS Service.
3. Navigate to Start > Control Panel > Administrative Tools > Event Viewer. Select EpiSSRS and verify it
says Service is starting and Initial login to AppServer.
4. Exit from the Configure Epi SSRS Service.
Progress Version 81
Appendix G: Install Epicor Enterprise Search
Use these steps to install and configure your Epicor Enterprise Search.
G.1 Verify SQL Server Prerequisites
Use these steps to verify the requirements before you begin the installation and configuration of Epicor Enterprise
Search.
1. Verify that you are using SQL Server 2008 or SQL Server 2008 Express with SQL Server 2008 Express R2.
Note If you plan to use Epicor Replication Server, you must use SQL Server 2008. Epicor Replication
Server does not support SQL Server 2008 Express or SQL Server 2008 Express R2.
2. Verify that the SQL Server 2008 installation has SQL and Windows Authentication enabled.
3. Verify that the server where Enterprise Search is installed also has SQL Server 2008 installed as the named
or primary instance. For example, if your server is named Candy, then SQL Server 2008 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.
4. Verify you are running SQL Server locally.
5. Verify that the account you used to log into the system is trusted by SQL Server.
G.2 Create Back Ups (if Previous Version Installed)
Use the following steps to create back ups if you have a previous version of Epicor Enterprise Search installed,
and if you made modifications to existing templates or created your own templates.
1. On the server where Enterprise Search is installed, navigate to C:\Program Files\EnterpriseSearch.
2. Create a backup of the following folders: Templates, Profiles, and Tuning.
G.3 Uninstall Epicor Enterprise Search (if Previous Version)
Use these steps to uninstall Epicor Enterprise Search if you have a previous version installed.
1. Select Start > Control Panel > Add or Remove Programs.
2. Select Epicor Enterprise Search and click Remove.
G.4 Install Epicor Enterprise Search Process
Use these steps to install Epicor Enterprise Search.
1. Log on to the server where you intend to install Enterprise Search.
82 Progress Version
5. On the Epicor Utilities Setup dialog, click the Install Enterprise Search button to start the installation.
The Epicor Enterprise Search is now installed.
G.5 Configure Replication Server for Epicor Enterprise Search
This section is optional if you are using SQL Server for your Epicor 9.05 transactional database. When Epicor 9.05
is using Progress for its transactional database, you must replicate the data to a SQL Server database for use by
Enterprise Search. The replicated database must be configured as a Fully Functional (Read Only) Subscribing
database, which means that the database includes the necessary schema and code needed to store data for a
fully working Epicor 9.05 application.
Note Refer to Replication Server documentation in the Replication Server snap-in for Admin Console and
in the Epicor 9.05 application for full details on how to assign replication profiles, configure replication
subscribers, and enable data replication.
Use the following steps as a basis to create a subscriber database that Enterprise Search can use for indexing and
searching.
1. In your Epicor 9.05 application, go to System Management > Replication > Replication System
Maintenance.
2. Assign the existing replication profile for Enterprise Search to the companies that are going to be indexed
for searching. Data from the tables defined in the profile are replicated to the subscriber database for each
of the companies that were assigned the profile.
Note The Enterprise Search profile only includes the tables needed to support indexing and searching
for Enterprise Search. It is not a profile that replicates all the necessary data that is needed to run a
fully working Epicor 9.05 application. This means that the Epicor 9.05 application, including Epicor
Web Access, must be running using the Epicor 9.05 transactional database and not using the replicated
database. If you need to run the Epicor 9.05 application against the replicated database, you must
either create or use an existing replication profile that includes all of the tables in the transactional
database.
3. Create a new Epicor 9.05 database for use as the subscriber database. To do this, use the default SQL script
located in the directory where your Epicor 9.05 application server is installed. For example, use \Epicor
Software\Epicor905\server\sql\Epicor905.sql.
4. Use the Replication Management Console to add this newly created database as a Functional subscriber.
Progress Version 83
G.6 Configure Epicor Enterprise Search
Use these steps to setup and configure Epicor Enterprise Search. To complete most of these steps, you use
Enterprise Search Management from the Epicor Administration Console.
1. Login to the Epicor Administration Console as a user who can authenticate to the Enterprise Search Server.
2. Open the Epicor Administration Console. To do this, navigate to Start > Programs > Epicor Software
> Epicor Administrative Tools > Epicor Administration Console.
3. If you did not previously have Enterprise Search installed or installed to a new search server, from the Help
menu, select Help Topics and follow the instructions in the Initial Configuration > Start Here topic. You
are done with this procedure. However, if you previously installed Enterprise Search on the same server,
start instead with the remaining steps:
4. If the search server is not registered, right-click Enterprise Search Management and select Register
Search Server. Use the configuration wizard to enter the following:
a. On the Welcome page, review the process details. Click Next.
b. For the Server Registration, enter the Name of the server where the Enterprise Search Server components
are installed. Click Ping Server to validate the server name. For the Port enter the port number of the
Enterprise Search Server service. Keep the default of 9098 unless the server has been manually configured
to a different port. Click Validate Service to Continue to validate the port. If both validations are
successful, you can click Next.
c. Review the Search Database details, including the search Server Name and the Database used to build
the search index. Click Finish.
5. Right-click the computer name of the registered search server and select Delete Database. Right-click the
computer name of the registered search server and select Create Database.
Note You only need to create one database per Enterprise Search server. One database stores all
search data. Using the above step, a database named SearchIndexversion is created on the default
SQL Server instance on the server where the Enterprise Search server components are installed. If you
want to choose the SQL Server instance used for the search database and/or choose its name, see the
"Set SQL Server for Search Indexing" topic in the online help.
6. Right-click the computer name of the registered search server and select Delete Web Application (if the
web application exists). Right-click the computer name of the registered search server and select Create
Web Application.
7. In the online help, go to the Initial Configuration > Start Here topic.
a. Begin with step 3 if you creating a new search index definition
b. Begin with step 4 to create a new search index from a previous version search template. Your old
template definitions should be available if you installed the search server components to the same location
as you previously installed search server components. Old template definitions cannot necessarily be
expected to work without some adjustments.
84 Progress Version
G.7 Uninstall Information
Use this information if you need to uninstall the Epicor Enterprise Search application.
• The uninstaller may warn that the Epicor Search Indexer service is running. If you receive this warning, select
the second option (continue anyway). A reboot is not required.
• The uninstaller will not delete files for indexed systems or other information not initially installed with the
system. These files are kept in the [Program Data]\EpicorSearch folder if you want to remove them manually.
Progress Version 85
Appendix H: Install Epicor Mobile Access
Use these steps to install and configure Epicor Mobile Access.
H.1 Enable IIS 6 Management Compatibility
If you are running IIS 7, use these steps to enable IIS 6 Management Compatibility. The steps are different based
on your operating system.
H.1.1 Using Vista and Windows 7
1. Open the Control Panel. Click Programs or Programs and Features.
2. Select the Turn Windows features on or off option
3. Expand Internet Information Services > Web Management Tools > IIS 6 Management Compatibility.
4. Verify that IIS Metabase and IIS 6 configuration compatibility is selected.
5. Exit the Control Panel.
H.1.2 Using Server 2008
1. Run Server Manager.
2. From Roles > Web Services (IIS), right-click and select Add Role Services. Note that this node is only
present when IIS is already installed.
3. Expand Management Tools > IIS 6 Management Compatibility.
4. Verify that IIS 6 Metabase Compatibility is installed.
5. Exit the Server Manager.
H.2 Install Epicor Mobile Access Process
Use these steps to install Epicor Mobile Access.
1. In order to use Epicor Mobile Access, a license must be imported. Verify that the Epicor Mobile Access license
was imported using the Epicor Admin Console using the previous Import License Codes section in this
guide.
86 Progress Version
5. On the Epicor Utilities Setup dialog, click Install Epicor Mobile Access to open the Epicor Mobile Access
Installer.
6. On the Welcome to the Epicor Mobile Access Setup wizard, click Next.
7. On the Application Server Connection dialog, enter the name of the Application Server. For example, enter
the server name that is hosting the Epicor application.
8. Enter the Port number for the Epicor application connection. This port must allow communication between
the Epicor Mobile Access server and the Epicor application server. Click Next.
9. On the Select Installation Address dialog, use the drop-down menu to select a Site. This is the site configured
in IIS. The default is Default Web Site.
Note If you need to create a site in IIS, refer to your Microsoft documentation.
10. Enter the Virtual Directory name for the Epicor Mobile Access application. The default is EpicorMobileAccess.
The name can be changed to any name allowed in IIS. If the default is accepted, a virtual directory is created
in IIS with a physical path and folder located under the \inetpub\wwwroot folder.
11. Use the drop-down menu to select an Application Pool that is configured in IIS. Click Next.
Note If you need to create an application pool in IIS, refer to your Microsoft documentation.
12. On the Confirmation dialog, click Next to begin the installation. Epicor Mobile Access is installed.
H.3 Configure Epicor Mobile Access
Use these steps to configure Epicor Mobile Access using your Epicor application. See the Epicor application help
for more detailed steps, if necessary.
2. Navigate to System Management > Company Maintenance and open the User program.
3. Select a User Id that requires ability to use Epicor Mobile Access on supported mobile devices. Click the
Security tab.
4. Select the Allow Mobile Access check box.
5. Click Save on the Standard toolbar.
6. If you want to make an Epicor application dashboard available for a mobile device, review the Create Mobile
Device Dashboards in the Epicor application help.
Progress Version 87
Appendix I: Install Epicor Information Worker
Use these steps to install Epicor Information Worker.
1. If you have a previous version of Epicor Information Worker installed, you must uninstall several components prior
to installing the new version. To do this:
a. Select Start > Control Panel > Add or Remove Programs.
b. Select Epicor Information Worker Configuration Manager and click Remove.
c. Select Epicor Information Worker Server for Epicor and click Remove.
d. Select Epicor Information Worker Server Framework and click Remove.
e. Verify the uninstallation was completed successfully.
2. Navigate to the location where your Epicor application is installed. For example, Epicor/Epicor905. Go to the /Info
Worker folder.
Note If you need to install Epicor Information Worker on a server other than where your Epicor application
is installed, copy the /Info Worker folder to that server.
3. Select and open the EpicorIWGuide.pdf file.
4. Use the instructions in the Epicor Information Worker Installation Guide to install Epicor Information Worker.
88 Progress Version
Appendix J: Install Epicor Sharepoint Publisher
Use these steps to install Epicor Sharepoint Publisher on your server.
1. Log on to the server where you intend to install Epicor Sharepoint Publisher.
5. On the Epicor Utilities Setup dialog, click the Sharepoint Publisher 32 Bit or Sharepoint Publisher 64 Bit
button to start the installation.
7. Specify the folder for the installation of Epicor Sharepoint Publisher. Select Everyone as the user of the computer.
Click Next.
The Epicor Sharepoint Publisher functionality is now installed.
Progress Version 89
Appendix K: Configure Your Help System
After your Epicor application is installed, your help system is ready to access from within the application by pressing
F1 or selecting Contents from the Help menu. The field-specific help is also available by selecting Field Help from the
Help menu.
The following steps are optional, but recommended if you want to improve the performance and efficiency of the help
system by hosting the help in a web site and implementing server-side searching. For example:
• Host Help System in a Web Site. If your Epicor application is used over a wide area network (WAN), by default
the help system (a large collection of non-compiled html files) is installed to be accessed from the file system.
Alternately, you can host the help on a web site to improve the speed of accessing the help.
• Implement Server-side Searching. By default, the help system searching capability relies on index files that are
downloaded to each client workstation. Alternately, you can implement server-side searching which uses Windows
Search and provides a more robust and faster search. In addition to having natural language searches, users can
do advanced searches using Boolean operators, and/or choose to search only among help topic titles. See the
application help for more information on advanced help system searches.
It is recommended that you complete both of these optional configurations. Note that you can host the help in a web
site without implementing the server-side help, but you cannot implement the server-side help without hosting the
help in a web site.
K.1 Host Help System in a Web Site
Use the following steps to configure your help system to run in a web site.
1. Navigate to the root where your Epicor application is installed. Copy the Help folder to your web server.
2. For Windows operating systems, select Start > Run. Enter inetmgr to start Internet Information Services
(IIS).
3. Open the IIS online help and follow the instructions for creating a virtual directory. Be sure you create a
virtual directory pointing to the physical location of the Help folder you copied in the previous step.
Note For Windows 2008, you must make the virtual directory an application and have it use an
application pool that uses the Managed pipeline mode of type Classic.
4. After you created the virtual directory, test the help by using your Internet browser to open the snm_enu.htm
file which is located in the Help/enu/Standard directory. For example, browse to
http://<servername>/Help/enu/Standard/snm_enu.htm.
Note Do not set the snm_enu.htm file as a default document.
5. Edit each client .mfgsys configuration file to use the help URL you just created. To do this:
a. Navigate to the Client\Config folder on your workstation.
b. Open the .mfgsys file in a text editor, such as Notepad.
c. Edit the <helpServer uri=" " /> line to add the new help URL between the empty quotes. For example,
if you created a virtual directory with an alias of Help on a server named MyServer, the edited line would
look similar to <helpServer uri="http://MyServer/Help/" />
90 Progress Version
K.2 Implement Server-Side Help Search (Windows Server 2008)
Use these steps to implement the server-side search using a Windows Server 2008 environment.
1. Verify that you completed the Host Help System in a Web Site instructions in the previous procedure.
2. Verify that ASP.NET is enabled on the web server. See your Internet Information Services (IIS) documentation
for information on how to make the verification.
3. Select Start > Programs > Administrative Tools > Server Manager.
4. Under Roles Summary, click the File Services. Add the File Services role if it does not already exist.
5. Under Role Services, check for Windows Search having a status of installed. If it is not, click Add Role
Services, select Windows Search Service and click Install.
Note If you had Windows 2003 Indexing Service installed (under Windows 2003 File Services), clear
its check box to uninstall it since you cannot run both Indexing Service and Windows Search at the
same time.
6. Select Start > Settings > Control Panel > Indexing Options. Note the locations being indexed. Click
Modify. Clear check boxes next to any folder that you do not want to index. Make sure that the Standard
folder under the Help\enu folder (for example, C:\www\Help\enu\Standard) is selected for indexing. In later
steps the help search will be configured to search only the help folder. However, you may want to clear
other folders just so the indexing is not taking any CPU cycles indexing files you do not care to have indexed.
Click OK and Close.
7. Open Windows Explorer. Navigate to the Standard folder under Help\enu where you installed the help.
8. Use a text editor such as Notepad to edit the Web.config file in the Standard folder. Find this line: <add
name="EpicorHelpSearch" connectionString="C:\Program Files\Epicor
Software\Epicor905\Help\enu\Standard" />. Change the connection string portion that is in quotes to
the path where your Help\enu\Standard folder is located. Save and close the file.
Note Using search in Epicor help only returns results from .html files in the folder (and its subfolders)
you configured in the above step.
9. Select Start > Run and enter inetmgr to start Internet Information Services (IIS). Go to the virtual directory
you created for the help system. Expand the nodes down to enu/Standard.
10. Right-click Standard and select Convert to Application. Click OK. Close the IIS console.
11. Open Windows Explorer. Go to the help system folder. Expand the node down to
enu/Standard/frameset.bak/indexserver.
12. Copy the snm_enu.htm file and paste it in the root of the Standard folder. When prompted, select Copy
and Replace to copy the file.
Progress Version 91
Appendix L: Upgrade to Infragistics NetAdvantage
If you use Epicor's Software Developer's Kit (SDK) to modify or extend the application forms, you may need to upgrade
the Infragistics NetAdvantage version that is used by your Epicor application. See the SDK documentation for specific
version information.
1. Review the SDK documentation that came with Epicor 9.05. The document includes recommended steps for a
successful migration.
2. Follow the Infragistics Upgrade instructions and, as a minimum, choose to install the Infragistics .Net 2.0
components.
92 Progress Version
Appendix M: Install SonicMQ
Use this appendix to install SonicMQ 7.6 on a mobile device. You must install SonicMQ if you use the Multi-Site module,
Customer Connect, Supplier Connect, EuroFinancials, or Mobile Connect so that information can transfer between
companies. The installation of SonicMQ is also required for users of financial consolidations.
M.1 Determine Your Security
Sonic Software has the ability to function with username/password security. In an effort to increase the security
of the software, customers are able to turn security on if they want.
1. Determine if you want to enable SonicMQ security during installation.

Note For Sonic Security to be enabled, it must be implemented during installation. If you already
have Sonic installed without security, then you must uninstall and reinstall of Sonic.
2. Be aware that the installation instructions differ based on whether you enable security:
• Use the following Install SonicMQ with Security Enabled instructions if you have decided to install SonicMQ
with the security functionality.
or
• Skip to the following Install Sonic MQ without Security instructions if you have decided NOT to install
Sonic MQ with the security functionality.
M.2 Install SonicMQ With Security Enabled
Use the following instructions to install SonicMQ as an advanced installation, which includes enabling the security
functionality.
Note If you do not want to install SonicMQ with security enabled, skip to the next section.
1. Insert the SonicMQ DVD into the drive.
2. Run the SETUP.EXE file in the root directory of the SonicMQ DVD.
3. Enter the directory where the Progress Client Software is installed. Click Next.
4. Select the SonicMQ software Advanced Install option. Click Next.
5. Click Next.
Files are copied from the SonicMQ install into your Progress directory. The Progress Sonic MQ Adapter
accesses these files to communicate with SonicMQ.
6. Begin the installation of SonicMQ. Click Next.
7. Read the registration and license information. Click Next. Read the license agreement, accept the terms.
Click Next.
Progress Version 93
8. Enter the SonicMQ License Key provided. Click Next.
9. Perform a new installation. Click Next.
10. Enter the directory where you would like SonicMQ to be installed.
11. If the directory does not exist, you will be prompted to create a new directory. Click Yes.
12. Select the Custom installation. Click Next.
13. By default, all features are installed. The first five are mandatory for Mobile Connect. Enter the program
group folder you want to use. Click Next.
14. Install the JRE. Click Next.
15. Keep the defaults for the Management Connection information. If you would like to change the defaults,
please contact Support before doing so. Click Next.
16. Keep the defaults for the Broker Options information, with the exception of checking the Enable Security
checkbox. If you would like to change the other defaults, please contact Support before doing so. Click
Next.
17. Review the installation. Click Next.
18. Monitor the progress of the install. Click Finish.
19. Reboot the server.
M.3 Install SonicMQ Without Security Enabled
Use the following instructions to install SonicMQ as a typical installation, which does not include enabling the
security functionality. If you want to install SonicMQ with security enabled, use the previous section instead.
1. Insert the SonicMQ DVD into the drive.
2. Click Next.
3. Select the Progress Client Software directory and click Next.
4. Select SonicMQ software, Typical install, and click Next.
5. Click Next.
6. SonicMQ is installed silently on your server. A command window may appear. Keep the window open until
the install is complete.
7. Run the postinstall process. To do this, double-click 76postinstall.exe on the CD-ROM, or choose Start >
Run and enter the command: D:\76postinstall.exe
9. The SonicMQ Install Location window appears. Enter the location where SonicMQ has now been installed.
The default is C:\epicor\SonicMQ76.
10. Click Next. Do not check the box that this is an upgrade.
94 Progress Version
11. Click Install.
12. Click Finished.
13. Reboot the server.
M.4 Install SonicMQ Updates
Use these steps to install any SonicMQ updates, if available.
M.4.1 Download Latest Update File
3. Go to the Third Party Products / Progress Sonic directory. Based on your environment, download the
latest Sonic service pack file onto your machine, if any are available.
M.4.2 Install Sonic SP for Windows
1. Double-click the Sonic service pack file. The installation program opens.
3. On the installation directory dialog, browse for a location or click Next to accept the default directory.
4. Click Next to confirm the information. The download of the install files begins. This may take several minutes.
5. Click Finish. The Service Pack files are now downloaded and the installation is ready to begin.
6. The Sonic SP Installation Welcome dialog opens. Click Next.
7. Review the License Agreement. Click Next.
8. To install Sonic on the primary Directory Service, select the Primary Directory Service check box. Click
Next.
9. Enter or browse for the Directory Name for the Directory Service. Click Next.
10. Enter the name of the broker and the location of the database. Click Next.
11. Review the summary information. Click Install. The Sonic update is installed.
12. When the Installation is finished, exit the installer.
Progress Version 95
M.5 Set Up Sonic Test Environment
If you use a test environment, it is recommended that you make a copy of your live data and put it in a completely
isolated environment on a test server.
This separation ensures that prototyping and testing is done in a quarantine area without the possibility of
inadvertent data being sent to your live environment. The precaution of a separate environment is recommended
where Sonic messaging is used since the test data has the same company id and messaging ports as your live
system. The separate environment minimizes the risk of human error when moving databases around for testing
and training purposes.
To set up a test environment, you will need the following:
• Test Server. A low-cost test server can be a low-end server or a XP Professional workstation with a minimum
of 2GB of RAM.
• Sonic Installation. The test server must have its own installation of Sonic.
• Progress Database. If the base database is Progress, the entire database and Epicor application must be on
the test server.
• SQL Database. If the base database is SQL, then the Epicor application is on the test server and the database
is located on the SQL server where the Epicor databases currently reside. This will save on SQL license cost.
Note Be sure to place your training database and your live database on separate servers. If you do not
and you run test multi-company processes, the shared records populate both the training and the live
databases.
M.6 Review Possible Installation Messages
Use the following troubleshooting tips to help resolve issues you may encounter.
M.6.1 Adapter .jms error in the AppServer log
Error: Application Service adapter.progress.jms not found at NameServer at Host 127.0.0.1 Port 5162. (8245)
Error connecting to the JMS AppServer Service.
Problem: The SonicMQ Adapter is not started.
Resolution: The SonicMQ Adapter "sonicMQ1" is created by default for you when you install the AppServer
license. If you go to the properties, it needs to contain a unique port number and be set to Auto start (which
means it starts when the Admin Service starts), otherwise it must be started manually from the Progress Explorer
Tool or OpenEdge Explorer Tool. If the SonicMQ Adapter is started properly, when you check the Status, status
information appears in the sonicMQ1 Status dialog box.
M.6.2 Javax.jms Exception error in the AppServer log
Error: javax.jms.JMSException: java.net.ConnectException: Connection refused: no further information:

TCP://localhost:2506. Error connecting to JMS AppServer service.
Problem: The SonicMQ broker cannot start. The SonicMQ Container is not started.
Resolution: Start the SonicMQ Container.
M.6.3 Javax.jms Security error in the AppServer log
Error: javax.jms.JMSSecurityException: Inauthentic Client. Error connecting to the JMS AppServer service
Problem: The SonicMQ "Administrator" Password is not correct, or the Device Username/Password is not correct.
96 Progress Version
Resolution: Enter a correct username and/or password.
M.6.4 General Error Message
Error: Not Accepting Messages at this Priority

Problem: The program UpdateDBIni.exe was not run properly following the installation of SonicMQ.
Resolution: All Sonic and Progress processes must be stopped. Run the fix program and reboot the server.
Progress Version 97
Appendix N: Set Up Multi-Company Functionality
Use this appendix to set up your Epicor 9.05 application to support multi-company functionality. You can also review
the Multi-Site Technical Reference Guide for this information. This guide is located within the application help under
the Multi-Site Management > Working With > Multi-Site Technical Reference Guide topic.
Note You must install the SonicMQ application before you can run Consolidation processing. This application
is required in order to pass data between multiple companies and databases.
N.1 Verify Multi-Site Management License
Verify you have the Multi-Site Management license module codes for both companies participating in
Multi-Company communication. If the companies reside on different databases, a separate serial number is
required.
N.2 Verify SonicMQ Broker Status
Use the following steps to verify the SonicMQ Broker status. The SonicMQ Broker is a batch file that enables a
TCP port to listen for messages being passed between two Epicor companies. The SonicMQ Broker must be
running in order for two companies to communicate in a Multi-Company environment.
The executable files used to start the SonicMQ Broker can be configured to start as a Windows service. Contact
Support for the batch file required to set up the Windows service.
Note If needed, you can run SonicMQ 6.1 (with Vantage 8.03x) and SonicMQ 7.6 (with Epicor 9.05) on
the same machine. To do so, contact Support for specific installation and configuration instructions.
1. Select Start > Programs > Sonic Software > SonicMQ 7.6 > Start [Machine Name].
2. Verify that the SonicMQ Broker is running. A successful startup of the SonicMQ Broker looks like the following:
98 Progress Version
N.3 Configure an External System Record
Use the following steps to configure an external system record.
1. Verify the status of External System Maintenance. To do this, select System Management > External
System Integration > Setup > External System Maintenance.
2. Search by clicking the External System button, and selecting the Multi record.
3. On the detail sheet, enter the information necessary for the Epicor application to know how to communicate
with Sonic. The fields include:
a. Sonic LAN Hostname & Sonic WAN Hostname. Enter the Hostname or IP Address of the machine
where the Sonic Container is running. If the value is left blank, the default localhost is used.
b. Sonic Security Enabled & Sonic Administrator Password. Use these fields if Sonic password security
was enabled during installation. Select the Sonic Security Enabled checkbox and enter a Sonic
Administrator Password. Note that the values in Sonic are case-sensitive. If the value is left blank, the
default "Administrator" is used.
c. Sonic Session Port. Enter a value that corresponds to the port number of the Progress NameServer.
This is used to find the SonicMQ Adapter, which is the software that Progress uses to communicate with
Sonic. If the value is left blank, the default 5162 is used. If more than one version of Progress/OpenEdge
is installed on the server, one of the two installations must use a different port number.
d. Sonic Broker Port. Enter the value that corresponds to the port number of the SonicMQ Container. If
the value is left blank, the default 2506 is used.
e. Sonic Listener Pause (sec). Enter the amount of time required for Progress to wait before it assumes
Sonic has finished sending all incoming messages. If the value is left blank, the default 10 is used.
f. Sonic Communication Protocol. Enter the following values: TCP - Transmission Control Protocol - this
is the default value; SSL - Secure Socket Layer; HTTP - Hypertext Transfer Protocol; HTTPS - Secure
Hypertext Transfer Protocol
The External System record would look similar to the following:
Progress Version 99
N.4 Configure an External Company Record
Use the following steps to configure an external company record.
1. Configure an External Company record for each company that will communicate with the current company.
For example, if you have three companies in your multi-company setup, each company will have two external
company records set up. In a two company multi-company setup, each company will have one external
company record.
2. Open External Company Maintenance. To do this, select System Management > External System
Integration > Setup > External Company Maintenance.
3. In the drop-down selection list at the top, select Multi-Company.
4. Search to see if any multi-company records already exist.
5. If the record does not exist, enter in the external company ID with which you will be exchanging information.
This is not the current company you are logged into. You cannot enter the current company ID as an external
company.
6. Enter the applicable information into the external company record. The External Company record would
look similar to the following:
7. Optionally, click on the available tabs and enter the following information:
• Connection. If you are connecting to a multi-company dashboard, enter connection options for the
servers so that you are allowed to view information between companies.
• External Plant. If you using consolidated purchasing, enter the external plant detail information.
• External Warehouse. If you are using consolidated purchasing, enter the external warehouse detail
information.
• Multi-Company. If you are using consolidated purchasing, multi-site GL journals, or AP allocations,
enter the necessary information.
100 Progress Version

8. If you use multi-site GL journals, or AP allocations, you need to initialize your GL accounts. To do this, from
the Actions menu, select Initialize > Send Multi-Company G/L Accounts.
9. Save the record. Close the External Company Maintenance window.
10. Switch companies. To do this, select Options > Change Companies.
11. Select the other company that will be used in this Multi-Company configuration.
12. Go back into External Company Maintenance and set up an external company record for this company
pointing to the original company.
As a result, each of the two companies in this example have an external company record pointing to each
other company in this Multi-Company setup.
N.5 Verify Your Startup Schedule
Use the following step to verify if you have a Startup Schedule.
1. Determine if a startup schedule has been created. To do this, select System Management > Utilities >
System Agent.
2. Click on the Agent ID button.
3. Perform a search, and open the only record returned. Expand the tree on the left until you see a list of
schedules. This may be blank.
The screen should look similar to the following if you have a startup schedule already created. Notice the
schedule type of StartUp.
4. If you do not have a startup schedule created, create one by selecting File > New > New Schedule.
5. Enter the Startup Task Schedule description and select StartUp as the Schedule Type.
6. Save the record. You now have a startup task schedule to which you can assign tasks, such as the
Multi-Company Server process.
Progress Version 101

N.6 Schedule the Multi-Company Server Process
Use the following steps to put the Multi-Company process on a Startup schedule:
1. Select System Management > Utilities > Multi-Company Server Process. The screen should look similar
to the following:
2. Select Startup Task Schedule (the schedule that already existed, or the one just created) from the Schedule
drop-down selection list.
3. Select Continuous and Recurring.
4. Click the Submit button in the toolbar.
Now the process is submitted to run. If you look at your system monitor, the Scheduled Tasks tab would look
similar to the following:
N.7 Start the Multi-Company Process
The Multi-Company process is attached to a startup schedule so it will not run until the server starts. Use the
following steps to mimic this server action, which will start and stop the process server and task agent in the
Progress Explorer Tool or OpenEdge Explorer Tool for this database.
1. Open the Progress Explorer Tool or OpenEdge Explorer Tool. Connect to the server, and go to AppServers.
For example, if a database was named custdb15, then the process server could be custdb15ProcessServer,
and the task agent could be custdb15TaskAgent.
2. Right-click on each entry and choose Stop, or press the Stop button at the top when the Appserver is
selected. Your screen would look similar to the following:

3. The task agent may take a minute to fully stop. To check to see if it stopped, right-click on it and select
Status. If you see the status screen, the process is still stopping. Once this screen goes away, the process
has stopped.
4. Restart the processes after they have stopped. To do this, right-click on each one and click Start, or highlight
the Appserver and press the Start button at the top.
5. After you have restarted both processes, check the task agent status to verify it is running. Broker Status
= Active, Active Server = 1 and Busy Server = 1.
6. Return to the System Monitor. The Multi-Company Process instance that was scheduled appears in the
Active Tasks tab. It will also still be in the Scheduled Tasks tab. When Multi-company functionality is
running, your System Monitor should look similar to the following:
N.8 Review Multi-Company Log File
Use these steps to review the informative log file that is created during processing. The file is located by default
in the working directory of the database, or wherever you specified during process scheduling.
1. Open the log file. Activity in the log file will look similar to the following:

2. Notice the messages stating there was a Sonic Session Failure. This message can be a result of any of the
following:
a. SonicMQ Container not installed, configured or running properly
b. SonicMQ Adapter not installed, configured or running properly
c. SonicMQ Security installed, but password value is not entered correctly
d. Inability to reach SonicMQ Container using the hostname and/or port numbers provided
After the issue is resolved, the session failure messages stop.

Note In a Multi-Company environment, the Multi-Company Server Process needs to be running only once.
In a Multi-Site environment, the process must be running for each database.
N.9 Test the Communication
Use the following steps to test the Multi-Company environment is communicating properly. You need to create
a Global Customer and verify that the customer is transmitted to the other companies.
1. Verify that the main (Epicor904) AppServer logging level is set to Verbose or Extended. This will also
increase the logging level for the Multi-Company log.
2. In one company (for example VN10T), create a new customer and select the Global checkbox.
The Multi-Company Process transmits Customer and ShipTo records from that company and sends it to
the other companies (for example VN20C and VN30C).
3. Save the record.
4. Review the MultiCompany.log file to verify that the record was sent to the Sonic Container. The log file
could look similar to the following

• If the outbound transmission is working properly, the Multi-Company log will include the message:
Processing Outbound Customer (VN10T/VN20C).
• If the inbound transmission is working properly, the Multi-Company log will include the message:
Processing Inbound Customer (VN20C).
If the records are being sent and received, your Multi-Company functionality is configured and running.
N.10 Review Sonic Container Information
Use the following steps to login to the Sonic Management Console, which provides an in-depth look into the
Sonic Container.
1. Open the Sonic Management Console. Enter your login information. The default information will work if
the management console is opened from the server that is also running the Sonic Container. Click OK.
2. Click on the Manage tab. Expand the tree on the left to the broker level.
3. Right-click on a subscription on the left and click Browse Local Subscriptions. Available message are
displayed. Click on the Body tab to view the message contents in XML format.
This same methodology for viewing contents in a sonic container apply for any Sonic application.
N.11 Review Validation Errors
Use these steps to review the validation errors. Careful examination is required when sharing information between
two companies. The companies may have different sets of codes, and intervention is needed during the transmission
process.
1. Review the log file for errors. With errors, your log file may look similar to the following:

2. Notice that the Company record, Quote Markup, Allocation Priority, Tax Region, Customer Group, and FOB
sent from company VN10T were invalid when the company arrived in company VN20C. On the ShipTo
record, the Territory and Tax Region were invalid.
3. Find out why the records were invalid. Correct the issues.
N.12 Review Automatic Data Translations
Use these steps to review the results of the automatic translation that runs during the inbound portion of the
transmission process. The translation process compares the code sets of the two companies and synchronizes
the data in order to save manual steps.
1. Review the translation data. Your data could look similar to the following:

For example, if the Terms Code NET30 exists in company VN10T, but the same code is N30 in company
VN20C, the inbound customer will fail validation. A translation should be set up in company VN20C on the
external company record for VN10T with Source Value NET30 and Target Value N30.
If company VN10T sends Customer records where the Terms Code is blank, and your system needs inbound
Customer records to have the Terms Code default to N30, create a record indicating the default value.
N.13 Review Integrated Workbench
When a Validation Error occurs, manual intervention is required. Most of the functions within Multi-Company
have a specially designed screen for handling these errors. Functions include Link Customer, Link Part, Link
Vendor, Incoming Intercompany PO Suggestions, and Add Intercompany Receipt.
1. If you are unable to fix a validation error using one of these screens, use the Integrated Table Workbench
to access the record. Your workbench could look similar to the following:
2. Modify the required values.
N.14 Review Multi-Company Functionality
Use the following programs to review Multi-Company functionality.
1. Global Table. Using Global Part, Global Customer, and Global Supplier functionality, a child company has
the ability to control which fields they want to be maintained by the Global Parent company. This can be
controlled for all external companies or can be maintained separately for each external company
2. Global Part. Use the Link Part tab in Part Maintenance.
3. Global Customer. From the Actions menu within Customer Maintenance, select the Link Customer
option.

4. Global Supplier. From the Actions menu within Supplier Maintenance, select the Link Supplier option.
5. Inter-Company Trading. Use the Incoming Intercompany PO Suggestions options from the Main Menu
or the Incoming Linked PO Suggestions in Customer Maintenance.
6. Global BAQ. Global BAQs are visible within Business Activity Query.
7. Consolidated Purchasing. Consolidated Purchase Orders are handled using the normal functionality in
Purchase Order Entry, Receipt Entry, and AP Invoice Entry.

Appendix O: Review Configuration File Settings
Use this appendix as a reference when modifying the configuration file settings in the default.mfgsys file. The mfgsys
file defines the main settings for server installation and each client installation. If the .exe file can see the default.mfgsys
file, the application is ready to run.
The configuration file is an XML file that contains syntax understood by the application. System Administrators use it
to control various installations.
Note You can also create a different configuration file and then have each workstation launch with this alternate
file. You can then keep the original file while you experiment with different configurations. Create the alternate
configuration, and then define the /CONFIG run time argument on each workstation.
Configuration File (*.mfgsys) Tags
XML Tag Purpose and Expected Value

Application Settings
<appsettings>
AppServerURL The address of the appserver where the client connects protocol://server:port; it
uses the form value "AppServerDC://servername:port"Protocol: AppServerDC by
default, or else AppServer for load balancing.Server: Host name of the machine
that runs AppServer.Port: The port of the broker that runs the software. Default is
8301. Also, AppServer accepts strings and numbers, but the port value only accepts
numbers.
CultureCode value The ISO language code for the software installation. This will be the language used
on the overall system or the specific client machine.For example "enu" (English
language)
ResourceFile A path name to the resource file. This file contains images and other resources that
can be changed by partners for branding purposes; for example
"C:\mfgsys\client\res\MfgBaseImages.resources"
ToolbarSettings The path and XML file that defines the users' default settings for the toolbar
functionality.For example, ".\res\ToolbarSettings.xml"
ProductID value The product identifier; for example "Epicor"
Version value The current release and patch number for the application; for example "9.05.500"
EnterpriseProcessing Whether multiple concurrent sessions are allowed on the workstation. The choices
are true or false (the default).
SmtpServer The SMTP server that will be used to send e-mail.
ProductBrandText value The text that appears with the desktop icon
ProductBrandIcon value The icon for the application that appears on the desktop
ProductLogonImage value The bitmap file that is double-clicked to log into the system
SplashImage The splash screen image when you first log in
HelpAboutImage value The bitmap file for the Help About window
User Settings <userSetting>
UserID value The user ID for auto-login; for example, "BobJones"


Password value The password for auto-login; for example, "BobJ"
DataCollectionUser value Defines whether or not this user is a data collection user; these users only have
access to Data Collection functionality. Only two values can be used - "true" or
"false"
StartSystemMonitor value Defines whether or not the System Monitor will start when the application is
launched.Only two values can be used - "true" or "false"
LastLoginID value The most recent login identifier that was used to access the application; for
example"BobJones"
LoginDefault value The login default setting that defines what appears in the User Name field. Four
values are possible:"Last" - Displays the last user ID that was used"List" - Displays
a list of all the recently entered user identifiers"Windows" - Displays the same user
ID used to log onto Windows on this client machine"None" - No default value;
the User Name field will be blank
FormOpenMode value The mode by which each form within the application will launch. Three values are
possible:"AutoSearch" - Each form automatically displays its search program. For
example, the Sales Order Entry program will automatically launch with its Sales
Order Search program ready for input"AutoPopulate" - Each form automatically
displays data from the first record linked to the form"Blank" - Each form loads
without a special mode; all the fields are empty
DefaultSearchFormLocation The area on your screen where all Search forms will appear by default:"top" - All
Search forms will automatically display in the top center of your screen"center" -
All Search forms will automatically display in the middle of your screen
SingleSignOn value The choices are true or false (the default). A value of true means that single sign-on
logic should be used. No prompt for user ID and password, should appear, but
instead the user ID of the current Windows user should be used.
Deployment Settings
<deploymentSettings>
DeploymentServer The URI of the deployment directory on the deployment server.
deploymentType value The method the deployment system uses to deploy client assemblies. The only
accepted values are xcopy (the default) and zip (which copies a named zip file locally
and then unzips).
deploymentPackage value If the deploymentType is of type zip, the name of the zip file. The default is
ReleaseClient.zip.
optimizeAssemblies value The choices are true or false. A setting of true requires the user to have admin
rights on the machine.
doDateComparison If deploymentType is set to xcopy, this setting determines whether the xcopy runs
and does a date comparison with the /D switch, or downloads all files regardless
of date.The choices are true (the default) or false. If it is set to false, then xcopy
copies all files regardless of modification date.
Help Settings <helpSettings>
HelpServerURL The path name that is used to point the client machine to the help files. If you want
to link the help files to a central server instead of individually on each client, enter
the path to the help files location on the server.
Epicor on the Web
<epicorOnTheWebSettings>


CustomerCenter product The product and URL used when the user accesses the Customer Center; for
example "Epicor" followed by the URL href =
"https://epicweb.epicor.com/SupportVantage/default.aspx"
OnlineSupport product The product and URL used when the user accesses online (ePortal) support; for
example "Epicor" followed by the URL href = "https://eportal.epicor.com"

Appendix P: Uninstall Options
Use these instructions if you need to uninstall the Epicor Application, if needed.
1. Use the Progress Explorer Tool or OpenEdge Explorer Tool to stop the following functions in order:
• Stop the databases.
2. Delete the databases:

• For SQL: Use SQL Management Studio to manually delete the SQL databases.
• For Progress: Browse to the database folder and manually delete the database files that are located in the
database subfolders. For example, go to C:\Program Files\Epicor Software\Epicor905\DB.
3. Remove the Epicor 9.05 application. To do so:
a. Insert your Epicor 9.05 DVD in the workstation's DVD-ROM drive (D:\). The autorun feature should launch the
Epicor 9.05 Installation program. If not, choose Start > Run and enter the command: D:\ setup.exe.
b. The Welcome dialog box appears. Click Next.
c. The Check Customer Center on the Web option appears. Click Next.
d. The Select the Software to Install window appears. Select the Install Epicor 9.05 Server option. Click Next.
e. Select which Server platform option you want to uninstall:

• Progress OpenEdge on Windows
• SQL on Windows
• SQL Unicode on Windows
f. The installation goes into Repair Mode. Choose Uninstall. Click Next.
g. To confirm the uninstall, click Next.
4. The uninstall process does not delete files that were added or updated since the initial installation. To complete
the uninstall process, go to the location where you initially installed the Epicor application. For example, go to
C:\Program Files\Epicor Software\Epicor905. Manually delete any existing files and folders.

Additional information is available at the Education and
Documentation areas of the EPICweb Customer Portal. To access
this site, you need a Site ID and an EPICweb account. To create an
account, go to http://support.epicor.com.

Epicor905 InstallGuide 90560x Progress

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Epicor905 InstallGuide 90560x Progress

Transféré par

Droits d'auteur :

Formats disponibles

Epicor 9.

Part I: Getting Started....................................................................................10

Chapter 1: Verify Release Documentation..............................................10

Chapter 2: Perform Required Upgrades...................................................12

Chapter 3: Set Up Test Environment........................................................14

Chapter 4: Create Back Ups......................................................................14

Part II: Pre-Installation....................................................................................16

Chapter 5: Pre-Installation Steps..............................................................16

5.9 Download Latest OpenEdge Updates................................................................................................19

Part III: Installation.........................................................................................21

Chapter 6: Install the Epicor 9.05 Server..................................................21

Chapter 7: Install Latest Updates.............................................................28

Chapter 8: Install Epicor Administration Functionality...........................31

Chapter 9: Install the Epicor 9.05 Client...................................................32

Part IV: Post-Installation.................................................................................35

Chapter 10: Post-Installation Steps on the Server..................................35

10.3 Upgrade to Service Connect 9.05...................................................................................................38

Chapter 11: Prepare Your Database.........................................................39

Chapter 12: Log in the First Time.............................................................45

Chapter 13: Restore Demonstration Database........................................50

Chapter 14: Configure Windows Admin Workstation (Optional)..........54

Appendix A: Configure 64-Bit Environment (Windows 2008)...............56

Appendix B: Install Embedded Education Courses.................................58

Appendix C: Install Epicor Administration Console................................61

Appendix D: Install and Deploy Epicor Web Access...............................62

Appendix E: Install Epicor DB Replication...............................................75

Appendix F: Install Epicor SQL Server Reporting (SSRS)........................76

F.2 Enable IIS 6 Management Compatibility............................................................................................76

Appendix G: Install Epicor Enterprise Search..........................................82

Appendix H: Install Epicor Mobile Access................................................86

Appendix I: Install Epicor Information Worker.......................................88

Appendix J: Install Epicor Sharepoint Publisher.....................................89

Appendix K: Configure Your Help System..............................................90

Appendix L: Upgrade to Infragistics NetAdvantage...............................92

Appendix M: Install SonicMQ...................................................................93

M.5 Set Up Sonic Test Environment........................................................................................................96

Appendix N: Set Up Multi-Company Functionality.................................98

Appendix O: Review Configuration File Settings.................................109

Appendix P: Uninstall Options...............................................................112

Part I: Getting Started

Chapter 1: Verify Release Documentation

1.1 Verify Revision Date

2. Navigate to Epicor 9 > Version 9.05.600.

1.2 Review Revision History

Release Section Description

Release Section Description

Chapter 2: Perform Required Upgrades

2.1 Verify Access to EPICweb

1. Verify you have Internet access at your workstation.

2.2 Verify Latest 9.04.507x Version Installed

2.3 Verify Financial Groups are Posted

Chapter 3: Set Up Test Environment

3.1 Set Up Test Environment Process

2. Copy your database into your test environment.

3. Verify your test environment is separate from your live system.

Chapter 4: Create Back Ups

4.1 Back Up Database and System

1. Verify your database is stopped.

2. Create a backup of all your database files.

a. Navigate to Start > Programs > OpenEdge 10.1c > Proenv.

b. Go to the folder where your database is located.

c. At the prompt type: proutil mfgsys -C truncate bi

d. Exit the ProEnv Utility.

4.2 Back Up Customized Reports