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

Installation of PLANTA Hybrid

Information

  • PLANTA Hybrid combines two PLANTA components: the agile PLANTA pulse component and the classical PLANTA project component. This connection (via PLANTA Hybrid), which enables synchronization of the data of both systems, allows you to benefit from the advantages of both agile and classical project management in project planning and controlling.

Requirements

The following requirements apply to the use of PLANTA Hybrid:
  • PLANTA project must be installed (at least DB 39.5.11). For information on the installation, see here.
  • PLANTA pulse must be installed. For information on the installation, see here.
  • PLANTA project and PLANTA pulse must be linked together.
  • PLANTA link must be licensed.

Settings

The following settings are required for PLANTA Hybrid (the linkage of PLANTA project and PLANTA pulse) to be ready for use:

  • PLANTA Server

From S 39.5.27

Configure the following server parameters in the web.conf for the PLANTA project system which is to communicate with the PLANTA pulse system:
  • generic_service - must be activated (true)
  • generic_service_interface - must be configured if necessary
  • generic_service_port - must be configured
  • ssl_generic_enable - must be activated (true) if you want to run PLANTA pulse on HTTPS.
  • apikey_auth_filter_generic - must be deactivated (false) since PLANTA pulse does not authenticate to the other web interfaces.
  • After you have configured the parameters, the server must be restarted.

Up to S 39.5.27

Configure the following server parameters in the web.conf for the PLANTA project system which is to communicate with the PLANTA pulse system:
  • generic_service - must be activated (true)
  • generic_service_interface - must be configured if necessary
  • generic_service_port - must be configured
  • ssl_generic_enable - must be deactivated (false) since SSL is not supported. If you want to have PLANTA pulse running on HTTPS, you have to work with a proxy/tunnel.
  • apikey_auth_filter_generic - must be deactivated (false) since PLANTA pulse does not authenticate to the other web interfaces.
  • After you have configured the parameters, the server must be restarted.

  • PLANTA link
    • Store the interfaces required for hybrid as global settings in the PLANTA Hybrid and PLANTA user synchronization areas in the PLANTA pulse and PLANTA Hybrid Parameters module and define further parameters in the PLANTA pulse area.
      • In the PLANTA Standard, all required standard interfaces are already stored by default.
    • Synchronize or link PLANTA project and PLANTA pulse users in the User Synchronization module.

The following settings must be made to enable time recording in PLANTA Hybrid:

From DB 39.5.16

  • PLANTA pulse (if you want to use extended time recording) NEW
    • Under time recording settings in the PLANTA Hybrid area, you have to
      • activate the Activate time recording on PLANTA project elements parameter and
      • configure the Protocol, Port, and Host parameters.

Please contact your PLANTA consultant if you want to use this time recording option.

Up to DB 39.5.16

  • in PLANTA project
    • Since pulse permits several postings per day, the appropriate time recording variant must be set in PLANTA project (load_creation_variant global parameter = 3).
    • The interface currently does not support automatic reverse postings, so that they should be turned off in PLANTA project (posting_cancelation global parameter = 0).

Notes

From DB 39.5.13

  • Since PLANTA Hybrid is based on web interfaces, please also observe the notes on Web Interfaces.
  • NEW If you have set-up PLANTA pulse with a self-signed certificate, the link_allow_self_signed_certificates parameter must be activated additionally.

Up to DB 39.5.13

  • Since PLANTA Hybrid is based on web interfaces, please also observe the notes on Web Interfaces.
  •          PLANTA project









     
    • Suche in Topic-Namen

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