Overview of the Roadway Characteristics Editor deployment guide
Getting your organization's event and route data into the Roadway Characteristics Editor (RCE) is straightforward. Follow the steps below to deploy your application in a secure and stable manner.
It is strongly recommended that you follow the steps in the order outlined below.
- InstallEsri Roads and Highways for Server
- Install a web server.
You can install a web server such as Microsoft Internet Information Services (IIS).
- Create a map document (MXD) with the appropriate routes and event layers using ArcGIS for Desktop and Esri Roads and Highways for Desktop.
- Publish the map document with ArcGIS for Server and enable the Roads and Highways Server "Linear Referencing" capability.
- Author a web map that includes the map service created in the previous step and the appropriate basemaps.
- Publish geoprocessing tools that will help maintain the integrity of event data when edited in Roadway Characteristics Editor.
- Using Windows Explorer, navigate to and copy the contents of $INSTALL_DIR$\Server\Web\RoadwayCharacteristics into the web folder of the web server.
For example, in IIS, the web folder may be located at C:\inetpub\wwwroot\RoadwayCharacteristics.Note:
The actual location of the IIS wwwroot directory could differ on your server machine. Use the IIS Management Console to get the location of the IIS wwwroot directory.
- Open the configuration (config.json) file within the RoadwayCharacteristics web folder and modify it to use the web map and geoprocessing services created from previous steps. Optionally, you can choose to change some default administrative settings like user authentication, map selection symbology and attribute sets while modifying the configuration file.
- Optionally enable security on ArcGIS Server to secure the map services being used within the Roadway Characteristics Editor web application.
Event IDs when adding or editing events
The Roadway Characteristics Editor requires an Event ID column in each of the event layers it is configured to edit. When new events are created by the Roadway Characteristics Editor, an Event ID must be provided for each record. The RCE can generate and provide Event IDs if the Event ID column is a string and greater than 32 characters in length. It will generate a Globally Unique ID (GUID) as a string and use that.
If the Event ID column is not a string greater than 32 characters, then the application will not specify an Event ID. If the database is not configured to generate a value, a null value will be stored. The user can provide an Event ID by placing this column in the attribute set used for the edit and provide a value, but this approach is not recommended as the user would need to provide an Event ID for each and every record, and the value must be unique.
If a null value is stored for an Event ID, the RCE will not support editing the record.