On the Agent Gateway Website Settings page, specify the IIS website created or used for the Agent Gateway.
Because the Privilege Manager Portal will be on the same server, you will need to specify the IP address, port, and host header that are unique on the server. To use HTTPS, configure the HTTPS binding and settings manually from IIS manager after the installation. If an existing Agent Gateway is being updated, use the same website settings that the previous version used. You can view the existing website settings from the Agent Gateway website in the IIS management console.
- Specify the Website name for the Agent Gateway application. The website will be created if it does not exist in IIS.
- Enter the IP address that will be used by the website. If all server IP addresses should be bound to the Agent Gateway website, enter an asterisk (*) .
- Enter the Port that will be used by the website.
- Specify the Host header name that will be used by the website. This optional value can be used to run several websites on same server using the same IP address and port, as long as host header names are unique.
On the SMTP Settings page, you can choose optional SMTP email settings so that the Agent Gateway can send emails. If an existing Agent Gateway is being updated, you can view the existing database server settings from Agent Gateway website's web.config file.
- Enter the SMTP Server name or IP address where the SMTP service is running.
- Enter the Port number where the SMTP service is listening to connections.
- Enter the email address from which the Agent Gateway sends emails.
On the Connections pages, you can specify the Agent Gateway connection for Recast Software products. The connection can be the database or another Agent Gateway. If an existing Agent Gateway is being used, you can view the existing connection settings from the Agent Gateway website web.config file.
- If the next connection from the Agent Gateway for Privilege Manager should be a database then select SQL Server and specify the Microsoft SQL Server instance where the database is located. If using the default instance on Microsoft SQL Server, only the server name should be used. If using a named instance on Microsoft SQL Server, the instance name needs to be specified as well. The alternative for specifying a named instance is to enter a server name and TCP/IP port where the Microsoft SQL Server instance is listening, separated by a comma (for example, sqlserver.ad.local, 4252).
- Specify the Database name for Privilege Manager.
- Select Microsoft SQL Server authentication for Agent Gateway to Privilege Manager connections. By default, the Agent Gateway application is running with Network Service credentials. Therefore when using Windows authentication for Microsoft SQL Server, the Active Directory computer object where Agent Gateway is being installed is used for authentication. Microsoft SQL Server authentication can be also selected and then SQL login ID and password will need to be specified.
- Select Gateway and specify the gateway URL address to choose another Agent Gateway as the next connection for Privilege Manager.
On the Destination Folder page, you can choose where the Agent Gateway website content will be placed.
If desired, click Change to install the Agent Gateway in a different folder.