Grooper 2.90.0063 is available as of 3-24-2021! Check the  Downloads Discussion  for the release notes and to get the latest version.
Grooper 22.00.0007 is available as of 6-28-2022! Check the  Beta Discussion  for the release notes and to get the latest version.
Grooper 21.00.0049 is available as of 7-1-2022! Check the  Downloads Discussion  for the release notes and to get the latest version.

Multiple repositories running off one license server

BobthebrainBobthebrain Posts: 2 ✭✭
edited January 2018 in The Astronauts (Q&A)
I've got a client right now that has a production Grooper repo, and it is actively in use on production work. They are wanting to know if it would be possible to create a second repository for Test/Dev, but still point it to the production license. The main concern here is testing and rolling out Grooper updates without causing issues with production work.
Tagged:

Best Answer

  • GrooperGuruGrooperGuru Posts: 476 admin
    edited January 2018 Answer ✓
    The short answer is that pointing multiple repositories to a single license server is an unsupported configuration, and should not function properly. If you really need a second, totally isolated system, that system needs a separate license and license service configured.

    With that said, I would challenge the conventional line of thinking that says you have to have a prod system and a test/dev system. We've made a series of architectural decisions from day one that make this unnecessary in the vast majority of situations. Let's first discuss the two types of upgrade scenarios... Major Versions and Minor Versions.

    With a minor version release (meaning, for example, an upgrade from 2.60.0078 to 2.60.0080) there are no changes being made to any data in the Grooper file store or the database. The changes are purely in the application itself. So while it is possible it could behave differently than it did previously, it can't immediately cause data corruption.

    With a Major version release (meaning, for example, 2.60.0078 to 2.70.0001) there will be changes to the database and or various objects in the repository. It is always recommended to do a complete database and filestore backup and/or VM snapshots prior to performing a major upgrade. In the event of catastrophic failure, you would just roll back.

    To test a minor release of Grooper without a secondary license, you would start by selecting and upgrading a single workstation. It is important that this be a machine which does not run any Grooper services.
    1. Uninstall the previous version from add/remove programs, then install the new version.
    2. In admin, clone any batch process you'd like to test. This isn't a requirement, but will keep production statistics from being skewed by the tests.
    3. Temporarily disable all services throughout the environment except licensing. This will prevent any batches you create from being immediately picked up and processed by other machines.
    4. Create a new batch, and manually process it through each automated step. This gives you the opportunity to test all of the front-end user activities and the automated activities. Because the upgraded machine is effectively completing every task, this proves the changes in software have not negatively impacted results.
    5. Once testing is completed and you are ready to upgrade the remainder of the environment, get all users out of Grooper and shutdown all global grooper services including licensing. On the already upgraded machine, launch Grooper Admin. Go to Infrastructure -> Machines. From here you can select any machine in the environment and choose to update system files. This will push all of the Grooper system files from this machine to the destination machine. A log will appear indicating which files were updated. If everything is successful, you should see quite a few files in this list.
    Matt Harrison
    Product Manager
    [email protected]
Sign In or Register to comment.