Website Manager: Add
On the add website screen, we have two tabs: General and URLs where the basic data of the website and the additional URLs are provided, respectively.
Accessible through the Administration interface or in the channel tree of the Portal Studio, by the context menu on the channel where the website is to be created.
Features
- It is an administration interface
Screens
- General
- Basic Information
- Name (string, required field, maximum size: 50) : Display name of the website, used to reference it in the portal administration. This field is mandatory and must be unique among websites.
- Static Directory (string, maximum size: 255) : Path to the directory where the static files of the website should be stored. The web server, which handles the HTTP requests, must be configured to serve the content of this directory when URLs corresponding to this website are requested. The directory must exist, and read and write permissions must be configured so that the portal process can create, read, or delete files in it. There cannot be more than one website with the same static directory or with intersections in the static directory tree. If this field is left blank, automatic detection will be used for the directory where the portal web application is installed (may not work in application servers that have issues with writing to the web application directory). This type of approach is allowed only for simple environments, where there is no web server to handle HTTP requests, and there is only one website. If more than one website is to be used in the environment, it is necessary to use a web server and define the static directories of all websites. The static directory can be specified through a simple absolute path or by using JVM system properties to compose the path. To use system properties, use ${system.properties['property_name']} as part of the path. For example: if the JVM has the system property websitesdir with the value /opt/webserver1/websites, then the path ${system.properties['websitesdir']}/internet will correspond to /opt/webserver1/websites/internet. If the value of a system property used in the static directory path is changed, the portal will not automatically move the files in the static directory; it will be the system administrator's responsibility to handle this task, which should be done with the portal offline (preferably along with the change of the system property). If the static directory path is changed through this screen, the portal will take care of moving the files it manages to the newly configured directory. However, any other file not managed by the portal will have to be manually moved to the correct directory.
- Root Channel (internal channel) : Channel of the portal that will be the root of the website.
- Priority (integer, required field) : Order in which the websites are checked to respond to a portal request. Websites with a lower priority value are checked first. That is, if there is an intersection between the URLs of two websites, the website with the lower priority value will be used.
- Integration with Google services
- Google Analytics API Key (string, maximum size: 255) : In this field, the client's access key to Google services will be defined, which can be used to generate access statistics for your content. More information in Google Analytics Integration.
- Google Maps API Key (string, maximum size: 255) : In this field, the client's access key to the Google Maps service will be defined.
- Basic Information
- URLs
- Main Base URLs : These URLs are used by the portal when it is necessary to generate an absolute URL related to the website. These URLs are mandatory. The last field of each URL, which corresponds to the path, is optional and can only be filled if you want the base URL to correspond to a more internal path. If a path is specified, it must start with '/' and end without '/'. Example: /my/path. By default, the values of the ports will be automatically filled when loading the screen with the values 80 and 443 for non-secure and secure URLs, respectively.
- Force navigation by the main URL: If this option is checked and a request is made for an additional URL of the website (see the URLs tab), the portal will respond with a redirect to one of the main URLs, according to the type of access (secure or non-secure). By default, this option is checked when adding a new website.
- Additional Base URLs : In the "Additional Base URLs" area, it is allowed to register additional URLs that this website must meet. If 'Force navigation by the main URL' is enabled, any access to an additional URL will be redirected to a main URL.
- Main Base URLs : These URLs are used by the portal when it is necessary to generate an absolute URL related to the website. These URLs are mandatory. The last field of each URL, which corresponds to the path, is optional and can only be filled if you want the base URL to correspond to a more internal path. If a path is specified, it must start with '/' and end without '/'. Example: /my/path. By default, the values of the ports will be automatically filled when loading the screen with the values 80 and 443 for non-secure and secure URLs, respectively.
Links
- Select Channel (Select)
Permissions
- Edit service instance content: Allows managing all data of this service instance with publisher profile.
Actions
- Ok