<?xml version="1.0" encoding="utf-8"?>
<!-- generator="FeedCreator 1.7.2-ppt DokuWiki" -->
<?xml-stylesheet href="https://gm.apps.lu/lib/exe/css.php?s=feed" type="text/css"?>
<rdf:RDF
    xmlns="http://purl.org/rss/1.0/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel rdf:about="https://gm.apps.lu/feed.php">
        <title>GECAMed - Gestion de Cabinets Médicaux faq:technical</title>
        <description></description>
        <link>https://gm.apps.lu/</link>
        <image rdf:resource="https://gm.apps.lu/_media/favicon.ico" />
       <dc:date>2026-04-09T23:18:36+00:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="https://gm.apps.lu/faq/technical/configuration_overview?rev=1575886768&amp;do=diff"/>
                <rdf:li rdf:resource="https://gm.apps.lu/faq/technical/firewall_ports?rev=1575886768&amp;do=diff"/>
                <rdf:li rdf:resource="https://gm.apps.lu/faq/technical/gecamed_properties?rev=1575886768&amp;do=diff"/>
                <rdf:li rdf:resource="https://gm.apps.lu/faq/technical/how_to_get_access_to_the_db?rev=1575886768&amp;do=diff"/>
                <rdf:li rdf:resource="https://gm.apps.lu/faq/technical/importexport?rev=1575886768&amp;do=diff"/>
                <rdf:li rdf:resource="https://gm.apps.lu/faq/technical/jasperreport_debug_messages?rev=1575886768&amp;do=diff"/>
                <rdf:li rdf:resource="https://gm.apps.lu/faq/technical/jboss_does_not_start?rev=1575886768&amp;do=diff"/>
                <rdf:li rdf:resource="https://gm.apps.lu/faq/technical/making_postgres_backups?rev=1575886768&amp;do=diff"/>
                <rdf:li rdf:resource="https://gm.apps.lu/faq/technical/restore_db_constraints?rev=1575886768&amp;do=diff"/>
                <rdf:li rdf:resource="https://gm.apps.lu/faq/technical/restoring_admin_password?rev=1575886768&amp;do=diff"/>
                <rdf:li rdf:resource="https://gm.apps.lu/faq/technical/update_gecamed_by_hand?rev=1575886768&amp;do=diff"/>
                <rdf:li rdf:resource="https://gm.apps.lu/faq/technical/where_is_the_client_logfile?rev=1575886768&amp;do=diff"/>
                <rdf:li rdf:resource="https://gm.apps.lu/faq/technical/where_is_the_server_logfile?rev=1575886768&amp;do=diff"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="https://gm.apps.lu/_media/favicon.ico">
        <title>GECAMed - Gestion de Cabinets Médicaux</title>
        <link>https://gm.apps.lu/</link>
        <url>https://gm.apps.lu/_media/favicon.ico</url>
    </image>
    <item rdf:about="https://gm.apps.lu/faq/technical/configuration_overview?rev=1575886768&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2019-12-09T10:19:28+00:00</dc:date>
        <title>Configuration Overview</title>
        <link>https://gm.apps.lu/faq/technical/configuration_overview?rev=1575886768&amp;do=diff</link>
        <description>Configuration Overview

Here is an overview over the locations of all important GECAMed specific files: [GECAMed Configuration Cheat Sheet]</description>
    </item>
    <item rdf:about="https://gm.apps.lu/faq/technical/firewall_ports?rev=1575886768&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2019-12-09T10:19:28+00:00</dc:date>
        <title>Firewall and Open Ports</title>
        <link>https://gm.apps.lu/faq/technical/firewall_ports?rev=1575886768&amp;do=diff</link>
        <description>Firewall and Open Ports

The following ports need to be open in your firewall in order to start and run GECAMed from the JBoss server:

	*  1098 jboss:service=Naming
	*  1099 jboss:service=Naming
	*  3873 jboss.remoting:type=Connector,name=DefaultEjb3Connector,handler=ejb3</description>
    </item>
    <item rdf:about="https://gm.apps.lu/faq/technical/gecamed_properties?rev=1575886768&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2019-12-09T10:19:28+00:00</dc:date>
        <title>GECAMed Client Properties</title>
        <link>https://gm.apps.lu/faq/technical/gecamed_properties?rev=1575886768&amp;do=diff</link>
        <description>GECAMed Client Properties

GECAMed client properties are a mecanism to remember personal GECAMed client settings form one session to another, for the same user on the same computer. 

Typical properties are locations and size of GECAMed windows, or the list of registered users that is available from the user drop down menu during login. The properties are stored in a file on the local computer, in the current user's home directory. For the different platforms this would be:</description>
    </item>
    <item rdf:about="https://gm.apps.lu/faq/technical/how_to_get_access_to_the_db?rev=1575886768&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2019-12-09T10:19:28+00:00</dc:date>
        <title>How to get access to the GECAMed database</title>
        <link>https://gm.apps.lu/faq/technical/how_to_get_access_to_the_db?rev=1575886768&amp;do=diff</link>
        <description>How to get access to the GECAMed database
not

The GECAMed database is a PostgreSQL database. Its configuration is described in the file “GECAMed-ds.xml”. You can find this file in the folder “&lt;GECAMed-folder&gt;/jboss-4.0.5.GA/server/default/deploy/</description>
    </item>
    <item rdf:about="https://gm.apps.lu/faq/technical/importexport?rev=1575886768&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2019-12-09T10:19:28+00:00</dc:date>
        <title>Import of Patient Data</title>
        <link>https://gm.apps.lu/faq/technical/importexport?rev=1575886768&amp;do=diff</link>
        <description>Import of Patient Data

