EXOR Traffic Interface Manager Admin Guide

Transcription

EXOR
Traffic Interface Manager Admin Guide
February 2014
Version: 4.7
Submitted by:
Bentley Systems (UK) Ltd.,
9th Floor,
20 Gracechurch Street,
London
EC3V 0BG
EXOR
TRAFFIC INTERFACE MANAGER ADMIN GUIDE
DOCUMENT TRACKER
EXOR Traffic Interface Manager Admin Guide
Trademark
Bentley and the "B" Bentley logo are either registered or unregistered trademarks or service marks of
Bentley Systems, Incorporated, or one of its direct or indirect wholly-owned subsidiaries.
Other brands and product names are trademarks of their respective owners.
Copyright
Copyright © 2013 Bentley Systems, Incorporated.
All Rights Reserved.
Including software, file formats, and audiovisual displays; may only be used pursuant to applicable
software license agreement; contains confidential and proprietary information of Bentley Systems,
Incorporated and/or third parties which is protected by copyright and trade secret law and may not be
provided or otherwise made available without proper authorization.
Restricted Rights Legend
If this software is acquired for or on behalf of the United States of America, its agencies and/or
instrumentalities ("U.S. Government"), it is provided with restricted rights. This software and
accompanying documentation are "commercial computer software" and "commercial computer software
documentation", respectively, pursuant to 48 C.F.R. 12.212 and 227.7202, and "restricted computer
software" pursuant to 48 C.F.R. 52.227-19(a), as applicable. Use, modification, reproduction, release,
performance, display or disclosure of this software and accompanying documentation by the U.S.
Government are subject to restrictions as set forth in this Agreement and pursuant to 48 C.F.R. 12.212,
52.227-19, 227.7202, and 1852.227-86, as applicable.
Contractor/Manufacturer is Bentley Systems, Incorporated, 685 Stockton Drive, Exton, PA 19341-0678.
Unpublished - rights reserved under the Copyright Laws of the United States and International treaties.
Version: 4.7
i
CONFIDENTIALITY STATEMENT
The contents of this document, including system ideas and concepts, are confidential and proprietary in nature and are not to be
distributed in any form without the prior written consent of Bentley, Inc.
EXOR
DOCUMENT TRACKER
Document Tracker
Document Details
File:
Prepared by:
Traffic Interface Manager Admin Guide V4.7.docx
Marc Kratzschmar
Manual Name:
Reviewed by:
Traffic Interface Manager Admin Guide
Version:
Approved for issue by:
1.0
Marc Kratzschmar
Date of Issue:
Product Manager:
Feb 2014
Marc Kratzschmar
File Name:
Document Centre/Exor/Product Manuals/4.7 Product Manuals/4.7 completed documentation/ Traffic Interface Manager Admin
Guide V4.7.docx
Document Version Control
Revision
Date
By
Chapter/Page
Description
1
01-Oct-2006
MK
All
General update to reflect version 4 changes
2
Nov 2010
IS
All
Reviewed to version 4.3
3
May2011
IS
None
No changes for v4.4
4
Nov 2011
IS
None
No changes for v4.5
5
Oct 2012
IS
All
Document reviewed for 4.6 release
6
Feb 2014
BA/IS
All
Re-formatted into Bentley template for 4.7 release
Version: 4.7
ii
EXOR
TABLE OF CONTENTS
Table of Contents
1
Introduction ........................................................................................................................................... 1
1.1
What Is Traffic Interface Manager? .............................................................................................. 1
1.1.1
Who should use this guide? .................................................................................................. 2
2 Traffic Interface Manager System Overview ........................................................................................ 3
2.1
Traffic Interface Manager Components ........................................................................................ 3
2.1.1
Modules................................................................................................................................. 3
2.1.2
Packages ................................................................................................................................ 4
2.1.3
DBMS_Jobs .......................................................................................................................... 4
2.1.4
Tables .................................................................................................................................... 4
2.1.5
Triggers ................................................................................................................................. 5
2.1.6
Domains ................................................................................................................................ 5
2.2
TRADAS components .................................................................................................................. 6
2.2.1
TRADAS Packages ............................................................................................................... 6
2.2.2
TRADAS DBMS_Jobs ......................................................................................................... 6
2.2.3
TRADAS Tables ................................................................................................................... 6
3 Installing Traffic Interface Manager ..................................................................................................... 7
3.1
Software Requirements ................................................................................................................. 7
3.2
Install Traffic Interface Manager Software ................................................................................... 8
3.2.1
Install Version 4.0 ................................................................................................................. 8
3.2.2
Install Version 3.2.0.0 ........................................................................................................... 8
3.3
Set up Apache Web Server ........................................................................................................... 9
3.3.1
Ensure Oracle Web Components are Installed...................................................................... 9
3.3.2
Copy Files ............................................................................................................................. 9
3.3.3
Create DAD .......................................................................................................................... 9
3.4
Set up TRADAS Database Link ................................................................................................. 10
3.5
Set Product Options .................................................................................................................... 11
3.5.1
TS_MAND .......................................................................................................................... 11
3.5.2
TS_DB_LINK ..................................................................................................................... 11
3.5.3
VALIDIRN ......................................................................................................................... 11
3.5.4
PUBLUSEJOB .................................................................................................................... 12
3.5.5
PUBSUSPEND ................................................................................................................... 12
3.5.6
TRADMONINT .................................................................................................................. 12
3.5.7
WEBREFINT ...................................................................................................................... 12
3.5.8
DEBUGAUTON ................................................................................................................. 13
3.6
Start Traffic Interface Manager DBMS_JOB ............................................................................. 13
4 Setting up Traffic Interface Manager Metadata .................................................................................. 14
Version: 4.7
iii
EXOR
TABLE OF CONTENTS
4.1
Traffic Interface Manager Metadata Setup Sequence ................................................................. 14
4.2
Metadata for Count Sites and Traffic Sections ........................................................................... 15
4.2.1
Count site (CS) Metadata .................................................................................................... 15
4.2.2
Traffic Section (TS) Metadata ............................................................................................ 17
4.3
Setting up Factor Groups ............................................................................................................ 20
4.3.1
Count Site and Traffic Section Direction Values ................................................................ 20
4.4
Metadata for Traffic Statistic Records ........................................................................................ 22
4.4.1
Setting up Traffic Statistic Metadata................................................................................... 22
4.4.2
Traffic Statistic Publish Type ............................................................................................. 22
4.5
Setting up GIS Themes ............................................................................................................... 24
5 Setting up TRADAS ........................................................................................................................... 25
5.1
Setting up TRADAS Software .................................................................................................... 25
5.1.1
Create TNS Entry to the Highways Computer .................................................................... 25
5.1.2
Create the Database Link and Synonyms............................................................................ 25
5.1.3
Compile the TRADAS Packages ........................................................................................ 26
5.1.4
Configure the DBMS_JOBS ............................................................................................... 26
5.2
Identifying TRADAS Statistics to Publish ................................................................................. 27
5.2.1
PTMP_KEY ........................................................................................................................ 27
5.2.2
PTMP_PDB_VIEW ............................................................................................................ 27
5.2.3
PTMP_PDB_COL .............................................................................................................. 27
5.2.4
PTMP_PDB_DATA_TYPE ............................................................................................... 28
5.2.5
PTMP_PDB_LENGTH ...................................................................................................... 28
5.2.6
PTMP_PDB_MINVALUE ................................................................................................. 28
5.2.7
PTMP_PDB_MAXVALUE................................................................................................ 28
5.2.8
PTMP_ASSET_TYPE ........................................................................................................ 28
5.2.9
PTMP_IIT_COL ................................................................................................................. 28
5.2.10 PTMP_DESC ...................................................................................................................... 28
5.2.11 PTMP_PDB_WHERE ........................................................................................................ 28
5.2.12 PTMP_PUBLISH_TYPE.................................................................................................... 28
5.2.13 PTMP_ASSET_LOCALE .................................................................................................. 28
5.2.14 PTMP_DATE_COL............................................................................................................ 29
5.3
Updating TRADAS Count Site Data .......................................................................................... 29
6 Publishing Traffic Statistics ................................................................................................................ 30
6.1
Preparing TRADAS for the Publish Process .............................................................................. 30
6.2
How the Publish Process Works ................................................................................................. 30
7 Troubleshooting the Publish Process .................................................................................................. 32
7.1
Troubleshooting TRADAS Traffic Interface Manager Components .......................................... 32
7.2
Messages ..................................................................................................................................... 32
Version: 4.7
iv
EXOR
TABLE OF CONTENTS
7.3
Job Control and Status Codes ..................................................................................................... 32
7.4
Monitoring the Publish Process .................................................................................................. 33
7.4.1
Valid Publish Job Status Code Transitions ......................................................................... 34
7.5
Reset the System ......................................................................................................................... 35
7.5.1
Manually Stop the Publish Process ..................................................................................... 35
7.5.2
Manually reset the publish process ..................................................................................... 35
Version: 4.7
v
EXOR
INTRODUCTION
1
Introduction
Welcome to Traffic Interface Manager by Exor! This document explains the steps necessary to set up and administer
Traffic Interface Manager. It is intended for system administration staff responsible for setting up or maintaining the
Traffic Interface Manager system.
The guide is divided into the following chapters:
 Traffic Interface Manager System Overview
 Installing Traffic Interface Manager
 Setting up Traffic Interface Manager Metadata
 Setting up TRADAS
 Publishing Traffic Statistics
 Troubleshooting the publish process
