Skip to main content

Introduction to IIS Web Deploy

The following InRule components are available for IIS Web Deploy.

ComponentDescriptionDeployment assetsHelp
Decision ServicesIndustry-leading platform for scalable, secure decision automation.IIS deployment package (InRule.Runtime.DecisionService.IIS.zip)Decision Services API Guide
Catalog ServiceCentral repository for storing, managing, and deploying rule applications.Coming soon...irCatalog for Rule Management
Catalog ManagerAdministrative UI to manage rule applications, users and permissions.Coming soon...Overview of the irCatalog Manager Website

The IIS self-hosted deployment package is available from the Azure App Services releases page under Assets for the selected release. Download the IIS deployment, InRule.Runtime.DecisionService.IIS.zip, for the version of Decision Services you are installing.

Prerequisites​

Before deploying the package, make sure that:

  1. IIS is installed on the target server.
  2. The .NET 10 ASP.NET Core Hosting Bundle is installed on the target server.
  3. Deployment is run from an elevated Command Prompt or PowerShell session.
  4. You have the configuration values required for the deployment package, including the IIS application name, Catalog Service URI and credentials, and Decision Services API keys.

Configuration​

The IIS package includes a SetParameters.xml file for the required deployment values, but some optional runtime settings are not part of that base parameter set. For example, settings such as the rule application label may need to be added or updated directly in the deployed web.config after deployment. If configuration values are changed after deployment, restart the IIS application so the changes are picked up.

The IIS deployment package also includes a README with the detailed deployment steps, package contents, and post-deployment guidance. Use that README as the primary reference when performing the installation.

Authentication​

Self-hosted​

For a self-hosted deployment of Decision Services, you will need to include the API key provided during the deployment configuration as the "inrule-apikey" header value on your requests to be able to authenticate to the service.

Example:

"inrule-apikey": "yourapikey"

Swagger​

If you want to make use of the Swagger UI for your Decision API, you will need to include the API key as a query string in the URL. The query string key should be the API key and the value will be your API key. Below you can see an example of a URL that includes the query string.

Swagger Page URL:

https://<domainname>/api/swagger/index.html?inrule-apikey=<apikey>

Swagger Json URL:

https://<domainname>/api/swagger/swagger.json?inrule-apikey=<apikey>
  • Replace the <domainname> with the default domain listed on the overview page of your deployed resource.
  • Replace the <apikey> with the API Key value you included in the configuration when deploying your self-hosted Decision Services.
note

The same approach applies to view the Swagger for the Rule Execution API.