Importing Patient data from other systems (such as legacy systems) is possible in GECAMed. To do so, we have defined an XML Schema, defining the syntax of XML files that can be imported into GECAMed. The current version of the XML schema is available here:</description>
    </item>
    <item rdf:about="https://gm.apps.lu/faq/technical/jasperreport_debug_messages?rev=1575886768&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2019-12-09T10:19:28+00:00</dc:date>
        <title>Jasperreport Debug messages</title>
        <link>https://gm.apps.lu/faq/technical/jasperreport_debug_messages?rev=1575886768&amp;do=diff</link>
        <description>Jasperreport Debug messages

Jasperreport outputs quiet a bit of debug messages when generating print objects. To get rid of them, edit the log4j.xml file in your jboss/server/default/conf directory and add the following lines in the Limit Categories section of the file.</description>
    </item>
    <item rdf:about="https://gm.apps.lu/faq/technical/jboss_does_not_start?rev=1575886768&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2019-12-09T10:19:28+00:00</dc:date>
        <title>JBoss Server does not start</title>
        <link>https://gm.apps.lu/faq/technical/jboss_does_not_start?rev=1575886768&amp;do=diff</link>
        <description>JBoss Server does not start

If the JBoss Application Server doesn't start properly, there may be several reasons. Please first see the server log files for problems.

Problem starting Hypersonic database

If there is an error message like the following, the Hypersonic database, used internally by the JBoss, is corrupted.</description>
    </item>
    <item rdf:about="https://gm.apps.lu/faq/technical/making_postgres_backups?rev=1575886768&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2019-12-09T10:19:28+00:00</dc:date>
        <title>Backup &amp; Restore GECAMed Database</title>
        <link>https://gm.apps.lu/faq/technical/making_postgres_backups?rev=1575886768&amp;do=diff</link>
        <description>Backup &amp; Restore GECAMed Database

One way to backup GECAMed databases is to use the pg_dump utility. Until today, we were using the -Ft option to dump into one single tar file which we subsequently compressed with the gzip utility. The current versions of gzip (prior to 1.3) have a filesize limit for the input file of 4 GBytes. Compressing larger files will corrupt the compressed file, making your backup useless. To resolve this issue, I would suggest to use pg_dump's custom file format to dump…</description>
    </item>
    <item rdf:about="https://gm.apps.lu/faq/technical/restore_db_constraints?rev=1575886768&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2019-12-09T10:19:28+00:00</dc:date>
        <title>Restore Database Constraints</title>
        <link>https://gm.apps.lu/faq/technical/restore_db_constraints?rev=1575886768&amp;do=diff</link>
        <description>Restore Database Constraints

When restoring a database backup it happens to appear that the constraints are not set (mostly under Windows), because of an error during the restore process. This can cause an inconsistency in the database, when deleting anything in GECAMed.</description>
    </item>
    <item rdf:about="https://gm.apps.lu/faq/technical/restoring_admin_password?rev=1575886768&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2019-12-09T10:19:28+00:00</dc:date>
        <title>Restore Admin Password</title>
        <link>https://gm.apps.lu/faq/technical/restoring_admin_password?rev=1575886768&amp;do=diff</link>
        <description>Restore Admin Password

If you have lost the admin password, and no other registered GECAMed user has admin rights or is available to log you in, there is a way to restore the original password for admin ('admin') manually. 

First you need access to GECAMed's PostgreSQL databank. This is always possible if you can access the server machine. See</description>
    </item>
    <item rdf:about="https://gm.apps.lu/faq/technical/update_gecamed_by_hand?rev=1575886768&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2019-12-09T10:19:28+00:00</dc:date>
        <title>Update GECAMed by hand</title>
        <link>https://gm.apps.lu/faq/technical/update_gecamed_by_hand?rev=1575886768&amp;do=diff</link>
        <description>Update GECAMed by hand

Expert Update Instructions



There are some legacy GECAMed installations that are not installed via the GECAMed installer and therefore are not updatable via the lateast GECAMed updaters.

You will find detailed instructions on how to update an GECAMed installation by hand. This is only for people who really know what they are doing.</description>
    </item>
    <item rdf:about="https://gm.apps.lu/faq/technical/where_is_the_client_logfile?rev=1575886768&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2019-12-09T10:19:28+00:00</dc:date>
        <title>Where are the client logfiles?</title>
        <link>https://gm.apps.lu/faq/technical/where_is_the_client_logfile?rev=1575886768&amp;do=diff</link>
        <description>Where are the client logfiles?

When starting a GECAMed client it will write some logfiles to your computer.
These can be found in the following directory
 Platform             Property File Location  Windows (bis XP)     C:\Documents and Settings\USERNAME\.gecamed\</description>
    </item>
    <item rdf:about="https://gm.apps.lu/faq/technical/where_is_the_server_logfile?rev=1575886768&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2019-12-09T10:19:28+00:00</dc:date>
        <title>Where are the server logfiles?</title>
        <link>https://gm.apps.lu/faq/technical/where_is_the_server_logfile?rev=1575886768&amp;do=diff</link>
        <description>Where are the server logfiles?

The GECAMed server, JBoss, writes his own logfiles which are located on the server computer where GECAMed is installed. 

These can be found in the following directory if you used the default GECAMed installation path:</description>
    </item>
</rdf:RDF>
