Skip navigation
All Places > Implementing ArcGIS > Blog
1 2 3 Previous Next

Implementing ArcGIS

70 posts

Here is the tenth of my twelve posts as a GovLoop Featured Contributor. This one discusses how GIS can be used as an effective Civic Engagement tool:

 

https://www.govloop.com/community/blog/gis-civic-engagement-tool/ 

Here is the ninth of my twelve posts as a GovLoop Featured Contributor. This one discusses how the Emergency Management industry provides a great example of the potential of GIS:

 

https://www.govloop.com/community/blog/emergency-management-provides-great-example-potential-gis/ 

Here is the eighth of my twelve posts as a GovLoop Featured Contributor. This one discusses the importance of a business plan for your GIS:

 

https://www.govloop.com/community/blog/time-talk-business-gis/ 

Here is the seventh of my twelve posts as a GovLoop Featured Contributor. This one discusses Best Practices:

 

https://www.govloop.com/community/blog/roadmap-success-best-practices/ 

 

Here is the sixth of my twelve posts as a GovLoop Featured Contributor. This one discusses how the Internet of Things (IoT) really requires integration with an enterprise GIS:

 

https://www.govloop.com/community/blog/iot-really-geoiot/ 

Here is the fifth of my twelve posts as a GovLoop Featured Contributor.  This one discusses when to write code and when not to:

 

https://www.govloop.com/community/blog/code-not-code-question/ 

When it comes to technology companies, product renaming and refocus is often inevitable. This recently occurred with Citrix as they have moved away from the "Xen" prefix and have simplified their product portfolio naming to make them easier to understand. For example, the new name for XenApp is "Citrix Virtual Apps" while XenDesktop is now "Citrix Virtual Desktops". These are the two primary products from Citrix that are used to deploy ArcGIS Desktop and ArcGIS Pro as virtualized applications. At the same time, Citrix is changing the associated product versioning and moving to a year and month format, for example:

 

      YYMM = Year and month when the product or component released. For example, a release in August 2018 appears       as 1808.

 

Citrix recently released the latest version of Citrix Virtual Apps and Desktops utilizing these changes and the current release is "Citrix Virtual Apps and Desktops 7 1808.2". This means that XenApp/XenDesktop 7.18 was the last release of the 7.x releases and the new version of "Citrix Virtual Apps" appears to be what XenApp 7.19 would have been and not a major upgrade, though Citrix is constantly evolving their products.

 

Though the naming changes are helpful for understanding product purpose, I don't anticipate much of an impact from these changes at a technical level. Over the last few years Esri has been certifying multiple Citrix releases and the most recent "certified" Citrix release for ArcGIS is XenApp/XenDesktop 7.17. It is likely that the new "Citrix Virtual Apps and Desktops" release, or a subsequent release, will be certified with the next major ArcGIS release so look for updates on the associated ArcGIS system requirements pages.

While at a client site installing and configuring ArcGIS Monitor, I needed to set up the ArcGIS Monitor Reporting Server with the client’s SSL Domain Certificate for the server so that no security error would be thrown when accessed. I was given the certificate in the PFX format (binary format for storing the server certificate, intermediate certificates, and the private key) common to Windows and readily imported by IIS. ArcGIS Monitor does not use IIS and requires that the Certificate and Private key be in separate files and in PEM format (Base64 encoded ASCII files).

 

Here are the steps I used to move from the single PFX file to the two PEM files required by ArcGIS Monitor Server.

 

  1. Download/Install OpenSSL software on an available workstation (For information on OpenSSL please visit: www.openssl.org)
  2. Open a command window and navigate to the PFX file location
  3. Extract the Public/Private key-pair 
  4. Extract the Certificate 
  5. Get the Private Key from the key-pair 
  6. The private key needs to be converted to pkcs8 format ***Copy the output and save it as sample_private_pkcs8.pem***
  7. Copy the sample_private_pkcs8.pem and sample_cert.pem files to the <Installation location>\ArcGIS Monitor\Server\ssl directory on the ArcGIS Monitor Report Server.
  8. Start ArcGIS Monitor Administrator - the Connections view appears.
  9. Click the File menu and click Open - the Open File dialog box appears.
  10. Browse to the <Installation location>\ArcGIS Monitor\Server\settings directory on the machine where ArcGIS Monitor Server is installed, click config.db, and click Open.
  11. Click Server on the main menu - the Server configuration pane appears. 
  12. Click the Private Key browse button - browse to and choose the sample_private_pkcs8.pem file and click Open.
  13. Click the Public Key browse button - browse to and choose the sample_cert.pem file and click Open. 
  14. Click the File menu and click Save to save your changes.
  15. Click the File menu and click Close to return to the Connections view.
  16. Right-click the ArcGIS Monitor Server service in the Windows Services manager and click Restart.
  17. The result is a secure connection to the ArcGIS Monitor Report Server 

Here is the fourth of my twelve posts as a GovLoop Featured Contributor.  This one highlights the work at the California Governor's Office of Emergency Services:

 

https://www.govloop.com/community/blog/real-digital-transformation-action-gis/ 

Here is the third of my twelve posts as a GovLoop Featured Contributor:

 

https://www.govloop.com/community/blog/time-actionable-open-data/ 

 

opendata

Here is the second of my twelve posts as a GovLoop Featured Contributor:

 

https://www.govloop.com/community/blog/rebranding-gis-to-better-understand-its-power/ 

For the next twelve weeks, I am a GovLoop featured contributor. Please check out my first post:

 

https://www.govloop.com/community/blog/moving-beyond-data-driven-analytics-driven/ 

Every organization strives to keep its systems running smoothly, but for some, that objective is mission critical.

Learn about the technical assistance level that aligns with your mission critical needs.  This is accomplished through assigned Technical Account Managers, 1-hour initial response to support requests, and 24/7/365 support.  No matter what your GIS needs may be Premium Support is designed to provide next level support for organizations of all sizes and industry.

 

Perhaps you’re not sure if Premium Support is right for your organization.  We can review your support history and help you better understand if a higher-level support would unlock your organizations potential. 

 

Using the link below you can learn more about the program and submit your request for additional information at the bottom.

 

https://support.esri.com/en/other-resources/supportservices#premium/usadomestic

Maximize your success in ArcGIS platform adoption by using a prioritization approach that balances business benefits with challenges, so you can prioritize high‐value, low‐effort activities. Read more about this concept, along with 17 additional best practices in our document Architecting the ArcGIS Platform:  Best Practices at this link: https://go.esri.com/bp

For many of our customers, installation and implementation of ArcGIS Monitor is a straightforward and quick process. Once the minimum requirements are met, most Monitor installations flow smoothly.

 

However, when advanced firewall and security practices are in place, these installation and configuration of ArcGIS Monitor can be much more complicated. For optimal success in highly secure environments, ask IT support staff to join in installation activities.

 

When the ArcGIS Monitor can’t quickly make a connection with other systems in the Enterprise ask IT to monitor the network traffic and see if any internal ports are blocking traffic. This may be an iterative process as you install the software, but without System and Process collectors, ArcGIS Monitor can't fully measure ArcGIS Enterprise Health. 

 

Onsite recently, in addition to opening ports 6443 and 7443 for ArcGIS Server and Portal connections, we had to request permission for ArcGIS Monitor to operate on ports 135, 49153 and 49154 on the ArcGIS Server, Portal and SQL machines in the deployment. Once these ports were opened, we could begin collecting on Memory, Network and Processing utilization. 

 

Collaboration between GIS Admins and IT is crucial for understanding security rules and limitations when implementing a product like ArcGIS Monitor.