RSBizWare Administration Guide - Rockwell Automation...Microsoft, SQL Server, Windows, Windows...

ADMINISTRATION GUIDE

Rockwell Automation Publication BZWARE-IN001N-EN-P-August 2017

Supersedes Publication BZWARE-IN001M-EN-P-June 2014

2 Rockwell Automation Publication BZWARE-IN001N-EN-P-August 2017

Preface

© 2017 Rockwell Automation, Inc. All rights reserved. Printed in USA. This document and any accompanying Rockwell Software products are copyrighted by Rockwell Automation, Inc. Any reproduction and/or distribution without prior written consent from Rockwell Automation, Inc. is strictly prohibited. Please refer to the license agreement for details.

You can view the Rockwell Automation End-User License Agreement ("EULA") by opening the License.rtf file located in your product's installation folder on your hard drive.

The third-party licenses are available in the Third-party Licenses folder on your hard drive.

FactoryTalk, FactoryTalk Activation, FactoryTalk Activation Manager, FactoryTalk Administration Console, FactoryTalk Diagnostics, FactoryTalk Directory, FactoryTalk Metrics, FactoryTalk Transaction Manager, Report Expert, RSBizWare, Rockwell, Rockwell Automation, Rockwell Software, RSLinx Classic, and RSLinx Enterprise are trademarks of Rockwell Automation, Inc. Any Rockwell Automation software or hardware not mentioned here is also a trademark, registered or otherwise, of Rockwell Automation, Inc.

Microsoft, SQL Server, Windows, Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2, Windows Server 2008, Windows 10, Windows 8.1, and Windows 7 are either registered trademarks or trademarks of Microsoft Corporation in the United States and other countries. Adobe, Acrobat, and Reader are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and other countries.

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

Rockwell Automation maintains current product environmental information on its website at http://www.rockwellautomation.com/rockwellautomation/about-us/sustainability-ethics/product-environmental-compliance.page.

Customer Support Telephone — 1.440.646.3434 Online Support — http://www.rockwellautomation.com/support/

Copyright notice

End User License Agreement (EULA)

Other licenses

Trademark notices

Other trademarks

Warranty

Environmental compliance

Contact Rockwell

Rockwell Automation Publication BZWARE-IN001N-EN-P-August 2017 3

Table of Contents

Chapter 1

Intended audience ....................................................................................... 11 The RSBizWare architecture .................................................................... 12

FactoryTalk Administration Console ............................................... 14 Service Console ....................................................................................... 15 Security Services Manager .................................................................... 15 RSBizWare databases (SQL Server or Oracle) ............................... 15 Information Services Manager ............................................................ 16 Report Schedule Manager .................................................................... 16 Configuration Console ......................................................................... 16 Web-based client .................................................................................... 16 FactoryTalk Transaction Manager Configuration Server ........... 17 FactoryTalk Transaction Manager .................................................... 17 Metrics Server Manager ........................................................................ 17

Where can I go for help? ............................................................................ 18

Chapter 2 Hardware and software requirements .................................................... 19 Run RSBizWare in a distributed environment .................................... 19 RSBizWare product dependencies .......................................................... 19

Chapter 3

Clean installation: supported installation scenarios ........................... 22 Information for users of SQL Server 2014 ...................................... 23 Installation and configuration checklist ........................................... 24 Step 1: Install Internet Information Services (IIS) ........................ 26 Step 2: Install SQL Server 2012 Service Pack 1 .............................. 32

Verify the configuration of SQL Server....................................... 39 Step 3: Install FactoryTalk Services ................................................... 42 Step 4: Configure FactoryTalk Activation ...................................... 47 Step 5: Create an RSBizWare SQL Server database ...................... 48 Step 6: Create an RSBizWare SQL Server database user ............. 49 Step 7: Install SQL Server 2012 Native Client ............................... 53 Step 8: Configure the ODBC data source ....................................... 54

Repair the connection to SQL Server .......................................... 59

Welcome to RSBizWare

RSBizWare prerequisites

Install RSBizWare

Table of Contents


Step 9: Verify if the local computer is added to the FactoryTalk Administration Console ....................................................................... 61 Step 10: Configure FactoryTalk groups and users ......................... 62

Configure Windows-linked FactoryTalk users ......................... 62 Configure FactoryTalk users ......................................................... 66

Step 11: Install RSBizWare ................................................................. 68 Step 12: Register the Security Services Manager............................. 70 Step 13: Register the Information Services Manager..................... 71 Step 14: Associate Metrics Server Manager with Information Services Manager .................................................................................... 75

Configure user-defined summarization fields (flex-fields) ..... 78 Step 15: Assign activations to RSBizWare servers ......................... 81 Step 16: Assign client activations to users ........................................ 83 Step 17: Assign application privileges to users ................................ 84

FactoryTalk Historian and FactoryTalk Metrics privileges ... 86 Step 18: Register FactoryTalk Transaction Manager .................... 87 Step 19: Define FactoryTalk Transaction Manager configurations ......................................................................................... 89 Step 20: Register FactoryTalk Transaction Manager configurations ......................................................................................... 93 Step 21: Configure SQL Server Reporting Services (SSRS) ........ 97 Step 22: Verify the SSRS configuration ......................................... 100 Step 23: Install and configure Report Expert ............................... 102 Step 24: Configure the FTMetricsEditors group ........................ 105 Step 25: Verify the Report Expert installation ............................. 106 Congratulations! ................................................................................. 107

Remove RSBizWare................................................................................. 108

Chapter 4

Migration: supported migration scenarios ......................................... 109 Migration checklist ............................................................................. 112 Step 1: Back up your FactoryTalk Transaction Manager configuration ........................................................................................ 115 Step 2: Back up your RSBizWare SQL Server database ............. 118 Step 3: Keep your database users for reference ............................. 121

Migrate RSBizWare

Table of Contents


Step 4: Keep your ODBC data source configuration for reference 123 Step 5: Keep your FactoryTalk Administration Console configuration for reference ............................................................... 124 Step 6: Install Internet Information Services (IIS) ..................... 125 Step 7: Install SQL Server 2012 Service Pack 1 ........................... 132 Step 8: Install FactoryTalk Services ................................................ 138 Step 9: Configure FactoryTalk Activation ................................... 143 Step 10: Restore your RSBizWare SQL Server database ........... 144 Step 11: Recreate your RSBizWare SQL Server database user . 147 Step 12: Install SQL Server 2012 Native Client.......................... 151 Step 13: Recreate the ODBC data source ..................................... 152

Repair the connection to SQL Server ....................................... 156 Step 14: Verify if the local computer is added to the FactoryTalk Administration Console .................................................................... 158 Step 15: Recreate your applications ................................................ 159 Step 16: Add a local Administrator account as a Windows-linked user 160 Step 17: Recreate your users ............................................................. 164 Step 18: Install RSBizWare .............................................................. 167 Step 19: Register the Security Services Manager.......................... 168 Step 20: Register the Information Services Manager.................. 169 Step 21: Associate Metrics Server Manager with Information Services Manager ................................................................................. 173 Step 22: Assign activations to RSBizWare servers ...................... 174 Step 23: Assign client activations to users ..................................... 177 Step 25: Restore your FactoryTalk Transaction Manager configuration ........................................................................................ 178 Step 24: Assign application privileges to users ............................. 180

FactoryTalk Historian and FactoryTalk Metrics privileges 182 Step 26: Register the configuration in the RSBizWare SQL Server database ..................................................................................... 183 Step 27: Update your FactoryTalk Transaction Manager configuration ........................................................................................ 184 Step 28: Register FactoryTalk Transaction Manager ................. 188 Step 29: Register the configuration in the Service Console ...... 189

Table of Contents


Step 30: Configure SQL Server Reporting Services (SSRS) ..... 192 Step 31: Verify the SSRS configuration ......................................... 195 Step 32: Install and configure Report Expert ............................... 197 Step 33: Configure the FTMetricsEditors group ........................ 201 Step 34: Verify the Report Expert installation ............................. 202 Step 35: Start your FactoryTalk Transaction Manager configuration ........................................................................................ 203 Congratulations! ................................................................................. 205

Chapter 5

Configure your SQL Server Data Tools (SSDT) to work with Report Expert custom reports ............................................................... 207 Configure Internet Explorer trusted sites........................................... 208 Install RSBizWare sample data ............................................................. 209

Chapter 6

Prepare for the upgrade ........................................................................... 212 Upgrade FactoryTalk Services Platform ............................................. 213 Upgrade the RSBizWare suite ............................................................... 214

Chapter 7

Start and stop RSBizWare servers ........................................................ 215 Manage Information Services Manager scheduled items ................ 216 Manage Information Services Manager external data sources ....... 216 Handle temporary database connection loss in the Information Services Manager ...................................................................................... 218 The Metrics Server Manager settings file ............................................ 220

Chapter 8

Software activation options ................................................................... 226 Server activations for FactoryTalk Metrics ................................... 227 Server activations for FactoryTalk Historian Classic ................. 227 Client activations for FactoryTalk Metrics .................................. 228 Client activations for FactoryTalk Historian Classic ................ 230 Example: FactoryTalk Metrics activation ..................................... 231 Example: FactoryTalk Historian Classic activation ................... 233 FactoryTalk Historian for Batch activation options .................. 234

Post-installation tasks

Upgrade RSBizWare on Microsoft Windows Server 2008 R2 SP1

Administer RSBizWare servers

Controll access to your RSBizWare system

Table of Contents


Manage FactoryTalk user groups and users........................................ 235 Configure FactoryTalk user groups ................................................ 235 Configure Windows-linked user groups ....................................... 237 Update the Service Console with users and groups changes ..... 239

Chapter 9 Assign application privileges to groups .......................................... 241 Assign object permissions to users and groups ............................. 242

Configure default object permissions ....................................... 242 Configure custom object permissions ....................................... 246

Chapter 10 Types of control connectors for the data collection ......................... 247 Types of enterprise connectors for the data collection .................... 248 Unregister FactoryTalk Transaction Manager configurations ..... 249 Start and stop FactoryTalk Transaction Manager configurations 252 Troubleshoot ............................................................................................. 253

Chapter 11 Types of diagnostic messages ................................................................. 255 Ways of logging diagnostic messages .................................................... 256 Configure server log files......................................................................... 256 View diagnostic logs ................................................................................. 259

Appendix A Remote connection to an RSBizWare server ..................................... 261 Register the Excel Add-in ....................................................................... 262

Appendix B Maintain frequently used RSBizWare tables and indexes .............. 265 Use Oracle with RSBizWare ................................................................. 266

Recommended database settings ..................................................... 267 Create tablespaces .......................................................................... 267 Configure the database user ........................................................ 267 Create a Net Configuration connection .................................. 268 Configure the Oracle ODBC data source ............................... 269

Tune the Oracle database for FactoryTalk Historian Classic .. 269

Manage user access

Configure data collection

Report diagnostic messages

Advanced topics

Database tips

Table of Contents


Improve the performance of your RSBizWare Oracle database 270 Prepare to run the Oracle database ............................................ 271

Appendix C Benefits of using the data compression ............................................... 273 How the data compression works ........................................................ 274 Compression ratio .................................................................................... 275 View compressed data ............................................................................. 276

Prepare the SQL Server uncompress view ..................................... 276 Query the SQL Server uncompress view ....................................... 277

Data compression considerations ......................................................... 278

Appendix D

Set the real-time clock in a ControlLogix processor using FactoryTalk Transaction Manager ...................................................... 282

In the processor ................................................................................... 283 In the database ..................................................................................... 283 In FactoryTalk Transaction Manager ............................................ 285

Send date/time information from a ControlLogix processor to a database ....................................................................................................... 285

In RSLogix 5000.................................................................................. 285 In FactoryTalk Transaction Manager ............................................ 286

Special considerations for a distributed Microsoft COM+ application .................................................................................................. 287 Enable network COM+ access for COM+ connectors in FactoryTalk Transaction Manager ...................................................... 288 Configure the Oracle 10g Instant Client for FactoryTalk Transaction Manager .............................................................................. 288 Configure FactoryTalk Transaction Manager Connectivity to SQL Server using Windows authentication ................................................ 289

Configure the SQL Server authentication .................................... 289 Configure the Windows-only authentication .............................. 290 Configure FactoryTalk Transaction Manager for connections with SQL Server .................................................................................. 291

Data types supported by SQL Server ................................................... 293

Data compression

Application notes for FactoryTalk Transaction Manager

Table of Contents


Behaviors when setting substitution options for FactoryTalk data points ........................................................................................................... 293 Resolve IP address to host name issues ................................................ 294 Remove a Configuration Server computer from FactoryTalk Transaction Manager .............................................................................. 295 Start and stop FactoryTalk Transaction Manager services manually 296 Considerations for distributed configurations .................................. 297 Considerations for copying and pasting FactoryTalk data points 298 Windows Event Viewer tips .................................................................. 300 Run RSLinx Classic as a service ............................................................. 301 Data block support ................................................................................... 301

Send data blocks from FactoryTalk Transaction Manager to a stored procedure .................................................................................. 302 Send data blocks from multiple rows in a table using Integer data 303 Send data blocks from one row in a table using Integer data .... 305

Sybase values .............................................................................................. 307 Int64 Signed/Unsigned in the Expression Editor ............................ 307 Int64 Signed/Unsigned as an output parameter in a stored procedure .................................................................................................... 308 Substitute values for a data point .......................................................... 308 Verify BigInt data types after FactoryTalk Transaction Manager update .......................................................................................................... 308 Restore default dialog box sizes ............................................................. 309 Miscellaneous ............................................................................................ 309

Table of Contents



Chapter 1

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.

This document 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 / network administrators

Create and maintain system databases and network resources, including logon accounts.

They should be familiar with:

Intended audience

Chapter 1 Welcome to RSBizWare


• Microsoft Windows operating systems.

• User accounts and security in the enterprise.

• Microsoft SQL Server or Oracle Enterprise Manager.

• Open Database Connectivity (ODBC).

• RSBizWare administrators

Install and configure the RSBizWare system so that it is ready for use for the end users.

They should be familiar with:

• Microsoft Windows operating systems.

• User accounts and security in the RSBizWare system.

• Open Database Connectivity (ODBC).

• Control system architecture, plant model (physical layout), and data model.

• If connecting to external databases, the RSBizWare administrators should be also familiar with the location and structure (schema) of those databases.

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.

The RSBizWare architecture

Welcome to RSBizWare Chapter 1


To understand this relationship, you need to understand the RSBizWare software architecture as shown in the following diagrams.



The FactoryTalk Administration Console is a stand-alone tool that allows you to configure and manage 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.

FactoryTalk Administration Console



• View system-wide diagnostic messages.

• Create and configure system groups and users.

The Service Console is the center of the RSBizWare architecture. 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.

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 the Security Services Manager as part of the initial configuration process. There is generally a single Security Services Manager running in an enterprise.

The FactoryTalk Historian Classic and FactoryTalk Metrics 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:

• A Microsoft SQL Server database.

Service Console

Security Services Manager

RSBizWare databases (SQL Server or Oracle)



If you plan to use a Microsoft SQL Server database, SQL Server 2008 R2 and any required service packs can be installed from the DVD included with the software.

• An Oracle database.

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.

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.

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.

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 for Batch add-on functionality.

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

Information Services Manager

Report Schedule Manager

Configuration Console

Web-based client



Manager hosts a special Web page, the Quick Web Home Page, to give users view-only access to RSBizWare reports stored on the 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 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.

The Metrics Server Manager—also referred to as the FactoryTalk Metrics Enterprise Connection—is 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 performs the following functions:

• Manages all timers, counters, and formulas defined in the FactoryTalk Metrics application.

• Summarizes raw control system data.

FactoryTalk Transaction Manager Configuration Server

FactoryTalk Transaction Manager

Metrics Server Manager



• Creates FactoryTalk Metrics Workcell History records in the RSBizWare database.

• Creates FactoryTalk Metrics Event History records in the RSBizWare database.

Consult the following resources for additional information about the product:

• Release notes

The release notes contain current information about the product, including hardware and software requirements, new features, known and fixed anomalies.

• User guides

The product user guides will help you understand how to use the RSBizWare products.

• Online help

The online help provides general information and step-by-step procedures for working with the product.

• Rockwell Automation Support Center

The support center provides a variety of services, such as trainings, webinars, and online support that will improve your experience using the RSBizWare suite.

Where can I go for help?


Chapter 2

RSBizWare prerequisites

In this chapter you will learn about the following:

• Hardware and software requirements 19

• Run RSBizWare in a distributed environment 19

• RSBizWare product dependencies 19

For up-to-date information on hardware and software requirements of the RSBizWare suite, refer to the RSBizWare Release Notes, available on the RSBizWare installation DVD.

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 the RSBizWare server (page 261)".

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 FactoryTalk-enabled 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.

Hardware and software requirements

Run RSBizWare in a distributed environment

RSBizWare product dependencies

Chapter 2 RSBizWare prerequisites


The following RSBizWare products are dependent on the FactoryTalk Services Platform:

• FactoryTalk Historian Classic

• FactoryTalk Metrics

The following RSBizWare products depend on the RSBizWare Platform features:



• FactoryTalk Historian for Batch

• FactoryTalk Web Services (FTWS)

• FactoryTalk Transaction Manager Datapoint Migration Tool

The following RSBizWare products are dependent on FactoryTalk Transaction Manager:




Chapter 3

Install RSBizWare

In this chapter you will learn how to perform a clean installation and then configure the RSBizWare software on your computer.

The RSBizWare suite consists of the following components:



• FactoryTalk Transaction Manager

The installation can be performed on:

• Microsoft Windows Server 2012

• Microsoft SQL Server 2012 Service Pack 1

You should avoid running the RSBizWare installation from a network DVD image. 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 installation DVD on a remote network drive, it is recommended that you first copy the installation directories from the DVD to a temporary location on your computer’s hard drive and run the installation from the hard drive. You can delete the temporary copy of the DVD image from the hard drive after the installation is complete.

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

Chapter 3 Install RSBizWare


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 the support identify the cause of your installation problem.

To perform a clean installation of RSBizWare and Report Expert, choose either of the following scenarios:

All-in-one installation

Clean installation: supported installation scenarios

Install RSBizWare Chapter 3


Installation on two computers

If you intend to create custom reports for Report Expert, a part of the RSBizWare suite, be aware that this version of SQL Server does not include SQL Server Data Tools (SSDT) that are required to create the custom reports.

This document describes installation steps for SQL Server 2012. You may follow the steps for installing SQL Server 2014 with one exception: you will need to install SSDT separately and configure them to work with Report Expert.

To use the custom reports functionality of Report Expert with SQL Server 2014:

1. Install a version of SSDT of your choice.

The installation steps are not covered in this document.

For details, see the SSDT documentation.

2. Configure your version of SSDT to work with Report Expert.

Information for users of SQL Server 2014



For details, see "Configure your SQL Server Data Tools (SSDT) to work with Report Expert custom reports (page 207)".

In order to successfully install and configure your RSBizWare and Report Expert software, follow the steps in the order presented below.

Configuring SQL Server

Step 1: Install Internet Information Services (IIS) (page 26)

Step 2: Install (page 32) or verify the configuration of Microsoft SQL Server 2012 Service Pack 1 (page 39)

Setting up your FactoryTalk environment

Step 3: Install FactoryTalk Services (page 42)

Step 4: Configure FactoryTalk Activation (page 47, page 143)

Setting up your RSBizWare SQL Server environment

Step 5: Create an RSBizWare SQL Server database (page 48)

Step 6: Create an RSBizWare SQL Server database user (page 49)

Step 7: Install SQL Server 2012 Native Client (page 53)

Step 8: Configure the ODBC data source (page 54)

Configuring FactoryTalk Administration Console

Step 9: Verify if the local computer is added to the FactoryTalk Administration Console (page 61)

Step 10: Configure FactoryTalk groups and users (page 62)

Installation and configuration checklist



Installing RSBizWare

Step 11: Install RSBizWare (page 68)

Configuring RSBizWare servers

Step 12: Register the Security Services Manager (page 70)

Step 13: Register the Information Services Manager (page 71)

Step 14: Associate Metrics Server Manager with Information Services Manager (page 75)

Configuring security for RSBizWare

Step 15: Assign activations to RSBizWare servers (page 81)

Step 16: Assign client activations to users (page 83)

Step 17: Assign application privileges to users (page 84)

Configuring data collection

Step 18: Register FactoryTalk Transaction Manager (page 87)

Step 19: Define FactoryTalk Transaction Manager configurations (page 89)

Step 20: Register FactoryTalk Transaction Manager configurations (page 93)

Installing and configuring Report Expert

Step 21: Configure SQL Server Reporting Services (SSRS) (page 97)

Step 22: Verify the SSRS configuration (page 100)

Step 23: Install and configure Report Expert (page 102)



Step 24: Configure the FTMetricsEditors group (page 105)

Step 25: Verify the Report Expert installation (page 106)

TIP • Internet Information Services (IIS) are required by Report Expert. • If you have chosen the installation on two computers, perform the

following steps on the Database server computer.

To install Internet Information Services (IIS):

1. On the Start screen, click Server Manager.

The Server Manager window appears.

2. Under Configure this local server, click Add roles and features.

The Add Roles and Features Wizard appears.

3. Click Next.

The Select installation type page appears.

4. Click Role-based or feature-based installation.

5. Click Next.

The Select destination server page appears.

6. Click Select a server from the server pool.

7. Under Server Pool, select the local server computer (i.e., the computer on which you are performing these steps).

8. Click Next.

Step 1: Install Internet Information Services (IIS)



The Select server roles page appears.

9. Click Web Server (IIS).

The Add Roles and Features Wizard dialog box appears.

10. Click Add Features.

11. Click Next.

The Select features page appears.

12. Select the following features:

Feature group Individual features .NET Framework 3.5 Features • .NET Framework 3.5 (Includes .NET 2.0 and 3.0)

.NET Framework 4.5 Features • .NET Framework 4.5 • ASP.NET 4.5 • WCF Services • HTTP Activation





14. Click Next.

The Web Server Role (IIS) page appears.

15. Click Next.

The Select role services page appears.



16. Select the following role services:

Role group Services Web Server • Common HTTP Features

• Default Document • Directory Browsing • HTTP Errors • Static Content • Security • Request Filtering • Windows Authentication • Application Development • .NET Extensibility 4.5 • ASP.NET 4.5 • ISAPI Extensions • ISAPI Filters

Management Tools • IIS Management Console • IIS 6 Management Compatibility • IIS 6 Metabase Compatibility

If a dialog box appears listing additional features required, click Add Features.

17. Click Next.

The Confirm installation selections page appears.

18. Review the list of the features that will be installed.



19. Select the Restart the destination server automatically if

required option.


20. Click Yes to confirm selecting the option.



21. Click Install.

The features that you have selected are being installed to your server.

22. Once the installation is complete, click Close.

23. Open your web browser, and type http://localhost.

The IIS 8.0 logo displayed in the window of the web browser confirms that the installation has been successful.



TIPS • If you have chosen the installation on two computers, perform the following steps on the Database server computer.

• It is recommended that you create a Windows user account or a Windows Domain user account on the computer on which you are installing SQL Server. You will use this account to install and configure SQL Server. For details, refer to the Microsoft Windows user documentation.

• If you already have an SQL Server installed, check (page 39) if its configuration meets the configuration requirements of RSBizWare.

The FactoryTalk Historian Classic and FactoryTalk Metrics require a single database for permanent storage. Although the applications share the same database, each of them uses unique tables to support its core functions. The database is referred to as the RSBizWare database. It can be either a Microsoft SQL Server database or an Oracle database.

If you plan to use Microsoft SQL Server, follow the steps presented in these sections.

If you plan to use Oracle, see "Using Oracle with RSBizWare (page 266)".

To install SQL Server:

1. Run the SQL Server 2012 Service Pack 1 installation media.

The SQL Server Installation Center wizard appears.

2. Click Installation, and then click New SQL Server stand-alone installation or add features to an existing installation.

Step 2: Install SQL Server 2012 Service Pack 1



The Setup Support Rules page appears.

3. Click OK.

The Product Key page appears.

The product key is already provided on the page.

4. Leave the default settings, and then click Next.

The License Terms page appears.

5. Read the license terms, click I accept the license terms, and then click Next.

