Wonderware InBatch 2014 R2 (11.0)

Wonderware InBatch 2014 R2 (v.10.2) Readme

Last revision: 13/01/2015

About This Readme

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

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

• Release Summary
• Minimum System Requirements
• Product Compatibility
• Licensing
• Installing Wonderware InBatch 2014 R2
• Resolved Issues
• Known Issues
• Known Issues – Documentation
• Wonderware InBatch Documentation

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 2014 R2 offers the following new features and enhancements:

• Technology update:
• Support for Wonderware System Platform 2014 R2. See the Compatibility Matrix for detailed information
• Support for the following new Foxboro Evo suite
• Foxboro Evo Control Core Services 9.1
• Foxboro Evo Control Software 6.0
• Consolidated delivery of recent Hotfixes

< top of document >

Minimum System Requirements

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

• Hardware Requirements
• Operating System Requirements
• Microsoft SQL Server Requirements
• Additional Software Requirements
• Wonderware InBatch Firewall Exceptions List
  

Hardware Requirements

The following hardware is recommended to support Wonderware InBatch 2014 R2 Client and Server installations:

Requirement	Client	Server
Processor	1.8 gigahertz (GHz)	2.8 gigahertz (GHz)
Processor Cores	2	4
RAM	2 gigabytes (GB)	8 gigabytes (GB)
Hard Disk	30 GB available	500 GB available
Video Adapter / Monitor Capability	1280 x 1024 resolution	1024 x 768 resolution
Network Speed (MBps)	1000	1000
Input Devices	CD-ROM or DVD-ROM drive for installation Keyboard Mouse or compatible pointing device

Hardware Requirements - Operating System

See your specific Microsoft operating system hardware requirements for details.

Operating System Requirements

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

Client Windows OS

Server Windows OS

.NET Framework

Virtualization

XP SP3 Professional (32-bit)

Vista (32/64-bit)

7 SP1 Professional, Enterprise, Ultimate (32/64-bit)

8 Professional, Enterprise (32/64-bit)

8.1 Professional, Enterprise (32/64-bit)

2008 R2 SP1 Standard, Enterprise (32/64-bit)

2008 R2 SP2 Standard, Enterprise (64-bit)

2012 Standard, Data Center (64-bit)

