Most of the configuration is already done for you. But, depending on your environment,
you may need to tweak a couple of parameters. Go to
./provisioning-portal/webapp/WEB-INF/jvending-config directory. Open the
stocking-handlers.xml file. Change the
par-file-output value under the
GENERIC stocking-handler to the directory where you want to store the tmp PAR files that JVending
processes. If /tmp is the default, so if that is okay, you don't need to do anything.
Also look within the web.xml file in the portal directory. Set the CONTENT_DELIVERY_URI to the hostname and port of the webserver. By default it is localhost:8080, which will run fine on an out of the box configuration of tomcat.
JVending 2.0.0 comes with a very simple portal designed to show the concepts behind the provisioning (if you need more advanced admin features and actual HTML and WML access to the content, download version 1.3.10a). Currently the 2.0.0 portal only supports stocking, viewing of content for the locale of the server, general content delivery and MIDP delivery. To use device detection requiresadding a parameter in the taglib, but it is disabled by default.
After you build the application, go to the provisioning-portal directory and look in its target directory. You will see the provisioning-portal-webapp.war. Place the war in the deployment directory of a web server that supports at least Servlet spec 2.4 and J2SE 1.5 (I have tested with tomcat 5.5.9)
Go to the URL of the app: http://localhost:8080/provisioning-portal-webapp, or whatever you URL is. You will see a page with two links: 1) Stock Par Files and 2) View Catalog. Click the Stock PAR Files link. Now browse and select you PAR File. Click submit and you will see the stocked content.
If you do not have your own PAR file, one is included in Sun's reference implementation.