- Analytics:
C:\ProgramData\VersionOne\Analytics\setup.log
- DataMart:
C:\ProgramData\VersionOne\DatamartLoader\setup.log
- General exceptions:
C:\ProgramData\VersionOne\Exceptions
- RDP onto Agility server.
- Go to
C:\inetpub\wwwroot\Agility\bin
. - Replace the
.lic
file. - Restarting server isn't necessary. New license will be used automatically.
- Obtain an updated Agility license file. A new license file must be obtained during any major version bump.
- Post notification alerting users that service may be down.
- Snapshot the Agility instance.
- Snapshot the Agility database (versionone).
- RDP onto Agility server.
- Download the latest Agility release.
- Disable Shibboleth Service Provider.
- Edit the file in
C:\opt\shibboleth-sp\etc\shibboleth\shibboleth2.xml
and disable Shibboleth on the RequestMapper paths (around line #70). - Set
RequireSession
tofalse
and then restart Shibboleth (shibd
in Windows Services):<Path name="Agility" authType="shibboleth" requireSession="false">
- This is done to allow a regular login page to be presented at example.domain.com/Agility so the Analytics Service can install correctly. Otherwise Shibboleth will attempt to redirect to the authentication service and prevent Analytics from installing correctly, you'll get an
Unexpected character encountered
error. - Also see Shibboleth RequestMatter docs
- Edit the file in
- Follow the installation guide PDF in the downloaded release archive.
- NOTE: Upgrade order is
Agility
, thenDataMart
, thenAnalytics
- NOTE: The new Agility license goes in
C:\inetpub\wwwroot\Agility\bin\license.lic
- Requires:
- DB password
- DB username
- Integration code
- NOTE: Upgrade order is
- Re-enable Shibboleth Service Provider.
- Edit the file in
C:\opt\shibboleth-sp\etc\shibboleth\shibboleth2.xml
and enable Shibboleth on the RequestMapper paths. - Set
RequireSession
totrue
and then restart Shibboleth (shibd_Default
in Windows Services):<Path name="Agility" authType="shibboleth" requireSession="true">
- Edit the file in
- Run DataMart ETL script.
- Test service connectivity.
- In the IIS manager, ensure Agility is running under
Application Pools
(start it if stopped) - Restart IIS with cmd.exe:
iisreset /restart
- Restart Shibboleth daemon
shibd.exe
from services