Escolar Documentos
Profissional Documentos
Cultura Documentos
Contents
This part of the guide explains how to verify the prerequisites prior to installing or upgrading your Epicor 9.05 installation.
1. Log on to EPICweb and go to the Customer Portal Page. Navigate to Support > Epicor 9 > Downloads.
Note You can use this link: https://epicweb.epicor.com/Support/epicor9/Downloads
3. In the Available Downloads list, locate and download the 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.
Your Epicor application version must be at the 9.05.700 service pack version in order to install this patch upgrade.
If you have not already done so, use the Epicor 9.05 Installation Guide for 9.05.700 to upgrade to this version.
It is strongly recommended that you set up a separate test environment prior to installing a new Epicor 9.05
application or upgrading from an existing Epicor version. You can use this test environment to test the new
application or to test your current system files, such as custom tools. Prior to upgrading, custom tools such as
personalizations, customizations, global alerts, Business Activity Queries (BAQs), Business Activity Manager (BAM)
events and Business Process Management (BPM) methods need to be tested and maintained prior to upgrading.
By using a separate testing environment, you will know what changes you have to make to your live system after
the upgrade, which helps ensure a successful upgrade.
Important Do not upgrade to Epicor 9.05 without first testing the installation in a separate test
environment.
1. Go to your system Temp folder. The location of the Temp folder differs based on your operating system.
To find the location of this folder, you can do one of the following:
• Select Start > Run. In the command window, type: %temp%. Click OK. The Temp folder location
opens in a browser. For example, the browser could open to C:\Users\[UserId]\AppData\Local\Temp.
• Select Start and right-click on Computer. Select Properties. Click the Advanced System Settings link
or the Advanced tab. Click Environmental Variables. In the User variables section, record the value
for the Temp variable.
Create the following back ups prior to continuing with your installation.
Database and system backups are very important. Do not skip this step.
2. Create a backup of your manufacturing software. In a standard installation, the files are located in the
\oe10xx and \epicor directories.
3. Verify that your backups are valid and can be restored if needed. To test that your backup is valid, restore
your backup to a test area, not your production area.
If you are using customized Crystal Reports, the report files must be backed up. These backups are very important.
Do not skip this step.
2. Save the reports as file names different from the standard report names.
2. Create a backup of all the .mfgsys files. For example, back up the default, train, test, and pilot files.
At the end of the service pack installation, the ClientZipInstaller program will automatically run and replace any
client-side .mfgsys files, such as default, train, and test with the .mfgsys files that currently reside on the server.
The program unpacks the client files, updates the current mfgsys files and then repackages the zip file with the
updated mfgsys files. This ensures that the mfgsys files are ready for the service pack installation. After the
installation, you can run the ClientZipInstaller program anytime you need it.
Use these steps to install the latest updates on your server. Updates can include Epicor 9.05 service packs, patches,
and help system patches.
In these instructions, drive C: refers to a local hard drive. If your local hard drive is assigned to a different letter, substitute
that letter during these instructions. Some of the instructions are based on using Windows Server 2008. If you use a
different operating system you may need to make slight adjustments to the instructions.
Use these steps to download the latest patch files that will be installed later in the installation process.
1. Log on to EPICweb and go to the Customer Portal Page. Navigate to Support > Epicor 9 > Downloads.
Note You can use this link:https://epicweb.epicor.com/Support/epicor9/Downloads
3. 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: PA90570xx-S.EXE
• SQL Unicode: PA90570xx-SU.EXE
Note Be sure to also download the Release Notes document for this specific release. The Release
Notes for a patch is called Epicor905_ReleaseNotes_90570xx.pdf.
Use these instructions to install the Epicor 9.05 patch on the server, if a patch is available.
2. Double-click on the file to run it. The InstallAware wizard verifies that the setup package content is compatible
with your environment and prepares for your installation. This may take several minutes.
4. Enter the directory where your Epicor program files are located. Click Next.
5. You may be prompted to verify your server name, operating system or database type. If prompted, select
the appropriate option and click Next. Note that this prompt is only displayed if your mfgsys.ver file is
incomplete.
7. A message appears, stating that the application patch installation is complete. Click Finished.
Use the following instructions to prepare your database prior to logging in the first time.
Use these instructions to initialize (for new installations) or convert (for existing installations) your database for
compatibility with the Epicor 9.05 application.
1. Verify that you have SQL and Progress installed on any machine where Epicor Admin Tools is installed.
2. Verify that the following steps are completed on the same server as where your SQL database is located.
3. Use the Progress Explorer Tool or OpenEdge Explorer Tool to verify that your Appservers are not running.
Your Appservers cannot be running when you run schema changes or conversions.
4. Use the Progress Explorer Tool or OpenEdge Explorer Tool to verify that your database is running. Your
database must be running in order to run schema changes or conversions.
5. Verify you created a backup of your database as a step in the Getting Started > Verify Prerequisites section.
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 Admin Tools program as Administrator. To do this, navigate to Start >
Programs > Epicor Software > Epicor 9.05, right-click Epicor Admin Tools and select to Run as
Administrator.
2. Login with a valid Epicor User ID and Password. Note that the user 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 verify that the mandatory conversions or initializations completed successfully, make sure the database
conversion date is the correct date. To do this:
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.
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.
Use the following instructions to update customized .mfgsys files, if you have customized .mfgsys files.
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.
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.
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 download the ESDM Installation Guide from EPICweb.
1. Log on to EPICweb and go to the Customer Portal Page. Navigate to Support > Epicor 9 > Downloads.
Note You can use this link: https://epicweb.epicor.com/Support/epicor9/Downloads
2. Navigate to 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. Download 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.
1. Use the Progress Explorer Tool or OpenEdge Explorer Tool to restart the AppServer processes in the following
order: Epicor905, Epicor905TaskAgent, Epicor905ProcessServer.
2. Verify that the AppServer processes are running before starting the client.
Use the following steps to verify and test your Epicor 9.05 application the first time you log in.
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.
2. Select Financial Management > General Ledger >Setup > GL Transaction 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.
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 Accounts (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.
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.
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.
Use the following steps to verify and maintain your customizations and personalizations. Note that the
Customization / Personalization Maintenance program attempts to automatically correct any problems that it
encounters during the verification process.
The verification process checks that each customization includes the following: a valid customization script, valid
custom properties, valid control keys, valid controls that are located on the form and properly docked, and
user-defined controls are added to the form. It also deletes customization properties that are no longer applied,
and cleans up the grid layout to remove obsolete fields.
5. Click Search. The customizations are displayed. Click Select All and then click OK to select all.
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.
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.
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.
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 User Guide.
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.
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.
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.
Use these steps to test any custom code programs that were created and updated for you by the Epicor Custom
Solutions Group.
2. Contact the Epicor Custom Solutions Group if you need other custom code upgraded. Note that the Epicor
Custom Solutions Group requires time to review, estimate, schedule, and complete your custom solutions.
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.
1. Log on to EPICweb and go to the Customer Portal Page. Navigate to Support > Epicor 9 > Downloads.
Navigate to Epicor 9 > Version 9.05.700.
2. In the Available Downloads list, download 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 upgrade to your Epicor 9.05 application, use the Release Notes
document to review the list of supplemental installations that must be upgraded.