Create Configuration File
3 min
In this step, you will be using the configuration wizard to create a configuration file containing your desired installation settings. If you have an existing configuration file, you will be able to import it in Step 3.
- In File Explorer, navigate to the directory where you extracted the Blueprint installation files to.
- Run the BlueprintSys.RC.Installer.Configuration.Wizard.exe executable.
- Enter your desired installation path. If you already have an existing configuration file to act as a starting point, you can import it here.
- Click Next.
- Specify the settings for your server configuration below:
- Active Directory: The default configuration deploys servers joined to Active Directory. Select No if you prefer a non-domain-joined server.
- Server Environment: Choose one of the following server configurations:
- Multi-server configuration: Select this option to host the Blueprint application and its databases on separate servers. This is the recommended deployment configuration and is the standard approach for most environments.
- Single-server configuration: Select this option to host both the Blueprint application and its databases on the same server. This configuration is intended for smaller environments and is not recommended for production deployments.
- Click Next.
- Specify the settings for your database server using the fields below:
- Database deployment model: Important: This option is only available for new installations. Pre-existing database configurations cannot be changed. Multiple databases cannot be merged and single databases cannot be separated.ο»Ώ
- Multiple databases: Selecting this option means that Blueprint will be deployed in its standard multi-database configuration. This option accommodates larger deployments as the databases can each be managed and stored individually. This is the recommended configuration.
- Single database: Selecting this option means that Blueprint will be deployed in a single-database configuration. This configuration is simpler to maintain but is less scalable compared to the multiple database option.
- Database server details:
- Database Server: SQL Server instance that will host the Blueprint databases. Enter the in the format: <ServerName>\<InstanceName>. For example: ACMECorp\MSSQLServer.
- Database Name: Specify the name of the primary Blueprint database. This name is also used as the prefix for the associated FileStorage and AdminStorage databases. For new installations, the specified database must not already exist.
- Database Authentication type: Important: This user must be a SQL Server System Administrator (SA). This will allow the installer to create the necessary databases and grant the appropriate permissions for the Blueprint application user specified earlier to be able to access them. The SA credentials are not stored in the system and they are only required during the installation process.ο»Ώ
- Windows Authentication: Select this option to connect to the SQL Server instance using the Windows account running the installation scripts. Ensure that this account has sysadmin (SA-equivalent) privileges on the SQL Server instance.
- SQL Authentication: Select this option to connect to the SQL Server instance using a SQL Server account. During installation, you will be prompted to enter the password for the specified account..
- Username: Specify the SQL Server account that will be used to deploy Blueprint to the database server. This account must have sufficient permissions to create and configure the Blueprint databases.
- Click Next.
- Specify your application server settings using the fields below:
- Site Name: Enter the name of the main Blueprint IIS site. The default is Blueprint.
- Host Binding (Optional): Enter the hostname that the Blueprint sites should use. Specifying a hostname overrides the default wildcard binding configured in IIS.
- Port Number: Specify the port used by the main site. By default, the site is bound to port 8080.
- Auxiliary Services Port Number: Specify the port used by the auxiliary site. By default, the site is bound to port 9101.
- Application Pool Identity: Specify the application pool identity:
- Built-in Account (ApplicationPoolIdentity): Select this option to run the Blueprint IIS application pools using the built-in ApplicationPoolIdentity account. This option is available only for single-server deployments.
- Custom Account:
- Username: Specify the domain user account that will be used to run the Blueprint application. For account requirements, refer to the User Account Requirements section above. During installation, you will be prompted to enter the password for this account.
- Click Next.
- Specify your Windows services settings using the fields below:
- Local Service: Run the Blueprint Windows services using the Windows Local Service account. This option is not available for a domain-joined server configuration.
- Network Service: Run the Blueprint Windows services using the Windows Network Service account. This option is not available for a domain-joined server configuration.
- Custom Account:
- Username: Specify the domain user account that will be used to run the Blueprint Windows services. For account requirements, refer to the User Account Requirements section above. During installation, you will be prompted to enter the password for this account.
- Click Next.
- Specify your message broker settings by filling in the following fields:
- SQL Server: By default, application messaging is managed by the SQL Server Service Broker and requires no further configuration.
- RabbitMQ Server: If you have an existing RabbitMQ installation that you would like to use instead, provide the following information. You will be prompted for the user account's password during installation.
- Host Name: The hostname of the RabbitMQ server
- Virtual Host: The virtual host used for RabbitMQ message processing
- User: The username of a RabbitMQ administrator account
- Click Next.
- If you want to activate Blueprint during the installation process and have an activation key already, you may enter it now. Multiple keys can be entered as comma-separated values. Otherwise, you can perform an online activation or a manual activation via e-mail at a later time.
- Click Next.
- Click Finish to generate the configuration file.
- The configuration file is saved in the same folder as the Configuration Wizard executable. The file name uses the format: BlueprintInstallSettings-<Version>-<DateTime>.xml.
- <Version>: The version of Blueprint being deployed.
- <DateTime>: The date and time the configuration file was created.