Wonderware InBatch 2014 (10.1)

Wonderware InBatch 2014 (v.10.1) Readme

Last revision: 12/12/2013

About This Readme

This document contains important information about Wonderware^® InBatch^™ 2014 (v.10.1). 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 2014 section.

• Release Summary
• System Requirements
• Product Compatibility
• Licensing
• Installing Wonderware InBatch 2014
• Resolved Issues
• Known Issues
• Known Issues – InBatch Documentation
• Updated 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 offers the following new features and enhancements:

• Support for the Invensys License Manager, which allows you to associate licenses with individual nodes on the system to assure correct software usage, install and manage licenses on local and remote nodes, and check the validity of licenses on your system
• Technology update:
• • Support for Wonderware System Platform 2014. See the Compatibility Matrix for detailed information.
  • Support for Foxboro Evo Process Automation System and IA Series 9.0
• 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 2014 software.

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

Hardware Requirements

Minimum Hardware Requirements - Client

The following hardware is recommended to support Wonderware InBatch 2014 on a Client installation:

• Processor: 1.8 gigahertz (GHz)
• Cores: 2
• RAM: 2 gigabytes (GB)
• Hard disk: 30 GB available
• Video adapter and monitor with 1280 x 1024 resolution
• Network Speed (MBPS): 1000
• CD-ROM or DVD drive for installation
• Keyboard
• Mouse or compatible pointing device

Minimum Hardware Requirements - Server

The following hardware is recommended to support Wonderware InBatch 2014 oa Server installation:

• Processor: 2.8 gigahertz (GHz)
• Cores: 4
• RAM: 8 gigabytes (GB)
• Hard disk: 500 GB available
• Video adapter and monitor with 1024 x 768 resolution
• Network Speed (MBPS): 1000

Minimum Hardware Requirements - Operating System

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 Server 2012	http://technet.microsoft.com/library/jj134246#BKMK_sysreq
Windows Server 2012 R2	http://technet.microsoft.com/library/dn303418.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
Windows 8 / Windows 8.1	http://windows.microsoft.com/en-us/windows-8/system-requirements

Operating System Requirements

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

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

Client Windows OS

Server Windows OS

.NET Framework

Virtualization

XP SP3 Professional (32-bit)

Vista (all versions)

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

8 Professional, Enterprise (32/64-bit)

