2 deFacto Service Accounts
Admin
This deFacto service will run a Windows NT service called “CallistoService” as well as an application pool called “Callisto” and requires the following access:
- Needs to be Administrator on Web Server with install rights
- Needs to be SysAdmin in SQL Server
- Needs to have Administrator Access to SSAS
- Needs to be a Domain user with access to validate users on the Active directory
- Needs to be given login as a service and login as batch job, security rights.
User
This deFacto service will run a Windows NT Service called “CLRptService” as well as an application pool called “CallistoUser” and requires the following access:
- Cannot be an Administrator on the deFacto servers.
- Needs to be SysAdmin in SQL Server
- Needs to have NO Access to SSAS
- Needs to be a Domain user with regular User/Domain User access.
- Needs to be given login as a service and login as batch job, security rights.
SQL / SSAS Service
- Service Running SQL needs read/Write/Create Access to SSAS
- Service Running SSAS needs SysAdmin Access to SQL
- SQL ALIAS Names are not supported.
Web Server
- IIS with the following Options Selected
- (Required)
- .NET 4.5+ (Required)
- SQL Server Standard/Enterprise Edition 2017 or later Client Components for web\application server. (Recommended)
- SQL Management Studio (for SQL 2016 install Management Studio 17.x) (Optional)
- Excel 2007+ Office Share components and Office tools installed
Note: If installing excel is an issue, deFacto installation port will need to be opened for external access via VPN.
SQL / SSAS Server
- SQL Server 2017 +
- If planning on using Predictive Forecasting make sure Machine Learning Services (In-Database) R and Python are installed.
- After SQL is installed run the following and then restart SQL Server
sp_configure 'external scripts enabled', 1;
RECONFIGURE WITH OVERRIDE;
- SSAS 2017+ in Multidimensional Mode.
Installs with ETL Server Install Checklist
- deFacto service account needs remote desktop access to all servers during development period. This access can be removed after development is finished.
- SQL Server Data Tools (SSDT) / Business Intelligence Development Studio is required for developing SSIS packages. It is called SQL Server Data Tools in SQL Server 2016+. In multi-server environment, deFacto recommends SSDT/BIDS installed on the application server. After the packages are developed, they will need to run on the SSIS server (Generally it is the same as SQL Server). deFacto creates a shared folder on the application server for SSIS to access the package.
Note: Please consult deFacto if creating a shared folder on app server is an issue. deFacto will recommend other configurations in that case.
For SQL Server 2019 you need to install Visual Studio 2019 and make sure to add the SQL Server Data Tools through the Visual Studio Installer :
Then add the following extension for SSIS:
For SQL Server 2017 and below you need to determine the correct install using the following links:
Which version of Data Tools to install for which SQL Server version:
SQL Server Data Tools Download Link:
https://msdn.microsoft.com/en-us/library/mt204009.aspx
- SQL Server Agent is required for on demand data load functionality. deFacto service account needs administrative access to create packages and then further modify packages via T-SQL. It is required in multi-server environments when SSIS and the application server are not the same.
- SQL Server Integration Services (SSIS) is required. deFacto service account requires access to SSIS to check on packages status. Steps to grant access can be found below under section “Grant Permissions to the Service”.
- SQL client connectivity tools and SDK are required.
- For data access the deFacto service account needs read access to all data sources.
Example: For GP data, deFacto service account needs read access to Dynamics database and all company databases.