Google Earth Enterprise Documentation Home | Fusion administration

Publish databases using disconnected publishing

If you want to publish databases on a server that does not have a network connection to your Google Earth Enterprise Fusion workstations, you can create a database that can be output to portable media, which can then be pushed and published to GEE Server.

A large database can be copied to portable media and loaded onto the server using geserveradmin commands, saving the time and bandwidth required to send terabytes of data over the network. In addition, you can also create deltas for the same databases, which can then be sent over the network.

Before you begin

To use the disconnected publishing service, you need to install the GEE Server - Disconnected Add-on, which you can add by running the installation process and choosing Custom as the installation type.

Prepare a disconnected database

Before creating a disconnected database, you can estimate the space required to store the disconnected database by running gedisconnectedsend with the --report_size_only option.

To estimate the size of a disconnected database:

1. From the command line, specify the database that you want to publish with the --report_size_only flag:

   # gedisconnectedsend --report_size_only --sendpath \
/gevol/assets/Databases/test.kdatabase/gedb.kda/ver001/gedb

To create a disconnected database:

1. Create an output directory on your portable media, which you will specify when you create the disconnected database.

   rm -rf /media/ddb/test_ver001/

   mkdir -p /media/ddb/test_ver001/

In this example, /gevol/assets/Databases/test.kdatabase/gedb.kda/ver001/gedb/ is the path to the gedb directory of the disconnected database.

Prepare delta disconnected databases

The disconnected database command includes the option, --havepath or --havepathfile, to create a delta disconnected database, based on different versions of the same database. To create the delta, the assetroot of the GEE Fusion machine must store the versions of databases, as reported by geserveradmin --listdbs on the GEE Server machine, from which the delta disconnected database is created.

When publishing from a GEE Fusion machine, in this example, machine_one, to a disconnected GEE Server machine, in this example, machine_two, verify the list of versions of the disconnected database for which you want to create the delta:

For example, on machine_two:

geserveradmin --fusion_host machine_one --listdbs > /home/user_name/ddb/dblist_server_host

On machine_one, create the delta disconnected database using the --havepathfile option:

gedisconnectedsend --output /media/ddb/test_ver001/ \

--havepathfile /home/user_name/ddb/dblist_server_host \

--sendpath /gevol/assets/Databases/test.kdatabase/gedb.kda/ver001/gedb

Publish on the remote server host

Connect the portable media to the Server host and mount the drive. In this example, /media/ddb/test_ver001/gevol/assets/Databases/test.kdatabase/gedb.kda/ver001/gedb/ is the path to the gedb directory of the disconnected database.

To publish on the remote server host:

1. Set ownership and permissions for the gedb directory:

   $ sudo chown -R gefusionuser:gegroup ddb/

   $ sudo chmod -R 755 ddb/

2. Register the database on the Server. Specifying the --stream_server_url is optional.

   geserveradmin --fusion_host fusion_host.company.com \

   --stream_server_url http://your_stream_server \

   --adddb \

   /media/ddb/test_ver001/gevol/assets/Databases/test.kdatabase/gedb.kda/ver001/gedb/

3. Push the files to the Server:

   geserveradmin --fusion_host fusion_host.company.com \

   --stream_server_url http://your_stream_server \

   --pushdb \

   /media/ddb/test_ver001/gevol/assets/Databases/test.kdatabase/gedb.kda/ver001/gedb/

4. Publish the database on the Server either using the GEE Server Admin console or on the command line. The GEE Server Admin console Publish dialog includes options to add search, snippet profiles, specify a virtual host, and turn on WMS.

   To publish on the command line:

   geserveradmin --fusion_host fusion_host.company.com \

   --stream_server_url http://your_stream_server \

   --publishdb \

   /media/ddb/test_ver001/gevol/assets/Databases/test.kdatabase/gedb.kda/ver001/gedb/

5. Verify that the database manifests:

   geserveradmin --stream_server_url http://your_stream_server \

   --listdbs

   geserveradmin --stream_server_url http://your_stream_server \

   --dbdetails \

   /media/ddb/test_ver001/gevol/assets/Databases/test.kdatabase/gedb.kda/ver001/gedb

6. Verify the integrity of files in the published database:

   ssh your_server

   /opt/google/bin/geindexcheck --database \

   /gevol/published_dbs/stream_space/your_fusion_host/gevol/assets/

   Databases/test.kdatabase/gedb.kda/ver001/gedb

   /opt/google/bin/geindexcheck --mode all --database \

   /gevol/published_dbs/stream_space/your_fusion_host/gevol/assets/

   Databases/test.kdatabase/gedb.kda/ver001/gedb

   The paths in the examples above were split onto multiple lines for documentation using backslashes. They should be entered on one line when completing your commands.

Symbolic links

Symbolic links are turned on by default in the published databases configuration file, AllowSymLinks=Y in the /gevol/published_dbs/.config, resulting in hard or soft symbolic links being created, depending on the logical volumes of the relevant directories:

• hard-link: the disconnected database folder and published_dbs folder are on the same logical volume.
• soft-link: the disconnected database folder and published_dbs folder are on different logical volumes.
• If the disconnected database folder is in /tmp, the directory files will be copied.

Delete disconnected databases

To delete disconnected databases at their end of life use geserveradmin --deletedb, the same procedure used for databases that are published normally.