myWorld

Release Notes
________________________________________________________________________________

2.6
Ubisense myWorld Release Notes

Contents
1 Introduction ........................................................................................................................ 4
1.1 Intended audience ...................................................................................................................... 4
2 Installation ......................................................................................................................... 5
2.1 Product structure modified .......................................................................................................... 5
2.2 Data model install localised ........................................................................................................ 5
2.3 Default configuration modified .................................................................................................... 5
2.4 Database upgrade ...................................................................................................................... 5
3 Server ................................................................................................................................ 7
3.1 Authorisation configuration modified........................................................................................... 7
3.2 Feature model extended ............................................................................................................. 7
3.3 Internals model re-worked .......................................................................................................... 7
3.4 CSV now default file format ........................................................................................................ 8
3.5 Layer groups added .................................................................................................................... 8
3.6 External search added ................................................................................................................ 8
3.7 New layer type myWorld External ............................................................................................... 9
3.8 Partial replication added ............................................................................................................. 9
3.9 Module structure modified .......................................................................................................... 9
3.10 Other changes .......................................................................................................................... 10
4 Client ............................................................................................................................... 11
4.1 Internals viewer enhanced ........................................................................................................ 11
4.2 Layer groups supported ............................................................................................................ 11
4.3 Search enhanced ...................................................................................................................... 11
4.4 Phone layout re-instated ........................................................................................................... 11
4.5 Other changes .......................................................................................................................... 12
5 Configuration pages ......................................................................................................... 13
5.1 Features page modified ............................................................................................................ 13
5.2 Layers page extended .............................................................................................................. 13
5.3 Applications page extended ...................................................................................................... 13
5.4 Replication page extended ....................................................................................................... 13
5.5 Other changes .......................................................................................................................... 14
6 Tools ................................................................................................................................ 15
6.1 myw_db command enhanced ................................................................................................... 15
6.2 myw_tilestore command ........................................................................................................... 16
7 Smallworld ETL................................................................................................................ 17
7.1 Glue methods changed ............................................................................................................. 17
7.2 Internals transform changed ..................................................................................................... 17

Page 2 of 26
Ubisense myWorld Release Notes

7.3 Feature export modified ............................................................................................................ 18

7.4 Tile export modified................................................................................................................... 18
7.5 Layer definition export added ................................................................................................... 18
8 JavaScript API ................................................................................................................. 20
8.1 API modified .............................................................................................................................. 20
8.2 Plugins can now publish buttons .............................................................................................. 20
8.3 External feature access re-worked ........................................................................................... 20
8.4 Geocoder now customisable .................................................................................................... 21
8.5 Tab control now supports dynamic add/remove ....................................................................... 21
8.6 Minification command modified ................................................................................................ 21
8.7 Custom controller registration changed .................................................................................... 21
8.8 Client re-caching supported ...................................................................................................... 21
8.9 Other changes .......................................................................................................................... 22
9 Documentation................................................................................................................. 23
10 Upgrading ........................................................................................................................ 24
10.1 Upgrading your myWorld server ............................................................................................... 24
10.2 Upgrading your Smallworld ETL configuration ......................................................................... 24
10.3 ETL post-upgrade actions ......................................................................................................... 24
10.3.1 Using the old internals model..................................................................................................... 24
10.3.2 Migrating to the new internals model ......................................................................................... 25

Page 3 of 26
Ubisense myWorld Release Notes

1 Introduction
This document provides a summary of the major changes in release 2.6 of
myWorld.

1.1 Intended audience

This document is intended for administrators and customizers with a detailed
technical knowledge of myWorld.

Page 4 of 26
Ubisense myWorld Release Notes

2 Installation
The following changes relate to installation and upgrade.

2.1 Product structure modified

The product structure is modified at this release. All core code and resources are
now located under sub-directory WebApps/myworldapp/core and are further
subdivided between server code (server) and client code (public).
This change should be transparent in day-to-day operation. It does impact a small
number of configuration and customisation processes. These impacts are
described in detail below.
The change is intended to clarify the division between core code (which should not
be edited) and modules (which can be customised).

2.2 Data model install localised