8.1 Professional, Enterprise (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 SP1 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

InBatch Server

N

N

N

N

N

Y

Y

Y

Y

Y

Y

C

C

Y

Y

Y

Y

InBatch Clients

Y

Y

Y

Y

Y

Y

Y

Y

Y

Y

Y

C

C

Y

Y

Y

Y

InBatch History Server

N

N

N

N

N

Y

Y

Y

Y

Y

Y

C

C

Y

Y

Y

Y

InBatch Reporting Content

Y

Y

Y

Y

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 "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.
• If a supported version of the Microsoft .NET Framework 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.

Microsoft SQL Server Requirements

	2008 SP3 Express-SSMSE (32-bit)	2008 SP3 Standard, Enterprise (32-bit Only)	2008 R2 SP1 (all versions)	2008 R2 SP2 Express-SSMSE (32-bit)	2008 R2 SP2 Standard, Enterprise (32/64 bit)	2012 (no SP)	2012 SP1 Express-SSMSE (32-bit Only)	2012 SP1 Standard, Enterprise (32/64 bit)
InBatch Server	N/A	N/A	N/A	N/A	N/A	N/A	N/A	N/A
InBatch Clients	N/A	N/A	N/A	N/A	N/A	N/A	N/A	N/A
InBatch History Server	N	Y	Y	N	Y	Y	N	Y
InBatch Reporting Content	*	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 2014 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 2014 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 2014 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
ArchestrA® System Platform	4.5	N	Y
	2012	N	Y
	2012 R2	Y	Y
	2014	Y	Y
Wonderware® InTouch® CE	10.1	N	N
Wonderware® Manufacturing Execution System	4.0	N/A	Y
	4.0 SP1	N/A	N
	4.0 SP2	N/A	Y
	4.5 P01	N/A	Y
Wonderware® InControl™	7.11 SP2 P01	N/A	N
Wonderware® Manufacturing Execution Module	1.0	N/A	N
Wonderware® QI Analyst™	8.0 SP1 P01	N/A	N
	8.0 SP2	N/A	Y
	8.0 SP3	N/A	Y
Wonderware® SCADAlarm™	6.0 SP2 P01	N	N
Wonderware® Intelligence	1.5	N	N
	1.5.100 (2012)	Y	Y
ArchestrA® Workflow™	1.5	N/A	N
	1.6 (2012 SP1)	N/A	N
	1.7 (2012 R2)	N/A	N
	1.8	N/A	N
	1.9 (2012 R2 SP1)	N/A	Y
Wonderware® Production Execution Module	2.1 SP1	N/A	Y
Foxboro® Control System	4.0 (and all Quick Fixes)	N/A	Y
	Foxboro Evo 2014	Y	Y
Wonderware® I/A Series	8.7 (Windows XP, Windows 2003)	Y	Y
	8.8 (Windows 7, Windows 2008)	Y	Y
	9.0 (Windows 7, Windows 2008)	Y	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 2014 supports ArchestrA licensing and ArchestrA.lic license files only, which does not provide the capability to run earlier versions of InBatch software with InBatch 2014 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 2014

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

Please note the Known Issue L00127339: "Machine names in redundant systems must be 12 characters or less."

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

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.

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

L00129712:	(HotFix L00128999): When a view application is converted from an older version to 10.0, during compilation of windows, the "Not connected to BatchServer" message appears four times.
L00129714:	(HotFix L00129376): UnilinkMngr crash did not cause an automatic failure to backup in redundant mode
L00113037:	(HotFix L00127976): New feature - ability to change colors in the SFC to identify different states.
L00125746:	(HotFix L00125535): Batch detail report using 90% of SQL server's CPU.
L00125953:	(HotFix L00125711): UnilinkMngr shuts down randomly after upgrade from InBatch 8.1 SP1 to 9.5 SP1.
L00125954:	(HotFix L00125601): ReportQReader stops responding for unknown reason, causing intermittent batch report generation failure.
L00126291:	(HotFix L00126059): MaterialSrv is not keeping the backup database in sync.
L00126292:	(HotFix L00125833): BatchMngr exits unexpectedly, displaying error "Cannot remove database sync file! [d2dt.c 1249 (error:2)]."
L00126293:	(HotFix L00125832): MaterialSrv automation server is logging blank messages to the SMC logger.
L00126796:	(HotFix L00126784): In some cases, no destination unit is allocated for a transfer phase.
L00126802:	(HotFix L00126787): System reports change in equipment status when new value is the same as the old value.
L00127199:	(HotFix L00113208): BatchMngr does not set Phase Hold if it receives delayed Phase Run after a Batch is Held (Batch-Phase Status option enabled to tie Batch and Phase actions together).
L00127601:	(HotFix L00127229): Batch GUI controls may cause error if multiple connections exist between units.
L00127603:	(HotFix L00127000): Batch Journal report takes longer than expected to run.
L00128343:	(HotFix L00127408): Update Runtime function can leave redundant system in wrong state if backup is offline.
L00128386:	(HotFix L00125678): IBMX displays error message "Timeout on START UPDATE tag request (waiting for good quality) - returning bad quality. Current quality [0x40]."
L00128552:	If the recipe XML contains a non-integer value for any or all of the Batch Size elements, the import function drops the decimal and changes the value to an integer.
L00128609:	(HotFix L00128416): Set Transition infinitely retries tag write.

< top of document >

Known Issues

This section describes important known issues.

• Installation Issues
• Other 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: 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 InBatch development client. Use the following workaround: Open a Microsoft Windows Explorer page Navigate to C:\Programs\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.
L00127339:	Machine names in redundant systems must be 12 characters or less.
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 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 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 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

L00129734:	User Guide Document needs update for new feature - "ability to change colors in the SFC to identify different states."
L00127895:	User Guide Document incorrectly states that you cannot perform an Update Configuration command on a running system.
L00126096:	User can add an optional parameter "x" for UnilinkMngr to set the disconnect client timeout value. If the user does not specify a value, the default of 15 seconds is used. When this parameter is enabled, UnilinkMngr will disconnect clients sending bad requests / responses, and will log a warning message, "Client disconnected as UnilinkMngr received a bad request/response." This function will also cause timeouts of reads and writes corresponding to the "x" parameter.
L00129265:	User Guide Document contains unused options for IBMX - "Verbose Mode" and "No Poke Acks". These options are no longer supported, and Verbose Mode has been replaced by a Trace log flag in the ArchestrA Logger
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.

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