Below we describe the actions to be taken in order to transfer the dLibra system server from one (computer) server to another. The servers can operate under the control of any operating systems. Also, it does not matter whether they are virtual servers or physical machines.

It is assumed that all services of the dLibra system server are installed on the server. You will find more information about the services of the dLibra system server in chapter 13. Scaling the dLibra System.

Transferring the dLibra Server Application and Data

Server configuration:

Parameter

Source server

Target server

The type of the operating system

Linux

Windows

The location of the dLibra server applications

/dlibra/dlibra-server

c:\dlibra\dlibra-server

The location of the directory with the content of digital objects

/dlibra/content/files

c:\dlibra\content\files

The location of the directory with search indexes

/dlibra/content/index

c:\dlibra\content\index

The location of the directory with a copy of search indexes

/dlibra/content/index_backup

c:\dlibra\content\index_backup

The location of the directory with the JPG cache

/dlibra/content/jpg-cache

c:\dlibra\content\jpg-cache

The location of the directory with the ZIP cache

/dlibra/content/zip-cache

c:\dlibra\content\zip-cache

The host IP address with the dLibra server

150.254.100.1

150.254.100.2

Before beginning the migration of the dLibra system, the target server should be configured in a similar way to the source server. First of all, Java Runtime Environment (JRE) 1.8 from the Oracle company (formerly Sun Microsystems) must be installed, and connections must be enabled on the ports required by the dLibra system server.

  1. Turn off the dLibra system on the source server.
  2. Copy the server application directory of the dLibra system server from the source server to the target server.
  3. Copy the directories with: the content of digital objects, search indexes, and a copy of search indexes. The ZIP and JPG cache directories do not have to be copied.
  4. Update the configuration files:
  • c:\dlibra\dlibra-server\conf\cs\service.properties:
    • contentDirectory=c:\\dlibra\\content\\files
    • zip.cachePath=c:\\dlibra\\content\\zip-cache
    • jpg.cachePath=c:\\dlibra\\content\\jpg-cache
  • c:\dlibra\dlibra-server\conf\lucene.properties:
    • indexDirectory=c:\\dlibra\\content\\index
    • indexBackupDirectory=c:\\dlibra\\content\\index_backup

If the network address (IP or domain address) of the target server is changed, additional actions must be carried out. If the address is not changed or is not used in the configuration, those actions should be skipped.

  1. In file c:\dlibra\dlibra-server\conf\server.xml, update the server address – attribute serverHost of the server element. In our case:

    <dlibra serverHost="150.254.100.2" serverPort="10051">
  2. In the database, in table SYS_SERVICES, update the values in column SER_HOST for the records of the moved services (all except for the ss service available on the 127.0.0.1 host and except for the ps service).
  3. In the Reader Application, in file dlibra-webapp/WEB-INF/conf/services.properties, update the value of parameter ss.url, by changing it to //150.254.100.2:10051/ss

Having carried out those actions, we can start up the dLibra system server on the new server, in accordance with the description in chapter 01. Starting up the dLibra System Server.

Moving the Database

If the database has also been moved, the connection parameters in file c:\dlibra\dlibra-server\conf\database.properties should be updated.

  • No labels