Page Comparison

This section describes how to add a new website (also called a "webinitiative" in XperienCentral) to an existing installation.

In This Section

...

Expanding the Directory Structure

For each new webinitiative, the directory structure needs to be expanded so the files from the new webinitiative will have their own place in the overall directory structure. In the directory structure below the new directories are shown after \wm:.

...

cd D:\GX-WebManager\wwwroot
mkdir mysecondsite
cd mysecondsite
mkdir cfg
mkdir upload
mkdir upload_mm
junction static ..\mywebsite\static
junction wm ..\mywebsite\wm

Back to top

...

Make the New Hostnames Resolvable

The server on which XperienCentral is installed needs to be able to resolve the hostnames that are used for the Edit environment and the external environment of XperienCentral. In this example the hostnames are “www.mysecondsite.com” and “edit.mysecondsite.com”. If the hostnames don’t resolve to the correct IP address on the server, add them to the file
c:\windows\system32\drivers\etc\hosts.

Back to top

...

Change the IIS Configuration

When adding a new webinitiative to XperienCentral, the configuration of the IIS webserver also needs to be modified. For each new webinitiative in XperienCentral, there will be two new websites in IIS: one for the frontend and one for the Edit environment. Follow the steps as described in /wiki/spaces/PD/pages/24721431 for creating a new frontend website. Follow the steps in /wiki/spaces/PD/pages/24721431 to create a new website for the Edit environment.

Back to top

...

Communicate Technical Details to the Software Developer

The system administrator needs to provide the following information to the developer:

• Hostname of the website and the edit environment (in the example from this document this would be www.mysecondsite.com and edit.mysecondsite.com);
• The DocumentRoot of the new website (in the example from this document this would be d:\xperiencentral\wwwroot\mysecondsite).

Back to top

...

Request a New configuration.xml

The configuration.xml contains a list of hostnames which will be supported by XperienCentral. The new hostnames for the new webinitiative have to be present in the configuration.xml, otherwise it is not possible to create the new webinitiative in XperienCentral. The software developer requests a new configuration.xml from GX Software; he or she then communicates the new hostnames that XperienCentral has to support. After the software developer has received the new configuration.xml from GX, he or she will send this file to the system administrator.

Back to top

...

Process the New configuration.xml

The System Administrator saves the new configuration.xml over the old one. Based on the directory structure in this document, the new configuration.xml has to be saved to D:\XperienCentral\configuration.

Back to top

...

Create the New Webinitiative within XperienCentral

The software developer can now create the new webinitiative within XperienCentral. XperienCentral has a wizard for creating the new webinitiative. In step 2 of this wizard, technical details are requested, therefore it is a good idea to gather this information before starting the wizard. The required details are:

...