Self Service & Analyst Portal - Community
Cireson Portal Components
Direct link to topic in this publication:
The Cireson Portal is comprised of four components - the ServiceManagement database, the Cache Builder, the Platform Host and the web site.
The ServiceManagement database is a standard SQL Server database that will be deployed automatically by the installer using an SQL Server "DacPac" (also known as a "Database Tier Application").
There only needs to be one ServiceManagement database per deployment of the Cireson Portal.
All websites can share a common ServiceManagement database.
Cache Builder Service
The Cache Builder service is a Windows service that is installed automatically by the installer. It is used to pull data out of Service Manager and Active Directory and store it in the ServiceManagement database as a cache of data designed to improve the performance of the Cireson Portal by storing the data in a format that is optimized for querying by the Cireson Portal.
There only needs to be one Cache Builder service per deployment of the Cireson Portal. If you are deploying multiple instances of the Cireson Portal (for load balancing as an example), you should disable installing the Cache Builder during the installation.
The Cireson Cache Builder retrieves information from the ServiceManager database, transforms it (for example; flattens hierarchies and merges data from multiple tables into one), and then stores it in the Cireson ServiceManagement database.
The following permissions are required for the Cache Builder service account:
- Must be a member of the SCSM Administrator user role
- sysadmin rights to the ServiceManager and ServiceManagement databases
The following ports should be available to the Cache Builder service:
- 5724 - For the System Center Data Access Service on the SCSM management server
- 1433 - Default port used to communicate with SQL Server
Platform Host Service
The Cireson Platform is a common runtime and technology stack that is being implemented to facilitate the production, and delivery of next generation Cireson applications.
Cireson Platform Applications are delivered using a Nuget based packaging format that is referred to as a Cireson Platform Extension or CPEX.
The Cireson Portal Web Site is an IIS web site which users connect to using a browser.
There can be multiple web sites installed in a farm configuration behind a load balancer.
Portal Communication Flow and Ports
When setting up the Cireson Portal, depending on the authentication method chosen, there are different deployment topology options. Please see the Authentication Options article
for further details of Authentication Methods and how to enable each type
- Integrated Windows Authentication - If you choose to install using Integrated Windows Authentication, the Cireson Portal web site must be installed on a server that is also running a System Center Service Manager management server. The web site should be configured to connect to 'localhost' so that the web site will connect to the System Center Data Access Service that is running locally on the server.
- Forms Authentication - If you choose to install using Forms Authentication, you may choose to either collocate the Cireson Portal web site and the System Center Service Manager management server on the same server or to have the Cireson Portal web site on one server and the Data Access Service on a different server.
|Note: The Cireson Cache Builder service must always be installed on the same server as a System Center Service Manager management server.|
Cireson recommends using a collocated Cireson Portal web site + System Center Service Manager management server for better resiliency and ease of management regardless of the authentication method.