≪ View Page

Unterschiede

Hier werden die Unterschiede zwischen zwei Versionen angezeigt.

Link zu dieser Vergleichsansicht

Beide Seiten der vorigen RevisionVorhergehende Überarbeitung
Nächste Überarbeitung		Vorhergehende Überarbeitung
en:installation_und_deinstallation [2026/03/16 08:27] – adminen:installation_und_deinstallation [2026/04/29 15:08] (aktuell) – admin
Zeile 1: Zeile 1:
 ====== Installation and Uninstallation ====== ====== Installation and Uninstallation ======
-===== Preliminary Remarks and Important Notes =====+===== Preliminary Notes and Important Information =====
  
-When using **PAM < 2.0**, please contact support in advance: [[mailto:software@ktp.upb.de|software@ktp.upb.de]].+If you are using **PAM < 2.0**, please contact support in advance: [[mailto:software@ktp.upb.de|software@ktp.upb.de]].
  
-If **PAM 2.0 or higher** is already installed, an existing PAM installation must be **uninstalled** before performing a new installation. **Note:** The material databases will remain intact unless you manually delete or overwrite them.+If **PAM 2.0 or higher** is already installed, any existing PAM installation must be **uninstalled** before reinstalling. **Note:** The material databases will be retained unless you delete or overwrite them manually.
  
