Wonderware InBatch 2012 R2 (10.0)

Материал из archestra.info
Перейти к: навигация, поиск

Wonderware InBatch 2012 R2 (v.10.0) Readme

Last revision: 3/8/2013

About This Readme

This document contains important information about Wonderware® InBatch™ 2012 R2 (v.10.0). Review this document for known issues and changes to the InBatch software and documentation included on this CD.

Important! Before upgrading your system, review the Installing Wonderware InBatch 2012 R2 section.

NOTE: Readme files from previous releases of Wonderware InBatch software are posted to the Wonderware Developer Network at http://wdn.wonderware.com/Downloads.

Release Summary

Wonderware InBatch 2012 R2 offers the following new features and enhancements:

  • New installation program and post-installation configuration utility
  • Integration of InBatch and ArchestrA:
    • A set of Application Server objects for replicating the InBatch model in Application Server
    • A utility that automatically creates/updates the InBatch Model in the InBatch objects in Application Server
    • A set of ArchestrA Symbols to monitor InBatch data in InTouch applications
  • Additional functionality in the InBatch Runtime Stateless API
  • A utility that generates a report of the differences between two recipes, including the ability to save the recipe in XML format when recipe changes are saved or the recipe is set to production
  • Support for subscribing to existing events in the Batch execution and using them in external applications (requires ArchestrA System Platform 2012 R2 or later)
  • Support for Microsoft SQL Server 2012
  • Support for ArchestrA licensing
  • Consolidated delivery of recent Hotfixes

< top of document >

System Requirements

This section describes the hardware, software, and operating system required to install the Wonderware InBatch 2012 R2 software.

Hardware Requirements

Minimum Hardware Requirements

The following hardware is recommended to support Wonderware InBatch 2012 R2:

  • Processor: 3.0 gigahertz (GHz) or faster processor
  • RAM: 2 gigabyte (GB) of memory
  • Hard disk: At least 4 GB of available disk space
  • Video adapter and monitor with SVGA (1024 × 768) resolution or higher
  • CD-ROM or DVD drive for installation
  • Keyboard
  • Mouse or compatible pointing device

See your specific Microsoft operating system hardware requirements for details.

Operating Systems Link to Microsoft Operating System Requirements
Windows Server 2003 R2 SP2 http://technet.microsoft.com/en-us/library/cc756124(WS.10).aspx
Windows Server 2008 R2 SP1 http://www.microsoft.com/windowsserver2008/en/us/system-requirements.aspx
Windows Server 2008 SP2 http://technet.microsoft.com/en-us/library/dd540766(WS.10).aspx
Windows Vista SP2 http://technet.microsoft.com/en-us/library/dd335032(WS.10).aspx
Windows XP Professional SP3 http://windows.microsoft.com/en-us/windows/help/learn-how-to-install-windows-xp-service-pack-3-sp3
Windows 7 SP1 http://windows.microsoft.com/en-US/windows7/whats-included-in-windows-7-service-pack-1-sp1

Operating System Requirements

The following table lists the operating system, .NET Framework, and virtualization requirements for InBatch 2012 R2.

Note: Only the versions shown in the following tables are supported for InBatch 2012 R2 components.

  Client
Windows OS		 Server
Windows OS		 .NET
Framework		 Virtualization
XP SP3
Professional
(32-bit)		 Vista SP2
Business,
Enterprise,
Ultimate
(32/64-bit)		 7
Professional,
Enterprise,
Ultimate
(32/64-bit)		 7 SP1
Professional,
Enterprise,
Ultimate
(32/64-bit)		 2003 SP2
Standard,
Enterprise
(32-bit)		 2003 R2 SP2
Standard,
Enterprise
(32-bit)		 2008 SP2
Standard,
Enterprise
(32/64-bit)		 2008 R2
Standard,
Enterprise
(64-bit)		 2008 R2 SP1
Standard,
Enterprise
(64-bit)		 3.5 SP1 4.0 4.5 Hyper-V
(Based on
Supported
OS version)		 VMWare 5.0
(Basic
virtualization;
no HA/DR*)		 VMWare
vSphere 5
InBatch Server 10.0:

 N N N N Y Y Y Y Y C Y Y Y Y Y
InBatch Clients 10.0: Y Y Y Y Y Y Y Y Y C Y Y Y Y Y
InBatch History Server 10.0: N N N N Y Y Y Y Y C Y Y Y Y Y
InBatch Reporting Content 10.0: Y Y N Y Y Y Y Y Y C Y Y Y Y Y

* High Availability/Disaster Recovery

 

Supported Y
Not Supported N
Coexist C

 

Notes:

  • For software requirements for the "InBatch Components for ArchestrA IDE/IEE" feature, see the software requirements for Wonderware Application Server.
  • For software requirements for the "InBatch Reporting Content" feature, see the software requirements for Wonderware Information Server.
  • The InBatch software is only supported on English versions of supported operating systems and Microsoft SQL Server.
  • You must install a supported version of the Microsoft .NET Framework before installing Wonderware InBatch 2012 R2. If a supported version is not installed, the Wonderware InBatch installation automatically installs it.
  • If you are using the InBatch History Server station, Internet Information Services (IIS) 6.0 or 7.0 or 7.5 is required.
  • InBatch 2012 R2 is not supported on a single node running on Windows XP SP3 32-bit. Windows XP SP3 32-bit does not support IIS 6.0, so the InBatch History Server feature cannot be installed.

Microsoft SQL Server Requirements

  2008 SP3 Express-SSMSE (32-bit) 2008 SP1 Standard, Enterprise (32-bit) 2008 SP3 Standard, Enterprise (32-bit Only) 2008 R2 SP1 Express-SSMSE (32-bit) 2008 R2 SP1 Standard, Enterprise (32/64 bit) 2008 R2 SP2 Standard, Enterprise (32/64 bit) 2012 Express-SSMSE (32-bit Only) 2012 Standard, Enterprise (32/64 bit) 2012 SP1 Standard, Enterprise (32/64 bit)
InBatch Server 10.0

 N/A N/A N/A N/A N/A N/A N/A N/A N/A
InBatch Clients 10.0 N/A N/A N/A N/A N/A N/A N/A N/A N/A
InBatch History Server 10.0 N Y Y N Y Y N Y Y
InBatch Reporting Content 10.0 * Y Y * Y Y * Y Y

 

Supported Y
Not Supported N
Check the requirements for Wonderware Information Server. *

 

*Note: Check if other products that use the same operating system as InBatch 2012 R2 are compatible with Microsoft SQL Server 2008 SP3.

Additional Software Requirements

The following table lists the additional typical software requirements for each InBatch station type when the InBatch software is used with ArchestrA System Platform:

Additional Software Requirements
Wonderware InBatch Station Type
Server
Run-time
Client
Development
Client
History
Server
Reporting
Content
Redundant
System

Wonderware Application Server bootstrap and IDE
Yes
-
Yes
-
-
Yes
Wonderware InTouch
-
Yes
-
-
-
-
Wonderware Information Server with ArchestrA Reports feature
-
-
-
-
Yes
-

For compatibility information regarding Wonderware InBatch 2012 R2 and Foxboro Control Software 4.0, contact your Invensys sales representative.

Wonderware InBatch Firewall Exceptions List

The following table lists the application names and their ports, that must be added in the Windows Firewall exceptions list for Wonderware InBatch:

Application Name
Port Number
BatchMngr
9008
EnvMngr
9002
InfoMngr
9012
HistQMngrvista
9015
HisQReader
9016
InBatch Middleware Access
8199
OLE Recipe Automation
5001
OLE Recipe Automation
5002
OLE Recipe Automation
5003
OLE Recipe Automation
5004
OLE Recipe Automation
5005
RedMngr
9006
RedMngrX
9013
RedMngrX2
9014
SecMngr
9004
UnilinkMngr
9007
aaLogger.exe
-
RecipeEdit.exe
-
TagLinker.exe
-
MaterialSrv.exe
-

< top of document >

Product Compatibility

Wonderware InBatch 2012 R2 is compatible and can co-exist with the following components. Compatibility means that the products can communicate with each other over the network. Co-existence means that the products can be installed on the same computer.