This chapter introduces you to Traffic Interface Manager.
1.1
What Is Traffic Interface Manager?
Traffic Interface Manager is an interface between TRADAS and the Highways by Exor suite that enables users to edit
count site and traffic section data, produce and publish, display, and archive traffic statistics. All this is supported within
highway information system that also integrates traffic data with Geographic Information System (GIS) and other
enterprise databases.
Highway agencies collect, manage, and distribute traffic information to satisfy a variety of traffic data users. Common
uses for traffic data include project selection, pavement design, capacity analysis, safety analysis, air quality, and travel
forecasting (note: in the USA see AASHTO Guidelines for Traffic Data Programs. American Association of State
Highway and Transportation Officials: Washington, D.C.1992, pages 95-105). To support this agencies establish traffic
monitoring programs.
Ideally traffic monitoring programs would provide complete and continuous count data for the entire road system or count
traffic on every road every year. Limits to personnel and equipment resources make this impossible so traffic data
programs usually consist of a relatively small number of permanent traffic recorders and a greater number of short-term
counts. In this way a representative sample within the roadway system is counted that contains an appropriate mix of
volume, vehicle classification, speed, and weight data. Once the data are collected, they must be subjected to quality
assurance checks, data analysis and management, and reporting procedures.
Traffic Interface Manager works with traffic statistic packages like TRADAS to provide a single system for processing all
traffic data. The TRADAS data collection component encapsulates the automatic polling activities of a variety of device
makes and models into a single distributed service. The TRADAS analysis components examine various types of traffic.
The result is a robust traffic data system with consistent analysis and reporting throughout.
This guide focuses on the Traffic Interface Manager components of the suite. These provide functionality to manage
network locations of traffic sections and traffic count sites and to query and archive traffic statistic data. Components that
are part of TRADAS are covered by separate documentation.
Note: TRADAS Version 3.0 User’s Guide. Chaparral Information Systems, 2004).
Exor recognizes that the purchase of comprehensive software products should represent a long-term investment. As a
result Exor provides a wide range of support services to ensure that clients can make best use of our software and obtain
the maximum return on their investment.
Version: 4.7
1
The contents of this document, including system ideas and concepts, are confidential and proprietary in nature and are not to be distributed in any form
without the prior written consent of Bentley, Inc.
EXOR
INTRODUCTION
Please contact your Bentley account manager for details of support and training services.
1.1.1
Who should use this guide?
Anyone responsible for the set up or maintenance of Traffic Interface Manager should find this Guide useful.
The guide assumes that you have an understanding of the terms and functions associated with your organization and the
management of traffic data collection and analysis. It also assumes that you are familiar with core Highways by Exor
modules.
The purpose of the guide is to provide administrators with an overview of how to set up Traffic Interface Manager.
Note: This guide is intended to be read together with the Traffic Interface Manager User Guide The User Guide should
be read first because it provides an introduction to the workings of Traffic Interface Manager and because it
contains information not included in this document.
Version: 4.7
2
EXOR
TRAFFIC INTERFACE MANAGER SYSTEM OVERVIEW
2
Traffic Interface Manager System Overview
Traffic Interface Manager consists of a number of components. These are listed in this chapter.
This chapter covers two topics:
 Traffic Interface Manager components
 TRADAS components
2.1
Traffic Interface Manager Components
This section lists all the components that provide Traffic Interface Manager functionality within Highways by Exor. These
components provide several kinds of functionality
 Provide tools to set up and maintain Traffic Interface Manager metadata and to synchronize metadata between
Traffic Interface Manager and TRADAS
 Check consistency between factor group membership values of traffic sections and the count sites along them
 Track changes to count sites made within Highways, and enable these to be updated within TRADAS
 Create an explicit link between count sites and traffic sections and make this available to TRADAS
 Create traffic statistics records within Highways
The following types of Traffic Interface Manager components are listed in separate sections below:
 Modules
 Packages
 DBMS_JOBS
 Triggers
 Domains
2.1.1
Modules
The Highways by Exor user interface is divided into modules that provide discrete sorts of functionality. Traffic Interface
Manager functionality is provided through the following modules:
Module
Title
File name
Module Type
TM0001
Traffic Interface Manager metadata maintenance
Tm0001
FMX
TMWEB0001
View traffic data metadata
tm3web_metadata.list_metadata
Web
TMWEB0010
Publish traffic data
tm3web.pre_publish_interface
Web
Version: 4.7
3
EXOR
2.1.2
2.1.3
Packages
TM3AUDIT
Audit related server code
TM3FG
Factor groups package
TM3FG_GEN
Generates the factor groups package
TM3INV
Inventory related server code
TM3META
Metadata maintenance package
TM3PUB
Publish related server code
TM3WEB
Code for server-driven dynamic HTML
TM3WEB_METADATA
Code for dynamic HTML display of Traffic
Interface Manager metadata
DBMS_Jobs
tm3pub.check_for_tradas_data
2.1.4
Tables
TM_CS_AUDIT
TM_FACTOR_GROUP_TYPES
TM_PUBLISH_CONTROL
TM_PUBLISH_CS
Regenerated with Generate Changes button
TM_PUBLISH_JOBS
TM_PUBLISH_JOBS_HISTORY
TM_PUBLISH_LINK
TM_PUBLISH_LINK_ERRORS
TM_PUBLISH_TS
TM_STATUS_TRANSITIONS
TM_STATISTICS_TYPES
TM_STATISTICS_TYPES_PK_ATTRS
Additional tables are generated during system set up, based on Traffic Interface Manager metadata. These use the
following naming convention:
TM_TRADAS_<statistic asset type code>
Regenerated with Create Interface Tables
Version: 4.7
4
EXOR
2.1.5
Triggers
NM_INV_ITEMS_INSTEAD_TM3_TRG
count site audit and locking
NM_MEMBERS_INSTEAD_TM3_TRG
count site and traffic section integrity
NM_INV_ITEMS
count site audit and locking
NM_MEMBERS
count site and traffic section integrity
TM_PUBLISH_CONTROL_WHO
TM_PUBLISH_JOBS_A_INS
TM_PUBLISH_JOBS_B_INS_UPD
TM_PUBLISH_JOBS_WHO
TM_PUBLISH_LINK_B_INS_UPD_DEL
2.1.6
NM_INV_ITEMS_INSTEAD_TM3_TRG
on INV_ITEMS view
NM_MEMBERS_INSTEAD_TM3_TRG
on NM_MEMBERS view
Domains
2.1.6.1 TM_PUBLISH_TYPES
This contains the publish ranges for publish runs. It is populated with:
 DAILY
 WEEKLY
 MONTHLY
 ANNUAL
2.1.6.2 TM_PDIRDIR
This contains compass directions that correspond to the primary direction of travel at count sites and traffic sections:
Value
Description
1
North
2
Northeast
3
West
4
Southeast
5
South
6
Southwest
7
West
8
Northwest
Version: 4.7
5
EXOR
2.2
TRADAS components
This section lists all the TRADAS components that provide Traffic Interface Manager functionality.
2.2.1
TRADAS Packages
UPDATE_SITE_FROM_CS
TM_PUBLISH
2.2.2
TRADAS DBMS_Jobs
update_site_from_cs.go
tm_publish.go
2.2.3
TRADAS Tables
PDB_TM_METAMODEL_PIC
TM_CZD
TM_TZD
TM_TMP_AUDIT
TM_TMP_CS
TM_TMP_GROUP
TM_TMP_ROADNAME
TM_TMP_SITE
TM_TMP_TS
TM_TMP_XLINK
TM_SITE_ERRORS
And other TRADAS Public Database tables and views as required.
Version: 4.7
6
EXOR
INSTALLING TRAFFIC INTERFACE MANAGER
3
Installing Traffic Interface Manager
Traffic Interface Manager relies on a number of other Highways by Exor components to be installed and configured.
Much of this configuration consists of setting up the system metadata to support Traffic Interface Manager entities. This
section describes specific software that must be in place for Traffic Interface Manager to work properly.
This chapter covers the setup of the following Highways by Exor components:
 Software Requirements
 Installing Traffic Interface Manager software
 Apache Web Server
 Product Options
 TRADAS Database Link
3.1
Software Requirements
The following software must be installed for Traffic Interface Manager to run:
 Oracle Database (version 9.2.x)
 Highways by Exor (version 4)
 Spatial Manager (version 4.x) or Spatial Data Manager (for GIS client functionality, version 3.1.1.1)
 TRADAS (version 2 or 3)
Note: Setting up the Highways by Exor modules is described in the Installation Guide that accompanies the installation
program.
Version: 4.7
7
EXOR
3.2
3.2.1
Install Traffic Interface Manager Software
Install Version 4.0
Version 3.1.3.0 is a patch release of Traffic Manager and must therefore be installed on the previous version (3.1.2.0),
which is, in turn a patch and must be installed on top of the previous version (3.1.1.0) back to 3.1.0.0.
Make sure that the Traffic Manager version 3.1.0.0 installation program has been run to install Traffic Manager software.
Download Traffic Interface Manager version 3.1.1.0 installation program to your Exor base directory.
To upgrade your Traffic Interface Manager highways by exor database from V3.1.0.0 perform the following steps:
 Change directory to BASE\tm3\install
 Login to SQL*PLUS as the highways owner
 At the SQL> prompt, type start tm3100_tm3130
You will be prompted to enter the exor base directory path.
Type in the path (c:\<exorbasedirectory>\). Be sure to end the path with a slash character (“\”).
3.2.2
Install Version 3.2.0.0
Run the install script.
Version: 4.7
8
EXOR
3.3
Set up Apache Web Server
The apache web server option must be installed with the Oracle database server to support the Traffic Interface Manager
HTML form. These instructions for configuring the Highways web server are appropriate for Oracle 9i.
The configuration can be divided into three parts:
 Ensure Oracle web components are installed.
 Create a Database Access Descriptor.
 Copy files to the Apache directory.
3.3.1
Ensure Oracle Web Components are Installed
The Oracle Java Virtual Machine (OJVM) must be installed. This is installed as part of the standard Oracle 9i installation.
The Apache Web Server must be installed. The web setup is all available in the standard Oracle documentation. Check the
apache tick box and the installer does the rest, assuming default port configurations etc.
3.3.2
Copy Files
Copy the contents of nm3\admin\web\ to <apache_html> using the same directory structure i.e., make sure all sub
directories are maintained e.g., nm3\admin\web\images\*.* are copied to <apache_html>\images\*.*
<apache_html> refers to the base directory for files accessed through the Apache web server. By default this is
ORACLE_HOME\apache\apache\htdocs.
Access NM3 Web using the following URL:
http://<hostname>/pls/nm3web
Where <hostname> is the address of the server Apache and your database is running on.
3.3.3
Create DAD
A Database Access Descriptor (DAD) must be created to handle the connection to the database by the web server.
Version: 4.7
9
EXOR
3.4
Set up TRADAS Database Link
If the TRADAS and Highways databases are not running on the same computer then a database link must be established
to the computer running the TRADAS database, and synonyms must be created. If they are both on the same computer
then only the synonyms are needed.
To set up the database link type the following command:
“create database link < target TRADAS database name> connect to <user name on
target TRADAS database> identified by <password on target TRADAS database>
using <target TRADAS database TNS alias>
One Synonym is needed for the pdb_tm_metamodel_pic table in the TRADAS Public Database. This should be named:
pdb_tm_metamodel_pic
Within the Highways application, the Product Option TS_DB_LINK, the link to the TRADAS table, needs to be set to the
public synonym:
pdb_tm_metamodel_pic
This does not have to be done before setting up Traffic Interface Manager. If it is done later, then remember to set the
TS_DB_LINK product option after creating the link.
Version: 4.7
10
EXOR
3.5
Set Product Options
The following Product Options must be set. The settings you choose should be based on your organizational requirements
for Traffic Interface Manager.
Product Option
Module
TS_MAND
TM
TS_DB_LINK
TM
VALIDIRN
TM
PUBLUSEJOB
TM
PUBSUSPEND
TM
TRADMONINT
TM
WEBREFINT
TM
DEBUGAUTON
HIG
Some system Options are replicated both as Product and System Options. Where this is the case the User Option setting
will take precedence over the Product Option setting.
Product Options and User Options are maintained using HIG9130 – Product Options and HIG1838 – User Options
respectively.
Note: Note that Product Options must only be changed under advice from Exor Support.
3.5.1
TS_MAND
Mandatory Traffic Sections,
This product option specifies whether traffic section asset types are mandatory or optional. Customers that do not have
traffic sections must set this option to N.
 Valid values: Y or N. Default value is Y.
