To open web application:
Make sure that the following conditions are met:
On the web application server, repository connection settings are set using the Setting Up Repository Connection dialog box in the desktop application and the Anyone Who Uses This Computer checkbox is selected.
For repository based on SQLite, the work with Foresight. Analytics Platform is available only in desktop application in single-user mode.
NOTE. On using Linux OS repository connection is set up via the registry.
The PP.xml file with the correct path to the BI server in the <service> section is created in the web application server part installation folder.
The PP.xml file where the identifier of connected repository is specified in the <metabase> section is created in the BI server installation folder. On web-application opening, connection to the specified repository will be executed by default.
NOTE. If the PP.xml file is not created on BI server, then specify the identifier of connected repository in the PP.xml file which is stored in the web application server part installation folder.
Open supported browser and specify the web application URL in the connection string:
ASP.NET (IIS) and Apache:
http://<IP address or workstation name>/fp_App_v9.2/app/welcome.html
NOTE. The fp_App_v9.2 virtual directory is created automatically on installing web application server part.
Java (Apache Tomcat):
http://<IP address or workstation name>:<port>/pp/app/welcome.html
NOTE. Before specifying the port, see the requirements in the Ports and Protocols section.
ASP.NET (IIS) and Apache:
http://<IP address or workstation name>/fp9.2/app/welcome.html
NOTE. The fp9.2 virtual directory is created manually on installing web application server part.
Java (Apache Tomcat):
http://<IP address or workstation name>:<port>/pp/app/welcome.html
NOTE. Before specifying the port, see the requirements in the Ports and Protocols section.
If web application login is set via HTTPS protocol, determine the protocol in the URL prefix.
After executing the operation, the HTML page opens depending on the authentication type:
If password or domain authentication is used, the login.html page opens, on which specify repository user or domain user credentials and click the Login button. If the connection is successful, the welcome.html page opens again, and a start page opens that is used to access repository objects.
If integrated domain authentication is used, then the welcome.html start page is displayed and there is no navigation to the login.html page, the current operating system user is used for login.If a connection under a repository user is required on integrated domain authentication, specify login.html instead of welcome.html in the address bar.
NOTE. By default, the web application reuses sessions with the repository if several connections are established under the same user. The session reuse mode can be set up in the PP.xml file.
The connection to the repository specified in the PP.xml file is executed by default.
To sent a link to the repository object in web application and navigate in ForesightAnalytics Platform, use HTML pages. If extensions are connected in web application, the designer of business applications URL and its navigation will differ from the standard web application.
In the web application URL specify HTML page:
welcome.html. The Foresight Analytics Platform start page.
login.html. System login.
adm.html. Security manager.
navigator.html. Object navigator.
dashboard.html. Dashboard.
etl.html. ETL tasks.
model.html. Modeling problem.
olap.html. Express report.
rds.html. MDM dictionary and table MDM dictionary.
reporter.html. Regular report.
time-series.html. Workbook.
workspace.html. Workspace.
Designer of business applications URL:
ASP.NET (IIS) and Apache:
http://<IP address or workstation name>/DBA_App_v9.2/#/<navigation>
NOTE. The DBA_App_v9.2 virtual directory is created automatically on installing designer of business application server part.
Java (Apache Tomcat):
http://<IP address or workstation name>:<port>/dba/#/<navigation>
Instead of the <navigation> substitution, specify:
login. System login
navigator. Object navigator.
agreement. Process.
dataentryform. Data entry/output form.
elt. Calculation algorithm of indicators.
dashboard. Dashboard
tasketl. ETL tasks.
express. Express report.
dictionary. MDM dictionary and table MDM dictionary.
report. Regular report.
wsp. Workspace.
After specifying thee HTML page in standard web application or substitution in designer of business applications, set web application URL parameters to open a specific object.
Web application URL contains a set of parameters to change repository and open objects. Parameters are set after HTML page or substitution that determines type of repository objects, in conjunction with the #, &, ? characters.
General view of wev application URL to change repository:
In standard web application:
http://<IP address or workstation name>/fp_App_v9.2/app/<html page>#repo=<repository identifier>
In designer of business applications:
http://<IP address or workstation name>/DBA_App_v9.2/#/<navigation>?repo=<repository identifier>
General view of web application URL to open object:
In standard web application:
http://<IP address or workstation name>/fp_App_v9.2/app/<html page>#key=<object key>&<optional parameters>&repo=<repository identifier>
In designer of business applications:
http://<IP address or workstation name>/DBA_App_v9.2/#/<navigation>?repo=<repository identifier>&app=<business application identifier>?key=<object key>&<optional parameters>
NOTE. General view of web application URL is given on the example of the ASP.NET (IIS) and Apache web servers. The set of parameters for web application URL on the Apache Tomcat web server is set similarly.
In web application general views the use of mandatory parameters and a set of optional parameters are given. Optional parameters are set in a free order and are divided by &.
The table contains description of the following parameters:
Parameter | Description |
repo | Repository identifier. Optional parameter. It is used to change repository specified in the PP.xml or DBA.config.json file to the repository with the specified identifier. On changing repository, parameter is used by the following pages: welcome.html, login.html, adm.html, navigator.html in the standard web application. It is used in the designer of business applications with substitutions: login, navigator. If the parameter is not specified, then the default connection is to the repository specified in the PP.xml or DBA.config.json file, if extensions are connected in the web application. The parameter is also used to open object by key, if the object is not in the default repository. |
app | Business application identifier. Optional parameter. It is used to open object to change business application specified in the DBA.config.json file to the business application with the specified identifier. If parameter is not set then by default opens the business application that is specified in the DBA.config.json file. The parameter is used only after the repo parameter. |
key | Object key. Mandatory parameter. It is used to open object by key.By default the objects are open from the repository specified in the PP.xml or DBA.config.json file. If the object is in the other repository then specify the repository identifier where the object is using the repo parameter. The object type in the standard web application is specified by HTML page before the key parameter:
The object type in the designer of business applications is determined by substitution before the key parameter:
|
mode | Object opening option. Optional parameter. It is used to open object for view or edit. The parameter can be set to:
mode=<value> NOTE. In the standard web application, editing is available for dashboards, modeling problems and express reports. In the designer of business applications, only dashboards can be edited. |
entry | Model equation key. Optional parameter. It is used to open model equations by key. The parameter is used after the key parameter in the format: entry=<equation key_1>,<equation key_2>,...,<equation key_n> |
params | Object parameters. Optional parameter. It is used to determine object parameters. The parameter is used after the key parameter in the JSON format: params={"<identifier of the parameter_1>":"<value_1>", "<identifier of the parameter_2>":"<value_2>", ..., "<identifier of the parameter_n>":"<value_n>"} NOTE. It is available to determine parameters for regular reports, express reports, data entry/output forms. |
The examples of parameters use:
Connection of the repository with the fpRepository identifier:
http://<IP address or workstation name>/fp_App_v9.2/app/welcome.html#repo=fpRepository
Opening express report with the 66814 key in the repository with the fpRepository identifier:
http://<IP address or workstation name>/fp_App_v9.2/app/olap.html#key=66814&mode=edit&repo=fpRepository
Opening regular report with the 90251 key and the PARAM1, PARAM2 parameters in the repository with the fpRepository identifier:
http://<IP address or workstation name>/fp_App_v9.2/app/reporter.html#key=90251&mode=view¶ms={"PARAM1":"1","PARAM2":["1","2"]}&repo=fpRepository
Opening data entry/output form with the 4945 key and the PARAM1, PARAM2 parameters in the repository with the fpRepository identifier:
http://<IP address or workstation name>/DBA_App_v9.2/#/dataentryform?repo=fpRepository?key=4945¶ms={"PARAM1":"1","PARAM2":["1","2","3"]}
See also:
Web Application Settings | Setting Up Web Application to Work via HTTPS