Bzware In001 - en P

INTEGRATED PRODUCTION & PERFORMANCE SUITE
RSBIZWARE ADMINISTRATORS GUIDE

PUBLICATION BZWARE-IN001G-EN-PAugust 2007
Supersedes Publication BZWARE-IN001F-EN-P
Contact Rockwell Copyright Notice
Trademark Notices
Other Trademarks
Warranty
Technical Support Telephone 440-646-3434 Online support http://www.rockwellautomation.com/support 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. FactoryTalk, Rockwell Automation, Rockwell Software, and RSLinx are registered trademarks of Rockwell Automation, Inc. The following logos and products are trademarks of Rockwell Automation, Inc.: RSBizWare, the RSBizWare logo, FactoryTalk Historian Classic, FactoryTalk Scheduler, FactoryTalk Activation, FactoryTalk Administration Console, FactoryTalk Services Platform, FactoryTalk Diagnostics, FactoryTalk Directory, FactoryTalk Security, FactoryTalk Metrics, and FactoryTalk Transaction Manager. ActiveX, Microsoft, SQL Server, and Windows either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. Oracle, and SQL*Net are registered trademarks of Oracle Corporation. All other trademarks are the property of their respective holders and are hereby acknowledged. This product is warranted in accordance with the product license. The products 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 products 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 (CPR9) Modified: July 12, 2007 6:27 pm
ii
Contents
RSBizWare 9.0 Installation Checklist 1 Welcome to RSBizWare
Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Database administrator/Network administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . RSBizWare administrator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The RSBizWare architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FactoryTalk Administration Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Service Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Security Services Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RSBizWare databases (SQL Server or Oracle) . . . . . . . . . . . . . . . . . . . . . . . . . . . Information Services Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Report Schedule Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Web-based client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Scheduler Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Scheduler Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FactoryTalk Transaction Manager Configuration Server. . . . . . . . . . . . . . . . . . . . FactoryTalk Transaction Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Metrics Server Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Where can I go for help? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reference the release notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reference the Users Guides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reference the online help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Get RSBizWare training . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Get phone support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Get Web support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Get on-site support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Get consulting services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Contact us . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ix 1
1 1 1 2 3 4 4 4 4 4 5 5 5 5 5 5 6 6 6 6 6 7 7 8 8 8 8
2 RSBizWare Prerequisites
Hardware requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Software requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Database server requirements/recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
iii
Running RSBizWare in a distributed environment . . . . . . . . . . . . . . . . . . . . . . . . . . RSBizWare Product Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A note about Windows DEP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DEP Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing DEP settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware DEP Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14 14 15 15 16 17
3 Installing or Upgrading the RSBizWare Software

Installation or upgrade? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing new RSBizWare software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the FactoryTalk Services Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing FactoryTalk Historian Classic, Metrics, and Scheduler . . . . . . . . . . . . Installing RSBizWare FactoryTalk Activations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using FactoryTalk Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring the Windows Firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrading an existing RSBizWare installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparing for an upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrading the FactoryTalk Services Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrading FactoryTalk Historian Classic, Metrics, and Scheduler . . . . . . . . . . . Removing RSBizWare programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Removing the FactoryTalk Activation Server software . . . . . . . . . . . . . . . . . . . . . . . Removing the FactoryTalk Services Platform software. . . . . . . . . . . . . . . . . . . . . . .
19
19 20 20 21 23 23 26 26 27 27 28 30 30 31
4 Installing and Creating a SQL Server Database

Installation or upgrade? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SQL Server 2000 versus SQL Server 2005 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SQL Server 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SQL Server 2005 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using SQL Server 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing SQL Server 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing Service Pack 4 for SQL Server 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a SQL Server 2000 database for use with RSBizWare . . . . . . . . . . . . . Creating a database owner in SQL Server 2000. . . . . . . . . . . . . . . . . . . . . . . . . . Using SQL Server 2005 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a user account for SQL Server 2005 . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing Internet Information Services (IIS) . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing other prerequisite software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing or Upgrading to SQL Server 2005 . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing Service Pack 1 for SQL Server 2005 . . . . . . . . . . . . . . . . . . . . . . . . . .
33
33 34 34 34 34 34 37 37 40 42 42 43 43 44 48
iv
CONTENTS
Creating a SQL Server 2005 database for use with RSBizWare . . . . . . . . . . . . . Creating a database owner in SQL Server 2005. . . . . . . . . . . . . . . . . . . . . . . . . . Creating an ODBC system DSN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrading your existing RSBizWare database . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
48 50 52 54
5 Administering a Security Services Manager
55
Registering a Security Services Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
6 Administering RSBizWare Servers

Registering an RSBizWare server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring Information Services Manager, Metrics Server Manager, or Scheduler Server settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing RSBizWare sample data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting and stopping an RSBizWare server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing Information Services Manager scheduled items . . . . . . . . . . . . . . . . . . . . Administering Information Services Manager external data sources. . . . . . . . . . . . . Configuring Information Services Manager default permissions. . . . . . . . . . . . . . . . Configuration Console object permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Report permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Report object permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Filter permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Report data source permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Administering FactoryTalk Metrics user-defined summarization criteria . . . . . . . . . Handling temporary database connection loss in the Information Services Manager The Metrics Server Manager Settings file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
57
57 58 61 61 61 62 63 65 65 66 66 66 67 68 70
7 Controlling Access to Your RSBizWare System

Software activation options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FactoryTalk Scheduler activation options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FactoryTalk Historian Classic activation options. . . . . . . . . . . . . . . . . . . . . . . . . FactoryTalk Historian Classic for Batch activation options. . . . . . . . . . . . . . . . . FactoryTalk Metrics activation options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Assigning activations to RSBizWare Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing FactoryTalk user groups and users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Importing RSBizWare groups and users into FactoryTalk . . . . . . . . . . . . . . . . . Creating user group accounts and user accounts . . . . . . . . . . . . . . . . . . . . . . . . . Creating a FactoryTalk user group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding a Windows-linked user group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a FactoryTalk user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding a Windows-linked user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
77
78 78 78 81 81 84 85 85 86 88 89 90 91
Application privileges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 FactoryTalk Historian Classic and FactoryTalk Metrics (Configuration Console) privileges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Managing user access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Assigning application privileges to groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Assigning application privileges to users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Assigning client activations to users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Assigning object permissions to users and groups . . . . . . . . . . . . . . . . . . . . . . . . 98
8 Configuring Data Collection
99
Registering the FactoryTalk Transaction Manager Configuration Server . . . . . . . . . 99 Defining a FactoryTalk Transaction Manager configuration . . . . . . . . . . . . . . . . . . 100 Control connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Enterprise connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Defining a FactoryTalk Transaction Manager connector . . . . . . . . . . . . . . . . . . . . . 105 Registering a FactoryTalk Transaction Manager configuration. . . . . . . . . . . . . . . . 106 Unregistering a FactoryTalk Transaction Manager configuration . . . . . . . . . . . . . . 109 Configuration startup and shutdown. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
9 Diagnostics Reporting
Message types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Output types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Log file configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
113
113 113 114 116
A Advanced Topics
117
Remote connection to an RSBizWare server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 Registering the Excel Add-in as a non-installing user . . . . . . . . . . . . . . . . . . . . . . . 117
B Database Tips
Maintaining frequently-used RSBizWare tables and indexes . . . . . . . . . . . . . . . . . Using Oracle with RSBizWare. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended database settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tuning an Oracle database for use with FactoryTalk Historian Classic . . . . . .
119
119 120 120 122
vi
CONTENTS
C Data Compression
Why use data compression? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How does data compression work? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . What will my compression ratio be? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How do I view my compressed data? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparing the SQL Server Uncompress view . . . . . . . . . . . . . . . . . . . . . . . . . . . Querying the SQL Server Uncompress view . . . . . . . . . . . . . . . . . . . . . . . . . . . Data compression considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
125
125 126 127 127 127 128 129
Index
131
vii
viii
RSBizWare 9.0 Installation Checklist

Follow the steps below to install and configure the RSBizWare software successfully. A copy of this checklist, printed on card stock, is distributed in the box with the product software.
PREREQUISITES
Hardware and Software Requirements Distribution Issues Make sure the computers on which you are installing the RSBizWare software meet these minimum hardware and software requirements. Read this section if you are installing the server and/or data collection components of the RSBizWare software onto several computers.
PAGE
Page 9
Page 14
INSTALLATION
Software Installation Software Upgrade Follow these instructions to install the RSBizWare software for the first time. Follow these instructions to upgrade the RSBizWare software from a previous version.
PAGE
Page 19 Page 19
CONFIGURATION
Database Configuration Create a SQL Server or Oracle database and an ODBC system DSN for use with FactoryTalk Historian Classic, FactoryTalk Metrics, and FactoryTalk Scheduler. Register the Security Services Manager that you will use to administer your RSBizWare software. Register and configure an Information Services Manager, Metrics Server Manager, Scheduler Server, or any combination of the three. This step is optional. Install the RSBizWare sample data for demonstration or training purposes. Assign activations to servers, create groups and users, and assign privileges to groups and users.
PAGE
Page 33 or Page 120 Page 55
Security Services Manager Registration RSBizWare Server Configuration Sample Data Installation Security Configuration
Page 57
Page 61 Page 77
ix
CONFIGURATION
Data Collection Configuration This step is for FactoryTalk Historian Classic and FactoryTalk Metrics users only. All other users can skip this step. Register a FactoryTalk Transaction Manager Configuration Server and create one or more FactoryTalk Transaction Manager configurations for data collection. FactoryTalk Historian Classic for Batch Oracle Upgrade This step is for FactoryTalk Historian Classic for Batch for Oracle users only. All other users can skip this step. Initialize or upgrade your RSBizWare database to Oracle 9i. Please refer to the FactoryTalk Historian Classic for Batch Users Guide available on the RSBizWare software installation CD-ROM. This step is for FactoryTalk Historian Classic for Batch users only. All other users can skip this step. Configure FactoryTalk Historian Classic for Batch in the Batch Archiver and the Batch Equipment Editor. Please refer to the FactoryTalk Historian Classic for Batch Users Guide document available on the RSBizWare software installation CD-ROM. Access and make use of RSBizWare diagnostic information.
PAGE
Page 100
FactoryTalk Historian Classic for Batch Configuration
Troubleshooting
Page 113
Welcome to RSBizWare
RSBizWare is a suite of tools and services aimed at increasing your manufacturing floor effectiveness and profitability with solutions that target scheduling, performance analysis and improvement, and data acquisition and integration. With the RSBizWare suite of tools you can: Improve gross margins and net profit without adding capacity or increasing your order volume. Gain a higher return on your investments in enterprise resource planning, customer relationship management, supply chain management, and shop-floor automation. Predict delivery dates accurately. See the impact of change so you can respond proactively.
Intended audience
The RSBizWare Administrators Guide is designed to help you understand the components that make up the RSBizWare suite of products. It also describes the steps required to install and configure the RSBizWare software properly and the options you have when deploying the RSBizWare software in your enterprise. This document is intended for the following types of users of the RSBizWare software:
Database administrator/Network administrator

This is the individual who is responsible for creating and maintaining system databases and network resources including logon accounts. This individual should be familiar with: Microsoft Windows operating systems User accounts and security in the enterprise Microsoft SQL Server or Oracle Enterprise Manager Open Database Connectivity (ODBC)
RSBizWare administrator
This is the individual who is responsible for installing and configuring the RSBizWare system so that it is ready for use by the individuals who will be using the client software. This individual should be familiar with: Microsoft Windows operating systems User accounts and security within the RSBizWare system
1
Open Database Connectivity (ODBC) Control system architecture, plant model (physical layout), and data model If connecting to external data sources, the RSBizWare administrator should be familiar with the location and structure (schema) of those databases
The RSBizWare architecture

The RSBizWare architecture is highly scalable. You can install the entire system on a single computer, or you can distribute services across several computers on a network. For example, you may choose to install the administrative and data collection services on a server-class computer in a secured room, while the client software is installed on several computers throughout your enterprise. The RSBizWare architecture has been optimized for performance and ease of administration. This leads to a system in which each functional application (e.g., FactoryTalk Metrics) is not always contained in a single software component. In many cases, a functional application may reside in several of the software components that make up the RSBizWare architecture. To understand this relationship, you need to understand the RSBizWare software architecture as shown in the following diagrams.
1 WELCOME TO RSBIZWARE
FactoryTalk Administration Console

The FactoryTalk Administration Console is stand-alone tool that allows the configuration and management of FactoryTalk-enabled applications. You must install at least one instance of the FactoryTalk Administration Console. You will use the FactoryTalk Administration Console to: Create and configure application, area, and data server elements in the FactoryTalk Directory. Set up redundancy for OPC data servers. Configure client computers to recognize the location of a FactoryTalk Directory server. Configure options for routing and logging system-wide diagnostic messages. View system-wide diagnostic messages. Create and configure system groups and users.
Service Console
At the center of the RSBizWare architecture is the Service Console. The Service Console is a Microsoft Management Console (MMC) snap-in that provides administrative functions for RSBizWare services. The Service Console is capable of accessing and controlling RSBizWare services that are running on computers across a TCP/IP network or on the local computer. It supports the tasks of server administration, activation and privilege assignment, and any custom functionality specific to the RSBizWare service that is being managed.
Note: The Service Console requests access to the Windows Service Control Manager with the SERVICE_ALL_ACCESS Access Right. Because of this the Windows user who logs into the Service Console is required to be a Windows administrator.
Security Services Manager

The Security Services Manager is the primary Windows service with which the Service Console interacts when performing its administration functions. RSBizWare application servers, such as the Information Services Manager, are registered with a Security Services Manager as part of the initial configuration process. There is generally a single Security Services Manager running in an enterprise.
RSBizWare databases (SQL Server or Oracle)

The FactoryTalk Historian Classic, FactoryTalk Metrics, and FactoryTalk Scheduler applications require a single database for permanent storage. Although they share the same database, each application uses unique tables to support its core functions. The RSBizWare database can be either a Microsoft SQL Server database or an Oracle database. If you plan to use Microsoft SQL Server, SQL Server 2000 and any required service packs can be installed from the CDs included with the software. If you plan to use an Oracle database, the Oracle database software must be installed on a computer that is accessible to the computers that will host the RSBizWare applications.
Information Services Manager

The Information Services Manager is a Windows service that provides all FactoryTalk Historian Classic and Metrics Server Manager functionality, including FactoryTalk Historian Classic time-series data configuration and storage, and FactoryTalk Metrics performance parameter data configuration and storage.
Report Schedule Manager

The Report Schedule Manager is a user application that runs, minimized, in the system tray. The Report Schedule Manager controls the execution of reports that have been scheduled by a Configuration Console and logs diagnostic results. Typically, the Report
Schedule Manager is on the computer where the Information Services Manager is installed.
Configuration Console
The Configuration Console provides FactoryTalk Historian Classic and FactoryTalk Metrics client functionality, including the ability to configure the plant model, shift patterns, FactoryTalk Historian Classic time-series data collection, and FactoryTalk Metrics performance parameters, and to create and/or view RSBizWare reports. The Configuration Console also provides FactoryTalk Historian Classic for Batch add-on functionality.
Web-based client
Web-based clients such as Microsoft Internet Explorer provide the ability to connect to the Information Services Manager and view RSBizWare reports without having the RSBizWare software installed on the client computer; instead, the Information Services Manager hosts a special Web page, the QuickWeb Home Page, to give users view-only access to RSBizWare reports stored on the Server.
Scheduler Server
The Scheduler Server is a Windows service that provides all FactoryTalk Scheduler server functionality for creating, modifying, and analyzing production schedules.
Scheduler Client
The Scheduler Client provides FactoryTalk Scheduler client functionality, including the ability to create, modify, and analyze production schedules for jobs that are to be produced using a limited set of resources.
FactoryTalk Transaction Manager Configuration Server

The FactoryTalk Transaction Manager Configuration Server is a Windows service that runs continuously to provide a single interface to the configuration files (.dat files) that make up FactoryTalk Transaction Manager. The Configuration Server simplifies access to configuration files by filtering all changes to the files and interfacing with other FactoryTalk Transaction Manager services. A collection of all changes that affect a configuration can be recorded in an audit trail.
FactoryTalk Transaction Manager

FactoryTalk Transaction Manager is an industrial transaction manager that provides a bidirectional link from control systems to enterprise databases. In the RSBizWare suite, FactoryTalk Transaction Manager Lite is an embedded component that is used by
FactoryTalk Historian Classic and FactoryTalk Metrics as the underlying data acquisition engine.
Metrics Server Manager

The Metrics Server Manageralso referred to as the FactoryTalk Metrics Enterprise Connectionis a Windows service that resides between FactoryTalk Transaction Manager and the RSBizWare database in order to provide an optimized engine for FactoryTalk Metrics calculations. All FactoryTalk Transaction Manager transactions that are created for FactoryTalk Metrics data collection send data to the Metrics Server Manager, not directly to the database. The Metrics Server Manager manages all timers, counters, and formulas defined in the FactoryTalk Metrics application, summarizes raw control system data, and creates PlantMetrics Workcell History and PlantMetrics Event History records in the RSBizWare database.
Where can I go for help?

Our commitment to your success starts with the suite of learning aids and assistance we provide with the RSBizWare product suite. Consult the following resources for additional information about these products:
Reference the release notes

The electronic release notes provide a list of the hardware and software that are necessary to use the RSBizWare software effectively and a list of known issues, issue fixes, and new features that are available in the current release of the software. The release notes are available from the RSBizWare software installation CD-ROM and from within the online help systems in the client applications.
Reference the Users Guides

The product Users Guides are designed to help you understand how to access and use the RSBizWare products. The Users Guides are focused on the end-user functions of the RSBizWare applications and do not cover installation and operation of underlying system services. A printed copy of the Users Guide for each product is distributed in the box with the product software and an electronic copy of the guide is available from the RSBizWare software installation CD-ROM.
Reference the online help

The online help provides general overview information, comprehensive step-by-step procedures, quick-start topics, and context-sensitive control definitions (for example, text boxes, drop-down lists, and option buttons) for working with all of the features in each of the RSBizWare applications. To view online help:
While running the Configuration Console software, select Help > Configuration Console Help from the menu in the client application main window. While running the Service Console application, select Action > Help from the menu in the console window. Click the Help button on any client application dialog. Tab to a control on the dialog and press F1.
Get RSBizWare training

One of the best ways to increase your proficiency at using Rockwell Automation products is to attend Rockwell Automation training programs. Our training programs can help you master the basics and show you how to unleash the full potential of our software. We offer a wide range of training programs, from regularly scheduled classes conducted at Rockwell Automation facilities to custom-tailored classes conducted at your enterprise. The size of each class is kept small intentionally to maximize student engagement. If you would like more information about our training programs, visit the Rockwell Automation site on the World Wide Web or contact the Rockwell Automation Training Coordinator. Our World Wide Web address and telephone numbers appear on the inside front cover of this document.
Get phone support

Rockwell Automations support team of outstanding professionals provides top-notch technical supportmonitoring and tracking your experience with our products to pave the road to your success in understanding and improving your factory performance. Rockwell Automation provides full support for the entire RSBizWare suite of products, which include FactoryTalk Historian Classic, FactoryTalk Metrics, FactoryTalk Transaction Manager, and FactoryTalk Scheduler. Questions concerning installation and the use of the software are handled by the Rockwell Automation Customer Support Center, staffed Monday through Fridayexcept U.S. holidaysfrom 8 AM to 5 PM Eastern time zone for calls originating within the U.S. and Canada. To reach the Customer Support Center, call 440-646-3434 and follow the prompts. For calls originating outside the U.S./Canada, locate the number in your country by visiting support.rockwellautomation.com and selecting the Phone/On-site link. A list will be presented from which you can locate the number to call in your country. WHEN
YOU CALL
When you call, you should be at your computer and prepared to give the following information:
the product serial number and version number, which can be found in the client software by selecting Help > About the type of hardware you are using the exact wording of any errors or messages that appeared on your screen a description of what happened and what you were doing when the problem occurred a description of how you attempted to solve the problem
Get Web support

In addition to phone support, the Rockwell Automation Customer Support Center offers extensive online knowledgebases of tech notes and frequently asked questions for support of non-urgent issues. These databases are updated daily by our support specialists. To receive regular e-mail messages with links to the latest tech notes, software updates, and firmware updates for the products that are of interest to you or to submit an online support request, visit support.rockwellautomation.com and select the Online link.
Get on-site support

