Wonderware InBatch Version 9.5 with SP1
Wonderware InBatch Version 9.5 with SP1 Readme
Last revision: 5/24/2012
About This Readme
This document contains important information about Wonderware® InBatch version 9.5 with SP1. Review this document for known issues and changes to the InBatch software and documentation included on this CD.
This Readme includes information about Wonderware InBatch version 9.5 with SP1 and InBatch 9.5. The information is ordered based on when Wonderware InBatch versions were released. Use the following links to the various sections of this Readme.
Important! Review the Installing Wonderware InBatch 9.5 with SP1 section prior to upgrading your system. |
Wonderware InBatch 9.5 with SP1 Release Notes
- Release Summary - Wonderware InBatch 9.5 with SP1
- System Requirements - Wonderware InBatch 9.5 with SP1
- Product Compatibility - Wonderware InBatch 9.5 with SP1
- Licensing - Wonderware InBatch 9.5 with SP1
- Installing Wonderware InBatch 9.5 with SP1
- Resolved Issues – InBatch 9.5 with SP1
- Known Issues - InBatch 9.5 with SP1
- Known Issues – InBatch 9.5 with SP1 Documentation
- Updated Wonderware InBatch 9.5 with SP1 Documentation
Wonderware InBatch 9.5 Release Notes
- Release Summary - Wonderware InBatch 9.5
- System Requirements - Wonderware InBatch 9.5
- Product Compatibility - Wonderware InBatch 9.5
- Licensing - Wonderware InBatch 9.5
- Installing Wonderware InBatch 9.5
- Resolved Issues – InBatch 9.5
- Known Issues - InBatch 9.5
- Known Issues – InBatch 9.5 Documentation
- Updated Wonderware InBatch 9.5 Documentation
Wonderware InBatch Version 9.5 with SP1 Readme
Release Summary
Wonderware InBatch 9.5 with SP1 offers the following new features and enhancements:
- Maintenance of Line product improvements by addressing issues reported by customers.
- Addressed high priority security vulnerabilities, and includes previously released InBatch™ 9.5 Security Update 00116779.
- Technology updates which include:
- Compatibility with the new Foxboro Control Software 3.1.
- Support for Windows 2008 R2 Hyper-V HA (High Availability) and DR (Disaster Recovery) features. For more information, refer to available support documentation on the WDN.
- Improved diagnostics with enhanced error and warning messages.
- Includes previously released hot fixes delivered since the InBatch 9.5 release.
System Requirements - Wonderware InBatch 9.5 with SP1
This section describes the hardware, software, and operating system required to install the Wonderware InBatch version 9.5 with SP1 software.
- Hardware Requirements
- Software Requirements
- Database Requirements
- Operating System Requirements
- I/A Series Operating System Requirements
- I/A Series Additional Software Requirements
- Additional Software Requirements
- Wonderware InBatch Firewall Exceptions List
Hardware Requirements
Minimum Hardware Requirements
The following hardware is recommended to support Wonderware InBatch 9.5 with SP1:
- 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 super VGA (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 |
Software Requirements
You must install Microsoft .NET Framework 3.5 SP1 before installing Wonderware InBatch 9.5 with SP1. If this version of the .NET Framework is not installed on the computer, the Wonderware InBatch installation automatically installs it.
I/A Series, InFusion and Foxboro Control Software configurations are supported only on certain operating systems and platforms.
Restriction
- InBatch 9.5 with SP1 is not supported on a single node running on Windows XP SP3. Windows XP SP3 32-bit does not support IIS 6.0, so the InBatch History Server feature cannot be installed.
Database Requirements
Microsoft SQL Server
Version | Type |
Service Pack Level |
Microsoft SQL Server 2005 | Standard or Enterprise Edition |
SP3 |
Microsoft SQL Server 2008 | Standard or Enterprise Edition |
SP1, SP3* |
Microsoft SQL Server 2008 R2 | Standard or Enterprise Edition |
- |
*Note: Check if other products that use the same Operating System as InBatch 9.5 with SP1 are compatible with Microsoft SQL Server 2008 SP3.
Operating System Requirements
The following table lists the operating systems that are supported and can be installed on computers that run Wonderware InBatch:
Operating Systems |
Service Pack Level |
Wonderware InBatch Features |
||||||
Server |
Run-time Client |
Development Client |
History Server |
Reporting Content |
Redundant System |
|||
Windows Server 2003 R2 Standard | 32-bit only | SP2 |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Windows Server 2003 R2 Enterprise | 32-bit only | SP2 |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Windows Server 2008 Standard | 32-bit & 64-bit | SP2 |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Windows Server 2008 Enterprise | 32-bit & 64-bit | SP2 |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Windows Server 2008 R2 Standard | 32-bit & 64-bit | SP1* |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Windows Server 2008 R2 Enterprise | 32-bit & 64-bit | SP1* |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Windows Vista Business | 32-bit & 64-bit | SP2 |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Windows Vista Enterprise | 32-bit & 64-bit | SP2 |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Windows Vista Ultimate | 32-bit & 64-bit | SP2 |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Windows XP Professional | 32-bit only | SP3 |
Yes |
Yes |
Yes |
No |
No |
Yes |
Windows 7 Professional | 32-bit & 64-bit | SP1* |
No |
Yes |
Yes |
No |
Yes |
Clients only |
Windows 7 Enterprise | 32-bit & 64-bit | SP1* |
No |
Yes |
Yes |
No |
Yes |
Clients only |
* - Supported with and without Service Pack
Notes:
I/A Series Operating System Requirements
The following table lists the I/A Series operating systems requirements for each station type:
Operating Systems |
Service Pack Level |
I/A Series and Foxboro Control Software Batch Station Type |
||||||
Server |
Run-time Client |
Development Client |
History Server |
Reporting Content |
Redundant System |
|||
P90/P91 Windows Server 2003 R2 | 32-bit only | SP2 |
Yes |
Yes |
Yes |
Yes |
- |
Yes |
P92 Windows XP | 32-bit only | SP3 |
Yes |
Yes |
Yes |
- |
- |
Yes |
Notes:
I/A Series Additional Software Requirements
The following table lists the additional software requirements of each station type for I/A Series:
Additional Software Requirements |
I/A Series and Foxboro Control Software Batch Station Type |
|||||
Server |
Run-time Client |
Development Client |
History Server |
Reporting Content |
Redundant System |
|
Foxboro Control Software 3.0 and 3.1 |
Yes |
- |
- |
- |
- |
Yes |
I/A Series Software 8.6 and 8.7 | Yes |
- |
- |
- |
- |
Yes |
Foxboro Control Software 3.1 InFusion View | - |
Yes |
- |
- |
- |
- |
Foxboro Control Software 3.1 IEE | - |
- |
Yes |
- |
- |
- |
Internet Information Services (IIS) 6.0 or 7.0 | - |
- |
- |
Yes |
- |
- |
Wonderware Information Server with ArchestrA Reports feature | - |
- |
- |
- |
Yes |
- |
Additional Software Requirements
The following table lists the additional software requirements for each InBatch station type:
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 (only when integrating with System Platform and InFusion) |
Yes |
- |
Yes |
- |
- |
- |
Wonderware InTouch 10.1 or higher | - |
Yes |
- |
- |
- |
- |
Internet Information Services (IIS) 6.0 or 7.0 | - |
- |
- |
Yes |
- |
- |
Wonderware Information Server with ArchestrA Reports feature | - |
- |
- |
- |
Yes |
- |
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 | - |
Product Compatibility - Wonderware InBatch 9.5 with SP1
Wonderware InBatch version 9.5 with SP1 is compatible and can co-exist with the following products:
- ArchestrA System Platform 2012
- Wonderware Application Server 3.5
- Foxboro Control Software 3.0 and 3.1
- I/A Series Software 8.4.3, 8.5, 8.6 and 8.7
- Wonderware InTouch® 10.5
- Wonderware Historian 9.0 P02 and 10.0 SP1
- Wonderware Historian Client 10.0 SP1 and 10.0 SP2
- Wonderware Information Server 4.0 and 4.5
- DIObjects 4.1 SP2
Licensing
Wonderware Component Licensing
Please contact your local Invensys Distributor or Sales representative for details about the licensing requirements for Wonderware components.
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 MES under the license from Microsoft.
Installing Wonderware InBatch 9.5 with SP1
For installation and upgrade instructions, see the InBatch Installation Guide.
Upgrading from Wonderware InBatch 9.0 and Wonderware InBatch 9.5 to Wonderware InBatch 9.5 with SP1 is automatic. 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 9.5 with SP1.
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.
Upgrading platforms which use the InBatch Stateless API
The following InBatch Stateless API methods have been modified to include DoneBy and CheckBy (DoneBy, DoneByPswd, CheckBy, CheckByPswd) arguments:
1. AddScheduleEntry
2. DeleteScheduleEntry
3. InitializeScheduleEntry
The AddScheduleEntry, DeleteScheduleEntry,and InitializeScheduleEntry methods use the security set for Access Schedule method. Use the security authentication set required for Access Schedule method of the Batch Client application.
To upgrade platforms which use the InBatch Stateless API
Any code or scripting that is using the AddScheduleEntry, DeleteScheduleEntry,and InitializeScheduleEntry methods will need to be modified. The following are the upgrade instructions:
- The InBatch upgrade needs to be run on all InBatch Runtime Client and Batch Server systems. This includes any WAS platforms that have InBatch API scripting deployed and running.
- Before running the InBatch upgrade, it is best to undeploy all WAS platforms that are deployed to a Batch Runtime Client or Batch Server.
- Install the InBatch upgrade and re-import the InBatch API DLL's into the Galaxy (see InBatch API Help file for details of importing DLL's).
- The upgrade may break existing scripts functionality. Verify future Known Issues in the InBatch 9.5 with SP1 Documentation section for changes in scripting that may be required for the scripts to work.
- Redeploy all platforms, engines, and objects as needed.
Resolved Issues - Wonderware InBatch 9.5 with SP1
This section describes all the resolved issues in Wonderware InBatch 9.5 with SP1.
L00117770: (Hot Fix 00117578) SR 103122817: This solves a problem where newly installed InBatch 9.0 SP2 History Server installations are not adding a system message (55001) to the SQL Server system message catalogue.
A problem occurs when four security access failures happen within three minutes of each other as it will cause an Audit Event record to be written to the ErrorQ table. This message will be stuck in the ErrorQ table, because of the missing message.
L00117823: SR 103123248: The Recipe Edit's Recipe header product name and product ID box only allowed for 16 characters. However, if more than 16 characters were entered it was corrupting data. The UI fields are now restricted to 16 characters. L00118246: (Hot Fix 00117799) SR 103123226: The Recipe Editor’s feature 2 verses 3 level process Variable window was showing corrupt data in the 2 level views.
Known Issues - Wonderware InBatch 9.5 with SP1
This section describes all the known issues in Wonderware InBatch 9.5 with SP1.
Known Issues – InBatch 9.5 with SP1 Documentation
The following table lists the known issues in the product documentation:
ItemLocation of ChangeExisting DocumentationChange InBatch Stateless API
In the InBatch Stateless API Reference Guide, under InBatch.API Namespace / Classes / Schedule / Methods, see the following 3 API calls:
1. AddScheduleEntry
2. DeleteScheduleEntry
3. InitializeScheduleEntryMissing
The following InBatch Stateless API methods have been modified to include DoneBy and CheckBy (DoneBy, DoneByPswd, CheckBy, CheckByPswd) arguments:
1. AddScheduleEntry
2. DeleteScheduleEntry
3. InitializeScheduleEntryThese methods use the security set for Access Schedule method. Use the security authentication set required for Access Schedule method of the Batch Client application. The following description provides an overview of the methods:
- AddScheduleEntry()
This method adds a new entry to the schedule, following the previous entry, for the given CLB (Campaign, Lot, Batch). If there is no entry in the schedule, the new entry is added to the beginning of the schedule. It may require DoneBy and CheckBy parameters, if security is enabled for the AddScheduleEntry functionality.
Syntax:
InBatch.API.Schedule.AddScheduleEntry (previousCampaign, previousLot, previousBatch, campaign, lot, batch, recipe, train, size, mode, doneById, doneByPassword, checkById, checkByPassword);
- DeleteScheduleEntry()
This method deletes the schedule entry with Open, Done, or Aborted status for the given CLB. It may require DoneBy and CheckBy parameters, if security is enabled for the DeleteScheduleEntry functionality.
Syntax:
InBatch.API.Schedule.DeleteScheduleEntry (campaign, lot, batch, doneById, doneByPassword, checkById, checkByPassword);
- InitializeScheduleEntry()
This method initializes schedule entry for the given CLB. It may require DoneBy and CheckBy parameters, if security is enabled for the InitializeScheduleEntry functionality.
Syntax:
InBatch.API.Schedule.InitializeScheduleEntry (campaign, lot, batch, doneById, doneByPassword, checkById, checkByPassword);For upgrading instructions, see Installing Wonderware InBatch 9.5 with SP1.
InBatch User's Guide
Missing
The Batch Display, Batch Schedule, and Batch View methods can take two host names for the -A command line parameter, separated by a semicolon (;).
The two host names must be the names of the master and the backup batch servers in a redundant configuration.
At startup, the runtime application determines which host is the master and then connects to it.
For example:
BatchDspl.exe -Ahost1;host2
Updated Wonderware InBatch 9.5 with SP1 Documentation
The Wonderware InBatch documentation set includes the following updated documents:
- ReadMe (This document) - Provides information about software and hardware requirements, known issues, licensing, and documentation updates.
The complete Wonderware InBatch 9.5 product library consists of a set of Portable Document Files (PDF) located in the Docs 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 9.5 installation instructions are located in the root folder of the Wonderware InBatch 9.5 installation CD, as a .chm file. You can view these instructions by clicking the Help when you start the Wonderware InBatch 9.5 installation procedure.
Wonderware InBatch Version 9.5 Readme
Last revision: 09/1/2011
Release Summary - Wonderware InBatch 9.5
Wonderware InBatch 9.5 offers the following new features and enhancements:
- InBatch supports :
- Windows Vista SP2 Ultimate (32-bit and 64-bit) and Business (32-bit and 64-bit) editions
- Windows 7 SP1 Professional (32-bit and 64-bit) and Enterprise (32-bit and 64-bit) editions
- Windows 2008 R2 SP1 Standard (32-bit and 64-bit) and Enterprise (32-bit and 64-bit) editions
- InBatch History database administration can now be accessed by using Internet Explorer 9.0.
- InBatch Reports can now be accessed by using Internet Explorer 9.0.
- InBatch History Server can now be installed on SQL Server 2008 R2.
- InBatch Reports now support regional settings for date and time formats.
- InBatch now supports logging data from multiple Batch Servers to a centralized History Server.
- Recipe names can now be up to 128 characters in length, so that the names can be same as in the ERP system.
- The Recipe Editor can now support the import and export of recipes in an XML based industry standard BatchML- BatchInformation Version 0401 schema with extensions where needed.
- The new InBatch stateless API interacts with the batches in a stateless manner by using the .NET Framework.
- BatchMngr and the Runtime Clients are now capable of handling Bad Quality I/O status.
System Requirements - Wonderware InBatch 9.5
This section describes the hardware, software, and operating system requirements to install the Wonderware InBatch version 9.5 software.
- Hardware Requirements
- Software Requirements
- Database Requirements
- Operating System Requirements
- I/A Series Operating System Requirements
- I/A Series Additional Software Requirements
- Additional Software Requirements
- Wonderware InBatch Firewall Exceptions List
Hardware Requirements
Minimum Hardware Requirements
The following hardware is recommended to support Wonderware InBatch 9.5:
- Processor - 3.0 gigahertz (GHz) or faster processor
- RAM - 2 gigabyte (GB) of memory
- Hard disk - At least 4 GB of available disk space
- Super VGA (1024 × 768) or higher-resolution video adapter and monitor
- 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 Software Requirements
You must install Microsoft .NET Framework 3.5 SP1 before installing Wonderware InBatch 9.5. If this version of the .NET Framework is not installed on the computer, the Wonderware InBatch installation automatically installs it.
I/A Series, InFusion and Foxboro Control Software configurations are supported only on certain operating systems and platforms.
Restriction
- InBatch 9.5 is not supported on a single node running on Windows XP SP3. Windows XP SP3 32-bit does not support IIS 6.0, so the InBatch History Server feature cannot be installed.
Database Requirements
Microsoft SQL Server
Version TypeService Pack
LevelMicrosoft SQL Server 2005 Standard or Enterprise EditionSP3Microsoft SQL Server 2008 Standard or Enterprise EditionSP1Microsoft SQL Server 2008 R2 Standard or Enterprise Edition-Operating System Requirements
The following table lists the operating systems that are supported and can be installed on computers that run Wonderware InBatch:
Operating SystemsService Pack LevelWonderware InBatch FeaturesServerRun-time
ClientDevelopment
ClientHistory
ServerReporting
ContentRedundant
SystemWindows Server 2003 R2 Standard 32-bit only SP2YesYesYesYesYesYesWindows Server 2003 R2 Enterprise 32-bit only SP2YesYesYesYesYesYesWindows Server 2008 Standard 32-bit & 64-bit SP2YesYesYesYesYesYesWindows Server 2008 Enterprise 32-bit & 64-bit SP2YesYesYesYesYesYesWindows Server 2008 R2 Standard 32-bit & 64-bit SP1*YesYesYesYesYesYesWindows Server 2008 R2 Enterprise 32-bit & 64-bit SP1*YesYesYesYesYesYesWindows Vista Business 32-bit & 64-bit SP2YesYesYesYesYesYesWindows Vista Enterprise 32-bit & 64-bit SP2YesYesYesYesYesYesWindows Vista Ultimate 32-bit & 64-bit SP2YesYesYesYesYesYesWindows XP Professional 32-bit only SP3YesYesYesNoNoYesWindows 7 Professional 32-bit & 64-bit SP1*YesYesYesYesYesYesWindows 7 Enterprise 32-bit & 64-bit SP1*YesYesYesYesYesYes* - Supported with and without Service Pack
Notes:
- For InBatch add-on for Win-XML Exporter software requirements, see software requirements for Wonderware Information Server.
- For InBatch IDE/IEE Extension software requirements, see software requirements for Wonderware Application Server.
I/A Series Operating System Requirements
The following table lists the I/A Series operating systems requirements for each station type:
Operating SystemsService Pack LevelI/A Series and Foxboro Control Software Batch Station TypeServerRun-time
ClientDevelopment
ClientHistory
ServerReporting
ContentRedundant
SystemP90/P91 Windows Server 2003 R2 32-bit only SP2YesYesYesYes-YesP92 Windows XP 32-bit only SP3YesYesYes--YesNotes:
- For InBatch Reporting Content software requirements, see software requirements for Wonderware Information Server.
- For InBatch add-on for Win-XML Exporter software requirements, see software requirements for Wonderware Information Server.
- For InBatch IDE/IEE Extension software requirements, see software requirements for Wonderware Application Server.
I/A Series Additional Software Requirements
The following table lists the additional software requirements of each station type for I/A Series:
Additional Software RequirementsI/A Series and Foxboro Control Software Batch Station TypeServerRun-time
ClientDevelopment
ClientHistory
ServerReporting
ContentRedundant
SystemFoxboro Control Software 3.0
(with I/A Series Software 8.6)
Yes----YesI/A Series Software version 8.5 and version 8.6 Yes----YesFoxboro Control Software 3.0 InFusion View -Yes----Foxboro Control Software 3.0 IEE --Yes---Internet Information Services (IIS) 6.0 or 7.0 ---Yes--Wonderware Information Server with ArchestrA Reports feature ----Yes-Additional Software Requirements
The following table lists the additional software requirements for each InBatch station type:
Additional Software RequirementsWonderware InBatch Station TypeServerRun-time
ClientDevelopment
ClientHistory
ServerReporting
ContentRedundant
SystemWonderware Application Server bootstrap and IDE
(only when integrating with System Platform and InFusion)
Yes-Yes---Wonderware InTouch 10.1 or higher -Yes----Internet Information Services (IIS) 6.0 or 7.0 ---Yes--Wonderware Information Server with ArchestrA Reports feature ----Yes-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 NamePort NumberBatchMngr 9008EnvMngr 9002InfoMngr 9012HistQMngrvista 9015HisQReader 9016InBatch Middleware Access 8199OLE Recipe Automation 5001OLE Recipe Automation 5002OLE Recipe Automation 5003OLE Recipe Automation 5004OLE Recipe Automation 5005RedMngr 9006RedMngrX 9013RedMngrX2 9014SecMngr 9004UnilinkMngr 9007aaLogger.exe -RecipeEdit.exe -TagLinker.exe -MaterialSrv.exe -
Product Compatibility - Wonderware InBatch 9.5
Wonderware InBatch version 9.5 is compatible and can co-exist with the following products:
- Wonderware Application Server 3.1 SP1, 3.1 SP2, 3.1 SP2 P01, and 3.1 SP3 P01
- ArchestrA System Platform 4.0 and 4.5
- Foxboro Control Software 3.0
- I/A Series Software 8.4.3, 8.5, and 8.6
- Wonderware InTouch® 10.1 SP1, 10.1 SP2, 10.1 SP2 P01, and SP3 P01
- Wonderware Historian 9.0 P02 and 10.0 SP1
- Wonderware Historian Client 10.0 SP1
- Wonderware Information Server 4.0 and 4.5
- DIObjects 4.1 SP2
Licensing
Wonderware Component Licensing
Please contact your local Invensys Distributor or Sales representative for details about the licensing requirements for Wonderware components.
Microsoft Office Fluent UI Licensing
The 2007 Microsoft Office Fluent User Interface is subject to protection under U.S. and international intellectual property laws, and is used by Wonderware MES under the license from Microsoft.
Installing Wonderware InBatch 9.5
For detailed installation and upgrade instructions, see the InBatch Installation Guide.
To upgrade from a version older than Wonderware InBatch 9.0, you must uninstall the previous version. After uninstalling the previous version run the Setup.exe from the InBatch 9.5 CD to complete the install.
To Upgrade from Wonderware InBatch 9.0, InBatch 9.0 with SP1, or InBatch 9.0 with SP2 to Wonderware InBatch 9.5 run SETUP.exe from the InBatch 9.5 CD and the process will automatically upgrade all installed InBatch components.
The upgrade supports Wonderware InBatch 9.0 with and without the I/A components.
Note: IBCli no longer ignores or retries bad quality. See the “Parm Timeout” option of BatchMngr in the “InBatch Users Guide – Chapter 2” for more details on configuring retries of I/O with Bad Quality.
Resolved Issues - Wonderware InBatch 9.5
This section describes all the resolved issues in Wonderware InBatch 9.5.
L00114247: (HotFix 2478) SR 103120585: While performing a clean up or Initialize All from the Batch Schedule, the SFC in the Batch Display returns to the beginning of the recipe that is running or displayed.
Known Issues - Wonderware InBatch 9.5
This section describes all the known issues in Wonderware InBatch 9.5.
Installation Issues
L00079361: When the InBatch Development Client is installed, files that cannot be deleted are not listed in a message.
When you uninstall an InBatch component (server or client), remove all items that may have been left behind, including the \InBatch folder.
L00079872: In the Feature Selection list of the InBatch Setup dialog box, "1" appears on the icon for the InBatch Development Client.
The following steps are a workaround for this problem. The final step removes the number 1 and does not produce any changes to the installed state:
- Install the InBatch development client and the InBatch run-time clients.
- Launch setup.exe.
- In the Application Maintenance dialog box, click Modify and then click Next.
- Uninstall the InBatch run-time client by deselecting it and install the InBatch PDF documentation. As a result, the InBatch PDF documentation is successfully installed and the In Batch run-time client is successfully uninstalled.
- Modify and select the InBatch development client that displays the number 1 and install the InBatch development client.
L00081166: An error message appears during the installation of InBatch Server with I/A components.
This message can appear if you select the root directory of the C:\ drive. Click OK and the installation will continue and complete successfully.
L00082077: When InBatch cannot find a valid attribute referenced in ArchestrA, the batch stops.
Use the following workaround for this issue:
- Start IBMX services in Advise All mode. In the Advise All mode, IBMX advises all Galaxy tags during services start-up.
- Check the Log Viewer for any configuration errors.
- If you do not find configuration errors, stop all services.
- Remove the Advise All mode.
- Start the services.
- Schedule and run the batch.
L00082238: An error dialog box appears when uninstalling InBatch. This error prevents the uninstall from completing.
- The following steps are a workaround to this problem. Step 6 allows the selection to be uninstalled without any issue when this error occurs.
- Install InBatch Server.
- Double-click setup.exe, select Modify, and click Next.
- From the Select Features list, deselect InBatch Server and select InBatch Development Client (without I/A support).
- Continue the installation to completion.
- Click Modify.
- Select the InBatch Development Client (a 1 appears on the image) and click Next to install the development client.
- Perform uninstall from the Control Panel (select Add/Remove Programs).
L00104903: Upgrading a computer to Windows 2008 SP2 or later with InBatch already installed will fail.
To fix this, use the UpgradeFix.exe located in the \InBatch Upgrade Tool folder on the InBatch CD.
L00106413: If InBatch Server fails to start after installing on Windows XP SP3, you must restart the InBatch Server node. L00106446: When installing Batch Server with IA Components on an I/A Series 8.5 system, you should have at a minimum Fox API 4.3.2 with QF1012359.
After installing this QF, remove the foxapi.dll from the \system32 directory and add D:\opt\fox\ais\bin to the "Path" System Variable in the Environment Variable section of the Computer Properties Advanced tab.
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
L00016907: WinXMLExporter does not recognize InBatch 8.1 ActiveX controls as "WONDERWARECONTROL" although they have an entry in the CFGOCX.xml file.
The workaround is to look in the 3rd Party Controls folder.
L00077400: Editors are not opening on the InBatch development client.
Use the following workaround:
- Open Windows Explorer.
- Navigate to C:\Programs\Wonderware\InBatch\cfg\Config_A.
- Right-click the file named vista.taf and select Delete.
L00079952: [IBMX Component] --- IBMX is crashing when services are stopped after undeploying and deploying Entire Galaxy.
Stop all the InBatch Services before you undeploy the entire galaxy.
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.
Type the System administrator's user name and grant the roles by selecting the check box for the Content Manager option.
L00106167: If the InBatch Server computer name contains lowercase characters, the development client applications will always get a TAF-lockmgr synchronization error. To fix this issue edit the InBatch Development Client shortcut links in the Start menu to contain the exact case spelling of the InBatch Server name.
After using the InBatch Configuration Utility to configure the InBatch Development Client, do the following.
- On the development client, use the Start menu to navigate to Wonderware\InBatch\InBatch Development Client [Your InBatch Server Name].
- Right-click on Material Editor shortcut and then click Properties. In the target box you will see the following string… a.–AINBATCHSERVERNAME
- Change the spelling of your InBatch Server name to the correct case spelling of your InBatch Server computer. Note: Do not add a space between “-A” and your InBatch Server name.
- Do this for each shortcut that has [Your InBatch Server Name] in the name.
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 (WIS) portal against a large recipe can result in a timeout.
L00116084: When printing recipes the Recipe Name overlaps the page header information when outputting in Postscript format.
Known Issues – InBatch 9.5 Documentation
This table lists known issues in the product documentation:
Item Location of Change Existing Documentation Change None
Updated Wonderware InBatch 9.5 Documentation
The Wonderware InBatch documentation set includes the following documents:
- Wonderware InBatch Installation Guide - Provides information about upgrading from the previous InBatch versions to InBatch 9.5.
- Wonderware InBatch User Guide - Provides information about the new features and enhancements.
- Wonderware InBatch COM Technical Reference Guide - This guide describes using the InBatch COM technology and provides practical examples of its use.
- Wonderware InBatch Stateless API Online Reference - Provides information about the new stateless API supported by the Batch Server.
- ReadMe (This document) - Provides information about software and hardware requirements, known issues, licensing, and documentation updates.
The Wonderware InBatch 9.5 product library consists of a set of Portable Document Files (PDF) located in the Docs 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 9.5 installation instructions are located in the root folder of the Wonderware InBatch 9.5 installation CD, as a .chm file. You can view these instructions by clicking the Help when you start the Wonderware InBatch 9.5 installation procedure.
© 2012 Invensys Systems, Inc. All Rights Reserved.