Wonderware InBatch 2017 u01 (12.1)

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

Batch Management 2017 Update 1 Readme

Batch Management 2017 Update 1 Readme

Last revision: 8/8/2019

This document contains important information about Batch Management 2017 Update 1 (v.12.1). Review this document for known issues and changes to the Batch Management software and documentation included on this CD.

In This Document

Release Summary

Minimum System Requirements

Product Compatibility

Licensing

Installing Batch Management 2017 Update 1

Resolved Issues

Known Issues

Known Issues - Documentation

Batch Management Documentation

Resource File

Release Summary

Batch Management 2017 Update 1 (v.12.1) offers the following new features and enhancements:

  • Unit-Centric Batch Management in InTouch OMI view

    Users can now open and log on to the Batch Management application in unit-centric InTouch OMI view, which enables users to monitor batches specific to a Unit.

  • Support for TLS 1.2

    Batch Management is now compatible with the latest version of transport layer security (TLS 1.2) for enhanced security.

  • Support for System Platform 2017 Update 3 and System Platform 2017 Update 3 SP1

    Support has been added for Shared Components of System Platform 2017 Update 3 and System Platform 2017 Update 3 SP1.

Minimum System Requirements

This section describes the hardware, software, and operating system required to install the Batch Management software.

  • Hardware Requirements
  • Operating System Requirements
  • Browser Requirements
  • Microsoft SQL Server Requirements
  • Additional Software Requirements
  • Firewall Exceptions Lists

Hardware Requirements

Minimum Hardware Requirements

The following hardware is recommended to support Batch Management:

Hardware 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 Batch Management 2017 Update 1.

Operating System

Client

Windows OS

Server

Windows OS

.NET Framework

Virtualization

 

8.1

Professional,

Enterprise

(32/64-bit)

10
(Build 1607 +)

Professional and Enterprise (32/64-bit)

2012

Standard,

Data Center (64-bit)

2012 R2

Standard,

Data Center (64-bit)

2016

Standard,

Data Center (64-bit)

2019

Standard,

Data Center (64-bit)

3.5.1

4.7.2

Hyper-V

(Based on Supported OS version)

VMWare 6.0 Update 1

(including HA/DR*)

VMWare Clients (including Horizon - App Virtualization)

Cloud Virtualization - Azure

VMWare Workstation 11 and higher

Batch Management Server

N

N

Y

Y

Y

Y

C

Y

Y

Y

Y

Y

Y

Batch Management Clients

Y

Y

Y

Y

Y

Y

C

Y

Y

Y

Y

Y

Y

Batch Management History Server

N

N

Y

Y

Y

Y

C

Y

Y

Y

Y

Y

Y

Batch Management Reporting Content

Y

Y

Y

Y

Y

Y

C

Y

Y

Y

Y

Y

Y

Supported

 

Y

Not Supported

N

Products do not share data directly, but can coexist.

N/A

Notes:
- For software requirements for the "Batch Management Components for ArchestrA IDE" feature, see the software requirements for Application Server.
- For software requirements for the "Batch Management Reporting Content" feature, see the software requirements for Microsoft SQL Server.
- If a supported version of the Microsoft .NET Framework is not installed, the Batch Management installation automatically installs it.

Browser Requirements

Application Name

Supported Version

Internet Explorer

Version 11 or later on the Windows operating system*

Microsoft Edge

Version 20

Google Chrome

Version 47 or later on the Windows operating system*

Firefox

Version 44 or later on the Windows operating system*

* Unless later versions of browsers deprecate the user interfaces used by Batch Management Reporting System.

Microsoft SQL Server Requirements

The following table lists the Microsoft SQL Server requirements.

 

2012 Standard, Enterprise
No SP, SP1, and SP2 (32/64 bit)

2012 SP2 Express -
SSMSE -
No SP, SP1, and SP2
(32/64 bit)

2014 Standard, Enterprise No SP, SP1, and SP2 (32/64 bit)

