Wonderware Tech Note 564 “Removing an Undeployed or Deleted Application Server’s Galaxy Erroneously Listed in Wonderware SMC”

Wonderware Tech Note 564 “Removing an Undeployed or Deleted Wonderware Application Server’s Galaxy Erroneously Listed in the Wonderware System Management Console, DAServer Manager and Log Viewer” is available.

In some instances when an Application Server’s Platform is undeployed or a Galaxy is deleted, the Galaxy information is not properly cleaned up on all of the Platforms in the Galaxy. When this occurrs a Galaxy may appear in the SMC in DAServer Manager and Log Viewer on a node that no longer has a platform deployed to it from this Galaxy. Unlike Node Groups, Galaxies in the SMC are read-only and cannot be deleted from the SMC.
This Tech Note explains how to remove a Galaxy listed in the SMC DAServer Manager and Log Viewer that should no longer appear.

Click here to review the tech note.

Wonderware PacWest Tech Note 82 “Resolving slow WindowMaker load times for Wonderware InTouch managed applications” is available

Wonderware PacWest Tech Note 82 “Resolving slow WindowMaker load times for Wonderware InTouch managed applications“, written by Hawey Wells, is available on the Wonderware PacWest website.
Default Wonderware InTouch application settings can result in long waits opening ArchestrA IDE managed applications containing a large number of windows with embedded ArchestrA Graphics.Each window is programmatically opened to complete the initial load of all ArchestrA graphics in the development environment. Adding a setting to the application’s INTOUCH.INI file can vastly improve the initial load times in Wonderware InTouch WindowMaker for instances when this delay adversely affects the speed of development. This document lists the steps necessary to locate and add the LoadAllActiveXOnStartup flag set to zero in the managed application’s INTOUCH.INI file.
Click here to review the tech note.

Wonderware PacWest Tech Note 80 “How to use the $PingNode Object Template in Wonderware Application Server” is available

Wonderware PacWest Tech Note 80 “How to use the $PingNode Object Template in Wonderware Application Server“, written by Mark Boisvert, is available on the Wonderware PacWest website.

This tech note describes how to use a custom $PingNode object template created for Wonderware Application Server. Object based on that template provides ping status for a given machine (node). The $PingNode object template includes the Ping script that can be customized to provide additional features. By default the enabled object will ping the configured node every 10 seconds and report general status and reply time. It also can be configured to alarm if a ping timeout is incurred. This type of information should be useful for monitoring system health of network hardware and other machines that are not part of the galaxy.
Click here to review the tech note.

Wonderware Application Server 3.0 Service Pack 2 is released

Wonderware Application Server 3.0 SP2 is released. The service pack addresses several issues related to multi-user edits, ArchestrA symbol functionality, and more.

Download the Service Pack and the related ReadMe file using the links below:

Wonderware customers from outside of the Wonderware PacWest distribution area can access the Service Pack on the Wonderware Support Website.

Wonderware InTouch 10.0 Service Pack 2 is released

Wonderware InTouch 10.0 SP2 is released. The service pack addresses several issues related to Terminal Services environments, ArchestrA symbol “InTouch:” references, and more.

Download the Service Pack and the related readme file using the links below.

Wonderware customers from outside of the Wonderware PacWest distribution area can access the Service Pack on the Wonderware Support Website.

How to retrieve wide-history data from Wonderware Historian using a stored procedure

Below is an example of a stored procedure that will retrieve wide-history data from Wonderware Historian (formerly known as IndustrialSQL Server):

CREATE PROCEDURE HistoryData
@StartDateTime datetime,
@EndDateTime datetime,
@Tags varchar(500) = ‘[SysDateDay], [SysDateMonth], [SysDateYear]’
–above: @Tags is an optional parameter, value after the equal sign is the default value if @Tags is omitted
AS
BEGIN
SET NOCOUNT ON
DECLARE @SQLString varchar(1000)
SET @SQLString = ‘SET QUOTED_IDENTIFIER OFF ‘
SET @SQLString = @SQLString + ‘SELECT * FROM OPENQUERY(INSQL, ‘
SET @SQLString = @SQLString + + ‘”SELECT DateTime = convert(nvarchar, DateTime, 21), ‘ + @Tags + ‘ ‘
SET @SQLString = @SQLString + ‘FROM WideHistory WHERE wwRetrievalMode = ”Cyclic” AND wwResolution = 1000 AND wwVersion = ”Latest” ‘
SET @SQLString = @SQLString + ‘AND DateTime >= ‘ + CHAR(39) + CAST(@StartDateTime AS varchar(50)) + CHAR(39)
SET @SQLString = @SQLString + ‘ AND DateTime <= ‘ + CHAR(39) + CAST(@EndDateTime AS varchar(50)) + CHAR(39) + ‘”)’
EXEC (@SQLString)
END

The procedure accepts 3 parameters:
– Start date/time
– End date/time
– optional comma separated list of tag – so that you can run it for different set of tags

To install the procedure just run the script above against your Historian’s Runtime database from within SQL Server Management Studio.

And here’s how you execute the command:

EXEC HistoryData ‘20081027 21:04:00′,’20081027 21:07:00’, ‘SysTimeSec, SysDateDay’

But you can also skip the 3rd parameter and run it this way:

EXEC HistoryData ‘20081027 21:04:00′,’20081027 21:07:00’