INTEGRATED PRODUCTION & PERFORMANCE SUITE

Batch

INSTALLATION GUIDE
PUBLICATION BATCH-IN009A-EN-P–August 2007
Supersedes Publication BATCH-IN008A-EN-P
 Contact Rockwell Customer Support Telephone — 1.440.646.3434
Online Support — http://www.rockwellautomation.com/support/

Copyright Notice © 2007 Rockwell Automation Technologies, Inc. All rights reserved. Printed in USA.
This document and any accompanying Rockwell Software products are copyrighted by Rockwell Automation
Technologies, Inc. Any reproduction and/or distribution without prior written consent from Rockwell Automation
Technologies, Inc. is strictly prohibited. Please refer to the license agreement for details.
Trademark Notices Allen-Bradley, ControlLogix, eProcedure, FactoryTalk, Rockwell Automation, Rockwell Software, RSLinx, RSView,
and the Rockwell Software logo, are registered trademarks of Rockwell Automation, Inc.

The following logos and products are trademarks of Rockwell Automation, Inc.:
RSBizWare, the RSBizWare logo, RSBizWare Batch, FactoryTalk Batch, RSBizWare BatchCampaign, RSBizWare
BatchHistorian, FactoryTalk Historian Classic for Batch, RSBizWare Historian, FactoryTalk Historian Classic,
RSBizWare MaterialTrack, and RSLoop Optimizer.

Any Rockwell software or hardware not mentioned here are also trademarks, registered or otherwise, of Rockwell
Automation Technologies, Inc.

Other Trademarks ActiveX, Microsoft, Microsoft Access, SQL Server, Visual Basic, Visual C++, Visual SourceSafe, Windows, Windows
ME, Windows NT, Windows 2000, Windows Server 2003, and Windows XP are either registered trademarks or
trademarks of Microsoft Corporation in the United States and/or other countries.
Adobe, Acrobat, and Reader are either registered trademarks or trademarks of Adobe Systems Incorporated in the
United States and/or other countries.
ControlNet is a registered trademark of ControlNet International.
DeviceNet is a trademark of the Open DeviceNet Vendor Association, Inc. (ODVA).
Ethernet is a registered trademark of Digital Equipment Corporation, Intel, and Xerox Corporation.
OLE for Process Control (OPC) is a registered trademark of the OPC Foundation.
Oracle, SQL*Net, and SQL*Plus are registered trademarks of Oracle Corporation.
All other trademarks are the property of their respective holders and are hereby acknowledged.

Warranty This product is warranted in accordance with the product license. The product’s performance may be affected by system
configuration, the application being performed, operator control, maintenance, and other related factors. Rockwell
Automation is not responsible for these intervening factors. The instructions in this document do not cover all the
details or variations in the equipment, procedure, or process described, nor do they provide directions for meeting every
possible contingency during installation, operation, or maintenance. This product’s implementation may vary among
users.
This document is current as of the time of release of the product; however, the accompanying software may have
changed since the release. Rockwell Automation, Inc. reserves the right to change any information contained in this
document or the software at anytime without prior notice. It is your responsibility to obtain the most current information
available from Rockwell when installing or using this product.

Version: 9.00.00 (CPR 9)

Modified: September 19, 2007 2:58 pm

ii
Contents

1 • How to Use this Guide 1

Getting started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Select a chapter for each computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

2 • What’s New in Version 9.0 3

Company and product name changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Product distribution changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
New system requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
New FactoryTalk Security installation defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Installing FactoryTalk Services Platform 2.10 (CPR 9) for the first time . . . . . . . 4
Upgrading from FactoryTalk Automation Platform 2.00 (CPR 7) . . . . . . . . . . . . 5
When running a mix of versions, some new features are unavailable . . . . . . . . . . 5
DEP support added. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
DEP settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Changing DEP settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Hardware DEP settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Using FactoryTalk AssetCentre to view audit messages . . . . . . . . . . . . . . . . . . . . . . . . 7
Multi-processor and hyperthreading support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
FactoryTalk Live Data support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Using FactoryTalk Batch with Logix5000 controllers. . . . . . . . . . . . . . . . . . . . . . . . . . 9
New DSDF file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Versioning information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
New common user assistance folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Activation grace period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
FactoryTalk Batch component enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
FactoryTalk Batch View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
FactoryTalk Batch Equipment Editor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
FactoryTalk Batch Recipe Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Report Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
FactoryTalk Batch Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
FactoryTalk Batch ActiveX controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

3 • System Requirements 15
System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Configuration requirements for Windows Server 2003 . . . . . . . . . . . . . . . . . . . . . . . . 17

iii
• • • • • FACTORYTALK BATCH INSTALLATION GUIDE

Tested 3rd-party software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Microsoft . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Adobe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Rockwell Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Anti-Virus software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

4 • Setting Up a FactoryTalk Batch System 19

FactoryTalk Batch component integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Server placement guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
FactoryTalk Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

5 • Install FactoryTalk Batch Server/Client 23

Pre-installation procedures for FactoryTalk Batch Server/Client . . . . . . . . . . . . . . . . 24
Verify the operating system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Install Microsoft Visual Basic (optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Install SQL Server 2005 (optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Set up security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Identify FactoryTalk Batch Server names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Log on to Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Enable the Windows Firewall. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Install the FactoryTalk Batch Server/Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Install the FactoryTalk Services Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Install FactoryTalk Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Install the FactoryTalk Batch Server/Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Configure the Batch Server/Client computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Set system date and time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Modify event log settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Create a shared directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Set security on the Logs and Journals folders . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Configure the server options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Define redundant servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Configure the Windows Firewall (optional). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Create an area model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Create recipes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

6 • Install FactoryTalk Batch Client 41

Pre-installation procedures for FactoryTalk Batch Client . . . . . . . . . . . . . . . . . . . . . . 42
Install operating system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Install Microsoft Visual Basic (optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Set up security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

iv
 • • • • •
CONTENTS

Identify server names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Log on to Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Enable the Windows Firewall. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Install the FactoryTalk Batch Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Install the FactoryTalk Services Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Install the FactoryTalk Batch Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Configure the FactoryTalk Batch Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Set system date and time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Modify event log settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Modify local security policy settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Create a shared directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Configure the Windows Firewall (optional). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

A • Uninstalling the FactoryTalk Batch Applications 53

Backing up your files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Uninstalling Batch 8.0 components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Allow the Message Queue to clear . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Disable the Material Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Disable COM+ Security and shut down the COM+ application . . . . . . . . . . . . . 55
Run the uninstall program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Delete the COM+ application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Delete the account profile running MaterialTrack . . . . . . . . . . . . . . . . . . . . . . . . 57
Delete the default directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Remove Registry subkeys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

B • Troubleshooting Your Installation 59

Running the FactoryTalk Directory Configuration Wizard . . . . . . . . . . . . . . . . . . . . . 59

Index vii

v
• • • • • FACTORYTALK BATCH INSTALLATION GUIDE

vi
1 How to Use this Guide
This guide provides the information and procedures you need for installing FactoryTalk®
Batch.

Getting started
Before upgrading your FactoryTalk Batch system, read the first four chapters of this guide
to become familiar with the new features and system requirements for FactoryTalk Batch
version 9.00.
Chapter 2, What’s New in Version 9.0 contains highlights of the new features, including
any new operating system requirements, and a description of each new feature and new
user interface element.
Review the system requirements in Chapter 3, FactoryTalk Batch System Requirements,
for important hardware, software, and operating system requirements in version 9.00.
Finally, review Chapter 4, Setting up a FactoryTalk Batch System, which outlines server
placement guidelines and information about implementing your FactoryTalk Batch
system.

Select a chapter for each computer

Refer to Chapters 5 and 6 for specific installation procedures. It is not necessary to read
every chapter. For each computer in your FactoryTalk Batch system, select the chapter
that most closely describes the FactoryTalk Batch products you are installing on that
computer. Depending on your FactoryTalk Batch system configuration, you may follow a
different chapter for each computer in your system, or you may find that you will repeat
the instructions in one chapter for several computers.
Begin your installation with the computers where you will install your FactoryTalk Batch
servers. After the servers are installed, install the FactoryTalk Batch Client components on
your client computers.

Examples
If, for example, your FactoryTalk Batch system will include a FactoryTalk Batch Server
and FactoryTalk Batch Client on one computer, and the FactoryTalk Batch Client on
several other computers, decide in advance on which computer you will install each
component. Next, read the corresponding chapters most closely resembling the
FactoryTalk Batch product configuration of each computer in your FactoryTalk Batch
system.

1
• • • • • FACTORYTALK BATCH INSTALLATION GUIDE

The following table shows a FactoryTalk Batch system with the corresponding chapter for
each computer:

Computer Components Reference

1 FactoryTalk Batch Server Chapter 5

FactoryTalk Batch Client “Install FactoryTalk Batch Server/Client”

2 and 3 FactoryTalk Batch Client Chapter 6

“Install FactoryTalk Batch Client”

2
2 What’s New in Version 9.0
The following sections describe new features that have been added to the RSBizWare
Batch components, including RSBizWare eProcedure® and RSBizWare MaterialTrack™,
in version 9.0:
„ Company and product name changes
„ Product distribution changes
„ New FactoryTalk Security installation defaults
„ DEP support added
„ Using FactoryTalk AssetCentre to view audit messages
„ Versioning information
„ Multi-processor and hyperthreading support
„ FactoryTalk Live Data support
„ New common user assistance folder
„ New DSDF file
„ Activation grace period
„ FactoryTalk Batch component enhancements (formerly RSBizWare Batch)

Company and product name changes

„ Rockwell Software Inc. has changed to Rockwell Automation, Inc. The parent
company, Rockwell Automation, has become Rockwell Automation Technologies,
Inc. This change will not affect user interfaces in the software, with the exception of
splash screens and About boxes.
„ In an effort to more closely align Rockwell’s product offerings, several products have
been renamed. The changes that directly affect the RSBizWare Batch modules are as
follows:

Current Name New Name

RSBizWare Batch FactoryTalk Batch

RSBizWare Historian FactoryTalk Historian Classic
RSBizWare BatchHistorian FactoryTalk Historian Classic for
Batch
RSAssetSecurity FactoryTalk Security

These changes directly affect the user interfaces (splash screens, About boxes, some
dialog boxes) but do not affect the registry settings, executables, .DLLs, etc.

3
• • • • • FACTORYTALK BATCH INSTALLATION GUIDE

Product distribution changes

The following changes were made to the way FactoryTalk Batch software components are
delivered:
„ RSBizWare eProcedure and RSBizWare MaterialTrack are now included in each
license of FactoryTalk Batch. Additionally, the FactoryTalk Batch Archiver, PC-
Based Phases and Batch View clients are no longer licensed and will be included in
FactoryTalk Batch.
„ MicroSoft SQL Client Access Licenses are no longer included with FactoryTalk Batch
or RSBizWare eProcedure. You must purchase SQL Server 2005, Service Pack 2 if
you wish to archive to SQL, store recipes in SQL databases, or if you use
MaterialTrack.

New system requirements

„ Windows® Server 2003 R2, Standard Edition is now required to run the FactoryTalk
Batch, RSBizWare™ eProcedure® and RSBizWare MaterialTrack™ Servers.
„ The FactoryTalk Batch, RSBizWare eProcedure and MaterialTrack clients can be
installed and run on Windows Server 2003 R2, Standard Edition or Windows XP
Professional Edition, Service Pack 2.
„ RSOPC™ Gateway™ has been renamed to FactoryTalk® Gateway, and is no longer
supported with FactoryTalk Batch. Instead, the FactoryTalk Batch Server can now
communicate directly to plant-floor controllers through FactoryTalk Live Data and
RSLinx® Enterprise. (See FactoryTalk Live Data support for more information.)

New FactoryTalk Security installation defaults

FactoryTalk Security (formerly RSAssetSecurity) installs as an integrated part of the
FactoryTalk Services Platform. The installation process varies, depending upon whether
you install FactoryTalk Services Platform 2.10 (CPR 9) for the first time on a computer, or
whether you upgrade from FactoryTalk Automation Platform 2.00 (CPR 7).

Installing FactoryTalk Services Platform 2.10 (CPR 9) for the

first time
When you install FactoryTalk Services Platform 2.10 for the first time on a computer,
without upgrading from an earlier version of the FactoryTalk platform, the installation
process:
„ Creates both a FactoryTalk Local Directory and a FactoryTalk Network Directory
on the computer. When the install process finishes, both directories are fully
configured and ready for use. If you are working with a stand-alone FactoryTalk

4
 • • • • •
2 • What’s New in Version 9.0

system on a single computer, use the Local Directory. If you are working with a
networked FactoryTalk system distributed across multiple computers, use the
Network Directory.
„ Allows any Windows Administrator user account to log on to either directory. The
installation process automatically adds the local Windows Administrators group to the
FactoryTalk Administrators group in each FactoryTalk Directory.
„ Allows any authenticated Windows user, not just administrative users, to log on
to the FactoryTalk Local Directory. The installation process automatically adds all
members of the local Windows Authenticated Users group to the FactoryTalk Local
Directory. Any Windows user that has successfully logged on to Windows on the local
computer is automatically a member of the Authenticated Users group.
„ Allows all new user accounts full access permissions. The installation process
automatically sets system policies to allow all new user accounts added to either
directory full access to that directory by default. To tighten security, you can change
system polices and restrict access rights for specific user accounts and for groups of
users.
For details, see FactoryTalk Security Help.

Upgrading from FactoryTalk Automation Platform 2.00 (CPR 7)

When you upgrade a computer from FactoryTalk Automation Platform 2.00 (CPR 7) to
FactoryTalk Services Platform 2.10 (CPR 9), the installation process automatically creates
a backup of your existing FactoryTalk Directory configurations. If something goes wrong
during the installation, you can restore the system from this backup. Information about the
location of the backup files is provided during installation.
In addition, while the installation process updates each directory with support for new
policy settings and new features, it leaves your original directory configurations intact. It
does not change your existing policy or security settings.
For details, see FactoryTalk Security Help.

When running a mix of versions, some new features are

unavailable
If your FactoryTalk system contains a mix of version 2.00 (CPR 7) and version 2.10
(CPR 9) clients connecting to computers hosting version 2.00 (CPR 7) FactoryTalk
Directory Servers, you cannot use these new security features in version 2.10 (CPR 9):
„ Action groups, which allow you to group together securable actions for various
FactoryTalk products, and then configure security settings once for the whole group of
actions. For example, you can use action groups to define security settings for various
roles, such as operator, supervisor, maintenance personnel, and so on.

5
• • • • • FACTORYTALK BATCH INSTALLATION GUIDE

„ Resource grouping, which allows you to group control hardware resources and then
define security settings once for the whole grouping.
For more details on action groups and resource grouping, see FactoryTalk Security Help.

DEP support added

Data Execution Prevention (DEP) is a security feature that is supported by both hardware
and software and intended to prevent the execution of malicious code in the Microsoft
Windows XP (Service Pack 2) and Microsoft Windows Server 2003 (Service Pack 1 and
R2) operating systems.

DEP settings
The DEP settings determine which applications and components are covered by DEP
protection. They apply to both hardware-supported and software DEP features. On
computers with the necessary hardware capabilities, hardware-supported DEP features are
enabled for the same set of applications and components as the software DEP features.
The following table explains the possible DEP settings and if those settings are supported
by Rockwell Software products.

Rockwell Software recommends that you use the default DEP settings unless you have a specific
reason to change them.

Supported by Rockwell
DEP Setting Description Software Products?

AlwaysOn Full DEP protection for the entire system (all applications No
and components, no exceptions).

OptIn DEP-enabled only for Windows system components and Yes

for applications that explicitly “opt in”. This is the default
setting for Microsoft Windows XP (Service Pack 2).

OptOut DEP-enabled for all processes except those that explicitly Yes
“opt out”. This is the default setting for Microsoft Windows
Server 2003 (Service Pack 1 and R2).

AlwaysOff DEP protection is disabled for the entire system (all Yes
applications and components, no exceptions).*

* Rockwell Automation does not recommend using this setting since it will make your system
more vulnerable to malicious code.

6
 • • • • •
2 • What’s New in Version 9.0

Changing DEP settings

To change the DEP settings, select Control Panel > System > Advanced > Performance
Settings > Data Execution Prevention. The Turn on DEP for essential Windows
programs and services only setting corresponds to the OptIn setting and the Turn on
DEP for all programs and services except those I select setting corresponds to OptOut
setting.
„ You must be an administrator of your computer to change these settings.
„ You must reboot the computer for the DEP setting changes to take effect.

Hardware DEP settings

Hardware DEP uses the processor to mark memory so that code cannot be executed from
data regions. When code attempts to execute in these marked areas, the processor
generates an exception. If you are using Microsoft Windows XP (Service Pack 2) or
Microsoft Windows Server 2003 (Service Pack 1 and R2) operating systems, the
offending program is terminated. Hardware DEP is also enabled as the factory default
setting. This feature is turned on or off in the computer BIOS settings.
To determine if your hardware supports DEP, refer to the hardware manual or contact your
hardware manufacturer.
For additional information, see the Microsoft Knowledgebase article at: http://
support.microsoft.com/kb/875352.

Using FactoryTalk AssetCentre to view audit messages

Auditing functionality provides a detailed audit trail of all user initiated changes to Area
and Recipe data from the FactoryTalk Batch Equipment Editor and Recipe Editor. In
releases prior to version 9.0, FactoryTalk Diagnostic’s native store was used as the
repository for this audit information. The FactoryTalk Diagnostics Viewer control allowed
you to view messages retrieved and merged from multiple products running on multiple
computers logging to multiple destinations.
In FactoryTalk Batch version 9.0, the FactoryTalk® AssetCentre diagnostic destination is
also supported. If the FactoryTalk AssetCentre event repository is present the audit trail is
written to FactoryTalk AssetCentre and not to the FactoryTalk Diagnostics native store.
The audit messages will be viewable in the FactoryTalk AssetCentre Client and not the
Diagnostics Viewer. If the FactoryTalk AssetCentre event repository is not present the
audit trail will be written, as it was in previous releases, to the FactoryTalk Diagnostic’s
native store. (See the FactoryTalk Batch Administrator’s Guide for more information.)

7
• • • • • FACTORYTALK BATCH INSTALLATION GUIDE

Multi-processor and hyperthreading support

FactoryTalk Batch, RSBizWare eProcedure and RSBizWare MaterialTrack have been
tested for functioning correctly when running on a hyperthreaded enabled or dual core
CPU. Hyperthreading technology enables multi-threaded applications to execute threads
in parallel.
A single desktop hyperthreading enabled processor can simultaneously process two
threads of code, which improves performance of a multi-threaded application running on
a single processor. In a dual processor environment, hyperthreading technology allows up
to four threads to process simultaneously taking advantage of available system resources
(the actual number of threads is user-configurable).
There are two FactoryTalk Batch components that are multi-threaded by design; the
FactoryTalk Batch Server and the RSBizWare eProcedure Server. All other FactoryTalk
Batch applications are single-threaded applications, but may use components that are
multi-threaded.

FactoryTalk Live Data support

The FactoryTalk Live Data protocol provides services that read and write real-time
manufacturing data from data servers and controllers for participating FactoryTalk-
enabled products in the FactoryTalk Directory. FactoryTalk Live Data improves on OPC-
DA by making communication with multiple servers easier.
FactoryTalk Batch subscribes to the FactoryTalk Live Data communication protocol as a
data client. RSLinx® Enterprise (CPR 9) must be part of your FactoryTalk system to
support the FactoryTalk Batch Live Data data client. RSLinx Enterprise (CPR 9) is a
communication server that provides plant-floor device connectivity for a wide variety of
Rockwell Automation applications and unparalleled connectivity to Logix processors.
In previous versions of FactoryTalk Batch, called RSBizWare Batch, RSOPC Gateway provided
connectivity from Batch to plant-floor controllers and devices. In FactoryTalk version 9.0, RSOPC
Gateway has been renamed to FactoryTalk Gateway, and is no longer supported with
FactoryTalk Batch. FactoryTalk Live Data support eliminates the need for FactoryTalk Gateway
with FactoryTalk Batch.

The following FactoryTalk Batch components were enhanced to support FactoryTalk Live
Data:
„ FactoryTalk Batch Server
„ FactoryTalk Batch Equipment Editor
„ Installation

8
 • • • • •
2 • What’s New in Version 9.0

Using FactoryTalk Batch with Logix5000 controllers

For CPR 9, FactoryTalk Batch supports only version 16 of the Logix5000 controllers.
Logix5000 configurations can make a significant impact on FactoryTalk Batch
performance.
General Guidelines for improving performance:
1. Schedule all tasks as Periodic rather than Continuous.
2. Configure the Unused System Overhead Timeslice setting for Reserve for System
Tasks as necessary
3. Increase the timeslice if necessary
(See the Logix System Configuration Manual for specific information on configuring
Logix5000 v.16.)

New DSDF file

The new DSDF file, RSLinxEnterprise.dsdf, defines the communication protocol and
protocol parameters the FactoryTalk Batch Server uses to communicate with FactoryTalk
Live Data data servers. The RSLinxEnterprise.dsdf file is located in the BATCHCTL\bin\
DataServers directory.

Versioning information
The FactoryTalk Batch Server now supports a new API item (CPRVersion) that returns the
server’s version information. Each of the FactoryTalk Batch Server clients (the
FactoryTalk Batch View, the RSBizWare eProcedure Client and the supported ActiveX
controls) checks the FactoryTalk Batch Server version on startup via CPRVersion and
determines compatibility with the server. If an incompatibility exists, the Client
application displays a warning message. The View and eProcedure Client also log the
results of the compatibility check.

This incompatible condition is untested and unsupported; it is strongly recommended that you
upgrade your system.

The FactoryTalk Batch View and eProcedure Client maintain a visible indication (of the
incompatibility) as long as they are connected to a FactoryTalk Batch Server with which
they are incompatible. The ActiveX controls support a new BatchVersionCompatible
property by which a user can determine whether a version incompatibility exists between
the Server and Clients.

9
• • • • • FACTORYTALK BATCH INSTALLATION GUIDE

If the FactoryTalk Batch Server is restarted while a FactoryTalk Batch Client is active, the
Client obtains the version information when it reconnects and continues as described
above.
If you are upgrading from an earlier version of the FactoryTalk Batch software
(RSBizWare Batch), please see “Changes to Existing Product Functionality in 9.0” in the
FactoryTalk Batch Component Upgrade Guide.

New common user assistance folder

Starting with version 9.0, all Rockwell Software applications will install their user
assistance files (online help, user documentation PDF files, and release notes) in a
common folder located at \Program Files\Common Files\Rockwell\Help. This allows
interaction between different products’ user assistance files.
The first Rockwell Software product installed on a computer creates the common folder.
The last Rockwell Software product removed from the computer removes the common
folder and all remaining user assistance files.

Activation grace period

When the FactoryTalk Batch Server is started, it performs a license check. If a valid
activation is found, a successful license check is returned to the Server. As a result of the
license check, the Batch Server determines which applications have a license.
If its normal license check process fails, the FactoryTalk Batch Server requests grace
period activation from FactoryTalk Activation, if the Allow Grace Period check box is
enabled in the FactoryTalk Batch Service Manager. The manner in which the grace period
activation is requested depends on the area model and why the license check process
failed. The FactoryTalk Batch Server will log the request for and receipt of the grace
period license.
When grace period activation is requested for multiple activations by one process, the
grace period is ended and the timer reset when any of the multiple activations can be
successfully obtained.
Every four hours the FactoryTalk Activation software attempts to check out each
activation requested as a grace period activation by the FactoryTalk Batch Server. If any
one of these activations is successfully checked out, the grace period for the Server ends.
If the FactoryTalk Batch Server is started in the Demo mode, an exception is made to the license
and unit checks. Even if no licenses are found, the Server will run for two hours and then shut
down.

10
 • • • • •
2 • What’s New in Version 9.0

FactoryTalk Batch component enhancements

FactoryTalk Batch View

The FactoryTalk Batch Clients (View, ActiveX Controls, and eProcedure Client) now
check for a compatible version of the FactoryTalk Batch Server at startup or reconnect.
„ If an incompatibility exists, the View displays a message to that extent and
recommends upgrading your system. The message is continually displayed for as long
as the View is connected to the FactoryTalk Batch Server.
Example message: The FactoryTalk Batch View is incompatible with the current
FactoryTalk Batch Server. It is strongly recommended that you upgrade your system
before continuing.
„ The FactoryTalk Batch View creates a log entry if connected to an incompatible
FactoryTalk Batch Server. The View also maintains a visible indication as long as it is
connected to a FactoryTalk Batch Server with which it is incompatible. The View log
wraps after the number of bytes indicated in the new ErrorLogMaxFileSize entry in the
BatchVEW.ini file

This is similar to the behavior for the FactoryTalk Batch Server log file.

„ A new key entry, ErrorLogMaxFileSize, is defined for the BatchVEW.ini file. The
default value is 1,000,000. It is created in a new ERROR section in the BatchVEW.ini
file. If the key and/or section do not exist, they are created at startup and set to the
default value.
„ The FactoryTalk Batch View log file contains header information that does not get
overwritten when the log wraps. The information in the header contains one line, with
the following information (similar to the FactoryTalk Batch Server’s log header
startup entry):

Column Number Displayed Information

1 <time stamp as normally displayed>

2 INFO
3 <file name outputting this entry>
4 <line number in above file>
5 <string resource ID for entry in column 10>
6 <blank>
7 <blank>

11
• • • • • FACTORYTALK BATCH INSTALLATION GUIDE

Column Number Displayed Information

8 <blank>
9 <blank>
10 FactoryTalk Batch View startup
11 Version = <w.x.y.z, similar to FactoryTalk Batch Server entry>

„ When starting the View, if a configured FactoryTalk Directory is not found, a message
displays.

FactoryTalk Batch Equipment Editor

„ When starting the Equipment Editor, if a configured FactoryTalk Directory is not
found, a message displays.
„ The FactoryTalk Batch Equipment Editor supports the creation of FactoryTalk Live
Data Servers and the assignment of FactoryTalk Live Data Servers to units and
equipment modules. To support the new functionality, RSLinx Enterprise (CPR 9)
must be part of your system.
„ The Data Servers dialog box enables you to add a FactoryTalk Live Data Server
to an area model.
„ Units and equipment modules defined in the area model support FactoryTalk Live
Data tags.

FactoryTalk Batch Recipe Editor

Text boxes added to Sequential Function Charts (SFCs), improved recipe printing, and
report generation are now incorporated into version 9.0 FactoryTalk Batch Recipe Editor
software.
„ The Text Box feature enables you to generate and associate comments with steps,
transitions, or an entire recipe. By adding text boxes to SFCs, important information
can be placed and saved with the recipe for easy reference.
„ Recipe printing now includes the ability to show/hide page boundaries and specify
margins in an updated menu format.
„ The Generate Report function allows you to select, preview, and print recipe
procedures. If no recipe is opened, all recipe procedures within the working set of
recipes can be printed. When a recipe is open and the Generate Report function is
selected, you can print all procedures within the opened recipe.
„ Using the Recipe Procedure Filter, procedures can be sorted by type and equipment to
produce an alphabetic listing of recipes that meets the selected criteria.

12
 • • • • •
2 • What’s New in Version 9.0

Report Editor
As of version 9.0, the following changes affect the Report Editor:
„ The Report Editor is no longer accessible through the Rockwell Software shortcut
menu. If you are still using this program, the executable file, batchrpe.exe, is located
in the \Program Files\Rockwell Software\Batch\bin directory.
„ The Report Editor User’s Guide is no longer supported and has been removed from
the FactoryTalk Batch user documentation.

FactoryTalk Batch Server

„ A new API item, CPRVersion, checks the CPR version of the FactoryTalk Batch
Server and returns it to the FactoryTalk Batch View, RSBizWare eProcedure Client
and supported ActiveX controls.
„ The FactoryTalk Batch Server now supports the FactoryTalk Live Data
communication protocol as a data client.
„ A new DSDF file supports Batch Server communication with FactoryTalk Live Data
Servers. The RSLinxEnterprise.dsdf file is located in the Batch DataServers directory.

FactoryTalk Batch ActiveX controls

„ A new property, BatchVersionCompatible, has been added to the ControlRecipeList,
ProcedureView, SignatureList, and PromptsList ActiveX controls. This property can
be used to determine whether a version incompatibility exists between the FactoryTalk
Batch Server and Clients (the ActiveX controls, FactoryTalk Batch View and
RSBizWare eProcedure Client). If an incompatibility exists, the control displays a
message to the user: “The [Control Name] ActiveX control is incompatible with the
current FactoryTalk Batch Server. It is strongly recommended that you upgrade your
system before continuing.”
„ A new method, RefreshSecurityToken, has been added to support the FactoryTalk
Batch ActiveX controls when they are hosted in FactoryTalk View SE. The new
method allows the ActiveX controls to use the log on features of the FactoryTalk View
SE client application.
„ As is the case with most ActiveX controls, the FactoryTalk Batch ActiveX controls
are not binary compatible with older versions of the controls. Therefore, you must
rebuild all applications (client displays, HTML pages or VB applications) built against
earlier versions of the Batch ActiveX Controls Library (8.0 or earlier). In HTML
pages that use the controls, the class IDs in the <OBJECT> tags must be updated. This
is done by looking up the class ID (CLSID) in the registry, or by deleting and

13
• • • • • FACTORYTALK BATCH INSTALLATION GUIDE

reinserting the control in an HTML editor. For HMI screens, the controls must be
deleted and reinserted.
Be sure you re-synchronize the code driving client containers to make sure references to the
ActiveX controls are still good.

„ If you are using the FactoryTalk Batch ActiveX controls with FactoryTalk View SE or
RSView32: You cannot open FactoryTalk View SE or RSView32 using a previous
version of a FactoryTalk Batch ActiveX control if the class ID’s (CLSID) TypeLib is
different. After installing the new version of the FactoryTalk Batch product, change
the CLSID’s TypeLib for the ActiveX controls, for example
batch.viewControlRecipeList and batchview.PromptsList, in the registry to the
previous CLSID’s TypeLib. Next, delete the older version of the ActiveX control from
your project, add the new one and save your project.
„ If you are using the FactoryTalk Batch ActiveX controls with FactoryTalk View SE or
RSView32: The user logged on to the FactoryTalk View is also logged on to the
FactoryTalk Batch ActiveX control when the ActiveX control starts.

14
3 System Requirements
Please review the following information before setting up your FactoryTalk Batch system.

System requirements
This section presents the minimum and recommended system requirements to
successfully install and run FactoryTalk Batch.
„ These requirements assume that no other applications will be running on the
computer, unless listed in the “Tested Third-Party Software” section.
„ A CD-ROM drive is required for software installation.
„ Ensure that all selected hardware is on the Microsoft® Windows™ Server 2003
Service Pack 1, Standard Edition, Windows Server 2003 RS2 Standard Edition
(recommended) or Windows XP™ Professional Service Pack 2 compatibility list.
Systems that do not meet the minimum requirements for the version of software being
used are not covered under warranty.
„ The FactoryTalk Batch Server computer cannot be configured as a:
„ Domain Controller
„ DHCP Server
„ WINS Server
„ RAS Server
„ DNS Server
„ Master Browser
„ Replication cannot be enabled on the FactoryTalk Batch Server computer.

Windows security mandates that the domain name and server name must contain only
alphanumeric characters (including “-” or “.”). Internet Explorer blocks cookies from a server if the
server name contains other characters, such as an underscore character (“_”). If a server or
domain name does contain illegal characters, the eProcedure Client will not retain the logged on
user's name.

„ Install FactoryTalk Batch software on an NTFS formatted hard drive, as Windows

Server 2003 security features are available only for drives formatted to use NTFS.

Systems with modified DCOM configuration settings are not covered under warranty. Configuring
settings using DCOMCNFG may stop the FactoryTalk Batch Server and the FactoryTalk Batch
Service Manager from functioning correctly.

15
• • • • • FACTORYTALK BATCH INSTALLATION GUIDE

The following is a list of the hardware and software required to install FactoryTalk Batch.
The minimum requirements are listed as normal text and the recommended requirements
are listed as Bold Italic text.

Server Client

1.2 GHz Pentium processor or greater, 1.2 GHz Pentium processor or greater
Computer
including hyper-threading models

512 MB RAM 256 MB RAM

Memory
(1 GB RAM recommended) (512 MB RAM recommended)

Available Hard 4 GB 2 GB
Disk Space (8 GB recommended) (4 GB recommended)

Hard Disk Format NTFS

Disk Drive(s) CD-ROM drive and a hard disk (SCSI or faster)

256-color VGA and 800x600 minimum resolution

Monitor (SVGA TrueColor with 2 MB of video RAM and 1024x768 resolution
recommended)

Mouse Microsoft Mouse, Microsoft IntelliMouse® or compatible pointing device

Operating System Windows Server 2003 R2 Standard Windows Server 2003 R2 Standard
Edition* Edition* or Windows XP Professional,
Service Pack 2*

Internet Explorer 6.0, Service Pack 1

English (United States)

Network 10 Megabit or faster Ethernet card, network cable

Network Protocol TCP/IP

FactoryTalk Batch is not warranted to run with any other third-party software
Other Software installed on the same PC, unless otherwise stated in writing by Rockwell
Automation.

Backup Removable media device such as a CD-RW drive, etc.

* Windows Server 2003 SP1 Standard Edition is also supported.

16
 • • • • •
3 • System Requirements

Configuration requirements for Windows Server 2003

FactoryTalk Batch version 9.0 requires a specific configuration of the Microsoft Windows
Server 2003 R2 Standard Edition operating system, as well as Microsoft SQL Server
2005, Service Pack 2 for using MaterialTrack. SQL Server can reside on the same
computer as the Batch Server but is not required, nor recommended.
If Oracle 9i is used in conjunction with the Batch Archiver application, it is strongly
recommended that the Oracle server software not reside on the same computer as the
Batch Server.

FactoryTalk Batch version 9.0 is supported in U.S. English and International Spanish only. You
must install the corresponding language version of Windows Server 2003 R2 Standard Edition or
Windows XP Professional, Service Pack 2, to ensure proper operation of FactoryTalk Batch.
Modifying regional settings is not supported.

The only configurations that are tested, and therefore warranteed, by Rockwell
Automation are as follows:

Component Version and Requirements

Servers
„ Microsoft Windows Server 2003 R2 Standard Edition*
„ Internet Explorer 6.0, Service Pack 1
„ Install the operating system using the default selections with the following exception:
• Select the Internet Information Server [IIS]
• Select Microsoft Message Queuing Service (required for RSBizWare
Operating
MaterialTrack)
System
Clients
„ Microsoft Windows Server 2003 R2 Standard Edition* or Windows XP Professional,
Service Pack 2
„ Internet Explorer 6.0, Service Pack 1
„ Install the operating system using the default selections with the following exception:
• Select Personal Web Manager or select the Internet Information Server [IIS]

* Windows Server 2003 SP1 Standard Edition is also supported.

It is highly recommended that you use the default installation directories for all components. The
application, test suite, and associated documentation assume default directories are used.
Extensive unit and system testing by Rockwell Automation ensures that all components function
as one solution after the application is configured.

17
• • • • • FACTORYTALK BATCH INSTALLATION GUIDE

Tested 3rd-party software

Microsoft
„ Internet Explorer 6.0, Service Pack 1
„ Excel XP, Service Pack 2
„ Word XP, Service Pack 2
„ PowerPoint XP, Service Pack 2
„ Access XP, Service Pack 2
„ Visual Basic 6.0, Service Pack 6
„ SQL Server 2005, Service Pack 2 (English version only)

Oracle
„ Oracle 9i

Adobe
„ Acrobat Reader 8.1

Rockwell Software
„ FactoryTalk Activation 3.0
„ FactoryTalk Services Platform 2.10
„ RSLinx Classic 2.52.00
„ RSLinx Enterprise 5.00.00
„ RSView32 7.20.00
„ FactoryTalk View SE 5.00.00
„ RSLogix 5000 v. 16

Anti-Virus software
All Rockwell Software products in this release have been tested using the latest anti-virus
software. For more detailed information, refer to Rockwell Knowledgebase technical note
ID 35330 (you may be required to log into the Knowledgebase before you can view the
information)

18
4 Setting Up a FactoryTalk Batch System
Please review the following information before setting up your FactoryTalk Batch system.

FactoryTalk Batch component integration

FactoryTalk Batch components are completely open, configurable products that help you
define, manage, monitor and control manufacturing at local or remote sites. A typical
FactoryTalk Batch architecture consists of one or more computers on a single network.
The following diagram gives an example of a possible FactoryTalk Batch network:
RSBizWare
MaterialTrack Server
RSBizWare FactoryTalk Batch
MaterialTrack Clients Clients
SQL
Server
Site Level

TCP/IP

FactoryTalk Batch Server

FactoryTalk Batch connects to SQL Server
Server (1-10) & for Master Recipe Storage
RSBizWare eProcedure Server
FactoryTalk
eProcedure Clients Batch Clients

Plant Floor

Proprietary Network

Process-Connected Device (PCD)

Server placement guidelines

There are a few guidelines to consider when deciding where to place your servers on the
network.
„ Up to ten FactoryTalk Batch Servers can exist in a FactoryTalk Batch network.
„ Install the RSBizWare MaterialTrack Server on a computer with SQL Server 2005. Do
not install the MaterialTrack Server on the same computer as the FactoryTalk Batch
Server.

19
• • • • • FACTORYTALK BATCH INSTALLATION GUIDE

„ Install the RSBizWare eProcedure Server on the same computer as the FactoryTalk
Batch Server.
„ Install RSBizWare BatchCampaign on the same computer as the FactoryTalk Batch
View.
The following table indicates the FactoryTalk Batch components that can reside on the
same computer. S represents the Server component and C represents the Client
component.

RSBizWare S
eProcedure** C
RSBizWare S
MaterialTrack C
S
FactoryTalk Batch
C
RSBizWare
BatchCampaign* C
S C S C S C C
eProcedure**
RSBizWare

MaterialTrack
RSBizWare

FactoryTalk Batch

BatchCampaign*
RSBizWare

* RSBizWare BatchCampaign must be installed on the same computer as the

FactoryTalk Batch View.
** RSBizWare eProcedure Server must be installed on the same computer as the
FactoryTalk Batch Server.

Because of memory utilization, do not install the RSBizWare eProcedure Client on the same
computer as the eProcedure and FactoryTalk Batch Servers.

FactoryTalk Activation

FactoryTalk Activation is used to license FactoryTalk Batch and RSBizWare eProcedure

and MaterialTrack.
Before you install the FactoryTalk Batch products you must install the FactoryTalk
Activation Server. The FactoryTalk Activation Server stores the activation files needed to
run FactoryTalk Batch, RSBizWare eProcedure and RSBizWare MaterialTrack. You can

20
 • • • • •
4 • Setting Up a FactoryTalk Batch System

install the FactoryTalk Activation Server on the same computer as the FactoryTalk Batch
Server. The FactoryTalk Activation Server installation includes the FactoryTalk
Activation Client.
The FactoryTalk Batch Server computer requires the FactoryTalk Activation Client to
enable communication with the FactoryTalk Activation Server. If your FactoryTalk
Activation Server is not on the same computer as the FactoryTalk Batch Server then you
must install the FactoryTalk Activation Client on the FactoryTalk Batch Server computer.
We recommend installing the FactoryTalk Activation Server and the FactoryTalk Batch Server on
the same computer.

FactoryTalk Activation for

FactoryTalk Batch, RSBizWare eProcedure
and RSBizWare MaterialTrack 9.00

MaterialTrack Server / Client

Batch Server
FactoryTalk Activation Server / Client
eProcedure Server

Batch Client \ FactoryTalk Activation Platform

eProcedure Client
The Batch Server checks for valid
licenses, and correct number of unit
licenses, for FactoryTalk Batch,
RSBizWare eProcedure and
RSBizWare MaterialTrack at start up.

FactoryTalk Activation Licensing for the FactoryTalk Batch Server

Activation Files for You can choose to install the FactoryTalk Activation Server on any computer
Batch, eProcedure that is on the same network as the Batch products.
and MaterialTrack
If your FactoryTalk Activation Server will reside on the same computer as
the Batch Server, you must install the FactoryTalk Activation Server, which
includes the FactoryTalk Activation Client, on the Batch Server computer.

If your FactoryTalk Activation Server will reside on a computer other than

the Batch Server computer, you must install the FactoryTalk Activation
Server on the other computer and the FactoryTalk Activation Client on the
Batch Server computer.

To obtain activation files for FactoryTalk Batch products you will need the
Host ID of the FactoryTalk Activation Server computer. The product keys
and serial numbers will be supplied with the software.

In this scenario, the Batch Server will not start unless valid activation
files are found for FactoryTalk Batch, RSBizWare eProcedure and
RSBizWare MaterialTrack.

21
• • • • • FACTORYTALK BATCH INSTALLATION GUIDE

Activation files are obtained in one of the following ways:

„ Go to the Rockwell Software licensing website at:
https://licensing.rockwellsoftware.com
„ Use the FactoryTalk Activation Tool on a computer that has internet access.
„ No internet access, call Technical Support to obtain an activation file via e-mail or fax.
Phone: 440-646-3434 in North America. Outside North America, call your local
support organization.

22
5 Install FactoryTalk Batch Server/Client
This chapter instructs you in installing the FactoryTalk Batch Server and Client software
on the same computer. If you have already installed and configured a FactoryTalk Batch
Server computer and just want to install Client components on a different computer,
please go to Chapter 6, “Install FactoryTalk Batch Client”.
There are setup procedures that must be completed before and after you install the
FactoryTalk Batch Server. The Server installation process is divided into three categories:
„ Pre-Installation Procedures
„ Installation Procedures
„ Configure the FactoryTalk Batch Server/Client

Use the following checklist when installing the Server and Client:

Pre-Installation Procedures for

FactoryTalk Batch Server/Client Page
‰ Install Operating System Install Windows Server 2003 R2. 24
Install if you plan to develop with the
‰ Install Microsoft Visual Basic ActiveX Controls Library on the Batch 26
Server Computer.
Install Microsoft SQL Server 2005,
‰ Install if recipes are stored in RDB format. 26
Service Pack 1
Configure security for your FactoryTalk
‰ Set Up Security 26
Batch System.
Identify the name of the computer where the
‰ Identify Server Names 26
FactoryTalk Batch Server is installed.
‰ Log on to Windows Log on with Administrator privileges. 26
Enable the firewall if you want the setup
‰ Enable Windows Firewall (optional) 27
program to populate the firewall exceptions.
Install FactoryTalk Batch Server/Client Page
Required for the FactoryTalk Batch
‰ Install FactoryTalk Services Platform 28
components.
FactoryTalk Activation is used for licensing
Install FactoryTalk Activation on the
‰ and must be installed prior to installing the 30
Batch Server
FactoryTalk Batch Server.
Install the FactoryTalk Batch Server/ Install the FactoryTalk Batch Server with the
‰ 34
Client FactoryTalk Batch Client Components.

23
• • • • • FACTORYTALK BATCH INSTALLATION GUIDE

Configure the FactoryTalk Batch Server/Client Page

Each computer in the FactoryTalk Batch
‰ Set System Date and Time 37
System must be set to the same date and time.
Configure the Windows Application and
‰ Modify Event Log Settings 38
System logs.
Skip this step if you installed your project
‰ Create a Shared Directory 38
files in the default directory, BATCHCTL.
The system administrator determines who
Set Security on Logs and Journal
‰ needs to access these files and assign the 38
Folders
appropriate permissions.
Server Options are configured in the
‰ Configure the Server Options 38
Equipment Editor.
Redundant Servers are defined in the
‰ Define Redundant Servers 38
Equipment Editor.
Complete this step on the FactoryTalk Batch
‰ Create an Area Model Server computer if you performed a full 39
install.
Complete this step on the FactoryTalk Batch
‰ Create Recipes Server computer if you performed a full 39
install.

Pre-installation procedures for FactoryTalk Batch Server/Client

Before you install the FactoryTalk Batch Server and Client you must install and configure
the Windows operating system, and install other third-party software that will be used
with your FactoryTalk Batch system.

Verify the operating system

For a FactoryTalk Batch Server or eProcedure Server 9.0 installation, Windows Server
2003 R2 Standard Edition must be configured as an Application Server to support
FactoryTalk Batch communications. This setup process is accomplished using the
Windows Configure Your Server Wizard.
1. After you log on to Windows, select Administrative Tools from the Manage Your
Server wizard.
If the Manage Your Server wizard does not display, select Administrative Tools
from the Start menu.
2. Double-click Configure Your Server Wizard. The Welcome to the Configure Your
Server Wizard dialog box opens.
3. Click Next. The Preliminary Steps dialog box opens.

24
 • • • • •
5 • Install FactoryTalk Batch Server/Client

4. Click Next. The Server Role dialog box opens.

5. Select Application Server (IIS, ASP.Net) and click Next. The Application Server
Options dialog box opens.
FactoryTalk Batch Server: You can leave the default options.
eProcedure Server: Check ASP.Net.
6. Click Next. The Summary of Selections dialog box opens.

7. Click Next. The configuration process begins.

8. When prompted click Finish. Close the Administrative Tools dialog box.

25
• • • • • FACTORYTALK BATCH INSTALLATION GUIDE

NETDDE SERVICES
In Windows Server 2003 R2 Standard Edition the NetDDE Services are turned off by
default. FactoryTalk Batch requires NetDDE so the following services must be set to
Manual or Automatic:
„ NetworkDDE
„ NetworkDDE DSDM

Install Microsoft Visual Basic (optional)

If you plan to develop with the ActiveX Controls Library, install Microsoft Visual Basic.
If you are using VB.NET with PC Based Phase Programming or ActiveX Controls, be aware that
Report, Request, and Parameter properties appear as Methods in the .NET environment. If you
require further assistance, contact Rockwell Support.

Install SQL Server 2005 (optional)

To store recipes in RDB format, install SQL Server 2005, Service Pack 1. SQL Server
2005 services must be running during the installation process.
Restart the computer after the SQL Server installation is complete.

Set up security
If you are installing the FactoryTalk Batch Server on a domain, create a domain user
account for the Server to use. If the Server is using a local account, you must create
Windows accounts with the same name and password on all computers in the workgroup.
FactoryTalk Security is used to support the FactoryTalk Batch Clients. The setup program
configures FactoryTalk Security with Open Access (no security). If you want to enable
security refer to “Understanding FactoryTalk Batch Security” in the FactoryTalk Batch
Administrator’s Guide.

Identify FactoryTalk Batch Server names

The setup program prompts you for the Domain or Workgroup name and the FactoryTalk
Batch Server user account name and password.

Log on to Windows
Log on to Windows Server 2003 R2 Standard Edition with administrator privileges. Close
any open applications.

You must have administrative privileges on the target computer to install FactoryTalk Batch.

26
 • • • • •
5 • Install FactoryTalk Batch Server/Client

Enable the Windows Firewall

If you want the installation program to populate the firewall exceptions automatically, you
must first enable Windows Firewall Service prior to running the installation. This allows
the Firewall Configuration Utility to add the necessary exceptions.

You must enable the service on both the Server and Client computers.

1. From the Start menu, point to Administrative Tools > Services. The Services dialog
box opens.

2. Right-click Windows Firewall/Internet Connection Service (ICS), and then click

Properties. The Windows Firewall/Internet Connection Service Properties dialog
box opens.

3. From the Startup type list, select Automatic, and then click OK. The service is
enabled.

27
• • • • • FACTORYTALK BATCH INSTALLATION GUIDE

4. Close the Services window.

If you have already installed FactoryTalk Batch or RSBizWare eProcedure, please see the
FactoryTalk Batch Administrator’s Guide for the required configuration changes to allow the
FactoryTalk Batch Server to speak with client applications with the firewall enabled.

For a complete list of the exceptions added to Windows Firewall during FactoryTalk
Batch component installation, see the FactoryTalk Batch Administrator’s Guide.

Install the FactoryTalk Batch Server/Client

These instructions assume that you are installing the FactoryTalk Batch Server computer
on a network with other FactoryTalk Batch Client computers. Before you begin the
installation, complete all the pre-installation procedures. You can exit installation at any
time by clicking the Cancel button.

Install the FactoryTalk Services Platform

You must install the FactoryTalk Services Platform before installing FactoryTalk Batch or
RSBizWare eProcedure components.
1. Insert the installation CD into the CD-ROM drive. The installation process starts
automatically.

To start installation manually, click the Start button, and then select Run. In the Run dialog
box, type d:\setup (where d is the drive letter for the CD-ROM drive), and then click OK.

28
 • • • • •
5 • Install FactoryTalk Batch Server/Client

2. In the Welcome dialog box, click Install FactoryTalk Components. The

FactoryTalk Component Installation dialog box opens.

3. Click Install FactoryTalk Services Platform. The FactoryTalk Services Platform

2.10 (CPR 9) dialog box opens.

If the Microsoft .NET Framework is not already installed on your computer, you are prompted
to install it. When it is installed, the FactoryTalk Services Platform 2.10 (CPR 9) dialog box
opens.

4. Click Next.

29
• • • • • FACTORYTALK BATCH INSTALLATION GUIDE

5. In the License Agreement dialog box, read the license agreement, and then select I
accept the terms in the license agreement. Click Next.
6. In the FactoryTalk Administration Console dialog box, select Install the
FactoryTalk Administration Console (if it is not already checked), and then click
Next.
You may see the Configuring FactoryTalk Directory progress box. It shows you that
any existing FactoryTalk Directories have been backed up, the backup file name(s),
and the path to the backup files.

The FactoryTalk Directory is configured during the installation process. It can be run
manually, however, if you need to define or reset a disabled Administrator account. (See
“Running the FactoryTalk Directory Configuration Wizard” for more information.)

7. Click Finish, then click Yes to restart your computer (if prompted to do so).

For more detailed information on FactoryTalk Directory installation and configuration, you can
view the FactoryTalk Administration Console help file (FTAdminEN.chm) located in
C:\Program Files\Common Files\Rockwell\Help.

Install FactoryTalk Activation

The Activation Server can be any computer in the domain (or workgroup) — downloaded
licenses will reside on that computer. Either the Activation Server or Client must be
installed on the Batch Server computer. If the Activation Client is installed on the Batch
Server computer you must configure it to point to the Activation Server computer in order
to acquire licenses.
The following instructions assume that the FactoryTalk Activation Server and the
FactoryTalk Batch Server reside on the same computer.

IMPORTANT: EVRSI activation keys are no longer supported in FactoryTalk Batch version 8.0
and higher. Instead you use the FactoryTalk Activation tool to obtain activations from the
Rockwell Software Activation website after they have been purchased. Please refer to the
Activate Rockwell Software Products brochure provided in your product package for more
information.

30
 • • • • •
5 • Install FactoryTalk Batch Server/Client

1. In the Welcome to FactoryTalk Batch dialog box, click Install FactoryTalk

Components. The FactoryTalk Components Installation dialog box opens.
If you restarted your computer after installing the FactoryTalk Services Platform, click the Start
button and select Run. In the Run dialog box, type d:\setup (where d is the drive letter for the
CD-ROM drive), and then click OK. Click Install FactoryTalk Components.

31
• • • • • FACTORYTALK BATCH INSTALLATION GUIDE

2. Click Install FactoryTalk Activation Server. The FactoryTalk Activation Server

InstallShield Wizard opens.

The FactoryTalk Activation Server install includes the FactoryTalk Activation Client.

3. Click Next. The End User License Agreement dialog box opens.
4. Read the license agreement and select I accept the terms in the license agreement.
Click Next.
5. Click Next.The Customer Information dialog box opens.
6. Enter the User Name and Organization. Click Next.
7. In the Setup Type dialog box, select Complete, and then click Next.

32
 • • • • •
5 • Install FactoryTalk Batch Server/Client

8. Click Install. The HASP Device Driver Welcome dialog box opens.

9. Click Next. The HASP Device Driver Installation Status dialog box opens.

10. Click Next and then click Finish. The FactoryTalk Activation setup program resumes.
11. When prompted, click Finish. The Rockwell Software Activation Wizard opens.
In the Activate Rockwell Software Products brochure, see Set up your activation server
(concurrent) for further instructions.

33
• • • • • FACTORYTALK BATCH INSTALLATION GUIDE

Install the FactoryTalk Batch Server/Client

1. On the Welcome to FactoryTalk Batch dialog box, click Install FactoryTalk Batch
(click Back to return to the Welcome dialog box, if necessary). The FactoryTalk
Batch Installation dialog box opens.

If the installation program detects an existing RSBizWare/FactoryTalk Batch installation, it gives

you the option to remove the current installation. You must remove the existing version of the
software before installing the upgrade. See “Uninstalling the FactoryTalk Batch Applications” for
instructions on removing the current installed version.

2. Click Install FactoryTalk Batch to start the installation process. The FactoryTalk
Batch InstallShield Wizard opens. Click Next.
3. In the License Agreement dialog box, read the license agreement, and then select I
accept the terms in the license agreement. Click Next.
4. The FactoryTalk Directory Selection dialog box opens.

5. Select the desired FactoryTalk Directory (the default is Network). Click Next.

34
 • • • • •
5 • Install FactoryTalk Batch Server/Client

6. In the Customer Information dialog box, type your name and organization in the
appropriate boxes, and then click Next.
7. In the Custom Setup dialog box, disable Client Components if you do not want to
install the editors on the Batch Server.

Installing the Client on the Batch Server computer is recommended because you must configure
the Server Options, which are located in the FactoryTalk Batch Equipment Editor Client.

The default installation directory is C:\Program Files\Rockwell Software\Batch. To set a different

directory, click the Change button, select the desired directory, and then click OK.

8. Click the Space button (near the bottom of the dialog box) to see if there is enough
disk space to install the selected options. The Disk Space Requirements dialog box
opens. If there is not adequate space, the drive is highlighted. Click OK.
9. Click Next.
10. The System Setup dialog box opens.
‡ If installing as part of an existing FactoryTalk Batch system, select Yes, I am
adding this computer to an existing FactoryTalk Batch System. Click Next.
The Existing Server Details dialog box opens.
Enter the Server Node Name. Click Next.
‡ If installing as the first install of the FactoryTalk Batch module software, select
No, this will be the first computer in a FactoryTalk Batch System. Click Next.

35
• • • • • FACTORYTALK BATCH INSTALLATION GUIDE

11. The Domain/Workgroup Details dialog box opens. Select Domain or Workgroup
to indicate how you are installing the Batch Server.
The FactoryTalk Batch Server user account is added to the batchsvr_group, the Administrators
group, the FactoryTalk Batch Archiver Service, and to the FactoryTalk Batch Server Service on
the local computer.

12. If the FactoryTalk Batch Server runs under a domain account:

‡ Type the Domain name in the Domain /Workgroup Name box.
‡ Complete the User Name and Password boxes for the Batch Server’s domain
account.
If the Server runs under a workgroup account:
‡ Type the Workgroup name in the Domain /Workgroup Name box.
‡ Complete the User Name and Password boxes for the Batch Server’s workgroup
account.
13. Click Next. The Microsoft SQL Server Recipe Storage dialog box opens.
14. In the Microsoft SQL Server Recipe Storage dialog box, indicate how you want to
store recipe files:
„ To store recipes in SQL Server, select Yes, I want to store recipes in SQL Server.
You must have SQL Server installed before selecting this option. If SQL Server is
not installed, click Cancel, install SQL Server 2005 SP2, restart the computer, and
then install FactoryTalk Batch.
„ If you do not want to use SQL Server to store recipes, select No, I do not want to
store recipes in SQL Server. Click Next. Your recipes are stored as binary files.
„ If you want to have the SQL Server on a different computer than the Batch Server,
select No, I do not want to store recipes in SQL Server.

36
 • • • • •
5 • Install FactoryTalk Batch Server/Client

15. Click Next.

16. In the FactoryTalk Historian for Batch Data Storage dialog box, indicate whether
you are using FactoryTalk Historian Classic for Batch or not. If you select Yes, the
appropriate archiver event filters and the frequency with which the archiver commits
event records to the database are automatically set for use with Historian Classic for
Batch. Click Next.
17. In the Ready to Install the Program dialog box, verify your selections. If anything is
incorrect, click the Back button and make the appropriate corrections. When you are
ready to proceed, click Install.

18. When prompted, click Finish, and then click Yes to restart your computer (if
prompted).

Configure the Batch Server/Client computer

You are now ready to configure the Batch Server computer. The following instructions are
provided to assist you in this process.

Set system date and time

Each computer on the network must be set to the same date and time. (See “Configuring
FactoryTalk Batch Settings” in the FactoryTalk Batch Administrator’s Guide.)

37
• • • • • FACTORYTALK BATCH INSTALLATION GUIDE

Modify event log settings

Configure the Windows Application and System logs to overwrite events as needed. (See
“Modifying Event Log Settings” in the FactoryTalk Batch Administrator’s Guide.)

Create a shared directory

If FactoryTalk Batch is installed in a networked environment, and you have installed the
project files to a directory that is not located in the BATCHCTL share, you must create a
share for that project directory. (See “Understanding FactoryTalk Batch
Communications” in the FactoryTalk Batch Administrator’s Guide for information on
creating a shared directory.)

Set security on the Logs and Journals folders

The data in the log files and the event journals (.evt) files may be lost if security is not
administered correctly on these folders. Setting security permissions on the folder is
recommended. The system administrator determines who needs access to these files and
assigns the appropriate permissions. The account(s) under which the FactoryTalk Batch
Server and Archiver are running must be given full access to these folders. (See the
FactoryTalk Batch Administrator’s Guide for more information.)

Configure the server options

Prior to configuring the FactoryTalk Batch Server, ensure that all project directories are
shared. Configure the FactoryTalk Batch Server using the FactoryTalk Batch Equipment
Editor’s Server Options dialog box.
Configure the FactoryTalk Batch Server to allow each network computer to read from and
write to the appropriate project directories, as well as the FactoryTalk Batch Server and
Archiver initialization files. (See “Working With the FactoryTalk Batch Server” in the
FactoryTalk Batch Administrator's Guide for information on the Server Options dialog
box.)

Define redundant servers

FactoryTalk Batch can be configured to store batch journals and batch restart information
in two separate locations. Using a secondary server allows you to perform a Manual
Failover if there is a hardware failure on the primary FactoryTalk Batch Server computer.
The second computer must be capable of running the server. Redundant servers are
defined by specifying the primary and secondary restart paths. These paths indicate where

38
 • • • • •
5 • Install FactoryTalk Batch Server/Client

system files are written if the system experiences a failure. If a secondary path is not
specified, FactoryTalk Batch does not write any secondary files. (See “Working With the
FactoryTalk Batch Server” in the FactoryTalk Batch Administrator’s Guide for
information on defining redundant servers.)
You must install area model and all recipe files on both the primary server and the secondary
server. You also must move activation files to the redundant server.

Configure the Windows Firewall (optional)

On Windows Server 2003 R2 with the Windows Firewall enabled: If you want to use the
firewall after the FactoryTalk Batch or RSBizWare eProcedure Server has been installed,
you must run the FactoryTalk Windows Firewall Configuration Utility.
1. From the Start menu, select All Programs > Rockwell Software > FactoryTalk
Tools, and then click Windows Firewall Configuration Utility.
2. The configuration utility starts. If the firewall has not been enabled, the following
dialog box opens. Click Yes to enable the firewall and continue.

3. When you click Yes, the utility continues and the configuration changes are made to
Windows Firewall, and the firewall is set to the new state (if different).
For a complete list of the exceptions made by the Windows Firewall Configuration Utility, refer to
the FactoryTalk Batch Administrator’s Guide.

Create an area model

Open the FactoryTalk Batch Equipment Editor and then create your area model. (See the
FactoryTalk Batch Equipment Editor User’s Guide for more information.)

Create recipes
Open the FactoryTalk Batch Recipe Editor and then create your recipes. (See the
FactoryTalk Batch Recipe Editor User’s Guide for more information.)

39
• • • • • FACTORYTALK BATCH INSTALLATION GUIDE

40
6 Install FactoryTalk Batch Client
This chapter instructs you in installing the FactoryTalk Batch Client software on a
computer other than the one on which the FactoryTalk Batch Server is installed. If you
have not yet installed and configured a FactoryTalk Batch Server computer, please go to
Chapter 5, “Install FactoryTalk Batch Server/Client”.
There are setup procedures that must be completed before and after you install the
FactoryTalk Batch Client. The Client installation process is divided into the following
three categories:
„ Pre-Installation Procedures
„ Installation Procedures
„ Configure the FactoryTalk Batch Client
Use the following checklist when installing the FactoryTalk Batch Client.

Pre-Installation Procedures for a FactoryTalk Batch Client Page

Install Windows Server 2003 or Windows XP, 42
‰ Install Operating System
Service Pack 2.
If you plan to develop with the ActiveX
‰ Install Microsoft Visual Basic 42
Controls Library on the client machine.
If the FactoryTalk Batch Server is using a
‰ Set Up Security local account, add this account to all 42
computers in the workgroup.
Specify the name of the computer where the
‰ Identify Server Names 43
FactoryTalk Batch Server is installed.
‰ Log on to Windows Log on with administrator privileges. 43
Enable the firewall if you want the setup
‰ Enable Windows Firewall (optional) 43
program to populate the firewall exceptions.
Install FactoryTalk Batch Client Page

Installing the FactoryTalk Services

‰ Install the FactoryTalk Services Platform. 45
Platform
Install the FactoryTalk Batch Client
‰ Install a FactoryTalk Batch Client 47
components.

41
• • • • • FACTORYTALK BATCH INSTALLATION GUIDE

Configure the FactoryTalk Batch Client Page

Each computer in the FactoryTalk Batch

‰ Set System Date and Time 50
system must be set the same.
Configure the Windows Application and
‰ Modify Event Log Settings 50
System logs.
Installing on a workgroup, setup users on the
‰ Modify Local Policy Security Settings 50
FactoryTalk Batch Client computer.
Skip this step if you installed your project
‰ Create a Shared Directory 50
files in the default directory, BATCHCTL.

Pre-installation procedures for FactoryTalk Batch Client

Before you install the FactoryTalk Batch Client you must install and configure the
Windows operating system, and install other third-party software that will be used with
your FactoryTalk Batch system.

Install operating system

For a FactoryTalk Batch Client only installation, install Microsoft Windows Server 2003
R2 Standard Edition or Microsoft Windows XP, Service Pack 2.

Install Microsoft Visual Basic (optional)

If you plan to develop with the ActiveX Controls Library, install Microsoft Visual Basic.
If you are using VB.NET with PC Based Phase Programming or ActiveX Controls, be aware that
Report, Request and Parameter properties appear as Methods in the .NET environment. If you
require further assistance, contact Rockwell Support.

Set up security
If the FactoryTalk Batch Server is using a local account, you must create Windows
accounts with the same name and password on all computers in the workgroup.
If you are implementing domain security, you must add the FactoryTalk Batch Server user
account to all remote FactoryTalk Batch View client computers. The following
configuration changes are implemented on the FactoryTalk Batch View remote computer.
1. Windows Server 2003: Click the Start button, point to All Programs >
Administrative Tools and then select Computer Management. The Computer
Management window opens.

Windows XP: Click the Start button, select Administrative Tools, and then select
Computer Management.
2. Expand Component Services.

42
 • • • • •
6 • Install FactoryTalk Batch Client

3. Right-click My Computer and select Properties. The My Computer Properties

dialog box opens.
4. Windows Server 2003: On the Default COM Security tab, select Edit Default in the
Access Permissions area.

Windows XP: On the COM Security tab, select Edit Default in the Access
Permissions area.
5. The Access Permission dialog box opens. Click Add.
6. Add the Batch Server Services user account, and then click OK.
7. Windows Server 2003: In the Permissions area of the Access Permission dialog box,
check Allow for Access Permission.

Windows XP: In the Permissions area of the Access Permission dialog box, check
Allow for Local Access and Remote Access.
8. Click OK twice, and then close Component Services.
FactoryTalk Security is used to support the FactoryTalk Batch Clients. The setup program
allows you to select either Open or Restricted Access. (For information on setting up
FactoryTalk Batch Client Security see “Understanding Batch Security” in the
FactoryTalk Batch Administrators Guide.)

Identify server names

If you are installing just the FactoryTalk Batch Client component, the setup program
prompts you for the name of the computer where the FactoryTalk Batch Server is
installed.

Log on to Windows
Log on to Windows with administrator privileges. Close any open applications.

Enable the Windows Firewall

If you want the installation program to populate the firewall exceptions automatically, you
must first enable Windows Firewall Service prior to running the installation. This allows
the Firewall Configuration Utility to add the necessary exceptions.

You must enable the service on both the Server and Client computers.

43
• • • • • FACTORYTALK BATCH INSTALLATION GUIDE

1. From the Start menu, point to Administrative Tools > Services. The Services dialog
box opens.

2. Right-click Windows Firewall/Internet Connection Service (ICS), and then click

Properties. The Windows Firewall/Internet Connection Service Properties dialog
box opens.

3. From the Startup type list, select Automatic, and then click OK. The service is
enabled.
4. Close the Services window.
If you have already installed FactoryTalk Batch or RSBizWare eProcedure, please see the
FactoryTalk Batch Administrator’s Guide for the required configuration changes to allow the
FactoryTalk Batch Server to speak with client applications with the firewall enabled.

For a complete list of the exceptions added to Windows Firewall during FactoryTalk
Batch component installation, see the FactoryTalk Batch Administrator’s Guide.

44
 • • • • •
6 • Install FactoryTalk Batch Client

Install the FactoryTalk Batch Client

These instructions assume that you are installing the FactoryTalk Batch Client on a
computer networked with other FactoryTalk Batch system computers. Before you begin
the installation, complete the pre-installation procedures. You can exit installation at any
time by clicking the Cancel button.

Install the FactoryTalk Services Platform

You must install the FactoryTalk Services Platform before installing FactoryTalk Batch or
RSBizWare eProcedure components.
1. Insert the installation CD into the CD-ROM drive. The installation process starts
automatically.

To start installation manually, click the Start button, and then select Run. In the Run dialog
box, type d:\setup (where d is the drive letter for the CD-ROM drive), and then click OK.

45
• • • • • FACTORYTALK BATCH INSTALLATION GUIDE

2. In the Welcome dialog box, click Install FactoryTalk Components. The

FactoryTalk Component Installation dialog box opens.

3. Click Install FactoryTalk Services Platform. The FactoryTalk Services Platform

2.10 (CPR 9) dialog box opens.

If the Microsoft .NET Framework is not already installed on your computer, you are prompted
to install it. When it is installed, the FactoryTalk Services Platform 2.10 (CPR 9) dialog box
opens.

4. Click Next.
5. In the License Agreement dialog box, read the license agreement, and then select I
accept the terms in the license agreement. Click Next.

46
 • • • • •
6 • Install FactoryTalk Batch Client

6. In the FactoryTalk Administration Console dialog box, select Install the

FactoryTalk Administration Console (if it is not already checked), and then click
Next.
You may see the Configuring FactoryTalk Directory progress box. It shows you that
any existing FactoryTalk Directories have been backed up, the backup file name(s),
and the path to the backup files.

The FactoryTalk Directory is configured during the installation process. It can be run
manually, however, if you need to define or reset a disabled Administrator account. (See
“Running the FactoryTalk Directory Configuration Wizard” for more information.)

7. Click Finish, then click Yes to restart your computer (if prompted to do so).

For more detailed information on FactoryTalk Directory installation and configuration, you can
view the FactoryTalk Administration Console help file (FTAdminEN.chm) located in
C:\Program Files\Common Files\Rockwell\Help.

Install the FactoryTalk Batch Client

Before installing the FactoryTalk Batch Client, you must install the FactoryTalk Services Platform
on the FactoryTalk Batch Client computer. The FactoryTalk Batch Server must be installed on the
same computer as the FactoryTalk Batch Client Components or the FactoryTalk Batch Server
must be installed on the FactoryTalk Batch network before installing the FactoryTalk Batch Client
Components.

1. In the Welcome dialog box, click Install FactoryTalk Batch (click Back to return to
the Welcome dialog box, if necessary). The FactoryTalk Batch Install Disk dialog
box opens.

If the installation program detects an existing RSBizWare/FactoryTalk Batch installation, it gives

you the option to remove the current installation. You must remove the existing version of the
software before installing the upgrade. See “Uninstalling the FactoryTalk Batch applications” for
instructions on removing the current installed version.

2. Click Install FactoryTalk Batch to start the installation process. The FactoryTalk
Batch InstallShield Wizard opens. Click Next.
3. In the License Agreement dialog box, select I accept the terms in the license
agreement. Click Next.

47
• • • • • FACTORYTALK BATCH INSTALLATION GUIDE

4. The FactoryTalk Directory Selection dialog box opens.

5. Select the desired FactoryTalk Directory (the default is Network), and then click Next.
6. In the Customer Information dialog box, type your name and organization in the
appropriate boxes, and then click Next.
7. In the Custom Setup dialog box, disable Server Components.

The default installation directory is C:\Program Files\Rockwell Software\Batch. To set a different

directory, click Change, select the desired directory, and then click OK.

48
 • • • • •
6 • Install FactoryTalk Batch Client

8. Click the Space button (near the bottom of the dialog box) and confirm there is
enough disk space for installing the selected options. The Disk Space Requirements
dialog box opens. If there is not adequate space, the drive is highlighted.
9. Click OK. If there was not adequate space, click Change to select a different drive (or
move/delete files from the selected drive), and then continue with the installation.
10. Click Next.
11. In the Existing Server Details dialog box, type the computer name of any existing
FactoryTalk Batch Server in the system. Click Next.
Do not use a double slash (\\) or any characters other than those in the actual server name. For
example, if the server name is \\DomainName\SERVER2, just enter SERVER2.

12. In the Batch User Name dialog box, type the domain or workgroup where the
FactoryTalk Batch Server is running, type the FactoryTalk Batch Server account
name, and then click Next.
13. In the Ready to Install the Program dialog box, verify your selections. If anything is
incorrect, click Back and make the appropriate corrections.

14. Click Install.

15. When prompted, click Finish, and then click Yes to restart your computer.

Configure the FactoryTalk Batch Client

You are now ready to configure the FactoryTalk Batch Client computer. The following
instructions are provided to assist you in this process.

49
• • • • • FACTORYTALK BATCH INSTALLATION GUIDE

Set system date and time

Each computer on the network must have the date and time set in the same manner. (See
“Configuring FactoryTalk Batch Settings” in the FactoryTalk Batch Administrator’s
Guide.)

Modify event log settings

Configure the Windows Application and System logs to overwrite events as needed. (See
“Modifying Event Log Settings” in the FactoryTalk Batch Administrator’s Guide.)

Modify local security policy settings

If your FactoryTalk Batch Client is installed on a workgroup and the operating system is
Windows XP, Service Pack 2, then you must configure the Local Security Policy
Settings. (See “Use FactoryTalk Security Accounts for Batch Clients” in the FactoryTalk
Batch Administrator’s Guide.)

Create a shared directory

If the FactoryTalk Batch Client is installed in a networked environment, and you have
installed the project files to a directory that is not located in the BATCHCTL share, you
must create a share for that project directory. (See “Understanding FactoryTalk Batch
Communications” in the FactoryTalk Batch Administrator’s Guide for information on
creating a shared directory.)

Configure the Windows Firewall (optional)

On Windows Server 2003 R2 with the Windows Firewall enabled: If you want to use the
firewall after the FactoryTalk Batch or RSBizWare eProcedure Server has been installed,
you must run the FactoryTalk Windows Firewall Configuration Utility.
1. From the Start menu, select All Programs > Rockwell Software > FactoryTalk
Tools, and then click Windows Firewall Configuration Utility.
2. The configuration utility starts. If the firewall has not been enabled, the following
dialog box opens. Click Yes to enable the firewall and continue.

50
 • • • • •
6 • Install FactoryTalk Batch Client

3. When you click Yes, the utility continues and the configuration changes are made to
Windows Firewall, and the firewall is set to the new state (if different).
For a complete list of the exceptions made by the Windows Firewall Configuration Utility, refer to
the FactoryTalk Batch Administrator’s Guide.

51
• • • • • FACTORYTALK BATCH INSTALLATION GUIDE

52
A Uninstalling the FactoryTalk Batch
Applications
This chapter explains how to uninstall earlier versions of the FactoryTalk® Batch
components: RSBizWare™ Batch, eProcedure® and MaterialTrack™. If you do not have
eProcedure or MaterialTrack installed, skip those sections in the following procedures.

You must have administrative privileges on the target computer in order to uninstall the software.

Backing up your files

Before uninstalling RSBizWare Batch 8.0 or earlier, you may want to back up the
following files (if you have not already backed them up). Close all applications, and stop
all Batch services (including the eProcedure Server).
Batch Server files
„ Batcharc.ini file (Batch\bin folder)
„ Batcharc.log file (Batch\bin folder)
„ Batchsvr.ini file (Batch\bin folder)
„ BatchIDCreation.dll (Batch\bin folder) (only if it has been customized)
„ BatchID Custom folder
„ Simulator configuration files (.sim files in any Recipes folder)
„ DSDF files (only if customized)
Batch Client files
„ Area models (Recipes folder) (Back up if stored on server node.)
„ Journal folders and contents (Back up if stored on server node.)
„ Log folders and contents (Back up if stored on server node.)
„ Recipes folders and contents (Back up if stored on server node.)
„ Custom bitmaps stored in the bmp folder
„ Batcheqp.ini file (Batch\bin folder)
„ Batchrcp.ini file (Batch\bin folder)
„ Batchvew.ini (Batch\bin folder)

53
• • • • • FACTORYTALK BATCH INSTALLATION GUIDE

eProcedure files
Before uninstalling RSBizWare eProcedure 8.0, back up all instruction files associated
with eProcedure, close all applications, and stop all Batch services.
„ Instruction files
„ User.asp files (if customized)
„ eProcedure databases
„ Any customized files that support the User.asp
MaterialTrack files
„ Materialserver.log file (Batch\bin folder)
„ MaterialBasedRecipe database
„ MaterialBasedRecipe_MAJ database
„ Sample2_Materials database (if used)
„ Any other material-based recipe databases unique to your facility

Uninstalling Batch 8.0 components

The steps required to uninstall Batch, eProcedure, and MaterialTrack are discussed in the
following section. You must complete all steps in this section that apply to the products
you are using to successfully uninstall Batch, eProcedure, and/or MaterialTrack.

Be sure you have backed up any customized Batch, eProcedure or MaterialTrack Server/Client
files, such as area models, databases, etc. Refer to the instructions given in the chapter specific
to your Batch system.

Allow the Message Queue to clear

(MATERIALTRACK USERS ONLY)

Allow the message queue that handles communication between the Material Server and
the Material Activity Journal to clear before proceeding.
1. Click the Start button, point to Programs > Administrative Tools, and then select
Computer Management. The Computer Management window opens.
2. Expand Services and Applications, expand Message Queuing, and then select the
Private Queues folder. The list of queues displays in the right pane.
3. Wait until the number of messages in the materialtrack, materialtrack_0, and
material_track0-4 queues reaches 0 (zero).

54
 • • • • •
A • Uninstalling the FactoryTalk Batch Applications

Disable the Material Server

(MATERIALTRACK USERS ONLY)

Before running the uninstall program, you must disable the Material Server.
1. On the Master Node computer in your RSBizWare network, open the Network Editor.
To identify the Master Node, open the Network Editor on any computer. In the left
pane select Network Model. In the right pane, the name of the Master Node displays
after User Name (ignore \username if present).
2. In the left pane, right-click the Material Server, and then select Remove Server.
3. Click the Synchronize button.
4. From the File menu, select Exit, and then click Yes to exit the Network Editor.

Disable COM+ Security and shut down the COM+ application

(MATERIALTRACK USERS ONLY)

Before you can shut down the COM+ application, you need to disable the security.
1. Click the Start button, point to Programs > Administrative Tools, and then select
Component Services. The Component Services window opens.
2. Expand Components Services, expand the Computers folder, expand My
Computer, and then select the COM+ Applications folder. The COM+ applications
display in the right pane.
3. Right-click MaterialTrack, and then select Properties. The MaterialTrack
Properties dialog box opens.
4. Select the Advanced tab, and then clear the Disable deletion and Disable changes
options.
5. Click OK.
6. Right-click MaterialTrack, and then select Properties. The MaterialTrack
Properties dialog box opens.
7. Select the Security tab, clear Enforce access checks for this application, and select
Perform access checks only at the process level. Security property will not be
included in the object context. COM+ security call context will not be available.
8. Click OK.
9. Right-click MaterialTrack and select Shut down.
10. Close the Component Services window.

55
• • • • • FACTORYTALK BATCH INSTALLATION GUIDE

Run the uninstall program

Before uninstalling Batch, eProcedure, or MaterialTrack, back up all files and database(s)
associated with these applications, then close all applications, and stop all Batch Services.

The CPR 9 (v. 9.00) installation programs for FactoryTalk Batch, RSBizWare eProcedure and
RSBizWare MaterialTrack now have a Remove option that displays if a previous version of the
software is detected. If that does not completely remove the software, use the following
procedures.

1. Click the Start button, point to Control Panel, and the select Add/Remove
Programs. The Add/Remove Programs dialog box opens.
2. To uninstall the FactoryTalk Batch Client or Server, select FactoryTalk Batch, and
then click Remove. A message box opens prompting you to confirm the removal.
3. Click Yes. The uninstall program runs and removes Batch.
4. To uninstall RSBizWare eProcedure, select RSBizWare eProcedure, and then click
Remove. A message box opens prompting you to confirm the removal.
5. Click Yes. The uninstall program runs and removes eProcedure. You may be prompted
to restart the computer.
6. To uninstall the RSBizWare MaterialTrack Client or Server, select RSBizWare
MaterialTrack, and then click Remove. A message box opens prompting you to
confirm the removal.
7. Click Yes. The uninstall program runs and removes MaterialTrack.
8. Restart the computer.

Delete the COM+ application

MaterialTrack users:
1. Click the Start button, point to Programs > Administrative Tools, and then select
Component Services. The Component Services window opens.
2. Expand Components Services, expand the Computers folder, expand My
Computer, and then select the COM+ Applications folder. The COM+ applications
display in the right pane.
3. Right-click MaterialTrack and select Delete. A message box opens prompting you to
confirm the deletion.
4. Click Yes.
5. Close the Component Services window.

56
 • • • • •
A • Uninstalling the FactoryTalk Batch Applications

FactoryTalk Batch / eProcedure users:

You must remove the FactoryTalk Batch Server’s user account from the DCOM settings before
installing the R2 upgrade on a Windows Server 2003 computer.

1. Click Start, point to Administrative Tools and then select Component

Services. The Component Services window opens.
2. Expand Component Services.
3. Right-click My Computer and select Properties. The My Computer
Properties dialog box opens.
4. On the Default COM Security tab, select Edit Default in the Access
Permissions area. The Access Permission dialog box opens.
5. Select the Batch Server’s user account from the list and then click Remove.
6. Click OK twice and close Component Services.
7. Install Service Pack 1 and then restart the computer.
8. Next, repeat steps 1 - 3.
9. On the COM Security tab, select Edit Default in the Access Permissions area.
The Access Permission dialog box opens.
10. Click Add. The Select Users, Computers, or Groups dialog box opens.
11. Type the Batch Server’s user account name, and then click OK.
12. In the Permissions area of the Access Permission dialog box, check Allow for
Remote Access.
13. Click OK twice and then close Component Services.

Delete the account profile running MaterialTrack

(MATERIALTRACK USERS ONLY)

1. Open Windows Explorer.

2. On the local drive, right-click the rpmServer (default) folder or the account folder
under which MaterialTrack is running, and then select Delete.

57
• • • • • FACTORYTALK BATCH INSTALLATION GUIDE

Delete the default directories

Make sure you have backed up files that are affected by the uninstall process before deleting the
default directories. (See “Backing up your files ” above for instructions.)

1. Open Windows Explorer.

2. Expand the Program Files folder, and then select the Rockwell Software folder. The
Batch folder displays in the right pane.
3. Right-click the Batch folder, and then select Sharing and Security. The Batch
Properties dialog box opens to the Sharing tab.
4. Select Do not share this folder, and then click OK.
5. Right-click the Batch folder, and then select Delete. A message box opens prompting
you to confirm the deletion.
6. Click Yes.
7. Close Windows Explorer.

Remove Registry subkeys

Make sure you have completed the procedure for backing up registry security settings before
removing registry subkeys.

1. Click the Start button, and then select Run. The Run dialog box opens.
2. In the Open box, type regedt32, and then click OK. The Registry Editor opens.
3. Expand HKEY_LOCAL_MACHINE on Local Machine.
4. Double-click the SOFTWARE subkey.
5. Select the BATCHCTL subkey, and then press the DELETE key. A warning box
opens prompting you to confirm the deletion.
6. Click Yes.
7. Close the Registry Editor.
The FactoryTalk Batch applications have been removed from the computer.

58
B Troubleshooting Your Installation
If you installed the Windows Server 2003 R2 upgrade without first removing the
FactoryTalk Batch Server’s user account, complete the following steps.
1. On a remote computer, open Component Services and point to Component
Services > Computers.
2. Right-click on Computers and select New > Computer. The Add Computer
dialog box opens.
3. Type the FactoryTalk Batch client computer’s name and click OK. The Batch
client computer is added.
4. Right-click on the [FactoryTalk Batch client computer] and select Properties.
5. On the COM Security tab, select the Batch Server’s user account and click
Remove.
6. Click OK twice and close Component Services.
7. Return to the FactoryTalk Batch client computer and restart.
8. Next, repeat steps 1– 3.
9. On the COM Security tab, select Edit Default in the Access Permissions area.
The Access Permission dialog box opens.
10. Click Add. The Select Users, Computers, or Groups dialog box opens.
11. Type the FactoryTalk Batch Server’s user account name, and then click OK.
12. In the Permissions area of the Access Permission dialog box, check Allow for
Remote Access.
13. Click OK twice and then close Component Services.

Running the FactoryTalk Directory Configuration Wizard

The FactoryTalk® Directory Configuration Wizard runs silently during the FactoryTalk
Service Platform installation or upgrade. It can be run manually, however, if you need to
define or reset a disabled Administrator account.

59
• • • • • FACTORYTALK BATCH INSTALLATION GUIDE

1. From the Windows Start menu, select All Programs > Rockwell Software >
FactoryTalk Tools, and then select FactoryTalk Configuration Wizard. The
FactoryTalk Directory Configuration Wizard opens.

FactoryTalk Batch, RSBizWare eProcedure® and RSBizWare BatchCampaign™

store client configuration settings in the Local and Network Directory, therefore the
following steps discuss both directories.
2. Select FactoryTalk Network Directory and FactoryTalk Local Directory and then
click Next.

60
 • • • • •
B • Troubleshooting Your Installation

3. The Reconfigure FactoryTalk Network Directory dialog box opens.

4. Type the User name and Password for an existing Network administrator account.
Re-type the password in the Confirm password box.
5. Click Next. The Reconfigure FactoryTalk Local Directory dialog box opens.

6. Type the User name and Password for an existing Local administrator account. Re-
type the password in the Confirm password box, and then click Next.

61
• • • • • FACTORYTALK BATCH INSTALLATION GUIDE

7. The Summary displays.

If “All Users” is selected, the Windows group, Authenticated Users, is added to the Local
Directory during installation.

8. Click Close to exit the wizard.

9. Click Finish, then click Yes to restart your computer (if prompted to do so).
For more detailed information on FactoryTalk Directory installation and configuration, you can
click the Help button on the wizard dialog box, or view the FactoryTalk Administration Console
help file (FTAdminEN.chm) located in C:\Program Files\Common Files\Rockwell/Help.

62
Index

A F
area model FactoryTalk Activation
open 39 install 30
FactoryTalk Batch Client
B install 34, 47
FactoryTalk Batch components 19
back up your files 53
FactoryTalk Batch Server
FactoryTalk Batch Client 53
install 34
FactoryTalk Batch Server 53
FactoryTalk Batch View
RSBizWare eProcedure 54
enhancements 11
RSBizWare MaterialTrack 54
FactoryTalk Directory Administrator
Batch Server
reset disabled account 59
computer 15
FactoryTalk Directory Configuration
identify name of 26
Wizard 59
BatchVEW.ini
FactoryTalk Services Platform
new key 11
installing 28, 45
C G
configuration requirements
grace period 10
for Windows Server 2003 17
configure
Windows Firewall 39, 50 H
create how to use install guide 1
shared directory 50 hyperthreading support 8

D I
DCOM configuration 15 identify
DCOM settings Batch Server name 26, 43
remove 57 install
default directories FactoryTalk Activation 30
delete 58 FactoryTalk Batch Client 47
delete FactoryTalk Batch Server & Client 34
COM+ application 56, 57 FactoryTalk Services Platform 28, 45
disable security 55 Microsoft Visual Basic 26
dongles 30 Microsoft Visual Basic (optional) 42
SQL Server 2005 26
E installation procedures
FactoryTalk Batch Client 34, 47
enhancements
FactoryTalk Batch Server 34
FactoryTalk Batch View 11
ErrorLogMaxFileSize 11
EVRSI activation 30

vii
• • • • • FACTORYTALK BATCH INSTALLATION GUIDE

L FactoryTalk Batch Server

configure the Server options 38
language support 17
create a shared directory 38
define redundant servers 38
M modify event log settings 38
Material Server set security on the Logs and Journals
disable 55 folders 38
message queue set system date and time 37
allow to clear 54 pre-installation procedures
Microsoft compatibility list 15 Batch Client
Microsoft Visual Basic identify Batch Server name 43
install (optional) 42 install Microsoft Visual Basic
modify (optional) 42
event log settings 50 install operating system 42
local security policy settings 50 set up security 42
multi-processor support 8 Batch Server
identify Batch Server name 26
N install SQL Server 2005 26
install the operating system 24
NetDDE services 26
install Visual Basic 26
new features
set up security 26
in FactoryTalk Batch 3
eProcedure Server
in RSBizWare Batch components 3
install the operating system 24
new system requirements 4
NTFS drives 15
R
O redundant servers, define 38
reset a disabled FactoryTalk Directory
operating system
Administrator account 59
verify 24
optional software
Microsoft Visual Basic 26 S
SQL Server 2005 26 server placement 19
set up security
P Batch Client 42
Batch Server 26
placing the server 19
shut down
post-installation procedures
COM+ application 55
Batch Client
SQL Server 2005
create shared directory 50
install 26
modify event log 50
system requirements 4, 15
modify local security policy settings 50
set system date and time 50
Batch Server T
open the area model 39 troubleshooting
Windows Server 2003 R2 upgrade 59

viii
 • • • • •
INDEX

U
uninstall 54
default directories 58
delete COM+ application 56, 57
delete MaterialTrack account profile 57
disable security 55
disable the Material Server 55
message queue 54
remove registry subkeys 58
run program 56
shut down COM+ apps 55

V
verify
operating system 24

W
Windows Firewall
configuration utility 39, 50
configure 39, 50
configuring after installing Batch 39, 50
configuring after installing eProcedure 39,
50
enable service 27, 43
exceptions 27, 43
service, enable 27, 43

ix