Vous êtes sur la page 1sur 178

Foxboro Evo™

Process Automation System

FoxCTS™ Change Tracking


Software
Configuration and Administration Guide

*B0193VV* *K*

B0193VV

Rev K
November 12, 2014
Invensys, Foxboro, Foxboro Evo, I/A Series, FoxAPI, AIM*API, AIM*AT, AIM*Historian, FoxCTS, FoxSelect,
FoxDraw, FoxView, and Micro-I/A are trademarks of Invensys Limited, its subsidiaries and affiliates.
All other brand names may be trademarks of their respective owners.

Copyright 2000-2014 by Invensys Systems, Inc.


All rights reserved.

Invensys is now part of Schneider Electric.

SOFTWARE LICENSE AND COPYRIGHT INFORMATION


Before using the Invensys Systems, Inc. supplied software supported by this documentation, you
must read and understand the following information concerning copyrighted software.
1. The license provisions in the software license for your system govern your obligations
and usage rights to the software described in this documentation. If any portion of
those license provisions is violated, Invensys Systems, Inc. will no longer provide you
with support services and assumes no further responsibilities for your system or its
operation.
2. All software issued by Invensys Systems, Inc. and copies of the software that you are
specifically permitted to make, are protected in accordance with Federal copyright
laws. It is illegal to make copies of any software media provided to you by
Invensys Systems, Inc. for any purpose other than those purposes mentioned in the
software license.
Contents
Figures.................................................................................................................................... ix

Tables..................................................................................................................................... xi

Preface................................................................................................................................. xiii

1. Overview ........................................................................................................................... 1
Platforms Not Supported .......................................................................................................... 1
FoxCTS Features ...................................................................................................................... 1
Change Tracking .................................................................................................................. 1
Security Enhancements ........................................................................................................ 2
FoxCTS Domain Definitions .................................................................................................... 3
System Monitor Domain ...................................................................................................... 4
FoxCTS Process Areas .......................................................................................................... 4
FoxCTS Related Logical Names ........................................................................................... 5
FoxCTS Server ..................................................................................................................... 5
FoxCTS Configurator ..................................................................................................... 5
FoxCTS Client ..................................................................................................................... 6
Local Login ..................................................................................................................... 6
FoxCTS User Accounts ........................................................................................................ 6
Standard Workstations .................................................................................................... 6
Workstations with Security Enhancements ...................................................................... 6
Operation ................................................................................................................................. 7
FoxCTS Server ..................................................................................................................... 7
FoxCTS Client ..................................................................................................................... 9
FoxCTS Client Operation .............................................................................................. 9
File Tracking ................................................................................................................. 11
Enhanced OAJ Messages ............................................................................................... 11
FoxCTS OAJ Host ............................................................................................................. 12
FoxCTS SysMon ................................................................................................................ 13
FoxCTS ICC Driver .......................................................................................................... 13
FoxCTS PACTware ........................................................................................................... 13
Limitations .............................................................................................................................. 14
Daylight Savings Time ....................................................................................................... 14
Control Stations Baseline ................................................................................................... 14
Foxboro Evo Control Editors ........................................................................................ 14
IACC ............................................................................................................................ 14
ICC ............................................................................................................................... 15
Foundation Fieldbus Devices ......................................................................................... 15
Foxboro Evo Control Editors ............................................................................................. 15
IACC Configurator ............................................................................................................ 15

iii
B0193VV – Rev K Contents

Control Configurator ......................................................................................................... 15


CP Initialization ............................................................................................................ 16
FoxCTS System Modifications ................................................................................................ 16
Primary Domain Controller ............................................................................................... 16
FoxCTS Server Modifications ............................................................................................ 19
FoxCTS OAJ Host Modifications ...................................................................................... 19
FoxCTS Client Modifications ............................................................................................ 19
Existing Environments .................................................................................................. 19
Initial Environments ...................................................................................................... 19
Environment Change Mechanism ................................................................................. 20
Tool Access .................................................................................................................... 20
OAJ Enhanced Messaging Modifications ....................................................................... 20
Integrated Control Configurator Access ......................................................................... 20
Login Mechanism .......................................................................................................... 20
FoxCTS SysMon Modifications ......................................................................................... 21
FoxCTS ICC Driver Modifications .................................................................................... 21
FoxCTS PACTware Modifications ..................................................................................... 21

2. Installation Planning ....................................................................................................... 23


Skills ....................................................................................................................................... 23
Installation and Configuration ........................................................................................... 23
FoxCTS Administrator ....................................................................................................... 23
System Requirements .............................................................................................................. 24
Supported Control Core Services and I/A Series Software Versions .................................... 24
FoxCTS Server Module ...................................................................................................... 24
FoxCTS OAJ Host Module ............................................................................................... 25
FoxCTS Client Module ...................................................................................................... 25
FoxCTS SysMon Module ................................................................................................... 25
FoxCTS ICC Driver Module ............................................................................................. 25
FoxCTS PACTware Module .............................................................................................. 25
Installation Overview .............................................................................................................. 26
FoxCTS Server ................................................................................................................... 26
FoxCTS OAJ Host ............................................................................................................. 26
FoxCTS Client ................................................................................................................... 26
FoxCTS SysMon (Optional) .............................................................................................. 26
FoxCTS ICC Driver (Optional) ......................................................................................... 26
FoxCTS PACTware (Optional) .......................................................................................... 27
FoxCTS Worksheets Overview ............................................................................................... 27
Standard FoxView Environments Modifications ..................................................................... 28
FoxView Example .............................................................................................................. 29
Display Manager Configuration File ....................................................................................... 31
FoxCTS Optional Login Configuration .................................................................................. 31
Foxboro Evo Control Editors Integration ................................................................................ 32
IACC Integration .................................................................................................................... 32

iv
Contents B0193VV – Rev K

PACTware Integration ............................................................................................................ 33

3. Installation ...................................................................................................................... 35
Primary Domain Controller .................................................................................................... 35
FoxCTS Server ........................................................................................................................ 36
Microsoft SQL Server Software .......................................................................................... 36
Installation for Control Core Services v9.0 or I/A Series Software v8.8 .......................... 36
Installation for I/A Series Software v8.5-v8.7 ................................................................. 37
SQL Server Configuration ............................................................................................. 39
FoxCTS Change Database ................................................................................................. 39
FoxCTS Server Module ...................................................................................................... 39
FoxCTS OAJ Host Module .................................................................................................... 40
FoxCTS Client Module .......................................................................................................... 42
FoxCTS SysMon Module ....................................................................................................... 45
FoxCTS ICC Driver Module .................................................................................................. 47
FoxCTS PACTware Module ................................................................................................... 49
Reboot Workstations .............................................................................................................. 49
FoxCTS Services ..................................................................................................................... 50
Control Core Services v9.0 or I/A Series Software v8.8 ....................................................... 50
I/A Series Software v8.5-v8.7 .............................................................................................. 51

4. FoxCTS Domain Configuration...................................................................................... 53


FoxCTS Configurator ............................................................................................................. 53
FoxCTS Domain Database Maintenance ........................................................................... 56
Backup .......................................................................................................................... 57
Restore .......................................................................................................................... 58
FoxCTS Domain Configuration ........................................................................................ 59
Process Areas ................................................................................................................. 59
Control Stations ............................................................................................................ 61
Workstations ................................................................................................................. 62
FoxCTS File Tracking ........................................................................................................ 64
File Tracking Clients ..................................................................................................... 64
Files to Track ................................................................................................................. 66
FoxCTS User Configuration .............................................................................................. 69
Environments ................................................................................................................ 69
Groups .......................................................................................................................... 71
User Types .................................................................................................................... 73
Password Controls ......................................................................................................... 75
User Accounts ............................................................................................................... 77

5. Additional Configurations ............................................................................................... 81


Inactivity Timers .................................................................................................................... 81
Inactivity Configuration ..................................................................................................... 81
Optional Configurations ......................................................................................................... 82

v
B0193VV – Rev K Contents

FoxCTS Login Box ............................................................................................................ 82


Customizing the FoxCTS Initial Environments ................................................................. 82
Initial Environment Login ............................................................................................. 82
Initial Environment Logout ........................................................................................... 82
Initial Environment ............................................................................................................ 83
Customizing the FoxCTS Menu ........................................................................................ 84
Foxboro Evo Control Editors/IACC Integration ..................................................................... 84
FoxCTS PACTware Module ................................................................................................... 85

6. FoxCTS Human Interface ............................................................................................... 87


FoxCTS Menu Items .............................................................................................................. 88
Admin (FoxCTS Configurator) .......................................................................................... 88
Chg_Env ............................................................................................................................ 89
Login .................................................................................................................................. 89
Standard Workstations .................................................................................................. 89
Logout ................................................................................................................................ 91
Passwd_Chg ....................................................................................................................... 92
User_Name ........................................................................................................................ 92
User Reconfirmation ............................................................................................................... 93
Enhanced Operator Action Journal ......................................................................................... 98
Tool Usage Tracking ............................................................................................................... 98
Other Scripts and Commands ............................................................................................ 98
ICCLaunch ............................................................................................................................. 99

7. Maintenance.................................................................................................................. 101
Uninstall FoxCTS Modules .................................................................................................. 101
Reinstall FoxCTS .................................................................................................................. 102
Upgrades ............................................................................................................................... 102
FoxCTS ........................................................................................................................... 102
Control Core Services or I/A Series Software .................................................................... 102
FoxView ........................................................................................................................... 102
Upgrades - PACTware ..................................................................................................... 103
System Commits ................................................................................................................... 103
FoxCTS SysMon Hosts .................................................................................................... 103
Quick Fixes ........................................................................................................................... 104
FoxCTS ........................................................................................................................... 104
Foxboro Software ............................................................................................................. 104
FoxCTS Client Module ............................................................................................... 104
FoxCTS Server Module ............................................................................................... 104
FoxCTS Services ................................................................................................................... 104
FoxCTS Log File ................................................................................................................... 105
Tool Wrapping ..................................................................................................................... 106
Adding a New Tool .......................................................................................................... 106

vi
Contents B0193VV – Rev K

Environments ........................................................................................................................ 106


Adding a New Environment ........................................................................................ 106

8. Troubleshooting............................................................................................................ 107
FoxCTS Log Files ................................................................................................................. 107
cmslog .............................................................................................................................. 107
Miscellaneous Script Log Files .......................................................................................... 107
FoxCTS Services ................................................................................................................... 107
Not Starting on Reboot (I/A Series Software v8.5-v8.7) ................................................... 107
Debug Logging ................................................................................................................. 108
FoxView ................................................................................................................................ 109
Minimized Console Window (I/A Series Software v8.5-v8.7) ........................................... 109
Common Problems ............................................................................................................... 109
Cannot Change Set Points ............................................................................................... 109
Menu Items Not Selectable .............................................................................................. 110
Local Group and Password File Not Updated .................................................................. 110
Database Reporting Problems ............................................................................................... 111
ICC Control Station Changes not Recorded .................................................................... 111
File Tracking Changes Not Recorded ............................................................................... 112
Changes Not Recorded from FoxSelect or FoxView ......................................................... 113
Enhanced Operator Action Journal Messages Not Recorded ............................................ 113
Performance Issues ................................................................................................................ 113
Control Network Loading Issues ...................................................................................... 113
User Interface Communications .................................................................................. 114
OAJ Communications ................................................................................................. 114
File Tracking ............................................................................................................... 114
ICC Driver Communication ....................................................................................... 114
System Performance ......................................................................................................... 115
Slow Down File Tracking ............................................................................................ 115
Slow Down CP Change Information Processing .......................................................... 115
FoxCTS Product Removal .................................................................................................... 115
FoxCTS Messages ................................................................................................................. 116
Login ................................................................................................................................ 116
User Reconfirmation ........................................................................................................ 117
FoxCTS PACTware Module Error Messages .................................................................... 118

9. FoxCTS Change Database............................................................................................. 119


Overview ............................................................................................................................... 119
Limitations ............................................................................................................................ 119
Installation ............................................................................................................................ 120
Integrity Software ............................................................................................................. 120
Integrity Configuration ......................................................................................................... 121
Licensing .......................................................................................................................... 121
Database Configuration .................................................................................................... 122

vii
B0193VV – Rev K Contents

Asset Models Import ........................................................................................................ 123


Asset Creation .................................................................................................................. 124
Data Collector Service ...................................................................................................... 125
Import Schedule ............................................................................................................... 126
Reports .................................................................................................................................. 129
Asset Explorer ................................................................................................................... 129
Change Tracking .............................................................................................................. 130

Appendix A. Worksheets ................................................................................................... 133

Appendix B. Command Usage........................................................................................... 149

Index .................................................................................................................................. 155

viii
Figures
1-1. Entity Relationship Diagram for the FoxCTS Domain ................................................. 3
1-2. Entity Relationship Diagram Expanded to Show FoxCTS Process Areas ....................... 4
1-3. FoxCTS Operation on the System ................................................................................ 8
1-4. FoxCTS and AIM*AT Software Integration ................................................................ 12
1-5. FoxCTSService Account ............................................................................................. 16
1-6. FoxCTS Groups .......................................................................................................... 17
1-7. FoxCTS Base Domain Controllers Policy ................................................................... 17
1-8. FoxCTS Computers Policy ......................................................................................... 18
1-9. FoxCTS Remote Desktop Servers ............................................................................... 18
3-1. FoxCTS OAJ Host Module Setup .............................................................................. 41
3-2. FoxCTS Client Module Setup .................................................................................... 43
3-3. FoxCTS Client OAJ Enhanced Messaging Setup ........................................................ 44
3-4. FoxCTS SysMon Module Setup ................................................................................. 46
3-5. FoxCTS ICC Driver Module Setup ............................................................................ 48
3-6. FoxCTS Services ......................................................................................................... 50
3-7. FoxCTS Services ......................................................................................................... 51
4-1. FoxCTS Configurator - Main Menu ........................................................................... 54
4-2. FoxCTS Configurator - Database Menu ..................................................................... 56
4-3. FoxCTS Configurator - Domain Database Backup ..................................................... 57
4-4. FoxCTS Configurator - Domain Database Restore ..................................................... 58
4-5. FoxCTS Configurator - Domain Configuration Menu ............................................... 59
4-6. FoxCTS Configurator - Process Area .......................................................................... 60
4-7. FoxCTS Configurator - Control Stations .................................................................... 61
4-8. FoxCTS Configurator - ............................................................................................... 63
4-9. FoxCTS Configurator - File Tracking Menu ............................................................... 64
4-10. FoxCTS Configurator - File Tracking Clients ............................................................. 65
4-11. FoxCTS Configurator - Files and Folders to Track ..................................................... 67
4-12. FoxCTS Configurator - Files to Track ........................................................................ 68
4-13. FoxCTS Configurator - User Configuration Menu ..................................................... 69
4-14. FoxCTS Configurator - Environments ........................................................................ 70
4-15. FoxCTS Configurator - Groups .................................................................................. 72
4-16. FoxCTS Configurator - User Types ............................................................................ 74
4-17. FoxCTS Configurator - Password Control .................................................................. 76
4-18. FoxCTS Configurator - User Accounts ....................................................................... 79
6-1. FoxCTS Menu ............................................................................................................ 87
6-2. FoxCTS Configurator ................................................................................................. 88
6-3. Change Environment Dialog Box ............................................................................... 89
6-4. FoxCTS Login - Standard Workstation ....................................................................... 90
6-5. FoxCTS Login - Workstation with Security Enhancements ........................................ 91
6-6. FoxCTS Change Password .......................................................................................... 92
6-7. FoxCTS User_Name Example .................................................................................... 92
6-8. Single User Reconfirmation Dialog Box ...................................................................... 93
6-9. Dual User Reconfirmation Dialog Box ........................................................................ 94
6-10. FoxCTS Palette ........................................................................................................... 94

ix
B0193VV – Rev K Figures

6-11. User Reconfirmation Test Display .............................................................................. 96


6-12. Dual Login User Reconfirmation ................................................................................ 97
6-13. ICCLaunch Dialog Box .............................................................................................. 99
7-1. FoxCTS Services ....................................................................................................... 105
8-1. modRegApp .............................................................................................................. 108
9-1. IntegrityWin ............................................................................................................. 120
9-2. Integrity Licensing .................................................................................................... 121
9-3. Integrity Database Configuration .............................................................................. 122
9-4. Integrity Asset Models Import ................................................................................... 123
9-5. Integrity Asset Creation ............................................................................................. 124
9-6. Integrity Data Collector Service ................................................................................ 125
9-7. Import Schedule - General Tab ................................................................................. 126
9-8. Import Schedule - Sequence Tab ............................................................................... 127
9-9. Import Schedule - Schedule Tab ............................................................................... 128
9-10. Import Schedule - Scheduled Items ........................................................................... 129
9-11. Asset Explorer - FoxCTS ........................................................................................... 130
9-12. Change Tracking - FoxCTS ...................................................................................... 131

x
Tables
Acronyms and Abbreviations ...................................................................................... xvi
2-1. Standard Operator.env File ......................................................................................... 29
2-2. Standard Operator.mbr File ........................................................................................ 29
2-3. Standard Operator.dbr File ......................................................................................... 30
2-4. Initial .acl File Example ............................................................................................... 30
2-5. Operator .acl File Example .......................................................................................... 31
5-1. FoxCTS PACTware Groups ....................................................................................... 85
8-1. FoxCTS Services - Debug Logs ................................................................................. 109
B-1. User Reconfirmation Facility ..................................................................................... 149

xi
B0193VV – Rev K Tables

xii
Preface

Purpose
The FoxCTS™ Change Tracking Software Administration and Configuration Guide provides
the information required to understand, install, configure, use, and maintain the FoxCTS
software package. The FoxCTS software is a tool that provides a trace of changes made to Control
Station Configurations and other important files.

Audience
The manual is intended for the person who will be the FoxCTS administrator. It is not intended
for Process Operators and, generally, is not needed by those who simply use the station.

Revision Information
The following changes were made to the manual for the FoxCTS software, Version 6.01.00.
Global changes made for this release.
Chapter 1 “Overview”
♦ Updated requirement information in “Platforms Not Supported” on page 1.
♦ Modified the section “FoxCTS User Accounts” on page 6 with new FoxCTS user
account information.
♦ FoxCTS Client now supports FoxView login with no login box as described in “Fox-
CTS Client Operation” on page 9.
♦ FoxCTS PACTware module documented on page 13.
Chapter 2 “Installation Planning”
♦ New optional login information documented on page 25.
Chapter 3 “Installation”
♦ General installation modification made.
♦ FoxCTS installation instructions for a primary domain controller added on page 35.
♦ Microsoft® SQL Server® installation instructions updated on page 36.
♦ FoxCTS PACTware module installation instructions added on page 49.
Chapter 4 “FoxCTS Domain Configuration”
♦ General modifications made throughout this chapter.
Chapter 5 “Additional Configurations”
♦ Optional login box documented on page 82.
♦ FoxCTS PACTware configuration discussed on page 85.
Chapter 6 “FoxCTS Human Interface”
♦ New login options documented on page 89.

xiii
B0193VV – Rev K Preface

Chapter 8 “Troubleshooting”
♦ FoxCTS PACTware error messages are documented on page 118.
Chapter 9 “FoxCTS Change Database”
♦ Integrity installation instructions updated on page 120.

Reference Documents
In addition to the information presented herein, you should be familiar with the following
documents.
♦ AIM*AT™ Suite AIM*API™ User’s Guide (B0193YN)
♦ I/A Series FoxAPI™ User’s Guide (B0193UD)
♦ I/A Series FoxAPI™ Installation Guide (B0193UC)
♦ Display Engineering for FoxView Software and Display Manager Software (B0193MQ)
♦ Display Commands (B0193DF)
♦ FoxDraw™ Software V10.4 (B0700FD)
♦ FoxView™ and FoxDraw™ Release V10.4.1 Notes (B0700SN)
♦ FoxView™ Software V10.4 (B0700FC)
♦ Control Database Deployment User’s Guide (B0750AJ)
♦ I/A Series System Configuration Component (IACC) User’s Guide (B0700FE)
♦ McAfee® ePolicy Orchestrator 4.0, Host Intrusion Prevention 7.0, and Device Control
2.2 (Installation and Configuration Guide for I/A Series Systems) (B0700EB) - For
I/A Series software v8.7 or earlier
♦ Optional McAfee Security Products Installation and Configuration Guide (B0700EX)
♦ McAfee VirusScan and AntiSpyware Enterprise 8.8i Installation (B0700EQ) - For I/A
Series v8.8 or later
♦ Operator Action Journal (B0193CW)
♦ Security Enhancements User’s Guide (B0700DX) - For I/A Series software v8.7 or
earlier
♦ Security Enhancements User’s Guide for I/A Series Workstations with Windows 7 or
Windows Server 2008 Operating Systems) (B0700ET) - For I/A Series software v8.8
or later
♦ System Messages (B0193CG)
These documents are available on the Foxboro Evo Electronic Documentation media
(K0174MA). The latest revisions of each document are also available through our Invensys
Global Customer Support at http://support.ips.invensys.com.

xiv
Preface B0193VV – Rev K

Terms and Definitions


The following list describes some of the common terms related to the FoxCTS product.

Workstation Foxboro Evo™ Workstation or I/A Series® Workstation.

System Foxboro Evo system or I/A Series system.

FoxCTS Change This is the database that contains the change records. This database is
Database maintained and viewed by the PAS® Integrity™ software that is installed
on FoxCTS Server.

FoxCTS The FoxCTS Configurator allows FoxCTS users, that have configurator
Configurator access rights, the ability to configure the FoxCTS domain.

FoxCTS Client A workstation with the FoxCTS Client module installed.

FoxCTS Domain A FoxCTS domain is the set of all stations (control stations, workstations,
and file tracking clients) and user accounts to be monitored by a single
FoxCTS Server. A FoxCTS domain is a superset of one or more System
Monitor domains. The FoxCTS domain is totally unrelated to the
Microsoft® domain used for security-enhanced workstations.

FoxCTS Domain This is the FoxCTS database that contains the configuration for the
Database FoxCTS domain. This database is created during the installation of the
FoxCTS Server module and is maintained using the FoxCTS
Configurator.

FoxCTS File Is a workstation that has the FoxCTS Client module installed and
Tracking Client contains files to track.

FoxCTS Server Is the workstation that has the FoxCTS Server module installed. The
FoxCTS Server records the changes made in a FoxCTS domain. The
FoxCTS Server will also host the FoxCTS change database that is hosted
by the PAS Integrity software. The FoxCTS Server is always a FoxCTS
Client and can be configured as a FoxCTS file tracking client.

ICCLaunch The FoxCTS Client utility that replaces the FoxView Config >
Control_Cfg > CIO_Config menu item. Note that the AIM*API software
(Foxboro Evo Control Core Service v9.0 or I/A Series Software v8.8) or
FoxAPI software (I/A Series v8.5-v8.7) must be installed and configured
for the ICCLaunch utility to function properly. See “ICCLaunch” on
page 99 for details.

Logical Names A logical name is a sequence of alphanumeric characters and underscores


that uniquely identifies a program that needs to exchange data with other
programs. A WP’s logical name is the name to which a CP sends its alarm
messages.

Process Area A FoxCTS process area allows the association of selected workstations and
control stations to a name.

xv
B0193VV – Rev K Preface

System Monitor This domain consists of a set of workstations whose operation is


Domain monitored by a System Monitor.

User Types FoxCTS user types associate FoxCTS groups to a FoxCTS user account.

Groups FoxCTS groups associates a group of FoxView environments to a group


name.

Acronyms and Abbreviations Used in This Document


Acronyms and Abbreviations

Acronyms/
Abbreviations Description
API Applications Programming Interface
CP Control Processor
CS Control Station. Any device that can run control blocks.
FF Device FOUNDATION™ Fieldbus Device
FoxCTS Foxboro Change Tracking Software
IACC I/A Series Configuration Component
ICC Integrated Control Configurator
GBs Gibabytes
MBs Megabytes
OAJ Operating Action Journal
OM Object Manager
OS Operating System
PDC Primary Domain Controller
RAM Random Access Memory
SMMR System Monitor Message Relay program
SysMon System Monitor

xvi
1. Overview
This chapter represents an overview of the FoxCTS product.
FoxCTS (Change Tracking Software) is a change-tracking package used to document
modifications in the control system.
The FoxCTS package is a response to practices required by OSHA 1910 and by other FDA
regulations. These regulations require that changes made to a control system be documented and
distributed to all affected parties, especially to the process operators and their supervisors.
Though the FoxCTS package provides support for regulations like 21 CFR Part 11, it is not
sufficient by itself to ensure that any given installation is compliant.
Certification of any given installation as compliant is achieved not only through the application of
hardware and software products, but also through external reviews, internal procedures, and a
variety of other mechanisms.
We are committed to having a combination of services, policies, procedures and automated tools
to facilitate compliance. Please contact your account representative about the services provided by
us to assist you in meeting these regulations.

Platforms Not Supported


The FoxCTS v6.01.00 software does not provide support for the following:
♦ I/A Series Software versions prior to v8.5.
♦ Foxboro Evo Control HMI.
♦ Workstations running the Solaris® operating system.
See page 24 for the software versions currently supported.

FoxCTS Features
The FoxCTS package adds enhanced change tracking, security, configuration, and management
functions to systems.

Change Tracking
The change tracking events that the FoxCTS package currently tracks include:
♦ Modifications made using ICC, IACC, or Foxboro Evo Control Editors. These
tracked changes include:
♦compound additions, deletions and changes
♦ block additions, deletions and changes
♦ parameter additions, deletions and changes
♦ FOUNDATION fieldbus device block and parameter changes
♦ Sequence logic changes (to primary or included files) made with either the Foxboro
Evo Control Editors, IACC, ICC, or FoxSFC packages.

1
B0193VV – Rev K 1. Overview

♦ Ladder logic changes are recorded, but as of this writing they are not properly reported
by Integrity™.
♦ ASCII and binary file changes.
♦ Environment definition file changes.
♦ The usage of all configuration tools found under the D:\usr\fox\sys, D:\usr\fox\soft,
and D:\usr\fox\config directories.
♦ Active and passive connections within accessible display files are recorded, but as of
this writing they are not properly reported by Integrity
♦ PACTware “Store to Device” events.
The FoxCTS package provides a number of other features.
♦ It includes an application that stores Operator Action Journal (OAJ) information in
an AIM*Historian database with additional information about the FoxCTS user that
made the system change.
♦ The FoxCTS product includes an User Reconfirmation application with supporting
examples for use with FoxView. This application allows easy configuration of display
manager actions to be executed only if the FoxCTS user is reconfirmed. See “User
Reconfirmation” on page 93 for details.
♦ Automatic logout and display manager exit from FoxView displays based on
inactivity. See “Inactivity Timers” on page 81 for details.
The system functions that the FoxCTS product does not track include:
♦ Changes made to the running control station using tools that use the Object Manager
(OM), Applications Programming Interface (API) or FoxAPI™ software.

Security Enhancements
The security of the system is enhanced in the following ways.
♦ FoxCTS user accounts are created by the FoxCTS administrator using the FoxCTS
Configurator. In the case of workstations with security enhancements, a FoxCTS user
account must be created for each Microsoft domain user account. See “User
Accounts” on page 77 for details regarding on FoxCTS account creation.
♦ FoxCTS Client stations may be configured to prompt for user logins. See “FoxCTS
Human Interface” on page 87 for examples.
♦ FoxCTS user account information controls access to environments by assigning a
default home environment and a FoxCTS User Type to the account. See “User Types”
on page 73 for details.)
♦ The FoxCTS user can access only those environments that have been identified in the
assigned FoxCTS User Type.
♦ The FoxCTS package associates the current FoxCTS user to configuration changes for
recording in the FoxCTS change database.
♦ Includes a User Reconfirmation application with supporting examples for FoxView
displays. This application allows an application engineer to easily configure the
display managers actions to be executed only if the FoxCTS user or users are
confirmed. See “User Reconfirmation” on page 93 for details.

2
1. Overview B0193VV – Rev K

FoxCTS Domain Definitions


A FoxCTS domain is:
♦ The set of all control stations, workstations, and so forth, monitored by a single
FoxCTS Server.
♦ A superset of one or more System Monitor domains.

NOTE
A FoxCTS domain is totally unrelated to the Microsoft domain.

The FoxCTS package requires checkpoint messages to trigger its checks of the control station
databases. Since these messages originate from the System Monitor to which a CP is assigned, the
following must be true:
♦ All control stations monitored by a FoxCTS Server must be assigned to a System
Monitor.
♦ All the control stations monitored by a System Monitor must record to the same
FoxCTS Server, that is, they must all belong to the same FoxCTS domain.
System Monitors, control stations, workstations, and file servers relate as shown below:

