Diferencias

Muestra las diferencias entre dos versiones de la página.

--- instalacion_processmaker [2016/05/12 10:22]
10.12.12.129 creado
+++ instalacion_processmaker [2017/03/27 17:44] (actual)
@@ Línea 1: / Línea 1: @@
-==== 2.0 - ProcessMaker Generic Installation ====
+====== 2.0 - ProcessMaker Generic Installation ======
+Recurso en [[http://wiki.processmaker.com/index.php/2.0/ProcessMaker_Generic_Installation]]
 Contents: [hide]
@@ Línea 18: / Línea 20: @@
 ===== Installing ProcessMaker =====
-. Go to http://sourceforge.net/projects/processmaker/files and download a recent tarball of ProcessMaker, which should be named processmaker-2.X.X.tar.gz The versions are numbered according to the pattern MAJOR.MINOR.REVISION, such as "2.0.36". 2. Move the processmaker-2.X.X.tar.gz file which was downloaded to the directory in your server where the ProcessMaker application will be stored. ProcessMaker can be installed in any directory which is not publicly accessible to the internet (so do NOT install it in /var/www in Linux/UNIX).
+Go to http://sourceforge.net/projects/processmaker/files and download a recent tarball of ProcessMaker, which should be named processmaker-2.X.X.tar.gz The versions are numbered according to the pattern MAJOR.MINOR.REVISION, such as "2.0.36". 2. Move the processmaker-2.X.X.tar.gz file which was downloaded to the directory in your server where the ProcessMaker application will be stored. ProcessMaker can be installed in any directory which is not publicly accessible to the internet (so do NOT install it in /var/www in Linux/UNIX).
 In Linux/UNIX, it is generally installed in the /opt directory, since it is an optional program which doesn't come from the standard repositories. In Windows XP and Server 2003, it is generally installed in the C:\Program Files directory.
@@ Línea 53: / Línea 55: @@
 Modify the following virtual host definition to match your environment:
-# Please change the IP address with your server's IP address and
+  # Please change the IP address with your server's IP address and
   # the ServerName with you own subdomain for ProcessMaker.
   NameVirtualHost your_ip_address
@@ Línea 91: / Línea 93: @@
 For example, if running ProcessMaker on a Windows XP server at address 192.168.1.100 on port 8080 with a domain at processmaker.mycompany.com:
-NameVirtualHost 192.168.1.100:8080
+  NameVirtualHost 192.168.1.100:8080
- #processmaker virtual host
+  #processmaker virtual host
- <VirtualHost 192.168.1.100:8080 >
+   <VirtualHost 192.168.1.100:8080 >
    ServerName "processmaker.mycompany.com"
    DocumentRoot C:\Program Files\processmaker\workflow\public_html
@@ Línea 101: / Línea 103: @@
 For example, if running ProcessMaker on a Linux server at address server1.example.com with a domain at pm.example.com:
- NameVirtualHost server1.example.com
+  NameVirtualHost server1.example.com
- #processmaker virtual host
+  #processmaker virtual host
- <VirtualHost server1.example.com >
+  <VirtualHost server1.example.com >
    ServerName "pm.example.com"
    DocumentRoot /opt/processmaker/workflow/public_html
@@ Línea 109: / Línea 111: @@
    <Directory  "/opt/processmaker/workflow/public_html">
    ...
 For example, if ProcessMaker is installed in the "/home/fred" directory on your local machine at port 8080 with an dynamic IP assigned by DHCP:
-NameVirtualHost *:8080
+   NameVirtualHost *:8080
- #processmaker virtual host
+   #processmaker virtual host
- <VirtualHost *:8080 >
+   <VirtualHost *:8080 >
    ServerName "*"
    DocumentRoot /home/fred/processmaker/workflow/public_html
@@ Línea 119: / Línea 122: @@
    <Directory  "/home/fred/processmaker/workflow/public_html">
    ...
 Note: It is also possible to define the virtual host for ProcessMaker directly in the Apache configuration by inserting the above VirtualHost definition in the Apache configuration file, which is generally named httpd.conf.
@@ Línea 124: / Línea 128: @@
 Generic Linux/UNIX:
+  /etc/httpd/conf.d/pmos.conf
-/etc/httpd/conf.d/pmos.conf
 Debian/Ubuntu:
+  /etc/apache2/sites-available/pmos.conf
-/etc/apache2/sites-available/pmos.conf
 Then issue the command:
+  a2ensite pmos.conf
-a2ensite pmos.conf
-Windows:
-C:\wamp\bin\apache\apache2.2.8\conf\extra\pmos.conf
-If using Windows, add the following line to the httpd.conf file, so that the ProcessMaker virtual configuration can proceed:
-Include "C:\wamp\bin\apache\apache2.2.8\conf\extra\pmos.conf"
-Note: If Apache is using the default port 80, then configure Skype and other programs to not use port 80. You can check whether a program is currently listening on port 80 with netstat -anb in Windows or netstat -tanp in Linux/UNIX.
-To configure Skype to stop listening on port 80, go to Tools > Options. Under the Advanced section of the "Options" dialog box, select the Connection tab. Deselect the option Use port 80 and 443 as alternatives for incoming connections.
 ===== ProcessMaker Configuration =====
@@ Línea 164: / Línea 157: @@
 ===== Additional Configuration =====
 Additional aspects of ProcessMaker may need to be configured. See Additional Server Configuration and the Configuration section of the wiki. Most installations of ProcessMaker need to configure the following: