Repairing or Modifying Your Instance
You can initiate auto-configuration of the IIS web server after installation in the event it was skipped during the installation process. To do so, run an installation using the same executable file you originally used to install the instance. Choose to Repair or Modify depending on whether the CSP for IIS component was included in your initial installation:
If the CSP for IIS component was originally installed, but IIS was either not configured or the configuration was manually deleted, you can run a Repair to initiate auto-configuration of the IIS web server.
The only way to include the CSP for IIS component without auto-configuring your instance is to specify CSPSKIPIISCONFIG=1. This flag can only be specified for an unattended installation, or when executing the installation file from the command line. If you did not include this flag during your installation, you should not run a Repair. You can instead Modify the instance to initiate auto-configuration.
If CSP for IIS was not included in your original installation, you can Modify your installation and select the CSP for IIS component. This will cause the installer to initiate auto-configuration of the IIS web server.
In either case, after the installation finishes you should verify additional configuration steps in order for all features to work properly:
To enable Management Portal access, set the CSPSystem account credentials for your instance within its server access profile. For details, see Step 6 of Automatic Configuration Behavior.
To enable the Launcher links, you need to configure the following InterSystems IRIS Server Manager parameters:
Set Web Server Port to the port number your web server is using (80 by default).
Set CSP Server Instance to the lowercase version of your instance name (for example, iris).