In Batch Install Guide

InBatch Installation Guide
Invensys Systems, Inc.
Revision A Last Revision: August 24, 2010
Copyright
2010 Invensys Systems, Inc. All Rights Reserved. All rights reserved. No part of this documentation shall be reproduced, stored in a retrieval system, or transmitted by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written permission of Invensys Systems, Inc. No copyright or patent liability is assumed with respect to the use of the information contained herein. Although every precaution has been taken in the preparation of this documentation, the publisher and the author assume no responsibility for errors or omissions. Neither is any liability assumed for damages resulting from the use of the information contained herein. The information in this documentation is subject to change without notice and does not represent a commitment on the part of Invensys Systems, Inc. The software described in this documentation is furnished under a license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of these agreements. Invensys Systems, Inc. 26561 Rancho Parkway South Lake Forest, CA 92630 U.S.A. (949) 727-3200 http://www.wonderware.com For comments or suggestions about the product documentation, send an e-mail message to ProductDocumentationComments@invensys.com.
Trademarks
All terms mentioned in this documentation that are known to be trademarks or service marks have been appropriately capitalized. Invensys Systems, Inc. cannot attest to the accuracy of this information. Use of a term in this documentation should not be regarded as affecting the validity of any trademark or service mark. Alarm Logger, ActiveFactory, ArchestrA, Avantis, DBDump, DBLoad, DT Analyst, Factelligence, FactoryFocus, FactoryOffice, FactorySuite, FactorySuite A2, InBatch, InControl, IndustrialRAD, IndustrialSQL Server, InTouch, MaintenanceSuite, MuniSuite, QI Analyst, SCADAlarm, SCADASuite, SuiteLink, SuiteVoyager, WindowMaker, WindowViewer, Wonderware, Wonderware Factelligence, and Wonderware Logger are trademarks of Invensys plc, its subsidiaries and affiliates. All other brands may be trademarks of their respective owners.
Contents
Welcome............................................ 5
Documentation Conventions...............................................5 Technical Support ...............................................................6
Chapter 1 Requirements ...................................... 7

Software Requirements.......................................................7
Chapter 2 Installation........................................ 15
Before You Install the InBatch Software .........................15 What Happens During the Installation Process...........15 Using User Account Control (UAC) Enabled Operating Systems with InBatch 9.0 with SP1 .........................16 Using Windows Server 2003 with InBatch 9.0 with SP1 .....................................................................17 Setting Up an InBatch 9.0 with SP1 System...................18 Setting Up an InBatch Server .......................................18 Installing an InBatch History Server............................24 Installing InBatch Reporting Content ..........................26 Installing an InBatch Development Client ...................29 Installing an InBatch Run-time Client .........................32 Installing a Redundant InBatch System ......................34 Installing the InBatch Add-on for WinXML Exporter......................................................................36 Installing an InBatch IDE/IEE Extension....................40
Contents
Installing the InBatch Documentation .........................41 Installing InBatch Client Components as Terminal Services.......................................................................42
Chapter 3 Upgrading Previous Versions to InBatch 9.0 with SP1 ..........................................43 Chapter 4 Uninstalling InBatch 9.0 with SP1.............49
Modifying the InBatch Server Installation......................49 Repairing the InBatch Server Installation ......................51
Chapter 5 Configuring InBatch ..............................53

Configuring the InBatch Server .......................................53 Configuring the InBatch History Server..........................55 Configuring the InBatch Reporting Content ...................56 Configuring the InBatch Run-Time Client ......................57 Configuring the InBatch Development Client .................58 Configuring a Redundant InBatch System......................60 Configuring the InBatch Redundant Server.................60 Configuring the InBatch Redundant Development Client ..........................................................................62 Configuring the InBatch Redundant Run-Time Client ..........................................................................64 Verifying the Redundant Configuration .......................65
Index ...............................................67
Welcome
The InBatch Installation Guide describes the installation options for InBatch components, such as InBatch Server, History Server, InBatch reporting content, Development Client, Run-time client, Redundant InBatch system and so on. It also explains the process for upgrading from an earlier version of InBatch, and uninstalling and configuring of InBatch software.
Documentation Conventions
This documentation uses the following conventions:
Convention Used for
Initial Capitals
Bold Monospace
Paths and file names. Menus, commands, dialog box names, and dialog box options. Code samples and display text.
Welcome
Technical Support
Wonderware Technical Support offers a variety of support options to answer any questions on Wonderware products and their implementation. Before you contact Technical Support, refer to the relevant section(s) in this documentation for a possible solution to the problem. If you need to contact technical support for help, have the following information ready:

The type and version of the operating system you are using. Details of how to recreate the problem. The exact wording of the error messages you saw. Any relevant output listing from the Log Viewer or any other diagnostic applications. Details of what you did to try to solve the problem(s) and your results. If known, the Wonderware Technical Support case number assigned to your problem, if this is an ongoing problem.
Chapter 1
Requirements
An InBatch system consists of several different station types. These include an InBatch server, InBatch history server, InBatch reporting node, and InBatch clients (run-time and development). Each station includes both InBatch software and other additional required software.
Software Requirements
The following table summarizes the station type, the InBatch software requirements, and the additional required software for each station type.
Chapter 1 Requirements
InBatch Station Type
Operating Systems
Additional Software
InBatch server
32-bit (x86) Windows XP SP3 Professional 32-bit (x86) Windows Server 2003 R2 SP2, Standard and Enterprise editions 32-bit (x86), 64-bit (x64) Windows Vista SP2, Business and Enterprise editions) 32-bit (x86), 64-bit (x64) Windows Server 2008 SP2, Standard and Enterprise editions 32-bit (x86) Windows XP SP3 Professional 32-bit (x86) Windows Server 2003 R2 SP2, Standard and Enterprise 32-bit (x86), 64-bit (x64) Windows Vista SP2, Business and Enterprise editions 32-bit (x86), 64-bit (x64) Windows Server 2008 SP2, Standard and Enterprise editions
Microsoft SQL Server InBatch History Server Wonderware Application Server 3.1 SP1 bootstrap and IDE (only when integrating with System Platform and InFusion)
InBatch run-time client
InBatch Server InBatch History Server Wonderware InTouch 10.1 or higher is installed
Software Requirements9
Operating Systems
Additional Software
InBatch development client
32-bit (x86) Windows XP SP3 Professional 32-bit (x86), 64-bit (x64), Windows Vista SP2, Business and Enterprise editions 32-bit (x86) Windows Server 2003 R2 SP1, Standard and Enterprise 32-bit (x86), 64-bit (x64) Windows Server 2008 SP2, Standard and Enterprise editions 32-bit (x86) Windows XP SP3 Professional 32-bit (x86), 64-bit (x64), Windows Vista SP2, Business and Enterprise editions 32-bit (x86) Windows Server 2003 R2 SP2, Standard and Enterprise 32-bit (x86), 64-bit (x64) Windows Server 2008 SP2 , Standard and Enterprise editions
InBatch Server InBatch History Server Wonderware Application Server 3.1 SP1 bootstrap and IDE (only when integrating with System Platform and InFusion
InBatch history server
InBatch Server (IIS6.0/7.0) 32-bit (x86) Microsoft SQL Server 2005 SP3, Standard and Enterprise. 32-bit (x86) SQL Server 2008 SP1, Standard and Enterprise
10
Operating Systems
Additional Software
InBatch reporting content
32-bit (x86) Windows XP SP3 Professional 32-bit (x86) Windows Server 2003 R2 SP2, Standard and Enterprise editions 32-bit (x86), 64-bit (x 64), Windows Vista SP2, Business and Enterprise editions 32-bit (x86), 64-bit (x 64) Windows Server 2008 SP2, Standard and Enterprise editions 32-bit (x86) Windows XP SP3 Professional 32-bit (x86), 64-bit (x64), Windows Vista SP2, Business and Enterprise editions 32-bit (x86) Windows Server 2003 R2 SP2, Standard and Enterprise 32-bit (x86), 64-bit (x64) Windows Server 2008 SP2, Standard and Enterprise editions
InBatch Server Wonderware Information Server with ArchestrA, with ArchestrA Reports Feature and configured Wonderware Information Server 3.1 to 4.0 InBatch History Server
InBatch redundant system
InBatch History Server
InBatch add-on for Win-XML Exporter
See software requirements for Wonderware Information Server
Wonderware Information Server 3.1 to 4.0 Win-XML Exporter
InBatch IDE/IEE Extension
See software requirements for Wonderware Application Server
Wonderware Application Server bootstrap 3.1 SP1 and IDE (only when integrating with System Platform and InFusion)
For information on upgrading and migrating databases to a later version of Microsoft SQL Server, see the Microsoft SQL Server documentation. The following table summarizes the 32-bit and 64-bit software support matrix for different operating systems.
32-bit Wonderware Software Support Matrix

Operating System Windows XP Windows 2003 R2 Windows Vista Windows 2008 Server Windows XP Windows 2003 (and R2) Windows Vista Windows 2008 Server 32-bit (x86) Processor Supported Supported Supported Supported Not Supported Not Supported Not Supported Not Supported 64-bit (x64) Processor Not Supported Not Supported Supported Supported Not Supported Not Supported Supported Supported
64--bit OS
32--bit OS
You can install InBatch on a single node running the Windows Vista operating system.
12
The following table summarizes the station type, the I/A Series batch software requirements, and the additional required software for each station type. For station types that require additional Wonderware software, see the product documentation for its software and hardware requirements.
I/A Series Batch Station Type
Operating Systems
Additional Required Software
InBatch server
P90/P91 Windows Server 2003 R2 SP2, (32-bit only) P92 Windows XP SP3, (32-bit only)
Wonderware Application Server 3.1 SP1, bootstrap and IDE (only when integrating with InFusion) InFusion Control Edition 2.0 (with I/A Series Software 8.5) 8.4.3 release of I/A Series Software 8.5 release of I/A Series Software
InBatch run-time client
P90/P91 Windows Server 2003 R2 SP2, (32-bit only) P92 Windows XP SP3, (32-bit only) P90/P91 Windows Server 2003 R2 SP2, (32-bit only) P92 Windows XP SP3 (32-bit only) P90/P91 Windows Server 2003 R2 SP2, (32-bit only) Windows XP SP3, (32bit only)
None
InBatch development client
Wonderware Application Server 3.1 SP1 bootstrap and IDE (only when integrating with InFusion)
InBatch History server
Microsoft SQL Server 2005 SP2 Standard and Enterprise, 32-bit (x86). 32-bit (x86) SQL Server 2008 Standard and Enterprise InBatch Server IIS 6.0/7.0
I/A Series Batch Station Type
Operating Systems
Additional Required Software
InBatch reporting content InBatch redundant system

Wonderware Information Server 3.1 to 4.0 See InBatch Server
P90/P91 Windows Server 2003 R2 SP2, (32-bit only) P92 Windows XP SP3, (32-bit only)
InBatch add-on for Win-XML Exporter
Wonderware Information Server 3.1 to 4.0 Win-XML Exporter (only when integrating with InFusion)
InBatch IDE/IEE Extension
See software requirements for Wonderware Application Server
Wonderware Application Server 3.1 SP1 bootstrap and IDE (only when integrating with InFusion)
The requirements for integrating InBatch with System Platform and InFusion are:
ArchestrA IDE/IEE must be installed on the InBatch development client or InBatch server nodes to allow browsing the Galaxy namespace. A Galaxy platform is required in the InBatch Server node to allow MX communication.
For additional information on these requirements, see the Wonderware Application Server documentation.
14
24
Chapter 2
Installation
This section describes the InBatch software installation.
Before You Install the InBatch Software

This section discusses several things to consider before you install the InBatch software.
What Happens During the Installation Process

The installation procedure:

Installs the selected feature(s). Upgrades the software automatically from InBatch 9.0 to InBatch 9.0 with SP1. During the upgrade, the existing Batch configuration files and history database files are backed up. Opens the TCP/IP ports required by InBatch that are blocked by default in Windows and configures the program exception for the OLE automation server. Adds all the InBatch history server portals to the trusted sites zone. Provides support for SQL Server 2005 SP3 and SQL Server 2008 SP1, Standard and Enterprise editions.
When the InBatch 9.0 with SP1 installation is complete, previous product and patch information is removed from the Add/Remove Programs option within the Control Panel.
16
Chapter 2 Installation
You can install InBatch run-time and development clients on the terminal server, but you cannot install an InBatch server on a terminal server.
Note When installing InBatch applications on the terminal server, you must use the Windows Control Panel Add Programs option rather than the standalone InBatch installation program that is associated with an InBatch installation. By using the Control Panel/Add Programs option, the Windows terminal server is able to properly manage the multisession environment. If you do not install your applications using this method, you are not able to access the client applications from operator stations.
Using User Account Control (UAC) Enabled Operating Systems with InBatch 9.0 with SP1
When UAC is enabled on Windows Vista and Windows 2008 operating systems, a security prompt is shown during InBatch 9.0 with SP1 installation.
Before You Install the InBatch Software17
If necessary, enter administrative user credentials to allow the installer to proceed.
Using Windows Server 2003 with InBatch 9.0 with SP1

Before you install InBatch 9.0 with SP1 on Windows Server 2003, you must configure the Windows Server 2003 settings. The computer name and the DNS host name defined in the setup of the TCP/IP protocol must be identical, including capitalization. InBatch 9.0 with SP1 fully supports the use of the Windows naming convention in computer names. As part of the InBatch history server installation process, the InBatch installation wizard does the following:

Adds a File Server role. Adds an Application Server role Allows Active Server Pages in the IIS Web Service Extensions For the AdminWeb, BatchWeb, and ReportWeb websites, enables the Enable Parent Paths option in IIS.
18
Setting Up an InBatch 9.0 with SP1 System

Setting up an InBatch 9.0 with SP1 system is a two-step process. You must first install any required software and configure the software and operating systems. For more information see Software Requirements in Chapter 1, Requirements.
Note In the InBatch server installation, the Windows Media Sensing feature is disabled so that you no longer need to install a loopback adapter.
You must be logged on as a user with administrative privileges to install the InBatch software.
Note The All-In-One single node solution is recommended only for small pilot projects and nonproduction development systems. The All-In-One solution requires that the InBatch server, the InBatch history server, InTouch, and the I/O server be installed on one machine.
The recommended installation sequence is:

1 2 3 4 5
Set up the InBatch server. Set up an InBatch history server. Set up an InBatch reporting node. Set up InBatch run-time or development clients. Set up an InBatch redundant server and clients.
Setting Up an InBatch Server

The first InBatch component you need to set up is the InBatch Server.
To install an InBatch server 1
Insert the InBatch CD into the CD-ROM drive. The auto-run capability of Windows starts the setup program. If it does not, from the Start menu, select Run and enter E:\setup.exe (where E: is your CD-ROM drive). The InBatch Installation Wizard starts and the main InBatch Setup dialog box appears. Click Next. The License Agreement dialog box appears.
Accept the license agreement and click Next. The Select Features dialog box appears.
Select the components you want to install. (InBatch Server, InBatch History Server, and InBatch Documentation are selected by default.) You can optionally install the I/A components. When you install InBatch Server, the installation wizard automatically installs the InBatch development client and the InBatch run-time client whether you have selected these components or not. In addition, the installation wizard also installs the following configuration components:

Environment Editor (EnvEdit) Process Modeling Editor (ModelEdit) Tag Linker Editor (TagLinker) Train Editor (TrainEdit) Materials Editor (MaterialEdit) Recipe Editor (RecipeEdit) Process Log Editor (LogEdit) Batch Reporting (BatchReport) Phase Logic Testing Tool (PhaseLogic) Change Password (ChgPwd) Security Editor (SecEdit)
20
The installation wizard also installs the following run-time components:

Environment Manager (EnvMngr) Environment Display (EnvDspl) Unilink Manager (UnilinkMngr) InBatch Client (IBCli) IBMX Service(for ArchetrA integration) Memory Tag Manager (MemTagMngr) Simulation Manager (SimMngr) Information Manager (InfoMngr) InBatch Server (IBServ) InBatch Function Server (IBFServ) Batch Manager (BatchMngr) Batch Scheduler (BatchSched) Batch Display (BatchDspl) Process Logger Manager (LogMngr) Security Manager (SecMngr) TagView Utility (TagView) Recipe Automation Server (RecipeEdit) Batch Talk ActiveX Control (OCXBATCH.OCX) Recipe Procedure SFC ActiveX Control (INBATCHSFC.OCX) Material Automation Server (MATERIALSVR.EXE) Batch Function Interface Type Libraries (BATCHOBJSRV.DLL & BATCHVBSERVER.DLL)
If you are installing the I/A Components, the installation wizard also installs the following components:

I/A- drivers I/A- linker BatchView I/A specific Config_A database
Installing I/A components is optional. You can install I/A components on systems where I/A is not present. If communication through IBMX is planned on InFusion systems, do not choose I/A components during installation. If communication is to be established through IADriver, then I/A components should be selected during installation.
At the bottom of the Select Features dialog box, type the drive and folder in which to install the software and click Next. If this system does not already have a Wonderware product installed on it, the User Name and Password dialog box appears. (If you already have a Wonderware product installed on this system, the installation wizard skips this dialog box and the next dialog box and opens the Ready to Install the Application dialog box, shown in Step 8.)
Do the following: Select the domain or local machine name from the drop-down list. (You must uncheck Create Local Account to enable this field.)

Type a user name, password, and confirm the password. Select Create Local Account to create a local admin user account using the credentials you specified on this dialog box.
22
Click Next. The Password Policy dialog box appears.
Click Next. The Ready to Install the Application dialog box appears.
Select Launch OSConfiguration Utility to add InBatch and I/A Batch programs and services to the Windows Firewall. If this check box is not selected, the installation does not add these programs and services to the Windows Firewall.
10 Click Next.
The installation wizard starts installing the software on your computer. A progress bar shows how the software installation is proceeding. When the installation is complete, the final InBatch Installation Wizard dialog box appears.
11 Click Finish.
You must configure the software with the Configuration Utility before you can use it. For information on configuring your software, see Configuring the InBatch Server on page 53.
24
Installing an InBatch History Server

Before you install an InBatch History Server, you must have a required version of Microsoft SQL Server set up on the node. If you intend to access the history databases with SQL Server authentication, you also need a SQL Server login name and password. I/A 8.5 computers use a "locked down" version of Windows, even in standard mode. Because of this, several Windows services and user accounts related to IIS must be enabled before installing the InBatch History Server. The following Windows services must be enabled and set to automatic:

IIS Admin Service WWW Publishing Service
The following user accounts must be enabled:

IUSR_AWXP01 IWAM_AWXP01
To install an InBatch history server 1
Insert the InBatch CD into the CD-ROM drive. The auto-run capability of Windows starts the setup program. If it does not, from the Start menu, select Run and enter E:\setup.exe (where E: is your CD-ROM drive). The InBatch Installation Wizard starts and the main InBatch Setup dialog box appears. Click Next. The License Agreement dialog box appears. Accept the license agreement and click Next. The Select Features dialog box appears. Select the components you want to install. (InBatch Server, InBatch History Server, and InBatch Documentation are selected by default.) When you install the InBatch history server, the installation wizard also installs the following components:

2 3 4
Batch History DB Batch Archive DB HistQReader BatchAdmin Utility
Optionally browse to the folder in which to install the software and click Next. The User Name and Password dialog box appears. Do the following: Select the domain or local machine name from the list.

7 8
Click Next. The Password Policy dialog box appears. Click Next. The SQL Server and Database Details dialog box appears.
Do the following: Type names into the InBatch history Database Name and the InBatch Archive Database Name boxes. (The name of the InBatch History Node is entered automatically.)
Select Windows authentication or SQL Server authentication. If you select SQL Server authentication, you must also enter a SQL Server login name and password.
26
Select Use Existing History Database to use the existing history database that you specified rather than to have the installation wizard create a new one. Select Use Existing Archive Database to use the existing archive database that you specified rather than to have the installation wizard create a new one.
10 Click Next.
The Ready to Install the Application dialog box appears.

11 Select Launch OSConfiguration Utility to add InBatch and
I/A Batch programs and services to the Windows Firewall. If this check box is not selected, the installation does not add these programs and services to the Windows Firewall.
12 Click Next.
13 Click Finish.
You must configure the software with the Configuration Utility before you can use it. For information on configuring your software, see Configuring the InBatch History Server on page 55.
Installing InBatch Reporting Content

Before you install InBatch reporting content, you must have Wonderware Information Server 3.1 or 4.0 set up on the node. If you intend to access the databases with SQL Server authentication, you also need a SQL Server login name and password.
To install InBatch reporting content 1
Insert the InBatch CD into the CD-ROM drive. The auto-run capability of Windows starts the setup program. If it does not, from the Start menu, select Run and enter E:\setup.exe (where E: is your CD-ROM drive). The InBatch Installation Wizard starts and the main InBatch Setup dialog box appears. Click Next. The License Agreement dialog box appears. Accept the license agreement and click Next. The Select Features dialog box appears.
2 3
Select the components you want to install. (InBatch Server, InBatch History Server, and InBatch Documentation are selected by default.) When you install the InBatch reporting content without either of the two subfeatures, Alarm Reports and IABatch Alarm Reports, the installation wizard installs all the report templates except for the alarm template. When you install the InBatch reporting content and the Alarm Reports subfeature, the installation wizard installs all the report templates, including the alarm template.
Note Install the IABatch Alarm Reports subfeature only on an I/ABatch node, not an InBatch node. When you install the InBatch reporting content and the IABatch Alarm Reports, the installation wizard installs the I/ABatch alarm reports on the I/ABatch node. Note Before you install InBatch Reporting content, Wonderware Information Server should be configured using the Wonderware Information Server Configurator. In particular, ArchestrA Reporting needs to be configured. For more details, see the Wonderware Information Server documentation.
When you install InBatch reporting content, the installation wizard also installs the following components:
5
Report Management WebPages and Links Report Templates ReportQReader Service
At the bottom of the Select Features dialog box, type the drive and folder in which to install the software and click Next. The User Name and Password dialog box appears. Do the following: Select the domain or local machine name from the list.

28
Click Next. If you are installing the Alarm Reports subfeature, the Alarm Server dialog box appears. Otherwise, the installation wizard displays the SQL Server and Database Details dialog box shown in Step 9.
Do the following: Type node names in the Alarm Server Node and the Database Name boxes.
Select Windows authentication or SQL Server authentication. If you select SQL Server authentication, you also need to enter a SQL Server login name and password.
Click Next. The SQL Server and Database Details dialog box appears.
10 Do the following:
Type node names in the InBatch History Node and the InBatch History Database Name boxes. Select Windows authentication or SQL Server authentication. If you select SQL Server authentication, you also need to enter a SQL Server login name and password.
11 Click Next.
The Ready to Install the Application dialog box appears.

12 Select Launch OSConfiguration Utility to add InBatch and
I/A Batch programs and services to the Windows Firewall. If this check box is not selected, the installation does not add these programs and services to the Windows Firewall.
13 Click Next.
14 Click Finish. You must configure the software with the Configuration Utility before you can use it. For information on configuring your software, see Configuring the InBatch Reporting Content on page 56.
Installing an InBatch Development Client

The InBatch development client and InBatch run-time client are both installed with the InBatch Server; however, you can also install them separately.
To install an InBatch development client 1
Insert the InBatch CD into the CD-ROM drive. The auto-run capability of Windows starts the setup program. If it does not, from the Start menu, select Run and enter E:\setup.exe (where E: is your CD-ROM drive). The InBatch Installation Wizard starts and the main InBatch Setup dialog box appears. Click Next. The License Agreement dialog box appears. Accept the license agreement and click Next. The Select Features dialog box appears.
2 3
30
Select the components you want to install. (InBatch Server, InBatch History Server, and InBatch Documentation are selected by default.) You can optionally install the I/A components. When the InBatch development client is installed, the installation wizard also installs the following components:

Process Modeling Editor Tag Linker Train Editor Material Editor Recipe Editor Batch Report Security Editor Process Log Editor
5
I/A Driver I/A Linker BatchView
At the bottom of the Select Features dialog box, enter the drive and folder in which to install the software and click Next. The User Name and Password dialog box appears. Do the following: Select the domain or local machine name from the drop-down list.

Type a user name, password, and confirm the password. Select Create Local Account to create a local Admin user account using the credentials you specified on this dialog box.
7 8 9
Click Next. The Password Policy dialog box appears. Click Next. The Ready to Install the Application dialog box appears. Select Launch OSConfiguration Utility to add InBatch and I/A Batch programs and services to the Windows Firewall. If this check box is not selected, the installation does not add these programs and services to the Windows Firewall.
10 Click Next.
11 Click Finish.
You must configure the software with the Configuration Utility before you can use it. For information on configuring your software, see Configuring the InBatch Development Client in Chapter 5, Configuring InBatch. To use the RecipeEdit or MaterialSrv automation servers on a 64-bit operating system, run the commands one time from a command prompt.
To run the commands 1 2 3 4 5
Close all open InBatch applications. Start a command prompt as an Administrator and change the directory to C:\Windows\sysWOW64. Type the following command: mmc comexp.msc /32. In the Distributed COM Configuration Properties dialog box, click the Applications tab. Configure the properties for both the Wonderware RecipeEdit and Wonderware MaterialSrv DCOM applications listed in the window. Do the following:
a b c
Select the Run application on the following computer check box. In the box, enter the name of the Batch Server. Click OK.
Note Do not select the Run application on this computer check box.
For more information on dcomconfig, see the InBatch COM Technical Reference.
Note InBatch OLE Automation Servers may not start successfully the first time they are used, if the InBatch Server node was not restarted after installing the InBatch server components. In that case, restart the InBatch server node for the OLE automation servers to operate correctly.
32
Installing an InBatch Run-time Client

The InBatch development client and InBatch run-time client are both installed with the InBatch Server; however, you can also install them separately. Before you install an InBatch run-time client, you must have Wonderware InTouch 10.1 or later set up on the node. (You dont have to have InTouch installed to install the I/A run-time client.) Installing I/A components is optional. You can install I/A components on systems where I/A is not present. If communication through IBMX is planned on InFusion systems, do not choose I/A components during installation. If communication is to be established through IADriver, then I/A components should be selected during installation. The installation program may prompt you to overwrite the following files. In both cases, click No.

wwtechsp.dll wwtechsp.wdf
To install an InBatch run-time client 1
Insert the InBatch CD into the CD-ROM drive. The auto-run capability of Windows starts the setup program. If it does not, from the Start menu, select Run and enter E:\setup.exe (where E: is your CD-ROM drive). The InBatch Installation Wizard starts and the main InBatch Setup dialog box appears. Click Next. The License Agreement dialog box appears. Accept the license agreement and click Next. The Select Features dialog box appears. Select the components you want to install. (InBatch Server, InBatch History Server, and InBatch Documentation are selected by default.) You can optionally install the I/A components. When the InBatch run-time client is installed, the installation wizard also installs the following components:

2 3 4
Batch Display Batch Scheduler Batch OCX Controls
5
I/A drivers I/ABatch BatchDisplay I/ABatch BatchView
At the bottom of the Select Features dialog box, enter the drive and folder in which to install the software and click Next. The User Name and Password dialog box appears. Do the following: Select the domain or local machine name from the drop-down list.

7 8 9
Click Next. The Password Policy dialog box appears. Click Next. The Ready to Install the Application dialog box appears. Select Launch OSConfiguration Utility to add InBatch and I/A Batch programs and services to the Windows Firewall. If this check box is not selected, the installation does not add these programs and services to the Windows Firewall. The installation wizard starts installing the software on your computer. A progress bar shows how the software installation is proceeding. When the installation is complete, the final InBatch Installation Wizard dialog box appears.
10 Click Next.
11 Click Finish.
You must configure the software with the Configuration Utility before you can use it. For information on configuring your software, see Configuring the InBatch Run-Time Client on page 57.
34
Installing a Redundant InBatch System

Redundancy is an optional feature of the Batch Management System. It is installed on both servers using the InBatch Server option of the installation program.
Installing a Redundant InBatch Server

Designate one computer as the master and begin installation on that computer. Then, repeat the installation on the other (backup) computer. For general installation details, see Setting Up an InBatch 9.0 with SP1 System on page 18.
To install and configure a redundant InBatch server 1
In the Select Features dialog box of the InBatch installation program, select both InBatch Server and InBatch Redundant System. If you are using I/A systems, also select the appropriate I/A components.
Go through the normal installation process for both the primary and the secondary servers.
Post-Installation Instructions for I/A Series Components

The status of a redundant server is made available to your I/A Series network through a shared variable. You can use the shared variable to monitor the redundancy status of the server. In operation, IADriver continuously attempts to write an integer value to the shared variable. If the write attempt fails, a message appears and the feature is no longer available. The format of the shared variable is:
<hostname>_RS
Where: <hostname> is a computer name and RS is appended to the <hostname> (for example, AW7004_RS).
To create the shared variable 1 2
Start a command prompt. In the D:\opt\fox\bin\tools directory, run the following command:
omcrt -v -i <hostname>_RS
Example
omcrt -v -i AW7004_RS
The shared variable that you created is discarded each time you restart your server. To avoid recreating this variable every time the server restarts, create the following two lines in a AW_RS.BAT batch file located in the D:\opt\fox\bin\tools\ directory. Use the appropriate host name.
sleep 120 omcrt -v -i <hostname>_RS
In the Startup folder for the Fox user, create a shortcut to this AW_RS.BAT batch file.
36
Installing InBatch Clients for Redundancy

These instructions assume that you have previously installed InBatch server software.
To install an InBatch development client
In the Select Features dialog box of the InBatch installation program, select InBatch Development Client and InBatch Redundant System.
To install an InBatch run-time client
In the Select Features dialog box of the InBatch installation program, select InBatch Runtime Client and InBatch Redundant System.
Installing the InBatch Add-on for WinXML Exporter

The InBatch add-on for Win-XML Exporter is a file that lets you convert the InTouch windows that contain InBatch ActiveX controls into XML format for publishing in Wonderware Information Server. For additional information about this process, consult the Wonderware Information Server documentation.
To install the InBatch add-on for WinXML Exporter 1
Insert the InBatch CD into the CD-ROM drive. The auto-run capability of Windows starts the setup program. If it does not, from the Start menu, select Run and enter E:\setup.exe (where E: is your CD-ROM drive). The InBatch Installation Wizard starts and the main InBatch Setup dialog box appears. Click Next. The License Agreement dialog box appears. Accept the license agreement and click Next. The Select Features dialog box appears. Select the components you want to install. (InBatch Server, InBatch History Server, and InBatch Documentation are selected by default.)
2 3 4
When the InBatch add-on for Win-XML Exporter is installed, the installation wizard also installs the following components:

Ocxcfg_merge.exe Batch_cfgocx.xml
In addition, the installation wizard installs the following components in the specified directories: ..\wwwroot\Wonderware\_library\codebase\ wwcontrols\bin

BatchDspl.exe BatchNativeSec.dll BatchObjSrv.dll BatchSched.exe BatchSecCtrl.dll BatchVBServer.dll dkintlib2.dll GuiBinder.dll GuiControls.dll histhook.dll HistQMngr.exe IBTD.dll IBTDctl.ocx IBTIMT.dll InBatchSFC.ocx LogEdit.exe MaterialEdit.exe MaterialSrv.exe ModelEdit.exe OcxBatch.ocx RecipeEdit.exe SecEdit.exe TagLinker.exe TIMEdit.exe TrainEdit.exe
38
..\wwwroot\Wonderware\_library\codebase\ wwcontrols\HistQ

HistQDB.dat HistQDB.dbd HistQDB.key
..\wwwroot\Wonderware\_library\codebase\ wwcontrols\HistQ\dflt_HistQ
5
HistQDB.dat HistQDB.dbd HistQDB.key GuiControls.cab IBUninst.dll IBUninstC.dll IBUninstR.dll
..wwwroot\Wonderware\_library\codebase\wwcontrols
At the bottom of the Select Features dialog box, type the drive and folder in which to install the software and click Next. The User Name and Password dialog box appears. Do the following: Select the domain or local machine name from the drop-down list.

7 8 9
Click Next. The Password Policy dialog box appears. Click Next. The Ready to Install the Application dialog box appears. Select Launch OSConfiguration Utility to add InBatch and I/A Batch programs and services to the Windows Firewall. If this check box is not selected, the installation does not add these programs and services to the Windows Firewall.
10 Click Next.
11 Click Finish.
You must configure the software with the Configuration Utility before you can use it. For information on configuring your software, see Chapter 5, Configuring InBatch.
40
Installing an InBatch IDE/IEE Extension

The InBatch IDE/IEE extension adds a Launch Environment Display menu item to the ArchestrA IDE. This menu option is disabled until the InBatch server is installed on the same node.
To install an InBatch IDE/IEE extension 1
Insert the InBatch CD into the CD-ROM drive. The auto-run capability of Windows starts the setup program. If it does not, from the Start menu, select Run and enter E:\setup.exe (where E: is your CD-ROM drive). The InBatch Installation Wizard starts and the main InBatch Setup dialog box appears. Click Next. The License Agreement dialog box appears. Accept the license agreement and click Next. The Select Features dialog box appears. Select the components you want to install. (InBatch Server, InBatch History Server, and InBatch Documentation are selected by default.) Click Next. The Ready to Install the Application dialog box appears. Select Launch OSConfiguration Utility to add InBatch and I/A Batch programs and services to the Windows Firewall. If this check box is not selected, the installation does not add these programs and services to the Windows Firewall. Click Next. The installation wizard starts installing the software on your computer. A progress bar shows how the software installation is proceeding. When the installation is complete, the final InBatch Installation Wizard dialog box appears.
2 3 4
5 6
Click Finish. You must configure the software with the Configuration Utility before you can use it. For information on configuring your software, see Chapter 5, Configuring InBatch.
8
Installing the InBatch Documentation

You can install the InBatch documentation on any node as part of any of the installations. You can also install the documentation on another computer.
Note The Adobe Acrobat reader must be installed on your system to read the documentation. You can download this from www.adobe.com. To install an InBatch server 1
Insert the InBatch CD into the CD-ROM drive. The auto-run capability of Windows starts the setup program. If it does not, from the Start menu, select Run and enter E:\setup.exe (where E: is your CD-ROM drive). The InBatch Installation Wizard starts and the main InBatch Setup dialog box appears. Click Next. The License Agreement dialog box appears. Accept the license agreement and click Next. The Select Features dialog box appears. Select the components you want to install. (InBatch Server, InBatch History Server, and InBatch Documentation are selected by default.) You can optionally install the I/A components. At the bottom of the Select Features dialog box, type the drive and folder in which to install the software and click Next. The User Name and Password dialog box appears. Do the following: Select the domain or local machine name from the drop-down list.

2 3 4
7 8
Click Next. The Password Policy dialog box appears. Click Next. The Ready to Install the Application dialog box appears.
42
Select Launch OSConfiguration Utility to add InBatch and I/A Batch programs and services to the Windows Firewall. If this check box is not selected, the installation does not add these programs and services to the Windows Firewall. The installation wizard starts installing the software on your computer. A progress bar shows how the software installation is proceeding. When the installation is complete, the final InBatch Installation Wizard dialog box appears.
10 Click Next.
11 Click Finish.
Installing InBatch Client Components as Terminal Services

Caution When you install InBatch run-time clients and development clients for use with Terminal Services, it is imperative that you do not perform the normal Auto-Run installation. 1 2 3 4 5
Insert the InBatch CD into your CD-ROM drive. Click Cancel and exit the Auto-Run installation. Click Start > Settings > Control Panel. Double-click Add/Remove Programs. Click Add New Programs and then click CD or Floppy. In the Open field of the Run Installation Program dialog, verify that SETUP.EXE appears. If not, click Browse and locate SETUP.EXE on the InBatch CD. Click Next. To install the appropriate InBatch client, follow the procedures for Installing an InBatch Run-time Client or Installing an InBatch Development Client.
6 7
43
Chapter 3
Upgrading Previous Versions to InBatch 9.0 with SP1
When you install InBatch 9.0 with SP1 on a system that already has InBatch 9.0, the installation procedure automatically detects the earlier version of InBatch and automatically upgrades it to InBatch 9.0 with SP1. When you upgrade from InBatch 9.0 to InBatch 9.0 with SP1, installation automatically makes a backup of the HistQ and Config_A folders at <Installed Path>\ InBatch. During the upgrade, a message box appears briefly to show the upgrade status.
This process updates the databases and other files to a format that is compatible with the InBatch 9.0 with SP1 installation procedures. For more information, see Wonderware InBatch Version 9.0 with SP1 Readme, Upgrading from Previous Version - Wonderware InBatch 9.0 with SP1 section. If you have a version of InBatch earlier than InBatch 9.0, you must manually uninstall it.
44
Chapter 3 Upgrading Previous Versions to InBatch 9.0 with SP1
You cannot select a particular InBatch component to upgrade. The installation detects the existence of the InBatch Server, the InBatch client, the InBatch History Server, and the Reporting Server and upgrades all the existing components. During the upgrade, modification of any of the existing features is not allowed.
Note As part of the installation process, you must supply the domain, user name, and password of an Administrator-level Windows user account. This account is used as the batch administrator for complex password requirements.
You may be prompted to restart the computer after successfully upgrading the InBatch History Server and Reporting Server nodes from version 9.0 to version 9.0 with SP1. The installation converts the batch history and batch archive databases automatically. After the software has been installed, you must convert the configuration (Config_A) databases separately. The conversion process is applicable when converting from earlier versions of InBatch (that is, from versions 8.1 SP1 or later to 9.0 with SP1). The conversion process is not applicable when upgrading from InBatch 9.0 to 9.0 with SP1. The conversion process makes the following changes.
Database Changes from the conversion
Environment database
IBMX service added. X parameters added to batchmngr. TIM references removed. Galaxy Access name added. Conversion to support Username length. Hyphens () in expressions converted to periods (.).
Configuration link database Security database Recipe database
45
To upgrade your InBatch software to InBatch 9.0 with SP1 1 2
Back up your InBatch 8.1 configuration and database files. Uninstall the InBatch 8.1 software using Add/Remove Programs on the Control Panel. This removes the InBatch software and configuration files, but leaves the databases. Insert the InBatch CD into the CD-ROM drive. The auto-run capability of Windows starts the setup program. If it does not, from the Start menu, select Run and enter E:\setup.exe (where E: is your CD-ROM drive). The InBatch Installation Wizard starts and the main InBatch Setup dialog box appears.
Follow the procedures in the Installation Wizard. After you have restored the configuration files from the previous version, you must convert them for use with InBatch 9.0 with SP1.
To convert the configuration files to InBatch 9.0 with SP1 1
If the databases in C:\Program Files\Wonderware\InBatch\cfg\config_A are not empty, delete the contents of that directory and then copy the contents of C:\Program Files\Wonderware\InBatch\cfg\dflt_cfg to the C:\Program Files\Wonderware\InBatch\cfg\config_A directory. On the InBatch server node, from the Start menu, select Environment Display. The Environment Display dialog box appears. From the File menu, select Exit and Shutdown. Close the WWLogger. From the Start menu, select Run, and then enter C:\Program Files\Wonderware\InBatch\bin\ CvtMaster.exe. A dialog box asks you to make sure that you have backed up your configuration files and that your InBatch History Server is connected to the history database.
3 4 5
46
Click OK. The Batch Database Conversion Utility dialog box appears.
Click Convert. The conversion utility converts the databases in the specified directory. When the conversions are complete, the utility displays information about the databases that were converted, databases that were not converted or that were skipped, and databases that were already in InBatch 9.0 with SP1 format. The utility logs information about the conversion operations in the DbCvt.txt file, located in the configuration folder.
Copy the SecurityDB.dat, SecurityDB.dbd, and SecurityDB.key files from the directory they were in to the C:\Program Files\Wonderware\InBatch\cfg\ Config_A directory. If you are upgrading from InBatch 8.1 and you had Model, Material, Recipe, Link, or Process Logger databases configured, then you must also copy the following databases to the C:\Program Files\ Wonderware\InBatch\cfg\Config_A directory.

CfgLinkDB.dat CfgLinkDB.dbd CfgLinkDB.key CfgModelDB.dat CfgModelDB.dbd CfgModelDB.key LinkDB.dat LinkDB.dbd LinkDB.key LoggerDB.dat LoggerDB.dbd LoggerDB.key MaterialDB.dat
47
MaterialDB.dbd MaterialDB.key ModelDB.dat ModelDB.dbd ModelDB.key RecipeDB.dat RecipeDB.dbd RecipeDB.key
The databases that are applicable while upgrading from I/A Batch 8.1 are:

CfgIALinkDB.dat CfgIALinkDB.dbd CfgIALinkDB.key IALinkDB.dat IALinkDB.dbd IALinkDB.key CfgModelDB.dat CfgModelDB.dbd CfgModelDB.key LoggerDB.dat LoggerDB.dbd LoggerDB.key MaterialDB.dat MaterialDB.dbd MaterialDB.key ModelDB.dat ModelDB.dbd ModelDB.key RecipeDB.dat RecipeDB.dbd RecipeDB.key
48
49
Chapter 4
Uninstalling InBatch 9.0 with SP1
You can uninstall the various InBatch 9.0 with SP1 components through the Add/Remove Programs function in the Control Panel.
Important If you have installed InBatch 9.0 with SP1 on a system that had a previous version of InBatch, the uninstall procedure does not roll back to an earlier version of the product. The entire product is removed. Be sure to back up the configuration and history databases before uninstalling.
Modifying the InBatch Server Installation

To modify your InBatch Server installation, you can use one of the following:

The InBatch Server installation program (Setup.exe) The Microsoft Windows Add/Remove Programs utility
50
Chapter 4 Uninstalling InBatch 9.0 with SP1
To modify using the InBatch Server installation program 1
Run Setup.exe from the CD-ROM. The Application Maintenance dialog box appears.
.
2 3
Click Modify and then click Next. Follow the prompts to modify InBatch Server.
To modify using the Add/Remove Programs utility 1 2 3 4 5
Open the Windows Control Panel. Double-click Add/Remove Programs. The Add or Remove Programs dialog box appears. Select Wonderware InBatch and then click Change. The Application Maintenance dialog box appears. Click Modify and then click Next.
Follow the prompts to modify InBatch Server. If any of the existing features are modified, then a backup is taken of the Config_A folder with a timestamp in the product installation folder location.
Repairing the InBatch Server Installation51
Repairing the InBatch Server Installation

You can reinstall missing or corrupted InBatch Server files, configuration settings, and other components. You can reset the default values for preferences.
Note The repair procedure only reinstalls the original files distributed on the InBatch Server product CD. It does not reinstall files updated from an InBatch Server patch. To repair using the InBatch Server installation program 1
Run Setup.exe from the CD-ROM. The Application Maintenance dialog box appears. .
2 3
Click Repair and then click Next. Follow the prompts to repair InBatch Server.
To repair using the Add/Remove Programs utility 1 2 3 4 5
Open the Windows Control Panel. Double-click Add/Remove Programs. The Add or Remove Programs dialog box appears. Select Wonderware InBatch and then click Change. The Application Maintenance dialog box appears. Click Repair and then click Next. Follow the prompts to repair InBatch Server.
52
Chapter 4 Uninstalling InBatch 9.0 with SP1
53
Chapter 5
Configuring InBatch
After you have installed the InBatch software, you need to configure it using the InBatch configuration utility. When you install an InBatch component, the InBatch installation process also installs the InBatch configuration utility on that node. You must run the InBatch configuration utility on each node to configure the component before you can use that component.
Note If you make any changes to the InBatch configuration after you have configured your components, you must use the configuration utility to update all the required nodes.
Configuring the InBatch Server

When you install the InBatch server, the installation process also installs the InBatch run-time and development clients on the same node. You can also install these clients separately on other nodes. The InBatch run-time and development clients use the same configuration information as InBatch server. When you configure InBatch server, the InBatch configuration utility automatically configures the local copies of the InBatch run-time and development clients as well.
54
Chapter 5 Configuring InBatch
To configure the InBatch server 1
On the Start menu, point to Programs, Wonderware, InBatch, and then click InBatch Configuration Utility. The InBatch configuration utility appears.
Click InBatch Server. The InBatch Server Configuration dialog box appears.
Type IP addresses or node names in the InBatch History Server Host Name and Wonderware Information Server Name fields. Select Share InBatch Folder to use the InBatch development client. Click Apply. A message confirms that the configuration was successful.
4 5
Click OK. The InBatch server configuration is complete. The InBatch run-time and development clients are also configured on this node.
Configuring the InBatch History Server55
Configuring the InBatch History Server

The InBatch history server typically is installed on a different node from the InBatch server.
To configure the InBatch history server 1
On the Start menu, point to Programs, Wonderware, InBatch, and then click InBatch Configuration Utility. The InBatch configuration utility appears. Click InBatch History Server. The InBatch History Server Configuration dialog box appears.
3 4 5
Type an IP address or node name in the InBatch Server

Node Name field.
Click Apply. A message confirms that the configuration was successful. Click OK. The InBatch history server configuration is complete.
56
Configuring the InBatch Reporting Content

The InBatch reporting content is installed on the same node as Wonderware Information Server.
To configure the InBatch reporting content 1
On the Start menu, point to Programs, Wonderware, InBatch, and then click InBatch Configuration Utility. The InBatch configuration utility appears. Click InBatch Reporting Content. The InBatch Reporting Content Configuration dialog box appears.
Type IP addresses or node names in the InBatch History Server Node Name and Alarm System Server Node Name fields. The Alarm System Server Node Name is the name of the server hosting the Alarm database.
Click Apply. A message confirms that the configuration was successful.
Click OK. The InBatch reporting content configuration is complete.
Configuring the InBatch Run-Time Client57
Configuring the InBatch Run-Time Client

By default, the InBatch run-time client is installed on the same node as the InBatch server and is configured as part of the InBatch server configuration process. If you install the client on a separate node, you must configure it separately.
To configure the InBatch run-time client 1
On the Start menu, point to Programs, Wonderware, InBatch, and then click InBatch Configuration Utility. The InBatch configuration utility appears. Click InBatch Runtime Client. The InBatch Runtime Client Configuration dialog box appears.
Type IP addresses or node names in the InBatch History Server Node Name and the InBatch Server Node Name fields. Click Apply. A message confirms that the configuration was successful.
Click OK. The InBatch run-time client configuration is complete.
58
Configuring the InBatch Development Client

By default, the InBatch development client is installed on the same node as the InBatch server and is configured as part of the InBatch server configuration process. If you install the client on a separate node, you must configure it separately.
Important If you are running the Configuration Utility as a standard user, you must remap any drives that were previously mapped by the Administrator and then click Apply.
A message appears informing you about the requirements for InBatch configuration.
Configuring the InBatch Development Client59
To configure the InBatch development client 1
On the Start menu, point to Programs, Wonderware, InBatch, and then click InBatch Configuration Utility. The InBatch configuration utility appears. Click InBatch Development Client. The InBatch Development Client Configuration dialog box appears.
Type IP addresses or node names in the InBatch History Server Node Name, the InBatch Server Node Name, and the Wonderware Information Server Node Name fields. Select the drive to map the batch server folder to from the drop-down list. Click Apply. A message confirms that the configuration was successful. Click OK. The InBatch configuration is complete.
4 5 6
60
Configuring a Redundant InBatch System

Redundancy is an optional feature of the Batch Management System. It is installed on both servers using the InBatch server option of the installation program. During the installation, you are prompted for specific information about your network.
Configuring the InBatch Redundant Server

To configure a redundant InBatch server 1 2
On the Start menu, point to Wonderware, then InBatch, and InBatch Configuration Utility. Click InBatch Redundant Server. The InBatch Redundant Server Configuration dialog box appears.
Type the Remote Batch Server Node Name. This is the name of the other InBatch server. For example, you could name it REMOTE. Type the InBatch History Server Node Name. This is the computer where you installed the InBatch History software. Type the Wonderware Information Server Node Name. This is the computer where you installed the reporting components.
Configuring a Redundant InBatch System61
6 7
Select the number of NICs, which is generally 2. Type the Local Host Name of Primary Network. This is the logical host name of the primary InBatch server, such as InBatch1. Type the Local Host Name of Secondary Network. This is the logical host name of the secondary network on the primary InBatch server, such as INBATCHA. Type the Remote Host Name of Primary Network. This is the logical host name of the primary network on the remote InBatch server, such as REMOTE1. the logical host name of the secondary network on the remote InBatch server, such as REMOTEB.
10 Type the Remote Host Name of Secondary Network. This is
11 Click Apply. 12 Repeat steps 3 through 12 on the other (backup) server. 13 As part of the InBatch redundant component installation
process, the InBatch Installation Wizard configures the following registry key: Key: HKEY_LOCAL_MACHINE\System\ CurrentcontrolSet\Services\Tcpip\Parameters Value Name: DisableDHCPMediaSense Data Type: REG_WORD Value: 1
RedCfg File Structure

The RedCfg file is created after you have performed the redundancy configuration with the Configuration Utility. The RedCfg file has the following structure: Line 1: Line 2: Line 3: Line 4: Line 5: Line 6: Line 7: Line 8: Line 9: The remote computer name Blank, not used The path to the remote computer config_A directory Blank, not used The local hostname for primary network (cannot be a computer name) The local hostname for secondary network (blank if not used) The remote hostname for primary network (cannot be a computer name) The remote hostname for secondary network (blank if not used) Blank, not used
62
Note The last line of the RedCfg file must be blank (that is, a carriage return.) The line numbers shown are for reference only. They are not actually entered in the file.
RedCfg File Example

The Master server creates the RedCfg file as follows:
InBatchBackup <blank line> \\InBatchBackup\config_A\ <blank line> InBatch1 InBatchA InBatch2 InBatchB <blank line>
The Backup server has the following RedCfg file:

InBatchMaster <blank line> \\ InBatchMaster \config_A\ <blank line> InBatch2 InBatchB InBatch1 InBatchA <blank line>
Configuring the InBatch Redundant Development Client

Whenever redundant InBatch servers have been installed, you can also configure InBatch development and run-time clients for redundancy.
Important Before you begin configuring a client for redundancy, you must first establish valid network connections between your servers and each client. To configure an InBatch Development Client 1
After the installation completes, on the Start menu, point to Wonderware, then InBatch, and InBatch Configuration
Utility.
On the InBatch Configuration Utility dialog box, click InBatch Redundant Client. The InBatch Redundant Client Configuration dialog box appears.
In the InBatch History Server Node Name box, type the name of the computer where you installed the InBatch History software. In the Wonderware Information Server Node Name box, type the name of the computer where the Wonderware Information Server software is installed. In the Primary Batch Server Node Name box, type the name of the InBatch master server. Click the arrow and select a drive to map to the primary (master) InBatch server folder. In the Secondary Batch Server Node Name box, type the name of the InBatch backup server. Click the arrow and select a drive to map to the secondary (backup) InBatch server folder. Click Apply.
5 6 7 8 9
64
Configuring the InBatch Redundant Run-Time Client

To configure an InBatch Run-Time Client 1 2
On the Start menu, point to Wonderware, then InBatch, and InBatch Configuration Utility. On the InBatch Configuration Utility dialog box, click InBatch Redundant Client. The InBatch Redundant Client Configuration dialog box appears.
In the InBatch History Server Host Name box, type the name of the computer where the history software is installed. In the Primary Batch Server Host box, type the name of the computer that is the primary server. In the Secondary Batch Server Host Name box, type the name of the computer that is the secondary server. Click Apply.
4 5 6
I/A Components Considerations

InBatch client stations must have access to the I/A Series batch directory D:\IASeriesBatch on the InBatch server stations. Consequently, you must share the I/A Series InBatch directory on the InBatch server station. Each InBatch client station must have the network drives mapped to the shared I/A Series InBatch directory on the InBatch server. If the only connection of the InBatch client to the InBatch servers is through the Mesh control network, I/A Series software must be running on the InBatch client station (a station separate from the InBatch server station) to map network drives to the InBatch servers before and during installation of the InBatch client software. If you have an alternative Ethernet connection between the InBatch client station and the InBatch server stations, perform the following two steps:
1 2
Use the control panel to prevent FoxAPI and Fox I/A from starting when you restart the station. Restart the station.
Verifying the Redundant Configuration

Important A thorough understanding of this section is critical for the proper deployment of a redundant batch system.
After installing and configuring redundant batch servers, verify that the servers are capable of properly switching over batch control.
To verify a redundant configuration 1 2 3
Navigate to the Environment Display dialog box. On the View menu, click Status. Verify that one of the computers has Master with Valid Backup and the other has Valid Backup. If they show Master with Invalid Backup and Invalid Backup, wait a few minutes for the servers to synchronize, and check again. If both servers appear as Master with Invalid Backup, use the File > Force System to Master command on one of the computers, then shut both down, and start one up first, then start the other.
66
4 5 6
When the master and backup status is established, shut down the master computer to test the failover. Restart the computer that has been shutdown and verify that its status is now Valid Backup.
Repeat the shutdown and restart sequence to the current master to fail back over, if necessary. Before starting two redundant servers within a workgroup, the Local Security Policy settings on each server must be configured properly.
To configure the local security settings of two redundant servers within a workgroup 1 2 3 4
Access ControlPanel\Administrative Tools \Local Security Policy. Starts the Windows Local Security Policy editor. Click Local Policies and Security Options. Select Network access (shares that can be accessed anonymously). Add the Config_A and InBatch shares to the setting.
67
Index
A
Add-on for WinXML Exporter, installing 36
I
IDE/IEE extension, installing 40 InBatch with SP1 15, 16, 17, 18, 43, 45, 46, 49 InBatch 9.0 converting the configuration files to 45 upgrading to 43 using Windows Server 2003 with 16, 17 InBatch 9.0 with SP1 17 Modifying InBatch Server Installation 49 Repairing InBatch Server Installation 51 Uninstalling 49 installation Add-on for WinXML Exporter 36 client components as terminal services 42 development client 29 Galaxy platform 13 IDE/IEE extension 40 InBatch PDF documentation 41 InBatch server 18 redundant deveopment client 36 redundant server 34 reporting content 26 run-time client 32 software requirements 7
C
client components, installing as terminal services 42 configuration development client 58 history server 55 InBatch server 53 redundant development client 36 redundant server 34 configuration files, converting to InBatch 9.0 45
D
development client, configuring 58 development client, installing 29 documentation conventions 5 documentation, installing 41
E
examples RedCfg file 62
H
history server, configuring 55
68 Index
system setup 18 using Windows Server 2003 with InBatch 9.0 16, 17
run-time client, installing 32
S
server, configuring 53 station types 12, 44
P
PDF documentation, installing 41
R
RedCfg file example 62 structure 61 redundant configuration, verifying 65 redundant development clients, installing and configuring 36 redundant servers I/A series post installation instructions 35 installing and configuring 34 redundant stations on I/A series, considerations 65 Repairing InBatch Server Installation 51 reporting content, installing 26
T
technical support, contacting 6 terminal services, installing InBatch client components as 42 types, station 12, 44
W
Windows 2003 Standard/Enterprise R2 SP2 8, 10 Windows Server 2003 R2 SP2 8 Windows Server 2008 SP2 8 Windows Vista SP1 Business 8, 9, 10 Windows XP SP2 or SP3 8, 9, 10 WinXML Exporter, installing the InBatch Add-on for 36

In Batch Install Guide

Transféré par

Informations du document

Description originale:

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

In Batch Install Guide

Transféré par

Droits d'auteur :

Formats disponibles

InBatch Installation Guide

Invensys Systems, Inc.

Revision A Last Revision: August 24, 2010

Chapter 1 Requirements ...................................... 7

InBatch Installation Guide

Chapter 5 Configuring InBatch ..............................53

InBatch Installation Guide

InBatch Installation Guide

InBatch Installation Guide

InBatch Installation Guide

InBatch Station Type

InBatch run-time client

InBatch Installation Guide

InBatch Station Type

InBatch development client

InBatch history server

InBatch Installation Guide

InBatch Station Type

InBatch reporting content

InBatch redundant system

InBatch History Server

InBatch add-on for Win-XML Exporter

See software requirements for Wonderware Information Server

Wonderware Information Server 3.1 to 4.0 Win-XML Exporter

InBatch IDE/IEE Extension

See software requirements for Wonderware Application Server

InBatch Installation Guide

32-bit Wonderware Software Support Matrix

InBatch Installation Guide

Additional Required Software

InBatch run-time client

InBatch development client

InBatch History server

InBatch Installation Guide

I/A Series Batch Station Type

Additional Required Software

InBatch reporting content InBatch redundant system

See software requirements for Wonderware Information Server

Wonderware Information Server 3.1 to 4.0 See InBatch Server

InBatch add-on for Win-XML Exporter

See software requirements for Wonderware Information Server

InBatch IDE/IEE Extension

See software requirements for Wonderware Application Server

InBatch Installation Guide

InBatch Installation Guide

This section describes the InBatch software installation.

Before You Install the InBatch Software

What Happens During the Installation Process

InBatch Installation Guide

InBatch Installation Guide

Before You Install the InBatch Software17

If necessary, enter administrative user credentials to allow the installer to proceed.

Using Windows Server 2003 with InBatch 9.0 with SP1

InBatch Installation Guide

Setting Up an InBatch 9.0 with SP1 System

The recommended installation sequence is:

Setting Up an InBatch Server

InBatch Installation Guide

Before You Install the InBatch Software19

InBatch Installation Guide

The installation wizard also installs the following run-time components:

I/A- drivers I/A- linker BatchView I/A specific Config_A database

InBatch Installation Guide