Refer to documentation Implementation
Fields
The following fields are present on this tab :
|
|   |
|   |
|
Close
Presentation
The grid '"Language information" is used to define the available language for the site.
Each language is associated to a set of HTML pages called "HTML Project". This grid is used to enter the default parameter that will be applied for each language. The user language code is specified in the URL via the LANG (&LANG=ENG) parameter. Indicates the HTML project language.
If this parameter is not displayed, XTEND will chose the configuration consolextend.server.gensetup.deflangparameter.
The action ASESSSWITCHLANG is used to switch the language.
List of web services pools used by the site. Each pool contains:
Close
Fields
The following fields are present on this tab :
Characteristics
|
|
|
|   |
|
Grid Language-related informations
| An HTML project is always associated with a language. The user language code is specified in the URL via the LANG (&LANG=ENG) parameter. If this parameter is not displayed, XTEND will chose the configurationxtend.server.gensetup.deflang. parameter. The action ASESSSWITCHLANG is used to switch the language. |
|   |
|
|   |
|   |
|   |
|   |
Grid Web services pools (*)
|
| The Pool by default can be used to call web services of the site. It is mandatory to enter a pool by default and strongly advised to check that:
|
| This field enables the user to optimize the communication between Xtend servers and the web service server when both applications are hosted on the same X3WEB server.
|
Webmaster email (*)
|
Close
Fields
The following fields are present on this tab :
Default page
|
|
|
|
|
|
Protocol
| The Protocol parameter is used to define the default protocol (HTTP or HTTPS) used to display the site pages. The HTTP and HTTPS port number are given by the configuration parameter: xtend.server.gensetup.http.defhttpport et xtend.server.gensetup.http.defhttpsport. |
Tools
|
|
|
Grid Free parameters (*)
|
|
Close
Presentation
The 'root' directories are used to store XTEND files. Resources (files, images) in these directories can be accessed from the browser via images or attachments tokens.
Design HTML and X_FILES can be placed under the X3 server (by default) or the X3Web server.
X_FILEAPP and X_TEND are always placed under the X3 server.
The HTTP protocol suggests instructions (HTTP Headers) that can be used to manage resource storage (images, PDF...) in the cache memory (caching) of the browser.
The server application decides, through theses instructions, the expiry date (not validated) of the resource.
This date defines the time period during which these resources must be considered as valid by the browser. Once the expiry date is reached, the resource will be asked to the server again (refreshed).
An efficient control of the cache management can be used to optimize the display time of pages.
The parameters Design HTML, X_FILEAPP, X_FILES, X_TEND, Flash are used to define the expiry date of these directories' resources:
The validity time is generated by XTEND in the resource's URL:
/xtend/data/exp(86400,65799)/remote/SOLPAIE/PAIE/X_TEND/X_HTML/FDBTEST/FRA/IMG/img1.jpg
To overload the validity period of the resource compared to the one defined by default, the user should use the ?exp=seconds parameter in the URL:
<img src="xtend/data/exp(86400,65799)/remote/SOLPAIE/PAIE/X_TEND/X_HTML/FDBTEST/FRA/IMG/img1.jpg?exp=30/">
When the directory that contains the resource is located in local X3WEB server, the management of the cache is delegated to the page's MEGA tags and to the Apache server (httpd.conf).
It is important to ask this question for each type of resource used by the site.
For instance, all resources that constitute the static HTML page and that can have an important size (images, CSS, JavaScript) are never modified (on the production site) and have a limited freshness period.
If XTEND is parameterized so that the Design HTML folder resources have a one-week validity period, the browser will load them only once a week.
Only the dynamic data transit through the network during the display of a page.
XTEND is used by the webmaster to force the refresh (erase cache) on all browsers, of all site resources that have a validity date via the following URL.
http://host:port/xtend/svc/X3SOL/X3FLDR/XTDSITE/admin/browser/clear
This function is useful:
These parameters indicate to the XTEND server whether it should check the files updates (timestamp) of the XML dictionary and the HTML page before the display so that it can take account of the modifications.
By default, the 'HTML page' parameters and the 'Web dictionary' are checked, it means that the engine is checking each request.
This process can take 5 to 100 ms depending on the network configuration.
It is compulsory to check updates in development mode because the HTML page and the dictionary are ceaselessly modified.
In production mode, the HTML site and the dictionary are never modified and it is advised to uncheck the parameters.
The checkbox 'Default value' updates the 'HTML page' parameters and the 'Web dictionary' with their default values.
The following URL enables the user to force the reload of the dictionary whatever the parameter value may be.
http://hostname:port/xtend/svc/SolutionX3/DossierX3/SiteXtend/admin/reposit/reload.
Close
Fields
The following fields are present on this tab :
Miscellaneous
|
|
Server scripts
|
|
Localization (*)
| Specify the location of the directory that contains the HTML project on:
Location on the X3 serverThe access to the resources located on the X3 server is made possible via the XTEND server (a specialized servlet) behaving like a proxy. The browser:
Local location of the X3WEB serverIn local mode of the X3WEB server, the root of the X3_PUB directory is located under: \WebData\LOCAL\X3SOLUTION\X3_PUB\. The 'Design HTML' and X_FILES directories must be copied to this root while complying with the tree structure when in 'X3WEB server' mode. The xtend.server.data.localpath=/data/local configuration parameter is used to define the server processing type that will be prompted to access the resources in local mode. If you wish to delegate the access to the resources to the the Apache server (optimization):
|
| Specify the location of the X_FILES (X3_PUB/X3FOLDER/X_TEND/X_FILES) directory on:
Location on the X3 serverThe access to the resources located on the X3 server is made possible via the XTEND server (a specialized servlet) behaving like a proxy. The browser:
Local location of the X3WEB serverIn local mode of the X3WEB server, the root of the X3_PUB directory is located under: \WebData\LOCAL\X3SOLUTION\X3_PUB\. The 'Design HTML' and X_FILES directories must be copied to this root while complying with the tree structure when in 'X3WEB server' mode. The xtend.server.data.localpath=/data/local configuration parameter is used to define the server processing type that will be prompted to access the resources in local mode. If you wish to delegate the access to the resources to the the Apache server (optimization):
|
| Specify the location of directories that contains the FLASH(/X3_PUB/X3_ROOT/X3CLI/XBLOCK/FLASH) component on:
Location on the X3 serverThe access to the resources located on the X3 server is made possible via the XTEND server (a specialized servlet) behaving like a proxy. The browser:
Local location of the X3WEB serverIn local mode of the X3WEB server, the root of the X3_PUB directory is located under: \WebData\LOCAL\X3SOLUTION\X3_PUB\. The 'Design HTML' and X_FILES directories must be copied to this root while complying with the tree structure when in 'X3WEB server' mode. The xtend.server.data.localpath=/data/local configuration parameter is used to define the server processing type that will be prompted to access the resources in local mode. If you wish to delegate the access to the resources to the the Apache server (optimization):
|
HTTP cache expires (*)
|
|
|
|
|
|
Check update (*)
|
|
|
Close
By default, the following reports are associated with this function :
PRTSCR : Screen print
This can be changed using a different setup.
This button is used to copy the site record. |
Used to define the selected site as the current site.
Used to access the XTEND pool setup.
Fields
The following fields are included in this window :
| Identifier for the connection pool. |
|   |
| SAFEX3 solution code. These are the codes of the solution and the X3 folder. |
| SAFEX3 folder code. These are the codes of the solution and the X3 folder. |
| Identifier of the web service. Used to differentiate connection pools with the same declared name on different X3WEB servers. |
Close
Fields
The following fields are included in this window :
Configuration
| X3WEB server hostname or IP address. |
| X3WEB server listening port (by default, 28880). |
| X3WEB server name if it can be accessed from outside. |
| X3WEB server port listen to from outside. |
| Maximum number of X3 connections for the pool. |
| Number of X3 connections open at the start of the pool. |
User
| Use of the web service pool. |
| Web service pool password. |
| Connection language of the Web service pool. |
Grid X3 WAS alias
| This is the XTEND pool identifier. |
|   |
| The user can use the https protocol for calling web services. |
| This is the maximum waiting time (in ms) for a web service request answer (SOAP). Once this waiting time has been reached, the XTEND sever remove an exception. |
| By default, the login and password are those used by the XTEND server:
The information will be taken into by the XTEND server if:
|
|   |
|   |
Close
This tool is used to regenerate the directories where files linked to sites are stored (HTML pages, resources, images...).
This tool is used to check that the directories where files linked to sites are stored (HTML pages, resources, images...) are generated.
This tool is used to delete the directories where files linked to sites are stored (HTML pages, resources, images...).
Some resources must be protected in read mode, i.e. they must be readable only by the current XTEND user.
To protect a resource in reading mode:
If another user tries to open this URL, the XTEND server will send a HTTP 404 error.
The name of the protected directory can be parameterized via the xtend.server.data.protectdir. console.
The protection of resources does not work if the access to resources is processed by Apache (see localization on X3WEB).
For example:
If the XTEND application generates reports (orders, invoices...) upon request of the user, the .pdf files created must be protected in reading mode:
The access to all /x_protect/* files will be protected.