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

Details

• PLANTA project is made available for download in the customer area of the PLANTA Transfer Server.

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

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

Software requirements

Hardware requirements

Database Requirements

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

Oracle Client

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

Microsoft SQL Server Client

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:

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