...
The configuration.xml is a file with a license key that also contains the valid hostnames for your installation. To create a new channel, a new configuration.xml containing the two new hostnames is required : - Send an e‑mail to developersupport@gxsoftware.com or contact your GX Software consultant in order to obtain a new configuration.xml. If you send an e-mail, do not forget to include the two new required hostnames
...
Configure the following fields:
| Setting | Description |
|---|---|
Name | The name of the new channel. |
Identifier | The identifier of the new channel. |
Based on channel | Choose a channel here if all the parameters are similar to those of an existing channel. It is recommended to base the new channel on an existing channel, because all the configuration settings (such as paths) will be duplicated. |
Step 2 of 4: Configuration Settings for the New Channel
...
Configure the following fields:
Fields | Description |
Hostname | The hostname of the public channel. |
Generator | The hostname of the Workspace environment. |
Default e-mail address | The default e-mail address for functionality that makes use of e-mail messages. |
Folder for uploads | The folder where uploaded files are stored. |
Upload URL | The base URL for uploaded files |
Folder for multimedia uploads | The folder where binary files are stored. |
Multimedia Upload URL | The fase URL of the uploaded binary files. |
Descriptor folders | The folders where the presentation JSPs are stored. A scheduled task scans these folders for descriptor files. Multiple folders can be specified separated by semicolons. |
Redirect base directory | The base folder of the static files. |
| Note |
|---|
If desired, the above settings can be modified in the General tab of the Setup Tool after the channel has been created. |
...
In step 3 you have to confirm that you want to create a new channel. Click [Create channel]. This operation could take a few moments. The new channel with one page, the homepage, has been created. You can now log in to the channel by accessing the URL by its new hostname (+port number) followed by /web/edit. Following the example in this topic, that URL is http://cms.mysecondsite.com:8080/web/edit.
| Note |
|---|
| By default the home page of the new channel is not in the published state, therefore visitors who navigate to the front-end of that channel will see a blank page. |
...
On this tab you have the following fields:
Field | Description |
(Filter block) Select channel | Select a channel to configure. |
(Filter block) Select model type | Filter to show only specific model types. |
(Share settings) Share | Select the models that you want to share. |
(Accept settings) Accept | Select the models that you want to accept from the other channel. |
Share automatically | If this option is selected, all sharable items of the selected model type (that are available) are automatically shared |
Accept automatically | If this option is selected, all sharable items of the selected model type (that are available) are automatically accepted |
In order to share the Content Repository in this example:
...
Below is a list of all model types that can be shared. When there are no comments for a model type the individual items of a model type can be shared. For example, with the queries you can choose on a query level which queries are shared or not.
Model Type | Comment |
Application integration: filter definitions |
|
Applications |
|
| Content Repository | Always the entire Content Repository and not individual content types |
Form resources | Form resources and form steps |
Form models |
|
Form rules (all handlers) |
|
| Forms | |
Languages |
|
Page section labels |
|
Personalization | Both personalization expressions as well as personalization models |
Presentations | Only presentations and no presentation variants |
Queries |
|
| User groups | |
Web users | Always all web users and not individual web users |
...
Multiple Channels versus Language Switch
For organizations that publish content in multiple languages you can either use multiple channels or use the language switch functionality available in the Language widget. The pros and cons of both approaches are described in the table below.
Language Switch | Extra Channels |
The site structure for all language versions of the channel is the same. Not all pages have to be translated or published. | Each channel has its own site structure. |
Authorization per language is not possible. An editor can edit pages and page sections in all the available languages. | Authorization is fully adjustable per channel. Each channel has its own edit environment. |
All languages use the same presentation. | There are many ways to separate the design or share parts of the design between several channels. |
No additional license required to use multiple languages. | An additional license is required for each extra channel. |
For a straightforward one-to-one translation of a channel and when the content is translated by the same group of editors, the natural choice would be the language switch. In cases where extra functionality is required or authorization is required for each language, then you probably want to set up a separate channel and to use sharing and accepting to share content.
...