Connect Azure BI Infrastructure to IFS Cloud RemoteΒΆ
To connect the BI Infrastructure created in Azure, fill in the following YAML file and pass it to the installer.
## This yml file is to be used with the IFS installer when IFS Cloud is deployed as REMOTE
## and the customer has deployed the BI infrastructure (e.g. SQL Server) in their own Azure Subscription
## i.e. Scenario 2 with AA
ifscore:
secrets:
ifsamSqlServerSsisDbName:
data: SSISDB ## The name of the SSIS database, default is SSISDB.
name: am-sql-ssisdb-name
ifsamIfsDataSource:
data: 10.10.10.10/SID1 ## Oracle <ORACLE HOST IP>/<SID>.
name: am-ifs-data-src
ifsamSqlServerDbName:
data: ifs-sql-dw ## The name of the SQL Server database inside the SQL Server, has to be manually created.
name: am-sql-db-name
ifsamSqlServerType:
data: AZURE ## SQL Server installation type AZURE in this case
name: am-sql-srv-type
ifsamSqlServerName:
data: ifs-sql-srv.database.windows.net ## Azure SQL Server url (<name>.database.windows.net)
name: am-sql-srv-name
ifsamSsisFolderName:
data: ifs-etl ## SQL Server Integration Services Catalog Folder Name (has to be manually created).
name: am-ssis-fold-name
ifsamSsasServerName:
data: asazure://northeurope.asazure.windows.net/ifsaassrv ## Azure Analysis Service url (Format is like asazure://<region>.asazure.windows.net/<name>)
name: am-ssas-srv-name
ifsamSsasUsername:
data: app:<GUID> ## Azure Service Principal Client ID (Make sure prefix "app:" is there like app:<guid>).
name: am-ssas-un
ifsamSsisProjectName:
data: IFSCloudAnalysisModelsSSISFramework ## Must be IFSCloudAnalysisModelsSSISFramework (The SSIS project will be created by an Aurena assistant).
name: am-ssis-proj-name
ifsamIfsinfoUsername:
data: IFSINFO ## IFSINFO / IAL_OWNER user name.
name: am-ifsinfo-un
ifsamSqlServerUsername:
data: MySqlUser ## SQL Server user (A Sql Server Authentication type user with db owner privileges).
name: am-sql-un
ifsamCustomerType:
name: am-customer-type ## MANAGED | REMOTE - REMOTE in this case.
data: REMOTE
passwords:
ifsamSqlServerPassword:
data: xxxxxxx ## Password for the SQL Server user.
name: am-sql-pwd
ifsamIfsinfoPassword:
data: xxxxxxx ## Password for IFSINFO / IAL_OWNER user.
name: am-ifsinfo-pwd
ifsamSsasPassword:
data: xxxxxxx ## Azure Service Principal secret's value (Usually a 40 char string, not a guid).
name: am-ssas-pwd
pbiesAadSecret:
data: xxxxxxx ## Azure Service Principal secret's value (Usually a 40 char string, not a guid).
name: pbies-aad-secret
busmodAadSecret:
data: xxxxxxx ## Azure Service Principal secret's value (Usually a 40 char string, not a guid).
name: busmod-aad-secret
#powerbi-svc
ifsapppowerbisvc:
replicas: 1
serviceConfigEnabled: "true"
azureAdClientId: a1a1a1a1-a1a1-a1a1-a1a1-a1a1a1a1a1a1 ## App registration page -> Application (client) ID, same value as ifsamSsasUsername without prefix "app:""
azureAdTenantId: a1a1a1a1-a1a1-a1a1-a1a1-a1a1a1a1a1a1 ## App registration page -> Directory (tenant) ID
azureAdServicePrincipalObjectId: a1a1a1a1-a1a1-a1a1-a1a1-a1a1a1a1a1a1 ## Enterprise Applications page -> Object ID of the service principal
authConfigUserNameClaim: http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress
authConfigCustomDataClaim: http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress
logLevel: warn
#busmod
ifsappbusmod:
replicas: 1
assServerName: asazure://xxxx.asazure.windows.net/xxxx ## Same value as ifsamSsasServerName
authService: https://xxxx.asazure.windows.net ## AAS site in the region
tenantId: a1a1a1a1-a1a1-a1a1-a1a1-a1a1a1a1a1a1 ## Microsoft Entra ID page -> Tenant ID, same as ifsapppowerbisvc.azureAdTenantId
appId: a1a1a1a1-a1a1-a1a1-a1a1-a1a1a1a1a1a1 ## App registration page -> Application (client) ID, same value as ifsamSsasUsername without prefix "app:""
Download the template YAML file from here.
For more information on Installation Parameters please refer: