LIDS AS Console Version 7.3.0

Transcription

1 LIDS AS Console Version 7.3.0

2

3 L7-A03-en0800 Asseco Central Europe, a.s., all rights reserved. The document contains some confidential information and is intended entirely to the hands of the authorized staff of institutions or companies it has been addressed to. No portion of the publication may be reproduced, maintained in the retrieval system or transferred any way including an electronic, mechanical, photographic or other record made without a prior agreement and written consent of the company of Asseco Central Europe, a.s.

4

5 LIDS AS CONSOLEC VERSION I Contents 1. Startup of LIDS AS Console System Panel...7 General...7 Logging...8 Client Properties...9 Network...11 Database...12 Synchronization of Database with LIDS Metadata...13 Synchronization of Security with LIDS Metadata...19 Session Monitor Project Panel...23 Project Info...23 Directories...24 Backdrops...25 Documentation...25 Browser...27

6 II CONTENTS

7 Chapter 1 Startup of LIDS AS Console

8

9 LIDS AS CONSOLEC VERSION Startup of LIDS AS Console The LIDS AS Console is started by starting the URL-address with the specified name of the computer where the corresponding J2EE application server is running and LIDS Application Server (LIDS AS) has been installed. The URL-address is supplemented with the number of the HTTP port and an application name. Thus the URL-address of the console can be as follows: Fig 1: Specification of the URL-address of the LIDS AS Console To log on to the console, a login name and password must be entered correctly. If authorization is activated in addition to authentication in the LIDS-project, assignment of access right APPRUN to LIDS AS Console application is verified. The actual LIDS AS Console contains two navigation panels (System and Project) which serve for basic administration and configuration of LIDS AS including a corresponding LIDS-project. Fig 2: Navigation panels in LIDS AS Console

10

11 Chapter 2 System Panel

12

13 LIDS AS CONSOLEC VERSION System Panel The System panel serves for basic configuration, administration and monitoring of LIDS AS. General Fig 3: System > General The basic information of LIDS AS is displayed in the General section. By pressing the Edit button, links Server URL, Browser, Security Manager and Codelist Manager are made available for editing. The Change language button serves for setting the language used for writing reports in log files, or in messages sent from LIDS AS to clients. Using the Configure long transactions button, it is possible to activate long transactions.

14 8 SYSTEM PANEL In the Track feature changes section, the logging of active operations with LIDS features can be configured. Only change types that are checked in this section are recorded in the table LIDS_FEATURE_HIST. To ensure higher security, it is not allowed to switch off the logging of LIDS feature deletion. If required, the logging can be switched off by editing the config.xml file manually. The Restart LIDS AS button enables the running LIDS AS to be restarted. This results in application server memory reinitialization. Among others, metadata, codelists and configuration data are reloaded and all users are logged off. The Reload Configuration button allows to update the configuration of LIDS AS after editing the config.xml file manually. Reload Configuration is one of the actions performed within Restart LIDS AS. Logging Fig 4: System > Logging

15 LIDS AS CONSOLEC VERSION The Logging section serves for setting parameters for log files of LIDS AS. Possible parameters are the following: the parameter specifying how detailed the logging is, displaying, number of backups, rotation, etc. The individual log files can be displayed using references. The Download all logs button allows the easy downloading of all log files together from LIDS AS to a selected directory the files are compressed into the single Logs.zip file. The Search logs button serves for searching log files according to various criteria. Fig 5: Searching log files Client Properties Fig 6: System > Client properties The Custom properties section contains a list of parameters used for central configuration of the client applications (LIDS Edit, LIDS Explorer etc.).

16 10 SYSTEM PANEL List of general parameters: as_timeout (integer) Time limit (sec) for receiving a response to a request passed on to the application server. After a timeout, the original request is canceled on the client side. automatic_download_relations (true/false) Manages automatic downloading of relations at the moment when the feature form is displayed. long_transactions (true/false) Support of long transactions. feature_page_size (number 1 to 1000) Number of records on one page when downloading data to browse and form. feature_page_size_till_end (number 1 to 1000) Number of records on one page when downloading all remaining data in browse and form. autocommit (true/false) Switches on/off option Automatic committing of operations after logging in to the project. BackdropCache_dir (directory path) Name of directory for temporary saving of backdrop map files. BackdropCache_exclusive (true/false) Suppression of downloading backdrop map files from the AS requested files are only searched for in the local cache. BackdropCache_update (true/false) Suppression of downloading backdrop map files from the local cache requested files are always downloaded from the AS. offline_download_all_codelists (true/false) Manages downloading of codelists on transfer to off-line mode (all codelists / only codelists defined for feature types selected for off-line mode). explorer_max_scale (number 1 to 500) Maximum allowed scale for Graphic Viewer window in LIDS Explorer. explorer_detail_max_scale (number 1 to 500) Maximum allowed scale for window displaying a detail. ustn_master_units (km/m/cm/mm/um) Master units for LIDS Edit with MicroStation. ustn_sub_units (km/m/cm/mm/um) Subunits for LIDS Edit with MicroStation. ustn_working_per_master (integer) Ratio of master units and subunits for LIDS Edit with MicroStation. ustn_3d_seed_file (true/false) Manages use of 2D/3D seed file for LIDS Edit with MicroStation. List of parameters for projects with configuration with SIAS: dynamic_vector_download (true/false) Manages availability of control icons for downloading of vector data. detail_raster_format (jpg, png) Format of files displaying a detail. allow_plain_scale_lock (true/false) Manages availability of function to lock scale for backdrop maps download.

17 LIDS AS CONSOLEC VERSION List of parameters for projects with configuration with TOMS: toms_use_sid (true/false) Manages use of SID or FID identifiers for requests sent from TOMS to LIDS AS. toms_max_objects (number 1 to ) Maximum allowed number for tab page TOMS. tdm_timeout (number) Time interval (sec) for checking the ECHO signal from TOMS Desktop Manager. toms_startup_raster (number >=0) Defines which raster will be displayed when GIS Explorer is launched from the TOMS module. The value determines the position of the given type of backdrop map in backdroptypearray in model.xml. toms_encoding Encoding used in terms of communication by TOMS modules with GIS Explorer. redline_featuretype Identification of feature type used for redline. Supported up to TOMS version 3.2. In terms of regular administration of the LIDS system, there is no need to add further parameters or to change the set values. Network The Network part affects communication by LIDS AS with the environment. Fig 7: System > Network It is possible to set the parameters for connection of LIDS AS in a local network to the Internet via the proxy server in the Proxy section. Connection to the Internet is not required for the basic functionality of LIDS AS, this is for example required for downloading external backdrop maps. It is possible to set the compression for communication between LIDS AS and client applications in the Response compression section. In the case of slower communication lines, this communication can be optimized a lower volume of data is transferred at the price of higher computational demands, both on the side of LIDS AS and also the client applications. MIME type responses stipulated here are compressed.

18 12 SYSTEM PANEL Database Fig 8: System > Database The Database section contains summary information about connecting LIDS AS to the Oracle database, i.e. the LidsDS and SecurityDS data source parameters. In terms of standard installation of LIDS AS, the LIDS DB and Security DB are in the same database scheme. The parameters of LidsDS and SecurityDS data sources are thus the same. If indexes of database tables are saved in another tablespace than appropriate database tables, a name of this tablespace must be specified in Index tablespace text field.

19 LIDS AS CONSOLEC VERSION For database administration, the following tools are available: Connection test (Ping connection button). Comparison and synchronization of the database content and metadata of the LIDS-project (Synchronize button). Updating of indices of database tables (Rebuild indices button). The regular updating of indices of database tables is very important especially from the point of view of speed of working with data of the LIDS-project. Rebuild indices updates all indices in the given DB scheme, including spatial ones. This also applies in the case of a versioned LIDS-project. Synchronization of Database with LIDS Metadata In order to ensure the correct functioning of the LIDS system, a database is required that precisely corresponds to the metadata of the LIDS-project. The tools described below in the AS console are used to ascertain inconsistencies and ensure synchronization of the database with the metadata. Synchronization of the database with the metadata follows the sequence of steps as described below. Synchronization of the database with metadata can only be launched in privileged mode. Fig 9: Database synchronization setting of synchronized types of changes

