Operations and Maintenance Guide R3B2 Revision 3.doc.doc

COORDINATED HIGHWAYS ACTION RESPONSE TEAMSTATE HIGHWAY ADMINISTRATION

CHART R3B2 Operations and Maintenance Guide Revision 3

Contract SHA-06-CHARTDocument # W011-UG-001R3Work Order 11, Deliverable 8

December 10, 2008By

CSC

Revision Description Pages Affected Date0 Initial Release All 08/11/20031 Add installation

instructions for CHARTWeb patch

A-25, A-26, A-31. This update also caused renumbering of the sections in Appendix A, and the update of all footers to reflect the new revision number.

10/07/2003

2 Update L&H Real Speak Server Installation for Windows 2000

A-19-A-21. This update also caused renumbering of the pages in Appendix A and the update of all footers to reflect the new revision number

02/15/05

2 Installation of Microsoft Speech API 5.1 SDK and distributable runtime

2 Installation of Nuance Vocalizer, Voice pack, and MSSAPI 5.1 Integration pack

2 Update for additional steps necessary for R1B4.00_patch2 installation

A-5 to A-12 06/16/2005

0 Update for R2B1 Rename document for R2B1Section 2: 1, 2 Section 3: 1, 2, 5-9,12-19, 22, 24, 66-69, 73,

76Section A: A.1.1 all, A.1.2 all, 13,14Deleted - Section A.1.7 (old) - CHART Web

ServiceDeleted – Section A.5 (old) - CHART

Reporting Tool Setup and InstallSection D: 10-12

12/12/2005

CHART Operations & Maintenance Guide R3B2 Revision 3 i 12/10/2008

Revision Description Pages Affected Date0 Update for Oracle 10g,

OEM 10g Grid, R2B2Replaced Section 3.9, A.2, A.3 with new procedures for Oracle 10g and Oracle OEM 10g Grid. Removed A.4 as it is included in the updated sections. Added database upgrade procedures for version 10.1.0.5 in Appendix A.Updated for CHART R2B2 as needed:Section 2: 2.1Section 3: 3.1, 3.5.1, 3.8.1 (Table 3-2, Table 3-3),3.8.4.5, 3.9.9.2 (Table 3-12, Table 3-13)Appendix A: A.1.1, A.1.2Appendix D: Camera Installation Form, Monitor Installation Form

6/30/2006 to8/4/2006

0 Update for R2B3 various 02/16/20071 For R2B3, update

Installation Instructions and substitute version number R2B3.03 where appropriate.

3-8, 3-11, 3-36, 3-45, A-2, A-4 to A-8, A-8 to A-13

5/14/2007

0 Update for R3B1 various 10/15/20071 For R3 B1, update

CHART installation instructions, including additional information on configuring the cluster. Add instructions for installing Nuance Text To Speech on a Windows 2003 server. Update GUI installation instructions. Update instruction for traffic event duplicatio rules. Update CHART version number as required.

3-7, 3-9, 3-10, 3-28 to 3-32, 3-44 to 3-53, A-2 to A-18, A-23 to A-68

1/23/2008

0 Update for R3B2 various 7/11/20081 9/30/2008

CHART Operations & Maintenance Guide R3B2 Revision 3 ii 12/10/2008

Revision Description Pages Affected Date2 Updates for R3B2

Patch 4 – post install steps

Updates for R3B2 Patch 4 – Attention patch steps

A-8, A-9

A-119

11/05/2008

3 Updates for R3B2 Patch 5 – post install steps for server, GUI, and FMS

A-10, A-14, A-15, A-66, A-67 12/10/2008

CHART Operations & Maintenance Guide R3B2 Revision 3 iii 12/10/2008

Table of Contents1 Introduction....................................................................................1-11.1 Purpose............................................................................................................................1-1

1.2 Scope................................................................................................................................1-1

2 Operations and Maintenance Overview.......................................2-12.1 System Overview.............................................................................................................2-1

2.2 Organizational Overview...............................................................................................2-3

2.2.1 System Operation....................................................................................................2-3

2.2.2 System Management...............................................................................................2-3

2.2.3 System Maintenance...............................................................................................2-3

3 Routine Operations........................................................................3-13.1 Operations Overview......................................................................................................3-1

3.2 Operations Principles.....................................................................................................3-6

3.3 Operations Personnel.....................................................................................................3-6

3.4 Maintenance Personnel..................................................................................................3-7

3.5 System Startup and Shutdown......................................................................................3-7

3.5.1 CHART Server System Startup..............................................................................3-8

3.5.2 CHART Web Server System Startup......................................................................3-9

3.5.3 CHART Web Server System Shutdown...............................................................3-10

3.5.4 FMS Server System Startup..................................................................................3-10

3.5.5 FMS Server System Shutdown.............................................................................3-10

3.6 System Backups............................................................................................................3-11

3.7 Operations Log Files....................................................................................................3-12

3.7.1 CHART Service Log Files....................................................................................3-12

3.7.2 CHART Web Service Log Files...........................................................................3-13

3.7.3 Apache Tomcat Log Files.....................................................................................3-13

3.7.4 Internet Information Services Log File.................................................................3-14

3.7.5 Velocity Log File..................................................................................................3-14

3.7.6 DMS Status Logs..................................................................................................3-14

3.7.7 TSS Raw Data Logs..............................................................................................3-14

CHART Operations & Maintenance Guide R3B2 Revision 3 iv 12/10/2008

3.7.8 Device Logs..........................................................................................................3-15

3.7.9 CHART Operations Log.......................................................................................3-15

3.8 System Administration and Configuration................................................................3-15

3.8.1 User Rights............................................................................................................3-15

3.8.2 Properties Files......................................................................................................3-26

3.8.3 CHART Web Service Properties File...................................................................3-27

3.8.4 Event Duplication Properties in System Profile...................................................3-28

3.8.5 FMS Port Configuration.......................................................................................3-32

3.8.6 Device Configuration............................................................................................3-35

3.8.7 Attention Server Users configuration...................................................................3-35

3.9 Database Operations and Maintenance......................................................................3-40

3.9.1 Environment..........................................................................................................3-40

3.9.2 Routine Database Maintenance Operations..........................................................3-45

3.9.3 Databases Maintenance Tasks..............................................................................3-45

3.9.4 Database Backup Set.............................................................................................3-46

3.9.5 Format of Job Identifier on OEM Console...........................................................3-47

3.9.6 CHART Maintenance Tasks.................................................................................3-48

3.9.7 Database Maintenance Task Schedule..................................................................3-50

3.9.8 Attention Database Maintenance (SQL Server) Task Schedule...........................3-50

3.9.9 Manual SQLServer Database Restore from HANSOC-PAGING -> GRNBLTWEB13-50

3.9.10 Open the file and goto end-of-file, Last entry will be the restore_logs. Database Recovery Procedures............................................................................................................3-51

3.9.11 Database Objects...................................................................................................3-56

3.10 Special Operating Instructions....................................................................................3-70

3.10.1 Special Instructions...............................................................................................3-70

3.10.2 Known Problems...................................................................................................3-71

4 Problem Identification and Resolution........................................4-14.1 Problem Identification...................................................................................................4-1

4.1.1 Communications Problems.....................................................................................4-2

4.1.2 Device Problems.....................................................................................................4-2

4.2 Maintenance Overview...................................................................................................4-3

CHART Operations & Maintenance Guide R3B2 Revision 3 v 12/10/2008

4.3 Maintenance Documentation.........................................................................................4-3

Acronym List...............................................................................................1References..................................................................................................1Appendix A – System Installation Instructions.......................................1

Install and configure the OpenSSL toolkit...............................................................................53

Set up a Certificate Authority (CA).........................................................................................54

Create an IIS Certificate...........................................................................................................55

OpenSSL.conf file (for reference only – use in step 5 of configuring the openSSL)..............56

Appendix B – Known Problems................................................................1Appendix C – Server Installation Forms..................................................1Appendix D – Device Installation Forms..................................................1Appendix E – System Status and Error Messages..................................1Appendix F – DMS Special Characters.....................................................1

FiguresFigure 2–1. CHART Release 3 Build 2 Network Architecture....................................................2-2

Figure 3–1. Port Configuration Utility......................................................................................3-33

Figure 3–2. Port Configuration List..........................................................................................3-34

Figure 3–3. ISDN, POTS and Voice Port Configuration..........................................................3-34

TablesTable 3–1. Functional Rights......................................................................................................3-16

Table 3–2. Possible Allocation of Functional Rights.................................................................3-23

Table 3–3. Properties Files.........................................................................................................3-27

Table 3–X1. Event Comparison System Profile Properties Summary.......................................3-28

Table 3–X2. Event Comparison System Profile Properties for Direction..................................3-29

Table 3–X3. Event Comparison System Profile Properties for Features...................................3-30

Table 3–X4. Event Comparison System Profile Properties for Distance...................................3-31

Table 3–4. Client Environment..................................................................................................3-40

Table 3–5. Server Environment..................................................................................................3-41

CHART Operations & Maintenance Guide R3B2 Revision 3 vi 12/10/2008

Table 3–6. CHART Databases...................................................................................................3-41

Table 3–7. CHART Database User IDs......................................................................................3-43

Table 3–8. Oracle Tools.............................................................................................................3-45

Table 3–9. CHART Application Database Tablespaces...........................................................3-56

Table 3–10. CHART Archive Database Tablespaces...............................................................3-57

Table 3–11. CHART Backend Service Static Tables.................................................................3-57

Table 3–12. CHART Backend Service Dynamic Tables...........................................................3-59

Table 3–13. CHART Web Service Static Tables.......................................................................3-60

Table 3–14. CHART Web Service Dynamic Tables..................................................................3-60

Table 3-15. R3B2 Replicated Tables.........................................................................................3-61

Table 3–16. Interim Archive......................................................................................................3-63

Table 3–17. Database User/Role Matrix....................................................................................3-65

Table 3–18. R3B2 Databases Role/Table/Privilege Matrix.......................................................3-65

Table 3–19. Interim Archive Role/Table/Privilege Matrix........................................................3-69

Table A–2. CHART FMS Comm Service Details.........................................................................16

CHART Operations & Maintenance Guide R3B2 Revision 3 vii 12/10/2008

1 Introduction1.1 PurposeThis document provides operations and maintenance personnel with information required for the maintenance and operation of the CHART system. CHART system administrators are intended to use this document as a companion to the CHART User’s Guide.

1.2 ScopeThis document covers system operations and maintenance activities for the MDSHA CHART system. This includes CHART and FMS servers, CHART web servers and web interface. The document consists of four sections. Section 1 contains introductory material. Section 2 presents an overview of the operations and maintenance of the system. Section 3 deals with routine operations and Section 4 with maintenance and problem reporting activities. Appendix A contains installation instructions for the system.

CHART Operations & Maintenance Guide R3B2 Revision 3 1 12/10/2008

2 Operations and Maintenance Overview2.1 System OverviewDriven by the requirements of the CHART system and taking into account guidelines for a national ITS architecture, the CHART system is designed as a distributed object system utilizing the Common Object Request Broker Architecture (CORBA) as the base architecture.

The CHART system is deployed as an eight-server system with the CHART servers located at the SOC, AOC, SHA District 3, SHA District 4, SHA District 5, Easton Microwave Facility, Frederick Law Enforcement Center (LEC), and Prince George’s County TRIP Center.

The CHART system includes Dynamic Message Sign (DMS), Highway Advisory Radio (HAR), and Transportation Sensor System (TSS) device management. HAR capabilities include command and control of HIS DR1500 HARs, operating either in standalone mode or as part of a Synchronized HAR. A Synchronized HAR is treated by the system in most respects as a single HAR, but actually consists of multiple DR1500 HARs in close geographical proximity playing the same message at precisely the same time.

CHART capabilities also include Closed Circuit Television (CCTV) camera video distribution and management, using an Internet Protocol (IP) based distribution system. In addition, there is support for iMPath MPEG-2 encoders and decoders for video devices. The Maryland Transportation Authority (MdTA) video network has been integrated into CHART, providing the ability to display and control MdTA cameras using the CHART software. CHART manages a limited number of connections between the MDSHA IP video network and the MdTA VICON V1500 video network as well as managing the limited connections within the MdTA video network.

CHART clients gain access to the appropriate server either over the local segment of the LAN or remotely via the MDOT network, via a web browser pointing to the CHART web server running on a separate web server at the SOC. The primary advantage of a browser-based user interface is the ease with which anyone with the proper access and the proper security credentials can view or operate the CHART system. The CHART GUI requires minimal browser configuration, such as allowing pop-ups for the CHART web site and the standard Flash plug-in. The CHART web services result in effectively no increase in computing load on the back-end CHART servers no matter how many browsers are connected.

The R3B2 version of CHART adds the ability to create pending events and to schedule them for later use, features used to notify groups and individuals via e-mail regarding traffic events, and ability to send generic notifications unrelated to traffic events. Enhancements to the event history logs and communication log are included in R3B2, in addition to enhancements related to plan management and usage. R3B2 also includes the ability to view traffic events from other agencies, as made available via an interface to the Regional Integrated Transportation Information System (RITIS).

Figure 2-1 depicts the R3B2 system and network architecture.


Figure 2–1. CHART Release 3 Build 2 Network Architecture


CHARTWorkstations

CCTVCameras

Field Mgmt.Server

HARs andShazams

Low Speed ITS Devices

Detectors

KROWDAOR21

M-A

03

1-M

TP

I0

X1

E

Fixed and Portable DMS

Page and Fax

External Systems

CHART IIArchive Server

CHART IIServers

CHART IP Multicast

VideoDisplay Monitors

NETWORKMDOT

Internet

2.2 Organizational OverviewThe responsibilities for the operation and maintenance of the CHART system are divided into three areas: System Operation, System Management, and System Maintenance.

2.2.1 System OperationThe operation of the CHART system is the responsibility of the MDSHA CHART operations staff.

2.2.2 System ManagementCSC and MDSHA CHART personnel handle the management of the CHART system jointly. MDSHA CHART personnel carry out CHART’s administrative functions. CSC handles database administration functions, system backups, and network and systems management.

2.2.3 System MaintenanceThe maintenance of the CHART system is the responsibility of the CSC team. The CSC team provides bug fixes as needed and system updates via scheduled releases. In addition, CSC provides maintenance on all hardware other than the actual field devices.


3 Routine Operations

3.1 Operations OverviewThis release of the CHART system consists of multiple FMS servers, eight CHART servers and eight CHART web servers supporting multiple client workstations connecting via HTTPS.

New functions for R3B2 include the capability to create pending traffic events (not yet opened) and to schedule them for future activation, the capability to send notifications about traffic events or notifications independent of traffic events, improvements to the event history logs and communications log, and enhancements to plan management and usage. R3B2 also includes the ability to view traffic events from other agencies in the CHART GUI via an interface with the Regional Integrated Transportation System (RITIS).

1) Traffic Events

- Create and manage Pending Traffic Events to allow data about a traffic event that will occur in the future or occur frequently to be entered in advance.

- Ability to use a Pending Traffic Event to create a new Traffic Event, either one-time (changing the pending event into a new Traffic Event) or multiple times (leaving the pending event in the system for future use).

2) Schedules

- A generic scheduling capability allows system/user actions to be scheduled for activation at one or more dates and times, or on a recurring basis.

- R3B2 provides support for an Open Event action, which can be used to schedule when a pending traffic event should be opened or used to create a new event.

- Schedules may contain one or more Open Event actions, or may include zero actions for use as a simple reminder.

- When a schedule activates, it causes an alert to appear on the home page of users in the schedule’s target operation center. The alert provides the ability for a user to execute the actions included in the schedule.

3) Notification

- Send notifications to groups or individuals via e-mail.

- Notifications may be sent for traffic events, in which case many features exist to allow information from the traffic event to be included in the notification message.

- Notifications may be sent in stand alone mode, unrelated to traffic events.

- A history of notifications sent is available for viewing as a combined system wide list, or within each traffic event, for those sent from the event.


4) Event and Communications Logs

- Ability to filter the logs to see user and/or system generated messages (and device messages in the case of event history).

- Improved navigation of the logs, including user customizable entries per page, direct page access, and forward/back controls.

- Improved log searching, to include user, system, and/or device messages as part of the search criteria.

5) Plans

- Ability to store filter criteria with each plan, such as the operations center the plan applies to or keywords.

- Ability to filter the list of plans based on filter criteria, both when managing plans or when adding a plan to a traffic event’s response plan.

- Automatic filter selection based on the traffic event type and location (county, region, or location alias) when selecting a plan for use in a traffic event response plan.

- Ability to add multiple DMS or HAR plan items to a plan in a single operation.

6) Alerts

- Ability to view, manage, and resolve Execute Scheduled Actions alerts that are generated from schedules.

7) External Events

- Ability to view events from other agencies that exist in the RITIS system.

The complete list of all functions now supported by R3B2 is shown below.

Operation Center

- Select Operation Center at Login

- Add an Operation Center

- Remove an Operation Center

- Modify an Operation Center

User management

- Add, delete, modify user accounts

- Define user roles

Device management and control

- Add or delete devices

- View, modify DMS configuration information


- Set DMS online, offline, maintenance mode, reset DMS

- View, modify TSS configuration information

- Set TSS online, offline, maintenance mode

- View, modify HAR configuration information

- Set HAR online, offline, maintenance mode,

- Blank, monitor, reset HAR

- View HAR Status

- View, modify SHAZAM configuration information

- Set SHAZAM online, offline, maintenance mode

- Reset SHAZAM to last known state

- Associate DMS or SHAZAM to HAR as HAR Notifier

- Associate HAR to Synchronized HAR as constituent HAR

- Copy DMS/HAR/SHAZAM/TSS

- Add, delete, modify port configuration information

NTCIP DMS Device Management and Control

- Add or delete NTCIP DMS

- View, modify NTCIP DMS configuration information

- Set NTCIP DMS online, offline, maintenance mode,

- NTCIP DMS reset (when supported by DMS hardware)

- Put message on NTCIP DMS, blank NTCIP DMS

DMS Message Libraries

- Create/delete message libraries

- Create/delete library messages

HAR Message Libraries

- Create/delete message libraries

- Create/delete library messages

HAR Message

- HAR Message Concatenation

- HAR Message Formatting

Manage video distribution

- View Camera, Monitor configuration information

- Specify a current Monitor Group

- Set Camera, Monitor online, offline


- View Camera, Monitor Status

- Display a camera on a CHART monitor

- Request PTZ control of a CHART camera

- Override PTZ control of a CHART camera

- Command a COHU 3955 or 3960 camera:

- Pan

- Tilt

- Zoom

- Focus

- Iris

- Red/Blue color balance

- Lens speed

- Set camera title (first line)

- Set camera title (second line)

- Reset

- Power on/off

- Configure tour list – a list of cameras to be displayed in sequence with a specified dwell time between displays

- Start a tour list on a specified monitor

- Stop a tour list running on a specified monitor

DMS Plan Libraries

- View/Filter plan libraries

- Create/delete plan libraries

- Create/delete plan items

HAR Plan Libraries

- View/Filter plan libraries

- Create/delete plan libraries

- Create/delete plan items

Arbitration Queue:

- Add message to Device Queue,

- Evaluate Device Queue,

- Revoke item in response tabs.

Operations Log


- Log user activity

- Log system and device status information

System Management/Monitoring

- Provide FMS communications and port status

- Support device communications failover between FMS servers

Communications Log

- Create/manage communications log entries

- Search communication log entries

Traffic Event

- Create/manage events

- Create/manage/utilize/schedule pending events

- Create/manage/search event history log entries

- Put message on DMS, blank DMS, turn DMS beacons on/off

- Put message on HAR/blank HAR

- Activate/deactivate SHAZAMs

Notification

- Send/manage notifications

- Search notification history

Schedules

- Create/manage schedules

- Execute schedules, when activated or immediately

Dictionaries

- Banned words dictionary

- Spell-check dictionary

- Text To Speech Pronunciation dictionary

User Utilities

- CHART Chat

- Alerts

View Port Manager Status

Text To Speech Conversion

- Convert text to speech using Pronunciation dictionary

External System Interfaces


- Interface with Regional Integrated Transportation Information System (RITIS) to import traffic events from other agencies and make them available for viewing within the CHART system.

Separate FMS installer, with simultaneous multiple CommService installation option

Multiple Server Sites

Multiple Web Server Sites

3.2 Operations PrinciplesThe CHART system operates 24 hours per day, 7 days per week. The system is designed to free CHART operators from system management functions so that they may concentrate on performing CHART functions. To that end, the system requires little in the way of care and feeding. Routine system management functions such as backups are automated and require only a periodic check to verify they have completed successfully. The CHART system is deployed in a distributed multi-server environment. In this distributed environment, data distribution and replication will be handled automatically by the system.

The configuration of the system for use, such as adding new users or devices, and the monitoring of system status are the primary non-CHART functions required for the operation of the system.

3.3 Operations PersonnelThe operation of the CHART system supports multiple types of users, including: CHART operators, CHART administrators, CHART maintenance operators, and view-only operators.

The View Only designation is designed to allow access to CHART by people outside the traditional CHART user community. This classification exists to prevent these users from interfering with the CHART uncontrolled resources processing, which attempts to ensure that at least one user is always logged into an operations center that has control of system resources.

When a user logs into CHART, the user’s rights are searched for any that allow the user to change system resources in any way, such as the right to control a device or change settings. If the user’s rights are a subset of the “View Only Rights” (defined via a system profile setting), the user is deemed “View Only” and is automatically logged into the ViewOnly operations center. Users that are not deemed “View Only” are prevented from logging into the ViewOnly operations center. Note that this View Only classification is not directly tied to a specific CHART role; it is based strictly upon whether a user can or cannot make changes to the system. This allows the CHART roles to continue to be used to determine what specific users can and cannot view, even if they are “View Only”.

This separation of View Only users from other users serves the following purposes:

1) View Only users are shown different web pages than other users in some areas of the application. For example, a View Only user is shown an active traffic event list in the working window when they log in, while other users are shown an operations center report.

2) The existence of an operations center that only has View Only users logged in keeps this operations center from ever controlling any system resources. This is achieved by the


fact that view only users, by definition due to their user rights, cannot add or alter CHART data, and thus cannot perform any action that causes their operations center to acquire the control of a system resource. Because the ViewOnly operations center can never control any system resource, View Only users are never prevented from logging out due to controlled resources.

3) The funneling of all View Only users into a ViewOnly operations center prevents View Only users from logging into other operations centers and being counted as a logged in user in the CHART uncontrolled resources detection algorithm. If a View Only user were allowed to log into a traditional operation center, this would lead to a scenario where one user gains control of a device and is permitted to logout because a View Only user is logged into the same center. CHART would not consider the controlled resource as being uncontrolled, however the View Only user would have no way to alter the resource to remove a stale message, close a traffic event, etc. Furthermore, the View Only user would have no way to logout because CHART prevents the last user from logging out of a center if the center has controlled resources.

Typically at least one user of the system is logged in as a CHART administrator. The CHART administrator creates user accounts, adds new devices to the system, controls the contents of the banned words dictionary, and monitors the operation of the system. This role can be fulfilled by SHA personnel and/or software maintenance personnel.

CHART operators use the CHART system to manage events and to control and monitor devices. This role is fulfilled by SHA personnel

CHART maintenance operators use CHART to test and maintain field devices. This role can be fulfilled by SHA personnel and/or Team CSC NOC and hardware maintenance personnel.

This document (CHART Operations and Maintenance Guide) and the CHART User’s Guide provide the necessary documentation for the operation of the CHART system. In addition to these guides the CHART system has an online help function for providing user information on system functions.

3.4 Maintenance PersonnelThe CSC team handles the CHART system maintenance functions. CHART software, communications and hardware problems are reported to the Maryland Department of Transportation (MDOT) Network Operations Center (NOC).

The following document is available as supporting information.

CHART R3B2 User’s Guide, to be published.

3.5 System Startup and ShutdownThis section provides information on the startup and shutdown of the CHART services. The procedure is the same for all CHART application servers.


3.5.1 CHART Server System StartupThe server processes may be manually started from the Windows Services Control Panel if necessary. When manually starting the CHART server processes using the Services control panel a specific order must be maintained. Oracle and Nuance services are started, followed by the CHART services in the order they are numbered, from 1A to 10B. The full list is:

Oracle services. Oracle services are different for each server. When starting CHART services, the server order does not matter.:

o OracleCSService (SOC only)

o OracleOraDb10g_home1TNSListenerchart2

o OracleServiceC2ARCH3 (SOC only)

o OracleServiceC2SOC3 (SOC only)

o OracleServiceC2AOC3 (AOC only)

o OracleServiceC2D5AN (District 5, Annapolis only)

o OracleServiceC2D4BR (District 4, Brooklandville only)

o OracleServiceC2LEC (Frederick LEC only)

o OracleServiceC2D3GR (District 3, Greenbelt only)

o OracleServiceC2TRIP (PG Trip Center only)

Nuance Watcher Daemon

V1500ManagerService (AOC only)

CHART R3B2.06 1A Trader

CHART R3B2.06 1B EventService

CHART R3B2.06 2A UserManagerEvents

CHART R3B2.06 2B UserManagerService

CHART R3B2.06 2C AlertService

CHART R3B2.06 2D AlertEvents

CHART R3B2.06 2E RITISEvents

CHART R3B2.06 2F RITISService

CHART R3B2.06 2G ScheduleEvents

CHART R3B2.06 2H ScheduleService

CHART R3B2.06 3A MsgUtilityEvents

CHART R3B2.06 3B MsgUtilityService

CHART R3B2.06 4A DMSEvents

CHART R3B2.06 4B DMSService


CHART R3B2.06 5A HAREvents

CHART R3B2.06 5B HARService

CHART R3B2.06 6A TrafficEventEvents

CHART R3B2.06 6B TrafficEventService

CHART R3B2.06 6C RoadwayLocationLookupService

CHART R3B2.06 7A TSSEvents

CHART R3B2.06 7B TSSService

CHART R3B2.06 8A EORSService

CHART R3B2.06 9A VideoEventService

CHART R3B2.06 9B VideoService

CHART R3B2.06 10A NotificationEvents

CHART R3B2.06 10B NotificationService

V1500 Manager Service (only applicable on VideoService Router server, e.g., aocchart2)

When shutting down services manually, they must be shut down in the reverse order.

If any services fail to start, refer to the appropriate application log file (see Section 3.7.1).

CHART’s CORBA based design serves to minimize dependencies between the CHART servers, clients, and remote FMS with regard to the order in which the systems are started. However, a CHART client will require access to a functioning CHART web server which has access to a functioning CHART server before a user can log in to the system. Likewise, the CHART server will require access to an appropriate functioning remote FMS in order to successfully control devices.

For CHART’s video distribution, dependencies exist in a few areas including the fact that the AOCCHART2 server serves all MdTA video. When restarting all video services, the AOCCHART2 video service must be the last to start, or can be restarted as the last step.

3.5.2 CHART Web Server System StartupThe services related to CHART web services are configured to start automatically on each of the physical web servers (see the installation procedures in Appendix A), however they may also be manually started using the Windows Services. When manually starting the CHART web services, the following order must be maintained:

1) World Wide Web Publishing Service

2) Apache Tomcat 5.5.9

There are no dependencies between the CHART clients (browsers), CHART web services, and the CHART services with regard to the order in which the systems are started. However, a


CHART browser client will require access to a functioning CHART web service before the CHART login screen is available. Further, the CHART web service requires access to a functioning remote CHART server (including the database) in order to successfully log in.

If a CHART web service is started before any CHART servers, there may be a delay up to the “discovery interval” specified in the CHART MainServlet.props properties file before the CHART web service discovers the CHART server objects. Logged-in administrative users may initiate a discovery at any time rather than waiting for this interval to expire.

If any service fails to start, refer to the appropriate application log file (see Section 3.7).

3.5.3 CHART Web Server System ShutdownThere are no special steps to take when shutting down the CHART web server – the normal Windows shutdown process may be followed at any time. When the CHART web service is shut down, any browsers actively connected to that web service will stop refreshing and may display errors. Further, the CHART login sessions hosted by that web service for each user logged into CHART will be destroyed. These users will continue to appear as logged in users in the CHART User Management Service until that service detects the absence of the user login sessions.

To shut down the CHART web service without shutting down the operating system, shutdown the services in reverse order of startup as detailed in section 3.5.2.

3.5.4 FMS Server System StartupThe FMS server process, CommService, will start up automatically with the startup of the operating system. Generally no operator intervention is required during the system boot process to make the system ready for use.

The CommService process may be manually started from the Windows Services Control Panel if necessary. The CommService process does not depend on any other server processes on the FMS server. The CommService does depend on the Trader and generic EventService running on the CHART server which the FMS service connects to (as indicated by the CommService.props file).

In the event that the CommService fails to start, see Section 3.7.1 on the application log files.

3.5.5 FMS Server System ShutdownTo perform a clean shutdown of an FMS server, first verify that there are no current active connections. The best way to do this is to use the “tail” command, if available, in a DOS window. Navigate to the installation directory of the CommService to be shut down, and enter the command tail –f <LogfileName> and hit enter. Watch the log for 30 seconds or so to ensure there is no current activity. If the tail command is not available, view the log file in an editor and quickly check the bottom of the file. These methods are not foolproof, but normally the CHART System or an operator will reattempt any aborted command anyway. Next use the normal Windows shutdown process to shut down the system. Alternatively, to shut down the CommService process without shutting down the operating system, use the Windows Services control panel to stop the CommService process. As of R3B2, FMS Servers and the Communication Services set up to run on them are:


ANNAD5FMS1: CHART R3B2.06 9A CommService AOCFMS1: CHART R3B2.06 9B CommServiceTeleB

CHART R3B2.06 9C CommServicePOTS AOCFMS2: CHART R3B2.06 9A CommService BALTOFMS1: CHART R3B2.06 9A CommService BHTADMINFMS1: CHART R3B2.06 9A CommService BROOKD4FMS1: CHART R3B2.06 9A CommService CAB305FMS1: CHART R3B2.06 9A CommService CHURCHFMS1: CHART R3B2.06 9A CommService DAYTONFMS1: CHART R3B2.06 9A CommService ELMRDFMS1: CHART R3B2.06 9A CommService GRNBLTD3FMS1: CHART R3B2.06 9A CommService ISDN

CHART R3B2.06 9B CommServiceTeleB CHART R3B2.06 9C CommServicePOTS HANSOCFMS1: CHART R3B2.06 9A CommServiceISDN CHART R3B2.06 9B CommServiceTeleB CHART R3B2.06 9C CommServicePOTS HANSOCFMS2: CHART R3B2.06 9A CommService HATUMFMS1: CHART R3B2.06 9A CommService HEREFORDFMS1: CHART R3B2.06 9A CommService HUT0304FMS1: CHART R3B2.06 9A CommService HUT0304FMS1 CHART R3B2.06 9B CommServiceDirect HUT0607FMS1: CHART R3B2.06 9A CommService HUT091011FMS: CHART R3B2.06 9A CommService HUT1213FMS1: CHART R3B2.06 9A CommService HUT1819FMS1: CHART R3B2.06 9A CommService HUT21FMS1: CHART R3B2.06 9A CommService HUT2425FMS1: CHART R3B2.06 9A CommService HUT333435FMS1: CHART R3B2.06 9A CommService HUT3637FMS1: CHART R3B2.06 9A CommService HUT434445FMS1: CHART R3B2.06 9A CommService MSPFFMS1: CHART R3B2.06 9A CommService TOC4FMS1: CHART R3B2.06 9A CommService FREDLECFMS1: CHART R3B2.06 9A CommService

NOTE: The above list is subject to change.

3.6 System BackupsAs a part of the normal CHART system maintenance activities, the database and CHART logs are saved to tape automatically each night. Other than a recovery image the only reason to make a backup of the CHART web servers is if the configuration of the system is changed (for example if there are changes to the property (.props) files, the velocity (.vm) files, or the help (.html) files).


3.7 Operations Log FilesThe system logs status, alert, and error information to log files. There are two types of log files: text files generated for debugging purposes, and data logged to the database for archiving and access via the CHART Reporting Tool. The text files include server and application log files for the backend services and web services, and device status files. The database information includes operations log entries, communications log entries, and data associated with event management.

On the web servers, log files of interest are created by CHART web service, Apache Tomcat, and MS IIS. The Tomcat and IIS logs are generally small and should be cleaned periodically – perhaps monthly.

3.7.1 CHART Service Log FilesApplication specific log files are generated by individual server applications. These files are located in the appropriate bin directory where CHART is installed. There is one log file for each service, except the Event, Trader, and TTS services. A new log file is automatically opened each day when the first message for that day is logged (this means there could be periods where no log files are created for a particular day if no messages are logged during that day). The files are named as follows:

AlertService_yymmdd.txt

CommService_yymmdd.txt (see Section A.1.4.1 for multiple communications services)

DMSService_yymmdd.txt

EORSService_yymmdd.txt

MsgUtilService_yymmdd.txt

NotificationService_yymmdd.txt

RoadwayLocationLookupService_yymmdd.txt

RITISService_yymmdd.txt

ScheduleService_yymmdd.txt

TrafficEventService_yymmdd.txt

TSSService_yymmdd.txt

UMService_yymmdd.txt

HARService_yymmdd.txt

VideoService_yymmdd.txt

(where yymmdd is the two digit year, month, and day of the creation of the file, (e.g. 061219).

To view these log files use Notepad or any other text editor.

In general, messages in these files will be more useful to the maintenance staff in debugging a problem than to the operations personnel in running the system. However, in the event that a


service does not start, these log files should be consulted to determine the reason. Occasionally Oracle initialization warnings will appear in the log files during startup. These warning messages occur when an application tries to connect to the database before the database has completed its startup. This situation is handled within the software so these messages appear as status only and do not indicate an error condition. An example message appears below.

04/12/00 01:16:32 PM Thread: main Class: CHART2.Utility.DBConnection - Error connecting to DBMS - ORA-01033: ORACLE initialization or shutdown in progress

Any Oracle messages other than the ORA-01033 message shown above should be reported to the maintenance support group.

Each log file contains informational messages, errors and warnings pertaining to its own operations. For example, the DMSService log file will record any errors received related to communicating with a DMS.

In the event of a problem with the system the administrator should make copies of the log files to provide to the maintenance personnel along with the problem report. Note that the CommService log files are located on the FMS servers. In the case where a problem involves communicating with a device in the field then the appropriate CommService log file should be copied from the FMS server involved.

3.7.2 CHART Web Service Log FilesCHART web services use self-cleaning, rotating log files like those used by the CHART backend services. Each day, a new file is created of the form

chartlite_yy_mm_dd.txt

These files are located in the web service directory in D:\Tomcat-5.5.9\webapps\chartlite\LogFiles\. All log entries for a specific day are kept in a log file with the corresponding date. In general, messages in these files are more useful to the maintenance staff in debugging a problem than to the operations personnel in running the system. However, in the event that the CHART service does not start, the log file for the current day should be consulted to determine the reason. Old log files are automatically deleted by the system. The number of days of log files maintained is configured in the web service properties file (MainServlet.props). See section A.1.11 for details.

In the event of a problem with the system the administrator should make a copy of the appropriate log file to provide to the maintenance personnel along with the problem report.

3.7.3 Apache Tomcat Log FilesTomcat creates a new log files every day of the form

localhost_log_yyyy-mm-dd.txt

Tomcat may also create other log files of a similar format (with the date appended) and also files named stdout.txt and stderr.txt.

The log files mentioned above are located under the Tomcat installation directory (e.g. D:\tomcat-5.5.9\logs) and contain messages useful for diagnosing problems with the tomcat web engine. See the Tomcat web site http://jakarta.apache.org/tomcat/ for help interpreting these


http://jakarta.apache.org/tomcat/

logs. Tomcat does not have a self-cleaning mechanism and thus the logs directory should be manually cleaned periodically.

3.7.4 Internet Information Services Log FileThe path to the IIS log file is D:\tomcat-5.5.9\logs\iis_redirect.log. This file should be consulted if the are problems accessing the CHART web service via Microsoft Internet Information Services (IIS). Refer to Microsoft documentation for instructions on how to interpret this file.

3.7.5 Velocity Log FileThe Velocity template engine, which is used by the CHART web service to build web page content, also keeps a log file. Generally this is useful only for debugging web pages that are built incorrectly or are missing entire sections. It may be of interest if someone attempts to customize the velocity template files.

This file is normally located at D:\tomcat-5.5.9\bin\velocity.log and Velocity truncates the file each time the CHART web service is restarted.

3.7.6 DMS Status LogsOne time each day the polled status for each DMS is logged to a flat file on the CHART server serving the DMS. The status for all DMSs served on a particular CHART server will share a single log file, separate from the application log file. A new log file for this purpose is created each day, with the date of the file contained in the file name. These files are located in the DMSService\DMSStatusLogs folder of the CHART installation directory. DMS Status log files are named as follows:

Status_yymmdd.txt

(Where yymmdd is the two digits year, month, and day of the creation of the file, e.g. 061219).

Other types of devices do not have these status logs.

3.7.7 TSS Raw Data LogsTraffic data obtained from TSS devices that are online are written to raw data files. This data includes volume, speed, and occupancy data for every poll of every device. Each poll causes one line to be written to the raw data file for that day, including the timestamp, device name, and zone, volume, speed and occupancy data received on that poll. Data for all TSSs is written to one file, which is changed each day. The raw data files are written to the TSSService\RawData directory in the CHART installation directory. They are named as follows:

RawData_yymmdd.txt

(Where yymmdd is the two digits year, month, and day of the creation of the file, e.g. 000503).


A TSS must be online to have raw data logged in these files. Although TSS RawData files are ASCII readable files and can be interpreted by human readers with some effort, they are designed for machine processing, not routine human review.

3.7.8 Device LogsDevice logs capture detailed device communications information for use in debugging problems with devices. By default these logs are not enabled. To enable a device log for a specific device you must check the Device Log checkbox on the General tab of the Properties dialog for the device. These files are located in the DMSService\DeviceLogs\ folder for DMSs, HARService\DeviceLogs\ for HARs, and TSSService\DebugLogs\ folder for TSSs in the CHART installation directory. Device log files are named as follows:

Devicename_yymmdd.txt

(Where Devicename is the name of the Device and yymmdd is the two digits year, month, and day of the creation of the file, e.g. 000503).

Device Logs are available only for DMSs, HARs and TSSs. HAR device logs log the touch-tones used in communicating with HARs. (AP55 communications are one-way only, so AP55 device logs are less useful than DR1500 device logs.) Since all SHAZAM communications are one-way only, SHAZAM device logs are not created. Device logs are very useful in debugging communications problems with DMS and TSS devices.

3.7.9 CHART Operations LogThe CHART operations log is maintained as a database table and logs user and system actions associated with the configuration and operation of the CHART system. Messages logged to this table consist of a timestamp, username, center ID, host computer name, action type, and description. This data can be analyzed using the CHART Reporting Tool.

Entries from the operations log are periodically saved to the archive database and deleted from the operational system. Typically three full days of operations log entries (plus the current day’s entries) are maintained in the operational system.

3.8 System Administration and ConfigurationThis section contains information on the system administration functions necessary to administer and setup the CHART system for use. General system administration information and documentation on the system administration dialogs in the CHART GUI can be found in the CHART User’s Guide. Administration and configuration functions require appropriate functional rights and are generally reserved for system administrators.

3.8.1 User RightsIn order for users to be able to exercise CHART functions they must have the appropriate functional rights. These are assigned through roles (see the CHART User Guide). Table 3–1 (below) shows the functional rights available for assignment to roles.


Table 3–1. Functional RightsFunctional Right Description

Adjust Color On Camera Allows the holder to adjust the color balance (a.k.a. color gain) on a camera for which the holder has a camera control session open.

Adjust Iris On Camera Allows the holder to adjust the iris on a camera for which the holder has a camera control session open.

Basic Operations Allows the holder to perform basic system operations including use the comm log, set response participants arrival, departure, and notification times, and remove a participant.

Block Display to Web and Media

Allows the holder to block display of a camera to monitors marked as "public" (typically, web encoders and media monitors).

Close External Traffic Event

Allows the holder to close external traffic events that exist in the CHART system. (Note that this is only required if stale external events remain in the CHART system due to a failed connection to the external system.)

Configure Arbitration Queue

Allows the holder to force reevaluation of the queue, change the priority of queue entries, and remove queue entries.

Configure Camera This right is needed to set the user-settable status a source and control status of a controllable camera. In the future, will also allow the holder to set the configurations of cameras and other video sources.

Configure DMS Allows the holder to add a DMS, remove a DMS, and configure a DMS including the capability to set the name of a DMS, set the polling interval of a DMS and set the DMS communications loss timeout.

Configure HAR Allows the holder to configure HAR and SHAZAM devices.

Configure Monitor Allows the holder to add, delete, and set the configurations of monitors.

Configure Monitor Group Allows the holder to add, delete, and set the configurations of monitor groups.

Configure Persistent Preset

Allows the holder to save and delete persistent presets, for any camera for which the holder has a camera control session open.

Configure Persistent Tour Allows the holder to add, modify, and delete video tours which are persisted and made available to all users.

Configure Self Allows the holder to change his/her own password provided they can provide the current password, view properties in his/her profile, and add properties to and delete properties from his/her profile.

Configure System Allows the holder to modify the system configuration.


Functional Right DescriptionConfigure System Participants

Allows the holder to configure the event participants defined in the system.

Configure TSS Allows the holder to add a TSS to the system, remove a TSS from the system, set the configuration of a TSS, and view the configuration of a TSS.

Configure Users Allows the holder to create a user, delete a user, create a new role, grant a role to a user, revoke a role from a user, delete a role from the system, set the functional rights in a role, and change a user’s password.

Configure Video Network Allows the holder to add, delete, and configure video fabrics, video switches, bridge circuits, and command processors. This right is expected to be restricted to very few users.

Create Manual Alert Allows the holder to create Manual Alerts.Delete Trader Entry Allows the holder to delete trader entries. This is a

dangerous right. This right should be granted only to software maintenance personnel who understand why trader entries might be deleted and the implications of deleting them.

Display Camera Allows the holder to display a camera on any monitor on which the holder has a right to display images.

Execute Schedules Allows the holder to execute schedules.Focus Camera Allows the holder to adjust the focus on a camera for which

the holder has a camera control session open.Maintain DMS Allows the holder to perform commands on a DMS that is

in maintenance mode, put a DMS in maintenance mode, move a DMS from maintenance mode to online mode, and move a DMS from maintenance mode to offline mode.

Maintain HAR Allows the holder to perform commands on a HAR or SHAZAM that is in maintenance mode, put a HAR or SHAZAM in maintenance mode, move a HAR or SHAZAM from maintenance mode to online mode, and move a HAR or SHAZAM from maintenance mode to offline mode.

Maintain TSS Allows the holder to put a TSS in maintenance mode, move a TSS from maintenance mode to online mode, and move a TSS from maintenance mode to offline mode.


Functional Right DescriptionManage All Alerts Allows the holder to extend existing rights to manage alerts

of specific types to include alerts at other than the user’s own operations center. For instance, if a user holds the Manage Generic Alert right only, he can manage (manipulate) Generic Alerts only at his own operations center; but if he also holds this right, he can manage (manipulate) Generic Alerts at all operations centers. (This right also extends to all operations centers the Manage Device Failure Alert right, the Manage Duplicate Event Alert right, etc.) Note: In order to manage alerts at other operating centers, the user also needs the View All Alerts right so he can see alerts at other operating centers.

Manage Device Comms Allows the holder to take an offline device online and take an offline device online.

Manage Device Failure Alert

Allows the holder to manage Device Failure Alerts. (Unlessthe Manage All Alerts right is also held, this allows a user to manage only Device Failure Alerts under the purview of the user’s own operations center.) Note: in order to manage this alert type, the user also needs the View Device Failure Alert right so he can see them.

Manage Dictionary Allows the holder to add/remove banned and approved words to/from the dictionary.

Manage Duplicate Event Alert

Allows the holder to manage Duplicate Event Alerts. (Unless the Manage All Alerts right is also held, this allows a user to manage only Duplicate Event Alerts under the purview of the user’s own operations center.) Note: in order to manage this alert type, the user also needs the View Generic Alert right so he can see them.

Manage Event Still Open Alert

Allows the holder to manage Event Still Open Alerts. (Unless the Manage All Alerts right is also held, this allows a user to manage only Event Still Open Alerts under the purview of the user’s own operations center.) Note: in order to manage this alert type, the user also needs the View Generic Alert right so he can see them.

Manage Execute Schedule Action Alert

Allows the holder to manage Execute Schedule Action alerts. (Unless the Manage All Alerts right is also held, this allows a user to manage only Execute Schedule Action alerts under the purview of the user’s own operations center.) Note: in order to manage this alert type, the user also needs the View Execute Schedule Action Alert right so he can see them.


Functional Right DescriptionManage Generic Alert Allows the holder to manage Generic Alerts. (Unless the

Manage All Alerts right is also held, this allows a user to manage only Generic Alerts under the purview of the user’s own operations center.) Note: in order to manage this alert type, the user also needs the View Generic Alert right so he can see them.

Manage Pronunciations Allows the holder to add, remove and modify TTS pronunciations.

Manage Schedules Allows the holder to manage Schedules, including the ability to add, edit, and remove schedules.

Manage Services Allows the holder to shutdown a service.Manage Traders Allows the holder to examine ORB Traders and trader

entries in them. This is a view-only right, however, it is expected that this right will be of little interest to anyone but software maintenance personnel.

Manage Traffic Event Allows the holder to change the properties of a traffic event.Manage Unhandled Resources Alert

Allows the holder to manage Unhandled Resources Alerts.(Unless the Manage All Alerts right is also held, this allows a user to manage only Unhandled Resources Alerts under the purview of the user’s own operations center.) Note: in order to manage this alert type, the user also needs the View Unhandled Resources Alert right so he can see them.

Manage User Logins Allows the holder to force a user to logout of the system.Merge Traffic Events Allows the holder to merge traffic events.Modify Message Library Allows the holder to create, rename, or remove message

libraries, add/remove a message to/from a library, change the description or content of a library message, and remove a stored message from the system.

Modify Plans Allows the holder to create and rename plans and plan items and remove an item from a plan.

Move to Persistent Preset Allows the holder to move a camera to a saved persistent preset, for any camera for which the holder has a camera control session open.

Override Camera Control Allows the holder to override a camera control session on a camera which is already controlled.

Override Camera Display Allows the holder to issue an override request for a camera display which the holder would otherwise have rights to perform. That is, the user must also have the DisplayCamera right and the appropriate DisplayOnLocalMonitor or DisplayOnRemoteMonitor right.

Override Shared Resource Control

Allows the holder to override control of shared resources that are controlled by other operations centers.

Pan/Tilt Camera Allows the holder to pan or tilt a camera for which the holder has a camera control session open.


Functional Right DescriptionPoll Camera Allows the holder to force the system to poll a camera for its

current communications status.Program Camera Allows the holder to enter program mode and perform

programming commands for a controlled camera for which the holder has a camera control session open.

Request Camera Control Allows the holder to initiate a camera control session on a camera.

Reset Camera Allows the holder to reset a camera for which the holder has a camera control session open.

Respond to Traffic Event Allows the holder to manage the response to a traffic event including adding, editing, and removing response plan items; and executing and revoking execution of the response plan items or the whole plan.

Revoke Camera Control This right allows the holder to revoke (and unrevoke) control of a camera to users claiming membership in a monitor group belonging to specified organization(s).

Revoke Video Display This right allows the holder to revoke (and unrevoke) display of a camera on monitors belonging to specified organization(s).

Run Persistent Tour Allows the holder to start and stop any permanent, persistent tour on any monitor on which the user is allowed to set the display.

Send a Notification Allows the holder to send notifications.Set Display On Local Monitor

Allows the holder to specify what is to be displayed on a monitor that is in the monitor group the user claims is his/her local monitor group.

Set Display On Remote Monitor

Allows the holder to specify what is to be displayed any monitor NOT in the monitor group the user claims is his/her local monitor group.

Set Lens Speed on Camera Allows the holder to set the lens speed on a camera for which the holder has a camera control session open.

Set Own Monitor Group Allows the holder to set his/her monitor group to one other than that assigned by default based on the operations center the user logs into.

Note: Since the setting of a user’s monitor group is performed only on the GUI, this right must be enforced by the GUI. This right is never tested by any CHART2 service.

Set Power On Camera Allows the holder to flip the power on a camera on or off, for any camera for which the holder has a camera control session open.

Set Traffic Alert Allows the holder to set or clear Traffic Alert text to be posted on the public web site.


Functional Right DescriptionSVFT Emergency Menu Abort

Allows the holder to issue the abort command for a Vicon SVFT video camera, which allows an emergency menu backout command in case the user finds himself with the SVFT displaying a menu while the CHART system is not displaying the programming menu dialog.

Take Notification Offline Allows the holder to take a notification offline.Title Camera Allows the holder to set the title(s) on a camera for which

the holder has a camera control session open.Transfer Any Shared Resource

Allows the holder to transfer control of a shared resource from one operations center to another.

Use Plans Allows the holder to activate a plan and all of the items in the plan.

View All Alerts Allows the holder to extend existing rights to view alerts of specific types to include alerts at other than the user’s own operations center. For instance, if a user holds the View Generic Alert right only, he can see Generic Alerts only at their own operations center; but if they also hold this right, they can view Generic Alerts at all operations centers. (This right also extends to all operations centers the View Device Failure Alert right, the View Duplicate Event Alert right, etc.) Note: this right allows a user to view alerts (which he has individual rights to view) at all operating centers, but does not grant the right to manage alerts at other operating centers. See Manage All Alerts.

View Camera Configuration

Allows the holder to view the configurations of cameras and other video sources. The Configure Camera right would be needed to modify any such configurations.

View Device Failure Alert Allows the holder to view Device Failure Alerts.(Unless the View All Alerts right is also held, this allows a user to view only Device Failure Alerts under the purview of the user’s own operations center.) Note: This is a view-only right. In order to manage this alert type, the user also needs the Manage Device Failure Alert right.

View Dictionary Allows the holder to get the current list of banned words from the dictionary.

View Duplicate Event Alert

Allows the holder to view Duplicate Event Alerts. (Unless the ViewAllAlerts right is also held, this allows a user to view only Duplicate Event Alerts under the purview of the user’s own operations center.) Note: This is a view-only right. In order to manage this alert type, the user also needs the Manage Duplicate Event Alert right.


Functional Right DescriptionView Event Still Open Alert

Allows the holder to view Event Still Open Alerts. (Unless the ViewAllAlerts right is also held, this allows a user to view only Event Still Open Alerts under the purview of the user’s own operations center.) Note: This is a view-only right. In order to manage this alert type, the user also needs the Manage Event Still Open Alert right.

View Execute Schedule Action Alert

Allows the holder to view Execute Schedule Action alerts. (Unless the ViewAllAlerts right is also held, this allows a user to view only Execute Schedule Action alerts under the purview of the user’s own operations center.) Note: This is a view-only right. In order to manage this alert type, the user also needs the Manage Execute Schedule Action Alert right.

View External Traffic Event

Allows the holder to view traffic events imported from other systems (such as RITIS).

View Generic Alert Allows the holder to view Generic Alerts. (Unless the View All Alerts right is also held, this allows a user to view only Generic Alerts under the purview of the user’s own operations center. Note: This is a view-only right. In order to manage this alert type, the user also needs the Manage Generic Alert right.

View HAR Configuration Allows the holder to view the configuration of HAR and SHAZAM devices.

View Monitor Configuration

Allows the holder to view the configurations of monitors and other video sinks. The Configure Monitor right would be needed to modify any such configurations.

View Monitor Group Configuration

Allows the holder to view the configurations of monitor groups. The Configure Monitor Group right would be needed to modify any such configurations.

View Notification Records Allows the holder to view notification records.View Persistent Tour Configuration

Allows the holder to view the configuration of video tours which are persisted and made available to all users.

View Pronunciations Allows the holder to view TTS pronunciations.View Schedules Allows the holder to view Schedules.View Shift Handoff Wiki Allows the holder to navigate to the Shift Handoff Wiki

from a CHART GUI link.View Traffic Event Allows the holder to view traffic event related information.View TSS Configuration Allows the holder to view the configuration of a TSS.View Unhandled Resources Alert

Allows the holder to view Unhandled Resources Alerts.(Unless the ViewAllAlerts right is also held, this allows a user to view only Unhandled Resources Alerts under the purview of the user's own operations center.) Note: This is a view-only right. In order to manage this alert type, the user also needs the Manage Unhandled Resources Alert right.


Functional Right DescriptionView User Configuration Allows the holder to get the list of all users, get the list of all

roles, get the list of functional rights that are assigned to a role, and get the list of roles that a particular user has been granted.

View User Logins Allows the holder to get a list of users currently logged into the system.

View Video Network Config

Allows the holder to view the configurations of video fabrics, video switches, bridge circuits, and to view video routes.

Zoom Camera Allows the holder to zoom a camera for which the holder has a camera control session open.

Table 3–2 shows the possible allocation of functional rights to roles in the R3B2 system.

Table 3–2. Possible Allocation of Functional RightsRole Functional Rights

Admin All functional rights, except for Manage Traders and Delete Trader Entry which are intended more for use by software maintenance personnel.

Monitor Basic OperationsView Traffic Event


Role Functional RightsOperator Adjust Iris On Camera

Basic OperationsConfigure SelfDisplay CameraFocus CameraHandle Uncontrolled Shared Resource EventExecute SchedulesManage Device CommsManage Device Failure AlertManage Duplicate Event AlertManage Event Still Open AlertManage Execute Schedule Action AlertManage Generic AlertManage Traffic EventManage Unhandled Resources AlertMove to Persistent PresetPan/Tilt CameraPoll CameraRequest Camera ControlReset CameraRespond to Traffic EventRun Persistent TourSend a NotificationSet Display On Local MonitorSet Display On Remote MonitorSet Lens Speed on CameraSet Own Monitor GroupTransfer Any Shared ResourceUse PlansView Camera ConfigurationView Device Failure AlertView Duplicate Event AlertView Event Still Open AlertView Execute Schedule Action AlertView External Traffic EventView Generic AlertView Monitor ConfigurationView Monitor Group ConfigurationView Notification RecordsView Persistent Tour ConfigurationView PronunciationsView SchedulesView Unhandled Resources AlertView Video Network ConfigurationView Traffic Event


Role Functional RightsSenior Operator All rights allocated to Operator role plus:

Adjust Color On CameraBlock Display to Web and MediaConfigure Camera Configure MonitorConfigure Monitor GroupConfigure Persistent PresetConfigure Persistent TourManage All AlertsManage SchedulesMerge Traffic EventsModify Message LibraryModify PlansOverride Camera ControlOverride Camera DisplaySet Power On CameraSet Traffic AlertTake Notification OfflineTitle CameraView All Alerts


Role Functional RightsTechnician Adjust Color On Camera

Adjust Iris On CameraBasic OperationsConfigure Arbitration QueueConfigure CameraConfigure DMSConfigure HARConfigure MonitorConfigure SelfDisplay CameraSet Display On Local MonitorFocus CameraHandle Uncontrolled Shared Resource EventManage Device Failure AlertManage Unhandled Resources AlertMaintain DMSMaintain HARMaintain TSSManage Device CommsPan/Tilt CameraPoll CameraRequest Camera ControlReset CameraSet Lens Speed on CameraSet Power On CameraTitle CameraTransfer Any Shared ResourceUse PlansView Camera ConfigurationView Device Failure AlertView HAR ConfigurationView Monitor ConfigurationView Monitor Group ConfigurationView Persistent Tour ConfigurationView Video Network ConfigurationView TSS ConfigurationView Unhandled Resources AlertZoom Camera

3.8.2 Properties FilesCHART applications make use of properties files containing parameters to control application behavior. The properties files are located in the installation directory under the folders for each


application. The table below lists each application and its corresponding properties file. Each file contains comments to describe the purpose and use of each parameter.

Table 3–3. Properties FilesApplication Properties File

AlertService AlertService.propsCommService CommService.propsDMSEventService DMSEventService.propsDMSService DMSService.propsEORSService EORSService.propsEventService EventService.propsHAREventService HAREventServiceHARService HARService.propsMsgUtilityEventService MsgUtilityEventService.propsMsgUtilityService MsgUtilityService.propsNotificationService NotificationService.propsRoadwayLocationLookupService RoadwayLocationLookupService.propsRITISService RITISService.propsScheduleService ScheduleService.propsTradingService TradingService.propsTrafficEventEventService TrafficEventEventService.propsTrafficEventService TrafficEventService.propsTSSEventService TSSEventService.propsTSSService TSSService.propsVideoEventService VideoEventService.propsVideoService VideoService.props

Most of the parameters in each file should be left set to their installed values. Certain parameters are often changed during installation, for instance, log files are sometimes kept for 14 days instead of 7, and services are sometimes run in debug mode. Certain other parameters may require modification during the normal course of system operation. Changes to the properties files will not take effect until the corresponding service is restarted.

3.8.3 CHART Web Service Properties FileThe CHART web service properties file is located in D:\tomcat-5.5.9\webapps\chartlite\WEB-INF\MainServlet.props.

The CHART web service makes use of a property file containing parameters to control application behavior. Some examples of properties are error logging level, which database to use, various timing values, the locations of the CHART CORBA Trading services, and the location of external web sites such as EORS, SHADE, and paging.


Most of the parameters in the props file should be left set to their installed values; however, there are certain parameters that may require modification during the normal course of system operation. See Appendix A for details about each setting in the properties file.

Changes to the properties file will not take effect until the Apache Tomcat 5.5 service is restarted.

3.8.4 Event Duplication Properties in System ProfileThere are eight System Profile Properties which the Traffic Event Service uses to determine what criteria to use to compare traffic events. If one of these comparisons proves successful, a Duplicate Event Alert is sent to the operating center which created the newer event. Even though these are System Profile Properties, which are normally configurable via the GUI, these eight properties are not viewable or editable via the GUI. They can be set by software maintenance or database administration personnel. (The System Profile Properties table is replicated, so these properties need to be set in only one database, then wait for the replication period and verify they were pushed out to at least one other CHART server.)

The eight properties have to do with the comparison of three different parts of the traffic event location: direction, intersecting features, and distance. These are discussed in the following three sections. A summary of the eight properties is presented in Table 3-X1.

Table 3–X1. Event Comparison System Profile Properties Summary

Prop Num Property Name Type Default

(1) EVENT_DUP_COMPARE_DIRECTION Boolean True

(2)EVENT_DUP_EVENT_WITH_DIR_CANT_MATCH_ROADWAY_EVENT_WITHOUT_DIR Boolean False

(3) EVENT_DUP_COMPARE_FEATURES Boolean True

(4) EVENT_DUP_ROADWAY_EVENTS_WITH_NO_FEATURES_CANT_MATCH Boolean False

(5)EVENT_DUP_EVENT_WITH_FEATURE_CANT_MATCH_ROADWAY_EVENT_WITHOUT_FEATURE Boolean True

(6) EVENT_DUP_INCOMPAT_FEATURES_CANT_MATCH Boolean True

(7) EVENT_DUP_MAX_MILEPOST_DELTA_MILLI_MILES_FOR_MATCH Integer 400

(8) EVENT_DUP_AVG_UNSPECIFIED_PROXIMITY_MILLI_MILES Integer 300

3.8.4.1 Event Duplication Properties for Direction

There are two properties pertaining to direction: Property (1) EVENT_DUP_COMPARE_DIRECTION and Property (2) EVENT_DUP_EVENT_WITH_DIR_CANT_MATCH_ROADWAY_EVENT_WITHOUT_DIR. These are described in Table 3-X2 (see below for how to read the table). Property (1) determines whether direction is considered at all in comparing event locations. If it is false, the value of Property (2) does not matter (hence there is an “X” for Property (2) in the last line of the table).


Property (2) says, if we are comparing direction, can an event with no direction specified ever be considered as a duplicate of an event with a direction?

How to read the table: Possible values for Property (1) are specified in the first column headed “Prop (1)”. Possible values for Property (2) are specified in the second column headed “Prop (2)”. The recommended setting (True for Prop 1, False for Prop 2) is shaded. Two event locations are listed in the shaded header rows near the top. Both events have the same intersecting data (“@ MD 32”). The body of the table indicates how the two events would be compared given the values to the left for properties 1 and 2. For example, if Property 1 is true and Property 2 is false (the recommended setting, the shaded line), an event at “I-95 N @ MD 32” would compare as NOT EQUAL (!=) to an event at “I-95 S @ MD 32” but the event comparison is the three rightmost columns, such as “I-95 @ MD 32” versus “I-95 @ MD 32” in the rightmost column would compare as equal (==). (In fact note that, no matter what the settings of these two properties, these two events in the rightmost column always compares as equal (==). Any two events which compare as equal (==) will generate a Duplicate Event Alert. Of course, the two event types have to be comparable as configured in the System Profile event comparison matrix which can be configured in the GUI.

Table 3–X2. Event Comparison System Profile Properties for Direction

Prop (1) EVENT_DUP_COMPARE_DIRECTION

Prop.

(1)

Prop (2) EVENT_DUP_EVENT_WITH_DIR_CANT_MATCH_ROADWAY_EVENT_WITHOUT_DIR

Prop. (2)

Event 1: I-95 N I-95 N I-95 N I-95

Event 2: I-95 S I-95 I-95 N I-95

(both events): @ MD 32 @ MD 32 @ MD 32 @ MD 32

T T != != == ==

T F Recommended != == == ==

F X == == == ==

3.8.4.2 Event Duplication Properties for Intersecting Features

There are four properties pertaining to direction: Property (3) EVENT_DUP_COMPARE_FEATURES, Property (4) EVENT_DUP_ROADWAY_EVENTS_WITH_NO_FEATURES_CANT_MATCH, Property (5) EVENT_DUP_EVENT_WITH_FEATURE_CANT_MATCH_ROADWAY_EVENT_WITHOUT_FEATURE, and Prop-erty (6) EVENT_DUP_EVENT_WITH_DIR_CANT_MATCH_ROADWAY_EVENT_WITHOUT_DIR. These are described in Table 3-X3 (see below for how to read the table). Property (3) determines whether intersecting features are considered at all in comparing event locations. If it is false, the value of the other three properties do not matter (hence there is an “X” for those properties in the first line of the table). Property (4) says, if we are comparing intersecting features, can an event with no intersecting feature specified ever be considered as a duplicate of another event with no intersecting feature specified? Property (5) is similar. It says, if we are comparing intersecting features, can an event with no intersecting feature specified ever be considered as a duplicate of another event which does have an intersecting feature specified? Property (6) says, if we are


comparing intersecting features, should events with incompatible features (an intersecting road vs. a milepost, or a state milepost vs. a county milepost) ever be considered as duplicates?How to read the table: Possible values for Property (3) are specified in the first column headed “Prop (3)”, possible values for Property (4) are specified in the second column headed “Prop (4)”, and so on. The recommended setting (True for Props 3, 5, and 6, False for Prop 4) is shaded. Two event locations are listed in the shaded header rows near the top. Both events have the same primary route (“I-95 N”). The body of the table indicates how the two events would be compared given the values to the left for properties 3 through 6. For example, if Properties 3, 5, and 6 are true and Property 4 is false (the recommended setting, the shaded line), an event at “I-95 N @ I-395” would compare as NOT EQUAL (!=) to an event at “I-95 N” but the event comparison is the two leftmost columns, such as “I-95” versus “I-95” in the leftmost column would compare as equal (==). Any two events which compare as equal (==) will generate a Duplicate Event Alert. Of course, the two event types have to be comparable as configured in the System Profile event comparison matrix which can be configured in the GUI.

Table 3–X3. Event Comparison System Profile Properties for Features

Prop (3) EVENT_DUP_COMPARE_FEATURES

Prop (3)

Prop (4) EVENT_DUP_ROADWAY_EVENTS_WITH_NO_FEATURES_CANT_MATCH

Prop (4)

Prop (5) EVENT_DUP_EVENT_WITH_FEATURE_CANT_MATCH_ROADWAY_EVENT_ WITHOUT_FEATURE

Prop (5)

Prop (6) EVENT_DUP_INCOMPAT_FEATURES_CANT_MATCH

Prop (6)

(both): I-95 N I-95 N I-95 N I-95 N I-95 N* I-95 N*

Evt 1: @ I-395 @ I-395 @ I-395 @ I-395 @ I-395

Evt 2: @ I-395 @ MD 32 @ mp 53 @ mp 7

F X X X == == == == == ==

T F F F == == == != == ==

T F F T == == == != != !=

T F T F == == != != == ==

T F T T Reco. == == != != != !=

T T F F == != == != == ==

T T F T == != == != != !=

T T T F == != != != == ==

T T T T == != != != != !=

* I-395 really is at milepost 53 (close – it is exit 53). I-395 is not near milepost 7. Note event comparison software treats these two cases the same – either they both match or they both don’t match.

3.8.4.3 Event Duplication Properties for Distance


There are two properties pertaining to direction: Property (7) EVENT_DUP_MAX_MILEPOST_ DELTA_MILLI_MILES and Property (8) EVENT_DUP_AVG_UNSPECIFIED_PROXIMITY_MILLI_ MILES. These are described in Table 3-X4 (see below for how to read the table). Property (7) specifies the maximum distance (in thousandths of a mile, “milli-miles”) by which two traffic events can be separated and still be considered duplicate events. The recommended value is 400 (0.4 miles, 4 tenths of a mile). This works in conjunction with Property (8) which specifies the distance (in milli-miles) to consider a traffic event away from an intersecting feature (Road or Milepost) if the traffic event is “prior to”, “past”, “north of”, “east of” (etc.) its feature. The recommended value is 300 (0.3 miles). This suggests that if an event is, for example, “north of” milepost 53 it is considered to be at milepost 53.3. With Property (7) set to 400, an incident “north of” milepost 53 would be considered to be a duplicate of an incident “at” milepost 53 (because 53.3 – 53.0 = 0.3 = 300 milli-miles, less than 400. However an incident “north of” milepost 53 would NOT be considered to be a duplicate of an incident “south of” milepost 53 (because 53.3 – 52.7 = 0.6 = 600 milli-miles, greater than the maximum of 400 milli-miles).

How to read the table: Possible values for Property (7) are specified in the first column headed “Prop (7)”, and possible values for Property (8) are specified in the second column headed “Prop (8)”. The recommended setting (400 for Prop 7 and 300 for Prop 8) is shaded. Two event locations are listed in the shaded header rows near the top. Both events have the same primary route (“I-95 N”). The body of the table indicates how the two events would be compared given the values to the left for properties 7 and 8. The number is the distance between the events which would be computed using Property (8), followed by an indication of whether the two events would be considered equal (==) or not equal (!=). Examples analogous to the two examples given in the previous paragraph are shown in the shaded row, in the middle column (AT 53 vs. PST 53) and the last column (PRI 53 vs. PST 53). Any two events which compare as equal (==) will generate a Duplicate Event Alert. Of course, the two event types have to be comparable as configured in the System Profile event comparison matrix which can be configured in the GUI.

Table 3–X4. Event Comparison System Profile Properties for Distance

Prop (7) EVENT_DUP_MAX_MILEPOST_DELTA_MILLI_MILES

Prop (7)

Prop (8) EVENT_DUP_AVG_UNSPECIFIED_PROXIMITY_MILLI_MILES

Prop (8)

(both): I-95 N I-95 N I-95 N I-95 N I-95 N I-95 N I-95 N

Event 1: AT 53 AT 53 AT 53 AT 53 AT 53 PRI 53 PRI 53

Event 2: PRI 52 AT 52 PST 52 PRI 53 AT 53 PST 52 PST 53

0 3001300!=

1000!=

700!=

300!=

0==

400!=

0!=

0 01000

!=1000

!=1000

!=0

==0

==1000

!=0

==

400 300 Reco.1300

!=1000

!=700

!=300

==0

==400

==600

!=


700 3001300

!=1000

!=700

==300

==0

==400

==600

==

1000 3001300

!=1000

==700

==300

==0

==400

==600

==

1000 01000

==1000

==1000

==0

==0

==1000

==0

==

Event 2a*: I-95 SPST 52

I-95 SPST 52

I-95 SPST 52

I-95 SPST 52

I-95 SPST 52

I-95 SPST 52

I-95 SPST 52

* If EVENT_DUP_COMPARE_DIRECTION is false, Event 2a is equivalent to Event 2, so Event 2a compared to Event 1 would have the same results as Event 2 compare to event 1. (It’s just that Event 2a is specified as a southbound event, and Event 2 is specified as northbound.)

Note: Mileage offsets cannot be computed for events “PRIOR TO” or “PAST” a feature if roadway direction is not specified.

Note: Intersecting features for all events listed in this table are state mileposts. (Or they could be county mileposts, but both events must have the same type of milepost in order to be comparable.)

3.8.5 FMS Port ConfigurationThe Port Configuration Utility is used to set the configuration of communications ports on FMS Servers. The Port Configuration Utility is located in the CommService installation directory and is activated by running PortConfigUtility.cmd on the FMS Server. Port Configurations are stored in files with an .xml extension. The default name of PortConfig.xml is usually used. These files are ASCII XML files which can be carefully edited by a technician experienced with XML files, but it is preferred that the Port Configuration Utility described here always be used for safety.

Use the File menu to select a configuration file (Figure 3-1). The configuration file is specified in the CommService.props file and defaults to PortConfig.xml. After selecting a configuration file a list of ports is displayed (Figure 3-2). To edit an existing entry select the entry and either right-click or use the Edit menu item. A pop-up menu will appear with options to add direct connections, POTS modems, ISDN modems, Telephony (Voice) Ports, edit the selected entry, or delete selected port.

Editing an entry or creating a new entry will display a window similar to those shown in Figure 3-3. To edit an entry, simply modify the fields as desired. For new port entries enter a name to identify the port, check the Port Enabled box to enable the port, and then specify the system device name for the port (e.g. COM1). It is recommended that the system device name be used for the port name to avoid confusion (e.g. system device COM1 is given port name COM1). For the modems you will also need to enter the modem initialization string (see below) and the modems connect timeout (the length of time in minutes the modem will wait for a connection to be established after dialing). Use care in entering the initialization strings to make sure that the number zero (0) is not entered as the letter O.


Figure 3–1. Port Configuration Utility

Modem Initialization Strings: Eicon ISDN ATE0Q0V1+ip6 POTS (Addco & PCMS DMSs) AT&F0E0Q0V1F4&K0&Q4+MS=1,0,300,1200 POTS (High Speed) AT&F0E0Q0V1When you have finished setting the port configurations make sure you use the File menu to save your changes before exiting the application.

Changes to the port configurations will not take effect until the CommService is restarted.


Figure 3–2. Port Configuration List

Figure 3–3. ISDN, POTS and Voice Port Configuration


3.8.6 Device ConfigurationThis section describes the steps necessary to establish valid device configurations. Details on using the CHART GUI to define devices are presented in the CHART User’s Guide.

3.8.6.1 DMS Devices

To add a DMS to the CHART system and configure it for use, the administrator uses the DMS Properties dialog. Prior to bringing up the DMS Properties dialog, the administrator should gather the information on the sign characteristics and communications parameters needed to configure the device. Appendix D contains a form that can be used to record the information.

3.8.6.2 TSS Devices

To add a TSS device to the CHART system and configure it for use, the administrator uses the TSS Properties dialog. Prior to bringing up the TSS Properties dialog, the administrator should gather the information on the device characteristics and communications parameters needed to configure the device. Appendix D contains a form that can be used to record the information.

Note that a TSS device in maintenance mode will continue to be polled, unlike message devices such as a DMS. To stop polling of a TSS device set the device to offline.

3.8.6.3 HAR Devices

To add a HAR device to the CHART system and configure it for use, the administrator uses the HAR Properties dialog. Prior to bringing up the HAR Properties dialog, the administrator should gather the information on the device characteristics and communications parameters needed to configure the device. Appendix D contains a form that can be used to record the information.

3.8.6.4 SHAZAM Devices

To add a SHAZAM device to the CHART system and configure it for use, the administrator uses the SHAZAM Properties dialog. Prior to bringing up the SHAZAM Properties dialog, the administrator should gather the information on the device characteristics and communications parameters needed to configure the device. Appendix D contains a form that can be used to record the information.

3.8.6.5 Video Devices

To add a Video device to the CHART system and configure it for use, the administrator uses the Add Camera, Monitor, Monitor Group, Command Processor, Video Fabric, Video Switch, or Bridge Circuit dialog. Prior to configuring the video configurations, the administrator should gather the information on the device characteristics and communications parameters needed to configure the device. Appendix D contains a form that can be used to record the information.

3.8.7 Attention Server Users configurationThis instruction assumes the Attention software has already been setup and a “Fake Paging Service” has been created. Instructions to setup the Fake Paging Service are in step 6.


1. Log on to the server hosting Attention at the console.

2. Create Targets / Individuals by selecting from the menu Setup => Users => Targets.

a. Click the “New” buttonb. Type in the “Target Name” - Last Name, First (Organization Office) device

type (if multiple listings) Example Smith, Joe (SHA CHART) emailc. In the comment section enter the service provider (MdTA includes this for

their contacts).d. In the Pager section click the “Service” drop down and select the previously

created fake page servicee. Type 1111 to the “PIN” field of the Pager section.f. In the Email section, type in the e-mail address to use into the “Internet” fieldg. Click the “Rights” button and check the boxes for the access rights for this

Target (normal targets for the CHART list DO NOT need any rights assigned)h. Click the “Save” button to save this new Target


3. Create Actions by selecting from the menu Setup => Actions. You will need an Action for every Target defined in the System.

a. Type in the “Action Name”. The actions are what will be used by the system to send notifications. This “Action Name should match the “Target Name” already entered in Step 2 b.

b. Click and drag the “Send Mail” icon to the right half of the dialog box.c. Double click on the mailbox / “Mail” to bring up another dialog box


i. For the “Mail Protocol” select “SMTP (Internet)”ii. For the “Send To” drop down, select the previously created Target

iii. For the “Subject”, clear out the default text and put a single spaceiv. For the “Message”, type in the text “<message>”. v. Click the “OK” button

d. Click the “Save” button to save the new action

4. In a web browser, login to the Attention! Web Console by going to http://<attentionservername>:81/attention and login with the CHARTNS account. This step will enable all the new Targets and Actions to make them usable by CHART. Also, this step shows how to create distribution lists.

a. To enable the new objects click the link for Attention! Contact Centeri. From the menu click the Admin => Enable Targets

1. Click the “Enable All” button2. Click the “OK” button

ii. From the menu click the Admin => Enable Actions1. Click the “Enable All” button2. Click the “OK” button

b. To create distribution lists, click the Setup => Distribution Lists from the menu. IMPORTANT NOTE – All distribution lists are accessible only by the user that created them. Therefore it is extremely important that all distribution lists that are to be used by CHART should be added from the CHARTNS account. The account will be the same account that the CHART Notification service uses to log in.

i. Click the “add a new list” linkii. Type in a descriptive “List Name”

iii. Click “Members” and go to the Find Actions text field and put a “%” to get all off the Actions and click the “Go” button. You can also add existing lists to this new distribution list.

iv. Select all of the Actions and / or Lists to add to this new Distribution List by clicking the check box next to their names.

v. Click the “close” button just below the Action text field. They should be added to the “Members” list now.

vi. Click the “Save” button5. To activate newly entered Targets in CHART you may either wait approximately 10

minutes for an automatic update or do a Perform Discovery from the Administration menu.

6. Create a “Fake Paging Service” by selecting from the menu Setup => Pagers. This is necessary to define Targets / Individuals.


a. Click the “New” buttonb. Type in the “Pager Name”c. Select a protocol from the protocol drop down list.d. Type in a “Host Name”, the name of the server should be fine.e. Click the “Save” button to save the new paging service


3.9 Database Operations and MaintenanceThis section provides information for a CHART Database Administrator (DBA) to facilitate administration of the CHART databases.

3.9.1 EnvironmentCurrently, the development DBA works remotely from the Network Operations Center (NOC). All instructions are assuming a local environment at the SOC or AOC. Tables 3-4 through 3-8 provide information regarding the CHART Oracle operational environment. The tables provide the following information:

Table 3-4 contains minimum software requirements for the Oracle Enterprise Manager workstation.

Table 3-5 contains minimum software requirements for the CHART Oracle database servers.

Table 3-6 identifies the CHART Oracle databases. Table 3-7 provides the Oracle user logins for each of the databases listed in Table 3-7. It

also lists Windows accounts used by Oracle to run Enterprise Manager jobs as listed in Section 3.9.7.

Table 3-8 lists Oracle tools referenced within this document and provides a brief description.

Table 3–4. Client EnvironmentClient Description

Oracle Enterprise Manager Server The name of this server is NOCOEM. It is currently located in the Network Operations Center (NOC) and is used to schedule and run all Oracle jobs. This workstation contains the following software:

Oracle 10g Database Enterprise Edition (Database: EMREP)

Oracle Enterprise Manager 10g

The CHART application runs in a multi-server, multi-database environment. Tables 3-6 and 3-7 describe the CHART databases and database servers. The SOC server hosts the master CHART application database as well as the Interim Archive database. The remaining servers host slave CHART application databases. Installation of each of these three types of databases (archive, master, and slave) is presented in Appendix A.


Table 3–5. Server EnvironmentServer Description

Database Servers The name of the CHART database servers are: HANOVERCHART1 (located at the SOC) AOCCHART2 (located at AOC) GREENBLTCHART1 BROOKD4CHART1 ANNAD5CHART1 PGTRIPCHART1 FREDLECCHART1 EASTONMWCHART1

The following Oracle software must be installed prior to installation of the CHART databases:

Oracle 10g Database Enterprise Edition Oracle Enterprise Manager Agent

Table 3–6. CHART DatabasesDatabase Name Description

C2SOC3 CHART operational database which resides on the database server at the SOC.

C2AOC3 CHART operational database which resides on the database server at the AOC.

C2ARCH3 CHART Interim Archive database which resides on the database server at the SOC.

EMREP Enterprise manager database that resides in the NOC on a workstation called NOCOEM.

C2D5AN CHART operational database which resides on the database server at District 5, Annapolis.

C2D4BR CHART operational database which resides on the database server at District 4, Brooklandville.

C2LEC CHART operational database which resides on the database server at the Frederick LEC.

C2D3GR CHART operational database which resides on the database server at District 3, Greenbelt.

C2TRIP CHART operational database which resides on the database server at the PG Trip Center.

C2MWEST CHART operational database which resides on the database server at the Easton Microwave Facility.


The SOC CHART application and database server (HANOVERCHART1) houses the Archive database stored on a SAN via the H:\ partition.

All CHART application and database servers are configured with disk storage arrays protecting the local C:\ and D:\ partitions. Some of these servers also have an unprotected E:\ drive for additional disk space to hold database backups.

At the SOC, the CHART application, Oracle software (On D:\ drive), and the CHART database is installed on the SAN H:\ partition. This will provide redundancy and fail-over capability in the event of either a server or disk failure at the SOC, with no single-point of failure. On the other CHART servers, the CHART application, Oracle software, and the CHART databases are installed on the D:\ partition.


Table 3–7. CHART Database User IDsPre-configured Oracle User Accounts and OS Accounts

Username DescriptionDBSNMP Automatically created during database creation phase. Used by the

Oracle Intelligent Agent.SYS Automatically created with the database and is highest privileged

user in database.ORACLE_BACKUP Windows user account on the database servers. This account is used

to perform all OEM-related maintenance on all database servers.OUTLN Automatically created during database creation phase.SYS Automatically created with the database and is highest privileged

user in database.SYSMAN Oracle Enterprise Manager schema ownerSYSTEM Automatically created with the database and has DBA privilege.

CHART Application Operational DatabasesUsername Description

ARCHIVE CHART user for archiving data.CH2DBA CHART schema owner.ALERTSERVICE CHART user for the CHART Alert ServiceCHARTLITESERVICE CHART user for the CHART GUI applicationDMSSERVICE CHART user for the CHART-DMSService serviceHARSERVICE CHART user for the CHART-HARService serviceMESSAGEUTILITYSERVICE CHART user for the CHART-MsgUtilityService serviceNOTIFICATIONSERVICE CHART user for the CHART NotificationService serviceREPADMIN CHART replication administrative user for administering the

replication environment.REPPROXY CHART replication propagation user for performing the replication

between databases.REPORT CHART user for performing ad-hoc queries. This user has select

privileges on all tables in CH2DBA schema.RMAN_ADMIN CHART user for performing all OEM-related maintenanceROADWAYLOCATIONLOOKUPSERVICE CHART user for the CHART- RoadwayLocationLookupServiceSCHEDULESERVICE CHART user for the CHART ScheduleService serviceTRAFFICEVENTSERVICE CHART user for the CHART-TrafficEventService serviceTSSSERVICE CHART user for the CHART-TSS serviceUSERMANAGEMENTSERVICE CHART user for the CHART-UserManager serviceVIDEOSERVICE CHART user for the CHART-Video service

C2ARCH3 Interim Archive DatabaseUsername Description

ARCHIVE CHART Interim Archive user for performing nightly archival from


Pre-configured Oracle User Accounts and OS AccountsUsername Description

the operational databases.ARCHIVE_USER CHART Interim Archive user for performing ad-hoc queries. This

user has select privileges on all tables in CH2DBA schema. CH2DBA CHART schema owner. It is also used for loading TSS data.RMAN_ADMIN CHART user for performing all OEM-related maintenance

EMREP Enterprise Manager DatabaseUsername Description

SYSMAN Oracle Enterprise Manager 10g schema owner.RMAN_ADMIN CHART user for performing all OEM-related maintenanceRMAN Recovery Catalog schema. This schema contains the Backup and

Recovery information for all databases.

NOTE: All databases contain user RMAN_ADMIN which is used to perform all OEM-related database maintenance tasks.


Table 3–8. Oracle ToolsTool Name Description

Oracle Enterprise Manager 10g Console

Enterprise manager Graphical User Interface (GUI) that provides the capability to centrally manage databases.

RMAN Oracle recovery manager utility that provides the capability to backup and recover Oracle databases.

Replication Manager Enterprise manager GUI that provides the capability to manage the replication environment.

Security Manager Enterprise manager GUI that provides the capability to manage users, roles, and privileges within a database.

Storage Manager Enterprise manager GUI that provides the capability to manage tablespaces and datafiles within a database.

3.9.2 Routine Database Maintenance OperationsMaintenance of the databases will be primarily performed through the Enterprise Manager tool located on workstations in the Network Operations Center (NOC), Hanover facility. All database management, except database recovery, will be performed with this management tool.

3.9.3 Databases Maintenance TasksThe NOCOEM server schedules and runs all maintenance tasks for the databases. All database maintenance scripts are designed to run from command shell with detailed usage descriptions. This allows the scripts to be executed independently of Oracle Enterprise Manager console if it is not available or cannot be quickly restored. It also allows the scripts to be used as needed on any servers.

The entire scripting structure resides in a folder called C:\OraScripts\. The breakdown of the directory structure is as follows:

\backup\ - contains scripts to perform backup of the databases using RMAN and export

\bin\ - contains all environment setup scripts, common subroutines, and utilities. Note that GZIP compress format is used throughout the entire database maintenance environment whenever possible to reduce the size of the backup files, including the export dump file. Use the GZIP utility here to uncompress files.

\catalog\ - contains scripts to setup RMAN catalog, this is a one-time setup only

\jobs\ - contains job scripts that perform occasional but not scheduled tasks

\log\ - temporary staging folder for various log files generated by job scripts

\maintain\ - job scripts that perform various database maintenance tasks

\temp\ - temporary folder

\TSS\ - scripts to perform TSS raw data loading into C2ARCH3 database


All scripts contain a common structure to display full usage instructions if no parameter is passed in. Simply type the script name in a command shell to display usage information.

3.9.4 Database Backup SetThe 10g database backup set is designed to provide maximum protection for the SHA CHART databases. Backup sets are located under:

- \Oracle\oradata\backup\{Date}\{SID}\RMAN\: RMAN backup set

- \Oracle\oradata\backup\{Date}\{SID}\export\: full database export, resulting file is compressed with GZIP to reduce space consumption

Inside the RMAN backup set the DBA will find not only all required database files and archived logs for recovery, but also the entire set of critical Oracle internal/external configuration files which are required to rebuild a database, including:

CONTROLFILE{Date}.CTL: backup of control file CONTROLFILE{Date}.SQL: converted SQL script to re-create control file DataFileLocation_{SID}.txt: output showing all data filenames and locations DBid_{SID}.txt: database ID init{SID}.ora: database init file listener.ora/tnsnames.ora/sqlnet.ora: network configuration files LogFileLocation_{SID}.txt: redo log filenames and locations PWD{SID}.ora: database external password file SPFILE{SID}.ORA: server parameter file \ChangeDrive\RMANChangeDriveScript_For_{Drive Letter}.sql: contains pre-generated

scripts to restore database to any drive letter(c-z) than the one the backup set was taken from. This is explained in details later in the database recovery procedures


3.9.5 Format of Job Identifier on OEM ConsoleAll OEM database maintenance tasks are scheduled as "Host command" in the OEM job library and follow the common naming convention:

{Exact time the job will run - in 24-hour notation}{D=Daily, W=Weekly, M=Monthly, Y=Yearly, "ONCE")

{Day to run (For weekly jobs)}{Type of job}

{Sub-Type of job (If any)}{Database server name on which the jobs will be run}

{Database SID name the jobs will be run on}{Initials of the job creator}

Examples

1240D_BACKUP_RMAN_HANOVERCHART1_C2SOC3_TK{Job will run at 12:40am}

{Job will run every night (Daily)}{Job type is to run backup}

{Job sub-type is using RMAN to run backup}{Database server name is HANOVERCHART1}

{Database name is C2SOC3}{Initials of the job creator are T. K.}

0130W_SUNDAY_REBUILD_INDEX_HANOVERCHART1_C2SOC3_TK{Job will run at 1:30am}

{Job will run weekly on every Sunday}{Job type is to rebuild indexes}

{Database server name is HANOVERCHART1}{Database is C2SOC3}

{Initials of the job creator are T. K.}

ONCE_DEL_ARCHIVED_LOG_HANOVERCHART1_C2SOC3_TK{Job will only be run as needed - not scheduled}

{Job type is to remove old archived logs}{Database server name is HANOVERCHART1}

{Database is C2SOC3}{Initials of the job creator are T. K.}


3.9.6 CHART Maintenance Tasks

Check OEM job status and database backup sets: From OEM console, go to Jobs, Activity, check for jobs with status "Problems" or "Running". Also, a job is not necessarily completed successfully if the status is "Succeeded". This is a limitation of the host command format in OEM job library. To ensure that backup process completed successfully, you must check all the backup logs by clicking the Status column for the job, then click Command Step to view the process. Also, it is recommended that a DBA checks the physical backup directories to make sure all database files were backed up properly since backup errors vary. All backup files are located under {Drive}:\oracle\oradata\backup\{Date}\{SID}\

Check replication job: From OEM console, go to Jobs, Activity, under Name, enter "%replication%", Status "Succeeded", max dates reflect the most current replication. If the dates are not current it means the replication jobs were not completed successfully. Follow the procedures below to fix the problem:

- select job,what,broken from user_jobs; - Find all jobs with status "Y" and execute the query for each of them: - exec dbms_job.broken(&jobno,FALSE); - commit;- Re-execute all replication jobs:- exec call_complete_refresh_CL_JOB;- exec call_complete_refresh_C2_JOB;- exec call_complete_refresh_Clog_JOB;- exec call_complete_refresh_VS_JOB;

Check archive process log. The log file is located on HANOVERCHART1 at: H:\oracle\admin\c2arch3\exp\ARCHIVE.log

Check TSS raw data file load: From OEM console, go to Jobs, Activity, under Name, enter "%tss%", and examine the log. If TSS raw data load fails then there will be a file on HANOVERCHART1 called H:\Oracle\Oradata\BACKUP\TSSRawData\ERROR_ErrorOccurred.log. This file is an indication that a previous load was unsuccessful so that the script will not attempt to run anymore subsequent loads. This is to prevent data corruption in situations where a load might fail on the weekend and the script continues to load subsequent data for the remaining days. If this file is present, you must correct the problem and DELETE THE FILE otherwise the TSS raw data load job will not run.

To correct TSS raw data load problem, examine all error log files (*.bad, *.discard, error*, *.log) on HANOVERCHART 1 in H:\oracle\oradata\backup\TSSRawData\{yesterday’s date} loaded\. After correcting the problematic TSS raw data file, delete the directory H:\oracle\oradata\backup\TSSRawData\{yesterday’s date} loaded\. Then reload all missing TSS raw data files from D:\Program Files\CHART R3B2.06 \bin\TSSService\


RawData\ using the syntax: C:\orascripts\tss\loadtss {TSS data filename only} c2arch3 c h d. Carefully check results of each load.

Database backup for SQL databases (Attention!):SQL Server database was loaded in two servers with the failover capability, Database backup will be performed on Server (one) and then it will be restored on Server (two). Server (two) will also be backup and will be stored on H: (SAN) Drive, hence it will be copied on the tape library.


3.9.7 Database Maintenance Task Schedule

Daily Jobs 12:05am - c:\orascripts\TSS\loadYesterdayTSSfile.bat: load yesterday's TSS raw data file 12:20am - c:\orascripts\maintain\analyze.bat: analyze statistics for the specified schema 12:30am - archive process. Not scheduled through OEM. This is scheduled as an internal

database job 12:40am - c:\orascripts\backup\rman\rman_backup.bat: backup database using RMAN 12:40am - c:\orascripts\backup\export\fullexp_gzip.bat: export entire database and GZIP the

export file 03:30am - c:\orascripts\maintain\delete_arc_log.bat: remove archive logs on an interval (rotate) 03:45am - c:\orascripts\maintain\rmbackup.bat: remove backup sets on an interval (rotate) 03:55am - c:\orascripts\maintain\check_rep.bat: check if replication is completed on c2soc3

database

Weekly Jobs 05:30am (Sunday) - c:\orascripts\maintain\rebuild_index.bat: rebuild all available indexes for a

specified schema 07:00am (Sunday) - c:\orascripts\maintain\rotate_listener_log.bat: archive and compress listener

log file (rotate)

3.9.8 Attention Database Maintenance (SQL Server) Task ScheduleDaily Jobs (HANSOC-PAGING)

01:00am - C:\ Attention_jobs\attentionsoftware.bak. : Backup to local drive 01:30am - C:\ Attention_jobs\maintain\ Backup_on_HDrive.BAT_ backup copy for SAN

Daily Jobs (grnbltweb1) 01:30am - C:\ Attention_jobs\ Restore_attention_Step1.BAT. : Restore Database on server

Daily Jobs (Hanoverchart1) 02:30am - C:\ Attention_jobs\ CopyFromPrimaryServerToHDrive.bat. : Copy to SAN

3.9.9 Manual SQLServer Database Restore from HANSOC-PAGING -> GRNBLTWEB1

Procedure to perform backup from HANSOC-PAGING (Primary Attention Site)

1. Login to HANSOC-PAGING [170.93.51.128] as a domain administrator account.

2. Go To Scheduler task screen

3. Pickup the task Primary_Server_backup, right click and select Run to execute it immediately.

4. This will put the backup on C:\backup\attentionsoftware.bak.

5. Verify the date and time for the file.


Procedure to perform restore on GRNBLTWEB1(Secondary Attention Site)

6. Login to grnbltweb1 [ 170.93.150.234 ] as a domain administrator account.

7. Go To Scheduler task screen

8. Pickup the task Restore_attention_Step, right click and select Run to execute it immediately.

9. After few minutes, system will restore the database.

10. Log file will be generated on c:\backup\GrbBltRestore_log.log

3.9.10 Open the file and goto end-of-file, Last entry will be the restore_logs. Database Recovery Procedures

The CHART OEM jobs running on each CHART server are configured to complete a full RMAN and export backup of the server’s CHART database(s) nightly. In addition, Oracle archive and redo logs are maintained on the server. Backups are maintained and rotated to allow for a long weekend. Finally, a tape backup is configured to run nightly backups of each CHART server. This configuration will support the following recovery requirements:

Automatic recovery of the database to the last committed transaction should the server properly or improperly re-boot, assuming no corruption of the data files on the server

Full recovery to the last committed transaction, assuming no corruption of the data files on the server

Recovery to the previous night’s tape backup if the data files on the server are corrupted or otherwise unavailable

Weekend recovery requirements are same as during the week with the following exception:

o If the backups jobs consistently fail for any reason over the weekend, recover to the last verified backup… the backup from the night before the last business day prior to the weekend (normally Thursday night’s backup)

3.9.10.1 Recovery Scenarios

Each database site can have the following types of failures: Data Corruption Disk Failure Server Failure Site Disaster Failure

The following recovery scenarios will be considered for each type of database site failure.

- Data Corruption Recovery – In this scenario the database has a corrupted datafile, but the control files, archive logs, redo logs are not corrupt. Recovery will require the backup


database files plus the archive and redo logs still available on the database server to bring the database up to the last successful transaction.

- Server Recovery – In this scenario, all database files are corrupt or otherwise not available (e.g., due to disk failure). Recovery will require the backup database files from a backup stored off server, if one is available, or a backup from the tape. Server recovery can only recover data up to the last successful and available backup. Data entered since the last backup will be lost.

- Site Disaster Recovery – In this scenario, the site has been lost due to catastrophe and the system will need to be recovered to an alternate site. Recovery will require the backup database files from a backup stored off site, if one is available. Site recovery can only recover data up to the last successful and available backup. Data entered since the last backup will be lost.

For the recovery scenarios, database recovery procedures are the same for all databases. This is because the RMAN backup and recovery scripts/procedures are designed to take advantage of backup sets plus any available log files for all databases. Depending on the recovery scenario, recovery will be to the last available backup or to the last successful transaction.

At this time, there is limited support for Site Disaster Recovery and backups are not stored off-site. If the server drives are made available and the backups can be extracted from them, then a restore using the procedures below to a different server can be performed. A site disaster will result in degraded operations for CHART.

Note that in order for Oracle to be able to locate the backup set, the drive letter and directory of the backup set during the restore process must be the same as the one the backup set was taken from. If you are restoring the database onto the same server, then make sure the directory contains the backup set. If you are restoring the database onto a different server, then make the backup set available on the same drive letter and directory on that server. Since it may not be possible to have the same drive letter on the destination server as the origin server, one way to emulate the same drive letter is to utilize an external USB drive:

Copy the database backup set onto the USB drive Insert USB drive into the server to restore the database to Go to Start, Settings, Control Panel, Administrative Tools, Computer Management,

Storage, Disk Management, at the lower panel, find the USB drive, right-click on it and select "Change Drive Letters and Paths"

There are two sets of recovery procedures for the databases, depending on the situations and the server resources available at the time of recovery:

Restore database back to the same drive letter as the backup directory and directory of the data files are unchanged

Restore database to a different drive letter than the one where backup set was taken and/or the destination directory of the data files are different

The procedures provided below assume a full database recovery, whether all of the database files are lost or not, as the procedures are the same in all cases.

3.9.10.2 Database recovery to the same drive/directory


NOTE: This procedure works for any database restore since all database backup sets are created with a common directory hierarchy.

Copy init.ora file and password file from the backup set to the Oracle codetree $ORACLE_HOME\database\ directory. Also you must configure listener.ora and tnsnames.ora for the restored database instance before proceeding

If restoring to a different server, create the Windows service for the database SID: oradim -NEW -SID {SID} -startmode auto -pfile {path and filename for init.ora} Windows will start the service for you immediately after you created the service go to Services and stop the Oracle service for the new database instance Create \oradata\{SID}\archive directory on the new server Create all admin directories such as \oracle\admin\{SID}\bdump, cdump...etc Log into RMAN: (DO NOT CONNECT to RMAN catalog) rman target rman_admin@{SID} nocatalog RMAN> startup nomount; Retrieve the database ID of the database by looking at the DBid.txt file in the backup set.

Set the database ID and restore the control files and the SPFILE. Do not use “restore controlfile from autobackup” since RMAN will only look back 7 days to find the autobackup file

RMAN> SET DBID {Database ID}; Locate the filename of the control file auto backup from the backup set; the filename will

look like "AUTOCTLFILEC-???????????" RMAN> Restore controlfile from '{Backup set path}\AUTOCTLFILEC-??????????’ RMAN> RESTORE SPFILE FROM '{Backup set path}\AUTOCTLFILEC-????????’ Restart instance with the SPFILE: RMAN> shutdown immediate; RMAN> startup mount; Turn autobackup for controlfile off otherwise it will create unnecessary copies to the

backup directory: RMAN> CONFIGURE CONTROLFILE AUTOBACKUP OFF; Check to make sure location of the backup set is correct by examining the variable

"CHANNEL DEVICE TYPE DISK FORMAT" by issuing the command: RMAN> show all; Make sure the backup set is available at the location shown above RMAN> restore database; RMAN> recover database; (NOTE: Ignore the warning message “RMAN-06054: media

recovery requesting unknown log”) RMAN> alter database open resetlogs; RMAN> CONFIGURE CONTROLFILE AUTOBACKUP ON; RMAN> exit; Add temp file. You can copy and paste the statement from the

"CONTROLFILE{Date}.SQL" included with the backup set. The "create temp file" statement can be located near the bottom of the file, e.g.:

SQL> ALTER TABLESPACE TEMP ADD TEMPFILE 'Temp file path and filename' SIZE 25165824 REUSE AUTOEXTEND ON NEXT 655360 MAXSIZE 32767M; If restoring to a new server, change the Windows database SID service to run SPFILE: SQL> create spfile from pfile;


Stop the Oracle service for the instance from Services panel Run “oradim -edit -sid {SID} -spfile” to change to run SPFILE Start the Oracle service for the instance from Services panel Verify that the restore database is running properly, then connect to RMAN catalog and

update the repository with the new database information. Refer to the Oracle Backup and Recovery Basics guide for details.

3.9.10.3 Database recovery to a different drive/directory NOTE: This procedure works for any database restore since all database backup sets are

created with a common directory hierarchy. Create \oradata\{SID}\archive directory in the destination drive Create all admin directories such as \oracle\admin\{SID}\bdump, cdump...etc in the

destination drive Copy init.ora file and password file from the backup set to the destination's Oracle

codetree $ORACLE_HOME\database\ directory. Also you must configure listener.ora and tnsnames.ora on the destination server before proceeding

Review the init.ora file included with the backup set and rename/create duplicated copies of the controlfile as necessary, e.g., control01.ctl

NOTE: Do not copy the control files to the oradata directory yet. Create a Windows service for the database SID: oradim -NEW -SID {SID} -startmode auto -pfile {path and filename of init.ora} NOTE: Windows will start the service for you immediately after you created the service. Stop the Oracle service for the newly-created instance Copy all the control files you created earlier into the \oradata\{SID}\ directory. Do not try

to restore control file from autobackup as the backup set location may or may not be accessible to RMAN

Start the Oracle service for the newly-created database instance Log into RMAN: (DO NOT CONNECT to RMAN catalog) rman target rman_admin@{SID} nocatalog RMAN> (Only if database is not mounted) alter database mount; (Note: 335683.1) Check to make sure location of the backup set is correct by examining the variable

"CHANNEL DEVICE TYPE DISK FORMAT" by issuing the command: RMAN> show all; Make sure the backup set is available at the location shown above Turn autobackup off RMAN> configure controlfile autobackup off; You are now ready to restore all datafiles to the new directory structure. The backup set

contains a set of scripts generated during the backup that you can use to restore datafiles to different drive letters.

If only the drive letter changes but the directory structure remains the same, simply select a script to be used.

If the directory of the destination server is different from that of the change drive letter scripts then edit the directories manually.

The change drive letter scripts are named "RMANChangeDriveScript_For_{Drive}.sql" located under the directory "ChangeDrive".


For example, if the new directory structure on the destination server is h:\oracle\oradata\{SID}\ then use the script "RMANChangeDriveScript_For_h.sql"

RMAN> @RMANChangeDriveScript_For_h.sql The script will exit RMAN, log into RMAN again. RMAN> recover database; (NOTE: Ignore the warning message “RMAN-06054: media

recovery requesting unknown log”) RMAN> alter database open resetlogs; Turn autobackup on: RMAN> CONFIGURE CONTROLFILE AUTOBACKUP ON; RMAN> exit; Add temp file. You can copy and paste the statement from the

"CONTROLFILE{Date}.SQL" included with the backup set. The "create temp file" statement can be located near the bottom of the file, e.g.:

SQL> ALTER TABLESPACE TEMP ADD TEMPFILE 'Temp file path and filename' SIZE 25165824 REUSE AUTOEXTEND ON NEXT 655360 MAXSIZE 32767M; Change the Oracle service for the database instance to run SPFILE: SQL> create spfile from pfile; Stop the Oracle service for the instance from Services panel Run “oradim -edit -sid {SID} -spfile” to change to run SPFILE Start the Oracle service for the instance from Services panel Verify that the restore database is running properly, then connect to RMAN catalog and

update the repository with the new database information. Refer to the Oracle Backup and Recovery Basics guide for details.


3.9.11 Database Objects

3.9.11.1 Storage Allocation

The basic storage allocation per database is divided into five major tablespaces; two for data, two for indexes, and one for Large Object (LOB) data and indexes. There is one tablespace for dynamic data and one for static data; the index tablespaces are also broken into dynamic and static.

Each tablespace name is prefaced with “CHART2” for the operational database and “C2ARCH3” for the interim archive; for example, CHART2_DATA and CHART2_STATIC_DATA.

Each tablespace lists the datafile name(s) where the data is stored. These datafiles correlate to the names found in the Enterprise Manager tool where the datafiles are maintained operationally. The scripts for creating the datafiles use the Oracle autoextend capability. The CHART2 databases also implement Oracle’s locally managed tablespaces. This means that the extent size for each tablespace is fixed, except for the System tablespace, which cannot be locally managed. The extent sizes are listed below in Tables 3–12 and 3–13. Some of the advantages of locally managed tablespaces are no fragmentation and the ability to handle substantially more extents than previous versions of Oracle with minimal to no performance hit.

Table 3–9. CHART Application Database TablespacesTablespace Purpose Extent Size

CHART2_DATA Table 3-2 data 128KB

CHART2_INDEX Table 3-2 indexes 64KB

CHART2_LOB_DATA HAR voice data 1000KB

CHART2_STATIC_DATA Table 3-1 data 64KB

CHART2_STATIC_INDEX Table 3-1 indexes 32KB

INDX Default index tablespace 32KB

RBS Standard Rollback 256KB

RBSBIG Archiving/Migration Rollback 1000KB

REPLICATION Replication objects 128K

SYSTEM Dictionary N/A

TEMP Sort space 1000KB

USERS Default data tablespace 128KB


Table 3–10. CHART Archive Database TablespacesC2ARCH3 Tablespace Purpose Extent Size

C2ARCH3_DATA Normal Event and Log data 4000KB

C2ARCH3_INDEX Normal Event and Log indexes 512KB

C2ARCH3_LARGE_DATA Rapidly growing Event and Log data

12000KB

C2ARCH3_LARGE_INDEX Rapidly growing Event and Log indexes

12000KB

C2ARCH3_STATIC_DATA Code table data 128KB

C2ARCH3_STATIC_INDEX Code table indexes 32KB

INDX Default index tablespace 32KB

RBS Standard Rollback 128KB

RBSBIG Archiving/Migration Rollback 1000KB

RCVCAT RMAN Repository 128KB

SYSTEM Dictionary N/A

TEMP Sort space 4000KB

USERS Default data tablespace 128KB

3.9.11.2 CHART R3B2 Overview

CHART R3B2 tables, using the DR3B2.06 schema consisting of 101 tables, are listed below in Table 3–11, R3B2 Static Tables and Table 3–13, R3B2 Dynamic Tables. New table names for R3B2 are bold and R3B1 tables modified for R3B2 are marked with ‘*’ in Tables 3-11 and 3-12 below. R3B1 table modifications for R3B2 include only additional columns being added.

The static tables contain the administrative data that are needed to set up the operational system. These data change infrequently. The volume estimates are based on the complete number of rows per entity required to store the CHART administrative data for the entire system. These data are pre-loaded.

Table 3–11. CHART Backend Service Static TablesNo. Table Name Expected Max Rows1. ALIAS 1002. BRIDGE_CIRCUIT 2003. CAMERA 5004. CAMERA_REGION_ENTRY 2005. CENTER 5006. CENTER_BACKUP_CENTER 15007. CH2_DICTIONARY 58. CODE_LIST 1009. CODE_LIST_ITEM 450


No. Table Name Expected Max Rows10. *CODEC 60011. CODEC_CONTROL_CONNECTION 20012. CODEC_VIDEO_CONNECTION 20013. COM_PORT_CONTROL_CONNECTION 5014. COMMAND_PROCESSOR_CONNECTION 5015. CONSTITUENT_HAR 316. DICTIONARY_WORD 10,00017. DMS 10018. DMS_FONT 10019. DMS_PHONE_NUMBER 50020. EVENT_PARTICIPANT 150021. FONT 10022. FUNCTIONAL_RIGHT 20023. *HAR 5024. HAR_NOTIFIER 100025. HAR_PHONE_NUMBER 50026. LRMS_GEOMETRY 20027. MESSAGE_LIBRARY 50028. MONITOR 40029. MONITOR_GROUP 20030. *MONITOR_GROUP_ENTRY 40031. ORGANIZATION 20032. PLAN 2,00033. PLAN_ITEM 10,00034. PLAN_ITEM_DIRECTION 1,50035. PROFILE_PROPERTY 12,30036. REGION 10037. RESOURCE_CATEGORY_TYPE 1038. RESOURCE_TYPE 10039. ROLE 10040. ROLE_ASSIGNMENT 2,00041. ROLE_FUNCTION 40042. SHAZAM 5043. SHAZAM_PHONE_NUMBER 50044. STANDARD_LANE 40045. STANDARD_LANE_CONFIG 10046. STORED_MESSAGE 10,00047. SYSTEM_PROFILE 100048. TOUR 10049. TOUR_ENTRY 10050. TSS 15051. TSS_PHONE_NUMBER 150052. TSS_ZONE 150053. TSS_ZONE_GROUP 30054. V1500CDU 1055. V1500HOST 10056. V1500KEYPAD 10057. VIDEO_FABRIC 1058. VIDEO_SWITCH 5059. VIDEO_SWITCH_CONNECTION 100060. USER ID 1,500


The R3B2 dynamic tables consist of data that grow or change based on operational functions. Tables that grow contain event data, operations, communications, and communications failure log data. The communications log data are stored for a user-specified period of time, currently for a two-week period of operation, and then deleted from the operational system. The operations and communications failure log data are stored for a user-specified period of time, currently for a three full days of operation, and then deleted from the operational system. The event data are stored during the time that the event is open plus a user-specified period of time after the event is closed. The user-specified period of time is a two-day period of operation. Event data are deleted from the operational database two days after an event is closed. The event and log data are migrated to the Interim Archive daily.

Table 3–12. CHART Backend Service Dynamic TablesNo. Table Name Max Rows1. ACTION 4002. ALERT 5003. ALERT_AMG 20004. ALERT_HISTORY 20005. ASSOCIATED_EVENT 2006. BRIDGE_CIRCUIT_STATUS 2007. CAMERA_MONITOR 4008. CAMERA_PRESET 5,0009. CAMERA_REVOKED_CONTROL 50010. CAMERA_REVOKED_DISPLAY 50011. CAMERA_STATUS 50012. CENTER_HANDOFF_REPORT13. CENTER_HISTORY 1014. CENTER_LOGIN 1,50015. COMMUNICATIONS_FAILURE_LOG 20,00016. COMMUNICATIONS_LOG 5,00017. DEVICE_EVENT 75018. DISABLED_VEHICLE_INDICATOR 1,50019. DMS_STATUS 10020. EVENT 2,00021. EVENT_HISTORY 45,00022. EVENT_RESOURCE 4,00023. EXECUTABLE_ACTION 20024. FOLDER25. FOLDER_OBJECT26. FOLDER_OP_CENTER27. HAR_AUDIO_OWNER 1,60028. HAR_CLIP_AUDIO 4029. HAR_MSG 1,00030. HAR_MSG_CLIP 3,00031. HAR_SLOT_CONFIG 80032. *HAR_STATUS 5033. INCIDENT 1,00034. INCIDENT_VEHICLES_INVOLVED 66035. LANE_STATE 4,000


No. Table Name Max Rows36. MONITOR_GROUP_CAMERA_STATUS 20037. MONITOR_STATUS 40038. MSG_CLIP_LIST 3,00039. NOTIFICATION_RECORD 20040. NOTIFICATION_REQUEST 20041. NOTIFICATION_STATUS 500042. OPERATIONS_LOG 40,00043. PROVIDER_COLLECTOR 1,00044. RESPONSE_PLAN_ITEM 5,00045. ROUTES 2,00046. SCHEDULE 20047. SCHEDULE_DOW_OCCURRED 500048. SCHEDULE_MULTIDATE 500049. SHAZAM_STATUS 5050. TOUR_STATUS 10051. TSS_STATUS 15052. VIDEO_SWITCH_STATUS 253. WEATHER 2,000

The CHART web service connects directly to the same CHART database to access web service specific tables. Four additional tables are used by the web service. These tables are replicated.

Table 3–13. CHART Web Service Static TablesNo. Table Name Max Rows1. FOLDER 1002. FOLDER_OBJECT 30003. FOLDER_OP_CENTER 200

Table 3–14. CHART Web Service Dynamic TablesNo. Table Name Max Rows1. CENTER_HANDOFF_REPORT 50

3.9.11.3 R3B2 Replication Overview

Database replication for R3B2 consists of replicating the tables listed in Table 3-15. The C2SOC3 database is the master and the remaining databases are updateable snapshots. The snapshot refreshes periodically, every 5 to 10 minutes.

Update capability on replicated global data will be controlled through the software by allocating Admin privileges via the functional rights to SOC users only. Non-SOC users will not have an Admin role. General users will be allowed update privileges via functional rights for specific tables. Conflict resolution consists of allowing the C2SOC3 master database to override any changes made in the C2AOC3 snapshot database. The possible conflicts are included in Table 3-15.


Table 3-15. R3B2 Replicated TablesReplicated Global Tables at

SOC and AOCRole Data Conflict Notes

CH2_DICTIONARY Admin No data conflicts. Read-only by application.

DICTIONARY_WORD Admin No data conflicts. Only a user with Admin privileges can modify this table. No C2AOC3 user will have admin privileges.

SYSTEM_PROFILE Admin No data conflicts. Only a user with Admin privileges can modify this table. No C2AOC3 user will have admin privileges.

USER_ID Admin Data conflicts are possible.All user roles - password updates only (excluding monitor role)

Data conflicts are possible.

ROLE Admin No data conflicts. Only a user with Admin privileges can modify this table. No C2AOC3 user will have admin privileges.

ROLE_ASSIGNMENT Admin No data conflicts. Only a user with Admin privileges can modify this table. No C2AOC3 user will have admin privileges.

ROLE_FUNCTION Admin No data conflicts. Only a user with Admin privileges can modify this table. No C2AOC3 user will have admin privileges.

PROFILE_PROPERTY All user roles Data conflicts are possible though highly unlikely since a user would have to be actively logged into both servers at the same time.

COMMUNICATIONS_LOG All user roles Data conflicts are possible.FUNCTIONAL_RIGHT Updated by DBA No data conflicts. Read-only

by application.ORGANIZATION Updated by DBA No data conflicts. Read-only

by application.


Replicated Global Tables at SOC and AOC

Role Data Conflict Notes

RESOURCE_CATEGORY_TYPE Updated by DBA No data conflicts. Read-only by application.

RESOURCE_TYPE Updated by DBA No data conflicts. Read-only by application.

FOLDER_OBJECT

FOLDER

FOLDER_OP_CENTER

CENTER_HANDOFF_REPORT

FONT

PRONUNCIATIONS

PROFILE_BINARY_PROPERTY

SYSTEM_BINARY_PROFILE

REGION

3.9.11.4 CHART Interim Archive Overview

The purpose of the Interim Archive database is to store the event history and log data generated by the CHART operational databases. The Interim Archive schema consists of the tables listed in Table 3–16, Interim Archive. At this point in time, the tables are pulled as is from the operational database without manipulating the data.

Since the full requirements of the archive are not known at this point and the complete content is not available, we are calling this storage an Interim Archive. It is the basic ingredients of the information CHART will have for eventually building the CHART Archive.


Table 3–16. Interim ArchiveNo. Table Name Max Rows1. ACTION 10,4002. ASSOCIATED_EVENT 5,2003. CENTER 5004. CENTER_HISTORY 105. CODE_LIST 1006. CODE_LIST_ITEM 4507. COMMUNICATIONS_FAILURE_LOG 520,0008. COMMUNICATIONS_LOG 130,0009. DATABASE_LIST 1010. DEVICE 1,00011. DISABLED_VEHICLE_INDICATOR 39,00012. EVENT 52,00013. EVENT_HISTORY 1,170,00014. EVENT_RESOURCE 104,00015. INCIDENT 26,00016. INCIDENT_VEHICLES_INVOLVED 17,16017. LANE_STATE 104,00018. OPERATIONS_LOG 1,040,00019. NOTIFICATION_RECORD 100,00020. NOTIFICATION_REQUEST 100,00021. NOTIFICATION_STATUS 1,000,00022. RESOURCE_CATEGORY_TYPE 1023. RESOURCE_TYPE 10024. TSS_DEVICE 20025. TSS_RAW_DATA 42,048,00026. TSS_RAW_DATA_TEMP 23,04027. WEATHER 52,00028. X_ACTION 10,40029. X_ASSOCIATED_EVENT 5,20030. X_EVENT 52,00031. X_EVENT_HISTORY 1,170,00032. X_EVENT_RESOURCE 104,00033. X_INCIDENT 26,00034. X_INCIDENT_VEHICLES_INVOLVED 17,16035. X_LANE_STATE 104,00036. X_RESOURCE_CATEGORY_TYPE 1037. X_RESOURCE_TYPE 10038. X_WEATHER 52,000

3.9.11.5 CHART Data Dictionary Report Tools


The Designer 6.0 tool also contains reporting capability in the Repository Reports. These reports provide information on the data dictionary objects contained under the directory Server Model Definitions. Most useful is the Table Definition report that provides detailed information on the tables in the physical database including the column data type, size and definition.

The Database and Network Design directory provides reports on database sizing. The Database Table and Index Size Estimate report provides the size of the database either for the database only; the database, tables and keys; or the database, tables, keys and columns.

The maximum size of the database storage for the R3B2 operational data in terms of data and indexes for a two-day period, based on a block size of 8KB, is:

Tables - 125MBIndexes - 20MB

The CLOB data is estimated at 1KB per message clip. The BLOB data is estimated at 350KB per message clip. The CLOB and BLOB data are stored in the HAR_MSG_CLIP and HAR_CLIP_AUDIO tables respectively.

The maximum size of the database storage for the Interim Archive database for one year, based on a block size of 16KB, is:

Tables - 7.5GBIndexes - 2GB

There are Function-based indexes in the Interim Archive database that do not appear in the Designer tool or the Size Estimate report. The Function-based indexes add an additional 55MB to the designer generated size estimate. The Designer tool does not support Function-based indexes. There are a total of four Function-based indexes as follows:

CFL_TRUNC_TIMESTAMP index on the COMMUNICATIONS_FAILURE_LOG tableCL_TRUNC_TIMESTAMP index on the COMMUNICATIONS_LOG tableEH_TRUNC_TIMESTAMP index on the EVENT_HISTORY tableOL_TRUNC_TIMESTAMP index on the OPERATIONS_LOG table

The maximum size is based on the volume shown in Tables 3–14 and 3–15 with the assumption that every row will be populated for the period of time estimated. Actual size will be less for the CHART application databases, since the volume is split between the two databases. The estimated size for the C2AOC3 database is roughly 15 percent of the total size for the entire database. Therefore, the distributed data will be approximately 123MB for the SOC and 22MB for the AOC. Actual size for the C2ARCH3 database may be less than estimated depending on the actual number of events and log entries that occur during that period.

3.9.11.6 Security Overview

The database security for CHART consists of assigning privileges to the CHART users at the application server level. Roles are assigned per application server. These roles are given privileges on specific tables based on what the application server requires to perform its functions. Database security does not monitor the individual user level. The database server


assumes that if access is granted to the user then the appropriate security check was performed prior to the user gaining access to the database.

Table 3–17, Database User/Role Matrix shows the users by application that can access the CHART R3B2 database and the roles assigned to those users.

Table 3–18, Database Role/Table/Privilege Matrix shows the tables that are accessible to a role and the specific privilege granted to that role for a given table.

Table 3–19, Interim Archive Role/Table/Privilege Matrix shows the tables that are accessible to a role and the specific privilege granted to that role for a given table in the interim archive database..

Table 3–17. Database User/Role MatrixUser Role

DMSSERVICE CHART2_DICTIONARY_ROLECHART2_DMS_CTRL_ROLE

HARSERVICE CHART2_DICTIONARY_ROLECHART2_HAR_CTRL_ROLE

MESSAGEUTILITYSERVICE CHART2_DICTIONARY_ROLECHART2_MSG_LIB_ROLECHART2_PLAN_ROLE

TRAFFICEVENTSERVICE CHART2_COMM_LOG_ROLECHART2_TRAFFIC_EVENT_ROLE

TSSSERVICE CHART2_TSS_CTRL_ROLE

USERMANAGEMENTSERVICE CHART2_RESOURCE_ROLECHART2_USER_MGMT_ROLE

ARCHIVE CHART2_ARCHIVE_ROLE

REPORT CHART2_REPORT_ROLE

ROADWAYLOCATIONLOOKUPSERVICE CHART2_LOCATION_ROLE

VIDEOSERVICE CHART2_VIDEO_CTRL_ROLE

NOTIFICATION_SERVICE CHART2_NOTIFICATION_ROLE

SCHEDULE_SERVICE CHART2_SCHEDULE_ROLE

Table 3–18. R3B2 Databases Role/Table/Privilege MatrixRole Table Privilege

Select Insert Update DeleteCHART2_CHARTLITE_ROLE CENTER X

CENTER_HANDOFF_REPORT X X X X

FOLDER X X X X

FOLDER_OBJECT X X X X


Role Table PrivilegeSelect Insert Update Delete

FOLDER_OP_CENTER X X X X

CHART2_COMM_LOG_ROLE CODE_LIST X

CODE_LIST_ITEM X

COMMUNICATIONS_LOG X X X

OPERATIONS_LOG X

CHART2_DICTIONARY_ROLE CH2_DICTIONARY X

CODE_LIST X

CODE_LIST_ITEM X

DICTIONARY_WORD X X X X

OPERATIONS_LOG X

CHART2_DMS_CTRL_ROLE CODE_LIST X

CODE_LIST_ITEM X

COMMUNICATIONS_FAILURE_LOG X

DEVICE_EVENT X X X

DMS X X X X

DMS_FONT X X X

DMS_PHONE_NUMBER X X X X

DMS_STATUS X X X X

FONT X X

OPERATIONS_LOG X

CHART2_HAR_CTRL_ROLE CODE_LIST X

CODE_LIST_ITEM X


CONSTITUENT_HAR X X X X

DEVICE_EVENT X X X

HAR X X X X

HAR_MSG X X X X

HAR_MSG_CLIP X X X X

HAR_NOTIFIER X X X X

HAR_PHONE_NUMBER X X X X

HAR_SLOT_CONFIG X X X X

HAR_STATUS X X X X

MSG_CLIP_LIST X X X X

OPERATIONS_LOG X

SHAZAM X X X X

SHAZAM_PHONE_NUMBER X X X X

SHAZAM_STATUS X X X X

CHART2_MSG_LIB_ROLE CODE_LIST X

CODE_LIST_ITEM X



HAR_AUDIO_OWNER X X X X

HAR_CLIP_AUDIO X X X X

HAR_MSG X X X X


MESSAGE_LIBRARY X X X X


OPERATIONS_LOG X

STORED_MESSAGE X X X X

CHART2_NOTIFICATION_ROLE NOTIFICATION_RECORD X X X X

NOTIFICATION_REQUEST X X X X

NOTIFICATION_STATUS X X X X

OPERATIONS_LOG X

CHART2_PLAN_ROLE CODE_LIST X

CODE_LIST_ITEM X

OPERATIONS_LOG X

PLAN X X X X

PLAN_ITEM X X X X

PLAN_ITEM_DIRECTION X X X

CHART2_REPORT_ROLE All CHART2 Tables(Reference Tables 3-12 and 3-13)

X

CHART2_RESOURCE_ROLE CENTER X X X X

CENTER_HISTORY X

CODE_LIST X X

CODE_LIST_ITEM X X

OPERATIONS_LOG X

ORGANIZATION X

RESOURCE_CATEGORY_TYPE X

RESOURCE_TYPE X X

CHART2_SCHEDULE_ROLE SCHEDULE X X X X

SCHEDULE_DOW_OCCURRENCE X X X X

SCHEDULE_MULTIDATE X X X X

OPERATIONS_LOG X

CHART2_TRAFFIC_EVENT_ROLE ACTION X X X

ASSOCIATED_EVENT X X X

CODE_LIST X

CODE_LIST_ITEM X

DEVICE_EVENT X X X

DISABLED_VEHICLE_INDICATOR X X X

EVENT X X X



EVENT_HISTORY X X X

EVENT_RESOURCE X X X X

HAR_MSG X X X X


INCIDENT X X

INCIDENT_VEHICLES_INVOLVED X X X X

LANE_STATE X X X


OPERATIONS_LOG X

RESPONSE_PLAN_ITEM X X X X

STANDARD_LANE X X X X

STANDARD_LANE_CONFIG X X X X

SYSTEM_PROFILE X X

WEATHER X X X

CHART2_TSS_CTRL_ROLE CODE_LIST X

CODE_LIST_ITEM X


OPERATIONS_LOG X

TSS X X X X

TSS_PHONE_NUMBER X X X X

TSS_STATUS X X X X

TSS_ZONE_GROUP X X X X

TSS_ZONE X X X X

CHART2_USER_MGMT_ROLE CENTER_LOGIN X X X

CODE_LIST X

CODE_LIST_ITEM X

EVENT_PARTICIPANT X X X

FUNCTIONAL_RIGHT X

OPERATIONS_LOG X

ORGANIZATION X

PROFILE_PROPERTY X X X X


RESOURCE_TYPE X X

ROLE X X X

ROLE_ASSIGNMENT X X X

ROLE_FUNCTION X X X

SYSTEM_PROFILE X X X X

USER_ID X X X X

CHART2_VIDEO_CTRL_ROLE CAMERA X X X X



CAMERA_MONITOR X X X X

CAMERA_REGION_ENTRY X X X X

CAMERA_STATUS X X X X

CODEC X X X X

CODEC_CONTROL_CONNECTION X X X X

CODEC_VIDEO_CONNECTION X X X X

LRMS_GEOMETRY X X X X

MONITOR X X X X

MONITOR_GROUP X X X X

MONITOR_GROUP_CAMERA_STATUS X X X X

MONITOR_GROUP_ENTRY X X X X

MONITOR_STATUS X X X X

OPERATIONS_LOG X

REGION X X X X

TOUR X X X X

TOUR_ENTRY X X X X

TOUR_STATUS X X X X

CHART2_LOOCATION_ROLE ROADWAY_LOCATION_STATES X X X X

ROADWAY_LOCATION_COUNTY X X X X

ROADWAY_LOCATION_ROUTE_REGION X X X X

ROADWAY_LOCATION _ALIAS X X X X

Table 3–19. Interim Archive Role/Table/Privilege MatrixUser Table Privilege

Select Insert Update DeleteARCHIVE ACTION X X

ASSOCIATED_EVENT X X

CENTER X

CENTER_HISTORY X X

CODE_LIST X

CODE_LIST_ITEM X

COMMUNICATIONS_FAILURE_LOG X X

COMMUNICATIONS_LOG X X

DISABLED_VEHICLE_INDICATOR X X

DMS X

EVENT X X

EVENT_HISTORY X X

EVENT_RESOURCE X X


User Table PrivilegeSelect Insert Update Delete

HAR X

INCIDENT X X

INCIDENT_VEHICLES_INVOLVED X X

LANE_STATE X X

OPERATIONS_LOG X X


RESOURCE_TYPE X

TSS X

TSS_ZONE X

TSS_ZONE_GROUP X

WEATHER X X

X_ACTION X X

X_ASSOCIATED_EVENT X X

X_EVENT X X

X_EVENT_HISTORY X X

X_EVENT_RESOURCE X X

X_INCIDENT X X

X_INCIDENT_VEHICLES_INVOLVED X X

X_LANE_STATE X X

X_RESOURCE_CATEGORY_TYPE X X

X_RESOURCE_TYPE X X

X_WEATHER X X

3.10 Special Operating InstructionsThis section contains special instructions on responding to certain problems and conditions that may arise in the CHART system.

3.10.1 Special InstructionsThis section contains instructions for responding to error conditions that the user may expect to encounter through normal usage of the system and instructions for handling special conditions that may arise during operations.

3.10.1.1 Deleting a device

If a field device must be deleted from the CHART system the device must first be placed in an offline state. In general, deleting a device from the system should be avoided unless the device is physically being removed or is being replaced with a different model type.


Deleting a DMS or HAR that is used in a plan will cause the corresponding plan item to become invalid. The plan item will display in the plan with the device indicated as unknown. The invalid plan item will be ignored if the plan is used as part of a response plan for an event.

3.10.1.2 Polling Interval

Though the software permits the polling interval to be set as low as one minute, R3B2 has a recommended minimum polling interval setting of two (2) minutes for DMS devices. Using a shorter interval may result in contention for communications ports. Configuration of locally polled DMSs typically have a polling rate of 4 minutes.

For RTMS devices the polling interval should not be set to a value less than the message period of the RTMS device. Polling an RTMS more frequently than its message period may result in no data being returned from the device, which causes the device to be flagged as comm failed. RTMS devices are typically configured for a polling interval of 5 minutes.

3.10.1.3 Event Service Failure

If the Event service should fail or stop working the CHART GUIs will no longer update. When the Event service is restarted the GUIs will begin updating within about 15 seconds. The GUIs will receive and display any new changes, however updates that occurred while the Event service was down (e.g. a new comm log entry) will not be displayed unless the GUI is restarted.

3.10.2 Known ProblemsSpecial operating instructions are necessary to work around or recover from certain known CHART bugs. CHART Server bugs are listed in Attachment J of the SCN, as well as Appendix B of this document. System limitations, i.e., CHART Server issues that are not CHART software bugs, are listed in Attachment H of the SCN. These would include issues such as COTS limitations. Other issues with the system that are imposed by things outside the direct control of the CHART organization, such as cables and telephone services provided by Verizon, Inc., are listed in Attachment M of the SCN.

CHART Web Server bugs are listed in the sections which follow.

3.10.2.1 Unable to play HAR messages on Windows Media Player 10

Apparently WMP 10 cannot play any audio file retrieved over an https connection, which includes CHART HAR audio. To work around this, the CHART web service now has properties file settings that govern the way it returns audio. It can be set to turn streaming off and save the audio to a file before redirecting the user to play the file via HTTP instead of HTTPS. The default setting is to play audio files via HTTP.

3.10.2.2 Incorrect HAR Audio File Format Causes HARs to Become Unresponsive

During Acceptance Testing it was discovered that using an unsupported audio format for HAR messages caused the HARs to become unresponsive to CHART (LiteA00000006). This required someone to reset the telephony board to get them working again. The CHART system should not have allowed the unsupported format to get down to the communications level, and it may


have been a configuration problem, but in any case it showed that an unsupported format can cause serious problems.

The CHART web service now includes configuration parameters in the MainServlet.props file that allow the acceptable audio formats to be defined. These settings have names that begin with chartlite.servlet.audioFormat. The CHART web service will block any audio file that does not have one of the defined formats from being sent on, therefore further helping to prevent unsupported audio formats from causing HAR problems.

During testing, the Windows Sound Recorder was defaulting to a format that caused problems (PCM 8-bit 8 KHz mono). One format that seemed to work during testing was CCITT uLaw 8kHz 8-bit 7 kb/s mono. To expect an operator to convert each file to a good format would be risky.There is apparently no way to set the default sound format from the Sound Recorder GUI in Windows 2000 or XP. A registry patch will be provided on the delivery CD that creates a “HAR” profile using CCITT uLaw 8kHz 8-bit 7 kb/s mono and sets that as the default format when Windows Sound Recorder starts up. (This registry settings file alters the following registry key: HKEY_CURRENT_USER\Software\Microsoft\Multimedia\Audio). It is recommended to apply the patch to the workstations where Windows Sound Recorder is used to record HAR messages.

3.10.2.3 Communications Log Check Boxes May Get Cleared

The Communications Log page allows the operator to make one or more entries into the communications log and then associate the entries with a new traffic event. Operators should be aware this page automatically refreshes on a regular basis. After selecting some number of log entries, it is possible for the page to be refreshed before the operator hits one of the create traffic event icons at the top of the page, thus clearing any checked log entries without the operator knowing it. Three work-around scenarios exist:

1. Re-check the log entries and hit one of the create traffic event icons before the next refresh

OR

2. Increase the Standard Page Refresh Rate value on the Change System Profile page. Note that this option affects most pages that refresh.

OR

3. Select the Search button on the Communication Log page to bring up the Communication Log Search Results page and make the log entry selections there (unlike the Communications Log page, the Communications Log Search Results page does not refresh).

3.10.2.4 Multiple Working Windows May Appear

Occasionally you may find that an additional working window may be opened. When this occurs, the work around is to close all working windows and click a link on the home page and a new working window will appear.



4 Problem Identification and Resolution4.1 Problem IdentificationThe CHART system provides several mechanisms for reporting system status and error information. The CHART GUI provides a command status window and a command failure window for informing the user of the result of an action. These messages are also recorded in the Operations Log. The status of actions performed in an open Event are recorded and displayed in the Event History. Messages that are displayed to the user and which may require some user action are listed in Appendix E.

In addition to those messages displayed to the user and logged in the Operations Log and Event History the CHART applications will log information to application specific log files (see Section 3.7). The CHART applications can be configured to record detailed debug information useful for trouble-shooting problems. See Section 3.8.2 for instructions on modifying application property file parameters.

The following table indicates some generic CHART GUI problems and possible resolution actions.

Symptom Initial Approach

Browser displays an error message See Appendix E for a matching message pattern.

The CHART web service log files may also provide information to help debug a problem and may help to determine if a problem exists in the CHART back end or the CHART web service. For example, the CHART web service will log a message if a CHART service returns an error message to a requested action. See section 3.7.2 for the location of CHART web service log files.

Browser page displays stale information Manually refresh the page using the browser.

Browser itself freezes Verify browser is the approved version (IE 6.0 or 7.0).

Unable to reach CHART web server Contact network administrator.

Able to reach the CHART web server but not the CHART web site (HTTP 404 error file not found)

Check the spelling of the web site. If spelling is correct, the CHART web service may need to be restarted. See Section 3.5.


4.1.1 Communications ProblemsCommunications problems with devices will be recorded in the PortManager log for the FMS PortManager that serves the device in question. If a communications problem is suspected then the PortManager should be set to debug mode (see Section 3.8.2) to record as much information on communicating with devices as possible. If this fails to identify the problem then addition information may be obtained through device specific information (see below).

4.1.2 Device ProblemsThe information available for aiding in the investigation of problems with devices is device type and model specific.

4.1.2.1 DMS Devices

The DMS Status logs (see Section 3.7.3) and the Device logs (see Section 3.7.4) provide detailed information on the status of a DMS and on the commands being sent from the CHART system to the device. For DMS devices where communications are established additional device information can be obtained through the device Properties display. Properties tabs for Extended Status, Lamp Status, and Pixel Status are available for certain DMS types as shown in the list below.

Extended Status FP9500, PCMS, Sylvia, TS3001

Lamp Status FP9500, Sylvia, TS3001

Pixel Status FP9500, TS3001

To obtain the extended status for a DMS perform the following steps:

1. Put the DMS in maintenance mode.

2. Right click on the device and select Get Extended Status

3. Wait for communications with the sign to complete then select Properties for the device.

4. Select the Extended Status tab.

To obtain the pixel status for a DMS perform the following steps:

1. Put the DMS in maintenance mode.

2. Right click on the device and select Pixel Test (this can also be performed from the Pixel Status tab in the Properties display).

3. Right click on the device and select Get Extended Status

4. Wait for communications with the sign to complete then select Properties for the device.

5. Select the Pixel Status tab.

4.1.2.2 HAR Devices

There are no Status Logs for HARs and SHAZAMs. There are also no Device Logs for SHAZAMs.


4.2 Maintenance OverviewThe CSC team provides the CHART system maintenance functions. CHART software, communications and hardware problems should be reported to the MDOT NOC.

4.3 Maintenance DocumentationThe following document is also available as supporting information:

CHART R3B2 User’s Guide, to be published.


Acronym ListAOC Authority Operations Center

CHART Coordinated Highways Action Response Team

CORBA Common Object Request Broker Architecture

CCTV Closed Circuit Television

COTS Commercial Off The Shelf [products]

DMS Dynamic Message Sign

EORS Emergency Operations Reporting System

FMS Field Management Station

GUI Graphical User Interface

HAR Highway Advisory Radio

ISDN Integrated Services Digital Network

ITS Intelligent Transportation Systems

JRE Java Runtime Environment

MDSHA Maryland State Highway Administration

MDTA Maryland Transportation Authority

NTCIP National Transportation Communications for ITS Protocol

NOC Network Operations Center

NVA No Video Available

OMG Object Management Group

ORB Object Request Broker

POTS Plain Old Telephone System

RITIS Regional Integrated Traffic Information System

RTMS Remote Traffic Microwave Sensor

SCN Software Change Notice

SID System Identifier

SOC State Operations Center

TCL Tool Command Language

TOC Traffic Operations Center

TSS Transportation Sensor System

TTS Text to Speech

CHART Operations & Maintenance Guide R3B2 Revision 2 AC-1 11/05/2008

ReferencesAdditional materials providing supporting information are listed below.

1. CHART System Requirements Repository2. CHART Business Area Architecture Report, January 27, 2007, WO1-BA-001.3. CHART R3B2 User’s Guide, to be published.4. TELE-SPOT 3001 Sign Controller Communications Protocol, document number 750208-040

v2.3, T-S Display Systems Inc., 19955. Functional Specification for FP9500ND – MDDOT Display Control System, document

number A316111-080 Rev. A6, MARK IV Industries Ltd., 1998.6. Maintenance Manual for the FP1001 Display Controller, document number 316000-443

Rev. E, Ferranti-Packard Displays, 19877. FP2001 Display Controller Application Guide, document number A317875-012 Rev. 8, F-P

Electronics, 19918. Engineering Specification - Brick Sign Communications Protocol, Rev. 1, ADDCO Inc.,

1999.9. PCMS Protocol version 4, document number 32000-150 Rev. 5, Display Solutions, 200010. BSC Protocol Specification (Data Link Protocol Layer), v. 1.3, Fiberoptic Display Systems

Inc., 199611. Sylvia Variable Message Sign, Command Set 9403-1, v. 1.4, Fiberoptic Display Systems Inc.,

199612. National Transportation Communications for ITS Protocol: Object Definitions for Dynamic

Message Signs (DMS) – Version 02, document number NTCIP 1203 v02.20 c, AASHTO, ITE, & NEMA, 2003

CHART Operations & Maintenance Guide R3B2 Revision 2 RE-1 11/05/2008

Appendix A – System Installation InstructionsThis appendix provides step-by-step instructions for the installation and configuration of the CHART system. Section A.1 describes the CHART system installation procedures and Section A.2 describes the CHART database installation procedures.

A.1 CHART System InstallationThe standard CHART system installation medium is a CD-ROM containing the CHART server and support applications (including the required version of the Java Runtime Environment). The installation procedure may be run directly from the CD-ROM or the installation directories may be copied from the CD-ROM to a local or networked disk and installed from there.

A.1.1 System Installation RequirementsCHART is designed to operate across a Windows network. The system requirements for each type of installation are listed below.

CHART Server Installation: Windows 2003 (with TCP/IP networking installed) Sun Java Runtime Environment (JRE) version 1.5.0_09 (for Windows) Oracle version 10g Release 1 and CHART Database (See Section A.2) MSSAPI 5.1/Nuance Text-To-Speech Engine (See Section A.1.4.2) Microsoft Visual C++ 6.0, Service Pack 6

FMS Server Installation: Windows 2003 (with TCP/IP networking installed) Sun Java Runtime Environment (JRE) version 1.5.0_09 (for Windows)

Installation Notes:

If another version of Java has been installed on the server, such when Oracle has been installed, after JRE 1.5.0_09, CHART may no longer work. This is due to the fact that the Oracle installation changes the Java Runtime Environment registry value and installs in the System32 directory. To fix this perform the following:1. Run the registry editor (regedt32.exe)2. Navigate to the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\

Java Runtime Environment.3. Change the “CurrentVersion” registry value to “1.5”.It may also be necessary to change the system PATH variable. After making the above change, open a DOS command window and enter “java -version”. If the command fails, or if a version other than 1.5.0_09 is returned, do the following:1. Go to Start>Control Panel2. Double-click System3. Select the Environment tab.

CHART Operations & Maintenance Guide R3B2 Revision 3 A-1 12/10/2008

4. In the System Variables window, scroll down and select Path.5. In the Value box, add the path to the JRE 1.5.0 bin directory to the beginning, separated by a

semi-colon (“;”). Example: C:\Program Files\Java\Jre\1.5.0\bin;<rest of path>

6. The installation setup does not allow reinstalling CHART R3B2.06 twice consecutively on the same machine. If you made a mistake, you will be asked to uninstall first before reinstalling again. Always use the “<CHART folder>/Uninstall CHART menu on the Start->Programs menu. In case you used GUI –only install CD, use the “Uninstall ChartII GUI” menu under Start->Programs.

7. Deleting the CHART directories without running the uninstall, creates a situation where you cannot reinstall CHART again on the machine. To recover from this situation: Delete the following registry key “HKEY_LOCAL_MACHINE\Software\Chart”

Also delete the CHART related desktop shortcuts and program menu shortcuts and folders in the C:\WINN\Profiles\AllUsers\Desktop and C:\WINNT\Profiles\AllUsers\Start Menu\Programs.

8. The installation creates install_log.txt under the target installation directory if the installation fails due to errors.

A.1.2 Installation Instructions for CHART ServersThis section describes the procedure for installing the CHART services on a CHART server. IMPOTANT NOTE: Stopping a service before it has completely started may throw the service into an unusable state that is only recoverable by rebooting the machine. When stopping a service that has been started in the past few minutes, first check the log file for that service and make sure it has started successfully.

SECOND IMPORTANT NOTE: A CHART server installation presumes a pre-existing Microsoft Visual C++ installation. Installing Microsoft Visual C++ places several DLLs in C:\WINNT\SYSTEM32\.

These same DLLs are needed in order to install the CHART services. Thus, if a CHART server installation is being performed on a new machine, or a machine without these DLLs already in place, you will need to copy some DLLs into the system 32 directory.

On this CHART R3B2.06 CD, the seven required DLLs are stored in the directory <CD drive letter>:\Install\Dynamic Link Libraries\Microsoft\. Copy the seven files there into C:\WINNT\SYSTEM32\. Do this BEFORE attempting to install the CHART services.

1. Prior to installation, ensure you have the following information:

The name of the operations center that is to be assigned to the server. This is case sensitive and must be specified exactly as it exists within the CHART system.


The host name of the computer that is running the Oracle database, the name of the database instance, and the port number being used by the database instance.

Database user names and passwords for the CHART Alert Service, the User Management Service, the DMS Service, the Message Utility Service, the EORS Service, the RoadwayLocationLookupService, the Schedule Servicethe TSS Service, the HAR Service, the Traffic Event Service, and the Video Service

Database connect string for EORS, if EORS Service is to be installed.

Database connect string for the CHART Mapping database, if the RoadwayLocationLookupService is to be installed.

Primary and Secondary Attention!NS Notification server names, including the API port number.

Attention!NS user name and password for sending notifications.

The form included in Appendix B may be used to record this information so that it is readily available when required during the installation.

2. Log into the target machine with administrator privileges

3. Shut down all CHART clients (Tomcat services on the web servers).

4. Shut down all backend CHART services.

As a general rule the previous version of the backend CHART services software is NOT uninstalled before installing a new version. The old version is essential or useful during and immediately following the installation for needed data files (Audio*.id files), for reference (previous .props files properties settings), and to provide an emergency fallback position.

5. Either manually set all old backend CHART services to Manual or Disabled startup (not Automatic) in Manage Computer (Services Applet), or delete the old services (NOT the directory) by running bin/RemoveServices.cmd after all services have been stopped. RemoveServices removes the services from Manage Computer (Services Applet), but does NOT delete the old installation directory. Do NOT run the uninstall command, as that will delete the directory (unless necessary data, .props files, .id files, etc., have been saved off or are surely not needed).

6. If required (and not used by any other application), remove any old Java Runtime Environment (e.g., JRE 1.3.1, which was used for R2B2). If JRE 1.5.0_09 is installed, it can remain.

7. Using regedit, see if there is a folder HKEY_LOCAL_MACHINE/SOFTWARE/CHART. If there is, remove the entire CHART folder within the registry, not just the key contained in the CHART folder.

8. If the CHART Message Utility Service is to be installed, the MSSAPI 5.1/Nuance Text to Speech software must already be installed on the same machine. The instructions for this software are outlined below in Section A.1.4.1.2. If the Text to Speech software is not installed before the Message Utility Service software is installed, the part of the service that deals with text to speech will be commented out in the Message Utility Service properties file. This can be uncommented later if the text to speech software is


subsequently installed. Note that the service will not do text to speech (and should not be configured to do text to speech) until Text to Speech software is installed, although it will run properly in all other respects. Currently all CHART application servers have MSSAPI 5.1/Nuance software installed and are configured to do text to speech within the Message Utility Service.

9. Insert the CHART installation CD in the CD ROM drive.

10. If not installed already, install Java 1.5.0_09. From the installation CD (Install/JRE1.5.0_09), run jre-1_5_0_09-windows-i586-p.exe. Select the typical setup, and let the JRE install in the default location. Java 1.5.0_09 should be installed on all existing CHART servers as of the CHART R2B3 release.

11. If Java 1.5.0_09 was installed, move the JRE to the front of the System Path. My Computer->Properties->Advanced-> Environment Variables button. Edit the System Path variable so that C:\Program Files\Java\jre1.5.0_09\bin;C:\Program Files\Java\jre1.5.0_09\bin\client is at the front.

12. Start the CHART installation by running CHART R3B2/04 Setup.exe from the CHART installation CD.

13. Complete the installation by following the on-screen instructions as follows:

a. Read the information on the Welcome screen and press the Next button to continue.

b. Read the Information window and press the Next button to continue.

c. The installation directory defaults to D:\Program Files\CHART R3B2.06\. This should be used for all installations. At the SOC, the D: drive must be used for proper cluster operation, and the same drive and directory should be used for consistency in all other production installations. Press the Next button to continue.

d. On the Select Components window make sure all components are selected except for the Comm Service. Press the Next button to continue. (Normally CommService is not installed on the CHART server machines.)

e. On the TCP Port Assignments window, change the port numbers if necessary. The default values are usually OK unless some other application is already using one or more of these values. The TCP Port Assignment should be set to 9002.

f. On the General Settings window, enter the name of the site where you are installing the servers. This name defaults to the host name, but could be any descriptive name for the site, such as “SOC Server Room”. Standard procedure is to keep the host name as is. As described above, this value is case sensitive and must exist within the CHART system. Verify the JRE version is correct. For R3B2.06 it should be 1.5.0_09. This must be correct, or else, the CHART won’t successfully register its services. Use the default values for heap size. Lastly, enter the number of days to keep log files (used by support personnel to troubleshoot software problems) or accept the default. The recommended value is 7 days. Press the Next button to continue.

g. On the Database Settings window, modify the database connection string if necessary. The connection string contains the host name of the database server (after


the @), the port used by the database server, and the instance name of the database, separated by colons. For example, as of January 2007 the connection string for the SOC services is “jdbc:oracle:thin:@HANOVERCHART1:1526:C2SOC3”, which specifies that the database server is running on the machine with virtual host name “HANOVERCHART1” on port 1526 and the database instance name is “SOC3”. As of January 2007 the connection strings for the seven CHART backend servers are:SOC: jdbc:oracle:thin:@HANOVERCHART1:1526:C2SOC3AOC: jdbc:oracle:thin:@AOCCHART2:1526:C2AOC3District 3, Greenbelt: jdbc:oracle:thin:@greenbltchart1:1526:C2D3GRDistrict 4, Brooklandville: jdbc:oracle:thin:@brookd4chart1:1526:C2D4BRDistrict 5, Annapolis: jdbc:oracle:thin:@annad5chart1:1526:C2D5ANFrederick LEC: jdbc:oracle:thin:@fredlecchart1:1526:C2LECPG Trip Center: jdbc:oracle:thin:@pgtripchart1:1526:C2TRIPEaston Microwave Facility: jdbc:oracle:thin:@eastonmwchart1:1526:MWESTNote: the instance name you enter is case sensitive – using the incorrect case will inhibit the ability to run the server applications as Windows services. The instance name can be checked by opening the Windows Service Control Manager dialog on the database server and viewing the service name that starts with “OracleService”. The database instance name (in its case sensitive form) is appended to this service name, e.g., OracleServiceSOC3.

Also enter the user names and passwords to be used by the CHART services for their database usage. The default user names should exist on any CHART database installation; however the passwords may need to be obtained from the database administrator.

h. On the EORS window, modify the database connection string if necessary. The connection string contains the host address/name of the database server and the port used by the database server. For example, as of January 2006 the connection string is “jdbc:inetdae:170.93.51.23:1433”, which specifies that the database server is running on the machine with the IP address 170.93.51.23 on port 1433. Also, modify the database instance name, user id, and password if necessary.

i. On the Required Services Locations window check the Trading Service and Event Service information. Access to a Trading Service and an Event Service are required. If you did not choose to install a Trading Service or Event Service during your installation, you must enter the host name and port for the service(s) that will be used. Press the Finish button to finish the customized settings.

j. Multiple traders can be specified by doing the following on the Required Services Locations window

a. To use a predefined trader list for field installs, click on the field install radio button

i. To modify trader configuration such as port, double click on the desired trader from the list box, update the text fields, and click the Edit Trader button.


b. To select an individual predefined trader, select the desired trader from the drop down box

c. To specify an unlisted trader, enter the name/port values in the text fields, and click the Add Trader Button.

d. Modifying the trader order is accomplished by selecting the desired trader from the list and using the Up, Down, and Delete buttons.

k. When the Setup Complete window appears, click on its finish button to complete the installation.

l. The installation installs a folder containing shortcuts to start each of the CHART services.

14. Look for an install_log.txt that may be created under the installation directory. This file should be present only when there are errors and lists the install steps completed. Check it for indications of any errors. If the installation fails, it may be due to the system PATH is too long. To check for this:

a. Go to a DOS prompt and switch to the directory of a service that failed to install (e.g., D:\CHART R3B2.06\bin\DMSService).

b. Execute the registration script, for example, type DMSServiceReg.c. If there is an error message that indicates that the line is too long, you will have to

update the system PATH to install CHART properly.d. First uninstall R3B2.06. From a DOS prompt, go to D:\Program Files\

CHARTR3B2.06. Type uninst and follow the directions.e. Edit the System PATH by going to the desktop, right-clicking on My Computer -

> Properties -> Advanced and clicking the Environment Variables button. Edit the PATH System variable to remove anything that is unnecessary.

i. Remove any repeats.ii. Remove d:\Chart\Lib if it is there.

iii. Remove and references to Java1.3.f. Re-install CHART as per the instructions above.

Post Installation Steps – CHART server applications are installed to run as Windows Services. This allows the CHART Servers to run with no users logged into the server machine and also provides the ability for automatic start-up of the servers when the server machine is booted.

1. Move the JRE to the front of the System Path. My Computer->Properties->Advanced-> Environment Variables button. Edit the System Path variable so that C:\Program Files\Java\jre1.5.0_09\bin;C:\Program Files\Java\jre1.5.0_09\bin\client is at the front.

2. Whether installing on the same server or a different server, if the new installation will have the same name and IP address, three *.id files will need to be copied over from the old installation to the new, so that the HAR audio IORs stored in the database will be the same as they were in the previous installation. The *.id files to copy are those three which begin with the word “Audio”, namely: /bin/MsgUtilityService/AudioClipManager.id, /bin/MsgUtilityService/AudioClipOwner.id, and /bin/TrafficEventService/AudioClipOwner.id


3. Edit the VideoService.props file (<Chart Installation directory>\bin\VideoService\VideoService.props) on AOCCHART2, the only CHART server which will be hosting the CHART VideoService RouterControlModule and VideoSwitchModule. On AOCCHART2, edit the VideoService.props file so the following lines are NOT commented out: DefaultServiceApplication.ModuleClassName3=CHART2.VideoSwitchControlModule.VideoSwitchControlModule DefaultServiceApplication.ModuleClassName4=CHART2.RouterControlModule.RouterControlModule

4. On the server which will host the VideoSwitchModule (for R3B2 this is AOCCHART2), set the V1500ManagerService to automatic. This is done by right-clicking on the V1500ManagerService from the Services applet, selecting Properties, and changing the Startup type to Automatic. All other CHART servers will have the V1500ManagerService remain as manual.

5. Edit the jacorb.properties file in the bin \ directory <Chart Installation directory>\bin\jacorb.properties). Change the line:jacorb.connection.client.pending_reply_timeout=30000to:# This value is commented out because apparently it cannot be# adjusted upwards in individual service .props files using the# ORBRequestTimeoutMillis property. #####jacorb.connection.client.pending_reply_timeout=30000

6. Edit the TSSService.props file (<Chart Installation directory>\bin\TSSService\TSSService.props). Under the line: DefaultServiceApplication.ORBConnectTimeoutMillis=5000Add the lines: ## Amount of time to wait for requests to other services to complete, specified# in milliseconds. #DefaultServiceApplication.ORBRequestTimeoutMillis=30000

7. Only one server in the field will run the RITISService at a time. It is important that both the RITISEvents and RITISService are disabled on all other installations. For initial deployment, the RITISService will run on hanoverchart1.

8. On the server which runs the RITIS service, a home Operations center must be identified and defined. It is anticipated that this will run only on the hanoverchart1 server. Add a valid operations center identifier: EventImportModule.OpCenterID=<32 byte ASCII identifier for the defined Op Center>. If this center has not already been added to CHART, perform this step after CHART has been started and the center can be added through the GUI. The identifier can be found in the Trader console (Administration->Trades-><server>->OperationsCenter).


9. The RITIS properties files must be updated to include the necessary information to connect to RITIS. First set DefaultServiceApplication.LogFileLevel=debug. Next, set EventImportModule.Password= <password supplied by UMD>, no brackets. Set the proper queue name: EventImportModule.QueueName=Clients.<name supplied by UMD>.ATIS.Events, no brackets. Finally, set the user name: EventImportModule.User=<User name supplied by UMD>, no brackets.

10. The RITIS properties file must also be updated to include only one trader (hanoverchart1).

11. On any server which runs the V1500 Manager Service (currently aocchart2), manually add an Oracle dependency to the registry. This is necessary so that the V1500ManagerService will not start until Oracle has started.

a. Run regedit from a DOS prompt.

b. Navigate to HKLM\System\CurrentControlSet\Services\CHART R3B2.06 4B DMSService.

c. Edit->Modify the DependOnService. Copy the line(s) for the Oracle service name. Pay particular attention to the leading and trailing “00”s if applicable. This will get pasted into the V1500ManagerService DependOnService registry value.

d. Navigate to HKLM\System\CurrentControlSet\Services\V1500ManagerService.

e. Edit->Modify the DependOnService. Paste in the Oracle service name from c.

12. Install Server Patch 1. Copy <R3B2.06 Installation CD>: \Server Patch1\CHART2 to D:\Program Files\R3B2.06\lib.



15. Install class files for Server Patch 4. Copy <R3B2.06 Patch 4 Installation CD>: \Server_Patch4\lib \CHART2 to D:\Program Files\R3B2.06\lib. Note that Patch 4 is on a separate installation CD.

16. Install new configuration files for Server Patch 4. Copy the three configuration files from <R3B2.06 Patch 4 Installation CD>: \Server_Patch4\bin\RITISService to D:\Program Files\R3B2.06\bin\RITISServiceb. Note that Patch 4 is on a separate installation CD.

17. Update the MsgUtility.props file for Server Patch 4. Replace the AudioClipModule.ClipCleanupTimeOfDay with these 4 properties .## Property that allows or disallows the audio clip cleanup task from running.# If false, audio clip cleanup never runs. Default=true.#AudioClipModule.RunAudioClipCleanupTask=true

## Property key that specifies at what time lost clips (i.e. clips without an


# owner) are deleted. Note: Cleanup always runs at the time specified TODAY, so# times late in the day are better, unless it is desired for cleanup to run# immediately upon startup. Default=00:00:00 (midnight).#AudioClipModule.ClipCleanupTimeOfDay=00:15:00

## Property that indicates whether audio clip owners should be deleted from the# database during audio clip cleanup. If there is trouble deleting too many# owners, this can prevent excess owners from being deleted. Default=true.#AudioClipModule.CleanupAudioOwners=false

## Property that indicates whether audio clips should be deleted from the# database during audio clip cleanup. If there is trouble deleting too many# clips, this can prevent excess clips from being deleted. Default=true.#AudioClipModule.CleanupUnneededAudioClips=false

18. Copy <R3B2.06 Patch 5 Installation CD>: \Server_Patch5\lib\CHART2 (the whole directory) to d:\Program Files\CHART R3B2.06\lib. This will copy the necessary class files into their proper directories.

19. Update each event service properties file (e.g., d:\Program Files\CHART R3B2.06\bin\AlertEventService\AlertEventService.props). Change the value of jacorb.events.maxDeadClientMins to 480

20. Update each CHART service properties file (e.g., d:\Program Files\CHART R3B2.06\bin\AlertService\AlertService.props). Add the following:

# Number of seconds that should elapse between event channel# verification cycles. Event channel verification is used# to make sure that clients are still connected to all of the event# channels they have discovered. The verification process automatically# reconnects the client to an event channel if its connection is# found to no longer exist during verification.# Default value: 60DefaultServiceApplication.EventChannelVerificationIntervalSecs = 900

21. Before starting any services, make a backup of the installation to two places. Copy the entire D:\Program Files\R3B2.06\ to C:\Install\ on the same server and on the co-located web server. Rename both copies to C:\Install\Backup of R3B2.06\.

NOTE: It is much easier to do this now, but if time is of the essence, this can be done later. If being done at a later time, look for and avoid copying very large *.txt or *.log files, which may be present, particularly in VideoService, TradingService, and DMSService directories. After the copy is complete, ensure the backups have none of the following files (which, aside from very large files already mentioned, are easier to copy and then delete than to avoid copying at all): MessageQueuePersist\ files and trader_db\ files (whose presence could be detrimental if this backup is ever restored), and all *.txt files, *.err files, or *.log files (which are unnecessary to keep).


22. The computer may be rebooted to bring up all services at once. This is absolutely necessary only on servers which run the V1500ManagerService. When the computer restarts, the CHART servers will start automatically. If the V1500ManagerService will not be run, the services can be started manually. This is often a better choice, it is faster and problems can be identified sooner. To do this:

a. Right click My Computer and click Manage…

b. Start CHART R3B2.06 1A Trader

c. Start CHART R3B2.06 1B EventService

d. Start Nuance Watcher Daemon if it is not already running (this should already be running from an earlier Nuance Text-to-Speech installation).

e. Start the following services, in order. If desired, the verification steps (next two step) can be interspersed, to verify that each service starts up in order, before proceeding on to the next service.CHART R3B2.06 2A UserManagerEventsCHART R3B2.06 2B UserManagerServiceCHART R3B2.06 2C AlerEventsCHART R3B2.06 2D AlertServiceCHART R3B2.06 2E RITISEventsCHART R3B2.06 2F RITISServiceCHART R3B2.06 2G ScheduleServiceCHART R3B2.06 2H ScheduleEventsCHART R3B2.06 3A MsgUtilityEventsCHART R3B2.06 3B MsgUtilityServiceCHART R3B2.06 4A DMSEventsCHART R3B2.06 4B DMSServiceCHART R3B2.06 5A HAREvents CHART R3B2.06 5B HARServiceCHART R3B2.06 6A TrafficEventEvents CHART R3B2.06 6B TrafficEventServiceCHART R3B2.06 6C RoadwayLocationLookupServiceCHART R3B2.06 7A TSSEventsCHART R3B2.06 7B TSSServiceCHART R3B2.06 8A EORSServiceCHART R3B2.06 9C VideoEventsCHART R3B2.06 9D VideoServiceCHART R3B2.06 10A NotificationEventsCHART R3B2.06 10B NotificationServiceV1500ManagerService

23. Verify that the CHART services are running. These are the services listed above which end with the word “Service”. Use the Service Control Manager to check that all CHART services have a status of “Started”.

24. Verify that there were no errors during the service start-up. This is done by checking each of the CHART Server’s log files for an entry that indicates the service has started


successfully. The log files can be found in the \bin folder of the installation directory under the service folder for each service and are named “UMService_”, “MsgUtilService_”, “TrafficEventService_”, “TSSService_”, “HARService_”, “EORSService_”, “DMSService_”, and “VideoService”, etc., with the current date appended, e.g., “DMSService_030801”. These files are standard text files and can be viewed with Notepad (but not WordPad since the most current files are in use).

25. At some point after services have been installed, copy all *.id files to the two backups made above, to the appropriate subdirectories of the backups made above: to C:\Install\Backup of R3B2.06\ on the same server and the co-located web server. (These files appear in the CHART service directories only, not the Trader directory or Event Service directories.)

NOTE: It is easier to make the initial copy earlier and just copy the *.id files now, rather than to do everything now have to wait for or bypass the copying of all the *.txt, *.err, and *.log files.) However, if an initial copy was not completed earlier due to time contraints, the copy can be done now. Just look for and avoid copying very large *.txt or *.log files, which may be present, particularly in VideoService, TradingService, and DMSService directories. After the copy is complete, ensure the backups have none of the following files (which, aside from very large files already mentioned, are easier to copy and then delete than to avoid copying at all): MessageQueuePersist\ files and trader_db\ files (whose presence could be detrimental if this backup is ever restored), and all *.txt files, *.err files, or *.log files (which are unnecessary to keep).

A.1.3 Installation Instructions for Field Management Station (FMS) Server

This section describes the procedure for installing the CHART Comm Service on an FMS server. NOTE: In the steps below, DO NOT uninstall previous versions of the Comm Service if they are supporting operations. Clear this with a CHART operations administrator.

1. If desired, uninstall any previous installations of the CHART Comm Service software. However, it is not necessary to uninstall old versions, especially if there may be a need to fall back. To leave the service(s) installed, you must manually set it to Manual or Disabled startup (not Automatic) so that it does not restart when the server is rebooted. You will need to uninstall an existing R3B2.06. NOTE: if the port configuration of the server is not changing when the new version is installed (normally the case), save off the file “PortConfig.xml” file to an area outside of the CHART R3B2.06\ directory that will be deleted during the uninstallation. If there are multiple Comm services running on the machine, save each PortConfig file to a separate location (i.e., do not overwrite or confuse them).

To uninstall a CommService:

a. Close all open files and directories under the CHART directory.

b. It is recommended that the CommService be manually terminated. This can be done through the Services applet (Start->My Computer->Manage->Services). If the Comm Service(s) does not stop, kill using the following procedure. Get the


service process ID from the Task Manager (<ctrl><alt><del> -> Task Manager -> Processes Tab). The Comm Service name will be js-<CommServiceName>.exe. Open a DOS prompt and go to the Chart utilities directory (c:\Utilities\Chart). Type ‘kill –f <process ID>’, no quotes, where <process ID> is the value already noted above. If there are multiple Comm Services installed, it may not be possible to match the process IDs to the Comm service since the names may be truncated or may all be js-CommService.exe. Since ALL Comm services need to be terminated anyways, all js-<CommServiceName>.exe processes can be terminated.

c. Click the “Uninstall FMS” menu on the Start->Programs menu. This will stop the Comm Service, remove it, and uninstall the files completely.

d. Verify that the Comm service(s) has been removed. You may need to log out and back in to verify (check the Services applet). If it has not been un-installed, it is likely that all of the files have not been removed from bin\CommService directory. From the DOS prompt, run uninstall.cmd to remove the Comm Service (e.g., go to c:\Program Files\CHART R3B2.06\bin\CommService, run CommServiceRemove.cmd). This entire directory structure can now be manually deleted.

c. If required, also remove the Java Runtime Environment.

2. Insert the CHART installation CD in the CD ROM drive.

3. There are two ways to install the Comm Service software. The first method is to install it from the same installation package that is used to install the CHART server software. The second is to use the CHART Comm Service installation package if available (recommended). The separate package is useful when the Comm Service is installed remotely because it is a much smaller package and can be transferred to the target computer more quickly. The smaller Comm Service installation package installs exactly like the larger package except that there is no need to select components.

4. If not installed already, install Java 1.5.0_09. From the installation CD (Install/JRE1.5.0_09), run jre-1_5_0_09-windows-i586-p.exe. Select the typical setup, and let the JRE install in the default location. JRE 1.5.0_09 should be installed on all FMS servers with a current CHART installation.

5. Move the JRE to the front of the System Path. My Computer->Properties->Advanced-> Environment Variables button. Edit the System Path variable so that C:\Program Files\Java\jre1.5.0_09\bin;C:\Program Files\Java\jre1.5.0_09\bin\client is at the front.

6. Complete the installation by following the on-screen instructions as follows:

a. Read the information on the Welcome screen and press the Next button to continue.

b. Read the Information window and press the Next button to continue.

c. Set the installation directory to D:\Program Files\CHART R3B2.06\ (that is, change to the D:\ drive if possible). Press the Next button to continue.


d. On the Select Components window select only the Comm Service. Press the Next button to continue. (Ignore this step if using the Comm Service install package).

e. On the Select Program Folder window, set the folder name to CHART R3B2.06. The data files will now be copied from the installation media to the target system.

f. On the TCP Port Assignments window, change the port numbers if necessary. The default values are usually OK unless some other application is already using one or more of these values, or if you are installing multiple copies of the service (see Section A.1.4.2). The initial TCP Port Assignment for the CHART R3B2 Comm Service is 9007 . If you are installing multiple Comm Services, the port assignment can be ignored because it’s configured on the multiple Comm. Service configuration page.

g. On the General Settings window, enter the name of the site where you are installing the servers. This name defaults to the host name, but could be any descriptive name for the site, such as “SOC Server Room”. Standard procedure is to leave it as the host name. Lastly, enter the number of days to keep log files (used to help the support personnel to troubleshoot problems) or accept the default. The standard value used for CHART is 7 days. Press the Next button to continue.

h. On the Required Services Locations window, edit the list so that only the FMS server that you are installing on (THIS server), is listed. Press the Finish button to finish the customized settings.

i. If multiple Comm Services are to be installed, check the install box for each comm. Service. Fill in the corresponding name and port fields. The name field should contain the port suffix. For example TeleB. If the Comm Service uses telephony, select the telephony checkbox. If only 1 Comm Service is being installed, just click next on the multiple comm. services page.

j. When the Setup Complete window appears, click on its finish button to complete the installation.

7. Check if install_log.txt is created under the installation directory. This file is only present when there are errors and lists the install steps completed.

8. Run the Port Configuration utility by double clicking “PortConfigUtility.cmd” in the Comm Service installation directory. (Section A.1.4.4 describes this in more detail.) This launches a Java utility that allows you to add Pots, ISDN, and voice modem ports to the FMS configuration. It is possible to copy in an old PortConfig file if the port configuration has not changed (see the top of this section for saving off the old PortConfig file). This may be edited by opening the existing file. Important note regarding copying PortConfig.xml files: No two CommServices running anywhere in the statewide CHART system can be using a PortConfig.xml file copied from the same original file. Copying an old PortConfig.xml file is acceptable ONLY when the CommService from which it is being copied will never run again. If this is not the case, or if unsure, create a new file. A new file is created by selecting New. Add in the appropriate COM port and modem initialization string (see section A.1.4.4). Save the file before exiting.


9. Edit the CommService.props file. Change the DefaultServiceApplication.ServiceName to CommService-<hostname> or CommService-<hostname>-<type>, where <hostname> is the hostname of the machine and type is “eicon”, “pots”, or “teleb”, etc. (e.g. CommService-elmrdfms1 or CommService-grnbltd3fms1-eicon).

10. If there are additional Comm Services which need to be added, perform the preceding two steps in each Comm Service’s directory. However, there should also an additional step to rename the js-CommSvc in the CommService directories. This allows the user to distinguish the CommServices when viewing through Windows Task Manager. Navigate to each CommService bin directory.

a. First, unregister the Comm Service by running CommRemoveService.cmd.b. Rename js-CommSvc to js-CommSvc-<port manager type>.exe (e.g., js-

CommSvc-eicon.exe).c. Edit the CommServiceReg file to use the new js-CommSvc-<port manager

type>.exe.d. Edit the CommRemoveService file to use the new js-CommSvc-<port manager

type>.exe.e. Run CommServiceReg.cmd.f. The service is now re-registered so it will run as js-CommSvc-<port manager

type>.exe.11. At this point the Comm Service(s) can be started. Rebooting the computer will start the

service, but it is not necessary and this is generally good to avoid rebooting if remoting in to the system. To restart the service without rebooting, go to the Control Panel and choose services. Start the “CHART R3B2.06 9A CommService”. If you installed multiple comm. services, start them as well.

12. Install patch R3B2.06 5. Copy <R3B2.06 Patch 5 Installation CD>: \FMS_Patch5\lib\jacorb.jar, idl.jar, CommService.jar to c:\Program Files\CHART R3B2.06\lib

13. Copy <R3B2.06 Patch 5 Installation CD>: \FMS_Patch5\lib\dll\ DialogicAPIUtilDLL.dll to c:\Program Files\CHART R3B2.06\lib\dll

14. Update each CommService properties file (e.g., c:\Program Files\CHART R3B2.06\bin\CommService\CommService.props). Add the following:# Number of seconds that should elapse between event channel# verification cycles. Event channel verification is used# to make sure that clients are still connected to all of the event# channels they have discovered. The verification process automatically# reconnects the client to an event channel if its connection is# found to no longer exist during verification.## Default value: 60DefaultServiceApplication.EventChannelVerificationIntervalSecs = 900

15. For each FMS server running a telephony CommService (i.e., hansocfms1 and grnbltd3fms1), update each Telephony CommService properties file (e.g., c:\Program Files\CHART R3B2.06\bin\CommServiceTELEB\CommService.props). Add the following:# The duration in 10ms increments for how long a DTMF tone should# play on a voice port#


FieldCommunicationsModule.DTMFDurationMS=20# The amplification in db for DTMF tones played on a voice port# Valid Range: -40 - 0 FieldCommunicationsModule.DTMFAmplificationDB=-20

.


Table A–2. CHART FMS Comm Service Details

ServerWindows Service Name

(in double quotes in *.Reg.cmd & *RemoveService.cmd files)

CHART Service Name(in .props file:

DefaultServiceApplicationServiceName

property)

NetConnectionSite(in .props file:

DefaultServiceApplicationNetConnectionSite

property)

PortManagerName(in .props file:

FieldCommunicationsModulePortManagerName

property)ANNAD5FMS1 CHART R3B2.06 9A CommService CommService ANNAD5FMS1 annad5fms1

AOCFMS1CHART R3B2.06 9B CommServiceTeleB CommServiceTeleB aocfms1 aocfms1-telebCHART R3B2.06 9C CommServicePOTS CommServicePOTS aocfms1 aocfms1-pots

AOCFMS2 CHART R3B2.06 9A CommService CommService aocfms2 aocfms2BALTOFMS1 CHART R3B2.06 9A CommService CommService BALTOFMS1 baltofms1BHTADMINFMS1 CHART R3B2.06 9A CommService CommService bhtadminfms1 bhtadminfms1BROOKD4FMS1 CHART R3B2.06 9A CommService CommService brookd4fms1 brookd4fms1CAB305FMS1 CHART R3B2.06 9A CommService CommService cab305fms1 cab305fms1CHURCHFMS1 CHART R3B2.06 9A CommService CommService churchfms1 churchfms1DAYTONFMS1 CHART R3B2.06 9A CommService CommService daytonfms1 daytonfms1ELMRDFMS1 CHART R3B2.06 9A CommService CommService elmrdfms1 elmrdfms1FREDLECFMS1 CHART R3B2.06 9A CommService CommService FREDLECFMS1 fredlecfms1

GRNBLTD3FMS1CHART R3B2.06 9A CommService CommService grnbltd3fms1 grnbltd3fms1-eiconCHART R3B2.06 9B CommServiceTeleB CommServiceTeleB grnbltd3fms1 grnbltd3fms1-telebCHART R3B2.06 9C CommServicePOTS CommServicePOTS grnbltd3fms1 grnbltd3fms1-pots

HANSOCFMS1CHART R3B2.06 9A CommService CommService HANSOCFMS1 hansocfms1-eiconCHART R3B2.06 9B CommServiceTeleB CommServiceTeleB HANSOCFMS1 hansocfms1-telebCHART R3B2.06 9C CommServicePOTS CommServicePOTS HANSOCFMS1 hansocfms1-pots

HANSOCFMS2 CHART R3B2.06 9A CommService CommService hansocfms2 hansocfms2HATUMFMS1 CHART R3B2.06 9A CommService CommService HATUMFMS1 hatumfms1HEREFORDFMS1 CHART R3B2.06 9A CommService CommService herefordfms1 herefordfms1

HUT0304FMS1* CHART R3B2.06 9A CommServiceCHART R3B2.06 9B CommService-direct

CommServiceCommServiceDirect

HUT0304FMS1HUT0304FMS1

hut0304fms1hut0304fms1

HUT0607FMS1 CHART R3B2.06 9A CommService CommService HUT0607FMS1 hut0607fms1HUT091011FMS CHART R3B2.06 9A CommService CommService hut091011fms hut091011fmsHUT1213FMS1 CHART R3B2.06 9A CommService CommService hut1213fms1 hut1213fms1HUT1819FMS1 CHART R3B2.06 9A CommService CommService HUT1819FMS1 hut1819fms1HUT21FMS1 CHART R3B2.06 9A CommService CommService hut21fms1 hut21fms1HUT2425FMS1 CHART R3B2.06 9A CommService CommService HUT2425FMS1 hut2425fms1HUT333435FMS1 CHART R3B2.06 9A CommService CommService HUT333435FMS1 hut333435fms1


ServerWindows Service Name

(in double quotes in *.Reg.cmd & *RemoveService.cmd files)

CHART Service Name(in .props file:

DefaultServiceApplicationServiceName

property)

NetConnectionSite(in .props file:

DefaultServiceApplicationNetConnectionSite

property)

PortManagerName(in .props file:

FieldCommunicationsModulePortManagerName

property)HUT3637FMS1 CHART R3B2.06 9A CommService CommService HUT3637FMS1 hut3637fms1HUT434445FMS1 CHART R3B2.06 9A CommService CommService hut434445fms1 hut434445fms1MSPFFMS1 CHART R3B2.06 9A CommService CommService MSPFFMS1 mspffms1TOC4FMS1 CHART R3B2.06 9A CommService CommService TOC4FMS1 toc4fms1

*Direct Ports installed off of this server


A.1.3.3 Post Installation Instructions for FMS Server

FMS server applications are installed to run as Windows services. This allows the server applications to run while no user is logged into the server machine and also provides the ability for automatic start-up of the servers when the server is booted. Depending on the type of installation being performed it may be necessary to modify the status of the FMS services. Follow the post installation steps below for the type of installation being performed.

Installation on New Hardware or Existing R3B2 System

1. Verify that the services are running. Use the Control Panel Services to check that all CHART2 Comm Services have a status of “started”.

2. Verify that there were no errors during the service start-up. This is done by checking each of the FMS Server’s log files for an entry that indicates the service has started successfully. The log files can be found in the \bin folder of the installation directory under the service folder for each service and are named “CommService_” with the current date appended, e.g., “CommService_061219”. These files are standard text files and can be viewed with Notepad (but not WordPad since the most current files are in use).

3. If installing on a new server, it is important to either:

a) Copy the *.id files from the old server’s <CHART Installation directory>\bin\CommService directory or directories to the same location(s) on the new server or

b) After starting the CommService on the new server, delete the old entry from the appropriate Trader by using the CHART GUI. Navigate to Administration->Traders- ><appropriate Trader> ->DirectPortManager. Delete the old entry. It will generally have a Failed Ping result. Repeat for the PortManager entry if necessary.

A.1.3.4 Port Configuration

If installing on a brand new FMS server from which an existing PortConfig file cannot be brought over (see previous section), after installing the CommService process on the FMS server run the port configuration utility (PortConfigUtility.cmd) located in the \bin\CommService folder in the installation directory. Use this utility to configure the available communications ports. This utility can also be used to modify a PortConfig file. More details are in section 3.8.3.

Use the File menu to create a new configuration file. Then from the Edit menu select the appropriate option to add direct connections, POTS modems, or ISDN modems for each communications port to be configured on the server.

For all types of ports enter a name to identify the port, check the Port Enabled box to enable the port, and then specify the system device name for the port (e.g., COM1). It is recommended that the system device name be used for the port name to avoid confusion (e.g., system device COM1 is given port name COM1). For the modems you will also need to enter the modem initialization string (see below) and the modem connect timeout (the length of time in minutes the modem will wait for a connection to be established after dialing). Use care in entering the initialization


strings to make sure that the number zero (“0”) is entered, not the letter “O”. (There are no instances of the letter “O” in the standard modem initialization strings given below.)

Modem Initialization Strings: Eicon ISDN ATE0Q0V1+ip6 POTS (Addco & PCMS DMS) AT&F0E0Q0V1F4&K0&Q4+MS=1,0,300,1200 POTS (High Speed) AT&F0E0Q0V1

For voice ports, system device name for the ports should be of format dxxxB1C1, which corresponds to the first port in the telephone socket module attached to the telephony board. Each telephony board supports 16 ports numbered sequentially from B1C1 to B4C4. So, port 2 on the socket module should be named dxxxB1C2, port 5 should be dxxxB2C1 and so forth.

When you have finished setting the port configurations make sure you use the File menu to save your changes before exiting the application

A.1.4 CHART Installation for Text To Speech ServicesA Text To Speech (TTS) Service must be installed before the CHART Message Utility Server will function correctly. Prior to R1B4 Patch 2, CHART supported only Lernout and Hauspie RealSpeak Server, version 1.2.0. With R1B4 Patch 2, CHART began supporting using TTS engines through the Microsoft Speech Application Programming Interface (MSSAPI), version 5.1. CHART will be able to use a TTS engine that integrates with MSSAPI 5.1. R3B2 and all releases beyond R1B4 Patch 2 are integrated and tested using Nuance Vocalizer 4.0 with Nuance SAPI 5.1 Integration for Nuance Vocalizer 4.0. The installation instructions for the MSSAPI 5.1/Nuance integration are in section A.1.4.1

A.1.4.1 MSSAPI 5.1/Nuance TTS Engine Installation

The MSSAPI 5.1/Nuance Text to Speech engine is used with Release 1 build 4 Patch 2 and after of CHART. There are five (5) steps to this installation process. Be aware that:

The CHART TTS CD is used to install the product. The Text to Speech server must be configured correctly. The Text to Speech server is configured to start automatically upon system start-up.

Note that several reboots are required during the installation.

The Nuance Vocalizer system uses ports for communications between the Nuance applications. The default ports are listed below:

Resource Manager: 7777

License Manager: 8471

Vocalizer TTS Engine: 32323, 22552

Refer to Microsoft Speech SDK 5.1 Reference for additional installation details. Refer to the Nuance Vocalizer 4.0.3 Release Notes, Developer’s Guide, Voice Pack Release Notes Version 4.0 for Nuance Vocalizer 4.0, Vocalizer Release Notes for Nuance SAPI 5.1 Integration for Vocalizer 4.0, and the Nuance SAPI 5.1 Integration for additional installation details.


The Java Runtime Environment (JRE) must be installed prior to installing the MSSAPI/NUANCE TTS products. If the JRE is not installed or if the JRE version is prior to 1.3.1_11, Vocalizer will attempt to install a JRE.

Installation on Microsoft Windows 2003

Install as follows:

1. Load CHART TTS Server CD. Install the packages in the order below.

a. Nuance Watcher Setup – Go into the Nuance\Watcher directory. Run the program “Nuance Watcher Setup.exe”. This will fail. Several files will need to be copied after the rest of the installation process completes.

b. Nuance Vocalizer 4.0 – Go into the Nuance\Vocalizer directory on the CHART TTS Server CD. Run the program “Setup.exe”.

i. Information Dialog Box OK

ii. Welcome Screen Next

iii. License Agreement Screen Yes

iv. Customer Information Screen

i. User Name: CHART

ii. Company Name: CHART

iii. Next

v. Select Components Screen

iv. Select Program files.

v. Select Java Tools.

vi. Make sure JRE is unchecked.

vii. Use Browse button to set the destination folder. This should be D:\Nuance\Vocalizer4.0. It is not necessary to navigate the directory tree within the browse function, just change the C: to a D:. (The setup program will not allow any spaces in this path.)

viii. Next

vi. Start Copying Files Screen Next

vii. Program will now be installed.

viii. Would you like to review the Release Notes Now Dialog No

ix. Setup Complete Finish. It is required that the machine be rebooted before continuing on with the installation, so set the checkbox to reboot the machine, or reboot manually before continuing with the next step.


c. Nuance Voice Pack: Laurie Woods –Go into the Nuance\VoicePack\LAURIE-VOICE-PACK-4-0-WIN32 directory. Run the program “Setup.exe”.

i. Welcome screen Next

ii. License Agreement Screen Yes

iii. Choose Destination Location Screen

i. Use Browse button to set the destination folder. This should be D:\Nuance\VoicePacks\v4\data\en-US\voices\lauriewoods\8k. It is not necessary to navigate the directory tree within the browse function, just change the C: to a D:. (The setup program will not allow any spaces in this path.)

ii. Next

iv. Start Copying Files Screen Next

v. Program will now be installed.

vi. Information Dialog OK

vii. Maintenance Complete Finish. (No reboot required for this step.)

d. Microsoft Redistributable Files – Go into the Microsoft\SAPI directory. Run the program “CHART MSSAPI51Setup.exe”.

i. Welcome Screen Next

ii. Ready To Install Screen Install

iii. Program will now be installed.

iv. Completing Screen Next

v. Installer2Go Screen Finish (No reboot required for this step.)

e. Nuance SAPI 5.1 Integration – Go into the Nuance\SAPI directory. Run the program “Setup.exe”.

i. Welcome Screen Next

ii. License Agreement Screen Yes

iii. Choose Destination Location Screen

i. Use Browse button to set the destination folder. This should be D:\Nuance\SAPI5.1. It is not necessary to navigate the directory tree within the browse function, just change the C: to a D:. (The setup program will not allow any spaces in this path.)

ii. Next

iv. Start Copying Files Screen Next

v. Program will now be installed.

vi. Would you like to review the Release Notes Now Dialog No


vii. Setup Complete Finish. It is required that the machine be rebooted before continuing on with the installation, so set the checkbox to reboot the machine, or reboot manually before continuing with the next step.

f. Nuance Watcher Setup (reprise). This step had failed previously. The appropriate registration and properties files will need to be copied from the installation CD.

i. Copy <Installation CD>:\Nuance\Watcher\watcherRegister.cmd to <Nuance Installation Drive>:\. Nuance\Vocalizer4.0\core\bin\win32.

ii. Copy <Installation CD>:\Nuance\Watcher\watcherUnRegister.cmd to <Nuance Installation Drive>:\. Nuance\Vocalizer4.0\core\bin\win32.

iii. Copy <Installation CD>:\Nuance\Watcher\watcherStartup.props to <Nuance Installation Drive>:\. Nuance\Vocalizer4.0\core\data.

iv. It may not be necessary, but the Installer at this point would have requested another reboot, so it may be a good idea to reboot the machine again at this point. If the machine is not rebooted, it may (or may not) be sufficient to merely start the “Nuance Watcher Daemon” from the Services applet.

A.1.5 Dialogic board installation/ConfigurationNote: Installer should also refer to separate FMS Server Build Instructions, which describes how to build an FMS Server. That document contains much more detail about installation of Dialogic boards as well as installation of other communications boards and more.

A.1.5.1 Setting the board identification number

If more then one board is to be used, each board must have a unique identification number. Turn the rotary switch (SW100) to select one of the 16 board ID settings.

A.1.5.2 Attaching the PEB Terminator (XTERM) (PEB MODE ONLY) Attaching the PEB terminator to the XTERM socket. To terminate the voice resource

board, use the resource module position. Insert the terminator in the resource module position, make sure that Pin 1 as indicated by black dot is positioned in the upper right corner in the XTERM socket.

A.1.5.3 Installing Dialogic Adapter Insert the Dialogic adapter in system PCI slot Attach station adapter to Dialogic board

A.1.5.4 Software Installation Configurationa) Insert CD in disk drive and run the setup program

Enter Name and company name <next>


b) A SETUP OPTIONSSelect Typical installation

c) Destination directoryD:\Program files\Dialogic <next>

d) Program folderUse the default program folder <next>

e) Current setting <next>Select run Dialogic board configuration <next>On the action menu select configure deviceChange the board interrupt to IRQ 7 <next>

f) Select the services menuSelect start modeClick automaticArrow down and start the services

A.1.6 CHART Web Server Installation InstructionsNOTE – If the web server software has already been installed and you are upgrading from a previous installation, see A.1.7: Upgrading an Existing CHART Web Server Installation.

Note that when a soft copy of this appendix is loaded into a browser, the links help to navigate through this installation and automatically launch the various installation steps. Ensure the ntiis_files subdirectory exists with the pictures.

OverviewThe following is an overview of the steps to install on a web server machine. These instructions assume that the machine is setup with Windows 2003 Server and Microsoft IIS installed.

1. Install the Java 1.5.0_09 SDK

2. (Optional)Install RSA 5.0 Agent for Windows 2003

3. Install Tomcat 5.5.9 Java Servlet Container

4. Install the CHART servlet

5. Configure the link between Tomcat and Microsoft IIS

6. Setup the CHART Web Site

7. Use SSL to protect the web site.

8. Setup RSA protection for the site.

9. (Optional) Enable the Java debugger


A.1.6.1 Install the Java 1.5.0_09 SDK

Execute the jdk-1_5_0_09-windows-i586-p.exe program that is included on the installation CD. Install to a directory named jdk1.5.0_09 on a hard drive that has ample space.

A.1.6.2 Install the RSA 5.0 Agent for Windows 2003

NOTE: Current CHART policy is to NOT make available over the public Internet, so this step is not needed unless there is a change in that policy.

These steps only need to be performed if the server will be accessed from the public internet.

1. Extract the agent softwareWin_Agent50_50.zip from the installation CD to the root directory on the drive of your choice. Example: D:\

2. Execute the agent installation program Agent.exe for the RSA agent. Follow on screen prompts. Detailed instructions are available in the RSA Agent Installation Guide (WindAgentAdmin) which is now located in the directory that you extracted the agent software to.

IMPORTANT NOTE: Until you can successfully authenticate from the RSA Agent software that you have just finished installing on the web server machine, you will not be able to authenticate from a web browser. If you are able to authenticate from the agent software, but are unable to authenticate from the browser, it may indicate a need to reboot the web server.

A.1.6.3 Install the Tomcat 5.5.9 Java Servlet Container1. Execute the jakarta-tomcat-5.5.9.exe program from the installation CD to install Tomcat. 2. During the installation procedure be sure to check the option to install Tomcat as a

service.


3. Install tomcat to a directory named tomcat-5.5.9 on a drive with ample space. The remainder of these instructions assume tomcat is installed on driver letter D in d:\tomcat-5.5.9

4. Accept the default of 8080 for the Connector Port, and choose an administrative login of admin, with no password. (This admin login will not be used because we will not install the admin console)

5. Verify that there is now a service installed on the machine called Apache Tomcat. This service should be setup to start automatically. (To view services, use StartAll ProgramsAdministrative ToolsComponent Services and click the “Services (Local)” item in the left hand pane)


6. Modify the default memory pool settings for Tomcat. These are set through the Tomcat Properties GUI. This is in the right hand side of the Windows taskbar (at the bottom of the screen), and is opened by clicking on it.

If the icon shown above is not present, start the properties GUI via StartAll ProgramsApache Tomcat 5.5Configure Tomcat

7. Once the properties GUI is open, click on the Java tab and set the “Initial memory pool” to 512 and the “Maximum memory pool” to 512.


Click Apply to save the memory values to the properties.

8. Ensure that the Working Path option in the Startup tab is set to d:\tomcat-5.5.9\bin


9. Click OK and then start (or restart) tomcat. If debugging needs to be added, do the steps in A.1.6.9 to minimize the restarts needed in the install process. Restart tomcat by accessing the Component Services window as described in step 5 above, and right click on Apache Tomcat and select Stop, and then again selecting Start.

10. Verify that Apache Tomcat is working. Open Internet Explorer (StartAll ProgramsInternet Explorer) and enter the following address: http://localhost:8080. You should see a page that informs you that you have setup Apache Tomcat successfully.

A.1.6.4 Install the CHART servlet1. Copy the chartlite.war file from the installation CD and save it to the webapps sub-

directory of tomcat. Example: d:\tomcat-5.5.9\webapps.

2. If Tomcat is running, it will automatically extract this file into a sub-directory under webapps called chartlite. If tomcat is not running, you will need to start it from the Windows 2003 Services Control Manager. (To view services, use StartAdministrative ToolsComponent Services and click the “Services (Local)” item in the left hand pane)

3. Wait for tomcat to fully expand the chartlite.war file into the chartlite directory. This should generally be finished within 5 minutes, and when complete, there should be 12 subdirectories in the chartlite directory.

4. Copy jar files to the tomcat endorsed directory. This is required to allow certain libraries used by CHART GUI to override those supplied within the Java runtime environment.


http://localhost:8080/

The files are to be copied FROM the following directory:D:\tomcat-5.5.9\webapps\chartlite\WEB-INF\lib

The Files are to be copied TO the following directory:D:\tomcat-5.5.9\common\endorsed

The files to be copied are listed below: CHART2WebInterface.jar avalon-framework-4.1.5.jar jacorb.jar logkit-1.2.jar ojdbc14.jar

5. Configure the configuration file parameters to suit your environment. The following is a list of parameters that are likely to need configuration. The file to edit is located in the webapps/chartlite/WEB-INF directory under Tomcat. Example: d:/tomcat-5.5.9/webapps/chartlite/WEB-INF/MainServlet.props a. chartlite.servlet.DBConnectString - This parameter contains the hostname/ip of the

database server machine and the port to use when connecting to the database. If a firewall exists between this machine and the database server machine, this address is likely to be the address of the firewall which will forward the packets on the specified port to the machine where the database server is actually running.

b. OAIAddr - This parameter needs to be set to the IP address that the CHART servers need to use when they attempt to reach the web server machine. This is likely to be the ip address of a firewall that will forward the packets on the iiop port to the web server.

c. ORBInitRef.TradingService0 – These parameters represent the trading services in the CHART system. The traders are represented with the parameters;

ORBInitRef.TradingService0ORBInitRef.TradingService1ORBInitRef.TradingService2 .. etc through to ORBInitRef.TradingService[n]

The values that are entered for these parameters should be as corbaloc object referencehostname or IPs, for instance;.ORBInitRef.TradingService0=corbaloc::localhost:9002/TradingService

The trading service local, or closest in the network, to the CHART web server installation should be listed first, i.e. ORBInitRef.TradingService0. Listing multiple trading services is optional however, and in the case of only one trading service ORBInitRef.TradingService0 should be used.


6. Use the Windows Component Services utility to restart the Apache Tomcat service. (To view services, use StartAdministrative ToolsComponent Services and click the “Services (Local)” item in the left hand pane.) Right click on the Apache Tomcat service and select “Stop”. When the service has stopped, right click the Apache Tomcat service and select “Start”.

7. Verify that the CHART servlet is running. Open Internet Explorer (StartAll

ProgramsInternet Explorer) and enter the following address: http://localhost:8080/chartlite/app. You should see an error page that informs you that you must access the system using https.

This error is to be expected and is not an indication of a problem. Seeing this error confirms that the CHART servlet is running; access via the required https will be set up in the steps that follow.

A.1.6.5 Configure the link between Apache Tomcat and Microsoft IIS1 Execute the isapi_redirect-1.2.10.exe program from the installation CD to install the ISAPI

connector. Install the ISAPI connector to d:\tomcat-5.5.9. 2 Next configure the ISAPI connector.

a The redirect log file does not install into d:\tomcat-5.5.9\logs due to a fault in the install sequence. It must be put in manually. Create a plain text file called isapi_redirect.log in d:\tomcat-5.5.9\logs\


http://localhost:8080/chartlite/app


b Run regedit (StartRun, enter “regedit” and click “OK”) and navigate to the key; [HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\Jakarta Isapi Redirector\1.0]

c The variable “log_file” needs to have log changed to logs, for example, “d:\tomcat-5.5.9\logs\isapi_redirect.log”

d Modify the variable log_level to “emerg”

e Close regedit.

3 Modify the Tomcat configuration files found in the directory d:\tomcat-5.5.9\conf\.It is recommended that you use Wordpad instead of Notepad to edit these files due to the absence of line feeds.

a Edit the workers.properties.minimal file and update the following fields to match the root address for Java and Tomcat. If these fields don’t already exist, add them as shown below and then edit if needed to match the Java and Tomcat locations.

## Java, Tomcat and OS environment#workers.tomcat_home=d:\tomcat-5.5.9workers.java_home=d:\jdk1.5.0_09ps=/

b Edit uriworkermap.properties, remove the references to jsp-examples and servlets-examples. Add the ajp worker for the chartlite webapp as shown below:

## Sites to be redirected to Tomcat#/chartlite=ajp13w/chartlite/*=ajp13w

Adding /jakarta virtual directory to IIS

4 Start the Internet Information Services (IIS) Manager. Use the menu under Start All ProgramsAdministrative Tools named “Internet Information Services (IIS) Manager.

5 Expand the top node of the tree control on the left for the “(local computer)” and then expand the node named “Web Sites”.


6 Rename the Default Web Site to “CHART GUI” as shown above. To do this, right click on the existing default web site and select rename, then type CHART GUI to replace the current name.

NOTE: The ISAPI Redirector install adds a virtual directory named jakarta. If you expand the tree for the CHART GUI web site and see a directory named jakarta, skip steps 7 thru 11 and continue with step 12.

7 Right click on the CHART GUI Web Site to view the menu and select NewVirtual Directory.

This will launch the Virtual Directory Creation Wizard:


8 Select Next, and enter an alias of “jakarta”

9 Select Next, and use the browse button to select a path


Browse to the tomcat-5.5.9\bin directory and click OK to select the path.


10 Click Next, and make sure Read and Execute permissions are enabled.

11 Click Next to complete the creation of the virtual directory.

12 Right click on the jarkarta virtual directory, and select the “Properties” menu. Verify the settings on the Virtual Directory tab appear as shown below.



Adding Jakarta ISAPI filter to IIS

13 The next task is to add the ISAPI filter isapi_redirect.dll to the server's IIS manager. Right click on the website name, CHART GUI, and choose Properties.


14 Click on the ISAPI filters tab

15 Click the Add button. Type in the filter name of “Jakarta Redirect” and then browse to d:\tomcat-5.5.9\bin\isapi_redirect.dll to set the Executable.


16 After setting the Filter name and Executable, click OK. The Jakarta Redirect will show in the list of filters with no status, and an unknown priority.

Adding Jakarta Web Services Extension to IIS

17 Right click on Web Services Extensions and select the “Add a new Web service extension…” menu.


18 Enter an extension name of Jakarta-Tomcat, then click the Add button to add a required file. Browse to tomcat-5.5.9\bin\isapi_redirect.dll, then click OK to add the file.

19 Make sure the “Set extension status to Allowed” box is checked, and click OK.

The Jakarta Tomcat extension will show in the list of allowed extensions with a green tick on it, indicating the Web Service Extension has been added and its status is Allowed, as shown below:


20 Restart IIS. Right click on the machine name (local computer), select the All TasksRestart IIS menu, and then OK.


21 Verify that the IIS/Tomcat redirector is working correctly. You should now be able to access the CHART site by visiting http://localhost/chartlite/app. You should see an error page telling you to access the site with a secure connection, such as the page shown below:

The appearance of this error is expected, and is not an indication of a problem.If you do not see this page, try a server reboot. We have found that sometimes IIS does not activate the ISAPI filter as it should. Otherwise, retrace the steps outlined in the sections above.

A.1.6.6 Set up the CHART web site

1 Extract the CHART web site files from the IISWebSite directory on the installation CD to c:\Inetpub

a Copy the entire chartlite subdirectory to c:\Inetpub

b When finished, you should have the following files copied to the web server:

c:\Inetpub\chartlite\index.htmlc:\Inetpub\chartlite\images\chart_logo.gif

2 Start the Internet Information Services (IIS) Manager (if not already running).


http://localhost/chartlite/app

3 Right click on the CHART GUI web site and select the Properties menu. View the Home Directory tab.


4 Click the Browse button and browse to the c:\Inetpub\chartlite directory to set the Local path.

5 Click on the Documents tab and click the Add button to add index.html as the default page content.


6 Make sure “Enable default page content” is checked, and remove any documents other than index.html that appear in the default content list.

Click OK to save the changes.

7 Test to make sure the web site is configured properly. You should now be able to access the CHART site by visiting http://localhost. You should see the CHART “splash” page as shown below.


http://localhost/

The “splash page” should redirect your browser to the CHART GUI application, and you will see an error page telling you to access the site with a secure connection, such as the page shown below:

The appearance of this error is expected, and is not an indication of a problem.

A.1.6.7 Use SSL to protect the web site

SSL requires the use of signed certificates. Certificates may be signed by a Certificate Authority (CA) or may be self-signed. The advantage to using a Certificate Authority is that browsers recognize the major certificate authorities and accept their certificates without prompting the user. For situations where prompting the user is acceptable (such as testing and possibly for internal use) a self-signed certificate has the advantage that it is free of charge and can be given a longer duration, reducing the maintenance of updating the certificate.

The general steps involved are as follows:

Export a Certificate Request from the Web Server Get the Certificate signed by a Certificate Authority (or self sign) Import the signed Certificate into the Web Server

A.1.6.7.1 Generate a Certificate Request1 Start the Internet Information Services (IIS) Manager (if not already running).


2 Open the Properties window for the CHART GUI web site. (Right click on CHART GUI and select Properties). View the Directory Security tab.

3 From the Directory Security tab, click Server Certificate. Click Next to begin the wizard.


4 Select Create New Certificate, then click Next

5 Choose Prepare the request now, but send it later and click Next.


6 Enter a name for the certificate. “CHART GUI” is recommended. Make sure Bit length is set to 1024, and the CSP option is not checked. Click Next.

7 Enter an Organization name of State Highway Administration, and an Organizational unit of CHART. Click Next.


8 Enter a common name that is the machine name of the server, which is supplied as the default value. (If this is a public facing web site (not the usual case for CHART), enter the fully qualified domain name such as mydomain.com.). Click Next.

9 Enter the geographic information for the CHART organization (not the server). Suggested values are County/Region (US), State/Province (MD), City/locality (Hanover). Click Next.


10 Enter a filename for the certificate request. C:\certreq.txt is the default value and is suggested. This name will be referred to later in the instructions. Click Next.

11 Review the information you have entered for the certificate request. Click Next.


12 The certificate request has been generated, and will be in c:\certreq.txt.

A.1.6.7.2 Get Certificate SignedYou may either get the certificate signed by a certificate authority (CA) such as Verisign or Thawte, or self sign the certificate. Follow section A.1.6.7.2.1 below to have the certificate signed by a well known CA, or follow section A.1.6.7.2.2 below to self sign the certificate. Since the current policy is to not make CHART GUI available to the public, a self signed certificate should be used.

A.1.6.7.2.1 Option A – Send Certificate to CA for signature

1 Copy the certificate request generated in step A.1.6.7.1 above (c:\certreq.txt) and send it to the certificate authority. (Note that many CAs have web sites to allow you to upload the certificate request)

2 When the CA provides your signed certificate, continue with step A.1.6.7.3

A.1.6.7.2.2 Option B – Create a Self Signed Certificate

Performing this procedure requires:

Windows 2000 or later

The certificate request (certreq.txt) generated in step A.1.6.7.1 above.

The OpenSSL tools from http://www.shininglightpro.com/products/Win32OpenSSL.html for Windows from Shining Light Productions. This is a Windows port of the popular OpenSSL toolkit.

Basic windows skills: creating directories, copying files, executing commands in a command window.


http://www.shininglightpro.com/products/Win32OpenSSL.html

NOTE: you do not need perform all of these steps on each server where CHART GUI is to be installed. Instead, it is recommended that you set up the OpenSSL toolkit and the certificate authority on a single computer and use that computer to sign certificates for all CHART GUI servers, skipping to the “Create IIS Certificate” step for servers 2-n.

Install and configure the OpenSSL toolkit

1. Get OpenSSL from the address above, and run the installer, accepting the defaults. These instructions assume OpenSSL is installed in C:\OpenSSL.

2. Add C:\OpenSSL\bin to your system path (Control Panel, System, Advanced, Environment Variables, System Variables) - this isn't strictly necessary but it makes things a lot easier.

3. Open a command window. (Start->Run, enter cmd, click OK)

4. Create a working directory. These instructions assume c:\ssl as the working folder.

c:\>md sslc:\>cd sslc:\ssl>

5. Download openssl.conf from http://www.dylanbeattie.net/docs/openssl.conf to your working folder. This file is also pasted into this document, at the end of this section. See the section entitled OpenSSL.conf file below.

6. Set up the directory structure and files required by OpenSSL: C:\ssl>md keysC:\ssl>md requestsC:\ssl>md certs

7. Create the file database.txt - an empty (zero-byte) text file as follows. (The ^Z is Ctrl-Z followed by a return.)c:\ssl>copy con database.txt^Z

C:\ssl>8. Create the serial number file serial.txt. This is a plain ASCII file containing the string

"01" on the first line, followed by a newline, as follows. (Again the ^Z is Ctrl-Z followed by a return.)C:\ssl>copy con serial.txt01^Z

C:\ssl>

Set up a Certificate Authority (CA)

1. First, we create a 1024-bit private key to use when creating our CA.:


http://www.dylanbeattie.net/docs/openssl.conf

C:\ssl>openssl genrsa -des3 -out keys/ca.key 1024Loading 'screen' into random state - donewarning, not much extra random data, consider using the -rand optionGenerating RSA private key, 1024 bit long modulus...........++++++..................++++++e is 65537 (0x10001)Enter PEM pass phrase: - choose a memorable pass phrase to use for this keyVerifying password - Enter PEM pass phrase: - type your pass phrase again for verification

The pass phrase will be requested whenever you use this key for anything, so make sure you remember it. This will create a file called c:\ssl\keys\ca.key, containing the certificate authority private key.

2. Next, we create a master certificate based on this key, to use when signing other certificates. Example answers are given – keep in mind that this certificate is for the certificate authority – the organization that will sign certificates.C:\ssl>openssl req -config openssl.conf -new -x509 -days 10001 -key keys/ca.key -out certs/ca.cerUsing configuration from openssl.confEnter pass phrase for keys/ca.key: - type your passphrase here.You are about to be asked to enter information that will be incorporatedinto your certificate request.What you are about to enter is what is called a Distinguished Name or a DN.There are quite a few fields but you can leave some blankFor some fields there will be a default value,If you enter '.', the field will be left blank.-----Country Name (2 letter code) [ ]: USState or Province Name (full name) [ ]: MarylandLocality Name (eg, city) [ ]: HanoverOrganization Name (eg, company) [ ]: State Highway AdministrationOrganizational Unit Name (eg, section) [ ]: CHARTCommon Name (eg, your websites domain name) [ ]: hansocchartlite.chart.state.md.usEmail Address [ ]: [email protected]

C:\ssl>This will create the CA certificate and store it as c:\ssl\certs\ca.cer

Create an IIS Certificate This is described in detail elsewhere on the web - see Microsoft Knowledge Base Article Q228821, available at http://support.microsoft.com/default.aspx?scid=KB;en-us;q228821. You should end up with a file called certreq.txt.

1. Copy the certreq.txt file into c:\ssl\requests

2. To sign the request, enter the following, all on one line:C:\ssl>openssl ca -policy policy_anything -config openssl.conf -cert certs/ca.cer -in requests/certreq.txt -keyfile keys/ca.key -days 10000 -out certs/iis.cer


http://support.microsoft.com/default.aspx?scid=KB;en-us;q228821

Using configuration from openssl.confLoading 'screen' into random state - doneEnter PEM pass phrase: enter pass phrase hereCheck that the request matches the signatureSignature okThe Subjects Distinguished Name is as followscommonName :PRINTABLE:'myCommonName'organizationalUnitName:PRINTABLE:'myOrganisationalUnit'organizationName :PRINTABLE:'myOrganisation'localityName :PRINTABLE:'myLocality'stateOrProvinceName :PRINTABLE:'myProvince'countryName :PRINTABLE:'GB'Certificate is to be certified until Feb 2 01:13:14 2004 GMT (360 days)Sign the certificate? [y/n]:y

1 out of 1 certificate requests certified, commit? [y/n]yWrite out database with 1 new entriesData Base Updated

C:\ssl>

Explanations of some of the command-line options used above follow:

o -policy policy_anything - specifies that we're using the 'policy_anything' policy from our openssl.conf file. This is a relaxed policy in which the name, country, etc. in the certificate don't need to match those used by the certification authority. Use -policy policy_match for a more restrictive CA.

o -config openssl.conf - specifies we're reading our configuration from openssl.conf in the current directory.

o -cert certs/ca.cer - specifies we're using our CA master certificate to sign the request.

o -in requests/certreq.txt - the certificate request we're signing.

o -keyfile keys/ca.key - the private key for our CA master certificate, which proves we're allowed to use it.

o -days 10000 - the time until the certificate will expire

o -out certs/iis.cer - the file in which to place our newly-signed certificate

3. Convert the signed certificate into x509 format for use with IIS: C:\ssl>openssl x509 -in certs/iis.cer -out certs/iisx509.cer

C:\ssl>

This will leave the new certificate in c:\ssl\certs\iisx509.cer - signed, sealed and ready to install


OpenSSL.conf file (for reference only – use in step 5 of configuring the openSSL)This section contains the contents of the openssl.conf file which is currently available at http://www.dylanbeattie.net/docs/openssl.conf.

# SSLeay example configuration file.# This is mostly being used for generation of certificate requests.## Original source unknown.# Modified 2003-02-07 by Dylan Beattie ([email protected])# http://www.dylanbeattie.net/docs/openssl_iis_ssl_howto.html

RANDFILE = .rnd

####################################################################[ ca ]default_ca = CA_default # The default ca section

####################################################################[ CA_default ]

certs = certs # Where the issued certs are keptcrl_dir = crl # Where the issued crl are keptdatabase = database.txt # database index file.new_certs_dir = certs # default place for new certs.

certificate = cacert.pem # The CA certificateserial = serial.txt # The current serial numbercrl = crl.pem # The current CRLprivate_key = private\cakey.pem # The private keyRANDFILE = private\private.rnd # private random number file

x509_extensions= x509v3_extensions # The extentions to add to the certdefault_days = 365 # how long to certify fordefault_crl_days= 30 # how long before next CRLdefault_md = md5 # which md to use.preserve = no # keep passed DN ordering

# A few difference way of specifying how similar the request should look# For type CA, the listed attributes must be the same, and the optional# and supplied fields are just that :-)policy = policy_match

# For the CA policy[ policy_match ]countryName = matchstateOrProvinceName = matchorganizationName = matchorganizationalUnitName = matchcommonName = suppliedemailAddress = optional

# For the 'anything' policy# At this point in time, you must list all acceptable 'object'# types.[ policy_anything ]


http://www.dylanbeattie.net/docs/openssl.conf

countryName = optionalstateOrProvinceName = optionallocalityName = optionalorganizationName = optionalorganizationalUnitName = optionalcommonName = suppliedemailAddress = optional

####################################################################[ req ]default_bits = 1024default_keyfile = privkey.pemdistinguished_name = req_distinguished_nameattributes = req_attributes

[ req_distinguished_name ]countryName = Country Name (2 letter code)countryName_min = 2countryName_max = 2stateOrProvinceName = State or Province Name (full name)localityName = Locality Name (eg, city)0.organizationName = Organization Name (eg, company)organizationalUnitName = Organizational Unit Name (eg, section)commonName = Common Name (eg, your website's domain name)commonName_max = 64emailAddress = Email AddressemailAddress_max = 40

[ req_attributes ]challengePassword = A challenge passwordchallengePassword_min = 4challengePassword_max = 20

[ x509v3_extensions ]# under ASN.1, the 0 bit would be encoded as 80# nsCertType = 0x40#nsBaseUrl#nsRevocationUrl#nsRenewalUrl#nsCaPolicyUrl#nsSslServerName#nsCertSequence#nsCertExt#nsDataType

A.1.6.7.3 Importing the Certificate

The following steps will be done on the server where you have installed CHART GUI.1 Copy the signed certificate, obtained from a well known CA, or self signed above, to the

CHART GUI server’s c:\ directory. (If you self signed the certificate using the instructions above, this file will be in c:\certs\iisx509.cer on the machine where the certificate was signed.)


2 Open the Internet Information Services (IIS) Manager if not already opened. (StartAll ProgramsAdministrative ToolsInternet Information Services (IIS) Manager). Open the Properties for the CHART GUI web site. View the Directory Security tab.

3 Click the Server Certificate button, and click Next.


4 Select Process the pending request and install the certificate and click Next.

5 Enter the location where you copied the signed certificate in step1. This will be c:\iisx509.cer if you created a self signed certificate in the sections above. Click Next to continue.


6 Enter the SSL port as 443 and click Next.

7 Verify the certificate data and click Next to continue.


8 Click on Finish to complete the import.

9 From the Directory Security tab, click the Edit button in the secure communications section of the page and ensure that the check the box to Require secure channel (SSL) is not checked.


10 From the Web Site tab, configure the ssl port for the site to 443.

11 Test SSL and normal access to the CHART web site by visiting https://localhost/. If you used a self signed certificate, you will see a warning, such as the one shown below.

You can click “Yes”. If you want to prevent the message in the future, you can click “View Certificate” and then “Install Certificate”.

After proceeding, you should see the CHART splash screen, and then be redirected to the CHART login screen. (You should not see an error telling you to access the site with a secure connection)


https://localhost/

A.1.6.8 Enable RSA protection of the site if it will be accessed via the internet

NOTE: Current CHART policy is to NOT make available over the public Internet, so this step is not needed unless there is a change in that policy.

1 Start the Internet Information Services (IIS) Manager (if not already running).

2 Go to the RSA SecurID tab.

3 Check Enable RSA and Protect this resource.

4 Make sure Use RSA Name Locking is not enabled.

5 Apply changes.

6 Test access to the CHART web site by visiting https://localhost.

a You should be challenged for an RSA username and password.

b After passing RSA authentication, you should see a CHART splash screen.

c After the splash screen, you should see a CHART login page.

A.1.6.9 (Optional) Enable the Java debugger

The Java debugger should be enabled if intermittent problems occur within the production environment. This will allow developers to more easily discover the cause of problems and provide resolutions. The debugger should only be enabled as a joint decision between MDSHA and the CHART development organization.

1. Open the Apache Tomcat Properties GUI. This is in the right hand side of the Windows taskbar (at the bottom of the screen), and is opened by clicking on it.

2. Add to the following java options on the Java tab of the Apache Tomcat Properties GUI;

-Xdebug-Xrunjdwp:transport=dt_socket,address=8222,server=y,suspend=n


https://localhost/

3. Click the OK button, and run regedit (StartRun type regedit and click OK) to verify the changes are in the following key:

[HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\Procrun 2.0\Tomcat5\Parameters\Java]

The multi-string value for Options should contain;

-Xdebug -Xrunjdwp:transport=dt_socket,address=8222,server=y,suspend=n


4. Restart the Apache Tomcat service. Open the Component Services window (StartAll ProgramsComponent Services, click on Services, right click on Apache Tomcat, select Stop. After stopped, right click on Apache Tomcat and select Start.

5. Verify the debugger is running. Open a console (StartRun, type in cmd and click OK) and type in netstat –a, this will show a list of processes. Check that a process is listening on port 8222.

A.1.7 Upgrading an Existing CHART Web Service InstallationIf the web server software is already installed and there is already a version of CHART running from a previous installation, the following steps explain how to upgrade given a new chartlite.war file:

1. Perform a temporary test installation of CHART (see Appendix C). Make sure the test installation works correctly and all target browsers are configured correctly before continuing.

2. On the CHART server machine, go to D:\tomcat-5.5.9\webapps and create a new directory called chartlite_new.

3. Using WinZip or equivalent, extract the contents of the new chartlite.war file into the chartlite_new directory (preserve the directory structure). (The WAR file is just a renamed ZIP file so you can rename the extension first if need be).


4. Copy MainServlet.props, velocity.props, and web.xml from the temporary CHART installation to the chartlite_new\WEB-INF directory.

5. Compare each setting in MainServlet.props, velocity.props, and web.xml in the chartlite_new\WEB-INF directory with the files of the same names from the chartlite\WEB-INF directory. Update appropriate settings in the chartlite_new version as necessary. When done, close all editors and make sure no windows have the directory open (Windows Explorer is OK to leave open). (Any windows accessing these files or directories will prevent the directories from being renamed in the following steps).

6. Create the directory D:\tomcat-5.5.9\inactive_chartlite_versions if it does not already exist.

7. Go to Windows Services utility and stop the Tomcat service. While Tomcat is down, users will not be able to use CHART, so perform the remaining steps quickly.

8. Rename the chartlite directory to chartlite_<version>, where <version> is the version number of the existing version. (If you are sure that this version will never be needed again, the directory can be deleted).

9. Move the chartlite_<version> directory to D:\tomcat-5.5.9\inactive_chartlite_versions.

10. Rename the chartlite_new directory to chartliteo11. Copy the following files from D:\tomcat-5.5.9\webapps\chartlite\WEB-INF\lib

to D:\tomcat-5.5.9\common\endorsed: CHART2WebInterface.jar avalon-framework-4.1.5.jar jacorb.jar logkit-1.2.jar ojdbc14.jarOracle-8.1.jar

12. For CHART R3B2.06 Patch 5, Copy <R3B2.06 Patch 5 Installation CD>: \GUI_Patch5\WEB-INF\classes\chartlite\servlet (the whole directory) to d:\tomcat-5.5.9\webapps\chartlite\WEB-INF\classes\chartlite. This will replace the two class files under the servlet sub-directory.

13. Copy <r3b2.06 patch 5 Installation CD>:\Delivery\R3B2_06_Patch5_CD Image\GUI_Patch5\templates (the whole directory) to d:\tomcat-5.5.9\webapps\chartlite. This will replace the one .vm file under the templates directory.

14. Switch to d:\tomcat-5.5.9\webapps\chartlite\ WEB-INF. Update MainServlet.props# Number of seconds that should elapse between event channel# verification cycles. Event channel verification is used# to make sure that clients are still connected to all of the event# channels they have discovered. The verification process automatically# reconnects the client to an event channel if its connection is# found to no longer exist during verification.## Default value: 60DefaultServiceApplication.EventChannelVerificationIntervalSecs = 900

15. Start Tomcat


A.1.8 Rolling Back a Previous CHART Web Service UpgradeIf CHART was upgraded from a prior version (as defined in the steps above) and you wish to roll back to using the old version, do the following:

1 Stop Tomcat2 Under the D:\tomcat-5.5.9\webapps directory, rename the chartlite directory to

chartlite_<version>, where version is the version of CHART that was just running. (If you are sure that it will never be needed again, the directory can be deleted instead).

3 Move the chartlite_<version> directory to D:\tomcat-5.5.9\inactive_chartlite_versions.

4 Move the D:\tomcat-5.5.9\inactive_chartlite_versions\chartlite_<original version> directory (that was created when the upgrade was performed) to D:\tomcat-5.5.9\webapps.

5 Rename the chartlite_<original version> directory to chartlite.6 Copy the following files from D:\tomcat-5.5.9\webapps\chartlite\WEB-INF\lib

to D:\tomcat-5.5.9\common\endorsed: CHART2WebInterface.jar avalon-framework-4.1.5.jar jacorb.jar logkit-1.2.jar ojdbc14.jarOracle-8.1.jar

7 Start Tomcat

A.1.9 Performing a Temporary CHART Web Service InstallationInstalling a new version of CHART on the “live”system is risky because if for some reason some features aren’t working properly it could disturb all users of CHART. Also if some browser configuration needs to be done, it is better to do it one workstation at a time rather than affecting all users’ browsers at the same time and having them all malfunction until the configuration changes can be made.1 Find a machine (other than the machine where CHART is currently running) that can be

used to run CHART. This machine should be on the same network as the CHART web server machine. The machine should have the same access to the Trader and the other CHART application server services.

2 Execute the jakarta-tomcat-5.5.9.exe program from the installation CD to install Tomcat, and install Tomcat to D:\tomcat-5.5.9.

3 Copy the chartlite.war file from the delivery CD to D:\tomcat-5.5.9\webapps4 Run D:\tomcat-5.5.9\bin\startup.bat and let it run for a couple of minutes while Tomcat

creates the chartlite directory under webapps, extracts the contents of chartlite.war into the new directory, and then tries to run the CHART servlet. However CHART will start displaying errors on the Tomcat screen because it is not configured correctly yet. When you see CHART log errors in the Tomcat window, stop Tomcat by hitting CTRL-C.

5 Edit D:\tomcat-5.5.9\webapps\chartlite\WEB-INF\MainServlet.props, and make sure the settings are correct. You may want to compare each setting with the same setting from the MainServlet.props from the running CHART installation, although not all settings may be


present in the old file. Also be aware that some settings may have been changed to fix bugs or workaround problems.

6 Copy the following files from D:\tomcat-5.5.9\webapps\chartlite\WEB-INF\libto D:\tomcat-5.5.9\common\endorsed:

CHART2WebInterface.jar avalon-framework-4.1.5.jar jacorb.jar logkit-1.2.jar ojdbc14.jarOracle-8.1.jar

7 Run D:\tomcat-5.5.9\bin\startup again. If MainServlet.props is configured correctly, CHART should display normal looking messages this time.

8 Open a browser on the same machine and verify that CHART is running by using the following URL: http://localhost:8080/chartlite/app , and you should see the Login page with operations centers in the list.

If CHART is working when tested from a browser on the same machine, it should also work from another machine using a URL such as: http://<temp-chartlite-machine>:8080/chartlite/app where <temp-chartlite-machine> is the machine name or IP address of the machine where the temporary CHART installation was done.

Once this test installation is working properly, copy the following files from D:\tomcat-5.5.9\webapps\chartlite\WEB-INF: MainServlet.props, velocity.props, and web.xml. These files will be very useful when installing on the real server, as they represent a known working configuration.

When the test installation is no longer needed, you can uninstall Tomcat from the machine or delete the D:\tomcat-5.5.9 directory.

A.1.10 CHART Workstation Configuration Instructions

Overview

The following is an overview of the steps to configure a browser to support CHART. These instructions assume that the Workstation machine has Windows XP installed however these instructions should work for Win2000 as well.

1. Is Browser Installation Necessary?

2. Verify Browser Installation

3. Browser Options

4. Verify Java Plugin

5. HAR Audio Format Patch



A.1.10.1 Is Browser Installation Necessary?

The State Operations Center has standardized on Microsoft Windows XP. The default browser installation for XP is Internet Explorer 6.0. Starting with CHART R3B2, Internet Explorer 7 is supported as well. 6.0 is also the minimum of the approved versions for CHART. If your workstation already has IE 6.0 or later installed you may skip to Verify Configuration.

Internet Explorer's version can be found by double-clicking the Internet Explorer icon on the desktop. Under the help menu, choose About Internet Explorer and look for the version 6.0 or above.

Note that Firefox may also be used to access CHART. Formal testing has not been done using Firefox so it is not officially supported, however several developers frequently use Firefox and there are no known issues.

A.1.10.3. Verify Browser Installation

To test your ability to connect to the site, double-click on the Internet Explorer icon on the desktop and type the location of the CHART web server in the Address field (if a Security Alert dialog asks if you want to proceed, choose View Certificate and Yes if you trust the issuer). If you do not see the CHART splash page followed by the CHART login page then review this procedure or contact your administrator to verify the CHART address and the ability of your computer to reach it.

A.1.10.4 Browser Options

To set up your browser to automatically go to the CHART website whenever Internet Explorer is started, navigate to the CHART page, and before logging in click on Tools->Internet Options->General tab, hit the Use Current button and hit the OK button.

Browser Security Settings

CHART uses features that require several security settings be enabled in the browser (or they can be set to “prompt” if applicable). If you are connecting to CHART via a LAN, then ensure these settings are enabled in the “Local intranet” zone, otherwise you will need to enable them for the “Internet” zone or add CHART as a trusted site. These settings may be different for various versions of IE and Windows Service Packs, let alone other browsers. To make sure all required security settings are enabled, it is recommended that the CHART URL be added as a “trusted site”.

In Internet Explorer 6.0 and later, go to Tools->Internet Options->Security tab, and click on the “Trusted Sites” icon and then add the CHART URL as a trusted site.


Setting IE 6.0 SP1, SP2, IE 7.0

Used for

Download signed ActiveX controls

Y Semi-automatic installation of Sun JRE on client browser. (can be set to “prompt”)

Initialize and script ActiveX controls not marked as safe

Y Updating the display in the DMS message editor pages.

Run ActiveX controls and plugins

Y Lane display and DMS message editors

Allow cookies that are stored on your computer

N/A Cookies are used to remember the last op center the user logged into.

Allow per-session cookies (not stored)

N/A Required for logging in.

File Download Y Listening to HAR audioSubmit non-encrypted form data

Y Submitting forms (if not using the https URL)

Active Scripting Y Enables Javascript, used for many featuresUserdata persistence Y Cookies are used to remember the last op

center the user logged into.

NOTE – the above list may or may not be complete.

Browser Functionality Settings

Under Internet Options->Advanced tab, the following must be enabled: Show pictures (used for device/event icons and the small DMS display images) Play animations in web pages (used for animating the small DMS display images)

Internet Explorer 7.0 Tab Settings

If using Internet Explorer 7.0, users may wish to take advantage of the browser’s tabbed browsing feature. Under Internet Options, navigate to the “General” tab and click the “Settings” button in the “Tabs” section and enable the following setting:

Enable Tabbed Browsing (requires restarting Internet Explorer)

To display the CHART home page and working window in separate windows, enable the following setting:

Always open pop-ups in a new window

To display the CHART home page and working window using tabs in a single window, enable the following setting:

Always open pop-ups in a new tab


Users with multiple monitors will most likely want to open pop-ups in a new window. Users with a single monitor may or may not want to open pop-ups in a new tab. The disadvantage of using tabs with CHART is that internet explorer does not automatically switch to display the working window tab when you click on a link on the home page, so an extra click is required to display the working window tab after making a choice on the home page.

NOTE – the above list may not be complete.

A.1.10.5 Verify Flash Plugin

CHART uses a “Rich Internet Application” for the content of its home page, and several other pages in the application. These pages require the Adobe Flash Player, version 9.0 or later to be installed, or a gray border will be shown instead of the current content. The Flash Player can be downloaded from the Adobe web site at http://www.adobe.com/products/flashplayer/. If a flash player is already installed, its version can be verified by logging into CHART, right clicking the mouse over an open area of the home page application. A popup menu will appear and if it has an item “About Adobe Flash Player 9…”, then flash player 9 is installed. You can click the menu to determine the exact (minor version) of Flash Player 9 that is installed.

A.1.10.6 Verify Java Plugin (Optional)

CHART uses image-based solutions to allow lane closures to be specified and to show the "true display" of a DMS message while it is being edited. These solutions use standard web technologies and no longer require a java plugin. An applet is also not required for recording HAR messages, as a user can record a message externally using a sound recording program and upload the audio file. If a user chooses to record HAR messages through CHART, however, the Java Plugin must first be installed in his or her browser. Follow the instructions below to verify that the plugin is installed..

1 Log into CHART and navigate to a Traffic Event Details page or a page showing traffic event lane graphicsHAR editor page. If you see the lane graphic recording control displayed, a compatible Java Plugin is already installed.

2 If you are prompted to install the Sun JRE, click on Yes to accept the installation. After the JRE is installed you should see the lane graphics recording control displayed.

3 If you were not prompted and do not see the lane graphics recording control, open another browser and type in the address bar: http://<chartlite-server>:8080/chartlite/install/jre-1_5_0_09-windows-i586-p.exe (substituting the CHART server machine name or IP address for <chartlite-server>). You should be able to download and install the JRE.

If you do not have sufficient Windows user rights, an administrator may need to run the JRE installation program.


http://www.adobe.com/products/flashplayer/

A.1.10.7 HAR Audio Format Patch For Windows Sound Recorder

HAR audio messages recorded in an unsupported audio format have been observed to cause serious problems with the HARs in CHART. Therefore it is important that operators choose a supported format when recording the audio (or convert to a recorded format when saving).

If Windows Sound Recorder is used to record HAR messages, by default it always starts up with a format that is incompatible with the HARs. This patch may be installed to set the default recording format in Sound Recorder to CCITT u-Law 8 kHz 8 bit8 bit mono (this format was found to work with the HARs during earlier testing of CHART). By making this the default recording format, operators will not need to remember to convert audio to a good format each time they use Sound Recorder. (Unsupported formats are blocked by CHART).

This patch should work on Windows 2000 and Windows XP.

To install the patch, double click on the following file on the delivery CD: Install\Workstation\HARSoundRecorderPatch\config_sound_recorder_for_correct_HAR_format.reg

A.1.11 CHART Web Service Properties File SettingsThe following table provides information about the CHART web service settings that exist in the properties file, located in D:\tomcat-5.5.9\webapps\chartlite\WEB-INF\MainServlet.props. Note that after making changes in the properties file, Tomcat must be restarted before the changes will take effect.


Property Name Default Value Description

chartlite.servlet.UseDatabase true Determines if the database should be used for folders and shift handoff reports. This value exists for testing and should always be set to true in the production environment.

jdbc.drivers oracle.jdbc.driver.OracleDriver

Specifies the name of the JDBC driver to be used. This should not be changed except by development staff for the proper driver specified must be included in the software distribution.

chartlite.servlet.DBConnectString None – to be set during installation

The connection string for the database. Should have the following form for an Oracle database:

jdbc:oracle:thin:@<hostname>:<port>:<SID>

chartlite.servlet.DBUserName CHARTLiteService

The name CHART uses to log into the Oracle database. This name must be obtained from the CHART Database Administrator.

chartlite.servlet.DBPassword None – to be set during installation

The password CHART uses to log into the Oracle database. This password must be obtained from the CHART Database Administrator.

chartlite.servlet.DBMaxConnections 2 The number of concurrent database connections opened by CHART. Only folder changes and edits to shift handoff reports require database operations, thus numerous connections are not needed.



chartlite.servlet.DBConnectionMonitorIntervalMillis 10000(10 seconds)

The interval at which database connections are checked to see if they are still in use. This check prevents misbehaved code from “leaking” a database connection. Connections found not to be in use are returned to the free pool within the application for reuse.

chartlite.servlet.LogFileName chartlite_ The prefix for log files created by CHART. The date of the log file is appended to the given name.

chartlite.servlet.LogKeepDays 7 The number of days of CHART log files to keep around. Log files older than this number of days are automatically deleted.

chartlite.servlet.LogLevel PRODUCTION The level of log messages to be written to the CHART log files. A level of DEBUG includes messages useful during software development. A level of PRODUCTION specifies the output of messages that are pertinent to the production environment, such as all errors and warnings but not trace messages. The logging level CHART’s System Profile page will override this setting, if it has been set in the system profile.



chartlite.servlet.OrbConnectTimeoutMillis 5000(5 seconds)

The amount of time the CHART web server should wait for a connection to be established with CHART application server to complete an operation on the application server. If CHART produces error messages stating it is unable to connect to the CHART server when the CHART server is known to be available and the network connection between CHART and the CHART server is known to be good, this value can be increased to attempt to solve the problem.

NOTE – this should match the value of the JacORB property:jacorb.connection.client.connect_timeout



chartlite.servlet.OrbRequestTimeoutMillis 30000(30 seconds)

The amount of time the CHART web server should wait for the CHART application server to complete an operation after it has been requested. Note that this timeout starts after a connection to the application service has been established. Note also that long running operations are performed asynchronously, and that CHART is given an “in progress” response almost immediately and is informed of the command’s progress via a command status object. The default value should be more than adequate for this setting. If CHART should indicate that an operation has not succeeded due to a CORBA timeout and the application server is known to have eventually processed the command, this value can be increased to attempt to determine the problem. Keep in mind, however that the application server should respond to all requests in a timely manner, thus other solutions should be investigated.

NOTE – this should match the value of the JacORB property:jacorb.connection.client.pending_reply_timeout

chartlite.servlet.RequireHTTPS true Flag that indicates that CHART should reject all requests that are not delivered using HTTPS. This value should be set to true in the production environment, and can be set to false in the development environment to keep each developer from having to setup a server encryption key.



chartlite.servlet.httpPort 80 The port that the web server uses for HTTP requests. CHART uses this for playing HAR audio files via HTTP because Windows Media Player has a bug (or security feature) that prevents WAV files to be played via HTTPS.

chartlite.servlet.ErrorTemplateFile Error.vm The name of the template used for error messages. If an alternative Error page is developed, this value can be changed rather than changing Error.vm itself to allow you to easily revert back to the originally deployed error page.

chartlite.servlet.FramingTemplateFile EnclosingTemplate.vm

The name of the template used for the main application layout, such as the page heading, the location of the navigation links, the page footer, etc. If a new look and feel for the web site is desired, create an alternative template similar to EnclosingTemplate.vm. Then change this property to have the name of the alternative template name. This allows you to easily revert back to the distributed template and original web site look and feel.

chartlite.servlet.LoginTemplateFile Login.vm The name of the template that contains the Login page. If an alternative login page is desired, create a file similar to Login.vm and change this setting. You can then easily revert back to the original login page if needed.

chartlite.servlet.displayWorkingPageMenu false Flag used to enable or disable the “Toggle Menu” link on the working window. This link allows a navigation menu to be displayed on the working window.



chartlite.servlet.NavBarTemplateFile TextNavBar.vm The name of the template that contains the navigation bar for the application. If an alternative navigation bar (such as an applet) is desired, create a template similar to TextNavBar.vm and place its name in this setting. You can then easily revert back to the original navigation bar if needed.

chartlite.servlet.ViewOnlyOpCenterName ViewOnly The name of the operations center defined in CHART where all users considered “View Only” will be logged in. CHART will also prevent any non View Only user from logging into this operation center. Ensure that CHART has an operation center with the name specified here (case sensitive) or view only users will not be able to log into the system.

chartlite.servlet.OperatorSessionTimeoutSecs 300(5 minutes)

The number of seconds that must elapse without a web page “hit” from an operational (non View Only) user before the user is considered timed out. Once timed out, the user’s CHART login session will be removed and CHART will eventually consider the user no longer logged in, possibly prompting an uncontrolled resource condition. Keep in mind that every page of an operational user has an updating status frame at the top of the page to detect instant messages and thus this value can be adjusted downward if the CHART detection of uncontrolled resources is not timely enough. Do not adjust this value lower than the frequent page refresh time in CHART, and in general it should be set to be at least twice the configured frequent page refresh time.



chartlite.servlet.ViewOnlySessionTimeoutSecs 900(15 minutes)

The number of seconds that must elapse without a web page “hit” from a View Only user before the user is considered timed out. Unlike operational users, View Only users can casually leave the CHART site without logging out. If they have not hit a page on the CHART site within the number of seconds specified by this setting, they will be considered timed out and will be automatically logged out from CHART. If the user then returns to the site, they will be prompted with the login page. This value can be adjusted upward if View Only users complain about being logged off when they are inactive. A balance must be struck, for until the user is timed out (or logs out), CHART allocates a small amount of resources to the user. A large timeout value should not be problematic for hundreds of users, but if the system starts to have thousands of users, this value will be more critical for freeing system resources (memory) in a timely manner.

chartlite.servlet.InstantMsgNumSendThreads 5 Number of threads to dedicate to the sending of instant messages.

chartlite.servlet.StrippedBrowserEnabled true This flag indicates if the CHART application should launch a new stripped down browser window when an operational user logs in. At the time of the software writing, the stripped down browser was desired, however this setting exists to allow the system to use the user’s current browser window (complete with forward and back buttons, etc.) when an operational user logs in instead of launching a new window by setting this value to false.



chartlite.servlet.TrapUserEnabled true This flag indicates if the CHART application should prevent operational users from closing their browser without logging out. If set to false, the application will allow users to close their browser without logging out and the OperatorSessionTimeoutSecs setting will be used to automatically logout operational users that have left the site. Setting this to false may lead to more instances of uncontrolled resources if users fail to relinquish control of resources before leaving the site or closing their browser.

chartlite.servlet.CmdStatusRemovalIntervalSecs 60 The number of seconds that will elapse between each check the system does to determine if there are completed successful command status objects that are to be removed from the system. Once removed from the system, these objects will no longer appear on the user’s command status page. Note that in progress and failed command status objects remain in the system until the user manually deletes them or logs out.

chartlite.servlet.DefaultLaneConfigurationName 4 lanes each direction with shoulders

The name of the default standard lane configuration to select in the lane configuration list when a traffic event does not have a configuration defined. The configuration name specified must exist in the CHART system.

chartlite.servlet.AudioStreamTimeoutSecs 120(2 minutes)

The number of seconds CHART should wait to stream audio data. This value can be adjusted upwards if CHART indicates it has timed out waiting for audio data during normal operating conditions.



chartlite.servlet.AudioStreamChunkSize 4096(4K)

The number of bytes to be streamed in each chunk of audio data passed from CHART.

chartlite.servlet.monitorSlotPaddingSec 5 When performing a Monitor HAR Slot operation, the amount of extra time that will be recorded in addition to the length of clip in the slot. Value is in seconds.

chartlite.servlet.PreferredTTSConverter None The name of the Text To Speech converter to use when CHART needs text converted to speech to allow the user to preview a clip. A setting of None causes CHART to discover an available converter and use it. A specific converter may be specified to cause CHART to use a particular converter that is on a faster network segment than other converters (for example if one is on the same LAN as CHART while another one is on the WAN, the one on the LAN should be preferred). Regardless of this setting, CHART will fail over to any available TTS converter if the preferred converter is unavailable.

chartlite.servlet.NumDiscoveryThreads 10 The number of threads CHART should use when discovering software objects. CHART software object discovery is performed when CHART initializes and then periodically during runtime to discover objects that were not otherwise discovered via the event pushing mechanism. The discovery can also be performed manually using the Perform Discovery link within the CHART navigation bar.

chartlite.servlet.NumProcessingThreads 20 The number of threads CHART should use for performing asynchronous processing, such as CORBA event handling.



chartlite.servlet.DiscoveryIntervalSecs 86400(30 minutes)

The number of seconds between automatic CHART application server object discovery cycles. The CHART server objects are discovered during startup and then changes to objects as well as additions and deletions of objects are communicated to CHART via the CHART server event pushing mechanism. CHART includes an automatic periodic discovery interval to allow CHART to continue to maintain the latest CHART information, even if the CHART event pushing mechanism were to fail.

chartlite.servlet.ArbQueuePollIntervalSecs 0 This value controls the feature in CHART that allows it to maintain a current status of CHART arbitration queues without the use of the CORBA notification service. When set to 0, CHART does not poll the arbitration queues for status. When set to a value greater than 0, this specifies the number of seconds between each poll of the CHART system for the current arbitration queue status. When enabled, 30 seconds is a reasonable value.

chartlite.servlet.useStreamingAudio false Flag that indicates whether to use streaming audio for Monitor HAR and Monitor HAR Clip. If audio streaming is disabled, the servlet will wait for audio to be accumulated in the servlet before the user can begin hear the audio. However, the use of streaming has been known to cause problems with Internet Explorer and Windows Media Player 9 and 10, which is why it is disabled by default. Perhaps it will work on a future version of IE / WMP.



chartlite.servlet.AsyncAudioCleanupIntervalSecs 300 The number of seconds between the check and clean-up of idle audio request objects. These objects are used to asynchronously collect audio from the CHART system when a user chooses to preview a clip or monitor a HAR or HAR slot. A mechanism exists to cleanup these objects when a user cancels a request or when audio has been delivered to the user’s browser, however this periodic clean-up cycle exists to make extra sure that resources are not leaked.

chartlite.servlet.AsyncAudioCleanupAgeSecs 300(5 minutes)

The age an audio request object must be before it is eligible for clean-up. During each cleanup interval (see above), each outstanding audio request object is checked for its age. If it is older than the value specified by this setting, it is cleaned up.

chartlite.servlet.AudioFileCleanupIntervalSecs 300 (5 minutes) Interval at which the system should check the har audio directory for old files and delete them.

chartlite.servlet.AudioFileCleanupAgeSecs 1800 (30 minutes) Age an audio file must reach to be eligible for automatic cleanup.

chartlite.servlet.helpPath WebHelp/ChartLiteHelp.htm#

The path to the main help page. This value is combined with a help page name to form the URL of a help page for a specific CHART web page.

chartlite.servlet.helpMappingFile help_mapping.txt The name of the file that contains a mapping between CHART web pages and their corresponding help page.

chartlite.servlet.helpDefaultPage ChartLiteHelp.htm

The name of the help page to be shown if a mapping for a particular CHART web page does not exist in the helpMappingFile.



chartlite.servlet.TempObjStoreCleanupSeconds 60 This setting specifies how frequently the system should check for abandoned temporary web page data. Temporary data objects are used when a user works on a task where data is temporarily saved before displaying another page, such as in the DMS editors. If the user leaves the web page, the data is cleaned up after a while.

chartlite.servlet.TempObjMaxAgeMinutes 30 This setting specifies how old temporary web page data can be before it is considered “abandoned” and cleaned up. Temporary data objects are used when a user works on a task where data is temporarily saved before displaying another page, such as in the DMS editors. If the user leaves the web page, the data is cleaned up after a while.

chartlite.servlet.MaxTraderHops 0 The max trader links that should be followed if linked traders are found during a query. A value of less than one means that trader links should not be followed. In this case the query will return only objects stored in the specified trader. A value of 1 or greater means that links should be followed up to the specified number of hops.

chartlite.servlet.audioFormat.encoding*chartlite.servlet.audioFormat.sampleRate*chartlite.servlet.audioFormat.sampleBits*chartlite.servlet.audioFormat.channels*chartlite.servlet.audioFormat.frameSize*chartlite.servlet.audioFormat.frameRate*chartlite.servlet.audioFormat.bigEndian*

none These settings specify audio formats that are supported by the CHART system. The * in each setting name shown is replaced with an index number of the audio format that is supported. For example, for the first audio format supported, this entire group of settings is included with the * replaced by 0. If a second audio format is supported, the entire group of settings is repeated, this time with the * replaced by 1.



chartlite.servlet.dms.charSize_X none List of acceptable DMS character sizes. The sizes must be encoded in the format: W x H, and the index (X) starts at 0. The default character size is the first one (X = 0)

chartlite.servlet.dms.defaultGeometry_X none The default geometries are used in the DMS stored message editor when no DMSs with the given geometries are present in the system. There can be multiple listings, and the index (X) starts at 0. Each geometry is formatted like: “3x20, 2 pages, 5x7 font”. The font should be consistent with the settings that specify the font sizes: charlite.servlet.dms.charSize_*.

chartlite.servlet.AllowSimulatedPortManagers false This setting allows simulated port managers to appear in the port manager lists when adding a device or editing the device configuration. This is useful for testing purposes. Device communications will only be simulated if the CHART server props files are configured to allow simulation.

chartlite.servlet.DefaultHARMaxRecordingSeconds 360 Default value for the max recording time when adding a HAR to the system.

chartlite.servlet.DefaultPortMgrTimeoutSeconds 20 Default value for port manager timeout when adding a device to the system.

chartlite.servlet.BannedWordLoginTimeoutSeconds 900 (15 minutes) Property that specifies the amount of idle time (in seconds) before a user is re-prompted for their password in order to view the banned word list. Idle time is defined as time in which no dictionary management activities are performed.



chartlite.servlet.FirstAvailableServiceRemoteUseMinutes

30 Property that specifies the amount of time (in minutes) that the system will use a remote instance of a first available service object (Dictionary, Communications Log, User Manager; and for creating alerts, libraries, notifications, plans, schedules, op centers, monitors, video tours) before it will attempt to use a local service object again. Local service objects are defined as objects that are discovered in the primary trader (ORBInitRef.TradingService0). All offers found in other traders will be considered remote. Set this value to -1 if remote objects should be used indefinitely (until failure).

chartlite.servlet.trafficevents.FirstAvailableServiceRemoteUseMinutes

5 Property that specifies the amount of time (in minutes) that the system will use a remote instance of a first available service object for creating Traffic Events before it will attempt to use a local service object again. Local service objects are defined as objects that are discovered in the primary trader ORBInitRef.TradingService0). All offers found in other traders will be considered remote. Set this value to -1 if remote objects should be used indefinitely (until failure).

chartlite.servlet.forceHttpAudioAppletComms false Specifies whether the audio applet should be forced to use http to upload and retrieve audio, even if the user is accessing the system via https. Setting this to true allows the applet to work on browsers that have the java 1.3.1 plugin which do not support https.

chartlite.servlet.logToStandardOutput false This is used to disable writing the output of the logging system to standard output. If logging to standard output is enabled, it will be captured in Tomcat's log files, which can lead to very large log files.



chartlite.servlet.enableViewHeap true This is used to enable a link that is used to view heap usage and manually perform garbage collection.

chartlite.servlet.TerminateCameraSessionsOnLogout true Specifies if camera control sessions are terminated when a user logs out.

chartlite.servlet.useOriginalShiftHandoffReport true Flag indicating whether to use the original Shift Handoff Report. This can be used instead of, or in addition to, the Wiki Shift Handoff Report.

chartlite.servlet.wikiShiftHandoffReportLinkName Wiki Shift Handoff Report

The name of the link to the Wiki shift handoff report, if the link is enabled via the URL.

chartlite.servlet.wikiShiftHandoffReportURL none The URL of the Wiki shift handoff report web site. Leave blank to turn off the Wiki Shift Handoff Report link.

chartlite.servlet.EORSRefreshIntervalMinutes 30 The refresh interval (in minutes) for querying the EORS system for its permits. If the value is <= 0, the EORS system will not be contacted.

chartlite.servlet.stopActiveTourBeforeStartTour false Flag indicating whether CHART will issue a command to stop an active tour before issuing a command to start a new tour.

chartlite.servlet.resolveEventChannelFactoryAttempts 3 The maximum number of times to try to resolve the event channel factory.

chartlite.servlet.defaultStates MD:Maryland:24 A comma delimited list of states to appear in the list of states when specifying a traffic event’s location if the server cannot be contacted to obtain the list of states. Each comma delimited entry includes the state code, state name, and FIPS code.

chartlite.servlet.defaultStateCode MD The state code of the state to be selected by default in the list of states shown when specifying a traffic event location. If the state code specified does not exist in the list, no state will be selected by default.



chartlite.servlet.defaultCounties.MD none The list of counties for the state of Maryland, to be used if the location service cannot be contacted. This is a comma delimited list, with each entry of the list containing a county code, county name, and county FIPS code (separated by colons). Example entry is 07:Cecil County:015. Default counties can be entered for other states by using a similar property with the state code for that state being used instead of MD (for example chartlite.servlet.defaultCounties.PA)

chartlite.servlet.defaultRegions.MD The list of regions for the state of Maryland, to be used if the location service could not be contacted to obtain this list. This is a comma delimited list of the region names. Default regions for other states can be included with a similar property by changing the MD of the property name to the state code of another state (for example chartlite.servlet.defaultRegions.PA)



chartlite.servlet.timeAfterRoadwayCallFailureToAllowCallsSec

0 This setting is used to specify the amount of time that must elapse before another attempt is made to contact the Roadway Location Service after a failure. This setting can be set to <= 0 to always attempt to call the service, regardless of when the last failure occurred. Use of this setting keeps the location entry form speedy while the location service is down, rather than having to experience a timeout each time location data is required from the service. For example, if this setting is set to 300, then after an error occurs attempting to get location data from the Roadway Location Service, the CHART GUI will not attempt to get data from the service again, and instead users can use cached data previously retrieved from the service, or can use free-form entries. In either case, they won’t experience delays on the form while an attempt is made to contact the service.



chartlite.servlet.linkName_X chartlite.servlet.linkURL_X chartlite.servlet.linkVisibleToViewOnlyUsers_Xchartlite.servlet.linkQuickMenuName_X

none These settings specify links to appear at the bottom of the CHART navigation bar. The linkName setting specifies the name of the link as it is to appear to the user. The linkURL setting specifies the URL to link to when the user clicks the link. The linkVisibleToViewOnlyUsers setting is a true or false value that specifies if the link should appear on the navigation bar for View Only users. The optional Quick Menu link name is the name of the link to be displayed at the top and bottom of the page, which may be shorter than the link name to conserve space. If no quick menu link name is specified, the link will not be displayed at the top / bottom of the page.

This set of settings can be repeated many times, where X is an index number starting at zero.

org.omg.CORBA.ORBClass org.jacorb.orb.ORB

This setting specifies the name of the Object Request Broker class. This value should only be changed by a software developer.

org.omg.CORBA.ORBSingletonClass org.jacorb.orb.ORBSingleton

This setting specifies the name of the Object Request Broker Singleton class. This value should only be changed by a software developer.

OAPort 9100 The IP port that is opened by the CORBA orb.



OAIAddr none IP address on multi-homed host (this gets encoded in object references). This value may be commented out on a single-homed host.

NOTE: Addresses like 127.0.0.X will only be accessible from the same machine!

ORBInitRef.NameService none The Naming Service is not used in CHART. This should be commented out.

jacorb.implname CHARTLite The name of the service implementation in CORBA, which would be used for resolving initial references. The imply name for CHART is not used externally, as no external CORBA client connects directly to CHART.

jacorb.log.default.verbosity 1 JacORB log levels:

0 = fatal errors only = "almost off" (FATAL ERRORS)1 = non-fatal errors and exceptions (ERROR)2 = important messages (WARN)3 = informational messages and exceptions (INFO)4 = debug-level output (DEBUG) (may confuse the unaware user

jacorb.log.default.log_pattern [%.23{time:dd-MM-yyyy HH:mm:ss:SSS}] %.20{category}:%.7{priority}: %{message}\\n%{throwable}

Default log patterns for here (Apache LogKit pattern syntax)

(The value deployed differs from the JacORB default in that it addsd a timestamp, which is necessary to correlate log messages from different log files.)



jacorb.connection.client.connect_timeout 5000 Initial timeout for establishing a connection.

NOTES:- The JacORB default is 0, which represents an infinite timeout.- This should match the CHART application property:chartlite.servlet.OrbConnectTimeoutMillis

jacorb.connection.client.pending_reply_timeout 30000 Wait the specified number of msecs for a reply to a request. If exceeded, a org.omg.CORBA.TIMEOUT exception will be thrown

NOTES:- The JacORB default is 0, which represents an infinite timeout.- This should match the CHART application property:chartlite.servlet.OrbRequestTimeoutMillis

jacorb.poa.log.verbosity 1 JacORB POA log levels:

0 = fatal errors only = "almost off" (FATAL ERRORS)1 = non-fatal errors and exceptions (ERROR)2 = important messages (WARN)3 = informational messages and exceptions (INFO)4 = debug-level output (DEBUG) (may confuse the unaware user

ORBInitRef.EventChannelFactory none Event service that the application should publish its event channel(s) into. This is used to publish CHART Client event channels, which are used for pushing events when entries are removed from the trader, etc.

ORBInitRef.TradingServiceX none Traders that should be used by CHART. X starts at 0 and increases. Trader 0 is the primary (local) trader and will be preferred over the others.



NOTE – there are many other JacORB settings that are not documented here. Only the ones that have been changed from the default JacORB properties files are listed above.


A.2 CHART Database Installation

A.2.1Oracle 10g Software Installation Procedures

Intended AudienceThe intended audience for the installation procedures is someone who

is familiar with Windows 2003

is familiar with Some level of Oracle DBA experience

Pre-install Checklist Verify Window 2003 R2 OS is installed on the software and must have the D drive with at

least 10GB free.

Login as a admin administrator account on Chart2 domain.

My Computer-> Manage->Local Users and Groups->Groups->administrator, now current user name to local administrator group.

Verify window registry and make sure there is no trace of Oracle software.

Verify OS services and make sure there is no trace of Oracle services.

Verify PATH and make sure there is no Oracle path present.

Oracle 10G Installation Procedures Insert Oracle 10G CD for 32 bit window OS. Install program should pop up

automatically, click Install/UnInstall button. If Install window not start, At E: drive and double click Setup.exe.

After some time Oracle Universal Installer will pop up and ‘Welcome to Oracle 10G database installation’ screen will appear, Check radio button Advance Installation and then press NEXT.

Default NAME will populate as OraDb10g_home1 and PATH will populate as D:\oracle\product\10.1.0\db_1 keep the default as it is and click NEXT.

On the next screen check radio button Enterprise Edition (808) MB and then press NEXT.

On the next screen, at the end of the screen, check Radio button Do Not Create the Starter Database and press NEXT.

Click Install to start Software installation.

Click EXIT at the end of installation screen.


POST-install Checklist Verify these additional services have been created during the Oracle 10G installation:

o OracleCSServiceo OracleOraDb10g_home1SNMPPeerEncapsulatoro OracleOraDb10g_home1SNMPPeerMasterAgent

Create the following directories.

o ORACLE\ADMINo ORACLE\ORADATAo ORACLE\ORADATA\BACKUP

Special Note: After the installation of Oracle 10.1.0.2, Oracle patches 10.1.0.3 and 10.1.0.5 must be

installed. Follow the procedures documented in Patch_10.1.0.5 Installation Procedures

A.2.2Oracle Patch For April 2007 Installation Procedures

Pre-install Checklist Verify that Oracle Patch software 10.1.0.3 and 10.1.0.5 are available

Verify that Oracle Patch for Oct 2006(#5500883), Apr 2007(#5907304), and OPatch Utility version 1.0.0.0.57(#2617419) are available

Oracle Software 10.1.0.2 must be installed

Oracle Patch 10.1.0.3 Installation ProcedureFollow the steps below to install the Oracle Patch set 10.1.0.3 :

Stop all Oracle services including the following:

OracleCSService

Distributed Transaction Coordinator

Change Directory to d:\10103_software and double click SETUP.EXE file

At the welcome screen click NEXT

The Default Name will come OraDb10g_home2, this need to be changed to OraDb10g_home1.

The Default name for the PATH will populate D:\oracle\product\10.1.0\db_2 this need to be change it to D:\oracle\product\10.1.0\db_1, click NEXT.

At Summary Screen Click Install button.

At End of Installation Screen, click EXIT.


Restart server

NOTE: Do not start any Oracle service. Proceed to the next section to install Oracle patch 10.1.0.5.

Oracle Patch 10.1.0.5 Installation ProceduresFollow the steps below to install Oracle patch 10.1.0.5:

Run setup.exe from the patch set installation CD The default name for the installation path will show D:\oracle\product\10.1.0\db_2 this

need to be change it to D:\oracle\product\10.1.0\db_1, click NEXT At Summary Screen Click Install button.

At End of Installation Screen, click EXIT.

Restart server

Proceed to Database Upgrade.

Oracle Database UpgradeFollow steps below to upgrade each database. This process will take about 40 minutes.

Login to database as SYS

SQL> shutdown immediate;

SQL> STARTUP;

SQL> ALTER SYSTEM SET SHARED_POOL_SIZE='150M' SCOPE=spfile;

SQL> ALTER SYSTEM SET JAVA_POOL_SIZE='150M' SCOPE=spfile;

SQL> SHUTDOWN;

SQL> STARTUP UPGRADE;

SQL> @c:\oracle\product\10.1.0\db_1\rdbms\admin\catpatch.sql

SQL> SHUTDOWN;

SQL> STARTUP;

SQL> @c:\oracle\product\10.1.0\db_1\rdbms\admin\utlrp.sql

SQL> exit;Proceed to apply Oct 2006 Oracle patch.

Oracle Patch for Oct 2006 Installation ProceduresOct 2006 Oracle Patch is #5500883

Shutdown all Oracle services and "Distributed Transaction Coordinator" service

Set ORACLE_HOME={$ORACLE_HOME}


Set the PERL5LIB and PATH environment variables to point to Perl in Oracle Home:

set PERL5LIB={$ORACLE_HOME}\perl\5.6.1\lib;%PERL5LIB%

set PATH={$ORACLE_HOME}\perl\5.6.1\bin\MSWin32-x86;%PATH%

Verify that Java is available in the following directories :

{$ORACLE_HOME}\jre\1.4.2\bin

{$ORACLE_HOME}\jdk\bin

CD to the patch directory where patch #5500883 is located and run "opatch apply" to update Oracle Home

Oracle home has been patched. Proceed to upgrade all databases

Oracle Patch for Oct 2006 Installation Procedures - Upgrade Databases

Start Oracle Listener service.

For each of the databases perform the following steps to patch the database files :

(Roughly about 15-30 minutes to process each database)

Start Oracle Instance service

CD %ORACLE_HOME%\CPU\cpuoct2006

Log into SQLPLUS as SYSDBA using SYS account and run SQL statements

SQL> shutdown;

SQL> startup migrate;

SQL> @%ORACLE_HOME%\cpu\cpuoct2006\catcpu.sql

SQL> shutdown;

SQL> startup;

SQL> @%ORACLE_HOME%\rdbms\admin\utlprp.sql 0;

SQL> quit;

Check %ORACLE_HOME%\cpu\cpuoct2006\Apply_<ORACLE_SID>_<timestamp>.log for errors

Enable DBSNMP account so database can be monitored by Grid Control :


SQL> ALTER USER DBSNMP ACCOUNT UNLOCK

SQL> PASSWORD DBSNMP

Update Opatch UtilityUpgrade Opatch utility to version 1.0.0.0.57. Patch ID is #2617419.


Unzip the new Opatch file and replace {$ORACLE_HOME}\OPatch\ with this new version.

Proceed to apply Apr 2007 patch.

Oracle Patch for Apr 2007 Installation ProceduresApr 2007 Oracle Patch ID is #5907304.

Shutdown all Oracle services and "Distributed Transaction Coordinator" service

Set ORACLE_HOME={$ORACLE_HOME}

Set the PERL5LIB and PATH environment variables to point to Perl in Oracle Home:

set PERL5LIB={$ORACLE_HOME}\perl\5.6.1\lib;%PERL5LIB%

set PATH={$ORACLE_HOME}\perl\5.6.1\bin\MSWin32-x86;%PATH%

Verify that Java is available in the following directories :

{$ORACLE_HOME}\jre\1.4.2\bin

{$ORACLE_HOME}\jdk\bin

CD to the directory where patch is located and run "opatch apply" to update Oracle Home

If the Opatch utility prompts whether to rollback previous bug fixes, answer YES.

Oracle home has been updated with Apr 2007 patchset. Proceed to upgrade all databases.

Oracle Patch for Apr 2007 Installation Procedures - Upgrade Databases

Start Oracle Listener service.

For each of the databases perform the following steps to patch the database files :

(Roughly about 15-30 minutes to process each database)

Start Oracle Instance service

CD %ORACLE_HOME%\CPU\cpuapr2007


SQL> shutdown;

SQL> startup migrate;

SQL> @%ORACLE_HOME%\cpu\cpuapr2007\catcpu.sql

SQL> shutdown;

SQL> startup;

SQL> @%ORACLE_HOME%\rdbms\admin\utlprp.sql 0;

SQL> quit;


Check %ORACLE_HOME%\cpu\cpuapr2007\Apply_<ORACLE_SID>_<timestamp>.log for errors

Enable DBSNMP account so database can be monitored by Grid Control :


SQL> ALTER USER DBSNMP ACCOUNT UNLOCK

SQL> PASSWORD DBSNMP

Oracle OEM Database UpgradeFollow procedures below to upgrade the emrep database. This process will take 40 minutes.Login to database as SYS

SQL> shutdown immediate;

SQL> STARTUP;

SQL> ALTER SYSTEM SET SHARED_POOL_SIZE='150M' SCOPE=spfile;

SQL> ALTER SYSTEM SET JAVA_POOL_SIZE='150M' SCOPE=spfile;

SQL> SHUTDOWN;

SQL> STARTUP UPGRADE;

SQL> @c:\oracle\product\10.1.0\db_1\rdbms\admin\catpatch.sql

SQL> SHUTDOWN;

SQL> STARTUP;

SQL> @c:\oracle\product\10.1.0\db_1\rdbms\admin\utlrp.sqlSQL> exit;

Upgrade Oracle Recovery Manager catalog by logging into the catalog as the RMAN user :RMAN> upgrade catalog;RMAN> upgrade catalog; (Re-issue command to confirm operation)RMAN> exit;

After applying Oracle patches for 10.1.0.5, Oct 2007, and Apr 2007, system is ready to install CHART application and archive databases.

A.2.3CHART Application Master Database (C2SOC3) Installation Procedures

Pre-install Checklist Have administrative personnel load the prod_backup file onto a local drive.

Oracle is installed on C drive.

Oracle Patch Set 10.1.0.3 is installed


copy ORA10G_CHART_SETUP directory to D:\ORA10G_CHART_SETUP.

Change attributes to read/write for D:\ORA10G_CHART_SETUP.

C2SOC3 Installation ProceduresFollow these steps to install C2SOC3 database:

Check listener

Check TNSNAMES

Check SQLNET.ora

Create the SOC instance by running the following batch file:

D:\ORA10G_CHART_SETUP\INSTANCES\BuildSOCInstance.bat C2SOC3

Set up Init.ora by copying

C:\Production_Setup\Step 1 HANOVER1_SERVER\Oracle 10G conversion\c2soc3\init(C2SOC3).ora

to

D:\ORA10G_CHART_SETUP\INSTANCES\C2SOC3\pfile\init.ora

Re-Check the following batch file, including Oracle_sid=C2SOC3:

D:\ORA10G_CHART_SETUP\INSTANCES\C2SOC3\Clone_database.bat

Re-check the sequences in the following file (use Notepad):

D:\PROD_BACKUP\EXP\815\S_ReGenrateSequences.sql

Clean the SQL statements and it should have only 8 rows.

Re-check the export backup files:

D:\PROD_BACKUP\EXP\815\C2SOC3_prod.DMP

D:\PROD_BACKUP\EXP\815\C2SOC3_prod.LOG

Create the C2SOC3 Instance by running the following batch files:

D:\ORA10G_CHART_SETUP\INSTANCES\C2SOC3\Clone_Database.bat > D:\ORA10G_CHART_SETUP\INSTANCES\C2SOC3\Clone_C2SOC3_ORA10G_Database.log

Verify the logs in

D:\ORA10G_CHART_SETUP\INSTANCES\C2SOC3\Clone_C2SOC3_ORA10G_Database.log

Logon as sysadmin:

sqlplus sysadmin/[email protected]_dom

Change passwords for C2SOC3 database

o Alter user sys identified by NEWPASSWORD;


o Alter user system identified by NEWPASSWORD;

o Alter user ch2dba identified by NEWPASSWORD;

o Alter user Archive identified by NEWPASSWORD;

o Alter USER USERMANAGEMENTSERVICE IDENTIFIED BY NEWPASSWORD;

o Alter USER MESSAGEUTILITYSERVICE IDENTIFIED BY NEWPASSWORD;

o Alter USER REPORT IDENTIFIED BY NEWPASSWORD;

o Alter USER TSSSERVICE IDENTIFIED BY NEWPASSWORD;

o Alter USER DMSSERVICE IDENTIFIED BYNEWPASSWORD;

o Alter USER TRAFFICEVENTSERVICE IDENTIFIED BY NEWPASSWORD;

o Alter USER HARSERVICE IDENTIFIED BY NEWPASSWORD;

o ALTER USER REPADMIN IDENTIFIED BY NEWPASSWORD;

o ALTER USER REPPROXY IDENTIFIED BY NEWPASSWORD;

o ALTER USER sysadmin IDENTIFIED BY NEWPASSWORD;

Set database cache advice to on, it is set to ready:

alter system set DB_CACHE_ADVICE=ON

R3B2 Update Procedures Copy R3B2_install Directory to D:\ drive

Verify file the file R3B2_setup.bat in D:\R3B2_install\R3B1_To_R3B2 directory.

Shutdown, add cursor_sharing = SIMILAR and Recreate spfile and start the database.

create spfile FROM pfile= ‘d:\ORACLE\ADMIN\C2SOC3\PFILE\init.ora’;

From the DOS command prompt :

D:\R3B2_install\R3B1 _To_R3B2\R3B2_setup.bat c2soc3 ch2dba_passwd

This will generate the log file 'c2soc3'_R2B3Setup.log in D:\R3B2_install\R3B1_To_R3B2\log directory.

Check the log file D:\R3B2_install\R3B1_To_R3B2\log\'c2soc3'_R3B2Setup.log.

After R3B2 upgrade, execute the following at SQLPLUS prompt

connect as ch2dba

UPDATE HAR SET MASTER_HAR_ID = ‘00000000000000000000000000000000’;

COMMIT;

Recreate the following Trigger


CREATE OR REPLACE TRIGGER TR_COMMUNICATIONS_LOG

BEFORE INSERT OR UPDATE

ON COMMUNICATIONS_LOG

FOR EACH ROW

BEGIN

--Make sure this is not a replicated transaction

If (DBMS_REPUTIL.FROM_REMOTE = FALSE and

DBMS_SNAPSHOT.I_AM_A_REFRESH = FALSE) Then

IF INSERTING THEN

-- populate the db_code field with the appropriate value

:new.db_code := 'S';

END IF;

IF UPDATING THEN

-- populate the updated_timestamp column when a record is updated

:new.updated_timestamp := SYSDATE;

END IF;

End if;

END TR_COMMUNICATIONS_LOG;

/

ALTER TRIGGER TR_COMMUNICATIONS_LOG ENABLE

/


A.2.4CHART C2AOC3 Application Slave Database Installation ProceduresThe following procedures detail how to install CHART C2AOC3 application database.

Pre-install Checklist Ask admin folks to load the prod_backup file to a local drive (e.g., D drive), check for the

following files:

D:\PROD_BACKUP\EXP\815\C2AOC3_prod.DMP

D:\PROD_BACKUP\EXP\815\C2AOC3_prod.LOG

Oracle must be installed on D drive.

copy ORA10G_CHART_SETUP directory to D:\ORA10G_CHART_SETUP.


C2AOC3 Installation Procedures From C:\Production_Setup\Step 2 AOCCHART2_SERVER\Oracle 10G conversion\

Oracle_10G_admin

o Check Listener

o Check TNSNAMES

o Check SQLNET.ora

Create the AOC instance by running:

D:\ORA10G_CHART_SETUP\INSTANCES\BuildAOCInstance.bat C2AOC3


C:\Production_Setup\Step 1 HANOVER1_SERVER\Oracle 10G conversion\init(C2AOC3).ora

to

D:\ORA10G_CHART_SETUP\INSTANCES\C2AOC3\pfile\init.ora

Re-Check the following batch file, including Oracle_sid=C2AOC3:

D:\ORA10G_CHART_SETUP\INSTANCES\C2AOC3\Clone_database.bat

o set SOC_CH2DBA_PWD

o set SOC_REPADMIN_PWD

o set SOC_PROXY_PWD

Re-check the sequences in the following file (use Notepad):


D:\PROD_BACKUP\EXP\815\A_ReGenrateSequences.sql

Clean the SQL statements and it should have only 8 rows.




Create the C2AOC3 Instance by running the following batch files:

D:\ORA10G_CHART_SETUP\INSTANCES\C2AOC3\Clone_Database.bat

D:\ORA10G_CHART_SETUP\INSTANCES\C2AOC3\Clone_C2AOC3_ORA10G_Database.log

Verify the logs in

D:\ORA10G_CHART_SETUP\INSTANCES\C2AOC3\Clone_C2AOC3_ORA10G_Database.log

Logon as sysadmin:

sqlplus sysadmin/[email protected]_dom

Change passwords for the C2AOC3 database

o Alter user sys identified by NEWPASSWORD;

o Alter user system identified by NEWPASSWORD;

o Alter user ch2dba identified by NEWPASSWORD;

o Alter user Archive identified by NEWPASSWORD;

o Alter USER USERMANAGEMENTSERVICE IDENTIFIED BY NEWPASSWORD;

o Alter USER MESSAGEUTILITYSERVICE IDENTIFIED BY NEWPASSWORD;

o Alter USER REPORT IDENTIFIED BY NEWPASSWORD;

o Alter USER TSSSERVICE IDENTIFIED BY NEWPASSWORD;

o Alter USER DMSSERVICE IDENTIFIED BYNEWPASSWORD;

o Alter USER TRAFFICEVENTSERVICE IDENTIFIED BY NEWPASSWORD;

o Alter USER HARSERVICE IDENTIFIED BY NEWPASSWORD;

o ALTER USER REPADMIN IDENTIFIED BY NEWPASSWORD;

o ALTER USER REPPROXY IDENTIFIED BY NEWPASSWORD;

o ALTER USER sysadmin IDENTIFIED BY NEWPASSWORD;

Set up the database links by executing the following commands:

connect ch2dba/NEWPASSWORD@c2AOC3


DROP database link c2soc3;

CREATE DATABASE LINK C2SOC3.CHART_DOM

CONNECT TO CH2DBA IDENTIFIED BY NEWPASSWORD;

SELECT * FROM GLOBAL_NAME@C2SOC3;

connect repproxy/NEWPASSWORD@c2AOC3



CONNECT TO REPPROXY IDENTIFIED BY REPUSER;


connect repadmin/NEWPASSWORD@c2AOC3



CONNECT TO REPADMIN IDENTIFIED BY NEWPASSWORD;

SELECT * FROM GLOBAL_NAME@c2SOC3 ;

Turn Replication on by executing the following commands:

connect repadmin/NEWPASSWORD@C2SOC3

PROMPT Turning on replication, this may take 20 seconds.

execute dbms_repcat.resume_master_activity('CH2DBA_MG');

PROMPT Verify that the following text says "NORMAL"

SELECT status FROM dba_repgroup;

Turn replication off by executing the following steps

connect repadmin/NEWPASSWORD@C2SOC3

PROMPT Turning OFF replication, this may take 20 seconds.

execute dbms_repcat.suspend_master_activity('CH2DBA_MG');

PROMPT Verify that the following text says "QUIESCED"

SELECT status FROM dba_repgroup;

Important Special Note: Do not ignore. This is the special task added at the last steps to make the SQL connection work. Verify the following Window services are set to run/execute as the local administrator:

OracleServiceC2AOC3


OracleOraDb10g_home1TNSListener

OracleOraDb10g_home1TNSCHART2




create spfile FROM pfile= ‘d:\ORACLE\ADMIN\C2AOC3\PFILE\init.ora’;

From a command prompt :

D:\R3B2_install\R3B1_To_R3B2\R3B2_setup.bat c2aoc3 ch2dba_passwd

This will generate the log file 'c2aoc3'_R2B3Setup.log in D:\R3B2_install\R3B1_To_R3B2\log directory.

Check the log file D:\R3B2_install\R3B1_To_R3B2\log\'c2aoc3'_R3B2Setup.log.


connect as ch2dba


COMMIT;





FOR EACH ROW

BEGIN




IF INSERTING THEN


:new.db_code := 'A';

END IF;

IF UPDATING THEN




END IF;

End if;


/


/

Replication SetupVerify Build_site.bat file exists in D:\R3B2_install\R3B2_Replication directory.

From the DOS prompt execute the following

D:\R3B2_install\R3B2_Replication\Build_site.bat

D c2aoc3_type ch2dba_pwd repadmin_passwd repproxy_pwd SOC_ch2dba_pwd ref_time

Following log files were create in D:\R3B2_install\R3B2_Replication\log\C2AOC3 directory.

01Droping_C2AOC3.log

02Building_snapshots_C2AOC3.log

03building_constraints_C2AOC3.log

04Building_Grants_C2AOC3.log

05Building_SYNONYMS_C2AOC3.log

06UserSetup_C2AOC3.log

07databaseLink_C2AOC3.log

08Replication_Grp_C2AOC3.log

09Replication_refresh_grp_C2AOC3.log

A.2.5 CHART Other Application Slave Database Installation Procedures

The following procedures detail how to install the other AOC-like CHART application slave databases. These procedures install the following databases (Oracle SIDs):

C2D5AN

C2D4BR

C2LEC

C2D3GR

C2TRIP


C2MWEST

Database Installation ProceduresDatabase install procedures are similar for each database. Replace SEEDDB with the corresponding Oracle SID listed above.

Run the corresponding batch file, according to the selected SID:

D:\R3B2_install\SeedDatabaseAOCtype\Build_CHART_Instance.bat C2D5AN 5

D:\R3B2_install\SeedDatabaseAOCtype\Build_CHART_Instance.bat C2D4BR 4

D:\R3B2_install\SeedDatabaseAOCtype\Build_CHART_Instance.bat C2LEC L

D:\R3B2_install\SeedDatabaseAOCtype\Build_CHART_Instance.bat C2D3GR 3

D:\R3B2_install\SeedDatabaseAOCtype\Build_CHART_Instance.bat C2TRIP T

D:\R3B2_install\SeedDatabaseAOCtype\Build_CHART_Instance.bat C2MWEST E

Set up the database:

D:\R3B2_install\SeedDatabaseAOCtype\SEEDDB\setup_database.bat > D:\R3B2_install\SeedDatabaseAOCtype\SEEDDB\log\Build_database.lst

View the log:

D:\R3B2_install\SeedDatabaseAOCtype\SEEDDB\log\Build_database.lst

Add triggers

sqlplus ch2dba@SEEDDB

at SQL prompt execute

check the instance and server by

select * from v$instance;

@D:\R3B2_install\SeedDatabaseAOCtype\SEEDDB\triggers.sql

Execute the following to install workaround package:

D:\R3B2_install\SeedDatabaseAOCtype\SEEDDB\WorkAroundPackages.sql

Add a new db code:

connect ch2dba@c2arch3

INSERT INTO database_list

(

DB_CODE

,DATABASE_NAME

,LAST_ARCHIVED_DATE

)

VALUES


('DB_CODE_FLAG','SEEDDB',sysdate-1);

change the actual password for archive, report and ch2dba users and execute at SQL prompt.

notepad @D:\R3B2_install\SeedDatabaseAOCtype\SEEDDB\db_link.sql

Verify Installation of SEEDDB installation

sqlplus ch2dev@SEEDDB

Check table access for FONT, CAMERA.

sqlplus ch2dba@SEEDDB

check for DB_CODE value.

set long 2000

select TRIGGER_BODY from user_triggers

where table_name='TOUR'

select TRIGGER_BODY from user_triggers

where table_name='CAMERA'

/

Check DELETE TOUR tables for new purge_data package.

select text from user_source

where name like '%PURGE%'

and text like '%TOUR%'

/


A.2.6Archive Database Installation Procedures

Pre-install Checklist Have administrative personnel load the prod_backup file to D:\PROD_BACKUP\EXP\815,

check for the following files:



Oracle must be installed on C drive.

The following directory must already exist in ORA10G_CHART_SETUP directory:

D:\ORA10G_CHART_SETUP.


Archive Database Installation Procedures Check Listener

Check TNSNAMES

Check SQLNET.ora

Create the ARCH instance by running:

D:\ORA10G_CHART_SETUP\INSTANCES\BuildARCHInstance.bat C2ARCH3


C:\Production_Setup\HANOVER1_SERVER\Oracle 10G conversion\C2ARCH3 copy init(C2ARCH3).ora

to

D:\ORA10G_CHART_SETUP\INSTANCES\C2ARCH3\pfile\init.ora

Re-Check the following batch file, including Oracle_sid= C2ARCH3:

D:\ORA10G_CHART_SETUP\INSTANCES\C2ARCH3\Clone_database.bat


D:\PROD_BACKUP\EXP\815\EXPDAT[01-10].DMP

D:\PROD_BACKUP\EXP\815\Export.LOG

Create the C2ARCH3Instance by running the following batch files:

D:\ORA10G_CHART_SETUP\INSTANCES\C2ARCH3\Clone_Database.bat

D:\ORA10G_CHART_SETUP\INSTANCES\C2ARCH3\Clone_C2ARCH3_ORA10G_Database.log

Verify the logs in


D:\ORA10G_CHART_SETUP\INSTANCES\C2ARCH3\Clone_C2ARCH3_ORA10G_Database.log

Login to and change passwords for C2ARCH3 database by executing the following commands:

connect sysadmin/[email protected]_dom

Alter user sys identified by NEWPASSWORD;

Alter user system identified by NEWPASSWORD;

Alter user ch2dba identified by NEWPASSWORD;

Alter user Archive identified by NEWPASSWORD;

Alter user Archive_user identified by NEWPASSWORD;

Alter USER RMANCHART2 IDENTIFIED BY NEWPASSWORD;

ALTER USER sysadmin IDENTIFIED BY NEWPASSWORD;

Set up the database links by executing the following commands:

connect archive/[email protected]_dom;



CONNECT TO ARCHIVE IDENTIFIED BY NEWPASSWORD

USING 'C2SOC3.CHART_DOM'

/


DROP database link c2aoc3;

CREATE DATABASE LINK C2AOC3.CHART_DOM


USING 'C2AOC3.CHART_DOM'

/

SELECT * FROM GLOBAL_NAME@C2AOC3;

connect ch2dba/[email protected]_dom





USING 'C2SOC3.CHART_DOM'

/


DROP database link c2aoc3;

CREATE DATABASE LINK C2AOC3.CHART_DOM


USING 'C2AOC3.CHART_DOM'

/

SELECT * FROM GLOBAL_NAME@C2AOC3;

Verify the jobs are present by executing the following commands:

column what format a50

column log_user format a14

column priv_user format a14

column schema_user format a14

column interval format a35

column last_date format a11

column this_date format a11

column next_date format a11

column broken format a6

select job,

log_user,

priv_user,

schema_user,

what,

to_char(next_date,'DD-MON-YYYY HH24:MI:SS') next_date,

to_char(last_date,'DD-MON-YYYY HH24:MI:SS') last_date,

interval,

to_char(this_date, 'DD-MON-YYYY HH24:MI:SS') this_date,

broken,

failures

from dba_jobs


/

Create the GETOPERATIONALDATA stored procedure by running the following commands:

DECLARE

jobno number;

CURSOR j1 is

SELECT job

FROM user_jobs

WHERE UPPER(what) = 'CH2DBA.GETOPERATIONALDATA.GETDATA;';

BEGIN

/* Determine if any jobs exist */

SELECT count(*) into jobno

FROM user_jobs

WHERE UPPER(what) = 'CH2DBA.GETOPERATIONALDATA.GETDATA;';

/* If jobs exist, remove them */

IF jobno > 0 THEN

FOR j1_rec in j1 LOOP

jobno:= j1_rec.job;

DBMS_JOB.REMOVE(jobno);

END LOOP;

END IF;

/* Create the job */

DBMS_JOB.SUBMIT(jobno,

'CH2DBA.GETOPERATIONALDATA.GETDATA;',

SYSDATE,

'TRUNC(SYSDATE+1) + 1/24');

COMMIT;

END;

/

Check that the procedure was created correctly:

select what, next_date, next_sec, last_date, last_sec, failures from user_jobs;


Execute the job manually to make sure it is working by executing the following commands:

connect archive/archive_user@c2arch3

execute DBMS_JOB.RUN(jobNo);

o View output to verify the following functions and procedures:

PROCEDURE GetData IS

FUNCTION GetTableData(DaysAgo NUMBER) RETURN NUMBER IS

PROCEDURE GetEventData(DaysAgo NUMBER) IS

PROCEDURE GetCodeListData(DaysAgo NUMBER) IS

PROCEDURE GetLogData(DaysAgo NUMBER) IS

PROCEDURE GetDeviceData(DaysAgo NUMBER) IS

PROCEDURE GetCenterData(DaysAgo NUMBER) IS

PROCEDURE WriteToLog(LogText VARCHAR) IS




create spfile FROM pfile= ‘d:\ORACLE\ADMIN\SEEDDB\PFILE\init.ora’;

From the DOS command prompt :

D:\R3B2_install\R3B1_To_R3B2\R3B2_setup.bat SEEDDB ch2dba_passwd

This will generate the log file ' SEEDDB '_R3B2Setup.log in D:\R3B2_install\R3B1_To_R3B2\log directory.

Check the log file D:\R3B2_install\R3B1_To_R3B2\log\' SEEDDB '_R3B2Setup.log.


connect as ch2dba


COMMIT;






FOR EACH ROW

BEGIN




IF INSERTING THEN


:new.db_code := ' SEEDDB_CODE ';

END IF;

IF UPDATING THEN



END IF;

End if;


/


/


Replication SetupVerify Build_site.bat file exists in D:\R3B2_install\R3B2_Replication directory.

From the DOS prompt execute the following

D:\R3B2_install\R3B2_Replication\Build_site.bat

D c2aoc3_type ch2dba_pwd repadmin_passwd repproxy_pwd SOC_ch2dba_pwd ref_time

Following log files were create in D:\R3B2_install\R3B2_Replication\log\ SEEDDB directory.

01Droping_ SEEDDB.log

02Building_snapshots_ SEEDDB.log

03building_constraints_ SEEDDB.log

04Building_Grants_ SEEDDB.log

05Building_SYNONYMS_ SEEDDB.log

06UserSetup_ SEEDDB.log

07databaseLink_ SEEDDB log

08Replication_ SEEDDB.log

09Replication_refresh_grp_ SEEDDB.log

A.3 Oracle Enterprise Manager Setup

A.3.1 Oracle Enterprise Manager Installation RequirementsThis section describes the requirements before installing the Oracle 10g Enterprise Manager. For detailed information refer to Oracle Enterprise Manager 10g Installation CD readme file.

A.3.1.1 Disable System Job The default system stats job must be disabled. As the SYS user, use the following query

to check for job status: SELECT STATE FROM DBA_SCHEDULER_JOBS WHERE JOB_NAME =

'GATHER_STATS_JOB'; If not already disabled, use the following command to disable the job: exec dbms_scheduler.disable('SYS.GATHER_STATS_JOB');

A.3.1.2 Environment Variable

If present, remove the environment variables ORACLE_HOME and ORACLE_SID prior to the install. After the installation, remove ORACLE_HOME variable. If you reboot the server without first removing the ORACLE_HOME environment variable the database services will not start.


A.3.1.3 SYSMAN SchemaMake sure destination database does not contain the SYSMAN user.

A.3.1.4 Oracle Enterprise Manager Database Requirements

Do not install the database from the OEM 10g installation because the database created will be of version 9.0.1.5. Create a 10g database for use with OEM 10g based on the criteria below. There is no need to allocate any tablespace for OEM 10g since the SYSMAN schema and related tablespaces will be created during installation.

Required Database Parameters aq_tm_processes: 1 compatible: 9.0.1.3 or greater db_block_size: 8192 dispatchers: NULL job_queue_processes: 10 open_cursors: 300 remote_login_passwordfile: EXCLUSIVE session_cached_cursors: 200 SGA_MAX_SIZE: 600M SGA_TARGET: 500M shared_pool_size: 230686720 timed_statistics: TRUE

Minimum Values db_cache_size: 134217728 fast_start_mttr_target: 300 hash_area_size: 1048576 large_pool_size: 0 pga_aggregate_target: 33554432 processes: 150 sort_area_size: 1048576 undo_management: AUTO undo_retention: 10800 undo_tablespace: UNDOTBS

Recommended AUTOEXTEND ON for UNOD and TEMP tablespaces

A.3.1.5 Database PackageMake sure DBMS_SHARED_POOL package is installed in the repository database. If not, execute the following script: <DB_HOME>/rdbms/admin/dbmspool.sql

A.3.1.6 Agent InstallBefore installing agent on a CHART-enabled server, disable the JAVA_HOME system variable. Then after installing agent, register the JAVA_HOME variable back.


A.3.1.7 Agent Path

After installation of agent, adjust system path so that the Oracle database server path is before the agent path.

A.3.2 Recovery Manager Catalog SetupThis section describes steps to setup the Oracle Recovery Manager Catalog on the database where Oracle Enterprise Manager 10g is installed. The RMAN catalog installation is a one-time only setup. Follow steps below for each database that needs to be registered with the RMAN catalog.

A.3.2.1 Catalog Server Name

In order to provide a centralized database management system, the name of the Oracle RMAN catalog is determined only by a variable "catDB". If the catalog name is to be changed then make sure that the variable is changed on the script for all database servers as well as on the OEM 10g server. The variable can be located by searching for the string "set catDB=" in the script:

c:\orascripts\bin\setenv.bat

A.3.2.2 Create RMAN Catalog

On the OEM 10g server, run the following script to setup a RMAN catalog:

c:\orascripts\catalog\create_rc.bat {SID of OEM database}{SYS password} {Oracle Home Drive} {Oracle data file drive}

After creating the RMAN catalog, examine the following log directory for errors:

c:\orascripts\log\

A.3.2 Database SetupEach database must be registered with the RMAN catalog. Registration is a one-time setup. Before proceeding make sure the database is not already registered with the RMAN catalog already by querying the catalog database:

select * from rman.rc_database;

If the database is not registered with the RMAN catalog then follow steps below to register it. Run the following scripts from the OEM server. Verify that the OEM server has access to the database to be registered by using TNSPING utility.

Note: The drive letters for Oracle home and data file listed below are on the server where you run the scripts - not on the target database server.

After each step, check log file under c:\orascripts\log for errors.

Setup RMAN_ ADMIN account: c:\orascripts\catalog\create_rman_admin.bat {SID of database to be registered} {SYS password} {Drive letter of Oracle Home} {Drive letter of Oracle datafile directory}


Register database to RMAN catalog: c:\orascripts\catalog\register_db_to_rc.bat {SID of database to be registered} {RMAN_ADMIN password} {Drive letter of Oracle Home} {Drive letter of Oracle datafile directory}

Setup RMAN parameters: c:\orascripts\catalog\create_rman_parm.bat {SID of database to be registered} {RMAN_ADMIN password} {Drive letter of Oracle Home} {Drive letter of Oracle datafile directory} {"catalog" or "nocat"}

A.3.3 Windows Server Setup

A.3.3.1 Windows Privilege On each of the Windows database servers, assign “Log on as a batch job” privilege to

“CHART2\oracle_backup” user. This needs to be done locally on the database server itself and not on the domain controller. Go to START - Settings - Control Panel - Administrative Tools – Local Security Policies – Local Policies – User Rights Assignments – Log On As a Batch Job

A.3.3.2 Windows 2003 Server Setup If the database is running on a Windows 2003 Server then complete the step below. Otherwise,

“Access Denied” error will occur when running database jobs from Oracle Enterprise Manager 10g console

Change directory to %Systemroot%\system32\ right-click on “cmd.exe”, click Properties, under Security tab, assign user "CHART2\oracle_backup" to the list with “Read” and “Read/Execute” rights


A.3.4 Oracle Enterprise Manager 10g Console SetupThis section describes steps to add database targets to the Oracle Enterprise Manager 10g console. For a database to be added to OEM 10g console, a host server must be added first. When the OEM agent is installed on the target database server and started, the server will automatically be added to the OEM 10g console. Refer to OEM 10g installation manual for details. Once a server is added to OEM 10g console, perform the steps to add the database target:

Log into Oracle Enterprise Manager 10g Console

Click Target tab

Click Database tab

Click Add and specify the host server where the database resides

Now OEM 10g will automatically perform discovery of any databases and add them to the SYSMAN repository

A.4 Attention!NS InstallationThe following describes the procedure for applying the Attention!NS patch (9/28/2208) on top of an existing Attention!NS installation. The full Attention!NS installation procedures are described in the vendor’s documentation and are beyond the scope of this document.

The patch installation procedure is as follows:

1. First stop the Attention! Notification System service from the Service Control Manager. Also make sure that the Attention! Web Interface stops too. It should stop as a result of stopping the first service.

2. Place the <R3B2 Patch 4Install CD>:\AttentionPatch\patch_09232008\attnccapi.dll file here: C:\Program Files\Attention Software, Inc\Attention! Notification System\Web\web\AttnCCApi\

3. Place the < R3B2 Patch 4Install CD>:\AttentionPatch\patch_09232008\libhttpd.dll file here: C:\Program Files\Attention Software, Inc\Attention! Notification System\Web\

4. After the DLLs are put in place, restart the Attention! service from the Service Control Manager.


Appendix B – Known Problems

The table below lists known problems and suggested workarounds for CHART R3B2. Additional known problems have workarounds documented in the CHART PR Database. These problems and workarounds are also reflected in Attachment J of the R3B2 Software Change Notice (SCN) provided with delivery of the system.

Indication of Problem Problem Description Suggested Workaround

“CORBA comm failure” error message

“CORBA comm failure” message is received.

Retry the action that caused this error. If the error persists it may indicate that a server is down. Notify the system administrator.

“Device communications timeout”

A command to a device generates a “Device communications timeout” message.

The device has not responded within the “Device Timeout Response” time period. Retry the action that caused this error. If the error persists it may indicate a problem with the device itself.

CHART Operations & Maintenance Guide R3B2 Revision 3 B-1 12/10/2008

Appendix C – Server Installation FormsCHART Backend Server Installation Form

This form may be used to record information needed for CHART backend server installations.Data Item Value Description

Operations Center The name of the operations center that is to be assigned to the server

Host Name The host name of the computer that is running the Oracle database

Database Instance The name of the database instance on the system specified by Host Name

Port Number The port number being used by the Database Instance

User Management Service User Name

Database user name for the CHART User Management Service

User Management Service Password

Database password for the CHART User Management Service

CHART Alert Service User Name

Database user name for the CHART Alert Service

CHART Alert service Password

Database password for the CHART Alert Service

CHART DMS Service User Name

Database user name for the CHART DMS Service

CHART DMS Service Password

Database password for the CHART DMS Service

CHART EORS Service User Name

Database user name for the CHART EORS Service

CHART EORS Service Password

Database password for the CHART EORS Service

CHART HAR Service User Name

Database user name for the CHART HAR Service

CHART Operations & Maintenance Guide R3B2 Revision 3 C-1 12/10/2008

Data Item Value Description

CHART HAR Service Password

Database password for the CHART HAR Service

CHART Message Utility Service User Name

Database user name for the CHART Message Utility Service

CHART Message Utility Service Password

Database password for the CHART Message Utility Service

CHART Notification Service User Name

Database user name for the CHART Notification Service

CHART Notification Service Password

Database password for the CHART Notification Service

CHART RoadwayLocationLookup Service User Name

Database user name for the CHART RoadwayLocationLookup Service

CHART RoadwayLocationLookup Service Password

Database password for the CHART RoadwayLocationLookup Service

CHART Schedule Service User Name

Database user name for the CHART Schedule Service

CHART Schedule Service Password

Database password for the CHART Schedule Service

CHART Traffic Event Service User Name

Database user name for the CHART Traffic Event Service

CHART Traffic Event Service Password

Database password for the CHART Traffic Event Service

CHART TSS Service User Name

Database user name for the CHART TSS Service

CHART TSS Service Password

Database password for the CHART TSS Service

CHART Video Service User Name

Database user name for the CHART Video Service

CHART Video Service Password

Database password for the CHART Video Service


CHART Web Server Installation Form

This form may be used to record information needed for CHART web server installations.Data Item Value Description

Location of Java SDK The directory name where the Java Software Development Kit is to installed e.g. C:\jdk1.5.0_09

Location of Java Secure Socket Extension

The directory for all Java extensions e.g. C:\jdk1.5.0_09\jre\lib\ext

Location RSA Agent Location of the RSA security agent (e.g. D:\)

Location of the CHART servlet

The location of the CHART web archive file (.war) e.g. D:\tomcat-5.5.9\webapps

Chartlite.servlet.DBConnectString

Value in MainServlet.props that uniquely identifies the database and connection protocol in use by CHART e.g. jdbc:oracle:thin:@hanoverchart1:1526:C2SOC3jdbc:oracle:thin:@chart2-svr3:1526:C2SOC

OAIAddr Value in MainServlet.props equal to host name or IP address this servlet should use when creating its InterOperable Object References (IORs). Generally this is the address of the firewall that forwards iiop packets to the servlet (e.g. OAIAddr = firewall.com). If the servlet is not behind a firewall this parameter can be commented out by prefixing it with a # (e.g #OAIAddr)

ORBInitRef.EventChannelFactory

Value in MainServlet.props equal to the host and port number of the CORBA Event Service that CHART is to use



(e.g. corbaloc::chart2-svr3:9001/DefaultEventChannelFactory. ) This must be the address of the firewall if one exists between the servlet and the Event Service

ORBInitRef.TradingServiceX Values in MainServlet.props equal to the host and port number of one or more CORBA Trading Services that CHART is to use (e.g. corbaloc::chart2-svr3:8002/TradingService. ) This must be the address of the firewall if one exists between the servlet and the Trading Service

Sites to be redirected to Tomcat

Values in uriworkermap.properties equal to the names of the sites that IIS is to forward to Tomcat e.g. /chartlite=ajp13w/chartlite/*=ajp13w

SSL port Port number for SSL authentication (e.g. 443)


Appendix D – Device Installation FormsThe following forms may be used to record information needed in order to add a new devices to the system.

DMS Installation Form


Sign Name The name of the sign as denoted by its assigned number.

Sign Type The type of sign display. One of Char/Full/Line/Other.

Location Text description of the location of the sign.

Direction Direction of traffic that the sign is facing.

Organization The owning organization for the sign.

Site The server where the device needs to be added.

Model ID The model ID of the sign.

Sign Height (characters) Vertical sign display dimension in characters.

Sign Width (characters) Horizontal sign display dimension in characters.

Character Height (pixels) Vertical dimension of a character cell in pixels.

Character Width (pixels) Horizontal dimension of a character cell in pixels.

Beacon Support Whether or not the sign has beacons.

Default Line Justification Indicates default position of message on sign. One of Center/Left/Right.

Max Pages The maximum number of pages this sign will display.

Default Page On Time (if supported)

The default time in seconds that the message will display on a page.

Default Page Off Time (if supported)

The default time in seconds that the page will remain blank between refreshes of the display.

Drop Address The multi-drop address for which the

CHART Operations & Maintenance Guide R3B2 Revision 3 D-1 12/10/2008


sign controller has been configured to respond to.

Community String The SNMP community string used to communicate to an NTCIP DMS. This must be a community string which allows read-write access to the DMS’s MIB. (This value is relevant for NTCIP DMSs only)

Phone # The default phone number for the sign. This should always be entered as the complete 10 digit number (plus prefix and long distance digit as needed) required to dial the device. This number will be used to pre-fill the phone number field in the Port Manager panel.

Poll Interval The frequency (in hours and minutes) to poll the sign for status information.

Polling Enabled Whether polling of this device is enabled or not.

Timeout The time period (in seconds) within which a port must be allocated by the port manager or the operation will timeout.

Port Managers The names of the port managers that will support communications with this device.

Connection type Whether this device has an ISDN or POTS modem or Telephony

Phone number to use for each port manager

The phone number to use from each port manager configured to serve this device.

Modem parameters The baud rate, flow control, number of data bits, parity, and number of stop bits to use when communicating with this device.


TSS Installation Form


TSS Name The name of the RTMS as denoted by its assigned number or name.

Location Text description of the location of the TSS device.

Organization The owning organization for the TSS device.


Polling Interval The interval at which the TSS needs to be polled when it is online or in maintenance mode.

Zone Group Number The number of the zone that the TSS belongs to.

Description Name of the Zone Group. This normally is the direction name of the traffic that the RTMS is providing information on.

Direction The direction of the traffic that the TSS is providing information on

Include Zones Specific areas on a given roadway that the RTMS is collecting information on. This could be the different lanes on any roadway (up to 8 areas).

Drop Address The multi-drop address for which the sign controller has been configured to respond to.

Phone # The default phone number for the sign. This should always be entered as the complete 10 digit number (plus prefix and long distance digit as needed) required to dial the device. This number will be used to pre-fill the phone number field in the Port Manager panel.







Modem parameters The baud rate, flow control, number of data bits, parity, and number of stop bits to use when communicating with this device.


HAR Installation Form


HAR Name The name of the HAR as denoted by its assigned number or name.

Location Text description of the location of the HAR.

Organization The owning organization for the HAR.

Model ID The Model type of the HAR.


Control Phone number The phone number used to control the HAR. This should always be entered as the complete 10-digit number (plus prefix and long distance digit as needed) required to dial the device. This number will be used to pre-fill the phone number field in the Port Manager panel.

Monitor Phone number The phone number to monitor the message on the HAR, if applicable. This should always be entered as the complete 10-digit number (plus prefix and long distance digit as needed) required to dial the device. This number will be used to pre-fill the phone number field in the Port Manager panel.

Access Code This is the access code, or PIN, that allows the system to communicate with the HAR.

Control Port Managers The names of the port managers that will be used to control the HAR.

Connection type Telephony is the only valid type and this choice cannot be changed.





Monitor Port Managers The names of the port managers that will support communications with the HAR controller to monitor what is being broadcast, if applicable.




Maximum Voice (sec.) The total RAM space available on the HAR for holding voice messages. The default value of six minutes corresponds to “medium quality” on the ISS AP55 HAR. HIS DR1500 HARs typically have 80 or 40 minutes of space.

Slot Type Default header, Default Message, and Default Trailer messages are either typed in text or recorded in audio format. Note that the default message plays without the default header and default trailer whenever the HAR is “blank,” therefore, it should include any relevant information normally included in the header and/or trailer (such as call sign, broadcasting organization, etc.)

Clip Description Short description of the Default Header, Default Message and the Default Trailer are stored in here.

Voice Length This is the length of the Default Header, Message or the Trailer. (This parameter is automatically updated and the user cannot change this.)

Audio This is selected when the currently selected clip was recorded in audio format or to record a new audio message.



Text This is selected when the currently selected clip was typed into the system in text format or to type in a new text message.

Message Notifiers List of devices (SHAZAMs, or DMSs which can act as SHAZAMs) that are normally associated with this HAR. Note that a notifier (DMS or SHAZAM) can be associated with only one HAR at a time. Notifiers which appear on the list to select from are currently associated with this HAR or are not associated with any HAR..


SHAZAM Installation Form


Name The name of the SHAZAM as denoted by its assigned number or name.

Location Text description of the location of the sign.

Direction This is the direction of the traffic that the SHAZAM is facing.

Organization The owning organization for the sign.

Message An identifying message affixed to the body of the SHAZAM.


Phone # The default phone number for the SHAZAM. This should always be entered as the complete 10-digit number (plus prefix and long distance digit as needed) required to dial the device. This number will be used to pre-fill the phone number field in the Port Manager panel.

Poll Interval The frequency (in hours and minutes) to poll the sign for status information.

Polling Enabled Whether polling of this device is enabled or not.


Connection type Telephony only




Camera Installation Form


Camera Model Type of Camera (Fixed / Uncontrollable, Cohu 3955, Vicon SVFT

Name CHART name for camera

Owning Organization Organization owning camera.

Is “No Video Available” Source?

Whether a video source is an NVA source or not (only for video sources).

Sending Device Type of video connection or video sending device: IP Encoder or Vicon V1500 switch

Sending Device : IP Video Fabric

Video Fabric: SHA IP VIDEO FABRIC (if IP encoder sending device)

Sending Device : Hostname / IP Addr

IP address or host name of encoder (if IP encoder video or control)

Sending Device : Encoder Type

Model of encoder (if IP encoder video or control), CoreTec MPEG4 or iMPath MPEG2

Sending Device : TCP Port TCP Port used to connect to the encoder (if IP encoder video).

Sending Device : Multicast Address

Multicast video address

(if IP Encoder video)

Sending Device : Multicast Port

Multicast video port

(if IP Encoder video)

Sending Device : Switch Name of video switch for camera (if Vicon V1500 switch video)

Sending Device : Input Port Port number for camera on video switch (if Vicon V1500 switch video)

Camera Number Camera number embedded into camera commands.

Location Description Textual description of location

Regions Region(s) in which camera is



located (AA Co., AOC, Balt Co., etc).

Camera Number Camera number embedded into camera commands.

Control Device Type of Control Device: IP via CODEC (IP encoder), Command Processor, or Comm Port

Control Device : Hostname / IP

IP address or host name of encoder (if IP encoder control)

Control Device : Port Port for commands sent to Codec (if IP encoder or omm port control)

Control Device : Command Processor

Name of command processor used for camera control (if Command Processor control)

Control Device : Baud Baud rate for serial port communications (if IP encoder or comm port control).

Control Device : Data Bits Number of data bits (if IP encoder or comm port control).

Control Device : Flow Control Flow control type (None, XON/XOFF, or RTS/CTS).

Control Device : Parity Parity (None, Space, Mark, Even, or Odd).

Control Device : Stop Bits Number of stop bits (1, 1.5, or 2).

Polling Enabled Outside Of Control Session

flag to enable polling of camera not actively controlled.

Poll Interval (outside of control session)

Polling interval for camera not actively controlled by operator

Poll Interval Within Control Session

polling interval for camera actively controlled

Device Logging Enabled Indicate if device log enabled for camera. 0 = off, 1 = on

Default Title Line 1 Default camera title line 1

Default Title Line 2 Default camera title line 2

TMDD : External Name TMDD name for camera



TMDD : Image Format TMDD Type of Image (MPEG, NTSC etc).

TMDD : Horizontal Datum LRMS horizontal datum model

TMDD : Latitude TMDD LRMS latitude: -90 to + 90 degrees (to up to six decimal places).

TMDD : Longitude TMDD LRMS longitude -180 to + 180 degrees (to up to six decimal places).

TMDD : Vertical Datum LRMS vertical datum model

TMDD : Height TMDD LRMS height: -127 to 127.

TMDD : Vertical Level TMDD LRMS vertical level: -127 to 127, where 0=ground level, positive is above ground level, negative is below ground level.

Site: Server/factory to which the device should be added.


Monitor Installation Form


Name Name of monitor

Owning Organization Organization owning the monitor

Receiving Device Type of Receiving Device: IP Decoder, Switch.

Receiving Device : IP Video_Fabric

Video Fabric for the monitor: SHA IP Fabric (IP decoder only)

Receiving Device : Decoder Type Model of decoder: CoreTec MPEG4 or iMPath MPEG2 (if IP decoder video)

Receiving Device : Hostname / IP Addr

IP address or host name of decoder (if IP decoder video)

Receiving Device : Decoder Type Model of decoder: CoreTec MPEG4 or iMPath MPEG2 (if IP decoder video)

Receiving Device : TCP Port Port for commands sent to decoder (if IP decoder video)

Receiving Device : Switch Switch monitor to which monitor is connected: FMT Switch, BHT Switch (if switch video).

Receiving Device : Output Port Output port on the switch to which monitor is connected (if switch video).

Is Public Monitor Whether monitor is “public” (web or media).

Monitor Groups List of monitor groups to which the monitor belongs.

Site: Server/factory to which the device should be added.


Appendix E – System Status and Error Messages

This section provides lists of those system status and error messages that may require some action by a user. The table below provides a list of backend server-side messages, an explanation of each message, and recommended user action. Following this table is a table of web server-side and GUI-side messages.

The strings enclosed in square brackets (“[]”) or angle brackets {“<>”) are replaced with appropriate information when the message is logged. For example [DMS Name] is replaced with the name of the DMS.

Message Explanation User ActionCombined Error Messages for DMS or HAR or SHAZAM (except as noted)

(ConnectFailure) [operation description] Could not connect to port [description].

A general (unexpected) connection failure. No further attempts will be made.

Possible device problem, comms problem, or software problem. Contact the NOC.

(PortOpenFailure) [operation description] Could not connect to port [port name], could not open port: [description].

The port on the PortManager computer which the CHART system is trying to use cannot be opened. It may not exist, may not be connected, , or may be disabled. Port will be marked (internally by the system) as marginal and will not be used for any communications again unless marginal ports are the only ones left. Meanwhile, for this call, the system will automatically attempt to use next PortManager (if there are any more).

Possible PortManager configuration problem, device problem, comms problem, or software problem. Contact the NOC. Check the configuration for this PortManager.

[description] failed (SW problem): [description].

Could not complete the specified operation for the reason provided in [description]. This is a software problem of some sort, an unexpected error occurred.

Contact software support.

[device name] is already in [mode] mode.

Device received a request to go into the mode it is already in. Indicates a software error, GUI should not allow attempt


CHART Operations & Maintenance Guide R3B2 Revision 3 E-1 122/10/2008

Message Explanation User Actionto be made.

[device name] is in [mode] mode. Must be in [mode] mode to [description] .

Device received a request to do something it cannot do in the current mode. Indicates a software error, GUI should not allow attempt to be made.


[Device name] put in maintenance mode (blank FAILED).

The device was put in maintenance mode, but the blank operation failed. This is reported as a success, as the desired end result (getting into maintenance mode) was achieved.

none

[operation description] [PortManager name] not found in trader.

PortManager is not running, has never contacted (or has been removed from) trader.

Remove this PortManager from the list (Field Comms tab of device props screen) and specify a different one. Meanwhile, the system will automatically attempt to use next PortManager (if there are any more).

Can’t [description] : [device name] controlled by [op center name] , you’re from [op center name].

An attempt was made to take control of a device from another op center without override authority. This can happen legitimately if two users from different op centers attempt to control an uncontrolled device at the same time. The second one in will get this message.

None required.

Can’t [description]: invalid user token (SW problem).

A user’s “token” could not be read in order to validate authority to perform the specified operation. Indicative of a software problem - users have no visibility or control over their own tokens.


Can’t [description]: Invalid user token (system error).

A user’s “token” could not be read in order to validate authority to perform the specified operation. Indicative of a software problem - users have no visibility or control over their own tokens.



Message Explanation User ActionCan’t [description]: System error while checking for resource conflict.

An unexpected system software problem was encountered attempting to validate a user’s authority to perform the specified operation.


Could not obtain port from PortManager [PortManager name] - PortManager object is no longer served from its previous server/port.

Software is running where the PortManager was expected to be found, but the desired PortManager is not there. Meanwhile, the system will automatically attempt to use next PortManager (if there are any more).

Could be a configuration problem in the CommService. Verify that the named PortManager is running.

Could not obtain port from PortManager [PortManager name] - Received CORBA SystemException failure.

System problem attempting to contact PortManager. Meanwhile, the system will automatically attempt to use next PortManager (if there are any more).

Call software support.

[DMS/HAR] message not valid: [description]

DMS & HAR Only

Message to be put on device is not valid (banned word(s) found).

Correct message and resend.

DMS/HAR Message not valid: cannot be blank.

DMS & HAR Only

Attempt to put a blank message on a DMS/HAR via a traffic event. This is not the same as blanking a device, this is actively putting a text message on the device which contains no characters or only spaces. (A blank message can be put on the sign in maintenance mode, but not online through a traffic event.) Indicates a software error, GUI or Traffic Event Service should not make the attempt.


Message cannot be validated: [description]

DMS & HAR Only

Message to be put on a device cannot be validated. Probably the Message Utility Service is down or unreachable.

Verify that Message Utility Service is running.


Message Explanation User ActionPortManager [PortManager name] could not return a Port - unexpected failure: [description];

Totally unexpected failure in the PortManager. Cryptic details will be provided. Meanwhile, the system will automatically attempt to use next PortManager (if there are any more).


PortManager [PortManager name] could not return a Port – Port did not become available within the specified timeout.

All ports of the required type (ISDN/POTS/Voice) at the specified PortManager are in use or out of service. The system will automatically attempt to use next PortManager (if there are any more).

None required.

PortManager [PortManager name] could not return a Port - PortManager is unavailable.

PortManager has been known to run previously, but cannot be contacted now. Either it is not running or it cannot be reached over the network. The system will automatically attempt to use next PortManager (if there are any more).

Verify that the named PortManager is running.

PortManager [PortManager name] could not return a Port - PortManager does not serve ports of the requested type.

PortManager does not (ever) have any ports of the specified type (ISDN/POTS/Voice). Meanwhile the system will automatically attempt to use next PortManager (if there are any more).

Remove this PortManager from the list (Field Comms tab of device props screen) and specify a one with the correct type of port (or change the ISDN/POTS/Voice radio button if that is wrong).

PortManager [PortManager name] could not return a Port - PortManager failure: [description]

Unexpected failure in the PortManager. Details will be provided in [description]. The system will automatically attempt to use next PortManager (if there are any more).


Put [device name] online failed: blank FAILED.

Could not blank a device prior to going online. Cannot put a device online that we can’t communicate with.

Attempt operation again. If it continues to fail then the device controller may be broken.


Message Explanation User ActionPut [device name] online failed: could not initialize [sign/HAR].

DMS & HAR Only

Could not communicate with a device that has never been communicated with before. Cannot put a device online that we can’t communicate with.

Place device in maintenance mode and then attempt to set the device online, or attempt to perform other maintenance mode operations on it.

Unauthorized attempt to [description] [device name] [description].

Unauthorized attempt to perform some action. If received by a legitimate CHART2 user, indicates a software error, GUI should not allow attempt to be made.


Cannot [description]: SW problem, port not a VoicePort

HAR & SHAZAM Only

Somehow the port which the service needs to communicate with the device was not a voice (telephony) port as expected.


Error adding [type] to the trader

Unexpected server-based error indicating an initialization problem with either the device service or the trader services.


Error connecting to DBMS. Unexpected server-based error indicating that the database server is non-responsive, shutdown, or no communication link exists to the server.


Cannot complete connection. No retries at this time.

No available ports could be found to contact the device and no more attempts will be made.

Enter another phone number(s) for the device if possible else contact software support.

Cannot complete connection. No retries on last [n] ports.

No available ports could be found to contact the device.

Wait for the system to either find an available port or finish checking the defined ports.

Cannot complete connection. No retry on last port.

No available ports could be found to contact the device

Enter another phone number(s) for the device if possible else contact software support.

Bad configuration: [parameter] of [value] invalid - must be at most [maximum value].

An attempt was made to set a numeric device configuration parameter to a value greater than the maximum allowable value for that parameter.

Change the parameter to a value less than or equal to the maximum value and retry.


Message Explanation User ActionBad configuration: [parameter] of [value] invalid - must be non-negative

An attempt was made to set a numeric device configuration parameter to a value less than zero.

Change the parameter to a value greater than or equal to zero and retry.

Bad configuration: [parameter] of [value] invalid - must be positive

An attempt was made to set a numeric device configuration parameter to a value less than one.

Change the parameter to a value greater than or equal to one and retry.

Bad configuration: [parameter] of [value] invalid - must be at least [minimum value].

An attempt was made to set a numeric device configuration parameter to a value less than the minimum allowable value for that parameter.

Change the parameter to a value greater than or equal to the minimum value and retry.

Bad configuration: PortManager list must not be null.

When setting device properties, at least one port manager must be selected.

Select a port manager and retry. If problem persists, contact software support.

Bad configuration: PortManager list must not be empty.

When setting device properties, at least one port manager must be selected.

Select a port manager and retry. If problem persists, contact software support.

Bad configuration: PortManager name # is null or empty

When setting device properties, all selected port manager phone numbers must be completely specified.

Make sure all selected port managers have phone numbers specified, or remove the port manager specified in the error from the configuration and retry. If problem persists, contact software support.

Bad configuration: no phone number provided. (PortManager #[number])

When setting device properties, all selected port manager phone numbers must be completely specified.

Make sure all selected port managers have phone numbers specified, or remove the port manager specified in the error from the configuration and retry. If problem persists, contact software support.

Bad configuration: no phone number provided. (default phone number)

When setting device properties, a default phone number must be completely specified.

Make sure default phone number is specified and retry. If problem persists, contact software support.

Bad configuration: non-standard character in number: [phone #]

When entering a phone number, only the following non-numeric characters are accepted: ‘*’, ‘#’

Remove any unacceptable characters from all phone numbers specified in the SHAZAM configuration and retry.

Bad configuration: [DMS/HAR/SHAZAM] must have a name.

When creating/changing device properties, a name must be entered.

Enter a name for the device and retry.


Message Explanation User ActionBad configuration: Port location data was not specified

When creating/changing device properties, port location data is required.

Enter port location data for the device and retry.

Bad configuration: Invalid port type, must be TELEPHONY

The port type specified for a HAR or SHAZAM must be TELEPHONY.

Change port type to TELEPHONY and retry or contact software support.

Bad configuration: Invalid ID for owning organization

When creating/changing device properties, an invalid/non-existent owning organization was not specified.

Select an owning organization and retry or contact software support.

Bad configuration: No configuration rights for the selected organization.

An attempt to create/change a device configuration was made by a user that does not have sufficient privileges for the selected owning organization.

Login as a new user that has sufficient privileges, contact the system administrator to upgrade the privileges of the existing user, or select a different owning organization and retry.

Many messages otherwise indicating success can also have the following warning messages appended:

Message Explanation User Action

- WARNING: Could not initialize [sign/HAR].

DMS & HAR Only

A device, which has never been communicated to, was put in maintenance mode, despite the fact that it could not be initialized. HARs and some DMSs (FP9500) require initialization prior to first use.

No action required, initialization will be attempted on subsequent attempts to use the device.

WARNING: could not push new config for [description] WARNING: could not push new status for [description]

Operation caused some data in the configuration or status of a device to change, but the new information was not successfully pushed out to the GUIs (or any other listeners) via the event channel. GUIs will report outdated information about the device unless/until another operation which also changes the configuration or status is successfully performed (with a successful push).

The user who requested the operation can perform a “Refresh” of the device that should cause the correct information to be pulled into the GUI (but other users at other GUIs would never know that their GUIs are out of synch. Therefore it behooves the user who receives this message to report this problem immediately.


Message Explanation User Action

WARNING: could not persist new config for [description]

Specified data could not be stored to the database. Application will continue to run otherwise unaffected, with correct information in memory, but unless/until another operation which also requires configuration to be persisted is successfully performed (with successful persistence), there is risk of data loss/inconsistency if the device service is terminated and restarted.

WARNING: could not persist new status for [description]

Specified data could not be stored to the database. Application will continue to run otherwise unaffected, with correct information in memory, but unless/until another operation which also requires status to be persisted is successfully performed (with successful persistence), there is risk of data loss/inconsistency if the device service is terminated and restarted.

WARNING: could not push new status for [description]

Updates to the status of a SHAZAM could not be sent to other logged-in users.

No action required.

WARNING: could not persist new status for [description]: [error description]

The status changes made to a SHAZAM could not be saved in the database. The database server may be either down or unreachable.



Warnings of various types could also be output on a configuration change attempt, for parameters that are missing, out of range, or otherwise invalid. In such cases parameters that are valid are updated. Such warnings are indicative of a software error, as the GUI should prevent invalid parameters from being transmitted.

Message Explanation User actionDMS

(CHART2Exception) [operation description] SW problem: General connection failure [description].

Unexpected error attempted to dial out to device. Additional details provided in [description]. No further attempts will be made.Possible values of [description]: “Port ” + m_name + ”:

Failure setting the serial port parameters.”

Problem setting baud rate, data bits, stop bits, parity, flow control. Indicative of a software error, no bad values should ever be allowed to get this far.

There may be others


(ModemConnectFailure) [operation description] Could not connect to port [port name], modem connect failure: Modem cmd: [modem command] , response code: [response code].

An error occurred actually trying to dial and complete the connection to the modem of the field device. Details are provided. Response codes which can be reported are:

NO DIAL TONE: Modem may not be connected to the phone line, or phone line is not in service. Will retry another port.

NO CARRIER: Modem failure. Will retry another port.

ERROR: General error with the modem. Will retry another port.

In the case of a failed call with no automatic retries the operation should be manually retried.


Message Explanation User action

UNKNOWN: Unexpected error with the modem. Port marked (internally by the system) as marginal and will not be used for any communications again unless marginal ports are the only ones left. Will retry another port.

NO ANSWER: The call was successfully dialed but the remote modem did not answer. Device may be off, disconnected, or malfunctioning, or the phone number may be incorrect. No more retries will be attempted.

BUSY: The call was successfully dialed but the remote modem did not answer. If running with multiple services for the same device type, it is possible that a misconfiguration problem could result in the device being in communication with another service at the same time. Otherwise, the device may be off, disconnected, or malfunctioning, or the phone number may be incorrect. No more retries will be attempted.


Message Explanation User action(ModemInitFailure) [operation description] Could not connect to port [port name], modem init failure: Modem cmd: [modem command] , response code: [response code].

The modem at the local (CHART) end cannot be initialized. Port will be marked (internally by the system) as marginal and will not be used for any communications again unless marginal ports are the only ones left.Meanwhile, for this call, the system will automatically attempt to use next PortManager (if there are any more).

None required.

(ModemNotResponding) [operation description] Could not connect to port [port name], modem not responding: [description].

The modem at the local (CHART) end is not responding. It may be off, disconnected, or malfunctioning. Port will be marked (internally by the system) as marginal and will not be used for any communications again unless marginal ports are the only ones left. The system will automatically attempt to use next PortManager (if there are any more).

None required.

[description] could not set Comm Loss timeout on sign: SW problem, Protocol Handler confusion.

(FP9500 DMS only) A bizarre software problem, attempting to communicate with what is thought to be an FP9500, but the ProtocolHandler is not an FP9500ProtocolHandler.


[description] could not set Comm Loss timeout on sign: SW problem, [description].

Could not set comm loss timeout on device for the reason provided in [description]. This is a software problem of some sort, an unexpected error occurred.



Message Explanation User action[description] could not set Comm Loss timeout on sign: SW problem, port not a DataPort.

(FP9500 DMS only) Could not set comm loss timeout on device. This is a bizarre software problem, where the Port being used is not a DataPort capable of transmitting data.

Verify the device and PortManager configuration and retry the operation.

[description] could not set Comm Loss timeout on sign: [description].

(FP9500 DMS only) Could not set comm loss timeout on device for the reason provided. The device is using a new protocol, or there are line or communication problems.

Verify the device configuration and retry the operation.

[description] failed: [description].

Could not complete specified operation for the reason provided. The device is using a new protocol, or there are line or communication problems.

Verify the device configuration and retry the operation.

[description] failed: SW problem, [device name] , port not a DataPort.

Could not complete the specified operation. This is a bizarre software problem, where the Port being used is not a DataPort capable of transmitting data.


[description] failed: SW problem, [DMS name] , Protocol Handler confusion.

(FP9500 and TS3001 DMS only) A bizarre software problem, attempting to communicate with what is thought to be an FP9500 or TS3001, but the ProtocolHandler is not of the right type.


[description] partial failure: Message set but could not set beacons: [description].

(FP9500 DMS only) Message was set but beacons could not be set.

Retry the operation.


Message Explanation User action[DMS name] blank and reset failed.

Successfully contacted DMS, but could not blank it or reset it.

Line may have been disconnected, or else indicates problem it sign, most likely.

[DMS name] blanked, reset failed.

Successfully contacted DMS and blanked it prior to reset, but the reset itself failed.

Line may have been disconnected, or else indicates problem in sign, most likely.

[DMS name] now reads: [description]. WARNING: beacon failure, but beacons were ([ ON: OFF]) anyway.

Successfully set the message on a DMS, but could not change the beacons - but they were already what was requested.

Hardware problem with beacons. This is reported as a success, as the desired end result was achieved.

[DMS name] now reads:[description]. WARNING: beacon failure, beacons now ([ ON: OFF]) .

Successfully set the message on a DMS, but could not change the beacons - they are now opposite to what was requested.

Hardware problem with beacons.

[DMS name] reset, but blank failed.

Successfully contacted sign, could not blank it, but the reset works.

This almost certainly indicates a hardware problem with the sign, as the connection is seen to have been maintained by virtue of the successful reset of the sign after the blank failed. This is reported as a success, as the desired end result was achieved.

[operation description] SW problem: Could not connect to port, it is not a modem port.

Cannot dial, the port acquired is not a capable of dialing. This is a severe, bizarre, unexpected problem. No further attempts will be made.


[operation description] SW problem: General port connect failure [description].

Unexpected software error attempting to connect on the specified modem port. No more retries will be attempted.


Cannot poll DMS: DMS is offline.

DMS received a request to poll the device when it is offline. Indicates a software error, GUI should not allow attempt to be made.



Message Explanation User actionCould not use port for [DMS device name] , it is not a data port. Poll unsuccessful.



Failure getting status via FMS: [description].

Could not poll or get extended status for the device for the reason provided in [description]. This is a software problem of some sort, an unexpected error occurred.


Message will not fit on sign. Message is too big to fit on a DMS (GUI should not have allowed attempt).


Poll [DMS name] failed: [description] .

Could not poll or get extended status for the device for the reason provided. The device is using a new protocol, or there are line or communication problems.

Verify the device configuration and retry the operation

Set msg, [DMS name]: failed: reason . Invalid response from device - response length ( [length] ) does not match the expected length of 4.

Set test msg, [DMS name]: failed: reason . Invalid response from device - response length ( [length] ) does not match the expected length of 4.

Set msg, [DMS name]: failed: reason . Invalid response from device - command type ( [command type] ) does not match the expected type of

These messages indicate some sort of problem communicating with the device down at the bit level while attempting to set a message online (“Set msg”) or in maintenance mode (“Set test msg”). Probably a hardware problem with the device, or perhaps a line problem.

Retry the operation. If it continues to fail then log a problem report.


Message Explanation User actionFP9500ProtocolDefs.IMMEDIATE_MESSAGE

Set test msg, [DMS name]: failed: reason . Invalid response from device - command type ( [command type] ) does not match the expected type of FP9500ProtocolDefs.IMMEDIATE_MESSAGE

Set msg, [DMS name]: failed: reason . Error setting beacons ([ON: OFF] ) : [error message]

Set test msg, [DMS name]: failed: reason . Error setting beacons ([ON: OFF]) : [error message]

Set msg, [DMS name]: failed: reason . Error setting beacons ([ON: OFF]) : Invalid response from device - response length ( resp.length ) does not match the expected length of 4. Set test msg, [DMS name]: failed: reason . Error setting beacons (beaconState ? ON: OFF ) : Invalid response from device - response length ( resp.length ) does not match the expected length of 4. Set msg, [DMS name]: failed: reason . Error setting beacons (beaconState ? ON: OFF ) : Invalid response from device - command type ( rspCmd ) does not match the expected type of FP9500ProtocolDefs.MESSAGE_SELECTION


Message Explanation User action Set test msg, [DMS name]: failed: reason . Error setting beacons (beaconState ? ON: OFF ) : Invalid response from device - command type ( rspCmd ) does not match the expected type of FP9500ProtocolDefs.MESSAGE_SELECTIONSet msg, [DMS name]: failed (SW problem): [description].

Some totally unexpected software error arose during processing. [description] will likely contain a description of an exception, like NullPointerException, ClassCastException, ClassNotFoundException, etc.


Set msg, [DMS name]: failed: SW problem, [DMS name] , port not a DataPort.

Indicates a bizarre software problem which should never happen.


Set test msg, [DMS name]: failed (SW problem): [description].

Some totally unexpected software error arose during processing. [description] will likely contain a description of an exception, like NullPointerException, ClassCastException, ClassNotFoundException, etc.


Set test msg, [DMS name]: failed: SW problem, [DMS name] , port not a DataPort.

Indicates a bizarre software problem that should never happen.


SW problem, [DMS name] , port not a DataPort. [description] unsuccessful.



SW Problem: Could not convert plaintext message to MULTI.

Software problem encountered converting a plaintext message to MULTI format.


GUI DMS ModulePoll interval must be shorter than comm loss timeout.

Self Explanatory Modify the poll interval to a value less than the comm loss


Message Explanation User actiontimeout

Polling must be enabled if comm loss timeout is enabled.

Self Explanatory Enable the polling interval.

You must specify at least one port manager.A valid phone number must be specified for all selected port managers.

Self Explanatory Take the required actions and try again.

Error editing DMS configuration. Unable to acquire Organization list

Initialization problem. Contact software support.

DMS name cannot be empty and must be between 1-15 characters in length

A DMS with the name <name> already exists. Please choose another name.

Location field cannot be empty and must be between 1-<max location length> characters in length

Program error - Contact Admin.


Sign type is invalid Unexpected Software Error. Contact Software SupportYou do not have DMS configuration rights for the selected owning organization <organization name>.

Insufficient rights Log in as a user with the required rights.

No direction specified. Please select a valid direction.

This should not happen. GUI Error

Contact Software Support

Error adding new DMS to system <error message>.

Unexpected Software Error. Contact Software Support

Unable to format the message for preview window.

There are no formatters available.Unexpected Software Error.


Invalid message: beacons enabled for blank message

There is no message set Set the message.

The message contains the following banned words:<banned words>

Some disapproved words were found

Remove the banned words from the message.


Message Explanation User actionMessage requires too many pages.<Problem description> requires too many pixels.Error showing message: <error description>.

There is either a page or row overflow.Or Unexpected Error

Try and enter a message with in the required limits.

Error setting message data: The server object has been deleted/ The server could not be contacted.

Message Utility Service may be down or unreachable

Check whether Message Utility Service is running or contact software support.

Error sending message:<error description>

Given the error description, refer to the DMS Error Messages to get more information

Error performing spell check: SpellChecker: Could not retrieve dictionary

Could not get a dictionary object


Error performing spell check: SpellChecker: Input text is null

Unexpected Error Contact software support.

General error performing spell check.


Specified pixmap is null.The specified pixmap is null. It cannot be shown.Unable to copy pixmap data. Invalid start point passed.

Should not happen Contact software support.

The message formatter provided is invalid (null).


Formatter <description> specified invalid character width: <char width>.Formatter < description> specified invalid character height: <char width>.Unable to load a font file for signs of type: < description> Message preview will not be available.A non-DMS response plan item <Plan item Name> is detected while creating the MULTI Broadcast editor.

Should not happen Contact software support.


Message Explanation User actionAn object of the type other than DMS (or null) is detected in the response plan item <Plan item Name>.The current message does not fit on format: <formatter description>Message not valid for format: <formatter description >

Self explanatory Modify the message accordingly.

The FP1001 and FP2001 models do not support non-zero page off time values.

Self Explanatory Use positive values for the page off time.

Add DMS failed:<DMS Name> - Unable to add DMS to a server.

There are no DMS factory objects to work with. Initialization problem

Check the DMSService is running and reachable.

No valid message library objects have been discovered by the GUI.

Initialization problem Check the Message Utility service is up and running and the trader has the required offers.

Non-CHART2 DMS Configuration returned from sign. Only CHART2 signs are supported at this time.

Self explanatory None Required

DMS does not exist in server. The object no longer exists. None Required.Unable to edit properties. Unable to edit properties of plan item for unknown DMS with ID:<DMS id>


An invalid type of DMS is being used by the plan item.


HARCannot [description]: not enough space on HAR’s RAM: action requires [X]ms, only [Y]ms available.

Cannot complete the requested operation because there is not enough space in the HAR’s RAM (six minutes at medium quality).

Delete some pre-stored user clips and retry the operation.


Message Explanation User actionCannot [description]: not enough space on HAR’s RAM: action requires [X]ms, only [Y]ms available (allowing for [Z]ms safety margin).

Cannot complete the requested operation because there is not enough space in the HAR’s RAM (six minutes at medium quality), with sufficient buffer. (The default safety margin, settable in the HARService.props file, is 10 seconds, which means a maximum of 5 minutes, 50 seconds can be stored on the HAR at medium quality).

Delete some pre-stored user clips and retry the operation.

Cannot [description]: SW Problem, could not register audio clip “desc”: not found.

An attempt to use an audio clip on a HAR failed because its AudioClipManager (part of the MsgUtilityService) could not find the clip in the database.

Contact software support. Meanwhile, re-record a new clip and use that one instead.

Cannot [description]: SW problem with clip “desc”: [reason]

Unexpected software problem working with HAR as indicated.


Cannot [description]: SW problem: Null pointer exception.

Unexpected software problem working with HAR.


Cannot [description]: SW problem: [details]

Unexpected software problem working with HAR.


Cannot [description] Thread interrupted before audio streaming could complete.

While the HAR service was receiving or waiting to receive audio data from an AudioClipManager or TTS service, the HAR processing received an unexpected software interrupt.

Contact software support. Meanwhile, attempt operation again.

Failure [description]: Error processing X clip(s): [details]

Unexpected error occurred while streaming audio data for clips to go to HAR. [details] may include: Timeout occurred during streaming: The TTS or audio service took too long to deliver audio to HAR service, timed out – TTS or audio service is overworked or malfunctioning Error for data[x]: [detail] –

Contact software support. Meanwhile, attempt operation again. If using audio, try text, or vice versa.


Message Explanation User actionDetails provided. Error for data[x]: Unknown error. – TTS or audio service did not supply a reason. This is expected if a timeout was also reported.

Failure [description]: Timeout occurred during streaming, unknown error(s) processing one or more clips

Unexpected error occurred. No details are available.

Contact software support. Meanwhile, attempt operation again. If using audio, try text, or vice versa.

Cannot [description]: unsupported audio format: [details]

Cannot download a clip into the HAR, the clip is not in an accepted format. Indicative of a software problem, GUI should not allow an unsupported audio format to be specified in the first place.


Cannot [description]: [reason]. An unexpected error occurred with a HARProtocolHandler request. Since the telephony board cannot detect hang-ups, this error should never occur.


Cannot [description]: Slot X is not a valid slot number.

An attempt to manipulate an invalid port on a HAR was detected (0, negative, or greater than 250). This is indicative of a software problem.


Failure preparing to download immediate message: Prestored clip in [header/trailer/body clip x] references prestored clip in empty slot Y.

An attempt to play an immediate mode message with a prestored clip failed because the prestored clip is not there. Indicative of a software problem.

Contact software support. Attempt the operation again; re-store the clip in the designated slot if necessary.

Cannot [description]: No clip in slot X.

An operation which required a clip in the designated slot could not be completed because there is no clip there (deleting the clip or using the clip as part of a message). Indicative of a software problem.

Contact software support. Attempt the operation again; re-store the clip in the designated slot if necessary.

Cannot [description]: SW problem, could not get root POA. Will not be able to

Severe software problem performing fundamental step necessary for manipulating

Contact software support. Check that all CHART processes are running.


Message Explanation User actiondownload clips until problem resolved. General Exception: [details].

clips on HARs.

HAR GUI MessagesError editing HAR configuration. Unable to acquire Organization list.

Organization objects not found.

Check the trader and check if GUI connected to xxx event channel.


Org is not valid.

You do not have HAR configuration rights for the selected owning organization ‘orgName’

Self Explanatory. Nothing.

Error monitoring slot message: reason.

Look up the ‘reason’ in error messages from HARService.

HARDefaultSlotDataProperties- Invalid default slot data.

The default clips are not valid. Bad clip data. Recreate them.

Error performing spell check:…

May be dictionary was not available. GUIDictionary may not be up.

Check that dictionary is available.

You must specify different phone numbers for control and monitor lines. “Phone number 'nn’ cannot be used for both controlling and monitoring the HAR

Self Explanatory Check the HAR configuration

No HAR access code specified. The access code should be an integer between 0 and 1,000,000


Invalid HAR access code value: “ accessCodeTxt “. The access code should be an integer between 0 and 1,000,000


General error performing spell check

Unknown error. Contact support

Error [updating/adding] stored message Could not contact the object in the server.

Communication problem. Contact Support.

Error [updating/adding] an existing library message

HARStored Message does not exist.

Check the HARStored message exists on server.


Message Explanation User actionCORBA object does not exist.Error [updating/adding] an existing library message..

Unknown errors Contact Support.

Error [updating/adding] an existing library message. General error…. Unexpected error, see the log file

General error. Contact Support.

An invalid type of HAR is being used by the plan item.

Unknown error while creating HAR planitem

Contact Support

The library message has not been discovered by the GUI. It may not exist.

GUI not updated yet. Refresh GUI and try. Make sure the library message exists on the server.

The HAR has not been discovered by the GUI. It may not exist.

GUI not updated yet. Refresh GUI and try. Make sure the HAR exists on the server.

Error creating a response plan item with HAR::CORBA object does not exist.

HAR is not available. Make sure the HAR exists on the server.

Error creating a response plan item with HAR:: Could not contact the object in the server..

Communication problem. Contact Technical Support.

Error creating a response plan item with HAR: Unexpected error, see the log file.

Unknown errors Contact Support.

Failed to preview clip.[Description] “Bad HARAudioPushConsumer object supplied.”

HARAudioPushConsumer not available.

Contact Support.

“Failed to preview a text clip ” [Description]“Unsupported audio format specified.”

Audio format for conversion is not supported.

Contact Support.

“Failed to preview an audio clip 'Description ‘Clip manager cannot find the clip.”;

‘Clip manager cannot find the clip.";

Check the trader. Check the clip manager is serving the clips.

Failed to preview a text clip '" …

Chart2 Exception Contact Support


Message Explanation User actionFailed to preview a text clip '" + clip.getDescription() + "'.

Unknown error Contact Support.

Error adding new HAR " config. to ‘name’: Access Denied."

Insufficient rights. Nothing.

"Error adding new HAR " config. to ‘name’ [reason]

Chart2Exception Refer HAR error message.

Error adding new HAR config to ‘name’: could not contact the server, the server process is probably down.

Communication problem. Check HARService is up and can be contacted. Contact Support.

"Error adding new HAR config. to ‘name’: timed out while attempting to contact server machine.


Error adding new HAR config. to ‘name’. the factory object does not exist in the server. ";

HARFactory was not found. Check the trader to see if the HARFactory is available..

Error adding new HAR config to name: could not contact the server, the server process is probably down.


Error adding new HAR config to ‘name’ [reason]

Chart2Exception Refer to error messages from HARService.

Error adding new HAR config to ‘name’.See Log File for details.

Unknown error. Contact Support.

Error [action] from HAR."Access denied, the following rights are required:


Error getting configuration from HAR The following banned word(s) were found:

Banned words found in clips. Remove the banned words from the clip.

"Error adding new HAR config. to ‘name’: timed out while attempting to contact server machine.



Message Explanation User actionError adding new HAR config. to ‘name’. the factory object does not exist in the server. ";

HARFactory was not found. Check the trader to see if the HARFactory is available..

Error adding new HAR config to name: could not contact the server, the server process is probably down.


Error adding new HAR config to ‘name’ [reason]

Chart2Exception Refer to error messages from HARService.

Error adding new HAR config to ‘name’.See Log File for details.


Error [action] from HAR. "Access denied, the following rights are required:


Error [action] configuration from HAR reason

Refer the reason in the HARModule error messages.

Error [action] configuration from HAR Unable to contact the server machine, there are network problems or the server machine is turned off.";


Error [action] configuration from HAR. Unable to contact the service on the server machine, the service is probably not running.


Error [action] configuration from HAR .The object does not exist in the server.

HAR was not found. Check the trader to see if the HARFactory is available..

Error [action] configuration from HAR . Unexpected CORBA error, see log file for details.


Error [action] configuration from HAR.General error, see log file for details.


The HAR type does not support creation of response plan items.



Message Explanation User actionAn invalid type of HAR is being used by the plan item.



Library message not available on GUI

Refresh GUI. Make sure the message exists on the server.


HAR is not available. Refresh GUI. Make sure the HAR exists on the server.

Error [action] configuration from HAR reason










Error [action] configuration from HAR. General error, see log file for details.












Message Explanation User actionError [action] configuration from HAR reason










Error [action] configuration from HAR.General error, see log file for details.













Error [action] configuration from HAR. General error, see log file for details.


The HAR type does not Unknown error. Contact Support.


Message Explanation User actionsupport creation of response plan items.An invalid type of HAR is being used by the plan item.







SHAZAM Error retrieving SHAZAM active notifier events object from database: [description]

Unexpected database server error.


Error occurred while getting reference [ID] of active notifier traffic event ID [ID]: [description]

Unexpected server-based error possibly indicating a loss of connectivity with the trader service.


Can’t obtain reference of active notifier TE ID [ID].

Unexpected server-based error possibly indicating a loss of connectivity with the trader service.


Error setting SHAZAM active notifier events in database: [description]

Unexpected database server error


Unexpected exception setting SHAZAM active notifier events in database: [description]



Exception in SHAZAMControlDB.[function name] while [description].



SQLException while retrieving SHAZAM configuration: [description]



SQLException while retrieving SHAZAM status: [description]




Message Explanation User actionException in SHAZAMControlDB [get Status, get Configuration, getSHAZAMList, or DeleteSHAZAM] while [task description]: [error description]



Exception in setConfigWithConnection while [task description]: [error description]

Either invalid values were entered for the SHAZAM configuration parameters or an unexpected database server error occurred

Correct the SHAZAM configuration parameters and retry. If problem persists, contact software support.

Exception in setPhoneNumbers while [task description]: [error description]

Either invalid values were entered for the SHAZAM phone number(s) or an unexpected database server error occurred.

Correct the SHAZAM phone number(s) and retry. If problem persists, contact software support.

Array index out of bounds while creating and publishing SHAZAM objects: [error description]

Unexpected server-based error indicating a SHAZAM service initialization problem.


Error retrieving SHAZAM object from database: [error description]

Unexpected server-based error indicating a SHAZAM service initialization problem or contact with the database server has been lost.


Error registering SHAZAM objects with the service app: [error description]

Unexpected server-based error indicating a SHAZAM service initialization problem.


Unexpected error while creating SHAZAM Factory: [error description]

Unexpected server-based error indicating a SHAZAM service initialization problem


Unauthorized attempt to add SHAZAM [SHAZAM name].

User does not have sufficient privileges to add a SHAZAM to the system.

Login as a new user that has sufficient privileges or contact the system administrator to upgrade the privileges of the existing user.

Cannot create SHAZAM [SHAZAM name] when SHAZAM is associated with a HAR

A SHAZAM cannot be created and associated with a HAR simultaneously.

First create the SHAZAM, then associate the SHAZAM with a HAR. If creating a SHAZAM with an associated HAR was not intended, contact software support.


Message Explanation User actionFailure adding SHAZAM [SHAZAM name] with ID=[ID]: [error description]

Unexpected system error Contact software support.

System failure removing SHAZAM.


Error adding type [type] to trader.



Could not create [SHAZAM name]: [error description]



SW Problem: Unable to create SHAZAM: no Protocol Handler! [error description]



Unauthorized attempt to get configuration of SHAZAM [SHAZAM name]

User does not have sufficient privileges to retrieve the configuration of a SHAZAM from the system.


Cannot remove SHAZAM [SHAZAM name] when SHAZAM is associated with a HAR

A SHAZAM cannot be removed from the system unless it is not associated with a HAR.

Remove the HAR association before removing the SHAZAM.

Cannot associate SHAZAM [SHAZAM name] with HAR (ID=[ID]) when SHAZAM is already associated with a HAR

A SHAZAM may be associated with only one HAR at a time.

Remove the existing HAR association before attempting to associate the SHAZAM with another HAR.

Invalid direction specified. An invalid direction was specified for the SHAZAM.

Select another direction or contact software support.

Unauthorized attempt to activate HAR notice on [SHAZAM name].

User does not have sufficient privileges to instruct the SHAZAM beacons to begin flashing.


Unauthorized attempt to deactivate HAR notice on [SHAZAM name].

User does not have sufficient privileges to instruct the SHAZAM beacons to stop flashing.



Message Explanation User actionSet HAR notice fails on [SHAZAM name], not associated with HAR

Unexpected error condition indicating that an attempt was made to activate/deactivate a SHAZAM that is associated with a HAR that has either been deleted or is unreachable.


Can not activate [SHAZAM name] as it is not online. SHAZAM will be activated shortly after being placed online

SHAZAMs that are not online cannot be activated via HAR response plan items (RPIs).

Put SHAZAM in online state.

Cannot perform maintenance mode [activate, deactivate] HAR Notice on [SHAZAM name]. The SHAZAM is not in maintenance mode

SHAZAM beacons can only be controlled without a HAR RPI if the SHAZAM is in maintenance mode.

Put SHAZAM in maintenance mode and retry.

Unknown request type. An unsupported SHAZAM command has been sent to the system.


Device access code must be provided.

The SHAZAM device access code is missing from the SHAZAM configuration.

Add the device access code to the SHAZAM properties and retry the operation.

Failed to [activate, deactivate] [SHAZAM name]: [error description]

An error occurred while activating or deactivating a SHAZAM.

Based on the error description, attempt to correct the error or contact software support.

[SHAZAM name] put in maintenance mode – could not deactivate beacon.

When the SHAZAM was placed in maintenance mode, the command to force the beacons to stop flashing failed.

No action required.

[SHAZAM name] failed to deactivate beacon

When an attempt was made to put a SHAZAM in online mode, the command to force the beacons to stop flashing failed.

Contact software support

[SHAZAM name] put in offline mode – could not deactivate beacon.

When the SHAZAM was placed in offline mode, the command to force the beacons to stop flashing failed.

No action required.

Attempted to initialize a SHAZAM which has already been initialized

An attempt was made to initialize a SHAZAM which has already been initialized

No action required.

Required NoticeInfo field(s) missing.

Unexpected software problem Contact software support.


Message Explanation User actionRequired online NoticeInfo field(s) missing.


Unexpected comm mode (OFFLINE).


Error initiating SHAZAM Programming: [description]

Command session cannot be initialized on the SHAZAM.


Error terminating SHAZAM Programming: [description]

Command session cannot be terminated on the SHAZAM


Error activating SHAZAM: [description]

The commands to begin flashing the beacons of a SHAZAM could not be sent.


Error deactivating SHAZAM: [description]

The commands to stop flashing the beacons of a SHAZAM could not be sent.


GUI SHAZAM ModuleFailed to construct a GUISHAZAM wrapper for: <SHAZAM name>

Problem getting the SHAZAM status from the server

The SHAZAM service maybe unreachable. Else contact Software Support.

Error editing SHAZAM configuration. Unable to acquire Organization list


SHAZAM name cannot be empty and must be between 1-<Max length> characters in lengthA SHAZAM with the name <name> already exists. Please choose another name.


No SHAZAM access code specified. An access code should be alphanumeric characters and has a length of 3 characters.An access code should be alphanumeric characters and has a length of 3 characters.


The phone number must contain four digits.

If specified, the exchange/area code must contain three digits.

If specified, the long distance indicator must contain the digit '1'.

The phone number must be numeric

Self Explanatory

Take the required actions and try again.


Message Explanation User actionIf specified, the dialing prefix must contain the digit '9'.For FOUR DIGIT format: phone number only.For SEVEN DIGIT format: phone number and exchange.For EIGHT DIGIT format: phone number, exchange and dial prefix.For TEN DIGIT format: phone number, exchange and area code.For ELEVEN DIGIT format: phone number, exchange, area code and either dial prefix or long distance indicator.For TWELVE DIGIT format: all fields must be filled in.An exchange/area code must be specified for this number.

Self Explanatory Specify an Exchange number/Area code.

The minimum polling interval is one minute.The maximum polling interval is twenty four hours.You must specify at least one port manager.A valid phone number must be specified for all selected port managers.


Error editing SHAZAM configuration. Unable to acquire Organization list

Unexpected Software Problem Contact Software support.

Location field cannot be empty and must be between 1-<Max Length> characters in length.

No direction specified. Please select a valid direction.




Message Explanation User actionYou do not have HAR/SHAZAM configuration rights for the selected owning organization <organization name>

Insufficient rights for the owning organization

Login as user with the required rights.

Add SHAZAM failed:<SHAZAM Name> - Unable to add SHAZAM to a server.

There are no SHAZAM factory objects to work with or they could not be reached.

Check the Service hosting the SHAZAM Module is running and reachable.

Traffic Event ManagementError getting the <Object Type> object

There is a problem contacting the traffic event server. The Server may be down. Possible values of Object Type are ActionEvent, CongestionEvent, Incident etc.


Error <action description>. Not authorized to set /create <signal state> for an <event type> event.



Error < action description>. Failure <description>. Reason: traffic event is closed.

The GUI should not allow an attempt to set new or modify properties to a closed event.GUI problem


Error < action description>. Error connecting to DBMS

Unexpected server-based error indicating that the database server is non-responsive, shutdown, or no communication link exists to the server.


Error < action description >. SQLException while executing statement <SQL Statement> - <Error description>

SQLException while accessing database - <Error description>Error - <Error Description>

Either there is some problem communicating with the database or there is a problem with the SQL statement. The Error description should be able to describe what the problem is



Message Explanation User actionError< action description >. Exception while parsing event data for single quotes - <Error description>

There is some problem with the data or parameters passed. The problem is related to quotes in the data passed.


Error<action description >. Failure updating <TrafficEvent Type> event data in the database. Exception caught - <Error Description>.

Unexpected problem while storing data in the database.

Try again and if the problem persists contact software support.

Error< action description>. Failure/Error <setting /creating/closing/adding/executing/removing/....> <action description> <Traffic event name>

Unexpected software problem while performing the action.


This tab is disabled because the event has been closed

The traffic event is closed that’s the reason why the tab of the event dialog has been disabled

No user action required

This tab is disabled because you do not have the 'Manage Traffic Event' user right

The user does not have sufficient privileges.

Login as a new user that has sufficient privileges, contact the system administrator to upgrade the privileges of the existing user

This tab is disabled because the event has not been opened

The traffic event is yet not opened

Open the traffic Event and the tab will be enabled.

This tab is disabled because the direction (on the 'General' tab) has not been set to a valid value

The direction of the event has not been set.

Go to the General tab and then set the direction or set it on the lane tab itself.

This tab is disabled becauseyou do not have the 'Respond to Traffic Event' or 'Basic Operations' user right

The user does not have sufficient privileges

Login as a new user that has sufficient privileges, contact the system administrator to upgrade the privileges of the existing user

No factories are available, can't open the traffic event.

This should not happen. Service Initialization problem.


Tried <no of factories> factory/factories , but the event could not be opened. Error< action description>. Failure creating event: Unknown event type

This should not happen. It says that an event type being created was not known to the Chart2 system. The GUI should not allow this.



Message Explanation User actionTried <no of factories> factory/factories , but the event could not be opened. Error< action description>. Failure activating traffic event <traffic event name>

There was a failure activating the object with CORBA.Unexpected software problem


Tried <no of factories> factory/factories , but the event could not be opened. Error< action description>. Failed to create a traffic event

Either there is an error publishing the event object with trader or registering the object with trader. Or the traffic event service is down or there are network problems contacting the traffic event service


Tried <no of factories> factory/factories , but the event could not be opened. Error< action description>. Error initializing traffic event group <Traffic Event Name>

There was a unexpected problem initializing the traffic event.

Try to create a new traffic event. If problem still persists call the software support.

Tried <no of factories> factory/factories , but the event could not be opened. Error <action description>.Could not record traffic event data.<Error Message>

There was some problem storing traffic event data to the database. Either software or database problem. Error Message should be able to tell us more.


Tried <no of factories> factory/factories , but the event could not be opened. Error <action description>.Failure adding traffic event group to database.

There was some problem storing Traffic event data to the database. Unexpected software problem.


Warning: Successfully opened the traffic event, but other error(s) occurred: Failed to add <size> of the initial log entries (<log entry descriptions>) / Failed to inform other GUIs that this event was opened./ Failed to add an entry to the Comm Log for the opening of this event. / Failed to add an entry to the event history for the opening of this event./ Failed to log the

The traffic event was created and registered and stored in the database but had any one or combination of problems specified.

Try creating a new traffic event and check whether it has the same problems. It is does contact software support.


Message Explanation User actioninitial event data to the event history.Unable to copy some information from original event.

If a copy of the traffic event is being made, some of the response plan items /response participation could not be copied over to the new traffic event created. Possible reasons:

The event has been already closed.

The RPI is not valid/non executable because it’s message structure is not valid or it message is null or the Device which is points to is unreachable.

Problem adding response plan item /response participation data to the database

Problem activating the response plan item/response participation object with CORBA.

System error.

Response Participation with the same ID already exists

Create new response plan items and response participation for the new traffic event.

Cannot set <action description >. The event is already closed.

This should not happen. GUI problem

Inform the software support.

Can't set the false alarm flag, the event has not been opened.

The event needs to be opened to perform the action.

Close the event. If the event has to be set as a false alarm, open the event and then click on the false alarm button.

Error <action description>Failure executing operation. Traffic event is under the control of different operations center

The traffic event is under the control of a different operations center. The current op center does not have override authority.

None required.


Message Explanation User actionError <action description>Traffic event <Traffic event Name> was closed but some failures were detected while closing. Check log for details.

The traffic event was closed but some of the response plan items could not be revoked successfully.

None required.

Error < action description >Failure overriding the log entry time in the database.

The log entry time could not be updated in the database.Some unexpected database problem.

None required. If problem persists contact software support

Error < action description >No stubbed log entries exist

The database is not available. Contact Software support to check whether database server has gone down.

Error < action description >No log entry exists with the specified id

Since the database is not available, the stubbed entries are used, but the specified id cannot be found in the list of stubbed entries.

None required

Error <action description>Invalid search criteria. -<Error description>

The database could not find the required record because the parameter on which the search was based was not valid

Contact Software support

Invalid date entered, can't set <input field name > time.

The date entered is not valid Enter a valid date and then try.

Invalid number entered for max queue length.

Max queue length must be a number.

A negative number is entered in the Max queue length/

A number should be entered.

Enter a positive number or 0.

Enter a valid number

Invalid source type. The source type entered is wrong. GUI Problem.

Enter a valid source type.

Error setting the direction for the traffic event, '<direction name>’ ' is not a recognized direction name.Error setting the county/state for the traffic event, '<county name>’ is not a recognized county/state name.

GUI Problem. Enter a valid direction.

Enter a valid county/state

Invalid direction specified. GUI Problem. This should not happen. The GUI should not allow an invalid direction to be entered.

Enter a valid direction


Message Explanation User actionNo records found for lane number <lane number> in event <Event id>

Unexpected database problem Contact software support.

Error creating Traffic Event. See log for details.(Encountered while copying a traffic event )

Some problem with the data passed to create the event.Possible reasonsWrong Event type. Incorrect data passed to create the event.


Dialog input is invalid, could not perform search.

A search is already underway, could not perform new search.

GUI problem. In this if the search dialog input is invalid the search button should be disabled.


Search failed. Error querying entries from the comm log.<Error Description>

Search failed. General error querying the entries. See the log file for details

Search failed. Comm log not found, can't perform search on the log.

There was a problem retrieving entry from log entry cache/memory.

Unexpected software problem while querying entries.

Unexpected software problem


Error <action>. General Error <action>


Error <action>.Unable to contact any Comm Log objects. <no of attempts made> attempts made.

The traffic Event service is down or unreachable.Or there was a problem getting the entries from the database.Or Error activating the LogIterator object

Restart the traffic event service and try again.Contact Software support.

Error<action> Insufficient access rights to use the Communications Log.

The user does not have sufficient privileges. The GUI should not allow access in the first place . GUI Error


Error getting information about the controlling operations center of the event.

Unexpected software error. Contact software support.

Error <action>. Failure adding response participation to this traffic event. Reason: Response Participation with the same ID already exists

The Response Participant has already been added to this event.

None Required


Message Explanation User actionError < action>. Failed to activate response participation

Failure to activate the response participation object with CORBA


Error <action> Could not record event data< Error Message>

Unexpected problem while storing information to the database. The Error Message should be able to tell more as to what the problem is.


Could not get the list of EORS permits from the server.

Unexpected software exception


(When invoking the editor for a Response Plan Item of the Response Panel.) Error invoking the editor.

The editor encountered an error when attempting to edit the response plan items

No editor could be found for editing the chosen response plan items

There was a problem invoking the editor for the response plan item.


No items were selected to execute.

A response plan item needs to be selected.

Select a Response Plan Item and click execute

Errors:<number>)Error <action>. Failure executing response plan item, reason: no message specified for execution

Either the DMS/HAR specified is not specified or correctly specified or cannot communicate with the DMS/HAR or Could get the DMS/HAR CORBA reference or caught CORBA or general exception while resolving the DMS or could not locate the DMS in the trader or the message is null or empty

Try setting a new message for the RPI and execute it again.

Errors:<number>)Error <action>. Failure executing response plan item: response plan item data could not be initialized

Either the DMS/HAR specified is not specified or correctly specified or cannot communicate with the DMS/HAR or Could get the DMS/HAR CORBA reference or caught CORBA or general exception while resolving the DMS or could not locate the DMS in the trader

Contact Software support.


Message Explanation User actionGeneral error storing an audio ClipUnable to contact any AudioClipManager objects.Caught database exception while storing clip.Failure registering interest for header/trailer/body clipSome CORBA exception

Failure executing response plan item: <reason>

HAR/DMS or message undefinedHAR/DMS is unreachable due to the reasons mentioned above.Disapproved Message ContentInvalid Token exception.Or while adding the entry to the DMS/HAR message queueAn error must have occurred. The DMS/HAR errors are mentioned in the earlier sections. Please refer to them.


Failure executing response plan item: '<Response Plan Item name> ' – execution command queue interrupted

The execution of the Response Plan Item was interrupted unexpectedly

Try executing the Response Plan Item again.

Failure executing one or more response plan items, see response plan item(s) for details

Response plan executed, failures detected during execution. Check log for details

HAR/DMS or message undefinedHAR/DMS is unreachable due to the reasons mentioned above.Disapproved Message ContentInvalid Token exception.Or while adding the entry to the DMS/HAR message queueAn error must have occurred. The DMS/HAR errors are mentioned in the earlier sections. Please refer to them.


No items were selected to be revoked.

No items were selected. Select the RPIs to be revoked and click the revoke button.


Message Explanation User actionErrors:<number>)Error <action>. Failure adding a request to revoke execution of the response plan item <response plan item name> to the Command Queue

Unexpected Software Error Contact Software Support.

Failure revoking execution of the response plan item:<reason>

HAR/DMS is unreachable due to the reasons mentioned above. Or while removing the entry from the DMS/HAR message queueThe DMS/HAR errors are mentioned in the earlier sections. Please refer to them

Depending on what the reason is check whether the HARService or DMSServiceIs running else contact software support.

Failure revoking execution of the response plan item: '<Response Plan Item Name>’- execution command queue interrupted

The revocation of the Response Plan Item was interrupted unexpectedly

Try revoking the Response Plan Item again.

Failure revoking execution of one or more response plan items, see response plan item(s) for details

Response plan execution revoked, failures detected during revocation. Check log for details


Errors: Warning: successful in removing the response plan item, but failed to revoke execution of the plan item. Targets include:<target names> . The targets may still be displaying the response message and it should be checked on manually later.

Failure adding the revoke command request to the Command Queue.Unexpected error.

Try again. If error persistsContact software support.

Errors <number>)Error <action>. Failure deleting response plan item

The Response Plan item with the specified id did not exist in the traffic event.

The response item should be displayed in the Traffic event.If it does restart the traffic event and the GUI.


Message Explanation User actionCould not delete response plan item data.<error message>

There was deleting the data from the database.


Error getting road condition from dialog.

No road condition was selected in RoadConditionPanel.

Select a road condition from the RoadConditionPanel

Road condition code is not up to date, showing 'unspecified' road condition..."

Unknown road condition, code does not match know road conditions. GUI Error


Invalid road condition specified, showing 'unspecified' road condition.

Null road condition passed.GUI Error


Error setting <Field Name> ' - invalid number entered.

The number should >0 and non negative.

Enter a valid number in the corresponding field.

Can't associate the events, both events must be opened first.

The events being associated should be open

Check that the traffic events being associated are open.

Error <action>. Failure associating traffic event ‘<traffic event name>’ with traffic event ‘<traffic event name to be associated>’

Error <action>. Unexpected error.

Possible reasons: Some error occurred while updating the database or some unexpected system error.

Try associating again else call software support.

Error ,action>.Error setting primary flag for traffic event <traffic event name>

Unexpected system error. Contact software support.

Error <action> Association of <traffic event name> could not be deleted from <associated traffic event name> because the associated traffic event is closed

The traffic event may be closed. GUI Error.


Error <action> Association of <traffic event name> could not be deleted from associated event with ID <associated traffic event name> , reason: <Error Reason>

Possible reasons: Some error occurred while updating the database or some unexpected system error.

Try disassociating again else call software support.

Error <action>. Failure removing traffic event association of traffic event <traffic event name> with traffic event < associated traffic event name>

Unexpected system error. Contact software support.


Message Explanation User actionThe following warnings are displayed when an object is being dragged on to an event.

The event needs to be opened before objects can be dropped

No objects were dragged.

There is already an association between the event and the object being dropped

User Cannot Manage Events

The traffic event type does not support response plans

You do not have rights to respond to traffic events

You do not have rights to respond to traffic events with this response item (organization conflict).

Some of the objects being dragged are unable to create response plan items.

The event is not open

Maybe the object was dragged properly There is already an link between the object being dragged and the traffic event

Insufficient rights

This traffic event type cannot have Response Plan Items

Insufficient rights

Insufficient rights

Some of the objects are not valid response plan items

Open the event and then drag the object.

Try dragging the object again.

None Required

Login as a user who has the rights to manage eventsNone Required

Login as a user who has the rights to respond to traffic eventsContact system admin

None Required.

Error/Errors: adding item/items <number>) Error creating response item/ Failed to create response item data/ Error creating response item data. See log file for details.

Possible Reasons: The DMS or HAR type does not support the creation of response plan items

None Required.

Error/Errors: adding item/items <number>) Unable to provide a target for: <description>/the item. Error getting a target for: <description>/the item.

The target of the response plan item to be added returned a null or some unexpected error occurred.


Error <action>. Failed to activate response plan item

The Response plan item to be added could be activated with the CORBA ORB



Message Explanation User actionNo working Comm Log object could be found, cannot add the entries.

Unexpected Error. Contact software support.

Error <action>. The initial entries have not been queried from the Comm Log.

The initial entries could not be queried for successfully Either because the traffic Event service is down or unreachable.Or there was a problem getting the entries from the database.Or Error activating the LogIterator object


Error<action>. Error retrieving one or more log entries

Error querying entries from the LogIterator. Software Error.

Contact Software Support.

Error adding <number> entry/entries: - <entry descriptions>. Error<action>. Failure adding one or more log entries to the Comm Log

Some of the entries could not be added to the database

If this error persists, contact software support.

Failure deleting response participation

Response participation does not exist in traffic event

None Required.

Could not delete participant data. <Error Message>

Some un-excepted Database problem


DICTIONARYError Initializing Dictionary - Check Dictionary Server Status

There was an error refreshing banned words. Possible causesare:a) communication problem with server.b)dictionary does not exist on the server.c)Access was denied due to insufficient rights.d) Timeout while contacting server.e)Software or Other errors.

Check the dictionary object exists on the server. Check if the operator has sufficient rights to access the dictionary. For Software errors call software support.

Error Initializing Dictionary - Check Dictionary Server Status

There was an error refreshing approved word. Possible causes area) communication problem with server.b)dictionary does not exist on

Check the dictionary object exists on the server. Check if the operator has sufficient rights to access the dictionary. For Other errors call software support


Message Explanation User actionthe server.c)Access was denied due to insufficient rights.d) TimeOut while contacting server.e)Software or Other errors.

Dictionary PropertyDialog – “Error adding approved words”

Possible causesare:a) communication problem with server.b)dictionary does not exist on the server.c)Access was denied due to insufficient rights.d) TimeOut while contacting server.e) Software or Other errors.

Check the dictionary object exists on the server. Check if the operator has sufficient rights to access the dictionary. For other errors call software support.

Dictionary PropertyDialog – “Error adding banned words”

Possible causesare:a) communication problem with server.b)dictionary does not exist on the server.c)Access was denied due to insufficient rights.d) TimeOut while contacting server.e)Software or Other errors.


Dictionary PropertyDialog – “Error removing banned words”

Possible causes are:a) communication problem with server.b)dictionary does not exist on the server.c)Access was denied due to insufficient rights.d) TimeOut while contacting server.e)Software or Other errors.


Dictionary PropertyDialog – “Error removing banned words”

Possible causes are:a) communication problem with server.b)dictionary does not exist on the server.

Check the dictionary object exists on the server. Check if the operator has sufficient rights to access the dictionary. For Software


Message Explanation User actionc)Access was denied due to insufficient rights.d) TimeOut while contacting server.e)Software or Other errors.

errors call software support.

USER MANAGEMENTAccess Denied, could not create user. The user is not authorized to create a User

Operator has insufficient rights to create user.

Nothing.

Invalid user name, could not create user. User with user name:’xxx’ already exists

Self Explanatory Nothing.

Invalid user name, could not create user. The username selected is invalid. A valid user name should be at least n characters long.


Invalid password, could not create user The password selected is invalid. A valid password should be atleast n characters long.


General server error, could not create user.

Error inserting in the database or other errors.

If it is a database error. Note why the record could not be created. Contact software support

Could not communicate with server object, could not create user.

Communication problems Contact technical support

Server object does not exist, could not create user.

Object does not exist on the server.

May be the user was deleted by another operator. Refresh the GUI and try again. Check the trader. See if the object is published. Check the database for the presence of the object.

General error, could not create user

Unknown error. Contact technical support

Access denied error, could not delete user ‘username’

Self explanatory Nothing.


Message Explanation User actionUnknown user, could not delete user ‘username’


User logged in, could not delete user ‘username’


Invalid action, could not delete user 'username’. Roles and Users cannot be deleted when logged in to a replicated database. Log in at the master "operations center and repeat the operation or contact the Database Administrator.

User can be deleted from SOC only.

Try from SOC.

General server error, could not delete user



Could not communicate with server object, could not delete user ‘username’

Communication problems. Contact technical support

Server object does not exist, could not delete user ‘username’



General error, could not delete user ‘username’

Unknown errors Contact technical support

Access denied error, failure getting user names: The user is not authorized to get a list of users in the System

Self explanatory Nothing

General server error, failure getting user names.



Error communicating with server object, failure getting user names.


Server object does not exist, failure getting user names.


May be the user was deleted by another operator. Refresh the GUI and try again. Check


Message Explanation User actionthe trader. See if the object is published. Check the database for the presence of the object.

General error getting user names..

Unknown errors. Contact technical support

Access denied error, could not create role ‘role.name’ The user is not authorized to get the Role list.


Duplicate role name, could not create role ‘rolename’

Self explanatory Nothing. Try another role name.

General server error, could not create role ‘rolename’….



CORBA comm error calling server, could not create role ‘role.name’…


CORBA transient error calling server, could not create role ‘rolename’…


CORBA object does not exist, could not create role ‘rolename’…

Could not find a server object. Check if the object is served from the server.

General error, could not create role ‘rolename’ …


Access denied error, failure getting system roles: …


"General server error, failure getting system roles: "…



Error communicating with server object, failure getting system roles.


Server object does not exist, failure getting system roles.


May be the user was deleted by another operator. Refresh the GUI and try again. Check the trader. See if the object is published. Check the


Message Explanation User actiondatabase for the presence of the object.

General error getting system roles.


Access Denied error getting roles: The user is not authorized to get the Role list


General server error getting roles: …



Could not call server to get roles.


Error getting roles:… Unknown errors. Contact technical supportGeneral error getting roles. Unknown errors. Contact technical supportAccess denied, could not delete role rolename The user is not authorized to delete a Role


Invalid role name, could not delete role rolename.

Role was not found in the database.

Double check the role exists.

The role is assigned to at least one user, could not delete role rolename.

Self explanatory Check user configuration. Remove the role assigned to any users and delete again.

General server error, could not delete role…



Invalid action, could not delete role 'rolename’ Roles and Users cannot be deleted when logged in to a replicated database. Log in at the master operations center and repeat the operation or contact the "Database Administrator.

Roles cannot be deleted from replicated database.

Try deleting from SOC.

Could not communicate with server object, could not delete role ‘rolename’

Communication Error Contact Technical Support.

Server object does not exist, could not delete role rolename


May be the user was deleted by another operator. Refresh


Message Explanation User actionthe GUI and try again. Check the trader. See if the object is published. Check the database for the presence of the object.

General error, could not delete role ‘rolename’

Unknown error Contact Technical Support.

Error getting role information: Access denied error getting the role functional rights.


The role 'rolename’ is not valid, could not get the role functional rights.

Role is not valid. May be the role has been deleted.

Refresh and try again. Check the database and server to see if the role really exists.

General server error, could not get the role functional rights.



Could not communicate with server object to get the role functional rights.


Server object does not exist, could not get the role functional rights.



General error, could not get the role functional rights for role ‘rolename’.

Unknown error. Contact tech. support

Access denied error setting the role functional rights. The user is not authorized to set role functional rights. "


Error setting the role rights - the role '"RoleName is invalid.

Role was deleted by someone. Refresh gui and try again. Check the trader and database to see if the role exists. Check roleconfiguration dialog to see if the user exists.

Error setting the role rights. SQL database constraint error

Corresponding functional right does not exist.

Double check if the functional right exists.


Message Explanation User actionGeneral server error setting the rights for role ‘rolename’…



Error communicating with server when setting the rights for role ‘rolename’…


Server object does not exist, failed to set rights for role ‘rolename’



General error, failed to set the rights for role ‘rolename’


Access denied, error getting roles for user 'username’. The user is not authorized to get user roles


Unknown user, error getting roles for user ‘username’

Role was deleted by someone. Refresh GUI and try again. Check the trader and database to see if the role exists. Check roleconfiguration dialog to see if the user exists.

General server error, failed to get roles for user ‘userName’…



Error communicating with server object, failed to get roles for user ‘username’


Server object does not exist, failed to get roles for user username



General error, failed to get roles for user username



Message Explanation User actionAccess denied, could not save changes to user username. The user is not authorized to grant roles to a user.


Unknown user, could not save changes to user ‘username’.

User was deleted by someone. Refresh GUI and try again. Check the trader and database to see if the user exists. Check user configuration dialog to see if the user exists.

Invalid role, could not save changes to user ‘username’.

Role was deleted by someone. Refresh GUI and try again. Check the trader and database to see if the role exists. Check roleconfiguration dialog to see if the user exists.

General server error, could not save changes to user



Could not communicate with the server object, could not save changes to user 'username’.


The server object does not exist, could not save changes to user ‘username’.



General error, could not save changes to user ‘username’


Access denied, could not set password for user.The user is not authorized to set a users password


Unknown user, could not set password for user

User was deleted by someone. Refresh GUI and try again. Check the trader and database to see if the user exists. Check userconfiguration dialog to


Message Explanation User actionsee if the user exists.

Invalid password, could not set password for user. The password selected is invalid. A valid password should be at least n characters long.

Self explanatory. Reselect a valid password.

General server error, could not set password for user "General server error setting the user's password



Error communicating with server object, could not set password for user ‘user’


Server object does not exist, could not set password for user ‘user’.



General error, could not set password for user ‘user’


Error setting profile properties. Requires the rights xxx.


Error setting profile properties …

Unknown error Contact Technical Support.

Error setting profile properties. Could not contact server.


Error setting profile properties. the Profile object does not exist in the server



General error setting profile properties.


Error deleting profile properties. Requires the rights xx

Self Explanatory Nothing


Message Explanation User actionError deleting profile properties…

Unknown error

Error deleting profile properties. Could not contact server.


Error deleting profile properties, the Profile object does not exist in the server.



General Error deleting profile properties.


Error getting profile properties. Requires the rights xx.


Error getting profile properties. Could not contact server.


Error getting profile properties. The UserManager object does not exist in the server.



General error getting profile properties.


Message Library ManagementError getting stored messages: <error description>

Unexpected software problem. The error description will give some more information.


General error adding the filters to the system.

Error storing the system filters in the system profile. Or Error saving the user filters in the profile for user. Unexpected software problem


Error getting library name from library in getNameFromLibrary()<error

Unexpected software problemThe service could be down or unreachable.



Message Explanation User actiondescription>Unable to check if any plans are using this stored message < in this library>. Would you like to remove it anyway?

CORBA exception while getting the Plan object or Error finding plans in the trader or unexpected system error


Insufficient rights to remove message.

Insufficient rights to perform action. GUI should not allow this in the first place


Error removing message: removeMessage: Failed to remove a Stored Message with id: <Message Name> from the library <Library Name>. Message not found.

The Message has already been removed from the library. May be the GUI was not updated.

None Required. Restart the GUI.

Error removing message: Unable to delete stored message from database.

Some unexpected database problem. We need to check the logs to give us more information on the error.


Error removing message: "Error while trying to push <event type> event on event channel. /n Failed to withdraw Stored Message <Message name> (library - <Library Name>) from the trader.

The Trading/Event Service is down or unreachable.

Check if the trading service/event service is up else contact software support.

Error removing stored message: Unable to contact server.

Possible reasons of failure: Message was not found in the library.

Unable to delete the message from the database. Could be a database problem.

Failed to withdraw Stored Message from the trader

Error occurred while pushing the Stored Message Removed Event on the event channel.

Unexpected System Error.


Unexpected error removing stored message.

Unexpected System Error. Contact Software Support.


Message Explanation User actionError removing library: <Library Name> Not authorized to remove a Message Library.

Insufficient rights. GUI should not have allowed this action to be performed.


Error removing library: <Library Name> Failed to remove Message Library <Library Name>

Possible reasons: Error getting reference to the Message Library object. Check that the Message Library service is running.Unexpected system error.


Error removing library:<Library Name> Error withdrawing Message Library from the trader: <error description>

The Trading Service is down or unreachable.

Check if the trading service is up else contact software support.

Error setting properties for library: < Not authorized to change message library name.>/< Error connecting to database.>/ <Unable to change library name in database.>/ <Error while trying to push <event type> event on event channel>/ <setName: failed to set name for Message Library <library name>.>

Insufficient user rightsSQL Exception error while setting library name in the MESSAGE_LIBRARY table in the database or some generic unexpected database error while setting library name in the table.Some Error occurred while pushing Library Name change on the event channel to notify other GUI’s. or unexpected system error.


Could not create library: Error retrieving factories from the trader

Could not create the library, no factories successfully created the library.

The trading service may be down or unreachable.

Could not create a Message Library Factory CORBA object.Insufficient user rights.Unable to obtain stored messages from the database.Audio failed to register interest or could be found to register interest.Failure storing clip.Unable to activate the Stored Message object with CORBA or register it with the trader

Check if the trading service is up and reachable or else contact Software Support.

Check if the Message Library Service is up and the server is reachable. Contact Software Support.


Message Explanation User actionDatabase error while storing a record in the MESSAGE_LIBRARY table.Failed to register library object with the trader or activate the library object.Unexpected System Error.Could not create the Message Library CORBA Object.Could not push the Library Added event on the event channel.Error storing the system filters in the system profile. Or Error saving the user filters in the profile for user.

Error <action description>: Not authorized to <action description>.



Error<action description>:Reason: Message configured to use custom header, but none supplied./ Message configured to use custom header, but the header clip is a null clip. /No message in body clip.

Unexpected software error. Create a message with the appropriate header’s and body clips and try again

Error creating stored message in library <library name> Banned words found: <word/words>

Some disapproved words were found in the message content.

Remove the banned words and try again

Error<action description>:Reason: Unable to contact any Dictionary objects <no of attempts> attempts made

Possible reasons: The service servicing the Dictionary module may be down or unreachable. Some problem while registering the dictionary objects


Error<action description>:Reason: General error checking for banned words

System Error Contact software support.


Message Explanation User actionError setting message content:<error description>Error creating stored message in library <library name>. Beacons can't be on with no message.

Unexpected Error Contact software support

Error creating stored message in library: Reason: Audio clip <audio clip description> not found to register interest.

A Database Error occurred while finding the audio clip.


Error creating stored message in library: Reason: Error while registering interest in audio clip <audio clip description>

Failure creating the AudioClipManager CORBA object or the AudioClipManager could not be resolved. General Unexpected system error.

Check whether Message library service may be down or unreachable or else Contact software support.

Error creating stored message in library: Reason: Unable to contact any AudioClipManager objects. <No of attempts> attempts made.

Unexpected software problem Contact software support

Error creating stored message in library: Reason: Caught DBException in storeClip(): <Database error description>

Database access error Contact software support

Error creating stored message in library: Reason: registerAudioClip() failed:

Unexpected Error while registering the audio clip while created a HAR stored message.


Error creating stored message in library: Reason: Unable to add/update stored message to database.

Database access error Contact software support

Error creating stored message in library: Reason: publishStoredMessage():unabl

Some unexpected CORBA exception or the trading service may be down or



Message Explanation User actione to get POA for a storedMessage <stored message name> in the library <library name>./unable to activate a stored message <stored message name> in the library <library name>./unable to obtain a reference for a stored message <stored message name> in the library <library name>./unable to register object for a storedMessage message <stored message name> in the library <library name>.

unreachable

Error creating stored message in library: Reason: publishStoredMessage(): Library <library name> already contains a Stored Message with ID: <Stored Message Identifier>

The Message already exists. None Required.

Error creating stored message in library: Reason: Error while trying to push StoredMessageAdded/StoredMessageChanged event on event channel.

Some unexpected problem occurred with the CORBA event channel.

None Required. The other GUI’s will be out of sync.Inform the Software support about this problem

Error <action> No permission to set message content.



Error <action> Invalid token exception while setting message data:<Error description>

The user token passed is invalid. Software Error.


Plan ManagementError getting plan name:<plan id> <error description>


Error getting plan items:<plan name> <error description>



Message Explanation User actionError removing plan: Not authorized to remove a plan.

Insufficient user rights. GUI should not allow this action to be performed in the first place


Error removing plan: Failed to remove Plan <Plan Name>.

Possible reasons: Error occurred while getting a Plan object.

Check that MsgUtilityService is running and the server is reachable.

Error removing plan: Plan to remove has not been specified.

This should not happen. Software error


Error removing plan: DB error while deleting a record from PLAN table: <error description>

Error removing plan: Generic error while processing database: <error description>

This is a database access error.

Check that the record exists in the database. Refresh the GUI.Then check whether the GUI still shows the plan.

Error removing plan: Error withdrawing Plan <Plan Name> from the trader:<error description>

There was a problem withdrawing the offer from the trader.

Check the trader to see that the plan does not exist else call software support.

Error creating plan: unable to get factory objects.

Could not query the trader for the Plan Factory objects

Check that the trader is running and is reachable. Contact the software support.

Error creating plan: No factories available.

Error creating plan: TriedFactories without success.

The trader could find any Plan Factory objects or getting a reference to the Plan factory object failed.

Could not get a plan factory object reference.Database error while getting plan item list.Error connecting to the database / Database error while inserting a record into PLAN table/ Unexpected error while processing database to insert the plan.Failed to export plan to the trader.Unexpected system error.

Check that the message utility service is running and reachable. Or else contact software support.



Message Explanation User action

Error creating plan: <plan name> user does not have sufficient rights to create plans.

User does not have sufficient rights. The GUI should not have allowed this action to be performed in the first place.


Unable to add plan item to plan <plan name>/Error adding message to Plan: Not authorized to add a Plan Item.



Unable to add plan item to plan <plan name>/Error adding message to Plan: Cannot create a Plan Item.< Item Data is null/Item Name not specified>.

This should not happen. Software error


Unable to add plan item to plan <plan name>/Error adding message to Plan: Error connecting to database/ Exception in PlanDB.insertPlanItem while<task description> <error description>

Database Error. Contact Software Support

Unable to add plan item to plan <plan name>/Error adding message to Plan: Failed to export a Plan Item <Plan item Name> (plan – <Plan name>)

Could not register this plan item with the trader.

Contact Software Support. Make sure the trading service is running and reachable.

Unable to add plan item to plan <plan name>/Error adding message to Plan: Plan: <Plan Name> already contains a Plan Item with ID: <Plan item id>

Software Error. Contact Software Support

Unable to add plan item to plan <plan name>/Error adding message to Plan:Failed to create and publish a Plan Item <plan item name> (plan - <plan name>

Unexpected system error Contact Software Support

Unable to add plan item to Could not register this plan Contact Software Support


Message Explanation User actionplan <plan name> item with the trader.

Unexpected system error.Database Error.

Error removing item:<plan item name> from plan <plan name> (Access denied. Reason= No permission to remove a Plan Item/Not authorized to remove a plan item. User needs rights=<Right Name>



Error removing item:<plan item name> from plan <plan name> (Plan Item with id: <id> not found in the hash table for Plan <Plan name>)

GUI is not updated to reflect this.

Refresh or restart the GUI. Check the database for the presence of this plan item.And check the trader for the offer of this plan item.

Error removing item:<plan item name> from plan <plan name> (Error connecting to database/ DB error while deleting a record from PLAN_ITEM table:<error description>/ Generic error while processing database:<error description>

Database error. Error description should give us more information


Error removing item:<plan item name> from plan <plan name> (Failed to withdraw Plan Item <Plan Item Name> (plan - <Plan Name> from the trader.)

Unexpected Error. And check the trader for the offer of this plan item.Check that the trading service is running and reachable

Error removing item:<plan item name> from plan <plan name>( Failed to remove a PlanItem <plan item name> from the Plan <plan name>)


Error <action description> <error description> Could not contact server/ Timed out while attempting to contact server/ The object does not exist in the server/ General

The service could be down or in a bad state. Or some unknown error occurred

Check that the required service is running and reachable. Contact Software Support


Message Explanation User actionerror while attempting to contact server/ Unexpected errorError setting plan item data: No permission to set Plan Item (data/name).



Error setting plan item data: Exception in PlanDB.insertPlanItem while <task description> <error description>

Error setting plan item name:DB error while setting PLAN_ITEM_NAME in the PLAN_ITEM table:<error description>

Error setting plan item name:Generic error while processing database: <error description>

Database error. Error description should give more info as to why this error occurred

Contact Software Support with error description.

The plan name must contain at least one character.

plan with the name <name> already exists. Please choose another name.

Self explanatory Take the required actions and try again.

Error setting plan properties: (Access denied. Reason=Not authorized to change plan name. User needs rights=<Right Name>)



Error setting plan properties: Failed to set plan name for plan <plan name>


TSS ModuleError getting hardware status from rtms:<error description>

Possible reasons: Could not get the RTMS object referenceThe error description should

Check that the TSS service is running and reachable else contact software support.


Message Explanation User actionbe able to provide more information

Add TSS failed: <TSS Name> - Unable to add TSS to a server.

There are no TSS factory objects to work with or they could not be reached.

Check the Service hosting the TSS Module is running and reachable.

Error adding new RTMS <RTMS name > to the <RTMS Factory name>: User does not have proper rights to<action description>.

Insufficient User Rights. The GUI should not have allowed this action to be performed


Error adding new RTMS <RTMS name > to the <RTMS Factory name>: Invalid configuration: TSS must have a name./ Invalid configuration: TSS must have a location./Invalid configuration: The owning organization id is not valid./Invalid configuration: The poll interval must be greater than zero./Invalid configuration: The default phone number is not valid./Invalid configuration value./

Invalid configuration: Port manager list is invalid./

Invalid configuration: drop address is not valid for an RTMS./

Invalid zone number in zone group<zone group description>/

Failure adding RTMS to database./

Error connecting and

Self Explanatory

The zone group number is not unique within the TSS configuration

The Port Manager List is null or empty

Drop address should be between 0 and 255 (inclusive)

Zone number is not between the min and max zone number as required for RTMS

Possible reasons: Error Connecting to the database or SQL exception.Error activating the new

Specify valid fields.

There should be at least one Port Manager specified.

Specify valid drop address.

Specify a valid zone number.

Check that the database is running and reachable. If yes contact software support.Check that the trading service


Message Explanation User actionpublishing RTMS <RTMS Name>

RTMS CORBA object ORRegistering the object with the trader.

is running and reachable an dif the new RTMS object has been registered in the trader. Else Contact Software Support.

Error adding new RTMS <RTMS name > to the <RTMS Factory name>: could not contact the server, the server process is probably down.

Self Explanatory Start the server TSS process.

Error adding new RTMS <RTMS name > to the <RTMS Factory name>: timed out while attempting to contact server machine.

Some network problems contacting the server machine

Contact technical support.

Error adding new RTMS <RTMS name > to the <RTMS Factory name>:the factory object does not exist in the server.

Unexpected Error. Check the trader for the factory object.

Error adding new RTMS <RTMS name > to the <RTMS Factory name>: could not contact the server, the server process is probably down.

There is some network problem or the server may be down

Check that the server is running and reachable.

Error adding new RTMS <RTMS name > to the <RTMS Factory name>: See Log File for details.

Unexpected Error. Contact Software Support.

The issued command could not be handled.

Unexpected Error. Contact Software Support.

Unable to get config and status from tss: Access denied

Insufficient rights. GUI should not allow this to happen.


Error getting config and status from tss <tss name>:<error description>

Unexpected Error. Check that the TSS service is running and reachable. Contact Software Support with error description.

Unable to contact server. Server is down or unreachable

Start the TSS process on the server and check whether it is reachable.


Message Explanation User actionError: Server side TSS object does not exist.

Server may be down or unreachable.

Start the TSS process on the server and check whether it is reachable. Check the trader for this TSS object.

You do not have the proper rights to perform this operation.



Device is now online/ offline. maintenance mode Warning: Error updating status in database.


Access denied <action description>: Improper functional rights. TSS: <TSS name>



Error setting TSS configuration: The device must be in maintenance mode when you set the configuration. TSS: <TSS name>

Before setting the configuration the device must be in maintenance mode. GUI should not allow this to happen.


Error setting TSS configuration:Warning: Config changed but following errors occurred - Failure while updating the database with the new configuration values.



Message Explanation User actionError setting TSS configuration:Warning: Config changed but following errors occurred - Failure while pushing event to notify others of new configuration values.

Operation caused some data in the configuration or status of a device to change, but the new information was not successfully pushed out to the GUIs (or any other listeners) via the event channel. GUIs will report outdated information about the device unless/until another operation which also changes the configuration or status is successfully performed (with a successful push).

The user who requested the operation can perform a “Refresh” of the device that should cause the correct information to be pulled into the GUI (but other users at other GUIs would never know that their GUIs are out of synch. Therefore it behooves the user who receives this message to report this problem immediately.

Warning: The TSS may have been previously removed. Removing reference.

The object does not exist. None Required. Check the trader to see that object does not exist.

Error removing TSS: <TSS Name> <error description

Unexpected Error Contact Software support with error description

Error removing TSS: <TSS Name> Error locating <TSS type> specified for removal.

The object does not exist. None Required. Check the trader to see that object does not exist and refresh the GUI.

Error removing TSS:Warning - RTMS has only been partially removed from the system.

Error disconnecting the object from the CORBA orb or Error withdrawing offer from the trader or Error removing RTMS from database or Error pushing object removed to the other GUI’s

None Required on part of the user but inform the software support.

Error editing TSS configuration. Unable to acquire Organization list

Unexpected Error Contact Software support

Invalid time entered:<time> Self explanatory Enter a valid time.

Program error, invalid owning organization exists in combo box

Self explanatory Contact Software support

Unable to create TSS. The required model support must be installed in the GUI. Error: Unable to create TSS

Unexpected Error. Contact Software support


Message Explanation User actionError: The zone group number must be numeric.

Error: A zone group with ID <ID> already exists.

Self Explanatory Enter a valid numeric zone group number.

Error extracting data that has been input. <error description>Error updating zone group data: Could not find zone group with number =<Zone group number>

Unexpected Error. Contact Software support

Invalid data received: expected VOL_LONG(number) message but received (number)

Error sending command (<description>) to RTMS

No response from device on receive #<no of Reads>

Invalid state encountered in state machine.

Checksum error - computed checksum (<computed checksum>) does not equal msg checksum (<checksum got>)

Error receiving data - receive #<no of Reads> - DataPortIOException: <error description>

Protocol Error while talking to the device.


FMSUnable to add port/update port status. Access denied. Reason xxx User needs rights yyy.

Insufficient rights Nothing.


Message Explanation User actionUnable to add port/update port status …

General error. Contact support

Unable to add port/update port status. Could not contact server

FMS service not reachable. Communication error. Contact Support.

Unable to add port/update port status. Timed out while attempting to contact server.

Communication error Retry. Contact Support

Unable to add port/update port status. Object does not exist on the server.

Port manager is not available. Check the trader. Check the Field Communications service is up.

Unable to add port/update port status. General error while contacting server.

General error. Contact support

Unable to add port/update port status. Unexpected error.

Unknown error. Contact support


Below is a list of web server-side and GUI-side messages, an explanation of each message, and recommended user action.

The strings enclosed in square brackets (“[]”) or angle brackets {“<>”) are replaced with appropriate information when the message is logged. For example [DMS Name] is replaced with the name of the DMS.

Attempted Action

Error Message Reason Suggested Action

General Invalid request: <action name>

A request was made, but there is no CHART request handler defined to handle it.

Contact administrator. (Administrator: check MainServlet.props and/or call software support)

General Action '<name>' is not supported.

CHART configuration file MainServlet.props is set up incorrectly. There is a request type mapped to a valid request handler, but the action is not implemented by that request handler.


General You do not have rights (or permission) to perform operation X

You probably do not have sufficient rights to perform the operation. However, the CHART code and/or template file should not have displayed the link to perform the operation.

For rights inquiries contact system administrator. Also contact software support.

General Unable to locate <object name or ID>

Either the object was removed from the CHART system after the page was displayed, or there is an internal error in CHART.

Contact software support if you believe the object should still exist in the system.

General <Object name or ID> not found

Either the object was removed from the application server after the page was displayed, or there is an internal error in CHART.



Attempted Action


General A required [form] parameter is missing.

A CHART velocity template file is not supplying the code with all of the parameters the code expects.


General Request is missing a required parameter.



General The <parameter name> parameter must be specified.



General Error getting form data. <other details>



General The parameter <X> is not numeric

The CHART velocity template file has a problem.


General Error redirecting to page <X>

CHART is attempting to take you to a page showing the results of the command, but there is some problem.

For most commands you can see the results by hitting the Back button or clicking on Refresh. If you issued a long running command such as a device command, open the Command Status page.

General Command was issued, but unable to monitor its status. Use the back button to return to the <page name> page.


If the command is finished you can see the results by hitting the Back button or clicking on Refresh. Also you can open the Command Status page.


Attempted Action


General Command was accepted, but unable to return to <page name>.


If the command is finished you can see the results by hitting the Back button or clicking on Refresh. Also you can open the Command Status page.

General VTL parse error in template <template file name>

The Velocity template file has incorrect syntax and needs to be edited.


General File not found: template <template file name>

An invalid template name exists in the code (or in another template file), or there is an installation error.


General Error loading template <template file name>

General error loading the template.


General Error <attempted action description>. Reason: Access denied. <details>

You do not have sufficient rights. However, CHART should not have displayed the link

Contact the system administrator for rights issues, and software support.

General Error <attempted action description>. Reason: Resource control conflict. <details>

The resource is under control of another operations center and you do not have the rights to override control.

Contact appropriate personnel at controlling operations center.

General Error <attempted action description>. Reason: CHART2Exception. <details>

The CHART application server service returned an error. This could happen for many reasons.

Contact administrator and/or software support

General Error <attempted action description>. Reason: CORBA comm failure, failure contacting object in the server

The CHART service you are trying to contact is probably not running.

Contact administrator to check health of service.


Attempted Action


General Error <attempted action description>. Reason: CORBA no response, timed out waiting for a response from server

Either the network is experiencing temporary problems, or the CHART service is too busy to respond in a reasonable amount of time (which indicates a system load problem).

In either case, contact the system administrator.

General Error <attempted action description>. Reason: CORBA object does not exist, object does not exist in the server

The object has been removed from the CHART application system, or the CHART application service is not fully started yet.

Wait a minute or so, then try again. If same error occurs, contact an administrator to see if object has been removed from the system.

General Error <attempted action description>. Reason: CORBA transient failure, failure contacting object in the server

The CHART service you are trying to contact is probably not running.

Contact administrator to check health of service.

General Error <attempted action description>. Reason: unexpected CORBA failure, see the log file

An unexpected CORBA error occurred when attempting to contact CHART service.


General Error <attempted action description>. Reason: unexpected failure, see the log file

General error. The reason can only be determined by looking at the CHART log file.


General Error handling <attempted action description>. Please notify an administrator



General Unable to <attempted action description>.



General Could not parse date. There was an error on a CHART date entry form



Attempted Action


General An error was reported by the system. Details follow: <details>

General error. Contact software support.

General The CHART system is currently unavailable. Please try again later.

Unable to contact the CHART application server service

Try again, then contact the system administrator.

View Arb Queue

Unable to view queue of device with ID <id>

Could not contact the CHART application server or the CHART application server returned error or internal CHART error


Evaluate Arb Queue

Unable to force queue evaluation of <deviceName>

Could not contact the CHART application server or the CHART application server returned error


Evaluate Arb Queue

Unable to force queue evaluation of device with ID <id>

Internal CHART error Contact software support.

Refresh Arb Queue

Unable to refresh arb queue of <deviceName>



Refresh Arb Queue

Unable to refresh arb queue of device with ID <id>


Move Arb Queue Entry

Unable to move entry in queue of <deviceName>



Move Arb Queue Entry

Unable to move entry in queue of device with ID <id>


Remove Arb Queue Entry

Unable to remove entry in queue of <deviceName>




Attempted Action


Remove Arb Queue Entry

Unable to remove entry in queue of device with ID <id>


View Service Details

Information for the selected service is not available.


Shutdown Service

An error occurred while attempting to shutdown the selected service (<name>). Detailed error information follows: <details>



Shutdown Service

The selected service is unavailable for contact at this time.


Set Service Log Level

You must select the log level to set the service to.

Invalid form data entered or template file error.

Enter a log level if you can, or contact software support.


Error on form: The log level selected is not numeric.

CHART template file error

Fix template and/or contact software support.


An error occurred in the CHART system. The detailed error information follows: < CHART error>

The CHART system returned an error

Check CHART application server service log file for details.


An error occurred while processing your request. The detailed error information follows: <details>

Error contacting service or internal CHART error.



The selected service is unavailable for contact at this time.


Ping Service The selected service is unavailable for contact at this time.


Check Spelling (Manual DMS Editor)

Please specify the word that should be used to replace <word>

The spell checking form is not supplying the code with all of the parameters it expects.



Attempted Action


Check Spelling (Manual DMS Editor)

Could not find a suggestion for word <word>

No suggestions were found

Skip this word or change the text and try again

Poll DMS Cannot poll <DMS name> because it is offline

CHART believes that the DMS is offline; however, the link to the Poll Now command should not have been displayed.

Put the DMS online or in maintenance mode first; also contact software support.

Edit DMS Response Message

The message could not be saved due to the following error: The message contains the following banned words: <banned words>

The message contains words defined in the banned words dictionary.

Change the wording of the message and try again.


The message could not be saved due to the following error: A line of the message is too long for this DMS and will be truncated.

The text of the message is too long to fit on the sign.

Modify the message and try again.


The message could not be saved due to the following error: The message will not fit on this DMS. It contains too many rows.

The message contains more rows (lines) than the DMS. However, CHART should not be allowing you to enter an invalid number of rows.

Use less rows and try again. Also contact software support.


The message could not be saved due to the following error: The message will not fit on this DMS. It requires <or contains> too many pages.




The message could not be saved due to the following error: The message will not fit on this DMS. It requires too many columns.




Attempted Action



Unable to load the response plan item editor. Please contact the system administrator if the problem persists.

Internal CHART error. Contact the system administrator and/or software support.


The message could not be saved. Please contact an administrator if the problem persists.

Either the DMS or Response Plan Item was removed from the CHART system after the page was displayed, or there is an internal error in CHART.



The message could not be saved because it could not be checked for banned words. Please notify an administrator if the problem persists.

Error when calling the CHART application server to check the message, or internal CHART error.

Contact the system administrator to check the health of the CHART service containing the dictionary module.


Unable to perform spell check. Would you like to set the message anyway?

General error occurred when attempting to spell check.

You can still set the message by clicking on Yes/OK/Submit. Also contact the system administrator.


Failure setting response plan item data, reason: <details>

The CHART application server system returned an error when setting the response item data.

Contact the administrator.


Failure setting response plan item data, please inform the administrator.

General error occurred when setting the response item data.

Contact the administrator or software support.


Failure saving the response plan item data.

General error occurred when setting the response item data.


Spell Check DMS Response Message

The spell check could not be performed. Please contact an administrator if the problem persists.

General error occurred when spell checking.



Attempted Action


Take HAR Offline

Error taking HAR <name> offline: <details>

General error occurred. Contact the administrator or software support.

Put HAR Online

Error putting HAR <name> online: <details>


Put HAR In Maint Mode

Error putting HAR <name> in maintenance: <details>


Set HAR Transmitter On

Cannot Set transmitter ON. The HAR is under control of operations center <op center name>



Set HAR Transmitter On

Error returned by the Set transmitter ON command: <details>



Set HAR Transmitter Off

Cannot Set transmitter OFF. The HAR is under control of operations center <op center name>



Set HAR Transmitter Off

Error returned by the Set transmitter OFF command: <details>



Reset HAR Cannot Reset HAR. The HAR is under control of operations center <op center name>



Reset HAR Error returned by the Reset HAR command: <details>



Setup HAR Cannot Setup HAR. The HAR is under control of operations center <op center name>




Attempted Action


Setup HAR Error returned by the Setup HAR command: <details>



Spell Checking Please specify the word that should be used to replace <word>

Probably you did not enter a word to replace the unapproved word.

Enter a replacement and try again.

Spell Checking Could not find a suggestion for word <word>

There are no defined words suitable for replacing the misspelled word.

Try again, or contact the system administrator.

Spell Check HAR Response Message

The spell check could not be performed. Please contact an administrator if the problem persists.

General error occurred when spell checking.


Listen To HAR Clip

Error processing the request to listen to a clip: <details>

Error processing the request or the clip is not in use.


Listen To HAR Clip

Unable to listen to the requested clip. The clip type is not supported.


Listen To HAR Clip

Unable to listen to the requested clip: The clip is empty.

The clip cannot be listened to; it is an empty clip.

The clip must be changed before listening.

Listen To HAR Clip

Error collecting audio data from server: <details>

CHART experienced an error when getting the audio data from the CHART system.

If problem persists, contact administrator.

View HAR Audio Playback Status

The request has timed out.

CHART is no longer providing feedback for audio playback that was requested.

Try the command again.


An error has occurred while delivering the audio data to the web browser:



Attempted Action



An error has occurred while retrieving the audio data:


Cancel Audio Playback

The request has timed out.

CHART is no longer providing feedback for audio playback that was requested.

No action required.

Preview HAR Text Message

Error collecting audio data from server: <details>

CHART experienced an error when getting the audio data from the CHART system.

If problem persists, contact administrator.

Edit HAR Response Message

An application error has occurred. Please notify an administrator if the problem persists.

Internal CHART error. Contact software support


An application error has occurred. Please notify an administrator if the problem persists.

Internal CHART error. Contact software support


The audio clip could not be used. Please try again or contact technical support.

An error occurred when trying to open the clip file or send the clip to the CHART application server



You must select an audio clip by clicking the 'Browse...' button.

You selected radio button for audio clip but did not select an audio file.

Choose an audio file and try again.


The message could not be saved because it could not be checked for banned words. Please notify an administrator if the problem persists.

Error when calling the CHART application server to check the message, or internal CHART error.

Contact the system administrator to check the health of the CHART application server service containing the dictionary module.


Attempted Action



The message could not be spell checked. Would you like to set the message anyway?

General error occurred when attempting to spell check.

You can still set the message by clicking on Yes/OK/Submit. Also contact the system administrator.


The message could not be set. Please contact an administrator if the problem persists.

Either the HAR or Response Plan Item was removed from the CHART system after the page was displayed, or there is an internal error in CHART.


Edit HAR Response Message (Cancel after spell check)

Error setting message to specified text. Please try again or contact technical support.

Error calling CHART to set the response message, or an internal CHART error occurred

Contact system administrator.


The following clips existed in this response plan item but will not be used once this message is saved.

The response message was originally created in the CHART application server. However, the CHART message editor supports only one message body clip, and it uses the default header and trailer for the HAR. This is by design.

Accept the change, or modify the message body as needed, or remove the response item and create a new one, or use the CHART GUI to edit the item.

Edit HAR Message

<Action failed msg>. Your editing session may have timed out. Please try again.

CHART has discarded the temporary data associated with the page because of inactivity.

Go back to the link to edit the HAR message and try it again.

Edit HAR Slot Message

The selected slot number cannot be edited.

The selected slot is not a user slot. Possible coding error.

Select another slot and/or contact the system administrator.

Send Instant Message

Please select one or more recipients and type a message.

You didn't specify the message and recipient, or there was an error on the form.

Enter the message and recipient and try again.


Attempted Action


Refresh SHAZAM

Cannot refresh SHAZAM <name> state because it is offline.

The SHAZAM is offline; however, CHART should not have displayed the link.

Put the SHAZAM online or in maintenance mode. Also contact software support.

Add New Traffic Event (all event types)

Error creating the traffic event wrapper [reason].

The traffic event could be created, but not added to the GUI cache and it may therefore not show up right away on the user’s screen.

Navigate to the list of open traffic events, as it may be in the list. Contact system administrator if problem persists.

Add New Traffic Event (all event types)

The traffic event could not be created by any available traffic event service.

Could not successfully contact CHART to create a traffic event. Most likely the CHART traffic event service is down or unresponsive or there are network problems.

Contact the system administrator.

Add Plan (or Plan Items) To Response

Unable to add <number> response plan items. See the details below. <details for each plan item>

The Plan may be old and the plan item may be referencing a device or library message that no longer exists. Or, CHART may not have successfully queried the CHART application server services (possibly because they are down)

If problem persists, contact system administrator to maintain the contents of the plan or to start appropriate CHART application server services.

Select DMS/HAR/Plan For Response Plan

Failure getting op center folder, see log file for more information.

Could not get the folder information to display a subset of devices or plans.

Try searching for the device or plan instead of selecting it. Also contact software support.

Search For DMSs/HARs/Plans To Add To Response Plan

No DMSs/HARs/Plans were found matching the search criteria.

The system could not find any items matching the search data.

Modify the fields on the search form to be less specific and try again, or else click on Select DMS/HAR/Plan instead of searching.


Attempted Action


Traffic Events (General)

Error <action name>: <details>

The CHART application server system may have returned an error, otherwise it may be a CHART web server problem.



Error <action name>, failed to revoke execution of <number> response plan items.

The CHART traffic event service had problems removing the response items from the response devices' arbitration queues. The CHART DMS and/or HAR services may be down.



Warning: successful in <action name>, but failed to revoke execution of <number> response plan items.

The CHART traffic event service had problems removing the response items; however, the overall operation was successful. The CHART DMS and/or HAR services may be down.



The requested traffic event was not found.

An action was requested on a specific traffic event but that event was not found in the GUI Cache. The object could have been removed from the system.

Refresh the traffic event list you were viewing and see if the object disappears, in which case it was removed from the system.

Edit Lane Configuration

The list of available lane configurations is not available.

CHART has not obtained a list of standard lane configurations from the CHART traffic event service. The event service may be down or there may be a database problem.



Attempted Action



Could not find a match for the specified lane configuration.

Either CHART has not been able to query the list of standard lane configurations, or the database has been changed since the lane configuration was set previously.

Try selecting another lane configuration from the list. If the list is not empty, the database has probably been changed.


If you wish to specify a lane configuration, you must first select a direction other than "None".

A direction must be specified to work with a lane configuration; otherwise the orientation of the roadway would be undefined so lane closures would be ambiguous.

Select a direction first and then select the configuration (if necessary)

Associate Event

Some errors occurred. Associated <number> of <number> events.

General error associating events. Possibly the CHART traffic event service is experiencing problems.


Merge Events Command was issued, but error redirecting you to the monitor command status page. You may view the command status via the Command Status link.

Redirect failed. Use the View Command Status link to view the progress of the merge.

Change Password

Type your current password and then type your new password twice.

You probably did not enter information in all required fields.

Try again. Enter the user name, password, and retype your password.

Change Password

The verify password does not match the new password.

The new password and the retyped password did not match.

Try again.

Change Password

Your username was not recognized by the server.

There may be a database problem, or your account may have been removed from the system.


Change Password

The current password you entered is incorrect.

The current password you entered was incorrect.

Try again.


Attempted Action


Change Password

The new password is not valid.

The new password must be at least 6 letters long and may not contain certain special characters.

Try again with a different password.

Change Password

The system is not available at this time.

Could not contact the CHART user management service.

Try again, but contact system administrator if problem persists.

Force Logout Force logout failed due to the following error: <details>


Login You must access CHART via a secure connection. Use https: as the beginning of the web address.

For security reasons, you must use an address that begins with https:// instead of http:// as https:// is required for SSL authentication

Edit the URL in the browser’s address bar and try again.

Login Error loading home page.

CHART is attempting to take you to the home page, but there is some problem.

Click on refresh, or try logging out and then log back in. Contact system administrator if problem is repeatable.

Login Error loading your start page.

CHART is attempting to take you to the home page, but there is some problem.

Click on refresh, or try logging out and then log back in. Contact system administrator if problem is repeatable.

Change User Please enter the new user’s username and password.

The new user did not fill in the required user name and password.

Try again.

Logout You are logged out, however an error occurred during the logout process. Please report the following information to your system administrator: <details>

Unexpected error logging out.



Attempted Action


Logout An error occurred during the logout process.

Unexpected error logging out.


Edit System Profile

The HAR inter-message spacing must be less than 65.

You entered an invalid value.

Correct the value and try again.

Edit System Profile

The HAR monitor time must be greater than 0 and less than 360



Edit System Profile

The standard refresh rate must be between 15 and 65535



Edit System Profile

The frequent refresh rate must be between 1 and 65535



Edit System Profile

The command status refresh rate must be between 1 and 65535



Edit System Profile

The max instant message history must be between 10 and 65535



Edit System Profile

The number of recent viewed events must be 10 or less.



Edit System Profile

The command status auto cleanup must be between 1 and 65535.



Edit System Profile

The normal service ping cycle must be between 1 and 65535.



Edit System Profile

The frequent service ping cycle must be between 1 and 65535.



Edit System Profile

The frequent service ping cycle timeout must be between 1 and 65535.



Set/Edit alert audio cue

The uploaded file does not appear to be an mp3 file.

The file uploaded for use as an alert audio cue is not an mp3 file.

Close the error message window and browse for another MP3 file.


Attempted Action


Add Word To Dictionary

Error adding word to dictionary. Please notify an administrator if the problem persists.

Unknown error adding word.

Contact administrator or software support.

Add Pronunciation to Dictionary

Error adding pronunciation. The following pronunciation(s) was(were) rejected.

The word that was added is a banned word.

Add a pronunciation for a different word, or remove the word from the banned words list if appropriate.

Transfer Resources

You must select at least one resource to transfer and one operations center where the resources are to be transferred.

These items were not selected.

Select the resources and operations center and try again.

Transfer Resources

The operation center selected is no longer valid.

Either the object was removed from the CHART system after the page was displayed, or there is an internal error in CHART.


View Folder Error viewing folder. No folder specified.

You did not select a folder from the form.

Select a folder and try again

Add Objects To Folder

Error adding objects to folder with ID <ID>



Add Objects To Folder

Error adding objects to folder. No folder specified.


Select a folder and try again.

Remove Objects From Folder

Error removing objects from folder with ID <ID>



Remove Folder Error removing folder. No folder specified.



Edit Folder Could not retrieve existing data for folder with ID <ID>




Attempted Action


Edit Folder Error setting name and/or centers for folder with ID <ID>



Edit Folder Folder change operation failed. No folder was specified.



Save Shift Handoff Report

You are not permitted to save a shift handoff report for another center.

CHART should not have provided a link to edit a shift handoff report for another operations center.


Override Comm Log Entry Timestamp

Error creating form to override timestamp.

CHART error displaying form.

Try again. If problem persists, contact system administrator.

Add DMS / TSS

Add DMS/TSS form data not found, possible timeout.


Restart the operation by clicking on Add DMS/TSS.

Add HAR / SHAZAM

Error displaying the Add HAR / SHAZAM form. The form may have timed out. Contact the system administrator if the problem persists.


Restart the operation by clicking on Add HAR / SHAZAM.

Add <device or object>

The name selected is already in use. Please choose another name.

Duplicate names are not allowed (to prevent confusion).

Enter a different name.


Could not add <device or object> to any Site using the automatic site selection feature

None of the factories in the system could be called to create the object.

Try again, and if it doesn’t work contact the system administrator – CHART services may be down.


Attempted Action



Could not add Operations Center to the selected Site. Try again or choose another site. Contact the system administrator if the problem persists.

The selected factory / site could not create the object. The CHART service at the selected site may be down.

Try again using automatic site selection.

Poll Multiple Online DMSs

No DMSs were selected for polling.

You did not select any DMSs on the select DMS(s) form.

Select one or more DMSs and try again.

Remove Operations Center

Unable to remove the operations center because there are one or more users logged in.

Users are logged in. Wait until users are logged out or force them to log out and try again.

Comm Log Search

Entries that do not have a checkbox next to them are no longer active in the system and cannot be included when creating a new traffic event.

Comm log entries that are older than a specified time are not eligible for being used to open a traffic event.

No workaround, except perhaps enter a new comm log entry the same as the old one.

Setting traffic event location (either while creating or editing traffic event)

Error getting data to populate form fields. [details]. Try using freeform text.

When choosing location fields, the system attempts to fill associated lists with only valid data for the current selections. If the Location Service is not available, you will see this message. It’s possible that some lists will continue to function as normal due to the data being cached by the GUI, however other fields will require the user to manually enter location information instead of selecting it from a list.

Select data from the lists where available. Type in field entries manually when lists of data are not available.


Attempted Action


Perform various actions on home page

HTTP Request Error The home page application was unable to communicate with the web server.

Try again and contact system administrator if problem persists – it could mean the web server is down.

Perform action on an alert

Error executing [action name]: Reason: Invalid State – Alert probably changed by another user.

The alerts list on the home page only updates periodically. It is possible for another user to perform an action on an alert and your home page does not reflect that change right away.

Refresh the home page, or use one of the alert filters to cause the alert list to refresh.

Schedules (General)

Error executing [action name]: Reason: <details>

An error occurred while performing a schedule related action.

Detailed messages that have a specific suggested action are listed below. Otherwise, the suggested action is to contact the system administrator.

Schedules (General)

Error loading the form – it may have timed out.

When adding or editing a schedule, it is held in temporary storage while changes are made, and too much time has elapsed since the last interaction.

Restart the add or edit operation.

Schedules (General)

Error finding the previously stored temporary form data – it may have timed out.

When adding or editing a schedule, it is held in temporary storage while changes are made, and too much time has elapsed since the last interaction.

Restart the add or edit operation.

Schedules (General)

No ScheduleFactory exists in the system at this time …

A CHART Schedule service is not running, or was not running previously.

Have the system administrator make sure at least one Schedule service is running, and then Perform Discovery.


Attempted Action


Schedules (General)

The <parameter name> is missing.

A required request parameter is missing from the request. This usually indicates a coding error.


Schedules (General)

The specified schedule could not be found.

The action was requested for a schedule that is no longer in the system.

Refresh the schedules list page and make sure the schedule still exists in the system.

Schedules (General)

You must log in to perform this action.

The session information for your browser was not found.

Logout and log back into CHART.

Schedules (General)

You do not have permission to perform this action.

Your user rights are not set to allow you to perform the action.

Ask the system administrator to grant you the right for the action you are attempting to perform.

Schedules(Add/Edit)

Please select a pending event.

You have submitted the form used to add or edit an Open Event action without selecting a pending event.

Return to the form and select a pending event, then resubmit.

Schedules (Remove action)

The action index is invalid.

The action may have been removed by someone else.

Return to the add/edit schedule page and refresh it. If the action still appears, contact the system administrator.

Schedules (Execute)

The operation may have timed out.

The time that has elapsed since you displayed the Execute form is too long.

Begin the Execute action again, making sure to complete and submit the form in a timely manner.


Attempted Action


Schedules (Execute)

Please select at least 1 action to execute.

You submitted the execute form without selecting any actions for execution.

Return to the form and select at least one action for execution and resubmit the form.

Schedules (Schedule Traffic Event)

Could not find traffic event that has been selected to be scheduled.

The traffic event no longer exists in the system.

Create a new pending event, or select a different pending event to schedule.

Notification (General)

Error <action>: <details>

This usually is caused by the CHART server returning an error.

In most cases, you will need to contact the system administrator to resolve the issue.

Notification (Search)

Insufficient rights to search notification history.

You have not been granted the right to search the notification history.

Ask the system administrator to grant you the right.

Notification (Search)

No Notification Factories found.

The Notification service is not running, or was started recently.

Ask the administrator to make sure at least one Notification Service is running, and then Perform Discovery.

Notification (Send)

You have not been given sufficient privileges for this operation.

You have not been granted the right to send notifications.



Attempted Action


Notification (Send)

The specified traffic event was not found.

You are attempting to send a notification for a traffic event and it is no longer found in the system.

Refresh your events list to make sure the traffic event has not been removed from the system, and if it exists and you continue to get this error, contact the system administrator.

Notification (Send)

You have not been granted rights to perform this operation.

You have not been granted the required user right to send notifications.

Ask the administrator to grant you the right to send notifications.

Notification (Send)

Message text not specified.

You have attempted to send a notification without any message text.

Enter message text prior to sending the notification.

Notification (Send)

Error, the message length <length> exceeds <max length> characters.

The message text is longer than the allowable message length.

Shorten your message text and re-send. Use multiple notifications if required.

Notifications (Send)

Specified traffic event was not found in the cache.

You are sending a notification for a traffic event and it is no longer found in the system.

View the traffic event list and make sure the event still exists in the system. If it does, and you still cannot send a notification for it, contact the system administrator.


No recipients were specified.

You are sending a notification but did not select any recipients.

Select one or more recipients and re-send.


Attempted Action



No available notification services could send the notification.

The Notification Service(s) failed to send the notification.

Retry, and contact the system administrator if the problem persists.

Notification (Search Notification History)

Invalid Date Range: Begin date after end date.

You submitted the search form and the selected begin date is after the end date.

Return to the search form and change the search dates such that the begin date is before the end date, then resubmit the form.

Notification (View Details or Remove from Cache)

Notification ID not specified in request, or notification not found in cache.

The notification could not be found.

Refresh the notification history and make sure the notification still exists in the system. If it does and you still receive this error, contact the system administrator.

Notification (Remove from Cache)

You have not been granted permission for this operation.

You have not been granted the right to remove an entry from the notification cache.


Notification (Remove from Cache)

Error deleting notification.

An error occurred while removing a notification. This could happen if the Notification Service is down, or if there is an internal error.


Plan Management (View Details)

The plan could not be viewed: <details>

An error occurred while attempting to retrieve the plan.

Make sure the plan still exists in the system and try again. Contact the system administrator if the problem persists.


Attempted Action


Plan Management (View Plans)

Error displaying plan list.

The initial attempt to view plans has failed because it received a failure while attempting to redirect the browser.

Retry the operation, and contact the system administrator if the problem persists.

Plan Management (Remove Plan)

The plan could not be removed. <details>

An error occurred while attempting to remove a plan. You may not have sufficient rights, the plan may no longer exist in the system, or a system error may have occurred.

If the plan could not be found, refresh the plan list and make sure it still exists. Otherwise, contact the system administrator.

Plan Management (Add Plan)

The add plan form could not be displayed. <details>

You may not have sufficient rights, or the Message Utility Service may be down.


Plan Management (Add Plan)

The plan could not be added. <details>

You may not have sufficient rights, the Message Utility Service may be down or may have returned an error, or an internal error may have occurred.


Plan Management (Edit Plan)

The plan properties could not be edited. <details>

You may not have sufficient rights, or the plan may no longer exist in the system. The Message Utility Service may be down, or may have returned an error message.

If the error details state the plan could not be found, refresh your plan list to make sure the plan was not removed from the system. Otherwise, contact the system administrator.


Attempted Action


Plan Management (Remove plan item)

The plan item could not be removed. <details>

You may not have sufficient rights, or the plan may no longer exist in the system. The Message Utility Service may be down, or may have returned an error message.

If the error details state the plan could not be found, refresh your plan list to make sure the plan was not removed from the system. Otherwise, contact the system administrator.

Plan Management (Add plan item)

The add plan item form could not be displayed. <details>

You may not have sufficient rights, there may not be any libraries defined in the system, or the plan may have been removed.

Update the plan list to make sure the plan still exists, and make sure at least one message library exists with messages for the device type (DMS or HAR). Otherwise, contact the system administrator.


Some plan item(s) could not be added <details>

One or more plan items could not be added to the plan. This could be due to the inability to find the device that is used in the plan item, the plan already having an item for that device, the message utility service being down or returning an error.

Make sure the devices included in the plan items still exist in the system by viewing the appropriate device list. Otherwise, contact the system administrator.


The plan item(s) could not be added <details>

This could be due to none of the devices included in the plan items not being found, the stored message being used not being found, or the plan itself not being found. This can also occur if an internal error occurs.

Make sure the device(s) and message used in the plan item(s) still exist. Otherwise, contact a system administrator.


Attempted Action



The search for target devices failed. <details>

There was a problem getting the list of devices available for use in a plan item.

Retry, and contact the system administrator if the problem persists.

Plan Management (Edit plan item)

The plan item could not be edited <details>

You may not have sufficient privileges, the plan or plan item may not be found, the device included in the plan item may not be found, the message library may not be found, or an internal error may have occurred. This may also occur if the Message Utility Service is down or returns an error.

Make sure the plan, plan item, and message library still exist in the system by viewing them in their appropriate list. If they all exist, contact the system administrator.


Appendix F – DMS Special CharactersThe following table lists the display of special characters on DMSs. At this time this information is known only for the two known types of NTCIP DMSs, Addco and Daktronics. The Addco data is derived from direct observation; the Daktronics data is derived from Daktronics documentation.

Addco NTCIP DMSCharacter(s) entered via CHART Character(s) displayed on the actual sign

_ (underscore) (solid 5x7 rectangle – all pixels in the 5x7 character matrix turned on)

` (grave accent a.k.a back tick) @ (Note: @ also displays as @ )

~ (tilde a.k.a. squiggle) (solid 5x7 rectangle – all pixels in the 5x7 character matrix turned on)

<, > <, > (but incorrectly presented in CHART “Show Display” window as filled in triangles (arrow heads) pointing in the same directions)

| (vertical pipe) \ (Note: \ also displays as \ )

{, } (curly braces) [, ] (square brackets)

[, ] (square brackets) Note: a single square bracket does not display on the sign, as square brackets are used to delimit MULTI tags and they are interpreted as incomplete MULTI tags. Two consecutive square brackets ([[ or ]]) are sent to the sign as a single square bracket – however, CHART interprets the two characters as two characters and thus each use of double brackets reduces by one the number of characters which can be put on the line. Furthermore, the sign tends to misinterpret the [ as the start of a MULTI tag and it gets confused. It is strongly recommended not to use this double bracket trick. If a square bracket is truly required, use the curly braces (see above).

All other characters Display on sign exactly as entered in CHART

Daktronics NTCIP DMSCharacter(s) entered via CHART Character(s) displayed on the actual sign

[, ] (square brackets) Note: a single square bracket does not display on the

CHART Operations & Maintenance Guide R3B2 Revision 3 F-1 12/10/2008

sign, as square brackets are used to delimit MULTI tags and they are interpreted as incomplete MULTI tags. Two consecutive square brackets ([[ or ]]) display on the sign as a single square bracket. This is the only way to produce square brackets on this sign. However, CHART interprets the two characters as two characters and thus each use of double brackets reduces by one the number of characters which can be put on the line. It is recommended not to use the double bracket trick for this reason, if possible.

All other characters Display on sign exactly as entered in CHART

CHART Operations & Maintenance Guide R3B2 Revision 3 F-2 12/10/2008

Date post:	14-Apr-2017
Category:	Documents
Upload:	databaseguys
View:	197 times
Download:	6 times