-With **PAM 3.0**, structural changes to the material database were introduced. Therefore, **local** as well as **network databases** from earlier versions must first be migrated to **PAM 3.0**. A detailed description can be found in the section **[[installation_und_deinstallation#migration_einer_alten_pam-datenbank_version_30 | Migration of an older PAM database]]**.+With **PAM 3.0**, structural changes were introduced to the material database. Therefore, **local** and **network databases** from earlier versions must first be migrated to **PAM 3.0**. A detailed description can be found in the section **[[installation_und_deinstallation#migration_einer_alten_pam-datenbank_version_30 | Migration of an old PAM database]]**.
  
-If you are working with a **network database** that has already been migrated to **PAM 3.0** (or higher), **all users** must update the PAM software to the **same major version** in order to continue working with that database.+If you are working with a **network database** that has already been migrated to **PAM 3.0** or higher, **all users** must update the PAM software to the **same major version** in order to continue working with this database.
  
 === Firebird === === Firebird ===
-PAM uses the relational DBMS **Firebird**. In order for PAM to access a database, the required [[https://download.ktp-software.de/Firebird-2.5.9.27139_0_Win32.exe | Firebird components]] must be installed on the computer.   +PAM uses the relational DBMS **Firebird**. In order for PAM to access a database, the required [[https://download.ktp-software.de/Firebird-5.0.4.1812-0-windows-x64.exe | Firebird components]] must be installed on the computer.   
-The **32-bit (x86)** variant is mandatory, even if the operating system is 64-bit (depending on the PAM architecture and drivers).+
  
 === Dongle Driver === === Dongle Driver ===
-To detect the license dongle (Sentinel HASP HL), the appropriate driver must be installed.   +The appropriate driver must be installed in order to detect the license dongle (Sentinel Hasp HL).   
-Installer: [[https://download.ktp-software.de/HASPUserSetup.exe|HASPUserSetup.exe]]+Installer: [[https://download.ktp-software.de/HaspUserSetup.zip|HaspUserSetup.zip]]
  
  
-The following prerequisites must be met for the installation and operation of PAM:+The following requirements must be met for installing and operating PAM:
  
 ^ **Database Server** ^ **Requirement** ^ **Notes** ^ ^ **Database Server** ^ **Requirement** ^ **Notes** ^
 | Operating system | Windows 11 (64-bit) |  | | Operating system | Windows 11 (64-bit) |  |
-| Database | Firebird **2.5.9** (Port **3050/TCP**) |  |+| Database | Firebird **5.0.4** (port **3050/TCP**) | If you are still using Firebird 2.5.9, please [[https://sigmadoc.ktp-software.de/doku.php?id=installation_und_deinstallation:migration_nach_5 | update]] it.| 
 | Additional software components | none |  | | Additional software components | none |  |
-| Required permissions | Administrator privileges | required for installation / firewall / service configuration |+| Required permissions | Administrator rights | required for installation/firewall/service configuration |
  
 ^ **PAM Client** ^ **Requirement** ^ **Notes** ^ ^ **PAM Client** ^ **Requirement** ^ **Notes** ^
 | Operating system | Windows 11 |  | | Operating system | Windows 11 |  |
-| Additional software components | 1) Firebird Client/Server **2.5.9** (x86) \\ 2) HASP Sentinel Dongle Driver (Sentinel LDK / HASP Runtime) | [[https://download.ktp-software.de/Firebird-2.5.9.27139_0_Win32.exe | Firebird components]] \\  [[https://download.ktp-software.de/HASPUserSetup.exe|Dongle driver]] | +| Additional software components | 1) Firebird Client/Server **5.0.4** (x64) \\ 2) HASP Sentinel dongle driver (Sentinel LDK / HASP Runtime) | [[https://download.ktp-software.de/Firebird-5.0.4.1812-0-windows-x64.exe | Firebird components]] \\  [[https://download.ktp-software.de/HaspUserSetup.zip|Dongle driver]] | 
-| Required permissions | User privileges (operation), administrator privileges (installation) |  |+| Required permissions | User rights (operation), administrator rights (installation) |  |
  
-**Note:** If the PAM client is intended to use a **local database**, the requirements of the database server also apply in addition (local Firebird service, local port / firewall, administrator privileges for setup).+**Note:** If the PAM client is to use a **local database**, the database server requirements also apply additionally: local Firebird service, local port/firewall configuration, and administrator rights for setup.
  
  
 ===== Uninstalling an Existing PAM Version ===== ===== Uninstalling an Existing PAM Version =====
  
-1. Exit PAM (including any open database connections, if applicable).+1. Close PAM, including any open database connections.
  
-2. In Windows, go to: **Settings > Apps > Installed apps** (or Control Panel) and select the existing PAM version.+2. In Windows: select the existing PAM version under **Settings > Apps > Installed Apps** or in the Control Panel.
  
 3. Run **Uninstall**. 3. Run **Uninstall**.
  
-4. **Important:** Database files (e.g. *.gdb/*.fdb) are **not** removed.+4. **Important:** Database files, such as *.gdb/*.fdb, are **not** removed.
  
 ===== Installing PAM ===== ===== Installing PAM =====
  
-1. Run the setup (right-click and select “Run as administrator” is recommended).+1. Run the setup, preferably by right-clicking and selecting “Run as administrator”.
  
 2. Select the language: 2. Select the language:
  
-{{ :en:en_pam311_dlg_setup_006.png?nolink |}}+{{ :de_pam311_dlg_setup_006.png?nolink |}}
  
  
 3. Complete the installation wizard. 3. Complete the installation wizard.
  
-4. [[ Installationsanleitung_Firebird |Install]] Firebird ([[https://download.ktp-software.de/Firebird-2.5.9.27139_0_Win32.exe | Firebird components]]).+4. [[ Installationsanleitung_Firebird | Install]] Firebird ([[https://download.ktp-software.de/Firebird-5.0.4.1812-0-windows-x64.exe | Firebird components]]).
  
-5. Install the dongle driver ([[https://download.ktp-software.de/HASPUserSetup.exe| dongle driver]]).+5. Install the dongle driver ([[https://download.ktp-software.de/HaspUserSetup.zip| Dongle driver]]).
  
-6. Start PAM and configure the database connection (local or network).+6. Start PAM and configure the database connection, either local or network.
  
  
-===== Migration of an Older PAM Database (Version < 3.0) =====+===== Migration of an Old PAM Database (Version < 3.0) =====
  
-=== Prerequisites ===+=== Requirements ===
  
-**Extended / administrative privileges** are required for the migration.+**Advanced / administrative rights** are required for the migration.
  
 Please note: Please note:
  
-  * During migration, the affected material database must **not** be open in any other program or by any other user (e.g. SIGMA, REX, PSI, or Flame Robin). +  * During the migration, the affected material database must **not** be opened by other programs/users, such as SIGMA, REX, PSI, or Flame Robin. 
-  * If the migration is started while another user is still connected, an error message will appear:+  * If the migration is started while another user is still connected, an error message appears:
  
-{{ :en:en_pam311_dlg_setup_001.png?nolink |}}+{{ :de_pam311_dlg_setup_001.png?nolink |}}
  
 === Migration Procedure === === Migration Procedure ===
  
-If you open a database from an older version (e.g. 2.x) in PAM 3.0, an informational dialog will appear:+When you open a database from an older version, such as 2.x, in PAM 3.0, an information dialog appears:
  
-{{ :en:en_pam311_dlg_setup_002.png?nolink |}}+{{ :de_pam311_dlg_setup_002.png?nolink |}}
  
-1. Ensure that there are **no other active connections** to the database.+1. Make sure that there are **no further connections** to the database.
  
-2. Click **“Upgrade”** to start the migration.+2. Click **“Update”** to start the migration.
  
-3. PAM automatically creates a backup version of the old database (compressed format).  +3. PAM automatically creates a backup version of the old database in compressed format.  
    Typical storage location:    Typical storage location:
    ''C:\Users\<User>\AppData\Roaming\KTP\PAM2.1\backups\''      ''C:\Users\<User>\AppData\Roaming\KTP\PAM2.1\backups\''  
-   File naming scheme: +   File name according to the following pattern: 
-   ''<DB-Name>-<BackupDate>-<ID>''+   ''<DB-name>-<backup-date>-<ID>''
  
  
-4. PAM then performs the database migration. If completed successfully, the log will look similar to the following example:+4. PAM then performs the database migration. After successful completion, the log may look like this:
  
-{{ :en:en_pam311_dlg_setup_003.png?nolink |}}+{{ :de_pam311_dlg_setup_003.png?nolink |}}
  
 === Restoring a Backup Database (gbak) === === Restoring a Backup Database (gbak) ===
  
-The backup file is stored in a compressed, non-human-readable format. Use the Firebird tool **gbak** to restore it.+The backup file is stored in a compressed format that cannot be read directly. To restore it, use the Firebird tool **gbak**.
  
 Example: Example:
  
 <code> <code>
-gbak -r -user SYSDBA -password <Password> "<Path_to_Backup_File>" "<Path_to_Target_Database.fdb>"+gbak -r -user SYSDBA -password <Password> "<Path_to_backup_file>" "<Path_to_target_database.fdb>"
 </code> </code>
  
 Notes: Notes:
   * **gbak** is located in the Firebird installation directory under ''...\bin\''.   * **gbak** is located in the Firebird installation directory under ''...\bin\''.
-  * Make sure to use the correct quotation marks for paths containing spaces.+  * Make sure to use correct quotation marks for paths containing spaces.
   * The target path should point to a writable directory.   * The target path should point to a writable directory.
  
Zeile 115: Zeile 115:
 ===== Upgrading a Material Database from 3.0 to 3.1 ===== ===== Upgrading a Material Database from 3.0 to 3.1 =====
  
-PAM 3.1 provides new features that require an adaptation of the database structure. When connecting to a database in 3.0 format, the following message is displayed:+PAM 3.1 provides new functions that require an adjustment of the database structure. When connecting to a database in format 3.0, the following notice is displayed:
  
-{{ :en:en_pam311_dlg_setup_004.png?nolink&600 |}}+{{ :de_pam311_dlg_setup_004.png?nolink&600 |}}
  
-You can still select **“Connect”**, but not all features may be available.   +You can still select **“Connect”**, but not all functions may be available.   
-Recommendation: Upgrade the database to the current format (v3.1) using **“Upgrade”**.+Recommendation: Update the database to the current format (v3.1) using **“Update”**.
  
 **Important notes:** **Important notes:**
-  * When using a shared network database, make sure that **no other users** are connected. +  * If using a shared network database, make sure that **no other users** are connected. 
-  * **Administrative privileges** are required for the upgrade. +  * **Administrative rights** are required for the update. 
-  * Only perform the upgrade if the required permissions are available and no other users are affected.+  * Perform the update only if the required permissions are available and no other users are affected.
  
  
 ===== Installing a PAM Database on a Server (Network Operation) ===== ===== Installing a PAM Database on a Server (Network Operation) =====
  
-**Scenario:** PAM stores the material data on an internal server. Users should primarily have **read-only access**, while only admins may write.+**Scenario:** PAM stores the material data on an internal server. Users should primarily have **read access**, while only administrators should have write access.
  
-{{ :en:en_pam311_dlg_setup_005.png?nolink |}}+{{ :de_pam311_dlg_setup_005.png?nolink |}}
  
 === Preparing the Infrastructure (Server) === === Preparing the Infrastructure (Server) ===
  
-  - Record the **server IP** (e.g. 123.123.123.123) +  - Note the **server IP**, for example 123.123.123.123 
-  - Install Firebird Server (x86) with administrator privileges according to the following [[Installationsanleitung_Firebird |instructions]].+  - Install the Firebird Server with administrator rights according to the following [[Installationsanleitung_Firebird |guide]].
   - Copy the PAM database file to the server, for example:   - Copy the PAM database file to the server, for example:
-    * Target path: ''C:\data\pam\PAM2se.GDB'' (or *.fdb) +    * Target path: ''C:\data\pam\PAM.GDB'' or *.fdb 
-  - Configure a Firebird alias (server): +  - Set the Firebird alias on the server: 
-    * Open the file ''C:\Program Files (x86)\Firebird\Firebird_2_5\aliases.conf'' with administrator privileges +    * Open the file ''C:\Program Files\Firebird\Firebird_5_0\databases.conf'' with administrator rights 
-    * Add the alias (must match the target path exactly):+    * Add the alias. It must match the target path exactly:
     * Example: <code>pam_db = C:\data\pam\PAM2se.GDB</code>     * Example: <code>pam_db = C:\data\pam\PAM2se.GDB</code>
-  - Add a firewall rule (server): +  - Add a firewall rule on the server: 
-    * Option A (recommended): Allow inbound TCP port **3050** +    * Option A, recommended: allow inbound TCP port **3050** 
-    * Option B: Allow the program: ''...\Firebird_2_5\bin\fbserver.exe'' +    * Option B: allow the program ''...\Firebird_5_0\firebird.exe'' 
-    * Grant access at least for Private / Domain profiles in accordance with company policy +    * Enable access at least for Private/Domain according to your company policy 
-{{ :en_pam311_dlg_setup_007.png?nolink |}}+{{ :de_pam311_dlg_setup_007.png?nolink |}}
  
          
Zeile 163: Zeile 163:
 3. In **Database Management**, click **“Add”** and enter the data: 3. In **Database Management**, click **“Add”** and enter the data:
  
-{{ :en:en_pam311_dlg_setup_008.png?nolink |}}+{{ :de_pam311_dlg_setup_008.png?nolink |}}
  
 Recommended fields: Recommended fields:
  
-  * **Database name:** freely selectable (e.g. “PAM-DB Net”)+  * **Database name:** freely selectable, for example “PAM-DB Net”
   * **Database server:** server IP or hostname   * **Database server:** server IP or hostname
-  * **Database path:** alias from ''aliases.conf'' (e.g. ''pam_db'') +  * **Database path:** alias from ''aliases.conf'', for example ''pam_db'' 
-  * **Username / password:** initially often ''sysdba'' / ''masterkey'' (recommended: change the password later)+  * **User name / password:** initially often ''sysdba'' / ''masterkey''; recommendation: change the password later
  
 4. Click **“Connect database”**. 4. Click **“Connect database”**.
Zeile 176: Zeile 176:
 ===== Users and Permissions on a PAM Network Database ===== ===== Users and Permissions on a PAM Network Database =====
  
-It is often desirable that only certain people may write records, while other users are restricted to read-only access.+Often, only certain users should be allowed to write data records, while other users should have read-only access.
  
-User management is performed on the server side in Firebird. An admin tool such as **Flame Robin** can be used for this purpose: [[https://www.flamerobin.org/|flamerobin.org]]+User management is performed server-side in Firebird. An administration tool such as **Flame Robin** can be used for this: [[https://www.flamerobin.org/|flamerobin.org]]
  
-**Step 1: Register the database in Flame Robin **+**Step 1: Register the database in Flame Robin**
  
 Menu: **Database -> Register existing database…** Menu: **Database -> Register existing database…**
  
-{{ :en:en_pam311_dlg_setup_009.png?nolink |}}+{{ :de_pam311_dlg_setup_009.png?nolink |}}
  
   * **Display name:** freely selectable   * **Display name:** freely selectable
-  * **Database path:** path to the database file (or alias path, depending on the setup) +  * **Database path:** path to the database file or alias path, depending on the setup 
-  * **Authentication:** saved username / password+  * **Authentication:** stored user/password
   * **User:** sysdba (admin)   * **User:** sysdba (admin)
   * **Password:** corresponding admin password   * **Password:** corresponding admin password
Zeile 194: Zeile 194:
 After successful registration, the database appears in the tree view: After successful registration, the database appears in the tree view:
  
-{{ :en:en_pam311_dlg_setup_010.png?nolink |}}+{{ :de_pam311_dlg_setup_010.png?nolink |}}
  
  
-**Step 2: Create users and change the SYSDBA password **+**Step 2: Create users and change the SYSDBA password**
  
 Menu: **Server -> Manage users…** Menu: **Server -> Manage users…**
  
-{{ :en:en_pam311_dlg_setup_011.png?nolink |}}+{{ :de_pam311_dlg_setup_011.png?nolink |}}
  
 **Create a new user:** **Create a new user:**
   * Select “Add user”   * Select “Add user”
-  * Set the username (e.g. ''pamuser'') and password:+  * Set the user name, for example ''pamuser'', and password:
  
-{{ :en_pam311_dlg_setup_012.png?nolink |}}+{{ :de_pam311_dlg_setup_012.png?nolink |}}
  
 **Change the SYSDBA password (recommended):** **Change the SYSDBA password (recommended):**
Zeile 213: Zeile 213:
   * Set a new password:   * Set a new password:
  
-{{ :en:en_pam311_dlg_setup_013.png?nolink |}}+{{ :de_pam311_dlg_setup_013.png?nolink |}}
  
-**Important:** The new password must then also be used in PAM for the database connection.+**Important:** The new password must then be used in PAM for the database connection.
  
  
-==== Client: Enter the Network Database Using the New Credentials ====+==== Client: Entering the Network Database with New Login Credentials ====
  
 In PAM: **File -> Databases** -> **Add** In PAM: **File -> Databases** -> **Add**
  
   * Server: hostname or IP   * Server: hostname or IP
-  * Database path: alias (e.g. ''pam_net_db'')+  * Database path: alias, for example ''pam_net_db''
  
-{{ :en:en_pam311_dlg_setup_014.png?nolink |}}+{{ :de_pam311_dlg_setup_014.png?nolink |}}
  
-If the SYSDBA password has been changed, you may need to confirm that a connection using the default password is no longer possible.+If the SYSDBA password has been changed, it may be necessary to confirm that a connection can no longer be established with the default password.
  
  
  
  
-===== Problems at Startup / Troubleshooting =====+===== Startup Problems / Troubleshooting =====
  
-=== Database connection fails ===+=== Database Connection Fails ===
  
 Possible causes: Possible causes:
  
-  * Port **3050/TCP** is not enabled in the firewall (server and, if applicable, client). +  * Port **3050/TCP** has not been opened in the firewall, on the server and possibly also on the client. 
-  * The Firebird service is not running (server). +  * The Firebird service is not running on the server. 
-  * The user does not have write permissions for database migration / upgrade.+  * The user does not have write permissions for database migration/update.
  
-If an error message appears during automatic extension / migration, connect once as the database administrator:+If an error message appears during automatic extension/migration, connect once as the database administrator:
   * User: **sysdba**   * User: **sysdba**
-  * Password: **masterkey** (if not changed)+  * Password: **masterkey**, unless it has been changed
  
 === Dongle Problems === === Dongle Problems ===
  
-If the dongle driver is installed, diagnostics can be performed using the Sentinel Admin Control Center:+If the dongle driver is installed, diagnostics can be performed via the Sentinel Admin Control Center:
  
-  * Open the browser: ''https://localhost:1947''+  * Open browser: ''https://localhost:1947''
  
 === Log === === Log ===
-In the folder <code> %APPDATA%\KTP\PAM2.1\pamlog.0.0.log </code>, PAM logs the program behavior.+PAM logs program behavior in the folder <code> %APPDATA%\KTP\PAM2.1\pamlog.0.0.log </code>.
  
-===== Note on Database Migration During Program Startup =====+===== Note on Database Migration at Program Startup =====
  
-  * Older material databases are generally upgraded automatically when connected for the first time (PAM 2.2+). +  * Old material databases are usually extended automatically the first time a connection is established (PAM 2.2+). 
-  * Starting with PAM 3, the **migration wizard** starts automatically when an older database version is detected. +  * Starting with PAM 3, the **migration wizard** starts automatically when an old database version is detected. 
-  * If write permissions are missing, a corresponding error message will appear. In this case: connect once as **sysdba** and perform the migration.+  * If write permissions are missing, a corresponding error message appears. In this case: connect once as **sysdba** and perform the migration.