3.5.2
TS_DB_LINK
TRADAS database link,
This product option is the name of the synonym that points to the metadata table in TRADAS.
It forms the link to the TRADAS PDB_TM_METAMODEL_PIC table.
3.5.3
VALIDIRN
Direction validation
This product option controls the validation of the primary direction of the route when creating TRADAS data.
It also specifies whether or not Traffic Interface Manager enforces the a rule-based validation check in the publish process
(when Traffic Interface Manager compiles a cross reference table of which count sites are on which traffic sections) that if
the street is two-way then it must be coded with a specific primary direction of north or east.
The code requires the following attribute fields to be available:
Version: 4.7
11
EXOR
 CS one way flow direction flag
 CS flow direction direction
 TS section direction
It also specifies whether or not Traffic Interface Manager enforces the rule that a count site can only be located on one
traffic section unless a stretch of dual carriageway is represented by two separate traffic sections (one in each direction) in
which case a count site can be on up to two traffic sections.
The Roadway Type attribute of the TS asset tells TM whether a section is part of a dual carriageway (and therefore
eligible to be one of two on which a count site can be located).
 Valid values: Y or N.
 Default value is Y
3.5.4
PUBLUSEJOB
Use DBMS_JOB for publish,
This product option specifies whether Traffic Interface Manager should use dbms_jobs for the publish process. It is
recommended that this option is set to Y so that the publish process is run using a dbms_job. This will allow the user to
monitor the status of the job from the browser.
 Default value is Y.
3.5.5
PUBSUSPEND
Suspend publish,
This product option specifies whether users will have the option of suspending the publish process once it has been
started.
 Default value is Y.
3.5.6
TRADMONINT
TRADAS monitoring time interval
This product option specifies the time interval which Traffic Interface Manager will wait to check for results from
TRADAS. The default setting is five minutes. This option is best modified by replacing the default interval of 5 specified
at the end of the formula with the minute interval you wish to have.
If this option is modified on a live TM installation then the TM dbms_job will have to be dropped then recreated for the
change to have an effect...
 Valid values: SQL statement.
 Default value is “sysdate + 1/(24*60*60*5)”.
3.5.7
WEBREFINT
Web page refresh interval
Version: 4.7
12
EXOR
This product option specifies how often (in seconds) the browser window will refresh when the publish process is
running.
 Valid values: number of seconds.
 Default value is “4”
3.5.8
DEBUGAUTON
Use autonomous debug
This product option specifies whether or not the system uses the autonomous debug function. This causes autonomous
transaction errors when used with Traffic Interface Manager
 Default value is “Y”
3.6
Start Traffic Interface Manager DBMS_JOB
The Traffic Interface Manager DBMS_JOB must be generated manually.
To start the DBMS_JOB run the following sql command in the Highways database:
exec tm3pub.create_tradas_monitor_job
This command creates the TM3PUB.CHECK_FOR_TRADAS_DATA DBMS_JOB
This should be done after the traffic statistic metadata has been set up.
The default intended interval for these jobs is sysdate + 1(24*60*60*5), which calculates to 5 times a second (more when
you consider Oracle only computes dates and times down to the second so it is actually just as fast as the job scheduler
can get to them).
Note: Zetting up the traffic statistics is described below in the chapter on Setting up Traffic Interface Manager
Metadata.
Version: 4.7
13
EXOR
SETTING UP TRAFFIC INTERFACE MANAGER METADATA
4
Setting up Traffic Interface Manager Metadata
Traffic Interface Manager requires a number of asset types to be defined within the Asset Manager metadata model.
These are types of traffic statistics and count sites and traffic sections that provide a mechanism to relate the traffic
statistics to the highway network.
This chapter covers the following topics:
 Traffic Interface Manager metadata setup sequence
 Metadata for count sites and traffic section
 Setting up factor groups
 Metadata for traffic statistic records
 Setting up GIS themes
4.1
Traffic Interface Manager Metadata Setup Sequence
The order in which Traffic Interface Manager metadata is set up is very important because many Traffic Interface
Manager functions are metadata drive, and some tables and procedures are created as part of the metadata setup process.
The following sequence should be followed:
 Install Traffic Interface Manager software
 Set TM product options
 Set up count site and traffic section asset metadata
 Set up factor groups
 Click on the Generate Change button
 Set up traffic statistic metadata (click on Import Tradas Metamodel button to set up the types, then add attributes)
 Select statistic asset types and date attributes
 Select statistic primary key attributes
 Click on Create Interface Tables button
 Start dbms_job
Version: 4.7
14
EXOR
4.2
Metadata for Count Sites and Traffic Sections
Metadata required for count sites and traffic sections are described here. Traffic Interface Manager makes use of a number
of specific data types within both Highways by Exor and TRADAS. Data can be exchanged between the two systems
because they both share the same metadata.
Traffic Interface Manager deals with two kinds of data: traffic statistic locations and traffic statistic records. Traffic
statistic locations are the places along the road network where traffic counts take place and for which traffic statistics are
calculated and reported. There are two kinds of traffic statistic location records within Traffic Interface Manager: count
sites and traffic sections.
4.2.1
Count site (CS) Metadata
A count site is a location where traffic is counted. It can be a collection of places (cluster in TRADAS terminology). It can
be for single carriageway or can be shared by two carriageways if the VALDIRN Traffic Interface Manager product
option is set to “Y”. An asset type with a type code CS must be set up to store count site locations and attributes.
Count site data in Traffic Interface Manager is automatically passed on to TRADAS. When Traffic Interface Manager is
present native TRADAS count site editing tools are disabled. Any count site information needed by TRADAS must
therefore be defined as CS attributes.
To set up CS asset type use the NM0410 Inventory Metamodel form. This is illustrated below.
First set up basic asset type information. The count site asset type code should be “CS”.
Figure 1 – Inventory Metamodel
Then add attribute field definitions. These must include a number of mandatory attributes discussed in the next section.
Version: 4.7
15
EXOR
Figure 2 - Attributes
Assign the TM_User role to the CS asset type, as well as any others assigned to all assets.
Figure 3 - Roles
4.2.1.1 Mandatory CS Attributes
If the VALDIRN Traffic Interface Manager product option is set to “Y” then there are three mandatory CS attributes (in
addition to the usual Asset Manager asset attributes). These are:
 A unique site ID
 A primary flow direction
 A one way flow flag