2014 Express-SSMSE No SP, SP1, and SP2 (32/64 bit)

2016 Standard, Enterprise

(32/64 bit)

2016 Express-
SSMSE
No SP and SP1
(32/64 bit)

SQL 2017 Standard, Enterprise No SP
(64 bit)

SQL 2017 Express -
SSMSE
No SP
(64 bit)

Batch Management Server

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

Batch Management Clients

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

Batch Management History Server

Y

Y*

Y

Y*

Y

 

Y*

Y

Y*

Batch Management Reporting Content

Y

Y*

Y

Y*

Y

Y*

Y

Y*

Supported

 

Y

Not Supported

N

* History Archive, Purge, and Restore will not work with SQL Express. Reporting only works with Express with Advanced Services and Reporting Scheduling Capabilities will not be available.

Additional Software Requirements

The following table lists the additional typical software requirements for each Batch Management station type when the Batch Management software is used with System Platform (SP):

Additional Software Requirements

Batch Management Station Type

 

Server

Run-time Client

Development Client

History Server

Reporting Content

Redundant System

Application Server bootstrap and IDE

Yes*

-

Yes

-

-

Yes*

InTouch

-

Yes

-

-

-

-

*Application Server IDE is required only during Development for GRAccess, and not during Runtime. IDE is required for Tag Linker Editor for browsing the Galaxy by creating an Access Name. Application Server Bootstrap is required only for Batch Management Server and Redundant Server during Runtime.

Batch Management Firewall Exceptions List

Batch Management requires certain network ports to be opened in the Windows Firewall to establish communication with other components and services on the network. Usually, this is automatically done during the installation and configuration process of Batch Management. However, if the Windows firewall is not enabled at the time of installation or if an alternative firewall is in use during installation, you need to open the appropriate network ports in the firewall manually for proper functioning of Batch Management. The following is a list of ports that must be added to the Windows Firewall exceptions list for Batch Management:

  • TCP port numbers for Batch Management: 8199, 9001 to 9012, 9015, and 9016.
  • UDP port numbers for Batch Management: 9013 and 9014.

Product Compatibility

Batch Management 2017 Update 1 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*

 

2017 Update 3 SP1

Y

Y

2017 Update 3

Y

Y

2017 Update 2

Y

Y

2017 Update 1

Y

Y

2017

Y

Y

2014 R2 SP1

Y

Y

2014 R2 P01

Y

Y

2014 R2

Y

Y

Platform Common Services**

4.3.3

Y

Y

4.2.2

Y

Y

4.0.0.13000

Y

Y

4.1.0

Y

Y

Wonderware® InTouch® CE

10.1

N

N

Wonderware® Manufacturing Execution System (MES)

 

MES 2017

N/A

Y

2014 R3

N/A

Y

2014 R2

N/A

Y

Manufacturing Execution Module

1

N/A

N

Wonderware® Intelligence

 

2017

Y

Y

2014 R3

 

Y

 

Y

 

Wonderware® Skelta BPM

 

2017 R2 U1

N/A

Y

2017

 

N/A

 

Y

 

Foxboro® Control Software

 

7.1

N

N

7.0

 

N

 

N

 

Foxboro® Evo Control Core Services

 

9.4

Y

Y

9.3

Y

Y

9.2

Y

Y

9.1

Y

Y

9.0

Y

Y

Foxboro® I/A Series Software

 

8.8

Y

Y

8.7
(Windows XP, Windows 2003)

N

N

Supported

 

Y

Not Supported

N

Products do not share data directly, but can coexist.

N/A

* Previously called ArchestrA System Platform

** Previously called Wonderware® ASB Framework

In some cases, the Batch Management software is supported in newer environments than a compatible product. The Batch Management 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 Batch Management and Foxboro Control Software, contact AVEVA Software Global Customer Support (GCS).

Licensing

Batch Management enforces licensing through AVEVA Enterprise License Manager.

