![]() ![]() Editing the ProcessMaker configuration file for Apacheįinally, change the location of the ProcessMaker code in the Apache configuration file. The contents of the compiled directory will automatically be recreated the next time that DynaForms are displayed in ProcessMaker. ![]() For example: rm -rf /usr/bin/processmaker/compiled/* Then delete ProcessMaker's compiled cache, which contains data also pointing to the old path. The srvConf.singleton file will be automatically recreated at the next login to ProcessMaker. For example: rm /usr/bin/processmaker/shared/srvConf.singleton PATH_SEP ) Īfter changing the path, then delete the binary file /shared/srvConf.singleton which contains data pointing to the old path. To: define( 'PATH_HOME', ' /usr/bin/processmaker/trunk/workflow/' ) ĭefine( 'PATH_GULLIVER_HOME', ' /usr/bin/processmaker/trunk/gulliver'. For example, change from: define( 'PATH_HOME', ' /opt/processmaker/trunk/workflow/' ) ĭefine( 'PATH_GULLIVER_HOME', ' /opt/processmaker/trunk/gulliver'. Under the ***System Directories & Paths*** section, change the paths to the new location. For example: vim /usr/bin/processmaker/workflow/engine/config/paths_installed.php Next, open the file /workflow/engine/config/paths_installed.php with a bare text editor. To: define( 'PATH_DATA', ' /usr/bin/processmaker/shared/' ) ĭefine( 'PATH_C', ' /usr/bin/processmaker/compiled/' ) For example, change the following lines from: define( 'PATH_DATA', ' /opt/processmaker/shared/' ) ĭefine( 'PATH_C', ' /opt/processmaker/compiled/' ) For example: vim /usr/bin/processmaker/workflow/engine/test/bootstrap/gulliverConstants.phpĬhange the paths to the new location. Then, open the file /workflow/engine/test/bootstrap/gulliverConstants.php with a bare text editor. ![]() For instance, if moving the code from /opt/processmaker to /usr/bin/processmaker in Linux/UNIX: mv /opt/processmaker /usr/bin/processmaker If moving the ProcessMaker code to a new location on the server, configuration files will need to be changed for Apache and in the ProcessMaker code.įirst, move the ProcessMaker code to a new location on the server. Use a bare text editor, such as Notepad or Notepad++ in Windows, vim or gedit in Linux/UNIX, to edit the configuration files and always make a backup of the files before editing them. Nonetheless, the IP address, port number, installation directory and MySQL databases can be altered after installation by editing the configuration files on the system. ProcessMaker sets its configuration settings at installation and does not provide a easy way to alter those settings from the graphical interface. Using the Workspace Backup and Restore utility.Configuring ProcessMaker for a Different Database Location.Increasing the maximum memory per session.Increasing the maximum size of uploaded files.Editing the ProcessMaker configuration file for Apache. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |