Test System Planning

Jonathan Semones -

Organizations often like to set up test systems.  Test systems can be used for trying out for training users, trying out new products or changes to existing products, sandboxed setup of features, development of integrated applications, etc...

Important! Setting up a Test system is a process that is not covered by Lucity Support.  We can provide information, and troubleshooting, but cannot do the process for you.  If you would like Lucity to do this for you then contact us and we will give you a quote.

Use this guide to decide what type of test system you want setup and plan out how to do it.

Types of Test Systems

Combined

This kind of test system is installed in the same instance of Lucity as your production system.  This means that it uses the same LucityServer location as your production.

Pros

  • Easy to setup
  • Lucity desktop applications (desktop, admin tools, security, lucity tools in arcmap) on each users machine can access both the test and production systems.
  • Because the test and production systems are tied together when you upgrade one it upgrades both.

Cons

  • Must be on the same version of Lucity as the Production system. 
  • Because the test and production systems are tied together you cannot test upgrading the test system without automatically upgrading the production system too.

Separate

This sets up a system completely separate from your production system.  The two systems do not share the same Lucity Server location and are typically on a completely different set of servers.

Pros

  • Test and production can be on different versions.  This is perfect if you want to test a new version before upgrading the production system.

Cons

  • Takes longer to set up as it is a completely different system.
  • Requires a different location for LucityServer and a different server for Lucity Services.
  • Lucity desktop applications (desktop, admin tools, security, lucity tools in arcmap) on a single computer cannot access both the test and production systems.  You need to have a separate machine to run these applications.

Extent of test system

When setting up a Separate test system organizations will either set up a test box or a complete test system. 

Test Box

The entire test system lives on one machine.  This includes LucityServer, Lucity Services, Lucity Desktop, Lucity Web, etc...  This is the easiest to setup as everything is on one box.  This is great if you are just planning on testing workflow processes in the various Lucity applications.  Users will typically remote to the test box or will access the test Lucity Web app from their browsers.

Complete Test System

Your entire production system is duplicated with a different set of servers.  This means that whatever servers you have in production you will have a matching server in the test system.  These servers will be configured the same as your production servers.  This is a harder system to set up and requires more resources.  The benefit of this system comes in testing inter-system processes like uploading documents, making mobile connections, etc...  With this system setup correctly you can tell exactly how your production system will respond to any changes you make as the two systems are nearly identical.

Licensing 

The license file you received from Lucity will typically include an NPR (non-production) license.  This is the license you will use for your test system.  These licenses will match the capabilities you have in your production system but will typically provide access for more users.  Some things are disabled or adjusted when using these licenses so that your two systems are not confused.  For example, notifications sent by NPR clients include a note indicating that the notification is from a Test system.

Have more questions? Submit a request

Comments