System Requirements

Information

• This topic contains

  • a description of technical details of the PLANTA software and

  • an overview of the supported platforms and database systems.

The PLANTA project System

For information

• PLANTA project is a container-based application and consists of the following components:

  • Container

    • Manager

    • Worker

    • webclient

    • customizing

    • project database (oracle or mssql)

    • pulse

    • pulse database (mongo)

    • gpt

  • Windows Client

• PLANTA project

  • can be operated on various container platforms and is functionally identical on all of them.

  • can usually be run on virtualized systems.

Notes

• The platforms and database systems supported by PLANTA project are subject to regular changes in accordance with the release policy of the suppliers.

• If third party providers decide to stop the support for certain product versions, PLANTA will have to take these products from their list of supported versions as well. Customers can still run the platform in question, however, they do so on their own responsibility. In case of any possible errors, issues or problems, PLANTA accepts no liability.

  • PLANTA can offer support for outdated versions to the customer, however, this kind of support is not covered by the maintenance contract. In such a case, please contact your PLANTA consultant.

Details

• Client and server communicate

  • via TCP/IP protocol.

  • server and database takes place via JDBC.

Delivery

• All container images are available on the PLANTA registry at https://registry.planta.services. The login data will be sent to you by PLANTA upon request. For further information on this topic, please see Login PLANTA OCI Registry

Requirements for using PLANTA project

The following systemic remarks on the container infrastructure in the PLANTA project environment should be regarded as reference points and tips.

Information

• As for any other software system, the processing speed of PLANTA project depends on the following basic factors:

  • Assigned container resources (CPU, memory)

  • Performance of the container infrastructure

  • data volumes processed

  • processing functions carried out

• The processing functions available in PLANTA project can roughly be categorized by the following criteria:

  • insertion/display/saving of a record

  • generic selection of data from the database

  • display of Gantt charts and utilization diagrams

  • scheduling/replanning

Details

• The question of how a container environment can be configured optimally for PLANTA project can be answered to a large extent under the following conditions:

  • There is generally reliable information on the number of users and on how they will use the system in terms of the

    • type of functions performed

    • number of functions performed

    • times of day/calendar cycles when the functions will be performed

    • time-critical functions from a user demand perspective

  • Details on the data volumes to be processed within the time-critical functions are available. Here, significant factors are:

    • number of projects/tasks

    • number of resources being planned

    • project durations

    • any possible individual data or data included in the processing from other applications (to which there are interfaces)

PLANTA Windows Client

For performance reasons, we strongly advise against making the client available to users via a network drive. This can also lead to errors in connection with the use of certain web components (charts, PLANTA secure).

Software requirements

Hardware requirements

PLANTA Web Client

Application Server

Software requirements

• The web interface for PLANTA project is made available via registry.planta.services in the form of a Linux-based docker image.

  • For access, please contact your PLANTA consultant.

• For deployment in productive environments we generally recommend that you use a reverse. Here are some things to be taken into account:

  • Each browser session maintains an active connection to the application server.

  • The browser connection uses the WebSocket standard.

  • Connections must always be routed to the same application server instance (sticky sessions).

Hardware requirements

• The latency between browser and application server is decisive for a good user experience. The average latency should therefore be lower than 150 ms.

• On the part of the backend, the web surface application server establishes a connection to the PLANTA project server per client session. Here, low latency is beneficial as well. Since latencies add up, a latency of < 10 ms is of advantage.

Terminal Devices

Software requirements

• Unlike the PLANTA project application itself, the Web Client does not require a designated platform.

• In general, end devices with a larger display will provide a better user experience..

Hardware requirements

• In general, faster terminal devices provide better user experience, however, due to the chosen basic architecture, the main load will be handled by the server. This enables you to work fluently even on devices with moderate performance.

PLANTA Server

Information

• The PLANTA Server is made available in docker container format and contains several container images: manager, worker, customizing, webclient, as well as optional components such as secure or PLANTA-GPT

• The container images require an OCI-compatible container runtime or platform, such as Docker, Podman, or orchestration platforms such as Kubernetes, Openshift, etc. For this purpose, PLANTA uses Docker containers.

