...
Before creating a new channel, stop XperienCentral (the web server).
In This Topic
Table of Contents | ||||
---|---|---|---|---|
|
...
Generate New Hostnames
To create a second channel, two new hostnames are required: the hostname for the public channel and the hostname for the Workspacer environment. In this document www.mysecondsite.com
and cms.mysecondsite.com
will be used as examples.
...
If you use a proxy server, add excludes for these hostnames in the proxy configuration of your browsers.
Request an Updated configuration.xml from GX Software
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
Update your configuration.xml
The new configuration.xml
that you receive from GX Software has to be saved in the following locations: <xperiencentral-root>\webmanager‑webapps\webmanager‑backend‑webapp\target\webmanager‑backend‑webapp‑1.0‑SNAPSHOT\WEB‑INF\siteworks\
and <xperiencentral-root>\webmanager-webapps\webmanager‑backend‑webapp\src\main\webapp\WEB-INF\siteworks\
...
Tip |
---|
The correct location for the |
...
Create a New Channel in XperienCentral
To create the new channel in XperienCentral, follow these steps:
...
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 until you publish it. |
...
Extending the Folder Structure (Optional)
The configuration of the new channel can be extended or altered to allow separate files or presentations.
Separating Presentations
When managing multiple channels, it might be necessary to share common resources and (parts of) the presentation. In order to realize this, the following conditions must be met:
...
file_upload_directory
andfile_upload_url
(for normal uploads)file_upload_mm_directory
andfile_upload_mm_url
(for Content Repository uploads)
...
Anchor | ||||
---|---|---|---|---|
|
For organizations with several channels and multiple publication channels (multi-channel publishing) it is often essential to be able to manage content from a central location and to reuse it in multiple places. This means not only content but also web users, forms etc. In a default installation with more than one channel, all content is strictly separated. Content sharing is not done automatically, so if you want to do this you have to configure it. Most of these configuration properties involve assigning different read/write permissions for different channels. Editors of the various channels must explicitly allow one another to read and reuse content. By explicitly specifying what can be read per channel, everything can be set up in a safe and flexible manner.
...
Note |
---|
In the following sections, the term "content" is used in a broader context and is used as a synonym for content types, model types, settings, web users, etc. Language labels don't belong to this form of content. Language labels are maintained in a single object pool that is valid for all channels (see Language Labels). |
Sharing and Accepting
In order to share content between channel A and channel B, the configuration has to be changed to be able to expose (share) the content of one channel with another as well as to receive (accept) content from another channel. Sharing content is configured in three steps. For each channel, specify the following:
...
In this example, we will configure two channels so that articles from the Content repository are shared between channel A and channel B, and editors on both channel A and B are able to add new articles and to use each other’s articles on their channel.
Step 1
Which content types are available for sharing is configured in Configuration > Channel Configuration on the [Functionalities] tab under "Shared model types". In order to share the Content Repository, select it in the list. For example:
...
Repeat this step for channel B.
Steps 2 and 3
Sharing and accepting are configured in Configuration > Channel Configuration on the [Sharing/Accepting] tab:
...
When this is completed the configuration looks like this:
Channel A
Channel B
Model Types
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 | The entire Content Repository is always shared 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 | All web users are always shared 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.
...
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.