Figure 1-1. Entity Relationship Diagram for the FoxCTS Domain

As shown in Figure 1-1, a FoxCTS domain may contain many SysMon domains, but each
SysMon domain is associated with exactly one FoxCTS domain. This relationship is also true for
SysMon domains and control stations, for FoxCTS domains and workstations.

3
B0193VV – Rev K 1. Overview

System Monitor Domain


The System Monitor domain consists of one or more workstations whose operation is
monitored by the same System Monitor. If a control station is in the domain of a System
Monitor, the System Monitor can be configured to report a message whenever a checkpoint
occurs on that control station. The system configuration tools allows the specification of one
historian to receive System Monitor checkpoint messages.
The FoxCTS package supplies an installation procedure that:
♦ Replaces the name of the targeted historian with the name of a SMMR (System
Monitor Message Relay) process
♦ Installs the SMMR that will send all System Monitor messages to the original
destination and exactly one FoxCTS Server.
The FoxCTS package provides the tool D:\opt\foxind\cms\sysmon\scripts\GetSysMonDo-
mains, which can be used to list all the System Monitors in a system along with the names of the
stations that they monitor.

FoxCTS Process Areas


The FoxCTS Process Areas allows the FoxCTS administrator to associate selected workstation,
control stations and file tracking clients and with a name. The concept of a Process Area is useful
when a single FoxCTS Server is monitoring two or more generally independent operations.
While the FoxCTS software requires that every station be associated with a Process Area, there is
no requirement that more than one Process Area be defined. Figure 1-2 illustrates the
relationships. If no Process Area name is configured, then the default name, UNKNOWN, will
be used.

Figure 1-2. Entity Relationship Diagram Expanded to Show FoxCTS Process Areas

4
1. Overview B0193VV – Rev K

NOTE
A FoxCTS domain can encompass one or more process areas and each process area
can encompass one or more file servers, workstations, and control stations.
Remember that each file server, workstation, and control station can only belong to
one process area.

FoxCTS Related Logical Names


During the installation of the FoxCTS software as many as four logical names can be created and
each type can have many logical names assigned.

NOTE
Each logical name must be unique throughout a given system.

The list that follows are the four types of logical names that pertain to the FoxCTS package.
♦ The FoxCTS Server Logical Name - The FoxCTS Server module installation
automatically assigns the name FoxCTS<ServerLbug> as the FoxCTS Server’s
logical name.
♦ The FoxCTS ICCDRVR Logical Name - The FoxCTS ICC Driver module
installation automatically assigns the name ICCDRV<cphostletterbug> as the
FoxCTS ICCDRVR’s logical name.
♦ The FoxCTS SysMon System Monitor Message Relay (SMMRxx) Name - During the
FoxCTS SysMon module installation, a logical name is assigned. It is ultimately, the
responsibility of the person who installs the FoxCTS SysMon module to ensure that
the name of the FoxCTS SysMon process is unique.
♦ The FoxCTS Operator Action Journal Relay (OAJxx) Name - During the FoxCTS
Client module installation a logical name is assigned, but only if the OAJ Messaging
option is selected. It is ultimately, the responsibility of the person who installs the
FoxCTS Client module to ensure that the name of the FoxCTS OAJ process is
unique.

FoxCTS Server
The FoxCTS Server is the workstation that holds, configures and maintains the FoxCTS domain
database. The FoxCTS Server station also collects the changes made in a FoxCTS domain. The
change records are processed and recorded to the local FoxCTS change database hosted by the
Integrity software.
The FoxCTS product includes the required PAS Integrity software and CM license.

FoxCTS Configurator
Access to the FoxCTS Configurator is only allowed from the FoxCTS Server’s primary display
manager by FoxCTS users that have been assigned configurator access rights. The FoxCTS
Configurator provides FoxCTS domain management and FoxCTS user account management.
♦ User Account Management - includes the addition and modification of the FoxCTS
user accounts, user environments and user privileges.

5
B0193VV – Rev K 1. Overview

♦ Domain Management - includes identifying control stations, workstations, file


tracking clients, and the files to be tracked in the FoxCTS domain.

FoxCTS Client
A FoxCTS Client is a workstation which sends change information to the FoxCTS Server.

Local Login
If the FoxCTS Client station is unable to communicate to the FoxCTS Server, the FoxCTS user is
logged in locally. In this event no login information is recorded to the FoxCTS change database.
Any file tracking or CP change information generated during this time will be buffered at the
FoxCTS Client machine until communication to the FoxCTS Server is restored.
CP change information for ICC-hosted CPs will not be processed until the first checkpoint after
communication to the FoxCTS Server is restored. Additionally, during a local login session the
CP change information gathered, will be attributed to the user UNKNOWN.
File tracking information will not be processed until additional file tracking changes are noted on
the FoxCTS Client machine.

FoxCTS User Accounts


The FoxCTS user accounts are configured and maintained by the FoxCTS administrator using
the FoxCTS Configurator. The FoxCTS user account is used to control station access and
FoxView environment access.
FoxCTS users must login before gaining access to FoxView. The login process for FoxCTS Clients
serves two main purposes.
♦ It allows a means of tracking changes back to the FoxCTS user who made them.
♦ It offers a way to restrict access to FoxView environments based on the FoxCTS user
account.
The FoxCTS user remains in the selected environment until either a valid FoxCTS user login or
logout occurs. Changes that are detected during the FoxCTS user login session will be recorded
against the user in the FoxCTS change database.
The FoxView environments that are available to the FoxCTS user are assigned using the
FoxCTS Configurator, see the page 53 for details.

Standard Workstations
When the FoxCTS Client module is installed on a standard workstation, the initial FoxView
display is bare except for a single Login button. When the Login button is selected, a valid
FoxCTS user name must be entered.

Workstations with Security Enhancements


When the FoxCTS Client module is installed on a workstation with security enhancements, the
initial FoxView environment displayed is determined by the current Microsoft domain user in
conjunction with the FoxCTS user account settings.

TIP
FoxCTS does not support user names with a space in them.

6
1. Overview B0193VV – Rev K

To control FoxView and environment access, a FoxCTS user account must be created for each
Microsoft domain user account.

Operation
The FoxCTS product is a change-tracking package used to document modifications in a system.
The FoxCTS package is divided into six modules: Server, Client, SysMon, OAJ Host, ICC Driver
and PACTware. The FoxCTS package uses a client/server architecture.

FoxCTS Server
The FoxCTS Server receives notification of system events from the FoxCTS clients. These events
are collected by the FoxCTS Server for recording in the FoxCTS change database. The FoxCTS
Server module consists of the following:
♦ A domain database that contains the FoxCTS domain configuration.
♦ Scripts and programs which support the analysis of file changes and of changes to the
workstation.
♦ Scripts and programs which support the recording of system login/logout information
and CP change information.
♦ A utility that processes collected change data.
When configured, the FoxCTS Server collects:
♦ Login/logout messages from the FoxCTS Client stations.
♦ Checkpoint messages from the System Monitor assigned by the System Definition.
♦ File change information from FoxCTS client stations configured for file tracking.
♦ CP change information from FoxCTS client stations that are CP hosts.
♦ CP and FF device change information from Foxboro Evo Control Editors or IACC
Server configured for FoxCTS support.

NOTE
The enhanced OAJ messages are not recorded in the FoxCTS change database.
These message are recorded in the AIM*Historian database.

When the FoxCTS Server receives CP change or file change information, the FoxCTS
Server processes and collects the changes to be recorded in the FoxCTS change database.
The login activity information provided to the FoxCTS Server by the FoxCTS Client station is
used to associate the FoxCTS user to the recorded change.
Figure 1-3 describes how a configuration change to a control processor is tracked in Steps 1-6 and
then how a file change is tracked in Steps 7-9.

NOTE
FoxCTS change-tracking communications can be performed over the control
network or over the plant information network. It is strongly recommended that the
plant information network be used, to avoid unnecessary control network traffic.

7
B0193VV – Rev K 1. Overview

Figure 1-3. FoxCTS Operation on the System

The information flow for FoxCTS user login and control configurator activity is as follows:
1. The FoxCTS user logs into FoxView which generates a login message that is recorded
in the FoxCTS change database.
2. The ICC is used to make a change. Starting the ICC generates an ICC login message
to the FoxCTS Server. Making changes to the CP alters its memory. Exiting the ICC
generates an ICC logout message to the FoxCTS Server and generates a
checkpoint notification to the CP’s System Monitor.
a. The checkpoint message is sent to the FoxCTS SMMR process. The FoxCTS
SMMR process then sends the message to the FoxCTS ICCDRVR process.
b. The FoxCTS ICCDRVR process determines the CP changes made
c. The FoxCTS Server receives and collects the change information.

8
1. Overview B0193VV – Rev K

3. HART Device changes made via PACTware are accumulated and then transferred to
the FoxCTS Server every five minutes.
4. Configuration changes made via IACC and Field Devices are accumulated at the
IACC Server and then transferred to the FoxCTS Server every 5 minutes.
5. Configuration changes made via the Foxboro Evo Control Editors and Field Devices
are accumulated at the Foxboro Evo Control Editors Server and then transferred to
the FoxCTS Server every 5 minutes.
6. Someone or some program alters a tracked file on a FoxCTS Client station and the
FoxCTS Client notices the change. The FoxCTS Client prepares the change
information and sends it to the FoxCTS Server for recording.
7. The FoxCTS Server processes the collected change information for recording in the
FoxCTS change database.

FoxCTS Client
The purpose of the FoxCTS Client module is to notify the FoxCTS Server of FoxView login and
logout activities, to note tool invocations at the FoxCTS Client station, to generate enhanced OAJ
messages, and to track specified files residing on the workstation. The FoxCTS Client module
consists of:
♦ Scripts and programs to support the tracking of change data.
♦ Scripts and programs that monitors a list of local files.
♦ Scripts and programs to transfer collected change data to the FoxCTS Server.
♦ Scripts and programs to support enhanced OAJ messages.
♦ Scripts and programs to support Single and Dual User Reconfirmation.
The FoxCTS login and logout commands generate the login/logout events used to implement
FoxCTS user tracking. The logout activity can also be generated by the FoxCTS’s automatic
(time-based) logout utility, see “Inactivity Timers” on page 81.

FoxCTS Client Operation


The FoxCTS Client module installation alters the change environment method and adds a
FoxView login requirement.
In the case of a standard workstation, the FoxView changes are:
♦ The initial environment is altered to display a single Login button in the upper-
leftmost location of the menu bar.
♦ A new FoxCTS menu item has been added to all FoxView environments. The
FoxCTS menu includes these items: Admin (FoxCTS Configurator), Login, Logout,
Chg_Env (Change Environment), Passwd_Chg (Password Change) and User_Name.
The operation of each of these commands is discussed in this chapter.
In the case of a security enhanced workstation, the FoxView changes are:
♦ FoxView will automatically login the current domain user.
♦ A new FoxCTS menu item has been added to all FoxView environments. The
FoxCTS menu includes these items: Admin (FoxCTS Configurator), Login, Logout,
Chg_Env (Change Environment) and User_Name. The operation of each of these
commands is discussed in this chapter.

9
B0193VV – Rev K 1. Overview

NOTE
The FoxCTS Configurator (Admin) item is only available at the FoxCTS Server
station.

When FoxView is started, the environment specified by the display manager configuration file
(dmcfg) is used. At a FoxCTS Client station, this environment must always be Initial.
The FoxCTS client supplied initial environment differs from the FoxView default initial
environment in that it:
♦ Disables all OM sets
♦ Protects all access levels
♦ Turns off the alarm bar
♦ In the case of standard workstations, it places a menu item labeled Login on the menu
bar where Sys menu item is normally located
♦ Logs out any FoxCTS user who may have been previously using this display.
In the case of standard workstations, the Login menu item is used to tell the FoxCTS package that
a new user is assuming responsibility for this FoxView display. When the Login item is selected, a
login dialog box appears.
In the case of security enhanced workstations, the domain user is automatically logged in to
FoxView in accordance with their FoxCTS account settings.
When the FoxCTS user successfully logs in, the FoxView display will be changed to the user’s
default home environment. If the FoxCTS user authentication fails, the dialog box will
display the reason for the failure. See “FoxCTS Messages” on page 116 for information regarding
login messages. The login information is recorded by the FoxCTS Server.
If the FoxCTS Client station is unable to communicate to the FoxCTS Server the FoxCTS user
is logged in locally. (See “Local Login” on page 6 for details.)
Once a user has successfully logged into the FoxView display, the default home environment is
displayed along with the added FoxCTS menu item. The FoxCTS menu picks include:
♦ Admin - The Admin item allows access to the FoxCTS Configurator for
configuration of the FoxCTS domain and user account administration. This item can
only be accessed from the primary display manager of the FoxCTS Server and only if
the current FoxCTS user has the correct permissions.
♦ Login - The Login item works basically the same as the Login button in the FoxCTS
initial environment. Essentially, it logs out the current FoxCTS user and raises the
FoxCTS login dialog box.
♦ Logout - The Logout item logs out the current FoxCTS user from the FoxView
display, restores the initial environment, and records the log out event in the
FoxCTS change database.
♦ Chg_Env - To enhance security, the FoxCTS package modifies the mechanism used to
change FoxView environments. Once a FoxCTS user is logged into a FoxView display,
the Chg_Env item is available under the FoxCTS menu item. The Chg_Env item
raises a dialog box, which lists the environments accessible to the current FoxCTS
user.

10
1. Overview B0193VV – Rev K

♦ - This item can be used to change the password of the current FoxCTS
Passwd_Chg
user. This menu item is only available on standard workstations.
♦ User_Name - Use this item to determine who is currently logged in to a FoxView
display.

File Tracking
File tracking is configured and implemented using the FoxCTS Configurator. The file tracking
service monitors the list of specified files for changes by observing the file modification time
stored automatically by the file system. When the modification date changes and actual changes
to the file are detected, the polling process transmits the tracked file contents to the FoxCTS
Server.

NOTE
Only files and folders on local hard drives can be tracked.

If the monitored file is actually a directory, then every file in that directory and all subdirectories
are monitored.

TIP
If tracking a large directory that contains many sub-directories, begin tracking the
lower level directories first, adding the higher level directories to the tracking list at
a later time.

Enhanced OAJ Messages


If the enhanced OAJ messages option is selected during the installation of the FoxCTS Client
module, the FoxCTS user information will be added to standard OAJ messages. The enhanced
OAJ message option introduces the following changes:
♦ The D:\usr\fox\wp\data\wp51_glbls.all file is altered to enable the sending of OAJ
messages to the OAJ Client’s logical name. With this change, OAJ messages will no
longer be sent to the specified historian; rather, they will be sent to the OAJ client
software. The OAJ Client software will enhance the message and forward it to an
AIM* instance for recording.

NOTE
This change is only in effect on reboot or if a manual configuration by the user of
the OAJ configuration is performed.

♦ Scripts and programs that support adding the FoxCTS user information to standard
OAJ messages are installed.

11
B0193VV – Rev K 1. Overview

FoxCTS OAJ Host


The FoxCTS OAJ Host module stores the enhanced OAJ messages from the FoxCTS Client
stations to the AIM*Historian. The FoxCTS OAJ Host module introduces the following changes:
♦ Scripts and programs that support building enhanced OAJ messages from the
FoxCTS Client-provided information and inserting them into the AIM* Historian
database.
♦ The AIM*Historian database is altered to include a new message group for the
enhanced OAJ messages.

NOTE
The FoxCTS OAJ Host module can only be installed on workstation that hosts an
AIM*Historian database. This module requires an AIM*Historian instance for the
recording of the enhanced OAJ messages.

Figure 1-4 shows some of the data flow in a system that implemented the FoxCTS product with
the enhanced OAJ message support and AIM*AT software.

PC’s
(AIM*Inform)

AIM*Inform retrieves Enhanced


OAJ data for presentation

Plant Information Network


Enhanced
OAJ
Information

AW AW WP
(hosts CP’s) (FoxCTS Server) AIM*Historian

Enhanced OAJ
CIO changes Information
File monitor

Login and File Tracking Info

Control Network

CP PLC Gateway

Figure 1-4. FoxCTS and AIM*AT Software Integration

12
1. Overview B0193VV – Rev K

FoxCTS SysMon
The FoxCTS SysMon module notifies the FoxCTS Server when a CP checkpoint message is
received from a control station within its domain. The FoxCTS SysMon software consists of:
♦ Scripts and programs that support the replacement of the System Monitor targeted
historian name with the name given to the smonMsgRelay process (SMMRxx).
♦ Scripts and programs that wait for the receipt of a CP checkpoint message, then
forwards that message on to the FoxCTS Server and the appropriate FoxCTS ICC
Driver.

NOTE
The FoxCTS SysMon module must be installed on each System Monitor host that
monitors ICC-hosted control stations in the FoxCTS domain.

FoxCTS ICC Driver


The FoxCTS ICC Driver module wraps the current scripts that invoke the ICCDRVR, so that
any future invocation of ICCDRVR will result in FoxCTS Server notification. It also receives CP
checkpoint messages from the CPs it hosts and performs change analysis. The FoxCTS ICC
Driver module consists of the following:
♦ Scripts and programs that support analysis of CP changes.
♦ Scripts and programs that wrap the iccdrvr task and other utilities (e.g. load_all and
save_all), and report their invocation to the FoxCTS Server.
When configured, the FoxCTS ICC Driver module can receive CP checkpoint messages
forwarded by the System Monitor assigned by the System Definition.

NOTE
The FoxCTS ICC Driver module must be installed on the control station boot host
for every ICC controlled control station in the FoxCTS domain.

FoxCTS PACTware
The FoxCTS PACTware module is installed on any workstation where PACTware software is
installed and change data is to be collected.
The FoxCTS PACTware module consists of the following:
♦ Scripts and programs that force a FoxCTS PACTware user login when PACTware is
invoked.
♦ Scripts and programs that report the initial PACTware baseline and subsequent “Store
to Device” events to the FoxCTS Server.

NOTE
The FoxCTS PACTware module is only installed on workstations where the
PACTware software is installed and change data is to be collected.

13
B0193VV – Rev K 1. Overview

Limitations
Daylight Savings Time
If the system administrator moves the time back one hour in support of daylight savings time, the
following can occur.
♦ Operator Action Journal entries can have the same time tags.
♦ File tracking and ICC changes made during the repeated hour may not be picked up
until the next change. For example if the /etc/hosts file was edited before the time
change at 1:30am and then again at 1:05am, after the time has been set back, this
change will not be recorded individually. However, this change will be picked up
during the next file edit after the 1:30am time stamp to that editing user.
♦ Multiple file tracking and configurator changes made during this period may not be
recorded. For example if the /etc/hosts file was edited before the time change at
1:30am and then again at 1:05am, after the time has been set back, this change will
not be recorded individually. If the file is edited again at 1:20am, after the time has
been set back, and the same lines have been modified the changes made at 1:05am will
not be recorded and the changes made at 1:20am will be picked up during the next
file edit after the 1:30am time stamp.

Control Stations Baseline


After FoxCTS has been configured, all FoxCTS control stations and FF devices identified for
change tracking should have a baseline created. For ICC-hosted control stations, failure to
perform the initial baseline results in the FoxCTS product not recording the first set of changes
made to the control station.

Foxboro Evo Control Editors


Initial baselines for Foxboro Evo Control Editors-hosted CPs are created when the Foxboro Evo
Control Editors’ FoxCTS tracking option is activated.
Reference the Control Database Deployment User’s Guide (B0750AJ) for instructions on activating
the FoxCTS tracking feature.

IACC
There are two approaches for creating baselines for IACC-hosted CPs after the FoxCTS tracking
feature has been activated.
1. Initialize the IACC-hosted CP. Once the CP is back online, perform an IACC
download for the CP.
2. Temporally switch the CP from IACC-hosted to ICC-hosted. Once the switch is
made, perform an ICC checkpoint. Note that this option will require that the
FoxCTS ICC Driver module be installed on the station that hosts the CP and the
FoxCTS SysMon module be installed on the System Monitor station that hosts the
CP, prior to the checkpoint.
Reference the I/A Series System Configuration Component (IACC) User’s Guide (B0700FE) for
instructions on activating the FoxCTS tracking feature.

14
1. Overview B0193VV – Rev K

ICC
The FoxCTS package treats the first checkpoint of the CP as the signal to create the baseline for
the FoxCTS change database.

FOUNDATION Fieldbus Devices


The commissioning procedure for Foundation Fieldbus devices will create the initial baseline for
the FoxCTS change database.

Foxboro Evo Control Editors


The use of user accounts is vital to the secure and traceable operation of both the Foxboro Evo
Control Editors and FoxCTS packages; with each package maintaining its own independent set of
user accounts.
It is the Foxboro Evo Control Editors’ user account information that is used for recording to the
FoxCTS change database.

IACC Configurator
The use of user accounts is vital to the secure and traceable operation of both the IACC and
FoxCTS packages, with each package maintaining its own independent set of user accounts.
It is the IACC user account information that is used for recording to the FoxCTS change
database.

Control Configurator
The FoxCTS product has a narrow ability to associate users with changes made using the
configuration tools. These tools include:
♦ The FoxView Config>Control_Cfg>CIO_STN_Cfg menu item.
If the engineer makes changes using the CIO_STN_Cfg item, the FoxCTS
package associates that change with the FoxCTS user who entered the ICC from that
particular workstation.
♦ The NEW option of the ICC.
If the NEW option is selected at any time, the FoxCTS package is unable to
determine which control stations are being changed by the FoxCTS user. In these
cases, the FoxCTS package reports which FoxCTS users could have possibly made the
detected changes, based upon current user logins. To ensure that detailed tracking
information is available, every effort should be made not to use the NEW button,
♦ The FoxView Config>Control_Cfg menu item CIO_AP_Cfg has been eliminated.
This item was eliminated since there was no way to track changes to a particular user.
♦ The FoxView Config>Control_Cfg menu item CIO_Config has been replaced.
This item will now activate the FoxCTS ICCLaunch utility.

NOTE
The AIM*API software (Control Core Services v9.0 or I/A Series v8.8) or FoxAPI
software (I/A Series v8.5-v8.7) must be installed and configured for the ICCLaunch
utility to function properly. See “ICCLaunch” on page 99 for details.

15
B0193VV – Rev K 1. Overview

♦ The ICC Driver (ICCDRVR) task.


The FoxCTS package automatically provides a default user (ICCDRVR) for the ICC
Driver Task, and the iccprt, save_all and load_all scripts.
♦ The ICC API.
Changes made using the ICC API directly are recorded, but no specific user is
assigned. The Device Integrator Configurator, that is available only for Microsoft
Windows operating systems, also uses the ICC API directly.

CP Initialization
After a CP has been initialized from the Control Configurator, the Control Configurator must be
exited immediately. A CP initialization triggers a Control Configurator session logout of the
current FoxCTS user, even though the Control Configurator remains open. If the Control
Configurator remains open, all future records created during this session will be recorded to the
user, UNKNOWN.

FoxCTS System Modifications


Primary Domain Controller
FoxCTS transfers files between the FoxCTS Server and its clients. For workstations with security
enhancements, FoxCTS provides a mechanism to create a non-interactive user account, groups
and policies on the Primary Domain Controller required for successful file transfers.
The following are the changes that are made to the Primary Domain Controller.
1. The non-interactive user account, FoxCTSServices, is created.

Figure 1-5. FoxCTSService Account

16
1. Overview B0193VV – Rev K

2. The FoxCTSServices and FoxCTSNetworkAccount groups are created.

Figure 1-6. FoxCTS Groups

3. Three FoxCTS policies are created.


a. Figure 1-7 shows the settings for the FoxCTS Base Domain Controllers policy.

Figure 1-7. FoxCTS Base Domain Controllers Policy

17
B0193VV – Rev K 1. Overview

b. Figure 1-8 shows the settings for the FoxCTS Computer policy.

Figure 1-8. FoxCTS Computers Policy

c. Figure 1-9 shows the settings for the FoxCTS Remote Desktop Servers policy.

Figure 1-9. FoxCTS Remote Desktop Servers

18
1. Overview B0193VV – Rev K

FoxCTS Server Modifications


The installation of the FoxCTS Server module makes several changes to the station. These
changes include:
♦ Addition of several Windows Services.
♦ Creation of the FoxCTS domain database in Microsoft SQL Server.
♦ Reduction of available disk space. (Disk space requirements will be impacted as the
database grows.)

FoxCTS OAJ Host Modifications


The installation of FoxCTS OAJ Host module makes several changes to the AIM*Historian host
on which it is installed. These changes include:
♦ Addition of a Windows Service.
♦ Modification of the message template definition file used by the AIM*Historian.

FoxCTS Client Modifications


This section discusses the system modifications made to a FoxCTS Client during the installation
process.

NOTE
All scripts that are changed during the FoxCTS Client installation will be changed
back to their pre-FoxCTS installation state when the FoxCTS Client module is
uninstalled.

Existing Environments
The following changes are made to the existing FoxView environments.
♦ The existing FoxView environments are moved from the standard locations to subdi-
rectories under d:/opt/foxind/cms/clnt/env.
♦ A new environment, CTS_ENV is created for the default FoxCTS administrator
accounts.
♦ Each existing environment is modified to include the FoxCTS menu item, as dis-
cussed on page 88.

Initial Environments
The FoxCTS Client module installation process places one or more copies of the FoxCTS initial
environment in the standard FoxView environment location, D:\opt\fox\env. The environment
names for these files are determined by the initial environment specified for each display manager
in the display manager configuration file (D:\opt\fox\customer\hi\dmcfg).
These initial environments are, by default, very restrictive. If the FoxCTS administrator does not
wish the initial environment to be as restrictive, for example, in a plant that does not want
operators to log in, the administrator must edit these environments accordingly. (See “Customiz-
ing the FoxCTS Initial Environments” on page 82 for details.)

19
B0193VV – Rev K 1. Overview

Environment Change Mechanism


The FoxCTS Client module installation provides a new mechanism for accessing the environ-
ments allowed to each FoxCTS user. When a FoxCTS user logs in, they are is put into their
default FoxView home environment. A FoxCTS user’s home environment, available environ-
ments and FoxCTS Configurator access rights are defined by the FoxCTS administrator.

Tool Access
All tools available from FoxView are wrapped to support FoxCTS user activity tracking. An
example of these various tools are the Display Builder, Display Alarm Configurator, Display
Configurator, Font Editor, AIM*Historian software, Palette Editor, Report Writer, PLB Monitor,
etc.

OAJ Enhanced Messaging Modifications


If the OAJ tracking option is selected during the FoxCTS Client installation, then the
D:\usr\fox\wp\data\wp51_glbls.all file is altered to enable the sending of OAJ messages to the
OAJ Client’s logical name. With this change, OAJ messages will no longer be sent to the specified
historian; rather, they will be sent to the OAJ client software. The OAJ Client software will
enhance the message and forward it to an AIM* instance for recording.

Integrated Control Configurator Access


Upon the installation of FoxCTS Client module the FoxView script that accesses ICC is replaced
with a new script, which logs ICC session information to the FoxCTS change database.

NOTE
FoxCTS users do not directly login/logout of the ICC.

The FoxCTS Client module forces login/logout to each FoxView display and
because the ICC is accessed from a FoxView display, the FoxCTS package can
associate the FoxCTS user to the display accessing the ICC.

Login Mechanism
For standard workstations, once the FoxCTS Client module has been installed, the Login and
Help buttons are the only items available at the initial FoxView startup. If a login is not
successful, a user cannot access any of the FoxView environments. The workstation users are
forced to log in as valid FoxCTS users before gaining access to FoxView.
For security enhanced workstations, once the FoxCTS Client module
Once the FoxCTS user has logged into a FoxView display, they can perform all the display
manager functions as described in the FoxView documentation. The FoxCTS software does not
alter the use of the FoxView displays.
For workstations with security enhancements, once the FoxCTS client module has been installed,
the domain user, in conjunction with FoxCTS user account settings, will control FoxView access.

20
1. Overview B0193VV – Rev K

FoxCTS SysMon Modifications


The installation of FoxCTS SysMon module makes the following change to the System Monitor
host:
♦ Modifies the destact.cfg file used by the System Monitor to specify its message
destinations.

FoxCTS ICC Driver Modifications


The installation of FoxCTS ICC Driver Task module results in several changes to the
workstation:
♦ Replaces the following files with a FoxCTS version: D:\opt\fox\ciocfg\api\iccdrvr.tsk,
iccprt, save_all, load_all.

FoxCTS PACTware Modifications