Licensing Information

Once installed, a link to the AVEVA Enterprise License Manager can be found in the \AVEVA folder on the Start menu.

It can also be accessed by pointing your browser to the following URL:

http://<nodename>/AELicenseManager

where <Nodename> is localhost or the name of the node where the AVEVA Enterprise License Manager is installed.

License Server

The AVEVA Enterprise License Server can be installed separately from the AVEVA Enterprise License Manager.

Installing Batch Management 2017 Update 1

Special Notes

  • Before upgrading, please take note of the known issues in the Installation Issues section of this document.
  • Before installing Batch Management 2017 Update 1 on a node with WSP 2014 R2 SP1, you must install WSP 2014 R2 SP1 GRAccess HotFix CR L00140512.

    Otherwise, you might encounter the following issues:

    • Error while Galaxy browsing from TagLinker
    • ArchestrA security will not work if enabled in Security Editor.

    Note: Prior to upgrading, confirm that your Hist Queue and Error Queue are empty. Because of changes to the Batch Management History database, any data left in the Hist Queue or 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.

  • Starting with 11.5, Batch Management History Server and Reporting Content no longer integrate with Information Server. These features are now available through Start Menu shortcuts. For more information, see the Batch Management Installation Guide and Batch Management User Guide.
  • While installing Batch Management or upgrading to the latest version, you can select and install the Licensing components. For more information about Licensing, see the Batch Management Installation Guide.
  • When Batch Management is upgraded or installed on System Platform 2017 Update 2 or earlier versions, ASB Service instances are not created for a new galaxy. Contact AVEVA Software Global Customer Support (GCS) for System Platform Hotfix.

Installing or Upgrading

For installation and upgrade instructions, see the Batch Management 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)
  • Wonderware InBatch 2014 R2 (10.2)
  • Wonderware InBatch 2014 R2 SP1 (11)
  • Wonderware InBatch 2014 R3 (11.5)
  • Wonderware InBatch 2014 R3 SP1 (11.5.1)
  • Batch Management 2017

The process will upgrade all components as required.

The following is a list of important points that you must note during the upgrade process.

  • Once the upgrade process is completed, you have to run the CVTMaster.exe utility to upgrade the application databases.
  • When you upgrade from previous versions (11.0 or earlier) of InBatch to Batch Management 2017 Update 1, all the InBatch links from Information Server database are removed. You can verify the NavNode, NavRole, NavPanelNode tables from where all InBatch related rows must be removed. The .rdl template files are also removed from the ArchestrA\InBatch Reports folder and are now deployed in the InBatch Reports folder in the Reporting service URL.
  • Users can access the reports from the standard Reporting Services URL or the shortcut menu available in the InBatch folder. The reports will not be available from the Information Server. Also, the History Database Administration and Reports Administration web pages now have their own shortcut menu and is available in the InBatch folder.
  • If you have created custom reports (InBatch versions prior to 11.5) and want to convert them to the latest version of Batch Management, no longer rely on Information Server. For more information, see the Batch Management Custom Report Update Guide (BatchManagementCustRepGuide.pdf).
  • The upgrade supports Batch Management 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 Batch Management 2017 Update 1.
  • When you upgrade InBatch from an earlier version to Batch Management 2017 Update 1, the .CSV message files available at "C:\Program Files\Wonderware\InBatch\Messages" are backed up and are placed at the same location: "C:\Program Files\Wonderware\InBatch\Messages".

    Any new .CSV files are also added to the following folder: "C:\Program Files\Wonderware\InBatch\Messages\English".

  • You need to manually update or copy the resources files to be able to get the correct messages after upgrade from InBatch 11.0. If you have not manually updated the resource files in InBatch v11.0, then you should copy all the resource files. For more information on the list of updated messages in the resource files, refer to the Resource File section.

    Note: If you are using the InBatch GUI Controls and upgrading from 10.2 or earlier, you may need to adjust some of your InTouch application layouts. Some of the controls have been increased in size to better accommodate larger values. Also, a new "Formula" column was added to several list controls.

