This document describes how to install and configure the Entire Operations Web Client
The following topics are covered:
The OGC6 application opens in your default browser.
By default, the user language set in the browser is used. In the upper-right corner of the login screen, there is a menu for language selection where you can before logging in switch between English and German.
You will be prompted to log in with your user ID and password according to your domain's settings .
For detailed information, see Starting/Ending an Operations Session in the User Manual.
You can use a different user ID for EntireX Broker Security. To do this, you must click the button labelled EntireX Communicator Broker Security © Copyright IBM Corp and then enter the required user ID and password.
The configuration file config.json is located in the following directory:
OGC6 folder\assets\config.json
To assign a name that will be displayed on the login screen of the
OGC6 instance:
appTitle":
"Instance name"
Example: "appTitle": "OGC6 Portal 1"
To set up the API endpoint for the OGC6 instance:
"basePath":
"server name"
Example: "basePath": "NOPRestServer1"
To set the instance timeout limit
:
"dataListLoadTimeOut": Time in
seconds
Example: "dataListLoadTimeOut": 1800
(1800 seconds, which is 30 minutes)
Using the configuration described above, you can create multiple instances of OGC6 and configure each one for a specific OGC6 REST server .
Below are examples of two separate instances.
Instance 1:
ogc6.war
appTitle: OGC6
basePath: NOPrest_tomcat
Instance 2:
ogc6-qa.war
appTitle: OGC6 QA
Every OGC6 instance uses the file extension .war.
The file name preceding the extension .war is reflected in the URL
used to navigate to the OGC6 instance.
The URL containing
filename.war is displayed in the form
https://<Host>:<Port>/filename/
.
Example:
For the filename ngx-ogc6-portal.war, the
URL of the OGC6 instance's login screen is
https://host:port/ngx-ogc6-portal/#/login
Note
Note: It is not recommended to rename the .war file
using a version number (e.g.
ngx-ogc6-X.Y.Z.war).
The file ngx-ogc6.war, its server folder and the
OGC6 instance folder must be located in the same directory in order for them to
work.
To check whether the OGC6 client can connect to its
REST server:
Start OGC6.
On the login screen, the server information in the Node Name and Server Name fields is automatically updated,
The connection has been successfully established if the node name and server name are displayed.