Você está na página 1de 3

Infor10 Financials Business (SunSystems)

SunSystems v6.1 Patch Set Installation Note SQL Server


The patching mechanism used in all previous versions of SunSystems is no longer applicable to
SunSystems v6.1. Do not attempt to use any previous version of patch tools delivered with earlier products
against this version.

Prerequisites
Patch Sets require an existing installation of Infor10 Financials Business (SunSystems) v6.1.
The patches delivered via the Windows Installer mechanism (that is, using the .msp files) are cumulative
and therefore can be installed on top of base 6.1 or any intermediate patch set level.
Note: Ensure that all users are logged out of SunSystems while you apply the patch set.

Changes to the Installation Mechanism for PS11 Onwards


The .cab file provided in this patch set consist of cumulative .cab files that contain all previous .cab files
as well as the current one. Therefore, when applying patches to the database tier, the only .cab file you
require is the current one. This can be used to bring any previous installation of SunSystems v6.1 up to the
current patch set level. This rolled-up format is intended to be the norm for all future patch sets, excluding
emergency patches.

Updating a SunSystems v6.1 Installation


For SunSystems v6.1, the SunSystems patch consists of two independent Windows Installer packages. The
first controls the SunSystems Client, Security and Application Server elements, the second controls the
SunSystems Reporting elements. Therefore patches consist of a patch file (.msp) that services the former,
and another .msp file that services the latter. In addition, the database tier must be patched, which is
controlled by the DB Deployer and its corresponding cabinet file.
For example:
For the SunSystems Client and Application tiers (including SunSystems Security) this patch set is
delivered as a Windows Installer patch file (.msp) for example, V61Patchset018-SQL.msp

SunSystems v6.1 Patch Set Installation Note SQL Server


For the SunSystems Reporting tiers, this patch set is delivered as a Windows Installer patch file (.msp)
for example, V61Patchset018-SRS.msp
For the Database tier, a cabinet file is provided which is applied to your databases using the DB
Deployer tool.

Updating a Database Tier


Note: If you run the DBDeployer.exe interactively, your user Id must either be a member of the
SunSystemsServices group, or have db owner rights to the SunSystems Domain and Data
databases.

Important Note: Use the DBDeployer that is supplied ships with this patch set to apply this patch
this version supersedes any earlier released versions.
To apply the patch set to your database tier, carry out the following steps:
1. Copy the contents of the folder Patchset nn for Database Tier from the root of your patch to a
location on one of your SunSystems Application Servers.
Note: The patch set includes a reload of the data dictionary. This is done using the bulk load
Microsoft SQL Server tool BCP.EXE so this tool must be available on the path before you attempt to
load the patch set, otherwise the patch set will fail.
2. Run SunSystems.Patches.DBDeployer.exe from the DBDeployer subfolder.
The SunSystems Database Patch Deployer is displayed, with a grid that lists the patches identified by
their Patch Number, Status (installed or uninstalled), Type, its dependencies, and date last modified.
3. From the Actions menu, select Load Patch then navigate to the new patch set cabinet file, for example,
V61Patchset018-SQL.cab.
4. Select the cabinet file then click Open to load it into the Database Patch Deployer. When the patch set is
loaded, it is displayed in the Database Patch Deployer grid, with a status of Uninstalled.
5. Select the patch set to highlight it in the grid, and then click Install. This applies the patch set to your
Domain, and to the SunSystems databases within that Domain.

Patch Set Installation Note - SQL Server Page 1 of 3.


Based on SunSystems software version 6.1 Patch Set 18 onwards Documentation version 61PSB February 2013.
Copyright 2013 Infor. All rights reserved. www.infor.com.
Infor10 Financials Business (SunSystems)

6. If there are any issues during the application of the patch set to the database tier, logs are written to the
following location:
%CommonAppDataFoplder%\Infor\Log\SunSystems\DBDeployer
By default, this location is:
C:\ProgramData\Infor\Logs\SunSystems\DBDeployer
7. The patch process ends with the Installed Successfully message.
Note: If this message states that some updated forms need compiling, consult the log to find the list
of forms concerned, and then ensure that these forms are compiled after the patch is fully installed.

Updating a SunSystems v6.1 Application Server


Note: In order to minimise the need to reboot and to avoid locked files, it is advisable to stop the
SunSystems services before applying a patch to the application tier and also to exit the Login
Monitor which is located on the system tray.
1. On the machine to be upgraded, execute the appropriate .msp file from the Patchset nn for
Client_App Tiers folder, by double clicking the .msp file. Follow the dialogs and install.
2. Following a successful application of the patch set across all tiers, you must restart the services. Always
restart the SunSystems Security Service first, as other SunSystems services depend on this.

Updating a SunSystems v6.1 Client


On the machine to be upgraded, execute the appropriate .msp file from the Patchset nn for
Client_App Tiers folder by double clicking the .msp file. Follow the dialogs and install.

Updating a SunSystems v6.1 Reporting Tier


On all machines that have the SunSystems Reporting Services entry listed in their Programs and Features,
stop SQL Server Reporting Services, and apply the SRS .msp from the Patchset nn for Client_App
Tiers folder by double-clicking the .msp file. Follow the dialogs and install.
After installing this patch set you should carry out the following:

SunSystems v6.1 Patch Set Installation Note SQL Server


1. Restart all SunSystems services and SQL Server Reporting Services.
2. Run Report Administrator to migrate your existing reports to the latest schema version. Any reports
that fail migration must be opened, corrected and redeployed in Report Designer.
3. Rebuild the Data Model in Data Access Manager.
Some patch sets may not require the above operations, but many do and they should always be carried out
to ensure SunSystems Reporting can be used normally after installation of the patch set.
New and updated example reports to support Faults Fixed documented in the Readme file are added to the
Example Reports - PS folder in the SunSystems Report Store.

Note:
Example reports should not be used operationally in the location to which they are initially installed,
which is primarily for demonstration purposes and liable to be overwritten on upgrade. Even when not
customised from the issued example, operational reports should be deployed to a folder structure
appropriate to the requirements of the business, and path variables amended and folder level access
permissions set accordingly.
That advice (see Report Administrator Help for details) also applies to the new and updated examples
installed by this patch set. In order to apply the relevant fixes above, operational reports, based on
examples for which a new version has been provided, should be updated using Report Designer and
redeployed either:
a) by amending the custom report to match the new example or
b) re-performing the customisation on the new examples as appropriate.
The Example Reports folder is normally hidden from users other than Administrators and Report
Designers using Folder Permissions. The same permissions should be applied to the Example
Reports - PS folder. Alternatively example reports may be removed from the operational report store
entirely and retained elsewhere.

Patch Set Installation Note - SQL Server Page 2 of 3.


Based on SunSystems software version 6.1 Patch Set 18 onwards Documentation version 61PSB February 2013.
Copyright 2013 Infor. All rights reserved. www.infor.com.
Infor10 Financials Business (SunSystems)

The patch set should now be fully installed and you can use SunSystems normally.

Removing the Patch Set


It is strongly recommended that you maintain all tiers of your implementation on the same patch set.

Removing the Patch Set from the Database Tier


Run SunSystems.Patches.DBDeployer.exe from the DBDeployer subfolder.
Select the patch set in the grid, and select Actions >> Uninstall. The patch will be removed.

Removing the Patch Set from the Client and Application Tiers
In the Control Panel >> Programs/Uninstall a Program, ensure the Show Updates option is checked. There is
a sub-entry under SunSystems 6 called Patchset nn. Click the remove option to uninstall the patch set. To
remove the patch set from a multi-tier implementation, you must do this on each tier. It is then recommended
to restart all the SunSystems services.

Removing the Patch Set from the Reporting Services Tiers


In the Control Panel >> Programs/Uninstall a Program, ensure the Show Updates option is checked. There is
a sub-entry under SunSystems Reporting Services called Patchset nn. Click the remove option to uninstall
the patch set. To remove the patch set from a multi-tier implementation, you must do this on each machine
that hosts an element on the SunSystems Reporting Services.

SunSystems v6.1 Patch Set Installation Note SQL Server

Patch Set Installation Note - SQL Server Page 3 of 3.


Based on SunSystems software version 6.1 Patch Set 18 onwards Documentation version 61PSB February 2013.
Copyright 2013 Infor. All rights reserved. www.infor.com.

Você também pode gostar