Release Notes. TopoOptimiser Oracle Database Module. Version /04/2018. t: +44 (0) e: w:

Transcription

1 Release Notes TopoOptimiser Oracle Database Module Version /04/2018 t: +44 (0) e: w: wwwmisoportalcom miso is a trading division of Dotted Eyes Ltd Dotted Eyes Ltd is registered in England Registered office: Northwood Street, Birmingham, B3 1TX Company registration number: Vat Number:

2 Contents Introduction 3 Overall capability of the product 3 Expected Usage 3 System requirements 3 Dependencies and Prerequisites 3 Database Connectivity and Support 4 Installing the Client 4 Requirements 4 Installation Process 4 Customise Installation Location 5 Connection to Database 5 Oracle Permissions 5 Upgrading 6 Users with Local Admin Rights 6 Users without Local Admin Rights 6 Uninstalling 6 Working in Offline Mode 7 Getting Offline 7 Getting Back Online 7 Scheduling Apps 7 Notes on this release 8 Updates 8 New Features 8 Known Issues 8 Workarounds 9 TOOM212I1 9 TOOM212I2 9 TOOM212I3 9 TOOM212I4 9 TOOM212I5 9 2

3 Introduction This document provides information about the processes, requirements and known issues that are relevant to: TopoOptimiser Oracle Database Module V2121 Overall capability of the product The TopoOptimiser Oracle Database Module (TOOM) consumes the native GZ files produced by Ordnance Survey (OS) for its OS MasterMap (OSMM) Topo Layer product and adds the styling and optimisation attributes from the standard TopoOptimiser App It then loads the entire dataset into a spatial Oracle Database in an optimised manner TOOM can then extract the data from the Database according to a range of parameters and output in fully styled data files in TAB, DWG and DXF formats as well as un-styled data files in SHP Expected Usage TOOM is expected to be used to maintain a current and accurate version of OSMM Topo Layer in an Oracle Database It is then expected that multi-user applications connect to the Database to consume the data It is expected that a small number of users are given direct access to the Database via the Database administrator It is not expected that large number of users are given direct access, instead best practice would see them served via third-party applications (eg Geoserver using WMS/WFS services) or GIS file outputs System requirements This product has been tested on the following Operating Systems: Windows 10 Windows 81 Windows 7 The following minimum hardware specification is recommended: 8Gb RAM 4 core availability Dependencies and Prerequisites The TOOM requires access to a valid and current FME Database licence in order to run; this licence can be fixed or floating Minimum FME requirements: 3

4 FME Database version (Build 17291) TOOM version 2121 is only supported on the Dataflow Player v210 and above This will need to be updated before attempting to licence or run the module Database Connectivity and Support TOOM supports the following ORACLE Database servers: Oracle 11g release 2 + o With Spatial enabled Installing the Client Requirements An internet connection will be required for the initial installation and login process Local administrator rights are required during the initial installation Once completed, DataFlow can be used as needed by users with restricted access rights Installation Process 1 Download the DataFlow Player through the DataFlow Store The user will need to log into their misoportal account in order to access the download area 2 Launch the installer 3 Once installed, launch the DataFlow Player 4 The user can then log into DataFlow using their misoportal account credentials Initial launch may take a few minutes while the Player configures 5 DataFlow will automatically check for any necessary updates If updates are available, DataFlow will ask whether or not the user wishes to proceed with their installation (see Upgrading guidance below) 6 The Player is now ready for use 4

5 Customise Installation Location 1 Download the DataFlow Player and launch as stated above 2 Select the Options button to browse to and confirm the custom installation location 3 Once installed, launch the DataFlow Player 4 The user can then log into DataFlow using their misoportal account credentials Initial launch may take a few minutes while the Player configures 5 DataFlow will automatically check for any necessary updates If updates are available, DataFlow will ask whether or not the user wishes to proceed with their installation (see Upgrading guidance below) 6 The Player is now ready for use Connection to Database The connection can be established within the TOOM Module 1 Open Topo Optimiser 2 Navigate to the Admin section and Configure Repositories and Destinations 3 Click Add a Repository 4 Select ORACLE Server and fill in the connection details 5 Click Test Connection to see if the connection details are correct 6 Save the Repository Oracle Permissions The Oracle user needs to have the role of Connect The Oracle user requires permission to: Alter any index Alter any indextype Alter any table Create any index Create any indextype Create any sequence Create any table Create session Delete any table Drop any index Drop any indextype Execute any procedure Insert any table Select any dictionary Select any table Unlimited tablespace 5

