• choose a profile that was created beforehand (when updating a site for example). In this case, the information regarding the profile is automatically taken into account. All you have to do is validate.
• create a new profile (during a first setup for example).
• choose no profile. In this case, the parameters of the deployment profile will be specified when installing the site (setup via package or via physical media).

Versions 16 and later
For an update, you have the ability to create new profiles (in most cases, one profile per server) and to select them for the update. The site will be deployed on all the selected servers:

• If the site is already installed on the server, the wizard will perform an update.
• If the site is not installed on the server, the server will perform a new setup.

Remark: If the setup fails on one of the servers, the setup continues normally on the other servers.

New in version 16
For an update, you have the ability to create new profiles (in most cases, one profile per server) and to select them for the update. The site will be deployed on all the selected servers:

• If the site is already installed on the server, the wizard will perform an update.
• If the site is not installed on the server, the server will perform a new setup.

Remark: If the setup fails on one of the servers, the setup continues normally on the other servers.

For an update, you have the ability to create new profiles (in most cases, one profile per server) and to select them for the update. The site will be deployed on all the selected servers:

• If the site is already installed on the server, the wizard will perform an update.
• If the site is not installed on the server, the server will perform a new setup.

Remark: If the setup fails on one of the servers, the setup continues normally on the other servers.

Entering information on the application server

The following information must be specified:

• Server address: name of computer accessible via the network, an IP address or an Internet address.
• Characteristics of WEBDEV account: User name and password (defined in the WEBDEV account manager by the host).
• Characteristics of system User account: this account corresponds to the Windows account of the Web server that will install the WEBDEV site (this account has been selected and defined in the Hosting Control Center).

• Define the server parameters.
• Defining the site parameters.
• Specify how to transfer setup files:
  • FTP. You can define the characteristics of the FTP server (port, IP address, transfer method).
  • Versions 24 and later
    HTTP
    New in version 24
    HTTP
    HTTP
• Specify the setup commands:
  • use authenticated requests.
  • Versions 16 and later
    use the HTTPS protocol.
    New in version 16
    use the HTTPS protocol.
    use the HTTPS protocol.
  • define (if necessary) the characteristics of the proxy.

• The name of the site. By default, this name corresponds to the name of the project. You can use a different name. This enables you to deploy several instances of the same project on the same server by giving them different site names. For example, the "REWALI" project can be deployed on a Web server:
  • as REWALI: this site is intended for the travel agency X1.
  • as RESA: this site is intended for the travel agency X2.
• The domain name of SiteMap file. This parameter must be filled in the case where the name of the server used for deployment is different from the domain name used to access it. The SiteMap file is a file used by Google for referencing.
• The subdirectory containing the data files in HFSQL Classic format. The name of this subdirectory is linked to the site name. It corresponds to the name of the directory where the data files of the site are installed. This directory is a subdirectory of the data directory assigned by the host. This directory name should be modified only if several sites share the same data files.
• The name of the deployment profile. This name will be given to the deployment profile in order to easily find it (when updating the site for example).

• The name of the deployment profile. This name will be given to the deployment profile in order to easily find it (when updating the site for example).
• Server parameters ("General" tab): Ex: www.myserver.com or 10.135.15.99, WEBDEV account, Account. These parameters are the ones specified in the previous screen: "Application server settings".
• the site parameters ("General" tab):
  • Site deployment name. By default, this name corresponds to the name of the project. You can use a different name. This enables you to deploy several instances of the same project on the same server by giving them different site names. For example, the "REWALI" project can be deployed on a Web server:
    • as REWALI: this site is intended for the travel agency X1.
    • as RESA: this site is intended for the travel agency X2.
  • Domain name of SiteMap file. This parameter must be filled in the case where the name of the server used for deployment is different from the domain name used to access it. The SiteMap file is a file used by Google for referencing.
  • Directory containing the data files in HFSQL Classic format. The name of this subdirectory is linked to the site name. It corresponds to the name of the directory where the data files of the site are installed. This directory is a subdirectory of the data directory assigned by the host. This directory name should be modified only if several sites share the same data files.
  • If the site must be deployed in all languages or only for certain languages (to be selected).
• Transfer of setup files ("Advanced" tab):
  • Selecting the transfer method:
    • Versions 24 and later
      HTTP
      New in version 24
      HTTP
      HTTP
    • FTP
  • When transferring by FTP, you can specify:
    • The address of the FTP server,
    • The FTP mode: Active or passive FTP
  • Setup commands:
    • Use authenticated requests (recommended). If this option is cleared (not recommended), the setup account used will be the WEB account. In this case, the rights required for setup may not be sufficient.
    • Use HTTPS protocol (an SSL certificate must be installed on the Web server). If this box is checked, a SSL certificate must be installed on the Web server. If this certificate is not signed by a trusted authority, a warning message will be displayed during the deployment. To avoid displaying this message, check "Ignore the security warnings from HTTPS certificates".
  • Use a proxy server for the HTTP and HTTPS connections. If this box is checked, you can specify the characteristics of the proxy server to use.