Epicor905 Spguide 905700 Sql 3g1r2o

[email protected]

conversion parameter to determine the service pack version from which you are currently upgrading. Specifying the conversion parameter prior to running the conversions can increase the conversion performance since it reduces the amount of data to be imported and it automates the upgrade of customized revisions. The parameter can be used in the following ways: • If the parameter value is left empty, the conversion import process replaces all posting rules and GL Transaction Type revisions, even those that have not changed since the previous service pack was installed. • If the parameter value specified is the previous service pack, for example "9.05.607", the conversion import process will begin at that service pack version and only import the posting rules that are new or updated since that previous release. • The parameter value must be entered as a service pack value, such as "9.05.607". Note that patches, such as 607a and 607b cannot be entered as a value. • The values can be specified as 9.05.602 or higher. 1.

On the server where your Epicor application is installed, navigate to the \Epicor905\server\cv folder.

2.

Use a text editor to open the ConversionParams.xml file.

SP Upgrade 9.05.60x to 9.05.700 - SQL

29

Post-Installation

3.

Epicor 9.05 Installation Guide

In the section, locate the tag. Enter a value to specify a service pack value for importing posting rules. The parameter section may look similar to the following: • X.XX.XXX where "x.xx.xxx" is the service pack version, such as "9.05.607".

4.

Review the mode specified for importing GL Transaction revisions. To do this, locate the tag. Review the values, which can be one of the following: • Update. Conversion will update current active revisions. • Override. Conversion will import new revisions for all Transaction Types. If this value is entered, you can also specify a MergeACTRevision value (Yes or No) to determine if you want to merge old versions of Active ACTRevision with the current versions.

5.

Save and close the file.

6.1.3 Restore Schema Holders If you are an existing SQL customer, use the following steps to restore your schema holders. 1. If your database and AppServers are running, use the Progress Explorer Tool or OpenEdge Explorer Tool to stop the OpenEdge database. 2. Make a backup copy of your current schema holder files. To do this, do the following: a. Go to the folder where your schema holder is located. For example, go to \Epicor905\db\newdb. b. Make a copy of your current schema holder files. The schema holder files are mfgsyssh.* 3. Navigate to Start > Programs > OpenEdge 10.2A right-click Proenv and select Run as from the menu. 4. Type the word prompt to return to a directory prompt. 5. Using cd commands, navigate to the folder where your schema holder is located. For example, navigate to \Epicor905\db\newdb. 6. In the folder where your schema holder files are located, if any previous schema holder files exist, you must delete them. For example, in the \Epicor905\db\newdb folder, delete the following files: mfgsyssh.db, mfgsyssh.d1, mfgsyssh.b1, and mfgsyssh.st. 7. To restore the schema holder backup file, at the prompt type one of the following commands, based on your environment: • SQL (32 bit): prorest mfgsyssh \backup\mfgsyssh32.bkup • SQL (64 bit): prorest mfgsyssh \backup\mfgsyssh64.bkup • SQL Unicode (32 bit): prorest mfgsyssh \backup\mfgsyssh32U.bkup • SQL Unicode (64 bit): prorest mfgsyssh \backup\mfgsyssh64U.bkup 8. Exit the ProEnv Utility.

30



Post-Installation

6.1.4 Run Schema Change Use these steps to run the schema change. 1. Change the starting method for the Service for OpenEdge. To do this: a. Select Start > Control > istrative Tools > Services. b. Right-click on Service for OpenEdge and select Properties. c. On the General tab, use the drop-down menu for Startup type to select Automatic. Click OK. Click Start to start the service. 2. Use the Progress Explorer Tool or OpenEdge Explorer Tool to do the following: a. Start the databases which you will be converting to the Epicor 9.05 level. b. that all appservers are stopped. 3. Open the Epicor Schema Change program. To do this, navigate to Start > Programs > Epicor Software > Epicor 9.05 > Epicor Schema Change icon for the appropriate database. 4. The Schema Change Required window appears. In the field, enter CHANGESCHEMA. Click Continue. 5. The Finish window appears. Click OK.

6.1.5 Start Main AppServer Use the following instructions to start the main AppServer. 1. Use the Progress Explorer Tool or OpenEdge Explorer Tool to start the main AppServer. 2. Minimize the Progress Explorer Tool or OpenEdge Explorer Tool. Do not start the other AppServers yet.

6.1.6 Import License Codes Use the following steps to import your Epicor 9.05 application license codes. Note If you are an existing customer using EDI or Demand Management, you must use these steps to import the new license for those modules. 1. In the Epicor istration Console, right-click on the desired database and select Connect to Application Server. 2. Right-click on the Licensing node and select Import License File. Your dialog may look similar to the following:


31

Post-Installation


3. Browse to the location where you previously ed the license code file. Select the file and click Open to import the file. 4. Double-click on the licensing code to open it. The Properties dialog opens. 5. 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.

6. Click OK. 7. Repeat the above steps, if you are importing licensing for multiple databases.

6.1.7 Stop Main AppServer Use the following instructions to stop the main AppServer. 1. Use the Progress Explorer Tool or OpenEdge Explorer Tool to stop the main AppServer. 2. Minimize the Progress Explorer Tool or OpenEdge Explorer Tool.

32



Post-Installation

