Skip to main content
Version: 4.3.0

Administrator configuration file examples

The configuration file below contains different examples of Administrator configurations. Identify the one that best matches your requirements and modify it as necessary.

Example files

Configure iCore Administrator as a new web site using forms authentication

<?xml version="1.0" encoding="utf-8"?>
<Configuration xmlns="http://schemas.icore.se/web/installConfig/1.1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://schemas.icore.se/web/installConfig/1.1 ../WebInstallConfig.xsd">
<!-- Install iCore Administrator as a new web site using forms authentication. -->
<Site SiteName="My iCore Site" PhysicalPath="%SYSTEMDRIVE%\inetpub\My iCore Site" xsi:type="WebAdmin.Site" >
<Binding Port="8080" IPAddress="*" Type="http" />
<ApplicationPool Name="My iCore Site" CreationDisposition="CreateIfNotExists"/>
<Authentication Type="Forms"/>
<Connections>
<!-- This endpoint is pointing to the default endpoint of the iCore System Access service on the local
machine. It may be desired to change this to the endpoint of the SAS on a remote machine, or
add additional endpoints to remote system access services. -->
<SystemAccessService Endpoint="net.pipe://localhost/iCore/SAS" Name="Default" />
</Connections>
</Site>
</Configuration>

Configure iCore Administrator as a new web site using Windows authentication

<?xml version="1.0" encoding="utf-8"?>
<Configuration xmlns="http://schemas.icore.se/web/installConfig/1.1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://schemas.icore.se/web/installConfig/1.1 ../WebInstallConfig.xsd">
<!-- Install iCore Administrator as a new web site using Windows authentication. -->
<Site SiteName="My iCore Site" PhysicalPath="%SYSTEMDRIVE%\inetpub\My iCore Site" xsi:type="WebAdmin.Site">
<Binding Port="8081" IPAddress="*" Type="http" />
<ApplicationPool Name="My iCore Site" CreationDisposition="CreateIfNotExists"/>
<Authentication Type="Windows"/>
<Connections>
<!-- This endpoint is pointing to the default endpoint of the iCore System Access service on the local
machine. It may be desired to change this to the endpoint of the SAS on a remote machine, or
add additional endpoints to remote system access services. -->
<SystemAccessService Endpoint="net.pipe://localhost/iCore/SAS" Name="Default" />
</Connections>
</Site>
</Configuration>

Configure iCore Administrator as a new web site using OIDC authentication

<?xml version="1.0" encoding="utf-8"?>
<Configuration xmlns="http://schemas.icore.se/web/installConfig/1.1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://schemas.icore.se/web/installConfig/1.1 ../WebInstallConfig.xsd">
<!-- Install iCore Administrator as a new web site using openidconnect authentication. -->
<Site SiteName="My iCore Site" PhysicalPath="%SYSTEMDRIVE%\inetpub\My iCore Site" xsi:type="WebAdmin.Site" >
<Binding Port="8082" IPAddress="*" Type="http" />
<ApplicationPool Name="My iCore Site" CreationDisposition="CreateIfNotExists"/>
<Authentication Type="OpenIdConnect"/>
<Connections>
<!-- This endpoint is pointing to the default endpoint of the iCore System Access service on the local
machine. It may be desired to change this to the endpoint of the SAS on a remote machine, or
add additional endpoints to remote system access services. -->
<SystemAccessService Endpoint="net.pipe://localhost/iCore/SAS" Name="Default" />
</Connections>
</Site>
</Configuration>

Configure iCore Administrator as a web application in a default web site

