Delivery Settings

This page allows you to specify settings related to ad delivery.

Global OpenX Server Access Paths
This group of settings defines access paths to specific elements of your OpenX server. These are specified by default when you first install the application.

Admin Interface URL
The URL by which you will access your OpenX installation's user interface.

Delivery Engine URL
The URL that will be used for delivering banners. This URL will be put into all of your zone invocation tags.

Delivery Engine URL (SSL)
The URL that will be used for delivering banners over SSL connections. This URL will be put into all of your zone invocation tags.

Image Store URL
The URL that will be used for delivering banner images.

Image Store URL (SSL)
The URL that will be used for delivering banner images over SSL connections.

If you have installed OpenX in the normal way then the Administrator Interface URL needs to be "www.example.com/path/to/OpenX/www/admin ", while the the two delivery engine URLs need to be "www.example.com/path/to/OpenX/www/delivery", where " www.example.com" is your site's URL, and "path/to/OpenX" is the directory under your site where you have installed OpenX.

By default, the image URLs will be " www.example.com/path/to/OpenX/www/images", however, you would be free to change these to whatever you require, assuming you also configure OpenX to store banner images in a location that will result in the images being available via the URL(s) you select here. See Global Webserver Local Banner Storage Settings .

A word on Configuration Files

For a normal installation , OpenX will have one configuration file in the var directory: www.example.com.conf.php.
You will only be able to access OpenX via this domain name (ie. www.example.com). If your web site can also be accessed by "example.com", for instance, then OpenX will not work using this domain name. It is not recommended that you attempt to configure your configuration files so that this will work - instead, use your web server to redirect web access. So, for example, calls to "example.com/OpenX/" will be sent to "www.example.com/OpenX".

For an installation using virtual hosts, then there will be a number of configuration files, one for each domain name used. However, you will note that only one configuration file contains the real configuration for OpenX - the delivery domain configuration file, so that less file parsing is required during delivery. All other configuration files are place holders that will redirect to the real configuration file.

Global Webserver Local Banner Storage Settings

Storing method
When adding a banner to your inventory, you must choose a banner type. If you choose the Local banner (Webserver) type, you can specify where the banner you upload is stored. If you want to store the banners in a local directory set this option to Local Directory. If you want to store the banner on an external FTP server set this option to External FTP Server. On certain types of web server you may want to use the FTP option even on the local web server.

Local Directory
If you specify Local Directory, enter the full path to the desired directory in the Local Directory field.

Moving banner files from the database to a local directory
An advantage in having your image files in a separate directory, outside of the OpenX root, is that they are unaffected by subsequent upgrades. If you already have those files stored in the database, you can move them to the local directory. Firstly, as mentioned above, specify Local directory as a storing method in the Main settings:Banner settings page. Ensure that you define the Public url and and Local directory in the appropriate fields. Click Save Changes.

Now click the Maintenance tab . From the choose section drop-down list, select storage. Click the Move images stored inside the database to a directory link. Your images are moved from the database to the local directory you specified.

External FTP Server
if you specify External FTP Server, complete the details in the form. Specify the FTP Host server where OpenX needs to copy the uploaded banners to. The Host Directory path you specify needs to be in the web server's document root, as the web server must be able to serve the files directly. Do not specify a trailing slash (/). If you don't specify a directory OpenX will upload the banner to the root directory of the ftp server. If you don't specify a username and password OpenX will attempt to log in as an anonymous user with the administrator's e-mail address. Note that security can be compromised if you are able to store your banners on an FTP server that can be accessed by anonymous users and is not recommended.

Global File Names
The files named here effectively constitute the OpenX delivery engine.

Global Delivery Caching Settings
To help speed up delivery, OpenX uses a cache which includes all the information needed to deliver the banner to your website visitors. You can specify the interval between cache updates in the Time Between Cache Updates (seconds) field. The default value is 1200 seconds. Remember that changing this value is a compromise - reducing the interval updates your cache more frequently, but at the expense of more load on your adserver; increasing the interval reduces the load, but you will have to wait longer for banner and zone changes to appear on the website.

Use Remote Origin Server
Currently undocumented.

Global Banner Delivery Settings

Evaluate banner delivery limitations during delivery
This checkbox is selected by default. De-select this checkbox if you do not wish to use delivery limitations and, since OpenX would no longer check for delivery limitations during delivery, gain a small improvement in performance.

Obfuscate channel when delivering ads
Select this checkbox if you wish to prevent channel information being detected.

Allow PHP code in ads to be executed
Select this checkbox to permit PHP code in ads to be executed. Note that this is a potential security risk and due consideration should be given to the consequences of this permission.

3rd Party Click Tracking Delimiter
[to be added]

Global P3P Privacy Policies
Use P3P Policies
Internet Explorer 6 is the first browser to implement the w3c P3P standard. The P3P standard is created to protect the privacy of your users. By default Internet Explorer will reject third party cookies unless a valid privacy policy header is also sent, together with the cookies. These setting will allow you send these privacy policies headers together with the cookies which OpenX sends. If you want to enable P3P Privacy Policies, select this checkbox.

P3P Compact Policy
This is the compact policy which is sent together with cookies. The default setting is: 'cur adm our nor sta nid', which will allow Internet Explorer 6 and later to accept the cookies used by OpenX. If you want you can alter these settings to match your own privacy statement.

P3P Policy Location
If you want to use a full privacy policy, you can specify the location of the policy in this field.

Remember to click Save Changes when you have completed specifying your settings.