6.1.8 Run Conversions Using Epicor Tools Use these steps to run the data initializations (for new installations) or data upgrades (for existing installations) on your Epicor 9.05 application. 1. On the server, run the Epicor Tools program as . To do this, navigate to Start > Programs > Epicor Software > Epicor 9.05, right-click Epicor Tools and select to Run as . 2. with a valid Epicor ID and . Note that the must have Security Manager rights. Click OK. 3. If prompted 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 rules. It is recommended that you take a screen capture of this message to be used later to review the blocked rules.

4. To that the mandatory conversions or initializations 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 programs that were run. If necessary, scroll to the right to see the Date the program was run. Note If you use Extended UD Table functionality, a schema change was run automatically for those extended UD tables.

5. When the processing is completed, close Epicor Tools.

6.1.9 Start Main AppServer Use the following instructions to start the main AppServer. 1. Use the Progress Explorer Tool or OpenEdge Explorer Tool to start the main AppServer. 2. Minimize the Progress Explorer Tool or OpenEdge Explorer Tool. Do not start the other AppServers yet.

6.2 Update Custom Client MFGSYS Files Use the following instructions to update customized .mfgsys files, if you have customized .mfgsys files. 1. Double-click the clientzipinstaller.exe file. The default location is \Epicor\Epicor905\clientzipinstaller. 2. Enter the file path location of the customized .mfgsys file. By default, the deploymentServer path from the default .mfgsys file is used as the location of the client zip file. Enter a specific location if you want to install the client zip file from a different location. 3. You can review changes to the configuration setting files by using the Config file editor. Select the check boxes for the mfgsys files you want to review.


33

Post-Installation


4. Click Finish. The Config file editor appears, prompting you to view changes that in the config settings for each mfgsys file that was checked. You can update the settings as necessary. 5. To accept changes in the Config file editor, click Close. The configuration files are updated so that they are current, ready to accept the service pack.

6.3 Update Credit Card Functionality If you use credit card functionality within the Epicor application, this release includes a PA-DSS validated solution for securing credit card payments. To be able to use this functionality, you must install and configure the ESDM (Epicor Secure Data Manager) program. The installation process includes installing Secure Data Service (SDS), Key Services, and AuthorizationLite Service. Use these steps to the ESDM Installation Guide from EPICweb. 1. Log on to EPICweb and go to the Customer Portal Page. Navigate to > Epicor 9 > s. Note You can use this link: https://epicweb.epicor.com//epicor9/s

2. Navigate to the product version you have installed. For example, navigate to Epicor 9 > Version Epicor 9.05.700. 3. Locate the ESDM folder. Based on your product version, it may be located under the Third Party Products folder. 4. the Epicor Secure Data Manager Installation Guide file onto your local machine. 5. Use that guide to update the credit card functionality. Be sure to also use the Appendix: Configure Epicor or Vantage section to complete the Epicor installation.

6.4 Restart the AppServers Use these steps to restart the AppServers. 1. Use the Progress Explorer Tool or OpenEdge Explorer Tool to stop the AppServer processes in the following order: Epicor905ProcessServer, Epicor905TaskAgent, Epicor905. 2. Use the Progress Explorer Tool or OpenEdge Explorer Tool to start the AppServer processes in the following order: Epicor905, Epicor905TaskAgent, Epicor905ProcessServer. 3. that the AppServer processes are running before starting the client. 4. Exit the Progress Explorer Tool or OpenEdge Explorer Tool.

34



Post-Installation

Chapter 7: Install Epicor 9.05 Client on a Workstation Use the following instructions to install the Epicor 9.05 client on your workstation. New customers or existing customers who are adding a new client workstation should use the following instructions to install the Epicor 9.05 Client. If you are an existing customer and you are not adding a new client, you should use the following instructions to update the version of Crystal Runtime installed on your client workstation. Note The instructions on Crystal 2008 SP3 Runtime installation can also be used on your server or Windows workstation, if you plan to print Crystal Reports forms from your server or Windows workstation.

7.1 Install Epicor 9.05 Client Software Use the following instructions to start the client installation. 1. Make sure you are logged in as the Local on the client workstation. 2. Use Windows Explorer to navigate to the server where Epicor 9.05 is installed. Go to the Epicor905 folder. Double-click to run the Epicor9Client.msi file. 3. The Welcome window appears for installing the client software. Click Next. 4. 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:\Epicor\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. 5. 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. 6. 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. 7. Click Next. 8. The Ready to Install the Application window appears. Click Next. 9. When finished, click Finish to complete. 10. If prompted, reboot the workstation at this time.


35

Post-Installation


7.2 Uninstall Previous Versions of Crystal Runtime Use the following steps to uninstall any previous version of Crystal Runtime. 1. Navigate to Start > Control > Programs > Uninstall a Program. 2. Select Crystal Reports .NET Runtime and click Uninstall. 3. that the uninstallation was completed successfully.

7.3 Install Crystal Reports 2008 Runtime Use the following steps to install Crystal Reports 2008 SP3 Runtime on your client. You can also use these steps to install Crystal Reports 2008 SP3 Runtime on your server or Windows workstation, if you plan to print Crystal Reports forms from your server or Windows workstation. Note You cannot install both Crystal Reports 2008 SP3 Runtime and Crystal Reports 2008 Developer on the same client. 1. If you have a previous version of Crystal Reports .NET Runtime installed on your client, use the following to uninstall the previous version: a. Navigate to Start > Control > Add or Remove Programs. b. Select Crystal Reports .NET Runtime and click Remove. c. the uninstallation was completed successfully. 2. Log on to EPICweb and go to the Customer Portal Page. Navigate to > Epicor 9 > s. Note You can use this link: https://epicweb.epicor.com//epicor9/s