Component Version Compatibility Co-existence
Wonderware® Application Server 3.5 Y Y
3.5 P01 Y Y
3.6 Y Y
Wonderware® InTouch® 10.5 Y Y
10.5 P01 Y Y
10.6 Y Y
Wonderware® Historian Client 10.0 SP2 N/A Y
10.1 N/A Y
Wonderware® Historian Server 10.0 SP1 N/A Y
11 N/A Y
Wonderware® Manufacturing Execution System 4.0 N/A Y
4.0 SP1 N/A Y
Wonderware® Information Server 4.5 Y Y
5.0 Y Y
Wonderware® InControl™ 7.11 SP2 P01 N/A Y
Wonderware® Manufacturing Execution Module 1.0 N/A Y
Wonderware® QI Analyst™ 8.0 SP1 P01 N/A Y
8.0 SP2 N/A Y
Wonderware® SCADAlarm™ 6.0 SP2 P01 N/A Y
Wonderware® Intelligence 1.5 N/A Y
1.6 N/A Y
ArchestrA® Workflow™ 1.5 N/A Y
1.5 SP1 N/A Y
Wonderware® Production Execution Module 2.1 SP1 N/A Y
Supported Y
Not Supported N
Products do not share data directly, but can coexist. N/A

In some cases, the Wonderware InBatch software is supported in newer environments than a compatible product. Wonderware InBatch software has been tested for compatibility with a listed product only in the environments that are supported by that particular product.

< top of document >

Licensing

Wonderware Component Licensing

Please contact your local Invensys Distributor or Sales representative for details about the licensing requirements for Wonderware components.

InBatch 2012 R2 supports ArchestrA licensing and ArchestrA.lic license files only, which does not provide the capability to run earlier versions of InBatch software with InBatch 2012 R2 licenses.

Microsoft Office Fluent UI Licensing

The 2007 Microsoft Office Fluent User Interface is subject to protection under U.S. and international intellectual property laws. The interface is used by Wonderware InBatch under the license from Microsoft.

< top of document >

Installing Wonderware InBatch 2012 R2

For installation and upgrade instructions, see the InBatch Installation Guide.

Upgrading to Wonderware InBatch 2012 R2 from the following versions is automatic:

  • Wonderware InBatch 9.0
  • Wonderware InBatch 9.0 with SP1, and SP2
  • Wonderware InBatch 9.5
  • Wonderware InBatch 9.5 with SP1
  • Wonderware InBatch 9.6

The upgrade supports Wonderware InBatch with I/A components and without I/A components.

To upgrade from a version older than Wonderware InBatch 9.0, first uninstall the previous version and then install Wonderware InBatch 2012 R2.

Note: Prior to upgrading, confirm that your Error Queue is empty. Because of changes to the InBatch History database, any data left in the Error Queue will not be accessible in the upgraded version. Also, ensure that all batches have ended and that all warm restart files have been deleted.

After you upgrade Batch Reporting Content (from a pre-InBatch 9.0 SP2 version), a new report template called BatchJournal_EOB is available. The BatchJournal_EOB template is for an optimized Batch Journal report that is meant to be used with End of Batch report triggers. To schedule this report in Wonderware Information Server, you must manually redeploy the Batch Reports by using the Wonderware Information Server Report Deployment tool.

Note: If InBatch Server fails to start after being installed on the Windows XP SP3 operating system, you must restart the InBatch Server node.

If you are using InBatch IBMX with Wonderware Application Server 2012, you must install the following to solve tag write issues:

  • Wonderware Application Server 3.5 Patch 01
  • Wonderware Application Server Hotfix L00120158
  • Wonderware Application Server Hotfix L00122616 (must be installed after L00120158)

If you are using the InBatch ApplicationObjects with Wonderware Application Server 2012, you must install the following hotfix to solve attribute read/write issues:

  • Wonderware Application Server Hotfix L00121831

If you are installing System Platform 2012 (or 2012 R2) on the Batch Server node and Wonderware Application Server is installed in a non-default location, then Application Server must be installed before you install the InBatch software. If you do not install in this order, the BatchEvent feature may not work properly.