Version: 4.7
16
EXOR
IIT_SITE_NO
VARCHAR2(50)
NO NULLS
IIT_PRIMARY_DIRN
VARCHAR2(1)
DOMAIN TM_FLOW_DIRN
IIT_ONE_WAY_FLOW
VARCHAR2(1)
DOMAIN YES_NO.
4.2.1.2 Adding CS Attributes to a Working System
Attribute columns can be added to a CS asset at any time. The type of attribute that is added and other metadata changes
required to accommodate the change depend on two things:
 Whether the new attribute values are needed by TRADAS
 Whether the new attribute represents a factor group.
Any changes to the attribute values will be audited in the TM audit tables
If a new attribute is not needed by TRADAS and is not a factor group then it can simply be added like any other Asset
Manager asset attribute. The publish process will ignore the new attribute, and it will not be present in the TRADAS
interface tables.
If the new attribute is a factor group (which is therefore needed by TRADAS) the interface tables and factor group
packages and related objects will have to be regenerated by clicking the Generate Changes button on the Traffic Interface
Manager Metadata maintenance form (TM0001).
The publish process will place the factor group values into the TRADAS interface tables
4.2.2
Traffic Section (TS) Metadata
A traffic section is a section of road network with homogeneous traffic characteristics that are measured at at least one
count site. An Inventory Type with a type code ‘TS’ must be set up to store traffic sections if Traffic Interface Manager is
configured to use traffic sections. This is the case, and a TS asset type is required, if any of the following product options
are set to “Y”:
 TS_MAND
 VALDIRN
TS assets must be defined as Contiguous Inventory so that they cannot overlap and that only one TS asset can exist along
any part of the road network.
To set up TS asset type use the NM0410 Inventory Metamodel form.
Set up basic asset type information using the Types tab. The traffic section asset type code should be “TS”.
Version: 4.7
17
EXOR
Figure 4 – Inventory Metamodel
Add attribute field definitions using the Attributes tab. These must include a number of mandatory attributes discussed in
the next section.
Figure 5 - Attributes
Assign the TM_User role to the TS asset type, as well as any others assigned to all assets.
Version: 4.7
18
EXOR
Figure 6 - Roles
4.2.2.1 Mandatory TS Attributes
If the VALDIRN Traffic Interface Manager product option is set to “Y” then there are three mandatory TS attributes (in
addition to the usual Asset Manager asset attributes). These are:
 A unique site ID
 A primary flow direction
 A flag to indicate whether CS assets located on the section can also be located on another section
IIT_SECTION_ID
VARCHAR2(50)
IIT_SECTION_DIRN
VARCHAR2(1)
IIT_ROADTYPE
VARCHAR2(1)
NO NULLS
Version: 4.7
19
EXOR
4.3
Setting up Factor Groups
Factor group memberships are maintained as attributes of both count sites and traffic sections. Every count site and traffic
section record may have factor group values.
If the VALDIRN Product Option is set to “Y” Traffic Interface Manager will ensure cross item data integrity by requiring
the values of factor group attributes, as well as section direction, for count sites to be the same as those of traffic sections.
Any count site created along a traffic section will inherit its factor group memberships as derived attributes.
The administrator must select CS and TS attributes that are to be used for factor groups from the TM0001 Traffic
Interface Manager Metadata Maintenance form, using the Factor Group tab on the form.
For each factor group, users must provide the following metadata:
 Display sequence
 Factor group name
 Factor group description
 View column name for factor group attribute in CS asset type
 View column name for factor group attribute in TS asset type
Use the Factor Groups tab on the Traffic Manager Metadata Maintenance form (TM0001) to enter factor group records
and select the attributes in CS and TS records that hold factor group membership values.
Figure 7 – Factor Groups
4.3.1
Count Site and Traffic Section Direction Values
If the VALDIRN Traffic Interface Manager product option is set to “Y” then directional statistics for most count sites and
traffic sections are calculated in TRADAS based on the flow direction fields corresponding to PDIR and NDIR in
TRADAS that are populated in traffic section and count site inventory items. Directional statistics for traffic sections that
Version: 4.7
20
EXOR
share count sites are calculated in the same way by TRADAS and assigned to the appropriate traffic section using the
following logic.
This is only an issue for shared count sites. Where there is a one-to-one relationship between count sites and traffic
sections all statistics (directional and combined) for a traffic section will be assigned to the traffic section statistics records
for that section. It will not matter whether the primary direction values match.
Where two traffic sections share a count site each directional statistic will have to be assigned to one of the two sections.
Traffic Interface Manager (and therefore TRADAS) will know that two sections may share a site if are one-directional
(IIT_ROADTYPE = 2 for one-directional, not 1 for two-directional) It will then look to see if the site has the same CS
foreign key as another TS. Lookup values for the domain CS_ROAD_TYPE are shown below:
VALUE
MEANING
1
Traffic flows in both directions
2
Traffic only flows in one direction
Directional statistics for shared sites will be assigned using the following logic.
Statistics records can have DIR1 and DIR2 direction attributes. DIR1 values will be the same as the primary direction
value (IIT_SECTION_DIRN) DIR2 values will be the opposite.
Each of the two sections that share a site will have a different (and opposite) primary direction values (and therefore DIR1
and DIR2 values for its statistics). TRADAS will assign DIR1 directional statistics to the sectional statistics record for
which their DIR1 value is the same as the PDIR in various TRADAS tables.
If the DIR1 value doesn’t match either the PDIR or the NDIR then the directional flow statistics will not be published to
either traffic section. Instead a record will be written to an error log listing the section and count site ids and a warning
message provided to users.
Combined statistics will be published to both sections.
Version: 4.7
21
EXOR
4.4
4.4.1
Metadata for Traffic Statistic Records
Setting up Traffic Statistic Metadata
Traffic statistic record types are first defined in TRADAS in the form of a table called PDB_TM_METAMODEL_PIC.
The data in this is used to create the inventory metamodel and the statistics type metadata. The metadata for traffic
statistic records is imported by clicking on the “Import TRADAS Metamodel” button on the Traffic Interface Manager
Metadata Maintenance form (TM0001).
Note: The PDB_TM_METAMODEL_PIC table is described below in the section titled “Identifying TRADAS Data to
Publish”.
4.4.2
Traffic Statistic Publish Type
Traffic statistics records are divided into groups by publish type. These types reflect different summary periods supported
by TRADAS. Four types are supported:
 DAILY
 WEEKLY
 MONTHLY
 ANNUAL