3. Navigate to Epicor 9 > Version 9.05.700 > Third Party Products > Crystal. 4. the latest Crystal 2008 SP3 Runtime file. For example, Crystal_2008_03_Runtime.zip. 5. Navigate to the ed 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. Click Next. 8. Review the license agreement information. Select I accept the License Agreement. Click Next. 9. If prompted, confirm the installation. Click Next. 10. The installation proceeds. When it is finished, click Finish.

36



Post-Installation

Chapter 8: the First Time Use the following steps to and test your Epicor 9.05 application the first time you .

8.1 Import Posting (Booking) Rules If you are installing Epicor 9.05 for the first time, use these steps to import your posting rules for both Standard and Extended Rules. 1. Open the Epicor 9.05 application. 2. Select Financial Management > General Ledger >Setup > GL Transaction Type. 3. From the Actions menu, select Import ACT Type. 4. Click the Input File Name button. Navigate to the necessary folder based on your posting rules type. For example, go to one of the following: • Standard rules: \\<servername>\Epicor905\server\PostingRules\Standard • Extended rules: \\<servername>\Epicor905\server\PostingRules\Extended 5. Select one or more .XML files. You can select multiple files by pressing the Shift key while you highlight the files. Click Open to select the highlighted files. 6. Select the Import All check box to specify that you want to import all the selected XML files. To specify individual XML files instead, you can select the Selected check box for each file. 7. If this is not the first time you are importing posting rule files, you can select the Replace All check box to replace your existing revision with the same name. To specify to replace individual XML files instead, you can select the Replace Existing check box for each file. 8. Select the Change All Revision Statuses To Active check box if you want to change the revision from a draft to active for all transaction types being imported. To specify to activate individual XML files instead, you can select the Activate check box for each file. 9. Select the Import into all companies check box if you want to import the posting rules into each company. Note that newly created revisions are automatically set to Active in all companies. 10. Click OK to begin the import. 11. You may be prompted with the Book Mapping dialog if any imported revisions contain books with IDs that do not exist in the company to which you are importing rules. Do the following and click OK: • Specify the mapping to select which book in the company should receive rules from which book in the import xml file. The import program verifies if the imported rules use segments that don't exist or are defined with a different name in the receiving book's Chart of s (COA). If such segments exist, you must either manually select the correct segment of the receiving COA that should be used or specify that these segments should be assigned new values during the import. • If you want to map the selected book identifier to all transaction types, select the Use for all transaction types check box.


37

Post-Installation


12. Click Save to save your imported financial data. 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.

8.2 Review Blocked Transaction Type Revisions Use the following steps to review GL Transaction Type revisions that were not updated during the conversion, if any exist. Revisions may have been blocked if the conversion process could not merge mandatory changes into custom revisions or could not activate the revision. If you were not prompted with an information message during the conversion, you can skip this step. 1. Get the screen capture of the Information message that you took during the conversion process. 2. Determine what revisions must be manually updated and activated. 3. To manually revise the rules and make the necessary adjustments, go to Financial Management > General Ledger > Setup > GL Transaction Type. 4. In the tree view area, select a revision. Based on the revision, you can do one of the following: • If you want to import the standard posting rules that came with your Epicor application, follow the instructions in the previous "Import Posting (Booking) Rules" section. Apply your customizations to the rules. • If you want to create a new revision, create it based on your custom posting rule and then apply your adjustments to it. Note You can review changes, which conversion applied to the revision, using Action menu > Change Log. You can also use Action menu > Compare Revisions to review differences between revisions.

5. After manually revising the rules, click the Revision tab. For the revision that you changed, use the drop-down menu to select the Active status. 6. Repeat the above step for each Revision listed on the Information message. Note If you have multiple companies, the Information message may list the same blocked transaction type for each company. You must review the blocked posting rules for each company where you have access.

8.3 Maintain Your Customizations and Personalizations Use the following steps to and maintain your customizations and personalizations. Note that the Customization / Personalization Maintenance program attempts to automatically correct any problems that it encounters during the verification process. The verification process checks that each customization includes the following: a valid customization script, valid custom properties, valid control keys, valid controls that are located on the form and properly docked, and -defined controls are added to the form. It also deletes customization properties that are no longer applied, and cleans up the grid layout to remove obsolete fields.

38



Post-Installation

1. Launch your Epicor 9.05 application. 2. Navigate to System Management > Utilities > Customization Maintenance. 3. Click the Search icon (binoculars) from the tool bar. 4. Select Customization as the Type and All as the Status. 5. Click Search. The customizations are displayed. Click Select All and then click OK to select all. 6. Click on the Actions menu. 7. Select the All command. 8. You are warned that this process may take several minutes. Click Yes. 9. The verification process reviews the selected personalizations and customizations. When complete, you are returned to the Customization/Personalization Maintenance window. 10. Select a customization/personalization you want to review. 11. Click the Warnings tab to review any elements that were not validated. Usually warnings are caused by properties stored in the customization data that cannot be applied. Common warnings that you might see include: a. Cannot locate control on form. The key used for the customization is no longer on the form. This could result from a renamed control or changed EpiGuid. b. Could not set the property. No code exists that sets this property. c. EpiBinding is not valid. Identifies the database field that should be used. d. Invalid Parent Type. Custom control was added to an invalid parent. 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 Customization. 17. Click the Detail tab to that the customization has ed validation. If it is valid, the current manufacturing version is Valid For and is the Status. 18. Repeat these instructions and select Personalization as the Type to and maintain your personalizations, if necessary.


39

Post-Installation


8.4 Deploy Dashboards to the Server Use these steps to redeploy your dashboard assemblies that were previously deployed in your Epicor 9.05 application. The dashboard assemblies are deployed to the server. Note For more information on how to build and deploy a dashboard, see the application help or the Epicor ICE 2.5 Tools Guide. 1. Launch your Epicor 9.05 application. 2. Navigate to System Management > Utilities > Dashboard Maintenance. 3. Click the Dashboard ID field and then click Search to display the list of dashboards. 4. In the results list, select all of the dashboards that have the Deployed check box selected. These dashboards were previously deployed. Click OK. 5. From the Actions menu, select Deploy All UI Applications. The selected dashboards are redeployed.

8.5 Test Business Activity Query (BAQ) Calculations During the Epicor 9.05 installation, unused obsolete fields are automatically deleted. Obsolete fields that are used in calculations within BAQ are not deleted, but calculations with obsolete fields no longer work. 1. Review your calculations within any BAQs you want to continue using after upgrading your system. 2. Launch the online help system. 3. Review the Schema Change topic to see which fields have been changed or removed. 4. Change each BAQ calculation so that it uses current fields. After you upgrade, your BAQ reports should work since your fields are valid.

8.6 Test Business Activity Manager (BAM) Upgrades If you use any global alerts that activate procedure (.p) programs, use these steps to compile these programs using the newly installed Progress 10.2A. 1. Review each BAM event that has a procedure program on your system. that it still has a valid business reason for being upgraded to the next version. 2. Add Comments within your procedure program, explaining your changes. 3. Save each BAM event, including the procedure files, in an archive location. 4. Move these BAM events and their procedure files to a new location. 5. If any schema changes affect the procedure program, update the .p program to reflect the new schema. 6. Compile each procedure program using Progress 10.2A. 7. Test each procedure program for issues.

40



Post-Installation

8.7 Update and Test Business Process Management (BPM) Directives Use these instructions to update your outdated BPM directives after upgrading and to identify any that need special attention due to schema changes or other factors. Note You must use these steps to properly upgrade your BPM directives. You cannot just copy the BPM directives in the Epicor905\BPM\bo directory to another directory. You also cannot keep the BPM directives in the current folder, they must be properly upgraded to a new location. 1. Navigate to System Management > Business Process Management > General Operations > Directive Update. 2. From the Actions menu, select Recompile All Outdated Directives. As the directives are converted and re-compiled, an hour glass is displayed. 3. Upon completion, the compile results are displayed. Any Method Directives that failed to compile after the conversion are listed. 4. Navigate to System Management > Business Process Management > Setup > Method Directives. 5. Use the Method Directives program to search for any Outdated Directives. 6. Open an outdated directive. 7. Click on the Actions menu and select Validate Method. 8. If a directive is outdated, the Pre-Processing, Base Processing and/or Post Processing sheets display the Outdated icon on each directive's Detail sheet. Research how to update each outdated directive to make it compatible with Epicor 9.05. This may involve updating your custom 4GL code to reflect the new schema. 9. Repeat these steps for all the outdated directives that you find.

8.8 Test Custom Code Programs Use these steps to test any custom code programs that were created and updated for you by the Epicor Custom Solutions Group. 1. Test your custom code programs. 2. the Epicor Custom Solutions Group if you need other custom code upgraded. Note that the Epicor Custom Solutions Group requires time to review, estimate, schedule, and complete your custom solutions.

8.9 Test System and Repeat Installation Based on your installation process, you are at one of the following points: • If you completed the Epicor 9.05 installation in a test environment, you are now ready to test the installed Epicor 9.05 application in that environment. After your testing is complete, you must repeat the entire installation in your production environment. • If you completed the Epicor 9.05 installation in your production environment, you are now ready to use the installed Epicor 9.05 application in that environment.


41

Post-Installation


Chapter 9: Restore Demonstration Database Use the following instructions to restore the Epicor 9.05 Demonstration Database, if desired. The Epicor 9.05 Demonstration Database is released with every Service Pack and is used with the Embedded Education Courses. Note that the Demonstration Database as delivered by Epicor must be used only with the Epicor application version for which it was released.

9.1 Demonstration Database File Use the following instructions to the appropriate Demonstration Database file based on your database platform. Each *.zip file includes a copy of the Demonstration Database that can be restored to replace the existing Demonstration Database. 1. Log on to EPICweb and go to the Customer Portal Page. Navigate to > Epicor 9 > s. You can click this link: https://epicweb.epicor.com//epicor9/s 2. Navigate to Epicor 9 > Version 9.05.700 > Demonstration Database. 3. the latest Epicor 9.05 Demonstration Database related to this installation. For example, the necessary files, based on your environment: • SQL (32): Epicor9_Database_90570x_Win32SQL.zip • SQL (64): Epicor9_Database_90570x_Win64SQL.zip • SQL Unicode (32): Epicor9_Database_90570x_Win32SqlUnicode.zip • SQL Unicode (64): Epicor9_Database_90570x_Win64SqlUnicode.zip