2012 R2 Standard, Data Center (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

Wonderware InBatch Server

N

N

N

N

N

Y

Y

Y

Y

C

C

Y

Y

Y

Y

Wonderware InBatch Clients

N

N

Y

Y

Y

Y

Y

Y

Y

C

C

Y

Y

Y

Y

Wonderware InBatch History Server

N

N

N

N

N

Y

Y

Y

Y

C

C

Y

Y

Y

Y

Wonderware InBatch Reporting Content

N

N

Y

Y

Y

Y

Y

Y

Y

C

C

Y

Y

Y

Y

 

Supported	Y
Not Supported	N
Coexist	C

 

Notes:

• For software requirements for the "Wonderware InBatch Components for ArchestrA IDE/IEE" feature, see the software requirements for Wonderware Application Server.
• For software requirements for the "Wonderware InBatch Reporting Content" feature, see the software requirements for Wonderware Information Server.
• The Wonderware InBatch software is only supported on US/English versions of supported operating systems and Microsoft SQL Server.
• If a supported version of the Microsoft .NET Framework is not installed, the Wonderware InBatch installation automatically installs it.

Microsoft SQL Server Requirements

The following table lists the SQL Server requirements:

	2008 SP3 Express-SSMSE (32-bit)	2008 SP3 Standard, Enterprise (32-bit)	2008 R2 SP1 (32/64 bit)	2008 R2 SP2 Express-SSMSE (32-bit)	2008 R2 SP2 Standard, Enterprise (32/64 bit)	2012 Standard, Enterprise (32/64 bit)	2012 SP1 Express-SSMSE (32-bit)	2012 SP1 Standard, Enterprise (32/64 bit)	2012 SP2 Standard, Enterprise (32/64 bit)	2014 Standard, Enterprise (32/64 bit)
Wonderware InBatch Server	N	N/A	N/A	N/A	N/A	N/A	N/A	N/A	N/A	N/A
Wonderware InBatch Clients	N	N/A	N/A	N/A	N/A	N/A	N/A	N/A	N/A	N/A
Wonderware InBatch History Server	*	Y	Y	*	Y	Y	*	Y	Y	Y
Wonderware InBatch Reporting Content	*	Y	Y	*	Y	Y	*	Y	Y	Y

 

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

 

Additional Software Requirements

The following table lists the additional typical software requirements for each Wonderware InBatch station type when the Wonderware InBatch software is used with Wonderware 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	-

Wonderware InBatch Firewall Exceptions List

The following table lists the application names and 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
Wonderware 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

< top of document >

Product Compatibility

Wonderware InBatch 2014 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® System Platform*
	2014 R2	Y	Y
	2014 P01	Y	Y
ArchestrA® System Platform
	2012 R2	N	N
	2012	N	N
Wonderware® InTouch® CE	10.1	N	N
Wonderware® Manufacturing Execution System
	4.5 P01	N/A	Y
	4.0 SP2	N/A	Y
	4.0 SP1	N/A	N
Wonderware® InControl™	7.11 SP2 P01	N/A	N
Wonderware® Manufacturing Execution Module	1.0	N/A	N
Wonderware® QI Analyst™
	8.0 SP3	N/A	Y
	8.0 SP2	N/A	Y
	8.0 SP1 P01	N/A	N
Wonderware® SCADAlarm™	6.0 SP2 P01	N	N
Wonderware® Intelligence	1.5 SP1 (2012)	Y	Y
	1.5	N	N
ArchestrA® Workflow™	2012 R2 SP1	N/A	Y
Wonderware® Skelta BPM™	2014 R2 (v4.1)	N/A	Y
	2014 (v4.0)	N/A	Y
Wonderware® Production Execution Module	2.1 SP1	N/A	Y
Foxboro® Evo	2014	Y	Y
Foxboro® Control System	6.0 (and all Quick Fixes)	Y	Y
	4.0 (and all Quick Fixes)	N	N
Foxboro® Evo Control Core Services	9.1	Y	Y
	9.0	Y	Y
Foxboro® I/A Series Software
	8.8	Y	Y
	8.7 (Windows XP, Windows 2003)	Y	Y

 

Supported	Y
Not Supported	N
Products do not share data directly, but can coexist.	N/A

 

* Previously called ArchestrA System Platform

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.

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

< 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.

Wonderware InBatch 2014 R2 supports Archestra.lic license files. Archestra.lic format licenses work with Wonderware InBatch 2012 R2 and later.

< top of document >

---

Installing Wonderware InBatch 2014 R2

Special Notes

• Before upgrading, please take note of the known issues in the Installation Issues section of this document.
• Note: Prior to upgrading, confirm that your Error Queue is empty. Because of changes to the Wonderware 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-Wonderware 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.
• Follow this installation order if you are installing System Platform 2012 or later on the Batch Server node with a custom Wonderware Application Server installation location:
1. Install Application Server
2. Install Wonderware InBatch
If you do not install in this order, the BatchEvent feature may not work properly.

Installing or Upgrading

For installation and upgrade instructions, see the Wonderware InBatch Installation Guide and the Installation Issues section of this document.

Upgrading the software from the versions listed below only requires running the Setup.exe:

• 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
• Wonderware InBatch 2012 R2 (10.0)
• Wonderware InBatch 2014 (10.1)

The process will upgrade all components as required.

Once the upgrade process is completed you have to run the CVTMaster.exe utility to upgrade the application databases.

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 2014 R2.

< top of document >

Resolved Issues

This section describes important resolved issues.

L00131007:	(HotFix L00129628): InBatch now displays the batch questions in the same order as present in the recipe and the answer to these question gets answered correctly.
L00132645:	(HotFix L00131745): BatchMngr would stuck during the writing phase parameters or sometimes UnilinkMngr would crash. The issue is now resolved.
L00131691:	(HotFix L00131564): Both Horizontal and Vertical scrollbars are now displayed in all three grids in BatchDisplay and InTouch Runtime windows.
L00135259:	(HotFix L00133743): It is now possible to hold batch (if configured) when phase transitions directly from ready to held.
L00133137:	(HotFix L00133252): BatchDspl is automatically changing CLB focus without any operator interaction. The issue is now resolved.
L00131434:	(HotFix L00132642, L00132139 ): EOB Report is now successfully printed with system using SQL Server 2008 R2 SP1 and later, SQL 2012 and SQL 2012 SP1 (Standard or Enterprise editions).
L00132644:	(HotFix L00131623): No communication issue is now visible and the InTouch application does not get disconnected from Security Manager.
L00132533:	(HotFix L00132551): Running certain recipes used to crash the Batch Manager because of the length of the recipe. Make sure that the maximum length that a message where equipment, operation, and phase names are used does not exceed 80 characters.
L00132170:	(HotFix L00132507): InBatch Reports link appear correctly on the Wonderware Information Server 2014 home page.

< top of document >

Known Issues

This section describes important known issues.

• Installation Issues
• Other Issues

Installation Issues
L00127339:	Machine names in redundant systems must be 12 characters or less.
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: Open the Registry Editor. Navigate down to [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management]. 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 Wonderware InBatch development client. Use the following workaround: Open a Microsoft Windows Explorer page. Navigate to C:\Programs\Wonderware\Wonderware InBatch\cfg\Config_A. Right-click the file vista.taf and select Delete.
L00126972:	Users do not need to be an Administrator for DoneBy/CheckBy to work. However, they do need the "Impersonate a user after authentication" permission set in the Local security policies.
L00128201:	Running the cvtmaster a second time results in conversion failure. Use the following workaround: Create a new folder, and name it something other than Config_A (e.g. test). Copy the contents of the Config_A folder to the folder you just created. Run cvtmaster, directing it to the new folder. Copy the database from the new folder to the Config_A folder.
L00081552:	Running Wonderware InBatch with IA components in a redundant configuration does not fail over when IADriver is shut down. The following table shows the redundancy status on master/backup 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 Backup Node Status Master Node Status Backup Node Status Master Node Status Backup Node Status End process from Task Manager (Correct Failover) Master failed Master with invalid backup Master failed Master with invalid backup Master failed Master with invalid backup Stopped from Runtime Services (Non-Failover) Master with valid backup Valid backup Master with valid backup Valid backup Master with valid backup Valid backup
L00082366:	Unable to import Wonderware InBatch tags to InTouch using DBload.exe. Wonderware 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 Wonderware 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 configuration and scheduling. After the custom reports are populated or deployed to the Wonderware InBatch > Execute Reports > Wonderware 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\Wonderware InBatchReports\ReportConfig Open the file RptServicesConfig.xml for editing. Add the following line under the <Folder> node: <Report Name="Custom Batch Detail" /> 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: 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/. Click Properties and then New Role Assignment. Enter the System administrator's user name and grant the roles by selecting the Content Manager option.
L00106510:	When you try to print Wonderware 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.
L00125348:	If you use the import utility in preview mode, no warning messages are shown if the utility imports a Wonderware 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 Wonderware 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 Wonderware InBatch versions.
• Wonderware InBatch Getting Started Guide - Describes the basic components of the Wonderware 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 Wonderware InBatch 2014 release.
• Wonderware InBatch User's Guide - Describes the components of the Wonderware 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 Wonderware InBatch COM technology and provides practical examples of its use.
• Wonderware InBatch Application Object Editor Help - Provides information about the Wonderware InBatchUnit, Wonderware InBatchConnection, Wonderware InBatchPhase, and Wonderware 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 >

---

© 2015 Invensys Systems, Inc. All Rights Reserved.