The documentation from version 39.5.17 of PLANTA project can be found in the new PLANTA Online Help.

System Requirements

Information
  • This topic contains
    • technical details of the PLANTA project system and
    • an overview of the supported platforms and database systems.
  • Target user groups for this topic are
    • technical consultants
    • IT administrators

The PLANTA project System

Information
  • PLANTA project is a 3-tier application and consists of the following components:
    • PLANTA project Service (business layer)
    • PLANTA project Client (presentation layer)
    • Database (data layer)
  • PLANTA project
    • can be run on a large number of platforms (operation systems) and database systems and is functionally identical on each of them.
    • is usually executable on virtualized systems.

Notes

  • The supported platforms and database systems are subject to regular change in accordance with the release policy of the suppliers.
  • If third party providers decide not to support certain product versions any longer, PLANTA has to take these products from their list of supported versions as well. Customers can still run this platform, 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 included in the maintenance contract. In this case, please contact your PLANTA consultant.

Details

From S 39.5.0

  • Communication between
    • client and server takes place by means of the TCP/IP protocol.
    • server and database takes place via JDBC.

Up to S 39.5.0

  • Communication between
    • client and server takes place by means of the TCP/IP protocol.
    • server and database takes place via OCI or ODBC.
  • Details

    PLANTA project Requirements

    Note

    • The following system technical remarks on hardware and software 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:
      • hardware performance (data bus, disk throughput, processor, memory, network)
      • data volumes processed
      • processing functions carried out
    • The processing functions which are possible in PLANTA project are categorized as:
      • insertion, display, and saving of a record
      • generic selection of data from the database
      • display of Gantt charts and resource utilization diagrams
      • scheduling/replanning

    Details

    • The question of how a server can be configured optimally for the PLANTA project application 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
        • volume of functions performed
        • times of day/calendar cycles when the functions will be performed
        • number and type of time-critical functions, demanded by the users
      • 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 Client

    Software requirements

    From C 39.5.28

    Requirements
    Framework .Net 4.7.1
    Operation system Windows x86/x64
    • Windows Server 2019
    • Windows Server 2016
    • Windows 10
      • Windows 10 Pro
      • Windows 10 Education
      • Windows 10 Enterprise
      • Current Branch for Business (CBB)
      • Long-Term Servicing Branch (LTSB)
    • Windows Server 2012 R2
    • Windows Server 2012
    • Windows 8
    • Windows 7
    • Windows Server 2008 R2
    • Windows Server 2008
    • Windows Vista

    From C 39.5.26

    Requirements
    Framework .Net 4.7.1 NEW
    Operation system Windows x86/x64
    • Windows 10
      • Windows 10 Pro
      • Windows 10 Enterprise
      • Windows 10 Enterprise
      • Current Branch for Business (CBB)
      • Long-Term Servicing Branch (LTSB)
    • Windows Server 2012 R2
    • Windows Server 2012
    • Windows 8
    • Windows 7
    • Windows Server 2008 R2
    • Windows Server 2008
    • Windows Vista

    From C 39.5.16

    Requirements
    Framework .Net 4.0 Full
    Operation system Windows x86/x64
    • Windows 10 NEW
      • Windows 10 Pro
      • Windows 10 Education
      • Windows 10 Enterprise
      • Current Branch for Business (CBB)
      • Long-Term Servicing Branch (LTSB)
    • Windows Server 2012 R2
    • Windows Server 2012
    • Windows 8
    • Windows 7
    • Windows Server 2008 R2
    • Windows Server 2008
    • Windows Vista

    From C 39.5.13

    Requirements
    Framework .Net 4.0 Full
    Operation system Windows x86/x64
    • Windows Server 2012 R2 NEW
    • Windows Server 2012 NEW
    • Windows 8
    • Windows 7
    • Windows Server 2008 R2
    • Windows Server 2008
    • Windows Vista
    • Windows XP

    Up to C 39.5.13

    Requirements
    Framework .Net 4.0 Full
    Operation system Windows x86/x64
    • Windows 8
    • Windows 7
    • Windows Server 2008 R2
    • Windows Server 2008
    • Windows Vista
    • Windows XP

    Hardware requirements

    Requirements
    CPU Minimum condition
    • Intel Core processor or similar with minimum 2 GHz
    Recommended
    • Intel Sandy Bridge or similar with minimum 2,6 GHz
    Main memory Minimum conditions
    • per project manager: 300 MB
    • per project team member: 100 MB
    Recommended
    • per project manager: 600 MB
    • per project team member: 100 MB
    Hard disk capacity 100 MB

    PLANTA Server

    Information
    • We recommend that you install the database for PLANTA project on a separate database server, however, it can also be installed on the PLANTA project Server.
    • The following information applies to the application server only.

    Attention

    From S 39.5.12

    • The server installation on Linux in conjunction with an MSSQL database is now possible.

    Up to S 39.5.12

  • The installation of server versions 39.5.0 to (including) 39.5.11 on Linux in conjunction with a MSSQL database is not possible at the moment.
  • Software requirements

    From S 39.5.29

    Requirements
    Operation system Architecture x64
    • Windows
      • Windows Server 2019
      • Windows Server 2016 Core
      • Windows Server 2016
      • Windows Server 2012 R2
      • Windows Server 2012
      • Linux
        • Suse Linux Enterprise 11/12/15
        • Red Hat Enterprise 6/7/8
        • NEW CentOS 6/7/8
      Database driver Supplied JDBC driver
      • Additional configuration or installation is not required anymore.
      Runtime
      • In Windows, the MSVC 2015 x64 distributables are installed automatically if they do not exist yet
      • For Linux, GLIB 2.14 or later and GCC 4.8.5 or later must be installed on the server
      • A particular Java version is not required, since the PLANTA server comes with its own Java version (Zulu). This has no influence on already existing Java versions on the system on which the PLANTA Server is installed.
      System settings
    • Linux:
      • Limitation of the virtual address space and of the stack size of the application server process are not supported, therefore such limitations must be removed under Linux.
        • The PLANTA Server automatically removes limitations of the virtual address space and of the stack size where possible.
        • If the attempt to remove limitations fails (e.g. due to a hard limit), a respective message is logged.
        • In this case, the limitations must be removed in the common way for Linux distributions.
      • The limitation of opened file descriptors (including network sockets) must be adjusted upon the occurrence of bottlenecks.
        • Errors due to a limitation of the number of opened files are displayed via the "Too many open files" error message.
        • In such cases, the limitation must be extended for the user account of the PLANTA service.
        • For this purpose, the configuration mechanisms of the used Linux distribution are to be used.
        • A possible reason for a higher use of file descriptors can be an update to PLANTA Server 39.5.16, as described in the Process Based Architecture topic.
      • OpenSSL Version
        • When using a distribution based on Redhat 8, it may be necessary to install a packet which assembles compatibility with OpenSSL10; e.g. the "compat-openssl10” packet in the case of Redhat 8.

      From S 39.5.28

      Requirements
      Operation system Architecture x64
      • Windows
        • Windows Server 2019 NEW
        • Windows Server 2016 Core
        • Windows Server 2016
        • Windows Server 2012 R2
        • Windows Server 2012
        • Linux
          • Suse Linux Enterprise 11/12
          • Red Hat Enterprise 6/7
        Database driver Supplied JDBC driver
        • Additional configuration or installation is not required anymore.
        Runtime
        • In Windows, the MSVC 2015 x64 distributables are installed automatically if they do not exist yet
        • For Linux, GLIB 2.14 or later and GCC 4.8.5 or later must be installed on the server
        • A particular Java version is not required, since the PLANTA server comes with its own Java version (Zulu). This has no influence on already existing Java versions on the system on which the PLANTA Server is installed.
        System settings
      • Linux:
        • Limitation of the virtual address space and the stack size of the application server process are not supported, therefore such limitations must be canceled under Linux.
          • The PLANTA Server automatically removes limitations of the virtual adress space and the stack size, where possible.
          • If the attempt to remove limitations fails (e.g. due to a Hardlimit), a respective message is logged.
          • In this case, the limitations must be removed in the way usual for the Linux distribution.
        • The limitation of opened file descriptors (including network sockets) must be adjusted upon occurrence of bottlenecks.
          • Errors due to a limitation of the number of opened files are displayed via the "Too many open files" error message.
          • In this case, the limitation must be extended for the user account of the PLANTA service.
          • For this purpose, the configuration mechanisms of the used Linux distribution are to be used.
          • A possible reason for a higher use of file descriptors can be an update to PLANTA Server 39.5.16, as described in the Process based architecture.

        From S 39.5.27

        Requirements
        Operation system Architecture x64
        • Windows
          • Windows Server 2016 Core
          • Windows Server 2016
          • Windows Server 2012 R2
          • Windows Server 2012
          • Linux
            • Suse Linux Enterprise 11/12
            • Red Hat Enterprise 6/7
          Database driver Supplied JDBC driver
          • Additional configuration or installation is not required anymore.
          Runtime
          • In Windows, the Distributables MSVC 2015 x64 are installed automatically if they do not exist yet
          • NEW For Linux, GLIB 2.14 or later and GCC 4.8.5 or later must be installed on the server
          • A particular Java version is not required, since the PLANTA server comes with its own Java version (Zulu). This has no influence on already existing Java versions on the system on which the PLANTA Server is installed.
          System settings
        • Linux:
          • Limitation of the virtual address space and the stack size of the application server process are not supported, therefore such limitations must be canceled under Linux.
            • The PLANTA Server automatically removes limitations of the virtual adress space and the stack size, where possible.
            • If the attempt to remove limitations fails (e.g. due to a Hardlimit), a respective message is logged.
            • In this case, the limitations must be removed in the way usual for the Linux distribution.
          • The limitation of opened file descriptors (including network sockets) must be adjusted upon occurrence of bottlenecks.
            • Errors due to a limitation of the number of opened files are displayed via the "Too many open files" error message.
            • In this case, the limitation must be extended for the user account of the PLANTA service.
            • For this purpose, the configuration mechanisms of the used Linux distribution are to be used.
            • A possible reason for a higher use of file descriptors can be an update to PLANTA Server 39.5.16, as described in the Process based architecture.

          From S 39.5.24

          Requirements
          Operation system Architecture x64
          • Windows
            • Windows Server 2016 Core NEW
            • Windows Server 2016
            • Windows Server 2012 R2
            • Windows Server 2012
            • Linux
              • Suse Linux Enterprise 11/12
              • Red Hat Enterprise 6/7
            Database driver Supplied JDBC driver
            • Additional configuration or installation is not required anymore.
            Runtime
            • MSVC 2010 x64
            • A particular Java version is not required as the PLANTA Server comes with its own Java version (Zulu). This has no influence on already existing Java versions on the system on which the PLANTA Server is installed.
            System settings
          • Linux:
            • Limitation of the virtual address space and the stack size of the application server process are not supported, therefore such limitations must be canceled under Linux.
              • The PLANTA Server automatically removes limitations of the virtual adress space and the stack size, where possible.
              • If the attempt to remove limitations fails (e.g. due to a Hardlimit), a respective message is logged.
              • In this case, the limitations must be removed in the way usual for the Linux distribution.
            • The limitation of opened file descriptors (including network sockets) must be adjusted upon occurrence of bottlenecks.
              • Errors due to a limitation of the number of opened files are displayed via the "Too many open files" error message.
              • In this case, the limitation must be extended for the user account of the PLANTA service.
              • For this purpose, the configuration mechanisms of the used Linux distribution are to be used.
              • A possible reason for a higher use of file descriptors can be an update to PLANTA Server 39.5.16, as described in the Process based architecture.

            From S 39.5.23

            Requirements
            Operation system Architecture x64
            • Windows
              • Windows Server 2016 NEW
              • Windows Server 2012 R2
              • Windows Server 2012
            • Linux
              • Suse Linux Enterprise 11/12
              • Red Hat Enterprise 6/7
            Database driver Supplied JDBC driver
            • Additional configuration or installation is not required anymore.
            Runtime
            • MSVC 2010 x64
            • A particular Java version is not required as the PLANTA Server comes with its own Java version (Zulu). This has no influence on already existing Java versions on the system on which the PLANTA Server is installed.
            System settings
          • Linux:
            • Limitation of the virtual address space and the stack size of the application server process are not supported, therefore such limitations must be canceled under Linux.
              • The PLANTA Server automatically removes limitations of the virtual adress space and the stack size, where possible.
              • If the attempt to remove limitations fails (e.g. due to a Hardlimit), a respective message is logged.
              • In this case, the limitations must be removed in the way usual for the Linux distribution.
            • The limitation of opened file descriptors (including network sockets) must be adjusted upon occurrence of bottlenecks.
              • Errors due to a limitation of the number of opened files are displayed via the "Too many open files" error message.
              • In this case, the limitation must be extended for the user account of the PLANTA service.
              • For this purpose, the configuration mechanisms of the used Linux distribution are to be used.
              • A possible reason for a higher use of file descriptors can be an update to PLANTA Server 39.5.16, as described in the Process based architecture.

            From S 39.5.20

            Requirements
            Operating system Architecture x64
            • Windows
              • Windows Server 2012
              • Windows Server 2012 R2
            • Linux
              • Suse Linux Enterprise 11/12
              • Red Hat Enterprise 6/7
            Database driver Supplied JDBC driver
            • Additional configuration or installation is not required anymore.
            Runtime
            • MSVC 2010 x64
            • NEW A particular Java version is not required as the PLANTA Server comes with its own Java version (Zulu). This has no influence on already existing Java versions on the system on which the PLANTA Server is installed.
            • Oracle Standard Edition JDK / Server JRE Java 1.7 (x64) NEW or Java 1.8 (x64)
              • When using Server JRE (Java SE Runtime Environment), the installation has to be executed exactly the way Oracle describes. Furthermore, the following variables must be set:
                • JAVA_HOME (e.g. /usr/java/jdk1.7.0_80)
                • CLASSPATH (e.g. /usr/java/jdk1.7.0_80/bin)
                • PATH (e.g. /usr/java/jdk1.7.0_80/bin:/usr/java/jdk1.7.0_80/jre/bin:$PATH)
              • In Windows systems, the JAVA_HOME environment variable is absolutely necessary . If it was not created by the Java installer itself, it must be set to the JDK directory manually.
              • If Java 1.8 is to be used, possibly existing installations of Java 1.7 must be uninstalled from the server on which the PLANTA Server is running.
              • If a more up-to-date Java version is installed afterwards, first the uninstall_planta_service.bat or uninstall_planta_service.sh and then the install_planta_service.bat or install_planta_service.sh file must be run so that PLANTA can be run on this Java version as well.
            System settings
          • Linux:
            • Limitation of the virtual address space and the stack size of the application server process are not supported, therefore such limitations must be canceled under Linux.
              • The PLANTA Server automatically removes limitations of the virtual adress space and the stack size, where possible.
              • If the attempt to remove limitations fails (e.g. due to a Hardlimit), a respective message is logged.
              • In this case, the limitations must be removed in the way usual for the Linux distribution.
            • The limitation of opened file descriptors (including network sockets) must be adjusted upon occurrence of bottlenecks.
              • Errors due to a limitation of the number of opened files are displayed via the "Too many open files" error message.
              • In this case, the limitation must be extended for the user account of the PLANTA service.
              • For this purpose, the configuration mechanisms of the used Linux distribution are to be used.
              • A possible reason for a higher use of file descriptors can be an update to PLANTA Server 39.5.16, as described in the Process based architecture.

            From S 39.5.19

            Requirements
            Operating system Architecture x64
            • Windows
              • Windows Server 2012
              • Windows Server 2012 R2
            • Linux
              • Suse Linux Enterprise 11/12
              • Red Hat Enterprise 6/7
            Database driver Supplied JDBC driver
            • Additional configuration or installation is not required anymore.
            Runtime
            • MSVC 2010 x64
            • Oracle Standard Edition JDK / Server JRE Java 1.7 (x64) NEW or Java 1.8 (x64)
              • When using Server JRE (Java SE Runtime Environment), the installation must be done exactly as required. Furthermore, the following variables must be set:
                • JAVA_HOME (e.g. /usr/java/jdk1.7.0_80)
                • CLASSPATH (e.g. /usr/java/jdk1.7.0_80/bin)
                • PATH (e.g. /usr/java/jdk1.7.0_80/bin:/usr/java/jdk1.7.0_80/jre/bin:$PATH)
              • In Windows systems, the JAVA_HOME environment variable is absolutely necessary . If it was not created by the Java installer itself, it must be set to the JDK directory manually.
              • If Java 1.8 is to be used, possibly existing installations of Java 1.7 must be uninstalled from the server on which the PLANTA Server is running.
              • If a more up-to-date Java version is installed afterwards, first the uninstall_planta_service.bat or uninstall_planta_service.sh and then the install_planta_service.bat or install_planta_service.sh file must be run so that PLANTA can be run on this Java version as well.
            System settings
          • Linux:
            • Limitation of the virtual address space and the stack size of the application server process are not supported, therefore such limitations must be canceled under Linux.
              • The PLANTA Server automatically removes limitations of the virtual adress space and the stack size, where possible.
              • If the attempt to remove limitations fails (e.g. due to a Hardlimit), a respective message is logged.
              • In this case, the limitations must be removed in the way usual for the Linux distribution.
            • The limitation of opened file descriptors (including network sockets) must be adjusted upon occurrence of bottlenecks.
              • Errors due to a limitation of the number of opened files are displayed via the "Too many open files" error message.
              • In this case, the limitation must be extended for the user account of the PLANTA service.
              • For this purpose, the configuration mechanisms of the used Linux distribution are to be used.
              • A possible reason for a higher use of file descriptors can be an update to PLANTA Server 39.5.16, as described in the Process based architecture.

            From S 39.5.18

            Requirements
            Operation system Architecture x64
            • Windows
              • Windows Server 2008 R2; min. Standard Edition
              • Windows Server 2012
              • Windows Server 2012 R2
            • Linux
              • Suse Linux Enterprise 11/12
              • Red Hat Enterprise 6/7
            Database driver Supplied JDBC driver
            • Additional configuration or installation is not required anymore.
            Runtime
          • MSVC 2010 x64
          • NEW Oracle Standard Edition JDK / Server JRE Java 1.7 (x64)
            • When using Server JRE (Java SE Runtime Environment), the Installation must be done exactly as required by Oracle.
            • In Windows systems, the JAVA_HOME environment variable is absolutely necessary. If (in JDK installations) it was not created by the Java installer itself, it must be set to the JDK directory manually.
            • If a more up-to-date Java version is installed afterwards, first the uninstall_planta_service.bat or uninstall_planta_service.sh and then the install_planta_service.bat or install_planta_service.sh file must be run so that PLANTA can run on this Java version as well.
            System settings
          • Linux:
            • Limitation of the virtual address space and the stack size of the application server process are not supported, therefore such limitations must be canceled under Linux.
              • The PLANTA Server automatically removes limitations of the virtual adress space and the stack size, where possible.
              • If the attempt to remove limitations fails (e.g. due to a Hardlimit), a respective message is logged.
              • In this case, the limitations must be removed in the way usual for the Linux distribution.
            • The limitation of opened file descriptors (including network sockets) must be adjusted upon occurrence of bottlenecks.
              • Errors due to a limitation of the number of opened files are displayed via the "Too many open files" error message.
              • In this case, the limitation must be extended for the user account of the PLANTA service.
              • For this purpose, the configuration mechanisms of the used Linux distribution are to be used.
              • A possible reason for a higher use of file descriptors can be an update to PLANTA Server 39.5.16, as described in the Process based architecture.

            From S 39.5.16

            Requirements
            Operation system Architecture x64
            • Windows
              • Windows Server 2008 R2; mind. Standard Edition
              • Windows Server 2012
              • Windows Server 2012 R2
            • Linux
              • Suse Linux Enterprise 10/11
              • Red Hat Enterprise 5/6
            Database driver Supplied JDBC driver
            • Additional configuration or installation is not required anymore.
            Runtime
          • MSVC 2010 x64
          • Oracle Standard Edition JDK Java 1.7 (x64)
            • If a more current Java version is installed later, you first have to execute the uninstall_planta_service.bat or uninstall_planta_service.sh file and afterwards the install_planta_service.bat or install_planta_service.sh file in the server directory so that PLANTA can run on this Java version as well.
            System settings
          • Linux:
            • Limitation of the virtual address space and the stack size of the application server process are not supported, therefore such limitations must be canceled under Linux.
              • The PLANTA Server automatically removes limitations of the virtual address space and the stack size, where possible.
              • If the attempt to remove limitations fails (e.g. due to a Hardlimit), a respective message is logged.
              • In this case, the limitations must be removed in the way usual for the Linux distribution.
            • NEW The limitation of opened file descriptors (including network sockets) must be adjusted upon occurrence of bottlenecks.
              • Errors due to a limitation of the number of opened files are displayed via the "Too many open files" error message.
              • In this case, the limitation must be extended for the user account of the PLANTA service.
              • For this purpose, the configuration mechanisms of the used Linux distribution are to be used.
              • A possible reason for a higher use of file descriptors can be an update to PLANTA Server 39.5.16, as described in the Process based architecture.

            From S 39.5.14

            Requirements
            Operation system Architecture x64
            • Windows
              • Windows Server 2008 R2; min. Standard Edition
              • Windows Server 2012 NEW
              • Windows Server 2012 R2 NEW
            • Linux
              • Suse Linux Enterprise 10/11
              • Red Hat Enterprise 5/6
            Database driver Supplied JDBC driver
            • Additional configuration or installation is not required anymore.
            Runtime
          • MSVC 2010 x64
          • Oracle Standard Edition JDK Java 1.7 (x64)
            • If a more current Java version is installed later, you first have to execute the uninstall_planta_service.bat or uninstall_planta_service.sh file and afterwards the install_planta_service.bat or install_planta_service.sh file in the server directory so that PLANTA can run on this Java version as well.
            System properties
          • Linux:
            • Limitations of virtual address space and stack size of the application server process are not supported. That is why they need to be canceled when you are working on Linux.
              • If possible, PLANTA server automatically removes limitations of virtual address space and stack size.
              • If the attempt of limitation canceling fails (e.g. due to a hard limit), a corresponding message is logged.
              • In this case, limitations need to be canceled in the usual Linux way.

            From S 39.5.8

            Requirements
            Operating system Architecture x64
            • Windows
              • Windows Server 2008 R2; min. Standard Edition
            • Linux
              • Suse Linux Enterprise 10/11
              • Red Hat Enterprise 5/6
            Database driver Supplied JDBC driver
            • Additional configuration or installation is not required anymore.
            Runtime
          • MSVC 2010 x64
          • Oracle Standard Edition Java 1.7 (x64)
            • If later a more current Java version is installed, you first have to execute the uninstall_planta_service.bat or uninstall_planta_service.sh file and afterwards the install_planta_service.bat or install_planta_service.sh file in the server directory so that also PLANTA can run on this Java version.
            System properties
          • Linux:
            • Limitations of virtual address space and stack size of the application server process are not supported. That is why they need to be canceled when you are working on Linux.
              • NEW If possible, PLANTA server automatically removes limitations of virtual address space and stack size.
              • If the attempt of limitation canceling fails (e.g. due to a hard limit), a corresponding message is logged.
              • In this case, limitations need to be canceled in the usual Linux way.

            From S 39.5.0

            Requirements
            Operating system Architecture x64
            • Windows
              • Windows Server 2008 R2; min. Standard Edition
            • Linux
              • Suse Linux Enterprise 10/11
              • Red Hat Enterprise 5/6
            Database driver Supplied JDBC driver
            • Additional configuration or installation is not required anymore.
            Runtime
          • MSVC 2010 x64
          • Oracle Standard Edition Java 1.7 (x64)
            • If a more up-to-date Java version is installed afterwards, first the uninstall_planta_service.bat or uninstall_planta_service.sh and then the install_planta_service.bat or install_planta_service.sh file must be run so that PLANTA can be run on this Java version as well.

            Up to S 39.5.0

            Requirements
            Architecture 32 bit
            Operating system Architecture x64
            • Windows
              • Windows Server 2012 R2
                • On this operating system, the PLANTA server component runs. However, installing the server by means of the installation script is not possible, so it has to be executed manually. In this case, please contact PLANTA hotline.
              • Windows Server 2008; min. Standard Edition
              • Windows Server 2008 R2; min. Standard Edition
            • Linux
              • Suse Linux Enterprise 10/11
              • Red Hat Enterprise 5/6
            Database driver
            • Oracle
              • Via OCI (Oracle, 32 bit client required)
            • MSSQL Server
              • Via ODBC (MSSQL server, 32 bit system DSN)
            Run time MSVC 2005
            (MS Visual C++ Redistributable)

            Hardware requirements

            From S 39.5.29

            Requirements
            CPU Minimum condition
            • NEW per core 2.2 GHz; Intel Broadwell or similar AMD server processors (2013)
            Recommended
            • NEW per core 2.5 GHz; Intel Cascade Lake or similar AMD server processors (2019)
            Notes
            • We recommend a maximum of 50 users per core (minimum two cores).
            • For more than 400 users, we recommend load balancing onto multiple servers (Round Robin).
            Main memory The main memory requirement is determined by the number of concurrent users and additional main memory.

            • Minimum condition
              • per project manager: 175 MB
              • per project team member: 60 MB
              Recommended
              • per project manager: 200 MB
              • per project team member: 70 MB
            Note
            • Regardless of the user dependent memory size, PLANTA project requires an additional main memory of 2-4 GB (per system). The real size depends on the data volume (see Database Requirements).
            Hard disk capacity 2 GB per installed PLANTA system
            Network
            Client <> Application server
            The client data traffic is similar to that of opening a website. Significant data transfer only arises through the interaction of users.

            Opening and viewing a medium sized project (schedule) causes a network load of, e.g., approx. 250 Kb if a compressing IPSec VPN tunnel is used. The communication effort is determined by the module constructions and the amount of data to be displayed - the schedule serves as an exemplary case

            Recommendation for bandwith
            • 25 clients that are simultaneously active: 100 Mbit/s
            • > 25 Clients that are simultaneously active: 1 Gbit/s
            By means of message compression, the mentioned network load caused by opening the schedule of a medium sized project can be decreased to approx. 30 kb. So even with a more narrow bandwidth, an acceptable performance (with regards to client server communication) can be achieved.
            Network
            Application server <> Database
            The application performance essentially depends on the latency time between the application and the database server. The longer the latency time, the worse is the performance of PLANTA project.

            • Minimum condition
              • 1 Gbit/s; latency 1 ms
            • Recommended
              • 1 Gbit/s; latency 1 ms

            From S 39.5.21

            Requirements
            CPU Minimum condition
            • NEW per core 2,0 GHz; Intel Ivy Bridge or similar AMD server processors (2013)
            Recommended
            • NEW per core 3 GHz; Intel Broadwell or similar AMD server processors (2016)
            Notes
            • We recommend 50 users per core (minimum two cores).
            • For more than 400 users, we recommend load balancing to multiple servers (Round Robin).
            Main memory The main memory requirement is determined by the number of concurrent users and additional main memory.

            • Minimum condition
              • per project manager: 175 MB
              • per project team member: 60 MB
              Recommended
              • per project manager: 200 MB
              • per project team member: 70 MB
            Note
            • Regardless of the user dependent memory size, PLANTA project requires an additional main memory of 2-4 GB (per system). The real size depends on the data volume (see Database Requirements).
            Hard disk capacity 2 GB per installed PLANTA system
            Network
            Client <> Application server
            The client data traffic is similar to that of opening a website. Significant data transfer only arises through the interaction of users.

            Opening and viewing a medium sized project (schedule) causes a network load of, e.g., approx. 250 Kb if a compressing IPSec VPN tunnel is used. The communication effort is determined by the module constructions and the amount of data to be displayed - the schedule serves as an exemplary case

            Recommendation for bandwith
            • 25 clients that are simultaneously active: 100 Mbit/s
            • > 25 Clients that are simultaneously active: 1 Gbit/s
            By means of message compression, the mentioned network load caused by opening the schedule of a medium sized project can be decreased to approx. 30 kb. So even with a more narrow bandwidth, an acceptable performance (with regards to client server communication) can be achieved.
            Network
            Application server <> Database
            The application performance essentially depends on the latency time between the application and the database server. The longer the latency time, the worse is the performance of PLANTA project.

            • Minimum condition
              • 1 Gbit/s; latency 1 ms
            • Recommended
              • 1 Gbit/s; latency 1 ms

            From S 39.5.2

            Requirements
            CPU Minimum condition
            • per core 2,4 GHz; Intel Nehalem or similar AMD Server processors (2009)
            Recommended
            • per core 2,5 GHz; Intel Sandy Bridge or similar AMD server processors (2011)
            Notes
            • We recommend 50 users per core.
            • For more than 400 users, we recommend load balancing to multiple servers (Round Robin).
            Main memory The main memory requirement is determined by the number of concurrent users and additional main memory.

            • Minimum condition
              • per project manager: 175 MB
              • per project team member: 60 MB
              Recommended
              • per project manager: 200 MB
              • per project team member: 70 MB
            Regardless of user related memory requirements, PLANTA project requires an additional main memory of 2-4 GB (per system). The real size depends on the data volume (see Database Requirements).
            Hard disk capacity 2 GB per installed PLANTA system
            Network
            Client <> Application server
            The client data traffic is similar to that of opening a website. Significant data transfer only arises through the interaction of users.

            Opening and viewing a medium sized project (schedule), e.g., causes a network load of approx. 250 kb if a compressing IPSec VPN tunnel is used. The communication effort is determined by the module constructions and the amount of data to be displayed - the schedule serves as an exemplary case

            Recommendation for bandwith
            • < = 25 clients that are simultaneously active: 100 Mbit/s
            • > 25 Clients that are simultaneously active: 1 Gbit/s

            By means of NEW message compression, the mentioned network load caused by opening the schedule of a medium sized project can be decreased to approx. 30 kb. So even with a more narrow bandwidth, an acceptable performance (with regards to client server communication) can be achieved.
            Network
            Application server <> Database
            The application performance essentially depends on the latency time between the application and the database server. The longer the latency time, the worse is the performance of PLANTA project.

            • Minimum condition
              • 1 Gbit/s; latency 1 ms
            • Recommended
              • 1 Gbit/s; latency 1 ms

            From S 39.5.0

            Requirements
            CPU Minimum condition
            • per core 2,4 GHz; Intel Nehalem or similar AMD Server processors (2009)
            Recommended
            • per core 2,5 GHz; Intel Sandy Bridge or similar AMD server processors (2011)
            Notes
            • We recommend 50 users per core.
            • For more than 400 users, we recommend load balancing to multiple servers (Round Robin).
            Main memory The main memory requirement is determined by the number of concurrent users and additional main memory.

            • Minimum condition
              • per project manager: 175 MB
              • per project team member: 60 MB
              Recommended
              • per project manager: 200 MB
              • per project team member: 70 MB
            Regardless of user related memory requirements, PLANTA project requires an additional main memory of 2-4 GB (per system). The real size depends on the data volume (see Database Requirements).
            Hard disk capacity 2 GB per installed PLANTA system
            Network
            Client <> Application server
            The client data traffic is similar to that of opening a website. Significant data transfer only arises through the interaction of users.

            Opening and viewing a medium sized project (schedule), e.g., causes a network load of approx. 250 kb if a compressing IPSec VPN tunnel is used. The communication effort is determined by the module constructions and the amount of data to be displayed - the schedule serves as an exemplary case

            Recommendation for bandwith
            • < = 25 clients that are simultaneously active: 100 Mbit/s
            • > 25 Clients that are simultaneously active: 1 Gbit/s
            Network
            Application server <> Database
            The application performance essentially depends on the latency time between the application and the database server. The longer the latency time, the worse is the performance of PLANTA project.

            • Minimum condition
              • 1 Gbit/s; latency 1 ms
            • Recommended
              • 1 Gbit/s; latency 1 ms

            Up to S 39.5.0

            Requirements
            CPU Minimum condition
            • per core 2,4 GHz; Intel Nehalem or similar AMD Server processors (2009)
            Recommended
            • per core 2,5 GHz; Intel Sandy Bridge or similar AMD server processors (2011)
            Notes
            • We recommend 50 users per core.
            • For more than 400 users, we recommend load balancing to multiple servers (Round Robin).
            Main memory The main memory requirement is determined by the number of concurrent users and additional main memory.

            • Minimum condition
              • per project manager: 150 MB
              • per project team member: 100 MB
              Recommended
              • per project manager: 200 MB
              • per project team member: 100 MB
            Regardless of user related memory requirements, PLANTA project requires an additional main memory of 2-4 GB. The real size depends on the data volume (see Database Requirements).
            Hard disk capacity 2 GB per installed PLANTA system
            Network
            Client <> Application server
            The client data traffic is similar to that of opening a website. Significant data transfer only arises through the interaction of users.

            Opening and viewing a medium sized project (schedule), e.g., causes a network load of approx. 250 kb if a compressing IPSec VPN tunnel is used. The communication effort is determined by the module constructions and the amount of data to be displayed - the schedule serves as an exemplary case

            Recommendation for bandwith
            • < = 25 clients that are simultaneously active: 100 Mbit/s
            • > 25 Clients that are simultaneously active: 1 Gbit/s
            Network
            Application server <> Database
            The application performance essentially depends on the latency time between the application and the database server. The longer the latency time, the worse is the performance of PLANTA project.

            • Minimum condition
              • 1 Gbit/s; latency 1 ms
            • Recommended
              • 1 Gbit/s; latency 1 ms

            Database Requirements

            From S 39.5.29

            Requirements
            Supported DBMS Oracle Database
            • Enterprise Edition
            • Standard Edition
            • Standard Edition ONE
            • XE ( Only for test and demonstration purposes up to a maximum of 10 users)
            Versions
            • NEW 19c
              • When you use DBMS Oracle 19c, the database must be configured in a way that renders it compatible with jdbc6. Please let us know if this is not possible in your case.
            • NEW 18c
              • When using DBMS Oracle 18c, the database must be configured in a way that renders it compatible with jdbc6. Please let us know if this is not possible in your case.
            • 12c (12.2)
            • 12.1
              • When you use DBMS Oracle 12.1, Oracle patch 20830993 must be installed to ensure the correct functioning of the PLANTA indices (see also Technical FAQ).

            Microsoft SQL Server
            • Enterprise Edition
            • Standard Edition
            • Express Edition ( Only for tests and demonstration purposes up to a maximum of 10 users)
            Versions
            • Version 2019
            • Version 2017
            • Version 2016
            • Version 2014
            • Version 2012
            Performance
            • 32-bit DBMS are still supported, however, 64-bit systems are more up-to-date, especially with regards to main memory and hard disk management and appropriate limitation
            • Memory
              • Host-RAID or SAN (fast hard disks)
                • PLANTA recommends SSDs.
                  • Investments in this area have shown to result in significant performance improvements.
            • The read speed of the database is important for the general performance.
              • A high write speed of the database has a positive influence on the performance of scheduling and replanning.
            Hard disk capacity Required hard disk capacity per database (essentially depends on the database volume ≙ number of tasks) depending on the extent of the individual data
            • Small: < 2.500 tasks – approx. 4 - 12 GB
            • Medium: < 25.000 tasks – approx. 6 - 18 GB
            • Large: approx. 250.000 tasks – approx. 10 - 30 GB
              Extraordinarily large amounts of individual files may require more space.
            Note
            • The best experience to date could be made with Linux in connection with Oracle.
              • If you can choose between Windows and Linux, we recommend using Linux.
            • After successful installation, about 20GB of space should remain available on the hard drive as a reserve.

            From S 39.5.28

            Requirements
            Supported DBMS Oracle Database
            • Enterprise Edition
            • Standard Edition
            • Standard Edition ONE
            • XE ( Only for test and demonstration purposes up to a maximum of 10 users)
            Versions
            • 12.2
            • 12.1
              • When using DBMS Oracle 12.1, Oracle patch 20830993 must be installed to ensure the correct functioning of the PLANTA indeces (see also Technical FAQ).

            Microsoft SQL Server
            • Enterprise Edition
            • Standard Edition
            • Express Edition ( Only for test and demonstration purposes up to a maximum of 10 users)
            Versions
            • Version 2019 NEW
            • Version 2017
            • Version 2016
            • Version 2014
            • Version 2012
            Performance
            • 32-bit DBMS are still supported, however, 64-bit systems are more up-to-date, especially with regards to main memory and hard disk management and appropriate limitation
            • Memory
              • Host-RAID or SAN (fast hard disks)
                • PLANTA recommends SSDs.
                  • Investments in this area have shown to result in significant performance improvements.
            • The read speed of the database is important for the general performance.
              • A high write speed of the database has a positive influence on the performance of scheduling and replanning.
            Hard disk capacity Required hard disk capacity per database (essentially depends on the database volume ≙ number of tasks) depending on the extent of the individual data
            • Small: < 2.500 tasks – approx. 4 - 12 GB
            • Medium: < 25.000 tasks – approx. 6 - 18 GB
            • Large: approx. 250.000 tasks – approx. 10 - 30 GB
              Extraordinarily large amounts of individual files may require more space.
            Note
            • The best experience to date could be made with Linux in connection with Oracle.
              • If you can choose between Windows and Linux, we recommend using Linux.
            • After successful installation, about 20GB of space should remain available on the hard drive as a reserve.

            From S 39.5.25

            Requirements
            Supported DBMS Oracle Database
            • Enterprise Edition
            • Standard Edition
            • Standard Edition ONE
            • XE ( Only for test and demonstration purposes up to a maximum of 10 users)
            Versions
            • 12.2
            • 12.1
              • When using DBMS Oracle 12.1, Oracle patch 20830993 must be installed to ensure the correct functioning of the PLANTA indeces (see also Technical FAQ).

            Microsoft SQL Server
            • Enterprise Edition
            • Standard Edition
            • Express Edition ( Only for test and demonstration purposes up to a maximum of 10 users)
            Versions
            • Version 2016 NEW
            • Version 2014
            • Version 2012
            Performance
            • 32-bit DBMS are still supported, however, 64-bit systems are more up-to-date, especially with regards to main memory and hard disk management and appropriate limitation
            • Memory
              • Host-RAID or SAN (fast hard disks)
                • PLANTA recommends SSDs.
                  • Investments in this area have shown to result in significant performance improvements.
            • The read speed of the database is important for the general performance.
              • A high write speed of the database has a positive influence on the performance of scheduling and replanning.
            Hard disk capacity Required hard disk capacity per database (essentially depends on the database volume ≙ number of tasks) depending on the extent of the individual data
            • Small: < 2.500 tasks – approx. 4 - 12 GB
            • Medium: < 25.000 tasks – approx. 6 - 18 GB
            • Large: approx. 250.000 tasks – approx. 10 - 30 GB
              Extraordinarily large amounts of individual files may require more space.
            Note
            • The best experience to date could be made with Linux in connection with Oracle.
              • If you can choose between Windows and Linux, we recommend using Linux.
            • After successful installation, about 20GB of space should remain available on the hard drive as a reserve.

            From S 39.5.24

            Requirements
            Supported DBMS Oracle Database
            • Enterprise Edition
            • Standard Edition
            • Standard Edition ONE
            • XE ( Only for test and demonstration purposes up to a maximum of 10 users)
            Versions
            • 12.2
            • 12.1
              • When using DBMS Oracle 12.1, Oracle patch 20830993 must be installed to ensure the correct functioning of the PLANTA indeces (see also Technical FAQ).

            Microsoft SQL Server
            • Enterprise Edition
            • Standard Edition
            • Express Edition ( Only for test and demonstration purposes up to a maximum of 10 users)
            Versions
            • Version 2014
            • Version 2012
            Performance
            • 32-bit DBMS are still supported, however, 64-bit systems are more up-to-date, especially with regards to main memory and hard disk management and appropriate limitation
            • Memory
              • Host-RAID or SAN (fast hard disks)
                • PLANTA recommends SSDs.
                  • Investments in this area have shown to result in significant performance improvements.
            • The read speed of the database is important for the general performance.
              • A high write speed of the database has a positive influence on the performance of scheduling and replanning.
            Hard disk capacity Required hard disk capacity per database (essentially depends on the database volume ≙ number of tasks) depending on the extent of the individual data
            • Small: < 2.500 tasks – approx. 4 - 12 GB
            • Medium: < 25.000 tasks – approx. 6 - 18 GB
            • Large: approx. 250.000 tasks – approx. 10 - 30 GB
              Extraordinarily large amounts of individual files may require more space.
            Note
            • The best experience to date could be made with Linux in connection with Oracle.
              • If you can choose between Windows and Linux, we recommend using Linux.
            • After successful installation, about 20GB of space should remain available on the hard drive as a reserve.

            From S 39.5.21 / DB 39.5.9

            Requirements
            Supported DBMS Oracle Database
            • Enterprise Edition
            • Standard Edition
            • Standard Edition ONE
            • XE ( Only for tests and demo purposes up to a max. of 10 users)
            Versions
            • 12.2
            • 12.1
              • When using DBMS Oracle 12.1, Oracle patch 20830993 needs to be installed in order to assure the PLANTA indices functionality is working correctly (for this, please also see Technical FAQs).
            • 11g R2 (from 11.2.0.1)

            Microsoft SQL-Server
            • Enterprise Edition
            • Standard Edition
            • Express Edition ( Only for tests and demo purposes up to a max. of 10 users)
            Versions
            • Version 2014
            • Version 2012 R2
            • Version 2008
            Performance
            • 32-bit DBMS are still supported, however, 64-bit systems are more up-to-date, especially with regards to main memory and hard disk management and appropriate limitation
            • Memory
              • Host-RAID or SAN (fast hard disks)
                • PLANTA recommends SSDs.
                  • Investments in this area have shown to result in significant performance improvements.
            • The read speed of the database is important for the general performance.
              • A high write speed of the database has a positive influence on the performance of scheduling and replanning.
            Hard disk capacity Required hard disk capacity per database (essentially depends on the database volume ≙ number of tasks) depending on the extent of the individual data
            • Small: < 2.500 tasks – approx. 4 - 12 GB
            • Medium: < 25.000 tasks – approx. 6 - 18 GB
            • Large: approx. 250.000 tasks – approx. 10 - 30 GB
              Extraordinarily large amounts of individual files may require more space.
            Note
            • The best experience to date could be made with Linux in connection with Oracle.
              • If you can choose between Windows and Linux, we recommend using Linux.
            • After successful installation, about 20GB of space should remain available on the hard drive as a reserve.

            From S 39.5.19

            Requirements
            Supported DBMS Oracle Database
            • Enterprise Edition
            • Standard Edition
            • Standard Edition ONE
            • XE ( Only for tests and demo purposes up to a max. of 10 users)
            Versions
            • 12c
            • 11g R2 (from 11.2.0.1)
              • When using DBMS Oracle 12c, Oracle patch 20830993 needs to be installed in order to assure the PLANTA indices functionality is working correctly (for this, please also see Technical FAQs).

            Microsoft SQL Server
            • Enterprise Edition
            • Standard Edition
            • Express Edition ( Only for tests and demo purposes up to a max. of 10 users)
            Versions
            • Version 2014 NEW
            • Version 2012
            • Version 2008 R2
            • Version 2008
            Performance
            • 32-bit DBMS are still supported, however, 64-bit systems are more up-to-date, especially with regards to main memory and hard disk management and appropriate limitation
            • Memory
              • Host-RAID or SAN (fast hard disks)
                • PLANTA recommends SSDs.
                  • Investments in this area have shown to result in significant performance improvements.
            • The read speed of the database is important for the general performance.
              • A high write speed of the database has a positive influence on the performance of scheduling and replanning.
            Hard disk capacity Required hard disk capacity per database (essentially depends on the database volume ≙ number of tasks) depending on the extent of the individual data
            • Small: < 2.500 tasks – approx. 4 - 12 GB
            • Medium: < 25.000 tasks – approx. 6 - 18 GB
            • Large: approx. 250.000 tasks – approx. 10 - 30 GB
              Extraordinarily large amounts of individual files may require more space.
            Note
            • The best experience to date could be made with Linux in connection with Oracle.
              • If you can choose between Windows and Linux, we recommend using Linux.
            • After successful installation, about 20GB of space should remain available on the hard drive as a reserve.

            From DB 39.5.6 / S 39.5.14

            Requirements
            Supported DBMS Oracle Database
            • Enterprise Edition
            • Standard Edition
            • Standard Edition ONE
            • XE ( Only for tests and demo purposes up to a max. of 10 users)
            Versions
            • 12c NEW
            • 11g R2 (from 11.2.0.1)
              • When using DBMS Oracle 12c, Oracle patch 20830993 needs to be installed in order to assure the PLANTA indices functionality is working correctly (for this, please also see Technical FAQs).

            Microsoft SQL Server
            • Enterprise Edition
            • Standard Edition
            • Express Edition ( Only for tests and demo purposes up to a max. of 10 users)
            Versions
            • Version 2012 NEW
            • Version 2012
            • Version 2008 R2
            • Version 2008
            Performance
            • 32-bit DBMS are still supported, however, 64-bit systems are more up-to-date, especially with regards to main memory and hard disk management and appropriate limitation
            • Memory
              • Host-RAID or SAN (fast hard disks)
                • PLANTA recommends SSDs.
                  • Investments in this area have shown to result in significant performance improvements.
            • The read speed of the database is important for the general performance.
              • A high write speed of the database has a positive influence on the performance of scheduling and replanning.
            Hard disk capacity Required hard disk capacity per database (essentially depends on the database volume ≙ number of tasks) depending on the extent of the individual data
            • Small: < 2.500 tasks – approx. 4 - 12 GB
            • Medium: < 25.000 tasks – approx. 6 - 18 GB
            • Large: approx. 250.000 tasks – approx. 10 - 30 GB
              Extraordinarily large amounts of individual data may require more space.

            Note

            • The best experience to date could be made with Linux in connection with Oracle.
              • If you can choose between Windows and Linux, we recommend using Linux.
            • After successful installation, about 20GB of space should remain available on the hard drive as a reserve.

            Up to S 39.5.14

            Requirements
            Supported DBMS Oracle Database
            • Enterprise Edition
            • Standard Edition
            • Standard Edition ONE
            • XE ( Only for tests and demo purposes up to a max. of 10 users)
            Version
            • 11g R2 (from 11.2.0.1)

            Microsoft SQL Server Is only supported for PLANTA project 39.4 DB version
            • Enterprise Edition
            • Standard Edition
            • Express Edition ( Only for tests and demo purposes up to a max. of 10 users)
            Versions
            • Version 2008 R2
            • Version 2008
            Performance
            • 32-bit DBMS are still supported, however, 64-bit systems are more up-to-date, especially with regards to main memory and hard disk management and appropriate limitation
            • Memory
              • Host-RAID or SAN (fast hard disks)
                • PLANTA recommends SSDs.
                  • Investments in this area have shown to result in significant performance improvements.
            • The read speed of the database is important for the general performance.
              • A high write speed of the database has a positive influence on the performance of scheduling and replanning.
            Hard disk capacity Required hard disk capacity per database (essentially depends on the database volume ≙ number of tasks) depending on the extent of the individual data
            • Small: < 2.500 tasks – approx. 4 - 12GB
            • Medium: < 25.000 tasks – approx. 6 - 18 GB
            • Large: approx. 250.000 tasks – approx. 10 - 30 GB
              Extraordinarily large amounts of individual data may require more space.
            Note
            • The best experience to date could be made with Linux in connection with Oracle.
              • If you can choose between Windows and Linux, we recommend using Linux.
            • After successful installation, about 20GB of space should remain available on the hard drive as a reserve.

            Oracle Database

            For the operation of PLANTA project with an Oracle database, the following is required:
            • Character set:
              • WE8ISO8859P15 (alternatively: UTF8 or WIN1252)
            • Date format:
              • NLS_DATE_FORMAT=DD.MM.RR
            • PLANTA project user rights:
              • System: grant connect, create session, create table, create index, create view, create materialized view, create procedure, create synonym, create sequence, create trigger, unlimited tablespace on „data", gathersystem_statistics, select any dictionary
              • Role: connect, gather_system_statistics
                • optionally: exp_full_database, imp_full_database

            Example

            • PLANTA project demo system:
              • Size: 4 GB
              • Tablespace management „locally managed /autoallocate"

            Note

            From S 39.5.0

            • The maximum number of connections has to be configured sufficiently large.
            • Depending on the setting of the Expected utilization parameter, at least 25, 100, or 250 connections must be allowed per PLANTA project installation.

            Up to S 39.5.0

            • Every client connection generates a database connection.
            • Accordingly, the required maximum number of connections depends on the highest number of users working simultaneously.

            Oracle Client

            From S 39.5.0

            Not required anymore

            Up to S 39.5.0

            Information
            • To operate PLANTA project, you have to install a 32 bit Oracle client version.

            Details

            • Character set:
              • NLS_LANG=GERMAN_GERMANY.WE8ISO8859P15 (Linux) or
              • NLS_LANG=GERMAN_GERMANY.WE8MSWIN1252 (Windows)
            • Date format:
              • NLS_DATE_FORMAT=DD.MM.RR
            • The SQL*Plus connection from PLANTA project server to the Oracle database is to be ensured, including the Oracle environment for the PLANTA project operating user.

            Note

            • From Oracle 10g (10.2.0.2), an Oracle script must be executed to assign Oracle library rights for PLANTA project access.
              • $ORACLE_HOME/install/changePerm.sh

            Microsoft SQL Server Database

            For the operation of PLANTA project with an MSSQL database, the following is required:
            • Character set:
              • WIN1252
                • Sort sequence: Latin1_General_CI_AS
            • Authentication:
              • SQL server authentication on the basis of 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
            • Then, create a new database with the name of the user and make the following settings there:
              • 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 default schema „dbo“ 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

            Note

            From S 39.5.0

            • The maximum number of connections has to be configured sufficiently large.
            • Depending on the setting of the Expected utilization parameter, at least 25, 100, or 250 connections must be allowed for each PLANTA project installation.

            Up to S 39.5.0

            • Every client connection generates a database connection.
            • Accordingly, the required maximum number of connections depends on the highest number of users working simultaneously.

            Microsoft SQL Server Client

            From S 39.5.0

            Not required anymore

            Up to S 39.5.0

            Details
            • Character set:
              • WIN1252
            • Installation of Enterprise Manager or SQL Server Management Studio.
            • SQL server authentification: A database source for the database server has to be set in ODBC data source administrator under System DSN.
            • An SQL connection to the Microsoft SQL server database planned for use with PLANTA project has to be ensured.

            Database Backup and Maintenance

            Information
            • PLANTA only stores user data 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 all accesses)
              • 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 operating the PLANTA software.

            Supported Interfaces/Products of the Third Party

            Information

            • PLANTA project supports the following products:

            From S 39.5.29/DB 39.5.15

            Product Version
            Microsoft Office 2019
            2016
            office 365
            Microsoft Project 2016
            SAP NetWeaver RFC 7.20
            Jira NEW 8

            From C 39.5.24/S 39.5.26/DB 39.5.11

            Product Version

            Microsoft Office

            2019 NEW
            2016
            office 365

            Microsoft Project

            2016
            SAP NetWeaver RFC 7.20

            Up to C 39.5.24/S 39.5.26/DB 39.5.11

            Product Version

            Microsoft Office

            2016
            2013
            2010
            office 365

            Microsoft Project

            2016
            2013
            2010
            SAP NetWeaver RFC 7.20

            Note

            • In order to use SAP RFC interface, you need following:
              • SAP system with NetWeaver compatible RFC implementation from version 7.20.
              • SAP RFC client libraries in 64bit-x64 version installed on the application server on which PLANTA project runs

                     PLANTA project









             
            • Suche in Topic-Namen

            • Suche in Topic-Inhalten
            This site is powered by the TWiki collaboration platform Powered by Perl