The Product Updates page appears.


The SQL Server setup files are installed.




7. Click Next.

The Setup Role page appears.

8. Click SQL Server Feature Installation, and then click Next.

The Feature Selection page appears.




NOTE If you intend to use SQL Server 2014 with RSBizWare, you won't see the SQL Server Data Tools (SDT) option, because SSDT are not available as a part of the SQL Server 2014 installation steps. To use SSDT, install your preferred SSDT version first (for details, refer to the SSDT documentation), and then configure your SSDT to work with RSBizWare. For details, see Configure your SQL Server Data Tools (SSDT) to work with Report Expert custom reports (page 207).

10. Click Next.

The Installation Rules page appears.

11. Click Next.

The Instance Configuration page appears.




The Disk Space Requirements page appears.

13. Click Next.

The Server Configuration page appears.

14. On the Service Accounts tab, define accounts for each SQL Server service.

15. Click the Collation tab, and then click Customize.

The Customize the SQL Server 2012 Database Engine Collation dialog box appears.



16. Click SQL collation, used for backwards compatibility.

17. In the list, select SQL_Latin1_General_CP1_CI_AS.

18. Click OK, and then click Next.

The Database Engine Configuration page appears.

19. Select Mixed Mode... as the authentication method.

20. Under Mixed Mode..., type the password for the SQL Server

System Administrator account (sa).

IMPORTANT Make sure that you do not lose or forget the password for the sa account. You will need to provide this password when you will be configuring the SQL Server Reporting Services (SSRS).

21. Under Specify SQL Server administrators, add at least one user as the SQL Server administrator.



22. Click Next.

The Reporting Services Configuration appears.

23. Click Next.

The Error Reporting page appears.

24. Click Next.

The Installation Configuration Rules page appears.

25. Click Next.

The Ready to Install page appears.



26. Click Install.

The Installation Progress page appears.

SQL Server 2012 is being installed.

27. Once your SQL server is installed successfully, close the SQL Server Installation Center wizard.

TIPS • If you have chosen the installation on two computers, perform the following steps on the Database server computer.

• If you already have an SQL Server installed, use the following steps to adjust its configuration to the requirements of the RSBizWare suite.

To verify the configuration of your SQL Server:

1. On the Start screen, type any part of the name SQL Server Installation Center (64-bit), and then click its shortcut.




3. Click OK.


Verify the configuration of SQL Server






5. Click Next.

The Installation Type page appears.

6. Click Add features to an existing instance of SQL Server 2012.

7. In the list, select the SQL Server 2012 instance that you will use with RSBizWare.



Click Next.


8. Make sure that your SQL Server configuration contains the following features:

9. Do either of the following:



• If your configuration contains all the features listed above, click Cancel, and then quit the SQL Server setup.

• If your configuration misses any features listed above:

1. Add the features.

2. Continue with step 10 in "Step 2: Install SQL Server 2012 Service Pack 1 (page 32)", and finish the configuration of your SQL Server.

When you select this option, the following components will be installed:

• FactoryTalk Services Platform with FactoryTalk Directory

FactoryTalk Services Platform is an underlying architecture and a set of common services (such as diagnostic messages, health monitoring services, access to real-time data, and shared plant resources such as tags and graphic displays) that Rockwell Automation products build upon. It is a prerequisite for all FactoryTalk-enabled software products.

• FactoryTalk Activation Manager

FactoryTalk Activation Manager allows you to download activation files using an Internet connection, and transfer the activation files to a computer that does not have an Internet connection. Install this software on the same computer as the FactoryTalk Directory server.

• RSLinx Enterprise

RSLinx Enterprise is a FactoryTalk Live Data server and a device-based alarm and event server. RSLinx Enterprise links Allen-Bradley networks and devices to Microsoft Windows products such as the FactoryTalk View SE (HMI software) and the RSLogix family of device programming software.

• FactoryTalk Alarms and Events (optional)

Step 3: Install FactoryTalk Services



FactoryTalk Alarms and Events provide a common, consistent view of alarms and events throughout a FactoryTalk system.

For more information on FactoryTalk, refer to FactoryTalk Help.

NOTE Make sure to install FactoryTalk Services on all computers, including the computer that will serve as the FactoryTalk Directory.

To install FactoryTalk Services:

1. Run the RSBizWare installation media.

The RSBizWare installation wizard appears.

2. Click FactoryTalk Metrics > Installation > Install FTServices.

The installation wizard appears.

3. Follow the steps as presented in the screenshots below.



4.



5.



6.

TIP • You may omit restarting the computer after the FactoryTalk Services installation is complete.

• For details on configuring the FactoryTalk Services, see FactoryTalk Help.

•

TIP If you have chosen the installation on two computers, perform the following steps on the RSBizWare server computer.

You need to activate your RSBizWare suite so that you can use its features.

You activate RSBizWare by obtaining license activation file(s) from the Rockwell Automation licensing website and assigning them to the RSBizWare suite using the FactoryTalk Activation Manager.

Step 4: Configure FactoryTalk Activation



To configure FactoryTalk Activation:

1. On the Start screen, type any part of the name FactoryTalk Activation Manager, and then click its shortcut.

The FactoryTalk Activation Manager window appears.

2. Follow the instructions displayed in the window to configure your activations.

TIP Click Help for more information, or refer to the instructions from the Activate Rockwell Software Products leaflet, available with your product installation package.

See also • Software activation options 226

TIP If you have chosen the installation on two computers, perform the following steps on the Database server computer.

FactoryTalk Historian Classic, FactoryTalk Metrics, and Report Expert require a single SQL server database to operate, since they share common tables in the database.

NOTE Perform the following steps using a database user that has privileges to create databases.

To create an SQL server database for the RSBizWare software:

1. On the Start screen, click SQL Server Management Studio.

The Microsoft SQL Server Management Studio window and the Connect to Server dialog box appear.

2. Select the computer that hosts SQL Server.

3. Type the login and password, and then click Connect.

4. In the Object Explorer, right-click Databases and select New Database.

Step 5: Create an RSBizWare SQL Server database



The New Database dialog box appears.

5. In the Database name text box, type a name for the database, for example RSBizWare.

6. Click OK.

The new database is saved and listed under Databases in the Object Explorer.

See also • Database tips 265


In this step you will create a user for your RSBizWare SQL database. The user will take up the role of the database owner. In SQL Server, a database user is called a login.

NOTE Perform the following steps using a database user that has privileges to create database users.

To create the RSBizWare database user:





4. In the Object Explorer, expand the Security folder.

5. Right-click Logins, and then click New Login.

The Login - New dialog box appears.

Step 6: Create an RSBizWare SQL Server database user



6. In the Login name box, type a name for the database user.

In this example we will use RSBizWareUser.

7. Click SQL Server authentication.

8. In the Password box, create a password for the database user.

9. In the Confirm password box, retype the password that you have created.

10. Clear the Enforce password expiration check box.

11. In the Default database list, select the name of your RSBizWare database that you created.



12. In the left pane of the Login - New dialog box, under Select a

page, click User Mapping.

13. Under Users mapped to this login, in the Map column,

check the box next to the name of your RSBizWare database.



14. In the Default Schema column, in the row of your

RSBizWare database, type the name of your database user.

15. Under Database role membership for <DatabaseName>, select the db_owner check box.

16. Click OK.



TIP If you have chosen the installation on two computers, perform the following steps on the RSBizWare server computer. Otherwise, go to "Step 8: Configure the ODBC data source (page 54)".

It is necessary that you install the Microsoft SQL Server 2012 Native Client on the target RSBizWare server computer so that you can use it in the ODBC data source configuration to establish connection with your RSBizWare SQL Server database.

To install the SQL Server 2012 Native Client:

1. Open the Microsoft SQL Server 2012 Feature Pack page (http://www.microsoft.com/en-us/download/details.aspx?id=29065).

2. Expand Install Instructions.

3. Scroll down to Microsoft® SQL Server® 2012 Native Client.

4. Click X64 Package.

5. Download the file.

6. Double-click sqlncli.msi.

The Microsoft SQL Server Native Client Setup wizard appears.

7. Click Next.

Step 7: Install SQL Server 2012 Native Client

http://www.microsoft.com/en-us/download/details.aspx?id=29065




8. On the License Agreement page, click:

9. Click Next.

10. On the Feature Selection page, leave the default settings, and then click Next.

11. On the Ready to Install the Program, click Install.

12. Once the installation is complete, click Finish.

TIP If you have chosen the installation on two computers, perform the following steps on the RSBizWare server computer and the Database server computer.

Before you install Report Expert on your server computer or configure any of the RSBizWare services, you need to correctly configure the Data Source Name (DSN) for Open Database Connectivity (ODBC).

RSBizWare servers access databases using the ODBC functionality. You need to create named connections to the RSBizWare database and any other databases that you want the RSBizWare applications to use.

Since both FactoryTalk Metrics and Report Expert are 32-bit applications, you need to configure the DSN with the ODBC Data Source Administrator for 32-bit applications.

Step 8: Configure the ODBC data source



To configure the data source name (DSN) for ODBC:



2. On the Tools menu, click ODBC Data Source (32-bit).

The ODBC Data Source Administrator (32-bit) dialog box appears.

3. Click the System DSN tab, and then click Add.

The Create New Data Source dialog box appears.

4. In the driver lists, select either of the following, depending on the type of the driver for which you want to set up the data source:

• SQL Server

• SQL Server Native Client 11.0

We recommend that you use the native client driver.

TIP If you select the SQL Server driver, some of the wizard pages may look different than those included in this procedure. However, the steps are identical for both drivers.

5. Click Finish.

The Create a New Data Source to SQL Server dialog box appears.



6. In the Name box, type the name of the data source.

In this example we will use ODBC RSB.

7. (Optional) In the Description box, type the description of the data source.

8. In the Server list, do either of the following:

• If your RSBizWare SQL Server database is on the computer on which you are performing these steps, select (local).

• If your RSBizWare SQL Server database is on the database server computer, select the name of this computer.

TIP See "Create an RSBizWare SQL Server database" for details.

9. Click Next.

10. Specify how SQL Server should verify login IDs:

1. Select the With SQL Server authentication... option.

2. In the Login ID and Password text boxes, type the name and password of the RSBizWare database owner that you created (page 49).

11. Click Next.

12. Click Change the default database to, and then select the database that you created.



13. Click Next.

14. Leave the default settings or modify them according to your needs.

15. Click Finish.

The ODBC Microsoft SQL Server Setup dialog box appears.

16. Verify the new ODBC data source configuration, and then click Test Data Source.



A message box with the test results appears.



TIP If the test does not complete successfully, make sure that you have selected the correct authentication mode for your SQL Server (page 59), and then run the test again.


The RSBizWare configuration requires the mixed mode as the authentication method for the SQL server. Follow the steps below to verify and/or correct the authentication method you have selected for your SQL server.

To check and/or correct the authentication method for the SQL server:



Repair the connection to SQL Server





4. In the Object Explorer, right-click the server name, and then select Properties.

The Server Properties dialog box appears.

5. Under Select a page, click Security.

6. Under Server authentication, check the selected server authentication mode.

If the Windows authentication mode is selected, change it to SQL Server and Windows Authentication mode.

7. Click OK.

The following message appears:

8. Click OK.

9. In the Object Explorer, right-click the server name, and then select Restart.


10. Click Yes.

The server authentication mode will be updated.




By default, the computer on which you have installed FactoryTalk Services Platform is automatically added to the FactoryTalk Administration Console, which is a part of FactoryTalk Services Platform.

The computer should be listed in the Explorer, under System > Computers and Groups > Computers.

If it is not listed there, you should add it manually.

To add your local computer to the FactoryTalk Administration Console:

1. In the FactoryTalk Administration Console, in the Explorer, expand System > Computers and Groups.

2. Right-click Computers, and then click New Computer.

The New Computer dialog box appears.

3. In the Computer text box, type the name of the computer, or click to search for it.

4. Click OK.

The computer is listed under Computers.

Step 9: Verify if the local computer is added to the FactoryTalk Administration Console



In this section you will create FactoryTalk user groups and users. The final infrastructure of groups and users will depend on your specific requirements and may differ from the one presented below.

In the following examples, we will add the local Windows Administrator account to FactoryTalk users. Then, we will create another FactoryTalk user and add it to a user group:

• Configure Windows-linked FactoryTalk users (page 62)

• Configure FactoryTalk users (page 66)

TIP For information on best practices for creating FactoryTalk user groups and users, see the FactoryTalk Security help (FTSecurityEN.chm), section "Best practices". The help file is available in the following location: C:\Program Files (x86)\Common Files\Rockwell\Help.

See also • Manage FactoryTalk user groups and users 235


In these steps you will add a local Administrator account as a Windows-linked user. The Administrator account is already automatically added to the Windows Administrators group under User Groups.

Step 10: Configure FactoryTalk groups and users

Configure Windows-linked FactoryTalk users



To add a local Administrator account as a Windows-linked user:

1. In the FactoryTalk Administration Console, in the Explorer, expand System > Users and Groups.

2. Right-click Users, and then click New > Windows-Linked User.

The New Windows-Linked User dialog box appears.

3. Click Add.

The Select Users dialog box appears.

4. Click Advanced.




5. Click Find Now.

6. Under Search results, users from the selected location are listed.



7. Select a user, and then click OK.

The Windows user that you have chosen appears under Enter the object names to select.

8. Click OK.

The Windows user appears in the New Windows-Linked User dialog box.



9. Click OK.

The newly added Windows-linked user appears under the Users folder in the Explorer.

TIP For more information on users and user groups in the FactoryTalk Administration Console, refer to the FactoryTalk help. To open the help file, on the Help menu click Contents.


To create FactoryTalk users:

1. On the Start screen, click FactoryTalk Administration Console.

The FactoryTalk Administration Console window appears.

2. In the Select FactoryTalk Directory dialog box, click Network, and then click OK.

TIP If you have not already logged on to the FactoryTalk Directory, you will be prompted to type your user name and password.

3. In the Explorer tree, expand Network > System > Users and Groups.

4. Right-click Users, and then click New > User.

Configure FactoryTalk users



The New User dialog box appears.

5. In the User name box, type a name of the user.

In this example we will use RSBizWareUser.

6. In the Password box, type a password for the user.

7. In the Confirm box, retype the password.

8. Click the Group Membership tab, and then click Add.

The Select User Group dialog box appears.

9. Click Administrators.

10. Click OK.



In the New User dialog box, the Administrators group is listed under Member of.

11. Click OK.

The newly created user appears under the Users folder in the Explorer. The user belongs to the FactoryTalk Administrators group.

TIP For more information on configuring the FactoryTalk Administration Console, refer to the FactoryTalk help. To open the help file, on the Help menu click Contents.


To install RSBizWare:



2. Click FactoryTalk Metrics > Installation > Install RSBizWare.


3. Click Next.


Step 11: Install RSBizWare



5. Click Next.

6. On the Customer Information page, type the following information:

7. Click Next.

8. On the Setup Type page, click:

9. Click Next.

10. On the Ready to Install the Program page, click Install.

The Installing page presenting the installation status appears.

Once the installation is complete, the InstallShield Wizard Completed page appears.

11. Click Finish.

A message prompting you to restart the computer appears.

12. Click Yes.




The Security Services Manager is a Windows service that is responsible for the following:

• Starting and stopping the RSBizWare server services.

• Administering licenses for all RSBizWare servers that are registered with the Security Services Manager.

The Security Services Manager lets you manage the servers and license activations from a single location.

To register the Security Services Manager:

1. On the Start screen, type any part of the name Service Console, and then click its shortcut.

TIP By default, the Service Console is located in the following directory: C:\Program Files (x86)\Rockwell Software\RSBizWare\RSBizwareMgr.msc

The Service Console window appears.


2. Click Yes.

The Service Console Registration dialog box appears.

3. In the Hostname or IP address box, type the name or IP address of the local computer.

Step 12: Register the Security Services Manager



Alternatively, click , and then search for the computer.

4. Click OK.

You have logged on to the Security Services Manager. The explorer tree in the Service Console is populated with Security Services Manager items.

NOTE Logging on to the Security Services Manager will activate the FactoryTalk single sign-on user functionality. For more information about the FactoryTalk single sign-on, refer to the FactoryTalk Security online help. The file is available in the following locations: • On a 32-bit operating system:

C:\Program Files\Common Files\Rockwell\Help\FTSecurityEN.chm.

• On a 64-bit operating system: C:\Program Files (x86)\Common Files\Rockwell\Help\FTSecurityEN.chm.


The server administration functions of the Security Services Manager enable you to control Information Services Manager and Metrics Server Manager Servers. Server administration functions include service configuration and service startup and shutdown.

To perform the server administration tasks, you must have the Windows System Administrator privilege, and your user account must be a member of the local administrator user group.

To register the Information Services Manager:

1. In the Service Console, under Security Services Manager, right-click Servers, and then click Register Server.


2. In the Server Type list, click Information Services Manager.

Step 13: Register the Information Services Manager



The Hostname or IP address box contains the name or the IP address of the local computer.

3. Click OK.

4. The Information Services Manager server appears under the Security Services Manager with the following icon: .

5. Click Information Services Manager.

6. In the Data Sources list, select the name of the ODBC data source that you created in "Step 8: Configure the ODBC data source (page 54)".

7. In the Database User ID box, type the name of the RSBizWare database user that you created in "Step 6: Create an RSBizWare SQL Server database user (page 49)".

8. In the Database Password box, type the password of your RSBizWare database user.

9. Click Test Connection.

A message confirming a successful connection appears.

10. Click OK.

11. Click Advanced.

12. Configure the following settings for QuickWeb reporting used in FactoryTalk Metrics and FactoryTalk Historian Classic:

Item Description Max Records to Return Type the maximum number of records that the

server should return for any single non-time-series query against the database. This can be a useful way to limit network traffic and control queries that are returning more than a useful amount of data. The default value is 1000.



Item Description Connection Pool Type the number of database connections that the

server should keep open. Each time a client makes a request for data from the database, a connection is assigned to the client from this pool. A small number of connections in the pool with a large number of connected users will create delays while users wait for an available connection. The default value is 5.

Session Connection Timeout Specify, in minutes, how long the server should maintain global credentials for users. After the session connection expires, the user will be required to log on before viewing report objects that have been set to use the global credentials. The default value is 30 minutes.

Host Alias Type 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. Use this option if the registered name of the computer is different than its host name.

Report Schedule Manager Host

Type the name of the computer where the Report Schedule Manager is running.

E-Mail Host Type the e-mail host that will be used to distribute scheduled report results.

Originating E-Mail Address Type the e-mail address that will be used to distribute scheduled report results.

Printer User Type the user name that will be used to connect to the printer to print scheduled reports.

Printer Password Type the password of the printer user. Report User Type the report user name that will be used to

connect to the Configuration Console to run the scheduled reports. If you are using scheduled reports, you must type a user with sufficient privileges to run all of the scheduled reports.

Report Password Type the password of the report user.



Item Description HTTP Port Type the port number on which the server will listen

for requests from Configuration Consoles. The Configuration Console uses HTTP in addition to raw TCP/IP to communicate to the Information Services Manager. 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 a value other than 8080.

HTML Root Type the name of the folder in which the server will store reports that have been saved in the Configuration Console. You will need to change the HTML Root directory setting if you have installed the server to a non-default location.

13. Click Apply.


14. Click Yes.




15. Click OK.

Once the server is restarted, the Information Services Manager server appears under the Security Services Manager with the following icon: .


To associate the Metrics Server Manager with the Information Services Manager:

1. In the Service Console, under Security Services Manager, expand Servers.

2. Right-click Information Services Manager, and then click Associate Metrics Server Manager.



3. Click OK.

The newly created Metrics Server Manager appears under Information Services Manager with the following icon: .

4. Click Metrics Server Manager.

5. In the Data Sources list, select the name of the ODBC data source that you created in "Step 8: Configure the ODBC data source (page 54)".

6. In the Database User ID box, type the name of the RSBizWare database user that you created in "Step 6: Create an RSBizWare SQL Server database user (page 49)".




Step 14: Associate Metrics Server Manager with Information Services Manager



9. Click OK.

10. (Optional) Click Advanced.

Review the following for additional information.

For this item: Type: Max Records to Return 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.

Connection Pool 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.

Session Connection Timeout The amount of time during which the server should maintain global credentials for users. After a user’s session connection expires, the user will be required to log on before viewing report objects that have been set to use the global credentials.

Host Alias (Optional) 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. The setting applies to a situation, when the registered name of the computer is different from the host name of the computer.


The name of the computer on which the Report Schedule Manager is running.

E-Mail Host The name of the SMTP server that will be used to distribute scheduled reports.

Originating E-Mail Address The originating e-mail address that will be used to distribute scheduled reports.

Printer User The user name that will be used to connect to the printer to print scheduled reports.

Printer Password The password of the printer user.



For this item: Type: Report User The report user name that will be used to connect to

the Configuration Console to run the scheduled reports. If you are using scheduled reports, provide a user with sufficient privileges to run all of the scheduled reports.

Report Password The password of the report user. HTTP Port The port number on which the server will listen for

requests from the Configuration Console. The default HTTP port is 8080. The Configuration Console uses HTTP in addition to raw TCP/IP to communicate with the Information Services Manager. 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.

HTML Root 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.

11. Click Apply.


During this process, the configuration that you have just defined is applied.

12. Click Yes.

The Metrics Server Manager appears under the Information Services Manager with the following icon: .



If you want to use the User-Defined Summarization Fields (Flex-Fields) in you configuration, configure them in the Metrics Server Manager (page 78).

A summarization criterion is a FactoryTalk Metrics Performance Parameter field for which you can collect activity area data. There are the following default summarization criteria:

• Shift

• Part Id

• Ideal Cycle Time

When the value of the field changes, it triggers the summarization of historical performance data for the activity area in the FactoryTalk Metrics 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 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.

Apart from the default summarization criteria, you can configure up to 5 user-defined summarization criteria, or flex-fields, to represent the fields that are most important to your organization.

Sample uses of user-defined summarization criteria include:

• An Operator ID criterion that will allow you to collect operator IDs and to report on the OEE value for a specific operator.

• A Lot Number 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 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.

Configure user-defined summarization fields (flex-fields)



By default, the user-defined summarization fields are disabled.

To enable and configure user-defined summarization fields:

1. In the Service Console, expand Metrics Server Manager, and then click FactoryTalk Metrics Flex- Fields.

In the right pane of the window, a list of 5 user-defined summarization fields appears.

2. Select the field that you want to configure, and then click Edit.

The Configure Summarization Criteria dialog box appears.

3. Select the Enable This Summarization Criteria check box.

4. In the Name box, replace the default name with a descriptive one that is meaningful to your organization.

In this example we will use Test Run State.

5. Select the Configuration of this Summarization Criteria is required for each Activity Area check box, if you want the data collection for this field to be mandatory.

6. Under Summarization Criteria Data Type, choose the type of data that will be collected for this field:

• String Value



Select this option, if you intend FactoryTalk Metrics to communicate with your ControlLogix controller.

The FactoryTalk Metrics Configuration Tool, which uses the FactoryTalk Metrics user-defined data type (UDT) to establish the communication with ControlLogix controllers, uses only the string values in the UDT to define flex-fields.

For more information on FactoryTalk Metrics Configuration Tool and the FactoryTalk Metrics user-defined data type, refer to the FactoryTalk Metrics User Guide, section "Automated Configuration".

• Numeric Value

• Boolean State Value

If you select this option, you will also need to type True and False display values.

In this example, we will select the Boolean State Value option, Test for the Display Value for True option, and Production for the Display Value for False option.

7. Click OK.

Your summarization field appears in the list as Enabled. It is now available for the Performance Parameters configuration.




To assign activations to the RSBizWare servers:

1. Under Security Services Manager, expand Administration.

2. Click Activations.

In the right pane of the window, activation details are provided.

The table provides the following information:

Item Description Total The total number of activations installed on the computer

where the selected Security Services Manager is running. The Security Services Manager checks all RSBizWare activations out of the FactoryTalk Activation.

Available The number of unassigned activations on the computer where the selected Security Services Manager is running. Unassigned activations will not be returned to the FactoryTalk Activation.

Step 15: Assign activations to RSBizWare servers



Item Description Assigned The number of activations that have been assigned to the

selected RSBizWare server. Only assigned activations will be detected by the product running on the selected server.

In the table, you may see the following types of activations:

Activation type Description Metrics Server Manager XX Workcells

A FactoryTalk Metrics server license for the specified number of work cells. You can assign more than one license. If you do, the number of work cells will be summed.

FactoryTalk Historian XXX Tag

A FactoryTalk Historian Classic server license for the specified number of tags. You can assign more than one license. If you do, the number of tags will be summed.

FactoryTalk Metrics Author

A single-user Authoring license that is assigned to a specific user. With this license, you can configure a FactoryTalk Metrics system using the Configuration Console.

FactoryTalk Historian Author

A single-user Authoring license that is assigned to a specific user. With this license, you can configure a FactoryTalk Historian Classic system using the Configuration Console.

RSBizWare Single User Runtime Activation

A license that allows a single user to access reports from FactoryTalk Historian Classic or FactoryTalk Metrics (using either Report Expert or QuickWeb.) You can assign more than one license. If you do, the number of users will be summed.

RSBizWare Unlimited User Runtime Activation

A license that allows an unlimited number of users to access reports from FactoryTalk Historian Classic or FactoryTalk Metrics (using either Report Expert or QuickWeb.). You can assign only one license of this type.

3. In the Assign Activations to list, select the RSBizWare server to which you want to assign activations.

4. Under Activation, click the activation that you want to assign to the server.

5. Click Assign an Activation.



The activation is assigned to the server.

The number of Available activations is reduced by 1, and the number of Assigned activations is increased by 1.



To assign client activations to users:

1. In the Service Console, expand Security Services Manager > Administration.

2. Click Users and Groups.

3. In the right pane of the window, under Users, click Refresh.

4. Click the user name for which you want to assign application privileges.

5. Click Edit User Properties.

Step 16: Assign client activations to users



The Security Control dialog box appears.

6. Click the License & Activation tab.

7. In the Server Type list, select the type of the server for which you want to assign privileges.

8. Under Place a check..., select the check box to the left of the activation that you want to assign to the user.

9. Click OK.


A privilege is a distinct function of FactoryTalk Metrics and FactoryTalk Historian Classic applications 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, the users assigned to that group are able to create new report objects in the Configuration Console.

Application privileges apply to the use of the Configuration Console and reporting using QuickWeb only. They do not apply to Report Expert.

Step 17: Assign application privileges to users



You can manage the privileges and permissions that a user has either by assigning privileges and permissions directly to the user or by assigning privileges and permissions to a user group, and then 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.

For information on privileges available with individual client activations, see "FactoryTalk Historian and FactoryTalk Metrics privileges (page 86)".

To assign application privileges to users:



3. In the right pane of the window, under Users, click the user name for which you want to assign application privileges.



5. In the Privileges tab, in the Server Type list, select the type of the server for which you want to assign privileges.

6. In the Server list, select a server of the specified server type.

7. Under Place a check..., select the check box to the left of the privilege that you want to assign to the user.

If the user has inherited privileges from a group, the privileges are indicated with the group icon: .

8. Click OK.



TIP While it is perfectly acceptable to assign privileges on a user-by-user basis, the process will become very tedious when you have a large number of users in the system. For this reason, you may want to assign privileges at a group level.

See also • Assign application privileges to groups 241

The following FactoryTalk Historian Classic and FactoryTalk Metrics (Configuration Console) privileges are available, depending on the assigned Author activation type.

Privilege Description Type of Author activation required 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.

FactoryTalk Metrics or FactoryTalk Historian Author

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.


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.


FactoryTalk Historian and FactoryTalk Metrics privileges



Privilege Description Type of Author activation required 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

Allows the selected user or group to use the Time-Series Reporting Tags dialog box 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.

None

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.

None

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.

None

Manage Performance Parameters

Allows the selected user or group to use the FactoryTalk Metrics Performance Parameters dialog box to specify the parameters that will be used in the calculation of OEE for an activity area.


Manage FactoryTalk Metrics Manual Data Collection

Allows the selected user or group to modify and delete FactoryTalk Metrics work cell data.


Manage Time Pattern Allows the selected user or group to create and modify time patterns, configure composites, and schedule exceptions.



The Information Services Manager and Metrics Server Manager use 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

Step 18: Register FactoryTalk Transaction Manager



to control the FactoryTalk Transaction Manager configurations that will be used to collect data.

In order to use FactoryTalk Transaction Manager configurations in the RSBizWare system on your computer or another computer in the network, register the computer as a FactoryTalk Transaction Manager configuration server.

To register a FactoryTalk Transaction Manager configuration server:

1. In the Service Console, expand Security Services Manager.

2. Right-click FactoryTalk Transaction Manager Configurations, and then click Register Server.


3. In the Hostname or IP address box, type the name or the IP

address of the server on which FactoryTalk Transaction Manager is installed.

4. Click OK.

TIP If the FactoryTalk Transaction Manager server contains any existing FactoryTalk Transaction Manager configurations, you will be prompted to select the configurations that you want to manage from the Service Console. The FactoryTalk Transaction Manager configurations that you select will be added under FactoryTalk Transaction Manager Configurations.



The FactoryTalk Transaction Manager server appears under FactoryTalk Transaction Manager Configurations with the following icon: .

See also • Configure data collection 247


FactoryTalk Transaction Manager configurations connect any control system from which data will be collected to the predefined data model used by the RSBizWare database to store production data. The configurations consist 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.

When you create a FactoryTalk Transaction Manager configuration, you are identifying the FactoryTalk Transaction Manager services

Step 19: Define FactoryTalk Transaction Manager configurations



that you want to use and the computer on which those services will run.

To define FactoryTalk Transaction Manager configurations:

1. In the Service Console, right-click your FactoryTalk Transaction Manager under FactoryTalk Transaction Manager Configurations, and then click Add Configuration.

The Add FactoryTalk Transaction Manager Configuration dialog box appears.

2. In the Name box, type a name for your configuration.

3. Next to the File Location box, click .

The Open dialog box appears.

4. Navigate to the location in which you will store the configuration file, and then click Open.

The path to and the name of the configuration file appears in the File Location box.



By default, the file name is the same as the configuration name.

5. In the Run As User box, type the name of the Windows system account that will be used by FactoryTalk Transaction Manager.

The account must have administrative privileges in the operating system.

6. In the Run As Password box, type the password of the Windows system account.

7. Select control and enterprise connectors for the configuration:

• Under Control Connectors, select the types of control connectors for the configuration.

• Under Enterprise Connectors, select the types of enterprise connectors for the configuration.

The type and number of the connectors depend on the application that you intend to configure:

This configuration type:

Requires these components:

FactoryTalk Metrics • One control connector, for example FactoryTalk LiveData.

• One PlantMetrics enterprise connector. • One or more other enterprise connector.

FactoryTalk Historian Classic • One or more control connectors. • One or more of the following enterprise

connectors: • ODBC • Oracle OCI • Microsoft OLE DB • Time-series Data Compression.

In this tutorial, you will define a FactoryTalk Metrics configuration.



8. Click OK.

9. The Add FactoryTalk Transaction Manager Connector dialog box appears for each connector that you have selected in your FactoryTalk Transaction Manager configuration.

10. Change the default settings, if necessary.

NOTE If you provide other Windows system account for the connector than the one that you have set for your configuration, make sure that the account has administrative privileges in the operating system.

11. Click Done.

Your configuration along with the connectors that you have selected for it appears in the tree under FactoryTalk Transaction Manager.





To register FactoryTalk Transaction Manager configurations:

1. In the Service Console, expand Information Services Manager.

2. Right-click Data Collection, and then click Register FactoryTalk Transaction Manager Configuration.

The FactoryTalk Transaction Manager Registration Wizard appears.

3. Click Next.

Step 20: Register FactoryTalk Transaction Manager configurations



The Local or Remote page appears.

4. Select either of the following:

• Search for FactoryTalk Transaction Manager Configurations on this computer.

• Search for FactoryTalk Transaction Manager Configurations on another computer.

If you have selected this option, point to the computer which you want to search for the configurations:

1. Next to the Computer box, click .

The Browse for Computer dialog box appears.

2. Navigate to and click the name of the computer.

3. Click OK.

The name of the selected computer appears in the Computer box.

5. Click Next.

The Select FactoryTalk Transaction Manager Configuration page appears.

6. Under Select an available FactoryTalk Transaction Manager Configuration, click the configuration that you want to use.



NOTE You can register only one FactoryTalk Transaction Manager configuration at a time.

7. Under Choose which RSBizWare application(s)..., click FT Metrics.

8. Click Next.

The Completing the Wizard page appears.

9. Review the choices you have made during the registration of your FactoryTalk Transaction Manager configurations.



10. Click Finish.

Your configuration appears in the tree under Data Collection.

Now you can use your configuration to create transactions in the Configuration Console.

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, refer to the FactoryTalk Historian Classic User Guide.

For information on defining performance parameters, refer to the FactoryTalk Metrics User Guide.



To configure SQL Server Reporting Services:

1. On the Start screen, type any part of the name Reporting Services Configuration Manager, and then click its shortcut.

2. The Reporting Services Configuration Manager window and the Reporting Services Configuration Connection dialog box appear.

3. Make sure that the Server Name and the Report Server Instance boxes points to the local computer and the locally configured report server instance.

4. Click Connect.

5. In the left pane of the window, click Service Account.

Step 21: Configure SQL Server Reporting Services (SSRS)



6. In the right pane of the window, make sure the Use built-in account option is selected, and that it points to ReportServer.

7. In the left pane of the window, click Database.

8. In the right pane of the window, under Current Report Server Database, make sure that SQL Server Name points to the local computer, and Database Name points to ReportServer.

9. Under Current Report Server Database Credential, click

Change Credentials.

The Report Server Database Configuration Wizard dialog box appears.

10. In the Authentication Type list, select SQL Server Account.

11. In the Username box, type sa (SQL Server System Administrator account).

12. In the Password box, type the password for the sa account.

You set this password when you were installing the SQL Server.




If the test is successful, the following message appears:


15. On the Credentials page, leave the default settings.

16. Click Next.

17. On the Summary page, review the database details.



18. Click Next.

19. Wait until the database is configured, and then click Finish.


To verify the configuration of SQL Server Reporting Services (SSRS):

1. On the Start screen, type any part of the name SQL Server Management Studio, and then click its shortcut.

2. The SQL Server Management Studio window and the Connect to Server dialog box appear.

3. In the Connect to Server dialog box, click Connect.

4. In the Object Explorer, click Connect > Reporting Services.

The Connect to Server dialog box appears.

5. Make sure that the Server type box reads Reporting Services.

Step 22: Verify the SSRS configuration



6. Click Connect.

The Report Server appears in the Object Explorer.

7. Exit the SQL Server Management Studio.


The Reporting Services Configuration Manager window and the Reporting Services Configuration Connection dialog box appear.



9. In the Reporting Services Configuration Connection dialog box, click Connect.

10. In the left pane of the window, click Report Manager URL.

11. In the right pane of the window, click the link in the URLs box.

The home page of the SQL Server Reporting Services appears in a web browser window.


When you install Report Expert, the installation automatically creates a Reporting Services database. The database is referred to as the Report Expert database and it is separate from the RSBizWare database. The Reporting Services is a part of the Microsoft SQL Server suite.

To install and configure Report Expert:



Step 23: Install and configure Report Expert



2. On the Welcome page, click FactoryTalk Metrics > Installation > Install Report Expert.

The installation program checks for installed applications.

3. On the Welcome page, click Next.


5. Click Next.

6. On the Customer Information page, type the following:

7. Click Next.

8. On the Setup Type wizard page, select:

• Complete, if you want to install all the features.

• Custom, if you want to install specific components.

If you choose this option, the Custom Setup page appears. Select the components that you want to install and their locations on the computer.

9. Click Next.

The Virtual directory information page appears. It displays the default virtual directory of the Report Expert web site: http://localhost/RockwellSoftware/ReportExpert



10. Click Next.

11. On the Database connection information page, provide the following information:

Item Description System DSN Name Select the name of the ODBC data source that you have

configured for your RSBizWare SQL Server database. Username Type the user name of your RSBizWare database. Password Type the password for the RSBizWare database user.

12. Click Next.


The Installing... page presenting the installation status appears.

14. On the InstallShield Wizard Completed page, click Finish.

The Database Load and Update wizard appears.


16. On the Product and Database Connection page, provide the following information:

Item Description ODBC DSN Select the name of the ODBC data source that you have

configured for your RSBizWare SQL Server database. User Type the user name of your RSBizWare database. Password Type the password for the RSBizWare database user.

17. Click Connect. The Available Product Modules list is populated with FactoryTalk components.

18. Under Available Product Modules, select these options:



TIP Select both options so that you have access to FactoryTalk Metrics and Report Expert sample data.

19. Click Finish to load data.

20. Click Close to exit the wizard.


In the initial configuration, Report Expert grants data editing only to those users that are identified as Report Expert Editors and are members of the default local group named FTMetricsEditors. Since the group is not created automatically during the installation of Report Expert, you need to create it manually, or point to a local group that already exists in your system and configure it appropriately. If you create a local group, you can either use the default name of the group - FTMetricsEditors - or choose another.

In the steps below we assume that you create a new local group that will contain all Report Expert editors.

To create and configure a local group for Report Expert Editors:

1. On the Start screen, type any part of the name Computer Management, and then click its shortcut.

2. The Computer Management window appears.

3. Create a new local group that will contain all of your Report Expert editors.

The default name for the group in the Report Expert configuration is host\FTMetricsEditors. You can use this name or choose another.

Step 24: Configure the FTMetricsEditors group



4. Add the Windows domain user name of each editor to the newly created group.

If you intend to use a local group that already exists in the system, or you have created a new group and chosen for it a different name than the default one, you need to update the Report Expert configuration file.

To update the Report Expert configuration file:

1. Open the <Report ExpertInstallationDirectory>\Website folder, and edit the Web.config file.

2. Replace the name of the default FTMetricsEditors group with the name of the group you have created or chosen to contain Report Expert editors.

For example, if the group that you use is named RptExpEditors, do the following:

Replace FTMetricsEditors: <add key="FTMetricsEditorsGroup" value="FTMetricsEditors"/>

...

<allow roles="FTMetricsEditors"/>

With RptExpEditors: <add key="FTMetricsEditorsGroup" value="RptExpEditors"/>

...

<allow roles="RptExpEditors"/>

3. Save the file.


To verify the Report Expert installation:

1. On the Start screen, type any part of the name Report Expert, and then click its shortcut.

Step 25: Verify the Report Expert installation



TIP By default, Report Expert is located in the following directory: C:\Program Files (x86)\Rockwell Software\Report Expert\RE.url

The Internet Explorer window and the Windows Security dialog box appear.

2. In the Windows Security dialog box, type the user name and the password to the computer on which you have configured ODBC for RSBizWare.

• For the all-in-one installation, this will be the local computer.

• For the installation on two computers, this will be the RSBizWare server computer.

If you have installed and configured Report Expert successfully, the Report Expert welcome page appears.

You have completed the installation and configuration of your RSBizWare environment. You are now ready to start the Configuration Console and begin to use the products.

Congratulations!



To modify the existing installation of RSBizWare software:

1. Run the RSBizWare installation DVD.

2. Select Install for the component that you want to modify.

3. Select one of the available options: Modify or Repair.

4. Follow the on-screen instructions to complete the process.

To remove RSBizWare applications:

• Use the installation DVD:

1. Run the RSBizWare installation DVD.

2. Select Install for the component that you want to remove.

3. Select Remove.


• Use Control Panel:

1. Go to Start > Control Panel > Add or Remove Programs (Programs and Features).

2. In the dialog box that appears, select the component you want to remove, and then click Remove (Uninstall/Change).


Remove RSBizWare


Chapter 4

Migrate RSBizWare

In this chapter you will learn how to migrate your RSBizWare environment between the following configurations:

From: To: Microsoft Windows Server 2003 R2 with Service Pack 2

Microsoft Windows Server 2012

Microsoft SQL Server 2005 Standard Edition with Service Pack 3

Microsoft SQL Server 2012 Service Pack 1

If your current RSBizWare environment is maintained on:

• Microsoft Windows Server 2008 R2 with Service Pack 1

• Microsoft SQL Server 2008 R2 Standard Edition with Service Pack 1

Upgrade it to the latest version following the steps presented in "Upgrading RSBizWare on Microsoft Windows Server 2008 R2 SP1 (page 211)".

To perform a migration of RSBizWare and Report Expert, choose one of the following scenarios:

Migration: supported migration scenarios

Chapter 4 Migrate RSBizWare


Migration from one source computer to one target computer (all-in-one installation)

Migration from a source computer to two target computers:

Migrate RSBizWare Chapter 4


Migration from two source computers to two target computers:

Migration from two source computers to one target computer (all-in-one installation):



In order to successfully migrate your RSBizWare and Report Expert software, follow the steps in the order presented below.

Backing up data

Step 1: Back up your FactoryTalk Transaction Manager configuration (page 115)

Step 2: Back up your RSBizWare SQL Server database (page 118)

Step 3: Keep your database users for reference (page 121)

Step 4: Keep your ODBC data source configuration for reference (page 123)

Step 5: Keep your FactoryTalk Administration Console configuration for reference (page 124)

Configuring SQL Server

Step 6: Install Internet Information Services (page 125)

Step 7: Install SQL Server 2012 Service Pack 1 (page 132)

Setting up your FactoryTalk environment

Step 8: Install FactoryTalk Services (page 138)

Step 9: Configure FactoryTalk Activation (page 143)

Recreating your RSBizWare SQL Server environment

Step 10: Restore your RSBizWare SQL Server database (page 144)

Step 11: Recreate your RSBizWare SQL Server database user (page 147)

Migration checklist



Step 12: Install SQL Server 2012 Native Client (page 151)

Step 13: Recreate the ODBC data source (page 152)

Recreating your FactoryTalk Administration Console configuration

Step 14: Verify if the local computer is added to the FactoryTalk Administration Console (page 158)

Step 15: Recreate your applications (page 159)

Step 16: Add a local Administrator account as a Windows-linked user (page 160)

Step 17: Recreate your users (page 164)

Installing RSBizWare

Step 18: Install RSBizWare (page 167)

Configuring RSBizWare servers


Step 20: Register the Information Services Manager (page 169)


Configuring security for RSBizWare

Step 22: Assign activations to RSBizWare servers (page 174)

Step 23: Assign client activations to users (page 177)

Step 24: Assign application privileges to users (page 180)



Restoring your FactoryTalk Transaction Manager configuration

Step 25: Restore your FactoryTalk Transaction Manager configuration (page 178)

Step 26: Register the configuration in the RSBizWare SQL Server database (page 183)

Step 27: Update your FactoryTalk Transaction Manager configuration (page 184)

Step 28: Register FactoryTalk Transaction Manager (page 188)

Step 29: Register the configuration in the Service Console (page 189)

Installing and configuring Report Expert

Step 30: Configure SQL Server Reporting Services (SSRS) (page 192)

Step 31: Verify the SSRS configuration (page 195)

Step 32: Install and configure Report Expert (page 197)

Step 33: Configure the FTMetricsEditors group (page 201)

Step 34: Verify the Report Expert installation (page 202)

Starting the FactoryTalk Transaction Manager configuration

Step 35: Start your FactoryTalk Transaction Manager configuration (page 203)



TIP If you are migrating the RSBizWare suite from two computers, perform the following steps on the Source RSBizWare server computer.

To successfully restore your FactoryTalk Transaction Manager configuration, you need to keep for reference the location in which the configuration is saved in FactoryTalk Transaction Manager, and create the configuration backup.

To check the location in which your FactoryTalk Transaction Manager configuration is saved:

1. Open FactoryTalk Transaction Manager.

2. On the Configuration menu, click Checklist.

The Configuration Checklist dialog box appears.

3. Under Define Configuration, click Step 1.

The FactoryTalk Transaction Manager Configuration dialog box appears.

In the Path text box, the location in which the configuration is saved is provided.

4. Keep it for reference.

To back up your FactoryTalk Transaction Manager configuration:


2. In the tree view, right-click the FactoryTalk Transaction Manager configuration that you want to migrate, and then click Stop Configuration.


Step 1: Back up your FactoryTalk Transaction Manager configuration



3. Click Yes.

4. Wait until all the services are stopped and the traffic lights icon next to the configuration in the tree view changes to the red light.

5. On the Configuration menu, click Backup.

The Remote rsq File Browse dialog box appears.

6. In the tree view, select the folder to which you want to save your configuration, or create a new one.

To create a new folder:

1. In the File Path text box, type the path to the folder and the folder name, and then click New.




2. Click Yes.


3. Click OK.

7. Click OK.


8. Click OK.




9. Click OK.

TIP If you are migrating the RSBizWare suite from two computers, perform the following steps on the Source Database server computer.

To back up your RSBizWare SQL Server database:

1. Open SQL Server Management Studio.


2. If necessary, type your login and password, and then click Connect.

3. In the Object Explorer, expand Databases.

4. Right-click the database that you want to migrate, and then click Tasks > Back Up.

Step 2: Back up your RSBizWare SQL Server database



The Back Up Database dialog box appears.

Under Destination, the default location to which the backup will be saved is provided.

Leave it or choose another location.

To choose another location for your database backup:

1. Under Destination, click Remove.

The default location is removed.

2. Click Add.

The Select Backup Destination dialog box appears.

3. Under File name, click .

The Locate Database Files dialog box appears.

4. Navigate to the location, in which you want to save the file.

5. In the File name text box, type the file name under which you want to save your RSBizWare SQL Server database backup.



6. Click OK.

7. In the Select Backup Destination dialog box, click OK.

Under Destination, your location and the file name of the RSBizWare database backup is listed.

5. In the left pane of the Back Up Database dialog box, under

Select a page, click Options.

6. Under Overwrite media, click Overwrite all existing backup sets.

7. Under Reliability, select the Verify backup when finished check box.



8. Click OK.

Once the backing up process is complete, the following message appears:

9. Click OK.

TIP If you are migrating the RSBizWare suite from two computers, perform the following steps on the Source Database server computer.

In order to successfully restore your RSBizWare SQL Server database on the target computer, you will need to recreate all the database users that are required by this database, along with their roles and passwords.

Since there is no automatic way of backing up this information, use your preferred method of storing it for reference.

Step 3: Keep your database users for reference



To view your RSBizWare SQL Server database users:

1. In the Object Explorer, expand your RSBizWare database tree item.

2. Expand Security, and then Users.

Under Users, the database users are listed.

To view database user roles:

1. Under Users, right-click a user, and then click Properties.

2. The Database User dialog box appears.

Under Database role membership, available roles are listed. The user's roles are selected.




It is necessary that you restore on the target computer the following elements of the ODBC data source configuration:

• The data source name.

• The login ID and the password of your RSBizWare SQL Server database to which you are connecting with the ODBC data source.


To view your ODBC data source configuration:

1. Go to Start > All Programs > Administrative Tools > Data Sources (ODBC).

The ODBC Data Source Administrator dialog box appears.

2. Click the System DSN tab.

3. Under System Data Sources, select the data source whose configuration you want to check, and then click Configure.

The information about the login and password to your RSBizWare SQL Server database is presented in different ways, depending on whether you have chosen the SQL Server Native Client 10.0 driver or the SQL Server driver to configure your ODBC data source:

• The configuration using the SQL Server Native Client 10.0 driver:

Step 4: Keep your ODBC data source configuration for reference



• The configuration using the SQL Server driver:


It is necessary that you restore on the target computer the following elements of the FactoryTalk Administration Console configuration:

• Applications

• Areas

• Servers

• Shortcuts to controllers

Step 5: Keep your FactoryTalk Administration Console configuration for reference



• User Groups

• Users


TIP If you are migrating the RSBizWare suite to two computers, perform the following steps on the Target Database server computer.

To install Internet Information Services (IIS):



2. Under Configure this local server, click Add roles and features.

The Add Roles and Features Wizard appears.

Step 6: Install Internet Information Services (IIS)



3. Click Next.

The Select installation type page appears.

4. Click Role-based or feature-based installation.

5. Click Next.

The Select destination server page appears.

6. Click Select a server from the server pool.

7. Under Server Pool, select the local server computer (i.e., the computer on which you are performing these steps).

8. Click Next.

The Select server roles page appears.

9. Click Web Server (IIS).





11. Click Next.

The Select features page appears.


Feature group Individual features .NET Framework 3.5 Features • .NET Framework 3.5 (Includes .NET 2.0 and 3.0)

.NET Framework 4.5 Features • .NET Framework 4.5 • ASP.NET 4.5 • WCF Services • HTTP Activation





14. Click Next.

The Web Server Role (IIS) page appears.

15. Click Next.

The Select role services page appears.



16. Select the following role services:

Role group Services Web Server • Common HTTP Features

• Default Document • Directory Browsing • HTTP Errors • Static Content • Security • Request Filtering • Windows Authentication • Application Development • .NET Extensibility 4.5 • ASP.NET 4.5 • ISAPI Extensions • ISAPI Filters

Management Tools • IIS Management Console • IIS 6 Management Compatibility • IIS 6 Metabase Compatibility

If a dialog box appears listing additional features required, click Add Features.

17. Click Next.

The Confirm installation selections page appears.

18. Review the list of the features that will be installed.



19. Select the Restart the destination server automatically if

required option.


20. Click Yes to confirm selecting the option.



21. Click Install.

The features that you have selected are being installed to your server.

22. Once the installation is complete, click Close.

23. Open your web browser, and type http://localhost.

The IIS 8.0 logo displayed in the window of the web browser confirms that the installation has been successful.




To install SQL Server:

1. Run the SQL Server 2012 Service Pack 1 installation media.




3. Click OK.

The Product Key page appears.

The product key is already provided on the page.


The License Terms page appears.

5. Read the license terms, click I accept the license terms, and then click Next.


Step 7: Install SQL Server 2012 Service Pack 1






7. Click Next.

The Setup Role page appears.

8. Click SQL Server Feature Installation, and then click Next.



NOTE If you intend to use SQL Server 2014 with RSBizWare, you won't see the SQL Server Data Tools (SDT) option, because SSDT are not available as a part of the SQL Server 2014 installation steps. To use SSDT, install your preferred SSDT version first (for details, refer to the SSDT documentation), and then configure your SSDT to work with RSBizWare. For details, see Configure your SQL Server Data Tools (SSDT) to work with Report Expert custom reports (page 207).

10. Click Next.

The Installation Rules page appears.

11. Click Next.

The Instance Configuration page appears.


The Disk Space Requirements page appears.

13. Click Next.



The Server Configuration page appears.

14. On the Service Accounts tab, define accounts for each SQL Server service.

15. Click the Collation tab, and then click Customize.

The Customize the SQL Server 2012 Database Engine Collation dialog box appears.

16. Click SQL collation, used for backwards compatibility.

17. In the list, select SQL_Latin1_General_CP1_CI_AS.


The Database Engine Configuration page appears.

19. Select Mixed Mode... as the authentication method.



20. Under Mixed Mode..., type the password for the SQL Server System Administrator account (sa).

IMPORTANT Make sure that you do not lose or forget the password for the sa account. You will need to provide this password when you will be configuring the SQL Server Reporting Services (SSRS).

21. Under Specify SQL Server administrators, add at least one user as the SQL Server administrator.

22. Click Next.

The Reporting Services Configuration appears.



23. Click Next.

The Error Reporting page appears.

24. Click Next.

The Installation Configuration Rules page appears.

25. Click Next.

The Ready to Install page appears.

26. Click Install.

The Installation Progress page appears.

SQL Server 2012 is being installed.

27. Once your SQL server is installed successfully, close the SQL Server Installation Center wizard.

When you select this option, the following components will be installed:

• FactoryTalk Services Platform with FactoryTalk Directory

FactoryTalk Services Platform is an underlying architecture and a set of common services (such as diagnostic messages, health monitoring services, access to real-time data, and shared plant resources such as tags and graphic displays) that Rockwell Automation products build upon. It is a prerequisite for all FactoryTalk-enabled software products.

• FactoryTalk Activation Manager

FactoryTalk Activation Manager allows you to download activation files using an Internet connection, and transfer the activation files to a computer that does not have an Internet connection. Install this software on the same computer as the FactoryTalk Directory server.

• RSLinx Enterprise

RSLinx Enterprise is a FactoryTalk Live Data server and a device-based alarm and event server. RSLinx Enterprise links

Step 8: Install FactoryTalk Services



Allen-Bradley networks and devices to Microsoft Windows products such as the FactoryTalk View SE (HMI software) and the RSLogix family of device programming software.

• FactoryTalk Alarms and Events (optional)

FactoryTalk Alarms and Events provide a common, consistent view of alarms and events throughout a FactoryTalk system.

For more information on FactoryTalk, refer to FactoryTalk Help.

NOTE Make sure to install FactoryTalk Services on all computers, including the computer that will serve as the FactoryTalk Directory.

To install FactoryTalk Services:



2. Click FactoryTalk Metrics > Installation > Install FTServices.


3. Follow the steps as presented in the screenshots below.



4.



5.



6.

TIP • You may omit restarting the computer after the FactoryTalk Services installation is complete.

• For details on configuring the FactoryTalk Services, see FactoryTalk Help.

TIP If you are migrating the RSBizWare suite to two computers, perform the following steps on the Target RSBizWare server computer.

To configure FactoryTalk Activation:

1. On the Start screen, type any part of the name FactoryTalk Activation Manager, and then click its shortcut.

The FactoryTalk Activation Manager window appears.




2. Follow the instructions displayed in the window to configure your activations.

TIP Click Help for more information, or refer to the instructions from the Activate Rockwell Software Products leaflet, available with your product installation package.




To restore your RSBizWare SQL Server database:

1. Copy the backup of your RSBizWare SQL Server database that you created in "Step 2: Back up your RSBizWare SQL Server database (page 118)" from the source computer to the computer on which you are performing these steps.





5. In the Object Explorer, right-click Databases, and then click Restore Database.

The Restore Database dialog box appears.

6. Under Source, click Device, and then click .

Step 10: Restore your RSBizWare SQL Server database



The Select backup devices dialog box appears.

7. Click Add.

The Locate Backup File dialog box appears.

8. Navigate to and select the backup file.

9. Click OK.

The backup file is listed under Backup media.

10. Click OK.



The Device text box points to the backup file, and the Database text box reads the database name from the backup file.

Under Destination, the Database text box reads the database name from the backup file.

IMPORTANT Make sure that the database name is the same as the name of the database that you are about to restore.

11. In the left pane of the dialog box, under Select a page, click Options.

12. Under Restore options, select the Overwrite the existing database (WITH REPLACE) option.

13. Click OK.

Once the restoring process is complete, the following message appears:

14. Click OK.

The database that you have restored appears under Databases in the Object Explorer.





In the following example, we are presenting how to recreate the database user that is the db_owner of the restored RSBizWare database. If you had other database users configured for your restored RSBizWare SQL Server database, you will need to recreate them all, along with their names, roles, and password, in a similar way.

To recreate your RSBizWare SQL Server database user:





4. Expand Database > <Your Restored Database> > Security > Users.

5. Under Users, delete all the users that were originally created for this database before the migration.

You will create them from scratch, because otherwise the existing users may generate errors.

6. In the Object Explorer, expand the Security folder.


Step 11: Recreate your RSBizWare SQL Server database user




8. In the Login name box, type a name for the database user.

IMPORTANT Make sure that the database user name is the same as the user name of the database that you have just restored.

9. Click SQL Server authentication.

10. In the Password box, type a password for the database user.

11. In the Confirm password box, retype the password that you have created.

12. Clear the Enforce password expiration check box.

13. In the Default database list, select the name of your RSBizWare database that you restored in "Step 10: Restore your RSBizWare SQL Server database (page 144)".



14. In the left pane of the Login - New dialog box, under Select a

page, click User Mapping.

15. Under Users mapped to this login, in the Map column, select

the check box next to the name of your RSBizWare database.



16. In the Default Schema column, in the row of your

RSBizWare database, type the name of your database user.

17. Under Database role membership for <DatabaseName>, select the db_owner check box.

18. Click OK.



TIP If you are migrating the RSBizWare suite to two computers, perform the following steps on the Target RSBizWare server computer. Otherwise, go to "Step 13: Recreate the ODBC data source (page 152)".

It is necessary that you install the Microsoft SQL Server 2012 Native Client on the target RSBizWare server computer so that you can use it in the ODBC data source configuration to establish connection with your RSBizWare SQL Server database.

To install the SQL Server 2012 Native Client:

1. Open the Microsoft SQL Server 2012 Feature Pack page (http://www.microsoft.com/en-us/download/details.aspx?id=29065).

2. Expand Install Instructions.

3. Scroll down to Microsoft® SQL Server® 2012 Native Client.

4. Click X64 Package.

5. Download the file.

6. Double-click sqlncli.msi.

The Microsoft SQL Server Native Client Setup wizard appears.

7. Click Next.

Step 12: Install SQL Server 2012 Native Client






9. Click Next.

10. On the Feature Selection page, leave the default settings, and then click Next.

11. On the Ready to Install the Program, click Install.

12. Once the installation is complete, click Finish.

TIP If you are migrating the RSBizWare suite to two computers, perform the following steps on the Target RSBizWare server computer and the Target database server computer.

To recreate your ODBC data source:



2. On the Tools menu, click ODBC Data Source (32-bit).

The ODBC Data Source Administrator (32-bit) dialog box appears.

3. Click the System DSN tab, and then click Add.

The Create New Data Source dialog box appears.

4. In the driver list, select SQL Server Native Client 11.0.

Step 13: Recreate the ODBC data source



NOTE Choose this driver even if you had the ODBC data source configured with the SQL Server driver on your source computer.

5. Click Finish.

The Create a New Data Source to SQL Server dialog box appears.

6. In the Name box, type the name of the data source.

IMPORTANT Make sure that this is the same name as it was for the ODBC data source configured on the source computer.

7. (Optional) In the Description box, type the description of the data source.

8. In the Server list, do either of the following:

• If your RSBizWare SQL Server database is on the computer on which you are performing these steps, select (local).

• If your RSBizWare SQL Server database is on the target database server computer, select the name of the target database server computer.

9. Click Next.

10. Specify how SQL Server should verify login IDs:

1. Select the With SQL Server authentication... option.

2. In the Login ID and Password text boxes, type the name and password of the RSBizWare database owner that you



restored in "Step 11: Recreate your RSBizWare SQL Server database user (page 147)".

11. Click Next.

12. Click Change the default database to, and then select the database that you restored in "Step 10: Restore your RSBizWare SQL Server database (page 144)".

13. Click Next.

14. Leave the default settings or modify them according to your needs.



15. Click Finish.

The ODBC Microsoft SQL Server Setup dialog box appears.

16. Verify the new ODBC data source configuration, and then click Test Data Source.

A message box with the test results appears.



17. Click OK.

TIP If the test does not complete successfully, make sure that you have selected the correct authentication mode for your SQL Server (page 156), and then run the test again.


The RSBizWare configuration requires the mixed mode as the authentication method for the SQL server. Follow the steps below to verify and/or correct the authentication method you have selected for your SQL server.

Repair the connection to SQL Server



To repair the connection to SQL Server:





4. In the Object Explorer, right-click the server name, and then click Properties.

The Server Properties dialog box appears.

5. Under Select a page, click Security.

6. Under Server authentication, check the selected server authentication mode.

If the Windows authentication mode is selected, change it to SQL Server and Windows Authentication mode.

7. Click OK.


8. Click OK.

9. In the Object Explorer, right-click the server name, and then click Restart.




10. Click Yes.

The server authentication mode will be updated.


By default, the computer on which you have installed FactoryTalk Services Platform is automatically added to the FactoryTalk Administration Console, which is a part of FactoryTalk Services Platform.

The computer should be listed in the Explorer, under System > Computers and Groups > Computers.

If it is not listed there, you should add it manually.

To add your local computer to the FactoryTalk Administration Console:

1. In the FactoryTalk Administration Console, in the Explorer, expand System > Computers and Groups.

2. Right-click Computers, and then click New Computer.

The New Computer dialog box appears.

3. In the Computer text box, type the name of the computer, or click to search for it.

Step 14: Verify if the local computer is added to the FactoryTalk Administration Console



4. Click OK.

The computer is listed under Computers.


To recreate the configuration, use the data from your source computer. For details, see "Step 5: Keep your FactoryTalk Administration Console configuration for reference (page 124)".

To recreate your applications:

1. On the Start screen, type any part of the name FactoryTalk Administration Console, and then click its shortcut.

The FactoryTalk Administration Console window appears.

2. In the Select FactoryTalk Directory, click OK.

3. In the Explorer, right-click Network, and then click New Application.

The New Application dialog box appears.

4. In the Name text box, type the same application name that you used in your original FactoryTalk Administration Console configuration.

5. Click OK.

6. In the Explorer, right-click your application, and then click New Area.

The New Area dialog box appears.

7. In the Name text box, type the same area name that you used in your original FactoryTalk Administration Console configuration.

8. Click OK.

Step 15: Recreate your applications



9. In the Explorer, right-click your area, and then click Add New Server > Rockwell Automation Device Server (RSLinx Enterprise).

The RSLinx Enterprise Server Properties dialog box appears.

10. Under Name, type the same server name that you used in your original FactoryTalk Administration Console configuration.

11. Click OK.

12. In the Explorer, expand the server item, and then double-click Communication Setup.

13. In the right pane of the window, under Device Shortcuts,

click Add.

A new shortcut appears in the list, available for editing.

14. Type the same shortcut name that you used in your original FactoryTalk Administration Console configuration.

15. Under Primary, expand the server tree, and point to the same connector that was assigned to the shortcut on your original FactoryTalk Administration Console configuration.

16. Click OK.


In these steps you will add a local Administrator account as a Windows-linked user. The Administrator account is already automatically added to the Windows Administrators group under User Groups.

Step 16: Add a local Administrator account as a Windows-linked user



To add a local Administrator account as a Windows-linked user:


2. Right-click Users, and then click New > Windows-Linked User.

The New Windows-Linked User dialog box appears.

3. Click Add.


4. Click Advanced.




5. Click Find Now.

6. Under Search results, users from the selected location are listed.



7. Select a user, and then click OK.

The Windows user that you have chosen appears under Enter the object names to select.

8. Click OK.

The Windows user appears in the New Windows-Linked User dialog box.



9. Click OK.

The newly added Windows-linked user appears under the Users folder in the Explorer.


To recreate the configuration, use the data from your source computer. For details, see "Step 5: Keep your FactoryTalk Administration Console configuration for reference (page 124)".

To recreate your users:


2. Right-click Users, and then click New > User.

The New User dialog box appears.

3. In the User name box, type the same user name that you used in your original FactoryTalk Administration Console configuration.

4. Select the User cannot change password option.

5. Select the Password never expires option.

Step 17: Recreate your users



6. In the Password box, type the password that you used for this user in your original FactoryTalk Administration Console configuration.

7. In the Confirm box, retype the password.

8. Click the Group Membership tab, and then click Add.

The Select User Group dialog box appears.

9. Click Administrators.

10. Click OK.

In the New User dialog box, the Administrators group is listed under Member of.



11. Click OK.

The newly created user appears under the Users folder in the Explorer. The user belongs to the FactoryTalk Administrators group.

Repeat the steps to restore other users that existed in your original FactoryTalk Administration Console configuration. Make sure that they have the same names, passwords, and user groups as in your original FactoryTalk Administration Console configuration.

TIP For more information on users and user groups in the FactoryTalk Administration Console, refer to the FactoryTalk help. To open the help file, on the Help menu click Contents.

See also • Manage FactoryTalk user groups and users 235




To install RSBizWare:



2. Click FactoryTalk Metrics > Installation > Install RSBizWare.


3. Click Next.


5. Click Next.

6. On the Customer Information page, type the following information:

7. Click Next.

8. On the Setup Type page, click:

Step 18: Install RSBizWare



9. Click Next.


The Installing page presenting the installation status appears.

Once the installation is complete, the InstallShield Wizard Completed page appears.

11. Click Finish.

A message prompting you to restart the computer appears.

12. Click Yes.


To register the Security Services Manager:

1. On the Start screen, type any part of the name Service Console, and then click its shortcut.

TIP By default, the Service Console is located in the following directory: C:\Program Files (x86)\Rockwell Software\RSBizWare\RSBizwareMgr.msc

The Service Console window appears.


Step 19: Register the Security Services Manager



2. Click Yes.


3. In the Hostname or IP address box, type the name or IP address of the local computer.

Alternatively, click , and then search for the computer.

4. Click OK.

You have logged on to the Security Services Manager. The explorer tree in the Service Console is populated with Security Services Manager items.

NOTE Logging on to the Security Services Manager will activate the FactoryTalk single sign-on user functionality. For more information about the FactoryTalk single sign-on, refer to the FactoryTalk Security online help. The file is available in the following locations: • On a 32-bit operating system:

C:\Program Files\Common Files\Rockwell\Help\FTSecurityEN.chm.

• On a 64-bit operating system: C:\Program Files (x86)\Common Files\Rockwell\Help\FTSecurityEN.chm.


To register the Information Services Manager:

1. In the Service Console, under Security Services Manager, right-click Servers, and then click Register Server.


2. In the Server Type list, click Information Services Manager.

3. Make sure that Hostname or IP address box contains the name or the IP address of the local computer.

4. Click OK.




5. The Information Services Manager server appears under the Security Services Manager with the following icon: .

6. Click Information Services Manager.

7. In the Data Sources list, select the name of the ODBC data source that you recreated in "Step 13: Recreate the ODBC data source (page 152)".

8. In the Database User ID box, type the name of the RSBizWare database user that you recreated in "Step 11: Recreate your RSBizWare SQL Server database user (page 147)".




11. Click OK.

12. Click Advanced.

13. Configure the following settings for QuickWeb reporting used in FactoryTalk Metrics and FactoryTalk Historian Classic:



Item Description Max Records to Return Type the maximum number of records that the

server should return for any single non-time-series query against the database. This can be a useful way to limit network traffic and control queries that are returning more than a useful amount of data. The default value is 1000.

Connection Pool Type the number of database connections that the server should keep open. Each time a client makes a request for data from the database, a connection is assigned to the client from this pool. A small number of connections in the pool with a large number of connected users will create delays while users wait for an available connection. The default value is 5.

Session Connection Timeout Specify, in minutes, how long the server should maintain global credentials for users. After the session connection expires, the user will be required to log on before viewing report objects that have been set to use the global credentials. The default value is 30 minutes.

Host Alias Type 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. Use this option if the registered name of the computer is different than its host name.


Type the name of the computer where the Report Schedule Manager is running.

E-Mail Host Type the e-mail host that will be used to distribute scheduled report results.

Originating E-Mail Address Type the e-mail address that will be used to distribute scheduled report results.

Printer User Type the user name that will be used to connect to the printer to print scheduled reports.

Printer Password Type the password of the printer user.



Item Description Report User Type the report user name that will be used to

connect to the Configuration Console to run the scheduled reports. If you are using scheduled reports, you must type a user with sufficient privileges to run all of the scheduled reports.

Report Password Type the password of the report user. HTTP Port Type the port number on which the server will listen

for requests from the Configuration Console. The Configuration Console uses HTTP in addition to raw TCP/IP to communicate to the Information Services Manager. 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 a value other than 8080.

HTML Root Type the name of the folder in which the server will store reports that have been saved in the Configuration Console. You will need to change the HTML Root directory setting if you have installed the server to a non-default location.

14. Click Apply.


15. Click Yes.




16. Click OK.

Once the server is restarted, the Information Services Manager server appears under the Security Services Manager with the following icon: .


To associate the Metrics Server Manager with the Information Services Manager:

1. In the Service Console, under Security Services Manager, expand Servers.

2. Right-click Information Services Manager, and then click Associate Metrics Server Manager.



3. Click OK.

The newly created Metrics Server Manager appears under Information Services Manager with the following icon: .

4. Click Metrics Server Manager.

Step 21: Associate Metrics Server Manager with Information Services Manager



5. In the Data Sources list, select the name of the ODBC data source that you recreated in "Step 13: Recreate the ODBC data source (page 152)".

6. In the Database User ID box, type the name of the RSBizWare database user that you recreated in "Step 11: Recreate your RSBizWare SQL Server database user (page 147)".




9. Click OK.

10. Click Apply.


11. Click Yes.

The Metrics Server Manager appears under the Information Services Manager with the following icon: .


To assign activations to the RSBizWare servers:

1. Under Security Services Manager, expand Administration.

2. Click Activations.

Step 22: Assign activations to RSBizWare servers



In the right pane of the window, activation details are provided.

The table provides the following information:

Item Description Total The total number of activations installed on the computer

where the selected Security Services Manager is running. The Security Services Manager checks all RSBizWare activations out of the FactoryTalk Activation.

Available The number of unassigned activations on the computer where the selected Security Services Manager is running. Unassigned activations will not be returned to the FactoryTalk Activation.

Assigned The number of activations that have been assigned to the selected RSBizWare server. Only assigned activations will be detected by the product running on the selected server.

In the table, you may see the following types of activations:

Activation type Description Metrics Server Manager XX Workcells

A FactoryTalk Metrics server license for the specified number of work cells. You can assign more than one license. If you do, the number of work cells will be summed.



Activation type Description FactoryTalk Historian XXX Tag

A FactoryTalk Historian Classic server license for the specified number of tags. You can assign more than one license. If you do, the number of tags will be summed.


A single-user Authoring license that is assigned to a specific user. With this license, you can configure a FactoryTalk Metrics system using the Configuration Console.


A single-user Authoring license that is assigned to a specific user. With this license, you can configure a FactoryTalk Historian Classic system using the Configuration Console.

RSBizWare Single User Runtime Activation

A license that allows a single user to access reports from FactoryTalk Historian Classic or FactoryTalk Metrics (using either Report Expert or QuickWeb.) You can assign more than one license. If you do, the number of users will be summed.

RSBizWare Unlimited User Runtime Activation

A license that allows an unlimited number of users to access reports from FactoryTalk Historian Classic or FactoryTalk Metrics (using either Report Expert or QuickWeb.). You can assign only one license of this type.

3. In the Assign Activations to list, select the RSBizWare server to which you want to assign activations.

4. Under Activation, click the activation that you want to assign to the server.

5. Click Assign an Activation.

The activation is assigned to the server.

The number of Available activations is reduced by 1, and the number of Assigned activations is increased by 1.





To assign client activations to users:




4. Click the user name for which you want to assign application privileges.



6. Click the License & Activation tab.

7. In the Server Type list, select the type of the server for which you want to assign privileges.

8. Under Place a check..., select the check box to the left of the activation that you want to assign to the user.

Step 23: Assign client activations to users



9. Click OK.


To restore your FactoryTalk Transaction Manager configuration:

1. Copy the backup of your FactoryTalk Transaction Manager configuration that you created in "Step 1: Back up your FactoryTalk Transaction Manager configuration (page 115)" from the source computer to the computer on which you are performing these steps.

2. On the Start screen, type any part of the name FactoryTalk Transaction Manager, and then click its shortcut.

The FactoryTalk Transaction Manager window appears.

3. On the Configuration menu, click Restore.

The Remote rsq File Browse dialog box appears.

4. In the folder tree, navigate to the folder that contains the backup file.

5. Select the backup file, and then click OK.

Step 25: Restore your FactoryTalk Transaction Manager configuration



The FactoryTalk Transaction Manager Restore Configuration dialog box appears.

6. In the Path text box, leave the default setting or select another location in which you want to save the configuration.

The location should be the same as the location of the original configuration before the migration.

7. Click OK.


8. Click Yes.




9. Click OK.

The configuration is restored.


A privilege is a distinct function of FactoryTalk Metrics and FactoryTalk Historian Classic applications 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, the users assigned to that group are able to create new report objects in the Configuration Console.

Application privileges apply to the use of the Configuration Console and reporting using QuickWeb only. They do not apply to Report Expert.

You can manage the privileges and permissions that a user has either by assigning privileges and permissions directly to the user or by

Step 24: Assign application privileges to users



assigning privileges and permissions to a user group, and then 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 to users:



3. In the right pane of the window, under Users, click the user name for which you want to assign application privileges.





7. Under Place a check..., select the check box to the left of the privilege that you want to assign to the user.

If the user has inherited privileges from a group, the privileges are indicated with the group icon: .

8. Click OK.

TIP While it is perfectly acceptable to assign privileges on a user-by-user basis, the process will become very tedious when you have a large number of users in the system. For this reason, you may want to assign privileges at a group level.



See also • Assign application privileges to groups 241

The following FactoryTalk Historian Classic and FactoryTalk Metrics (Configuration Console) privileges are available, depending on the assigned Author activation type.

Privilege Description Type of Author activation required 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.


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.


FactoryTalk Historian and FactoryTalk Metrics privileges



Privilege Description Type of Author activation required Manage Reporting Tags

Allows the selected user or group to use the Time-Series Reporting Tags dialog box 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.

None

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.

None

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.

None

Manage Performance Parameters

Allows the selected user or group to use the FactoryTalk Metrics Performance Parameters dialog box to specify the parameters that will be used in the calculation of OEE for an activity area.


Manage FactoryTalk Metrics Manual Data Collection

Allows the selected user or group to modify and delete FactoryTalk Metrics work cell data.


Manage Time Pattern Allows the selected user or group to create and modify time patterns, configure composites, and schedule exceptions.



To register your FactoryTalk Transaction Manager configuration in the RSBizWare SQL Server database:





4. In the Object Explorer, expand Databases > <Your Restored Database> > Tables.

Step 26: Register the configuration in the RSBizWare SQL Server database



5. Navigate to the RSSqlConfig table.

6. Right-click the table, and then click Edit Top 200 Rows.

7. In the right pane of the window, under sHost, replace the

name or IP of the source computer on which you backed up the RSBizWare SQL Server database with the name or IP of the target computer on which you restored the database.

8. Press Enter.

9. Close the table tab.


To update your FactoryTalk Transaction Manager configuration:

1. In FactoryTalk Transaction Manager, on the Configuration menu, click Checklist.

The Configuration Checklist dialog box appears.


Step 27: Update your FactoryTalk Transaction Manager configuration



The FactoryTalk Transaction Manager Configuration dialog box appears.

3. Make sure that the following options are selected:

4. Click Apply.


5. Click Yes.




6. Click OK.

7. Click Close.

8. In the Configuration Checklist dialog box, under Define Connectors, click Step 2.

The Connector Definition dialog box appears.

9. In the Host Name text box, replace the name of the source computer on which you backed up the FactoryTalk Transaction Manager configuration with the name of the target computer on which you restored the configuration.

10. In the User Name text box, replace the name of the user of the source computer with the name of the user of the target computer.

11. In the Password text box, replace the password of the user of the source computer with the password of the user of the target computer.

12. Click Host / User.




13. Click OK.


14. Click OK.

You have updated the host names, user names, and password for all the connectors defined for your FactoryTalk Transaction Manager configuration.

15. Click Apply.


16. Click OK.




17. Click Yes.


18. Click OK.



To register a FactoryTalk Transaction Manager configuration server:

1. In the Service Console, expand Security Services Manager.

2. Right-click FactoryTalk Transaction Manager Configurations, and then click Register Server.


Step 28: Register FactoryTalk Transaction Manager



3. In the Hostname or IP address box, type the name or the IP

address of the server on which FactoryTalk Transaction Manager is installed, if it is not already provided.

4. Click OK.

The FactoryTalk Transaction Manager server appears under FactoryTalk Transaction Manager Configurations with the green traffic lights icon: .



Although you have already registered your configuration in "Step 26: Register the configuration in the RSBizWare SQL Server database (page 183)", you need to repeat the process on the Service Console level.

To register your FactoryTalk Transaction Manager configuration in the Service Console:

1. In the Service Console, expand Information Services Manager.

Step 29: Register the configuration in the Service Console



2. Right-click Data Collection, and then click Register FactoryTalk Transaction Manager Configuration.

The FactoryTalk Transaction Manager Registration Wizard appears.

3. Click Next.

4. On the Local or Remote page, click Next.

The Select FactoryTalk Transaction Manager Configuration page appears.

It lists your restored FactoryTalk Transaction Manager configuration in status the RSBizWare applications for which the configuration has already been registered in the RSBizWare SQL Server database.



5. Select the configuration, and then click Next.


6. Click Yes.

The Completing the Wizard page appears.

7. Click Finish.

Your configuration is listed in the tree under Data Collection.





To configure SQL Server Reporting Services:


2. The Reporting Services Configuration Manager window and the Reporting Services Configuration Connection dialog box appear.

3. Make sure that the Server Name and the Report Server Instance boxes points to the local computer and the locally configured report server instance.

4. Click Connect.

5. In the left pane of the window, click Service Account.

Step 30: Configure SQL Server Reporting Services (SSRS)



6. In the right pane of the window, make sure the Use built-in account option is selected, and that it points to ReportServer.

7. In the left pane of the window, click Database.

8. In the right pane of the window, under Current Report Server Database, make sure that SQL Server Name points to the local computer, and Database Name points to ReportServer.

9. Under Current Report Server Database Credential, click

Change Credentials.

The Report Server Database Configuration Wizard dialog box appears.

10. In the Authentication Type list, select SQL Server Account.

11. In the Username box, type sa (SQL Server System Administrator account).

12. In the Password box, type the password for the sa account.

You set this password when you were installing the SQL Server.




If the test is successful, the following message appears:


15. On the Credentials page, leave the default settings.

16. Click Next.

17. On the Summary page, review the database details.



18. Click Next.

19. Wait until the database is configured, and then click Finish.


To verify the configuration of SQL Server Reporting Services (SSRS):

1. On the Start screen, type any part of the name SQL Server Management Studio, and then click its shortcut.

2. The SQL Server Management Studio window and the Connect to Server dialog box appear.

3. In the Connect to Server dialog box, click Connect.

4. In the Object Explorer, click Connect > Reporting Services.


5. Make sure that the Server type box reads Reporting Services.

Step 31: Verify the SSRS configuration



6. Click Connect.

The Report Server appears in the Object Explorer.

7. Exit the SQL Server Management Studio.


The Reporting Services Configuration Manager window and the Reporting Services Configuration Connection dialog box appear.



9. In the Reporting Services Configuration Connection dialog box, click Connect.

10. In the left pane of the window, click Report Manager URL.

11. In the right pane of the window, click the link in the URLs box.

The home page of the SQL Server Reporting Services appears in a web browser window.


To install and configure Report Expert:



2. On the Welcome page, click FactoryTalk Metrics > Installation > Install Report Expert.

The installation program checks for installed applications.



Step 32: Install and configure Report Expert



5. Click Next.

6. On the Customer Information page, type the following:

7. Click Next.

8. On the Setup Type wizard page, select:

• Complete, if you want to install all the features.

• Custom, if you want to install specific components.

If you choose this option, the Custom Setup page appears. Select the components that you want to install and their locations on the computer.

9. Click Next.

The Virtual directory information page appears. It displays the default virtual directory of the Report Expert web site: http://localhost/RockwellSoftware/ReportExpert

10. Click Next.

11. On the Database connection information page, provide the following information:

Item Description System DSN Name Select the name of the ODBC data source that you have

configured for your RSBizWare SQL Server database.



Item Description Username Type the user name of your RSBizWare database. Password Type the password for the RSBizWare database user.

12. Click Next.


The Installing... page presenting the installation status appears.

14. On the InstallShield Wizard Completed page, click Finish.

The Database Load and Update wizard appears.


16. On the Product and Database Connection page, provide the following information:

Item Description ODBC DSN Select the name of the ODBC data source that you have

configured for your RSBizWare SQL Server database. User Type the user name of your RSBizWare database. Password Type the password for the RSBizWare database user.

17. Click Connect. The Available Product Modules list is populated with FactoryTalk components.

18. Under Available Product Modules, select these options:



TIP Select both options so that you have access to FactoryTalk Metrics and Report Expert sample data.

19. Click Finish to load data.

20. Click Close to exit the wizard.











In the initial configuration, Report Expert grants data editing only to those users that are identified as Report Expert Editors and are members of the default local group named FTMetricsEditors. Since the group is not created automatically during the installation of Report Expert, you need to create it manually, or point to a local group that already exists in your system and configure it appropriately. If you create a local group, you can either use the default name of the group - FTMetricsEditors - or choose another.

In the steps below we assume that you create a new local group that will contain all Report Expert editors.

To create and configure a local group for Report Expert Editors:

1. On the Start screen, type any part of the name Computer Management, and then click its shortcut.

2. The Computer Management window appears.

3. Create a new local group that will contain all of your Report Expert editors.

The default name for the group in the Report Expert configuration is host\FTMetricsEditors. You can use this name or choose another.

4. Add the Windows domain user name of each editor to the newly created group.

If you intend to use a local group that already exists in the system, or you have created a new group and chosen for it a different name than the default one, you need to update the Report Expert configuration file.

Step 33: Configure the FTMetricsEditors group



To update the Report Expert configuration file:

1. Open the <Report ExpertInstallationDirectory>\Website folder, and edit the Web.config file.

2. Replace the name of the default FTMetricsEditors group with the name of the group you have created or chosen to contain Report Expert editors.

For example, if the group that you use is named RptExpEditors, do the following:

Replace FTMetricsEditors: <add key="FTMetricsEditorsGroup" value="FTMetricsEditors"/>

...

<allow roles="FTMetricsEditors"/>

With RptExpEditors: <add key="FTMetricsEditorsGroup" value="RptExpEditors"/>

...

<allow roles="RptExpEditors"/>

3. Save the file.


To verify the Report Expert installation:





Step 34: Verify the Report Expert installation







To start your restored FactoryTalk Transaction Manager configuration:

1. On the Start screen, type any part of the name Configuration Console, and then click its shortcut.

TIP: By default, the Service Console is located in the following directory: C:\Program Files (x86)\Rockwell Software\RSBizWare\RSBizWare Production Client.exe

The Configuration Console window and the RSBizWare Login dialog box appear.

Step 35: Start your FactoryTalk Transaction Manager configuration



2. In the User text box, type the name of the user of your RSBizWare SQL Server database.

3. In the Password text box, type the user password.

4. In the Server text box, type or select from the list the name of the computer on which you have installed the RSBizWare SQL Server database:

• If your RSBizWare SQL Server database is on the computer on which you are performing these steps, select localhost.

• If your RSBizWare SQL Server database is on the target database server computer, select the name of this computer.

5. Click Login.

6. On the welcome page, under FactoryTalk Historian/Metrics Tasks, click:

The FactoryTalk Transaction Manager Configurations dialog box appears.

7. Select your restored configuration, and then click Start.



Once the configuration is started, its traffic lights icon changes to green.

You have successfully completed the migration of your RSBizWare environment. You are now ready to start the Configuration Console and begin to use the products.

Congratulations!


Chapter 5

Post-installation tasks

Additional settings are required to use RSBizWare properly with Microsoft Windows operating systems and Internet Explorer, which provide additional security features intended to protect your system from unknown programs and web sites.

To configure your SQL Server Data Tools (SSDT) to work with Report Expert custom reports:

1. Install SQL Server Data Tools (SSDT).

See the SSDT documentation for details.

When installing SSDT, make sure that all the following options are selected:

• SQL Server Database

• SQL Server Analysis Services

• SQL Server Reporting Services

• SQL Server Integration Services

2. Run the ReportExpertDeployment.exe file, located in the Deployment folder of your Report Expert installation directory, for example:

C:\Program Files (x86)\Rockwell Software\Report Expert\Deployment

The Report Expert Deployment Tool window appears.

3. In the window, click the Reports design tool configuration tab.

4. Next to the Path to report templates design tool binaries folder box, click .

Configure your SQL Server Data Tools (SSDT) to work with Report Expert custom reports

Chapter 5 Post-installation tasks


5. In the window that appears, navigate to the location in which your SSDT is installed, for example:

C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\PrivateAssemblies

6. Click OK.

7. In the Report Expert Deployment Tool window, click Deploy.

Your SSDT is configured to work with Report Expert custom reports.

The following image presents the Report Expert Deployment Tool window after the SSDT configuration has been successfully performed.

To view RSBizWare reports properly with Internet Explorer, you need to add the name of the RSBizWare server to trusted sites in Internet Explorer.

To configure trusted sites:

1. Open Internet Explorer.

Configure Internet Explorer trusted sites

Post-installation tasks Chapter 5


2. On the Tools menu, click Internet Options. The Internet Options dialog box appears.

3. Go to the Security tab, click Trusted Sites, and click Sites.

The Trusted Sites dialog box appears.

4. Under Add this Web site to the zone, type http://ServerName.

ServerName is the name of the RSBizWare server as shown in the System Properties in Control Panel.

5. Click Add.

6. Click Close, and then click OK.

To import the sample data into the RSBizWare database:

1. Go to Start > All Programs > Rockwell Software > FactoryTalk Tools > Database Wizard.

The Database Load and Update Wizard appears.

2. Click Next.

The Product and Database Connection page appears.

3. In the ODBC DSN list, select your ODBC data source.

4. In the User text box, type the user name of your RSBizWare database owner.

5. In the Password box, type the password of your RSBizWare database owner.

6. Click Connect.

Under Available Product Modules, a list of sample data appears.

Install RSBizWare sample data

Chapter 5 Post-installation tasks


7. Select the data that you want to import.

8. Click Finish.

The Processing page with the import status appears.

After the import is complete, the Completing the Database Load and Update Wizard page appears.

9. Click Close.


Chapter 6

Upgrade RSBizWare on Microsoft Windows Server 2008 R2 SP1



• Microsoft SQL Server 2005 Standard Edition with Service Pack 3

Migrate it to the latest version following the steps presented in "Migrate RSBizWare (page 109)".



• Microsoft SQL Server 2008 R2 Standard Edition with Service Pack 1

Upgrade it to the latest version following the steps presented in this chapter.


• Prepare for the upgrade 212

• Upgrade FactoryTalk Services Platform 213

• Upgrade the RSBizWare suite 214

Chapter 6 Upgrade RSBizWare on Microsoft Windows Server 2008 R2 SP1


If you are upgrading from a prior version of the FactoryTalk Metrics or FactoryTalk Historian Classic 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 file - located in the directory into which the software was installed - before beginning the upgrade process.

• The RSBizWare software will automatically upgrade your RSBizWare database as part of the configuration process. However, you may want also to consider upgrading your SQL server to the newest version supported by RSBizWare.

For up-to-date information on hardware and software requirements, consult Rockwell Automation Product Compatibility and Download Center (http://www.rockwellautomation.com/support/pcdc.page).

For details on upgrading SQL Server, refer to the Microsoft SQL Server documentation.

Before upgrading your automation system software from an earlier version of FactoryTalk Services Platform, take note of the following key points:

• You must remove all Rockwell Automation products that depend on FactoryTalk before removing 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 a new version of FactoryTalk Services Platform, all participating

Prepare for the upgrade

http://www.rockwellautomation.com/support/pcdc.page

Upgrade RSBizWare on Microsoft Windows Server 2008 R2 SP1 Chapter 6


software products must also be upgraded to compatible versions.

• 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 be compatible with this version of FactoryTalk Services Platform.

To upgrade FactoryTalk Services Platform:

1. Run the RSBizWare installation media. The RSBizWare installation wizard appears.

NOTE It is recommended that you 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 in the installation wizard on the RSBizWare installation media.

2. On the Welcome page, click FactoryTalk Metrics > Installation > Install FactoryTalk Services Platform.

The installation wizard checks for installed applications, and then displays a message informing you that a previous version of FactoryTalk Services Platform is installed. Click OK to proceed with the upgrade.

The previous version of FactoryTalk Services Platform is removed and the installation wizard appears.


During the installation, the wizard backs up existing FactoryTalk Directories, configures a FactoryTalk Local Directory and a FactoryTalk Network Directory.

Upgrade FactoryTalk Services Platform

Chapter 6 Upgrade RSBizWare on Microsoft Windows Server 2008 R2 SP1


The Configuring FactoryTalk Directory dialog box displays 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 are also logged to FactoryTalk Diagnostics.

NOTE The RSBizWare products make use of the Network Directory only.

To upgrade the RSBizWare suite:

1. Run the RSBizWare installation media. The RSBizWare installation wizard appears.

NOTE It is recommended that you 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 in the installation wizard on the RSBizWare installation media.

2. On the Welcome page, click FactoryTalk Metrics > Installation > Install RSBizWare.

3. The installation wizard checks for installed applications, and then displays a message informing you that a previous version of the RSBizWare suite is installed. Click OK to proceed with the upgrade.

4. The previous version of the RSBizWare suite is removed and the installation wizard appears.


For details, see "Step 13: Install RSBizWare (page 68)".

Upgrade the RSBizWare suite


Chapter 7

Administer RSBizWare servers

To perform the server administration tasks, you must have the Windows System Administrator privilege, and your user account must be a member of the local administrator user group.

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.

In the Service Console, the traffic light to the left of the Information Services Manager or Metrics Server Manager name in the Security Services Manager tree indicates the server run mode.

This icon: Indicates that the server is:

Not running. Any attempts to change the server settings or connect a client to the server will be unsuccessful. To start the server, right-click it, and then click Start Server.

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. To restart the server, right-click it, and then click Restart Server.

Running. When a server is running, you can change server settings, connect clients to the server, and configure external data sources. To stop the server, right-click it, and then click Stop Server.

Start and stop RSBizWare servers

Chapter 7 Administer RSBizWare servers


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:

• In the Service Console, expand your Information Services Manager tree item, and then click Scheduled Items.

The list of scheduled reports appears in the right pane of the window.

Use this list to view the reports and to delete scheduled reports that are no longer necessary.

To delete a scheduled report:

• Click a report, and then click Remove.

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

To create a new external data source (DSN):

1. In the Service Console, expand your Information Services Manager tree item, an then click External Data Sources.

The list of external data sources appears in the right pane of the window.

2. Click Add.

Manage Information Services Manager scheduled items

Manage Information Services Manager external data sources

Administer RSBizWare servers Chapter 7


The Data Source Properties dialog box appears.

3. In the Server DSN list, select the name of the ODBC Server

DSN that the server will use to access the external database.

The available DSNs are the ones that exist on the computer where the Information Services Manager is running.

4. In the Description box, type a description of the external data source.

The description will appear in the list of available data sources in the Report Data Source Wizard in the Configuration Console.

5. In the User box, type the user name that the server will use to connect to the data source.

6. In the Password box, type the user password.

7. In the Max Connections box, type the number of connections that the server will 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.


If the connection attempt is successful, the following message appears:

9. Click OK.

Now the tables and views in your external data source will be available to users when they create new report data sources.

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

Errors known by the Information Services Manager to cause temporary database connection loss:

General ODBC errors: Oracle-only errors: 08003 1033 08004 1089 08S01 3111 24000 3112 34000 3113 S1000 3114

Handle temporary database connection loss in the Information Services Manager



General ODBC errors: Oracle-only errors: S1001 S1008 S1009 S1010 S1109 01000 37000

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.

To create the dberrors.txt file:

1. Open a text editor.

2. Type 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 in separate lines in the text file:

3. Save the text file as dberrors.txt in the directory where the

RSBizWare software was installed.

By default, the RSBizWare software is installed in: C:\Program Files (x86)\Rockwell Software\RSBizWare.

NOTE All registry values specified are located in the HKEY_LOCAL_MACHINE\Software\Rockwell Software\PlantMetrics\Current Configuration\OnyxServer registry key.

To allow the Metrics Server Manager to make more efficient use of memory, manage the processing of RSL files better, 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 (the default location is C:\Program Files (x86)\Rockwell Software\RSBizWare) 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.

The following Metrics Server Manager-specific settings can be stored in the file:

The Metrics Server Manager settings file



Value name (units) Default value

Description Location in pre-RSBizWare 9.0 software

LogLocation ServerCalls (On or Off)

On Turns the application-specific informational and debug-level logging on or off for function calls at the global server level.

The LogLocation registry value, with bit 1 set in the hexadecimal bitmask.

LogLocation RSSqlThreadGeneral (On or Off)

Off Turns the application-specific informational and debug-level logging on or off for general processing messages from the FactoryTalk Transaction Manager process thread.


LogLocation RSSqlRSLFileDetail (On or Off)

On Turns the application-specific informational and debug-level logging on or off for RSL file content messages from the FactoryTalk Transaction Manager process thread.


LogLocation ScheduleThread (On or Off)

Off Turns the application-specific informational and debug-level logging on or off for Schedule thread messages.


LogLocation CalcThreadGeneral (On or Off)

On Turns the application-specific informational and debug-level logging on or off for general processing messages in the Calculator thread.


LogLocation CalcThreadSchedule (On or Off)

Off Turns the application-specific informational and debug-level logging on or off for time pattern schedule processing messages in the Calculator thread.


LogLocation CalcThreadData Details (On or Off)

On Turns the application-specific informational and debug-level logging on or off for data processing messages from the Calculator thread.


LogLocation CalcThreadCalculation (On or Off)

On Turns the application-specific informational and debug-level logging on or off for OEE calculation messages in the Calculator thread.


LogLocation CalcThreadEvent Detail (On or Off)

On Turns the application-specific informational and debug-level logging on or off for event processing messages in the Calculator thread.


LogLocation CalcThreadFault Metrics (On or Off)

Off Turns the application-specific informational and debug-level logging on or off for fault metric calculation messages in the






Calculator thread. LogLocation CalcThreadMachine State (On or Off)

Off Turns the application-specific informational and debug-level logging on or off for machine state calculation messages in the Calculator thread.


LogLocation ServerRequests (On or Off)

Off Turns the application-specific informational and debug-level logging on or off for server request handling.


LogLocation DataProcessing Queue (On or Off)

Off Turns the application-specific informational and debug-level logging on or off for data processing queue handling.


LogLocation Memory Management (On or Off)

Off Turns the application-specific informational and debug-level logging on or off for messages in the Memory Management thread.

This value did not exist in versions of the software prior to RSBizWare 9.0.

StartupRSLAgeLimit (Minutes) 10 Discards the first RSL file processed if it is as many minutes older than the current time as specified in the value.

The RSL Check Time Duration registry value.

InitializeFromSingle Timestamp (1 or 0)

1 1 - Initialize data collection from a single timestamp provided by the heart beat transactions and discard data that is older than the initializing time. 0 - Use all data regardless of the timestamp.

The Init Values Type registry value.

ShiftRecursion Duration (Minutes)

60 The amount of time used to recursively search for the start of the current shift.

The Shift Recurse Gap registry value.

Summarization Overlap (Seconds)

2 Summarization criteria changes that occur within this amount of time will be considered a single change and will not generate multiple summarizations.

The Summarization Gap registry value.

DataQueueSleep Threshold (# of Data Queue Items)

100 The number of items waiting to be processed. If the number is exceeded, the Calculator thread remains awake for a small amount of time not to consume all the CPU time. This is the number of items indicating that the server is busy enough so that it does not need to sleep.

The Sleep Threshold registry value.

DataQueueWarning Threshold (# of Data Queue Items)

500 or 5 * Sleep

The number of items waiting to be processed. When the number is reached, a

This value was hardcoded in previous versions of the software.





warning log message is generated and the database update rate is changed to the configured warning state update rate.

DataQueueError Threshold (# of Data Queue Items)

1000 or 10 * Sleep

The number of items waiting to be processed. When the number is reached, an error log message is generated and the database will only be updated when summarizations occur.


DatabaseUpdate Interval (Seconds)

30 The frequency with which the Calculator thread will update the database with calculated values during normal processing.


WarningDatabase Update Interval (Seconds)

300 The frequency with which the Calculator thread will update the database with calculated values while the server is in a warning state.

This value did not exist in versions of the software prior to RSBizWare 9.0.

EnabledWorkcell PollingRate (Minutes)

10 The frequency with which the Metrics Server Manager checks the database for newly enabled or disabled workcells.


PartCountBuffering Duration (Seconds)

10 The frequency with which the Calculator thread will buffer part counts before performing an OEE calculation operation.


MaxMemoryUsage (KB) 0 No limit The 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 the value to zero means no limit. Any value below 50,000 will be ignored.

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.

MinMemoryProcess Duration (Minutes)

5 The Metrics Server Manager tracks the number of records in each RSL file and the time during which the RSL file was processed to determine the amount of memory needed for the amount of time specified. The server will keep enough memory to process data for as many minutes as specified in the value and may release memory back to the system when

This value did not exist in versions of the software prior to RSBizWare 9.0. This variable was created to allow the server to release unused memory back to the operating system.





more memory has been allocated to process a large influx of RSL files.


Chapter 8

Controll access to your RSBizWare system

In this chapter you will learn about the types of activations and privileges available for the RSBizWare suite.

In order to assign activations, you need first to:

1. Install FactoryTalk Activation.

For details, see:

Step 4: Install FactoryTalk Activation

2. Configure FactoryTalk Activation.

For details, see:


3. Register the RSBizWare servers.

For details, see:




Activation and security activities are performed in the following components of the RSBizWare suite:

Activity: Performed in: Creating user groups and users FactoryTalk Administration Console

See "Step 12: Configure FactoryTalk groups and users".

Chapter 8 Controll access to your RSBizWare system


Activity: Performed in: Assigning server activations Service Console

See "Step 17: Assign activations to RSBizWare servers".

Assigning client activations to users Service Console See "Step 18: Assign client activations to users".

Assigning application privileges to users and groups

Service Console See "Step 19: Assign application privileges to users (page 84)".

Assigning default object permissions to users and groups

Service Console. See "Configuring default object permissions (page 242)".

Assigning custom object permissions to users and groups

Configuration Console. See the Configuration Console online help, section "Set permissions".

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.

The following activation types are available for FactoryTalk Metrics and FactoryTalk Historian Classic:

• Server activations.

• Client activations:

• Runtime client activations.

• Author client activations.

Software activation options

Controll access to your RSBizWare system Chapter 8


Server activations are based on the total number of activity areas that are monitored by FactoryTalk Metrics. The activity areas may be workcells, lines, areas, sites, and/or enterprises.

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 server activations include new activations for the Manual Data Editing (MDE) workcells. The licenses are required to:

• Create manual workcells without using any data points during the configuration.

• Create manual events that have no link with data points.

NOTE If there is no valid MDE activation, or the limit of available MDE activations is exceeded, a warning message appears.

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.

Server activations are 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.

Server activations are cumulative up to the 70,000 reporting tag limit. For example, you can install a 1500 reporting tag activation as

Server activations for FactoryTalk Metrics

Server activations for FactoryTalk Historian Classic



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.

To view the total number of licensed reporting tags:

1. Open the Configuration Console.

2. On the Tools menu, click FactoryTalk Historian > Manager Time-Series Reporting Tags.

The Time-Series Reporting Tags dialog box appears.

At the bottom of the dialog box, in the Total Tags Licensed box, the total number of licensed reporting tags is displayed.

Client activations 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 Runtime Client activations

The RSBizWare Runtime client activations allow users to view FactoryTalk Historian Classic and FactoryTalk Metrics reports interactively using Microsoft Internet Explorer, the

Client activations for FactoryTalk Metrics



Configuration Console, or RSBizWare ActiveX controls embedded in other applications like RSView32.

The activations are assigned to an Information Services Manager 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.

The following types of the RSBizWare Runtime Client activations are available:

• Single-User Runtime Client activations

Assign these activations to the Information Services Manager in sufficient quantity to accommodate the total number of concurrently connected Runtime users.

• Unlimited-User Runtime Client activation

Assign these activations to the Information Services Manager if you want to allow any number of users (limited by hardware availability and network performance) to connect concurrently.

This option is recommended if a large number of concurrent users is expected.

• FactoryTalk Metrics Author activations

The Author activations are single-user activations that add 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 Metrics Server Manager activation.

The FactoryTalk Metrics Author activations are assigned to individual user accounts. However, these activations determine the total number of concurrent users who are permitted to log on 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 on 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 administrator’s discretion.

Client activations 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 Runtime Client 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.

The activations are assigned to an Information Services Manager 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.

The following types of the RSBizWare Runtime Client activations are available:

• Single-User Runtime Client activations

Assign these activations to the Information Services Manager in sufficient quantity to accommodate the total number of concurrently connected Runtime users.

Client activations for FactoryTalk Historian Classic



• Unlimited-User Runtime Client activation

Assign these activations to the Information Services Manager if you want to allow any number of users (limited by hardware availability and network performance) to connect concurrently.

This option is recommended if a large number of concurrent users is expected.

• FactoryTalk Historian Classic Author activation

The Author activations are single-user activations that add the ability to configure FactoryTalk Historian Classic data collection, develop custom reports, and publish them for use by runtime users.

One FactoryTalk Historian Classic Author activation is included with each FactoryTalk Historian Classic Server activation.

FactoryTalk Historian Classic Author activations are assigned to individual user accounts. However, these activations determine the total number of concurrent users who are permitted to log on and perform authoring functions at the same time. This allows the System Administrator to assign all potential authoring users a FactoryTalk Historian Classic Author activation provided the concurrent number of logged on authors does not exceed the total number of FactoryTalk Historian Classic 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 administrator’s discretion.

Let’s say our 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.

Example: FactoryTalk Metrics activation



We have:

• 30 runtime users across all shifts, 10 of which could be concurrently logged on (based on shift).

• 6 authoring users across all shifts, 2 of which could be concurrently logged on (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 users—10 of which are runtime-only users, and an additional 2 users are authoring/configuring. Remember that 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).



Let’s say our 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.

We have:

• 30 runtime users across all shifts, 10 of which could be concurrently logged on (based on shift).

• 6 authoring users across all shifts, 2 of which could be concurrently logged on (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 Classic Server with 1,500 Reporting Tag Limit

• (1) 9358-HSTS2100 FactoryTalk Historian Classic 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 users—10 of which are runtime-only users, and an additional 2 users are authoring/configuring. Remember that each FactoryTalk Historian Classic 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:

Example: FactoryTalk Historian Classic activation



• The FactoryTalk Historian Classic Server activations and the 10 RSBizWare Runtime Client activations are assigned to the appropriate Information Services Manager.

• A FactoryTalk Historian Classic Author activation is assigned to each of the 6 authoring users (2 per shift).

FactoryTalk Historian 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 for Batch activations to specific servers. However, you will need to assign your FactoryTalk Historian Classic server activation to a server and your RSBizWare client activation to users.

There are the following types of activation options:

• FactoryTalk Historian for Batch module for 3 units

Use this activation for systems with up to three S88 defined units.

The activation includes a FactoryTalk Historian Classic Server with 150 Reporting Tag Limit activation and an RSBizWare Single-User Author Client activation.

• FactoryTalk Historian for Batch module connection to 1 Batch Server

Use this activation for systems with a single Batch Server.


• FactoryTalk Historian for Batch module connection to 1-3 Batch Servers

Use this activation for systems with up to three Batch Servers.

FactoryTalk Historian for Batch activation options




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.

The process of creating FactoryTalk users was already discussed in the following sections:

• "Step 12: Configure FactoryTalk groups and users"

• "Configure Windows-linked FactoryTalk users (page 62)"

• "Configure FactoryTalk users (page 66)"

In this chapter you will learn how to:

• "Configure FactoryTalk user groups (page 235)"

• "Configure Windows-linked user groups (page 237)"

• "Update the Service Console with users and groups changes (page 239)"

To create a FactoryTalk user group:

1. Open the FactoryTalk Administration Console.

2. Expand System > Users and Groups.

Manage FactoryTalk user groups and users

Configure FactoryTalk user groups



3. Right-click the User Groups folder, and then click New > User Group.

The New User Group dialog box appears.

4. In the Name box, type a name for the group.

5. In the Description box, type a description of the group.

6. Click Add.

The Select User or Group dialog box appears.



7. Select the user accounts which you want to assign as members of the group, and then click OK.

8. In the New User Group dialog box, click OK.

The new user group appears under User Groups.

9. Update the Service Console with users and groups changes

(page 239) to propagate the changes.

NOTE If you decide to add users to the Administrators group in the FactoryTalk Administration Console, bear in mind that all the FactoryTalk Security user accounts that belong to this group will automatically gain full permissions on all RSBizWare objects (reports, report data sources, report objects, and filters).

NOTE To access Quick Web as a Windows-linked user, a user must have Windows login access rights to the computer running the Information Services Manager.

To add a Windows-linked user group:

1. Open the FactoryTalk Administration Console.

2. Expand System > Users and Groups.

3. Right-click the User Groups folder, and then click New > Windows-Linked User Group.

The New Windows-Linked User Group dialog box appears.

Configure Windows-linked user groups



4. Click Add.

The Select Groups dialog box appears.


• Under Enter the object names to select, type one or more names of groups, separated by semicolons, and then click Check Names to validate the names.

• Click Advanced, and then search and select the groups in the Select Groups dialog box.

6. Click OK.

7. In the New Windows-Linked User Group dialog box, click

OK.

The new linked user group appears under User Groups.



8. Update the Service Console with users and groups changes

(page 239) to propagate the changes.

If you want group level permissions to take effect on individual users that are added to or removed from the group, refresh the Users and Groups pane in the Service Console.

To refresh the Users and Groups pane in the Service Console:

1. Open the Service Console.

2. Expand Security Services Manager > Administration.



TIP Only the FactoryTalk groups that have at least one user assigned to them will be displayed under Groups.

Update the Service Console with users and groups changes


Chapter 9

Manage user access

Client activations control the functions that 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.

The process of managing user access was already discussed in the following sections:

• "Step 18: Assign client activations to users"

• "Step 19: Assign application privileges to users (page 84)"


In this chapter you will learn about:

• "Assign application privileges to groups (page 241)"

• "Assign object permissions to users and groups (page 242)"

To assign application privileges to groups:




4. In the right pane of the window, under Groups, click the group name for which you want to assign application privileges.

5. Click Edit Group Properties.

Assign application privileges to groups

Chapter 9 Manage user access





8. Under Place a check..., select the check box to the left of the privilege that you want to assign to the group.

9. Click OK.

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. For details, see "Step 12: Configure FactoryTalk groups and users".

Object 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 permission for which users and groups can be given privileges is the ability to edit a particular report object.

There are the following types of object permissions:

• Default object permissions (page 242).

• Custom object permissions (page 246).

You may set the baseline permissions that will be given to a certain group or user for every instance of an object type that is created.

For example, if you want the user "JLSmith" to have permission to edit every report object that is ever created, you need to set the "Edit Report Object" default security for JLSmith for the "Report Object" object.

There are the following types of permissions available:

• Filter permissions

Assign object permissions to users and groups

Configure default object permissions

Manage user access Chapter 9


• Report permissions

• Report data source permissions

• Report object permissions (page 244)

There are the following filter permissions:

Item Description Delete Filter Allows the selected users or groups to delete the filter.

Author Licenses only. Edit Filter Allows the selected users or groups to make changes to the filter.

Author Licenses only. Edit Filter Security Allows the selected users or groups to grant security permissions for

the filter to other users or groups. Author Licenses only.

View Filter Allows the selected users or groups to view the filter.

There are the following report permissions:

Permissions Description Delete Report Allows the selected users or groups to delete the report.

Author Licenses only. Edit Report Allows the selected users or groups to make changes to the report.

Author Licenses only. Edit Report Security Allows the selected users or groups to grant security permissions for

the report to other users or groups. Author Licenses only.

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.

Filter permissions

Report permissions



There are the following report data source permissions:

Item Description 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.

Delete Report Data Source Allows the selected users or groups to delete the report data source. Author Licenses only.

Edit Report Data Source Allows the selected users or groups to make changes to the report data source. Author Licenses only.

Edit Report Data Source Security

Allows the selected users or groups to grant security permissions for the report data source to other users or groups. Author Licenses only.

View Report Data Source Allows the selected users or groups to view the report data source.

There are the following report object permissions:

Permission Description Delete Report Object Allows the selected users or groups to delete the

report object. Author licenses only.

Edit Report Object Allows the selected users or groups to make changes to the report object. Author licenses only.

Edit Report Object Security Allows the selected users or groups to grant security permissions for the report object to other users or groups. Author licenses only.

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.

Report data source permissions

Report object permissions

Manage user access Chapter 9


To grant permissions:

1. In the Service Console, expand the Information Services Manager tree item, and then click Default Permission Settings.

In the right pane of the window, a list of default permission settings appears.

2. Select the object type for which you want to set the default

permissions, and then click Permissions.

The Default Object Security dialog box appears.

3. Click the Users tab.

4. Expand the tree item for the user for whom you want to assign default permissions.

5. Select the check boxes to the left of the default permissions that you want to grant to the user.

Grant default object permissions



6. Repeat the steps for other users (the Users tab), users groups

(the Groups tab), and the general access (the Everyone tab).

7. Click Save.

After you have assigned default permissions for a type of object, the creator of a new object of that type may choose to customize the permissions for his object by revoking a user’s permissions for his new object or granting permissions for his new object to a user who does not have the default permission.

For example, if JLSmith was given the default "Edit Report Object" permission, we can create a new report object and revoke JLSmith’s 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 another user, LMJones, allowing Jones to edit our report object regardless of whether he has the default "Edit Report Object" permission.

Custom object permissions are assigned to users and groups in the Configuration Console. For details, see the Configuration Console online help, section "Configure permissions for an object".

Configure custom object permissions


Chapter 10

Configure data collection

The basic configuration of the data collection was already discussed in the following sections:

• "Step 20: Register FactoryTalk Transaction Manager (page 87)"

• "Step 21: Define FactoryTalk Transaction Manager configurations"

• "Step 22: Register FactoryTalk Transaction Manager configurations (page 93)"

In this chapter you will learn about:

• "Types of control connectors for the data collection (page 247)"

• "Types of enterprise connectors for the data collection (page 248)"

• "Unregister FactoryTalk Transaction Manager configurations (page 249)"

• "Start and stop FactoryTalk Transaction Manager configurations (page 252)"

• "Troubleshoot (page 253)"

The FactoryTalk 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.

You can use the following types of control connectors:

Types of control connectors for the data collection

Chapter 10 Configure data collection


Item Description 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.

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 Live Data to communicate with FactoryTalk Live Data 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.

The FactoryTalk 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.

You can use the following types of enterprise connectors:

Item Description 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 locally install SQL*NET 2.3x or later, Net8, or Oracle Net services (all from Oracle). You can then connect to an Oracle database versions 9i through 11g.

Types of enterprise connectors for the data collection

Configure data collection Chapter 10


Item Description Microsoft OLE DB The Microsoft OLE DB enterprise database connector should only be

used for interfacing with Microsoft SQL Server. Microsoft OLE DB allows you to browse an SQL Server 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 system 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 (page 273)".

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.

Unregister FactoryTalk Transaction Manager configurations



To unregister a FactoryTalk Transaction Manager configuration:


2. Expand Security Services Manager > Servers > Information Services Manager > Data Collection.

3. Right-click the FactoryTalk Transaction Manager configuration, and then click Stop Configuration.

4. Wait until the configuration is stopped.

The traffic light icon next to the configuration changes to .

5. Right-click the FactoryTalk Transaction Manager configuration, and then click Unregister Configuration.


6. Click Yes.

The FactoryTalk Transaction Manager Registration Removal Wizard appears.

7. Click Next.

8. On the Which RSBizWare Application page, select the applications from which you want to unregister the configuration.



9. Click Next.

If you are unregistering a configuration from FactoryTalk Historian Classic, the Historical Data dialog box appears.


• Leave the Delete all historical data... check box cleared, if you do not want to delete the data. Your users will still be able to report on the data.

This is the default setting.

• Select the Delete all historical data... check box, if you want to delete the data that has been collected using this configuration. Your users will not be able to report on the data.

11. Click Next.



12. Click Finish.

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, refer to the FactoryTalk Historian Classic User Guide.

For information on defining performance parameters, refer to the FactoryTalk Metrics User Guide.

After transactions have been created in the FactoryTalk Transaction Manager configuration, the configuration must be started for data collection to occur.

To start a configuration:


2. Expand Security Services Manager > FactoryTalk Transaction Manager Configurations > FactoryTalk Transaction Manager.

3. Right-click your configuration, and then click Start Configuration.


To stop a configuration:



Start and stop FactoryTalk Transaction Manager configurations



3. Right-click your configuration, and then click Stop Configuration.


TIP For more information on traffic light icons, see "Start and stop RSBizWare servers (page 215)"

You can view the transaction statistics of a running configuration, which are useful for determining the source of problems when they occur.

To view the transaction statistics:



3. Click the configuration for which you want to view transaction statistics.

The configuration data and statistics appear in the right pane of the window.

Transaction statistics include the following:

This item: Displays: 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.

Troubleshoot



This item: Displays: 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.


Chapter 11

Report diagnostic messages

When an RSBizWare service is running, it generates diagnostic reporting messages that are useful for determining the source of problems when they arise.


• Types of diagnostic messages 255

• Ways of logging diagnostic messages 256

• Configure server log files 256

• View diagnostic logs 259

An RSBizWare service may produce the following types of diagnostic reporting messages:

Message type Description 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.

Types of diagnostic messages

Chapter 11 Report diagnostic messages


You can log diagnostic messages using:

• Log files

Choose this method, if you want the diagnostic messages to be written directly to a text file.

• Microsoft Event Viewer

Choose this method, if you want the diagnostic messages to be sent to the Windows Log, and viewed in the Event Viewer on the server computer.

• E-mail

Choose this method, if you want the diagnostic messages to be sent via e-mail. Your system administrator will be automatically notified when the server produces diagnostic messages of a certain type.

For details, see "Configure server log files (page 256)" and "View diagnostic logs (page 259)".

To configure the log file:



3. Click Configure Diagnostic Logs.

The diagnostic log configuration appears in the right pane of the window.

Ways of logging diagnostic messages

Configure server log files

Report diagnostic messages Chapter 11


4. In the Log File Source list, select the name of the server or

configuration for which you want to configure the log file.

5. In the Location box, either leave the default location of the file or choose another location.

6. In the Number of Messages, Max File Size, and Buffer Size boxes, either leave the default values, or change them.

When choosing other values, keep the following in mind:

• Depending on the type of logging options that you choose and the activity level of the server, the log files can become very large. The Number of Messages and Max File Size values will limit the size of the log file. 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 the Buffer Size can improve server performance, but it may prevent you from seeing diagnostics messages in near-real time. Using the



Buffer Size of zero will turn off all buffering so that diagnostic messages are written as events occur.

7. In the Number of log file revisions to keep box, type the number of revisions of the log file that you want to store for diagnostic purposes. Keep the following in mind:

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

8. Under Logging Options, select the check boxes under each type of the diagnostic messages to associate them with the available ways of logging the messages.

NOTE: Since the servers and FactoryTalk Transaction Manager configurations produce a large quantity of debug messages, selecting the Debug option can significantly increase the size of the log file, and significantly affect performance. This option is not recommended unless you are trying to troubleshoot a problem.

9. In the From Address box, type the e-mail address from which you want the log report e-mails to be sent.

10. In the To Address box, type the e-mail address to which you want to the log report e-mails to be sent.

11. In the Password box, type the password for the e-mail address that you provided in the From Address box.

12. In the SMTP Server box, type the name of the outgoing e-mail server to be used for sending the log report e-mails.

13. Click Apply.

14. Restart the server or the configuration for which you have set the log file configuration.

Report diagnostic messages Chapter 11


To view diagnostic logs of a server:


2. Expand Security Services Manager > Servers.

3. Click the server for which you want to view the log file.

4. In the right pane of the window, click View Log.

To view diagnostic logs of a configuration:



3. Click the configuration for which you want to view the log files.

4. In the right pane of the window, click View Configuration Log File or View Merged Log File.

View diagnostic logs


Appendix A

Advanced topics


• Remote connection to an RSBizWare server 261

• Register the Excel Add-in 262

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

Open this port: To communicate with: 4120 Information Services Manager 4121 Security Services Manager 4122 Metrics Server Manager 4123 Report Schedule Manager 402 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

Remote connection to an RSBizWare server

Appendix A Advanced topics


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.

TIP For information on using the Excel Add-in, see the FactoryTalk Metrics User Guide and the FactoryTalk Historian Classic User Guide.

The Excel Add-in, which enables you to retrieve RSBizWare data directly into Microsoft Excel, is installed during the installation of the RSBizWare suite.

However, the installation of the Excel Add-in only registers the component for the user that is performing the installation. Other users that intend to use the add-in should manually register it for themselves.

To register the Excel Add-in:

1. Open the RSBizWare installation DVD.

2. Go to the Support folder.

3. Copy the ExcelAddIn.reg file to the computer.

4. Double-click the file.


Register the Excel Add-in

Advanced topics Appendix A


5. Click Yes.


6. Click OK.

Appendix A Advanced topics



Appendix B

Database tips


• Maintain frequently used RSBizWare tables and indexes 265

• Use Oracle with RSBizWare 266

There are certain RSBizWare database objects - tables and indexes - that are frequently used by RSBizWare database views. The database views are, in turn, used by most RSBizWare reports.

The frequent use of these database objects may result in the following:

• Indexes can become fragmented.

• Log files can become very large.

• Tablespaces can fill up.

In order to prevent the report performance from degrading, the following database maintenance should be performed on a regular basis:

• Adding separate tablespaces.

• Partitioning.

• Adding additional data files.

• Purging older data.

Maintain frequently used RSBizWare tables and indexes

Appendix B Database tips


The following table lists the frequently used RSBizWare tables and indexes, as well as the RSBizWare components that use them.

Frequently used RSBizWare tables and indexes

Table Index Component RSDataPointSample RSDataPointSample_IDX1

FactoryTalk Historian Classic RSSQL_CMPCOMPRESS RSSQL_CMPCompress_IDX1 OEEEvent OEEEvent_IDX1

OEEEvent_IDX2 OEEEvent_IDX3 OEEEvent_IDX4 OEEEvent_IDX5 OEEEvent_IDX6 OEEEvent_IDX7 OEEEvent_IDX8 FactoryTalk Metrics

OEEStateData OEEState_Data_IDX1 OEEWorkcell OEEWorkcell_IDX1

OEEWorkcell_IDX2 OEEWorkcell_IDX3 OEEWorkcell_IDX4 OEEWorkcell_IDX5

The FactoryTalk Historian Classic and FactoryTalk Metrics 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 time-series analysis capabilities of the FactoryTalk Historian Classic application.

Use Oracle with RSBizWare

Database tips Appendix B


In this section you will learn about the following:

• Create tablespaces 267

• Configure the database user 267

• Create a Net Configuration connection 268

• Configure the Oracle ODBC data source 269

The tablespaces for the RSBizWare installation should contain:

• Data

• Index

• Temp

• Rollback segments

The RSBizWare data model will be loaded into the default tablespace of the user initializing the database. It is recommended that you use Oracle Change Management utilities to move indexes and keys to the index tablespace that you create.

For details, refer to the Oracle documentation.

The database user, who will be the owner of the RSBizWare schema, should have the privileges for creating:

• Procedures

• Public synonyms

• Sessions

• Sequences

Recommended database settings

Create tablespaces

Configure the database user



• Synonyms

• Tables

• Triggers

• Views

The user should also be configured to use the following tablespaces:

• Data. Default tablespace, quota unlimited.

• Index. Quota unlimited.

• Temp. Temporary tablespace.

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.

To create a new Net Configuration connection:

1. Name your Net Configuration connection. For example, BW.

2. Select the TCP/IP (Internet Protocol) connection.

3. Type the host name of the computer on which your Oracle database is running.

4. Accept the default port 1521.

5. Name the service. For example, BW.

6. Test your connection.

Create a Net Configuration connection



RSBizWare services connect to Oracle using ODBC. Use the ODBC Data Source Administrator to create a new ODBC connection.

To create a new ODBC connection to Oracle:

1. Open Data Sources (ODBC) from the Administrative Tools.

The ODBC Data Source Administrator dialog box appears.

2. Click the System DSN tab.

3. Click Add.

The Create New Database Source dialog box appears.

4. Select the Oracle ODBC Driver.

5. Give the data source a name and description. For example, RSBizWare, and RSBizWare database.

6. Type the service name and the Oracle user name that you defined in the Net Configuration connection.

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 should help you improve performance using FactoryTalk Historian Classic 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.

Configure the Oracle ODBC data source

Tune the Oracle database for FactoryTalk Historian Classic



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.

• ROLLBACK Tablespace:


• Turn Auto Extend ON.


• INDEX Tablespace:



• Turn the Auto Extend ON.


• TEMPORARY Tablespace:



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

Improve the performance of your RSBizWare Oracle database



• Set sort_area_size to 2000000.

• Set sort_area_retained_size to 1000000.

After you configured the tablespaces and the init.ora file, you can complete the configuration of your Oracle database.

Do the following:

1. Restart the Oracle service for your database.

For details, refer to your Oracle documentation.

2. Create a Net Configuration connection.

For details, see "Create a Net Configuration connection (page 268)".

3. Create the Oracle ODBC data source.

For details, see "Configure the Oracle ODBC data source (page 269)".

4. Start the Information Services Manager in the Service Console.

For details, see "Start and stop RSBizWare servers (page 215)".

Prepare to run the Oracle database


Appendix C

Data compression

The Time-series Data Compression Enterprise Connector stores time-series data in a predefined compressed format in either an Oracle or a Microsoft SQL Server database. The compressed data point records contain binary data that can only be viewed through the FactoryTalk Historian Classic application.

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 server’s hard disk), there is a finite amount of data that can be stored. As a result, the user must be mindful of the amount of stored data, the frequency of data storage, 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 every 10 seconds. The disk space used after a year can be estimated as follows:

Without compression, after the amount of logged data approached the disk capacity, the user would typically 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.

Benefits of using the data compression

Appendix C Data compression


Aside from the maintenance considerations involved in 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.

The following diagram explains the way the data compression works:

The Time-series Data Compression Enterprise Connector is designed to capture time-series 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, with the use of the Time-series Data Compression Enterprise Connector, a user-configured number of data point samples will be collected,

How the data compression works

Data compression Appendix C


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 maximum and minimum 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.

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 with a block size of 256:

Signal type Compression ratio Steady State 15:1

Saw Tooth 7:1

Random 3:1

Compression ratio



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 uncompressing 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 RSBizWare database.

Before using the SQL Server Uncompress view, you need to grant the EXECUTE permissions to the public user for the following stored procedures:

• sp_OACreate

• sp_OADestroy

• sp_OAGetErrorInfo

• sp_OAMethod

• sp_OAStop

To grant the EXECUTE permission for a stored procedure:

1. Open the SQL Server Management Studio.

2. In the Object Explorer, expand Databases > System Databases > master > Programmability > Extended Stored Procedures > System Extended Stored Procedures.

3. Under System Extended Stored Procedures, locate the stored procedure, for example sp_OACreate.

4. Right-click the procedure, and then click Properties.

The Extended Stored Procedure dialog box appears.

View compressed data

Prepare the SQL Server uncompress view



5. Under Select a page, click Permissions.

6. In the right pane of the window, click Search.

The Select Users or Roles dialog box appears.

7. Under Enter the object names to select, type public, and then click Check Names.

8. Click OK.

The name appears under Users or roles.

9. Under Permissions for public, select the Grant check box for the Execute permission.

10. Click OK.

11. Repeat the steps for the other stored procedures.

To query the data from the Uncompress view, use the following stored procedures in the SQL Server Query Analyzer:

Use this stored procedure: To specify: spSetUncompressTimeRange <start date/time, end date/time>

The time range for which data will be returned.

spSetUncompressReportingTag <reporting tag name>

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.

Query the SQL Server uncompress view



The time range and/or reporting tag name that you specify in these stored procedures are kept in the UncompressReportingTags and UncompressTimeRange worktables. To clear the values from the worktables for the current Query Analyzer session, use the following stored procedures:

Use this stored procedure: To clear: spClearUncompressTimeRange The time range from the worktable that is

created by the spSetUncompressTimeRange stored procedure.

spClearUncompressReportingTag The reporting tag name from the worktable that is created by the spSetUncompressReportingTag stored procedure.

For example:

spSetUncompressTimeRange '01-28-2013 18:00:00', '01-28-2013

18:07:00'

go

spSetUncompressReportingTag 'Injection Molding Pressure -

Compression'

go

select *

from Uncompress

where tTimestamp >= '01-28-2013 18:00:00'

and tTimestamp <= '01-28-2013 18:03:00'

go

spClearUncompressTimeRange

go

spClearUncompressReportingTag

go

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 you attempt to chart the compressed data using the RSBizWare time series report object, there may not yet be any data in the database for the report

Data compression considerations



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 in order to display your data.

If the data cannot reach the database server, the Data Compression service caches its data on the local hard disk until the database becomes 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 the services are shut down manually, the data may not be written to the database until the configuration is started again.


Appendix D

Application notes for FactoryTalk Transaction Manager


• Set the real-time clock in a ControlLogix processor using FactoryTalk Transaction Manager 282

• Send date/time information from a ControlLogix processor to a database 285

• Special considerations for a distributed Microsoft COM+ application 287

• Enable network COM+ access for COM+ connectors in FactoryTalk Transaction Manager 288

• Configure the Oracle 10g Instant Client for FactoryTalk Transaction Manager 288

• Configure FactoryTalk Transaction Manager Connectivity to SQL Server using Windows authentication 289

• Data types supported by SQL Server 293

• Behaviors when setting substitution options for FactoryTalk data points 293

• Resolve IP address to host name issues 294

• Remove a Configuration Server computer from FactoryTalk Transaction Manager 295

• Start and stop FactoryTalk Transaction Manager services manually 296

• Considerations for distributed configurations 297

Appendix D Application notes for FactoryTalk Transaction Manager


• Considerations for copying and pasting FactoryTalk data points 298

• Windows Event Viewer tips 300

• Run RSLinx Classic as a service 301

• Data block support 301

• Sybase values 307

• Int64 Signed/Unsigned in the Expression Editor 307

• Int64 Signed/Unsigned as an output parameter in a stored procedure 308

• Substitute values for a data point 308

• Verify BigInt data types after FactoryTalk Transaction Manager update 308

• Restore default dialog box sizes 309

• Miscellaneous 309

You can use FactoryTalk Transaction Manager combined with a stored procedure to set a real-time clock in a ControlLogix processor. In this manner, you can use your database server to ensure a reasonable level of coordination between real-time clocks in various control processors in your system.

To complete this procedure, you must perform tasks in:

• The processor (page 283).

• The database (page 283).

• The FactoryTalk Transaction Manager configuration (page 285).

For more information and sample files, go to the Rockwell Automation Knowledgebase Web site

Set the real-time clock in a ControlLogix processor using FactoryTalk Transaction Manager

Application notes for FactoryTalk Transaction Manager Appendix D


(http://www.rockwellautomation.com/support/) and search for ID 23299.

In the processor, define the following:

• A 16-bit integer (for example, Result).

• An array of 7, 32-bit integers (for example, Current).

• An array of 7, 32-bit integers (for example, New).

• Ladder logic to set the processor's wall-clock time when Result.0 = 1 and Result.1 = 0.

• Ladder logic to read the processor's wall-clock time into the current array.

In the database, define a stored procedure that reads the system clock and sends outputs as a byte-swapped varbinary(12) string.

The following is a sample SQL script for creating a stored procedure which reads the current time in the controller, compares it to the system time, and writes back the server's current time. The stored procedure can be reworked slightly to log the difference between the processor and computer real-time clocks (if desired).

NOTE This SQL script is for Microsoft SQL Server 2000 only. Other databases will require modified scripts to function properly.

SET QUOTED_IDENTIFIER OFF

GO

SET ANSI_NULLS ON

GO

CREATE PROCEDURE logix5000time (

-- @control_id AS INT, --uncomment this line if you wish to log the time difference

@control_time_in AS DATETIME,

@control_time_out AS VARBINARY(24) OUT

) AS

DECLARE @system_time as datetime,

@difference as int,

In the processor

In the database

http://www.rockwellautomation.com/support/



@tbin0 AS VARBINARY(4),





@tbin5 AS VARBINARY(4)

/* check current time */

SELECT @system_time = GETDATE();

/* Uncomment this section and create the ControllerTimeDiff table if you

wish to log the difference */

/*

SELECT @difference = DATEDIFF(second,@control_time_in,@system_time);

INSERT INTO [dbo].[ControllerTimeDiff]

( [ControllerID],[ControllerTime],[SystemTime],[Difference])

VALUES ( @control_id, @control_time_in, @system_time, @difference);

*/

/* output the current system time to the controller */

SELECT @tbin0 = DATEPART(year,@system_time);

SELECT @tbin1 = DATEPART(month,@system_time);

SELECT @tbin2 = DATEPART(day,@system_time);

SELECT @tbin3 = DATEPART(hour,@system_time);

SELECT @tbin4 = DATEPART(minute,@system_time);

SELECT @tbin5 = DATEPART(second,@system_time);

/* this select statement handles the byte swapping necessary to output a block of

32 bit integers to the controller. As you can see you must swap the high and

low bytes in each word, and the high and low word in each 32 bit integer. */

SELECT @control_time_out =

(SUBSTRING(@tbin0,4,1)+SUBSTRING(@tbin0,3,1)+SUBSTRING(@tbin0,2,1)+SUBSTRING(@tbin0,1,1))+





(SUBSTRING(@tbin5,4,1)+SUBSTRING(@tbin5,3,1)+SUBSTRING(@tbin5,2,1)+SUBSTRING(@tbin5,1,1));

GO

SET QUOTED_IDENTIFIER OFF



GO

SET ANSI_NULLS ON

GO

In FactoryTalk Transaction Manager, configure:

• A scheduled or device-scheduled data point defined as a signed short, pointing to the result tag.

• A scheduled or device-scheduled data point defined as PLC TimeStamp, pointing to Current[0],L6 with the size of 6 elements.

• A scheduled or device-scheduled data point defined as signed long, pointing to New[0],L6 with the size of 6 elements.

• A data object pointing to the stored procedure in the database.

Perform the steps described below for RSLogix 5000 and FactoryTalk Transaction Manager to send date/time information from a ControlLogix processor to a database:

• In RSLogix 5000 (page 285).

• In FactoryTalk Transaction Manager (page 286).

Perform the following steps:

1. Create a controller tag of the following type: SystemTimeDINT, style=decimal, Type =DINT[7]

2. Create a controller tag of the following type: SystemTimeINT, style=decimal, Type=INT[7]

3. In the ladder logic, add a rung with the instruction GSV.

Get system value CIP Object class: WALLCLOCKTIME CIP Object name: - Attribute name: DateTime

In FactoryTalk Transaction Manager

Send date/time information from a ControlLogix processor to a database

In RSLogix 5000



Get system value Dest SystemTimeDINT[0]

4. In the ladder logic, create 7 move instructions, which move:

• SystemTimeDINT[0] to SystemTimeINT[0]







The preferred connector for communicating with the ControlLogix processor is the Generic OPC connector, not the RSLinx Classic Connector. Beginning with RSLinx Classic 2.20.00, RSLinx Classic supports online browsing of the ControlLogix processor's memory to select data points.

The following example explains configuration for both the Generic OPC Connector and the RSLinx Classic Connector.

Perform the following steps:

1. Using the Generic OPC Connector, define the following:

Item Description Item String [topic]SystemTimeINT[0],L6 (where topic is the topic

defined in RSLinx Classic pointing to the ControlLogix processor).

Datapoint Name Either type in a unique name or let the system name the point for you automatically.

Access Path - Data Type PLC Timestamp Elements 6

In FactoryTalk Transaction Manager



2. Using the RSLinx Classic Data Points dialog box, define the following:

Item Description Item Address SystemTimeINT[0],L6 Datapoint Name Either type in a unique name or let the system name the

point for you automatically. Topic Use Default or the specific topic you have defined in RSLinx

Classic Data Type PLC Timestamp Elements 6

3. Create a transaction and bind the FactoryTalk Transaction Manager data point to a date/time field in the database (the actual data type may be called TIMESTAMP or DATE or DATETIME, depending on the database used).

If you are using a configuration that uses online edits, you can only distribute certain parts of the application across multiple computers. In a configuration that uses online edits via a COM+ enterprise connector, there are three main parts:

• Transaction Control Manager (TCM).

• The COM+ enterprise connector.

• The .DLL file written by the user.

If you wish to put the TCM and the COM+ enterprise connector on separate computers, then the user-written .DLL must be located on the same computer as the COM+ enterprise connector. If you have the TCM and the COM+ enterprise connector on the same computer, then the user-written .DLL can be located on a different computer. You cannot, however, locate the TCM, COM+ enterprise connector and the user-written .DLL on different computers.

The COM+ network access is disabled by default on Windows 2003 Standard Server computers. For details on how to enable it, see

Special considerations for a distributed Microsoft COM+ application



"Enable network COM+ access for COM+ connectors in FactoryTalk Transaction Manager (page 288)".

COM+ network access is disabled by default on Windows 2003 Server Standard Edition Server platforms. On these platforms, COM+ can be used only locally by default.

To enable the network COM+ access for COM+ connectors in FactoryTalk Transaction Manager:

1. Open Control Panel.

2. In Control Panel, click Add or Remove Programs.

3. Click Add/Remove Windows Components.

4. Click Application Server, and then click Details.

5. Select the check box next to Enable network COM+ access, and then click OK.

6. Click Next, and then click Finish.

To configure the Oracle 10g R2 Instant Client:

1. Install the Oracle 10g R2 Instant Client with default settings.

2. Install the Oracle patch for defect #4951251.

NOTE If you do not install the Oracle patch for defect #4951251, FactoryTalk Transaction Manager will not find the Oracle SQLNet connections defined in the tnsnames.ora file.

3. Open the following directory:

c:\oracle\product\10.2.0\Client_1

4. In the Client_1 folder, create a new folder, Network.

5. In the Network folder, create a new folder, Admin.

6. From the database server system, copy the tnsnames.ora file to the Admin folder.

Enable network COM+ access for COM+ connectors in FactoryTalk Transaction Manager

Configure the Oracle 10g Instant Client for FactoryTalk Transaction Manager



7. Click Start > Run, type regedit, and then press Enter.

The Registry Editor appears.

8. Navigate to the following folder:

My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE

9. Right-click the folder, and then click New > String Value.

In the right pane of the window, a New Value #1 appears, available for editing.

10. Rename the value to Oracle_Home.

11. Double-click the value.

The Edit String dialog box appears.

12. In the Value data box, type: c:\oracle\product\10.2.0\Client_1

13. Click OK.

The following sections describe how to configure RSSql v7.00.00 and later and FactoryTalk Transaction Manager 12.00 and later connectivity to Microsoft SQL Server 2005 using Windows authentication.

These steps apply regardless of whether Microsoft SQL Server is configured with Windows-only authentication or with mixed mode (SQL Server and Windows) authentication.

To configure the SQL Server authentication in FactoryTalk Transaction Manager:



The Configuration Checklist window appears.

Configure FactoryTalk Transaction Manager Connectivity to SQL Server using Windows authentication

Configure the SQL Server authentication



3. In the Configuration List name, select the name of your configuration.


The Data Object Definition dialog box appears.

5. Next to the Database Connection box, click .

The Database Connection Definition dialog box appears.

6. In the User Name box, type the name of the RSBizWare SQL Server database user.

7. In the Password box, type the password for the RSBizWare SQL Server database user.

8. Click Test.

A confirmation message appears.

9. Click OK, and then click Apply.

To configure the Windows-only authentication for FactoryTalk Transaction Manager:

1. On the SQL Server computer, select Start > Programs > Microsoft SQL Server 2005 > SQL Server Management Studio.

The Microsoft SQL Server Management Studio appears.

2. In the Object Explorer tree, expand Security.



4. Next to the Login name box, click Search.

The Select User or Group dialog box appears.

5. Find the user that you want to add as the database user, and then click OK.

6. In the Login - New dialog box, click OK.

Configure the Windows-only authentication



7. In the Object Explorer tree, expand Databases > <Your database> > Security.

8. Right-click Users, and then click New Database User.

The Database User - New dialog box appears.

9. In the User name box, type a name for the user.

10. Next to the Login name option, click .

The Select Login dialog box appears.

11. Select the login that you created in steps 3-6.

12. Click OK.

13. In the Object Explorer tree, expand Databases > <Your database> > Tables.

14. Right-click the table for which you want to set the permissions, and then click Properties.

The Table Properties dialog box appears.

15. Under Select a page, click Permissions.

16. In the right pane of the window, click Search.

The Select Users or Roles dialog box appears.

17. Find the user that you created in steps 8-12.

18. Click OK.

19. Under Permissions, set the permissions for the user.

20. Click OK.

To configure the FactoryTalk Transaction Manager server computer:

1. Go to Start > Administrative Tools > Computer Management.

The Computer Management dialog box appears.

2. Expand System Tools > Local Users and Groups > Groups.

Configure FactoryTalk Transaction Manager for connections with SQL Server



3. To the Administrators group, add the same user that you added in "Configure the Windows-only authentication (page 290)".

4. Go to Start > Administrative Tools > Local Security Policy.

The Local Security Settings dialog box appears.

5. Expand Security Settings > Local Policies > User Rights Assignment.

6. In the right pane of the window, find and double-click Log on as a service.

The Log on as a service Properties dialog box appears.

7. Add the same user that you added in "Configure the Windows-only authentication (page 290)".

8. In the Computer Management dialog box, expand Services and Applications > Services.

9. In the right pane of the window, double-click FactoryTalk Transaction Manager Configuration Server.

The Properties dialog box appears.

10. Click the Log on tab.

11. Click This account.

12. Select the same user that you added in "Configure the Windows-only authentication (page 290)".



The Configuration Checklist window appears.

15. In the Configuration List name, select the name of your configuration.


The Data Object Definition dialog box appears.

17. Next to the Database Connection box, click .



The Database Connection Definition dialog box appears.

18. Make sure that the user and password boxes are blank.

The following data types are supported by SQL Server:

• bigint • binary • bit • char • datetime • datetime2 • decimal • float • image • int • money

• numeric • real • smalldatetime • smallint • smallmoney • sysname • text • tinyint • varbinary • varchar • varchar

Keep the following behaviors in mind when you are specifying substitution options for FactoryTalk data points.

NOTE The following behaviors assume that the device is properly connected when the transaction executes.

If you select this option: And the device is off at startup, then the transaction:

And the device is on at startup, then the transaction:

No Substitution Fails because a required data point was not available. For corrective action information, see the possible solution section for error 33080.

Fails because a required data point was not available. For corrective action information, see the possible solution section for error 33080.

Substitute Value Uses the specified substitute value and quality is set to 1.

Uses the specified substitute value and quality is set to 1.

Data types supported by SQL Server

Behaviors when setting substitution options for FactoryTalk data points



If you select this option: And the device is off at startup, then the transaction:

And the device is on at startup, then the transaction:

Substitute Previous Value Fails because a previous value for substitution did not exist. For corrective action information, see the possible solution section for error 33175.

Uses the previous substitute value and the quality is set to 1.

Use Bad Quality Uses the bad quality value provided by the data server.

Uses the bad quality value provided by the data server.

Use Substitution for Bad Quality Uses the substitution for bad quality value provided by the data server.

Uses the substitution for bad quality value provided by the data server.

Use Previous Substitution for Bad Quality Uses the previous substitution for bad quality value provided by the data server.

Uses the previous substitution for bad quality value provided by the data server.

In RSSql v8.00.00 and FactoryTalk Transaction Manager 12.00 or later, you can no longer enter IP addresses in the Add Configuration Server or FactoryTalk Transaction Manager Configuration dialog boxes. If you have been using IP addresses on these dialog boxes in RSSql v7.50.00 and earlier, you must change your configurations to use host names.

To resolve an IP address in a Windows Domain:

If you are working in a Windows Domain, perform the following steps:

1. In FactoryTalk Transaction Manager, replace the IP address with the appropriate host name.

2. At the command prompt, type: ping <host name for the computer>

For example: ping FactoryTalk Transaction ManagerServerA

3. View the output of this operation and verify that the IP address that is displayed matches the IP address that you used in your previous FactoryTalk Transaction Manager configuration.

Resolve IP address to host name issues



To resolve an IP address in a Windows Workgroup:

If you are working in a Windows Workgroup, perform the following steps:

1. Go to <Windows>\Systems32\Drivers\Etc.

2. Open the Hosts file in a text editor.

3. Type a host to ID mapping for each computer that is running FactoryTalk Transaction Manager.

4. Save the file.

5. At the command prompt, type: ping <host name for the computer>

For example: ping FactoryTalk Transaction ManagerServerA

6. View the output of this operation and verify that the IP address that is displayed matches the IP address that you used in your previous FactoryTalk Transaction Manager configuration.

After renaming a computer that FactoryTalk Transaction Manager is running on and adding a Configuration Server with the new computer name, the old computer name may continue to appear in the Configuration tree with a red slash. This condition occurs because the old computer name is no longer available on the network.

As a workaround, perform the following steps:

• In FactoryTalk Transaction Manager, right-click the configuration server that you want to remove, and then click Delete Configuration Server.

Remove a Configuration Server computer from FactoryTalk Transaction Manager



If it does not work, remove the old server manually:

1. In the Registry Editor, find HKLM\Software\Rockwell Software\RSSql\Configuration Servers\.

2. Delete the folder with the old computer name.

3. Restart FactoryTalk Transaction Manager

In some instances, it may be necessary to manually start or stop FactoryTalk Transaction Manager services from a DOS command prompt. The following table summarizes the FactoryTalk Transaction Manager service names and the associated name for that service as it appears in the Services list (accessible from Control Panel).

FactoryTalk Transaction Manager service name Displayed name rssql_cfg_server FactoryTalk Transaction Manager Configuration Server rssql_comp_storer FactoryTalk Transaction Manager Compression Server rssql_ddecoll FactoryTalk Transaction Manager DDE Connector rssql_lnxcoll FactoryTalk Transaction Manager RSLinx Classic Connector rssql_mts_storer FactoryTalk Transaction Manager COM+ Connector rssql_oci_storer FactoryTalk Transaction Manager OCI Enterprise Connector rssql_oledb_storer FactoryTalk Transaction Manager OLE DB Enterprise Connector rssql_opccoll FactoryTalk Transaction Manager OPC Connector rssql_pm_storer FactoryTalk Transaction Manager FactoryTalk Metrics Enterprise

Connector rssql_rnacoll FactoryTalk Transaction Manager FactoryTalk Connector rssql_rsvcoll FactoryTalk Transaction Manager RSView Connector rssql_storer FactoryTalk Transaction Manager ODBC Enterprise Connector rssql_tb FactoryTalk Transaction Manager service rssql_tmctrl FactoryTalk Transaction Manager Transaction and Control Manager

service

For example, if you want to start the FactoryTalk Transaction Manager Configuration Server from a DOS command prompt, type the following:

Start and stop FactoryTalk Transaction Manager services manually



net start rssql_cfg_server

Additionally, if you want to stop the FactoryTalk Transaction Manager service in the FactoryTalk Transaction Manager from a DOS command prompt, type the following:

net stop rssql_tb

You can distribute FactoryTalk Transaction Manager control and enterprise connectors among several computers. Keep the following points in mind when distributing FactoryTalk Transaction Manager connectors on multiple computers:

• UNC paths for configuration files cannot be used. The configuration files must be local to the Configuration Server. The configuration file path is defined in Step 1 of the Configuration Checklist in FactoryTalk Transaction Manager.

• FactoryTalk Transaction Manager must be logged into a Windows Server 2012/2008/2003 account that has administrative privileges in all computers that are part of the FactoryTalk Transaction Manager system. This is required for the Windows Server 2012/2008/2003 service control manager to be able to start and stop the FactoryTalk Transaction Manager services.

• The FactoryTalk Transaction Manager configurations that you create must use cache file paths and error logging paths that comply with the Universal Naming Convention (UNC). Each time you define a FactoryTalk Transaction Manager control connector or enterprise connector, you must indicate the host name of the remote computer on which that service will run. Additionally, you must assign that service to a user account with sufficient privileges to access UNC files on the applicable computers.

• If you have defined a connector to run on a remote computer, FactoryTalk Transaction Manager v9.00.00 or later will

Considerations for distributed configurations



browse that computer's OCI connections, ODBC DSNs, and most files. The only files that FactoryTalk Transaction Manager does not browse remotely are DDE and RSLinx Classic connector tag files.

• FactoryTalk Transaction Manager cannot query remote DDE servers to retrieve configured DDE topic information (excluding the RSLinx Classic OPC or RSView32 control connectors). When the generic DDE control connector is located on a remote computer, you can do one of the following to configure DDE topic names:

• Manually enter DDE topic names in the FactoryTalk Transaction Manager DDE Data Point Configuration dialog box.

• Install and configure the DDE server on both computers so that it can be automatically queried for topic names.

Keep the following in mind when copying and pasting FactoryTalk data points in the data point grid on the FactoryTalk Data Point dialog box.

Copying

Consider the following rules when copying FactoryTalk data points:

• You must use Ctrl+C.

• You can copy FactoryTalk data points in/from Microsoft Excel.

• You can copy multiple adjacent rows.

• You cannot copy multiple non-adjacent rows. If multiple non-adjacent rows are selected, all rows between the first and last row will be copied.

Considerations for copying and pasting FactoryTalk data points



• You cannot copy individual cells. If you attempt to copy an individual cell, the entire row (all columns, including internally hidden columns) will be copied.

• You cannot copy items when a configuration is running or if the configuration has pending edits.

Pasting

Consider the following rules when pasting FactoryTalk data points:

• You must use Ctrl+V.

• You can paste FactoryTalk data points in/from Microsoft Excel.

• You can paste one or more rows into the data point grid. All rows appear at the bottom of the data point grid. All internally hidden columns are ignored.

• You can paste existing data points into the data point grid. FactoryTalk Transaction Manager recognizes that the data points already exist and prompts you to:

• Modify the existing data point

• Create a new data point

• Cancel the paste operation

• You cannot paste one or more individual cells in a row.

• You cannot paste a data point that does not contain either a valid value or an empty string for the following collection parameter columns in the data point grid:

• Data type

• Mode

• Data valid units

• Data retrieval units

• Substitution policy



If these conditions are not met, the paste operation is terminated.

• You cannot perform a paste when a configuration is running or if the configuration has pending edits.

FactoryTalk Transaction Manager supports sending error messages to the Windows Event Viewer. If you have defined error logging in FactoryTalk Transaction Manager and no messages display when you view error log files, make sure you are looking in the Application event log in the Windows Event Viewer.

To trace a FactoryTalk Transaction Manager problem in the Windows Event Viewer:

1. Go to Start > Administrative Tools > Event Viewer.

2. The Event Viewer dialog box appears.

3. Expand Windows Logs.

4. Right-click Application, and then click Filter Current Log.

The Filter Current Log dialog box appears.

5. Select check boxes next to all the event levels (Critical, Warning, Verbose, Error, Information).

6. In the Event sources list, select RSSql.

7. (Optional) In the Task category list, select a specific category.

8. Click OK.

The application logs are filtered and display only the logs related to FactoryTalk Transaction Manager.

Windows Event Viewer tips



FactoryTalk Transaction Manager does not support RSLinx Classic as an application. You must run RSLinx Classic as a Windows 2012/2008/2003 service.

If you do not run RSLinx Classic as a Windows 2012/2008/2003 service while you are configuring RSLinx Classic from a remote location, the following error message appears.

To setup RSLinx Classic to run as a service:

1. Go to Start > Program Files > Rockwell Software > RSLinx > RSLinx Classic Launch Control Panel.

The RSLinx Classic Launch Control Panel dialog box appears.

2. (Optional) Select the Always Run As Service check box, if you want RSLinx Classic to start as a service at all times.

3. Click Start.

You can define a data point in FactoryTalk Transaction Manager to map to multiple contiguous registers in a controller. This allows you to read a block of ASCII registers and send them to the database as a single string.

Run RSLinx Classic as a service

Data block support



The stored procedure reads a data block, separates the integer values, and inserts them into a table. This stored procedure is used to bind a data block item from a FactoryTalk Transaction Manager control connector.

In certain situations, it is more efficient to send a data block of integers than to use the Parse() expression. To send data blocks to a stored procedure and then separate them, set up a data block in a FactoryTalk Transaction Manager control connector, such as N7:0,L100 (a block of 100 integers from N7:0 to N7:99) and pass this value to the stored procedure as outlined below. This stored procedure uses a table created with the CREATE TABLE testerout(run INT,my_val INT) command.

NOTE The stored procedures only accept positive integers from 0 to 32,767.

CREATE PROCEDURE chunk_eater(@in_binary VARBINARY(255))

AS

DECLARE

@offset INT,

@string_len INT,

@in_byte_int INT,

@loop INT,

@upper_word VARBINARY(2),

@lower_word VARBINARY(2)

BEGIN

SELECT @string_len = DATALENGTH(@in_binary)

SELECT @loop = 1

WHILE @string_len >= @loop

BEGIN

--------------------------------------------------------------

Note: This procedure only accepts positive integers. You may modify the upper

-- word of each integer for negative integer values.

--------------------------------------------------------------

--------------------------------------------------------------

You can view the following code using upper_word and lower_word. The values are

-- inserted into a TESTEROUT table, which records the integer value (in my_val) and

-- the "run" or integer location. The location for sending a data block of n7:0,L100

Send data blocks from FactoryTalk Transaction Manager to a stored procedure



-- results in value of 199. To alter this inversion, subtract the current location

-- from the string length.

--------------------------------------------------------------

SELECT @upper_word = SUBSTRING(@in_binary,(@string_len - @loop)+0,1)

SELECT @lower_word = SUBSTRING(@in_binary,(@string_len - @loop)+1,1)

-- lines directly above substring out the 2 bytes of the word

-- they are combined in reverse order for byte swapping.

SELECT @in_byte_int = CONVERT(int,(@lower_word+@upper_word))

INSERT INTO testerout(run,my_val) VALUES (@loop,@in_byte_int)

SELECT @loop = @loop + 2

END --GREAT BIG WHILE LOOP

END-- proc

FactoryTalk Transaction Manager can write to a controller a data block consisting of integers selected from multiple rows of a table. The stored procedure reads four integers (ints) from a database table and concatenates them in a binary (varbinary) stream, which is then bound to a data block in FactoryTalk Transaction Manager.


Following is a sample creation table from which data can be retrieved:

CREATE TABLE my_next_int_table (int1 INT,int2 INT,int3 INT,int4 INT,record_row INT)

INSERT INTO my_next_int_table values (1,2,3,4,1)














Send data blocks from multiple rows in a table using Integer data























Following is a sample creation statement containing dummy data:

CREATE PROCEDURE chunk_maker_cursor(@in_number int, @out_binary VARBINARY(200) OUT)

AS

DECLARE

@val1 INT,

@binary1 VARBINARY(2),

@loop INT

DECLARE int_cursor CURSOR

LOCAL FORWARD_ONLY STATIC READ_ONLY

FOR SELECT int1 FROM my_next_int_table

WHERE record_row = @in_number

ORDER BY int1

BEGIN

----------------------------------------------------------------

Note: This procedure only accepts positive integers, some math must be applied to

-- the upper word of each integer for negative integer values.

--------------------------------------------------------------

--------------------------------------------------------------

-- The following code illustrates how the substring is combined:

--------------------------------------------------------------

-- initialize loop var



SELECT @loop = 1

OPEN int_cursor

FETCH NEXT FROM int_cursor

INTO @val1

WHILE @@FETCH_STATUS = 0

BEGIN

SELECT @binary1 = @val1

-- The following code illustrates how the substring is combined in reverse order for

-- byte swapping. Because the first loop must differ, the following IF statement is

-- uninitialized. Intializing it will alter the end value of the binary string.

IF @loop = 1

BEGIN

SELECT @out_binary = (SUBSTRING(@binary1,2,1)+SUBSTRING(@binary1,1,1))

END

ELSE

BEGIN

SELECT @out_binary = (SUBSTRING(@binary1,2,1)+SUBSTRING(@binary1,1,1)) + @out_binary

END

-- Get next row

FETCH NEXT FROM int_cursor

INTO @val1

select @loop = @loop + 1

END --while for fetch

CLOSE int_cursor

DEALLOCATE int_cursor

END—proc

FactoryTalk Transaction Manager can write to a controller a data block consisting of multiple integers selected from one row of a table. The stored procedure combines columns of a database table into a binary string, which is then bound to a FactoryTalk Transaction Manager data block item.

The stored procedure finds the row in my_int_table that matches the input parameter (where the column record_row is equal to the input variable @in_number), and returns the four integers combined in a varbinary field. In FactoryTalk Transaction Manager, bind the in_number to an integer register in the controller such as n227:0.

Send data blocks from one row in a table using Integer data



The register can contain values 1 through 10. Then bind the varbinary field @out_binary to a 4-element data block, such as N7:0,L4.


CREATE TABLE my_int_table (int1 INT,int2 INT,int3 INT,int4 INT,record_row INT IDENTITY)

INSERT INTO my_int_table values (1,2,3,4)










CREATE PROCEDURE chunk_maker(@in_number int, @out_binary VARBINARY(8) OUT)

AS

DECLARE

@val1 INT,

@val2 INT,

@val3 INT,

@val4 INT,




@binary4 VARBINARY(2)

BEGIN

--------------------------------------------------------------

-- Note: This procedure only accepts positive integers. You may modify the

-- upper word of each integer for negative integer values.

--------------------------------------------------------------

--------------------------------------------------------------

-- The following code illustrates how the substring is combined:

--------------------------------------------------------------

SELECT @val1=int1, @val2=int2, @val3=int3, @val4=int4

FROM my_int_table

WHERE record_row = @in_number

SELECT @binary1 = @val1, @binary2 = @val2, @binary3 = @val3, @binary4 = @val4



-- The following code illustrates how the substring is combined in reverse order

-- for byte swapping. Two substrings are created for each varbinary that has

-- the value of the integers, then all the varbinaries are concatenated.

SELECT @out_binary = (SUBSTRING(@binary4,2,1)+SUBSTRING(@binary4,1,1))+(SUBSTRING(@binary3,2,1)+SUBSTRING(@binary3,1,1))+(SUBSTRING(@binary2,2,1)+SUBSTRING(@binary2,1,1))+(SUBSTRING(@binary1,2,1)+SUBSTRING(@binary1,1,1))

END-- proc

An application error occurs upon configuration startup when you attempt to connect to a Sybase back end. This error occurs because the system environment variable for Sybase is missing or invalid. Usually the ODBC driver installation sets the path and variables. However, if the drivers were installed as a user account other than administrator, the variables are not set.

The typical settings are:

Variable: SYBASE

Value: C:\Sybase

The Expression Editor operates on its internal Double data type that does not cover the entire Int64 range. This requires imposing the following limits on all incoming and outgoing Int64 parameters:

• For Int64 Signed: from -9007199254740991 to 9007199254740991.

• For Int64 Unsigned: from 0 to 9007199254740991.

The Expression Editor returns rounded results according to the double data type behavior.

The Expression Editor rounds any arithmetical operation result if the result exceeds the double type precision limit (including integer and floating point numbers). The transaction passes but the passed

Sybase values

Int64 Signed/Unsigned in the Expression Editor



value is not exact. This behavior can lead to having invalid data stored in the database.

Int64 Signed / Unsigned as an output parameter in a stored procedure has the following limitations:

• For the Int64 Signed / Unsigned data point types in a hexadecimal, octal or 0.x decimal format, the maximum value is 2147483647.

• For the Int64 Signed data point types in a decimal format, the range is between -9,223,372,036,854,775,807 and 9,223,372,036,854,775,807.

• For the Int64 Unsigned data point type in a decimal format, the range is between 0 and 18,446,744,073,709,551,615.

There are the following limitations for a substitute value for a data point:

• For a substitute value in hexadecimal and octal formats, the maximum value is 2147483647.

• For a substitute value in a decimal format, the value has to fall within a range between -9007199254740991 and 9007199254740991.

If you have a configuration created with a previous version of FactoryTalk Transaction Manager with the MS SQL Server-specific BigInt data type, and you have upgraded the system to FactoryTalk Transaction Manager 12.00, perform the following action to ensure that data is correctly written to the BigInt column:

• Go to the Step 4 in the Checklist, and click Apply to refresh the data object.

Int64 Signed/Unsigned as an output parameter in a stored procedure

Substitute values for a data point

Verify BigInt data types after FactoryTalk Transaction Manager update



FactoryTalk Transaction Manager remembers the sizes and positions of most commonly used dialog boxes as specified by the user.

To reset the sizes and positions of the dialog boxes:

1. Exit FactoryTalk Transaction Manager.

2. Click Start > Run, and then type regedit.

The Registry Editor appears.

3. Find My Computer\HKEY_CURRENT_USER\Software\Rockwell Software\RSSql\Window State.

4. Do the following:

To reset the settings for: Do: The Step 3 dialog box of the Checklist.

Open the Windows State folder, and then delete the DlgRna key.

The Step 5 dialog box of the Checklist.

Open the Windows State folder, and then delete the DlgTrn key.

The main window of FactoryTalk Transaction Manager.

Open the Windows State folder, and then delete the MainFrm key.

All dialog boxes in FactoryTalk Transaction Manager.

Delete the Windows State folder.

Oracle OCI enterprise connectors require administrator privileges

When using an OCI enterprise connector, ensure that you have local administrator privileges on your computer. Either add the OCI enterprise connector user to the local administrators group in Windows, or change the user of the OCI enterprise connector to an existing user that has administrator privileges.

SQL Server considers inputs and outputs the same

The SQL Server ODBC driver lists outputs of stored procedures as both inputs and outputs.

Restore default dialog box sizes

Miscellaneous


Index

A Administer RSBizWare servers 215 Advanced topics 261 Application notes for FactoryTalk Transaction Manager 281 Assign application privileges to groups 241 Assign object permissions to users and groups 242

B Behaviors when setting substitution options for FactoryTalk data points 293 Benefits of using the data compression 273

C Clean installation

supported installation scenarios 22 Client activations for FactoryTalk Historian Classic 230 Client activations for FactoryTalk Metrics 228 Compression ratio 275 Configuration Console 16 Configure custom object permissions 246 Configure data collection 247 Configure default object permissions 242 Configure FactoryTalk Transaction Manager Connectivity to SQL Server using Windows authentication 289 Configure FactoryTalk Transaction Manager for connections with SQL Server 291 Configure FactoryTalk user groups 235 Configure FactoryTalk users 66 Configure Internet Explorer trusted sites 208 Configure server log files 256 Configure the database user 267 Configure the Oracle 10g Instant Client for FactoryTalk Transaction Manager 288

Configure the Oracle ODBC data source 269 Configure the SQL Server authentication 289 Configure the Windows-only authentication 290 Configure user-defined summarization fields (flex-fields) 78 Configure Windows-linked FactoryTalk users 62 Configure Windows-linked user groups 237 Configure your SQL Server Data Tools (SSDT) to work with Report Expert custom reports 207 Congratulations! 107, 205 Considerations for copying and pasting FactoryTalk data points 298 Considerations for distributed configurations 297 Controll access to your RSBizWare system 225 Create a Net Configuration connection 268 Create tablespaces 267

D Data block support 301 Data compression 273 Data compression considerations 278 Data types supported by SQL Server 293 Database tips 265 Documentation feedback 316

E Enable network COM+ access for COM+ connectors in FactoryTalk Transaction Manager 288 Example

FactoryTalk Historian Classic activation 233 FactoryTalk Metrics activation 231

Index


F FactoryTalk Administration Console 14 FactoryTalk Historian and FactoryTalk Metrics privileges 86, 182 FactoryTalk Historian for Batch activation options 234 FactoryTalk Transaction Manager 17 FactoryTalk Transaction Manager Configuration Server 17 Filter permissions 243

G Grant default object permissions 245

H Handle temporary database connection loss in the Information Services Manager 218 Hardware and software requirements 19 How the data compression works 274

I Improve the performance of your RSBizWare Oracle database 270 In FactoryTalk Transaction Manager 285, 286 In RSLogix 5000 285 In the database 283 In the processor 283 Information for users of SQL Server 2014 23 Information Services Manager 16 Install RSBizWare 21 Install RSBizWare sample data 209 Installation and configuration checklist 24 Installation Assistance 316 Int64 Signed/Unsigned as an output parameter in a stored procedure 308 Int64 Signed/Unsigned in the Expression Editor 307

Intended audience 11

M Maintain frequently used RSBizWare tables and indexes 265 Manage FactoryTalk user groups and users 235 Manage Information Services Manager external data sources 216 Manage Information Services Manager scheduled items 216 Manage user access 241 Metrics Server Manager 17 Migrate RSBizWare 109 Migration

supported migration scenarios 109 Migration checklist 112 Miscellaneous 309

N New product satisfaction return 316

P Post-installation tasks 207 Preface 2 Prepare for the upgrade 212 Prepare the SQL Server uncompress view 276 Prepare to run the Oracle database 271

Q Query the SQL Server uncompress view 277

R Recommended database settings 267 Register the Excel Add-in 262

Index


Remote connection to an RSBizWare server 261 Remove a Configuration Server computer from FactoryTalk Transaction Manager 295 Remove RSBizWare 108 Repair the connection to SQL Server 59, 156 Report data source permissions 244 Report diagnostic messages 255 Report object permissions 244 Report permissions 243 Report Schedule Manager 16 Resolve IP address to host name issues 294 Restore default dialog box sizes 309 Rockwell Automation support 316 RSBizWare databases (SQL Server or Oracle) 15 RSBizWare prerequisites 19 RSBizWare product dependencies 19 Run RSBizWare in a distributed environment 19 Run RSLinx Classic as a service 301

S Security Services Manager 15 Send data blocks from FactoryTalk Transaction Manager to a stored procedure 302 Send data blocks from multiple rows in a table using Integer data 303 Send data blocks from one row in a table using Integer data 305 Send date/time information from a ControlLogix processor to a database 285 Server activations for FactoryTalk Historian Classic 227 Server activations for FactoryTalk Metrics 227 Service Console 15 Set the real-time clock in a ControlLogix processor using FactoryTalk Transaction Manager 282 Software activation options 226

Special considerations for a distributed Microsoft COM+ application 287 Start and stop FactoryTalk Transaction Manager configurations 252 Start and stop FactoryTalk Transaction Manager services manually 296 Start and stop RSBizWare servers 215 Step 1

Back up your FactoryTalk Transaction Manager configuration 115 Install Internet Information Services (IIS) 26

Step 10 Configure FactoryTalk groups and users 62 Restore your RSBizWare SQL Server database 144

Step 11 Install RSBizWare 68 Recreate your RSBizWare SQL Server database user 147

Step 12 Install SQL Server 2012 Native Client 151 Register the Security Services Manager 70

Step 13 Recreate the ODBC data source 152 Register the Information Services Manager 71

Step 14 Associate Metrics Server Manager with Information Services Manager 75 Verify if the local computer is added to the FactoryTalk Administration Console 158

Step 15 Assign activations to RSBizWare servers 81 Recreate your applications 159

Step 16 Add a local Administrator account as a Windows-linked user 160 Assign client activations to users 83

Step 17 Assign application privileges to users 84 Recreate your users 164

Step 18

Index


Install RSBizWare 167 Register FactoryTalk Transaction Manager 87

Step 19 Define FactoryTalk Transaction Manager configurations 89 Register the Security Services Manager 168

Step 2 Back up your RSBizWare SQL Server database 118 Install SQL Server 2012 Service Pack 1 32

Step 20 Register FactoryTalk Transaction Manager configurations 93 Register the Information Services Manager 169

Step 21 Associate Metrics Server Manager with Information Services Manager 173 Configure SQL Server Reporting Services (SSRS) 97

Step 22 Assign activations to RSBizWare servers 174 Verify the SSRS configuration 100

Step 23 Assign client activations to users 177 Install and configure Report Expert 102

Step 24 Assign application privileges to users 180 Configure the FTMetricsEditors group 105

Step 25 Restore your FactoryTalk Transaction Manager configuration 178 Verify the Report Expert installation 106

Step 26 Register the configuration in the RSBizWare SQL Server database 183

Step 27 Update your FactoryTalk Transaction Manager configuration 184

Step 28 Register FactoryTalk Transaction Manager 188

Step 29 Register the configuration in the Service Console 189

Step 3 Install FactoryTalk Services 42 Keep your database users for reference 121

Step 30 Configure SQL Server Reporting Services (SSRS) 192

Step 31 Verify the SSRS configuration 195

Step 32 Install and configure Report Expert 197

Step 33 Configure the FTMetricsEditors group 201

Step 34 Verify the Report Expert installation 202

Step 35 Start your FactoryTalk Transaction Manager configuration 203

Step 4 Configure FactoryTalk Activation 47 Keep your ODBC data source configuration for reference 123

Step 5 Create an RSBizWare SQL Server database 48 Keep your FactoryTalk Administration Console configuration for reference 124

Step 6 Create an RSBizWare SQL Server database user 49 Install Internet Information Services (IIS) 125

Step 7 Install SQL Server 2012 Native Client 53 Install SQL Server 2012 Service Pack 1 132

Step 8 Configure the ODBC data source 54 Install FactoryTalk Services 138

Step 9 Configure FactoryTalk Activation 143

Index


Verify if the local computer is added to the FactoryTalk Administration Console 61

Substitute values for a data point 308 Sybase values 307

T The Metrics Server Manager settings file 220 The RSBizWare architecture 12 Troubleshoot 253 Tune the Oracle database for FactoryTalk Historian Classic 269 Types of control connectors for the data collection 247 Types of diagnostic messages 255 Types of enterprise connectors for the data collection 248

U Unregister FactoryTalk Transaction Manager configurations 249 Update the Service Console with users and groups changes 239

Upgrade FactoryTalk Services Platform 213 Upgrade RSBizWare on Microsoft Windows Server 2008 R2 SP1 211 Upgrade the RSBizWare suite 214 Use Oracle with RSBizWare 266

V Verify BigInt data types after FactoryTalk Transaction Manager update 308 Verify the configuration of SQL Server 39 View compressed data 276 View diagnostic logs 259

W Ways of logging diagnostic messages 256 Web-based client 16 Welcome to RSBizWare 11 Where can I go for help? 18 Windows Event Viewer tips 300

Rockwell Automation Publication BZWARE-IN001N-EN-P-August 2017 Supersedes Publication BZWARE-IN001M-EN-P-June 2014 Copyright © 2017 Rockwell Automation Technologies, Inc. All Rights Reserved.

Rockwell Automation support

Rockwell Automation provides technical information on the Web to assist you in using its products. At http://www.rockwellautomation.com/support/ you can find technical and application notes, sample code, and links to software service packs. You can also visit our Support Center at https://rockwellautomation.custhelp.com/ for software updates, support chats and forums, technical information, FAQs, and to sign up for product notification updates.

In addition, we offer multiple support programs for installation, configuration, and troubleshooting. For more information, contact your local distributor or Rockwell Automation representative, or visit http://www.rockwellautomation.com/services/online-phone.

Installation Assistance

If you experience a problem within the first 24 hours of installation, review the information that is contained in this manual. You can contact Customer Support for initial help in getting your product up and running.

United States or Canada 1.440.646.3434

Outside United States or Canada Use the Worldwide Locator at http://www.rockwellautomation.com/rockwellautomation/support/overview.page, or contact your local Rockwell Automation representative.

New product satisfaction return

Rockwell Automation tests all of its products to help ensure that they are fully operational when shipped from the manufacturing facility. However, if your product is not functioning and needs to be returned, follow these procedures.

United States Contact your distributor. You must provide a Customer Support case number (call the phone number above to obtain one) to your distributor to complete the return process.

Outside United States Please contact your local Rockwell Automation representative for the return procedure.

Documentation feedback

Your comments will help us serve your documentation needs better. If you have any suggestions on how to improve this document, complete this form, publication RA-DU002.

Rockwell Automation maintains current product environmental information on its website at http://www.rockwellautomation.com/rockwellautomation/about-us/sustainability-ethics/product-environmental-compliance.page.

http://www.rockwellautomation.com/rockwellautomation/distributor-locator/sales-locator.page

http://literature.rockwellautomation.com/idc/groups/literature/documents/du/ra-du002_-en-e.pdf

RSBizWare Administration Guide - Rockwell Automation...Microsoft, SQL Server, Windows, Windows...

Documents

Transcript of RSBizWare Administration Guide - Rockwell Automation...Microsoft, SQL Server, Windows, Windows...