Rockwell Automation field support engineers are located around the globe to provide assistance with special projects, unexpected problems, or emergency situations on-site. Field support engineers are available for dispatch 24x7x365 and can arrive at many locations the same day. To learn more about this and other support services, visit the Customer Support Web site at support.rockwellautomation.com.
Get consulting services

Rockwell Automation provides expert consulting and turnkey implementation of the RSBizWare suite. Please contact your local representative for more information.
Contact us
We strive to help all of our customers become successful in their manufacturing improvement efforts. Toward this objective, we invite you to contact your local representative or Rockwell Automation at any time that we may be of service to you.
RSBizWare Prerequisites
This chapter details the minimum hardware and software requirements that your computer must meet in order to use the RSBizWare software effectively; the issues that you must consider when upgrading from a previous version of FactoryTalk Historian Classic, FactoryTalk Metrics, or FactoryTalk Scheduler; and the issues that you must consider when installing components of the RSBizWare software onto more than one computer.
Hardware requirements
The RSBizWare products are highly configurable and scalable applications, and hardware requirements vary considerably depending upon the size and architecture of the application. For example: The server and database components of an RSBizWare application can be resident on a single computer, or distributed between multiple computers. The computer requirements for each architecture will be different. The entry-level FactoryTalk Historian Classic application allows 150 tags, the largest FactoryTalk Historian Classic application allows 70,000 tags. The largest has over 450 times more tags than the smallest. Obviously, a computer that runs a 150-tag system adequately will have little chance of running a 70,000-tag system. Similarly, the largest Metrics Server Manager has 40 times the workcell count of the smallest server. FactoryTalk Metrics has no license limits on the number of custom events configured in an application. So it is possible to configure a 100 workcell system (for example) that logs anywhere between zero and millions of custom events per day. Obviously, as you increase the number of workcells that you monitor and increase the number of events that you track, you will need progressively more powerful computers to effectively handle the load. The number of clients accessing the system and viewing reports has an impact on hardware requirements. The specifications for server computers listed here are to be considered minimums for a very small RSBizWare application where all services are running on one computer, or for larger applications where there is a separate database server. Your Rockwell Automation salesperson or system integrator should be able to help you assess the hardware requirements for your particular application.
Note: All RSBizWare software can be run on single processor, dual processor, and dual-core processor computers. Note: The RSBizWare installer requires a minimum of 30 MB of free disk space on the drive containing the temporary folder (identified by the User TMP environment variable). If the drive
containing the temporary folder does not have this much free disk space, you must either free up the appropriate amount of disk space or move the temporary folder to a drive that contains sufficient disk space.
To use the Information Services Manager effectively, your server computer should be a server class machine and must have at least: 2.0 GHz Pentium 4 processor (the Information Services Manager supports multiple processors) 1 GB of RAM 100 MB of free hard disk space to install RSBizWare with an additional 300 MB if you plan to install Microsoft SQL Server on this computer or an additional 400 MB if you plan to install the Oracle client software on this computer. You should also plan on additional disk space, as required, to accommodate the data you will collect and store in the database. 1024 x 768 resolution monitor CD-ROM compatible drive (for installation purposes) 3.5-inch diskette drive (to install disk-based activations; not required for FactoryTalk Activation) To use the Scheduler Server effectively, your server computer should be a server class machine and must have at least: 2.0 GHz Pentium 4 processor 1 GB of RAM 300 MB of free hard disk space to install RSBizWare with an additional 300 MB if you plan to install Microsoft SQL Server on this computer or an additional 400 MB if you plan to install the Oracle client software on this computer. You should also plan on additional disk space, as required, to accommodate the data you will collect and store in the database. 1024 x 768 resolution monitor CD-ROM compatible drive (for installation purposes) 3.5-inch diskette drive (to install disk-based activations; not required for FactoryTalk Activation) To use the Configuration Console effectively, your personal computer must have at least: 200 MHz Pentium II processor or better
10
2 RSBIZWARE PREREQUISITES
64 MB of RAM 112 MB of free hard disk space 800 x 600 resolution monitor CD-ROM compatible drive or network connection to the server (for remote installation) To use the RSBizWare Client (web only) effectively, your personal computer must have at least: 50 MB of free hard disk space for ActiveX install To use the Scheduler Client effectively, your personal computer must have at least: 300 MHz Pentium II processor or better (A processor speed of 900 MHz or better is recommended. FactoryTalk Schedulers data processing routines can be calculation intensive, so a faster processor results in less time required to perform these activities.) 128 MB RAM or higher (Due to the calculation-intensive processing, the more RAM available, the faster the calculations will be.) 60 MB of free hard disk space for software install Access to a shared network drive to store production data files Since FactoryTalk Scheduler has a graphical interface that typically contains many items, a 21-inch monitor is recommended CD-ROM-compatible drive or network connection to the server (for remote installation)
Software requirements
To use the Information Services Manager or the Scheduler Server software effectively, the software installed on your server computer must meet the following minimum requirements: Microsoft Windows 2000 Server (Service Pack 3 or higher), Windows XP (Service Pack 2), or Windows Server 2003 Standard Edition (Service Pack 1 or R2)
Note: To access QuickWeb as a Windows-linked user, a user must have Windows login access rights to the computer running the Information Services Manager.
Microsoft Internet Explorer 6.0 (Service Pack 1) (available from the RSBizWare software installation CD-ROM)
11
SQL Server or Oracle (see Database server requirements/recommendations on page 13 for details) Microsoft Data Access Components (MDAC) 2.8 (MDAC 2.8 is installed with the Information Services Manager and Scheduler Server software) FactoryTalk Services Platform (available from the RSBizWare software installation CD-ROM) FactoryTalk Activation (available from the FactoryTalk Activation CD-ROM.) Adobe Acrobat Reader 8.0 to view documentation (available from the RSBizWare software installation CD-ROM) ODBC Driver Manager 3.510 or higher TCP/IP network connectivity To use the Configuration Console software effectively, the software installed on your personal computer must meet the following minimum requirements: Windows 2000 Professional or Windows 2000 Server (Service Pack 3 or higher), Windows XP (Service Pack 2), or Windows Server 2003 Standard Edition (Service Pack 1 or R2) Microsoft Internet Explorer 6.0 (Service Pack 1) (available from the RSBizWare software installation CD-ROM) If you will be using the Configuration Console to configure FactoryTalk Historian Classic or FactoryTalk Metrics data collection, your personal computer must also have Microsoft Data Access Components (MDAC) 2.8 (MDAC 2.8 is installed with the Configuration Console software) Adobe Acrobat Reader 8.0 to view documentation (available from the RSBizWare software installation CD-ROM) HTTP 1.1 (To make sure this is active on the client computer, open Internet Explorer and select Tools > Internet Options from the menu. Click the Advanced tab and confirm that the Use HTTP 1.1 check box under the HTTP 1.1 Settings tree is selected.) TCP/IP network connectivity
Note: Using Windows Server 2003 R2 Standard Edition Terminal Services, you can run the Service Console, Configuration Console, Excel Add-In, and QuickWeb user interfaces in terminal sessions to communicate with an Information Services Manager running on a remote machine.
To use the RSBizWare Client (web only) software effectively, the software installed on your personal computer must meet the following minimum requirements:
12
Microsoft Internet Explorer 6.0 (Service Pack 1) (available from the RSBizWare software installation CD-ROM) To use the Scheduler Client software effectively, the software installed on your personal computer must meet the following minimum requirements: Windows 2000 Professional (Service Pack 3 or higher) or Windows XP (Service Pack 2) Microsoft Internet Explorer 6.0 (Service Pack 1) (available from the RSBizWare software installation CD-ROM) Microsoft Data Access Components (MDAC) 2.8 (MDAC 2.8 is installed with the Scheduler Client software) Adobe Acrobat Reader 8.0 to view documentation (available from the RSBizWare software installation CD-ROM)
Database server requirements/recommendations

Though it is not required to have a separate machine to store the RSBizWare database, it is recommended. You database server must meet the following requirements and should meet the specified recommendations. For instructions on installing SQL Server 2000 or SQL Server 2005, see Installing and Creating a SQL Server Database on page 33.
Requirements
SQL Server 2000 (Service Pack 4) or SQL Server 2005 (Service Pack 1); or Oracle 8.1.7, Oracle 9.2.0.1.0, or Oracle 10G. (A licensed version of Microsoft SQL Server 2005 Standard Edition is included with the RSBizWare software on separate CDs.) For SQL ServerSQL Server ODBC driver SQLSRV32.DLL version 3.7 or higher For Oracle 8.1.7Oracle ODBC driver version 8.01.74 or 8.01.75 and a version 8.1.7 Net8 client For Oracle 9.2.0.1.0Oracle ODBC driver version 9.02.00.06 and a version 9.02 Net client For Oracle 10G R2 StandardOracle ODBC driver version 10.02.00.01 and a version 10.2.0.1 Net client Microsoft Data Access Components (MDAC) 2.8 (available from the RSBizWare software installation CD-ROM)
13
ODBC Driver Manager 3.510 or higher TCP/IP network connectivity
Recommendations
Dual processors (Pentium III Xeon or better). Data storage options: RAID (For small implementations, RAID 1 is recommended. For large implementations, RAID 10 is recommended. RAID 10 is the best option, but is the most expensive. SQL Server can run well with RAID 1 arrays. One RAID 1 for data files and one RAID 1 for transaction log), or storage on an array of disks. If you use an array of disks for storage, we recommend the following: SQL ServerAt least 2 SCSI drives using different controller cards, one drive to store the Transaction Log and one drive to store the data files OracleIt is a good idea to separate the following files onto different disks for the best performance: Disk 1 - Data files Disk 2 - Index files Disk 3 - Temp files Disk 4 - Rollback Segment files Disk 5 - System tables and Control files 1 GB RAM.
Running RSBizWare in a distributed environment

If you plan to run RSBizWare clients outside your company network, you may need to open a port on your corporate firewall so that external RSBizWare clients can connect to an RSBizWare server. For information on opening a port on your corporate firewall, see Remote connection to an RSBizWare server on page 117.
RSBizWare Product Dependencies

