In this article:
Business application designer back end is used to work in web interface with ready a business application, which is created using the Prognoz Platform 9 extension -Designer of Business Applications.
The installation must be executed under the user who has local computer administrator permissions.
Before installation make sure that a server role has been added if the web server is installed on server Windows OS. If web server is installed not on the server Windows OS, it is necessary to connect IIS services before installing.
The back end can be installed by means of the DBAWebServer.exe installer (common for x86 and x64 platforms).
The installer executes the following operations:
It installs files of business application designer back end.
Sets up IIS.
It creates a pool of applications (DBA Pool v9.0) and a virtual directory (DBA_App_v9.0).
NOTE. To ensure correct installation, check that Internet Information Services software package is installed at the workstation. Instructions for installing the package can be found in the documentation for the appropriate package.
To ensure back end work, the installed and configured BI server and business application created in repository are required.
Run the installer, select installation language. After the installation is prepared, the start page appears containing introductory information:
To continue the installation, click the Next button.
Then, select the folder to which the back end files will be installed. By default, it is installed to the C:\Program Files\Foresight\ or C:\Program Files(x86)\Foresight\ folder on installing to x64 OS. To change the folder, click the Change button. The Designer of Business Application Web Server directory will be created in the selected folder.
To continue the installation, click the Next button.
On the next page click the Install button to start the installation.
On the last page click the Finish button to finish the installation.
After the back end is installed, it is required to determine connection settings to BI server and determine repository and business application which will be further used for work.
Go to the folder with the installed back end, for example, C:\Program Files\Foresight\Designer of Business Application Web Server\ (C:\Program Files (x86)\Foresight\Designer of Business Application Web Server\ when working in x64 OS).
The sample-DBA.config.json file will be available in the Config subfolder. Rename this file or its copy to DBA.config.json. Open obtained file in text editor.
Determine the BI server address which will be used for repository connection and data transfer as the ppServiceUrl element value. The address format - http://<ServerName | IP-address>[:<Port>][/<VirtualCatalog>]/axis2/services/PP.SOM.Som, for example: "ppServiceUrl": "http://SampleServer/PPBI_App_v9.0x64/axis2/services/PP.SOM.Som".
NOTE. On working with business application the direct connection to BI server is executed from the user computer that is why the ppServiceUrl element value should be set to the address to which the user has access.
If BI server and web server are physically located on the same computer, then a relative path to BI server can be specified in ppServiceUrl, for example, /PPBI_App_v9.0x64/axis2/services/PP.SOM.Som.
Replace all ID_REPO text labels with the repository description identifier where extensions are installed, and a business application is created. Connection settings to the specified repository should be also determined for BI server (Windows / Linux).
Replace all ID_APP text labels with the created and configured business application in repository.
The example of the file that must be created after the specified operations are executed:
{
"targetRepo": "TEST_REPO",
"targetApp": "START_APP",
"ppServiceUrl": "http://SampleServer/PPBI_App_v9.0x64/axis2/services/PP.SOM.Som",
"locale": ["ru"],
"repositories": {
"TEST_REPO": {
"repoIdent": "TEST_REPO",
"apps": {
"START_APP": {
"appIdent": "START_APP",
"breadcrumbRootTitle": "FORESIGHT. Business application",
"mainMenuLogo": "assets/design/img/PPlogo_sm.png",
"pageMetadataLogo": "assets/design/img/PPlogo.png"
}
}
}
}
}
The specified steps are minimum required to get access to business application in the web interface. If required, other settings can be determined, and the number of repositories and business applications available to work with can be extended. For details see description of the DBA.config.json file structure.
If all settings are correct, to check go to the URL of the created virtual directory in the browser (for example, http://SampleServer/DBA_App_v9.0/). The start page of business application designer should open to authorize in repository. Determine login and password. After credentials are checked, the business application interface opens.
The business application uses settings determined in the DBA.config.json file. When working with the default URL (for example, http://SampleServer/DBA_App_v9.0/), the targetApp business application opens from the targetRepo repository. The targetApp and targetRepo field values are set in the DBA.config.json file. To connect to a different repository and open a different business application, which settings are contained in the DBA.config.json file, the user can add additional parameters repo and app to the URL: http://SampleServer/DBA_App_v9.0?repo=TEST_REPOSITORY&app=TEST_APP.
If BI server and back end of business application designer are located in one domain, and the back end is addressed from another domain, the error may occur: "Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource." To resolve the error, enable executing requests to BI server from another domain. The method of solution depends on the web server type, on which the BI server is deployed.
To correct the error, execute the following operations at the IIS web server:
Open the IIS manager and select an application corresponding to the BI server in the connection tree - PPBI_App_v9.0x64.
Select the HTTP Response Headers among the available functions.
Add the following headers:
Access-Control-Allow-Headers with the value "content-type, accept-language, get-ppbi-time, cache-control, soapaction".
Access-Control-Allow-Origin with the value *. To get access only from specific domains, specify names of necessary domains instead of *: http://www.a.com http://www.b.com.
Restart the IIS web server.
To correct the error, execute the following operations at the Apache web server:
Open the httpd.conf configuration file for edit.
Uncomment the following strings:
LoadModule rewrite_module modules/mod_rewrite.so
LoadModule headers_module modules/mod_headers.so
Set the All value in the <Directory />...</Directory> block for the AllowOverride directive, and also add the following strings inside the block:
Header always set Access-Control-Allow-Headers "content-type, accept-language, get-ppbi-time, cache-control, soapaction"
Header always set Access-Control-Allow-Origin "*"
RewriteEngine On
RewriteCond %{REQUEST_METHOD} OPTIONS
RewriteRule ^(.*)$ $1 [R=200]
Restart the Apache web server.
See also: