Configuring Responder
Responder Overview
Version: 10.2.1c and 10.2.1c SP3 |
Responder is a GIS hosted, distributed Outage Management System (OMS). Responder focuses on providing the most valuable information to the right people for storm restoration as well as during daily operations, allowing them to make informed decisions. Its user-friendly interface and intuitive menus allow dispatchers to perform their tasks quickly and efficiently, thus restoring power as fast as possible and making concise choices on where to dispatch crews for maximum impact based on both geographical and tabular data.
 |
Editing XML Files: The Responder configuration requires you to edit several XML configuration files. DO NOT edit these XML files using a word processing program such as WordPad or Microsoft Word as it may corrupt your configuration file. To ensure the integrity of your configuration files, use an XML editing application (e.g., XML Spy) or a text editor (e.g., Notepad). |
|
This diagram shows the various Responder configuration files and to which Responder component they should point. |
This diagram depicts the various Responder components and how they interact. |
|
Use these steps to set up a new Responder implementation. This section includes a Before You Begin topic as well as data preparation and configuration. |
Use these steps to upgrade an existing Responder implementation to a new version. This section also shows you how to remove a previous version of OASyS PubSub. |
|
This section outlines tasks that may be performed periodically to maintain data integrity. |
This section describes how to configure optional functionality such as clustering and auto reconnect. All functionality in this section will not be available unless it is configured as described. |
|
This section addresses the resolutions to potential issues an implementer may encounter while configuring Responder. |
This section discusses how to set up and use the TroubleMaker application. |
|
Installing any part of Responder onto an Active Directory Domain Controller machine is neither recommended nor supported. |
Backing Up Layout Files: Responder uses several *.layout files for customization. It is a good idea to back up these *.layout files before you begin configuration. When backing up, be sure to change the .layout extension. Responder looks for files that end with .layout. This includes your backup file if you haven't changed the name (e.g., Regions.custom.layout can become Regions.custom.layout.backup).
Licensing: When configuring Responder, you must have access to an ArcFM license that allows you to assign model names to the geodatabase. If you have access to only a Responder or ArcFM Viewer license, you will not be able to edit model names or view the ArcFM Solution Configuration Guide in ArcCatalog.
This product includes software developed by the Apache Software Foundation.