This section lists the dependencies between the RSBizWare products and other Rockwell Automation products. Software media from Rockwell Automation bear a Coordinated Product Release (CPR) code (i.e., CPR#) to identify compatibility with other Rockwell Automation applications. The FactoryTalk Services Platform and all of the FactoryTalkenabled software products participating in the same automation system must be part of the same CPR. When running multiple software applications from Rockwell Automation, you are advised to confirm the compatibility of the versions before proceeding with installation.
14
The following RSBizWare products are dependant on the FactoryTalk Services Platform: FactoryTalk Historian Classic FactoryTalk Metrics FactoryTalk Scheduler The following RSBizWare products depend on the RSBizWare Platform features: FactoryTalk Historian Classic FactoryTalk Metrics FactoryTalk Scheduler FactoryTalk Historian Classic for Batch Factory Talk Web Services (FTWS) FactoryTalk Transaction Manager Datapoint Migration Tool The following RSBizWare products are dependant on FactoryTalk Transaction Manager: FactoryTalk Historian Classic FactoryTalk Metrics
A note about Windows DEP

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.
Note: Rockwell Software recommends that you use the default DEP settings unless you have a specific reason to change them.
DEP settings Setting AlwaysOn Description Full DEP protection for the entire system (all applications and components, no exceptions). Supported by Rockwell Software Products? No
15
DEP settings Setting OptIn Description Supported by Rockwell Software Products?
Yes DEP-enabled only for Windows system components and for applications that explicitly opt in. This is the default setting for Microsoft Windows XP (Service Pack 2). DEP-enabled for all processes except Yes those that explicitly opt out. This is the default setting for Microsoft Windows Server 2003 (Service Pack 1 and R2). DEP protection is disabled for the entire system (all applications and components, no exceptions). Note: Rockwell Software does not recommend using this setting, since it will make your system more vulnerable to malicious code. Yes
OptOut
AlwaysOff
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.
Note: Keep the following in mind:
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.
16
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 Knowledge base article at: http://support.microsoft.com/kb/875352.
17
18
Installing or Upgrading the RSBizWare Software

This chapter describes how to install new RSBizWare software on your computer and how to upgrade an existing RSBizWare installation. These instructions are for a stand-alone system on a single computer. All install and upgrade functions are performed on the local machine only. It is recommended that you quit all Windows application programs before installing or upgrading the RSBizWare software. If you are running Windows 2000 or Windows Server 2003 and are performing the RSBizWare software server installation tasks, you must have the Windows System Administrator privilege, and your user account must be a member of the local administrator user group. After you are finished with the steps described in this chapter, be sure that you refer to the RSBizWare Installation Checklist on page ix of this document for software configuration instructions. The software will not run until you complete the configuration steps listed on the checklist.
Important! If you encounter problems during RSBizWare installation and you need to call
support, make sure that you have access to the log file created during installation. This file is named RSBizWareX_YY_ZZ.log, where X corresponds to the major version number, YY to the minor version number, and ZZ to the patch number. It is usually located in the \Documents and Settings\username\Local Settings\Temp folder, where username is the name of the installing user. However, this location can vary depending on the value of the %TEMP% environment variable. This file contains information that can help support identify the cause of your installation problem.
Installation or upgrade?
Installation versus upgrade If you are... Installing new software Upgrading an existing installation See... Installing new RSBizWare software on page 20 Upgrading an existing RSBizWare installation on page 26
19
Installing new RSBizWare software

If you are installing new RSBizWare software, you must do the following: 1. Install the FactoryTalk Services Platform. For instructions, see Installing the FactoryTalk Services Platform on page 20. 2. Install FactoryTalk Historian Classic, FactoryTalk Metrics, and FactoryTalk Scheduler. For instructions, see Installing FactoryTalk Historian Classic, Metrics, and Scheduler on page 21. 3. After installing new RSBizWare software, you should do the following: Install the activations for your new software. For more instructions, see Installing RSBizWare FactoryTalk Activations on page 23. Configure the Windows firewall for use with RSBizWare. For more instructions, see Configuring the Windows Firewall on page 26.
Installing the FactoryTalk Services Platform

The FactoryTalk Services Platform contains centralized security services managed by FactoryTalk Security. It is strongly recommended that you review the default security policies described in the FactoryTalk Services Platform documentation. When you fully understand FactoryTalk Security, you will need to determine how you want to use it with RSBizWare. 1. Insert the RSBizWare product CD into the CD-ROM drive. If the Windows autoplay feature has not been disabled, the RSBizWare software autorun screen will display. If the autoplay feature has been disabled on your computer, start the Windows Explorer, navigate to the CD drive that contains the CD, and double-click the autorun.exe file.
Note: You should read the RSBizWare software release notes before installing the software. The release notes may contain more up-to-date information than was available when this document was published. A shortcut to the release notes is available from the autorun dialog on the RSBizWare Software CD.
2. From the main menu of the autorun screen, click Installation. 3. On the Installation dialog, click Install FactoryTalk Services Platform. After the install program checks for installed applications, the Welcome page of the FactoryTalk Services Platform installation wizard will display. 4. On the Welcome dialog, click Next. 5. On the License Agreement dialog, read the terms of the agreement and select the I accept... option if you want to continue the installation. Click Next to continue.
20
3 INSTALLING OR UPGRADING THE RSBIZWARE SOFTWARE
6. Confirm that the Install the FactoryTalk Administration Console option is selected and click Next to continue. 7. On the Ready to Install the Program dialog, click Install to start the installation. The status of the install will be displayed on the wizard page. During install, the wizard performs the following tasks: Configures a FactoryTalk Local Directory and a FactoryTalk Network Directory.
Note: The RSBizWare products make use of the Network Directory only.
Adds the local Windows Administrators group to the FactoryTalk Administrators group in each directory. This allows any user, logged in with a Windows Administrators account, access to either directory. Allows all new user accounts full access to either directory. If you want to tighten security, you can change system polices and restrict access rights for specific user accounts and for groups of users, as described in the FactoryTalk Services Platform documentation. 8. Click Finish to complete the installation.
Installing FactoryTalk Historian Classic, Metrics, and Scheduler

1. From the main menu of the autorun screen, click Installation. 2. On the Installation dialog, click Install RSBizWare to display the Welcome page of the RSBizWare installation wizard. 3. On the Welcome dialog, click Next. 4. On the License Agreement dialog, read the terms of the agreement and select the I accept... option if you want to continue the installation. Click Next to continue. 5. On the Customer Information dialog you must enter your user information and a valid serial number. You can find your serial number on the Activation Certificate that shipped with the RSBizWare software. The serial number you enter here will be displayed in the About box of the client software and will be requested in the event that you need to call the Rockwell Automation support center. Click Next to continue. 6. The Setup Type dialog allows you to select the type of installation that you want to perform. Select an installation type and click Next to continue. Complete This option will install all three RSBizWare applications FactoryTalk Historian Classic, FactoryTalk Metrics, and FactoryTalk Scheduler and all of their required client and server components on the local computer. The
21
wizard will install the software in the C:\Program Files\Rockwell Software\RSBizWare\ directory on the local computer. This installation option is useful if you want everything to run on a single machine. You should not use this installation option if either of the following is true: You dont want to install all three RSBizWare applications. You want to distribute the installation among several computers. Client This option will install the Configuration Console only. The wizard will install the software in the C:\Program Files\Rockwell Software\RSBizWare\ directory on your computer. This option is useful if you have already performed the complete installation on a server-class computer and you are now installing the client on workstations throughout your enterprise. Custom This is the most flexible option for installing the RSBizWare software. This is useful if you want to choose the applications and components that are installed or if you want to specify a custom install path.
Note: It is NOT recommended that you attempt to run the Complete RSBizWare install or the Custom RSBizWare install from a networked CD image on a remote computer. During the installation, the computer will reboot and the installation may resume before the remote network drives are mounted, which will result in an installation error. If you have an image of the RSBizWare product CD on a remote network drive, it is recommended that you first copy the installation directories from the CD to a temporary location on the local computers hard drive and run the installation from the hard drive. You can delete the temporary copy of the CD image from the hard drive after the installation is complete.
7. If you selected the Custom option in the previous step, the Custom Setup dialog will display. This dialog allows you to choose the software components that will be installed and to change the install path from the default. To select a component, click the icon graphic to the left of the text and select This feature will be installed on local hard drive from the menu that is displayed. The current install path is listed at the bottom of the dialog. To change the install path, click the Change button to browse to a different destination directory. When you are satisfied with your software component selections and your installation path, click Next to continue.
Note: If you specify a drive other than the default system application drive (typically, the C drive) for the FactoryTalk Transaction Manager component, some of the files associated with that component will be installed on the default system application drive.
8. The Ready to Install the Program dialog will ask you to verify that you are ready to begin installing the software. Click Install to begin the installation, which will take several minutes to complete.
22
9. When the installation is complete, the InstallShield Wizard Completed dialog will display. Click the Finish button to exit the Installation Wizard. 10. When prompted to restart your system, click Yes.
Note: If you have never used a Microsoft System Installer (MSI) installation program, be aware that the process may require more than one reboot.
Installing RSBizWare FactoryTalk Activations

Rockwell Automations products are copy-protected. Only computers with access to the proper activation can run the software. The FactoryTalk Historian Classic, FactoryTalk Metrics, and FactoryTalk Scheduler products are activated by FactoryTalk Activation files, generated by Rockwell Automation and distributed over the Internet (although you can still use FactoryTalk Activation without Internet access). RSBizWare activations are installed onto the machine where the Security Services Manager is running. NEW
CUSTOMERS
If you have purchased a new FactoryTalk Historian Classic, FactoryTalk Metrics, or FactoryTalk Scheduler version 9.0 (CPR 9) product, you must activate the software using the FactoryTalk Activation process described below. UPGRADE
CUSTOMERS
If you are upgrading a FactoryTalk Historian Classic, FactoryTalk Metrics, or FactoryTalk Scheduler application that uses FactoryTalk activations or have purchased additional FactoryTalk activations with your FactoryTalk Historian Classic, FactoryTalk Metrics, or FactoryTalk Scheduler upgrade, you must activate them using the FactoryTalk Activation process. If you are upgrading a FactoryTalk Historian Classic, FactoryTalk Metrics, or FactoryTalk Scheduler application that uses existing EvRSI activations, your EvRSI activations are valid with the new software and you will continue to use the Move Activation utility to manage those activations. After you upgrade to version 9.0, your existing activations should be recognized by the software.
Note: EvRSI activation will be replaced by FactoryTalk Activation in a future release. If you are using EvRSI activation, please contact your local Rockwell Automation Sales office or Technical Support for information on migrating your activations to FactoryTalk Activation. For Rockwell Automation Technical Support in the U.S. call (440)646-3434. Outside the U.S. see http://www.rockwellautomation.com/locations/.
Using FactoryTalk Activation

This new, streamlined process activates your software via activation files generated by Rockwell Automation and distributed over the Internet (although you can still use
23
FactoryTalk Activation without Internet access). Please note that you should follow these activation instructions to activate RSBizWare properly. For more information about FactoryTalk Activation, see the FactoryTalk Activation help available at Start > Programs > Rockwell Software > FactoryTalk Activation > FactoryTalk Activation Help, as well as the Activate Your Rockwell Automation Products flyer that was included with your RSBizWare CD package.
There are two options for activating your software with FactoryTalk Activation:
Install the FactoryTalk Activation tool on your Security Services Manager machine. Install the FactoryTalk Activation tool on a remote machine that can serve as an Activation Server. If you are running several Rockwell Automation products at your location, you may want to use an Activation Server to streamline activation of your Rockwell Automation products in the future. INSTALLING FACTORYTALK ACTIVATION MANAGER:
ON THE
SECURITY SERVICES
Note: The FactoryTalk Activation tool and files only need to be installed on the Security Services Manager machine. No activation files are loaded onto client machines.
1. Insert the FactoryTalk Activation Server CD into the CD-ROM drive. If the Windows autoplay feature has not been disabled, the FactoryTalk autorun screen will display. If the autoplay feature has been disabled on your computer, start the Windows Explorer, navigate to the CD drive that contains the CD, and double-click the autorun.exe file. 2. Install the FactoryTalk Activation Server software. 3. The FactoryTalk Activation Server installation wizard will open. Choose a Complete install. 4. After the main part of the installation wizard completes, the HASP Device Driver Installation wizard will launch automatically. If you need to use a dongle to activate any of the software that will run on this machine, install this device driver via this wizard; otherwise, cancel this installation wizard. This device driver is not needed to activate RSBizWare or any of its components. 5. Click Finish to exit the FactoryTalk Activation Server installation. 6. The FactoryTalk Activation Wizard will open. Click Next to begin the activation process. 7. Enter your product serial number and product key (printed on the Activation Certificate document, enclosed with the software CD). Click Next.
24
8. After checking for activations, your activation status will be displayed. Enter your number of activations. Click Next. 9. Choose the I need product activation for this computer option. Click Next. 10. Highlight your network connection. Click Next. 11. Confirm your selections. Click Next. 12. Your activation file location will be displayed as well as your Host ID. If you would like to activate additional software, select the Activate More Software checkbox. Click Finish. 13. Open the FactoryTalk Activation Server tool via Start > Programs > Rockwell Software > FactoryTalk Activation > FactoryTalk Activation Tool. 14. Click the Rehost Activations tab to view the activations. (Click the Start button on the Settings tab to run the Activation Server so that your activations will display in the Current Activations tab; you may need to click Refresh).
What if I don't have Internet access on my computer? If Internet access is
available in your facility, but not available from the computer where you want to activate your new software, you can download an activation file to the computer with Internet access; then copy the activation file to the computer where the activation is needed. 1. On the computer without Internet access, follow Steps 1-5 in the previous section. 2. Using the FactoryTalk Activation Server tool, get the Host ID of that machine and write it down. 3. On a computer with Internet access, follow Steps 6-12; however, in Step 9, choose the I need product activation for another computer option. Use the Host ID copied earlier. 4. The activation file will be written to this machine. Copy the activation file to the computer without Internet access. The default activation directory is: C:\Program Files\Common Files\Rockwell\ Activations. 5. Continue with Steps 13-14 in the previous section. INSTALLING FACTORYTALK
ACTIVATION FROM AN
ACTIVATION SERVER:
If you have purchased several Rockwell Automation products, you may choose to load all of your activation files on a different server than your software (an Activation Server) and then activate RSBizWare (and your other Rockwell Automation products) from that server.
25
1. Install and run the FactoryTalk Activation Server tool (on the FactoryTalk Activation Server CD) on the Activation Server machine. 2. Use the Activation Servers Host ID to activate your software product. 3. Install and run the FactoryTalk Activation Client tool from the FactoryTalk Activation Server CD on the Security Services Manager machine (RSBizWare should already be installed on this machine).
Note: No activation files are loaded onto client machines.
4. Click the Settings tab and then enter the path to the Activation Server. 5. Before you can use the new activations, reboot the Security Services Manager machine.
Need more help? For help at any point, click the Help button on any FactoryTalk Activation tool dialog or FactoryTalk Activation Transfer tool dialog, or click the Help link on the Rockwell Automation Activation Web site at http://licensing.software.rockwell.com.
If you cannot connect to the Internet, call Technical Support for help creating an activation file from an e-mail or fax. In North America, call 1-440-646-3434. Outside North America, call your local support organization.
Configuring the Windows Firewall

If you are running RSBizWare on Windows Server 2003 or Windows XP and you intend to use the Windows Firewall, consult the topic entitled Configuring the Windows Firewall for RSBizWare in the RSBizWare Release Notes.
Upgrading an existing RSBizWare installation

If you are upgrading an existing RSBizWare installation, you must do the following: 1. Make sure that you have made the appropriate upgrade preparations. For more information, see Preparing for an upgrade on page 27. 2. Upgrade the FactoryTalk Services Platform. For instructions, see Upgrading the FactoryTalk Services Platform on page 27. 3. Upgrade FactoryTalk Historian Classic, FactoryTalk Metrics, and FactoryTalk Scheduler. For instructions, see Upgrading FactoryTalk Historian Classic, Metrics, and Scheduler on page 28. 4. Security groups and users created in earlier versions of RSBizWare can be imported into FactoryTalk using the RSBizWare FactoryTalk Security Import tool. See Importing RSBizWare groups and users into FactoryTalk on page 85 for instructions on running the import tool.
26
Preparing for an upgrade

If you are upgrading from a prior version of the FactoryTalk Metrics, FactoryTalk Historian Classic, or FactoryTalk Scheduler software, there are several things that you should take into consideration before you proceed with the upgrade: It is recommended that you create a backup copy of your RSBizWare database, FactoryTalk Transaction Manager configurations, and sesame.dat filelocated in the directory into which the software was installedbefore beginning the upgrade process. The RSBizWare software will automatically upgrade your existing RSBizWare database as part of the configuration process. However, if you are running RSBizWare on SQL Server 2000, you may want to upgrade to SQL Server 2005 after upgrading RSBizWare. For more information, see Upgrading your existing RSBizWare database on page 54. Before upgrading your automation system software from an earlier version of FactoryTalk Services Platform, take note of the following key points: You must uninstall all Rockwell Automation products that depend on FactoryTalk before uninstalling and reinstalling the FactoryTalk Services Platform on the same computer. The FactoryTalk Services Platform, and all of the FactoryTalk-enabled software products participating in the same automation system, must be part of the same Coordinated Product Release (CPR). To upgrade to FactoryTalk Services Platform 2.10.00, all participating software products must also be upgraded to versions that support CPR 9. For a networked automation system, upgrade the computer hosting the Network Directory Server first, and then upgrade the client computers on the network. After installing FactoryTalk Services Platform, reinstall the software products that you plan to use in the automation system. All of the participating FactoryTalk-enabled software products must support CPR 9.
Upgrading the FactoryTalk Services Platform

1. Insert the RSBizWare product CD into the CD-ROM drive. If the Windows autoplay feature has not been disabled, the RSBizWare software autorun screen will display. If the autoplay feature has been disabled on your computer, start the Windows Explorer, navigate to the CD drive that contains the CD, and double-click the autorun.exe file.
Note: You should read the RSBizWare software release notes before upgrading the software. The release notes may contain more up-to-date information than was available
27
when this document was published. A shortcut to the release notes is available from the autorun dialog on the RSBizWare Software CD.
2. From the main menu of the autorun screen, click Installation. 3. On the Installation dialog, click Install FactoryTalk Services Platform. After the install program checks for installed applications, you will see a dialog telling you that a previous version of FactoryTalk Services Platform is installed. Click Next to proceed with the upgrade. 4. On the Welcome dialog, click Next. 5. On the License Agreement dialog, read the terms of the agreement and select the I accept... option if you want to continue the upgrade. Click Next. 6. Confirm that the Install the FactoryTalk Administration Console option is selected and click Next. 7. On the Ready to Install the Program dialog, click Install to start the installation. The status of the install will be displayed on the wizard page. During install, the wizard will back up existing FactoryTalk Directories and configure a FactoryTalk Local Directory and a FactoryTalk Network Directory. The Configuring FactoryTalk Directory dialog will display the names of the files to which the existing FactoryTalk Directories have been backed up and the name of the Windows folder where the backup files are written. Backup locations will also be logged to FactoryTalk Diagnostics.
Note: The RSBizWare products make use of the Network Directory only.
8. On the Finish dialog of the FactoryTalk Services Platform installation wizard, click Finish to complete the upgrade.
Upgrading FactoryTalk Historian Classic, Metrics, and Scheduler

1. From the main menu of the autorun screen, click Installation. 2. On the Installation dialog, click Install RSBizWare to display the Welcome page of the RSBizWare installation wizard. 3. On the Welcome dialog, click Next. 4. On the License Agreement dialog, read the terms of the agreement and select the I accept... option if you want to continue the upgrade. Click Next to continue. 5. On the Customer Information dialog you must confirm your user information and serial number. You can find your serial number on the Activation Certificate (for
28
FactoryTalk Activation) that shipped with the RSBizWare software or on the activation floppy disk (for master disk activation). The serial number you enter here will be displayed in the About box of the client software and will be requested in the event that you need to call the Rockwell Automation support center. Click Next to continue. 6. The Setup Type dialog allows you to select the type of upgrade that you want to perform. Select a setup type and click Next to continue. Complete This setup option will upgrade all three RSBizWare applications FactoryTalk Historian Classic, FactoryTalk Metrics, and FactoryTalk Scheduler and all of their required client and server components on the local computer. The wizard will install the software in the C:\Program Files\Rockwell Software\RSBizWare\ directory on the local computer. This installation option is useful if you want everything to run on a single machine. You should not use this setup option if either of the following is true: You dont want to upgrade/install all three RSBizWare applications. You want to upgrade a multi-computer installation. Client This option will upgrade the Configuration Console only. The wizard will install the software in the C:\Program Files\Rockwell Software\RSBizWare\ directory on your computer. This option is useful if you have already performed the complete installation on a server-class computer and you are now installing the client on workstations throughout your enterprise. Custom This is the most flexible option for upgrading the RSBizWare software. This is useful if you want to choose the applications and components that are upgrade.
Note: It is NOT recommended that you attempt to run the Complete RSBizWare install or the Custom RSBizWare install from a networked CD image on a remote computer. During the installation, the computer will reboot and the installation may resume before the remote network drives are mounted, which will result in an installation error. If you have an image of the RSBizWare product CD on a remote network drive, it is recommended that you first copy the installation directories from the CD to a temporary location on the local computers hard drive and run the installation from the hard drive. You can delete the temporary copy of the CD image from the hard drive after the installation is complete.
7. If you selected the Custom option in the previous step, the Custom Setup dialog will display. This dialog allows you to choose the software components that will be installed and to change the install path from the default. To select a component, click the icon graphic to the left of the text and select This feature will be installed on local hard drive from the menu that is displayed.
29
The current install path is listed at the bottom of the dialog, though you cannot change the install path. When you are satisfied with your software component selections, click Next to continue.
Note: If you specify a drive other than the default system application drive (typically, the C drive) for the FactoryTalk Transaction Manager component, some of the files associated with that component will be installed on the default system application drive.
8. The Ready to Install the Program dialog will ask you to verify that you are ready to begin upgrading the software. Click Install to begin the upgrade, which will take several minutes to complete. 9. When the upgrade is complete, the InstallShield Wizard Completed dialog will display. Click the Finish button to exit the Installation Wizard. 10. When prompted to restart your system, click Yes.
Note: If you have never used a Microsoft System Installer (MSI) installation program, be aware that the process may require more than one reboot.
Removing RSBizWare programs

If you wish to remove selective RSBizWare components from your computer, run the RSBizWare installation program again and choose the Modify option. If you wish to uninstall all RSBizWare components from your computer, perform one of the following: Run the RSBizWare installation program again and choose the Remove option. Select Settings > Control Panel > Add/Remove Programs from the Windows Start menu. The Windows Add/Remove Programs utility will display. Highlight the RSBizWare entry and click the Remove button to uninstall all RSBizWare components. No reboot is required when uninstalling RSBizWare.
Removing the FactoryTalk Activation Server software

If you wish to remove the FactoryTalk Activation Server software from your computer, select Settings > Control Panel > Add/Remove Programs from the Windows Start menu. The Windows Add/Remove Programs utility will display. Highlight the FactoryTalk Activation Server entry and click the Remove button to uninstall the FactoryTalk Activation Server software.
30
Removing the FactoryTalk Services Platform software

If you wish to remove the FactoryTalk Services Platform software from your computer, select Settings > Control Panel > Add/Remove Programs from the Windows Start menu. The Windows Add/Remove Programs utility will display. Highlight the FactoryTalk Services Platform entry and click the Remove button to uninstall the FactoryTalk Services Platform software.
31
32
Installing and Creating a SQL Server Database

The FactoryTalk Historian Classic, FactoryTalk Metrics, and FactoryTalk Scheduler applications require a single database for permanent storage. Although they share the same database, each application uses unique tables to support its core functions. This database is referred to as the RSBizWare database. The RSBizWare database can be either a Microsoft SQL Server database or an Oracle database. If you plan to use Microsoft SQL Server, read this chapter to learn how to create a SQL Server database for use with FactoryTalk Historian Classic, FactoryTalk Metrics, and FactoryTalk Scheduler. (If you plan to use Oracle, see Using Oracle with RSBizWare on page 120.) If you intend to use Report Expert with RSBizWare, you must install SQL Server 2005. When you install Report Expert, the installation automatically creates a Reporting Services database that is separate from the RSBizWare database. This database is referred to as the Report Expert database.
Installation or upgrade?
Installation versus upgrade If you are... Installing new software Upgrading an existing installation See... SQL Server 2000 versus SQL Server 2005 on page 34 Upgrading your existing RSBizWare database on page 54
33
SQL Server 2000 versus SQL Server 2005

You can use either SQL Server 2000 or SQL Server 2005 with RSBizWare. However, if you intend to install and use Report Expert with RSBizWare, you must install SQL Server 2005.
SQL Server 2000

If you intend to use SQL Server 2000, do the following: 1. Install the database software, apply the corresponding service pack, create an RSBizWare database, and create a database owner as described in Using SQL Server 2000 on page 34. 2. Create an ODBC system DSN for the database as described in Creating an ODBC system DSN on page 52.
SQL Server 2005

If you intend to use SQL Server 2005, do the following: 1. (Strongly recommended.) Create a separate Windows user account under which to run the SQL Server processes as described in Creating a user account for SQL Server 2005 on page 42. 2. Install the Microsoft Internet Information Services (IIS) component as described in Installing Internet Information Services (IIS) on page 43. 3. Install the database software, apply the corresponding service pack, create an RSBizWare database, and create a database owner for the RSBizWare database as described in Using SQL Server 2005 on page 42. 4. Create an ODBC system DSN for the RSBizWare database as described in Creating an ODBC system DSN on page 52.
Using SQL Server 2000

Follow the instructions in this section if you intend to use SQL Server 2000.
Installing SQL Server 2000

If you want to use SQL Server 2000, you must obtain the software separately. Follow these instructions to install SQL Server 2000. 1. To install SQL Server from the CD, insert the SQL Server CD into the CD-ROM drive. If the Windows autoplay feature has not been disabled, the SQL Server 2000 software autorun screen will display. If you disabled the autoplay feature on your
34
4 INSTALLING AND CREATING A SQL SERVER DATABASE
computer, start the Windows Explorer, navigate to the CD drive that contains the SQL Server CD, and double-click the autorun.exe file. 2. Select the SQL Server 2000 Components option from the autorun screen to display the Install Components screen. 3. Select the Install Database Server option to display the Welcome dialog for the Installation Wizard. Click Next to display the Computer Name dialog. 4. Make sure the Local Computer option is selected and click Next to display the Installation Selection dialog. 5. Make sure that the Create a new instance... option is selected and click Next to display the User Information dialog. 6. Enter your user information and click Next to display the End-User License Agreement. 7. Make sure you read the terms of the software license agreement and click Yes if you want to continue the installation and display the CD-Key dialog. 8. Enter your 25-digit key and click Next to display the Installation Definition dialog. 9. The Installation Definition dialog allows you to specify the SQL Server tools that will be installed on the local machine. Choose the Server and Client Tools option and click Next to display the Instance Name dialog. 10. Make sure the Default box is checked and click Next to display the Setup Type dialog.
35
11. Select the Typical installation option and click Next to display the Services Accounts dialog.
12. Select the Use the same account for each service option and the Use the Local System account Service Settings option. Click Next to display the Authentication Mode dialog.
13. Select the Mixed Mode option and provide a password for the system administrator (sa) account. Click Next to display the Start Copying Files dialog.
36
14. Click Next to display the Choose Licensing Mode dialog.
15. The type of RSBizWare Runtime Client License you purchased determines the licensing mode that you should select. If you purchased one or more Single-User Client Licenses, select the Per Seat licensing mode and set the number of devices equal to the number of RSBizWare Runtime Client Licenses you purchased. If you purchased an Unlimited-User Runtime Client License, you should select the Processor License and set the number of processors equal to the number of processors specified in the license you purchased. This number should equal the number of processors on the machine hosting SQL Server. 16. Click Continue. 17. Click Finish to complete the installation.
Installing Service Pack 4 for SQL Server 2000

You must obtain and install Service Pack 4 for SQL Server 2000 prior to installing or upgrading RSBizWare.
Creating a SQL Server 2000 database for use with RSBizWare

FactoryTalk Historian Classic, FactoryTalk Metrics, and FactoryTalk Scheduler require a single SQL Server database to operate. As these three applications share common tables in the database, they must be configured to run using the same SQL Server database.
37
1. To create a new database for use with the RSBizWare software, start the SQL Server Enterprise Manager by selecting Programs > Microsoft SQL Server > Enterprise Manager from the Windows Start menu. 2. In the SQL Server Enterprise Manager, expand the Microsoft SQL Servers item under the Console root tree. Expand the SQL Server Group tree item. 3. Expand the tree item for the computer where you installed SQL Server.
Note: If the server computer where you installed SQL Server does not appear in the list, right-click the SQL Server Group item and select New SQL Server Registration from the shortcut menu. Follow the steps of the Register SQL Server Wizard to register the server computer. Make sure you select the Windows Authentication connection mode.
4. Right-click the Databases folder and select New Database from the shortcut menu.
38
The Database Properties dialog will display.
5. Enter a database name in the Name field. For the examples in this document, we will use BizWare. 6. Click OK to save your new database.
39
Creating a database owner in SQL Server 2000

You now need to set up the database user that the RSBizWare servers will use to log on to the database. In SQL Server, the database user is called a login. The following steps can be used to create the login. For additional information on how to create the login, consult your SQL Server documentation. 1. In the SQL Server Enterprise Manager, expand the Security folder in the navigation tree. Right-click the Logins item and select New Login from the shortcut menu to display the SQL Server Login Properties dialog.
2. Enter a database user name in the Name field. For the examples in this document, we will use BizWareUser. 3. In the Authentication section, select the SQL Server authentication option. Enter a password for the database user in the Password field. 4. In the Defaults section, choose the name of the database that you just created.
40
5. Click the Database Access tab.
6. In the Permit column, check the box next to the name of the database that you just created to allow the user access to the database. 7. Database roles for this user will be listed in the bottom half of the window. Check the db_owner box.
Note: Do not assign Administrator server roles to this login.
8. Click OK to save your changes and close the dialog. You will be prompted to confirm the user password that you specified on the General tab. 9. Close the SQL Server Enterprise Manager utility.
41
Using SQL Server 2005

Follow the instructions in this section if you intend to use SQL Server 2005.
Creating a user account for SQL Server 2005

It is recommended that you create a Windows user on the computer on which you are installing SQL Server and assign that user to the standard Users group. You should then run the SQL Server components under the new users account. To create this user and assign it to a group, do the following: 1. Right click the My Computer icon on the desktop and select Manage from the shortcut menu to display the Computer Management dialog. 2. Expand the Local Users and Groups item in the tree. 3. Right click the Users folder and select New User from the shortcut menu to display the New User dialog. 4. Create the new user as shown in the following example (you do not need to name the user sqluser) and click Create.
42
5. Expand the Groups folder in the tree and ensure that the new user is a member of the standard Users group. (For security reasons, the fewer privileges that the SQL Server user has, the better.) 6. Close the Computer Management dialog.
Installing Internet Information Services (IIS)

You must install IIS before installing SQL Server 2005. For full information on installing IIS, consult your Microsoft documentation. You will need your Windows Server CD during this installation. 1. From the Windows Start menu select Settings > Control Panel > Add or Remove Programs. 2. Click the Add/Remove Windows Components button. 3. On a Windows 2003 Server computer, select the Application Server item from the Windows Component Wizard and click Details. On a Windows Server 2000 computer, select the Internet Information Services (IIS) item from the Windows Component Wizard and click Details. 4. On a Windows 2003 Server computer, select and ensure that the ASP.NET check box from the Application Server dialog and click OK. On a Windows Server 2000 computer, ensure that the SMTP Service and World Wide Web Server check boxes are selected from the Internet Information Services dialog and click OK. 5. Click OK again to return to the Windows Component Wizard. 6. Click Next and follow the remaining instructions in the wizard to complete the installation.
Installing other prerequisite software

To install SQL Server 2005 on Windows Server 2000, you must install the following if it is not already installed in the specified order: 1. Windows Installer 3.1 Redistributable 2. Microsoft Data Access Components (MDAC) 2.8 Service Pack 1 You can download this software from Microsofts Web site by navigating to www.microsoft.com/downloads and searching for the specified products (using the exact text in the preceding list).
43
Installing or Upgrading to SQL Server 2005

A licensed version of Microsoft SQL Server 2005 Standard Edition is packaged with the RSBizWare software. This version of SQL Server is provided for use with RSBizWare only and cannot be used for other external applications. 1. To install or upgrade SQL Server from the CD included with the software, insert the SQL Server CD into the CD-ROM drive. If the Windows autoplay feature has not been disabled, the SQL Server 2005 software autorun screen will display. If you disabled the autoplay feature on your computer, start the Windows Explorer, navigate to the CD drive that contains the SQL Server CD, and double-click the autorun.exe file. 2. On the Start screen, click the Server components, tools, Books Online, and samples item under the Install section. 3. On the End User License Agreement dialog, read the terms of the software license agreement and select the I accept ... check box if you want to continue the installation. Click Next to display the Installing Prerequisites dialog. 4. The Installing Prerequisites dialog will install prerequisite software required by SQL Server 2005 (such as the .NET Framework 2.0). Click Install to install the prerequisite software. When the installation completes, click Next to display the Welcome dialog. 5. Click Next to display the System Configuration Check dialog. 6. Ensure that all of the requirements are met successfully. (If any are not, you should cancel the installation/upgrade and perform any requirements.Then, resume the installation from the beginning.) Click Next to display the Microsoft Server Installation dialog and then the Registration Information dialog. 7. Enter your Registration information. Click Next to display the Components to Install dialog.
44
8. On the Components to Install dialog, select the following components at a minimum: SQL Server Database Services (for all RSBizWare installations) Reporting Services (if this database will contain Report Expert) Workstation components, Books Online and development tools (if you intend to manage the database directly on this computer; if you intend on managing the database from another computer, you will need to install this component on that computer)
Click Next to display the Instance Name dialog. 9. Select an appropriate instance type or accept the default value. Click Next to display the Service Account dialog (new installation) or the Existing components dialog (upgrade).
45
10. For upgrades only, select the SQL Server Database Services check box to upgrade the SQL Server 2000 database to SQL Server 2005. You will not see this panel during a new installation. (Note that the exact version number of the SQL Server Database Services can vary from the one shown below.) Click Next to display the Upgrade Logon Information dialog.
11. For upgrades only, select the appropriate authentication mode. You will not see this panel during a new installation. Click Next to display the Service Account dialog.
46
12. Select the account or accounts to use when running the various components of SQL Server. (It is strongly recommended that you select Use a domain user account and specify the user created in Creating a user account for SQL Server 2005 on page 42.) Click Next to display the Authentication Mode dialog (new installation) or the Report Server Installation Options dialog (upgrade).
13. For new installations only, on the Authentication Mode dialog, select Mixed Mode and create a password for the system administrator (sa) user account. You will not see this panel during an upgrade. Click Next to display the Collation Setting dialog. 14. For new installations only, select appropriate collation settings or accept the default values. You will not see this panel during an upgrade. Click Next to display either the Report Server Installation Options dialog. 15. Select appropriate report server installation options or accept the default values. Click Next to display the Error and Usage Report Settings dialog. 16. Select appropriate error and usage report settings or accept the default values. Click Next to display the Ready to Install dialog. 17. On the Ready to Install dialog, click Install. 18. On the Setup Progress dialog, click Next when the installation completes.
47
19. On the Completing Microsoft SQL Server 2005 Setup dialog, click Finish.
Installing Service Pack 1 for SQL Server 2005

You must obtain and install Service Pack 1 for SQL Server 2005 prior to installing or upgrading RSBizWare.
Creating a SQL Server 2005 database for use with RSBizWare

FactoryTalk Historian Classic, FactoryTalk Metrics, and FactoryTalk Scheduler require a single SQL Server database to operate. As these three applications share common tables in the database, they must be configured to run using the same SQL Server database. 1. To create a new database for use with the RSBizWare software, start the SQL Server Management Studio by selecting Programs > Microsoft SQL Server 2005 > SQL Server Management Studio from the Windows Start menu. 2. On the Connect to Server dialog, select the computer containing the SQL Server software and click Connect. 3. In the SQL Server Management Studio, right-click the Databases folder and select New Database from the shortcut menu.
48
The New Database dialog will display.
4. Enter a database name in the Database name field. For the examples in this document, we will use BizWare. 5. Click OK to save your new database.
49
Creating a database owner in SQL Server 2005

You now need to set up the database owner for the RSBizWare database. In SQL Server, a database user is called a login. The following steps can be used to create the login. For additional information on how to create the login, consult your SQL Server documentation. 1. In the SQL Server Management Studio, expand the Security folder in the Object Explorer tree. Right-click the Logins item and select New Login from the shortcut menu to display the Login - New dialog.
2. Enter a database user name in the Login name field. For the examples in this document, we will use BizWareUser. Select the SQL Server authentication option, create a password for the new login, and clear the Enforce password expiration option. Finally, select the database that you just created from the Default database list.
50
3. Select the User Mappings item from the Select a page list. In the grid at the top of the dialog, do the following: Select the checkbox for the RSBizWare database (for example, BizWare). Set the Default Schema to the same name as the User (for example, bizwareuser). In the checkbox list at the bottom of the dialog, select db_owner.
4. Click OK to save your changes and close the dialog. 5. Close the SQL Server Management Studio.
51
Creating an ODBC system DSN

RSBizWare servers access databases via ODBC. You will need to create named connections to the RSBizWare database and any other databases that you want the RSBizWare applications to use. This step must be done on the computers where your RSBizWare servers will be running. 1. On a Windows Server 2003 computer, select Administrative Tools > Data Sources (ODBC) from the Windows Start menu. On a Windows 2000 Server computer or a Windows Server 2003 in Classic mode, select Programs > Administrative Tools > Data Sources (ODBC) from the Windows Start menu. 2. The ODBC Data Source Administration dialog will display. Select the System DSN tab and click Add. 3. Select SQL Server (for SQL Server 2000) or SQL Native Client (for SQL Server 2005) from the list of drivers and click Finish to display the Create a New Data Source dialog.
4. Enter a data source name in the Name field. 5. Enter a description of the data source in the Description field. 6. Enter the name of the computer where the RSBizWare database was created. If the database was created on the local server, choose (local) from the Server list (or type (local) if it does not appear in the list).
52
7. Click Next to display the Microsoft SQL Server DSN Configuration dialog.
8. Use this dialog to specify how SQL Server should authenticate login IDs. Select the With SQL Server authentication... option. 9. In the Login ID and Password fields, enter the name and password of the owner of the database that you created in the previous sections. Click Next on this dialog and the following dialog. 10. Click Finish to display the ODBC Microsoft SQL Server Setup dialog. 11. Click the Test Data Source button. The test results box should contain the message Tests Completed Successfully! If the test does not complete successfully, it is very likely that the problem is with your setup of SQL Server. During the SQL Server install, the default authentication mode is Windows Authentication, but our setup requires Mixed Mode authentication (Windows Authentication and SQL Server Authentication). If you accepted the default Windows Authentication during installation, perform the following steps to change the authentication mode setting: Open the SQL Server Enterprise Manager and select your server from the SQL Server Group. Right-click the server and select Properties from the shortcut menu. On the Security tab, select the SQL Server and Windows Authentication option. Click OK to save your changes and close the dialog. 12. Click OK until you exit the ODBC Data Source Administrator program.
53
Upgrading your existing RSBizWare database

If you are upgrading from a previous version of FactoryTalk Historian Classic, FactoryTalk Metrics, or FactoryTalk Scheduler, you do not need to perform most of the instructions in this chapter. Instead, do one of the following: If you intend to use Report Expert, you can do either of the following: Install Report Expert on a different database computer from your current RSBizWare database. If you do this, you must install SQL Server 2005 on the new database computer. If you intend to do this, you must follow the instructions in Using SQL Server 2005 on page 42 on the computer that will contain Report Expert. You must also apply Service Pack 4 to the SQL Server 2000 database containing the RSBizWare Database as described in Installing Service Pack 4 for SQL Server 2000 on page 37 and then upgrade RSBizWare. Install Report Expert on the same database computer as your current RSBizWare database. If you do this, you must upgrade your database computer to SQL Server 2005 after upgrading RSBizWare and before installing Report Expert.
Important! To perform the database upgrade, you must ensure that you have a good
understanding of the nontrivial upgrade process. Before attempting this upgrade, it is strongly recommended that you read the upgrade documentation (SQL Server Setup Help) that comes with SQL Server 2005 and run the Upgrade Advisor tool.
If you do not intend to use Report Expert, you can apply Service Pack 4 to the SQL Server 2000 database as described in Installing Service Pack 4 for SQL Server 2000 on page 37 after upgrading RSBizWare. Because the RSBizWare software will automatically upgrade your existing RSBizWare database as part of the server configuration process, it is strongly recommended that you create a backup copy of your database before you continue with the configuration steps listed on the RSBizWare Installation Checklist.
54
Administering a Security Services Manager

The Security Services Manager is a Windows service that is integrated with the Windows security system. It is responsible for RSBizWare server startup and shutdown, and for security group, user, and license administration for all RSBizWare servers that are registered with the Security Services Manager. The Security Services Manager enables you to control the servers and security groups, users, and license activations from a single location.
Registering a Security Services Manager

1. To start the Service Console console application and register the Security Services Manager service, select Programs > Rockwell Software > RSBizWare > Service Console from the Windows Start menu. 2. When you start the Service Console for the first time, you will be prompted to register a Security Services Manager. Click Yes to register a Security Services Manager. 3. Enter the computer name or IP address of the machine on which the Security Services Manager was installed.
Registering the Security Services Manager with the Service Console simply tells the Service Console where it can find the Security Services Manager on the network. Press OK to register the server and close the dialog.
55
56
Administering RSBizWare Servers

The server administration functions of the Security Services Manager enables you to control Information Services Managers, Metrics Server Managers, and Scheduler Servers. Server administration functions include service configuration and service startup and shutdown.
Registering an RSBizWare server

Before the Security Services Manager can control an Information Services Manager or Scheduler Server, you must register the server with the Security Services Manager. Registering an RSBizWare server with the Security Services Manager simply tells the Security Services Manager where to locate the server on the network. 1. To register an RSBizWare server, expand the Security Services Manager tree, rightclick the Servers tree item, and select Register Server from the shortcut menu to display the Service Console Registration dialog.
Note: Before the Security Services Manager can control a Metrics Server Manager, you must associate the server with an existing Information Services Manager. To associate a Metrics Server Manager with an Information Services Manager, right-click an Information Services Manager tree item under the Security Services Manager and select Associate Metrics Server Manager from the shortcut menu.
57
2. The Server Type list contains the types of servers that you can register. Select the type of server that you want to register. If you are using FactoryTalk Metrics or FactoryTalk Historian Classic, select Information Services Manager from the list. 3. The Hostname or IP address field defaults to the name of the local machine. Enter the computer name or IP address of the machine on which the server software is installed. If you are registering a remote host, you can use the Browse button (...) to the right of the Hostname box to find the computer on the network. 4. The description will default to Server Type on Hostname where Server Type is the type of server that you selected and Hostname is the name of the computer that you entered. If desired, you may change the description of the server to something more meaningful to your organization. 5. Press OK to register the server. The server will now be displayed in the Security Services Manager tree.
Configuring Information Services Manager, Metrics Server Manager, or Scheduler Server settings
After you register an Information Services Manager or Scheduler Server or associate a Metrics Server Manager, the server will display in the tree and the Security Services Manager will attempt to start the server. If the server is not configured completely, it will start in configuration mode, indicated by a question mark icon to the left of the server name in the tree. Before you attempt to start your server for the first time, you will need to set various operational parameters of the server. 1. Click the server tree item in the Security Services Manager tree to display the server settings dialog.
58
6 ADMINISTERING RSBIZWARE SERVERS
Use the controls in the Database Connection Properties frame to establish a connection between the server and the database that you created when the software was installed. 2. Select the ODBC data source to which you want the server to connect. 3. Enter the user name and password that the server will need to connect to the ODBC data source. 4. Press the Test Connection button to confirm that the server can connect to the selected ODBC data source. 5. (Information Services Manager and Scheduler Server only.) Press the Advanced button. The advanced properties of the server are displayed at the bottom of the dialog.
The Advanced Server Settings for the Scheduler Server will only contain the Max Records, Connection Pool, and Listen on Port fields. 6. (Information Services Manager and Scheduler Server only.) In the Max Records to Return box, enter the maximum number of records that the server should return for any single non-time-series query against the database. This is a useful way to control queries that are returning a large amount of data.
59
7. (Information Services Manager and Scheduler Server only.) In the Connection Pool box, enter the number of database connections that the server should keep open. Each time a client makes a request for data from the database, the client is assigned a connection from this pool. 8. (Information Services Manager only.) When the registered name of the computer is different from the host name of the computer, enter the alias (registered name) that the Information Services Manager will use to refer to itself when connecting to the Security Services Manager and handling report requests across the Internet. 9. (Information Services Manager only.) Enter the amount of time that the server should maintain global credentials for users. After a users session connection expires, the user will be required to logon before viewing report objects that have been set to use the global credentials. 10. (Information Services Manager only.) Enter the name of the computer where the Report Schedule Manager is running. 11. (Information Services Manager only.) Enter the SMTP server name and originating e-mail address that will be used to distribute scheduled reports. 12. (Information Services Manager only.) Enter the user name and password that will be used to connect to the printer to print scheduled reports. 13. (Information Services Manager only.) Enter the report user name and password that will be used to connect to the Configuration Console to run the scheduled reports. If you are using scheduled reports, you must enter a user with sufficient privileges to run all of the scheduled reports. 14. (Information Services Manager only.) The Configuration Console uses HTTP in addition to raw TCP/IP to communicate to the Information Services Manager. Enter the port number on which the server will listen for requests from Configuration Consoles. The default HTTP port is 8080.
Note: Oracle 9.2.0.1.0 uses port 8080. If you are using this version of Oracle, you must set the HTTP port to something other than 8080.
15. (Information Services Manager only.) Enter the name of the folder in which the server will store RSBizWare reports that have been saved in the Configuration Console. You should only need to change the HTML Root directory setting if you installed the server to a non-default location. 16. Press Apply to make your changes permanent. When you are prompted to restart your server, click Yes. If you are restarting a brand new server, the server will take several minutes to load or initialize the database. Do not reboot your computer while the server is attempting to restart.
60
Installing RSBizWare sample data

RSBizWare sample data is available for demonstration or training purposes. To import the sample data into the RSBizWare database, run the RSBizWare DB Load Wizard from the Windows Start menu by selecting Programs > Rockwell Software > FactoryTalk Tools > Database Wizard.
Starting and stopping an RSBizWare server

The traffic light to the left of the Information Services Manager, Metrics Server Manager, or Scheduler Server name in the Security Services Manager tree indicates the server run mode.
A red traffic light indicates that the server is not running. Any attempts to change the server settings or connect a client to the server will be unsuccessful. A traffic light with a question mark indicates that the server is in configuration mode. The server is running, but you may change only server settings for the server. Any attempts to connect a client to the server will be unsuccessful. After you have configured the server settings, you can stop the server and restart it. A green traffic light indicates that the server is running. When a server is running, you can change server settings, connect clients to the server, and configure external data sources. To start a server that is not currently running, right-click the server in the Security Services Manager tree and select Start Server from the shortcut menu. To stop a server that is running, right-click the server in the Security Services Manager tree and select Stop Server from the shortcut menu. To stop and restart a running server with a single command, right-click the server in the Security Services Manager tree and select Restart Server from the shortcut menu.
Note: In order to start or stop a remote server successfully, your Windows user account must have permission to access the remote machine with specific permission to start and stop Windows service programs.
Managing Information Services Manager scheduled items

The Configuration Console supports the ability to schedule reports to be performed at some time in the future. To view a list of reports scheduled by the Configuration Consoles that are connected to a particular Information Services Manager, open the Information Services Manager tree item and click the Scheduled Items tree item. The Scheduled Items
61
list will display in the work area to the right. Use this list to view the reports and to delete scheduled reports that are no longer necessary. To delete a scheduled report, right-click the report in the grid and select Delete from the shortcut menu that will display.
Administering Information Services Manager external data sources

The reporting features of the Configuration Console can be applied to data that exists outside of the RSBizWare database. Before you can report on the data in an external database table or view, you will need to create an external data source. An external data source is a connection to any SQL Server or Oracle database that a server can communicate with using ODBC. After you have created the external data source, it will be available to users when they create new report data sources to access tables or views in the external database. 1. To create a new external data source, open the tree item for the Information Services Manager that you are maintaining and click the External Data Sources tree item. The External Data Source grid will display in the work area to the right. 2. Right-click a column sub-header in the grid and select New from the shortcut menu to display the Data Source Properties dialog.
3. Select the name of the ODBC Server DSN that the server should use to access the external database. The DSNs shown are those that exist on the computer where the Information Services Manager is running.
62
4. Enter a text description of the external data source. This is the name that will appear in the list of available data sources on the Report Data Source Wizard dialogs in the client. 5. Enter the user name and password that the server should use to connect to the data source. 6. Enter the number of connections that the server should maintain to this external data source in order to service requests from clients. Client requests can share a single connection, but more than one connection may help reduce delays for multiple client requests. 7. Press the Test Connection button to confirm that the server can connect to the database. If the connection attempt is successful, a Connection Successful message is displayed. 8. Click OK to save your changes and exit the dialog. Now the tables and views in your external data source will be available to users when they create new report data sources.
Configuring Information Services Manager default permissions

Information Services Manager security allows you to set the baseline permissions that will be given to a certain group or user for every instance of an object type that is created in the Configuration Console. For example, if you want the user JLSmith to have permission to edit every report object that is ever created in the client application, you need to set the Edit Report Object default security for JLSmith for the Report Object object. After you have assigned default permissions for a type of object, the creator of a new object of that type may choose to revoke a user's permissions for his new object or may choose to grant permissions for his new object to a user who does not have the default permission. This is referred to as a custom permission. For example, if JLSmith was given the default Edit Report Object permission, we can create a new report object and revoke JLSmiths custom Edit Report Object permission for this report object so Smith cannot edit our new report object. Or we can grant the custom Edit Report Object permission to LMJones, allowing Jones to edit our report object regardless of whether he has the default Edit Report Object permission. Custom permissions are assigned in the Configuration Console.
Note: Before you can assign default permissions to a type of object that is used in the Configuration Console, you must create security groups and users. See Creating user group accounts and user accounts on page 86 for information about the creation of security groups and users.
63
1. To view a list of objects for which you can specify default security, open the Information Services Manager tree item and click the Default Permission Settings tree item. The Default Permission Settings list will display in the work area to the right.
2. To set the default permissions for an object type, select the object type from the list and press the Permissions button. The Default Object Security dialog that is displayed allows you to specify the permissions that will be granted to users or groups for all objects of the selected type.
3. To assign default permissions to a user, click the Users tab. Select the user from the list and expand the user folder.
64
4. Click the check boxes to the left of the default permissions that you want to grant to the user. You can grant permissions to everyone or to selected Security Groups in the same manner. 5. Press Save to save your changes and close the dialog.
Configuration Console object permissions

An object-level permission is a privilege that is granted to security groups or individual users that allows access to a specific object within the client application. An example of an object-level permission for which users and groups can be given privileges is the ability to edit a particular report object. For example, if JLSmith is granted edit permissions for the report object called Test Report Object, then JLSmith will be able to make and save changes to that report object. Individual users can have object permissions granted to them and they can inherit object permissions from the security groups to which they belong. If a group has been granted permissions for the Edit Report Object feature for a particular report object, users assigned to that group are able to edit the report object also. Object permissions are granted through the Service Console by doing the following: 1. Selecting the Default Permission Settings item under the Information Services Manager item in the Service Console tree. 2. Selecting the appropriate permission type and clicking Permissions. 3. Setting the appropriate permissions in the Default Object Security dialog (described in the sections that follow).
Report permissions
View Report: Allows the selected users or groups to view the report. For the user or group to be able to view the report, you must make sure that the permissions for the report data sources, report objects, and filters (optional) used on this report are also set for the selected user or group. Edit Report: (Author licenses only) Allows the selected users or groups to make changes to the report. Delete Report: (Author licenses only) Allows the selected users or groups to delete the report. Edit (Report) Security: (Author licenses only) Allows the selected users or groups to grant security permissions for the report to other users or groups.
65
Report object permissions

View Report Object: Allows the selected users or groups to view the report object. The report object will be available for use by the selected users or groups. Edit Report Object: (Author licenses only) Allows the selected users or groups to make changes to the report object. Delete Report Object: (Author licenses only) Allows the selected users or groups to delete the report object. Edit (Report Object) Security: (Author licenses only) Allows the selected users or groups to grant security permissions for the report object to other users or groups.
Filter permissions
View Filter: Allows the selected users or groups to view the filter. The filter will be available for use by the selected users or groups. Edit Filter: (Author licenses only) Allows the selected users or groups to make changes to the filter. Delete Filter: (Author licenses only) Allows the selected users or groups to delete the filter. Edit (Filter) Security: (Author licenses only) Allows the selected users or groups to grant security permissions for the filter to other users or groups.
Report data source permissions

Allow <All> Filter Selection: Allows the selected users or groups to select the (all) filter from any column filter list associated with a report data source. If this check box is cleared, the selected users and groups will not be allowed to select the (all) filter from any column filter list associated with a report data source. View Report Data Source: Allows the selected users or groups to view the report data source. Edit Report Data Source: (Author licenses only) Allows the selected users or groups to make changes to the report data source. Delete Report Data Source: (Author licenses only) Allows the selected users or groups to delete the report data source. Edit (Report Data Source) Security: (Author licenses only) Allows the selected users or groups to grant security permissions for the report data source to other users or groups.
66
Administering FactoryTalk Metrics user-defined summarization criteria

A summarization criterion is a FactoryTalk Metrics Performance Parameter field for which activity area data can be collected. When the value of the field changes, it triggers the summarization of historical performance data for the activity area in the PlantMetrics Workcell History report data source. The collected values can then be used to filter OEE performance data for the activity area. For example, if your system is configured to collect Part ID (a default summarization criterion) for an activity area, you will be able to calculate the OEE performance for the activity area when it is producing a particular kind of part. In addition to the default summarization criteriaShift, Part ID, and Ideal Cycle Time for which FactoryTalk Metrics can collect data values, you can configure up to five userdefined summarization criteria, or flex fields, to represent the fields that are most important to your organization. User-defined summarization criteria function just as the default summarization criteria do, but because they are user-defined they allow you to tailor FactoryTalk Metrics to meet your organizations data collection and summarization needs. Sample uses of user-defined summarization criteria include: An Operator ID user-defined summarization criterion that will allow you to collect operator IDs and to report on the OEE value for a specific operator. A Lot Number user-defined summarization criterion that will allow you to collect lot numbers and report on the OEE value for a specific lot of products. A Test Run State user-defined summarization criterion that will allow you to report on the OEE value for parts that were produced when the activity area was in a production state only. 1. To configure a user-defined summarization field, open the tree item for the Metrics Server Manager that you are maintaining and click the FactoryTalk Metrics FlexFields tree item. The User-defined Summarization Fields grid will display in the work area to the right.
67
2. There are five user-defined summarization fields that you can enable or disable as desired. Right-click the user-defined summarization field that you want to modify and select Properties from the shortcut menu to display the Configure Summarization Criteria dialog.
3. Select the Enable This Summarization Criteria check box. This will make the summarization criterion available for Performance Parameters configuration. 4. Edit the text in the Name field to provide a name that is meaningful to your organization. 5. Select the Required check box if you want to require the user to collect data for this field. 6. Select a data type from the options available in the Summarization Criteria Data Types box. This specifies the type of data that will be collected for this field. If you select Boolean, you will need to enter True and False display values. 7. Press OK to save your changes and close the dialog. You do not need to restart the server for the summarization criteria changes to take effect. The next time a user attempts to configure performance parameters for an activity area, this field will be available for use.
Handling temporary database connection loss in the Information Services Manager

If the connection between the Information Services Manager and the database (Oracle or SQL Server) is broken, and the error message that the server receives from the database is
68
one of the errors known by the server to cause temporary database connection loss, the server will attempt to reconnect to the database without user intervention.
Table 6-1. Errors known by the Information Services Manager to cause temporary database connection loss. General ODBC Errors: 08003 08004 08S01 24000 34000 S1000 S1001 S1008 S1009 S1010 S1109 01000 37000 Oracle-Only Errors: 1033 1089 3111 3112 3113 3114
If the server does not recognize the error message, the server will look for a text file called dberrors.txt that may contain additional error numbers. If the server finds the text file and the database error matches any of the entries in the text file, the server will attempt to reconnect to the database. However, if the server does not recognize the error message and is unable to find the text file or the text file does not contain the error message, the server will be disabled and will need to be restarted manually.
Note: If the Metrics Server Manager encounters one of the general errors, it will attempt to reconnect to the database; however, the Metrics Server Manager will not attempt to look for errors in the dberrors.txt file.
The dberrors.txt file is a text file that you can create and maintain to tell the Information Services Manager about any additional database error messages that your organization would like to consider as typically signaling temporary database connection loss. 1. To create the dberrors.txt file, select Programs > Accessories > Notepad from the Windows Start menu. A blank text file is created.
69
2. Enter the numbers of the database error messages that you expect to cause temporary database connection loss on your system. The file should contain a single database error number per line for every additional database error.
Note: While some of the general ODBC errors contain characters, only numeric values may be entered in the dberrors.txt file.
For example, if you expect the Oracle ORA-08114 and ORA-10015 errors to cause temporary database connection loss on your system, enter 8114 and 10015 on separate lines in the text file, as shown below.
3. Save the text file as dberrors.txt in the directory where the RSBizWare software was installed. If you accepted the default installation, the software was installed in the C:\Program Files\Rockwell Software\RSBizWare directory.
The Metrics Server Manager Settings file

To allow the Metrics Server Manager to make more efficient use of memory, better manage the processing of RSL files, and release all unused memory back to the operating system, a Metrics Server Manager Settings file is available. The PlantMetricsServerSettings.xml file will be created in the directory from which the Metrics Server Manager runs (C:\Program Files\Rockwell Software\RSBizWare, if you accepted the default installation.) the first time the Metrics Server Manager is started. All relevant Metrics Server Manager-specific settings used in previous releases will be extracted from the registry and - along with additional values that were formerly hard coded - will be stored in the newly created file.
70
Note: All registry values specified are in the HKEY_LOCAL_MACHINE\Software\Rockwell Software\PlantMetrics\Current Configuration\OnyxServer registry key.
Table 6-2. Metrics Server Manager Settings Default Value On Location in preRSBizWare 9.0 Software
Value Name (Units) LogLocation ServerCalls (On or Off)
Description
Turns the application-specific In the LogLocation informational and debug-level registry value, with bit 1 logging on or off for function set in the hexadecimal calls at the global server level. bitmask. Turns the application-specific In the LogLocation informational and debug-level registry value, with bit 2 logging on or off for general set in the hexadecimal processing messages from the bitmask. FactoryTalk Transaction Manager process thread. Turns the application-specific In the LogLocation informational and debug-level registry value, with bit 4 logging on or off for RSL file set in the hexadecimal bitmask. content messages from the FactoryTalk Transaction Manager process thread. Turns the application-specific In the LogLocation informational and debug-level registry value, with bit 8 logging on or off for Schedule set in the hexadecimal bitmask. thread messages. Turns the application-specific In the LogLocation informational and debug-level registry value, with bit logging on or off for general 10 set in the hexadecimal bitmask. processing message in the Calculator thread. Turns the application-specific In the LogLocation informational and debug-level registry value, with bit 20 set in the hexadecimal logging on or off for time pattern schedule processing bitmask. messages in the Calculator thread.
LogLocation RSSqlThreadGeneral (On or Off)
Off
LogLocation RSSqlRSLFileDetail (On or Off)
On
LogLocation ScheduleThread (On or Off)
Off
LogLocation CalcThreadGeneral (On or Off)
On
LogLocation CalcThreadSchedule (On or Off)
Off
71
Table 6-2. Metrics Server Manager Settings Default Value On Location in preRSBizWare 9.0 Software
Value Name (Units) LogLocation CalcThreadDataDetails (On or Off)
Description
Turns the application-specific LogLocation registry informational and debug-level value, with bit 40 set in the hexadecimal bitmask. logging on or off for data processing messages from the Calculator thread. Turns the application-specific LogLocation registry informational and debug-level value, with bit 80 set in the hexadecimal bitmask. logging on or off for OEE calculation messages in the Calculator thread. Turns the application-specific LogLocation registry informational and debug-level value, with bit 100 set in the hexadecimal bitmask. logging on or off for event processing messages in the Calculator thread. Turns the application-specific LogLocation registry informational and debug-level value, with bit 200 set in the hexadecimal bitmask. logging on or off for fault metric calculation messages in the Calculator thread. Turns the application-specific LogLocation registry informational and debug-level value, with bit 400 set in logging on or off for machine the hexadecimal bitmask. state calculation messages in the Calculator thread. Turns the application-specific LogLocation registry informational and debug-level value, with bit 1000 set logging on or off for server in the hexadecimal bitmask. request handling. Turns the application-specific LogLocation registry informational and debug-level value, with bit 4000 set in the hexadecimal logging on or off for data processing queue handling. bitmask.
LogLocation CalcThreadCalculation (On or Off)
On
LogLocation CalcThreadEventDetail (On or Off)
On
LogLocation CalcThreadFaultMetrics (On or Off)
Off
LogLocation CalcThreadMachineState (On or Off)
Off
LogLocation ServerRequests (On or Off)
Off
LogLocation DataProcessingQueue (On or Off)
Off
72
Table 6-2. Metrics Server Manager Settings Default Value Off Location in preRSBizWare 9.0 Software
Value Name (Units) LogLocation MemoryManagement (On or Off)
Description
Turns the application-specific This value did not exist informational and debug-level in versions of the logging on or off for message software prior to in the memory management RSBizWare 9.0. thread. RSL Check Time Discard the first RSL file Duration registry value. processed if it is this many minutes older than the current time. 1 - Initialize data collection Init Values Type registry value. from a single timestamp provided by the heart beat transactions and discard data that is older than the initializing time. 0 - Use all data no matter what the timestamp.
StartupRSLAgeLimit (Minutes)
10
InitializeFromSingleTimestamp (1 or 0)
ShiftRecursionDuration (Minutes) SummarizationOverlap (Seconds)
60
The amount of time used to Shift Recurse Gap recursively search for the start registry value. of the current shift. Summarization Gap Summarization criteria changes that occur within this registry value. amount of time will be considered a single change and will not generate multiple summarizations. The count of items waiting to Sleep Threshold registry be processed above which the value. Calculator thread will no longer sleep for a small amount of time to keep from consuming all the CPU time. This is the number of items that indicate the server is busy enough it does not need to sleep.
DataQueueSleepThreshold (# of Data Queue Items)
100
73
Table 6-2. Metrics Server Manager Settings Default Value Location in preRSBizWare 9.0 Software
Value Name (Units) DataQueueWarningThreshold (# of Data Queue Items)
Description
500 or 5 * The count of items waiting to This value was hardcoded in previous Sleep be processed at which a warning log message will be versions of the software. generated and the database update rate will be changed to use the configured warning state update rate. 1000 or The count of items waiting to This value was hard10 * Sleepbe processed at which an error coded in previous log message will be generated versions of the software. and the database will only update when summarizations occur. 30 How often the Calculator thread will update the database with calculated values during normal processing. How often the Calculator thread will update the database with calculated values while the server is in a warning state. This value was hardcoded in previous versions of the software.
DataQueueErrorThreshold (# of Data Queue Items)
DatabaseUpdateInterval (Seconds)
WarningDatabaseUpdateInterval (Seconds)
300
This value did not exist in versions of the software prior to RSBizWare 9.0.
EnabledWorkcellPollingRate (Minutes)
10
How often the Metrics Server This value was hardManager checks the database coded in previous for newly enabled or disabled versions of the software. work cells. This value was hardNumber of seconds the Calculator thread will buffer coded in previous part counts before performing versions of the software. an OEE calculation operation.
PartCountBufferingDuration (Seconds)
10
74
Table 6-2. Metrics Server Manager Settings Default Value Location in preRSBizWare 9.0 Software This value did not exist in versions of the software prior to RSBizWare 9.0. This variable was created to resolve a problem with the server crashing when handling large numbers of RSL files.
Value Name (Units) MaxMemoryUsage (KB)
Description
0 No limitThe Metrics Server Manager monitors the process memory size; if the server exceeds the limit set in this value, the server halts the processing of RSL files until enough items have been released to handle the number of records in the current RSL file. Setting to zero means no limit. Any value below 50,000 will be ignored. 5
MinMemoryProcessDuration (Minutes)
The Metrics Server Manager This value did not exist tracks the number of records in versions of the in each RSL file and the time software prior to the RSL file was processed to RSBizWare 9.0. This variable was created to determine the amount of allow the server to memory needed for the amount of time specified. The release unused memory back to the operating server will keep enough memory to process this many system. minutes of data and may release memory back to the system when more has been allocated to process a large influx of RSL files.
75
76
Controlling Access to Your RSBizWare System

This chapter defines the types of activations and privileges available for the RSBizWare suite of products and describes the procedures for assigning activations to servers and assigning activations and privileges to user groups and users. While these topics relate to the overall security of your system, these steps are performed within different areas on your desktop. To help orient you to the structure for these activities, we offer the following overview. We'll begin by defining the various types of software licensing options. The software you purchase determines the license options that may be activated. Next we will discuss the steps for assigning server activations to an RSBizWare server. This activity is performed in the Service Console. It is important to note that the server must first be registered with the Security Services Manager. See Registering an RSBizWare server on page 57 for information on registering RSBizWare servers. This is followed by a presentation of the procedures you will perform in the FactoryTalk Administration Console to create user groups and users. And finally, we will discuss the Configuration Console application privileges that are available and we will focus on the assignment of application privileges to users and groups in the Service Console.
Note: To further define security within your RSBizWare system, you may assign default and custom object permissions to user groups and users. These activities are discussed elsewhere, but are listed here to provide a comprehensive view of how to control access to your RSBizWare system.
Table 7-1. Application areas where activation and security activities are performed. Activity: Assigning server activations Creating user groups and users Assigning client activations to users Assigning application privileges to users and groups Assigning default object permissions to users and groups Assigning custom object permissions to users and groups Performed In: Service Console FactoryTalk Administration Console Service Console Service Console Service Console. See Configuring Information Services Manager default permissions on page 63. Configuration Console. See the Set Permissions topic in the Configuration Console online help.
77
Software activation options

RSBizWare security is managed by a Windows service called the Security Services Manager. The Security Services Manager makes use of the Windows security system and is responsible for management of the activations and user accounts for RSBizWare products across the enterprise. See Installing RSBizWare FactoryTalk Activations on page 23 for information about installing RSBizWare activations onto the machine where the Security Services Manager is
running.
FactoryTalk Scheduler activation options

FactoryTalk Scheduler activation is client-based and controls the users ability to edit and configure a schedule within the Scheduler Client. Each FactoryTalk Scheduler user is required to have either a Full Client License or View-Only Client License assigned to him in order to use the software. SCHEDULER FULL CLIENT LICENSE A Scheduler Full Client License allows the user to create, edit, and configure schedules. Currently, the Scheduler Client activation only allows one Scheduler Full Client License user and any number of Scheduler View-Only Client License users to access the same schedule at one time. If a second Scheduler Full Client License user attempts to access a schedule that has already been opened by another Scheduler Full Client License user, the second Scheduler Full Client License user will default to a Scheduler View-Only Client License user status. SCHEDULER VIEW-ONLY CLIENT LICENSE A Scheduler View-Only Client License is only able to view a previously created schedule.
FactoryTalk Historian Classic activation options

Three general types of FactoryTalk Historian Classic activations are available: Server activations, Runtime Client activations, and Author Client activations. SERVER
ACTIVATION
FactoryTalk Historian Classic Server activation is based on the total number of reporting tags that can be configured. These reporting tags can reference data points from your control system collected natively with FactoryTalk Historian Classic, as well as those referenced in other report data sources such as custom database tables. After your server reaches its reporting tag limit, you will not be able to configure additional reporting tags. To view a complete list of configured reporting tags, use the Time-Series Reporting Tags dialog available from the Configure > Time-Series Reporting Tags menu in the Configuration Console.
78
7 CONTROLLING ACCESS TO YOUR RSBIZWARE SYSTEM
Server activations are cumulative up to the 70,000 reporting tag limit. For example, you can install a 1500 reporting tag activation as well as a 150 reporting tag activation and assign both activations to the same Information Services Manager for a total of 1650 reporting tags. However, you cannot install a 70,000 reporting tag activation and a 5000 reporting tag activation and assign both activations to the same Information Services Manager for a total of 75,000 reporting tags.
Note: Any FactoryTalk Historian Classic server activation will also activate a single FactoryTalk Metrics workcell.
CLIENT
ACTIVATION
Client activations are available to allow users to simply view previously created FactoryTalk Historian Classic and FactoryTalk Metrics reports (Runtime activations), or to view previously created FactoryTalk Historian Classic and FactoryTalk Metrics reports and to author new FactoryTalk Historian Classic reports (Author activations). Within a particular client activation, access is restricted by the privileges and permissions that have been granted to security groups and individual users.
RSBizWare Single-User and Unlimited User Runtime activations. The
RSBizWare Runtime client activations allow users to view FactoryTalk Historian Classic and FactoryTalk Metrics reports interactively using Microsoft Internet Explorer, the Configuration Console, or RSBizWare ActiveX controls embedded in other applications like RSView32. These activations are assigned to an Information Services Manager (not to individual users), and determine the total number of concurrent runtime users who are permitted to login and view reports at the same time. This allows the System Administrator greater flexibility managing user activations. Two types of RSBizWare Runtime Client activations are available. Single-User Runtime Client activations need to be assigned to the Information Services Manager in sufficient quantity to accommodate the total number of concurrently connected Runtime users. If a large number of concurrent users is expected, an Unlimited-User Runtime Client activation should be assigned to the Information Services Manager. This will allow any number of users (limited by hardware availability and network performance) to connect concurrently.
FactoryTalk Historian Author activation. The FactoryTalk Historian Author
activation is a single-user activation that adds the ability to configure FactoryTalk Historian Classic data collection, develop custom reports, and publish them for use by runtime users. One FactoryTalk Historian Author activation is included with each FactoryTalk Historian Server activation. FactoryTalk Historian Author activations are assigned to individual user accounts; however, these activations determine the total number of concurrent users who are
79
permitted to login and perform authoring functions at the same time. This allows the System Administrator to assign all potential authoring users a FactoryTalk Historian Author activation provided the concurrent number of logged-in authors does not exceed the total number of FactoryTalk Historian Author activations installed. Additional authoring privileges (such as Manage Reporting Tags, Add Time-Series Comment, and many others) are individually assigned to users at the system administrators discretion. AN
EXAMPLE OF
FACTORYTALK HISTORIAN CLASSIC
ACTIVATION
Lets say our BizBikes factory has 100 employees running three shifts per day. Each shift has 10 individuals who need to view RSBizWare reports, and 2 individuals who configure FactoryTalk Historian Classic data collection and/or author reports. FactoryTalk Historian Classic collects, logs, and reports on 1625 tags. So, we have: 30 runtime users across all shifts, 10 of which could be concurrently logged in (based on shift) 6 authoring users across all shifts, 2 of which could be concurrently logged in (based on shift) In this scenario, a total of 36 user accounts would be configured or imported from the Windows domain, and 6 of those users would be given authoring privileges. Our factory would need to purchase the following activations: (1) 9358-HSTS2300 FactoryTalk Historian Server with 1,500 Reporting Tag Limit (1) 9358-HSTS2100 FactoryTalk Historian Server with 150 Reporting Tag Limit (10) 9358-BIZ1C0PENE RSBizWare Single-User Runtime Client activations Our factory is activated for a total of 12 concurrent users10 of which are runtime-only users, and an additional 2 users are authoring/configuring. (Remember, each FactoryTalk Historian Server activation includes an Author activation so this would give us a total of 2 Single-User Author Client activations) After the activations are loaded onto the computer that is running the Security Services Manager, the activations are assigned as follows: The FactoryTalk Historian Server activations and the 10 RSBizWare Runtime Client activations are assigned to the appropriate Information Services Manager. A FactoryTalk Historian Author activation is assigned to each of the 6 authoring users (2 per shift).
80
FactoryTalk Historian Classic for Batch activation options

FactoryTalk Historian Classic for Batch activation is based on the total number of Batch Units or Batch Servers in your system and the activations are cumulative. For example, you can install two 3-unit activations for a total of 6 units.
Note: It is not necessary to assign FactoryTalk Historian Classic for Batch activations to specific servers; however, you will need to assign your FactoryTalk Historian server activation to a server and your RSBizWare client activation to users.
FACTORYTALK HISTORIAN CLASSIC
FOR
BATCH MODULE
FOR
3 UNITS
The FactoryTalk Historian Classic for Batch Module for 3 Units activation is suitable for systems with up to three S88 defined units. This activation includes a FactoryTalk Historian Server with 150 Reporting Tag Limit activation and an RSBizWare Single-User Author Client activation. FACTORYTALK HISTORIAN CLASSIC FOR BATCH MODULE CONNECTION TO 1 BATCH SERVER The FactoryTalk Historian Classic for Batch Module Connection to 1 Batch Server activation is suitable for systems with a single Batch Server. This activation includes a FactoryTalk Historian Server with 300 Reporting Tag Limit activation and an RSBizWare Single-User Author Client activation. FACTORYTALK HISTORIAN CLASSIC FOR BATCH MODULE CONNECTION 1 3 BATCH SERVERS The FactoryTalk Historian Classic for Batch Module Connection 1 - 3 Batch Servers activation is suitable for systems with up to three Batch Servers. This activation includes a FactoryTalk Historian Server with 1500 Reporting Tag Limit activation and an RSBizWare Single-User Author Client activation.
FactoryTalk Metrics activation options

Three general types of FactoryTalk Metrics activations are available: Server activations, Runtime Client activations, and Author Client activations. SERVER
ACTIVATION
FactoryTalk Metrics Server activation is based on the total number of workcells (really the total number of activity areas, which can be workcells, lines, areas, sites, and/or enterprises) that are monitored by FactoryTalk Metrics. A workcell is counted against the license when it is enabled in the Configuration Console. After your server reaches its workcell limit, you will not be able to enable any more workcells. The total number of enabled workcells is listed on the FactoryTalk Metrics Configuration Checklist dialog
81
available from the Configure > FactoryTalk Metrics > Configuration Checklist menu in the Configuration Console. Server activations are cumulative. For example, you can install a 100 workcell activation as well as a 10 workcell activation and assign both activations to the same Information Services Manager for a total of 110 workcells.
Note: Any FactoryTalk Metrics server activation will also activate 25 FactoryTalk Historian Classic time-series reporting tags.
CLIENT
ACTIVATION
Client activations are available to allow users to simply view previously created FactoryTalk Historian Classic and FactoryTalk Metrics reports (Runtime activations), or to view previously created FactoryTalk Historian Classic and FactoryTalk Metrics reports and to author new FactoryTalk Metrics reports (Author activations). Within a particular client activation, access is restricted by the privileges and permissions that have been granted to security groups and individual users.
RSBizWare Single User and Unlimited User Runtime activations. The RSBizWare Runtime client activations allow users to view FactoryTalk Historian Classic and FactoryTalk Metrics reports interactively using Microsoft Internet Explorer, the Configuration Console, or RSBizWare ActiveX controls embedded in other applications like RSView32.
These activations are assigned to an Information Services Manager (not to individual users), and determine the total number of concurrent runtime users who are permitted to login and view reports at the same time. This allows the System Administrator greater flexibility managing user activations. Two types of RSBizWare Runtime Client activations are available. Single-User Runtime Client activations need to be assigned to the Information Services Manager in sufficient quantity to accommodate the total number of concurrently connected Runtime users. If a large number of concurrent users is expected, an Unlimited-User Runtime Client activation should be assigned to the Information Services Manager. This will allow any number of users (limited by hardware availability and network performance) to connect concurrently.
FactoryTalk Metrics Author activation. The FactoryTalk Metrics Author activation
is a single-user activation that adds the ability to configure the FactoryTalk Metrics application, configure data collection, develop custom reports, and publish them for use by runtime users. One FactoryTalk Metrics Author activation is included with each FactoryTalk Metrics Server Manager activation. FactoryTalk Metrics Author activations are assigned to individual user accounts; however, these activations determine the total number of concurrent users who are permitted to
82
login and perform authoring functions at the same time. This allows the System Administrator to assign all potential authoring users a FactoryTalk Metrics Author activation provided the concurrent number of logged-in authors does not exceed the total number of FactoryTalk Metrics Author activations installed. Additional authoring privileges (such as Manage Performance Parameters, Manage Time Pattern, and many others) are individually assigned to users at the system administrators discretion. AN
EXAMPLE OF
FACTORYTALK METRICS
ACTIVATION
Lets say our BizBikes factory has 100 employees running three shifts per day. Each shift has 10 individuals who need to view RSBizWare reports, and 2 individuals who configure FactoryTalk Metrics data collection and/or author reports. FactoryTalk Metrics collects, logs, and reports on 35 workcells. So, we have: 30 runtime users across all shifts, 10 of which could be concurrently logged in (based on shift) 6 authoring users across all shifts, 2 of which could be concurrently logged in (based on shift) In this scenario, a total of 36 user accounts would be configured or imported from the Windows domain, and 6 of those users would be given authoring privileges. Our factory would need to purchase the following activations: (1) 9358-PLTM2300ENE FactoryTalk Metrics Server Manager with 25 Workcell Limit (1) 9358-PLTM2200ENE FactoryTalk Metrics Server Manager with 10 Workcell Limit (10) 9358-BIZ1C0PENE RSBizWare Single-User Runtime Client Our factory is activated for a total of 12 concurrent users10 of which are runtime-only users, and an additional 2 users are authoring/configuring. (Remember, each FactoryTalk Metrics Server Manager activation includes an Author activation so this would give us a total of 2 Single-User Author Client activations.) After the activations are loaded onto the computer that is running the Security Services Manager, the activations are assigned as follows: The FactoryTalk Metrics Server Manager activations and the 10 RSBizWare Runtime Client activations are assigned to the appropriate Information Services Manager. A FactoryTalk Metrics Author activation is assigned to each of the 6 authoring users (2 per shift).
83
Assigning activations to RSBizWare Servers

Before you can assign server activations to an RSBizWare server, the server must be registered with the Security Services Manager. See Registering an RSBizWare server on page 57 for information on registering RSBizWare servers. 1. To assign activations to servers, click the Activations tree item under the Administration tree item on the Security Services Manager tree. The Activations dialog will display in the work area.
2. The drop-down list at the top of the Activations dialog contains all RSBizWare servers that are registered with this Security Services Manager. Select the server to which you want to assign activations. 3. The Activations list in the middle of the dialog lists the activations that can be assigned to the selected server. Each row has several fields that help you manage the use of RSBizWare software activations: Total: The total number of activations installed (via the FactoryTalk Activation tool or the Move Activation utility) on the computer where the selected Security Services Manager is running. Available: The number of unassigned activations on the computer where the selected Security Services Manager is running. Assigned: The number of activations that have been assigned to the RSBizWare server selected from the list at the top of the dialog.
84
4. Select an activation from the Activations list and press Assign a license to associate the activation with the selected server. When you assign an activation to a server, you should see the Available count for that activation decrement and the Assigned count for that activation increment. Press Unassign a license to remove the activation from the selected server.
Managing FactoryTalk user groups and users

User accounts are used to authenticate, and authorize or deny access, to individual users in your FactoryTalk automation system. User accounts are also used to audit user activity. A user group account is a collection of user accounts that you can use to simplify the administration of security permissions. Users belonging to a particular group receive all of the permissions and rights that you assign to the group. By changing a user's group memberships, you can quickly change the resources to which the user has access.
Note: You should be aware of the of the following anomalous behavior of the specified user/group permissions:
All FactoryTalk Security user accounts that belong to the Administrators group will have full permissions on all RSBizWare objects (reports, report data sources, report objects, and filters) even though those permissions do not appear to be set in the various object permission browsers. Group level permissions do not take effect on individual users that are added to or removed from the group until the Users and Groups dialog is refreshed in the RSBizWare Enterprise Manager.
Importing RSBizWare groups and users into FactoryTalk

If you are upgrading from an earlier version of the RSBizWare software (prior to CPR7), security groups and users created in earlier versions can be imported into FactoryTalk using the RSBizWare FactoryTalk Security Import tool.
85
To run the RSBizWare FactoryTalk Security Import tool from the Windows Start menu select Programs > Rockwell Software > RSBizWare > Migrate RSBizWare Security to FactoryTalk Security.
1. To begin the import, click Import. 2. You will be prompted to log on to FactoryTalk. Enter the Administrator username and password that was created when you set up the Network directory and click OK to start the import process. 3. The Finished dialog is displayed when the import process is complete. Click Close to exit the import tool.
Note: Your existing RSBizWare System Administrator (admin) account will automatically be added to the Administrators user group during the import.
Creating user group accounts and user accounts

To create user group accounts and user accounts in the FactoryTalk Administration Console, select Programs > Rockwell Software > FactoryTalk Administration Console from the Windows Start menu.
86
When prompted to select the FactoryTalk directory you want to use, select Network and press OK to continue. If you have not already logged on to FactoryTalk, you will be prompted to do so. Enter the administrator user name and password that was created when the FactoryTalk Services Platform was installed and press OK. The FactoryTalk Administration Console is displayed. In the Explorer pane, expand the Network FactoryTalk Directory tree, and then expand the System folder until the Users and Groups folder is visible. Expand the Users and Groups folder to display the User Groups folder and the Users folder.
87
Creating a FactoryTalk user group

1. Right-click the User Groups folder and select New > User Group from the shortcut menu to display the New User Group dialog.
2. Enter a name for the group in the Name box. 3. In the Description box, enter a description of the group. 4. Add or remove user accounts: To add a member to the group, click the Add button. In the Select User dialog box, select the user accounts you want to be members of the group and then click OK to save your changes and close the dialog. To remove a member from the group, select the user accounts you want to remove and then click Remove. 5. Click Create to save your changes and close the dialog.
88
Adding a Windows-linked user group

Note: To access QuickWeb as a Windows-linked user, a user must have Windows login access rights to the computer running the Information Services Manager.
1. Right-click the User Groups folder and select New > Windows-linked User Group from the shortcut menu to display the New Windows-Linked User Group dialog.
2. Click Add to display the Select Groups dialog.
3. In the Select Groups dialog box, type in one or more groups names (separated by semicolons) and click Check Names to validate them or click the Advanced button to
89
browse for groups in the specified location (computer). Click OK to add the selected groups and close the dialog. 4. In the New Windows-Linked User Group dialog box, review the list of groups you added. To remove any groups you might have added unintentionally, select the groups, and then click Remove. To add more groups, repeat Steps 2 and 3. 5. Click Create to save your changes and close the dialog.
Creating a FactoryTalk user

1. Right-click the Users folder and select New > User from the shortcut menu to display the Add New User dialog.
2. On the General tab of the Add New User dialog box, enter a short name for the user (for example, jjenkins) in the User name box. 3. In the Full name box, type the full name of the user (for example, Jane Jenkins).
90
4. In the Description box, type a description of the user (for example, Shift Supervisor). You can also use this box to record contact information for the user, such as a telephone number or e-mail address. 5. Specify the account options: User must change password at next logon: Select this check box to force the user to change the account password when next logging on to the system. Clear this check box to allow the user to keep the same password. User cannot change password: Select this check box to prevent the user from changing the account password. Clear this check box to allow the user to change the account password. Password never expires: Select this check box to allow the user to continue using the same password indefinitely. Clear this check box to require that the user change the account password at intervals specified by the security policy. Account is disabled: Select this check box to prevent the user from logging into the account. Clear this check box to allow the user to log into the account. 6. In the Password box, type a password for the user account. 7. In the Confirm password box, type the same password you typed in the Password box. 8. To add the user account to one or more user groups, use the Group Membership tab. 9. Click Create to save your changes and close the dialog.
Adding a Windows-linked user

1. Right-click the Users folder and select New > Windows-linked User from the shortcut menu to display the New Windows-Linked User dialog.
91
2. Click Add to display the Select Users dialog.
3. In the Select Users dialog box, type in one or more user names (separated by semicolons) and click Check Names to validate them or click the Advanced button to browse for users in the specified location (computer). Click OK to add the selected groups and close the dialog.
92
4. In the New Windows-Linked User dialog box, review the list of users you added. To remove any users you might have added unintentionally, select the users, and then click Remove. To add more users, repeat Steps 2 and 3. 5. Click Create to save your changes and close the dialog.
Application privileges
A privilege is a distinct function of the client application that is assigned to security groups or individual users. Individual users can have privileges assigned to them, and they can inherit privileges from the security groups to which they belong. For example, if a group has been granted privileges for the Configuration Console Create New Report Objects feature, users assigned to that group are able to create new report objects in the Configuration Console.
FactoryTalk Historian Classic and FactoryTalk Metrics (Configuration Console) privileges

Note: The user must also have a FactoryTalk Historian or FactoryTalk Metrics Author activation in order to have access to the function of the client application.
Create New Reports: Allows the selected user or group to create reports for personal use. A report that has been created under this privilege can be viewed and edited by the user who created the report. Create Public Reports: Allows the selected user or group to create reports for public use. The creator of the report can grant view and edit privileges for the report to other users and groups. Create New Report Objects: Allows the selected user or group to create report objects for personal use. A report object that has been created under this privilege can be viewed and edited by the user who created the report object. Create Public Report Objects: Allows the selected user or group to create report objects for public use. The creator of the report object can grant view and edit privileges for the report object to other users and groups. Create New Filters: Allows the selected user or group to create filters for personal use. A filter that has been created under this privilege can be viewed and edited by the user who created the filter. Create Public Filters: Allows the selected user or group to create filters for public use. The creator of the filter can grant view and edit privileges for the filter to other users and groups.
93
Create New Report Data Sources: Allows the selected user or group to create report data sources. A report data source that has been created under this privilege can be viewed and edited by the user who created the report data source. Save Report Object Contents to File: Allows the selected user or group to save the data from a text report object to a comma separated values (.csv) or html (.htm) file. Organize Plant Model: Allows the selected user or group to create and modify activity areas in the plant model. Manage Reporting Tags: (FactoryTalk Historian Author activation only) Allows the selected user or group to use the Time-Series Reporting Tags dialog to create, modify and configure reporting tags. View Time-Series Comment: (FactoryTalk Historian Classic users only) Allows the selected user or group to view the Value, X-Axis, and Y-Axis comments that have been associated with time-series data. Add Time-Series Comment: (FactoryTalk Historian Classic users only) Allows the selected user or group to associate Value, X-Axis, and Y-Axis comments with time-series data. Edit/Delete Time-Series Comment: (FactoryTalk Historian Classic users only) Allows the selected user or group to modify and delete Value, X-Axis, and Y-Axis comments that have been associated with time-series data. Manage Performance Parameters: (FactoryTalk Metrics Author activation only) Allows the selected user or group to use the FactoryTalk Metrics Performance Parameters dialog to specify the parameters that will be used in the calculation of OEE for an activity area. Manage FactoryTalk Metrics Manual Data Collection: (FactoryTalk Metrics Author activation only) Allows the selected user or group to modify and delete FactoryTalk Metrics workcell data. Manage Time Pattern: (FactoryTalk Metrics Author activation only) Allows the selected user or group to create and modify time patterns, configure composites, and schedule exceptions.
Managing user access

Client activations control the functions an individual user is permitted to perform on a specific RSBizWare server. Access to the content on that server is further restricted by assignment of application privileges and object permissions. You can manage the privileges and permissions a user has either by assigning privileges and permissions directly to the user or by assigning privileges and permissions to a user group, then
94
placing the user in one or more user groups. A user belonging to a group will inherit the privileges and permissions that have been assigned to the group. Since users can belong to multiple groups, groups can be broken down into logical areas of application functionality. To assign application privileges and client activations in the Service Console, select Programs > Rockwell Software > RSBizWare > Service Console from the Windows Start menu. In the Service Console tree, expand the Security Services Manager tree item, then expand the Administration tree item. Click the Users and Groups tree item to display the Users and Groups dialog in the work area.
On the Users and Groups dialog, click the Refresh button to display the groups and users that have been configured in the FactoryTalk Administration Console. Only the FactoryTalk groups that have at least one user assigned to them will be displayed in the Groups list.
95
Assigning application privileges to groups

1. On the Users and Groups dialog, select a group from the Groups list and press the Edit Group Properties button to display the Security Control dialog.
2. Select the RSBizWare server type for which you want to assign privileges. You must have at least one RSBizWare application server of that server type registered in order to assign privileges for that server type. 3. Select one of the registered application servers. 4. To assign a privilege to the group, click the check box to the left of the privilege name. Any user that belongs to the selected group will then be updated on the next login to that application server. In the above example, we have assigned the Save Report Object Contents to File, and Manage Reporting Tags privileges to the Production Managers group. 5. Click OK to save your changes and close the dialog.
Assigning application privileges to users

If the users that you have created or imported in the FactoryTalk Administration Console are to have authoring capabilities in the client software, you will need to assign client licenses for one or more RSBizWare client applications to the users.
96
1. On the Users and Groups dialog, select a user from the Users list and press the Edit User Properties button to display the Security Control dialog.
2. Select the RSBizWare server type for which you want to assign privileges. You must have at least one RSBizWare application server of that server type registered in order to assign privileges for that server type. 3. Select one of the registered application servers. 4. To assign a privilege to the user, click the check box to the left of the privilege name. In the above example, John Smith has inherited the Save Report Object Contents to File, and Manage Reporting Tags privileges from the Production Managers group, of which he is a member. 5. Click OK to save your changes and close the dialog.
97
Assigning client activations to users

1. On the Users and Groups dialog, select a user from the Users list and press the Edit User Properties button to display the Security Control dialog. 2. Click the License & Activation tab.
3. Select the RSBizWare server type for which you want to assign activations. 4. Click the check boxes next to the activations that you want to assign to this user. The check marks indicate the activations that have been assigned to the user. 5. Click OK to save your changes and close the dialog.
Assigning object permissions to users and groups

To further define security within your RSBizWare system, you may assign default and custom object permissions to user groups and users. Default object permissions are assigned in the Service Console. See Configuring Information Services Manager default permissions on page 63 for instructions. Custom object permissions are assigned in the Configuration Console. See the Set Permissions topic in the Configuration Console online help for instructions.
98
Configuring Data Collection

The Information Services Manager and the Metrics Server Manager use Rockwell Automations FactoryTalk Transaction Manager to collect data from the control system and log it into the RSBizWare database. The FactoryTalk Transaction Manager Configuration administration functions of the Security Services Manager allow you to control the FactoryTalk Transaction Manager configurations that will be used to collect data. Administration functions include FactoryTalk Transaction Manager Configuration Server registration, creation of configurations and connectors, configuration startup and shutdown, and system troubleshooting.
Registering the FactoryTalk Transaction Manager Configuration Server

The Configuration Server is a Windows 2000 service that runs continuously to provide a single interface to the configuration files (.dat files) that make up FactoryTalk Transaction Manager. The Configuration Server simplifies access to configuration files by filtering all changes to the files and interfacing with other FactoryTalk Transaction Manager services. A collection of all changes that affect a configuration can be recorded in an audit trail. Before the Security Services Manager can control the FactoryTalk Transaction Manager configurations on your computer or on another computer on the network, you must first register the FactoryTalk Transaction Manager Configuration Server. Registering the FactoryTalk Transaction Manager Configuration Server with the Security Services Manager simply tells the Security Services Manager where to locate FactoryTalk Transaction Manager configurations on the network. 1. To register the FactoryTalk Transaction Manager Configuration Server, make sure the Security Services Manager is running. Right-click the FactoryTalk Transaction Manager Configurations tree item under the Security Services Manager and select Register Server from the shortcut menu to display the Service Console Registration dialog.
99
2. The Hostname or IP address field defaults to the name of the local machine. Enter the computer name or IP address of the host computer whose FactoryTalk Transaction Manager configurations you would like to view. If you are registering a remote host, you can use the Browse button (...) to the right of the Hostname box to find the computer on the network. 3. The description will default to FactoryTalk Transaction Manager on Hostname where Hostname is the name of the computer that you entered. If desired, you may change the description of the server to something more meaningful to your organization. 4. Click OK to register the server. All of the FactoryTalk Transaction Manager configurations on this server will be added into the FactoryTalk Transaction Manager Configuration tree. You can also unregister the FactoryTalk Transaction Manager Configuration Server as needed. To unregister the FactoryTalk Transaction Manager Configuration Server, rightclick the server tree item and select Unregister Server from the shortcut menu.
Defining a FactoryTalk Transaction Manager configuration

After you have registered the FactoryTalk Transaction Manager Server computer with the Service Console, you can define FactoryTalk Transaction Manager configurations. A FactoryTalk Transaction Manager configuration connects any control system from which data will be collected to the predefined data model used by the RSBizWare database to store production data. The configuration consists of transactions and the connectors, data points, and data objects required to implement the transactions. A transaction is a single exchange of data between the industrial control system typically a network of programmable logic controllers (PLCs)and a database. An example of a transaction is a temperature value that is collected from a data point on a programmable logic controller and logged to a database table. A data point is a specific data location or register in the control system that is made available to FactoryTalk Transaction Manager transactions. After it is defined, a data point can be used by any FactoryTalk Transaction Manager transaction.
The FactoryTalk Transaction Manager is a Windows service that controls and executes FactoryTalk Transaction Manager transactions contained in a configuration. The Transaction Manager uses connectors to interface with field devices and the database.
100
8 CONFIGURING DATA COLLECTION
Control connectors
The Transaction Manager interfaces with the industrial control system device via a control connector. A control connector is a Windows service that collects data from a data server such as a PLC and sends it to the FactoryTalk Transaction Manager. The following are the types of control connectors that you can use: Dynamic Data Exchange (DDE): The DDE control connector service is provided for legacy connections to DDE servers or to provide functionality that is not supported by the OPC specification. RSLinx Classic OPC: The RSLinx Classic control connector service is the preferred method to use when browsing for data tags that reside in Allen-Bradley Programmable Logic Controllers, except for ControlLogix 555x processor items. You should use Generic OPC control connectors with ControlLogix 555x processors. RSView32: The RSView32 control connector service is used to interface with tags provided by RSView32 applications. The RSView32 control connector must be installed on the same computer on which the RSView32 project is running. Generic OPC: The Generic OPC control connector service is used to interface with items provided by any OPC server that conforms to OPC interface specifications. FactoryTalk LiveData Connector: FactoryTalk Transaction Manager uses FactoryTalk LiveData to communicate with FactoryTalk LiveData servers, such as RSLinx Classic and RSView Supervisory Edition. FactoryTalk Transaction Manager connects to the FactoryTalk Directory, which allows FactoryTalk Transaction Manager to browse the available data items. This control connector is required if you plan to perform online edits with your configuration.
Enterprise connectors
The Transaction Manager interfaces with the database via an enterprise connector. An enterprise connector is a Windows service that receives data from the FactoryTalk Transaction Manager and logs it to a database. The following are the types of enterprise connectors that you can use: ODBC: The ODBC enterprise database connector allows you to interface with virtually any ODBC-compliant database including Microsoft Access, Microsoft SQL Server 6.5 or later, IBM DB2 or Sybase. Oracle OCI: The Oracle Call Interface (OCI) enterprise database connector allows you to connect to database objects from an Oracle server. If you are using Oracle OCI, you need to install locally SQL*NET 2.3x or later, Net8, or Oracle Net services (all from Oracle). You can then connect to an Oracle database versions 8.1 through 9.2.
101
Microsoft OLE-DB: The Microsoft OLE DB enterprise database connector should only be used for interfacing with Microsoft SQL Server 2000. Microsoft OLE DB allows you to browse a SQL Server 2000 database without a data source name (DSN) and is the preferred method of connection. Microsoft COM+: The Microsoft COM+ enterprise application connector allows you to interface with Microsoft COM+ application components. These components must be integrated into a Windows 2000 COM+ environment. RSBizWare-only applications do not support this connector. It is for use only with FactoryTalk Transaction Manager Professional installations. FactoryTalk Metrics: The FactoryTalk Metrics enterprise application connector is used only with FactoryTalk Metrics. The connector stores data in the RSBizWare database. SAP: The SAP enterprise application connector allows you to interface with SAP R/3 systems modules. RSBizWare-only applications do not support this connector. It is for use only with FactoryTalk Transaction Manager Professional installations. Time-series Data Compression: This connector stores time-series data in a pre-defined compressed format in either an Oracle database or a Microsoft SQL Server database. The compressed data point records contain binary data that can only be viewed through FactoryTalk Historian Classic. For a detailed description of data compression and the Compression connector, see Data Compression on page 125.
102
When you create a FactoryTalk Transaction Manager configuration, you are identifying the FactoryTalk Transaction Manager services that you want to use and the computer on which those services will run. 1. To create a FactoryTalk Transaction Manager configuration, right-click the FactoryTalk Transaction Manager Configurations tree item in the Service Console tree and select FactoryTalk Transaction Manager Actions > Add Configuration from the shortcut menu to display the Add FactoryTalk Transaction Manager Configuration dialog. This dialog allows you to specify connection parameters for the FactoryTalk Transaction Manager configuration.
2. Provide a name for your configuration and the file path where your configuration will be stored. 3. Online editing is the ability to make changes to data collection without stopping and restarting the FactoryTalk Transaction Manager configuration that is performing the collection. If you want to be able to perform online editing, select the Enable online edits check box. Online edits require the use of the FactoryTalk LiveData control connector. For additional information about online edits, see the Online Edits topic in the online help.
103
4. Enter the user name and password for the Windows system account that the Transaction Manager will use when it runs. This account must have Administratorlevel privileges in the operating system. 5. Select the types of control and enterprise connectors that the configuration will use. A configuration can contain any combination of control and enterprise connectors; however, if you will be performing online edits with this configuration, you can use only the FactoryTalk LiveData control connector. For FactoryTalk Metrics, you will need: One FactoryTalk Metrics Enterprise Connector At least one control connector You do not have to select any other connectors unless you plan to use them to create custom transactions to perform functions not supported by FactoryTalk Metrics. For FactoryTalk Historian Classic, you will need: One or more of the following enterprise connectors: ODBC, Oracle OCI, Microsoft OLE-DB, or Time-series Data Compression At least one control connector You do not have to select any other connectors unless you plan to use them to create custom transactions to perform functions not supported by FactoryTalk Historian Classic. 6. Click OK to save your changes and close the dialog.
104
Defining a FactoryTalk Transaction Manager connector

1. The Add FactoryTalk Transaction Manager Connector dialog shown below will display once for each connector that you selected on the Add FactoryTalk Transaction Manager Configuration dialog. This dialog allows you to name the connector and to define where the services will run.
2. Provide a name for the connector or accept the defaults that are provided. 3. Enter the user name and password for the Windows system account that the connector will use when it runs. This account must have Administrator-level privileges in the operating system on the host computer. 4. If you want to add another connector of this same type to the configuration, check the Add Another Connector check box. You will be prompted to define the new connector when you close this dialog.
Note: You cannot configure multiple FactoryTalk Transaction Manager Control Connectors of the same type to run on the same server.
5. Press Done to save your changes and close the dialog. After all connectors have been configured, the configuration, the Transaction Manager, and the connectors will be displayed on the Service Console tree. To add additional FactoryTalk Transaction Manager connectors to a configuration, rightclick the desired configuration in the tree and select Add a Connector from the shortcut menu.
105
Registering a FactoryTalk Transaction Manager configuration

After you have created a FactoryTalk Transaction Manager configuration, you will need to register it with an Information Services Manager in the Service Console if you want to make the configuration available to FactoryTalk Historian Classic or FactoryTalk Metrics for data collection. 1. Open the tree item for the Information Services Manager with which you want to register your configuration. Right-click the Data Collection tree item under the server tree item and select Register FactoryTalk Transaction Manager Configuration from the shortcut menu that will display. The FactoryTalk Transaction Manager Registration Wizard Welcome screen will display. 2. Click Next to begin the wizard and to display the Local or Remote dialog, which allows you to specify where to look for FactoryTalk Transaction Manager configurations.
3. You can look on your local machine or on a remote machine for FactoryTalk Transaction Manager configurations. To search on a remote computer for FactoryTalk Transaction Manager configurations, click the Browse button (...). You must have Windows Administrative privileges on the remote computer.
106
4. Click Next to continue to the Select FactoryTalk Transaction Manager Configuration dialog, which lists the configurations that the wizard has found on the selected machine. Use this dialog to associate the selected FactoryTalk Transaction Manager configuration with FactoryTalk Metrics and/or FactoryTalk Historian Classic.
5. Select a FactoryTalk Transaction Manager configuration from the list. You can register only one FactoryTalk Transaction Manager configuration at a time. 6. The check boxes at the bottom of the dialog will reset to indicate the status of the configuration with the FactoryTalk Historian Classic and FactoryTalk Metrics applications. Select the check box(es) next to the application(s) with which you want to register the configuration.
107
7. Click Next to continue. If you chose to register a configuration with the FactoryTalk Historian Classic application, the Enterprise Connection Database Settings dialog will display. This dialog allows you to specify the database connectivity settings for one or more of the following FactoryTalk Transaction Manager enterprise connections: ODBC, OCI, OLE DB, and Time-series Data Compression. The Configured column tells you whether the connectivity settings have been configured for the enterprise connection.
8. Select an enterprise connection from the list and press Configure to display the Enterprise Connection Settings dialog.
108
The exact look of the Enterprise Connection Settings dialog will depend on the type of enterprise connection that you are configuring, but it is basically gathering database connectivity information. The figure above shows the dialog that will display for the Compression Enterprise Connector. 9. Enter the database connectivity information that is requested. 10. When you are finished configuring database connectivity information, click OK to save your changes and close the dialog. You will be returned to the Enterprise Connection Database Settings dialog.
Note: Since you will not be able to come back to the Enterprise Connection Database Settings dialog to configure the connectivity settings for any enterprise connections that you skip, make sure you specify the connectivity settings for all of the FactoryTalk Transaction Manager enterprise connections that you intend to use.
Press Next to continue to the Summary dialog. 11. On the Completing the Wizard dialog, review the choices you made during the registration of your FactoryTalk Transaction Manager configurations. Press Finish to save your changes and exit the wizard. The configuration will now be displayed in the Data Collection tree that is under the Information Services Manager.
Unregistering a FactoryTalk Transaction Manager configuration

If you no longer want users to be able to use a FactoryTalk Transaction Manager configuration for future data collection within the RSBizWare software, you will need to unregister the configuration. Unregistering a configuration will disassociate the configuration from FactoryTalk Metrics and/or FactoryTalk Historian Classic. Unregistering the configuration will not delete the configuration. The configuration will remain a valid FactoryTalk Transaction Manager configuration and can still be used within the FactoryTalk Transaction Manager software.
Note: You cannot unregister FactoryTalk Transaction Manager configurations that are being used in the FactoryTalk Metrics Performance Parameters for an enabled activity area.
1. Right-click the FactoryTalk Transaction Manager configuration in the Data Collection tree item under the Information Services Manager. Select Unregister Configuration from the shortcut menu to display the FactoryTalk Transaction Manager Registration Removal Wizard Welcome screen.
109
2. Click Next to begin the wizard and display the Select RSBizWare Application dialog.
3. Select the applications for which you want to unregister the configuration. You can unregister the FactoryTalk Transaction Manager configuration from FactoryTalk Metrics and/or FactoryTalk Historian Classic.
110
4. Click Next to continue. If you are unregistering a configuration from FactoryTalk Historian Classic, the Historical Data dialog will display.
5. Select the Delete all historical data... check box if you want to delete the data that has been collected using this configuration. This will release the database space that is used by the data. If you do not choose to delete the data, your users will still be able to report on the data. Click Next to continue to the Summary dialog. 6. On the Completing the Wizard dialog, review the choices you made during the unregistration of your FactoryTalk Transaction Manager configurations. Press Finish to save your changes and exit the wizard. The configuration is removed from the Data Collection folder in the Security Services Manager tree.
Configuration startup and shutdown

At this point, there are no FactoryTalk Transaction Manager transactions in the configuration. FactoryTalk Transaction Manager transactions are created when users define time-series data collection (FactoryTalk Historian Classic) or performance parameters (FactoryTalk Metrics). For information on defining time-series data collection, see the FactoryTalk Historian Classic Users Guide. For information on defining performance parameters, see the FactoryTalk Metrics Users Guide.
111
After transactions have been created in the FactoryTalk Transaction Manager configuration, the configuration must be started for data collection to occur. Use the Service Console to start and stop FactoryTalk Transaction Manager configurations as needed (subject to Windows security and Service Control access on the host computer). To start your configuration, right-click the configuration in the Service Console tree and select Start Configuration from the shortcut menu. To stop the configuration, select Stop Configuration from the shortcut menu. In the server tree, the traffic light to the left of the server name indicates the state of the configuration. A red traffic light indicates that the configuration is not running. A yellow traffic light indicates that one or more of the FactoryTalk Transaction Manager services for the configuration did not start. A green traffic light indicates that the configuration is running.
Troubleshooting
You can view the transaction statistics of a running configuration. Click the configuration for which you want to view transaction statistics. The FactoryTalk Transaction Manager Configuration dialog will display in the work area. The list box at the bottom of the dialog contains a list of transaction statistics for the selected configuration. Transaction statistics include the following: Total: The total number of transactions that have been triggered. Passed: The number of transactions that have completed successfully. Failed: The number of transactions that have failed. % Passed: The number of successful transactions divided by the total number of transactions. Cached: The number of transactions that are currently in the Transaction Cache files. DB Passed: The number of transactions that have been successfully inserted into the database or handed to the Metrics Server Manager. DB Failed: The number of transactions that have not been inserted into the database or handed to the Metrics Server Manager as a result of a database error. DB Pending: The number of transactions that are waiting to be inserted into the database or handed to the Metrics Server Manager.
112
Diagnostics Reporting
When an RSBizWare service is running, it generates diagnostic reporting messages that are useful for determining the source of problems when they arise.
Message types
An RSBizWare service may produce the following types of diagnostic reporting messages: Debug: Low-level debugging messages primarily for technical support. Info: Informational messages for reporting status. Warn: An exception condition that may have prevented the server from performing a non-essential action. Error: An exception condition that prevented the server from performing an essential action. Fatal: An exception condition that caused the server to stop running.
Output types
There are several ways to log diagnostic messages. You can choose to have the server direct log messages to an e-mail address, to the Event Log on the server machine, and/or to a text log file on the server machine. LOG
FILES
Log files are the most common way to log diagnostic messages. Messages can be written directly to a text log file that you specify. Press the View Log button on the Server Settings dialog for the RSBizWare server to view the log file that is created by the server. THE WINDOWS EVENT VIEWER Messages that are sent to the Windows Event Log can be viewed using the Windows Event Viewer on the server machine. E-MAIL If you choose to have messages directed to e-mail, the Security Services Manager will send an e-mail containing messages of the types that you select to the recipient that you specify. This is useful if you want to notify your System Administrator automatically when the server produces a certain level of message, such as when a fatal message is generated.
113
Log file configuration

The Service Console allows you to specify how to handle the messages that are generated by RSBizWare servers and FactoryTalk Transaction Manager configurations. To configure the diagnostic reporting settings for a server, you must already have the server registered with the Security Services Manager. To configure the diagnostic reporting settings for a configuration, you must already have the configuration server for that configuration registered with the Security Services Manager. Open the Administration tree item in the Security Services Manager tree and click the Configure Diagnostic Logs tree item. The Configure Diagnostic Logs dialog will display in the work area to the right of the tree.
Use this dialog to specify how messages that are generated by the server will be handled. 1. The list at the top of the Configure Diagnostic Logs dialog contains the names of the servers and configurations for which you can configure log file information. Select the name of the server or configuration for which you want to configure log file information. 2. Use the Log File fields to provide the path and file name for the log file to which the diagnostic information will be written. Remember that the file name has to be a valid path on the computer where the selected RSBizWare server or FactoryTalk Transaction Manager configuration is running.
114
9 DIAGNOSTICS REPORTING
3. Depending on the type of logging options you choose and the activity level of the server, the log files can become very large. The Number of Messages and Max File Size fields will limit how large the log file grows. After the maximum number of messages or the maximum file size is reached, diagnostic logging will wrap to the top of the file. While this limits the size of the log file, it does present a risk of losing earlier log messages as the file wraps. The Buffer Size value restricts how often the server writes to the log file. The value represents the number of bytes of diagnostic messages that are buffered before they are written. Using a higher value for Buffer Size can improve server performance, but it may prevent you from seeing diagnostics messages in near-real time. Using a Buffer Size of zero will turn off all buffering so that diagnostic messages are written as events occur. Unless you have disk space or performance concerns, you can accept the default values for Number of Messages, Max File Size, and Buffer Size. 4. The Number of Log File Revisions to Keep field allows you to keep multiple revisions of the log file for diagnostic purposes. Enter the number of revisions of the file that you want to store. If you specify a number greater than zero, the server will create a new log file each time it is started, up to the number of revisions specified. After the number of revisions is reached, the server will begin to overwrite the existing log files. 5. Use the Logging Options check boxes to indicate the types of messages that you want the server to write to the different output options.
Note: Since the servers and FactoryTalk Transaction Manager configurations produce a large quantity of Debug messages, turning on the Debug logging option can significantly increase the size of the log file and can significantly affect performance. This option is not recommended unless you are trying to troubleshoot a problem.
6. Specify how the e-mail log reports will be sent. Enter the SMTP e-mail address from which you want the log report e-mails to be sent and the e-mail address to which you want to send the log report e-mails. Enter the e-mail account password of the sending account and the outgoing e-mail server to be used when the log report e-mails are sent. The e-mail logging option uses the SMTP protocol to send e-mail, so make sure the e-mail server you select supports SMTP. 7. Press Apply to make your changes permanent. You can change the logging options at any time, but you will need to stop and restart the selected RSBizWare server or FactoryTalk Transaction Manager configuration in order for the changes to take effect.
115
System troubleshooting
The messages that are generated by the server or configuration are useful for monitoring system activity and determining the source of problems when they arise. To monitor the server or configuration, or to diagnose a problem with the server or configuration, you can view the contents of the server log file, use the Windows Event Viewer to view the contents of the Windows Event Log, or examine the contents of the log e-mail that was sent. To view the contents of the log file that is generated by the server or configuration, click the tree item for the server or configuration in the Security Services Manager tree. The Server Settings or Configuration Settings dialog will display. Press the View Log button to open the log file.
116
Advanced Topics
Remote connection to an RSBizWare server
RSBizWare clients connect to RSBizWare servers over a TCP/IP socket connection, using the IP address and the port number of the RSBizWare server machine. To allow successful connections between remote RSBizWare clients and RSBizWare servers, network security must be configured to permit access to the server ports. If you are running Windows XP or Windows Server 2003 and the Windows Firewall is enabled, network security configuration will be performed for you. If you are running another firewall system, you will need to manually open the following ports to allow inbound and outbound traffic: Port 4120 - To communicate with the Information Services Manager Port 4121 - To communicate with the Security Services Manager Port 4122 - To communicate with the Metrics Server Manager Port 4123 - To communicate with the Report Schedule Manager Port 4124 - To communicate with the Scheduler Server Port 402 - To communicate with the FactoryTalk Transaction Manager Configuration Server The Configuration Console also uses HTTP in addition to raw TCP/IP to communicate to the Information Services Manager. The default HTTP port is 8080; however, the HTTP port can be changed through the Server Settings for the Information Services Manager in the Service Console.
Note: Oracle 9.2.0.1.0 uses port 8080. If you are using this version of Oracle, you must set the HTTP port to something other than 8080.
Registering the Excel Add-in as a non-installing user

The Excel Add-in, which enables you to retrieve RSBizWare data directly into Microsoft Excel, is installed automatically with the RSBizWare Complete install option. It can also be installed by way of the RSBizWare Custom install option. (See Installing or Upgrading the RSBizWare Software on page 19). However, the installation process for the Excel Add-in only registers the component for the user doing the installation. If one or more other users on a particular computer intend to use the Excel Add-in, each such user must manually register the Excel Add-in.
117
To register the Excel Add-in as a non-installing user, each such user must do the following on each machine on which the Excel Add-in was previously installed: 1. Log into the computer as the local user who intends to use the Excel Add-in. 2. Copy the ExcelAddin.reg file from the \Support folder on the RSBizWare CD to a folder on the local machine. 3. Double-click the ExcelAddin.reg file. 4. When prompted to add the information in the ExcelAddin.reg file to the registry, click Yes.
Note: For information on using the Excel Add-in, see the FactoryTalk Historian Classic Users Guide and the FactoryTalk Metrics Users Guide.
118
Database Tips
This chapter contains miscellaneous tips on using SQL Server and Oracle with RSBizWare.
Maintaining frequently-used RSBizWare tables and indexes

The RSBizWare tables and indexes listed in the following two tables are used heavily by the specified components of the RSBizWare product. The tables and indexes are used extensively by RSBizWare database views that are in turn used by most RSBizWare reports. If these tables and indexes are not properly maintained, report performance can degrade.
Table B-1. Frequently-used RSBizWare tables Component FactoryTalk Historian Classic FactoryTalk Historian Classic FactoryTalk Metrics FactoryTalk Metrics FactoryTalk Metrics FactoryTalk Metrics FactoryTalk Metrics FactoryTalk Metrics Table
RSDataPointSample RSSQL_CMPCOMPRESS OEEEvent OEEEventFlexData OEEFaultMetricData OEEStateData OEEWorkcell OEEWorkcellFlexData
Table B-1. Frequently-used RSBizWare indexes Component FactoryTalk Historian Classic FactoryTalk Historian Classic FactoryTalk Metrics FactoryTalk Metrics FactoryTalk Metrics FactoryTalk Metrics Table
RSDataPointSample_IDX1 RSSQL_CMPCompress_IDX1 OEEEvent_IDX1 OEEEvent_IDX2 OEEEvent_IDX3 OEEEvent_IDX4
119
Table B-1. Frequently-used RSBizWare indexes Component FactoryTalk Metrics FactoryTalk Metrics FactoryTalk Metrics FactoryTalk Metrics Table
OEEEvent_IDX5 OEEWorkcell_IDX1 OEEWorkcell_IDX2 OEEWorkcell_IDX3
These database objects have the following characteristics that result in the need for periodic maintenance. Indexes can become fragmented Log files can become very large Tablespaces can fill up Separate tablespaces may be needed Partitioning may be necessary Additional data files may be necessary Older data may need to be purged All of these issues can be addressed by creating and executing a regularly scheduled database maintenance plan.
Using Oracle with RSBizWare

The FactoryTalk Historian Classic, FactoryTalk Metrics, and FactoryTalk Scheduler applications require a single database for permanent storage. Although they share the same database, each application uses unique tables to support its core functions. The RSBizWare database can be either a Microsoft SQL Server database or an Oracle database. If you plan to use Oracle, read this chapter to learn about recommended Oracle database settings and to learn how to tune your Oracle database for use with the timeseries analysis capabilities of the FactoryTalk Historian Classic application.
Recommended database settings

This section details the recommended settings to use when you are configuring an Oracle database for use with RSBizWare.
120
B DATABASE TIPS
CREATING
TABLESPACES
It is recommended to have the Oracle Database Administrator create separate tablespaces for an RSBizWare installation. Tablespaces needed: Data Index Temp Rollback Segments Oracle 9i and 10g eliminate the task of managing rollback segments. Administrators can assign a tablespace for rollback space, and the database will do the work.
Note: The RSBizWare data model will be loaded into the DEFAULT tablespace of the user initializing the database. It is not recommended Oracle practice to have all objects in the same tablespace. It is recommended that you use Oracle Change Management utilities to move Indexes and Keys to the Index tablespace you create. Please refer to Oracle documentation for instructions.
CONFIGURING
THE DATABASE USER
The next step is to create a database user that will be the owner of the RSBizWare schema. The user needs these minimum privileges: CREATE SESSION, CREATE TABLE, CREATE PROCEDURE, CREATE PUBLIC SYNONYM, CREATE VIEW, CREATE TRIGGER, CREATE SYNONYM, and CREATE SEQUENCE. After the user is created, the user should be configured to use the following tablespaces: Data Default Tablespace, quota unlimited Index Quota unlimited Temp Temporary Tablespace CREATING
A
NET CONFIGURATION
CONNECTION
A Net Configuration connection is needed in order for processes, such as the Information Services Manager, to connect to the database. Run the Net Configuration Assistant on the computers that will be hosting RSBizWare services such as the FactoryTalk Transaction Manager Enterprise Connector service and the Information Services Manager to create Net Configuration connections to the database. The Oracle database does not need to be running on the same computers as these services. Follow these steps to create a new Net Configuration connection: 1. Name your Net Configuration connection BW.
121
2. Select TCP/IP (Internet Protocol) connection. 3. Enter the host name of the computer where your Oracle database is running and accept the default port of 1521. 4. Enter BW in the Service Name field. 5. Test your connection. 6. Finish the configuration. CREATING
AN
ORACLE ODBC DSN
RSBizWare services connect to Oracle using ODBC. Use the ODBC Data Source Administrator, available from the Settings > Control Panel > Administrative Tools > Data Sources (ODBC) on the Windows 2000 Start menu, to create a new ODBC Connection. Follow these steps to create a new ODBC connection to Oracle: 1. Select the Oracle ODBC Driver. 2. Give the data source a name and description. For example, when configuring an ODBC DSN for the Information Services Manager, use the name BizWare and the description RSBizWare Database. 3. Enter the Service Name and Oracle User Name that you used for your Net Configuration connection.
Tuning an Oracle database for use with FactoryTalk Historian Classic

This section is intended for organizations that want to use Oracle as a database solution for the FactoryTalk Historian Classic application. These are suggested database settings that we feel will help you improve performance using FactoryTalk Historian Classics time-series analysis capabilities. It is assumed that you have already installed the RSBizWare software and that you have accepted a typical installation. After you have created your Oracle RSBizWare database, you will need to configure the following settings before you attempt to start the Information Services Manager. PERFORMANCE
TUNING YOUR
RSBIZWARE
DATABASE
Change the tablespace configuration settings as follows: DATA Tablespace: Change the Size to 500 MB. Change the % Increase to 10. Turn the Auto Extend ON. Change Initial to 1024 (KB). Check the Unlimited box.
122
B DATABASE TIPS
ROLLBACK Tablespace: Change the Size to 100 MB. Turn Auto Extend ON. Check the Unlimited box. INDEX Tablespace: Change the Size to 200 MB. Change the % Increase to 10. Turn the Auto Extend ON. Check the Unlimited box. TEMPORARY Tablespace: Change the Size to 250 MB. Change the % Increase to 10. Turn Auto Extend ON. The following are recommended settings for the init.ora file: Add the following line after the control_files line.
rollback_segments = (SYSTEM, RB0, RB1, RB2, RB3, RB4, RB5, RB6)
Set db_block_buffers to 20000. Set sort_area_size to 2000000. Set sort_area_retained_size to 1000000. PREPARING
TO RUN THE NEW
ORACLE
DATABASE
The next step is to restart the database so the new settings take effect, then configure the necessary parameters so that FactoryTalk Transaction Manager and the Information Services Manager can connect to the database. 1. In order for the changes to the init.ora to take effect, you must stop and restart the OracleService[Database Name] service. Refer to your Oracle documentation for instructions. 2. Follow the instructions for creating a Net Configuration connection in Recommended database settings on page 120. 3. Follow the instructions for creating an Oracle ODBC DSN in Recommended database settings on page 120. 4. Start the Information Services Manager in the Service Console. Starting and stopping an RSBizWare server on page 61 for information on starting the server. After the server is started, the database will load.
123
124
Data Compression
The Time-series Data Compression Enterprise Connector stores time-series data in a predefined compressed format in either an Oracle or Microsoft SQL Server database. The compressed data point records contain binary data that can only be viewed through the FactoryTalk Historian Classic application.
Why use data compression?

When an application such as FactoryTalk Historian Classic or RSView32 collects and stores data in a database, it consumes incremental storage space with each data record that is stored. For a given storage medium (usually the database servers hard disk), there is a finite amount of data that can be stored. As a result, the user must be mindful of how much data is being stored, how often it is being stored, and the size of the storage medium. For example, assume that you have configured your FactoryTalk Historian Classic application to collect and log data for 100 data points from your control system once every 10 seconds. The disk space used after a year can be estimated as follows:
100 Data Points ------------------------ 86,400 Seconds 365 Days 10.1 Gb ------------------------------------- 42 Bytes- ------------------------------------- ---------------------- = -----------------10 Seconds Data Point 1 Day 1 Year 1 Year
Without compression, after the amount of logged data approached the disk capacity, the user would traditionally have to: Increase the total disk size by adding additional disk drives or replace the existing disk with a larger disk. Archive the stored data to a backup medium (i.e. a tape drive), freeing disk space for future logging. Aside from the maintenance considerations involved with these two options, the ultimate result is that the logged data may have to be taken offline and may no longer be readily available to users who wish to view and/or report on it. This tends to make the archiving option undesirable. The Time-series Data Compression Enterprise Connector conserves disk space by storing the data in a compressed format. Since the available disk space is used more efficiently, data can be maintained online for longer periods of time. This reduces maintenance costs associated with disk replacement or archiving, and maximizes your investment in your current hardware.
125
How does data compression work?
The Time-series Data Compression Enterprise Connector is designed to capture timeseries data and store it in the database in a compressed format, reducing the size of your data files. Typically, FactoryTalk Historian Classic inserts a new record in the database each time a data point sample is collected; however, using the Time-series Data Compression Enterprise Connector, a user-configured number of data point samples will be collected and compressed into a block of data that is then inserted into the database as a single record. The following user-readable summary information is included with the block of data: An internal data point identifier The time range covered by the compressed data The max and min data point samples that were collected The number of data point samples that make up the compressed record The number of samples (if any) collected with bad OPC quality
126
C DATA COMPRESSION
What will my compression ratio be?

Your individual compression ratio will vary based on several factors, including the nature of the data being collected and transaction parameters such as block size, sample rate, and signal type. For example, steady-state data will yield a higher compression factor than random data. For this reason, it can be difficult to exactly predict the compression ratio that you will realize. The following compression ratios were observed based on system testing with data point samples collected once a second and a block size of 256.
Signal Type Steady State Saw Tooth Random Compression Ratio 15:1 7:1 3:1
How do I view my compressed data?

Compressed data can be graphed and viewed easily using time-series report objects in an RSBizWare report. Depending on the time range and options selected, the chart will display either individual values for the collected data point obtained by un-compressing the block or the summary information from the compressed block. Additionally, the Information Services Manager utilizes a powerful sampling algorithm which may be invoked if a large time span is selected for the chart. Compressed data can also be viewed through the Uncompress view, available only in the SQL Server BizWare database.
Preparing the SQL Server Uncompress view

Before using the SQL Server Uncompress view, you must make permission changes in the SQLServer Master database. You must grant EXECUTE permissions for the public user for the following stored procedures, found in the Extended Stored Procedures folder of the Master database in the SQL Server Enterprise Manager: sp_OACreate sp_OADestroy sp_OAGetErrorInfo sp_OAMethod sp_OAStop
127
To grant the EXECUTE permission to a stored procedure, perform the following steps: 1. Locate the stored procedure in the Extended Stored Procedures list of the SQL Server Master database. 2. Right-click the item and select Properties from the shortcut menu. The Extended Stored Procedure Properties dialog is displayed. 3. Click the Permissions button to display the Object Properties dialog. 4. Select the check box in the public row and the EXEC column. 5. Press OK to return to the Extended Stored Procedure Properties dialog. 6. Press OK to return to the extended stored procedure list.
Querying the SQL Server Uncompress view

To query the data from the Uncompress view, use the following stored procedures in the SQL Server Query Analyzer: spSetUncompressTimeRange start date/time, end date/time. Use this stored procedure to specify the time range for which data will be returned. spSetUncompressReportingTag reporting tag name. Use this stored procedure to specify a single reporting tag for which data will be returned.
Note: You may further refine your query of the data from the Uncompress view by following the SetUncompress statements with a SELECT statement containing a WHERE clause.
The time range and/or reporting tag name that you specify in these stored procedures are stored in the UncompressReportingTags and UncompressTimeRange working tables. To clear the values from these working tables for the current Query Analyzer session, use the following stored procedures: spClearUncompressTimeRange. Use this stored procedure to clear the time range from the working table that is created by the spSetUncompressTimeRange stored procedure. spClearUncompressReportingTag. Use this stored procedure to clear the reporting tag name from the working table that is created by the spSetUncompressReportingTag stored procedure. For example, spSetUncompressTimeRange '01-28-2003 18:00:00', '01-28-2003 18:07:00' go
128
C DATA COMPRESSION
spSetUncompressReportingTag 'Injection Molding Pressure Compression' go select * from Uncompress where tTimestamp >= '01-28-2003 18:00:00' and tTimestamp <= '01-28-2003 18:03:00' go spClearUncompressTimeRange go spClearUncompressReportingTag go
Data compression considerations

Remember that the Time-series Data Compression Enterprise Connector accumulates data point samples until the number of samples equals the configured block size. At that point, a record is inserted into the database. If you have recently started your FactoryTalk Transaction Manager configuration and attempt to chart compressed data using the RSBizWare time-series report object, there may not yet be any data in the database for the report object to chart as its default time range is set to the last 2 hours. You may need to wait until at least one compressed block of data has been written to the database before your data will be displayed. The Data Compression service is simple and robust; therefore, logging problems will more than likely be due to external factors such as network problems or a database becoming unavailable. If the data cannot reach the database server, the Data Compression service caches its data to the local hard disk until the database is available. When the database becomes available again, the data is automatically sent to the database and the cache files are purged. If you view the Windows Task Manager or Service Control Panel, you may notice the Data Compression service running even though your FactoryTalk Transaction Manager configuration is stopped. Do not manually shut down any compression services. If these services are shut down manually, the data may not be written to the database until the configuration is started again.
129
130
Index
A
activations 23 FactoryTalk 23 FactoryTalk Activation with no Internet access 25 Add/Remove Programs utility 30 administration console 3 administrator 1 application privileges 93 audience 1 author license 79, 82
D
data compression 125 data point 100 database administrator 1 database connection loss 68 database server requirements 13 database upgrade 54 database user 40, 50 default security 63 defining a connector 105 defining a FactoryTalk Transaction Manager configuration 100 DEP 15 diagnostics reporting message types 113 output types 113 distributed issues 14
C
checklist, installation ix client install 22, 29 client license FactoryTalk Historian Classic 79 FactoryTalk Metrics 82 FactoryTalk Scheduler 78 complete install 21, 29 compression ratio 127 compression, data 125 Configuration Console 5 configuration, FactoryTalk Transaction Manager 100 register 106 unregister 109 configuring a server 58, 61 connector 105 control 101 enterprise 101 consulting services 8 contact us 8 control connector 101 copy protection 23 creating a database user 40, 50 a SQL Server database 37, 48 an ODBC system DSN 52 custom install 22, 29
E
enterprise connector 101 Excel Add-in, registering 117 external data source 62
F
FactoryTalk Activation 23 installed on Activation Server 25 installed on Security Services Manager FactoryTalk Administration Console 3 FactoryTalk Historian Classic installation 21, 28 licenses 78, 79 privileges 93 FactoryTalk Historian for Batch 81 FactoryTalk Metrics installation 21, 28 privileges 93 FactoryTalk Scheduler Client 5 installation 21, 28 Server 5 24
131
FactoryTalk Security Import 85 FactoryTalk Transaction Manager configuration 100 register 106 unregister 109 Configuration Server 5, 99 transaction 100 Transaction Manager 100 troubleshooting 112 firewall 117 flexible fields 67
O
object permissions 65 ODBC system DSN 52 online help 6 on-site support 8 Oracle 120 output types 113
P
permissions default 63 object-level 65 phone support 7 privileges, application
H
hardware requirements help 6 9
93
I
Information Services Manager 4 installation 21, 28 installation checklist ix installing SQL Server 34, 42, 43, 44
Q
QuickWeb Windows-linked users 12, 89
R
registering a Configuration Server 99 a FactoryTalk Transaction Manager configuration 106 a server 57 release notes 6 remote connection 117 remove installation 30 Report Schedule Manager 4 RSBizWare administrator 1 architecture 2 FactoryTalk Security Import 85 runtime license 79, 82
L
license 84 license activations 84 licenses FactoryTalk Historian Classic 78 FactoryTalk Historian for Batch 81 FactoryTalk Metrics 81 FactoryTalk Scheduler 78 log file configuration 114 loss of database connection 68
M
message types 113 Metrics Server Manager Move Activation - 32 Bit 6 23
S
sample data 61 scheduled items 61 security default 63 Security Import 85 Security Services Manager server registration 57
N
Net Configuration connection Net8 connection 121 network administrator 1 121
4, 55
132
INDEX
starting and stopping 61 server configuration 58, 61 server license 84 FactoryTalk Historian Classic 78 FactoryTalk Historian Classic for Batch 81 FactoryTalk Metrics 81 Service Console 4 service pack, SQL Server 37, 48 software installation 21, 28 software requirements 11 SQL Server 34, 42, 43, 44 service pack 37, 48 starting a configuration 111 a server 61 stopping a configuration 111 a server 61 summarization fields 67 support on-site support 8 phone support 7 web support 8 system troubleshooting 116
T
technical support 7, 8 training 7 transaction 100 Transaction Manager 100 troubleshooting 112, 116 message types 113 output types 113
U
uninstall 30 unregistering a FactoryTalk Transaction Manager configuration 109 upgrading a database 54 user administration 85 user group administration 85 Users Guide 6 user-defined summarization fields 67
W
web support 8 web-based client 5 Windows and DEP 15 Windows-linked user groups and users Windows-linked users and QuickWeb
85 12, 89
133
134

Bzware In001 - en P

Transféré par

Informations du document

Description originale:

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Bzware In001 - en P

Transféré par

Droits d'auteur :

Formats disponibles

INTEGRATED PRODUCTION & PERFORMANCE SUITE

RSBIZWARE ADMINISTRATORS GUIDE

Contact Rockwell Copyright Notice

RSBIZWARE ADMINISTRATORS GUIDE

3 Installing or Upgrading the RSBizWare Software

4 Installing and Creating a SQL Server Database

5 Administering a Security Services Manager

Registering a Security Services Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

6 Administering RSBizWare Servers

7 Controlling Access to Your RSBizWare System

RSBIZWARE ADMINISTRATORS GUIDE

8 Configuring Data Collection

RSBIZWARE ADMINISTRATORS GUIDE

RSBizWare 9.0 Installation Checklist

RSBIZWARE ADMINISTRATORS GUIDE

FactoryTalk Historian Classic for Batch Configuration

Database administrator/Network administrator

RSBIZWARE ADMINISTRATORS GUIDE

The RSBizWare architecture

FactoryTalk Administration Console

RSBIZWARE ADMINISTRATORS GUIDE

Security Services Manager

RSBizWare databases (SQL Server or Oracle)

Information Services Manager

Report Schedule Manager

FactoryTalk Transaction Manager Configuration Server

FactoryTalk Transaction Manager

RSBIZWARE ADMINISTRATORS GUIDE

Metrics Server Manager

Where can I go for help?

Reference the release notes

Reference the Users Guides

Reference the online help

Get RSBizWare training

Get phone support

RSBIZWARE ADMINISTRATORS GUIDE

Get Web support

Get on-site support

Get consulting services

RSBIZWARE ADMINISTRATORS GUIDE

RSBIZWARE ADMINISTRATORS GUIDE

Database server requirements/recommendations

RSBIZWARE ADMINISTRATORS GUIDE

ODBC Driver Manager 3.510 or higher TCP/IP network connectivity

Running RSBizWare in a distributed environment

RSBizWare Product Dependencies

A note about Windows DEP

RSBIZWARE ADMINISTRATORS GUIDE

DEP settings Setting OptIn Description Supported by Rockwell Software Products?

Changing DEP settings

Hardware DEP Settings

RSBIZWARE ADMINISTRATORS GUIDE

Installing or Upgrading the RSBizWare Software

RSBIZWARE ADMINISTRATORS GUIDE

Installing new RSBizWare software

Installing the FactoryTalk Services Platform

3 INSTALLING OR UPGRADING THE RSBIZWARE SOFTWARE

Installing FactoryTalk Historian Classic, Metrics, and Scheduler

RSBIZWARE ADMINISTRATORS GUIDE

3 INSTALLING OR UPGRADING THE RSBIZWARE SOFTWARE

Installing RSBizWare FactoryTalk Activations

Using FactoryTalk Activation