Directory structure | Description |
---|---|
/ | Besides the subdirectories described below, it contains the Java core of the program in PlantaServer.jar as well as some scripts for installing or starting the server. The server should not be started via these scripts but via the corresponding scripts of the PLANTA service . |
config | Here, the config files are located, that determine how PLANTA behaves. hibernate.cfg.xml (defines the database connection), planta_server.conf and globals.conf (server behavior, connection to the client) are of particular importance.Note: These files are already configured during the PLANTA server installation and usually don't have to be adjusted manually. Further Information on the config files |
dlls | Contains native libraries (system close code in C) including the core library of the PLANTA Server (planta.dll / libplanta.so ) |
jars | Contains files for the Java server (hence, for the configurable connection to the database, multi-client connections), especially for hibernate libraries |
log | Contains the logfiles created by the server |
migration | NEW Contains migration packets and the corresponding SQL files. They are usually run automatically after the installation (see carrying out the migration). For further information on the migration, see migration process. |
py | Contains the Python files. Further information can be found at Python integration. |
api | Contains the API methods of the PLANTA software |
ppms | Contains the current API |
customizing | Contains the customizing relevant API methods |
earth | Contains the customizing files for 39.4 |
venus | Contains the customizing files for 39.5 |
server | Contains the customizing relevant API methods |
wrapper | Contains the wrapper structure |
planta | Contains the new API |
distribution | Contains the default Python library |
pysrc | Contains program libraries of third party providers for remote debugging with eclipse |
sql | Contains sql subdirectories |
migration | Here, three scripts are located (for each, MSSQL, or Oracle), which are automatically run during the installation. |
planta_de | Contains sql-scripts that are run by the migration scripts during the automatic migration of the database (see Carrying out the Migration). |
yajsw | Short for „yet another java service wrapper" – contains functionality for starting and administrating the PLANTA Server as a service (PLANTA service) |
bat | Contains scripts (for Windows or Linux, depending on the operation system used), with which the PLANTA service can e.g. be installed, started, stopped, or its status can be retrieved (see PLANTA service ) |
conf | Contains configuration files for the PLANTA service. These files are already configured during the installation and are not to be adjusted manually. |
lib, scripts, temp | Contains internal libraries for the Java Service Wrapper |
Directory structure | Description |
---|---|
/ | Besides the subdirectories described below, it contains the Java core of the program in PlantaServer.jar as well as some scripts for installing or starting the server. The server should not be started via these scripts but via the corresponding scripts of the PLANTA service . |
config | Here, the config files are located, that determine how PLANTA behaves. hibernate.cfg.xml (defines the database connection), planta_server.conf and globals.conf (server behavior, connection to the client) are of particular importance.Note: These files are already configured during the PLANTA server installation and usually don't have to be adjusted manually. Further Information on the config files |
dlls | Contains native libraries (system close code in C) including the core library of the PLANTA Server (planta.dll / libplanta.so ) |
jars | Contains files for the Java server (hence, for the configurable connection to the database, multi-client connections), especially for hibernate libraries |
log | Contains the logfiles created by the server |
migration | Contains migration packets for the migration of database 39.4.4.0 to S 39.5.0 They are usually run automatically after the installation (see carrying out the migration). For further information on the migration, see migration process. |
py | Contains the Python files. Further information can be found at Python integration. |
customer | Contains the customized Python files as well as files that change or expand the standard functionalities.
|
planta_ch | Contains the Python files by PLANTA Switzerland |
planta_de | %Contains the new import wrapper. The real files are located at /customizing/ and /server/ . |
pysrc | Contains the files for the Python debugger |
system | Contains the former import wrapper. The files in the subdirectories of this directory
|
api NEW | Contains the API methods of the PLANTA software |
ppms NEW | Contains the current API |
customizing NEW | Contains the customizing relevant API methods |
earth NEW | Contains the customizing files for 39.4 |
venus NEW | Contains the customizing files for 39.5 |
server NEW | Contains the server relevant API methods |
wrapper NEW | Contains the wrapper structure |
planta NEW | Contains the new API |
distribution NEW | Contains the default Python library |
pysrc NEW | Contains program libraries by third party providers for remote debugging with eclipse |
sql | Contains sql subdirectories |
migration | Here, three scripts are located (for each, MSSQL, or Oracle), which are automatically run during the installation. |
planta_de | Contains sql scripts that are run by the migration scripts during the automatic migration of the database (see Carrying out the Migration) |
yajsw | Short for „yet another java service wrapper" – contains functionality for starting and administrating the PLANTA Server as a service (PLANTA service) |
bat | Contains scripts (for Windows or Linux, depending on the operation system used), with which the PLANTA service can e.g. be installed, started, stopped, or its status can be retrieved (see PLANTA service ) |
conf | Contains configuration files for the PLANTA service. These files are already configured during the installation and are not to be adjusted manually. |
lib, scripts, temp | Contains internal libraries for the Java Service Wrapper |
Directory structure | Description |
---|---|
/ | Besides the subdirectories described below, it contains the Java core of the program in PlantaServer.jar as well as some scripts for installing or starting the server. The server should not be started via these scripts but via the corresponding scripts of the PLANTA service . |
config | Here, the config files are located, that determine how PLANTA behaves. hibernate.cfg.xml (defines the database connection), planta_server.conf and globals.conf (server behavior, connection to the client) are of particular importance.Note: These files are already configured during the PLANTA server installation and usually don't have to be adjusted manually. Further Information on the config files |
dlls | Contains native libraries (system close code in C) including the core library of the PLANTA Server (planta.dll / libplanta.so ) |
jars | Contains files for the Java server (hence, for the configurable connection to the database, multi-client connections), especially for hibernate libraries |
log | Contains the logfiles created by the server |
migration | Contains migration packets for the migration of database 39.4.4.0 to S 39.5.0 They are usually run automatically after the installation (see carrying out the migration). For further information on the migration, see migration process. |
py | Contains the Python files. Further information can be found at Python integration. |
customer | Contains the customized Python files as well as files that change or expand the standard functionalities.
|
planta_ch | Contains the Python files of PLANTA Switzerland |
planta_de | Contains the standard Python files as provided with the standard |
pysrc | Contains the files for the Python debugger |
system | Contains the old import wrapper. The files in the subdirectories of this directory
|
sql | Contains sql subdirectories |
migration | NEW Here, three scripts are located (for each, MSSQL, or Oracle), which are automatically run during the installation. |
planta_de | Contains sql scripts that are run by the migration scripts during the automatic migration of the database (see Carrying out the Migration) |
yajsw | Short for „yet another java service wrapper" – contains functionality for starting and administrating the PLANTA Server as a service (PLANTA service) |
bat | Contains scripts (for Windows or Linux, depending on the operation system used), with which the PLANTA service can e.g. be installed, started, stopped, or its status can be retrieved (see PLANTA service ) |
conf | Contains configuration files for the PLANTA service. These files are already configured during the installation and are not to be adjusted manually. |
lib, scripts, temp | Contains internal libraries for the Java Service Wrapper |
Directory structure | Description |
---|---|
/ | Besides the subdirectories described below, it contains the Java core of the program in PlantaServer.jar as well as some scripts for installing or starting the server. The server should not be started via these scripts but via the corresponding scripts of the PLANTA service . |
config | Here, the config files are located, that determine how PLANTA behaves. hibernate.cfg.xml (defines the database connection), planta_server.conf and globals.conf (server behavior, connection to the client) are of particular importance.Note: These files are already configured during the PLANTA server installation and usually don't have to be adjusted manually. Further Information on the config files |
dlls | Contains native libraries (system close code in C) including the core library of the PLANTA Server (planta.dll / libplanta.so ) |
jars | Contains files for the Java server (hence, for the configurable connection to the database, multi-client connections), especially for hibernate libraries |
log | Contains the logfiles created by the server |
migration | Contains migration packets for the migration of database 39.4.4.0 to S 39.5.0 They are usually run automatically after the installation (see carrying out the migration). For further information on the migration, see migration process. |
py | Contains the Python files. Further information can be found at Python integration. |
customer | Contains the customized Python files as well as files that change or expand the standard functionalities.
|
planta_ch | Contains the Python files of PLANTA Switzerland |
planta_de | Contains the standard Python files as provided with the standard |
pysrc | Contains the files for the Python debugger |
system | Contains the old import wrapper. The files in the subdirectories of this directory
|
sql | Contains sql subdirectories |
migration | Here, there are three scripts each for MSSQL or Oracle, that must be executed manually immediately after the installation has finished (see preparation of the database). |
planta_de | Contains sql scripts that are run by the migration scripts during the automatic migration of the database (see Carrying out the Migration) |
yajsw | Short for „yet another java service wrapper" – contains functionality for starting and administrating the PLANTA Server as a service (PLANTA service) |
bat | Contains scripts (for Windows or Linux, depending on the operation system used), with which the PLANTA service can e.g. be installed, started, stopped, or its status can be retrieved (see PLANTA service ) |
conf | Contains configuration files for the PLANTA service. These files are already configured during the installation and are not to be adjusted manually. |
lib, scripts, temp | Contains internal libraries for the Java Service Wrapper |
Directory structure | Description |
---|---|
/ | Contains, besides the subdirectories described below, a.o. the binaries as well as the ppms.conf or planta_server.conf files in which different server parameters can be set. |
log | Contains the logfiles created by the server |
py | Contains the Python files |
Directory structure | Description |
---|---|
If you store an e-mail on a hyperlink, a copy of this mail is created in this directory. If there are no write rights on the client directory, a copy is created. | |
Help | Contains the documentation for the IronPython API of the client |
Lib | Contains the IronPython files |
Licenses | Contains the licenses for the used components |
Log | Contains the logfiles created by the server This drectory is generated if the Client is started after activating the logging with the log client parameter. |
Ole | Here, the OLE objects are stored in order to be available more quickly later. The OLE directory is generated when the client is started for the first time. |
Resources | Contains the graphics used in the client |