Hoppa till huvudinnehållet

Creating a test site

Kommentarer

5 kommentarer

  • Dan Griffin

    If I understand correctly, you should be able to use the "Copy Site" button in Essentials (beside "Edit Site" in the site list).  Then  edit the copy of your site.xml in a text editor (find & replace) to point to the copy of your map service.

    <MapService ConnectionString= "url=http://yourserver/arcgis/rest/services/MyMapCopy/MapServer" 

    0
  • Permanently deleted user

    Dan's suggestion is a good one.  One caveat, though, whenever I've used the "Copy Site" button I've had to manually update the paths to any workflows, print templates, etc.

    Also, if you're not comfortable with manually editing the site.xml file, you can change the path using the Essentials Manager.  Click the Map tab, then click the "Edit Map Service" button for the map service, then click the "Edit Connection Settings" button.  Enter your new URL in the "Service URL" field.  If the map services are otherwise identical the change will be made.  If they aren't identical you'll get a warning message.

    In your situation my preference would be to have an Essentials instance dedicated to testing, so you don't have a test site and production site in the same instance.  I don't know if that's an option for you, but I can explain further if you're interested.

    Steve

     

    0
  • Janice Nollar-Conrad

    Thank you for the suggestions! Steve, can you please explain further? I'm not exactly sure what is meant by "the same instance". Wouldn't they already be separate if different REST points were created from a separate mxd (or msd) file?

    0
  • Permanently deleted user

    Hi Janice,

    We're overloading the term "instance" here.  In Essentials, you may install multiple named instances of Essentials to the same computer.  This will result in having a completely new installation (instance!) of Essentials on your server.

    Steven's suggestion is to install a new instance of Essentials with a name.  For example, if you called your new instance "Test", it would default to installing to:

    C:\Program Files (x86)\Latitude Geographics\Geocortex Essentials\Test\Rest Elements (etc)

    Which would be beside the default instance at:

    C:\Program Files (x86)\Latitude Geographics\Geocortex Essentials\Default\Rest Elements (etc)

    However, for your purposes you should be fine with making a copy of your site, then using REST Manager to change the map service connection information to have your site reference a different service.  Note again that you may only do this if the services are functionally identical (all the same layers and groups!).

    Now would also be a good time to take an inventory of what map resources you are consuming.  Changing the service may cause problems with workflows, particularly if the workflows are using exact URLs to perform queries.  Consider the situation where you have removed a slow-running layer.  The site that references that service has all of the service layers configured (perhaps with aliases).  If you don't do anything, the site will stop loading because there is a missing layer.  When you load the site in REST Manager, you must resolve the missing layer - if there are new unconfigured layers, you may choose to reassign it or you can remove it from the site.  Now the site will load, but it might not work - removing a layer will reassign all of the layer IDs (and therefore, the layer query URLs), so your workflow that was querying a streets layer may now be querying a towns layer!

    Regards,

    -Malcolm

    0
  • Permanently deleted user

    In addition to what Malcolm said, I will also suggest taking a look at section 5.2 of the (https://support.geocortex.com/SharedFiles/Download.aspx?pageid=12&mid=14&fileid=655) Installation Guide for more information on installation options and instances.  I disagree that the term "instance" is being overloaded in this discussion.  In light of the documentation's use of the term, what else would one call it?

    When talking about test sites, my preference is to have the test site separated from the production site.  Maybe my approach is too cautious, but experience has shown me that separating "test" from "production" will save you grief in the future. 

    Janice, I have our development environment set up to accomplish what you're asking about, and I'm willing to continue the discussion offline if you'd like.  I've received help from others in the forum and don't mind "giving back" when I can, and it seems like offline is the best place to proceed.  My email is (steven.graham@wi.gov)   Phone number is in my profile if you'd rather go that route.

    Steve

     

     

     

    0

Du måste logga in om du vill lämna en kommentar.