Figure 8 – Input Details
After clicking on the button an Input Details form pops up for the user to enter the appropriate Admin Unit and start date
for traffic statistic record types.
Version: 4.7
22
EXOR
This function creates two inventory types for each traffic statistic record type—one normal one, with an “s” in its name,
and one temporary one, with a “z” instead of the “s”.
Any functions that process inventory information will change to take publish type as a parameter to decide what types to
process.
The generation of primary key values for statistic asset records is data driven. Following the import from TRADAS and
generation of the types, the administrator must choose a combination of attribute columns and connectors to make up the
key for each statistic type. This is done by selecting primary key attributes in the Statistics tab of the Traffic Interface
Manager Metadata Maintenance form (TM0001) shown below.
The most common primary key is the foreign key to the top level parent count site or traffic section asset (which is the ID
of this asset) and the statistic date field, connected by a hyphen.
Be sure to create views for each statistic asset type by clicking on the Create View button on the Inventory Metamodel
form after editing the asset attributes.
Figure 9 - Statistics
Select each statistic types in turn in the top block. Then, for each one, select the desired attributes that should be combined
to generate the primary key for records of that type. Also select the connector that you want to be placed between adjacent
attributes in the key.
A set of temporary statistics is generated as part of the publish process for evaluation purposes. These are exactly like the
permanent statistics records. The only difference is that they have a “z” in their name instead of an “s”.
4.4.2.1 Create Interface Tables
Once all statistic assets have been set up and their types, date attributes, and primary keys have been selected, click on the
Create Interface Tables button to generate interface tables for the publish process.
Version: 4.7
23
EXOR
4.5
Setting up GIS Themes
GIS themes must be set up for each traffic statistic type as well as for count sites and traffic sections so that these can all
be displayed on maps using Spatial Data Manager by Exor.
Note: See the Exor GIS Themes Setup document for instructions on how to set up GIS_THEMES).
The system will set up GIS themes for permanent statistic types which are created by the publish process.
This should be done by the system. Use the GIS Themes form to view existing settings.
Version: 4.7
24
EXOR
SETTING UP TRADAS
5
Setting up TRADAS
This section discusses TRADAS set up and configuration issues.
It addresses the following topics:
 Setting up TRADAS software
 Identifying statistics to publish
 Updating TRADAS count site data
5.1
Setting up TRADAS Software
Installation for TRADAS end of Traffic Interface Manager is done on the TRADAS server computer. Before you begin,
you must know the following information:
 The username/password@dbname of the TRADAS computer
 The information necessary to create a TNS entry for the highways computer
 The username/password of the TRADAS account on the highways computer
Installation consists of a number of steps:
 Create TNS entry to the highways computer
 Create the database link and synonyms
 Creating TM work tables
 Compiling the packages
 Configure DBMS_JOBS
5.1.1
Create TNS Entry to the Highways Computer
Create and test the TNS entry by connecting via SQL*Plus to the TRADAS user on the highways computer.
5.1.2
Create the Database Link and Synonyms
This step is accomplished by running the cr_syn.sql within SQL*Plus. This script will prompt you to enter the
username/password of the highways TRADAS user, the TNS alias name, and the dblink name. The first time this script is
run there will be errors on several DROP SYNONYM statements, which can be ignored. This script can be rerun as
needed.
IMPORTANT – Oracle introduced a “feature” in Oracle 8 that if the GLOBAL_NAME parameter in the init.ora file is
TRUE, the db link name must be the same as the full database name you are accessing (e.g.,
“RDBA.MRWA.WA.GOV.AU”). See metalink article 19367.1 for more information.
The database link can be checked by going to an SQL*Plus prompt and executing:
“select sysdate from dual@dblinkname;”
You should get a valid date returned. If you get an ORA-02085 error, the dblinkname is wrong and needs to be changed to
the database name in the error message.
The synonyms should be tested by performing the following command for each of the synonyms:
select count(*) from synonym;
Version: 4.7
25
EXOR
SETTING UP TRADAS
The following synonyms should be checked:
 TM_CS_AUDIT
 TM_PUBLISH_CS
 TM_PUBLISH_TS
 TM_PUBLISH_JOBS
 TM_PUBLISH_LINK
 TM_PUBLISH_LINK_ERRORS