9.2 Prerequisites Use the following instructions to the prerequisite steps have been completed. 1. All Appservers and OpenEdge Databases are stopped. 2. Epicor 9.05 Service Pack or Patch has been installed, if available. 3. Epicor 9.05 Post-Installation steps have been completed.

9.3 Restore the Demonstration Database Use the following instructions to restore the Demonstration Database using SQL Server. These instructions assume you have an EpicorTrain905 database in SQL Server 2008 R2. 1. Go to the location where you ed the zipped files. 2. Open the .zip file. For example, open Epicor9_Database_90570x_WinxxSQLx.zip file. Extract the Epicor9_Database_WinxxSQLx.BAK file directly into the C:\Epicor\Epicor905\db\Training folder. 3. Navigate to Start > All Programs > OpenEdge 10.2A, right-click ProEnv and select Run as from the menu. A DOS window opens.

42



Post-Installation

4. At the proenv> prompt, type: Prompt and press Enter. 5. Type: cd\ and press Enter. 6. At the c:\> prompt, type: cd \Epicor\Epicor905\db\Training and press Enter. 7. At the C:\Epicor\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:\Epicor\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, 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. In the Restore column, select the check box for the backup you are installing. 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. 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. A dialog box is displayed indicating the database restoration is complete. Click OK.


43

Post-Installation


24. Exit SQL Server Management Studio.

9.4 Start Main AppServer Use the following instructions to start the main AppServer. 1. Use the Progress Explorer Tool or OpenEdge Explorer Tool to start the main AppServer. For example, EpicorTrain905. 2. Minimize the Progress Explorer Tool or OpenEdge Explorer Tool. Do not start the other AppServers yet.

9.5 Import License Codes and Enable Modules Use the following instructions to import the product license codes and enable the modules. 1. Open the Epicor istration Console. To do this, navigate to Start > All Programs > Epicor Software > Epicor istrative Tools > Epicor istration Console. 2. with a valid ID and . Note that the must have Security Manager rights. For example, as epicor / epicor. 3. Connect to the location of your training environment, such as EpicorTrain905. 4. Specify the imported license file for each company. To do this: a. Select the Companies node. In the Companies column, right-click on your specific company, such as Epic01, and select Properties. b. Click the browse (...) button to search and select your serial number from the list of Available Serial Numbers. Click OK. c. Repeat to for each of the other companies, such as Epic02 and Epic03. 5. Enable the modules attached to the imported licenses. To do this: a. From the list, select Licensing. b. Right-click on the license serial number and select Properties. c. Click the Modules tab. d. Select the individual modules to activate, or click the Enable all Licensed button to select all the modules. The Enabled check box should be selected for the modules you want to activate. e. Click OK. 6. When finished, exit the Epicor istration Console.

44



Post-Installation

9.6 Run Manual Conversion Use the following instructions to run the required manual conversion to reset the sequence table. Your main appserver must be stopped prior to running the conversions, and then restarted after the conversion has finished. 1. If your main appserver is started, you must stop it prior to running the conversions. For example, use the Progress Explorer Tool to stop the EpicorTrain905 appserver. 2. Open the Epicor Tools program. To do this, navigate to Start > Programs > Epicor Software > Epicor 9.05 > Epicor Tools. 3. with a valid ID and . Note that the must have Security Manager rights. For example, as epicor / epicor. 4. Select Run Database Conversion. 5. Scroll down the list of programs to number 5460 called Re-set DB Sequences. Highlight the program to select it. 6. From the Conversion menu, select Run Conversion Program. Click Yes to confirm. 7. After the conversion finishes, exit Epicor Tools. 8. Start your main appserver. For example, use the Progress Explorer Tool to start the EpicorTrain905 appserver.

9.7 Set Up System Agent for Printing (Demo Database) Use the following instructions to set up your system agent. The paths for the System Agent, which control report printing, must be reset after a database restore. These instructions assume your database is set to be the Mfgsys database directly located in this folder: C:\Programs Files\Epicor Software\Epicor905\db\Training. 1. Review the paths you specified during the server software installation for the following locations: • Destination Location • Print Folder Destination Location • Server Share Location 2. Launch your Epicor 9.05 application. 3. Navigate to System Management > Utilities > System Agent. 4. Click Agent ID to search for the system agent identifier. 5. The identifiers are listed. Select SystemTaskAgent. Click OK. 6. In the Task AppServer section, change the AppServer URL to AppServerDC://localhost:9413. 7. In the System AppServer section, change the AppServer URL to AppServerDC://localhost:9411. 8. The name defaults to print. Enter the as print.


45

Post-Installation


9. In the SystemAppServer section, enter your directory paths. For example: Directory

Description

Examples

Server File

specifies the local path on the server to the c:\Epicor\EpicorData print directory usr/epicor/epicordata

Client File

specifies the unc path to the print directory \\<servername>\EpicorData

Client Program

specifies the unc path to the server directory \\<servername>\Epicor905\Server

10. Save the System Agent changes. Exit System Agent Maintenance. 11. Close the Epicor 9.05 application.

9.8 Start Remaining Appservers Use the following instructions to start the remaining Appservers. 1. Open the Progress Explorer Tool or OpenEdge Explorer Tool. Start the Appservers in the following order: • EpicorTrain905TaskAgent • EpicorTrain905ProcessServer 2. Exit the Progress Explorer Tool or OpenEdge Explorer Tool.

