Skip to content

Latest commit

 

History

History
61 lines (52 loc) · 3.42 KB

agility.md

File metadata and controls

61 lines (52 loc) · 3.42 KB

Digital.ai Agility

Logs

  • Analytics: C:\ProgramData\VersionOne\Analytics\setup.log
  • DataMart: C:\ProgramData\VersionOne\DatamartLoader\setup.log
  • General exceptions: C:\ProgramData\VersionOne\Exceptions

License updates

  1. RDP onto Agility server.
  2. Go to C:\inetpub\wwwroot\Agility\bin.
  3. Replace the .lic file.
  4. Restarting server isn't necessary. New license will be used automatically.

Upgrades

  1. Obtain an updated Agility license file. A new license file must be obtained during any major version bump.
  2. Post notification alerting users that service may be down.
  3. Snapshot the Agility instance.
  4. Snapshot the Agility database (versionone).
  5. RDP onto Agility server.
  6. Download the latest Agility release.
  7. 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 to false 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
  8. Follow the installation guide PDF in the downloaded release archive.
    • NOTE: Upgrade order is Agility, then DataMart, then Analytics
    • NOTE: The new Agility license goes in C:\inetpub\wwwroot\Agility\bin\license.lic
    • Requires:
      • DB password
      • DB username
      • Integration code
  9. 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 to true and then restart Shibboleth (shibd_Default in Windows Services): 
      <Path name="Agility" authType="shibboleth" requireSession="true">
  10. Run DataMart ETL script.
  11. Test service connectivity.

Troubleshooting

  • 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