Shared Services and development examples and ideas

Permanently deleted user

23 November 2011 18:42

Hi

I'm interested to hear from anyone who is working with Geocortex either as a shared service or shared design of workflows and reports

There would be multiple offices in different locations working with Geocortex locally but contributing to a central library of Geocortex components (workflows and reports)

Components need to have some form of version control and metadata to help searching and discovery.

 

Has anyone any experience with this type of thing?

Thanks

 

Mark

Mark Thompson

 

Senior GIS Consultant

 

Explorer Graphics Ltd (North South GIS New Zealand)

 

A NorthSouth GIS Group Company

 

 

Geographic Information Centre, Discovery Drive, PO Box 58031, Whitby, Porirua 5245, New Zealand

 

Ph: +0275 529 711| Fax: +64 4 234 7863 | Email: markt@egl.co.nz  | Web: http://www.egl.co.nz |

0

• 

  Permanently deleted user

  24 November 2011 01:01

  For my part, I would also be interested in hearing how others are managing their spatial application infrastructure.  Quite often there are different departments sharing the same Geocortex Essentials installation, and based on the security and management requirements of each there can be different ways to approach this.  Multiple Essentials instances?  A scheme where departments make all requests through an Essentials administration team who then performs the work?  A completely shared development environment where any one of a number of people can log in at any time and make changes?  Depending on the environment, there can be advantages to each - I'd like to hear how it's been architected in different organizations.

  Speaking only to the versioning of components, at Latitude we use Subversion to track edits to development pieces (both to the core product and to professional services projects).  Being able to track changes to files, see who made different edits, and grab files from a specific version or point in time is essential for us (no pun intended!).  I think there is room for Subversion to be applied to both development and non-development environments as well.  It's easy to learn/use and flexible - in fact, it's what I use at home to manage my digital photo library.  It's certainly a good option for versioning shared Essentials components such as Workflows and Report Templates, which are text files and the differences between versions can be easily tracked.

  John

  0
• 

  Permanently deleted user

  24 November 2011 05:08

  John,

   

  In response to your questions…

   

   

  Regarding multiple business areas sharing Geocortex, I have set up each area with its own Essentials instance in the production environment.   That gives me some extra flexibility should the need arise.

   

   

  In our development environment I have set up an instance for each person doing development so they don’t have to worry about conflicting with others.  We only have a small number of people doing development so that has worked well for us.  If a developer has any special configuration they want applied to their instance, we discuss it and I make the necessary configuration changes. 

   

   

  I handle all the production deployments, so I keep track of any configuration changes in the instances.

   

   

  Since we’re small, and each developer has their own instance, we are not using any versioning products yet.  I do encourage everyone to make copies of their site.xml and/or viewer.xml files prior to making major changes, though.

   

   

  Steve

  0
• 

  Cattyann Campbell

  19 Oktober 2012 02:13

  We have a shared development environment with one of the municipality in the County.

   

  Same server and a small dev team of 6 that's under treat of growth...

  Anyway you can read all about it at our Portal- http://geo.tompkins-co.org/geoportal/

  The City has some services open to the public on the shared portal and a separate portal locked down with security for its staff with more advanced functionality, they are big into reporting and starting to develop workflows...

  All of this sit on the same server around the corner from me and since the City and the County share a "fat pipe" in between the City team login and do their own admin work as if they are sitting in my office.

  I take care of server setup, troubleshooting, and deployment with them looking over my shoulders for moral support

   

  They get to play /customer/servlet/servlet.FileDownload?file=00P6000000e87wBEAQ  It works pretty well until someone add a bad xml that breaks the sites. I will emphasize backing up those sites and main config.xml and viewer settings. We recently migrated to a new server I don't advise doing this unless there is utter need.

  0

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