9.9 Test Demonstration Database Update Use the following instructions to that the Demonstration Database was properly updated. 1. Open the Epicor 9.05 application. 2. using a valid ID and . For example, as epicor / epicor. 3. From the Help menu, select About Epicor 9. 4. that the version has changed to the correct version you installed.

46



Post-Installation

Chapter 10: Configure Windows Workstation Use these optional steps to configure a Windows Workstation, if one is needed. These steps can be run on a client or server machine, but they cannot be run on a server that has a 64-bit version of OpenEdge installed. The 32-bit and 64-bit OpenEdge Software cannot be located on the same machine. Note For a Windows install, this is an optional step if you want to configure a super-client workstation.

10.1 Install ODBC Driver (Native Client 10) If you use SQL, use these steps to and install the 32-bit Native Client 10 ODBC driver. Note The Native Client 10 ODBC driver is required if you are installing the Tools and Schema Change shortcuts from the client workstation onto a Client Server machine. The installation of this ODBC driver is required for the client to communicate with the database. 1. Go to the Microsoft Center website to the 32-bit SQL Native Client 10. The 32-bit SQL Native Client is in a Feature Pack for Microsoft SQL Server 2008. The link is: http://www.microsoft.com/do wnloads/details.aspx?FamilyId=C6C3E9EF-BA29-4A43-8D69-A2BED18FE73C&displaylang=en 2. In the Feature Pack for Microsoft SQL Server 2008, scroll to the link for Microsoft 32-bit SQL Server Native Client. the 32-bit SQL Native Client 10. 3. Install the 32-bit SQL Native Client 10. that it is installed correctly.

10.2 Install Progress OpenEdge 1. that your machine does not have a 64-bit version of OpenEdge installed. 2. Install the 32-bit version of Progress OpenEdge 10.2.A. See the Install Progress OpenEdge 10.2A section of this document for instructions. Note The OpenEdge 10.2A Service Pack and Service Pack Hot Fix are also installed.

10.3 Install Epicor 9.05 Client 1. Install the Epicor 9.05 Client. See the Install the Epicor 9.05 Client section of this document for instructions. You must complete all the steps in that section. Note During the installation, if this Windows Workstation machine is where you plan to run the Epicor Tools and Epicor Schema Changes, be sure to select the following check boxes to create the shortcuts: Epicor Tools and Epicor Schema Change. Note During the installation, if this Windows 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.


47

Post-Installation


Chapter 11: Troubleshooting Use the following section if you need assistance in troubleshooting any installation issues.

11.1 Share the Epicor Folders Use the following steps to share the Epicor folders. Note that if you are using Windows Server 2008, the steps may be slightly different. 1. On the C: drive, create the C:\Epicor\Epicor905 folder if it does not already exist. a. Right-click on the \Epicor\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. 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 s. Read-only includes Read & Execute, List Folder Contents, and Read. Add an and assign the Full Control. Click OK. 2. On the C: drive, create the C:\Epicor\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 Permissions. It is recommended that you assign Full Control to each folder. Click OK. d. Click OK to accept the share options.

11.2 Specific Folders are Not Read-Only Use these steps to 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 \Epicor\Epicor905. 2. Right-click on the Client folder. Select Properties. 3. On the General tab, unselect the Read Only check box. Click Apply. 4. The Confirm Attribute Changes dialog appears. The Apply changes to this folder, subfolders and files option is selected by default. Click OK. Click OK to exit the Client Properties folder. 5. Repeat the previous steps for the ClientServer and Server folders. Note For 64-bit installations, the ClientServer folder is located in the \Epicor\Epicor905\32 directory.

48



Post-Installation

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

Purpose and Expected Value

Application Settings AppServerURL

The address of the appserver where the client connects protocol://server:port; it uses the form value "AppServerDC://servername:port"Protocol: AppServerDC by default, or else AppServer for load balancing.Server: Host name of the machine that runs AppServer.Port: The port of the broker that runs the software. Default is 8301. Also, AppServer accepts strings and numbers, but the port value only accepts numbers.

CultureCode value

The ISO language code for the software installation. This will be the language used on the overall system or the specific client machine. For example "enu" (English language)

ResourceFile

A path name to the resource file. This file contains images and other resources that can be changed by partners for branding purposes; for example "C:\mfgsys\client\res\MfgBaseImages.resources"

ToolbarSettings

The path and XML file that defines the s' default settings for the toolbar functionality. For example, ".\res\ToolbarSettings.xml"

ProductID value

The product identifier; for example "Epicor"

Version value

The current release and patch number for the application; for example "9.05.500"

EnterpriseProcessing

Whether multiple concurrent sessions are allowed on the workstation. The choices are true or false (the default).

SmtpServer

The SMTP server that will be used to send e-mail.

ProductBrandText value

The text that appears with the desktop icon

ProductBrandIcon value

The icon for the application that appears on the desktop

ProductLogonImage value

The bitmap file that is double-clicked to to the system

SplashImage

The splash screen image when you first

HelpAboutImage value

The bitmap file for the Help About window

Settings <Setting> ID value


The ID for auto-; for example, "BobJones"

49

Post-Installation


XML Tag


value

The for auto-; for example, "BobJ"

DataCollection value

