DMDAD
DMD² AD[bearbeiten]
The DMD² Ad Overlay System (DMDAD) is an application whose purpose is targeted Ad Delivery to Stores. This piece of Software has been custom programmed for DMD².
DMD² customers shall use that application to schedule the Ads they want to be played in their Stores.
Introduction[bearbeiten]
No Introduction yet :)
General[bearbeiten]
Only media types of WAVE and MP3 will be accepted. After upload, they will be converted to the connected shop's format.
Bug Report / Suggestions[bearbeiten]
Add your Bug Reports / Suggestions here.
Mantis is [Here]
Wrong Naming: Overlay[bearbeiten]
Please rename 'Overlay' to 'Ads'
Special Chars[bearbeiten]
Special Swiss Chars e.g. "ä", "ö" are not correctly interpreted. See "Täglich 15 Uhr" within the Schedules section.
Groups[bearbeiten]
Bug Report / Suggestions[bearbeiten]
Add your Bug Reports / Suggestions here.
Scheduling of Groups not working[bearbeiten]
We tried to schedule a Group containing 2 shops - but the Overlays were not played nor scheduled.
- I looked into this, this problem was due to the Schedule using misformatted overlays. The overlays "Shatner" and "Ten Easy Steps" cannot be used because they were uploaded when the client was configured with 56kbps/24kHz/Stereo and therefore need to be re-uploaded to be used successfully. I've tested using the group schedule with one of the properly encoded overlay (the lipo dvd one) and it was scheduled and played correctly. Make sense ? - Ed
- Additionally I will delete the bad overlays so they cannot be used. - Ed
Deletion of Groups not yet possible[bearbeiten]
This would be a necessity for the customer to be able to delete Groups.
- Deletion of both groups and schedules have been added. Ed.
Stores[bearbeiten]
Bug Report / Suggestions[bearbeiten]
Add your Bug Reports / Suggestions here.
Schedules[bearbeiten]
Bug Report / Suggestions[bearbeiten]
Add your Bug Reports / Suggestions here.
Scheduling of Grouped Entities does not (yet) work.[bearbeiten]
- tested with Schedule "MIGROS Groupschedule"
- tested with Overlay "Migros Test Ad 4"
- tested with Entity "2 Stores"
--> looking at the 2 stores contained in the "2 stores group" indicates that the grouped schedule has not been added.
Recurrances within the day needed[bearbeiten]
Request: Recurrance of a schedule on a "per hour" or less method should be possible. We figure that shops would want to play the special "ad" every 1.5 hours or so within the day.
Schedules cannot be deleted[bearbeiten]
Please allow Schedules to be deleted
- Deletion of both groups and schedules have been added - Ed.
Overlays[bearbeiten]
Bug Report / Suggestions[bearbeiten]
Add your Bug Reports / Suggestions here.
Renaming of 'Overlays'[bearbeiten]
It might be better to rename the term 'Overlays' to 'Ads'
- This is easy to do, shall I make this change ? - Ed
Pre-requisites[bearbeiten]
- Java 1.5 SDK Downloaded binary distribution from java.sun.com
- JBoss http://www.jboss.org/ Version: jboss-4.0.5.GA, take preconfigured install on adserver1.dmd2.ch in /usr/local/jboss-4.0.5.GA
- Icecast - special, customized version located on adserver1.dmd2.ch in /home/ezaleski/work/icecast-2.3.1
Note: It is essential to use the preconfigured jboss that is on adserver1.dmd2.ch, it can be tarred up directly and copied to another host. There are a lot of configuration files in jboss, and I could probably write a whole document on it alone.
Code Location[bearbeiten]
There are two main pieces to DMDAD, the actual DMDAD application, and the customized version of icecast that goes with it.
Here is the code for DMDAD: http://www.oddsock.org/alex/DMDAD.current.tar.gz Here is the code for The DMDAD modified Icecast: http://www.oddsock.org/alex/icecast-2.3.1_DMDAD.tar.gz
Configuration Files[bearbeiten]
System Software Configs[bearbeiten]
Application Software Configs[bearbeiten]
There are a few application config files of importance. Most, if not all, of the config files are actually packaged into the DMDAD application, and if any changes need to be made, they should be made in the source directory, and then DMDAD should be repackaged (using ant) and then redeployed to JBoss.
Database connections are defined in the DMDAD/context.xml and DMDAD/jboss-web.xml files.
Application specific parameters are defined in DMDAD/config/dmd2.properties. This file contains only a few pieces of information, file.upload.dir (where uploaded overlays are stored) and baseURL (should be a full link to the main application).
Daemon Jobs[bearbeiten]
There is a single daemon job which is responsible for fetching overlays that need to be send out to stores, and queuing them into JMS for dispersal. There is a script in the DMDAD/scripts directory called startDaemon.sh which starts the daemon, and a script stopDaemon.sh which will stop it.
/home/ezaleski/work/DMDAD/scripts
Cron Jobs[bearbeiten]
there are no cronjobs
Users/Groups Setup[bearbeiten]
Right now, everything should run as the user ezaleski, because that is the user that owns the JBoss install, and also the file.upload.dir.
Security Updates[bearbeiten]
Security updates are fine, just make sure not to do any Major updates, (like upgrading to Java 1.6, or Tomcat 5.6)
Client Applications (if any)[bearbeiten]
None
