Skip to main content

Make bulk/programmable changes to DocumentStore

Comments

10 comments

  • Permanently deleted user
    Hi Jack,

     

    I am not aware of a method but you can try using a tool like Fiddler to capture a manual change in Essentials Manager and see what the request that is being sent out looks like.  You can then try and recreate the request.

     

    Regards,

     

    Wayne
    0
  • Permanently deleted user
    Thanks Wayne, that sounds doable.
    0
  • Tom Neer
    Jack,

     

    Messing with Geocortex Core is dangerous. Before you do anything, make sure you have backups using the backup utility. With that said, take a look at https://github.com/appbaseio/dejavu. 

     

    Best,

     

    -Tom
    0
  • Permanently deleted user
    BTW, I found using the Manager for ElasticSearch.exe tool I could export and modify the JSON document, then import it back (haven't tried yet the import part). I probably will give it a go see how it works (in our test enviro).
    0
  • Permanently deleted user
    Hi everyone, I have had some success with editing the JSON file exported from ElasticSearch tool. The steps are, export the document/moniker/chunk entities out as JSON, then modify the data, delete the old entities in the doc store using ElasticSearch Tool, and import the modified JSON file. It works for document entities, moniker entities, however, if I it didn't work for Chunk entities even without any change to the content, as soon as the old entities are deleted and the new ones are imported in, If I go https://myserver/Geocortex/Essentials/RestManager/documents/readDocument?id=a259296efbc74d44a3ee4b94e08c2b05&format=json, i got the following error. I don’t know if I have missed anything or it was something to do with the ElasticSearch tool or on Geocortex side. I would appreciate anyone have experience of this Elastic Tool could point me to the right direction.  A bit background here, we are doing server migration, the changes are include AD , Geocortex server and ArcGIS server domain, authentication method etc. and we have a large number of save projects need to migrate. 

     

    {

     

      "error": {

     

        "code": 400,

     

        "formalCode": "generic failure",

     

        "formalMessage": "Operation is not valid due to the current state of the object.",

     

        "message": "[generic failure] Operation is not valid due to the current state of the object.",

     

        "type": "GenericError"

     

      }

     

    }

     

     
    0
  • Permanently deleted user
    Jack, I'm in the progress of migrating projects as well and hit the same issue you did. Any chance you figured out a solution or workaround to this?

     

     

    Cheers

     

    Shane
    0
  • Permanently deleted user
    hi Shane, I ended up creating a WF5 workflow that allows the users in the new environment to enter the ID of a saved project, the workflow then reads the json string of the save project returned from the old environment, and re-create the key elements like measurement, markups, bookmarks etc. in new environment, and save it as a new saved project. it doesn't restore the layer selections of the saved projects, but technically can be done. If you're interested, please provide me with your email dress I can send you the WF5 code. cheers
    0
  • Permanently deleted user
    Thanks Jack, that would be great! shane_helm@tcenergy.com Cheers
    0
  • Nico Burgerhart
    I'm also interested: nico.burgerhart(at)sweco.nl
    0
  • Dario Simcic
    Hi Jack,

     

    awesome work!

     

    If you want to share it with me too: d.simcic(at)geographics.it

     

    We're trying to find a successfull way to migrate projects.

     

    Thanks!
    0

Please sign in to leave a comment.