<?xml version="1.0" encoding="utf-8"?>
<Configuration xmlns="http://schemas.icore.se/web/installConfig/1.1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://schemas.icore.se/web/installConfig/1.1 ../WebInstallConfig.xsd">
<!-- Install iCore Administrator as a web application in a default web site. -->
<Application SiteName="My iCore Site" ApplicationName="iCore Administrator" PhysicalPath="%SYSTEMDRIVE%\inetpub\wwwroot\WebAdmin" xsi:type="WebAdmin.Application">
<ApplicationPool Name="My iCore Site" CreationDisposition="CreateIfNotExists" />
<Authentication Type="Forms"/>
<Connections>
<!-- This endpoint is pointing to the default endpoint of the iCore System Access service on the local
machine. It may be desired to change this to the endpoint of the SAS on a remote machine, or
add additional endpoints to remote system access services. -->
<SystemAccessService Endpoint="net.pipe://localhost/iCore/SAS" Name="Default" />
</Connections>
</Application>
</Configuration>

Elements in the configuration file

ElementAttributeDescription
Site-Contains the configuration of an installation of a new web site in IIS.
xsi:typeMust be "WebAdmin.Site".
SiteNameThe name of the web site which is to be created.
PhysicalPathThe physical path to where the site content is to be stored. The content can reside on the local computer or in a remote directory or shared directory. If your content will be stored on the local computer, specify the physical path, such as C:\Content. If your content will be stored in a remote share, type the Universal Naming Convention (UNC) path, such as \Server\Share.
Binding-Defines the binding to use for the newly created site.
PortThe port to which to bind.
IPAddressThe IP address that users can use to access this site. Specify '*' to listen to all available unassigned interfaces.
TypeThe binding type, may be either http or https. Select http if you want the website to have an HTTP binding, or select https if you want the website to have a Secure Sockets Layer (SSL) binding.
HostnameSpecify this attribute if you want to assign one or more host names, also known as domain names, to one computer that uses a single IP address.  If you specify a host name, clients must use the host name instead of the IP address to access the website.
ApplicationPool-Defines the application pool for the site or application to use.
NameThe name of the application pool.
CreationDispositionSpecifies if the application pool to use should be created or not.
See also Remarks below.
AuthenticationTypeThe authentication method used for the site.
See also Remarks below.
Connections-Contains information about connections to web services to configure. Only supported for WebAdmin sites/applications.
Connections/SystemAccessService-Defines the connection to a System Access Service from an Administrator application.
EndpointThe address of the endpoint to connect to.
See also Remarks below.
NameThe name of this connection.
Application-Contains properties to control the installation of a web application into an existing web site.
xsi:typeMust be "WebAdmin.Application".
SiteNameThe name of an existing web site in which to create the new web application.
ApplicationNameThe name of the application to create.
PhysicalPathThe physical path where the application content is to be stored. The content can reside on the local computer or come from a remote directory or shared directory. If your content will be stored on the local computer, specify the physical path, such as C:\Content. If your content will be stored in a remote share, type the Universal Naming Convention (UNC) path, such as \Server\Share.

Remarks

<ApplicationPool CreationDisposition="" > attribute

The following values can be used: ApplicationPool

  • UseExisting: No new Application Pool should be created, the name specified refers to an existing application pool.
  • CreateIfNotExists: The application pool should be created if it does not already exist, otherwise the existing one is used.
  • CreateNew: A new application pool should be created. If it already exists, an error will be generated.

<Authentication Type="" > attribute

  • Windows: The Windows credentials of the user will be used for authentication.
  • Forms: Pre-defined user accounts are validated and matched with roles.
  • OpenIdConnect: Use an Open ID connect provider for authentication.

For more information, see Authentication types

<SystemAccessService Endpoint="" > attribute

The default endpoint (net.pipe://localhost/iCore/SAS) points to the iCore System Access Service on the local computer. If you want to, for example, use a SAS running on a remote computer, you need to do the following:

  1. On the remote computer: Use a PowerShell cmdlet to add the new endpoint.
  2. On the local computer: Change the Endpoint element in the configuration file, so it points to the new endpoint.
  3. On the local computer: Use a PowerShell cmdlet to remove the (old) default endpoint. This step is optional
  4. On the remote computer: Restart SAS directly in Windows, or use a PowerShell cmdlet.

If you plan to install the Administrator website and SAS on different computers, you need to add an endpoint of type net.tcp to handle communication between the two. For an example on how this can be done, see iCore PowerShell cmdlet.