Defines whether or not this is a data collection ; these s only have access to Data Collection functionality. Only two values can be used - "true" or "false"

StartSystemMonitor value

Defines whether or not the System Monitor will start when the application is launched. Only two values can be used - "true" or "false"

LastID value

The most recent identifier that was used to access the application; for example"BobJones"

Default value

The default setting that defines what appears in the Name field. Four values are possible:"Last" - Displays the last ID that was used"List" - Displays a list of all the recently entered identifiers"Windows" - Displays the same ID used to log onto Windows on this client machine"None" No default value; the Name field will be blank

FormOpenMode value

The mode by which each form within the application will launch. Three values are possible:"AutoSearch" - Each form automatically displays its search program. For example, the Sales Order Entry program will automatically launch with its Sales Order Search program ready for input"AutoPopulate" - Each form automatically displays data from the first record linked to the form"Blank" - Each form loads without a special mode; all the fields are empty

DefaultSearchFormLocation

The area on your screen where all Search forms will appear by default:"top" - All Search forms will automatically display in the top center of your screen"center" - All Search forms will automatically display in the middle of your screen

SingleSignOn value

The choices are true or false (the default). A value of true means that single sign-on logic should be used. No prompt for ID and , should appear, but instead the ID of the current Windows should be used.

Deployment Settings <deploymentSettings> DeploymentServer

The URI of the deployment directory on the deployment server.

deploymentType value

The method the deployment system uses to deploy client assemblies. The only accepted values are xcopy (the default) and zip (which copies a named zip file locally and then unzips).

deploymentPackage value

If the deploymentType is of type zip, the name of the zip file. The default is ReleaseClient.zip.

optimizeAssemblies value

The choices are true or false. A setting of true requires the to have rights on the machine.

doDateComparison

If deploymentType is set to xcopy, this setting determines whether the xcopy runs and does a date comparison with the /D switch, or s 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 HelpServerURL

50

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.



XML Tag

Post-Installation


Epicor on the Web <epicorOnTheWebSettings> CustomerCenter product

The product and URL used when the accesses the Customer Center; for example "Epicor" followed by the URL href = "https://epicweb.epicor.com/Vantage/default.aspx"

Online product

The product and URL used when the accesses online (ePortal) ; for example "Epicor" followed by the URL href = "https://eportal.epicor.com"

11.4 Time Synchronization on Client and Server If you received the error message "The authorization credential is expired", use these steps to the time synchronization of your client and server. You may receive this error while performing a search from a client workstation to the Epicor Web Access server if the time values that are set on the client and server are not accurate according to the time zone. 1. On the client workstation, go to Start > Control > Date and Time. that the time is accurate according to the time zone. 2. On the Epicor Web Access server, go to Start > Control > Date and Time. that the time is accurate according to the time zone.

11.5 Known Issue with Turkish Format Culture Display When the Format Culture is set to Turkish, several items display incorrectly and you may get an unhandled exception error that causes the application to become unstable. To resolve the unhandled exception error, you can set the Format Culture to German in order to use the formats for that language instead. To do this: 1. Open your Epicor 9.05 application. Navigate to System Management > Company Maintenance > . 2. Enter or browse for a specific . 3. In the Format Culture field, select German. Keep the Language set to Turkish. 4. Save the record. Close the application. Note While this change resolves most of the issues, it also causes a minor issue with a Crystal Reports tool bar that cannot be resolved. The reports are now formatted and displayed correctly in Turkish culture, but the issue may appear in the report tool bar where several icons and text are displayed in German.

11.6 Configure Environments for Test and Pilot During the installation of Epicor 9.05, the only two environments completely configured by the installation are under ports 9401 and 9411 for your main production and Train environments. Use the following steps if you want to configure additional environments, such as Test and Pilot. The Pilot and Test environments are installed (including the .ini files, .pf files, and shortcuts), but the schema (for SQL installations) and databases are not restored. Note that these steps are different for Progress and SQL environments.


51

Post-Installation


1. Copy the files from Epicor905\db\newdb\backup to Epicor905\db\pilot and Epicor905\db\newdb\test. Note that an empty attachable SQL database or new SQL script database can be found in the same directory as the schema. 2. Restore the schema. 3. Restore Schema holder. To do this, go to \db\newdb\backup. Based on your operating system, use one of the following files: • mfgsyssh64u.bkup • mfgsyssh64.bkup • mfgsyssh32u.bkup • mfgsyssh32.bkup 4. Start your Application Server. 5. Restore SQL database. The SQL Script used to create an empty database is located in \db\newdb\backup. The SQL script name to create empty database name may vary based on which Epicor 9.05 version is being installed. 6. Create ODBC connections or they exist for EpicorPilot905 and EpicorTest905. 7. Start Schema database holder. 8. Run Schema Change tool to update the empty database and to the empty database is at the correct version. 9. Run Tools. form appears. 10. Start your Application Server. 11. to the istration console. a. Create Environment connection. For example, create EpicorPilot905 or EpicorTest905 b. Apply the license. c. Create your company. 12. Run Tools to update the empty database with beginning data. 13. to your Epicor application.

11.7 Progress Client Has Stopped Working During an Epicor 9.05.700, if you receive the error message that your "Progress client has stopped working", you must use the OpenEdge Explorer tool to stop your database. You received this error because the database is marked as Read-Only, but the database is running.

52



Post-Installation

