Date: Thu, 28 Mar 2024 11:08:07 +0000 (UTC) Message-ID: <538496056.6185.1711624087385@ip-10-10-7-29.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_6184_894421498.1711624087384" ------=_Part_6184_894421498.1711624087384 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Deployment to live should be similar to test deployment, using y= our final set of configuration files. These can be transferred from one sys= tem to another. Remeber to change database connections if your live databas= e is different to you test one. It is a good plan to retain a test system f= or continued testing.
As you deploy, follow each step that you used in your test environment b= uild, testing as you go to make sure no steps are missed out.
If you wish to conduct exhaustive tests on you grouper installation you = can run the complete test suite. To do this you need to start with an empty= database, correctly configured in grouper.hibernate.properties, and a defa= ult sources.xml file. You should also set true in all junit test includes i= n grouper.properties. Next, open a command line and go to GROUPER_HOME/bin = and run ./gsh.sh -test -all (linux) or gsh.bat -test -all (windows). The te= sts take some time to complete, but all should pass OK.
Grouper loader initiates scheduled jobs which operate on the whole group= repository (database), you must ensure that jobs such as daily report and = changelog are only enabled on only one instance of the Grouper loader daemo= n. During testing it is easy to start multiple instances of the Daemon, but= it is important to avoid doing this. It is therefore a good idea to have 2= versions of the grouper-loader.properties file - one version which include= s the scheduled jobs enabled, and another which does not. Jobs which can be= scheduled include:
These will be covered in later sections.
If you ran the tests you should reinitialise your schema with:
Linux:
GROUPER= _HOME/bin/gsh.sh resetRegistry()
Windows:
GROUPER= _HOME\bin\gsh.bat resetRegistry()
Load your data. If you'v ebeen following this documentation without jump= ing ahead you may not actually have any data to load (other than by using t= he UI). Don't worry, we'll be looking at the various methods of getting dat= a into and out of Grouper in later sections.