Date: Thu, 28 Mar 2024 23:43:59 +0100 (CET) Message-ID: <1004291602.5678.1711665839929@gazella.mgmt.psnc> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_5677_1195766961.1711665839929" ------=_Part_5677_1195766961.1711665839929 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Below we describe the actions to be taken= in order to transfer the reader application 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 mac= hines.
It is assumed that the domain name of the new ser= ver is identical with the name assigned to the old server.
Server configuration:
Parametr |
Source server |
Target server |
---|---|---|
The type of the operating system |
Linux |
Windows |
The location of the reader application | /dlibra/dlibra-webapp-6.0.0 |
c:\dlibra\dlibra-webapp-6.0.0 |
The location of the directory with the cache<= /p> |
/dlibra/webappwork/cache |
c:\dlibra\webappwork\cache |
The location of the directory with JCR | /dlibra/webappwork/jcr |
c:\dlibra\webappwork\jcr |
The location of the directory with the JCR to= be restored |
/dlibra/webappwork/jcr-restore = td> | c:\dlibra\webappwork\jcr-restore = |
The location of the directory with the backup= copies of JCR |
/dlibra/webappwork/jcr-backup | c:\dlibra\webappwork\jcr-backup <= /td> |
The location of the directory with temporary = files |
/dlibra/webappwork/upload/temporary<= /p> |
c:\dlibra\webappwork\upload\temporary |
The host IP address with the reader applicati= on |
150.254.100.1 |
150.254.100.2 |
Before beginning the migration of the dLibra system, the target server s= hould be configured in a similar way to the source server. First of all, Ja= va Runtime Environment (JRE) =E2=80=93 at least in version 1.8 =E2=80=93 fr= om the Oracle company (formerly Sun Microsystems) and a web application con= tainer (Apache Tomcat) must be installed, and connections must be enabled o= n the ports required by the dLibra system server.
seriali= zation.path=3Dc:\\dlibra\\webappwork\\cache
jcr.wor= king.dir=3Dc:\\dlibra\\webappwork\\jcr
jcr.res= tore.dir=3Dc:\\dlibra\\webappwork\\jcr-restore
for the pl.psnc.dlibra.web.comp.periodic.JCRBackupTask task=
<nam= e>jcr.backup.dir</name> <value>c:\dlibra\webappwork\jcr-backup/</value>
upload.= temp.dir=3Dc:\\dlibra\\webappwork\\upload\\temporary
If the IP address of the target server is changed= , additional actions must be carried out. If the address is not changed, th= ose actions should be skipped.
my.url
to =
//150.254.100.102:10051/ss
=E2=80=9D parameter.If a distributed authentication platform is run i= n the reader application, its configuration should be updated. In this case= , a fragment of the =E2=80=9CMigrating the Configuration of a Distributed A= uthentication Platform=E2=80=9D instruction from the Instruction for Updating from the 5.8 to= 6.0 Version chapter will be useful.
The last step will be to install the reader appli= cation on the Tomcat server.
Once the actions described above have been perfrm= ed, we can run the reader application of the dLibra system on the new serve= r.