11.8 Change or Uninstall Epicor 9.05 Application Use these steps to add or remove programs and features related to your Epicor 9.05 application. This section also includes steps to uninstall the Epicor 9.05 application from your server or Epicor 9.05 client from your workstation. Note It is highly recommended that you create a backup of all your important files, such as your databases, prior to uninstalling the application.

11.8.1 Add or Remove Programs and Features Use these instructions if you want to add or remove programs or features that are related to your Epicor 9.05 application. 1. Navigate to Control > Programs and Features.. 2. Right-click on Epicor 9.05 (database) and select Change from the menu. The Install Wizard opens the Epicor 9.05 installation menu. The dialog may look similar to the following:

3. The Add / Remove Features option is selected by default. Click Next. 4. On the Select Features dialog, select the features you want to add or remove. Click Next. The Epicor 9.05 features you selected are added or removed. Note When adding features, the components for the Utilities, Server Add-On, and Web Add-On features are delivered as executable files to a folder on your server. The components are delivered, but they are not installed. After your installation, you can use the Supplemental Installation section of this guide for instructions on installing these additional features and programs.


53

Post-Installation


5. If prompted, click Finish.

11.8.2 Repair or Reinstall Epicor 9.05 Application The Epicor 9.05 installation menu includes an option to Repair / Reinstall the Epicor 9.05 application. While this is a standard option available in an install wizard process, it is not recommended that you use this option with your Epicor 9.05 application due to customizations or configuration settings unique to your system.

11.8.3 Uninstall Epicor 9.05 Application Use these instructions if you need to uninstall the Epicor 9.05 application from your server. It is highly recommended that you create a backup of all your important files, such as your databases, prior to uninstalling the application. 1. Create a backup of your databases. For example, go to the \Epicor905\DB folder and create a backup of your database files. 2. Navigate to Control > Programs and Features. 3. Right-click on Epicor 9.05 (database) and select Uninstall from the menu. The dialog may look similar to the following:

4. The Uninstall Epicor 9.05 option is selected by default. Click Next. 5. On the Ready to Update Your System dialog, click Next. The Epicor 9.05 application is uninstalled. 6. If prompted, click Finish.

54



Post-Installation

7. The uninstall process may not delete files that were added or updated since the initial installation. To complete the uninstall process, go to the location where you initially installed the Epicor application. For example, go to \Epicor\Epicor905. Manually delete any existing files and folders.

11.8.4 Uninstall Epicor 9.05 Client Use these instructions if you need to uninstall the Epicor 9.05 client from your workstation. 1. Navigate to Control > Programs and Features. 2. Right-click on Epicor 9.05 Client and select Uninstall from the menu. 3. In the Previous Install dialog, the Update or Uninstall a single instance option is selected by default. Use the drop-down menu to select the instance. Click Next. 4. On the Shortcut Creation dialog, select the Uninstall this client check box. Click Next. 5. On the Confirmation dialog, click Yes. The Epicor 9.05 client is uninstalled. 6. When it is completed, click Finish. 7. The client uninstall process may not delete all the files that were added or updated since the initial installation. To complete the uninstall process, go to the location where you initially installed the Epicor client. For example, go to \Epicor905\Client. Manually delete any existing files and folders.


55

Supplemental Installations


Part IV: Supplemental Installations Use the following information to help complete your Epicor 9.05 application set up. Complete the sections appropriate for the components and products you intend to use.

1.

Log on to EPICweb and go to the Customer Portal Page. Navigate to > Epicor 9 > s. Navigate to Epicor 9 > Version 9.05.700.

2.

In the Available s list, the Supplemental Installation Guide. Note that this guide is the same for all platforms.

3.

Use the Supplemental Installation Guide to install the components and products you intend to use with your Epicor 9.05 application. Note If you are installing a patch your Epicor 9.05 application, use the Release Notes document to review the list of supplemental installations that must be upgraded.

Supplemental installations can include the following: • Configure 64-Bit Environment (Windows 2008) • Install Epicor istration Console • Install BPM Server • Install Epicor Enterprise Search • Install Embedded Education Courses • Install Epicor Information Worker • Install Epicor DB Replication • Install Epicor SQL Server Reporting (SSRS) • Install Epicor Mobile Access • Install Epicor Sharepoint Publisher • Install and Deploy Epicor Web Access • Reinstall Epicor Web Services • Service Connect 9.05 • Epicor Portal 9.05 • Infragistics NetAdvantage • Install SonicMQ • Install Progress OpenEdge 10.2A (Advanced/Manual) • Configure Epicor Online Help • Set Up Multi-Company Functionality

56


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 . To create an , go to http://.epicor.com.

Epicor905 Spguide 905700 Sql 3g1r2o

Overview 26281t

More details 6y5l6z

Related Documents 3h463d

Epicor905 Spguide 905700 Sql 3g1r2o

Sql 4p3c4t

Sql 4p3c4t

Sql 4p3c4t

Sql Server T-sql Cheatsheet 35666y

Advanced Sql And Pl-sql 451wq

More Documents from "Victor Motolinia" 634y1p

Epicor905 Spguide 905700 Sql 3g1r2o

Adult-mind-series-2nd-edition-brochure-2016.pdf 2d6560

Tyler Joseph Drown 4k2e

Finkok Alta Produccion 2i2t1z

Have You Ever Seen The Rain.pdf 6q6e1s

4p345f