Miles to go …

Rails powered by the GlassFish Application Server explains all the benefits of using GlassFish for developing and deploying your Rails applications. If you are using NetBeans 6.1 builds then you can deploy your Rails application directly on GlassFish v3 from within NetBeans IDE. No longer you need to have different development and deployment options.

This blog explains how to install a bleeding-edge GlassFish v3 plugin and use it to deploy your Rails app natively on GlassFish (no WAR or anything . Let’s get started! Note, this plugin is bleeding edge and will soon be released on the Beta Update Center.

1. Install “GlassFish v3 TP2″ plugin in NetBeans 6.1
   1. In NetBeans 6.1 IDE, go to “Tools”, “Plugins” and click on “Settings”. The following window is shown:

      

   2. Click on “Add” and specify the URL of Bleeding Edge Update Center values as shown (copy from “http://deadlock.netbeans.org/hudson/job/javadoc-nbms/lastSuccessfulBuild/artifact/nbbuild/nbms/updates.xml.gz”):

      

      Click on “OK”. The updated “Plugins” window looks like:

      

      Notice “Available Plugins” has changed from 58 to 140 as many more bleeding edge plugins are now available.

   3. Click on “Available Plugins” and search for “GlassFish” in the top-right corner text box as shown below:

      

   4. Select “GlassFish V3 JRuby Integration” and “GlassFish V3 JavaEE Integration” plugin and click on “Install” as shown below:

      

      Follow the instructions to install the plugin. The IDE needs to restart for successful plugin installation.

   5. In the restarted IDE,  go to “Services” tab, right-click on “Servers” and select “Add Server…”. Select “GlassFish v3 TP2″ as shown below:

      

   6. Select “Next >”, accept the license agreement and click on “Download V3 Now…”

      

      Click on “Download V3 Now…”. This downloads the latest GlassFish v3 TP2 build and installs in “/Users/arungupta/GlassFish_V3_TP2″ directory. This is only an interim build, final TP2 build will be available soon! The following screen is shown once GlassFish v3 is installed:

      

      Click on “Finish”. In 58 seconds, you downloaded and installed the entire GlassFish v3 app server, cool isn’t it!

2. Create a Rails app and deploy on GlassFish V3
   1. In NetBeans IDE, in the “Projects” tab, right-click and select “New Project…”. Select “Ruby” in “Categories” and “Ruby on Rails Applications” in “Projects” as shown:

      

      Click on “Next”.

   2. Now comes the cool part. Enter the application name and select the recently installed GlassFish v3 as shown:

      

      This is a brand new feature in the “GlassFish v3 TP2″ plugin available only on “Bleeding Edge” Update Center. It’ll soon replace the default GlassFish v3 plugin from the Beta Update Center.

      Click on “Finish” to take all other defaults.

   3. On the newly created project, right-click and select “Run” as shown:

      

   4. The default browser page “http://localhost:8080/” shows up. Change the URL to “http://localhost:8080/HelloRails” and the following page shows up:

      

Now, NetBeans IDE and GlassFish v3 serves your need for a complete development and deployment platform for Ruby-on-Rails applications.

If any part of the tooling is not working or you have suggestions and improvement then please file bugs on IssueZilla (“serverplugins” component) and use “glassfish_v3″ subcomponent. If any part of the runtime is not working, then please file bugs on Issue Tracker (“V3″ component) and use “jruby” subcomponent.

Please leave suggestions on other TOTD (Tip Of The Day) that you’d like to see. A complete archive is available here.

Technorati: totd glassfish v3 netbeans rubyonrails

TOTD #30 explained how to create CRUD application using Grails and hosted using in-built Jetty servlet engine and in-memory HSQLDB database. Jetty and HSQLDB are built into Grails and allows to start easily. You can also use GlassFish and MySQL for deploying your applications in production environment.

This blog entry walks you through the steps of deploying a Grails application on GlassFish and MySQL.

1. If MySQL is already installed, then download GlassFish v2 UR1. Otherwise you can also Download GlassFish v2 UR1 and MySQL co-bundle from usual Download Page (instructions).
2. Configure MySQL database
   1. Download MySQL Connector/J 5.1.6 from here.
   2. Extract the bundle and copy “mysql-connector-java-5.1.6-bin.jar” to the “lib” directory of Grails application.
   3. Start MySQL database as:
      

      ~/testbed/grails-1.0.2/samples/crud >sudo /usr/local/mysql/bin/mysqld_safe –user root –console Starting mysqld daemon with databases from /usr/local/mysql/data

   4. Create database by giving the following command:
      

      ~/testbed/grails-1.0.2/samples/crud >/usr/local/mysql/bin/mysqladmin create crudProd –user root

3. Configure the Application
   1. Edit “grails-app/conf/DataSource.groovy” to specify MySQL configuration. The updated file looks like (changes highlighted in bold):

      dataSource {         pooled = false         driverClassName = “com.mysql.jdbc.Driver“         username = “root“         password = “”         dialect = “org.hibernate.dialect.MySQL5InnoDBDialect” } hibernate {     cache.use_second_level_cache=true     cache.use_query_cache=true     cache.provider_class=’org.hibernate.cache.EhCacheProvider’ } // environment specific settings environments {         development {                 dataSource {                         dbCreate = “create-drop” // one of ‘create’, ‘create-drop’,'update’                         url = “jdbc:hsqldb:mem:devDB”                 }         }         test {                 dataSource {                         dbCreate = “update”                         url = “jdbc:hsqldb:mem:testDb”                 }         }         production {                 dataSource {                         dbCreate = “update”                         url = “jdbc:mysql://localhost/crudProd“                 }         } }

      Being in production, it’s recommended to use InnoDB tables instead of MyISAM tables. This can be easily specified by using the dialect as explained here. More details about the contents of “DataSource.groovy” can be found here.
      

   2. Create a WAR by giving the following command:

      ~/testbed/grails-1.0.2/samples/crud >grails war Welcome to Grails 1.0.2 – http://grails.org/ Licensed under Apache Standard License 2.0 Grails home is set to: /Users/arungupta/testbed/grails-1.0.2 Base Directory: /Users/arungupta/testbed/grails-1.0.2/samples/crud Note: No plugin scripts found Running script /Users/arungupta/testbed/grails-1.0.2/scripts/War.groovy Environment set to production    [delete] Deleting: /Users/arungupta/.grails/1.0.2/projects/crud/resources/web.xml    [delete] Deleting directory /Users/arungupta/.grails/1.0.2/projects/crud/classes . . . [propertyfile] Updating property file: /Users/arungupta/testbed/grails-1.0.2/samples/crud/staging/WEB-INF/classes/application.properties     [mkdir] Created dir: /Users/arungupta/testbed/grails-1.0.2/samples/crud/staging/WEB-INF/plugins      [copy] Warning: /Users/arungupta/testbed/grails-1.0.2/samples/crud/plugins not found.       [jar] Building jar: /Users/arungupta/testbed/grails-1.0.2/samples/crud/crud-0.1.war    [delete] Deleting directory /Users/arungupta/testbed/grails-1.0.2/samples/crud/staging Done creating WAR /Users/arungupta/testbed/grails-1.0.2/samples/crud/crud-0.1.war

4. Deploy the WAR file as:
   
   g="2" cellspacing="2">
   

   ~/testbed/grails-1.0.2/samples/crud >~/testbed/glassfish/v3/p2b9/glassfish/bin/asadmin deploy crud-0.1.war crud-0.1 deployed successfully Command deploy executed successfully.

   The application is now accessible at “http://localhost:8080/crud-0.1″ and looks like:

   

5. READ – Click on “StateController” and the following page is shown:

   

6. CREATE – Click on “New State” and enter the values as shown below:

   

   and click on “Create” to see the following page:

   

7. UPDATE & DELETE – You can click on “Edit” or “Delete” to perform U or D of CRUD or click on “State List” to view the updated list.

Please leave suggestions on other TOTD that you’d like to see. A complete archive is available here.

Technorati: groovy grails glassfish mysql scripting netbeans

After a simple Grails application, let’s create a CRUD application. Such an application allows to perform basic database operations to read table rows from the database, create new rows, and edit and delete existing rows. This blog shows how such an application can be created using Grails, hosted on built-in Jetty servlet engine and use in-memory HSQLDB database for persistence.

A follow-up entry will show how this application can be deployed in production mode on GlassFish and using MySQL database.

1. Create a Grails application
   1. After Grails download and configuration, create a new application “crud” as:

      ~/testbed/grails-1.0.2/samples >grails create-app crud Welcome to Grails 1.0.2 – http://grails.org/ Licensed under Apache Standard License 2.0 Grails home is set to: /Users/arungupta/testbed/grails-1.0.2 Base Directory: /Users/arungupta/testbed/grails-1.0.2/samples Note: No plugin scripts found Running script /Users/arungupta/testbed/grails-1.0.2/scripts/CreateApp.groovy Environment set to development     [mkdir] Created dir: /Users/arungupta/testbed/grails-1.0.2/samples/crud/src     [mkdir] Created dir: /Users/arungupta/testbed/grails-1.0.2/samples/crud/src/java     [mkdir] Created dir: /Users/arungupta/testbed/grails-1.0.2/samples/crud/src/groovy     [mkdir] Created dir: /Users/arungupta/testbed/grails-1.0.2/samples/crud/grails-app     [mkdir] Created dir: /Users/arungupta/testbed/grails-1.0.2/samples/crud/grails-app/controllers     [mkdir] Created dir: /Users/arungupta/testbed/grails-1.0.2/samples/crud/grails-app/services     [mkdir] Created dir: /Users/arungupta/testbed/grails-1.0.2/samples/crud/grails-app/domain     [mkdir] Created dir: /Users/arungupta/testbed/grails-1.0.2/samples/crud/grails-app/taglib     [mkdir] Created dir: /Users/arungupta/testbed/grails-1.0.2/samples/crud/grails-app/utils     [mkdir] Created dir: /Users/arungupta/testbed/grails-1.0.2/samples/crud/grails-app/views     [mkdir] Created dir: /Users/arungupta/testbed/grails-1.0.2/samples/crud/grails-app/views/layouts     [mkdir] Created dir: /Users/arungupta/testbed/grails-1.0.2/samples/crud/grails-app/i18n     [mkdir] Created dir: /Users/arungupta/testbed/grails-1.0.2/samples/crud/grails-app/conf     [mkdir] Created dir: /Users/arungupta/testbed/grails-1.0.2/samples/crud/test     [mkdir] Created dir: /Users/arungupta/testbed/grails-1.0.2/samples/crud/test/unit     [mkdir] Created dir: /Users/arungupta/testbed/grails-1.0.2/samples/crud/test/integration     [mkdir] Created dir: /Users/arungupta/testbed/grails-1.0.2/samples/crud/scripts     [mkdir] Created dir: /Users/arungupta/testbed/grails-1.0.2/samples/crud/web-app     [mkdir] Created dir: /Users/arungupta/testbed/grails-1.0.2/samples/crud/web-app/js     [mkdir] Created dir: /Users/arungupta/testbed/grails-1.0.2/samples/crud/web-app/css     [mkdir] Created dir: /Users/arungupta/testbed/grails-1.0.2/samples/crud/web-app/images     [mkdir] Created dir: /Users/arungupta/testbed/grails-1.0.2/samples/crud/web-app/META-INF     [mkdir] Created dir: /Users/arungupta/testbed/grails-1.0.2/samples/crud/lib     [mkdir] Created dir: /Users/arungupta/testbed/grails-1.0.2/samples/crud/grails-app/conf/spring     [mkdir] Created dir: /Users/arungupta/testbed/grails-1.0.2/samples/crud/grails-app/conf/hibernate [propertyfile] Creating new property file: /Users/arungupta/testbed/grails-1.0.2/samples/crud/application.properties      [copy] Copying 2 files to /Users/arungupta/testbed/grails-1.0.2/samples/crud      [copy] Copying 2 files to /Users/arungupta/testbed/grails-1.0.2/samples/crud/web-app/WEB-INF      [copy] Copying 5 files to /Users/arungupta/testbed/grails-1.0.2/samples/crud/web-app/WEB-INF/tld      [copy] Copying 87 files to /Users/arungupta/testbed/grails-1.0.2/samples/crud/web-app      [copy] Copying 17 files to /Users/arungupta/testbed/grails-1.0.2/samples/crud/grails-app      [copy] Copying 1 file to /Users/arungupta/testbed/grails-1.0.2/samples/crud      [copy] Copying 1 file to /Users/arungupta/testbed/grails-1.0.2/samples/crud      [copy] Copying 1 file to /Users/arungupta/testbed/grails-1.0.2/samples/crud [propertyfile] Updating property file: /Users/arungupta/testbed/grails-1.0.2/samples/crud/application.properties Created Grails Application at /Users/arungupta/testbed/grails-1.0.2/samples/crud

   2. In your project directory, create a domain class as:
      

      ~/testbed/grails-1.0.2/samples/crud >grails create-domain-class state Welcome to Grails 1.0.2 – http://grails.org/ Licensed under Apache Standard License 2.0 Grails home is set to: /Users/arungupta/testbed/grails-1.0.2 Base Directory: /Users/arungupta/testbed/grails-1.0.2/samples/crud Note: No plugin scripts found Running script /Users/arungupta/testbed/grails-1.0.2/scripts/CreateDomainClass.groovy Environment set to development      [copy] Copying 1 file to /Users/arungupta/testbed/grails-1.0.2/samples/crud/grails-app/domain Created  for State      [copy] Copying 1 file to /Users/arungupta/testbed/grails-1.0.2/samples/crud/test/integration Created Tests for State

      This creates “State.groovy” class in “grails-app/domain” directory and looks like:

      class State { }

      Add two fields to store state name and the corresponding abbreviation as shown below:

      class State {         String name         String abbrev }

   3. Change “grails-app/conf/BootStrap.groovy” class to initialize the domain with sample data as shown below:
      

      class BootStrap {      def init = { servletContext ->           new State(name:”California”, abbrev:”CA”).save()           new State(name:”New York”, abbrev:”NY”).save()           new State(name:”Texas”, abbrev:”TX”).save()           new State(name:”Wisconsin”, abbrev:”WI”).save()      }      def destroy = {      } }

   4. Create a new controller as:
      

      ~/testbed/grails-1.0.2/samples/crud >grails create-controller state Welcome to Grails 1.0.2 – http://grails.org/ Licensed under Apache Standard License 2.0 Grails home is set to: /Users/arungupta/testbed/grails-1.0.2 Base Directory: /Users/arungupta/testbed/grails-1.0.2/samples/crud Note: No plugin scripts found Running script /Users/arungupta/testbed/grails-1.0.2/scripts/CreateController.groovy Environment set to development      [copy] Copying 1 file to /Users/arungupta/testbed/grails-1.0.2/samples/crud/grails-app/controllers Created Controller for State     [mkdir] Created dir: /Users/arungupta/testbed/grails-1.0.2/samples/crud/grails-app/views/state      [copy] Copying 1 file to /Users/arungupta/testbed/grails-1.0.2/samples/crud/test/integration Created ControllerTests for State

      This generates ”grails-app/controllers/StateController.groovy” with the following content:

      class StateController {     def index = { } }

      Replace it with to define a scaffold:

      class StateController {     def scaffold = State }

2. Start the application using built-in Jetty Servlet engine and in-memory HSQLDB database as shown below:
   

   ~/testbed/grails-1.0.2/samples/crud >grails run-app Welcome to Grails 1.0.2 – http://grails.org/ Licensed under Apache Standard License 2.0 Grails home is set to: /Users/arungupta/testbed/grails-1.0.2 Base Directory: /Users/arungupta/testbed/grails-1.0.2/samples/crud Note: No plugin scripts found Running script /Users/arungupta/testbed/grails-1.0.2/scripts/RunApp.groovy Environment set to development Running Grails application.. 2008-04-18 17:26:29.962::INFO:  Logging to STDERR via org.mortbay.log.StdErrLog 2008-04-18 17:26:29.075::INFO:  jetty-6.1.4 2008-04-18 17:26:29.155::INFO:  No Transaction manager found – if your webapp requires one, please configure one. 2008-04-18 17:26:30.886:/crud:INFO:  Set web app root system property: ‘crud’ = [/Users/arungupta/testbed/grails-1.0.2/samples/crud/web-app/] 2008-04-18 17:26:30.886:/crud:INFO:  Initializing Log4J from [file:/Users/arungupta/.grails/1.0.2/projects/crud/resources/log4j.properties] 2008-04-18 17:26:30.945:/crud:INFO:  Initializing Spring root WebApplicationContext [0] spring.GrailsWebApplicationContext Refreshing org.codehaus.groovy.grails.commons.spring.GrailsWebApplicationContext@848dfb: display name [org.codehaus.groovy.grails.commons.spring.GrailsWebApplicationContext@848dfb]; startup date [Fri Apr 18 17:26:32 PDT 2008]; parent: org.springframework.web.context.support.XmlWebApplicationContext@cddcc3 [1] spring.GrailsWebApplicationContext Bean factory for application context [org.codehaus.groovy.grails.commons.spring.GrailsWebApplicationContext@848dfb]: org.springframework.beans.factory.support.DefaultListableBeanFactory@11f136 2008-04-18 17:26:34.655:/crud:INFO:  Initializing Spring FrameworkServlet ‘grails’ 2008-04-18 17:26:35.716::INFO:  Started [email protected]:8080 Server running. Browse to http://localhost:8080/crud

   The application is now accessible at “http://localhost:8080/crud” and looks like:

   

3. READ – Click on “StateController” and the following page is shown:

   

4. CREATE – Click on “New State” and enter the values as shown below:

   

   and click on “Create” to see the following page:

   

5. UPDATE & DELETE – You can click on “Edit” or “Delete” to perform U or D of CRUD or click on “State List” to view the updated list as shown below:

   

Please leave suggestions on other TOTD that you’d like to see. A complete archive is available here.

Technorati: groovy grails glassfish jetty hsqldb scripting crud

From proof-of-concept to production in 8 weeks, WorldxChange Communication NZ‘s online billing system is another succes story of JRuby and GlassFish v2. The portal is designed solely using NetBeans 6.1 IDE.

Here are some of the quotes from the completed questionnaire:

From my perspective, the main advantage was that I could deploy my JRuby project war file directly to Glassfish, allowing me to develop and test our online ViewBill portal using a production grade, scalable web server.

From a geek perspective, we love that Glassfish combined with JRuby and allowed us to integrate many different disparate systems to create a seamless interface for our customers to use.

started using the Glassfish v3 gem for final testing of new code releases and to check functionality prior to production deployment.

I do not believe that I could have developed this project any faster using different toolsets or technologies and have been massively impressed with the combination of Glassfish and JRuby.

Read more details here.

Rails powered by the GlassFish Application Server explains why to use GlassFish for powering your Rails applications.

You can find all all about JRuby and GlassFish efforts on the GlassFish wiki or JRuby wiki.

Technorati: glassfish netbeans rubyonrails jruby ruby stories