LogoLogo
  • LIBSAFE Advanced Pro - System Administrator Manual
  • Introduction
    • Basic concepts
    • General considerations
  • System configuration
    • Storage
      • Storage groups
      • Disks
        • Different storage system types and their integration in LIBSAFE
      • Datamover
    • Digital signature profiles
      • Certificates for the digital signature service
    • Access
      • Users
        • Two-Factor Authentication (2FA)
      • Groups
      • User permissions
    • Alarms and Notifications
      • Alarm definition
      • Configured alarms
        • Configuring an alarm: example 1
        • Configuring an alarm: example 2
      • Notifications panel
    • Extras and tools
      • Programmed tasks
      • Logs manager
      • File management
      • Database management
      • Database management (read-only mode)
      • Web interface configuration variables
      • Configuration variables
      • API system services
      • Server cluster - Parallelization
        • Details of activity in one node
        • Editing or creating a node and its associated services
        • Node deactivation
        • Deleting nodes
        • Processing Cluster customization
      • SAML integration as a SSO (Single Sign On) when login in LIBSAFE
    • License
  • Preservation configuration
    • Ingestion sanitizers
      • Ingestion sanitizers detail
      • Ingestion sanitizer editing
    • Preprocessors
      • Preprocessor details
      • Creation of the preprocessor
      • Preprocessor editing
    • Ingestion checks
      • Ingestion check details
      • Creation of the ingestion check
      • Ingestion check editing
      • Main ingestion checks
    • Metadata filters
      • Metadata filter detail
      • Creation of metadata filter
      • Metadata filter editing
    • Dissemination Information Package (DIP) profiles
      • DIP profile detail
      • Creation of DIP profiles
      • DIP profile edition
    • Connectors
      • Connector Detail
      • Create a new connector
      • Edit a connector
    • File formats
      • File format detail
    • File format characterizers
      • File format characterizer detail
    • File format validators
      • File format validator detail
    • File format evolvers
      • File format evolver detail
  • Frequently Asked Questions (FAQ) and additional notes
Powered by GitBook
On this page

Was this helpful?

  1. System configuration
  2. Extras and tools
  3. Server cluster - Parallelization

Processing Cluster customization

PreviousDeleting nodesNextSAML integration as a SSO (Single Sign On) when login in LIBSAFE

Last updated 3 years ago

Was this helpful?

In order to make better use of the available resources at infrastructure level, it is possible to increase the demands or specialise them to serve or execute the activities that is part of the LIBSAFE processes.

Since the platform allows associating one or several nodes to its logical structure, it is also possible that each node can specialize in performing different activities by parallelizing their executions. In this way, a node can have multiple instances of the same service in addition to the common or typical services, or even have only one dedicated service in multiple instances. All this allows performing complex tasks in parallel and optimizing execution times or processing high volumes of data faster.

LIBSAFE has a service configuration panel in which it is very easy to define how the physical infrastructure is to be used in favour of performance.

With options to parameterize the minimum and maximum number of instances, to define always active services or to parameterize the own configurations of the services, besides the option to move with the "drag and drop" effect some service, it is possible to manage each one of the nodes of the system as well as to order them for their visualization in the services management panel (Processing Cluster).

There are services such as WEBINTERFACE or COMPLIANCECHECKER that have special characteristics and are treated differently from the rest. WEBINTERFACE can only have a maximum of one instance in a node and COMPLIANCECHECKER is not accessible through this configuration panel as it is the master service of the environment.

For the changes to take effect in the system, it is necessary that the services and nodes are stopped; this so that the configurations can be applied correctly. Some changes may not force nodes and services to be stopped, so LIBSAFE will indicate this through the interface by means of specific warnings for each case.