The synonym NE_ID_SEQ can be check by the following sql:
select ne_id_seq.nextval from dual;
If a synonym fails, first check the database link using the above instructions and then try the same query as before, but
replace synonym with synonym@dblinkname. If that works, rerun the cr_syn.sql, if it doesn’t, either this user doesn’t
have the correct permission to access the tables in the highways database or the tables don’t exist at all.
5.1.3
Compile the TRADAS Packages
There are two packages that must be compiled using SQL*Plus. After logging on, run @publish and
@update_site_from_cs.sql. If the above steps are completed, the scripts should compile successfully. If they do not
compile, please contact Chaparral Systems.
5.1.4
Configure the DBMS_JOBS
DBMS_JOB entries are created by running the cr_job.sql. Before a DBMS_JOB will run, however, the
JOB_QUEUE_PROCESSES in the init.ora file must be set to 2 or greater.
You can test this step checking the last_date variable and making sure it changes every minute: select to_char(last_date,
‘MM/DD/YYYY HH24:MI’) from dba_jobs;. If the last_date doesn’t change or is NULL, increase the
JOB_QUEUE_PROCESSES variable in the init.ora file, restart the instance, and recheck.
Version: 4.7
26
EXOR
SETTING UP TRADAS
5.2
Identifying TRADAS Statistics to Publish
TRADAS statistics that are published to Traffic Interface Manager are identified in the PDB_TM_METAMODEL_PIC
table. This is used during system configuration to generate Traffic Interface Manager metadata, so it should be set up
early in the system configuration process.
The Traffic Interface Manager statistics metadata can also be configured manually, independently of the
PDB_TM_METAMODEL_PIC table. In this case make sure that the Traffic Interface Manager and TRADAS statistics
definitions match.
Essentially this table is used to select from the very large number of statistic types available in the TRADAS Public
Database, a smaller number of statistics that will be most valuable in the Highways database, and to define the Highways
asset types that will be used to store and query these statistics.
The PDB_TM_METAMODEL_PIC table contains the following attributes:
5.2.1
PTMP_KEY
NUMBER(10)
PTMP_PDB_VIEW
VARCHAR2(30)
PTMP_PDB_COL
VARCHAR2(30)
PTMP_PDB_DATATYPE
VARCHAR2(12)
PTMP_PDB_LENGTH
NUMBER(2)
PTMP_PDB_MINVALUE
NUMBER(10)
PTMP_PDB_MAXVALUE
NUMBER(10)
PTMP_ASSET_TYPE
VARCHAR2(4)
PTMP_IIT_COL
VARCHAR2(50)
PTMP_DESC
VARCHAR2(100)
PTMP_PDB_WHERE
VARCHAR2(50)
PTMP_PUBLISH_TYPE
VARCHAR2(10)
PTMP_ASSET_LOCALE
NUMBER(1)
PTMP_DATE_COL
DATE
PTMP_KEY
The PTMP_KEY field contains a uniqe ID.
5.2.2
PTMP_PDB_VIEW
The PTMP_PDB_VIEW contains the name of the view in the TRADAS Public Database that holds the statistics to be
published
5.2.3
PTMP_PDB_COL
The PTMP_PDB_COL contains the column in the TRADAS Public Database view (PTMP_PDB_VIEW) that holds the
statistic to be published
Version: 4.7
27
EXOR
SETTING UP TRADAS
5.2.4
PTMP_PDB_DATA_TYPE
The PTMP_PDB_DATA_TYPE field contains the Oracle database object type for the TRADAS Public Database column
5.2.5
PTMP_PDB_LENGTH
The PTMP_PDB_LENGTH field contains the length of the TRADAS Public Database column
5.2.6
PTMP_PDB_MINVALUE
The PTMP_PDB_MINVALUE field contains the minimum value that can be put into the TRADAS Public Database
column.
5.2.7
PTMP_PDB_MAXVALUE
The PTMP_PDB_MAXVALUE field contains the maximum value that can be put into the TRADAS Public Database
column.
5.2.8
PTMP_ASSET_TYPE
The PTMP_ASSET_TYPE field contains the Exor Asset type code for the published statistic
5.2.9
PTMP_IIT_COL
The PTMP_IIT_COL field contains the Exor Asset attribute view column (IIT_COL) value for the published statistic
5.2.10 PTMP_DESC
The TTMP_DESC field contains the Exor Asset attribute description field value for the published statistic
5.2.11 PTMP_PDB_WHERE
ThPTMP_PDB_WHERE field contains a where clause for selecting statistics records from the TRADAS Public Database
5.2.12 PTMP_PUBLISH_TYPE
The PTMP_PUBLISH_TYPE field must contain the code for the type of publish. Valid values are: ‘DAILY’,
‘MONTHLY’, and ‘ANNUAL’. This value goes into a Traffic Interface Manager table called
TM_STATISTICS_TYPES.
5.2.13 PTMP_ASSET_LOCALE
The PTMP_ASSET_LOCALE field indicates whether the statistic applies to a count site or traffic section. It contains
number 1if the statistic is for a site or a number 2 if it is for a section.
Version: 4.7
28
EXOR
SETTING UP TRADAS
5.2.14 PTMP_DATE_COL
The PTMP_DATE_COL field must contain the Exor asset attribute field that contains the statistic date.
5.3
Updating TRADAS Count Site Data
Manual count site updating functionality in TRADAS should be disabled to avoid inconsistency between edits made in the
two systems.
Changes to count site items in the Highways by Exor database are published in a count site audit table called
TM_CS_AUDIT. This table contains all changed attribute fields as they are before and after the change (except location
information) as well as information about when the edit was made. The audit table includes an attribute called SITE_NO
which corresponds to the unique count site identifier in TRADAS.
TRADAS polls the audit table at a regular interval that is set within TRADAS by a DBMS_Job called
update_site_from_cs.go. The default frequency for this update is every minute. It can be changed by TRADAS customer
support if needed.
Version: 4.7
29
EXOR
PUBLISHING TRAFFIC STATISTICS
6
Publishing Traffic Statistics
6.1
Preparing TRADAS for the Publish Process
The publish process calculates traffic statistics for traffic sections and publishes statistics for both count sites and traffic
statistics to the Highways by Exor database. The publish process reads count site statistics from the TRADAS Public
Database, so this should be updated before the publish process is started.
To do this:

Make sure that Phases 1 through 5 of the Annual process have been run for the year for which ANNUAL
statistics are to be published before the publish process is started.
 Ensure that the Public Database has been updated. This happens every night at midnight, or it can be done
manually, using the fdm_update procedure. This is typically invoked by double-clicking an icon on the
TRADAS server's desktop.
We recommend that users do not update TRADAS data while the publish process is running. For example, do not submit
raw data files to the system or run processes like the Monthly submittal. This will speed up the publish process and avoid
any conflicts arising if by the Public Database being updated during the publish process.
6.2
How the Publish Process Works
The diagram below illustrates how the publish process works.
Version: 4.7
30
EXOR
PUBLISHING TRAFFIC STATISTICS
Begin
Start publish
List count sites, traffic sections,and
which sites are along which sections
at effective date
Do factor group
values and
directions match?
TM_PUBLISH_CS
TM_PUBLISH_TS
TM_PUBLISH_LINK
No
Yes
Display site and section
numbers where factor
group values and
directions do not match
Stop publish
Read tables into TRADAS
TM_PUBLISH_LINK_
ERRORS
List mismatches between TRADAS
and Highways records
Display sites that do not
match
Read count site statistics from
TRADAS Public Database
Calculate traffic section statistics
Write traffic statistics to tables
One table per statistic
type, generated from
metadata
Create temporary inventory items for
statistics
One table per statistic
type, generated from
metadata
No
Accept
statistics?
Stop
publish
Yes
Commit statistics
Create annual inventory items for
statistics
Clean up temporary
publish tables
One new statistic
attribute of each type
for the time period
End
Figure 10 – Publish Process Works
Version: 4.7
31
EXOR
TROUBLESHOOTING THE PUBLISH PROCESS
7
Troubleshooting the Publish Process
This chapter provides information for trouble-shooting the Traffic Interface Manager publish process.
7.1
Troubleshooting TRADAS Traffic Interface Manager Components
Note:
1.
2.
3.
4.
Nothing happens when sites are updated from highways or the publish process is initiated.
Check whether Captain Bligh is running
Check to see whether the Captain Bligh process is running on the TRADAS server. If not, restart it.
Check temporary TRADAS publish tables
There is a table called TM_TMP_CS in the TRADAS database that is used during the process and cleared at the
end of the publish. If a process crashes for some reason, that table may incorrectly contain records, indicating to
TRADAS that the process continues to run and thereby disallow any other process from starting.
To clear this condition, from SQL*Plus type:
 delete tm_tmp_cs;
 commit;
Note: Site changes in highways are not propagating correctly to TRADAS.
Check the tm_site_errors table in the TRADAS database for more information. The following lists the possible errors:
 There should only be one TRADAS site <site>.
This error occurs when there are duplicate sites within the TRADAS database. Run the TRADAS sql expiredupsites.sql to
relieve this problem.
7.2
Note:
7.3
Messages
For a list of Traffic Interface Manager publish process messages and explanations see Chapter 6:
Troubleshooting in the Traffic Interface Manager User Guide
Job Control and Status Codes
Traffic Interface Manager writes job control codes for the TCO_CONTROL field of the TM_PUBLISH_CONTROL
table. The four possible codes are listed below:
0
ok
1
suspend publish signaled
2
publish suspended
3
stop publish signaled
The publish process will not run unless this code is set to 0. If the publish process is aborted abnormally it may be
necessary to reset the code value manually.
Version: 4.7
32
EXOR
Traffic Interface Manager status is also shown in the TM_RUNNING table in the TRADAS database. The PROCESS
column in this table can have three values:
 null
 PUBLISH
 COUNT_SITE_UPDATE
Null indicates that no TRADAS processes are currently being run. PUBLISH indicates that the publish process is being
run. COUNT_SITE_UPDATE indicates that the count site update process is being run.
7.4
Monitoring the Publish Process
The publish process is governed by two tables in the Highways database:
 TM_PUBLISH_CONTROL
 TM_PUBLISH_JOBS
Each has a row for each publish job which is written to the TCO_JOB_ID column. The TCO_CONTROL column in the
TM_PUBLISH_CONTROL table should be 0 when a publish job is started and also at the end of successful publish. If it
is 3 then a stop has been signaled.
The TPJ_STATUS column value in the TM_PUBLISH_JOBS table indicates the status of a publish job. Values and their
meanings are listed below:
Value
Meaning
0
There are no active jobs
1
Pre-publish data population in progress...
2
Pre-publish data population completed with errors.
3
Deleting temporary statistics...
4
Pre-publish complete and data ready for TRADAS.
5
Pre-publish suspended.
6
Stopping publish job...
10
TRADAS creating site statistics
11
TRADAS pre-publish failed.
12
TRADAS temporary statistics generated.
14
Reading TRADAS temporary statistics
15
TRADAS temporary statistics read failed
16
TRADAS temporary statistics read complete.
20
Temporary statistics transferring to main database.
21
Temp stats transfer complete, finishing...
22
Transfer of temporary statistics failed
30
Publish job complete.
Traffic Interface Manager status is also shown in the TM_RUNNING table in the TRADAS database. The PROCESS
column in this table can have three values:
Version: 4.7
33
EXOR
 null
 PUBLISH
 COUNT_SITE_UPDATE
Null indicates that no TRADAS processes are currently being run. PUBLISH indicates that the publish process is being
run. COUNT_SITE_UPDATE indicates that the count site update process is being run.
7.4.1
Valid Publish Job Status Code Transitions
Only the following TPJ_STATUS code transitions are allowed:
Version: 4.7
34
EXOR
7.5
Reset the System
If the publish process becomes hung up before it ends you can manually stop the process and reset the system. Follow the
instructions in the next two sections to carry out these steps in the order described:
 Manually stop the publish process
 Manually reset the publish process
7.5.1
Manually Stop the Publish Process
When you click on the Stop Publish button in the Traffic Interface Manager publish statistics form, the TCO_CONTROL
value in the Highways TM_PUBLISH_CONTROL table is set to “3”. When the message to stop gets through to the
system, this is set back to “0” and the TPJ_STATUS value in the Highways TM_PUBLISH_JOBS table is set to “6”
while various clean-up functions are performed.
Do this before the TRADAS publish process starts (i.e., before the “TRADAS creating site statistics” message appears on
the publish form).
The process can be also stopped and reset manually by following the procedure below. This is only necessary if you want
to stop the process while the TRADAS publish process is active, i.e., the TPJ_STATUS code =10 and the message on the
Traffic Interface Manager publish form is: “TRADAS creating annual site statistics”.
One reason for doing this is to interrupt and reset the publish process if something seems to be wrong on the TRADAS
side.
7.5.2
Manually reset the publish process
Resetting the database when the publish process has been stopped involves four steps:
 Physically stop the TRADAS publish package
 Ensure TCO_CONTROL = 0
 Change TPJ_STATUS to “11”
 Remove any records from TM_TMP_CS
 Clear out TIM publish tables
You will have to log in to the Highways database and the TRADAS database as owner to carry out these steps.
7.5.2.1 Physically stop the TRADAS publish package
Stop the instance or bounce the TRADAS database
7.5.2.2 Ensure TCO_CONTROL = 0
If the “Stop Publish” button on the Traffic Interface Manager publish form (TMWEB0010) has been pressed then the
value of the TCO_CONTROL field in the Highways TM_PUBLISH_CONTROL table will be “3”. Use a utility like
SQL+ or TOAD to manually change it to “0”. If it is already “0”, leave it alone.
7.5.2.3 Change TPJ_STATUS to “11”
The TPJ_STATUS field in the Highways TM_PUBLISH_JOBS table will be “10” while TRADAS generates traffic
statistics for the publish. Use a utility like SQL+ or TOAD to manually change it to “11”, which indicates that the
TRADAS publish process has not completed properly.
Version: 4.7
35
EXOR
7.5.2.4 Remove any records from TM_TMP_CS in the TRADAS database
During the publish process TRADAS TM_TMP_CS table holds a copy of the records in the Highways database
TM_PUBLISH_JOBS table. If the publish process is interrupted then these records may remain the table.
If they do then use a utility like SQL+ or TOAD to remove them with the following SQL command:
truncate tm_tmp_cs;
commit;
7.5.2.5 Clear out Traffic Interface Manager publish tables in the Highways database
Records will exist in Highways publish tables that must be cleared before another publish. Using TOAD, disable the
foreign keys linking the tables:
TM_PUBLISH_CONTROL
TCO_TPJ_FK
TM_PUBLISH_CS
TPC_TPJ_FK
TM_PUBLISH_TS
TPT_TPJ_FK
TM_PUBLISH_LINK
TPL_TPC_FK
TPL_TPT_FK
Run the script truncate_publish_tables.sql found in <exor_base>\tm3\pbclr folder. This will clear out publish tables:
TM_PUBLISH_LINKS_ERRORS
TM_PUBLISH_LINK
TM_PUBLISH_CS
TM_PUBLISH_TS
TM_PUBLISH_JOB_HISTORY
TM_PUBLISH_CONTROL
TM_PUBLISH_JOBS
The content of truncate_publish_tables.sql is shown below:
alter table tm_publish_control disable constraint tco_tpj_fk cascade
/
alter table tm_publish_cs disable constraint tpc_tpj_fk cascade
/
alter table tm_publish_ts disable constraint tpt_tpj_fk cascade
/
truncate table tm_publish_link_errors
/
truncate table tm_publish_link
/
truncate table tm_publish_cs
/
truncate table tm_publish_ts
/
truncate table tm_publish_job_history
/
Version: 4.7
36
EXOR
truncate table tm_publish_control
/
truncate table tm_publish_jobs
/
alter table tm_publish_control enable constraint tco_tpj_fk
/
alter table tm_publish_cs enable constraint tpc_tpj_fk
/
alter table tm_publish_ts enable constraint tpt_tpj_fk
/
commit
/
Using TOAD, enable the foreign keys in the four tables (above), and commit the changes.
Version: 4.7
37

EXOR Traffic Interface Manager Admin Guide

Transcription

Similar documents

MEET ME NOW

March 26, 2015 - St. Charles Herald Guide

wall street 101 - Bentley University

Silego Technology - Globalpress Electronics Summit

SUMMER 2016 RELEASES

Wasted Whiskey is Buffalo based country music band that

press release

A585 Windy Harbour to Skippool Improvement

Douglas Commons Douglas Commons