• We recommend that you install the database selected for PLANTA project on a separate database server, however, it can also be installed in a container.

• The following information applies to the application server only (manager + worker).

Hardware requirements

PLANTA Server and PLANTA Online Help

In order for PLANTA users to be able to use contextual help via the F1/F2 keys directly from the system, you have to make sure that the project application server has Internet access or at least access to the IP address: 3.65.222.100.

Database Requirements

Oracle Database

For the operation of PLANTA project with an Oracle database, the following is required:

• Character set:

  • UTF8

• Date format:

  • NLS_DATE_FORMAT=DD.MM.RR

• PLANTA project user rights:

  • System privileges: CREATE SESSION, CREATE TABLE, CREATE VIEW, CREATE MATERIALIZED VIEW, CREATE PROCEDURE, CREATE SYNONYM, CREATE SEQUENCE, CREATE TRIGGER,EXECUTE ON SYS.DBMS_CRYPTO

Example

• PLANTA project demo system:

  • Size 4 GB

  • Tablespace management "locally managed /autoallocate"

Microsoft SQL Database Server

For the operation of PLANTA project with an MSSQL database, the following is required:

• Character set:

  • WIN1252

    • Sorting: Latin1_General_CI_AS

• Authentication:

  • SQL server authentication with user name and password

• The following settings have to be applied when creating a database user manually:

  • DEFAULT_DATABASE = [model],

  • DEFAULT_LANGUAGE = [Deutsch],

  • CHECK_EXPIRATION = OFF,

  • CHECK_POLICY = OFF

• Create a new database with the name of the corresponding user and make the following settings:

  • COMPATIBILITY_LEVEL = 100,

  • ANSI_WARNINGS = OFF,

  • ARITHABORT = ON,

  • AUTO_CLOSE = OFF,

  • AUTO_CREATE_STATISTICS = ON,

  • AUTO_UPDATE_STATISTICS = ON,

  • AUTO_SHRINK = OFF,

  • CONCAT_NULL_YIELDS_NULL = OFF ,

  • CURSOR_CLOSE_ON_COMMIT = OFF,

  • CURSOR_DEFAULT = GLOBAL,

  • NUMERIC_ROUNDABORT = OFF,

  • QUOTED_IDENTIFIER = OFF,

  • RECURSIVE_TRIGGERS = OFF,

  • AUTO_UPDATE_STATISTICS_ASYNC = OFF,

  • DATE_CORRELATION_OPTIMIZATION = OFF,

  • PARAMETERIZATION = SIMPLE,

  • READ_WRITE ,

  • MULTI_USER ,

  • PAGE_VERIFY = CHECKSUM

• PLANTA project user/login:

  • Create a user with "dbo" default schema for the database to be used for PLANTA project.

    • Set the user language to "English" and the "two digit year cutoff" option of the newly created database to "2069".

    • Rights (Owned Schemas/Role Members):

      • db_owner

• Assign the database to be used for PLANTA project to the login as the standard database.

  • Settings:

    • Permission to connect to database = Grant

    • Login = Enable

Backup/Maintenance of the Database

For information

• PLANTA stores user data only within the database.

• The database is not run by PLANTA but by the customer. This includes backup as well as regular maintenance and optimization work on the database (e.g. optimizing the performance by setting and removing indices due to changed data volume).

These database activities have to be executed by administrators with respective knowledge and skills. Alternatively, PLANTA can be charged with these tasks. In this case, please contact your PLANTA consultant.

Backup

• For a backup, it is necessary to save the following components:

  • the user data of the database user used by PLANTA (PLANTA uses one database user for any access)

  • the technical data of the used PLANTA release (program, standard Python code, individual Python code) of Client and Server

A backup that works for the described data is required for the operation of the PLANTA software.

Supported Interfaces/Third Party Products

Additional requirements for PLANTA Hybrid

If you plan to use PLANTA in a hybrid way, the conditions for PLANTA pulse must be met in addition to aforementioned conditions for PLANTA project. You will find all required information on this subject under System Requirements in the PLANTA pulse help area.