Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
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.
SQL Version Revision: September 13, 2011 3:33 p.m. Total pages: 119 install_sql.ditaval
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
SQL Version
Contents
5.8.3 Using Windows Server 2008 R2..............................................................................................19 5.9 Download Latest Updates.................................................................................................................19 5.10 Download Latest OpenEdge Updates..............................................................................................20 5.11 Setup Progress OpenEdge Explorer Tool..........................................................................................20
SQL Version
Contents
10.3.1 Establishing an administrative account..................................................................................37 10.3.2 Establishing Local Security Policy...........................................................................................37 10.3.3 Establishing the AdminService Setting...................................................................................38 10.4 Upgrade to Service Connect 9.05...................................................................................................38 10.5 Upgrade to Epicor Portal 9.05.........................................................................................................39 10.6 Setup Full-Text Searching on MS SQL Server....................................................................................39 10.6.1 Review the Process - Building Full-Text Catalogs....................................................................39 10.6.2 Starting the MS SQL Search Service.......................................................................................40 10.6.3 Enabling Full-Text Search for Your Database.........................................................................40 10.6.4 Defining the Catalogs...........................................................................................................40 10.6.5 Changing Database Schema.................................................................................................41 10.6.6 Initial Population of Catalogs................................................................................................41 10.6.7 Verifying that the MSSQL Server Agent is Running................................................................42 10.6.8 Setting Up the Catalogs to Update Incrementally..................................................................42 10.6.9 Testing Server Impact for each Job........................................................................................43
SQL Version
Contents
13.3 Restore the Demonstration Database - SQL Server...........................................................................55 13.4 Import Product Licenses and Enable Modules..................................................................................57 13.5 Start Database and Main Appserver................................................................................................57 13.6 Run Manual Conversion..................................................................................................................58 13.7 Set Up System Agent for Printing (Demo Database).........................................................................58 13.8 Restart Remaining Appservers.........................................................................................................59 13.9 Test Demonstration Database Update.............................................................................................59
SQL Version
Contents
D.12 Generate Web Forms for User Dashboards.....................................................................................78 D.13 Review Supported Browsers and Configuration..............................................................................78 D.14 Set Up Compression for Performance Tuning.................................................................................79 D.14.1 Compression for Windows 2008 or Vista (IIS7).....................................................................79 D.15 Set EWA Server Timeout.................................................................................................................80
Appendix E: Install Epicor Replication Server.........................................81 Appendix F: Install Epicor SQL Server Reporting (SSRS)........................82
F.1 Verify SSRS Prerequisites...................................................................................................................82 F.2 Enable IIS 6 Management Compatibility............................................................................................82 F.2.1 Using Vista and Windows 7....................................................................................................82 F.2.2 Using Server 2008...................................................................................................................83 F.3 Install Custom Assembly DLL File (Report Server)................................................................................83 F.4 Install Microsoft Report Viewer 2010 Redistributable Package...........................................................84 F.5 Configure Epicor SQL Report Monitor...............................................................................................84 F.6 Maintain Epicor SQL Report Monitor Configuration...........................................................................87
Appendix I: Install Epicor Information Worker.......................................94 Appendix J: Install Epicor Sharepoint Publisher.....................................95 Appendix K: Configure Your Help System..............................................96
K.1 Host Help System in a Web Site........................................................................................................96 K.2 Implement Server-Side Help Search (Windows Server 2008)..............................................................97
SQL Version
Contents
SQL Version
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:
SQL Version
Getting Started
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.
Pre-Install
10
SQL Version
Getting Started
Section Post-Install
Description Changed "Verify Parameter File Settings"; Changed "Restore Demonstration Database" Security Manager login to epicor / epicor
SQL Version
11
Getting Started
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
SQL Version
Getting Started
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.
SQL Version
13
Getting Started
14
SQL Version
Getting Started
SQL Version
15
Pre-Installation
16
SQL Version
Pre-Installation
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.
SQL Version
17
Pre-Installation
18
SQL Version
Pre-Installation
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.
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: SQL Server (32 bit): SP90560x-S.EXE SQL Server (64 bit): SP90560x-S64.EXE SQL Unicode (32 bit): SP90560x-SU.EXE SQL Unicode (64 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: SQL Server: PA90560xx-S32.EXE SQL Server 64: PA90560xx-S64.EXE SQL Unicode: PA90560xx-SU32.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.
SQL Version
19
Pre-Installation
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).
4. After being installed, you can access the OpenEdge Explorer tool from Start > Programs > OpenEdge Explorer.
20
SQL Version
Installation
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. b. Use the instructions provided on the website to guide you through the installation process.
SQL Version
21
Installation
22
SQL Version
Installation
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.
SQL Version
23
Installation
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. 18. Reboot your server.
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. 6. The Welcome window appears. Click Next.
24
SQL Version
Installation
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
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. 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.
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.
SQL Version
25
Installation
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.
26
SQL Version
Installation
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. a. 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. a. If prompted with a message that The SQL Database restore failed, most likely you selected a SQL Instance that is not SQL 2008 or later, click OK. The installation continues. 11. On the Server Setup window, click Finish. If prompted to confirm exiting the setup program, click OK. The server software installation is complete.
SQL Version
27
Installation
28
SQL Version
Installation
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.
SQL Version
29
Installation
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.
30
SQL Version
Installation
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.
SQL Version
31
Installation
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. 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 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. b. Use the instructions provided on the website to guide you through the installation process.
32
SQL Version
Installation
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.
SQL Version
33
Installation
2. 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
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.
34
SQL Version
Post-Installation
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 -disabledeltrig Description Required Value
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. changes read-only record retrieval to get consistent results Improve performance -rereadnolock -ttmarshal 5
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 PRGRS_NOWAIT_OVERRIDE TXN_ISOLATION PRGRS_NATIVE_LOCKWAIT Required Value PRGRS_NOWAIT_OVERRIDE,1 TXN_ISOLATION,1 PRGRS_NATIVE_LOCKWAIT,30000
SQL Version
35
Post-Installation
5. For both SQL and Progress databases, use the following to verify the optional parameters in the .pf file. Parameter -Bt Description Improve appserver performance in dealing with temporary tables. 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. Optional Value -Bt 4096
6. If needed, review the parameter values in the following example .pf files. Example: Progress
Example: SQL
36
SQL Version
Post-Installation
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.
SQL Version
37
Post-Installation
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
38
SQL Version
Post-Installation
SQL Version
39
Post-Installation
40
SQL Version
Post-Installation
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: sp_fulltext_catalog 'custxprt', 'create','e:\fulltextcatalogs\custxprt' 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.
SQL Version
41
Post-Installation
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.
42
SQL Version
Post-Installation
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.
SQL Version
43
Post-Installation
44
SQL Version
Post-Installation
3. The Schema Change Required window appears. In the Password field, enter CHANGESCHEMA. Click Continue.
SQL Version
45
Post-Installation
Note The automated SQL database conversion may take longer than normal because it now more fully accommodates the upgrade to SQL 2008.
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.
46
SQL Version
Post-Installation
2. Browse to the location where you previously downloaded the license code file. Select the file and click Open to import the file. 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.
SQL Version
47
Post-Installation
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
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.
48
SQL Version
Post-Installation
Stop the OpenEdge database. 2. Use the Progress Explorer Tool or OpenEdge Explorer Tool to start the following functions in order: Start the OpenEdge database. Start the Appservers.
SQL Version
49
Post-Installation
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.
50
SQL Version
Post-Installation
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.
SQL Version
51
Post-Installation
Description specifies the local path on the server to the print directory specifies the unc path to the print directory specifies the unc path to the server directory
52
SQL Version
Post-Installation
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.
SQL Version
53
Post-Installation
54
SQL Version
Post-Installation
SQL Version
55
Post-Installation
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 one of the following and press Enter: SQL 32 bit: prorest mfgsyssh mfgsyssh32.bkup SQL Unicode 32 bit: prorest mfgsyssh mfgsyssh32u.bkup SQL 64 bit: prorest mfgsyssh mfgsyssh64.bkup SQL Unicode 64 bit: prorest mfgsyssh mfgsyssh64u.bkup 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. 10. At your server, navigate to Start > Programs > Microsoft SQL Server 2008 > SQL Server Management Studio (SSMS). 11. Within SSMS, verify the Server Type is connected to the database engine. 12. Navigate to the Databases node. 13. Right-click on the EpicorTrain905 database. From the context menu, select Tasks > Restore > Database. The Database window displays. 14. Click on the General tab. Within the Source for Restore section, select From Device. 15. Click on the [...] button. The Specify Backup window displays. 16. For the Backup Media option, select File. 17. Click the Add button to locate and select the backup file. This file is: Epicor9_Database_WinxxSQLx.BAK 18. Click OK twice to complete the selection. 19. Select the check box next to the Backup Name field. This defines the back up set to restore. 20. Click on the Options tab. 21. Select both the Overwrite the existing database and Leave Database Ready to use (Restore with Recovery) check boxes. 22. Verify the Restore Database Files As fields match the correct server directory paths where the database files currently exist. For example: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\ EpicorTrain905.mdf C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\ EpicorTrain905_log.ldf 23. Click OK. 24. A dialog box displays indicating the database restoration is complete. Click OK. 25. Exit SQL Server Management Studio.
56
SQL Version
Post-Installation
SQL Version
57
Post-Installation
58
SQL Version
Post-Installation
9. In the SystemAppServer section, enter your directory paths. For example: Directory Server File Client File Client Program Description specifies the local path on the server to the print directory specifies the unc path to the print directory specifies the unc path to the server directory Examples c:\Program Files\Epicor Software\EpicorData/usr/epicor/epicordata \\<servername>\EpicorData \\<servername>\Epicor905\Server
10. Save the System Agent changes. Exit System Agent Maintenance. 11. Close the Epicor 9.05 application.
SQL Version
59
Appendices
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.
60
SQL Version
Appendices
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.
SQL Version
61
Appendices
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.
62
SQL Version
Appendices
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. 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.
SQL Version
63
Appendices
64
SQL Version
Appendices
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.
SQL Version
65
Appendices
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.
66
SQL Version
Appendices
D.2.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.
SQL Version
67
Appendices
2. Navigate to Epicor 9 > Version 9.05.600 > Third Party Products > Crystal. 3. Download the latest Crystal Reports Runtime file from EPICweb to your workstation. For example: Crystal_2008_03_Runtime.zip. 4. Navigate to the downloaded file. Open the .zip file and extract the contents. 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. 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.
68
SQL Version
Appendices
2. Navigate to Epicor 9 > Version 9.05.600 > Third Party Products > Crystal. 3. Download the latest Crystal Reports Embedded Server file from EPICweb to your workstation. For example: Crystal Reports 2008 Embedded Server SP3.zip. 4. Navigate to the downloaded file. Open the .zip file and extract the contents. 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. 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.
SQL Version
69
Appendices
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.
2. The Epicor Web Access Installer windows appears. Click Next. 3. The Basic Installer Settings dialog opens. It looks similar to the following:
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:
70
SQL Version
Appendices
Enter the following information: 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. 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:
SQL Version
71
Appendices
Enter the following information: 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. 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.
72
SQL Version
Appendices
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.
SQL Version
73
Appendices
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 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.
74
SQL Version
Appendices
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.
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.
SQL Version
75
Appendices
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.
76
SQL Version
Appendices
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.
SQL Version
77
Appendices
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.
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.
78
SQL Version
Appendices
SQL Version
79
Appendices
80
SQL Version
Appendices
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 Replication Server.
SQL Version
81
Appendices
82
SQL Version
Appendices
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.
SQL Version
83
Appendices
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.
84
SQL Version
Appendices
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.
SQL Version
85
Appendices
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.
86
SQL Version
Appendices
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.
SQL Version
87
Appendices
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.
88
SQL Version
Appendices
2. Go to the directory where your Epicor application is installed. For example, go to \Epicor Software\Epicor905. 3. Double-click on the EpicorUtilities.exe file. 4. On the Welcome to the Epicor Utilities Setup wizard, click Next. 5. On the Epicor Utilities Setup dialog, click the Install Enterprise Search button to start the installation. 6. On the Welcome dialog, click Next. 7. On the Confirm Installation dialog, click Next. The files are installed. 8. When the installation is complete, click Close. The Epicor Enterprise Search is now installed.
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.
SQL Version
89
Appendices
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.
90
SQL Version
Appendices
SQL Version
91
Appendices
92
SQL Version
Appendices
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. 13. When the installation is complete, click Close.
SQL Version
93
Appendices
3. Select and open the EpicorIWGuide.pdf file. 4. Use the instructions in the Epicor Information Worker Installation Guide to install Epicor Information Worker.
94
SQL Version
Appendices
SQL Version
95
Appendices
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/" />
96
SQL Version
Appendices
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="file:C:/ExamplePath/ExamplePath/Help/enu/Standard" />. Change the connection string portion that is in quotes to the path where your Help\enu\Standard folder is located. Leave the file as is and use forward slashes instead of back slashes as is shown in the example path. 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.
SQL Version
97
Appendices
2.
98
SQL Version
Appendices
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.
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.
SQL Version
99
Appendices
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.
100
SQL Version
Appendices
11. Click Install. 12. Click Finished. 13. Reboot the server.
2. Navigate to Epicor 9 > Version 9.05.600. 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.
SQL Version
101
Appendices
102
SQL Version
Appendices
SQL Version
103
Appendices
104
SQL Version
Appendices
SQL Version
105
Appendices
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.
106
SQL Version
Appendices
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.
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.
SQL Version
107
Appendices
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:
108
SQL Version
Appendices
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:
SQL Version
109
Appendices
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.
110
SQL Version
Appendices
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.
SQL Version
111
Appendices
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.
112
SQL Version
Appendices
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.
SQL Version
113
Appendices
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.
114
SQL Version
Appendices
CultureCode value
ResourceFile
ToolbarSettings ProductID value Version value EnterpriseProcessing SmtpServer ProductBrandText value ProductBrandIcon value ProductLogonImage value SplashImage HelpAboutImage value User Settings <userSetting> UserID value
SQL Version
115
Appendices
Purpose and Expected Value The password for auto-login; for example, "BobJ" 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" Defines whether or not the System Monitor will start when the application is launched.Only two values can be used - "true" or "false" The most recent login identifier that was used to access the application; for example"BobJones" 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 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 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 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.
FormOpenMode value
DefaultSearchFormLocation
SingleSignOn value
Deployment Settings <deploymentSettings> DeploymentServer deploymentType value The URI of the deployment directory on the deployment server. 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). If the deploymentType is of type zip, the name of the zip file. The default is ReleaseClient.zip. The choices are true or false. A setting of true requires the user to have admin rights on the machine. 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.
116
SQL Version
Appendices
Purpose and Expected Value 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" The product and URL used when the user accesses online (ePortal) support; for example "Epicor" followed by the URL href = "https://eportal.epicor.com"
OnlineSupport product
SQL Version
117
Appendices
118
SQL Version
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.