Resolved Issues

This section describes important resolved issues.

L00154597

"End Of Batch" report of Batch Journal is empty when the ‘Batch Server Name’ system parameter is configured with the Batch Server name.

L00150903

While configuring a recipe instruction to append the unit/connection description, the appended unit/connection description is not reported to batch history in the Phase Instruction Detail messages. The phase instructions only include the instructions (without the appended value).

L00152048

Failed to validate the recipes via Export/Import between two systems.

L00151912

While launching Recipe Editor with OS security, the domain user authentication fails, and the message "Native authentication failed. The data area passed to a system call is too small. [122]" is logged in the SMC logger.

L00152068

Strong name verification failure. Need details to use 11.5.1 RecipeEditorInterop.dll in PowerShell.

L00151177

InBatch GUI Controls inside InTouch appear to be the source of a memory leak.

L00153058

BatchMngr crashes during recipe execution.

L00152941

BatchMngr crashes with warm restart file problem.

L00153094

In .NET & native InTouch application, the Phase button labels are displayed as Units at runtime.

L00153519

Rollback History schema and Report changes made in 11.5 Hot Fix L00149154.

L00153520

InTouch crashes when the value 3 is used for SEC_WINDOWTYPE in BatchSec1.FunctionClearance method.

L00150257

UnlinkMngr.exe is randomly crashing along with BatchMngr and I/A Drive.

L00154109

AuthSessionID is missing or incorrect for Connection Manual Equipment Allocation.

L00153434

"Sleep" command should be updated to "timeout" for etcmds program.

[Doc update in the Environment Management System chapter of the Batch Management User Guide]

L00151636

Offset in the column length with the BatchSchedGetItem method of InBatch BatchSchedList.ocx. Return string is different than described in manual.

[Doc update in the Batch Management ActiveX Control chapter of the Batch Management COM Technical Reference Guide]

L00152506

Recipe or Material automation severs on a 64-bit machine fail to run when they are configured with the 64-bit DCOM settings.

[Doc update in the Material Database Automation Server and Recipe Database Automation Server chapters of the Batch Management COM Technical Reference Guide]

Known Issues

This section describes important known issues.

  • Installation Issues
  • Other Issues

Installation Issues

1213460

When you install Batch Management 2017 Update 1 Update 1 (v. 12.1) on a computer where System Platform 2017 is already installed, ArchestrA IDE is not able to connect to the pre-existing Galaxy or create a new Galaxy.

Workaround: Do the following:

In the Registry Editor, under the "HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\aaGR\" location, delete the Key "DependOnService" which has the value "ArchestrADataStore32".

Also, delete the Key "DependOnService" from the HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Services\aaGR and HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\aaGR locations.

616969

Configuration of the History Server feature fails, when you upgrade InBatch History Server to InBatch version 11.5.1 from versions prior to InBatch 11.0.

 

Before proceeding with the upgrade, ensure that you delete all SQL Jobs related to Archive\Purge\Restore. Prior to InBatch 11.0 version, any SQL Agent jobs (Archive\Purge\Restore jobs) created in InBatch History Server may have been associated with BatchAdminUser, BatchReportAdmin, or BatchUser role. These user roles have been removed in 11.0 release.

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

    If a registry value named 'SessionViewSize' exists, ensure that 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).

L00127339

Machine names in redundant systems must be 12 characters or less.

Other Issues

1055512

Batch Management web client Icons and images are distorted in Mozilla Firefox browsers.

Workaround: Do the following settings in the Firefox browser:

  1. Open the Firefox browser.
  2. Navigate to Options > General.
  3. Under the Performance option, clear the Use recommended performance settings” and Use hardware acceleration when available check boxes.
  4. Restart the browser.

     

455938

When you access the InBatch Reports using Internet Explorer 11, the user interface fields of the Reports header are not displayed correctly.

Note: This issue is reported only on a system with SQL Server 2012.

Workaround: To resolve this issue, add the target site to Compatibility View Settings in Internet Explorer browser.

459424

Ensure that you adjust the InTouch application layouts to account for the new Formula column in the lists, if you are using GuiControl lists (ScheduleEdit.Schedule, BatchView.Batch, and BatchView.AllocationQueue). The width of other GUI Control lists may have also been increased to support better presentation of longer values.

614956

SSRS report execution (i.e. when you open the report and click 'View Report') displays a blank page in the Chrome browser.

 

Workaround: To resolve this error, do the following:

  1. Browse to the Directory where reporting services is installed.

    For example: C:\Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\ReportServer.

  2. Open the file named reportserver.config.
  3. Insert the following line in the document:

    <Configuration >

    .......

    <HTMLViewerStyleSheet > SafariChromeFix </HTMLViewerStyleSheet>

    .......

    </Configuration >

  4. Save the file.
  5. Navigate to C:\Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\ReportServer\Styles directory.
  6. Make a copy of the file named SP_Full.css, and name the copy SafariChromeFix.css.
  7. Update the following lines to the top in the SafariChromeFix.css file:

    div { overflow: visible !important; }

  8. Save and close the file.

    All the existing reports on this instance of Reporting Services are displayed on all browsers including Chrome and Safari.

     

    Note: The reportserver.config may be overwritten with updates to reporting services. In such cases, add the <HTMLViewerStyleSheet > SafariChromeFix </HTMLViewerStyleSheet> tag into the config file every time.

     

L00077400

Editors are not opening on the Wonderware InBatch development client.

 

Workaround:

  1. Open a Microsoft Windows Explorer page.
  2. Navigate to C:\Programs\Wonderware\Wonderware InBatch\cfg\Config_A.
  3. Right-click the file vista.taf, and then select Delete.

     

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

 

 

L00082612

Custom-created reports that are populated to the batch report directory are not available for configuration and scheduling.

Use the following steps to configure and schedule the custom reports.

For example, suppose a report named "Custom Batch Detail" is populated in the list.

 

  1. Update the RptServicesConfig.xml file in the following location:

    <systemdrive>:\Inetpub\wwwroot\ReportWeb\ReportConfig

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

    <Report Name="Custom Batch Detail" file="CustomBatchDetail.rdl" description="My Custom Report" />

  4. Save the file.

    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. However, the Watchdog tag still functions 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. The tag can be of any data type.
  • Disable pinging using the IBCli Disable Ping option.

L00125348

If you use the Import Utility in the preview mode, warning messages are not shown. This is observed when the utility imports a Wonderware InBatch ModelDB, in which any of the following have duplicate names (case sensitive): processes, transfers, segments, units, connections, or phases. However, warning messages are shown when you perform an actual import.

L00128201

When you run the cvtmaster for a second time, conversion fails.

 

Workaround:

  1. Create a new folder and name it (E.g. Test). Ensure that the folder name is not Config_A.
  2. Copy the contents of the Config_A folder to the new folder.
  3. Run cvtmaster, directing it to the new folder.
  4. Copy the database from the new folder to the Config_A folder.

L00139186

Error and warning messages related to ReportQueueReader are logged in the SMC logger after you enable the Enhanced security mode using "aaConfigSQL" tool.

 

Workaround: Ensure that the ServiceDB user (configured to run the InBatch ReportQueueReader service) has access to printers and has the privilege to print.

1010526

 

Compatibility issues with Vijeo Citect 2016

 

  • In the Citect Design window, the application crashes when the 'InBatchGUIConfig' control is inserted prior to inserting the 'InBatchSFC' control on the same page.

    Workaround: The 'InBatchSFC' control must be inserted prior to the 'InBatchGUIConfig' control on the page/symbol.

  • Font size cannot be changed on any of the Batch ActiveX controls in Vijeo Citect.
  • An error message is displayed on the Control Area when you hold the InBatch Field ActiveX controls and drag them to a different location on page, during design time.
  • Tooltip does not get displayed on the Batch ActiveX controls at runtime.

