Creating jaxb files from the opentravel schema

Probably the easiest way to deal with complicated xml documents is to use the jaxb tool from java. jaxb converts a schema definition from .xsd format to java classes. If you are trying to use jaxb on the opentravel.org schema there are a few gotchas:

• First, since the schema is so large, there are a few places where there are duplicate element names.
• Second, since the schema was not developed with jaxb in mind, there are a few element names (such as 'class') that are not legal in java.

Luckily, I wrote a utility that makes it a lot easier to use jaxb, called ota-schema-tools. This is part of the open source ota-tools project. You can download these tools at the sourceforge project page. After you have downloaded the tools, unzip them into a directory.

After a few quick steps, the schema tool is ready to go:
1. Download the schema(s) that you want to use from opentravel.org and drop it in the ota-schema-zip-files directory:

2. Edit the ota.xsd file in the ota-schema-tools/config/2008A directory to include only the schema you will need (or leave it alone to compile all the schema). For example, here I only want to use the OTA_Ping messages:

3. Run the schema tool:
If jaxb is not in your classpath, you will need to tell ant where it is with the -Djaxb.home=/location-of-jaxb-home flag. Also, if you are compiling a lot of schemas, you will have to set the ANT_OPTS=javac-options property. Here is what I type:

ota-schema-tools> export ANT_OPTS=-Xmx512m ota-schema-tools> ant -Djaxb.home=/usr/local/java/web/glassfish/ dist

When I run this command I get the error: OTA_TourInformation.xsd and OTA_RailAvailRS.xsd is not a part of this compilation.
No problem. The jaxb configuration file is set up to fix problems in the entire schema. Just remove these lines from the ota-schema-tools/config/2008A/jaxb/binding.xjb file:

I deleted these highlighted lines. Now run this line again from your command prompt:
ant -Djaxb.home=/usr/local/java/web/glassfish/ dist
Voila! Your schema are compiled and neatly packaged in a opentravel2008a.jar file.

Now that wasn't that hard, was it!

awstats web site statistics for glassfish

awstats is a open source web server log analyzer. Glassfish is an open source java-based web-server. Click here to check out the statistics on my two glassfish domain servers: domain1 domain2. Of course you will restrict access when you deploy this.

To get the awstats package to work with glassfish:

1. Download and untar awstats (to /usr/local/awstats)
2. Follow the instructions for installing awstats and run the configuration utility.
   Remember to create the /etc/awstats/ and /var/lib/awstats/ directories and set write permission.
   Edit the config file (/etc/awstats/yourconfigfilename) and change the LogFile property to:
   LogFile="sed -e 's/"\([0-9\.]*\)"/\1 - -/g' -e 's/"\([^"]*-0800\)"/[\1]/g' /usr/local/java/web/glassfish/domains/domain1/logs/access/server_access_log.%YYYY-0-%MM-0-%DD-0.txt |"
   where "/usr/local/java/web/glassfish" is the location of your glassfish server. Also remember to change the time zone offset (mine is -0800) to your timezome offset.
   Change the DirIcons property to:
   DirIcons="icon"
   You will probably want to change your SiteDomain and HostAliases properties to match your domain name.
   I got this info from Glen Smith's blog, Thanks!
3. Open your glassfish admin page (http://www.yourserver.com:4848), go to configuration -> http service and click the Access Logging enabled box.
   Click on the Access Log Tab and enter:
   %client.name% %datetime% %request% %status% %response.length% %header.referer% %header.user-agent%
   in the Format text box.
   This makes your log format similar to the apache log format
4. Go you your awstats/wwwroot directory and create a sub-directory WEB-INF
   Create a web.xml file in this directory that contains:
   
   <?xml version="1.0" encoding="UTF-8"?>
   <web-app id="WebApp_ID" version="2.4"
   xmlns="http://java.sun.com/xml/ns/j2ee"
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
   xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
   <servlet>
   <servlet-name>cgi</servlet-name>
   <servlet-class>org.apache.catalina.servlets.CGIServlet</servlet-class>
   <init-param>
   <param-name>debug</param-name>
   <param-value>0</param-value>
   </init-param>
   <init-param>
   <param-name>cgiPathPrefix</param-name>
   <param-value>cgi-bin</param-value>
   </init-param>
   <load-on-startup>5</load-on-startup>
   </servlet>
   <servlet-mapping>
   <servlet-name>cgi</servlet-name>
   <url-pattern>/awstats.pl</url-pattern>
   </servlet-mapping>
   </web-app>
   Afterwards, cd to the wwwroot/cgi-bin directory type chmod a-w *.pl just to be careful.
5. Now, install this as a web server in the glassfish admin screen (http://www.yourserver.com:4848)
   Applications -> Web Applications -> Deploy
   And deploy the web server directory: /usr/local/awstats/wwwroot. Make sure your context root is awstats.
   
   
   
6. Try to invoke the servlet as it's described in the awstats documentation:
   http://www.yourdomain.com/awstats/awstats.pl?config=yourconfigfilename
   You should see the awstat config data. Cool!