Rest Services installation

This section only applies to agencies using Rest Services in an on-premises environment. For multi-tenant agencies, the Rest Services are provisioned by the Infor Cloud team.

There are two options for installing Rest Services:

  • Shared: If you're installing Rest Services on the same server as Infor Operations and Regulations, you can use a shared installation. In a shared installation, the Rest Services use the dlls and the config files in the Infor Operations and Regulations application directory.
  • Stand-alone: If you're installing Rest Services on a separate server, you must use a stand-alone installation. In a stand-alone installation, Rest Services has its own copies of the Infor Operations and Regulations dlls and config files, because the ones in the Infor Operations and Regulations application directory are not locally available.

    See Stand-alone installation.

If you are installing a stand-alone instance of Rest Services, you will be required to provide the encryption key for your Infor Operations and Regulations site. Each agency is randomly assigned a unique encryption key on installation or upgrade to Infor Operations and Regulations 8.5.0 or later. The encryption key can be found by selecting the AGENCY node in the Hansen8 configuration.

You will also be required to specify a deployment ID and a Redis service to connect the Rest Services to Infor Operations and Regulations. The deployment ID identifies the environment group that the Rest Services belong to. An environment group consists of one or more instances of Infor Operations and Regulations and related applications such as the Batch Manager and Rest Services. The deployment ID can be found by selecting the DEPLOYMENT node in the Hansen8 configuration for the Infor Operations and Regulations site.

Redis is a messaging service that Infor Operations and Regulations uses to interact with related applications such as the Batch Manager and Rest Services. The Redis settings for an Infor Operations and Regulations deployment are stored in the INFRASTRUCTURE node of the Hansen8 configuration.