20 14 SYSTEM PANEL The synchronized types of changes are set in the first step of database synchronization with the metadata. Synchronization takes place on the side of the database, so containers represent database tables here. It is possible to set whether new database tables will be added, modified ones be modified or superfluous ones be deleted. Fig 10: Database synchronization summary of inconsistencies ascertained In the next step, LIDS AS ascertains existing inconsistencies and displays a summary of them. This concerns a list of database tables, which will be added, modified or removed. After the details have been displayed, a detailed list of inconsistencies for each table is displayed. It is also possible to check the SQL script, which will be launched for removal of each inconsistency. It is now up to the LIDS AS administrator to decide which of the proposed actions is to be performed. The required actions are marked by checking off.

21 LIDS AS CONSOLEC VERSION Fig 11: Database synchronization - detailed list of proposed actions and their selection

22 16 SYSTEM PANEL Fig 12: Database synchronization summary of actions performed In the next step, a well-arranged summary of actions performed is displayed to be checked and confirmed by the LIDS AS administrator.

23 LIDS AS CONSOLEC VERSION Fig 13: Database synchronization settings The final step in synchronization of the database with the metadata is setting of the method of synchronization: Synchronization can be performed directly in the database. This is quick and convenient, but potentially dangerous. Warning: when synchronizing the database with the metadata, DDL commands are launched in the database. Rollback of changes made is not thus possible, even in the event of occurrence of errors during synchronization. The output from synchronization can be exported to SQL script. This can be done independently or combined with direct implementation of changes in the database. It is possible to set whether to end synchronization or continue in the event of occurrence of errors.

24 18 SYSTEM PANEL Fig 14: Database synchronization successful conclusion

25 LIDS AS CONSOLEC VERSION Synchronization of Security with LIDS Metadata We know that it is necessary for the database to be synchronized with the metadata for the correct functioning of the LIDS system. Apart from this, it is necessary to also ensure synchronization of security with the metadata. LIDS is a system with elaborate management of access rights and requires that basic metadata objects (feature types, their attributes, security codelists,...) are correctly registered in security, i.e. in database tables with SEC prefix. Inconsistency of metadata and security mostly exhibits itself in the user not being able to actively work with some data or not being able to see it at all. For detection of problems with security, it is possible to use a user with id = 0, after installation the login/password is administrator/berit. Access rights are not evaluated for this user and any possible problems or inconsistencies in security do not occur with him. Two buttons, Compare and Synchronize, are used for synchronization of security with LIDS metadata. Whereas Compare only detects inconsistencies and records them into a log file, Synchronize modifies registration in security. Synchronization of security with metadata can only be launched in privileged mode. Session Monitor Fig 15: System > Session monitor The Session monitor section serves for monitoring currently logged on users. Basic information is displayed in the session list, with the aid of the Detail reference, it is possible to display details about the selected session. A detailed summary of the activity of the given user is especially provided by the list of LIDS AS services called. The time of their performance then serves as a guideline when tuning the system's performance. The selected session can be terminated from its displayed detail by the administrator using the Invalidate session button.

26 20 SYSTEM PANEL If the session list is confusing, only that sessions that interest you can be filtered out from it using the Filter sessions and Clear filter buttons. Sessions can be filtered by IP address of the remote computer, user name or identification of the database session. Fig 16: Detail of the selected session

27 Chapter 3 Project Panel

28

29 LIDS AS CONSOLEC VERSION Project Panel The Project panel serves for basic manipulation with the LIDS-project within LIDS AS enables the project to be started, stopped or started in the privileged mode as well as manipulating with its configuration files, backdrop maps, documentation and LIDS Browser application settings. Project Info Fig 17: Project > Project info The Project info section displays basic information about the LIDS-project. Using appropriate buttons, it is either possible to start the server in the privileged mode (Run in privileged mode button), or to stop the project (Stop project button), or to start it in the standard mode (Start project button). The privileged mode is used for administering LIDS AS. The server does not allow standard client services in this mode. In order to implement more serious administration action such as updating of metadata or synchronization of the database with the metadata, LIDS AS must be switched to privileged mode. After being launched, LIDS AS is in suspended project status, i.e. metadata is not yet downloaded. LIDS AS switches to standard status automatically when any client service is first called up. When starting a project from the LIDS AS console, it is possible to tick off the pertinent checkbox to force a complete check of metadata. Warning: due to time demands posed by the checks, metadata is not checked during regular operation, LIDS AS may thus be operated for a relatively long period of time with incorrect metadata.

