Whats New

This version 2.03 release of AutoSave for System Platform (A4SP) provides users with a fully functional
and seamlessly integrated solution for managing changes and securing your historical data within your
Galaxy. This release includes, but is not limited to, the following new features:
Support for System Platform 2014 (Application Server 4.0)
IMPORTANT UPGRADE NOTICE! - It is critical to update A4SP prior to upgrading your
System Platform product! This is due to the fact that all object ID's will be changed during the
System Platform 2014 upgrade process. Customers should follow the upgrade process defined
in the Installation Overview.
This version no longer formally supports or is tested against Application Server 3.1 SP3 P1
1.
New report to detail managed instances, if a custom list of instances is being tracked. 2.
Internal updates and corrections. 3.
WARNING: If you plan to install A4SP on an existing AutoSave Server, and you are running the
AutoSave Program Export Event Module (or Acronis or RJ3), please contact MDT Technical Support
before continuing.
System Requirements
The system requirements for A4SP v2.03 are as follows:
A4SP Service
Must be installed on the Wonderware Galaxy Repository Node installed with the following
versions:
Application Server 3.5 (refer to the Wonderware documentation for System
Requirements)
i.
or, Application Server 3.6 (refer to the Wonderware documentation for System
Requirements)
ii.
or, Application Server 4.0 (refer to the Wonderware documentation for System
Requirements)
iii.
Requires the AutoSave client, which is automatically installed with the following version:
AutoSave 5.07.03 ( The AutoSave Client is certified to work on Windows OS as
defined in both the Server System Requirements, and Client System Requirements.)
i.
Requires network communication outgoing to the AutoSave Server via port 22260
Requires network communication incoming from the A4SP Client via port 22270*
[Optional] Network communication outgoing to the A4SP Client via port 22271*
This allows remote status messages to be delivered to remote A4SP Clients* i.
If desired, the A4SP Service must NOT be running as the Local System Account, which
restricts this communication.*
ii.
1.
A4SP Client
Must be installed on a Wonderware IDE Workstation installed with the following versions:
Application Server 3.5 (refer to the Wonderware documentation for System
Requirements)
i.
or, Application Server 3.6 (refer to the Wonderware documentation for System
Requirements)
ii.
2.
or, Application Server 4.0 (refer to the Wonderware documentation for System
Requirements)
iii.
Requires the AutoSave client which is automatically installed with the following version:
AutoSave 5.07.03 (The AutoSave Client is certified to work on Windows OS as defined
in both the Server System Requirements, and Client System Requirements.)
i.
Requires network communication outgoing to the AutoSave Server via port 22260, and
outgoing to the A4SP Service via port 22270*
[Optional] Network communication incoming from the A4SP Service via port 22271*
AutoSave Server/Client
An AutoSave Server (v5.07.03) must exist or be installed, as the repository for the A4SP
System. (see Server System Requirements)
AutoSave modules (v2.03) for A4SP must be installed. They are included on the CD, and will
be installed automatically via the AutoSave server installer.
3.
NOTES:
The WW Network Service account should not be used for the A4SP Service, the GR Node
MSSQLSERVER service or the A4SP Client login. This account is created for internal
communications between Wonderware software products only.
Things to Consider
Users of this release of AutoSave for System Platform (A4SP) should consider the following. These items
may change in future updates. Contact your A4SP support provider for more details:
It is critical to update A4SP prior to upgrading your System Platform product! This is due to the fact
that all object ID's will be changed during the System Platform 2014 upgrade process. Customers
should follow the upgrade process defined in the Installation Overview.
1.
A4SP currently only supports change tracking of a single Galaxy on a GR Node, to an AutoSave
Repository. Additional Galaxies may exist on the GR Node, but they can not be managed by A4SP.
2.
A4SP currently does not track changes to the following:
Security Groups, Roles or Users.
Template containment relationships; however, restore will place a template under its previous
Container template if it exists.
The creation of a Toolset may not be reflected in the A4SP navigation pane, until such a time
that an object is created within that Toolset
The movement of objects between toolsets is not tracked, until that object itself has been
changed or updated
3.
There are currently no compare details provided for graphical objects, client controls or managed
InTouch applications.
4.
The Base Templates, $Symbol and $ClientControl are not accessible via A4SP 5.
The Galaxy cannot be deleted with the A4SP Service or Client connected. If a Galaxy must be
deleted, please refer to the section on Deleting a Galaxy.
6.
After A4SP installation, if a new Galaxy is made based off the Galaxy being monitored by A4SP,
some additional tables and triggers should be removed. Contact your A4SP Support provider for
more information.
7.
Best Practices
AutoSave Device and Galaxy Storage
Though you are able to store multiple Galaxies, as well as automation devices within a single AutoSave
repository, if the data being stored is excessive, or the hardware is not scaled properly performance
problems can occur. This is just the nature of the bandwidth, processors, memory and other factors.
If you plan to store multiple Galaxies or a combination of Galaxies and automation devices, it is
recommended to consult with your AutoSave for System Platform support provider.
Bulk Operations
It is important to note that any bulk operation which may cause the creation or change of many hundreds
or thousands of changes may be greatly affected by the operation of the A4SP system. As a result it is
highly recommended that before running such an operation (such as the upgrade of your System Platform,
or the import of many new objects) that the A4SP Service be shutdown on the GR Node, and restarted
after the operation is complete. You will not lose the changes during that process, as they will still be
queued for backup in the Galaxy. This will just delay the backup operation until after the bulk operation is
complete, which decreases the load and any process conflicts that may occur.
Patches and Service Packs
It is important to make sure your A4SP System is running with the latest version, as well as the latest
Patches and Service packs. Please check the product downloads and support pages for the latest updates to
these products.
A4SP User Accounts
It has been seen that a customer using the WW Network User, for the login credentials of the A4SP Client
or A4SP Service, can cause conflicts. As such, we recommend NOT using the WW Network User for
either operation. In addition, the MSSQLSERVER service account on the GR Node should run with
appropriate privilege to add tables/triggers, and not use the WW network service account.