Install environment

Chris Roberts

19 juin 2019 01:48

This maybe a dumb question....We have a Dev, QA and Production setup for our Geocortex environment (QA and Prod are both a 2 server cluster). My questions is when installing Printing 5 on prem where should I install it? Just on our single dev server. Or, on both our Prod servers? Or on all three environments.

0

• 

  Stefan Schweigert

  19 juin 2019 15:13

  Hi Chris,

   

  No such thing :). I would suggest that you install only on one of your production servers. The performance of generating prints is largely based on your server's networking abilities and the access to the data used in those prints, more so than the computing power of the machine itself. You can export and import print templates between servers if you wish to create them on your QA server, then move them to prod as well.

   

  Thanks, Stefan

  0
• 

  Eric Kriener

  26 septembre 2019 14:56

  so, @Stefan Schweigert? , we can install our GC5 stuff on a dev and prod server and it's all good (license wise)?

  0
• 

  Stefan Schweigert

  26 septembre 2019 15:54

  Hi Eric,

   

  I would first confirm with your account manager as to your current installation entitlements.

   

  Thanks, Stefan

  0
• 

  Eric Kriener

  8 octobre 2019 14:09

  ok, circling back to this... @Stefan Schweigert? 

  "You can export and import print templates between servers if you wish to create them on your QA server, then move them to prod as well."

   

  Does this not then create duplicates of everything out in our AGOL organization?

   

  What's the process for 'moving' a report/print/workflow to the other server?

  I have found it's not as simple as just changing the Data Source URL of the AGOL item...

   

  thanks.

  0
• 

  Stefan Schweigert

  8 octobre 2019 15:51

  Hi Eric,

   

  If you creating client-side workflows using the on-prem versions, then the items created in AGOL will already be accessible in any installed instance. When wanting to move items that are hosted within Portal instances, see the following sections as each product has different requirements:

   

  Workflow Section

  Reporting Section

  Printing Section

   

  Thanks, Stefan

  0
• 

  Eric Kriener

  8 octobre 2019 15:56

  I'm getting this:

   

  Unable to open print item

  The remote server returned an error: (404) Not Found.

   

  when trying to open things on our external dmz server that were created on our internal dev server...that are stored in AGOL (not a portal)

  0
• 

  Stefan Schweigert

  8 octobre 2019 16:16

  Hi Eric,

   

  Is the print item shared publicly in AGOL?

  0
• 

  Eric Kriener

  8 octobre 2019 16:18

  yes

  0
• 

  Eric Kriener

  8 octobre 2019 16:23

  and if I try to open one (that I exported from the internal server and imported on the external server) on the internal server, I get this:

   

  Unable to open print item

  Internal Server Error

   

  0
• 

  Stefan Schweigert

  8 octobre 2019 17:22

  Hi Eric,

   

  I made a correction to my comment above as this statement only applies to workflow. There are additional step required to move reports and prints between servers, even if they are publicly available.

   

  You should be able to export from your internal server, import onto your external server, save on your external server, then access this item through the new item URL created. You cannot directly reference the internal server's item.

   

  Does that help?

   

  Thanks, Stefan

  0
• 

  Eric Kriener

  8 octobre 2019 17:25

  I suppose.

  So there will basically be two copies of them in our AGOL?

  0

Vous devez vous connecter pour laisser un commentaire.