30 24 PROJECT PANEL The Metadata files section displays references to metadata files of the LIDS-project (Model.xml, Presentation.xml, Resource.xml, Thematization.xml, Tool.xml and Option.xml). The files can be displayed using the references. The Validate and update project button serves for validation and uploading the new metadata files into LIDS AS. The Download project files button allows the easy downloading of all project (not only metadata) files together from LIDS AS to a selected directory the files are compressed into the single Project.zip file. The Metadata extension files section displays references to metadata files for individual extensions of LIDS AS. The files can be displayed using the references. Validate and upload buttons serve for validation and uploading new extension files into LIDS AS. The Project resources section displays actual timestamp of project resources. The Refresh timestamp button serves for updating time stamp and forcing updating of all LIDS-project sources in the client applications. This update must be performed after any change to project sources. Project sources list can be switched between displaying of all project sources (Show all resources option is checked) and displaying of missing sources that are registered in project metadata but not stored on LIDS AS. Individual project sources can be added or replaced using Upload buttons. Upload resources button in the Upload resources from archive part can be used to load sources in bulk from a zip archive. Directories Fig 18: Project > Directories The Directories section serves for displaying and setting the paths to project directories. The existence of the entered directories is checked and the pertinent information displayed for each. The paths can be changed to others which are required, by filling in the Directory item followed by saving the settings using the Save button or Save changes button.

31 LIDS AS CONSOLEC VERSION Backdrops Fig 19: Project > Backdrops The Backdrops section serves for setting the paths to directories with LIDS-project backdrop maps. The existence of the directories is checked and the pertinent information displayed for each. The Show reference is used to display a list of layers defined for individual types of LIDS-project backdrop maps. The hierarchical layers can be created or regenerated with the aid of the Run rebuild button. Regeneration of a hierarchical layer is usually an operation that poses great demands on time. But it is not necessary to regenerate the whole layer every time. If only part of the input files were added or changed, it is possible to limit generation only to them. If generation was prematurely interrupted for any reason, it is possible to relaunch it later with the Recovery option. In this case, previously generated files are preserved and are not regenerated again. Documentation The Available documentation section serves for creating and displaying of the documentation of the LIDS data model in particular supported languages. The selected language version of the documentation is created using the Build selected button.

32 26 PROJECT PANEL The Download documentation button allows the easy downloading of complete documentation from LIDS AS to a selected directory the files are compressed into the single Documentation.zip file. Fig 20: Project > Documentation The documentation can be displayed in HTML-format using the View file references. The selected documentation of the data model of the LIDS-project is opened always in a new browser window. Fig 21: Documentation of the LIDS-project

33 LIDS AS CONSOLEC VERSION Browser Fig 22: Project > Browser The Browser configuration section displays reference to LIDS Browser application. The Configure LIDS Browser button serves to reconfigure the LIDS Browser application function applies changes from actual configuration file Browser.xml. The Download configuration button allows the easy downloading of project configuration files LocatorMap.xml, MainMap.xml and BrowserConfig.xml from LIDS AS to a selected directory the files are compressed into the single Context.zip file. The WMS layers part contains a list of all currently available WMS layers. When mentioned in the browser.xml metadata file, they start to be available in the LIDS Browser application. Precaching can be set for individual WMS layers; LIDS AS does not then need to generate them for every client request, but uses the data prepared in the cache. Caching is not suitable for all types of data. It is especially suitable for static vector layers and for external WMS layers. On the contrary, it is absolutely unsuitable for vector data with dynamic symbology dependent on scale and for data with different access rights for different users.

34 28 PROJECT PANEL