Latest Contributions by EricIronside

These days, the preferred method for monitoring a GeoEvent Server in a production system is the ArcGIS Monitor. But sometimes you want to just see/monitor the local system directly within GeoEvent to quickly evaluate how the system is performing (or alert you if it isn't performing well).  Below are instructions for deploying an input connector that will collect some basic information from your system and output it to a csv file.  You are free to modify the configuration once imported to write the data to a geodatabase and/or alert when certain parameters exceed certain tolerances. Import the System Info Transport Unzip the attached zip file below to a temporary location. You will deploy the new System Info Transport to your GeoEvent server. Method 1: Copy to the deploy folder Copy the .jar file from the temporary location into your GeoEvent Deploy directory. On Windows the default location for the deploy directory is: c:\Program Files\arcgis\server\geoevent\deploy\ ). Method 2: Import the .jar file using GeoEvent Manager In GeoEvent Manager, navigate to Site > Components > Transports and press the Add Local Transport button. Press the Choose Files button, browse to the temporary location, select the .jar file, press Open, then press the Add button. Once the System Info Transport is deployed it will show up in your list of inbound transports within GeoEvent Manager on the Site > Components > Transports page (you may have to refresh the page). Import the configuration In GeoEvent Manager navigate to Site > GeoEvent > Configuration Store and press the Import Configuration button. Press the Choose File button, browse to the location of the GeoEventConfig SystemInfo.xml file, press the Open button, then press the Next button. Select Import Configuration and press the Import button. This will import the System Info Connector, GeoEvent Definition, Input, Output, and Geoevent Service for you. Explore the connector Navigate to Site > GeoEvent >  Connectors   The connector utilizes the System Info Transport, which generates information in generic JSON format. The adapter is the Generic JSON Adapter. The following fields are hidden from the user since they are not used: Expected Date Format, Construct Geometry from Fields, X/Y/Z Geometry field, Default Spatial Reference, Learning Mode, As GeoJSON, and JSON Object Name. Note that the JSON Object Name is first default hard coded to ‘OperatingSystemInformation’. The remaining fields can be left in the Shown Properties area. You may wish to modify the Update Interval, since the default value (1 second) may be too frequent for long term monitoring. Explore the GeoEvent Definition A default system-info-in GeoEvent Definition is supplied in the configuration with some basic parameters. You may wish to have the input re-generate a new GeoEvent Definition for you just to be sure that the properties reported on your system are the same. To do this, follow the steps below: Rename the system-info-in GeoEvent definition to something like system-into-in-orignal. Navigate to Services > Inputs > system-info and make the following change and save the input: Create GeoEvent Definition: Yes GeoEvent Definition Name (New): system-info-in-auto Run the input until at least one event is received, then turn the input off. Navigate to Site > GeoEvent > GeoEvent Definitions and make a copy of the site-info-in-auto GeoEvent Definition. Name the copy: site-info-in Save the copy Navigate back to Services > Inputs > system-info and make the following change and save the input: Create GeoEvent Definition: No GeoEvent Definition Name (Existing): system-info-in At this point you can delete the system-info-in-auto and system-info-in-original   GeoEvent Definitions, since they are no longer used. Explore the GeoEvent Service The GeoEvent Service system-info using the system-info input to generate a system-info-in event every 60 seconds. These events are written directly to an output that writes the events to a csv file in the GeoEvent Backup folder. By default this folder (on Windows) is located: C:\ProgramData\Esri\GeoEvent\systeminfo\ These csv files will record the status of your server over time and can be easily manipulated in Excel to create graphs of the historical system resources.  ... View more

With the 2020 Esri UC coming up next week I wanted to highlight what Esri and the larger GIS community are doing this year to promote Diversity, Equity & Racial Justice. I believe that everyone should step up and participate in these activities.    Click the links below to see what is going on and how you can get involved: Diversity-Equity-Inclusion-Racial-Justice-at-the-esri-UC2020 Racial Equity & Social Justice SIG Thursday, July 16 @ 9:15 AM PT  GIS for Equity & Social Justice SIG Thursday, July 16 @ 11:45 AM PT  https://userconference2020.schedule.esri.com/schedule/1335296033Women and GIS SIG Thursday, July 16 @ 1 PM PT ... View more

With the 2020 Esri UC coming up next week I wanted to highlight the ability to schedule appointments with experts to get your questions answered, your designs reviewed, or whatever it is that you feel may need a review by an expert.   Click the link below to schedule your appointment today: UC/Experience/ArcGIS-Appointments ... View more

When writing a custom component for GeoEvent using the GeoEvent SDK, it is sometimes helpful to cache some information to the file system. This information could be a cache of the most recent data or configuration properties. This blog shows you how to allocate a folder within the GeoEvent file structure that will allow you create files and store data that will persist through GeoEvent Server restarts. Step 1: OSGI Blueprint Configuration The first step is to modify the config.xml file under your src/main/resources/OSGI-INF/blueprint/ folder.  You need to add the following property to your <bean>: <property name="dataFolder" value="./data/yourfolder" /> For example: <bean id="myTransportServiceBean" class="com.esri.geoevent.transport.example.MyTransportService" activation="eager"> <property name="bundleContext" ref="blueprintBundleContext" /> <property name="dataFolder" value="./data/mytransport" /> </bean> The base directory is the install directory for GeoEvent Server (default on Windows is c:\Program Files\arcgis\server\geoevent\ ). Within the GeoEvent Server install folder there are two directories that are recommended for use: ./data/: The data directory is a file cache of information such as OSGI bundles, logs, and other temporary files. The files in this folder are used for caching the state of GeoEvent Server between restarts.  If you are storing a cache of your custom component's data or configuration information, this is an ideal location. ./assets/: The assets folder is a place where you can store information that will be available on the GeoEvent Server Manager's web server.  You can use this location to store any information that may potentially be accessed via a browser. This could be configuration information or a status page for your custom component.  Items in this folder can be accessed using the following URL: https://yourServerName:6143/geoevent/assets/ Step 2: Add a setDataFolder() method to your Service After you make the config.xml file change above, OSGI will inject a folder location into your service bean.  Within your Service Java class, you need to add a setter method to allow the framework to inject this folder object.  Here's an example transport Service class: public class MyTransportService extends TransportServiceBase { protected static File dataFolder; public MyTransportService() { definition = new XmlTransportDefinition(getResourceAsStream("geotab-transport-definition.xml")); } public void setDataFolder(File inDataFolder) { dataFolder = inDataFolder; if (!dataFolder.exists()) { dataFolder.mkdirs(); } } @Override public Transport createTransport() throws ComponentException { return new MyTransport(definition, dataFolder); } } Step 3: Use the folder After the above changes, your custom component will have access to a file folder location that can be used to store files.  As mentioned above, these files can contain configuration information, cached data, status information, or whatever you like. ... View more