Installing the Session Web site extension
The Session Web site extension is a core Content Delivery Server Role software component that must be installed in order for Experience Manager, one of the main user interfaces of SDL Web, to work.
- Prerequisites for the Session Web site extension
You can only add the Session Web site extension to a Web site that already has the API (RESTful) Server Role or the deprecated API (in-process) Server Role installed. - Copying resources for the Session Web site extension
Add resources for the Web site extension to your Web site. - Setting a log location for your Content Delivery software component
By default, Content Delivery software components write their log files to a folder called c:/SDLWeb/log/ (Java) or c:/SDLWeb/log/apirestnet.log (.NET). Set a proper location in the Logback configuration file, logback.xml. If your software component is installed as a .NET Web application, you may also need to activate Windows Event logging by running EventLogCreator.exe. - Preventing 404 errors on your staging Web site
Place a blank HTML file in the root of the staging Web site to prevent 404 messages on your staging Web site while editing. - Updating frame references on your staging Web site
If your staging Web site contains any link that points to the_topframe (either through atargetattribute set to the value_top, or through JavaScript), such a link will not work correctly while a user is editing the Web page. To fix this, change such target reference in one of several ways. - Installing the Session Web site extension as a Java/JSP Web application
Installing the Session Web site extension as a Java Web application may require some Web application-server specific configuration before deployment can start. - Installing the Session Web site extension as a .NET Web application
Installing the Session Web site extension as a .NET Web application requires some specific configuration before it can be deployed.