The system administrator should follow these general patch installation guidelines. Any patch may have specific requirements so all patch documentation should be read and understood before attempting to install.
1. Review all patch installation instructions. Carry out any pre-installation instructions if any. Also, review any source code modifications that may need to be reintegrated. If you have any custom modifications, you should also run the Test of Patch function.
2. Patches may be delivered in a patch set which may contain many patch files or may be delivered individually. Patches may come zipped or unzipped but regardless of how they are delivered, the patches must be made available on the Application server. Patch files have either a “.dat” extension or no extension. You will need to locate the file or directory containing the patch files.
3. Create a temporary folder on the server. Unzip or simply move the patch files to this new temporary folder.
4. Logon to the Folder with the admin username. Run the Patch integration function (PATCH) under Patches in the Development > Utilities block under.
5. To install a patch once all information has been entered, click OK. To exit without installing the patch, click Close page.
6. When the patching process completes, review the displayed trace file. Be sure to review all pages, using the arrows if necessary. If a problem was encountered during the patch installation, an error message will be written to the trace file.
7. Review patch installation instructions again and carry out any after installation instructions if they exist.
8. Integrate any modifications made to the files contained in the TRT_Change directory. See the above section Code Review for more details.
There are two methods for validating a transaction either individually or as a group.
Occasionally, a patch may require that menus be validated. To validate a menu, run the Menus function (VALMENU) under Dictionary > Validations in the Development > Utilities block. In the Menu profile field, enter the menu name to be validated and click OK.
1. Review all patch installation instructions. Carry out any pre-installation instructions if any. Also, review any source code modifications that may need to be reintegrated. If you have any custom modifications, you should also run the Test of Patch function.
2. Patches may be delivered in a patch set which may contain many patch files or may be delivered individually. Patches may come zipped or unzipped but regardless of how they are delivered, the patches must be made available on the Application server. Patch files have either a “.dat” extension or no extension. You will need to locate the file or directory containing the patch files.
3. Create a temporary folder on the server. Unzip or simply move the patch files to this new temporary folder.
4. Logon to the Folder with the admin username. Run the Patch integration function (PATCH) under Patches in the Development > Utilities block under.
- In the Patch directory field, enter the full path and folder name or file name. By specifying a folder, all patch files contained in the folder are installed. Again, all patch files have a ‘.dat’ extension or no extension.
- When using the selection icon, you can select the file using either the built in Patch volume or you must have the directory you defined as a volume in the Volumes function in the Administration > Collaboration block.
- Check both the Patch integration and Comment overwrite checkboxes.
- In the FOLDERS section, delete any folders that you wish to exclude from receiving the patches. Normally you will either want to apply the patch to all folders or to a single folder that has been set up as a Test folder.
5. To install a patch once all information has been entered, click OK. To exit without installing the patch, click Close page.
6. When the patching process completes, review the displayed trace file. Be sure to review all pages, using the arrows if necessary. If a problem was encountered during the patch installation, an error message will be written to the trace file.
7. Review patch installation instructions again and carry out any after installation instructions if they exist.
- After installation, instructions usually ask that one or more X3 transaction types be revalidated.
- Time saving tip: If you are installing more than one patch or patchset, note all the transactions that need to be revalidated and revalidate the noted transactions after all patches have been installed.
8. Integrate any modifications made to the files contained in the TRT_Change directory. See the above section Code Review for more details.
Transaction validation
There are two methods for validating a transaction either individually or as a group.
- Individual validation – to validate a transaction individually you would go to the specific transaction type maintenance function, select a specific transaction and then click Validation.
- Group validation – To validate all transactions of a particular type or all transactions of multiple types you can run the Transaction generation function (GENMSKTRT) under Dictionary in the Development > Utilities block.
- For each module you wish to have its transactions generated, select Yes in the Validation column. Set to No for the modules you do not wish to have transactions generated.
Menu validation
Occasionally, a patch may require that menus be validated. To validate a menu, run the Menus function (VALMENU) under Dictionary > Validations in the Development > Utilities block. In the Menu profile field, enter the menu name to be validated and click OK.
-
Sage X3 and Sage Software are trademarks of Sage Software, Inc. Microsoft SQL Server, Microsoft SQL Enterprise Manager and SQL Server Management Studio are registered trademarks of Microsoft Corporation. Oracle is is a registered trademark or Oracle Corporation. All other product names used here are trademarks or registered trademarks of their respective owners.
Sage X3 and Sage Software are trademarks of Sage Software, Inc. Microsoft SQL Server, Microsoft SQL Enterprise Manager and SQL Server Management Studio are registered trademarks of Microsoft Corporation. Oracle is is a registered trademark or Oracle Corporation. All other product names used here are trademarks or registered trademarks of their respective owners.
-