6 Upgrading The DataFlow Player contains an updater which checks for updates to the Player on login whilst in online mode Installation of updates requires Local Admin Rights If updates are available, the user will be asked to confirm whether they have the required Local Admin Rights to perform installation Users with Local Admin Rights To install updates: Follow the instructions when logging in Users without Local Admin Rights All DataFlow Apps and Modules have been designed so that an ICT Administrator can download the application, test it and then apply it 1 The ICT Administrator uses the User credentials to download the Player and the App 2 The ICT Administrator tests the Player, App and Module This will download an encrypted zip file containing the update files In order to access this, please contact Miso 3 The ICT Administrator wraps the Player, App and Module and applies it to the desktop using the Dataflow Player 4 The User logs on and authenticates Uninstalling 1 Uninstall DataFlow using Programs and Features within the Control Panel 2 Manually remove any files that remain after uninstalling Default installation location: a Navigate to the following location: C:\Apps\miso b Delete the two folders: C:\Apps\miso\DataFlow and: C:\Apps\miso\FME 6

7 Working in Offline Mode Getting Offline Offline Mode can be used when a persistent internet connection in not possible This requires a user-specific offline code which can be requested using the address associated with the user misoportal account here: To use DataFlow in offline mode: 1 Launch DataFlow 2 Select Always Offline Code to reveal further options 3 Enter offline code and log into DataFlow to launch the application While in offline mode, DataFlow will be unable to detect or install new updates Apps that connect to external websites or APIs will not function in offline mode and will be unavailable to use Getting Back Online To bring DataFlow back online when an internet connection is again present: 1 Launch DataFlow 2 Select Always Offline Code to reveal further options 3 Remove offline code and log into DataFlow to launch the application Scheduling Apps TOOM cannot be scheduled 7

8 Notes on this release Updates Ref Name Description TOOM212U1 Load to Oracle Improved creation of spatial metadata when loading into Oracle and indexing This now allows for viewing the data held within the database with a GIS application TOOM212U2 Extract to GIS Files TOOM212U3 Extracting Text Layer Enhanced indexing of tables within Oracle for extracting to tiled GIS files Improved handling of text layers that contain special or combined characters (for example ä, é, ã) so these can be extracted fully New Features There are no New Features in this version Known Issues Ref Name Description TOOM212I1 TOOM212I2 Catalogue Destination Table Truncation Extract with a Custom Parameter File Table name conflict when extracting the Catalogue back into the database and choosing to truncate Extracting while using a custom parameter file that creates a single output table from multiple attribute tables will cause the extract process to fail TOOM212I3 Catalogue Extract The catalogue table will not be created when extracting to tiled MapInfo Tab, MapInfo Mif-Mid or ESRI Shapefile format TOOM212I4 TOOM212I5 MapInfo Tab Seamless Table Creation Destination Table Truncation Extracting to tiled MapInfo Tab format will intermittently fail to create seamless tables TOOM is currently unable to truncate user tables when extracting into an existing Oracle tablespace 8

9 Workarounds TOOM212I1 This issue will affect users who wish to extract back into the Oracle database, using the same Oracle User In doing so the destination tables will be truncated and the information held in the Catalogue table will be lost To avoid this loss of data the Catalogue table cannot be extracted back into the database TOOM212I2 Using a custom parameter file that creates a single output table from many attribute tables is not supported within Topo Optimiser v2121 or below For example, creating the output table Vegetation from features held within Topographic Area, Topographic Point and Boundary Line will cause the extract to fail In order to avoid this error it is advised that output tables are created from a single attribute table in a one-to-one relationship TOOM212I3 When extracting from Oracle into tiled MapInfo Tab, MapInfo Mif-Mid or ESRI Shapefile format the catalogue file will not be created As a workaround please contact Miso and we will provide a secondary FME workbench to manually extract this file TOOM212I4 This is an intermittent issue that occurs only when creating MapInfo Tab files in a tiled format In the event that these seamless tables are not created, please contact Miso and we will provide a secondary FME workbench to manually create these TOOM212I5 This issue will affect users who wish to extract back into the Oracle database to an existing tablespace The data held within the destination tablespace will not be truncated which may result in the duplication of data A solution to this issue is currently in development As a workaround, please manually drop or truncate these tables within Oracle first before completing the load 9