The external name of objects in the default configuration (note feature, background
maps, default roles, ...) can now be translated automatically at install time. This
avoids the need to manually update the configuration after installation.
Translation is enabled by supplying the name of a language pack in the --lang
option of the myw_db install command.
Contact Ubisense support for details of available language packs.

2.3 Default configuration modified

The following layers are no longer included in the default configuration created by
myw_db install:
1. Google Weather and Google Clouds: These layer definitions are no longer
useful as Google has terminated the services they access.
2. Internals: This layer definition no longer makes sense in the new internals
model (see below). Instead, layer definitions for internals objects can be
imported from ETL layer dumps or created manually when required.
These changes affect new installations only. Existing layer definitions are not
modified.

2.4 Database upgrade

There are data model and other database changes at this release, including:
 Modifications to DD and geometry index tables to support secondary
geometries
 New tables to support layer groups
 New fields to support external search
 New tables and fields to support partial replication
Page 5 of 26
Ubisense myWorld Release Notes

A database upgrade is provided to make these changes. You must upgrade your
database using the myw_db command line tool.
See Upgrading for more details.

Page 6 of 26
Ubisense myWorld Release Notes

3 Server
The following server-side changes have been made at this release.

3.1 Authorisation configuration modified

myWorld auth engines and other authorisation parameters are now configured in
myworldapp.ini file (rather than in server_config.json). File server_config.json is
removed at this release.
This change is intended to simplify system configuration and to enable serving of
multiple databases from a single installation.
See product document Installation & Configuration for details of the new
authorisation configuration mechanism.

3.2 Feature model extended

The myWorld data dictionary has been extended to support features with
secondary geometries. These geometries form part of the new internals model
(see below). For example, an access_point feature might have a primary geometry
in the geographic world and a secondary geometry giving its position in a floorplan
world.
A secondary geometry is declared by adding a field of type point, linestring or
polygon in a .def file. Unlike the primary geometry (the_geom) you are free to
name it what you want. A feature can have multiple secondary geometry fields.
Each must be accompanied by a string field that holds the name of the world in
which the geometry is located (a geometry world name field). Secondary geometry
definitions are normally generated automatically by the ETL based on information
configured in Magik glue code.
Note: Each geometry of a myWorld feature should normally be located in a
different world. Secondary geometries are not intended for modelling multiple
geometric representations of the same feature in the same world or for holding
separately locatable labels within a single world.

3.3 Internals model re-worked

The internals model has been re-worked to support nested internals and features
with multiple associated worlds (for example, equipment racks with front and back
views). Main features of the new model are:
 A feature can 'own' one or more internal worlds. For example, a building
might own a floorplan world. Owned worlds are identified by secondary
geometries whose world name match the object's URN. The secondary
geometry also defines the initial view for the world.
 Other features can have primary or secondary geometries in the owner's
worlds. For example, an equipment rack might have a footprint geometry
in the building's floorplan world. For features located solely in internal
worlds, the system uses world ownership to infer containment.

Page 7 of 26
Ubisense myWorld Release Notes

 Internals worlds are grouped into world types depending on the kind of
drawing they represent. For example, a telecoms database might have
world types floorplan, terminal enclosure, rack front view and rack back
view.

 Each world type has an associated layer definition that controls rendering
and selectability when the world is displayed. Rendering can be via tiles or
vectors. The association between the layer and its world type is made
using the layer definition category field.
The old internals model based on a myw_internal_world_view field and a single
Internals layer is still supported but is no longer recommended. If you use internals,
you should consider migrating to the new internals model at this release. Contact
Ubisense support for details of the migration process.
The new internals model is described in detail in product documents myWorld ETL
for Smallworld and Installation & Configuration.

3.4 CSV now default file format

Comma-separated value format (CSV) is now the recommended file format for
bulk feature data (rather than JSON). CSV is faster to generate and more compact
than JSON, supports secondary geometries without extension and is supported by
native database tools. It is now the default output format for ETL feature export and
the myw_db dump operation.

The myw_db command continues to support dump and load of JSON files and the
server REST interface continues to use GeoJSON for feature data exchange.
Note, however, that these use a myWorld-specific extension to the GeoJSON
format to represent features with secondary geometries (since the GeoJSON
standard does not support multiple geometries).
You should consider moving you ETL feature export to CSV at this release.

