Latest Contributions by GillPaterson

Thanks so much for posting this example. ... View more

Hi Davin, I am just starting to research this as well. Did you make any progress? ... View more

After installing the 10.8.1 log4j patch for datastore I haven't seen it as often. I think I got it once after the DataStore servers were restarted, but it then seemed to be fine after that. So my thinking at the moment is that a restart of either the service or machine will help. I haven't been able to test to say exactly that it will help, but just what I noticed after other actions. And the validation still shows, so also thinking possibly that this might be ok/normal. "datastore.layer.extent.updated": false   ... View more

Hi Ben, I am seeing the same issue now with 10.8.1 and I was just wondering if you found anything to fix it. The only thing I can find is to uninstall and re-install which I am not really wanting to do. ... View more

Yes, definitely, not just for GeoEvent but also improved performance for the hosting ArcGIS Server too. We have whitelisted all ArcGIS related folders from the antivirus app. An older article about which folders to exclude from the anti virus is referenced in the last comment of this thread ... View more

From memory we didn't find anything specific for this issue, however we did up the specs of the machine to 16gb RAM and also changed the default setting from 'live data' being ticked, to unticked. We potentially did some other stuff as well. Changing the live data setting helped our issue of slow queries to the feature service in both map rendering and populating data tables. Our services aren't stream services and contain a considerable amount of data compared to a lot of other GeoEvent dataset examples. Sorry I can't be more specific, I did take notes at the time, but I can't find them now sorry. Happy to help if you have more questions. ... View more

Our final solution looked like this which slightly differs to the steps in the blog by Jon but it worked well for us. As above we split the install between 2 groups of servers 1. Disable Group 1 servers in the LB so that no new connections from users could be made 2. Run TVT on the still live services to ensure that the Group 2 servers still live in the LB were working properly 3. Uninstall Group 1 and clean up any left over files. Restart servers 4. Install new software 5. Set up new data share config folder for Portal and ArcGIS Server using the service account user 6. Set up Portal and ArcGIS server sites (including ArcGIS Server sites for GeoEvent) 7. Configure Relational and Spatiotemporal data stores (update SSL certs) 8. Register other datastores in ArcGIS Server Manager 9. Install and configure Web Adaptors for Portal and ArcGIS Server 10. Import service config and global settings into GeoEvent and publish output feature services (using connection to ArcGIS server using machine name url and credentials to create the datastore connection in GeoEvent Manager) 11. Publish mxd based services to ArcGIS Server using connection created with machine name url and initial admin user 12. Configure any other ArcGIS Server of Portal settings that don't require a LB URL, eg heap sizes for services that have a higher load, date settings and default user roles in Portal. 13. Run TVT on these new services using machine URLs 14. Switch Groups in LB - Disable Group 2, Enable Group 1 = Start of Outage 15. Update Web Context URL in Group 1 Portal and ArcGIS Server 16. Federate Group 1 ArcGIS Server with Portal and set hosting server. Check that all services have been added as Portal items. 17. Federate GeoEvent and any other servers 18. Set any other Post install config for Portal - eg name, description (we have a script that does this) 19. Enable Windows Auth 20. Update Portal Items (we have a script to do this), Groups and sharing of items. 21. Update GeoEvent datastores and output connections to use lb URL (no credentials or tokens required as federated). 22. Run TVT using LB and windows auth = End of outage (for us this was around 3 hours). 23. Start Uninstall and re-install of Group 2 servers 24. Join Portal into site from Group 1, this will cause a ~2 minute outage. 25. Join ArcGIS Server into site from Group 1 26. Install and configure Web Adaptors for Portal and ArcGIS server using Group 1 machine names 27. Configure Datastores to ArcGIS server machine from Group 1 28. Enable Group 2 servers in LB ... View more

Also, our non prod env is disconnected from the internet. On Portal service startup around 750 errors are recorded where it can't find styleItem files eg D:\Program Files\ArcGIS\Portal\framework\webapps\rootapp\styleItems\RealisticTransportation\web\Tesla_P7.json Are these not included in the cabinet install files? is there somewhere else we can get them? ... View more

So reading through the blog and its links I think the following is a possible plan. (First run is in the UAT env, although these servers are in the production domain for internet access. There are no changes or additions to the LB apart from disabling/enabling server rules) - Split the current HA env. - Remove Group 1 from the LB - Set Group 2 as read only and leave live in LB to limit downtime - Uninstall, Clean, Install 10.8 and configure Portal site, AGS site, Datastores reg to AGS site, GeoEvent sites and SBDS reg to AGS site. - Install WA and register Portal and AGS through machine URLs - ? Set Portal webContext to LB URL (even though at this point this machine is disabled in the LB?) - Federate AGS and GeoEvent (Service URL = LB URL, Admin URL = local machine) - test services and apps through machine URLs (but if Federated through LB URL will tokens be from the new updated Portal? or from the Portal still live in the LB (which means that they will be invalid)?) - switch groups in LB - Group 1 live, Group 2 removed So I think my main points of concern are when to set the Portal webContext URL, the Federation URLs and if the Service URL is set to the LB URL if the services and apps can still be tested prior to turning traffic back on through the LB. (Hopefully I have made sense!) ... View more

Thanks for the link Jonathon I will read through that now, and yes, it is currently HA. We are hoping to split it and update them separately and join them back together at the end. ... View more

Thank you! ... View more

Hi, Is the portal sharing API Create Service still the best option for creating a feature service with a spatiotemporal datasource in 10.8?  Thanks, Gill ... View more

Thanks Jonathan, I am looking forward to 10.8! ... View more