The installation of FoxCTS PACTware module results in several changes to the workstation:
♦ Adds files to the existing PACTware directories APP and ADDINS for use with
FoxCTS.

21
B0193VV – Rev K 1. Overview

22
2. Installation Planning
This chapter reviews the planning process recommended to take prior to the installation of the
FoxCTS modules.
Read the material in the following sections carefully and consider the information prior to
installing the FoxCTS product. The more planning that is done prior to installation, the easier the
installation will be.
The following is a list of issues to consider prior to installing the FoxCTS modules.
♦ Skills required by FoxCTS administrator and other users.
♦ Check that the system resources meet the FoxCTS module requirements.
♦ Review and standardize your current FoxView environments on all machines that will
be FoxCTS Clients. See “FoxCTS Client Modifications” on page 19 for more
information.
♦ Review the display manager configuration file, dmcfg, to ensure that the proper
environments are specified for reboot/restart of the display manager. See “Initial Envi-
ronments” on page 19 for more information.
♦ Decide whether or not the workstations requires a user login after it boots.
♦ Complete the FoxCTS module installation worksheets, see Appendix A “Worksheets”.

Skills
Installation and Configuration
Configuration of the FoxCTS product requires knowledge of your systems configuration. In
particular:
♦ A general working knowledge of the system.
♦ A knowledge of the machine’s operating system.
♦ The CPs letterbugs. (See the file D:\etc\cplns.)
♦ The stations letterbugs. (See the D:\usr\fox\sp\hldb file for a list of station letterbugs
and station type codes. Contact the Invensys Global Customer Support Center at
866-746-6477 (US) or http://support.ips.invensys.com, for information regarding
station type codes.

FoxCTS Administrator
This person usually installs, configures, and maintains the FoxCTS product. Typically, the
FoxCTS administrator requires the highest level of skills. The following is a list of the
FoxCTS administrator skill requirements:
♦ An understanding of standard services:
♦ System Monitor
♦ Control Configurator

23
B0193VV – Rev K 2. Installation Planning

♦ FoxView environments
♦ System checkpoints
♦ An understanding of how the system is divided. For example, which machines will be
the FoxCTS Server(s), which systems will be monitored, which machines are the
workstation clients, and file tracking clients.
♦ An understanding of the concept of creating FoxCTS users.

System Requirements
The system requirements for the six FoxCTS modules are discussed in this section.

Supported Control Core Services and I/A Series Software


Versions
FoxCTS version 6.01.00 currently supports the following software versions:
♦ I/A Series Software v8.5 - v8.8 Standard or Security Enhanced with default domain
group policies.
♦ Control Core Services v9.0 Standard or Security Enhanced with default domain
group policies.

NOTE
When using security enhanced workstations please be aware that changing the
Invensys provided default domain group policies or improperly using McAfee®
ePolicy Orchestrator (ePO) firewall can adversely affect the proper operation of
FoxCTS. Modifying Active Directory Group Policies is considered an advanced
action and should only be undertaken by qualified personnel. Use of any firewall,
including the Invensys authorized McAfee ePO firewall could also adversely affect
the functionality of FoxCTS if not configured properly. Care should be taken to
closely follow instructions provided by the following documents: Security Enhance-
ments User’s Guide for I/A Series Workstations (Windows 7 or Windows Server 2008
Operating Systems) (B0700ET), and Optional McAfee Security Products Installation
and Configuration Guide (B0700EX).

FoxCTS Server Module


The FoxCTS Server module must be installed on a workstation with adequate disk space, CPU
idle time and RAM. The FoxCTS Server station can also function as a FoxCTS Change Database
Server, FoxCTS Client, file tracking client, OAJ host, and SysMon host.
The minimum requirements for the FoxCTS Server Module are:
♦ Approximately 11 GBs of disk space required for the FoxCTS databases.
♦ A CD-ROM used for installation.

24
2. Installation Planning B0193VV – Rev K

FoxCTS OAJ Host Module


The FoxCTS OAJ Host module requires the following minimum configuration for proper
installation and operation:
♦ AIM*Historian Version 3.3 or greater is installed licensed, configured and running
with an instance on the machine where the FoxCTS OAJ Host Module is to be
installed.

FoxCTS Client Module


The FoxCTS Client module requires the following minimum configuration for proper
installation and operation:
♦ If OAJ enhanced messaging is to be installed then AIM*Historian Version 3.3 or
greater must be installed and configured somewhere on the system.
♦ If the ICCLaunch utility is to be used, the AIM*API software (Control Core Services
v9.0 or I/A Series Software v8.8) or FoxAPI software (I/A Series Software v8.5-v8.7)
must be installed and configured on the FoxCTS Client station.

FoxCTS SysMon Module


The FoxCTS SysMon module requires the following minimum configuration for proper
installation and operation
♦ ICC is used for the control configurations.

FoxCTS ICC Driver Module


The FoxCTS ICC Driver module requires the following minimum configuration for proper
installation and operation:
♦ ICC is used for the control configurations.

FoxCTS PACTware Module


The FoxCTS PACTware module requires the following minimum configuration for proper
installation and operation:
♦ Installation of the PACTware software.
♦ Only one PACTware version can be installed on the machine.

25
B0193VV – Rev K 2. Installation Planning

Installation Overview
This section provides a brief installation overview of the FoxCTS modules.

FoxCTS Server
The FoxCTS Server module can only be installed on workstations.
♦ Install the PAS Integrity software. The Integrity software and license is included as
part of the FoxCTS product.
♦ License and configure the Integrity software.
♦ Install the FoxCTS Server module, “FoxCTS Server” on page 36.
♦ Configure the FoxCTS domain, “FoxCTS Domain Configuration” on page 53. (The
FoxCTS domain can only be configured on the FoxCTS Server after the
FoxCTS Client module has been installed.)

FoxCTS OAJ Host


The FoxCTS OAJ Host module can only be installed on workstations.
♦ Install AIM*Historian software.
♦ Create AIM*Historian Instance.
♦ Install FoxCTS OAJ Host module. For installation instructions see “FoxCTS OAJ
Host Module” on page 40.

FoxCTS Client
The FoxCTS Client module can only be installed on workstations.
♦ Install and configure the AIM*API software (Control Core Services v9.0 or I/A Series
Software v8.8) or FoxAPI software (I/A Series v8.5-v8.7). The FoxCTS Client module
replaces the FoxView Config>Control_Cfg menu item CIO_Config with the Fox-
CTS ICCLaunch utility. See “ICCLaunch” on page 99 for details.
♦ Install the FoxCTS Client module. For installation instructions see “FoxCTS Client
Module” on page 42.

FoxCTS SysMon (Optional)


The FoxCTS SysMon module should only be installed on workstations that are System Monitor
hosts, provided ICC is used to configure the CPs.
♦ Install the FoxCTS SysMon module. For installation instructions see “FoxCTS Sys-
Mon Module” on page 45.

FoxCTS ICC Driver (Optional)


The FoxCTS ICC Driver module should only be installed on workstations that are CP Hosts,
provided ICC is used to configure the CPs.
♦ Install the FoxCTS ICC Driver module. For installation instructions see “FoxCTS
ICC Driver Module” on page 47.

26
2. Installation Planning B0193VV – Rev K

FoxCTS PACTware (Optional)


The FoxCTS PACTware module should only be installed on a workstation where PACTware
change data is to be collected.
♦ Install the FoxCTS PACTware module. For installation instructions see “FoxCTS
PACTware Module” on page 49.

FoxCTS Worksheets Overview


This section discusses the FoxCTS module installation and FoxCTS domain configuration work-
sheets that are provided in Appendix A “Worksheets”. These worksheets have been developed as a
tool to assist the FoxCTS administrator in gathering and organizing information required for the
configuring of the FoxCTS modules. The worksheets are divided into two categories.
♦ FoxCTS Module Worksheets - These worksheets are used during the FoxCTS
module installations.
♦ Module Overview Worksheet - This master worksheets identifies the work-
stations that will be part of the FoxCTS Domain and identifies what FoxCTS
modules will be installed on each workstation.
♦ Server Module Worksheet - Identifies the workstation that will be FoxCTS Server
and how the FoxCTS Server is to be configured during installation.
♦ Client Module Worksheet - Identifies the workstations that will be FoxCTS
Clients and how the FoxCTS Clients are to be configured during installation.
♦ OAJ Host Module Worksheet - Identifies the workstations that will support
FoxCTS Enhanced OAJ messages and how the FoxCTS OAJ Hosts are to be
configured during installation.
♦ SysMon Module Worksheet - Identifies the workstations that will be installed
with FoxCTS SysMon software and how FoxCTS SysMon is configured during
installation.
♦ ICC Driver Module Worksheet - Identifies the workstations that will be installed
with ICC Driver software and how FoxCTS ICC Driver is configured during
installation.
♦ PACTware Module Worksheet - Identifies the workstations that will be installed
with PACTware software and how FoxCTS PACTware is configured during
installation.
♦ FoxCTS Domain Configuration Worksheets - These worksheets are used in the
FoxCTS Domain configuration process.
♦ Process Area Worksheet - Assigns process areas to the FoxCTS Domain.
♦ Control Station Worksheet - Assigns control stations to the FoxCTS Domain.
♦ Workstation Worksheet - Assigns workstations to the FoxCTS Domain.
♦ File Tracking Client Worksheet - Identifies the file tracking clients workstations.
♦ File/Directory Tracking Worksheet - Identifies the files and directories to be
tracked.
♦ Environments Worksheet - Assigns FoxView environments that will be used by
FoxCTS users.

27
B0193VV – Rev K 2. Installation Planning

♦ Groups Worksheet - Associates group names to environments.


♦ User Types Worksheet - Associates user types names to default environments and
group environments.
♦ User Accounts Worksheet - Identify FoxCTS user account information.

Standard FoxView Environments Modifications


A FoxView environment consists of:
♦ A set of menu bar items that define what displays and programs a user may access.
♦ A set of protection classes, also known as access levels, that control what items in the
menus and object on the graphics are available for manipulation by the operator.
♦ An optional password, which has to be entered before the environment is changed.
♦ A set of environment specific actions to take when the environment is entered.
The physical representation of the concept of an environment is contained in the environment
file. The FoxView environment files are located in the directories D:\opt\fox\env,
D:\opt\customer\env, and/or a user specified directory.
Environment files are invoked in one of two manners:
♦ Through user selection
♦ At startup as specified by the display manager configuration file
(D:\usr\fox\customer\hi\dmcfg).
The standard environments shipped are not the best examples of environment file configurations.
Because each environment selection can affect the next environment selected, ensure that the
following suggested changes have been addressed in every environment file prior to FoxCTS
Client module installation.
1. Direct the FoxView display manager to delay the Operation Action Journal (OAJ)
message until the FoxView environment password has been successfully entered
(dmcmd nologscr).
2. Invoke the FoxView Environment Password screen (blue screen with a data entry box)
if a password has been configured for this environment (dmcmd passwd).
3. Log the environment change to the OAJ (dmcmd chng_env).
4. Protect all protection classes/access levels (dmcmd protect all).
5. Unprotect the particular protection classes/access levels appropriate for this
environment (dmcmd unprotect value 0-10,100).
6. Enable or disable Object Manager sets as appropriate to the environment
(dmcmd enable omsets or dmcmd disable omsets).
7. Set up the menu buttons (dmcmd button x <label> <pathname|command>).
8. Call an initial display (dmcmd <pathname>).
9. Perform other site-specific actions.

28
2. Installation Planning B0193VV – Rev K

FoxView Example
A FoxView environment consists of as many as five files each with a different extension and
purpose. The file extensions and their meanings are listed below.
.env - This is the master environment file. It is the file that FoxView reads initially. This file
causes FoxView to take certain common actions and to execute the other files.
.mbr - This script sets the FoxView menu bar.
.dbr - This script sets the FoxView display bar. It specifies the size and shape of the icons along
the left side of the FoxView process graphic area. These icons are shortcuts to common displays.
.acl - This script is intended as the location for the protect/unprotect and setacl commands
The standard FoxView Process Operator’s environment files are located in the D:\opt\fox\env
directory. The standard FoxView environments are deficient because not all the possible file types
are supplied. Table 2-1, Table 2-2 and Table 2-3 show the standard Operator environment files
and their configuration.

Table 2-1. Standard Operator.env File

Environment File Lines Comments


dmcmd nolog_script Delays the sending of an OAJ message until the environment
change is complete, i.e., when the password, if any, has been
successfully entered.
dmcmd passwd Puts up the standard blue FoxView Password screen if a password is
configured. If the password is entered successfully the rest of the
script runs. If it is not, control returns to the previous environment.
dmcmd chng_env Generates an OAJ message saying that the environment has been
changed.
$ENV_DIR/Operator.acl Invokes the script that sets the access levels (protection classes).
$ENV_DIR/Operator.dbr Invokes the script that sets the display bar icons/buttons.
$ENV_DIR/Operator.mbr Invokes the script that sets the menu bar.
$ENV_DIR/Operator.dms Invokes the script that runs the environment specific display
manager scripts.

Table 2-2. Standard Operator.mbr File

Environment File Lines Comments


dmcmd script Identifies that what follows is a set of display manager
commands.
dmcmd mruflush Clears the most recently used file list from the File menu.
Button -1 &File
$ENV_DIR/file.mnu
Button -1 &Disp /opt/menus
Button -1 Disp_&1 /opt/menus/d1
Button -1 Disp_&2 /opt/menus/d2

29
B0193VV – Rev K 2. Installation Planning

Table 2-2. Standard Operator.mbr File (Continued)

Environment File Lines Comments


Button -1 &Help
$ENV_DIR/help.mnu

Table 2-3. Standard Operator.dbr File

Environment File Line Comments


dmcmd script Identifies that what follows is a set of
display manager commands.
dmcmd dbar_tmplt $FV_DBAR/icon_display_bar Sets the display bar to icon mode.
dmcmd dbar_button 1 "dmcmd chng_env_dlg" -l Sets up a change environment button.
"Change Env" -b $FV_DBAR/chgenv.i
dmcmd dbar_button 2 "dmcmd stddisp" -l "Select Sets up a FoxSelect button.
Screen" -b $FV_DBAR/selscrn.i
dmcmd dbar_button 3 "dmcmd psc" -l "Print Screen" -b Sets up a Print Screen button.
$FV_DBAR/printer.i
dmcmd dbar_button 4 $INITDSP Sets a display shortcut button.
dmcmd dbar_button 5 /opt/menus/demo/centrifuge Sets a display shortcut button.
dmcmd dbar_button 6 /opt/menus/demo/extraction Sets a display shortcut button.
dmcmd dbar_button 7 /opt/menus/demo/overlay1 Sets a display shortcut button.
dmcmd dbar_button 8 /opt/menus/demo/asceptic_pack Sets a display shortcut button.

If the .acl environment file does not exist for this environment, add a .acl file to hold the
commands to enable/disable OM sets and to set the appropriate protection classes.Table 2-4
illustrates the Initial environment’s .acl file and Table 2-5 is an example of an Operator
environments .acl file that will allow full access.

Table 2-4. Initial .acl File Example

Environment File Line Comments


dmcmd script Identifies that what follows is a set of display
manager commands.
dmcmd protect all Disables all access levels/protection classes.
dmcmd disable omsets Prevents the operator from making set point and
other changes to the control stations.
dmcmd alarm_bar off Suppresses the alarm bar.

30
2. Installation Planning B0193VV – Rev K

Table 2-5. Operator .acl File Example

Environment File Line Comments


dmcmd script Identifies that what follows is a set of display
manager commands.
dmcmd unprotect all Enables all access levels/protection classes.
dmcmd enable omsets Allows the operator to make set point and other
changes to the control stations.
dmcmd alarm_bar on Displays the alarm bar.

Display Manager Configuration File


The display manager configuration file, D:\usr\fox\customer\hi\dmcfg, defines the
characteristics of the FoxView’s displays running on each workstation. Defined characteristics
include:
♦ Update rates
♦ FoxView logical names
♦ Alarm Manager names and associations
♦ Size
♦ Initial environment after reboot/restart of a FoxView display manager.
During the installation of the FoxCTS Client module, protected environments are created in the
standard location (D:\opt\fox\env) based on the information retrieved from the dmcfg file.
As a result, the desired Initial Environment for each FoxView display manager may or may not
exist after installation.

TIP
The D:\usr\fox\customer\hi\dmcfg file is read during installation and having it
correct on the workstation prior to installation will reduce the configuration effort.

It is recommended that the dmcfg file be identical on all the workstations and that it contain all
the information for each workstation in the system. It is strongly advised that the dmcfg files be
reviewed and standardized before the installation of the FoxCTS Client module.

FoxCTS Optional Login Configuration


Another common issue among FoxCTS users is whether or not the operators are required to log
into an workstation in order to use it. Different plants take strong positions on each end of the
issue.
Though by default the FoxCTS package requires initial log in, it does support going to the
operator’s environment without a login when the workstation reboots or the display manager
restarts.
If operators are not required to log into the workstation before use, the following configuration is
recommended:

31
B0193VV – Rev K 2. Installation Planning

♦ Decide which environment is started on the workstation when a FoxView display


manager restarts or workstation reboot occurs.
♦ Set the FoxView display manager configuration file to specify that environment name.
♦ Install the FoxCTS Client module.
♦ Alter the FoxView files.
See “Customizing the FoxCTS Initial Environments” on page 82 for details on customizing the
FoxCTS Client initial environment files and logins.

Foxboro Evo Control Editors Integration


Refer to the latest version of the Control Database Deployment User’s Guide (B0750AJ), for Fox-
CTS implementation instructions.

TIP
The Foxboro Evo Control Editors require that every workstation that hosts a CP,
where change tracking is to be recorded, be configured with the FoxCTS Server
name.

The initial Foxboro Evo Control Editors baseline for the FoxCTS change database is created when
the FoxCTS option is activated in the Foxboro Evo Control Editors.

IACC Integration
Refer to the latest version of the I/A Series System Configuration Component (IACC) User’s Guide
(B0700FE), for FoxCTS implementation instructions.

TIP
The IACC software requires that every workstation that is a System Monitor Host
and monitors CPs in the FoxCTS Domain, be configured with the FoxCTS Server
name.

The IACC initial baseline for the FoxCTS change database is created on a per-CP basis when the
following steps are followed:
1. The IACC option for FoxCTS change tracking support is configured and enabled.
2. Use one of the following techniques to create the baseline:
a. Use IACC to initialize and download each CP.
b. Temporarily switch each CP to ICC control and perform a checkpoint. Once the
checkpoint is complete, switch the CP back to IACC control. (This option will
require that the FoxCTS SysMon and FoxCTS ICC Driver modules are installed
at the time of the baseline checkpoint.)

32
2. Installation Planning B0193VV – Rev K

PACTware Integration
The initial PACTware device baseline for the FoxCTS change database is created during the first
PACTware upload of the device.

33
B0193VV – Rev K 2. Installation Planning

34
3. Installation
This chapter deals with the installation of the FoxCTS modules.
Installation and configuration of the FoxCTS software is not a trivial process. It is a good idea to
review the “Installation Planning” on page 23 section of this manual prior to installation of any
FoxCTS module.
To save time and reduce the chance of errors, be sure to complete the installation worksheets in
Appendix A “Worksheets” before attempting to install the FoxCTS product.
Be sure to note the following information before proceeding with the installation of any FoxCTS
module.
♦ Complete the FoxCTS module(s) installation at the workstation before starting the
next workstations installation. This will help ensure that duplicate logical names are
not suggested during the installation process.
♦ If the workstation is rebooted after the FoxCTS module installation, be sure that the
station reboot is complete before installing the next workstation.

Primary Domain Controller


A Primary Domain Controller (PDC) that supports workstation running Control Core Services
v9.0 or I/A Series Software v8.8 must be configured prior to the installation of any FoxCTS
module. This procedure will create a user, groups and policies required to support the FoxCTS
RcpRshSvc Service in a secured domain.

TIP
No FoxCTS modules are actually installed on the Primary Domain Controller.

The Primary Domain Controller must be configured prior to installing any FoxCTS module on
an workstation.
1. Log in to the Primary Domain Controller as a domain administrator.
2. Using the FoxCTS for Windows media, start the domain configuration process by
right-clicking the E:\FoxCTS\PDC\FoxCTSBuild.bat file and selecting the “Run as
administrator” option.
If any errors are reported while running the FoxCTSBuild.bat file, they must be
corrected. Once the corrections have been made, rerun the FoxCTSBuild.bat file.
3. Verify that the FoxCTS security policies match the settings found in Figure 1-7,
Figure 1-8 and Figure 1-9.

TIP
Do not proceed with installing the FoxCTS modules until the PDC configuration is
complete and correct.

35
B0193VV – Rev K 3. Installation

FoxCTS Server
This section describes the FoxCTS Server module installation on a workstation.

Microsoft SQL Server Software


Microsoft SQL Server® software must be installed before the installation of the FoxCTS Server
module. The FoxCTS media includes a copy of Microsoft SQL Server 2008 Express Edition (for
use with Control Core Services v9.0 or I/A Series Software v8.8) and Microsoft SQL Server 2005
Express Edition (for use with I/A Series Software v8.5-v8.7).

NOTE
If Microsoft SQL Server 2008 or Microsoft SQL Server 2005 software is already
installed on the workstation, the installation of the Microsoft SQL Server Express
Edition software is not necessary.

Installation for Control Core Services v9.0 or I/A Series Software v8.8
To start the Microsoft SQL Server 2008 Express Edition software installation process on an work-
station running Control Core Services v9.0 or I/A Series Software v8.8:

TIP
Only use the installation procedures found in this manual to install the Microsoft
SQL Server 2008 Express Edition software.

1. Install the Microsoft SQL Server 2008 Express Edition software. When installing on
workstations with security enhancements, log in as a domain user that is a member of
the “IA Installer” and “Domain Admin” groups but do not use the “iainstaller”
account.
2. Disconnect all shared drives prior to installing SQL Server Express. The SQL Server
Express installation investigates all mounted drives and network/shared drives and this
process can minutes to hours to complete.
3. Using the FoxCTS for Windows media, start the SQL Server installation process by
selecting the E:\SqlSrvr\SQL2008\SQLEXPR_x86_ENU.exe file.
4. At the Open File - Security Warning window select Run.
5. If the User Account Control window appears, select Yes to allow the installation of
the software.
6. At the SQL Server Installation Center select New installation or add fea-
tures to an existing installation.
7. At the License Terms window accept the license agreement and select Next.
8. At the Features window take the default settings but change the installation directory
to D:\Program Files (x86)\Microsoft SQL Server\ and select Next.
9. At the Instance Configuration window change the Instance root directory to
D:\Program Files (x86)\Microsoft SQL Server\ and select Next.
10. At the System Configuration window change the SQL Server Database Engine to
NT AUTHORITY\SYSTEM and select Next.

36
3. Installation B0193VV – Rev K

11. At the Database Engine Configuration window take the default settings and select
Next.
12. At the Error Reporting window take the default settings and select Next.
13. At the Complete window select Close.
14. Close the SQL Server Installation Center window.
Continue with the installation of the Microsoft SQL Management Studio:
1. At the Open File - Security Warning window select Run.
2. If the User Account Control window appears, select Yes to allow the installation of
the software.
3. At the SQL Server Installation Center select New installation or add fea-
tures to an existing installation.
4. At the Installation Type windows take the defaults and select Next.
5. At the License Terms window accept the license agreement and select Next.
6. At the Features window take the default settings and select Next.
7. At the Error Reporting window take the default settings and select Next.
8. At the Complete window select Close.
9. Close the SQL Server Installation Center window.
10. Installation of the Microsoft SQL Server 2008 Express Edition is now complete.
11. Use Windows Services to verify that the SQL Server (SQLEXPRESS) Service is set to
Log On As Local System. If it is not, adjust accordingly.
12. Installation of the Microsoft SQL Server 2008 Express Edition is now complete.
13. If installing on workstations with security enhancements, proceed to “SQL Server
Configuration” on page 39.

Installation for I/A Series Software v8.5-v8.7


To start the Microsoft SQL Server 2005 Express Edition software installation process on a work-
station running I/A Series Software v8.5-v8.7:

TIP
Only use the installation procedures found in this manual to install the Microsoft
SQL Server 2005 Express Edition software.

1. Install the Microsoft SQL Server 2005 Express Edition software as a user that has
software installation privileges.
2. Using the FoxCTS media, start the installation process by selecting the
E:\SqlSrvr\SQL2005\SQLEXPR.EXE file.
3. Only use the installation procedures found in this manual to install the SQL Server.
4. At the Open File - Security Warning window select Run.
5. At the End User License Agreement window accept the license agreement and select
Next.
6. At the Installing Prerequisites window select Install.

37
B0193VV – Rev K 3. Installation

7. When the required components are installed successfully, select Next.


8. At the Welcome to the MSSQL Server Installation Wizard window select Next.
9. At the System Configuration Check window select Next.
10. At the Registration Information window fill-in the site specific information and
select Next.
11. At the Feature Selection window:
♦ Select Browse.
♦ Change the installation directory to D:\Program Files\Microsoft SQL
Server
♦ Select OK.
♦ Select Next.
12. At the Authentication Mode window select Next.
13. At the Error and Usage Report Settings window leave both boxes unchecked and
select Next.
14. At the Ready to Install window select Install.
15. At the Completing Microsoft SQL Server 2005 Setup window select Finish.
Continue with the installation of the Microsoft SQL Management Studio:
1. Select the SQLServer2005_SSMSEE.msi file.
2. At the Open File - Security Warning window select Run.
3. At the Welcome to the Install Wizard for Microsoft SQL Server Management Stu-
dio Express window select Next.
4. At the License Agreement window accept the license agreement and select Next.
5. At the Registration Information window select Next.
6. At the Feature Selection window select Next.
7. At the Ready to Install the Program window select Install.
8. At the Completing the Microsoft SQL Server Management Studio Express window
select Finish.
9. Installation of the Microsoft SQL Server 2005 Express Edition is now complete.
10. If installing on workstations with security enhancements, proceed to “SQL Server
Configuration” on page 39.

38
3. Installation B0193VV – Rev K

SQL Server Configuration


If the provided Microsoft SQL Server Express Edition software was installed, the following
modifications must be made.
1. Select Microsoft SQL Server 2008 R2 or Microsoft SQL Server 2005 from the Start
menu and double-click the SQL Server Management Studio Express item.
2. At the Connect to Server windows select Connect. (You should be using Windows
Authentication.)
3. From the Microsoft SQL Server Management Studio select the Security folder and
then the Login folder.
a. Double-click the BUILTIN\Users item from the list.
b. From the Login Properties - BUILTIN\Users window, select the Server Roles
item. Make sure that both the sysadmin and public boxes are checked. Select
OK when finished.
4. Close the Microsoft SQL Server Management Studio window.

FoxCTS Change Database


It is a good practice to install, license and configure the FoxCTS Change Database (PAS Integrity
software) prior to the installation of the FoxCTS Server module.
Refer to “FoxCTS Change Database” on page 119 for details regarding the FoxCTS Change
Database installation and configuration.

FoxCTS Server Module


The FoxCTS Server is responsible for collecting information from stations on the control
network. Be sure to note the following information before proceeding with the installation of the
FoxCTS Server module.
♦ The Microsoft SQL Server software must be installed prior to the installation of the
FoxCTS Server module.
♦ Install and configure the Integrity software prior to the installation of FoxCTS. See
“Integrity Software” on page 120 for installation instructions.
♦ All configurator sessions must be closed during the installation process.
To start the FoxCTS Server module installation process on a workstation:
1. When applicable, verify that the PDC configuration changes on page 35 have been
made prior to installation the FoxCTS Server module.
2. Verify that the Microsoft SQL Server software has been installed.
3. Verify that the Integrity software has been installed, licensed, and configured per the
instructions found on page 120.
4. Install the FoxCTS Server module. When installing on workstations with security
enhancements, log in as a domain user that is a member of the “IA Installer” and
“Domain Admin” groups but do not use the “iainstaller” account.
5. Using the FoxCTS for Windows media, start the installation process by selecting the
E:\FoxCTS\Server\setup.exe file.
6. If a message box appears with a security warning, select Run.

39
B0193VV – Rev K 3. Installation

7. At the Welcome to the InstallShield Wizard for FoxCTS Server window select Next.
8. At the License Agreement accept the terms and select Next.
9. At the Ready to Install the Program window select Install.
10. If a message box appears to verify the installation, select Yes.
11. At the InstallShield Wizard Completed window select Finish.
12. If prompted do not reboot at this time. Reboot the PC after all of the required
FoxCTS modules have been installed.
a. For I/A Series Software v8.5-v8.7, reboot the PC by selecting Start, then Run,
enter the command foxshutdown 10 1 1 and select OK.
b. For Control Core Services v9.0 or I/A Series Software v8.8, select the Windows
Restart button.

FoxCTS OAJ Host Module


This section describes the FoxCTS OAJ Host module installation.

TIP
Only use the installation procedures found in this manual to install the FoxCTS
OAJ Host module.

Be sure to note the following information before proceeding with the installation of the FoxCTS
OAJ Host module.
♦ When applicable, verify that the PDC configuration changes on page 35 have been
made prior to installation the FoxCTS OAJ Host module.
♦ A FoxCTS Server must be installed before any other FoxCTS modules are installed.
♦ AIM*Historian must be installed, licensed, configured, and running with an instance
prior to the installation of the FoxCTS OAJ Host Module.
Please read the installation questions carefully and answer the questions per your installation
requirements.
1. The Control Core Services or I/A Series Software must be running during the instal-
lation of the FoxCTS OAJ Host Module.
2. Install the FoxCTS OAJ Host module. When installing on workstations with security
enhancements, log in as a domain user that is a member of the “IA Installer” and
“Domain Admin” groups but do not use the “iainstaller” account.
3. Using the FoxCTS for Windows media, start the installation process by selecting the
E:\FoxCTS\OAJ\setup.exe file.
4. If a message box appears with a security warning, select Run.
5. At the Welcome to the InstallShield Wizard for FoxCTS OAJ Host window select
Next.
6. At the License Agreement accept the terms and select Next.
7. At the FoxCTS OAJ Host Module Setup window, Figure 3-1, fill in the site specific
information and select Next.

40
3. Installation B0193VV – Rev K

Figure 3-1. FoxCTS OAJ Host Module Setup

8. At the Ready to Install the Program window select Install.


9. If a message box appears to verify the installation, select Yes.
10. At the InstallShield Wizard Completed window select Finish.
11. If prompted do not reboot at this time. Reboot the PC after all of the required
FoxCTS modules have been installed.
a. For I/A Series Software v8.5-v8.7, reboot the PC by selecting Start, then Run,
enter the command foxshutdown 10 1 1 and select OK.
b. For Control Core Services v9.0 or I/A Series Software v8.8, select the Windows
Restart button.

41
B0193VV – Rev K 3. Installation

FoxCTS Client Module


This section describes the FoxCTS Client module installation on workstations.

TIP
Only use the installation procedures found in this manual to install the FoxCTS
Client module.

Be sure to note the following information before proceeding with the installation of the FoxCTS
Client module.
♦ When applicable, verify that the PDC configuration changes on page 35 have been
made prior to installation the FoxCTS Client module.
♦ A FoxCTS Server must be installed before other FoxCTS modules are installed.
♦ If reinstalling the FoxCTS for Windows Client module be sure to check the
D:\usr\fox\wp\data\init.user file to make sure that all of the FoxCTS entries have
been removed. See “Reinstall FoxCTS” on page 102 for details.
Please read the installation questions carefully and answer the questions per your installation
requirements.
1. The Control Core Services or I/A Series Software must be running during the
installation of the FoxCTS Windows Client module.
2. Install the FoxCTS Client. When installing on workstations with security enhance-
ments, log in as a domain user that is a member of the “IA Installer” and “Domain
Admin” groups but do not use the “iainstaller” account.
3. Using the FoxCTS for Windows media, start the installation process by selecting the
E:\FoxCTS\Client\setup.exe file.
4. If a message box appears with a security warning, select Run.
5. At the Welcome to the InstallShield Wizard for FoxCTS Client window select Next.
6. At the License Agreement accept the terms and select Next.
7. At the FoxCTS Client Module Setup window, Figure 3-2, fill in the site specific
information and select Next.

NOTE
The IP Address entered here is for FoxCTS communications. Using a plant
information network for FoxCTS communications is strongly recommended.

42
3. Installation B0193VV – Rev K

Figure 3-2. FoxCTS Client Module Setup

8. If the OAJ enhanced messaging box has been checked the FoxCTS Client OAJ
Enhanced Messaging window, Figure 3-3, will appear. Fill in the site specific
information and select Next.

NOTE
(1) The IP Address entered here is for FoxCTS communications. Using a plant
information network for FoxCTS communications is strongly recommended.
(2) The OAJ Message Relay Name must be unique on the entire system.

43
B0193VV – Rev K 3. Installation

Figure 3-3. FoxCTS Client OAJ Enhanced Messaging Setup

9. At the Ready to Install the Program window select Install.


10. If a message box appears to verify the installation, select Yes.
11. At the InstallShield Wizard Completed window select Finish.
12. If prompted do not reboot at this time. Reboot the PC after all of the required
FoxCTS Windows modules have been installed.
a. For I/A Series Software v8.5-v8.7, reboot the PC by selecting Start, then Run,
enter the command foxshutdown 10 1 1 and select OK.
b. For Control Core Services v9.0 or I/A Series Software v8.8, select the Windows
Restart button.

44
3. Installation B0193VV – Rev K

FoxCTS SysMon Module


This section describes the FoxCTS SysMon module installation on workstations. Only use the
installation procedures found in this manual to install the FoxCTS SysMon module.

TIP
The FoxCTS SysMon module must be installed on the System Monitor host for
every system monitor that is used for monitoring ICC-controlled control stations in
the FoxCTS domain.

Be sure to note the following information before proceeding with the installation of the FoxCTS
SysMon module.
♦ When applicable, verify that the PDC configuration changes on page 35 have been
made prior to installation the FoxCTS SysMon module.
♦ A FoxCTS Server must be installed before other FoxCTS modules are installed.
Please read the installation questions carefully and answer the questions per your installation
requirements.
1. The Control Core Services or I/A Series Software must be running during the instal-
lation of the FoxCTS SysMon module.
2. Install the FoxCTS SysMon module. When installing on workstations with security
enhancements, log in as a domain user that is a member of the “IA Installer” and
“Domain Admin” groups but do not use the “iainstaller” account.
3. Using the FoxCTS for Windows media, start the installation process by selecting the
E:\FoxCTS\SysMon\setup.exe file.
4. If a message box appears with a security warning, select Run.
5. At the Welcome to the InstallShield Wizard for FoxCTS SysMon window select
Next.
6. At the License Agreement accept the terms and select Next.
7. At the FoxCTS SysMon Module Setup window, Figure 3-4, fill in the site specific
information and select Next.

NOTE
The SMMR Name must be unique on the entire system.

45
B0193VV – Rev K 3. Installation

Figure 3-4. FoxCTS SysMon Module Setup

8. At the Ready to Install the Program window select Install.


9. If a message box appears to verify the installation, select Yes.
10. At the InstallShield Wizard Completed window select Finish.
11. If prompted do not reboot at this time. Reboot the PC after all of the required
FoxCTS modules have been installed.
a. For I/A Series Software v8.5-v8.7, reboot the PC by selecting Start, then Run,
enter the command foxshutdown 10 1 1 and select OK.
b. For Control Core Services v9.0 or I/A Series Software v8.8, select the Windows
Restart button.

46
3. Installation B0193VV – Rev K

FoxCTS ICC Driver Module


This section describes a FoxCTS ICC Driver module installation on workstations. Only use the
installation procedures found in this manual to install the FoxCTS ICC Driver module.

TIP
The FoxCTS ICC Driver module must be installed on the control station boot host
for every ICC controlled control station in the FoxCTS domain.

Be sure to note the following information before proceeding with the installation of the FoxCTS
ICC Driver module.
♦ When applicable, verify that the PDC configuration changes on page 35 have been
made prior to installation the FoxCTS ICC Driver module.
♦ A FoxCTS Server must be installed before other FoxCTS modules are installed.
Please read the installation questions carefully and answer the questions per your installation
requirements.
1. The Control Core Services or I/A Series Software must be running during the instal-
lation of the FoxCTS ICC Driver module.
2. Install the FoxCTS ICC Driver module. When installing on workstations with secu-
rity enhancements, log in as a domain user that is a member of the “IA Installer” and
“Domain Admin” groups but do not use the “iainstaller” account.
3. Using the FoxCTS for Windows media, start the installation process by selecting the
E:\FoxCTS\IccDriver\setup.exe file.
4. If a message box appears with a security warning, select Run.
5. At the Welcome to the InstallShield Wizard for FoxCTS_ICC Driver window select
Next.
6. At the License Agreement accept the terms and select Next.
7. At the FoxCTS ICC Driver Module Setup window, Figure 3-5, fill in the site specific
information and select Next.

NOTE
The IP Address entered here is for FoxCTS communications. Using a plant
information network for FoxCTS communications is strongly recommended.

47
B0193VV – Rev K 3. Installation

Figure 3-5. FoxCTS ICC Driver Module Setup

8. At the Ready to Install the Program window select Install.


9. If a message box appears to verify the installation, select Yes.
10. At the InstallShield Wizard Completed window select Finish.
11. If prompted do not reboot at this time. Reboot the PC after all of the required
FoxCTS modules have been installed.
a. For I/A Series Software v8.5-v8.7, reboot the PC by selecting Start, then Run,
enter the command foxshutdown 10 1 1 and select OK.
b. For Control Core Services v9.0 or I/A Series Software v8.8, select the Windows
Restart button.

48
3. Installation B0193VV – Rev K

FoxCTS PACTware Module


This section describes a FoxCTS PACTware module installation on workstations. Only use the
installation procedures found in this manual to install the FoxCTS PACTware module.

TIP
The FoxCTS PACTware module must be installed on workstations where
PACTware software is installed and change data is to be collected.

Be sure to note the following information before proceeding with the installation of the FoxCTS
PACTware module.
♦ When applicable, verify that the PDC configuration changes on page 35 have been
made prior to installation the FoxCTS PACTware module.
♦ A FoxCTS Server must be installed before other FoxCTS modules are installed.
♦ Multiple versions of PACTware on the same station is not supported.
Please read the installation questions carefully and answer the questions per your installation
requirements.
1. The Control Core Services or I/A Series Software must be running during the instal-
lation of the FoxCTS PACTware module.
2. The PACTware software must be installed.
3. Install the FoxCTS PACTware module.When installing on workstations with security
enhancements, log in as a domain user that is a member of the “IA Installer” and
“Domain Admin” groups but do not use the “iainstaller” account.
4. Using the FoxCTS for Windows media, start the installation process by selecting the
E:\FoxCTS\PW\setup.exe file.
5. If a message box appears to verify the installation, select Yes.
6. At the Welcome to the InstallShield Wizard for FoxCTS PW window select Next.
7. At the License Agreement accept the terms and select Next.
8. At the Ready to Install the Program window select Install.
9. If a message box appears to verify the installation, select Yes.
10. At the InstallShield Wizard Completed window select Finish.

Reboot Workstations
Do not forget to reboot the workstations after all of the required FoxCTS modules have been
installed by using one of the following shutdown commands.
♦ For I/A Series Software v8.5-v8.7, reboot the PC by selecting Start, Run, then enter
the Foxboro shutdown command foxshutdown 10 1 1 and then select OK.
♦ For Control Core Services v9.0 or I/A Series Software v8.8, select the Windows
Restart button.

49
B0193VV – Rev K 3. Installation

FoxCTS Services
This section pertains to the FoxCTS Services that are created when the FoxCTS modules are
installed. The Services list will only show those FoxCTS Services that have been created during
the FoxCTS module installation.
After the PC has been rebooted verify that all of the FoxCTS Services started.
1. From the Services window, Figure 3-7, look for the FoxCTS labeled Services. This list
will only contain the FoxCTS Services created for the FoxCTS modules.
2. If a FoxCTS Services did not start, highlight the FoxCTS Service that is not running
and start the service.

Control Core Services v9.0 or I/A Series Software v8.8


For workstations running Control Core Services v9.0 or I/A Series Software v8.8, the FoxCTS
Services setting for the Startup Type is set to Automatic.

Figure 3-6. FoxCTS Services

50
3. Installation B0193VV – Rev K

I/A Series Software v8.5-v8.7


For workstations running I/A Series Software v8.5-v8.7, the FoxCTS Services setting for the
Startup Type is set to Manual. All FoxCTS Services are started on reboot by the fox_apps.dat
mechanism. This ensures that the I/A Series applications are running before the FoxCTS Services
start.

TIP
If a FoxCTS Service does not start after a reboot, it might be necessary to modify
the StartDelay parameter for that service. For additional information regarding
modifying the StartDelay parameter see “Not Starting on Reboot (I/A Series Soft-
ware v8.5-v8.7)” on page 107.

Figure 3-7. FoxCTS Services

51
B0193VV – Rev K 3. Installation

52
4. FoxCTS Domain Configuration
This chapter describes the FoxCTS domain configuration that must be performed after the
installation of the FoxCTS Server module.
The FoxCTS package is a complex product and its configuration requires an understanding of the
system and the use of standard workstation tools. A FoxCTS domain is comprised of control
processors, workstations, and process areas. Only a FoxCTS user with appropriate configurator
rights can assign process areas, control stations, workstations, file tracking clients and files to be
tracked.

NOTE
A FoxCTS domain is totally unrelated to the Microsoft domain used for security-
enhanced workstations.

Be sure to complete the FoxCTS Configuration worksheets from Appendix A “Worksheets”


before performing the FoxCTS domain configuration.

FoxCTS Configurator
Use the FoxCTS Configurator to setup and maintain the FoxCTS domain and FoxCTS user
accounts.
Once the FoxCTS Server has been installed:
1. For initial access to the FoxCTS Configurator:
a. For workstations with security enhancements, log in to the workstation as the
Microsoft domain user that installed the FoxCTS Server module. This default
administrator account has permission to configure the FoxCTS domain. The
FoxCTS FoxView login will occur automatically by default.
b. For standard workstations, log in to FoxView as the default FoxCTS user, Admin,
with the password gnomes. You will be prompted to change the password to this
account during the first use. This default administrator account has permission to
configure the FoxCTS domain.
2. Start the FoxCTS Configurator by selecting one of the following startup methods. In
either case, only a FoxCTS user with the appropriate FoxCTS Configurator access
rights can use the FoxCTS Configurator.
♦ Select the FoxCTS > Admin items from the FoxView menu bar. Using this
method, the FoxCTS Configurator can only be launched from the FoxCTS
Server’s primary display manager.
♦ For workstations with security enhancements the FoxCTS Configurator can also
be started by selecting Start > All Programs > FoxCTS > FoxCTS Config-
urator.
Figure 4-1 represents the main menu of the FoxCTS Configurator.

53
B0193VV – Rev K 4. FoxCTS Domain Configuration

Figure 4-1. FoxCTS Configurator - Main Menu

The FoxCTS Configurator includes the following menu items:


♦ FoxCTS
♦ Exit - Closes the FoxCTS Configurator and the FoxCTS domain database.
♦ Database
♦ Backup - Saves the FoxCTS Domain Database to a local file,
d:\opt\foxind\cms\srvr\domainBkups\FOXCTS_<date>_<time>.bak. A good
disasters recovery plan would include preserving a copy of this file to an external
storage device.
♦ Restore - Restores a previously saved FoxCTS Domain Database. This restore
process will completely destroy the existing database.
♦ Domain Configuration
♦ Process Areas - Manage the FoxCTS Process Areas in the FoxCTS Domain. At
least one Process Area name should be created for the FoxCTS Domain. If no
Process Area is assigned the default name, Unassigned, will be used.
♦ Control Stations - Manage FoxCTS Control Stations in the FoxCTS Domain. A
control station is any station with control blocks. The default control station list is
built from the FoxCTS Server’s cplns file.
♦ Workstations - Manage the FoxCTS stations in the FoxCTS Domain. Identify
any workstation that has the FoxCTS Client module installed. The default list is
built from the FoxCTS Server’s dmcfg file.
♦ File Tracking
♦ Client Stations - Manage File Tracking Clients in the FoxCTS Domain. A file
tracking client is any workstation that has the FoxCTS Client module installed
and configured to track files. The default list of file tracking clients is built from
the FoxCTS Server’s hldb file.

54
4. FoxCTS Domain Configuration B0193VV – Rev K


Files - Manage files for file tracking.
♦ User Configuration
♦ Environments - Manage the FoxView environment files available for use by the
FoxCTS user accounts. Only those environments listed here will be available for
use in the FoxCTS Domain. The default list of environments is built from the
FoxCTS Server’s standard FoxView environment directories.
♦ Groups - Manage the FoxCTS Groups for the FoxCTS Domain. A FoxCTS
Group is a collection of FoxView environments. The FoxCTS Groups are then
assigned to FoxCTS User Types.
♦ User Types - Manage the FoxCTS User Types for the FoxCTS Domain. The
FoxCTS user’s default home environment and environment group(s) are
controlled by the FoxCTS User Type. These User Types will then be assigned to
FoxCTS user accounts.
♦ User Accounts - Manage the FoxCTS user accounts for the FoxCTS Domain.
♦ Password Control - Manage password security for the FoxCTS user accounts.
Allows the customization of security rules that govern FoxCTS user passwords.
This menu item is only active for standard workstation installations.
The common buttons used by the FoxCTS Configurator are:
♦ Add - Adds the new item to the FoxCTS domain database.
♦ Update - Updates the selected item to the FoxCTS domain database.
♦ Delete - Deletes the item from the FoxCTS domain database. Deletes are only
possible if data has not been recorded to the FoxCTS change database.
♦ Print - Displays the current list of items to a report using a text editor.
♦ Clear - Clears the currently selected information displayed in the dialog box.
♦ Exit - Close the current dialog box.

TIP
Sort the various FoxCTS Configurator lists by selecting the column heading. Lists
are sorted in ascending or descending order.

55
B0193VV – Rev K 4. FoxCTS Domain Configuration

FoxCTS Domain Database Maintenance


This section pertains to the maintenance of the FoxCTS domain database. The FoxCTS
Configurator domain database maintenance, Figure 4-2, consists of two parts:
♦ Backup - Make a backup of the current FoxCTS domain database. It is a good
practice to copy this file to an external storage device for an additional backup.
♦ Restore - Restores a previous backup of the FoxCTS domain database. Restoring the
FoxCTS domain database will destroy the current domain database.

Figure 4-2. FoxCTS Configurator - Database Menu

56
4. FoxCTS Domain Configuration B0193VV – Rev K

Backup
The FoxCTS Configurator saves the FoxCTS domain database to the file,
d:\opt\foxind\cms\srvr\domainBkups\FOXCTS_<date>_<time>.bak. It is a good idea to copy
this file to an external storage device.
Figure 4-3 represents the Domain Database Backup dialog box of the FoxCTS Configurator.

Figure 4-3. FoxCTS Configurator - Domain Database Backup

Take the following steps to save the FoxCTS domain database.


1. Start the FoxCTS Configurator from the FoxView menu bar.
2. Select the Database menu item and then select the Backup pull-down menu item.
a. Select the Save button to save the existing FoxCTS domain database. The
database will be saved to the d:\opt\foxind\cms\srvr\domainBkups folder.
b. A message box will display when the database has been successfully saved.
c. Select Exit to close the dialog box.

57
B0193VV – Rev K 4. FoxCTS Domain Configuration

Restore
The FoxCTS domain database can be restored from any location.

! CAUTION
Restoring the FoxCTS domain database will destroy the existing FoxCTS domain
database.

Figure 4-4 represents the Domain Database Restore dialog box of the FoxCTS Configurator.

Figure 4-4. FoxCTS Configurator - Domain Database Restore

Take the following steps to restore the FoxCTS domain database.


1. Login in as a FoxCTS user with database access level and start the FoxCTS
Configurator from the FoxView menu bar.
2. Select the Database menu item and then select the Restore pull-down menu item.
a. Select the Browse button to locate the FoxCTS domain database backup file. The
default save folder is d:\opt\foxind\cms\srvr\domainBkups.
b. Select the desired database backup file and then select the OK button.
c. Select the Restore button to restore the selected backup file. (The restore process
will destroy the existing FoxCTS domain database.)
d. Select Exit to close the dialog box.

58
4. FoxCTS Domain Configuration B0193VV – Rev K

FoxCTS Domain Configuration


This section pertains to the configuration of the FoxCTS Domain. The FoxCTS Configurator
Domain Configuration, Figure 4-5, consists of three parts:
♦ Process Areas
♦ Control Stations
♦ Workstations

Figure 4-5. FoxCTS Configurator - Domain Configuration Menu

Process Areas
A FoxCTS Process Area is a logical grouping of equipment in a FoxCTS domain. A FoxCTS
domain consists of control stations, workstations, file servers, and operator consoles. The FoxCTS
product supports subdivisions of the FoxCTS domain into groupings of equipment that make
sense for the specific site. These subdivisions are called Process Areas.
The data fields displayed on the Process Area dialog box are:
♦ Process Area Name - This is the name given to identify a FoxCTS Process Area. At
least one FoxCTS process area should be configured. If no process area is configured,
then the default process area name, Unassigned, will be used. The process area name
could reference a particular area of a plant. The following are Process Area Name
restrictions:
♦ cannot exceed 12 characters in length.
♦ illegal characters for use in a process area are: + = / [ ] “ ‘ : ; , ? * \
< > | { } ‘
♦ do not create more than 50 process area names

59
B0193VV – Rev K 4. FoxCTS Domain Configuration

♦ Process Area Description - Enter a brief description of the Process Area. The
following are Process Area Description restrictions:
♦ cannot exceed 41 characters in length
♦ illegal characters for use in a description are: + = / [ ] “ ‘ : ; , ? * \
< > | { } ‘
Figure 4-6 represents the Process Area dialog box of the FoxCTS Configurator.

Figure 4-6. FoxCTS Configurator - Process Area

Take the following steps to create or modify the Process Areas in a FoxCTS domain.
1. Start the FoxCTS Configurator from the FoxView menu bar.
2. Select the Domain Configuration menu item and then select the Process Areas
pull-down menu item.
3. Enter a new Process Area Name or select an existing Process Area name from the list.
There should be at least one Process Area assigned to a FoxCTS domain. When no
Process Area is created then the default name, Unassigned, is used.
♦ Select the Add button to add a process area to the FoxCTS domain database.
♦ Select the Update button to save changes made to the selected process area.
♦ Select the Delete button to delete the selected process area from the FoxCTS
domain database. Note: It is not possible to delete the process areas ALL and
Unassigned from the domain database. It is not possible to delete process areas
that are used in other parts of the FoxCTS Domain configuration.
♦ Select the Print button to display the Process Area information in a text editor.
♦ Select the Clear button to clear the dialog box without saving.
♦ Select Exit to close the dialog box.

60
4. FoxCTS Domain Configuration B0193VV – Rev K

Control Stations
A control station is any station with control blocks. The set of control stations includes, but is not
limited to, CP10s/20s/30s/40s/60s/270s/280s, FDGs, DIs, and Application Integrators.
After the FoxCTS domain has been configured, all FoxCTS control stations should have a
baseline established. See “Control Stations Baseline” on page 14 for details on creating a baseline.

TIP
(1) Create the Process Areas before editing the Control Stations.
(2) Edit the Control Stations before editing the workstations.
(3) Delete any Control Stations from this list that no longer exist.

The data fields displayed on the Control Stations dialog box are:
♦ Control Station Name - The letterbug name of the control station to be tracked by
the FoxCTS package. The default control station list is created from the FoxCTS
Server’s D:\usr\fox\sp\cplns file.
♦ CS Subtype - The control station subtype name is maintained by the FoxCTS
software and is not configurable by the FoxCTS Configurator. The default CS
Subtype is CS.
♦ Process Area Name - The Process Area name assigned to this control station.
Figure 4-7 represents the Control Stations dialog box of the FoxCTS Configurator. In this
example the selected Control Station’s Process Area Name is being assigned.

Figure 4-7. FoxCTS Configurator - Control Stations

61
B0193VV – Rev K 4. FoxCTS Domain Configuration

Take the following steps to create or modify the Control Stations in a FoxCTS domain.
1. Start the FoxCTS Configurator from the FoxView menu bar.
2. Select the Domain Configuration menu item and then select the
Control Stations pull-down menu item.
3. Enter a new Control Station or select an existing Control Station name from the list.
♦ Select the Add button to add a control station to the FoxCTS domain database.
♦ Select the Update button to save changes made to the selected control station.
♦ Select the Delete button to delete the selected control station from the FoxCTS
domain database.
♦ Select the Print button to display the Control Station information in a text
editor.
♦ Select the Clear button to clear the dialog box without saving.
♦ Select Exit to close the dialog box.

Workstations
A FoxCTS Client station is a workstation that has the FoxCTS Client module installed and
configured. A FoxCTS Server is always a FoxCTS Client. In order to track configuration and user
login/logout sessions, each FoxCTS Client station must be identified.

TIP
(1) Create the Process Areas before editing the workstations.
(2) Edit the Control Stations before editing the workstations.
(3) Delete any workstations from this list that no longer exist.

The data fields displayed on the workstations dialog box are:


♦ Name - The letterbug name of the workstations to be tracked by the
FoxCTS product. The default workstation list is created from the FoxCTS
Server’s D:\usr\fox\customer\hi\dmcfg file.
♦ WS Operating System - The workstations operating system.
♦ Process Area Name - The Process Area name assigned to this workstation.
Figure 4-8 represents the workstations dialog box of the FoxCTS Configurator. In this example
the selected workstation’s Process Area Name is being assigned.

62
4. FoxCTS Domain Configuration B0193VV – Rev K

Figure 4-8. FoxCTS Configurator -

Take the following steps to create or modify the workstations in a FoxCTS domain.
1. Start the FoxCTS Configurator from the FoxView menu bar.
2. Select the Domain Configuration menu item and then select the Workstations
pull-down menu item.
3. Enter a new workstation or select an existing workstation name from the list.
♦ Select the Add button to add a workstation to the FoxCTS domain database.
♦ Select the Update button to save changes made to the selected workstation.
♦ Select the Delete button to delete the selected workstation from the FoxCTS
domain database. It is not possible to delete the workstations ALL and
UNKNWN from the database. It is not possible to delete the workstations that
are used in other parts of the FoxCTS Domain configuration.
♦ Select the Print button to display the workstation information in a text editor.
♦ Select the Clear button to clear the dialog box without saving.
♦ Select Exit to close the dialog box.

63
B0193VV – Rev K 4. FoxCTS Domain Configuration

FoxCTS File Tracking


This section pertains to the configuration of file tracking. The FoxCTS Configurator file tracking
configuration, Figure 4-9, consists of two parts:
♦ File Tracking Clients
♦ Files to Track

Figure 4-9. FoxCTS Configurator - File Tracking Menu

File Tracking Clients


A file tracking client is any workstation that has the FoxCTS Client module installed and
configured with files to be tracked.

TIP
(1) When activating file tracking, it is a good practice to use the plant information
network whenever possible. This will keep file tracking traffic off the control
network.
(2) Create the Process Areas before editing the File Tracking Client stations.

The data fields displayed on the File Tracking Client dialog box are:
♦ FT Client Letterbug Name - The letterbug name of the workstation to be tracked by
the FoxCTS package. The default list of potential file tracking client workstations is
created from the FoxCTS Server’s D:\usr\fox\sp\hldb file.
♦ FT Client Operating System - The FT Client’s operating system.
♦ FT Client IP Name or IP Address - The letterbug name, plant information network
name, or IP Address. If using a plant information network name, then this name
must be listed in the FoxCTS Server’s C:\windows\system32\drivers\etc\hosts file.
♦ Process Area Name - The Process Area name assigned to this workstation.

64
4. FoxCTS Domain Configuration B0193VV – Rev K

Figure 4-10 represents the File Tracking Client Stations dialog box of the FoxCTS Configurator.
In this example the selected workstation’s IP Address and Process Area Name are being assigned.

Figure 4-10. FoxCTS Configurator - File Tracking Clients

Take the following steps to create or modify the File Tracking Clients in a FoxCTS domain.
1. Start the FoxCTS Configurator from the FoxView menu bar.
2. Select File Tracking and then select the Client Stations pull-down menu item.
3. Enter a new File Tracking Client or select an existing File Tracking Client name from
the list.
♦ Select the Add button to add a File Tracking Client to the FoxCTS domain
database.
♦ Select the Update button to save changes made to the selected File Tracking
Client.
♦ Select the Delete button to delete the selected File Tracking Client from the
FoxCTS domain database.
♦ Select the Print button to display the File Tracking Client information in a text
editor.
♦ Select the Clear button to clear the dialog box without saving.
♦ Select Exit to close the dialog box.

65
B0193VV – Rev K 4. FoxCTS Domain Configuration

Files to Track
Manages the FoxCTS File Tracking Client’s file(s)/directory(s) that will be tracked.
Keep the following in mind when file tracking:
♦ FoxCTS file tracking clients only are able to track files and folders on their local
hard drives.
♦ Extreme caution should be used when monitoring directories because when
tracking a directory FoxCTS change database entries are automatically created for
each file and sub-directory underneath the specified directory.
♦ If file tracking a directory that contains many subdirectories and files, start file
tracking at the lowest level directories in the directory tree and add the higher level
directory names, until all subdirectories and files are being tracked.
♦ The use of wild cards in the file names is not supported.
The data fields that displayed on the Files to Track dialog box are:
♦ FT Client Letterbug Name - The letterbug name of the workstation to be tracked by
the FoxCTS product. Select from the list of available workstations or enter the FT
Client workstation name.
♦ Path - Enter the complete directory path to the file or directory to be tracked. This
field cannot be left blank. Be sure to include the drive letter when entering the path.
♦ File/Folder Name - Enter the file or folder name that is to be tracked. This field
cannot be left blank
♦ Poll Period (Seconds) - This is the period of time, in seconds, between checking for
file changes. Select from the default list of poll periods or enter a poll period.
♦ Monitor Status - Identify if the file/folder is to be monitored. This option controls
whether or not the file or folder is actually being tracked. The list of configured files
and folders to be tracked will display a status of M (monitored) or U (unmonitored).
Figure 4-11 represents the Files and Folders to Track dialog box of the FoxCTS Configurator. In
this example the env directory on 3AW70D is being setup for file tracking.

66
4. FoxCTS Domain Configuration B0193VV – Rev K

Figure 4-11. FoxCTS Configurator - Files and Folders to Track

Take the following steps to create or modify the files to track in a FoxCTS domain.
1. Start the FoxCTS Configurator from the FoxView menu bar.
2. Select the File Tracking menu item and then select the Files pull-down menu
item.
3. Enter new file tracking information or select an existing file tracking entry from the
list.
♦ Select the Add button to add file tracking items to the FoxCTS domain database.
♦ Select the Update button to save changes made to the selected file tracking entry.
♦ Select the Delete button to delete the selected file tracking entry from the
FoxCTS domain database.
♦ Once the files and folders for tracking have been identified. Select the Build
button to initiate file tracking. The Build button will launch the Generate/
Activate File Tracking List(s) dialog box, Figure 4-12.
♦ From the Generate/Activate File Tracking List(s) dialog box highlight the File
Tracking Client stations to be updated or activated.
♦ Then select the Activate button. This button causes the FoxCTS Server to
generate the list of files and folders to be tracked by each file tracking client
station. This list is then sent to their respective file tracking client stations for
file monitoring.
♦ A message box will appear when the lists are successfully built.

67
B0193VV – Rev K 4. FoxCTS Domain Configuration

♦ Select the Print button to display the file tracking information in a text editor.
♦ Select the Clear button to clear the dialog box without saving.
♦ Select Exit to close the dialog box.

Figure 4-12. FoxCTS Configurator - Files to Track

68
4. FoxCTS Domain Configuration B0193VV – Rev K

FoxCTS User Configuration


This section pertains to the configuration of FoxCTS user accounts. The FoxCTS Configurator
User Configuration, Figure 4-13, consists of five parts:
♦ Environments
♦ Groups
♦ User Types
♦ User Accounts
♦ Password Control (This menu item is only active on standard installations of the
Control software.)

Figure 4-13. FoxCTS Configurator - User Configuration Menu

Environments
The FoxView environments that will be available to FoxCTS user accounts must be assigned.
These environments must be specified before FoxCTS environment groups are assigned.

TIP
When configuring environments for FoxCTS users, it is important to make sure
that these environments actually exist on every FoxCTS Client station.

The data fields displayed on the Environment dialog box are:


♦ Environment Name - The FoxView environment name to be used in the FoxCTS
domain. The default list of FoxView environments is created from the FoxCTS
Server’s D:\opt\foxind\cms\clnt\env directory. The following are Environment name
restrictions:
♦ names must conform to FoxView standards

69
B0193VV – Rev K 4. FoxCTS Domain Configuration

♦ cannot exceed 40 characters in length


♦ illegal characters for use in an environment name are: + = / [ ] “ ‘ : ; ,
? * \ < > | { } ‘ and a space
♦ do not create more than 50 environment names
Figure 4-14 represents the Environments dialog box of the FoxCTS Configurator. In this example
a new environment is being added.

Figure 4-14. FoxCTS Configurator - Environments

Take the following steps to create or modify the FoxView environment in a FoxCTS domain.
1. Start the FoxCTS Configurator from the FoxView menu bar.
2. Select the User Configuration menu item and then select the Environments pull-
down menu item.
3. Enter a new FoxView environment name or select an existing environment name
from the list.
♦ Select the Add button to an environment to the FoxCTS domain database.
♦ Select the Update button to save changes made to the selected environment.
♦ Select the Delete button to delete the selected environment from the FoxCTS
domain database.
♦ Select the Print button to display the environment information in a text editor.
♦ Select the Clear button to clear the dialog box without saving.
♦ Select Exit to close the dialog box.

70
4. FoxCTS Domain Configuration B0193VV – Rev K

Groups
A FoxCTS Group is a collection of FoxView environments. FoxCTS user accounts access to
environments is restricted through the use of FoxCTS Groups. Each group contains a set of
allowed environments for a named group. These group names are then associated with FoxCTS
user accounts through the use of FoxCTS User Types.

NOTE
(1) When creating FoxView environment groups, the FoxView environment’s .env
extension is dropped.
(2) The FoxCTS Groups must be created before FoxCTS User Types are assigned.
(3) FoxCTS Groups and User Types assignments will not override domain environ-
ment security policies.

The data fields displayed on the Group dialog box are:


♦ Group Name - The FoxCTS Group name assigned to a collection of FoxView
environments. The FoxCTS default Group, FV_ADMIN, cannot be deleted. The
default groups PWADMIN, PWPLANENGR, PWMAINT, PWOPERATOR and
PWOBSERVER are created for use with the FoxCTS PACTware module, see page 85
for details.

The following are Group name restrictions:


♦ names cannot exceed 20 characters
♦ illegal characters for use in a group name are: + = / [ ] “ ‘ : ; , ? * \
< > | { } ‘ and a space
♦ do not create more than 50 group names
♦ Assigned Environments - The list of FoxView environments currently assigned to the
group.
♦ Available Environments - The list of the remaining FoxView environments that can
be assigned to the group. This list originally will include all FoxView environments
assigned in the FoxCTS Configurator.
Figure 4-15 represents the Groups dialog box of the FoxCTS Configurator.

71
B0193VV – Rev K 4. FoxCTS Domain Configuration

Figure 4-15. FoxCTS Configurator - Groups

Take the following steps to create or modify the FoxCTS Groups in a FoxCTS domain.
1. Start the FoxCTS Configurator from the FoxView menu bar.
2. Select the User Configuration menu item and then select the Environments pull-
down menu item.
3. Enter a new Group name or select an existing Group name from the list.
♦ Select the Add button to add a Group to the FoxCTS domain database.
♦ Select the Update button to save changes made to the selected Group.
♦ Select the Delete button to delete the selected Group from the FoxCTS domain
database.
♦ Select the Print button to display the group information in a text editor.
♦ Select the Clear button to clear the dialog box without saving.
♦ Select Exit to close the dialog box.

72
4. FoxCTS Domain Configuration B0193VV – Rev K

User Types
FoxCTS User Type is responsible for assigning a default home environment and available
environment group(s). The FoxCTS User Type is assigned to each FoxCTS user account to
control access to the FoxCTS environments.

NOTE
(1) The FoxCTS Groups and User Types must be assigned before FoxCTS user
accounts are created.
(2) FoxCTS Groups and User Types assignments will not override domain environ-
ment security policies.

The data fields displayed on the FoxCTS User Type dialog box are:
♦ User Type Name - The FoxCTS User Type name assigned to this collection. The
FoxCTS default User Type, Admin, cannot be deleted. The following are User Type
name restrictions:
♦ cannot exceed 20 characters in length
♦ illegal characters for use in an user type name are: + = / [ ] “ ‘ : ; , ? *
\ < > | { } ‘ and a space
♦ do not create more than 50 user type names
♦ FoxView Home Environment - The default home FoxView environment assigned to
this user type. The available home environment list is based on the selected Assigned
Environment Group(s).
♦ Assigned Environment Group(s) - The list of FoxCTS Groups currently assigned to
the selected User Type.
♦ Available Environment Group(s) - The list of the remaining Groups that can be
assigned to the User Type.
Figure 4-16 represents the User Type dialog box of the FoxCTS Configurator. In this example a
new User Type is being added.

73
B0193VV – Rev K 4. FoxCTS Domain Configuration

Figure 4-16. FoxCTS Configurator - User Types

Take the following steps to create or modify the FoxCTS User Types in a FoxCTS domain.
1. Start the FoxCTS Configurator from the FoxView menu bar.
2. Select the User Configuration menu item and then select the User Types pull-
down menu item.
3. Enter a new User Type name or select an existing User Type name from the list.
♦ Assign the required group(s).
♦ Select the home environment. The environment list is generated from the groups
that have been assigned.
♦ Select the Add button to add a user type to the FoxCTS domain database.
♦ Select the Update button to save changes made to the selected user type.
♦ Select the Delete button to delete the selected user type from the FoxCTS
domain database.
♦ Select the Print button to display the user type information in a text editor.
♦ Select the Clear button to clear the dialog box without saving.
♦ Select Exit to close the dialog box.

74
4. FoxCTS Domain Configuration B0193VV – Rev K

Password Controls
This menu item is only available for standard workstation, since security enhanced installations
security and passwords are managed by the domain.
The FoxCTS administrator can customize security rules that govern FoxCTS user passwords.
These rules control password length, password aging, password reuse, and number of retries
before the FoxCTS user is locked out.

NOTE
The FoxCTS Password Controls should be assigned before FoxCTS user accounts
are created.

The data fields displayed on the Password Controls dialog box are:
♦ Minimum Password Length - This field specifies the number of characters that the
passwords contain. The default minimum password length is 4 characters. The
maximum length of a password is 14 characters.
♦ Minimum Numeric Characters - This field specifies the minimum number of
numeric characters, if any, required in a password. The sum of minimum numeric
and alphabetic characters cannot exceed the minimum password length specified.
♦ Minimum Alphabetic Characters - This field specifies the minimum number of
alphabetic characters, if any, required in a password.The sum of the minimum
numeric and alphabetic characters cannot exceed the minimum password length
specified.
♦ Minimum Uppercase Characters - This field specifies the minimum number
of uppercase characters, if any, required in a password.The sum of uppercase
characters and lowercase characters entered cannot exceed the minimum
alphabetic characters specified.
♦ Minimum Lowercase Characters - This field specifies the minimum number
of lowercase characters, if any, required in a password.The sum of uppercase
and lowercase characters entered cannot exceed the minimum alphabetic
characters specified.
♦ Maximum Password Age in Days - This field controls password aging and sets the
maximum number of days between controlled password changes.
♦ Minimum Days to Password Reuse - This field controls the minimum number of
days that must pass before an old password can be reused. This field is used in
conjunction with the Minimum Password to Reuse field.
♦ Minimum Password to Reuse - This field controls the minimum number of
passwords that must be used before an old password can be reused. This field is used
in conjunction with the Minimum Days to Password Reuse field.
♦ Number of Failures before Lockout - This field controls the maximum number of
consecutive invalid passwords that can be provided either during login, password
change, or user confirmation before the user’s account is temporarily disabled. Once
an account has been disabled only the FoxCTS administrator can reactivate the
account. Note: The failure counter is only reset after the successful login.

75
B0193VV – Rev K 4. FoxCTS Domain Configuration

Figure 4-17 represents the Password Control dialog box of the FoxCTS Configurator. In this
example the Password Controls are being changed from the default settings.

Figure 4-17. FoxCTS Configurator - Password Control

Take the following steps to modify password security settings in a FoxCTS domain.
1. Start the FoxCTS Configurator from the FoxView menu bar.
2. Select the User Configuration menu and then select the Password Controls
pull-down menu item.
3. Modify the password security settings.
a. Select the Update button to save the changes made to the password control
settings.
b. Select the Print button to display the password control setting in a text editor.
c. Select the Default button to restore the password control setting to the FoxCTS
default settings.
Select Exit to close the dialog box.

76
4. FoxCTS Domain Configuration B0193VV – Rev K

User Accounts
FoxCTS User Accounts are responsible for controlling access to FoxView environments at a
workstation and provide a way to track user interactions.
Before FoxCTS user accounts are created the following steps must be performed.
♦ FoxView environments to be used by FoxCTS users identified.
♦ FoxCTS environment Groups created.
♦ FoxCTS User Types created and environment Groups assigned.
♦ FoxCTS workstations identified.
♦ FoxCTS user account information must be identified, i.e., first name, last name,
employee ID, user login name, user type, process area access, workstation access, and
FoxCTS Configurator access rights.
The data fields displayed on the User Accounts dialog box are:
♦ Last Name - FoxCTS user’s last name. A user last name cannot exceed 32
characters. (The users last name can always be changed in the FoxCTS Configurator.)
♦ First Name, M.I. - FoxCTS user’s first name and optional middle initial. A user
first name cannot exceed 32 characters. (The users first name can always be changed
in the FoxCTS Configurator.)
♦ Employee ID - The assigned employee ID. Employee IDs cannot exceed 32
characters. (The employee ID can always be changed in the FoxCTS Configurator.)
♦ Login Name - The unique user login name for each FoxCTS user account. If the
FoxCTS domain includes security-enhanced workstations, be sure that the
FoxCTS Login Name matches the Microsoft domain login name. The following
are FoxCTS Login Name restrictions:
♦ Once a login name has been created it cannot be changed.
♦ cannot exceed 30 characters
♦ are not case sensitive
♦ illegal characters for use in a login name are: + = / [ ] “ ‘ : ; , ? * \
< > | { } ‘ and a space
♦ Password - Set a password for the FoxCTS account.
♦ For security enhanced workstations, the password field is disabled and the
account status is set to ACTIVE.
♦ For standard workstation, an initial password is created and the account status
is set to PASSWORD EXPIRED to force the user to change their password
on their first login attempt. The FoxCTS user will have to know their initial
password in order to change passwords.
In the case where FoxCTS controls the user accounts and passwords, the following
are password restrictions:
♦ cannot exceed 14 characters
♦ illegal characters for use in password are: + = / [ ] “ ‘ : ; , ? * \
< > | { } ‘ and a space

77
B0193VV – Rev K 4. FoxCTS Domain Configuration

♦ Account Status - Assigns the user account status. This field is disabled and the
account status set to ACTIVE for security enhanced workstations.
The valid options for account status are:
♦ ACTIVE - The FoxCTS user can login at a FoxCTS Client station.
♦ PASSWORD EXPIRED - The FoxCTS user will have to change the
password on the next login. This is the default setting at account creation.
♦ TEMPORARILY INACTIVE - The FoxCTS user cannot login until the
FoxCTS administrator changes this status. If the FoxCTS user has exceeded
the number of login retries, their account status will automatically change to
TEMPORARILY INACTIVE and the FoxCTS user cannot login until the
FoxCTS administrator changes their User Account Status.
♦ PERMANENTLY INACTIVE - The FoxCTS user cannot login until the
FoxCTS administrator changes this status.
♦ User Type - Assigns the FoxCTS user type for this user account. This setting
controls the default home environment and other environments this user has
access.
♦ Assigned Process Areas - The list of process areas currently assigned to the
FoxCTS user account. If a specific process area is selected, the list of Assigned
Workstations Allowed will automatically be set to ALL.
♦ Available Process Areas -The list of process areas currently unassigned.
♦ Assigned Workstations Allowed - The list of workstations currently assigned to
the FoxCTS user account. If a specific workstation is selected, the list of Assigned
Process Areas will automatically be set to ALL.
♦ Available Workstations Allowed -The list of workstations currently unassigned.
♦ FoxCTS Configurator Access - FoxCTS Configurator Access assigned to this user
account. Available options are None or Access.
Figure 4-18 represents the User Accounts dialog box of the FoxCTS Configurator. In this example
a FoxCTS User Account is being added.

78
4. FoxCTS Domain Configuration B0193VV – Rev K

Figure 4-18. FoxCTS Configurator - User Accounts

Take the following steps to create or modify the FoxCTS User Accounts in a FoxCTS domain.
1. Start the FoxCTS Configurator from the FoxView menu bar.
2. Select the User Configuration menu item and then select the User Accounts
pull-down menu item.
3. Enter a new User Account or select an existing User Account from the list.
♦ Select the Add button to add a new user account to the FoxCTS domain database.
♦ Select the Update button to save changes to the selected user account.
♦ Select the Print button to display the user account information in a text editor.
♦ Select the Clear button to clear the dialog box without saving.
♦ Select Exit to close the dialog box.

79
B0193VV – Rev K 4. FoxCTS Domain Configuration

80
5. Additional Configurations
This chapter discusses some optional FoxCTS configurations that can be made after the
installation of the FoxCTS package.

Inactivity Timers
With the installation of the FoxCTS Client module the FoxCTS administrator can control idle
FoxCTS sessions and idle display managers by using inactivity timers. When the FoxCTS Client
module is installed, default inactivity timers are created for every display manager listed in the
local workstations dmcfg file that the workstation hosts. The default settings for all inactivity
timers is LOGOUT=0 and EXIT=0, effectively disabling the inactivity timer.
The available inactivity timers are:
♦ FoxCTS Session Logout Timer (LOGOUT) - The amount of time, in minutes, a
FoxCTS user session can remain idle before the user is logged out of the session.
♦ Display Manager Exit Timer (EXIT) - The amount of time, in minutes, that the
FoxView display manager can remain idle before the display manager is closed. This
timer does not apply to the primary display manager, since it cannot be closed.
Both inactivity timers are controlled by parameters set in ASCII file(s) located in the
D:\opt\foxind\cms\clnt\login\etc\dm folder.
♦ The default file controls all logout and exit times for the display managers that do not
have their own <dmName> file created.
♦ The <dmName> files are created to control the logout and exit times for a specific
display manager.

Inactivity Configuration
Each FoxView display manager in the system may have a different set of inactivity timers and
these display manager named files override the settings in the default file.
Use the following instructions to edit the parameters in an inactivity configuration file:
1. Open a command window from the FoxCTS Client station.
2. Change to the correct directory.
cd D:\opt\foxind\cms\clnt\login\etc\dm
3. Use any text editor to edit the default or <dmName> file to adjust each timer,
LOGOUT (user inactivity) and EXIT (display manager inactivity). Enter the
inactivity value in minutes.
4. Reboot the PC.

81
B0193VV – Rev K 5. Additional Configurations

Optional Configurations
The following are optional FoxCTS configurations that can be used to customize the FoxCTS
installation.

FoxCTS Login Box


For workstations with security enhancements the FoxCTS login box is optional and by default no
FoxCTS login box displays. If the FoxCTS login box is desired for entering a Job Number, simply
create the d:/opt/foxind/cms/clnt/LOGINBOX file. The existence of the LOGINBOX file
controls whether or not the FoxCTS Login box appears.

Customizing the FoxCTS Initial Environments


After FoxCTS Client module installation, the FoxCTS administrator may customize the default
FoxCTS initial login environment. However, the FoxCTS login functionality which exists in the
initial login environment, must be maintained. The FoxView initial environments are kept in
directory D:\opt\fox\env. This section contains a full description of how to customize the Fox-
CTS initial login FoxView environment.
Consult FoxView document to obtain instructions on configuring environments and on how to
add protection classes to the Process and System buttons on the menu bar.

NOTE
Be aware that the FoxCTS product cannot attribute changes to a specific FoxCTS
user unless a forced FoxView login occurs. (For workstations with enhanced
security, this login is performed automatically by default.)

Initial Environment Login


This section provides instructions on how to customize the FoxView initial environment.
If an automatic login window pop-up is not desired, follow these instructions:
1. Open a command window from a FoxCTS Client station.
2. Change to the directory containing the Init_Env file: cd D:\opt\fox\env
3. Using any text editor, edit the initial environment file: vi Initial.env
4. Delete the line that reads D:\usr\fox\FoxCTS\Login.
5. Save the changes to the Initial.env file.
6. Copy the edited Initial.env file to the FoxCTS Client FoxView environment
directory. For example:
cp D:\opt\fox\env\Initial.env D:\opt\foxind\cms\clnt\env\Initial.env
The FoxCTS Logout function returns the workstation to the initial Login environment. In order
to disable this functionality, the Logout file must be modified.

Initial Environment Logout


The FoxCTS Logout function returns the FoxCTS user to the initial Login environment. In order
to disable this functionality, that is, to be able to return to the initial environment, the Logout file

82
5. Additional Configurations B0193VV – Rev K

must be modified to include the settings of the customized Initial.env file.


The following instructions explain how to customize the FoxView Logout Environment:
1. Open a command window from a FoxCTS station.
2. Move to the FoxCTS directory that holds the FoxView environments by typing:
cd D:\opt\foxind\cms\clnt\env
3. Display the environment file:
more Initial.env
4. Open a second command window and change to the FoxCTS commands directory:
cd D:\usr\fox\FoxCTS
5. Use a text editor to edit the Logout file to reflect the customized settings to the
Initial_Env file. Save the changes to the Logout file.

Initial Environment
After FoxCTS Client module installation, the Logout script initially point to the Initial
environment for FoxView. The following steps could be taken to alter the default FoxCTS login
process.
1. Copy the FoxCTS edited files from the FoxCTS Client environment directory
D:\opt\foxind\cms\clnt\env to the default FoxView environment directory
D:\opt\fox\env.
cp D:\opt\foxind\cms\clnt\env\<preferred Env>.* D:\opt\fox\env
2. Once the copy is complete, the following lines must be added to the .env files:
dmcmd nolog_scripts
dmcmd passwd
dmcmd chng_env
dmcmd run sh /opt/foxind/cms/clnt/login/bin/run_cms_logout.sh
/opt/foxind/cms/tmp/logoutStatusFromInit_Env “$GCLBUG”
“$DMNAME” “$USERNM”
dmcmd = USERNM ““
dmcmd = COMMNT ““
dmcmd = JOBNO ““
dmcmd = SUPVFN ““
dmcmd = SUPVID ““
dmcmd = SUPVLN ““
dmcmd = SUPVNM ““
dmcmd = USERFN ““
dmcmd = USERID ““
dmcmd = USERLN ““
3. Edit the FoxCTS Display FoxView Logout script, D:\usr\fox\FoxCTS\Logout, to
contain just the following line. Any other lines in this file should be deleted.
D:/opt/fox/env/Initial.env

4. Edit the display manager Inactivity Timer Logout script,


D:\opt\foxind\cms\clnt\login\bin\logoutUser to read:
dmcmd == :$USERNM : dmcmd exit_script
/usr/fox/sys/Logout

83
B0193VV – Rev K 5. Additional Configurations

dmcmd msglin “User Logged Out: NO ACTIVITY.”


5. Copy the preferred environment over the default FoxCTS Initial.env environment.
cd /opt/fox/env
cp <preferredEnv>.env Initial.env
cp <preferredEnv>.acl Initial.acl
cp <preferredEnv>.dbr Initial.dbr
cp <preferredEnv>.dms Initial.dms
cp <preferredEnv>.mbr Initial.mbr

Customizing the FoxCTS Menu


The files that control the menu items under the FoxCTS menu are located in the
D:\usr\fox\FoxCTS folder. The FoxCTS menu items are described as follows.
Admin - This pull-down menu item starts the FoxCTS Configurator but only if the current
FoxCTS user has the proper access rights. This menu item is only available at the FoxCTS Server
station.
Chg_Env - This pull-down menu item allows the current FoxCTS user access to his specified
environments.
Login - This pull-down menu item logs out the current FoxCTS user and logs in a new FoxCTS
user.
Logout - This pull-down menu item logs out the current FoxCTS user.
Passwd_Chg - For standard installations of the Control software, this pull-down menu item is
available to allow the current FoxCTS user to change their password.
User_Name - This pull-down menu item displays the name of the current user. This pull-down
menu item is optional and may be removed for security reasons.
If relocating any of these commands, keep in mind that a FoxCTS user needs to be allowed to
login, logout and change environments. For this reason, it is recommended that the Login,
Logout, and Chg_Env menu options remain at their default location. The other FoxCTS menu
options Admin and User_Name may be relocated.
For example, at the FoxCTS Server station the FoxCTS Admin menu item, may be moved into
the Config menu by following these instructions:
mv D:\usr\fox\FoxCTS\Admin D:\usr\fox\config

Foxboro Evo Control Editors/IACC Integration


It is possible to use the same user name for the Foxboro Evo Control Editors, IACC and FoxCTS
software packages but user accounts will have to be created and maintained separately in each
product.

84
5. Additional Configurations B0193VV – Rev K

FoxCTS PACTware Module


The PACTware product uses user rights to control access to the HART field devices. Once the
FoxCTS PACTware module is installed, FoxCTS Group assignments will be used to determine
PACTware user rights. The FoxCTS Groups listed in Table 5-1 are created automatically and are
used to support the PACTware user rights.
To control PACTware access, assign the FoxCTS PACTware Group to the desired FoxCTS User
Type and then assign the FoxCTS User Type to the appropriate FoxCTS user account.

NOTE
FoxCTS PACTware Groups can be assigned to multiple FoxCTS User Types but
only one FoxCTS PACTware group should be assigned to a FoxCTS User Type. If
multiple FoxCTS PACTware group assignments have been made to a FoxCTS User
Type, then the most restrictive group assigned will be used.

Table 5-1. FoxCTS PACTware Groups

FoxCTS Groups PACTware User Right


PWADMIN FoxCTS User Type(s) assigned with this group will have
PACTware Administrator rights.
PWPLANENGR FoxCTS User Type(s) assigned with this group will have
PACTware Planning Engineer rights.
PWMAINT FoxCTS User Type(s) assigned with this group will have
PACTware Maintenance rights.
PWOPERATOR FoxCTS User Type(s) assigned with this group will have
PACTware Operator rights.
PWOBSRVR FoxCTS User Type(s) assigned with this group will have
PACTware Observer rights.

Reference the PACTware Process Automation Configuration Tool document for more information
regarding the PACTware user rights and reference “Groups” on page 71 for more information
regarding FoxCTS Groups.

85
B0193VV – Rev K 5. Additional Configurations

86
6. FoxCTS Human Interface
This chapter discusses the FoxCTS Human Interface.
After the installation of the FoxCTS Server station, only the default FoxCTS administrator may
login to the FoxView display. The default FoxCTS administrator user access is initially limited to
only the FoxCTS menu items and all other FoxView environments are not available. The initial
purpose of the default administrator user is to configure the FoxCTS domain.
The initial FoxCTS administrator login will depend on whether or not the workstation has
security enhancements.
♦ For FoxCTS Server stations that have a standard configuration, log in as the user
admin with the default password, gnomes. This default FoxCTS administrator
account is set up to force the user to change the password during the initial login.
The new password will need to include at least one numeric and one upper-case
alphanumeric character, in keeping with the default password control rules.
♦ For FoxCTS Server stations that have enhanced-security, log in as the Microsoft
domain user that installed the FoxCTS Server module. This default administrator
account has permission to configure the FoxCTS domain.
Once the FoxCTS domain is configured, any authorized FoxCTS user may access the display
manager from a workstation that has the FoxCTS Client module installed.
By default the FoxView FoxCTS button contains menu items for Admin, Chg_Env, Login,
Logout, Passwd_Chg and User_Name, Figure 6-1.

NOTE
(1) The Admin menu item only appears at the FoxCTS Server station.
(2) The Passwd_Chg menu item only appears on standard workstations.

Figure 6-1. FoxCTS Menu

87
B0193VV – Rev K 6. FoxCTS Human Interface

FoxCTS Menu Items


The FoxView’s FoxCTS button is on the FoxView menu bar. The FoxCTS menu items are
defined as follows:
Admin - Starts the FoxCTS Configurator. Only FoxCTS users with the proper access
rights can start the configurator. This menu item is only available at the FoxCTS Server
station.
Chg_Env - Lists the available environments assigned to the current user.
Login - Logs the current user out and then logs the new user in.
Logout - Logs the current user out.
Passwd_Chg - Change the password of the current FoxCTS user. Only available for
standard workstation installations.
User_Name - Displays the current FoxCTS user’s login name.

Admin (FoxCTS Configurator)


The FoxCTS Configurator is only available to FoxCTS users with the proper access level and is
only available at the FoxCTS Server station.
To access FoxCTS Configurator:
1. Select the FoxCTS menu button on the FoxView menu bar.
2. Select Admin to launch the FoxCTS Configurator, see Figure 6-2. Select FoxCTS >
Exit to close the configurator.

Figure 6-2. FoxCTS Configurator

88
6. FoxCTS Human Interface B0193VV – Rev K

Chg_Env
Only those environments configured for the current FoxCTS user account will be displayed. To
change environments:
1. For FoxView, select the FoxCTS menu button on the FoxView menu bar and select
Chg_Env from the menu and wait for the FoxCTS Change I/A Environment dialog
box to appear, see Figure 6-3.

Figure 6-3. Change Environment Dialog Box

2. Make a selection from the FoxCTS Change I/A Environment dialog box:
a. Select one of the FoxView environments from the list box.
b. Select Home to return to the current user’s assigned home environment.
c. Select Cancel to exit the Change Environment dialog box.

Login
The user login dialog box can be started in one of the following ways.
♦ For standard installations of the Control software, when FoxView is started the
FoxCTS login dialog box automatically appears. If the FoxCTS Login dialog box is
not used within 60 seconds, the dialog box times out and closes. If the dialog box is
closed, then the login dialog box will have to be launched from the display manager
Login item.
♦ Select the initial environment’s Login item.
♦ Select the FoxCTS menu item Login.

Standard Workstations
The following describes the FoxCTS login in process for standard workstation installations.
1. Wait for the FoxCTS User Login dialog box to appear, see Figure 6-4. The message
line of the display manager should show “Local Application Startup” shortly before
the Login dialog box appears.

89
B0193VV – Rev K 6. FoxCTS Human Interface

NOTE
The following characters cannot be used in user login names, passwords, or job
numbers: + = / [] “ ‘ : ; , ? * \ < > | { } ‘ and a space.

Figure 6-4. FoxCTS Login - Standard Workstation

2. Enter a valid FoxCTS user login name in the User field and press Enter.
3. Enter the password of the FoxCTS user in the Password field and press Enter.
4. If you want to track changes by a work order, tracking number or job number, enter
that information in the Job Number field. If not, leave the Job Number field empty
and select OK.

TIP
(1) Use a underscore (_) or a dash (-) to separate a multi-worded job number, for
example: No1234_Config-Displays.
(2) A job number cannot exceed 35 characters.

Workstations with Security-Enhancements


This section describes the FoxCTS FoxView login process for workstations with security
enhancements.

No FoxCTS Login Box


By default the FoxCTS User Login dialog box will not appear and the login process for the
current Microsoft domain user takes place in the background, with progress messages appearing
on the FoxView display’s message line.

90
6. FoxCTS Human Interface B0193VV – Rev K

Optional FoxCTS Login Box


If FoxCTS has been configured per the instructions found on page 82, to invoke the FoxCTS
User Login dialog box:
1. Wait for the FoxCTS User Login dialog box to appear, see Figure 6-5. The message
line of the display manager should show “Local Application Startup” shortly before
the Login dialog box appears.

NOTE
The following characters cannot be used in job numbers: + = / [] “ ‘ : ; ,
? * \ < > | { } ‘ and space.

Figure 6-5. FoxCTS Login - Workstation with Security Enhancements

2. The current Microsoft domain user login name appears in the User field and this field
is disabled. There must be a FoxCTS user account created with this Microsoft domain
login name for a successful FoxCTS login to occur.
3. The Password field is disabled since this Microsoft domain user has already been
successfully authenticated by the Microsoft primary domain controller.
4. If you want to track changes by a work order, tracking number or job number, enter
that information in the Job Number field. If not, leave the Job Number field empty
and select OK.

TIP
(1) Use a underscore (_) or a dash (-) to separate a multi-worded job number, for
example: No1234_Config-Displays.
(2) A job number cannot exceed 35 characters.

Logout
To log the current FoxCTS user out of the FoxView session.
1. Select the FoxCTS menu button from the FoxView menu bar.
2. Select Logout from the FoxCTS menu.

91
B0193VV – Rev K 6. FoxCTS Human Interface

Passwd_Chg
This menu pick is only available for standard workstations and is used to change the password of
the current FoxCTS user.
1. For FoxView select, the FoxCTS menu button from the FoxView menu bar.
2. Select Passwd_Chg from the menu.
3. Wait for the FoxCTS Change Password dialog box to appear, see Figure 6-6. Enter the
required password information and select OK.

NOTE
(1) The following characters cannot be used in user login names, passwords, or job
numbers: + = / [ ] “ ‘ : ; , ? * \ < > | { } ‘ and a space.
(2) The password has a maximum length of 14 characters.

Figure 6-6. FoxCTS Change Password

User_Name
To determine the currently logged in FoxCTS user:
1. For FoxView select, the FoxCTS menu button from the FoxView menu bar.
2. Select User_Name from the menu, see Figure 6-7.
3. The current FoxCTS user’s login name appears in brackets on the display manager’s
message line. In this example, the current FoxCTS user is ajohnson.

Figure 6-7. FoxCTS User_Name Example

92
6. FoxCTS Human Interface B0193VV – Rev K

User Reconfirmation
The FoxCTS User Reconfirmation component allows the execution of any valid display manager
commands from a process graphic, provided that qualified FoxCTS user(s) endorse or reconfirm
the action. User reconfirmation is most commonly used to control sensitive process changes from
process graphics that can be accessed by a wide range of plant personnel. User reconfirmation is
initiated from a FoxView display pick.
Before implementing FoxCTS User Reconfirmation, the FoxCTS administrator must decide:
1. The display manager command to be implemented.
Examples:
dmcmd stddisp CTS_SCRN_TST_PID (Brings the detail display for
CTS_SCRN_TST_PID.)
dmcmd toggle $P3:$P4.MA (Toggle the MA value.)
2. The number of FoxCTS users that must endorse the user reconfirmation action before
it can be performed.
The username(s) provided must refer to an active FoxCTS user account(s). The
currently logged in FoxCTS user name will appear in the User field.

TIP
There must be a FoxCTS user login name that matches the Microsoft domain user
login name for a successful User Reconfirmation to occur.

Figure 6-8. Single User Reconfirmation Dialog Box

93
B0193VV – Rev K 6. FoxCTS Human Interface

Figure 6-9. Dual User Reconfirmation Dialog Box

3. The process-specific displays from which the FoxCTS User Reconfirmation can be
launched.
Launching user reconfirmation from a process graphic requires adding additional
symbols to the graphic. These symbols will occupy space on the process graphic and
may require graphics to be rearranged or redesigned.
The FoxCTS Client module provides FoxView palettes and symbols (Figure 6-10)
that simplify the addition of user reconfirmation to the graphics.

Figure 6-10. FoxCTS Palette

94
6. FoxCTS Human Interface B0193VV – Rev K

In Figure 6-11, the Standard Embedded Objects consists of a small lock symbol and
accompanying data readout box to the right of the lock symbol. The embedded object
labeled “SINGLE” will result in the pop-up of a Single Password User Reconfirmation
dialog box (Figure 6-8), while the “DOUBLE” object results in the pop-up of a Dual
Password User Reconfirmation dialog box (Figure 6-9).
The single and double embedded objects can be placed on the process graphic for
simple, single pick invocation of user reconfirmation. However, the objects may take
up more display real estate than is available. For this reason, the FoxCTS software
offers the Standard Embedded Buttons, along with the single data readout box,
located at the bottom of the FoxCTS palette.
The administration can replace each modifiable process variable text fields with a data
readout box, and locate a single lock symbol somewhere on the graphic. This arrange-
ment allows multiple readouts to share the same single lock button.
In order to use the FoxCTS templates, copy the templates to the appropriate folder.
For example:
cp -r d:/opt/foxind/cms/clnt/tests/scrnAct/fvlib/FV10/*
D:/opt/customer/displib
More detailed confirmation instructions can be found at the end of this section.
The FoxCTS Generic Screen Action Test display (Figure 6-11) is provided as an
example and is located in d:/opt/foxind/cms/clnt/tests/scrn-
Act/fvdisp/SCRN_TEST.fdf. This test display can be viewed on a workstation by
running the following command from a NutCracker shell:
/usr/local/pref -<dmName> DMCMD /opt/foxind/cms/clnt/tests/scrn-
Act/fvdisp/SCRN_TEST

95
B0193VV – Rev K 6. FoxCTS Human Interface

Figure 6-11. User Reconfirmation Test Display

To see the FoxCTS user reconfirmation capabilities operate from the test display,
provide the necessary information under the Generic Screen Action Test section, then
manipulate the data readout and lock buttons.
The Generic Screen Action Test display’s red lock button contained in the Single Pick
User Reconfirmation box will cause a dual FoxCTS User Reconfirmation box to
appear (Figure 6-12). If the FoxCTS username/password are valid, the resulting
display manager action will display an overlay which allows the user to provide a new
value for the CTS_SCRN_TEST:PID.SPT variable.
When the user selects the CLOSE button, the SPT value is updated to reflect the new
value. No action is taken if either FoxCTS username/password is invalid.

96
6. FoxCTS Human Interface B0193VV – Rev K

Figure 6-12. Dual Login User Reconfirmation

FoxCTS username/password combinations are validated differently depending on the


circumstances:
♦ On security-enhanced workstations, the username/password is authenticated
against the Microsoft primary domain controller.
♦ On standard workstations, the username/password is verified against the FoxCTS
domain database. If the FoxCTS Server is temporarily unavailable, the username
and password are verified locally.
Take the following steps to use the Single User Login or Dual User Login symbols:
♦ Start the FoxDraw software and open the graphic for editing.
♦ Open the FoxCTS palette, select the desired FoxCTS symbol (Single Login or
Dual Login) and drag it to the graphic.
♦ Configure the item to connect to the correct ompound:block.parameter. There
are two changes required (one to Operation Action and one to Dynamic Update):
♦ Select the Object
♦ Select Readout
♦ Select the Dynamic Update tab
♦ Change the word CBP to the actual compound:block.parameter
♦ Select the Operation Action tab
♦ Change the word CBP to the actual compound:block.parameter
♦ Save the changes to the item.

97
B0193VV – Rev K 6. FoxCTS Human Interface

Enhanced Operator Action Journal


The FoxCTS package includes an enhancement to the Operator Action Journal system. This
enhancement is not directly visible to the user of the system, but is visible to users of the
AIM*Inform software.
The enhanced Operator Action Journal functionality adds the following fields to the standard
OAJ message:
♦ FoxCTS User’s Name - First, Last and login name
♦ FoxCTS User’s User ID
♦ FoxCTS Job (Work Order Tracking) Number
In addition, the User Reconfirmation will generate an OAJ message that has the following
additional fields:
♦ FoxCTS Supervisor’s Name - First, Last and login name (Dual User Reconfirmation
only.)
♦ FoxCTS Supervisor’s User ID (Dual User Reconfirmation only.)
♦ Comment on the action (Single or Dual User Reconfirmation.)
This information is all recorded in AIM*Historian database if the package is installed and can be
viewed using the AIM*Inform tool.

Tool Usage Tracking


The FoxCTS package provides two tools, wrap_all_tools and unwrap_all_tools, that may be used
to extend usage tracking to user written tools launched from FoxView menu items.
The wrap_all_tools command, located in the directory D:\opt\foxind\cms\clnt\scripts, reads the
files in the specified directory and alters the file in such a way that all programs started by the
display manager commands run, applic, wp_applic and = PGM are recorded with login and log-
out records in the FoxCTS change database.
The unwrap_all_tools command, also found in the directory
D:\opt\foxind\cms\clnt\scripts, reverses the changes made by wrap_all_tools.
See instructions in “Command Usage” on page 149 for details on how to use these tools.

Other Scripts and Commands


For those customers who wish to log the use of scripts and tools other than those launched by the
FoxView menu picks, the FoxCTS package supplies a tool that may be used to meet this need.
This tool is a script called wrap_tool. It allows the user to login and out the use of user
created scripts and programs. See “Command Usage” on page 149 for details and examples on
how to use this tool.

98
6. FoxCTS Human Interface B0193VV – Rev K

ICCLaunch
After the FoxCTS Client module installation, the CIO_Config menu pick starts the FoxCTS
ICCLaunch utility that allows the user to select a compound, enter the ICC, and be tracked by
the FoxCTS package.

NOTE
The AIM*API software (Control Core Services v9.0 or I/A Series Software v8.8) or
FoxAPI software (I/A Series Software v8.5-v8.7) must be installed and configured for
the ICCLaunch utility to function properly.

Figure 6-13. ICCLaunch Dialog Box

The ICCLaunch dialog box, Figure 6-13, includes the following selection:
Compound Filter - This field allows the user to enter the criteria for filtering.
Filter - This button starts the filter query.
Rebuild - This button builds an updated list of compound names. When new compounds are
added the Rebuild button must be used to update the list.
ICC - This button launches ICC for the selected compound.
Quit - This button quits the ICCLaunch utility.
Examples:
1. To find all compounds that start with the number 2, just enter the number 2 in the
Compound Filter field and select the Filter button.
2. To find all compounds that have the letters CP in them, enter *CP* in the
Compound Filter field and select the Filter button.

99
B0193VV – Rev K 6. FoxCTS Human Interface

100
7. Maintenance
This section discusses the regular maintenance that may have to be done after the FoxCTS
module(s) are installed.

Uninstall FoxCTS Modules


Uninstalling the FoxCTS software returns the workstation to its original state with the exception
of any modifications to the environment files that may have made during the use of the FoxCTS
package.
1. If uninstalling the FoxCTS Server, the FoxCTS Domain database can be backed up
to be restored at a later date. See page 57 for database backup instructions.
2. The FoxCTS modules can be uninstalled by using:
a. Windows Programs and Features or
b. Windows Add Remove Programs.
3. Select the FoxCTS module to be uninstalled and select Yes or OK to any message
boxes that appear.
4. Be sure to check the following before rebooting.
♦ If the FoxCTS Server module was uninstalled, copy the
d:\opt\foxind\cms\srvr\domainBkups folder to a location outside of the
d:\opt\foxind\cms folder.
♦ If the FoxCTS Client module was uninstalled, check the environment files in
d:\opt\fox\env folder to ensure that the files are correct and up-to-date before
deleting the d:\opt\foxind\cms\clnt or d:\opt\foxind\cms folders.
5. Reboot the PC after all of the desired FoxCTS modules have been uninstalled.
a. For I/A Series Software v8.5-v8.7, reboot the PC by selecting Start, then Run,
enter the command foxshutdown 10 1 1 and select OK.
b. For Control Core Services v9.0 or I/A Series Software v8.8, select the Windows
Restart button.
6. After uninstalling a FoxCTS module:
♦ If other FoxCTS modules remain installed, just remove the folder name of the
uninstalled FoxCTS module, D:\opt\foxind\cms\<moduleName>.
♦ If all of the FoxCTS modules have been uninstalled, remove the
D:\opt\foxind\cms folder.

101
B0193VV – Rev K 7. Maintenance

Reinstall FoxCTS
Before reinstalling FoxCTS be sure to:
♦ Delete the D:\opt\foxind\cms folder if all FoxCTS modules have been uninstalled.
♦ Delete the D:\opt\foxind\cms\<moduleName> folder, for the FoxCTS modules that
have been installed.
After the proper directory(s) have been deleted, follow the instructions to install a new copy of the
FoxCTS modules.

TIP
When the FoxCTS Server module is uninstalled a backup of the current FoxCTS
domain database is created in the d:\opt\foxind\cms\server\domainBkups folder. It
is possible to relocate this backup file for later use.

Upgrades
FoxCTS
For most upgrades the following sequence of events must occur during an upgrade.
1. Follow the instructions in this manual for backing up the FoxCTS domain database.
2. Uninstall all of the FoxCTS modules on all of the workstations in the FoxCTS
domain. A suggested order for module removal would be: ICC Driver, SysMon,
Client, OAJ Host, and Server.
3. After all the FoxCTS modules have been uninstalled, remove the d:\opt\foxind\cms
folder.
4. Install the FoxCTS Server module and restore the backup of the FoxCTS domain
database.
5. Install the remaining FoxCTS modules on all workstations in the FoxCTS domain.

Control Core Services or I/A Series Software


Some upgrades will require that all of the FoxCTS modules be uninstalled. After the successful
software upgrade, the FoxCTS modules can be reinstalled.

FoxView
If a FoxView upgrade is performed or a FoxView quick fix that replaces the foxview.exe file is
installed, then the following steps must be performed.
1. Turn off the I/A Series Software and reboot.
2. Change to the D:\opt\fox\wp\foxview folder.
a. Copy the foxview.exe file to foxview.exe.foxcts.
b. Copy the foxview_cts.exe file to foxview_cts.exe.orig
3. Upgrade the FoxView software or apply the FoxView Quick Fix but do not reboot the
4. Change to the D:\opt\fox\wp\foxview folder.

102
7. Maintenance B0193VV – Rev K

a. Rename the new foxview.exe file to foxview_cts.exe.


b. Copy the foxview.exe.foxcts file to foxview.exe.

TIP
If the FoxCTS version of the foxview.exe file was not copied prior to the FoxView
upgrade or quick fix, then copy the FoxCTS version of the foxview.exe file from the
FoxCTS installation media.

Upgrades - PACTware
If the PACTware software is upgraded, then the following procedure must be followed.
1. Uninstall the FoxCTS PACTware module.
2. Uninstall the PACTware software.
3. Rename or delete the [C: | D:]\Program Files\PACTware Consortium folder.
4. Verify that the Registry was deleted the following key:
HKEY_LOCAL_MACHINE\SOFTWARE\PACTware.
5. Install the new version of the PACTware software.
6. Re-install the FoxCTS PACTware module.

System Commits
FoxCTS SysMon Hosts
If one of the system utilities Install Release Update, Install Selected Package(s)/Load Release
Level Diskettes, or Reinstall Cancelled/Failed Packages is used on the FoxCTS System Monitor
hosts, then the FoxCTS SysMon module either needs to be reinstalled or the following steps must
be preformed.
1. Make a note of the FoxCTS SMMRxx name assigned to this station. (This name can
be found in the D:\opt\foxind\cms\sysmon\data\IANAME file.)
2. Run the required utility Install Release Update, Install Selected
Package(s)/Load Release Level Diskettes, or Reinstall Cancelled/Failed Packages.
3. Use the grep command to check if the SMMRxx name has been removed. If nothing
comes back the name was not found. For example:
C:\Program Files\nutc\mksnt\grep SMMR02 D:\usr\fox\sp\IIF.prm
4. Use the glof command to verify that the SMMRxx name no longer exists. A status of
255 means the name was not found. For example:
C:\opt\fox\bin\tools\glof -p SMMR02
5. If the grep and glof commands indicate that the SMMRxx name now exists, proceed
to Step 7.
6. If the grep and glof commands indicate that the SMMRxx name no longer exists:
a. Make a copy of the current destact.cfg file. For example:
cd D:\usr\fox\sysmgm\sysmon
cp destact.cfg destact.cfg.old

103
B0193VV – Rev K 7. Maintenance

b. Update the destact.cfg file with the SMMRxx destination name. For example:
cd D:\opt\foxind\cms\sysmon\bin
chg_destact SMMR02 D:\usr\fox\sysmgm\sysmon\destact.cfg
cd d:\usr\fox\sysmgm\sysmon
cp destact.cfg.new destact.cfg
7. Restart SysMon with the FoxCTS destination name by rebooting the PC.

Quick Fixes
FoxCTS
Please refer to the specific FoxCTS quick fix user notes for installation instructions.

Foxboro Software
Installation of some Foxboro software Quick Fixes will require that some, or all, of the FoxCTS
modules be uninstalled before the installation of the Quick Fix. After the installation of the Quick
Fix, the FoxCTS module(s) can be reinstalled.

FoxCTS Client Module


The FoxCTS Client must be uninstalled before any Quick Fix relating to the FoxView software,
or the Integrated Control Configurator is installed. After the installation of the Quick Fix, the
FoxCTS Client module can be reinstalled.

FoxCTS Server Module


If the Quick Fix will change the file D:\usr\fox\bin\fox_apps.dat folder, then this file must be
backed up before installing the Quick Fix. After the installation of the Quick Fix, the backed up
file can be restored.

FoxCTS Services
Only those FoxCTS Services of the installed FoxCTS modules will appear in the Services list.
For Control Core Services v9.0 or I/A Series Software v8.8, all FoxCTS Services Startup Type are
set to Automatic.
For I/A Series Software v8.5-v8.7, all FoxCTS Services are run as LocalSystem and the Startup
Type is set to Manual. All FoxCTS Services are started on reboot by the fox_apps.dat mechanism.
The following is a list of the possible FoxCTS Services that might be running on a FoxCTS
station:
♦ FoxCTS Client FT - Installed as part of the FoxCTS Client module.
♦ FoxCTS Iccdrvr - Installed as part of the FoxCTS ICC Driver module.
♦ FoxCTS OAJ Client - Installed as an option to the FoxCTS Client module.
♦ FoxCTS OAJ Server - Installed as part of the FoxCTS OAJ Host module.
♦ FoxCTS RCPRSH - Installed as part of the FoxCTS Server, FoxCTS Client and
FoxCTS ICC Driver modules.

104
7. Maintenance B0193VV – Rev K

♦ FoxCTS Scheduled Tasks - Installed as part of the FoxCTS Server and FoxCTS Client
modules.
♦ FoxCTS Server - Installed as part of the FoxCTS Server module.
♦ FoxCTS Sysmon - Installed as part of the FoxCTS SysMon module.
If needed, use the following procedure to start a FoxCTS Service manually.
1. From the Services window, Figure 7-1, look for the FoxCTS labeled Services.

Figure 7-1. FoxCTS Services

2. If a FoxCTS Services did not start, highlight the FoxCTS Service that is not running
and start the service.
The following processes integrate with the FoxCTS software but are actually a component of
another product.
♦ FoxCTSTransferUtility - Installed and maintained by the IACC product. This is the
IACC schedule task that transfers change data to the FoxCTS Server.
♦ FoxCTS.Transfer.Service - Installed and maintained by the Foxboro Evo Control
Editors. This is the Foxboro Evo Control Editors Service that transfers change data to
the FoxCTS Server.

FoxCTS Log File


The FoxCTS Server module maintains a comprehensive log (cmslog) file that consists of the
change activities on a FoxCTS domain. The FoxCTS Server module maintains a set of eight daily
backups of the cmslog file, named cmslog (current), cmslog.0 (newest) through cmslog.7 (oldest).

105
B0193VV – Rev K 7. Maintenance

Tool Wrapping
During the FoxCTS Client module installation, the installed tools and any other display manager
script that contains the display manager commands run, applic, wp_applic, =PGM. The display
manager scripts that are located in the directories, D:\usr\fox\config, D:\usr\fox\soft and
D:\usr\fox\sys are wrapped so that FoxCTS product can record user access. These tools include
but are not limited to: Display Builder, Display Configuration, FoxPanels, Palette Editor, etc.

NOTE
All tools wrapped during or after the FoxCTS Client module installation are
unwrapped when the FoxCTS Client is uninstalled.

Adding a New Tool


If a new tool or display manager script is installed on a FoxCTS Client station, the following steps
must be used before user access to this tool is recorded.
1. From a command window from a FoxCTS Client station.
2. Run the wrap script:
sh
cd D:/opt/foxind/cms/clnt/scripts
wrap_all_tools <directoryName> (For example: wrap_all_tools D:/usr/fox/soft)

Environments
During the installation of the FoxCTS Client the FoxView environment files are backed up to the
D:\opt\foxind\cms\bkup folder and moved to the D:\opt\foxind\cms\clnt\env folder where they
are modified for change tracking use. The environment files that are left behind in the
D:\opt\fox\env folder are initial environments required for use by the dmcfg file.

Adding a New Environment


The following procedure can be used to add a new environment after the installation of the
FoxCTS Client module.
1. To ensure the environment file is correctly modified for change tracking, copy an
existing environment file from the D:\opt\foxind\cms\clnt\env folder.
For example:
sh
cd D:/opt/foxind/cms/clnt/env
cp Engineer.acl Tst_Engr.acl
cp Engineer.env Tst_Engr.env
cp Engineer.dbr Tst_Engr.dbr
cp Engineer.mbr Tst_Engr.mbr
2. Edit the copied file to meet the specific needs but be careful not to edit the required
FoxCTS lines.
3. Use the FoxCTS Configurator to add the new environment.

106
8. Troubleshooting
This chapter provides the FoxCTS administrator information and techniques to assist in
troubleshooting some of the most common problems that may arise with the FoxCTS software.

FoxCTS Log Files


The FoxCTS package performs extensive logging that can be valuable in solving problems. The
following are log files that may be of particular interest.

cmslog
The FoxCTS Server’s cmslog file is the master log file that records the major operations performed
by the FoxCTS package. For example, by examining this file, the FoxCTS user with the proper
privileges, can see when the FoxCTS module was notified of a checkpoint and, therefore, begin
examining the CP for changes. For more information regarding the cmslog file see “FoxCTS Log
File” on page 105.

Miscellaneous Script Log Files


Many of the major FoxCTS scripts write log files in the directory D:\opt\foxind\cms\srvr\logs or
D:\opt\foxind\cms\clnt\logs. Each of these files is a trace of the activity generated by the
respective script. The log file is written once per execution and is overwritten each time the script
runs, so it does not grow beyond that initial size. Examination of these various script log files can
be instrumental when troubleshooting a suspected FoxCTS module problem.

FoxCTS Services
Not Starting on Reboot (I/A Series Software v8.5-v8.7)
If the FoxCTS Services do not start after a reboot with I/A Series Software v8.5-v8.7 it might be
necessary to adjust the FoxCTS Services StartDelay setting for the service. Changing the
StartDelay setting will delay the starting of the FoxCTS Service by the number of seconds
configured. Use the FoxCTS utility, modappreg, that is located in the d:\opt\foxind\cms\data
folder to modify the StartDelay setting of a FoxCTS Service.
To change the StartDelay of a FoxCTS Service:
1. Start the modappreg utility, Figure 8-1.
a. Select FoxCTS for the Application to be modified.
b. Select the desired FoxCTS module to adjust the StartDelay, see Table 8-1.
c. Double-click the StartDelay item from the list.
d. Change the value (New Value) for the StartDelay item. Increase the StartDelay
time by 20 seconds intervals until the FoxCTS Service successfully starts during a
reboot.
e. Click the Change Value button to save the change.

107
B0193VV – Rev K 8. Troubleshooting

f. Click the Exit button to close the modappreg utility.


2. During the next workstation reboot verify the FoxCTS Service successfully started.

Debug Logging
Each of the FoxCTS Services can be forced to log to a debug file using the FoxCTS utility,
modappreg, that is located in the d:\opt\foxind\cms\data folder.

Figure 8-1. modRegApp

To start debugging a FoxCTS Service:


1. Stop the desired FoxCTS Service via the Windows Services menu.
2. Start the modappreg utility, Figure 8-1.

TIP
For those using workstations with security enhancements, it might be necessary to
run ModAppReg.exe as Administrator. For example: using My Computer right-
click d:\opt\foxind\cms\data\ModAppReg.exe and select “Run as administrator”.

a. Select FoxCTS for the Application to be modified.


b. Select the desired FoxCTS module to start debug logging.
c. Double-click the Debug item from the list.
d. Change the value (New Value) for the Debug item to +Dn where n is a number
between 1 and 6. A good default setting to use is +D5.
e. Click the Change Value button to save the change.
f. Click the Exit button to close the modappreg utility.
3. Start the modified FoxCTS Service via the Windows Services menu.

108
8. Troubleshooting B0193VV – Rev K

4. Debug logging is now activated and the files will be generated in the FoxCTS module
associated with the selected FoxCTS Service.
Table 8-1 associates the FoxCTS Service name to the module name (modappreg) and to the
debug log file name.

Table 8-1. FoxCTS Services - Debug Logs

modappreg
Service Name Module Name Debug Log Name
FoxCTS Client FT Client\cmspoll D:\opt\foxind\cms\clnt\debug\cmspoll
FoxCTS Iccdrvr Iccdrvr\iccdrvd D:\opt\foxind\cms\iccdrvr\debug\iccdrvd
FoxCTS OAJ Client OAJ\oajAimRelay D:\opt\foxind\cms\oaj\debug
FoxCTS OAJ Server OAJ\oajMsgRelay D:\opt\foxind\cms\oaj\debug
FoxCTS Server Server\foxcmsd D:\opt\foxind\cms\srvr\debug\foxcmsd
FoxCTS Sysmon SysMon\smonMsgRelay D:\opt\foxind\cms\sysmon\debug\smonMsgRelay

FoxView
Minimized Console Window (I/A Series Software v8.5-v8.7)
If the FoxView console window appears minimized on the Taskbar, edit the
d:/usr/fox/system32/logon.cmd file to launch FoxView as follows:
Edit the line:
\usr\fox\system32\startp /b \usr\fox\system32\run_as_user.exe foxview.exe

to read:
\usr\fox\system32\startp /b \usr\fox\system32\run_as_user.exe -h foxview.exe

Common Problems
The following section addresses some common problems encountered when using the FoxCTS
product.

Cannot Change Set Points


The process graphics do not allow set point changes after the FoxCTS Client was installed.
The FoxCTS Client software is designed to enhance security as well as track changes. Therefore,
the Initial Environment shipped with the FoxCTS Client module disables OM sets. Thus, all
other environments need to be modified to enable OM sets.
During the FoxCTS Client module installation the environments were moved from their original
locations, D:\opt\fox\env, D:\opt\customer\env and other locations to the FoxCTS location
D:\opt\foxind\cms\clnt\env. Be sure to make the necessary changes to the environment files
located in the FoxCTS FoxView environment directory.

109
B0193VV – Rev K 8. Troubleshooting

Menu Items Not Selectable


The FoxView menu items are not selectable after the FoxCTS Client module was installed.
The FoxCTS Client software is designed to enhance security as well as track changes. Therefore,
the Initial Environment shipped with the FoxCTS Client module protects everything. Thus, all
other environments need to be modified to enable the appropriate access levels (protection
classes).
During the FoxCTS Client module installation the environments were moved from their original
locations, D:\opt\fox\env, D:\opt\customer\env and other locations to the FoxCTS location
D:\opt\foxind\cms\clnt\env. Be sure to make the necessary changes to the environment files
located in the FoxCTS FoxView environment directory.

Local Group and Password File Not Updated


Use one of the following procedures to resolve problems with the FoxCTS Client stations local
group and password files not getting updated.
1. Verify that the FoxCTS RcpRshSvc Service is running. If this service is not running,
attempt to start it. If startup fails, contact Global Customer Support for assistance.
2. Verify that the FoxCTS Server’s d:/opt/foxind/cms/data folder has a
<letterbug>.installed file for each station that has been installed with the FoxCTS
Client module. If any files are missing, just copy an existing <letterbug>.installed file
and rename it with the letterbug of the FoxCTS Client station.
3. Push the updates from the FoxCTS Server station.
a. Start a DOS Command window and start a NutCracker shell.
b. Run the script d:/opt/foxind/cms/srvr/scripts/do_UpdatePasswd <lBug>. Where
<lBug> is the name of the FoxCTS Client station.
c. Verify the d:/opt/foxind/cms/clnt/login/etc/group and passwd files have been
updated on the FoxCTS Client station.
d. If the files have not been updated, check the generated log file,
d:/opt/foxind/cms/srvr/logs/do_UpdatePasswd, for error messages.
♦ Correct any problems reported in the log file.
♦ Re-run the d:/opt/foxind/cms/srvr/scripts/do_UpdatePasswd script.
4. Pull the updates from the FoxCTS Server station.
a. Start a DOS Command window and start a NutCracker shell.
b. Run the script d:/opt/foxind/cms/clnt/login/bin/run_UpdatePasswd.sh.
c. Verify the d:/opt/foxind/cms/clnt/login/etc/group and passwd files have been
updated.
d. If the files have not been updated, check the generated log file,
d:/opt/foxind/cms/clnt/logs/run_UpdatePasswd.sh, for error messages.
♦ Correct any problems reported in the log file.
♦ Re-run the d:/opt/foxind/cms/clnt/login/bin/run_UpdatePasswd.sh script.

110
8. Troubleshooting B0193VV – Rev K

Database Reporting Problems


ICC Control Station Changes not Recorded
At the FoxCTS Server, check the D:\opt\foxind\cms\srvr\logs\cmslog for two things.
1. If no checkpoint message for the Control Station exist:
♦ Check that the Control Station is assigned to a System Monitor.
♦ If the Control Station is assigned to a System Monitor, confirm that the System
Monitor is not set to inhibit alarms from the station.
♦ If the System Monitor is not set to inhibit alarms, confirm that the FoxCTS
Sysmon package was installed at the CP’s Sysmon host and is properly running,
and is sending it’s information to the appropriate location. This can be done by:
♦ Use the D:\opt\foxind\cms\sysmon\bin\show_hist tool. The result returned
from show_hist should be the name assigned during the FoxCTS SysMon
installation (SMMRxx), rather than the historian name.
♦ Use the Windows Task Manager to verify that the smonMsgRelay.exe
process is running on the Sysmon host.
♦ Use Windows Services to stop the FoxCTS Sysmon service.
♦ Use the FoxCTS modappreg utility to set the debug switch (+D6) to verify
the receipt of the checkpoint message from the workstation. See “Debug Log-
ging” on page 108 for details.
♦ Use Windows Services to restart the FoxCTS Sysmon Service.
2. If there is no evidence of change information being inserted into the FoxCTS change
database:
♦ Check the FoxCTS Server’s D:\opt\foxind\cms\data\CHKPT directory for a file
with the format <CP><datetime>.data.xml. This is the Control Station change
information. If the file exists, then wait about 5 minutes and this information will
be inserted to the FoxCTS change database.
♦ If no such data file exists, check the Control Station host machine to make sure
the FoxCTS ICCDRVR module was installed on the Control Station host and is
properly running, and sending it’s information to the FoxCTS Server. This can be
done:
♦ Using the Windows Task Manager, verify that the iccdrvr.exe service is run-
ning on the Control Station host.
♦ Check the D:\opt\foxind\cms\data directory for a file with the format
<CP><datetime>.data.xml.
♦ If no such data file exists, the FoxCTS ICCDRVR module may have been
configured incorrectly. Check the following log files:
♦ D:\opt\foxind\cms\iccdrvr\logs\chk4_cio_chgs (Check for error messages.)
♦ D:\opt\foxind\cms\iccdrvr\cms_profile (Make sure that the value of
CMS_HOST and CMS_HOSTIPADDR are correct.

111
B0193VV – Rev K 8. Troubleshooting

File Tracking Changes Not Recorded


Check to make sure that the following directory name, file name, and drive restrictions have been
met.
♦ FoxCTS file tracking client workstations running a Windows operating system can
only track directories and files on their local hard drives.
♦ The use of wild cards in the file names is not supported.
♦ Directory name or file name does not contain any spaces.
If file tracking changes are not recorded in the change database, check the FoxCTS Server
machine:
1. Check the D:\opt\foxind\cms\data\FT directory for any files from the File
Tracking Clients. This is the file change information. If files exist, then wait about 5
minutes and this information will be inserted into the FoxCTS change database.
2. Verify that the FoxCTS Server was properly configured to track files for the File
Tracking Client station of interest, see “Files to Track” on page 66.
3. Verify that the FoxCTS Server attempted to send the tracking list to the correct
FoxCTS Client station. Look at the FoxCTS Server’s
D:\opt\foxind\cms\srvr\logs\build_poll_list log file for any errors.
If the FoxCTS Server checks out, then examine the FoxCTS Client stations:
1. Verify that the FoxCTS Client station has received its list of files to be tracked by
checking the D:\opt\foxind\cms\data directory for files with the name
<LBUG>.pollList or pollList.
2. Verify that the FoxCTS Client station is in the process of tracking the listed files.
♦ Check the d:\opt\foxind\cms\clnt\logs directory for current files with names
prefixed by xferFile.
♦ Do the xferFile.* logs indicate that the tracked files were deleted? (Deletion could
occur because the file name was misspelled or the file name does not exist.)
3. Run the file tracking services in debug.
♦ Use Windows Services to stop the FoxCTS Client FT Service.
♦ Use the FoxCTS modappreg Utility to set the debug switch (+D6) to verify that
file changes are being tracked. See “Debug Logging” on page 108 for details.
♦ Use Windows Services to restart the FoxCTS Client FT service.
♦ From the FoxCTS Configurator, rebuild the file tracking list for this FoxCTS File
Tracking Client station.
♦ At the FoxCTS Client, examine the d:\opt\foxind\cms\clnt\debug\cmspoll
debug log file.

112
8. Troubleshooting B0193VV – Rev K

Changes Not Recorded from FoxSelect or FoxView


If the changes made using FoxSelect or FoxView are not being recorded.
♦ The FoxCTS package does not directly track changes made using FoxSelect or
FoxView. The FoxCTS package does provide an Enhanced Operator Action Journal
(EOAJ) message. This service takes the OAJ messages normally generated by these
applications and adds user information to the standard Operator Action Journal
message. This enhanced message is then recorded in an AIM*Historian instance. If
the problem is that EOAJ messages are not being recorded, please see the information
that follows.

Enhanced Operator Action Journal Messages Not Recorded


If the EOAJ messages are not being recorded, the following items need to be checked:
♦ Is the Operator Action Journal (OAJ) turned on for the workstation.
This can be checked by using the OAJ configurator.
♦ Is the OAJ message targeted to the FoxCTS oajMsgRelay program - named OAJxxx
where xxx is a number from 000 to 999?
This name can be checked by examining the Historian destination in the OAJ
configurator display.
♦ Is the oajMsgRelay program running?
♦ Use the Windows Task Manager to verify that the oajMsgRelay.exe process is run-
ning.
♦ Is the FoxCTS OAJ Host module, oajAimRelay, installed and running on the
AIM*Historian host?
♦ Use the Windows Task Manager to verify that the oajAimRelay.exe service is run-
ning on the AIM*Historian host.
♦ Is the AIM*Historian instance active?
Use the AIM*Historian Manager application to check the instance.
♦ Is the AIM*Historian instance configured to store FoxCTS EOAJ messages
(Group=FoxCTS; MsgType=OAJMSG)?
Check the configuration by using histspy to view the message configuration database.
♦ Is the tool you are using to view the messages properly configured?
Check the configuration by using histspy to view the message database. If histspy
shows the messages, the problem is in the tool.

Performance Issues
Control Network Loading Issues
The FoxCTS software, by default, will attempt to communicate via the primary (Control
Network) Ethernet port. If after the installation of the FoxCTS software the Control Network
traffic appears to be too heavy it is possible to shift some of the FoxCTS communications across
the second Ethernet port. The following explains some alternate FoxCTS communication
configurations.

113
B0193VV – Rev K 8. Troubleshooting

User Interface Communications


A FoxCTS Client can be forced to send all user-related requests to the FoxCTS Server via the
second Ethernet port by editing the D:\opt\foxind\cms\clnt\cms_profile file.
Original line:
CMSHOSTIPADDR=‘GetIPADDR $CMS_HOST‘
Replace with:
CMSHOSTIPADDR=<FoxCTS Server’s 2nd Ethernet port address>

OAJ Communications
A FoxCTS Client can be forced to send all OAJ message to the AIM* Server via the second
Ethernet port. This can be done as follows:
1. During the installation of the FoxCTS Client enter the IP address of the
AIM*Historian Server’s plant information network address.
2. If the FoxCTS Client is already installed, edit the following line in the
D:\opt\foxind\cms\clnt\cms_profile file.
Original line:
AIMHOSTIPADDR=<AIM* Server’s ControlNetwork port address>
Replace with:
AIMHOSTIPADDR=<AIM* Server’s 2nd Ethernet port address>

File Tracking
The FoxCTS Server can be forced to send all file tracking related requests to the FoxCTS Client
via the second Ethernet port address. This can be done the following ways.
1. During the installation of the FoxCTS Client enter the IP address of the FoxCTS
Server’s second Ethernet port address.
2. If the FoxCTS Client is already installed edit the following line in the
D:\opt\foxind\cms\clnt\cms_profile file.
Original line:
CMSFTHOSTIPADDR=‘GetIPADDR $CMS_FTHOST‘
Replace with:
CMSFTHOSTIPADDR=<FoxCTS Server’s ControlNetwork port address>

ICC Driver Communication


The FoxCTS ICC Driver can be forced to send all CIO Change related data to the FoxCTS
Server via the second Ethernet port by editing the following line in the
D:\opt\foxind\cms\iccdrvr\cms_profile file.
Original line:
CMSHOSTIPADDR=‘GetIPADDR $CMS_HOST‘
Replace with:
CMSHOSTIPADDR=<FoxCTS Server’s 2nd Ethernet port address>

114
8. Troubleshooting B0193VV – Rev K

System Performance
Since file tracking can slow down the performance of an workstation, this sections deals with ways
to improve system performance after file tracking has been implemented.

Slow Down File Tracking


The following techniques can be used to slow down file tracking, thus improving performance.
1. To slow down the FoxCTS Server’s processing of the tracked files from every five
minutes, use the FoxCTS modappreg Utility to change the StartTimexx value for the
Schedule Task, Taskxx, with the name d:\opt\foxind\cms\srvr\script\chk4_FT_data,
to some value greater than it current value.
2. The FoxCTS Server script, d:\opt\foxind\cms\srvr\script\do_chk4_FT_Data,
processes all the tracked file information in the d:\opt\foxind\cms\data\ft directory,
each time it runs. To slow this process down, edit the do_chk4_FT_Data script to
wait longer between successive files processed. Edit the original line
TIME_IN_SECS=2 with a larger value.

Slow Down CP Change Information Processing


1. The FoxCTS Server scheduled task, chk4_dev_data current runts every five minutes
to look for new CP change data from the CP Hosts. Use the FoxCTS modappreg
Utility to change the StartTimexx value for the Schedule Task, Taskxx, with the name
d:\opt\foxind\cms\srvr\script\chk4_dev_data, to some value greater than it current
value.
♦ The FoxCTS Server script, d:\opt\foxind\cms\srvr\script\do_chk4_cio_chgs,
processes all the CP change information. To slow this process down, edit the
do_chk4_cio_chgs script to wait longer between successive files processed. Edit the
original line TIME_IN_SECS=10 with a larger value.

FoxCTS Product Removal


If there are any problems uninstalling the FoxCTS Client module, the following tar files, were
created during the installation, in an effort to help return the machine back to a pre-FoxCTS
condition. These files are only created the first time the FoxCTS Client module is installed.
♦ /opt/Custom_cts.tar - Restores the /opt/custom folder.
♦ /opt/CustomerEnv_cts.tar - Restores the /opt/customer folder.
♦ /opt/fox/ciocfg/api_cts.tar - Restores the /opt/fox/ciocfg/api folder.
♦ /opt/fox/env_cts.tar - Restores the /opt/fox/env folder.
♦ /opt/fox/wp/FoxView_cts.tar - Restores the /opt/fox/wp/FoxView folder.
♦ /usr/fox/bin_cts.tar - Restores the /usr/fox/bin folder.
♦ /usr/fox/config_cts.tar - Restores the /usr/fox/config folder.
♦ /usr/fox/soft_cts.tar - Restores the /usr/fox/soft folder.
♦ /usr/fox/sys_cts.tar - Restores the /usr/fox/sys folder.
♦ /usr/fox/wp/bin_cts.tar - Restores the /usr/fox/wp/bin folder.
♦ /usr/fox/customer/config_cts.tar - Restores the /usr/fox/customer/config folder.

115
B0193VV – Rev K 8. Troubleshooting

♦ /usr/fox/sysmgm/sysmon_cts.tar - Restores the /usr/fox/sysmgm/sysmon folder.

FoxCTS Messages
This section describes the common FoxCTS messages that may be encountered during normal
usage of the software.

Login
The following is a list of the FoxCTS Client and PACTware login messages.
BAD INITIAL ENVIRONMENT
The home environment for this FoxCTS user does not exist in this workstations
D:\opt\foxind\cms\clnt\env directory.

INVALID CHARACTER IN JOB


The FoxCTS user has entered an invalid character in the dialog box Job No. field. See “Login” on
page 89 for the list of invalid characters and try again.

ATTEMPTING LOGIN
Attempting to verify the user’s name, password, and suitability to log in at this station.

LOGIN SUCCESSFUL
User login was successful.

ATTEMPTING TO CHG ENV


Attempting to change to the default display manager environment configured for this FoxCTS
user, see “User Types” on page 73 for more information regarding FoxCTS user types.

SRVR DOWN - LOGIN VERIFIED LOCALLY


The FoxCTS Server is not responding to login attempts. A simple verification (valid
user/password only) will be performed locally at this FoxCTS Client station so that the user can
gain access to FoxView menus and tools. In this event no login information is recorded in the
FoxCTS change database. During a local login session file tracking and CP change information
will be recorded as soon as communications to the FoxCTS Server is re-established but CP change
information will be recorded as the user UNKNOWN. For this reason the FoxCTS user must re-
login to the FoxCTS Client station just as soon as the FoxCTS Server is available.

FOXCTS LOGIN INVALID


The Microsoft domain login name being used does not exist in the FoxCTS domain database.
The FoxCTS Administrator must create a matching user account via the FoxCTS Configurator,
see “User Accounts” on page 77 for more information regarding FoxCTS users.

INVALID USER NAME


Cannot find the provided user name in the FoxCTS domain database, see “User Accounts” on
page 77 for more information regarding FoxCTS users.

116
8. Troubleshooting B0193VV – Rev K

INVALID USER/UNAUTHORIZED ACCESS


The FoxCTS user is not allowed access to this workstation based on the configuration
information entered in the FoxCTS domain database. Refer to “User Accounts” on page 77 for
more information regarding user configuration.

User Reconfirmation
The following is a list of the FoxCTS user reconfirmation messages. Many of the standard login
and password messages will apply to user reconfirmation.
VALIDATION SUCCESSFUL
Reconfirmation was successful. The action requested when reconfirmation was successfully
completed and will be carried out now.

INVALID USER NAME


When performing a single or double user reconfirmation, the FoxCTS login name provided must
have a valid, active FoxCTS user account with correctly defined process area/ access to the
machine where the reconfirmation is taking place.

INVALID SUPV NAME


When performing a double user reconfirmation, the supervisor name provided must be a valid,
active FoxCTS user account with correctly defined process area/ access to the machine where the
reconfirmation is taking place.

INVALID USER TYPE


When performing a user reconfirmation in which the user type requirements is specified (via the
command line option [-fut <userType1>]), the FoxCTS user name provided must have the same
user type as the one specified in the command line. See the section “User Reconfirmation” on
page 93 for details.

INVALID USER TYPE (SUPV)


When performing a user reconfirmation in which the user type requirement is specified (via the
command line option [-sut <userType1>]), the FoxCTS user name for the supervisor provided
must have the same user type as the one specified in the command line. See the section “User
Reconfirmation” on page 93 for details.

USER & SUPV NAMES must BE UNIQUE


When performing a double user reconfirmation the FoxCTS user name and supervisor FoxCTS
user name cannot be the same.

NOT AUTHORIZED TO USE THIS AW/WP/ENV


The FoxCTS user name entered during the reconfirmation is not configured for access to the
machine he is trying to perform the reconfirmation on or he is not allowed access to the current
environment that is active at the display manager. See the section “User Reconfirmation” on
page 93 for details.

117
B0193VV – Rev K 8. Troubleshooting

FoxCTS PACTware Module Error Messages


The following is a list of error messages that can occur when using PACTware with the FoxCTS
PACTware module installed.
After connecting to the device, please perform load from device to estab-
lish a baseline file for comparison with subsequent download FoxCTS Audit
Trail.
This may occur when a new field device is added.

No device parameter change detected.


This occurs when a “Save to Device” is requested and no changes have been detected. No data will
be sent to the FoxCTS Server.

No device baseline exists; changes NOT reported to FoxCTS.


This occurs when a “Save to Device” is requested and no baseline has been created. No change
data will be sent to the FoxCTS Server until an upload from the device occurs.

Error comparing device parameter files; consult exception log.


This occurs when a “Save to Device” is requested. There was an error comparing the changes
made to the previous changes. No data will be sent to the FoxCTS Server.

118
9. FoxCTS Change Database
This chapter provides the FoxCTS administrator information about the FoxCTS Change
Database Server.

Overview
The FoxCTS product uses the PAS Integrity software for reporting and historical data storage
purposes. The FoxCTS product ships with the minimum Integrity software and license available
and includes the Integrity CTS Asset Model necessary to support the FoxCTS product. The PAS
company offers variations of the Integrity software that can be used in conjunction with the
Integrity CTS Asset Model.
Integrity software documents that might be helpful are located on the FoxCTS media in the
Integrity_FoxCTS\Windows\Documents folder.

Limitations
The following list contains the known limitations of the Integrity software.
♦ The Integrity software must be installed on the FoxCTS Server.
♦ The maximum database size when using the Integrity software is 10 GB. The size
limitation can be increased by upgrading the Integrity software. Contact PAS, Inc. at
sales@pas.com for details.
♦ Currently there is no database size monitoring feature available.
♦ Currently there is no database archive or restore features available.
♦ Currently there is no report printing mechanism available.
♦ Currently sequence logic and ladder logic is not available for viewing until a second
change has been recorded.
♦ Currently when a compound or block is deleted from a CP, only the last recorded
change history information is available. The history of the compound or block is no
longer viewable from the Integrity software.

119
B0193VV – Rev K 9. FoxCTS Change Database

Installation
This section provides installation instructions for the FoxCTS Change Database.

Integrity Software
The PAS company offers variations of the Integrity software that can be used in conjunction with
the Integrity CTS Asset Model. If a previous version of the Integrity software is already installed
on the FoxCTS Server, contact PAS, Inc. at sales@pas.com for CTS Asset Model compatibility
and installation instructions.
The following installation instructions are for IntegrityWin v4.2.
1. Using the FoxCTS for Windows media, start the installation process by selecting
E:\Integrity_FoxCTS\Integrity_v4.2.0.03_Setup.exe file.
2. At the Destination Folder window, change the destination folder to
D:\Program Files\PAS\Integrity\IntegrityWin.
3. At the Custom Setup window, select to install the IntegrityWin option and unselect
the IntegrityWeb option.

Figure 9-1. IntegrityWin

4. When the installation completes, copy the


E:\Integrity_FoxCTS\Invensys CTS.iam file to
D:\Program Files\PAS\Integrity\IntegrityWin\DataCollector\Asset
models\Invensys CTS.

120
9. FoxCTS Change Database B0193VV – Rev K

Integrity Configuration
Once the Integrity software is installed it requires configuration. Follow the procedures in this
section to configure the Integrity software for use with the FoxCTS product.

Licensing
If the Integrity CE software was installed per the instructions found in this manual, then select
the License Type of Integrity CM Permanent License when filling out the PAS license request
form.
1. Fill out the PAS Invensys Integrity License Request Form that is located on the
FoxCTS for Windows CD-ROM under the Integrity_FoxCTS folder.
2. Once the PAS license request form is completed, send it to RapidSupport@PAS.com
for processing. It will take approximately 24 hours for PAS to process the license
request form.
3. Once PAS has processed the license request form, start the Integrity software
(IntegrityCE) and the Product Licensing dialog box appears.
4. Validate the license via telephone by selecting the Begin button (Figure 9-2).

NOTE
The cost of one Integrity CM license, that is required for the FoxCTS Change
Database Server, is included with the purchase of the FoxCTS product.

Figure 9-2. Integrity Licensing

121
B0193VV – Rev K 9. FoxCTS Change Database

Database Configuration
Once the Integrity product has been licensed follow these steps to configure a new database.
1. From the Integrity Setup dialog box select Database (Figure 9-3).
2. Select the Yes button to create a new database.
3. Use the default location.
4. Use one of the following name for the SQL Server Computer name field:
a. <YourPCname>\SQLEXPRESS (SQL Server 2005 Express installations.)
b. <YourPCname> (SQL Server 2008 Express and other SQL Server installations.)
c. <YourPCname>\InFusionSecurity (SQL Server installed with Foxboro Evo
Control Software.)
5. Name the database: CTS
6. Select the Windows Authentication mode radio button.
7. Leave both Additional Configuration check boxes unchecked.
8. Select Save.

Figure 9-3. Integrity Database Configuration

122
9. FoxCTS Change Database B0193VV – Rev K

Asset Models Import


Once the database has been configured follow these steps to import the FoxCTS Asset model.
1. From the Integrity Setup dialog box select Asset models (Figure 9-4).
2. Browse the D:\Program Files\PAS\Integrity\IntegrityWin\DataCollec-
tor\Asset Models folder.
3. From the Available asset mode list select Invensys CTS and use the right-arrow to
move it to the Asset model(s) to be imported list.
4. Select the Import button.

Figure 9-4. Integrity Asset Models Import

123
B0193VV – Rev K 9. FoxCTS Change Database

Asset Creation
Once the FoxCTS asset model has been imported the following steps will create a FoxCTS asset.
1. From the Integrity Setup dialog box select Assets (Figure 9-5).
2. Select the Add button.
3. At the Add Asset Window, enter FoxCTS for the Asset Name and select the Asset
model Invensys CTS.
4. Use D:\opt\foxind\cms\srvr\data\pas for the Import folder name.
5. Select the Save button.

Figure 9-5. Integrity Asset Creation

124
9. FoxCTS Change Database B0193VV – Rev K

Data Collector Service


Once the asset model has been configured follow these steps to start the Data Collector Service.
1. From the Integrity Setup dialog box select Data Collector service (Figure 9-6).
2. Select the Start button to start the Integrity DataCollector2 service.
3. Once the service Status is running select the Save button.

Figure 9-6. Integrity Data Collector Service

125
B0193VV – Rev K 9. FoxCTS Change Database

Import Schedule
Once the Data Collector service is started the import schedule must be set. This schedule will
control how often data from the FoxCTS Server is imported to the Integrity database.
1. From the Integrity Setup dialog box select Import schedule.
2. From the Schedule Imports and Monitor Process dialog box select the Add button.
3. Select the General tab (Figure 9-7).
a. Enter a Schedule Name, for example SCHEDULE1.
b. Verify the Server run on, is the name of this PC.
c. Check the Enable button.

Figure 9-7. Import Schedule - General Tab

126
9. FoxCTS Change Database B0193VV – Rev K

4. Select the Sequence tab (Figure 9-8).


a. Select the FoxCTS asset from the Asset list.
b. Highlight All from the Definitions list and select the right-arrow.

Figure 9-8. Import Schedule - Sequence Tab

127
B0193VV – Rev K 9. FoxCTS Change Database

5. Select the Schedule tab (Figure 9-9).


a. Change the Perform schedule to Hourly. This setting controls how often the
FoxCTS Server data is imported to the Integrity database.
b. Select the OK button.

Figure 9-9. Import Schedule - Schedule Tab

128
9. FoxCTS Change Database B0193VV – Rev K

Once the schedule task is added is will appear in the Schedule Imports and Monitor Process list,
Figure 9-10.

Figure 9-10. Import Schedule - Scheduled Items

Reports
Once the Integrity Server has received and processed change data information from the FoxCTS
Server station and is processed the recorded data can be viewed by using the Integrity software by
using the following Asset Navigator tools:
♦ Asset Explorer - Organizes FoxCTS change records by Activities, Block Types,
Compounds, Field Devices, Tracked Files, and Users
♦ Change Tracking - Organizes FoxCTS change records by change events.

Asset Explorer
Use the Integrity Navigator Asset Explorer tool to view FoxCTS change records grouped by
Activities, Block Types, Compounds, Field Devices, Tracked Files, and Users.
1. From the Integrity Navigator select the Asset Explorer.
2. From the Asset Explorer dialog box select the FoxCTS Asset (Figure 9-11).
3. Select the required item from the FoxCTS asset list. In the example the 70A_TEST
compound was selected and the compound contents is displayed.

129
B0193VV – Rev K 9. FoxCTS Change Database

Figure 9-11. Asset Explorer - FoxCTS

a. The Properties tab displays the current parameters.


b. The Modification tab displays the recorded changes.
c. The File MOC tab can compare recorded sequence logic changes for individual
sequence blocks, and compare recorded ladder logic changes for individual PLB
blocks.
d. The File Compare tab can compare recorded file changes for individual tracked
files.
e. The Notes tab allows notes to be created.

Change Tracking
Use the Integrity Navigator Change Tracking tool to view change records by change events.
1. From the Integrity Navigator select the Change Tracking.
2. From the Change Tracking dialog box select the FoxCTS Asset (Figure 9-12).
3. Select an Import event or select a Date range. (When using a Date range be sure to
click the Update button after the to and from dates have been selected.) In the
example that follows a Date range was used, the BLOCK object type selected, and the
compound:block 5B_TEST:5B_FRENCH was selected. At the right a comparison of
the sequence logic files associated with the block is displayed.

130
9. FoxCTS Change Database B0193VV – Rev K

Figure 9-12. Change Tracking - FoxCTS

4. Once a import event or date range has been selected use the Additions and
Deletions or Modifications tab to select the change record for review.
5. Once the change record is identified:
a. The Properties tab displays the current parameters.
b. The Modifications tab displays the recorded changes.
c. The File MOC tab can compare recorded sequence logic and ladder logic changes.
(This tab is only available for blocks containing sequence and ladder logic.)
d. The File Compare tab can compare recorded file changes for individual tracked
files.
e. The Notes tab allows notes to be created for the changes.

131
B0193VV – Rev K 9. FoxCTS Change Database

132
Appendix A. Worksheets
This appendix provides worksheets to assist with the planning and configuring the FoxCTS
product.
The following worksheets are designed to assist the FoxCTS administrator in planning and
configuring the FoxCTS Domain. Proactive planning will save time and frustration during the
installation and configuration of the FoxCTS modules.
The FoxCTS Domain Installation worksheets will be used during the FoxCTS module
installation process.

FoxCTS Domain Installation Worksheets


The following worksheets identify the information required during the installation of the
FoxCTS modules.

Module Overview Worksheet


This worksheet will help the FoxCTS administrator identify what FoxCTS modules will be
installed on each workstation.

FoxCTS
FoxCTS FoxCTS FoxCTS FoxCTS ICC FoxCTS
Letterbug Server Client OAJ Host SysMon Driver PACTware

133
B0193VV – Rev K Appendix A. Worksheets

Letterbug - Letterbug name of the stations that requires installation of a FoxCTS module.
FoxCTS Server - This station will act as a FoxCTS Server.
FoxCTS Client - This station will act as a FoxCTS Client.
FoxCTS OAJ Host - This station will act as a FoxCTS OAJ Host.
FoxCTS SysMon - This station will require FoxCTS SysMon.
FoxCTS ICCDRVR - This station will require FoxCTS ICC Driver.
FoxCTS PACTware - This station will require FoxCTS PACTware.

Server Module Worksheet


The FoxCTS Server is responsible for collecting information from stations on a control
network. This worksheet identifies the information that is required during the installation of the
FoxCTS Server module.

FoxCTS Server Letterbug Name

134
Appendix A. Worksheets B0193VV – Rev K

OAJ Host Module Worksheet


This FoxCTS module will add FoxCTS user information to standard OAJ messages. The FoxCTS
OAJ Host module requires an AIM*Historian instance prior to installation.

FoxCTS OAJ Host AIM*Historian Server AIM*Historian


Letterbug Name (Letterbug) Name Instance Name

FoxCTS OAJ Host Letterbug Name - Letterbug name of the workstations that is to be the Fox-
CTS OAJ Host.
AIM*Historian Server (Letterbug) Name - Letterbug name of the workstations that hosts the
AIM*Historian Instance.
AIM*Historian Instance Name - Identify the instance name of the AIM*Historian host.

135
B0193VV – Rev K Appendix A. Worksheets

Client Module Worksheet


Users on this station will be forced to log in with passwords that will control their available
environments. Users Login/Logout activities, ICC activities and file editing will be recorded on
the FoxCTS Server.

AIM* FoxCTS
FoxCTS FoxCTS FoxCTS Historian AIM* OAJ
Client Server FoxCTS OAJ Letterbug Historian Message Alternate
Letterbug Letterbug Server IP Custom Enhanced Name and Instance Relay Dest.
Name Name Address FoxView Path Messaging IP Address Name Name Name

FoxCTS Client Letterbug Name - Letterbug name of the workstations that is to be a FoxCTS
Client.
FoxCTS Server Letterbug Name - FoxCTS Server’s Letterbug name that will be hosting this
station.
FoxCTS Server IP Address - FoxCTS Server’s IP address.
Custom FoxView Path - (OPTIONAL) Specify a custom FoxView environment folder other
than /opt/fox/env, /opt/custom or /opt/customer/env.
OAJ Enhanced Messaging - (Optional) FoxCTS OAJ enhanced messaging to be used at this
FoxCTS Client station. The following columns are only used if OAJ enhanced messaging is
selected.
AIM*Historian Letterbug Name and IP Address - (Optional) AIM* Historian’s
Letterbug and IP Address.
AIM*Historian Instance Name - (Optional) AIM* Historian’s instance name.
FoxCTS OAJ Message Relay Name - (OPTIONAL) Select a unique FoxCTS OAJ
message relay name for this workstation. For example, OAJ001.
Alternate Dest. Name - (Optional) Alternate destination for non-OAJ messages, e.g.
RBatch.

136
Appendix A. Worksheets B0193VV – Rev K

SysMon Module Worksheet


This FoxCTS module will intercept Control Configurator Checkpoint messages and forward
them to the FoxCTS Server.

NOTE
The FoxCTS SysMon module should be installed on the System Monitor host for
every system monitor that is used for monitoring ICC controlled control stations in
the FoxCTS Servers domain.

System Monitor Message


FoxCTS SysMon FoxCTS Server FoxCTS SMMR Destination (Historian
Letterbug Name Letterbug Name Name Name)

FoxCTS SysMon Letterbug Name - Letterbug name of the workstations that requires the Fox-
CTS Sysmon module.
FoxCTS Server Letterbug Name - FoxCTS Server’s Letterbug name that will be hosting this
station.
FoxCTS SMMR Name - Select an unique FoxCTS SMMR name for this workstation.
For example, SMMR01.
System Monitor Message Destination - Historian name.

137
B0193VV – Rev K Appendix A. Worksheets

ICC Driver Module Worksheet


The FoxCTS ICC Driver module detects the running of the iccdrvr process.

NOTE
The FoxCTS ICCDRVR module should be installed on the control station boot
host for every ICC controlled control station in the FoxCTS domain.

FoxCTS ICC Driver FoxCTS Server Letterbug


Letterbug Name Name FoxCTS Server IP Address

FoxCTS ICC Driver Letterbug Name - Letterbug name of the workstations that requires the
FoxCTS ICC Driver module.
FoxCTS Server Letterbug Name - FoxCTS Server’s Letterbug name that will be hosting this
station.
FoxCTS Server IP Address - FoxCTS Server’s IP address.

138
Appendix A. Worksheets B0193VV – Rev K

PACTware Module Worksheet


The FoxCTS PACTware module is installed only on FoxCTS Clients stations where PACTware
change data is to be collected.

NOTE
The FoxCTS PACTware module must be installed on workstations where
PACTware change data is to be collected.

FoxCTS PACTware FoxCTS Server FoxCTS Server PACTware Baseline


Letterbug Name Letterbug Name IP Address Installed Completed

FoxCTS PACTware Letterbug Name - Letterbug name of the workstations that requires the
FoxCTS PACTware module.
FoxCTS Server Letterbug Name - FoxCTS Server’s Letterbug name that will be hosting this
station.
FoxCTS Server IP Address - FoxCTS Server’s IP address.
PACTware Installed - PACTware software installed.
FoxCTS Client Installed - FoxCTS Client module installed.

139
B0193VV – Rev K Appendix A. Worksheets

FoxCTS Domain Configuration Worksheets


The following worksheets identify the information required during the configuration of the
FoxCTS Domain.

Process Area Worksheet


The FoxCTS Process Area worksheet identifies the FoxCTS Process Area(s) in the FoxCTS
Domain. A FoxCTS Process Area is used to logically group equipment so that tracked changes can
be referenced by process areas.

NOTE
At least one Process Area should be assigned in the FoxCTS Domain. If no Process
Area is assigned, then the default Process Area name, UNKNOWN, will be used.

Process Area Name Description

Process Area Name – Name of the FoxCTS Process Area.


Description – Description of the FoxCTS Process Area.

140
Appendix A. Worksheets B0193VV – Rev K

Control Station Worksheet


The FoxCTS Control Station Worksheet identifies the control stations that will be assigned to
this FoxCTS Domain. A control station is any station that can run control blocks. Control sta-
tions include, but are not limited to, CPs, DIs, GWs, AW-Is, Micro-I/A stations, and so on.
After the FoxCTS Domain has been configured, all CPs should establish a baseline. The FoxCTS
Server will then use this baseline to capture changes. The initial CP checkpoints can increase the
FoxCTS change database size quickly and affect system performance. It is a good idea to only
checkpoint one CP at a time. You can examine the log file, D:\opt\foxind\cms\srvr\logs\cmslog,
to determine when each checkpoint has completed.
Even though all CPs listed in the FoxCTS Server’s D:\usr\fox\sp\hldb file are automatically added
during installation the Process Area Name should be assigned and any control stations listed no
longer in service removed.

Control Station Name Process Area Name CP Checkpoint Completed

Control Station Name – Letterbug name of the control station.


Control Station Subtype - This field is generated by FoxCTS configurator and cannot be
changed.
Process Area Name – Assign a process to this control station.
Check Point Completed - Has the baseline been generated for this control station.

141
B0193VV – Rev K Appendix A. Worksheets

Workstations Worksheet
The FoxCTS Workstations Worksheet identifies workstations (FoxCTS Client stations) that will
track FoxCTS user login/logout activity. FoxCTS Client stations will have the FoxCTS Client
module installed.
Even though all workstations listed in the FoxCTS Server’s
D:\usr\fox\customer\hi\dmcfg file are automatically added during installation the Process
Area Name should be assigned and any workstations identified no longer in service removed.

Name Process Area Name

Name – The letterbug name of the FoxCTS Client station.


Process Area Name – Assign a process area to this workstation.

142
Appendix A. Worksheets B0193VV – Rev K

File Tracking Client Worksheet


The FoxCTS File Tracking Client Worksheet identifies the FoxCTS Client stations that will track
files/directories.

Client IP Name or
IP Address
FT Client Letterbug Name (Optional) Process Area Name

FT Client Letterbug Name – Letterbug name of the FoxCTS Client station that will track files.
Client IP Name/IP Address – (Optional) PC Name or IP Address. This entry is only required if
file tracking will be done over a Plant Information Network. If using a PC Name, the PC Name
and IP Address must be correctly entered in the FoxCTS Server’s
c:\windows\system32\drivers\etc\hosts file.
Process Area Name – Assign a process to this FoxCTS FT Client station.

143
B0193VV – Rev K Appendix A. Worksheets

File/Directory Tracking Worksheet


The FoxCTS File/Directory Worksheet identifies the files and directories that will be tracked.

! CAUTION
(1) Be extremely careful when monitoring directories because when tracking a
directory, entries are automatically created for each file and subdirectory beneath it.
(2) Tracking a large number of files can increase the FoxCTS change database size
quickly and will impact the performance on both the FoxCTS Server and FoxCTS
Client stations.
(3) During the period immediately following the file tracking build it is important
to monitor the size of the FoxCTS change database so that the FoxCTS change
database size can be increased if needed.

FT Client
Letterbug File or Poll
Name or Folder Period
PC Name Path Name (Seconds) Monitor

FT Client Letterbug Name or PC – Letterbug name or PC Name (if tracking over the Plant
Information Network) of the FoxCTS Client station.
Path – Complete path to the file or folder to be tracked. Do not forget to include the drive letter.
Only files and folders on the local hard drives can be tracked.
File or Folder Name – Enter the file name or folder name to be tracked. The use of wild cards is
not supported.
Poll Period – Period of time, in seconds, between checking for file changes.
Monitor – Identify if the file or folder is ready to be monitored.

144
Appendix A. Worksheets B0193VV – Rev K

Environments Worksheet
The FoxCTS Environments Worksheet identifies the FoxView environments that are to be used
with the FoxCTS package.

NOTE
After the installation of the FoxCTS Client module, the environment files are
relocated to the D:\opt\foxind\cms\clnt\env folder.

Environment Name

Environment Name - Valid FoxView environment name.

145
B0193VV – Rev K Appendix A. Worksheets

Groups Worksheet
The FoxCTS Groups Worksheet identifies the FoxCTS Group names and associates FoxView
environments to these names.

Group Name Assigned Environment(s)

Group Name – Assign a group name to a collection of FoxView environments.


Assigned Environment(s) – List the FoxView environment(s) that will be assigned to this
FoxCTS Group.

146
Appendix A. Worksheets B0193VV – Rev K

User Types Worksheet


The FoxCTS User Types Worksheet identifies the FoxCTS User Types and assigns a default home
environment and FoxCTS Group(s). These user types will be used when setting up FoxCTS user
accounts and will control the user environment choices.

User Type Name Home Environment Assigned Environment Group(s)

User Type Name – Assigned User Type name to a collection of FoxCTS Groups.
Home Environment – Assigned default home environment for the User Type.
Assigned Environment Group(s) – List the FoxCTS Group(s) that are assigned to this User Type.

147
B0193VV – Rev K Appendix A. Worksheets

User Accounts Worksheet


The FoxCTS User Accounts Worksheet identifies the FoxCTS users and their account
information.

CTS
User First Config
User Last Name, Employee User Login User Process Access
Name M.I. ID Name Type Area WS Lvl

User Last Name – FoxCTS user’s last name.


User First Name, M.I. – FoxCTS user’s first name and middle initial.
Employee ID – FoxCTS user’s employee ID.
User Login Name – FoxCTS user’s login name. (This is the same login name used for the
Microsoft domain.) When accounts are created, the user account status is set to “ACTIVE”.
User Type – Assigns the FoxCTS user type for this user. This User Type will control the user’s
default home environment and control the environments to which this user has access.
Process Area(s) Allowed – Assign the process area(s) to which the user has access.
Workstation(s) Allowed – Assign the workstation(s) to which the user has access.
CTS Configurator Access Lvl – Assign the FoxCTS Configurator access rights, if any, to this user.
The valid entries are Access or None.
User Account Status – On account creation this is automatically set to “ACTIVE”.

148
Appendix B. Command Usage
This appendix describes the usage of commands and scripts associated with the FoxCTS
software.

User Reconfirmation
Command Syntax
The scrnAct command requires four command line argument in addition to the display man-
ager command that is to be run.
The following table shows three usages of the User Reconfirmation facility:
♦ Raising an overlay used for data entry
♦ Raising a detail display
♦ Changing the value of the .MA parameter of a block.

Table B-1. User Reconfirmation Facility

Purpose Configuration Comment


Raise an overlay connected to = P1 CTS_SCRN_TST:PID.SPT ; The overlay would be
CTS_SCRN_TST:PID.SPT /opt/foxind/cms/clnt/login/ configured to allow
while requiring only the opera- bin/scrnAct $GCLBUG changes. The overlay will
tor to login $DMNAME 1 dmcmd ov /opt/fox- not be raised if the login
ind/cms/clnt/ fails.
tests/scrnAct/disp/SCRN_TEST 1
Raise a detail display for /opt/foxind/cms/clnt/login/bin/ The detail display will not
CTS_SCRN_TST scrnAct $GCLBUG $DMNAME 1 appear if the login fails.
dmcmd stddisp
CST_SCRN_TST:PID
Toggle the MA parameter of /opt/foxind/cms/clnt/login/bin/ The MA will not toggle
CTS_SCRN_TST:PID while scrnAct $GCLBUG $DMNAME 2 unless the login is
requiring two logins toggle CTS_SCRN_TST:PID.MA successful.

The usage is as follows:


scrnAct <gcLbug> <DMName> [1 | 2] <dmcmd> [[<dmCmdArg>]...] [-h[elp]]
[-fut <UserType> [-sut <UserType>]]
where:
<gcLbug> - Station Letterbug ($GCLBUG)
<DMName> - FoxView display manager name ($DMNAME)
[1 | 2] - Number of user log-ins required
<dmcmd> - Display manager command to execute

149
B0193VV – Rev K Appendix B. Command Usage

<dmCmdArg> - Arguments passed to the display manager command. Quoted arguments will be
preserved.
[-h] or [-help] - Prints help text to stdout
[-fut <UserType>] - User type of the first signer. <UserType> is a user type defined in the
FoxCTS domain database. Typically the first user type would be Operator.
[-sut <UserType>] - User type of the second signer. <UserType> is a user type defined in the
FoxCTS domain database. Typically the second user type would be Supervisor. The user type of
the second signer can only be specified if the user type of the first is also specified.

NOTE
User type specifications are optional. Without them, any user type can sign in either
slot.

Configuration
Configuration requires attaching a program invocation to a pickable point on a graphic.
Within the Display Configurator, the following is the general procedure:
♦ Open a graphic file.
♦ Select the object to be configured.
♦ Select Display menu.
♦ Select the Select menu item.
♦ Click on the FUNCTION menu.
♦ Select the Execute program menu item.
♦ Type a command in the box. See below for examples.
♦ Select OK.
♦ Save the display.
♦ Exit.
Within the FoxDraw software, the following is the general procedure:
♦ Open a graphic file or create a new one.
♦ Select the object to be configured.
♦ Select the Object menu.
♦ Select Configure Objects menu item.
♦ Select the correct text item in the list under Select Object in the Configure Objects
dialog box.
♦ Select Add icon (a large plus (+) sign).
♦ Select Display Command in the dialog box that appears.
♦ Select OK in the same dialog box.
♦ Type a command in the box labeled Command String in the dialog box that appears.
♦ Type a command in the box. (See below for examples.)
Select OK in the same dialog box.
♦ Save the display and exit.

150
Appendix B. Command Usage B0193VV – Rev K

wrap_all_tools, unwrap_all_tools
Name
wrap_all_tools - Updates FoxView script files in the specified directory so that all run, applic,
and wp_applic commands are logged by the FoxCTS package.
unwrap_all_tools - Undoes the changes made by wrap_all_tools.

Synopsis
wrap_all_tools <directoryName>

Description
The script wrap_all_tools edits the files in the specified directory such that they will log the use of
any run, applic, and wp_applic commands. The logging information consists of a FoxCTS login
record for the starting and exiting of the command invoked by the display manager
commands: run, applic, and wp_applic.

Example
To wrap the configurator scripts located in the D:\usr\fox\config directory, run the following
script from a NutCracker shell window:
D:/opt/foxind/cms/clnt/scripts/wrap_all_tools D:/usr/fox/config
To unwrap the configurator scripts located in D:\usr\fox\config, run the following script from a
NutCracker shell window:
D:/opt/foxind/cms/clnt/scripts/unwrap_all_tools D:/usr/fox/config
The script used to launch the Display Alarm Configurator normally reads:
dmcmd scripts
dmcmd wp_applic $GCLBUG
dmcmd run /usr/fox/wp/bin/admc
The wrapped version reads:
dmcmd script # Updated by FoxCTS installation: Tue May 21 11:23:45 GMT 2010
dmcmd wp_applic /opt/foxind/cms/clnt/login/bin/wrap_tool DispAlarmCfg
$GCLBUG $DMNAME “$USERNM” “$JOBNO” $ENV /usr/fox/wp/bin/listsupp.sh
/usr/fox/wp/bin/listsupp.sh $GCLBUG
dmcmd run /bin/sh /opt/foxind/cms/clnt/login/bin/wrap_tool DispAlarmCfg
$GCLBUG $DMNAME “$USERNM” “$JOBNO” $ENV /usr/fox/wp/bin/admc
/usr/fox/wp/bin/admc $GCLBUG

151
B0193VV – Rev K Appendix B. Command Usage

wrap_tool
Name
wrap_tool - Updates the FoxCTS client with information on the startup and shutdown of a
specified script or program

Synopsis
wrap_tool <ToolName> <gclbug> <dmName> <userNm> <jobNo> <env> <pgmA> <pgmB>
[<arg1>..<argn>]
where
<ToolName> - Generic name of tool, e.g., CIO_Control
<gclbug> - Letterbug for of station running the tool-$GCLBUG
<dmName> - FoxView name of the display manager running the tool-$DMNAME
<userNm> - FoxCTS user running tool- $USERNM
<jobNo> - Job Number - $JOBNO
<env> - Environment or other information - $ENV or text
<pgmA> - Name to be recorded in FoxCTS change database as the program or script run.
<pgmB> - Actual program or script to be run.
<arg1> - First argument for the program to be run.
<argn> - Nth argument for the program to be run.

Description
The script wrap_all_tools invokes a service on the FoxCTS Server so that the startup and the
shutdown of a particular program can be logged in the FoxCTS change database.
In normal operation, wrap_tool will:
♦ Log the startup of the program from the FoxCTS client
♦ Run <pgmB> with its arguments
♦ Log the shutdown of the program from the FoxCTS client
If the <pgmB> argument is set to FoxCTSLoginOnly, no program is run. Rather, a login record
for <pgmA> is recorded.
If the <pgmB> argument is set to FoxCTSLogoutOnly, no program is run. Rather, a logout
record for <pgmA> is recorded.
These two arguments allow login records to be recorded for programs that cannot be actually
wrapped.

152
Appendix B. Command Usage B0193VV – Rev K

Example
The following lines show the textedit program being wrapped.
wrap_tool CustomerTool 1AW70C 1DM70C jsmith N/A “my text” /usr/open-
win/bin/textedit
/usr/openwin/bin/textedit
The use of the FoxCTSLoginOnly and FoxCTSLogoutOnly keywords is demonstrated by the
wrapping of the Restart_DM item. The original script read:
dmcmd script
exit 0
Since there is no way to wrap the display manager command exit 0, the FoxCTS wrap_tool uses
the following to simulate a wrapping.
dmcmd script # Updated by FoxCTS installation: Tue May 21 11:24:16 GMT 2002
dmcmd run /bin/sh /opt/foxind/cms/clnt/login/bin/wrap_tool Restart_DM
$GCLBUG $DMNAME $USERNM $JOBNO $ENV
exit 0 FoxCTSLogin Only
dmcmd run /bin/sh /opt/foxind/cms/clnt/login/bin/wrap_tool Restart_DM
$GCLBUG $DMNAME $USERNM $JOBNO $ENV
exit 0 FoxCTSLogout Only
exit 0

153
B0193VV – Rev K Appendix B. Command Usage

154
Index

.acl 29, 30, 31


.dbr 29, 30
.env 29
.mbr 29

A
Abbreviations xvi
Account Management 5
Acronyms xvi
Admin Utility 88
AIM*Historian 2, 7, 12, 19, 25, 26, 135, 136
Audience xiii

B
Backup 56, 57
baseline 14, 141

C
Change Database xv
Change Tracking 1, 130
cmslog 105, 107, 111
Command Usage 149
unwrap_all_tools 151
User Reconfirmation 149
wrap_all_tools 151
Common Problems 109
Configuration
Integrity 121
Control Configurator 15
Control Stations 14, 61
CP Initialization 16
CS Subtype 61

D
Daylight Savings Time 14
Default User Account 87
Definitions xv
destact.cfg 104
dmcfg 19, 28, 31
Domain Configuration 53, 54, 59
Control Stations 54, 61
Process Areas 54, 59

155
B0193VV – Rev K Index

Users 69
Workstations 54, 62
Domain Database xv, 54
Backup 54, 57
Maintenance 56
Restore 54, 58
Domain Management 6

E
Enhanced OAJ Messages 11, 98
Environments 28, 106
Add 106
Custom 82
Initial Environment 83
Login 82
Logout 82
Initial 19
Modifications 28

F
Features 1
File Tracking 11, 54
Client Stations 54
Files 55
File Tracking Configuration 64
Activate 67
Build 67
File Tracking Clients 64
Files to Track 66
Foxboro Evo Control Editors 15, 32, 84
FoxCTS xvi, 1
Change Database xv
Client xv
Configurator xv
Domain xv
Domain Database xv
File Tracking Client xv
Groups xvi, 71
Menu 84
Process Area xv, 59
Server xv
Services 104
SysMon
System Commits 103
User Types xvi, 73
FoxCTS Administrator 23
FoxCTS Client 6, 9, 19, 25, 26
FoxCTS Configurator 5, 53, 88

156
Index B0193VV – Rev K

Starting 53
FoxCTS Domain 3, 5
FoxCTS Domain Configuration 53
FoxCTS ICC Driver 13, 21, 25, 26
FoxCTS Login Box 82
FoxCTS Menu 88
Admin 10, 11, 88
Chg_Env 10, 88, 89
Customization 84
Login 9, 10, 88, 89
Logout 10, 88, 91
Passwd_Chg 11, 88, 92
User_Name 11, 88, 92
FoxCTS Messages 116
Login 116
User Reconfirmation 117
FoxCTS OAJ Client 20
FoxCTS OAJ Host 12, 19, 25, 26
FoxCTS PACTware 13, 21
FoxCTS Palette 94
FoxCTS Server 5, 7, 19, 24, 26
FoxCTS Services 50, 51, 104, 105
FoxCTS SysMon 13, 21, 25, 26
FoxCTS.Transfer.Service 105
FoxCTSTransferUtility 105
FoxView 102, 109
Minimized Console Window 109

G
GetSysMonDomains 4
Groups xvi, 71, 72

H
histspy 113
Human Interface 87
FoxCTS Menu
Chg_Env 89
User_Name 92

I
IACC 15, 32, 84
ICC 15, 20
iccdrvr.tsk 21
ICCLaunch xv, 99
Inactivity Timer 81
Installation 35, 120
FoxCTS Change Database Server
39

157
B0193VV – Rev K Index

FoxCTS Client 42
FoxCTS ICC Driver 47
FoxCTS OAJ Host 40
FoxCTS PACTware 49
FoxCTS Server 36, 39
MS SQL Server 36
FoxCTS SysMon 45
Integrity Software 120
Overview 26
Planning 23
Reboot 49
Integrity xv, 39, 121
Asset Creation 124
Asset Explorer 129
Asset Models 123
Change Tracking 130
Configuration 121
Data Collector 125
Database 122
Import Schedule 126
Licensing 121
Limitations 119
Navigator 129, 130
Reports 129

L
Limitations 14
Local Login 6
Logical Name xv
Logical Names 5
FoxCTS ICC Driver 5
FoxCTS Server 5
FoxCTS SMMR 5
OAJ Relay Name 5
Login 10
Box 91
Optional 31
Security Enhanced 90
Standard 89
Login Box
Standard 90
Login Name 77

M
Maintenance 101
McAfee 24
Microsoft SQL Server
Installation 36

158
Index B0193VV – Rev K

modappreg 107, 108, 111


Monitor Status 66

O
OAJ Host 12
oajAimRelay 113
oajMsgRelay 113
Operation 7, 8
Overview 1

P
PACTware 33
Password Controls 75
Days to Reuse 75
Minimum Alphabetic Characters 75
Minimum Length 75
Minimum Lowercase Characters 75
Minimum Numeric Characters 75
Minimum Uppercase Characters 75
Number of Retries 75
Password Aging 75
Password Reuse 75
User Accounts 77
Platform Support 1
Poll Period 66
Preface xiii
Process Area xv, 4, 59
Description 60
Name 59
Process Areas 4
Purpose xiii

Q
Quick Fixes 104
Foxboro Software 104
FoxCTS 104
FoxCTS Client 104
FoxCTS Server 104

R
Reconfirmation
Dual 97
Reinstall 102
Restore 56, 58

159
B0193VV – Rev K Index

S
scrnAct 149
Security Enhancements 2
Services 50, 51, 104, 105, 107
Debug Log 108
Not Starting 107
show_hist 111
Skills 23
SMMR 13
StartDelay 107
System xv
System Commits 103
FoxCTS SysMon 103
System Modifications 16
System Monitor Domain xvi, 4
System Requirements 24

T
Terms xv
Tool Usage Tracking 98
Tool Wrapping 106
Troubleshooting 107, 119
Control Network Loading 113
Control Station Records 111
File Tracking 112, 114
FoxCTS Removal 115
FoxSelect 113
FoxView 113
ICC Driver Communications 114
Menu Items 110
OAJ Communications 114
OAJ Messages 113
Performance 113
Set Point Changes 109
System Performance 115
User Interface Communications 114

U
Uninstall 101
unwrap_all_tools 98, 151
Upgrades 102
Control Core Services 102
FoxCTS 102
FoxView 102
I/A Series 102
User Account 6, 77
User Account Status 78
Active 78
Password Expired 78

160
Index B0193VV – Rev K

Permanently Inactive 78
Temporarily Inactive 78
User Configuration 55, 69
Environments 55, 69
Groups 55, 71
Password Control 55
Password Controls 75
User Accounts 55
User Types 55, 73
User Reconfirmation 93, 149
Configuration 150
Dual 94
Single 93
Test Display 96
User Types xvi, 73

W
Worksheet 27, 133
Control Station 141
Environments 145
File Tracking Client 143
File/Directory Tracking 143, 144
FoxCTS Domain Installation 133
Groups 146
Process Area 140
User Accounts 148
User Types 147
Workstation 142
Workstation xv
FoxCTS Client 62
Workstations
Secured 6
wp51_glbls.all 20
wrap_all_tools 98, 151
wrap_tool 152

161
Invensys Systems, Inc.
10900 Equity Drive
Houston, TX 77041
United States of America
http://www.invensys.com

Global Customer Support


Inside U.S.: 1-866-746-6477
Outside U.S.: 1-508-549-2424
Website: https://support.ips.invensys.com

Vous aimerez peut-être aussi