A Nonprofit Case Study: OpenShift, JBoss, and Amazon Web Services

In the real estate industry, buyers and sellers are constantly researching listing property information such as status, price, and location. A Multiple Listing Service (MLS) is a localized database which association members, salespersons and broker salespersons, access to update their clients with relative property information. However, this process has become slow and outdated because of the Internet and the Web.

The Global Real Estate And Technology Consortium (GR8C) is a scientific nonprofit located in Orlando, Florida. Its mission is to promote the education, operation, and use of the World Wide Multiple Listing Service (WWMLS) to its fullest potential by developing protocols, specifications, and standards for the benefit of all people throughout the world.

This case study will provide a low-level look at the Multiple Listing Service Network Protocol (MLSN), a new request-response messaging protocol developed by the GR8C for querying property information on user reserved port 32801. The session will discuss how OpenShift is used to build, deploy, and monitor configured JBoss Application Servers as MLSN Servers to Amazon’s Web Services Platform. In addition, the presenter will share key lessons learned and technical issues dealing with OpenShift. Finally, an MLSN client to MLSN server messaging demonstration will be provided.

–Corey

RTFMing the docs, I cd’d to the util directory and then ran: ant -f release-admin.xml. First try failed with the following error message:

BUILD FAILED
Warning: Could not find file …\path\to\jms\jms-ra.rar to copy

So I vi’d release-admin.xml and read the copy command found on line 116. Looks like it wanted a jms-ra.rar in a directory called jms. I examined my jboss installation and didn’t find a jms directory present within my developmental server so I created a jms/ directory and copied an available copy of jms-ra.rar into the jms directory.

Unfortunately, you cannot just simply rerun the install file, release-admin.xml, straightaway. You must remove the messaging/ directory completely before reinstalling.

rm-rf messaging/
(I know, I know, this is a no no but my first red bull of the day was still in full circulation. )

After removing the messaging/ directory, I retried:

ant -f release-admin.xml

Success! The build was successful and now it’s on to JBoss ESB and the helloworld.esb for testing messaging and eventual soap client service.