3.5 Layer groups added

myWorld now supports grouping of layers for presentation in the client GUI. This
can improve usability in installations with large numbers of layers. A layer group is
presented as an expandable tree in the client, allowing users to manipulate the
visibility of the group as a whole and its individual components.
Two types of layer group are supported; exclusive (in which only one member of
the group is displayed at any time) and non-exclusive (in which each member can
be controlled independently).
Layer groups are managed using a new tab Groups in the Layers configuration
page.

3.6 External search added

myWorld now supports feature search in WFS and other external layers. External
searches are presented to the user as additional Query items in the search

Page 8 of 26
Ubisense myWorld Release Notes

autocomplete suggestions. Selecting the item causes the query to be sent to the
external system and its results displayed in the Details tab.
To enable search for an external layer, add a Datasource parameter in your layer
definition. This can be done using the Layers configuration page. See help text on
that page for more details.
Note: The Datasource parameter was called Select Spec in previous releases.

3.7 New layer type myWorld External

There is a new layer type myWorld External for accessing features from a different
myWorld server. This is intended primarily for displaying data from the master
database when working 'online' in a Native App.
A myWorld External layer supports rendering, selection and search. It can be
mapped to either a myWorld Tile layer or myWorld Vector layer in the external
database. Drawing styles and DD information for features in the layer are
automatically retrieved from the external database.
Client access is via REST calls to the external server. The username and
password for this access are configured as part of the layer's Datasource
parameter.
For more details see help text in the Layers configuration page.

3.8 Partial replication added

myWorld replication now supports creation of extracts limited to a specific sub-set
of feature types and tile files. This can be useful for creating task-specific replicas
(e.g. a replica containing data for outside plant only) and in custom replica
synchronisation strategies.
Partial replication is enabled by passing a table_set name to the myw_db
extract command. Table Sets are configured using a new tab in the Replication
configuration page. The table_set parameter is optional; if omitted, extraction
behaviour is as in previous releases.
See Replication and Offline Working in product document Installation &
Configuration for more details.

3.9 Module structure modified

There are a number of changes to the custom module (and other modules) at this
release:
1. The location for custom controllers within the module has changed.
Controller code must now be placed in subdirectory
<module>/server/controllers rather than in <module>/controllers.
2. The Python call used to register controller routes in routing.py has
changed. See Custom controller registration changed below for more
details.

Page 9 of 26
Ubisense myWorld Release Notes

3. The custom module must now contain a version_info.json file in its root
directory. This file is used in the construction of a 'bust' string for
JavaScript caching. See Client re-caching supported below for more
details.
You may need to update your custom module for these changes.

3.10 Other changes

Other changes at this release are:
1. Google licence configuration: The mechanism for configuring you Google
licence client and channel IDs has changed. This information is now
entered using a database setting (rather than by editing an HTML
template). See document Installation & Configuration for more details.
2. Query against null: It is now possible to test for null field values in query
definitions, for example to define a query "signal_loss <> null"

Page 10 of 26
Ubisense myWorld Release Notes

4 Client
The following changes have been made to the JavaScript application at this
release.

4.1 Internals viewer enhanced