Starting with InBatch 2012 R2, the LogViewer has been replaced with the ArchestrA Logger, which is available within the System Management Console (SMC).

< top of document >

Resolved Issues

This section describes important resolved issues.

L00123326: (HotFix L00123080): A BatchMngr infinite loop scenario occurs at SET transition.
L00123334: (HotFix L00123311): If identical Manual and/or Data phases are executed at the same time on the same equipment within a batch, the following warning appears in the logger: "Batch X/Y/Z running recipe [A] attempted to run two instances of the phase [B] on equipment [C] at the same time. This can result in unpredictable results.".
L00124051: (HotFix L00123987): The Batch Server and InTouch clients stop responding when the Batch Security ActiveX Control (BatchSecCtrl.dll) and SecMngr are used.
L00124346: (HotFix L00124306): After an upgrade from InBatch 8.1 SP1 to InBatch 9.5 SP1, the Recipe Editor stops responding when synchronizing, validating, and exporting recipes.
L00124412: (L00122483): The Recipe Editor stops responding when synchronizing and validating all recipes. Logs "INVALID PARAMETER WAS ENCOUNTERED".

< top of document >

Known Issues

This section describes important known issues.

Installation Issues

L00107356: Due to the large number of services running on IA Series platforms, the installation program should check the value of the SessionViewSize registry setting. It is likely that this registry value does not exist and will need to be created. If you ever notice that services unexpectedly fail to start, the value of this setting may be too small. Follow these steps:
  1. Open the Registry Editor.
  2. Navigate down to [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management].
  3. If a registry value named SessionViewSize exists, make sure it is at least 30 (hex) or 48 (decimal).

If it does not exist, create a new DWORD value named SessionViewSize and set it to 30 (hex) or 48 (decimal).

Other Issues

L00077400: Editors are not opening on the InBatch development client.

Use the following workaround:

  1. Open a Microsoft Windows Explorer page
  2. Navigate to C:\Programs\Wonderware\InBatch\cfg\Config_A.
  3. Right-click the file vista.taf and select Delete.
L00081552: Running InBatch with IA components in a redundant configuration does not fail over when IADriver is shut down.

The following table shows the redundancy batch status on master/slave nodes when IBMX, IBCli, and IADriver are stopped from the Runtime Services dialog box or when you end the process from Task Manager.

 
IBMX
IBCli
IADriver
Action on the master node Master Node Status Slave Node Status Master Node Status Slave Node Status Master Node Status Slave Node Status
End process from Task Manager Master failed Master with invalid backup Master failed Master with invalid backup Master failed Master with invalid backup
Stopped from Runtime Services Master with valid backup Valid backup Master with valid backup Valid backup Master with valid backup Valid backup

 
L00082366: Unable to import InBatch tags to InTouch using DBload.exe.

InBatch uses a dot (.) instead of a hyphen (-) as a delimiter in tag names. InTouch supports only a hyphen as a delimiter. Before you load the InBatch tag names into InTouch, edit the .CSV file and replace the dot delimiters with hyphens.
L00082612: Custom-created reports that are populated to the batch report directory are not available for being configured and scheduled.

After the custom reports are populated or deployed to the InBatch > Execute Reports > InBatch list on the Launch Pad, use the following steps to configure and schedule the reports. For example, suppose that a report named "Custom Batch Detail" is populated in the list.

You must update the RepServicesConfig.xml file in the following location:

<systemdrive>:\Inetpub\wwroot\Wonderware\InBatchReports\ReportConfig

  1. Open the file RptServicesConfig.xml for editing.
  2. Add the following line under the <Folder> node:

    <Report Name="Custom Batch Detail" />

  3. Save the file.

Example:

<Folder>
<Report Name="Custom Batch Detail: />
.......
.......
.......
</Folder>

Now, the report named Custom Batch Detail is available for configuring and scheduling. Add a similar line for each custom report that is populated in the Execute Reports list.
L00098867: When using the IBCli application, some I/O Servers or DAServers (including FS Gateway) may report an error about an "Unknown Watchdog" tag. This error is only reported when IBCli starts, but the Watchdog tag will still function as expected.

If you get the following errors from IBCli:

  • Too many ping timeouts (NOTE: only if you get this error repeatedly).
  • Failed to register 'Watchdog' ping tag - pinging is disabled.
  • Do one of the following:
    • Try to upgrade to a newer I/O Server or DAServer version.
    • Create a tag called Watchdog in the I/O or DAServer.

It can be any data type. Disable pinging using the IBCli Disable Ping option.
L00106015: An error occurs when you access the Reports link in the Wonderware Information Server Portal after logging in as a system administrator and not as a portal admin of the Wonderware Information Server installed node. To avoid this error, perform any one of the following workarounds:

Start Internet Explorer using Run As Administrator command and navigate to the portal using the system administrator credentials.

Do the following:

  1. Start Internet Explorer using the Run As Administrator command with the credentials of the user who had configured the Information Server feature and enter the URL: http://localhost/reports/.
  2. Click Properties and then New Role Assignment.

Enter the System administrator's user name and grant the roles by selecting the check box for the Content Manager option.

L00106510: When you try to print InBatch reports from a Wonderware Information Server client, the following error appears: "Unable to load client print control"

For instructions about how to resolve this issue, see Tech Note 648, "Troubleshooting ArchestrA Reports Printing Problems," that is available from the Wonderware Technical Support website.
L00113744: SR 103121815 Outputting a Batch Journal report through the Wonderware Information Server portal against a large recipe can result in a timeout.
L00125348: If you use the import utility in preview mode, no warning messages are shown if the utility imports a InBatch ModelDB in which any of the following have duplicate names (case sensitive): processes, transfers, segments, units, connections, phases. However, the import utility does show a warning when you do the actual import.

< top of document >

Known Issues – Documentation

Newer operating systems no longer include the WinHlp32.exe Help viewer component, which is required for viewing .hlp files. The InBatch software includes the following .hlp files:

  • BatchView.hlp
  • IALink.hlp
  • Ib_func.hlp
  • TagView.hlp
  • TIMEdit.hlp

To view these Help files, download and install the viewer component from Microsoft at http://support.microsoft.com/kb/917607.

< top of document >

Wonderware InBatch Documentation

The Wonderware InBatch documentation set includes the following:

  • ReadMe (This document) - Provides information about software and hardware requirements, known issues, licensing, and documentation updates.
  • Wonderware InBatch Installation Guide - Provides information about installation and upgrading from the previous InBatch versions.
  • Wonderware InBatch Getting Started Guide - Describes the basic components of the InBatch software and provides a tutorial to help you get started using the product.
  • Wonderware InBatch Demo Guide - Describes a demo application that shows you how to use some of the new features in the InBatch 2012 R2 release.
  • Wonderware InBatch User's Guide - Describes the components of the InBatch software and how to use them to create applications.
  • Wonderware InBatch Stateless API Online Reference - Provides information about the stateless API supported by the Batch Server.
  • Wonderware InBatch COM Technical Reference Guide - Describes using the InBatch COM technology and provides practical examples of its use.
  • InBatch Application Object Editor Help - Provides information about the InBatchUnit, InBatchConnection, InBatchPhase, and InBatchSegment objects.

The Wonderware InBatch product library consists of a set of Portable Document Files (PDF) located in the UserDocs folder of the Wonderware InBatch installation CD. Install the Adobe Reader on your computer to view the Wonderware InBatch documentation. You can download the latest version of the Adobe Reader from the Adobe Corporation web site:

www.adobe.com/products/acrobat/readstep2.htm

After installing the Adobe Reader, double-click a PDF file to view the book. Click the Open command on the File menu to open a book in the Adobe Reader.

The Wonderware InBatch installation instructions are located in the root folder of the Wonderware InBatch installation CD, as a .chm file. You can view these instructions by clicking the Help when you start the Wonderware InBatch installation procedure.

< top of document >

© 2013 Invensys Systems, Inc. All Rights Reserved.

Источник — «http://www.archestra.info/index.php?title=Wonderware_InBatch_2012_R2_(10.0)&oldid=3699»