1102209

 

The 'History Admin' and the 'Report Web' pages display the following error:

Unable to contact Batch Host to determine if security is enabled. Check Batch Host and restart browser.

 

This error is observed when you:

  1. Install and configure Batch Management Server on Node #1.
  2. Install and configure Batch Management History and Reports on Node #2.
  3. Launch Environment Display on Node #1.
  4. Launch History Admin page or Report Web page on Node #2.

 

Workaround:

  1. Launch Internet Explorer on Node #2.
  2. Under Tools, select Internet Options.

    The Internet Options dialog box appears.

  3. Click the Security tab and then select Trusted sites.
  4. Under Security level for this zone, click Custom level.

    The Security Settings – Local Intranet Zone dialog box appears.

  5. Under User Authentication > Logon, ensure that the Automatic logon with current user name and password option is selected.

     

1105212

Under the Usage Details tab in the Schneider Electric License Manager web page, the Device Name is displayed as:

  • “<<HOSTNAME>>.1” for the consumed Server license.
  • “<<HOSTNAME>>.2" for the Development/Runtime client license.

     

    Workaround:

    In the Schneider Electric License Manager web page, click Sync to synchronize the license server.

     

1105211

License refresh failed, and a valid client license could not be acquired from the license server. A warning message is logged in the SMC logger.

 

Workaround:

Apply the License Server Hot Fix CR L00150512.

 

Known Issues - Documentation

  • Newer operating systems no longer include the WinHlp32.exe Help viewer component, which is required for viewing .hlp files. The Batch Management software includes the following .hlp files:
    • BatchView.hlp
    • IALink.hlp
    • TagView.hlp

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

  • The Help for Batch Management web client is best viewed in Microsoft Edge or Mozilla Firefox browsers.

Batch Management Documentation

The Batch Management documentation set includes the following:

  • ReadMe (This document) - Provides information about software and hardware requirements, known issues, licensing, and documentation updates.
  • Batch Management Installation Guide - Provides information about installation and upgrading from the previous versions.
  • Batch Management Getting Started Guide - Describes the basic components of the Batch Management software and provides a tutorial to help you get started using the product.
  • Batch Management Demo Guide - Describes a demo application that shows you how to use some of the new features in the Batch Management release.
  • Batch Management User's Guide - Describes the components of the Batch Management software and how to use them to create applications.
  • Batch Management Stateless API Online Reference - Provides information about the stateless API supported by the Batch Server.
  • Batch Management COM Technical Reference Guide - Describes using the Batch Management COM technology and provides practical examples of its use.
  • Batch Management Application Object Editor Help - Provides information about the InBatchUnit, InBatchConnection, InBatchPhase, and InBatchSegment objects.
  • Batch Management Custom Report Guide - Provides information about how to convert old (pre 11.5) custom reports to work without Information Server and to have UTC support in Batch Management.
  • Batch Management Help - Describes using the Batch Management Web Client to view batch details.

The Batch Management product library consists of a set of Portable Document Files (PDF) located in the UserDocs folder of the Batch Management installation CD. Install the Adobe Reader on your computer to view the Batch Management 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 Batch Management installation instructions are located in the root folder of the Batch Management installation CD, as a .chm file. You can view these instructions by clicking the Help when you start the Batch Management installation procedure.

Resource File

The following messages are modified in the Batch Management 2017 Update 1 release.

Resource Name

Message

New/
Modified

Notes

BatchMngr.csv

msg417

No Batch is allocated to selected Unit!

New

 

SupervisorClient.csv

ErrNoBatchRunning

There are currently no batches running on the selected unit.

New

 

Copyright © 2019 AVEVA Group plc and its subsidiaries. All rights reserved.   |   Contact Us