Administration Manual

SYSTRAN Enterprise Server 6 - Administration Guide 25
LICENSING
Corresponds to licensing data
SYSTRAN/engines_linux or
SYSTRAN/engines_solaris
Houses the engines data (bin directory containing the
executable file and libraries, and the dict dictionary
containing the linguistic resources)
SYSTRAN/systran.war
Contains the server application code and all corresponding
resources
The data located in the 3RDPARTY directory is linked to the system and is not
used in upgrade scenarios.
1. Backup the original installation.
2. Unzip the Installation Kit by issuing the following command (assumes an
Installation Kit named 6.02.00.70_20080307_linux.zip):
% unzip SYSTRAN_server_6.02.00.70_20080307_linux.zip
The SYSTRAN_server_6.02.00.70_20080307_linux directory is created.
3. Navigate to the new directory by issuing the following command:
% cd SYSTRAN_server_6.02.00.70_20080307_linux
4. Issue the following commands to mount the Installation Kit (assumes commands
are run without updating JBoss and legacy data):
a. % cp LICENSING/${OSTYPE}/* ${INSTALLDIR}/lib
b. % tar cf - SYSTRAN/systran.war | ( cd
${INSTALLDIR}/server/deploy/default/systran.war ; tar xf -
)
c. % tar cf - SYSTRAN/engines_${OSTYPE} | ( cd
${INSTALLDIR}/server/deploy/default/systran.war/engines ;
tar xf - )
5. Restore the legacy data.
a. % cd ../save_dir
b. % cp config/systran*
${INSTALLDIR}/server/deploy/default/systran.war/config/
The systran.war/config/hibernate.cfg.xml file is used to define properties
of the relational database. If it is be modified by the administrator, the
modifications should be incorporated manually in the hibernate.cfg.xml file of
the new installation.
c. % cp –r database/*
d. % cp libsyslic.ls ${INSTALLDIR}/lib/libsyslic.ls
e. % cp –r custom/*
f. ${INSTALLDIR}/server/deploy/default/systran.war/custom
g. % cp –r template/*
h. ${INSTALLDIR}/server/deploy/default/systran.war/template
6. Recompile dictionaries.