Configuring the Travel Times Plugin connection - Travel Times 12.4

Before you can use the Travel Times Plugin, you must configure the plugin connection.

1. From the Config Tool homepage, open the Plugins task.
2. In the Plugins task, select the plugin role from the entity browser and click the Travel time properties tab.
3. In Primary engine settings section, configure the following:

   Service url

   URL for the Travel Times Engine.

   Username

   Username to access the Travel Times Engine.

   Password

   Password to access the Travel Times Engine.

   Admin username

   Username to access the Travel Times Engine as an administrator.

   Admin password

   Password to access the Travel Times Engine as an administrator.

   Client ID

   Client ID used to give access to the API. This is set up in the Travel Times Engine.

   Token

   Token used to give access to the API. This is set up in the Travel Times Engine.

   NOTE: The Client ID and Token work together to give access to the API.

   Authentication method

   Authentication method for the Travel Times Plugin

   Relay only mode

   Feature is used when the plugin is only sending data to the engine and not receiving any data.

4. In Timing and inventory settings section, configure the following:

   Select entities

   Select which traffic networks you want to monitor.

   Tip: The entities you select here are populated in the Area view task. In the Inventory configuration editor window:

   • Double-click the inventories you want to add.
   • Choose to add nodes, traffic routes, or entire traffic networks.

   To delete entities, navigate to the Area view task.

   Background refresh

   Time intervals of when the plugin synchronizes with the engine.

   Status update

   Time interval for each engine update.

   First warning

   Raises an event for when a traffic route, traffic link, or node has stayed in the same state.

   Second warning

   Raises an event for when a traffic route, traffic link, or node has stayed in the same state.

   NOTE: The second warning will occur after the first warning.

   Database history persistence

   How long the user wants to keep the traffic route, traffic link, and node states in the database and cache.

5. In the Proxy settings section, configure the following:

   Web proxy hostname/IP

   If using a web proxy to get to the Travel Times Engine enter the hostname or IP here.

   Web proxy port

   If using a web proxy to get to the Travel Times Engine, enter the port here.

6. (Optional) To map a Security Center event to events in the Travel Times Engine, configure the following:
   NOTE: Alarms are automatically generated for these events.

   Node failure event

   Used to create an event in Security Center which will be triggered when a node failure event occurs in the Travel Times Engine.

   NOTE: Reasons as to why the detector failed are in the Travel Times Engine.

   Node low battery event

   Used to create an event in Security Center which will be triggered when a low battery event occurs in the Travel Times Engine.

7. Click Apply.