Installation Guide
Windows MSSQL Database
Copyright © 2010 by Epicor Software Corporation. All rights reserved. Printed in the United States of America. No part of this publication may be reproduced in any form without the prior written consent of Epicor Software Corporation. Epicor, Vantage, and Vista are registered trademarks of Epicor Software Corporation. All other trademarks are property of their respective owners. Microsoft product screen shots reprinted with permission from Microsoft Corporation. Epicor Software Corporation makes no representations or warranties with respect to the contents of this document and specifically disclaims any implied warranties of merchantability, satisfactory quality or fitness for any particular purpose. The contents of this document are believed to be current and accurate as of its date of publication. Changes to this document between reprintings 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. Item Code: 90560-905
1. Perform Required Upgrades... Page 5 2. Set Up Test Environment... Page 6 3. Create Back Ups... Page 7 4. Epicor 9.05 Pre-Installation Steps... Page 8 5. Install the Epicor 9.05 Server... Page 14 6. Install Latest Updates... Page 22 7. Install Epicor Administration Functionality ... Page 24 8. Install the Epicor 9.05 Client ... Page 25 9. Post-Installation Steps on the Server ... Page 28 10. Prepare Your Database for Epicor 9.05 ... Page 37 11. Log in the First Time ... Page 42 12. Restore Demonstration Database ... Page 48 Appendix A: Configure 64-Bit Environments (If needed) ... Page 54 Appendix B: Install Embedded Education Courses... Page 55 Appendix C: Install and Deploy Epicor Web Access ... Page 69 Appendix D: Install Epicor Replication Server ... Page 74 Appendix E: Install Epicor SQL Server Reporting (SSRS)... Page 79 Appendix F: Install and Configure Epicor Enterprise Search... Page 85 Appendix G: Install Epicor Information Worker... Page 87 Appendix H: Configure Your Help System... Page 88 Appendix I: Upgrade to Infragistics NetAdvantage ... Page 92 Appendix J: Install SonicMQ... Page 92 Appendix K: Set Up Multi-Company Functionality... Page 96 Appendix L: Review Configuration File Settings... Page 108 Appendix M: Uninstall Options... Page 111
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:
Yes
Are you on the latest SP/Patch?
Epicor 9.05 Pre-Installation
Install Epicor 9.05 Server
Install Epicor 9.05 Client
Epicor 9.05 Post-Installation
- Download and install Microsoft Tools: .NET 3.5 and Web Services 3.0 Runtime - Start Server Installation from Epicor DVD - Install OpenEdge 10.2A (Service Pack, Hot Fix)
- Share Epicor Folders
- Install Epicor 9.05 Server Software
- Download and install Microsoft Tools: .NET 3.5 and Web Services 3.0 Runtime - Start Client Installation from Epicor DVD - Install Epicor 9.05 Client Software
- Install Crystal Runtime; Update Parameter File - Establish Progress AppServer security - Upgrade Service Connect 9.05 (optional)
- Upgrade Epicor Portal 9.05 (optional)
- Set up ODBC connections (new SQL only)
- Set up full-text searching (new SQL only)
Prepare Your Database
Epicor 9.05 is ready!
Set Up Test Environment
I am an Existing customer on 9.04.50x
I am a New customer
on 9.05
Create Back Ups
Log In the First Time
New Customers: Set Up system agent (printing) Existing Customers: Import Booking Rules, Set Up system agent, Maintain customizations, Test BAQ / BAM / BPM / custom code Optional Installations:
- Configure 64-Bit Environments - Install Epicor Education Courses - Install Epicor Web Access - Install Epicor Replication Server - Install Epicor SSRS - Install Epicor Enterprise Search - Install Epicor Information Worker - Configure Your Help System - Upgrade Infragistics NetAdvantage
- Install Sonic MQ - Set Up Multi-Company - Review Configuration Settings - Uninstall Options
Install Latest Updates (Service Pack, Patch)
No
Upgrade to 9.04.50xx (latest SP/Patch)
- Convert your database
- Connect to Epicor and application servers - Import license codes
- Run data conversions, stop and start servers
Restore Demonstration Database Install Epicor Administration
1. 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.
1.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).
If you do not have an Epicor customer User ID and Password, request one by
visiting our Epicor’s Customer Portal site. (http://support.epicor.com).
3. If you are new to EPICweb, review the links available on Epicor’s Customer Portal
home page. Information includes: * An Overview of the New EPICweb * Change or Reset Your Password
1.2 Verify Your Epicor Application is on Version 9.04
If you are an existing customer, prior to installing Epicor 9.05, your Epicor application must be upgraded to the latest version of 9.04.50x.
Note! If your Epicor application is at version 8.03.40x or earlier, you must first upgrade to Epicor 9.04. Contact your Epicor consultant for assistance if necessary.
4. 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
5. From the 9.04 section, download the Epicor 9 Installation - 9.04 guide for either
Progress, SQL or Linux/UNIX, based on your database.
6. Use the instructions to upgrade your Epicor application from 8.03.40x to 9.04.
7. Verify you have completed the required steps in the “Run Additional Conversions”
section prior to installing 9.05. 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 very
important that you manually run this conversion prior to installing 9.05. After converting to 9.05, you cannot run this conversion because the link between the historical data and the converted data is no longer available.
* 10012 - Setting BitFlag Field
1.3 Install Latest 9.04.50x Service Pack and Patch
Use this step to install the latest 9.04.50x service pack and patch onto your 9.04 system.
1. After you have upgraded your system to 9.04, 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
2. Download and install the latest Service Pack and Patch onto your 9.04 system. For
example, download and install the 9.04.506x Patch. Use the Service Pack or Patch Installation Guide, available on that same site, for instructions.
3. If you want to convert or create links from GL Journal detail to historical source
documents, verify you have manually run Conversion 10080 - (Creating TranGLC for posted PartTran).
Note! Do not skip this step if you want to convert or create links from GL Journal detail to historical source documents. It is very important that you manually run this conversion prior to installing 9.05. You cannot run this conversion after you have upgraded to 9.05 because the link between the historical data and the converted data is no longer available.
1.4 Perform Upgrade to SQL 2008
If you use SQL, use the instructions that came with SQL 2008 to install SQL 2008 on your database server. To use the Epicor 9.05 application, SQL 2008 must be installed. Be sure you install any Microsoft service pack and patch updates related to SQL 2008.
2. 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.
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.
3. Create Back Ups
Create the following back ups prior to continuing with your installation.
3.1 Back Up Database and System
Database and system backups are very important. Do not skip this step!
1. Create a backup of all your database files.
2. Create a backup of your other database files, such as test, train and pilot.
3. Create a backup of your manufacturing software. In a standard installation, the
files are located in the \oe101c and \epicor directories.
4. For SQL installations, it is recommended that you detach the EpicorTrain904
database so that a new Epicor 9.05 training database version can be installed.
5. 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.
3.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.
3.3 Back Up Custom Client MFGSYS Files
Use the following instructions to backup your custom MFGSYS files.
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.
3.4 Back Up Customizations
If you use customizations, it is recommended that you create a backup prior to installing. These backups can be used in case your current customizations do not convert properly.
1. Navigate to System Management - Utilities.
2. Select Customization Maintenance.
3. Click Name to open the search feature.
4. Select Customization as the Type. Click Search. Click OK.
5. Select a customization to back up.
6. Select Export Customization from the Actions menu.
7. Click Export to export the customization to the filename specified.
8. Repeat these steps for each customization you wish to export.
4. Epicor 9.05 Pre-Installation Steps
Use these steps prior to installing the Epicor 9.05 application.
4.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.
4.2 Review Software Requirements
Software requirements have been updated for this release. Use the following information to update your system.
* Windows Server 2003 Service Pack 2, Windows Server 2003 R2, Windows Server 2008, or Windows Server 2008 R2 must be installed on the server. * Windows XP Service Pack 2 must be installed on all Windows XP
workstations.
* 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. See the Microsoft Corporation website for IIS download information.
* 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 use a SQL database with the Epicor 9.05 application, you must have SQL 2008 installed on your database server. Use the instructions that came with SQL 2008 to install SQL 2008 on your system.
* If you use SQL or SQL Unicode and you are installing the Admin Tools and Schema Change shortcuts from the client workstation onto a Client Server Admin machine, you must also download and install the Microsoft SQL Server 2008 Native Client 10.0 driver. The installation of this driver allows the client ODBC connection to be successful.
* 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.
4.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
4.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.
* 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.
* If you use Windows Server 2008, you also need to install Application Server and IIS with V6 compatibility.
* 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.
4.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)
4.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
Note! To request assistance from Services, fill out the Services Request Form. The
form is available on the EPICWeb Services site. The link is: https://
epicweb.epicor.com/_layouts/formserver.aspx?XsnLocation=/FormServerTemplates/ Services%20Request.xsn&OpenIn=Browser&Source=https://epicweb.epicor.com/ services/Pages/default.aspx
4.7 Set Up SQL Collation for Epicor 9.05
A typical SQL installation sets the default database collation to be dependent on the Regional Settings of the SQL Server. This collation must match the collation of the individual Manufacturing databases in order for queries to operate properly. For example, if the collation does not match, searches on Parts Entry or Sales Order Entry will not work. This collation is not related to full text indexing; other full text indexed table searches will run fine. This is an issue only when the SQL server is not localized for English (US).
Use these steps to verify your SQL database collation.
1. Review the list of collation settings that are dependent on Regional Settings. To do
this, click on the following SQL 2008 link: (http://msdn.microsoft.com/en-us/
library/ms143508.aspx)
The correct collation setting for Manufacturing databases is
SQL_Latin1_General_CP1_CI_AS , which is the default for English (US) localized systems.
2. If the collation does not match, you must reinstall SQL Server and select custom
to allow a collation setting to be selected. Simply changing the databases to match a different system collation setting does not resolve the issue.
The SQL installer does not show the codes; it only shows descriptions. The required selection is under Collation Settings, SQL Collations. An example is Dictionary Order, Case-Insensitive, 1252 codepage.
This produces the required matching SQL_Latin1_General_CP1_CI_AS collation.
3. Change the Compatability Level to SQL 2008 (100) for all databases that will run
in the Epicor 9.05 application. The Epicor 9.05 application does not support SQL 2005.
4.8 Verify Prerequisite Hardware
If you have a Windows 64-Bit installation, use the following steps to verify your hardware requirements.
- Server. The central machine that coordinates activity on the network. - Client. The workstation for the typical user.
- Windows Admin Workstation. A client workstation for the administrator, from which the installation should be run. This is a very privileged client or “super-client”. This Windows Admin Workstation is available on the network. The workstation hardware can have either a 32-bit or 64-bit operating system.
4.9 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.
Using Windows Server 2003
1. Navigate to Start - Control Panel - System.
2. Click the Advanced tab. Click Error Reporting.
3. Select Disable Error Reporting.
4. Click OK until you exit.
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.
4.10 Download Latest Updates
Use these steps to download the latest service pack and patch files that will be installed later in the installation process.
1. Log on to EPICweb and go to the Customer Portal Page. Navigate to Support >
Note! You can use this link: https://epicweb.epicor.com/Support/epicor9/Downloads
2. Navigate to Epicor 9 > Version 9.05.600.
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 - SQL Server (32 bit): SP90560x-S.EXE
- SQL Server (64 bit): SP90560x-S64.EXE - SQL Unicode (32 bit): SP90560x-SU.EXE - SQL Unicode (32 bit): SP90560x-SU64.EXE
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-P.EXE - Progress on Windows (64 bit): PA90560xx-P64.EXE - SQL Server: PA90560xx-S.EXE
- SQL Server 64: PA90560xx-S64.EXE - SQL Unicode: PA90560xx-SU.EXE - SQL Unicode 64: PA90560xx-SU64.EXE
5. Download the latest Epicor 9.05 help content pack related to this installation. For
example, download the HELP90560x.EXE file.
6. Go to the OpenEdge/Version 10.2A directory. Based on your environment,
download the latest OpenEdge service pack file onto your machine. For example, select one of the following files:
- For Windows 32: 102ASP2.exe - For Windows 64: 102ASP2x64.exe
7. Go to the OpenEdge/Version 10.2A directory. Based on your environment,
download the latest OpenEdge hot fix file onto your machine. For example, select one of the following files:
- For Windows 64: Rl102asp0211hf-64.EXE file.
8. If you need to use the OpenEdge Explorer, instead of the Progress Explorer Tool,
go to the OpenEdge/Version 10.2A folder. Based on your environment, download the necessary files, including the OpenEdge Management and Explorer Guide. These files are also located on the Epicor 9.05 DVD in the OEManage folder.
5. 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.
5.1 Install Microsoft Tools: .NET 3.5 and WSE or WCF Runtime
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. (The link is: http://www.microsoft.com/downloads/ details.aspx?displaylang=en&FamilyID=ab99342f-5d1a-413d-8319-81da479ab0d7
- Download the latest version of Microsoft .NET 3.5 to your server. - 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 to Download Web Services Enhancements (WSE) 3.0 Runtime.
(The link is http://www.microsoft.com/downloads/ details.aspx?FamilyID=1F445589-818A-4E7B-B49B-FFE9393E4D0A&displaylang=en).
- Download the latest version of Microsoft Web Services Enhancements (WSE) 3.0 Runtime to your server and Windows Admin workstation.
- Use the instructions provided on the website to guide you through the installation process.
5.2 Stop Appservers and Database
Use the following steps to stop the appservers and database prior to starting the installation.
1. Sign on to the server and Windows Admin workstation as Administrator or
Administrator equivalent.
2. Existing customers (Epicor 9 /Vantage/Vista) need to select Start — Programs
— OpenEdge 10.1C — Progress Explorer Tool. Use the Progress 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.
5.3 Start Server Installation
Use the following steps to start the server installation.
1. Insert your Epicor 9.05 DVD in the Windows Admin 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.
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
5.4 Install Progress OpenEdge 10.2A
Use these instructions to install Progress OpenEdge 10.2A on your server and
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.
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:
If you selected the Typical / Automatic Install option:
1. Select the OpenEdge folder location for the Progress software directory. 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.
If you selected the Advanced / Manual Install option:
1. The OpenEdge 10.2A window appears. Click Install.
2. The Welcome window appears. Click Next.
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.
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.
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. 18. Reboot your server.
5.5 Install Progress OpenEdge 10.2A Service Pack
Use the following instructions to install the latest Progress OpenEdge service pack file on your server and Windows Admin workstation.
Note! Do not skip this step!
1. For existing users, select Start — Programs — OpenEdge 10.2A — Progress
Explorer Tool. 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. For example, for SP2 (32 bit) go to the 102ASP2.exe file or for SP2 (64-bit) go to the 102ASP2x64.exe file.
5. Double-click the OpenEdge service pack file. The installation program opens.
6. The Welcome window appears. Click Next.
7. Click Next to confirm you have backed up your system files.
8. Click Next to confirm the summary information. The installation proceeds.
- 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.
5.6 Install Progress OpenEdge 10.2A Hot Fix
Use the following instructions to install the latest Progress OpenEdge hot fix file on your server and Windows Admin workstation.
Note! Do not skip this step!
1. Go to the OpenEdge hot fix file that you downloaded to your machine during a
Pre-Installation step. For example, for SP2 Hot Fix 11 (32 bit) , go to
Rl102Asp0211hf.EXE or for SP2 Hot Fix 11 (64 bit) Rl102Asp0211hf-64.EXE
2. Double-click the file. The installation program opens.
3. The Welcome window appears. Click Next.
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.
8. Reboot your server.
5.7 Share the Epicor Folders
Use the following steps to share the Epicor folders. If you are using Windows Server 2008, the steps may be slightly different.
Note! If you want to secure the folders, your Administrator can change these values.
1. On the C: drive, create the C:\Program Files\Epicor Software\Epicor905 folder
if it does not already exist.
- Right-click on the \Epicor Software\Epicor905 folder and select Sharing and Security.
- 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.
- Click the Permissions button. It is recommended that you assign Full Control to the Everyone group. Click OK to accept the permissions.
- 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.
- Right-click on the folder icon and select Sharing and Security.
- Select the option to Share this Folder. EpicorData displays as the default share name.
- Click the Permissions button. It is recommended that you assign Full Control to each user folder. Click OK.
- Click OK to accept the share options.
5.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 which Server platform option you want to run:
- OpenEdge on Windows - SQL on Windows
- SQL Unicode 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.
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 is C:\Program Files\Epicor
Software\Epicor905 or specify a different drive location.
* The default installation directory for a 64-bit Windows install is C:\Program Files (X86)\Epicor Software\Epicor905 or specify a different drive location. * The default printer work directory is C:\Program Files\Epicor
Software\EpicorData or specify a different drive location.
* The default printer work directory for a 64-bit Windows install is C:\Program Files (X86)\Epicor Software\EpicorData or specify a different drive location.
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.
- On that same window, select a location where you want the SQL databases (.mdf) files installed. Browse to find a location or select the default which is C:\Program Files\Microsoft SQL Server\MSSQL\Data. Click Next.
7. The Microsoft SQL Server Instance window appears. Browse and select your SQL
2008 instance. Click Next.
8. When prompted with a “SQL Connection failed. Would you like to try again?”
message, click Cancel. This is normal.
9. The Wizard completion window appears. Click Next.
10. The Start Installation window appears. Click Next. Processing messages appear. This may take several minutes.
- If prompted with a message that “The SQL Database restore failed, most likely because you selected a SQL Instance that is not SQL 2008 or later”, click OK.. This is normal. The installation continues.
11. After the Client Files Installer configures the client, the installation is complete. On the Finish window, click Finish.
12. On the Server Setup window, click Exit. If prompted to confirm exiting the setup program, click OK.
6. Install Latest Updates
Use these steps to install the latest Epicor 9.05 service pack, patch and help system patch on your system.
6.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.
6.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. A Welcome window appears. Click Next.
4. A confirmation window appears. Click Yes to proceed.
5. Enter the directory where your program files are located. Click Next.
7. You might be prompted to verify your server name, operating system or database type. If prompted, select the appropriate option and click Next.
8. The Start Installation window appears. Click Next.
9. A message appears, stating that the application service pack installation is
complete. Click Finished.
The Epicor application service pack is now installed.
6.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.
2. Double-click on the file to run it.
3. A Welcome window appears. Click Next.
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.
6.4 Install Epicor 9.05 Help Content Service Pack
Use these steps to install the Epicor Help Content Service Pack on your system.
1. Go to the Epicor 9.05 Help Content service pack file that you downloaded during
a Pre-Installation step.
3. A Welcome window appears. Click Next.
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.
7. Install Epicor Administration Functionality
Use these instructions to install administration functionality, including the Epicor Administration Console and Windows Admin Workstation, if needed.
7.1 Install Epicor Administration Console
Use these steps to install the Epicor Administration Console on your server or Windows Admin Workstation.
1. Go to the directory where your Epicor application is installed. For 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.
7.2 Configure Windows Admin Workstation (64-bit Only)
If you installed the 64-bit versions of OpenEdge and the Epicor 9.05 application, you must use these steps to configure the Windows Admin Workstation. These steps can be run on a client or server machine, but they cannot be run on a server that already has a 64-bit version of OpenEdge installed.
Note! The 32-bit and 64-bit OpenEdge Software cannot be located on the same machine.
1. Verify that your machine does not have a 64-bit version of OpenEdge installed.
2. If you use SQL or SQL Unicode and you are installing the Admin Tools and
Schema Change shortcuts from the client workstation onto a Client Server Admin machine, you must also download and install the Microsoft SQL Server 2008 Native Client 10.0 driver. The installation of this driver allows the client ODBC connection to be successful.
3. Install the 32-bit version of Progress OpenEdge 10.2.A. See the Install Progress
OpenEdge 10.2A section of this document for instructions.
4. 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.
5. 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.
6. 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.
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.
8. Install the Epicor 9.05 Client
Use the following instructions to install the Epicor 9.05 client on your workstation.
8.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.
8.2 Install Microsoft Tools: .NET 3.5 and WSE or WCF Runtime
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. (The link ishttp://www.microsoft.com/downloads/ details.aspx?displaylang=en&FamilyID=ab99342f-5d1a-413d-8319-81da479ab0d7
- Download the latest version of Microsoft .NET 3.5 to your workstation. - 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 to Download Web Services Enhancements (WSE) 3.0 Runtime.
(The link is http://www.microsoft.com/downloads/ details.aspx?FamilyID=1F445589-818A-4E7B-B49B-FFE9393E4D0A&displaylang=en).
- Download the latest version of Microsoft Web Services Enhancements (WSE) 3.0 Runtime to your server and Windows Admin workstation.
- Use the instructions provided on the website to guide you through the installation process.
8.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.
2. Go to the Epicor905 folder. Double-click to run the Epicor9Client.msi file.
3. The Epicor 9.05 Client Setup menu opens. Click Install Epicor 9.05 Client
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.
- For the Client Destination, click Browse to navigate to a destination folder. For example, you can use C:\Program Files\Epicor Software\Epicor905.
- For the Server Share Location, use \\<servername>\Epicor905, where
<servername> is the machine name where the server installation was done.
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.
- Epicor 9.05: Select this checkbox to run your Epicor 9.05 database from this workstation.
- 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.
8.4 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.
3. Go to one of the following locations, based on your operating system: * Windows 2003/ Windows XP: Documents and Settings\All Users\Start
Menu\Programs\Epicor Software
* Windows 2008/ Windows 7/ Vista: Users\Public\Start Menu\Programs\Epicor Software
4. Paste the Epicor905 folder.
9. Post-Installation Steps on the Server
Use the following instructions to set-up your server after installation.
9.1 Install Crystal Reports 2008 Runtime
Use the following steps to install Crystal Reports 2008 Runtime on your server and Windows Admin workstation. This step is only required if you plan to print Crystal Reports forms from the server.
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. Go to the Third Party Products / Crystal directory. Download the latest Crystal
2008 Runtime file. For example, download Crystal_2008_Runtime.zip.
4. Unzip the file. Double-click to run the EXE file. For example, run the
CRRuntime_12_0_mlb.exe file.
5. The Welcome window appears for Crystal Reports 2008 Runtime. Click Next.
6. Review the o agreement information. Select I accept the License Agreement.
Click Next.
7. When prompted for the Product ID, do the following:
- Using a text editor, open the License Key.txt file that was extracted in a previous step.
- Copy the text and paste it into the Product ID field. - Click Next.
9. The installation proceeds. When it is finished, click Finish.
9.2 Update Basic Parameter File Settings
Use these steps to improve database performance if you have more than 4 GB RAM on the server where your Epicor application is installed.
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.
The available parameter files include: - Mfgsys.pf
- MfgTrain.pf - MfgTest.pf - MfgPilot.pf
3. Find the -Bt 4096 parameter entry. Increase the 4096 to a higher number based on
the amount of memory available. For example, if you have 8 GB of RAM available on the server, increase the number to 8192.
4. Save the file.
9.3 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.
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. 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 —
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 Establishing the AdminService Setting
Use the following instructions to establish the AdminService setting.
1. Use the Progress 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.
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.
9.4 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.
9.5 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.
9.6 Setup Full-Text Searching on MS SQL Server
To emulate the Progress database engine on Microsoft SQL Server, the need for keyword searches on certain fields is required. However, SQL Server does not allow the same, less featured, quicker searches that Progress natively allows. In order to fulfill this need, you are required to use the more fully featured and resource-intensive Microsoft Search Service.
The Microsoft Search Service uses Full-Text Catalogs to perform word searches on specific fields in the database. The Full-Text Catalogs are separate files of proprietary data structures, established for the purpose of evaluating ‘Contains’ and ‘FreeText’ queries.
These files are not automatically updated along with the rest of the database. Full-Text Catalogs must be “refreshed” on a periodic basis for them to reflect current data. The following information reviews the approach to keeping these Catalogs up-to-date while minimizing the impact of the refresh process on the overall server performance.
Review the Process - Building Full-Text Catalogs
Populating Full-Text Catalogs requires a great deal of processing power and substantial writes to the Disk subsystem on the server. Due to this, you benefit greatly from moving the catalogs to separate disks to avoid contention for the disk when writing the catalogs. More than one Catalog being built onto a disk results in Catalogs competing for space. The server’s resources will dictate how well you can avoid this bottleneck. Another variable in the creation of the Catalogs is the ‘Noise’ files used. Noise files contain any words or characters to be skipped in the creation of the Catalogs. Since our description fields largely do not contain actual text, the noise files are blank since this allows searching on most everything. The noise file feature is targeted more at the evaluation of text where there are many filler words that are unimportant for searching. SQL Server allows two “refresh” options: Full Population which refreshes the entire catalog from the metadata in the database; and Incremental Population which refreshes only the parts that have been changed. Results vary based on the placement of the catalogs on the disks, server resources, and the number of changes. However, Incremental populations take on average about one-third the time of Full populations. Since populating (refreshing) the Catalogs is done on a regular basis and since the process can be intensive, optimizing performance is an important part of optimizing the overall database server.
Starting the MS SQL Search Service
1. To verify that MS Search Service is running on the server, select Start — Control
Panel — Administration Tools — Services.
2. Confirm that the following Services are set:
* SQLServer Started Automatic
* SQLServerAgent Started Automatic
* SQLServer FullText Search Started Automatic
For any services that are not started, start the service and change the startup configuration if needed.
3. You may need to register a new SQL Server. To do this, open SQL Server
Management Studio. Register the server by selecting SQL Server Group. Right-click and choose New SQL Server Registration. Follow the prompts to set this up. Enabling Full-Text Search for Your Database
specific database.
1. In SQL Server Management Studio, right-click on the database that you want to
enable full text searching and select Properties.
2. In the Select a page section on the left side, select the Files option. Select the Use
full-text indexing check box. Click OK. Defining the Catalogs
After enabling text search on the database, you need to you need to enable the full-text searching on the specific database, tables, and columns. To do this, you need to define the Catalogs.
The Catalogs are separate files, so you need to determine where to place the files. For performance reasons, locating the Catalogs on separate drives avoids contention for disk resources during the regular populations of the Catalogs. Consider this, along with the times that you will run the jobs. If you choose to change the locations, you need to perform step 6 in the following steps to drop the catalogs then you can re-edit the scripts and jobs to reflect the new strategy.
Note! The MSSQL Full Text scripts are available in the following folder: C:\:Program Files\Epicor Software\Epicor905\server\sql.
1. At the server, use Windows Explorer to navigate to the batch file
CatalogDirCreate.bat. This file is located in C:\Program Files\Epicor Software\Epicor905\server\sql. (All SQL scripts are located in this path.).
Note! By default, the CatalogDirCreate.bat file is configured to use Drive E:. If you want to change the location from E:, right-click on the file, and edit it in a text editor to specify a different drive. For example, on the first line of execution code, change the e: to d: to specify the D: drive. Save and close the file.
2. Double-click to run the file. This batch file places the Catalogs on the E: drive and
in the single folder called FullTextCatalogs. If you prefer to place some Catalogs on a different drive to improve performance, edit this batch file or create the folders manually.
3. Open Query Analyzer and connect to the MSSQL Server running the Epicor905
database. Open the following script file: FullTextCatalogCreate.sql.
4. Review each catalog ‘create’ statement for each Catalog to verify the drive path.
For example, in the custxprt catalog, the ‘create’ statement looks similar to the following:
The above statement locates the Catalog on the E: drive in the fulltextcatalogs\custxprt folder. If you changed the drive path in the
CatalogDirCreate.bat file, you must edit this statement to reflect the physical path on the server to the folders created when the bat file was run. Catalogs can only be created on hard drives on the server, not on tapes or network drives. After editing the FullTextCatalogCreate.sql script, save the changes and keep for future needs.
5. Run the script from the Query Analyzer, the results window should read ‘Query
batch completed’ at the bottom of the window when completed. Confirm that the catalogs are created by opening SQL Server Management Studio then your server, ‘Databases’. Choose the Epicor905 Database, then drill down to ‘Full-Text Catalogs.’ All 32 Catalogs should appear in this list. You may need to ‘Refresh the display or open and close SQL Server Management Studio to get it to reflect the new Catalogs.
6. This is an optional step to change location. To drop the existing metadata and
Catalogs, run the FullTextCatalogDrop.sql script in the Query Analyzer. After this step, you will need to perform the above steps in the previous “Starting the MS Search Service” section again to re-setup the Catalogs.
Changing Database Schema
In order to run the Incremental population, the tables with the column used in a Full-Text population must contain a “timestamp’ column. The SQL Server can use this column to determine whether columns have been changed since the last Refresh.
1. Back up your MSSQL database before proceeding.
2. In the Query Analyzer, from the File menu, select Open - File. Select and run the
FullTextSchemaChange.sql script. This script adds the Timestamp field to each of the tables to allow MSSQL Server to know whether a record has changed since the last population.
Note! If the “timestamp” column already exists in a table, due to a previous script run, the message “Column name in each table must be unique” is displayed in the Results pane. This message lets you know that the “timestamp” field has already been successfully added to the table.
Initial Population of Catalogs
At this point, the MSSQL Server database is prepared and the Catalogs are created. You now need to add data. You do this by initially fully populating them.
1. Return to the Query Analyzer. From the File menu, select Open - File. Select and run the FullTextCatalogFullPop.sql script to perform a Full population of the database. This may take a few minutes to several hours depending on the size of your database and the speed of your server. This step needs to be run only once.
When running the this initial population of the catalogs, you can use the Windows Task Manager to help you determine when the populations have completed. To do this, open the Windows Task Manager and click on the Performance tab. Review your CPU usage. Once your CPU usage returns to a less utilitized status, then the Catalog Initial Population should be complete.
2. To test that the Catalogs have been populated, log onto the Epicor application.
Check that the keyword searches function is based on the data currently in your database. The preferred testing method is to use the Where Part Description Contains field for the Part Search component.
If your search returns appropriate data, then your Full-Text configuration is complete. Verifying that the MSSQL Server Agent is Running
The MSSQL Server Agent is an optional service that must be started and set to Auto-start with the MSSQL Server engine service.
1. Verify that in the above section “Starting the MS Search Service” you confirmed
that certain services were running and configured, including MSSQLServerAgent.
2. Navigate to Start — Control Panel — Administration Tools — Services.
Verify the following services are started: * MSSQL Server
* MSSQL Server Agent
3. Close the Services program.
Setting Up the Catalogs to Update Incrementally
After you have finished the initial population of your full-text catalogs, you may want to set your catalogs to be updated incrementally so they reflect the most current information. Each Full-Text enabled column has been split into its own separate Catalog to allow the flexibility of being run independently. Certain Catalogs will not be changed often enough to warrant running the refresh jobs on a daily basis (such as langorg). Use the following steps to configure an incremental schedule.
1. Log into Microsoft SQL Server Management Studio. Expand the SQL Server
Agent.
3. On the General page, enter a name for the schedule. For the category, select Full-Text. Enter a brief description of the schedule task.
4. Select the Steps page. Click the New button. Enter the name for the step. Verify
that Transact-SQL script (TSQL) type is selected. Select the database on which you want this job to run. Click Open.
5. Select the FullTextIncremental.sql script. Click Open. You should see the
contents of the script displayed in the window. Verify that the USE statement contains the name of your database. Click OK.
6. Select the Schedules page. Click the New button.
7. Enter the desired days and times you want the schedule to run. Click OK. Click
OK on the Job Properties window.
You have now configured your catalogs to be incremented automatically on a schedule. Testing Server Impact for each Job
After building the full-text catalogs and setting up the schedule, each Administrator should review the overall impact of the process and determine a strategy to balance timeliness and server performance. To do this:
1. At the server, go to Start - Control Panel - Administrative Tools and open the
Performance program. Right-click on the Counter column and select Add Counters. For Performance Object: Processor, add % Processor Time. For Performance Object: Memory, add Pages/sec.
2. Run each job individually.
3. In the Performance monitor, review the Processor and Memory values and verify
that they are low enough to see the effect of the populations, such as Processor Time: 25% or under and Pages/sec: 10 or under. Note that this process may need to be the only activity running against the server in order to view the real effect.
4. You can also confirm the current status of the Catalog using Enterprise Manager -
Databases - Manufacturing - Full-Text Catalogs. The listing of the Catalogs with their ‘Status’ and ‘Last Population’ are included. Note that this screen does not refresh easily.
You can also run ‘sp_help_Fulltext_Catalogs’ in the Query Analyzer to determine the current status. See the BOL (SQL Server books online) for detail.
5. Adjust the individual schedules of the Catalog Refreshes to optimize timeliness
10. Prepare Your Database for Epicor 9.05
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. Note! If you use SQL and you are a new customer installing the Epicor 9.05
application for the first time, you only need to complete the “Restore Schema Holders” steps in the “Convert Your Database” section.
10.1 Convert Your Database
Use these instructions to convert your database from 9.04.50x to Epicor 9.05 for compatibility with the Epicor 9.05 application.
Pre-Conversion Tasks
1. For SQL installations, verify that you have SQL and Progress installed on any
machine where Epicor Admin Tools is installed.
2. For SQL installations, verify that the following steps are completed on the same
server as where your SQL database is located. The Epicor 9.05 Schema Change process cannot be executed remotely.
3. If your database and Appservers are running, you need to select Start —
Programs — OpenEdge 10.2A — Progress Explorer Tool. Use the Progress Explorer Tool to stop the following functions in order:
* Stop the Appservers.
* Stop the OpenEdge database.
4. On the server, log in as the Local Administrator.
5. Navigate to the Microsoft SQL Server Management Studio.
6. Detach the Epicor904 database.
7. Place a copy of the Epicor904 database on the Epicor 9.05 test server.
8. In the Management Studio, delete the existing Epicor 905 Database.