The internals viewer has been enhanced to support nested internals and features
with multiple geometries.
The viewer now shows a separate tab for each geometry of the current feature
(labelled with the view's world type). Individual views can be expanded to fill part of
all of the map area and used to select objects that may themselves contain
internals. Expanded views are placed on a stack and can be shrunk back to their
original size if desired.

4.2 Layer groups supported

The Layers tab now supports display of layer groups. These are presented as an
expandable tree item.
The user can change visibility of the group as a whole or its individual components
using checkboxes. The state of layers within the group can be saved in bookmarks
and layer lists, as with 'top level' layers.

4.3 Search enhanced

Search functionality has been enhanced as follows:
1. Algorithm improved: The search algorithm has been improved and
simplified. All searches now match using the same algorithm, regardless of
the number of terms entered. (In previous releases, searches containing
more than two terms were treated as a special case.)
2. Performance improved: The performance of search in large databases has
been improved.
3. External search added: Search autocomplete suggestions can now include
queries on external databases. See above for more details.

4.4 Phone layout re-instated

Phone layout is re-instated at this release.
As in earlier releases, the application automatically selects phone layout if device
width is below a pre-defined threshold. Users can also select a layout explicitly
using a layout parameter in their myWorld URL.
Note that phone layout continues to offer limited functionality compared with
desktop layout. For example, it does not support editing of features or viewing of
internals.

Page 11 of 26
Ubisense myWorld Release Notes

4.5 Other changes

Other changes at this release are:
1. New button Clear selections: The Details tab toolbar includes a new button
Clear selections that resets the current selection.
2. JavaScript re-cache automated: The server can now force clients to
automatically reload their JavaScript code after a software upgrade. This
'bust' mechanism removes the need to users to clear their browser cache
manually. See Client re-caching supported below for more details.

Note: Since previous versions of the client did not include a 'bust'
mechanism, users may still have to clear their cache manually when
moving to myWorld 2.6

Page 12 of 26
Ubisense myWorld Release Notes

5 Configuration pages
The following changes have been made to the configuration pages at this release.

5.1 Features page modified

The Features configuration details page has been modified as follows:
1. The Groups tab has been re-worked to improve usability.
2. The Stored Fields tab has been extended to includes geometry fields.
3. The Available Fields list used for drag-and-drop no longer includes
geometry and world owner fields.
For more details see Installation & Configuration.

5.2 Layers page extended

The Layers configuration page has been extended as follows:
1. There is a new tab Groups for managing layer group definitions.
2. The is a new layer type myWorld External for accessing layers from other
myWorld servers (see Server above)
3. In WFS and custom layer definitions, field Select Spec is renamed
Datasource. This parameter now controls both selection and search
behaviour.
For more details see Installation & Configuration.

5.3 Applications page extended

The Applications configuration page has been modified as follows:
1. The details page now allows you to grant an application access to layers of
any category (rather than just background maps and overlays).
This change is primarily to support the new internals model. It may also be useful
for layers containing system level features that are not directly accessible to users.

5.4 Replication page extended

The Replication configuration page has been extended as follows:
1. There is a new tab Table Sets for configuring table set definitions. These
are used in partial replication (see Server above)
2. The Extracts tab includes addition information on the Region and Table
Set used to create each extract.
3. The Replicas tab includes additional information on the most recent
download made for each replica.
For more details see Installation & Configuration.

Page 13 of 26
Ubisense myWorld Release Notes

5.5 Other changes

Other changes at this release are:
1. JSON editor: The Settings (Advanced) and Layers pages now provide a
specialised editor for JSON parameters. Facilities provided include syntax
checking and automatic text formatting.

Note: This functionality is not available on Internet Explorer 8.

Page 14 of 26
Ubisense myWorld Release Notes

6 Tools
The following changes relate to the command line tools.

6.1 myw_db command enhanced

The following changes have been made to basic myw_db operations at this
release:
1. Operation install supports an new option --lang. This can be used to
select a language pack for localising the default configuration.
2. Operation list supports new values layer_groups, table_sets and
rights for the what parameter.

3. Operation load supports new file formats .table_set, .layer_group and

.rights.
4. Operation dump supports new values layer_groups and table_sets
for the what parameter.
5. Operation dump option --format now supports modifiers that control
geometry encoding and other file properties. For example, format
csv(wkt) outputs data with geometry encoded as Well Known Text (rather
than Extended Well Known Binary).
6. Operation dump now outputs feature data in format csv(ewkb) by default
(that is, CVS with geometry encoded in PostGIS Extended Well Known
Binary).
7. Operation dump option --compact is withdrawn at this release. Use
--format json(compact) instead.

8. When using operation load to import feature data from JSON, fields with
a value null in the JSON file are now set to NULL in the database. (In
previous releases such fields were set to their default value, which could
lead to unexpected behaviour.)
In addition, the following replication-related operations have been modified.
9. Operation extract takes new optional parameters table_set and name.
These are used in partial replication.
10. Operations export and import now export feature data as CSV (rather
than JSON).
11. Operation import now supports import of updates from a single replica
(or set of replicas) via a new optional argument replica.
12. Operation import now only checks for updates from 'live' replicas. This
can improve performance if you have a large number of terminated
replicas in your master database.
13. Operation list replicas --full now includes information on shard
usage and most recent download for each replica.
For more details use --help for the operation of interest.

Page 15 of 26
Ubisense myWorld Release Notes

6.2 myw_tilestore command

There are no changes to the myw_tilestore command at this release.

Page 16 of 26
Ubisense myWorld Release Notes

7 Smallworld ETL
The following changes have been made to the myWorld ETL for Smallworld
component at this release.

7.1 Glue methods changed

There are various changes to glue methods at this release to support the new
internals model:
1. New methods: Three new glue methods are introduced:
myw_secondary_geometries
myw_internal_worlds
myw_geographic_location
All these methods have backstop implementations and only require
subclassing on internals objects and world owners. Their use is described
in detail in myWorld ETL for Smallworld.

2. Deprecated methods: The following are no longer recommended but can

still be used if you opt to continue with the old internals model:
myw_internal_dataset_world
myw_internal_world_scaling_factor

3. Withdrawn methods: The following glue methods are now obsolete (are
replaced by parameters in your internals layer definitions):
myw_internal_tiling_config
myw_internal_world_ace_name
myw_internal_world_buffering_factor
myw_internal_world_max_scale
myw_internal_world_min_scale
To avoid confusion, Ubisense recommend removing the obsolete glue
methods from your configuration.

4. Changed methods: The signature of method

myw_change_provokes_tile_redraw?() has been extended to support
returning a set of worlds which need re-rendering.

Product document myWorld ETL for Smallworld explains the signatures and use of
all glue methods in detail. It also contains a new section dealing specifically with
the process of exporting internals data. Section Upgrading below explains the
minimum steps required to port you ETL configuration at this release.

7.2 Internals transform changed

The default formula used to compute nominal geographic coordinates for objects in
internal worlds has been modified. This change improves processing of internals
objects in myWorld spatial searches and spatial extractions.

Page 17 of 26
Ubisense myWorld Release Notes

If you are upgrading from a previous release you will need to re-export all your
internals features and tiles for this change. Alternatively, you can revert to the 2.5
formula by setting the following shared variable in your glue code or image build:
myw_etl_settings.internal_world_origin_method << :geometry_bounds
See section 4.3 of product document myWorld ETL for Smallworld for more details
on this setting.

7.3 Feature export modified

ETL feature export has been modified as follows:
1. Secondary geometries: The export engine now exports any secondary
geometries and nested internals associated with each feature, based on
the configured glue code.
2. World names: The myw_geometry_world_name field for internals objects
now includes 'world type' prefix, for example:

myWorld 2.5 value: gisYYbuildingYY12345

myWorld 2.6 value: int/gisYYbuildingYY12345

This change is to support the new internals model.

3. Export format: Feature data is now exported in CSV format by default. This
change affects new installations only since export format is stored as an
option in your feature export config XML files.
You should also consider switching your feature exports to CSV format at this
release.

7.4 Tile export modified

ETL tile export has been modified as follows:
1. Internals layers: Internal world tiles are now exported by defining a
separate layer of type Internals (rather than as a side effect of exporting an
overlay). This allows you to set internals tiling parameters (ACE name,
zoom levels, etc) in your config file rather than in glue code. It also permits
use of different tiling parameters for different types of internal worlds.
2. Options withdrawn: Tiling options Include internals? and Internal worlds
only? are withdrawn at this release as they are no longer meaningful.
3. Buffering factor: The Tile Export Tool now allows you to enter any value for
your buffering factor (rather than restricting you to a pulldown list).
See product document myWorld ETL for Smallworld for more details.

7.5 Layer definition export added

It is now possible to export an ETL tile layer definition as a myWorld .layer file.
The information exported includes the layer name, tiled levels and features that are

Page 18 of 26
Ubisense myWorld Release Notes

selectable in the associated ACE. This can provide a useful starting point for
configuring your myWorld layer settings.
You can export layer definitions using the Tile Export Tool and Sync Manager
Dialog.

Page 19 of 26
Ubisense myWorld Release Notes

8 JavaScript API
The following changes have been made to the JavaScript customisation API at this
release.

8.1 API modified

The following non-backwards compatible API changes are made in this release:
1. Toolbar button registration: The mechanism for adding custom buttons to
toolbars has been changed. Plugins now declare buttons which can then
be added to the toolbar (rather than adding the plugin itself). If you have
implemented toolbar button plugins you will need to refactor your code.
See below for more details.
2. External selection: The classes for accessing feature data in external
databases have been re-worked. If you have implemented a custom
ExternalSelection class you will need to modify its subclassing and
registration. See below for more details.
3. Geocoder access: The system geocoder instance is now accessed directly
as a property of the application (rather than via a geocoder plugin). If your
custom code uses the geocoder you will need to update it.
4. Google maps library: The Google Maps Library is now loaded lazily. You
must modify any code that uses GoogleMapsApi to call
myw.googleMapsLibrary.load() and wait for the promise it returns to
resolve before attempting to access the library.
You should review your customisations for impact from these changes.

8.2 Plugins can now publish buttons

A plugin can now expose one or more PluginButton objects via its buttons
property. These buttons can then be added to controls such as the toolbar when
building an application definition.
This change removes the need to implement a separate plugin for each button a
customiser might wish to display on a toolbar. The old mechansim for placing a
plugin directly on a toolbar is no longer supported. Plugin methods
.getToolbarImgSrc(), .getToolbarTitle(), ... .getDivElement() are now obsolete.
For more details see the Customisation Guide and JavaScript API documentation
for PluginButton and Control.

8.3 External feature access re-worked

The classes for accessing feature data in an external database have been
reworked. Class myw.ExternalSelection is replaced by myw.ExternalDatasource
which handles both selection and search. If you have implemented a custom class
for external selection you will need to refactor it to implement interface
IExternalDataSource and register itself in externalDatasources.

Page 20 of 26
Ubisense myWorld Release Notes

For more details see the Customization Guide and JavaScript API documentation
for IExternalDataSource.

8.4 Geocoder now customisable

It is now possible to replace the default geocoding engine (Google) by a custom
implementation. To do this:
 Write a custom class that implements interface myw.Igeocoder

 In your application definition, set the class as the value of

myw.applicationDefinition.Geocoder.
Note that the API for accessing the geocoder from within custom code has also
changed (see above).

8.5 Tab control now supports dynamic add/remove

The TabControl class has been refactored to be more flexible and reusable. It now
provides an API for dynamic addition/replacement of tabs. In addition, a tab
definition now accepts new options removable and draggable. These create a tab
which the user can close or 'tear-off'.
For more details see JavaScript API documentation for TabControl and
tabDefinition for more details.

8.6 Minification command modified

The name and location of the JavaScript minification utility has changed. The utility
is now called build_minified_js and is located in WebApps/myworldapp/core/utils.
Also, the minification utility can now be run on Linux.

8.7 Custom controller registration changed

The location for custom controllers within a module has changed. Controller code
must now be placed in subdirectory <module>/server/controllers rather than in
<module>/controllers.
In addition, the Python call used to register routes in routing.py has changed; you
must call add_routes() rather than make_map().
For more details see the Customization Guide.

8.8 Client re-caching supported

The server can now force clients to refresh their cached JavaScript via a 'bust'
mechanism. This avoids the need for users to manually clear their browser cache
after a software upgrade.
The bust string is constructed from version stamps in core/version_info.json and
modules/custom/version_info.json. Clients cache their JavaScript files against this
string so if it changes their cache is effectively invalidated. Since the bust includes
Page 21 of 26
Ubisense myWorld Release Notes

the core version stamp, future myWorld core software upgrades will automatically
trigger a re-cache. You can also force a bust yourself by changing the version
stamp in you custom module. This can be useful when deploying changes to your
custom code.

8.9 Other changes

Other changes at this release are:
1. A Control can now override methods visibilityChanged() and
invalidateSize() to handle changes in the layout or owning control.
2. Database protocols .getFeatures() and .getFeaturesByValue() now support
the use of null (or empty string) values with '=' and '<>' operators.
For more information see the JavaScript API Documentation.

Page 22 of 26
Ubisense myWorld Release Notes

9 Documentation
The documentation set has been updated to reflect the new features described
above. In addition:
 myWorld ETL for Smallworld now includes step-by-step instructions for
configuring your glue code, with examples. Reference material for glue
code methods has been moved to an Appendix.
 Installation & Configuration documentation has been extended to cover
definition of internals layers. There is also a a new sub-section describing
partial replication.
 The Customization Guide has been extended to cover the publishing of
plugin buttons and configuration of external datasources.
 The User Guide has been streamlined and updated for recent product
changes.

Page 23 of 26
Ubisense myWorld Release Notes

10 Upgrading
This section provides an overview of the upgrade process for this release.

10.1 Upgrading your myWorld server

Upgrading your myWorld server installation involves:
1. Installing the myWorld software
2. Porting your customisations
3. Upgrading your database
These steps are described in more detail in product document Installation &
Configuration.
To upgrade your database use:
myw_db <db_name> upgrade 260

There are no server-side post-upgrade configuration steps at this release.

10.2 Upgrading your Smallworld ETL configuration

Upgrading your myWorld ETL for Smallworld installation involves:
1. Installing the software
2. Updating your images
These steps are described in detail in myWorld ETL for Smallworld.
You may need to perform some ETL post upgrade configuration steps at this
release (see below).

10.3 ETL post-upgrade actions

If your ETL export includes internals data you must modify your configuration after
upgrading. The changes you make will depend on whether you chose to stay with
the old internals model or migrate to the new one.

10.3.1 Using the old internals model

Configuring your system to use the old model is a relatively simple process:
1. Configure settings: In your glue code or image build, set the following
shared variables on myw_etl_settings:

Shared Variable Value

internal_world_origin_method :geometry_bounds
include_internal_world_view_property? _true

These settings ensure that your internals data continues to be output using
the 'old' transform and that world owners continues to be given a
myw_internal_world_view field.

Page 24 of 26
Ubisense myWorld Release Notes

2. Define the int layer: In your tile export configuration, add a new layer
definition int with type internals. This layer will be used to perform internals
tile exports. Its bounds should be copied from a geographic layer (an
overlay). Its ACE name, zoom level and other parameters should be set to
the values that in previous releases came from your glue code. The Tile
Export Tool provides a GUI for performing this configuration.
Note: The layer must be called int since this was the world type used for
pre-myWorld 2.6 exports.
3. Add the int layer to batch jobs: In your Sync Manager control file, add the
int layer to the list of tile exports. This will ensure that it participates in
incremental exports.
Full and incremental exports should now behave as in myWorld 2.5, except that
myw_world_owner_field values will include an int/ prefix (as described in Feature
export modified above). Existing world owner data in the myWorld database is
migrated to the new format by the database upgrade.

10.3.2 Migrating to the new internals model

Migrating to the new internals model is more onerous and involves:
1. Updating your glue code to define secondary geometries for, at least,
world owners.
2. Adding one or more internals layer in your tile export
3. Re-exporting feature and tile data for internals objects and world owners
4. Updating your internals layer definitions in myWorld
The new model does, however, provide functional benefits and greater flexibility in
terms of internals layer configuration.
For a full description of the how to export internals data using the new model see
Section 9 in myWorld ETL for Smallworld.

For assistance with any of the processes above please contact Ubisense support.

Page 25 of 26
Ubisense myWorld Release Notes

For more information

Ubisense contact

Ubisense support desk

St Andrews House, St Andrews Road
Cambridge, CB4 1DL, England
Telephone +44 1223 532670
Fax +44 1223 535167
e-mail [email protected]

Copyright and Legal Notice

Copyright  2015 Ubisense Group plc all rights reserved.

This document contains confidential and proprietary information, and is the property of
Ubisense Group plc.

Reproduction without prior written permission from Ubisense Group plc

is prohibited.
Ubisense Group plc
St Andrews House
90 St Andrews Road
Cambridge CB4 1DL
England UK

Page 26 of 26