In this article we will learn how to begin developing web applications using Ruby on Rails. First we setup the development environment, then develop a simple CRUD (create, read, update, delete) application using MySQL database, and deploy the application to Apache web server. An an example, we will develop a very simple point of sales (POS) application that consists only 3 tables: orders, order_details, and items.

Ruby on Rails Installation

Install Ruby if it’s not installed yet on your system:

# apt-get install  ruby1.8 ruby1.8-dev

 

Install Ruby Gem package management directly from Rubyforge since we need the newer version than version 1.3.1 that is shipped with Debian 5:

# wget http://rubyforge.org/frs/download.php/70696/rubygems-1.3.7.tgz

# tar xfz rubygems-1.3.7.tgz

# cd rubygems-1.3.7.tgz

# ruby setup.rb

# ln -s /usr/bin/gem1.8 /usr/bin/gem

 

Install Ruby on rails version 2.3.8 using gem command:

# gem install -v=2.3.8 rails

 

Start Developing the Application

We are going to put our application on /opt/rubyapp or whatever directory you like.

# cd /opt

# mkdir rubyapp

 

On that directory, run rails command to create a new application skeleton. We are going to create a simple POS application and we call it simplepos.

# rails simplepos

 

Rails will create the application skeleton on the directory name we specified. Go to that directory and run the server.

# cd simplepos

# ruby script/server

 

Ruby on Rails server will start and we can access it from http://yourserver-ip:3000, like the following:

Note: I once found a conflicting port 3000 on Debian 5, which was used by Dr WEB application. Simply stop that service or change the port in order that Rails application to start correctly.

You can see that the default database driver is SQL lite. We need to change this to MySQL. Edit the config/database.yml:

development:
  adapter: mysql
  database: simplepos_development
  user: root
  password: 1234
  pool: 5
  timeout: 5000

# Warning: The database defined as "test" will be erased and
# re-generated from your development database when you run "rake".
# Do not set this db to the same as development or production.
test:
  adapter: mysql
  database: simplepos_test
  user: root
  password: 1234
  pool: 5
  timeout: 5000

production:
  adapter: mysql
  database: simplepos_production
  user: root
  password: 1234
  pool: 5
  timeout: 5000

Adjust the user name and password according to your system. Then run this command to create all the databases defined on the config file:

# rake db:create:all

 

Run the server again (ruby script/server) and make sure that our database is now MySQL:

The Application Design

Our application is quite simple. It contains only 3 tables

• orders for storing sales transactions with the following fields:
• number
• order_date
• items for storing items to be sold the following fields:
• number
• name
• description
• unit_price
• order_details for storing order details with the following fields:
• order_id
• item_id
• qty
• unit_price
• amount

Here is the relation of the 3 tables:

Creating Model , Controller, and View using Scaffold for Orders Data

Let’s move on to coding. Rails provides us a very powerful scaffolding script that allows us to easily create the model, view, and controller, and even the tables related to the model.

First, create the Order model. Here we follow the Rails convention: model use singular word.

# ruby script/generate scaffold Order number:integer order_date:date

Rails will create our Order model, view, and controller. Take a look on simplepos/app folder. Next create the database table according to the fields that we sepcified on the scaffold above:

# rake db:migrate

Now, run the server again (ruby script/server) and test the CRUD functionality for the Order data by entering the URL address: http://yourserver-ip:3000/orders. We can see the list orf orders on the index page, a new order creation link, along with edit, update, and delete link if there’s an order already.

Listing orders:

Adding new order:

Order created:

List the orders on the order list:

Editing the order:

Deleting the order:

What have we have is a complete CRUD application for Orders table created automatically by Rails scaffolding.

Creating Model , Controller, and View using Scaffold for Items Data

Now create the model, controller, view, and table for items data, using the same steps as above.

# ruby script/generate scaffold Item number:integer name:string description:text unit_price:decimal

Then create the database table according to the fields that we specified on the scaffold above:

# rake db:migrate

And try to run the items CRUD by pointing to URL http://yourserver-ip:3000/items . You should be able to list, create, edit, and delete the items data now. This is the example of creating new item form.

Validating Data

If we need to validate data entered by the user, then we can easily edit the model and add validations to the fields. For example, we need to validate the existence of number and  order_date fields on orders table. Also we need to validate whether total_amount field is a number or not. Edit the app/model/order.rb file and add the following bold lines:

class Order < ActiveRecord::Base
   validates_presence_of :number, :order_date 
end

Stop and start the server again, and let’s enter the wrong data according to the validation rule.

Entering a blank number, order_date.

Of course, we could also add the validation to Items data by editing the app/model/item.rb file, by adding the following bold lines:

class Item < ActiveRecord::Base
   validates_presence_of :number, :name, :unit_price
   validates_numericality_of :unit_price
end

Try to create a blank number, name, unit_price on item data:

Creating Order Details MVC and Set the Relation

Order details is the place where we stored the actual sales transaction. It will record the items purchased on a particular order number. So it has a relation to items table and orders table as well, both for a “belongs to” relationship. So the relations will be:

• orders has many order_details
• items has many order_details
• order_details belongs to orders and items

Let’s create the MVC for this order details using the same steps as before:

# ruby script/generate scaffold OrderDetail order:references item:references qty:integer unit_price:decimal amount:decimal

Note that we used references data type for order and item on OrderDetail model. This will make Rails to create a relationship between OrderDetail and Order and Item model (ie OrderDetails belongs to Order and Item). It will also create a reference column on the order_details table, which is order_id and items_id.

Then create the database table according to the fields that we specified on the scaffold above:

# rake db:migrate

 

And take a look at the generated order_details table:

mysql> explain order_details;
+————+—————+——+—–+———+—————-+
| Field      | Type          | Null | Key | Default | Extra          |
+————+—————+——+—–+———+—————-+
| id         | int(11)       | NO   | PRI | NULL    | auto_increment |
| order_id   | int(11)       | YES  |     | NULL    |                |
| item_id    | int(11)       | YES  |     | NULL    |                |
| qty        | int(11)       | YES  |     | NULL    |                |
| unit_price | decimal(10,0) | YES  |     | NULL    |                |
| amount     | decimal(10,0) | YES  |     | NULL    |                |
| created_at | datetime      | YES  |     | NULL    |                |
| updated_at | datetime      | YES  |     | NULL    |                |
+————+—————+——+—–+———+—————-+
8 rows in set (0.00 sec)

Note: created_at and updated_at are auto generated columns when we create the scaffolding.

Let’s define this relations to the models. First edit the order model (app/model/order.rb) and add the following bold lines:

class Order < ActiveRecord::Base
   validates_presence_of :number, :order_date
   has_many :order_details
end

And to the item model (app/model/item.rb)

class Item < ActiveRecord::Base
   validates_presence_of :number, :name, :unit_price
   validates_numericality_of :unit_price
   has_many :order_details
end

Also check the order detail model (app/model/order_detail.rb) has the relationship already because we specify that order and items are references when do the scaffolding.

class OrderDetail < ActiveRecord::Base
  belongs_to :order
  belongs_to :item
end

Edit routes.rb

We also need to edit the config/routes.rb so that the URL for order and order details also have a relationship information that order has many order_details. Modify the file so it looks like the following:

ActionController::Routing::Routes.draw do |map|
  map.resources :items

  map.resources :orders, :has_many => :order_details

….

It will enable us to access the order details data below the order URL like this: http://yourserver:3000/orders/1/order_detail

Adding Order Detail Form

We need to add the detail form below the Order show page so that we can add item details for a particular Order.

Add these bold lines just below the Date field of the Order:

…

<p>
  <b>Order date:</b>
  <%=h @order.order_date %>
</p>

<h1>Order details</h1>
<table>
<tr>
   <th>Item</th>
   <th>Qty</th>
   <th>Unit Price</th>
   <th>Amount</th>
</tr>

<%= render :partial => @order.order_details %>

<% form_for [@order, OrderDetail.new] do |f| %>
<tr>
   <td><%= f.label :item_id, "item" %></td>
   <td><%= f.label :qty, "Qty" %></td>
</tr>
<tr>
   <td><%= f.select :item_id, @items.map {|u| [u.name,u.id %></td>
   <td><%= f.text_field :qty %></td>
</tr>
<tr>
   <td></td><td><%= f.submit "add detail" %></td>
</tr>
<% end %>
</table>

...

We need to create a new file under app/views/order_details, called app/views/order_details/_order_detail.html.erb. This file is required by the :render=>partial line above and is a partial template file used to render each order detail lines for an Order.

<% div_for order_detail do %>
<tr>
   <td><%=h order_detail.item.name %></td>
   <td><%=h order_detail.qty %></td>
   <td><%=h order_detail.unit_price %></td>
   <td><%=h order_detail.amount %></td>
</tr>
<% end %>

Then, we create a form for order details of an order ( form_for [@order, OrderDetail.new] do |f| ). After this, f variable will be related to order_details, but when submitted it will go to  /orders/<id>/order_details.

On that form, we use select() helper function to render a selection box that is populated with all items data that we have where users can pick an item from. Using @items.map we create an array that is required by the select() as its option values.

Next, edit app/controller/orders_controller.rb file so that it provides us with @items object that we used on the select() above.

def show
  @order = Order.find(params[:id])
  @items = Item.find(:all)

  respond_to do |format|
    format.html # show.html.erb
    format.xml  { render :xml => @order }
  end
end

Modify app/controller/order_details_controller.rb so that it contains only one create method (delete all other methods generated by the scaffolding process). This is invoked when we create a new order_detail record.

class OrderDetailsController < ApplicationController
   def create
      @order = Order.find(params[:order_id])
      @order_detail = @order.order_details.create!(params[:order_detail])
      item = Item.find(params[:order_detail][:item_id])
      qty = params[:order_detail][:qty]
      @order_detail.update_attributes(:amount=>item.unit_price.to_i * qty.to_i , :unit_price=>item.unit_price)
      redirect_to @order
   end
end

On this method, first we find the order identified by an ID (params[:order_id]) which is a parameter posted by the order detail form.

Found the Order, we create an OrderDetail record by calling @order.order_details.create!() method. This is possible because we have declared that an order can have many order_details.

Next we find the item that is being selected by the user, to find out its unit_price and calculate the order detail amount. Then we update the attributes of order_details using these values.

After all processes are done, we redirect back to the order URL (redirect_to @order).

It’s time now to try our modified application, go to Order URL and click Show link. We will have a new look of the form:

Try to add items on the order and check the unit price and amount.

Calculating Order’s Total Amount

It’s time to calculate the total amount of an order which is the sum of amounts of all order_details that it has.

This is easily calculated using the relation that we have set before (order has many order_details). After defining that relation, we will be able to call order.order_details.sum(colname) and get the total value of colname on the order_details table where order_id is the order that we are looking at.

So, we can edit add/model/order.rb to add a new method total_amount that will return the sum of column amount on the table that it has many (order_details):

class Order < ActiveRecord::Base
   validates_presence_of :number, :order_date, :total_amount
   validates_numericality_of :total_amount
   has_many :order_details

   def total_amount
      self.order_details.sum(:amount)
   end
end

Now we can use that method from our views. Edit the app/views/orders/index.html.erb:

<h1>Listing orders</h1>

<table>
  <tr>
    <th>Number</th>
    <th>Order date</th>
    <th>Total amount</th>
  </tr>

<% @orders.each do |order| %>
  <tr>
    <td><%=h order.number %></td>
    <td><%=h order.order_date %></td>
    <td><%=h order.total_amount %></td>
    <td><%= link_to ‘Show’, order %></td>
    <td><%= link_to ‘Edit’, edit_order_path(order) %></td>
    <td><%= link_to ‘Destroy’, order, :confirm => ‘Are you sure?’, :method => :delete %></td>
  </tr>
<% end %>
</table>

Here is the look of the modified index pages:

And also the app/views/orders/show.html.erb:

<p>
  <b>Number:</b>
  <%=h @order.number %>
</p>

<p>
  <b>Order date:</b>
  <%=h @order.order_date %>
</p>

<p>
  <b>Total amount:</b>
  <%=h @order.total_amount %>
</p>

. . .

Here is the look of the modified show page:

Decorating and Layout

Per model layout

As part of the scaffolding process, Rails generates a layout template for each model that we created. It is located on app/views/layouts directory. For example, we change the layout of the Items data, which is the app/views/layouts/items.html.erb.

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
       "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
  <meta http-equiv="content-type" content="text/html;charset=UTF-8" />
  <title>Items: <%= controller.action_name %></title>
  <%= stylesheet_link_tag ‘scaffold’ %>
</head>
<body>

<p style="color: green"><%= notice %></p>

<%= yield %>

</body>
</html>

As you can see, it’s a regular HTML file with a special tag that comes from Rails, which are    <%= stylesheet_link_tag ‘scaffold’ %>  and <%= yield %>. The first tag is how Rails application link a CSS file, in this case scaffold.css. Rails automatically search this file on public/stylesheets directory on our application folder.

The next tag is <%= yield %>. This is a Rails variable that contains the data generated by the view. So everything that we write on the view files will be contained in this variable and rendered on this layout file.

Let’s modify the body background color for Items data only, so change the body tag to <body style="background-color:#aaa">. We should see the background color for Items listing, edit, create, and update page will be changed.

Global application layout

If you’d like to change the layout globally for each model pages, then you will need to create a new file called app/views/layouts/application.html.erb, and delete  all other layout files generated by the scaffold. You can copy from another layout file exists as a template, then do the layout adjustments on that file and rename it to application.html.erb.

Having only application.html.erb will make Rails to use that file as the layout for the application. So you have to delete all other layout files, otherwise Rails will use that file instead.

The CSS, image, and Javascript files location

On your application directory, there’s a directory named public. This is where we store all public resources, like CSS, images, and Javascript files.

Rails provides us with some helper functions to generate the proper path for accessing these things, for example image_tag() to access images on public/images, stylesheet_link_tag() to access CSS files, and javascript_include_tag() to access Javascript files.

The Default Welcome Page

When pointing our browser to http://yourserver-ip:3000/ we will get the Ruby on Rails welcome page by default. We can change this default behaviour by editing the config/routes.rb file. Look at the map.root :controller => "welcome" line, and uncomment that line.

…

map.root :controller => "welcome"

…

 

It means that our application’s default controller is called welcome, which is not exist right now.

Next step, we need to delete public/index.html file.

# rm public/index.html

Then, we need to create that controller, simply by  running script/generate again but this time with controller parameter and not scaffold as we have used before.

# ruby script/generate controller welcome index

The command tells Rails to create for us a controller named welcome with a method index. Beside that Rails will also create a view file on app/views/welcome/index.html.erb that we can customize right away.

Let’s modify app/views/welcome/index.html.erb  so that it will show us a main menu for our application :

<h1>Welcome to Simple POS</h1>

<ul>
   <li><%= link_to "Orders" , orders_path %></li>
   <li><%= link_to "Manage Items" , items_path %></li>
</ul>

Here we use another Rails helper function link_to() which will create a HTML <a href> tag, which will display a link text as specified by the first parameter, and will jump to the URL that we specified in it’s second parameter.

We also use orders_path and items_path, which are the helper functions that is automatically generated by the scaffolding process to go to the index page (listing) of the order and item data.

The link can also be referred as these:

   <%= link_to "Orders" , :controller=>"orders", :action=>"index" %>

Testing the Application

Rails provides us a test suite for testing out our application programmatically. This will make us easier to test all functionality of our application without testing it manually by entering data on the user interface pages.

For example, it we need to test the application functionalities, run this comman:

# rake test:functionals

We can see the test results and  will be notified if something not expected exists.

Deploying Into Apache Web Server

Install modrails aka Passenger to be used by Apache web server:

gem install passenger

Then type:

passenger-install-apache2-module

Then follow the instructions on that script.

Deploying on name based virtual host:

Add a virtual host entry to your Apache configuration file. Make sure that the following conditions are met:

• The virtual host’s document root must point to your Ruby on Rails application’s public folder.
• The Apache per-directory permissions must allow access to this folder.
• MultiViews must be disabled for this folder.

For example:

<VirtualHost *:80>
    ServerName www.simpleblog.com
    DocumentRoot /opt/rubyapp/simpleblog/public
    <Directory /opt/rubyapp/simpleblog/public>
        Allow from all
        Options -MultiViews
    </Directory>
</VirtualHost>

You may also need to tweak your file/folder permissions. Make sure that the following folders are readable and executable by Apache:

• this public folder.

• the application’s config folder.

• all parent folders. That is, /opt/rubyapp/simpleblog , /opt and /opt/rubyapp/must also be readable and executable by Apache.

  Then restart Apache. The application has now been deployed.

Deploying to a sub URI:

Suppose that you already have a virtual host:

<VirtualHost *:80>
    ServerName www.yoursite.com
    DocumentRoot /www/yoursite
    <Directory /www/yoursite>
        Allow from all
    </Directory>
</VirtualHost>

And you want your Ruby on Rails application to be accessible from the URL http://www.yoursite.com/simpleblog.

To do this, make a symlink from your Ruby on Rails application’s public folder to a directory in the document root. For example:

ln -s /opt/rubyapp/simpleblog/public /www/yoursite/simpleblog

Next, add a RailsBaseURI option to the virtual host configuration, and also make sure that:

• The Apache per-directory permissions allow access to this folder.

• MultiViews is disabled for this folder.

For example (notice the lines in bold):

<VirtualHost *:80>
    ServerName www.yoursite.nl
    DocumentRoot /www/yoursite
    <Directory /www/yoursite>
        Allow from all
    </Directory>

    RailsBaseURI /simpleblog
    <Directory /www/yoursite/simpleblog>
        Options -MultiViews
    </Directory>
</VirtualHost>

Then restart Apache. The application has now been deployed.

Deploying to a port based virtual host

What if you want to access your application using a port number, like http://yoursite.com:9000. To do this, use Apache’s port based virtual host.

Add Listen directive to ports.conf or httpd.conf:

Listen 9000

 

Then add a virtual host entry to your Apache configuration file. Make sure that the following conditions are met:

• The virtual host’s document root must point to your Ruby on Rails application’s public folder.
• The Apache per-directory permissions must allow access to this folder.
• MultiViews must be disabled for this folder.

For example:

<VirtualHost *:9000>

   ServerName www.yoursite.com

      DocumentRoot /opt/rubyapp/simpleblog/public

      <Directory /opt/rubyapp/simpleblog/public>

         AllowOverride all

         Options -MultiViews

      </Directory>

</VirtualHost>

Also, delete or comment out the NameVirtualHost * directive on your httpd.conf.

Then restart Apache. The application has now been deployed.

Resources

• http://rubyonrails.org
• http://www.railscasts.com
• http://www.modrails.com

Akhmad Daniel Sembiring

akhmad.daniel[at]gmail.com

vitraining.com -CEO

Image via Wikipedia

Apache: Name Based Virtual Host

The server machine has a primary name server.domain.tld. Then there are two aliases (CNAMEs) for that server say www.domain.tld and www.sub.domain.tld for the address server.domain.tld.

We need different server configuration for each name so that each name can act as differrent web servers.

Here is the configuration for the vhost.conf file (the one that will be included in the main config file httpd.conf)

The asterisks match all addresses, so the main server serves no requests. Due to the fact that www.domain.tld is first in the configuration file, it has the highest priority and can be seen as the default or primary server.

Apache: Config for IP-based virtual hosts

Setup 1

The server machine has two IP addresses (111.22.33.44 and 111.22.33.55) which resolve to the names server.domain.tld and www.otherdomain.tld respectively. The hostname www.domain.tld is an alias (CNAME) for server.domain.tld and will represent the main server.

Here is the configuration for the vhost.conf file (the one that will be included in the main config file httpd.conf)

www.otherdomain.tld can only be reached through the address 111.22.33.55, while www.domain.tld can only be reached through 111.22.33.44 (which represents our main server).

Setup 2

Same as setup 1, but we don’t want to have a dedicated main server.

Here is the configuration for the vhost.conf file (the one that will be included in the main config file httpd.conf)

The main server can never catch a request, because all IP addresses of our machine are in use for IP-based virtual hosts (only localhost requests can hit the main server).

Setup 3:

The server machine has two IP addresses (111.22.33.44 and 111.22.33.55) which resolve to the names server.domain.tld and www-cache.domain.tld respectively. The hostname www.domain.tld is an alias (CNAME) for server.domain.tld and will represent the main server. www-cache.domain.tld will become our proxy-cache listening on port 8080, while the web server itself uses the default port 80.

Here is the configuration for the vhost.conf file (the one that will be included in the main config file httpd.conf)

The main server can never catch a request, because all IP addresses (apart from localhost) of our machine are in use for IP-based virtual hosts. The web server can only be reached on the first address through port 80 and the proxy only on the second address through port 8080.

Port-based vhosts

The server machine has one IP address (111.22.33.44) which resolves to the name www.domain.tld. If we don’t have the option to get another address or alias for our server we can use port-based vhosts if we need a virtual host with a different configuration.

Here is the configuration for the vhost.conf file (the one that will be included in the main config file httpd.conf)

A request to www.domain.tld on port 80 is served from the main server and a request to port 8080 is served from the virtual host.

Persyaratan

• Windows 2000, Windows XP, Windows Server 2000 atau Windows Server 2003
• WinZip
• mengerti DOS commands prompt, i.e. CD, DIR, MKDIR, COPY, REN

Langkah-langkah

• Instal Apache HTTP Server 2.0.55 (alternatif Apache melalui XAMPP)
• Instal ActivePerl 5.6.1
• Instal DBD-Pg and DBI
• Instal PostgreSQL 8.0.4 (Part 1)
• Instal PostgreSQL 8.0.4 (Part 2)
• Instal SQL-Ledger 2.8.17
• Updating HTTPD.CONF
• Set Administrator Password dan membuat Dataset

Instalasi Apache

Download versi terbaru program apache dari httpd.apache.org. misalnya apache_2.0.55-win32-x86-no_ssl.msi. Jalankan program tersebut sehingga muncul wizard instalasi apache.

Pada dialog box berikut ini, contreng radio button “I accept the terms … ” dan klik tombol Next.

Dialog box berikutnya berisi infromasi README information untuk versi Apache HTTP server.
Klik tombo Next untuk melanjutkan.

Pada dialog box Server Information , masukkan infromasi berikut (asumsi tidak ada setting DNS di jaringan anda):

• Network Domain: localhost
• Server Name: localhost
• Admin Email: email address anda
• Contrne radio button “for All Users, on Port 80, as a Service”, dan klik tombol Next.

Dialog box berikutnya meminta anda menentukan jenis setup. Boleh pilih Typical atau Custom.
Lalu klik tombol Next.

Jika pada dialog box sebelumnya dipilih setup type Custom maka program setup meminta anda untuk menentukan item yang hendak diinstall. Secara default, semuanya dipilih untuk diinstall. Lalu klik tombol Next.

Akhirnya anda diminta untuk memulai proses installasi Apache HTTP server. Klik pada tombol Install.

Ketika muncul dialog box Installation Wizard Completed klik tombol Finish.

Selanjutnya lihat pada bagian bawah kanan layar komputer. Pada System Tray anda akan melihat icon yang baru sudah installed. Gambarnya adalah bulu merah dengan panah hijau didalamnya. Panah hijau menandakan bahwa installasi sukses.

Jika anda letakkan mouse cursor diatas icon tersebut lalu right click dan memilih Open Apache
Monitor, anda dapat dengan mudah untuk Start/Stop/Restart Apache HTTP server melalui applet ini.

Untuk melakukan test installasi Apache HTTP Server , buka Internet web browser dan masukkan alamat http://127.0.0.1 atau http://localhost. Anda akan melihat halaman yang berisi pesan mengenai software yang sudah berhasil di instal.

Instalasi ActivePerl 5.6.1

Download program bundle untuk sistem operasi Win32 pada alamat http://www.activestate.com/Products/ActivePerl/, misalnya (pada saat tulisan ini dibuat) ActivePerl-5.6.1.638-MSWin32-x86.msi

Jalankan program msi install file tersebut.

Note: Version 5.6.1 digunakan dengan alasan untuk kemudahan install driver DBD-Pg and DBI.
Note: Jika anda melihat dialog box security warning , klik tombol Run untuk melanjutkan

Pada dialog box ActivePerl Welcome , klik tombol Next.

Pada dialog box berikutnya, klik radio button “I accept the terms … ” dan klik tombol Next.

Pada dialog box Custom Setup , anda melihat semua items sudah dipilih secara default untuk installasi. Klik tombol Next untuk melanjutkan

next dialog box berikutnya memberi infromasi tentang fitur PPM3. Anda boleh pilih pilihan ini jika diinginkan. Klik tombol Next untuk melanjutkan.

Items setup pilihan akan ditampilkan pada dialog box berikutnya. Biarkan nilai default dan klik tombol Next.

Akhirnya proses installasi akan dimulai ketika anda klik tombol Install.

Ketikan anda melihat dialog box Installation Wizard Completed klik tombol Finish.

Installing DBD-Pg and DBI

Untuk instalasi DBD-Pg dan DBI, download module perl yang sudah dikompilasi dari
http://www.edmund-mergl.de/export/ . Nama filenya masing-masing adalah DBD-Pg.zip. File paket DBD-Pg dan DBI diperlukan untuk menyediakan mekanisme database interface antara sql-ledger dan Postgres.

Note: MCSPAN tidak dapat digunakan di Windows sehingga kita perlu module yang telah dikompilasi.
Note: Modul DBD-Pg tersebut diatas tidak bisa digunakan di ActivePerl versi 5.8. Nanti setelah berhasil diinstall di versi 5.6 anda boleh upgrade ActivePerl 5.8.

Unzip file DBD-Pg.zip ke sembarang directory temporary pada komputer anda.

Dengan Command prompt, masuk ke directory DBD-Pg.

Pada command prompt, ketik: ppm install –location=. DBD-Pg lalu tekan tombol Enter.

Setelah installing DBD-Pg modul ketik pada command prompt: ppm dan tekan tombol Enter.

Pada PPM prompt, ketik install DBI dan tekan tombol Enter.

Ketika diminta untuk menginstall DBI package, ketikkan huruf y pada prompt dan tekan tombol
Enter.

Untuk keluar dari PPM command prompt, ketik exit dan tekan tombol Enter.

temporary directory yang tadi dibuat boleh dihapus.

Instalasi PostgreSQL

Untuk meng-install PostgreSQL server, download file terakhir untuk Win32 system dari http://wwwmaster.postgresql.org/download/mirrors-ftp/.  Pada saat buku ini ditulis, file install yang digunakan adalah: postgresql-8.0.4.zip. Anda boleh menggunaan file dengan versi yang lebih tinggi jika sudah ada. Kemudian, unzip file diatas dan jalankan program installasi postgresql-8.0.msi.

Catatan: jika anda melihat kotak dialog security warning, klik pada tombol Run untuk melanjutkan

Kemudian, anda akan melihat kotak dialog PostgreSQL Installation Wizard. Pilih bahasa yang inginkan pada instruksi installation dan klik tombol Start untuk memulai.

Kemudian anda akan melihat Welcome to the PostgreSQL Installation Wizard. Klik pada tombol Next untuk melanjutkan.

Kotak dialog berikutnya akan berisi catatan installation. Klik pada tombol Next untuk melanjutkan.

Kotak dialog selanjutnya menunjukkan pilihan apa saja yang akan di-instal. Selain dari pilihan default, anda dapat memilih PostgreSQL dan “Entire Feature will be installed on local hard drive .” Kemudian klik pada tombol Next untuk melanjutkan.

Selanjutnya, buka user management applet pada Window dan buat satu user baru. Contohnya pada Windows XP Professional, masuk ke Computer Management MMC dan pilih Users. Lalu, buka bagian Action/New User.

Buat User baru sebagai berikut:

User Name: postgres
Password: postgres
Un-check: “User must change password at next logon”

Lalu, klik tombol Create.

Catatan: Account ini tidak boleh di-setup dengan administrator privileges. Postgres tidak dapat berjalan sebagai user admin.

Selanjutnya, pada proses instalasi PostgreSQL, ketikkan user tersebut diatas pada kolom Account Name: postgres dan passwordnya pada kotak dialog Service Configuration. Klik tombol Next.

Kotak dialog Initialize database cluster akan muncul. Masukkan nama superuser dari postgres dan password account ini. Lalu, klik pada tombol Next untuk melanjutkan.

Kotak dialog selanjutnya memberikan pilihan jika anda ingin meng-install PL/pgsql. Biarkan saja seperti setting default dan klik tombol Next.

Lalu, anda akan diminta modul tambahan apa saja yang ingin diinstal. Biarkan saja apa adanya dan klik tombol Next.

Kotak dialog Enable PostGIS akan muncul. Biarkan saja apa adanya dan klik tombol Next.

Akhirnya, kotak dialog Ready to install muncul. Klik tombol Next untuk memulai proses instalasi.

Ketika proses installation selesai, klik tombol Finish.

Masuk ke menu Windows Start/Run dan ketik perintah: runas /user:postgres cmd.exe lalu tekan tombol Enter. Ini akan memunculkan command prompt yang dijalankan oleh user postgres.

Ketika diminta password, ketikkan password postgres dan tekan tombol Enter.

Jika tadinya adan memilih lokasi default untuk semua program, pindahlah dari C:\Windows\system32 ke direktori C:\Program Files\PostgreSQL\8.0\bin.

Pada prompt anda harus mengetikkan perintah berikut ini untuk membuat user PostgreSQL baru:

createuser -d -a sql-ledger

dan tekan tombol Enter. Anda akan diminta untuk memasukkan password untuk account PostgreSQL ini. Masukkan password postgres dan tekan tombol Enter.

Selanjutnya, buka file pg_hba.conf file yang ada di C:\Program Files\PostgreSQL\8.0\data directory dengan Notepad.exe. Scroll ke bagian bawah file dan update baris-baris ini:

host all all 127.0.0.1/32 md5

menjadi:

host all all 127.0.0.1/32 trust

Simpan perubahan dan keluar dari Notepad.exe.

Install SQL Ledger

Untuk meng-install SQL-Ledger, download file production release terbaru dari:

http://www.sql-ledger.org/cgi-bin/nav.pl?page=source/index.html&title=Download

Pada saat buku ini ditulis file install yang digunakan adalah: sql-ledger-8.5.1.tar.gz

Catatan: Ketika men-download file tersebut, Windows akan membuat nama file tersebut sebagai sql-ledger-2.8.5.tar.tar. Mohon di-rename menjadi to: sql-ledger-2.8.5.tar.gz sebelum melakukan unzip.

Unzip file tersebut ke direktori Apache HTTP server, misalnya
C:\Program Files\Apache Group\Apache2. Direktori ini dipilih untuk memudahkan instalasi dan proses backup nantinya. Ketika anda membuka file sql-ledger-2.8.5.tar.gz, maka anda akan diminta untuk men-decompress file tersebut ke suatu temporary folder. Klik pada tombol Yes untuk melanjutkan.

Lalu, klik pada tombol Extract pada aplikasi Winzip.

Lalu, arahkan ke direktori program Apache server, misalnya
C:\Program Files\Apache Group\Apache2 atau ketikkan direktori tujuan pada kolom Extract to. Kemudian klik pada tombol Extract.

Kemudian, download lagi file program SHEBANG. Program ini diperlukan untuk meng-update files agar menyesaikan dengan lokasi perl di Windows. Untuk mendownload nya:

• Buka web page dengan alamat http://www.sql-ledger.org/source/windows/shebang
• Buka menu File/Simpan As.
• Arahkan ke direktori SQL-Ledger. Directory ini seharusnya ada di C:\Program Files\Apache Group\Apache2\sql-ledger
• Pastikan bahwa Simpan as type adalah Text File
• klik tombol Simpan

Selanjutnya, buka Command Prompt dan arahkan ke direktori
C:\Program Files\Apache Group\Apache2\sql-ledger .

Pada prompt, ketikkan perintah: type admin.pl |more
Perintah ini akan menampilkan ini file admin.pl pada console. Perhatikan bahwa pada baris paling pertama dari script ini adalah lokasi program Perl yang tidak benar untuk Windows. Ini adalah lokasi direktori untuk UNIX/Linux.

Kemudian, tekan tombol CTRL dan C key bersamaan.

Pada command prompt, ketikkan: ren shebang.txt shebang dan tekan tombol Enter.

Pada command prompt, ketikkan: perl shebang dan tekan tombol Enter.

Pada commange prompt, ketikkan sekali lagi perintah ini: type admin.pl |more
Perhatikan pada baris paling pertama dari script ini bahwa lokasi program Perl sekarang sudah valid.

Meng-update HTTPD.CONF

Buka file httpd.conf di Notepad.exe. Klik menu Start/Run dan ketikkan
notepad C:\Program Files\Apache Group\Apache2\conf\httpd.conf pada kolom Open. Lalu tekan tombol OK.

Lalu, scroll ke bawah sampai akhir file httpd.conf dan tambahkan directive di bawah ini:

Alias /sql-ledger "C:/Program Files/Apache Group/Apache2/sql-ledger/"
<Directory "C:/Program Files/Apache Group/Apache2/sql-ledger/">
AllowOverride All
AddHandler cgi-script .pl
Options +ExecCGI
Order Allow,Deny
Allow from All
</Directory>
<Directory "C:/Program Files/Apache Group/Apache2/sql-ledger/users/">
Order Deny,Allow
Deny from All
</Directory>

Sekarang simpan file httpd.conf dan keluar dari Notepad.exe. Masuk melalui menu File/Simpan lalu File/Exit.

Restart  Apache HTTP server seperti pada langkah 11 pada bagian Instalasi Apache HTTP Server 2.0.55.

Buka web browser dengan URL http://localhost/sql-ledger. Selanjutnya akan muncul halaman seperti di bawah ini.

Setting Password Administrator dan Database

Buka URL http://localhost/sql-ledger/admin.pl dan klik tombol Login.

Lalu, klik tombol Change Admin Password . Default password adalah kosong.

Jika anda sudah mengisikan password baru, klik tombol Change Password .

Lalu, anda akan dimintai password. Masukkan password anda yang baru dan klik tombol Continue .

Selanjutnya, klik pada tombol Pg Database Administration.

Karena anda menggunakan PostgreSQL pada Windows, ketikkan localhost pada kolom Host name dan nomor port 5432 pada kolom Port .

Ketikkan nama dataset yang anda inginkan, misalnya toko. Masukkan nama tersebut semua dalam huruf kecil. Pilih Bahasa-Indonesia_default pada pilihan Create Chart of Account. Lalu, klik tombol Continue .

Jika dataset berhasil dibuat, anda akan melihat pesan seperti dibawah. Lalu, klik pada tombol Continue .

Administrasi User

Langkah selanjutnya adalah membuat user yang akan menggunakan SQL-Ledger.

Lakukan hal ini dengan men-klik tombol Add User pada menu Administrator.

Halaman isian data user akan muncul seperti berikut ini:

Pada halaman ini, pada bagian SQL-LEdger Accounting Administration/ Edit Usr:

1. Isikan pada kolom Login : kode login user yang anda inginkan, misalnya admin
2. Isikan pada kolom Password: password untuk login di atas misalnya admin.
3. Isikan pada kolom Name: nama lengkap user misalhya administrator
4. Isikan pada kolom Signature:
5. Isikan pada kolom Phone: nomor telephone
6. Isikan pada kolom Fax: nomor Fax
7. Isikan pada kolom Company: nama perusahaan
8. Pilih pada kolom Date Format: format tanggal yang akan digunakan
9. Pilih pada kolom Number format: format angka yang akan digunakan
10. Isikan pada kolom Drop Down Limit: jumlah item pilihan yang akan dimunculkan untuk semua jenis pilihan pada form isian
11. Isikan pada kolom Menu Width: lebar frame menu
12. Pilih pada kolom Language: bahasa yang akan digunakan, misalnya Bahasa Indonesia
13. Isikan pada kolom Session Timeout: berapa lama sistem akan otomatis logout jika tidak ada aktifitas selama waktu tersebut
14. Pilih pada kolom Stylesheet: model kombinasi warna
15. Isikan pada kolom Use Template: template yang akand digunakan
16. Jika perlu isikan pada kolom New Template: nama template baru

Pada bagian Database:

1. klik pada Driver Pg
2. Isikan pada kolom Dataset: nama dataset yang telah anda buat pada langkah sebelumnya yaitu toko
3. Isikan pada kolom User dan Password: nama username dan password PostgreSQL yang telah anda buat pada langkah 2.4 Instalasi PostgreSQL point 9, yaitu postgres dan password postgres
4. Isikan pada kolom Host dan Port: nama komputer dimana PostgreSQL jalan yaitu localhost dan post 5432.

Pada bagian Access Control: pilih jenis user dan akses menu-menu yang diperbolehkan untuk user ini.

Ketika selesai, klik tombol Simpan di bagian bawah halaman ini. Jika user berhasil dibuat maka akan muncul pada halaman SQL-Ledger Administrator seperti berikut ini:

Untuk meng-edit user , klik pada login user tersebut, sehingga muncul kembali halaman yang menampilkan informasi lengkap user tersebut seperti pada langkah sebelumnya.

Akhmad Daniel Sembiring

vITraining.com – Qualified IT Products, Outsourcing, and Services

Ligarwangi.com – Linux, E-book, Coffee, Gift, etc

Pada kondisi dimana user minta bisa mencoba aplikasi yang kita bangun menggunakan WAMP (Windows Apache MySQL PHP) dan belum terdapat server komputer yang dapat kita installkan infrastruktur yang dibutuhkan, kita dapat menggunakan portable WAMP yang dapat dijalankan dari USB.

Kondisi lainnya adalah ketika kita ingin membuat versi trial aplikasi web kita ke calon customer.

Salah satu yang dapat digunakan adalah USB Webserver (http://www.usberbserver.nl).  Aplikasi ini berisi Apache, PHP, dan MySQL yang telah dikonfigurasi dan siap dijalankan sehingga kita tinggal mengisi aplikasi web yang akan kita demokan ke client.

Instalasi USB Webserver cukup mudah, tinggal extract file setupnya aja ke drive USB yang mau dibawah.  Setelah disetup dan diextrak, akan terdapat beberap direktori dibawah direktori utama misalnya E:\UsbWebserver, dimana E: adalah USB drive.

Direktori yang paling penting adalah D:\UsbWebserver\Root, dimana kita akan menyimpan aplikasi  web yang akan dijalankan.

Setelah dijalankan USB Webserver akan siap melayani akses web server pada port 8080 (dapat diganti melalui Settings Apache). Jadi misalnya aplikasi kita disimpan pada direktori C:\UsbWebserver\Root\demo maka aplikasi tersebut tinggal diakses melalui web browser pada alamat http://127.0.0.1:8080/demo.

Ketika dijalankan, maka terlihat halaman untuk setingan utama USB Webserver yaitu bahasa, hide at start, dan open localhost at start untuk menjalankan browser secara otomatis saat aplikasi dijalankan:

Pada halaman tsb kita dapat mengontrol server MySQL, APache, dan SMTP yaitu dengan menklik tombol-tombol yang terdapat pada bagian atas halaman tsb. Tanda kotak artinya server sedang berjalan, dan untuk mematikannya klik tombol tsb sehingga berubah menjadi tombol segitiga yang artinya server sedang tidak berjalan.

Klik tab Smtp untuk menampilkan settingan server SMTP yaitu host, port, dan email.

Klik tab Apache untuk melihat settingan server Apache, yaitu port webserver yang default nya 8080, dan jenis error yang akan ditampilkan pada log, defaultnya semua error.

Klik pada tab MySQL untuk melihat settingan MySQL yaitu port yang defaultnya  3307 dan password root MySQL yaitu usbw. APlikasi yang hendak kita jalankan perlu menyesuaikan dengan setting yang didefinisikan disini.

Untuk menyimpan settingan yang sudah ditentukan klik tombol "Opslaan" … gak tau artinya apa soalnya bhs Belanda, tapi kira-kira kayak OK gitu.. Atau klik tombol "Annuleren" untuk cancel.

Untuk membuka log file, config file, phpmyadmin, dll dapat digunakan tombol segitiga dibagian atas tengah window.

Menu yang muncul dapat digunakan untuk:

• membuka halaman setting spt diatas, Settings->Usb Webserver
• membuka config file apache httpd.conf, Settings->Apache
• membuka config file PHP.INI, Settings->PHP
• membuka config file phpmyadmin, Settings->Phpmyadmin
• membuka web browser pada alamat default, Localhost
• membuka folder root directory, Root Directory
• membuka web browser PhpMyAdmin
• membuka web browser yang berisi halaman informasi PHP, Php Info
• membuka halaman About
• dan menutup aplikasi

Beberapa Catatan

• settingan port mysql defaultnya 3307, sehingga aplikasi anda perlu menyesuaikan terutama pada function db_connect mysql, atau ganti settingan ini menjadi default MySQL yaitu 3306.
• settingan port apache defaultnya 8080, sehingga pemanggilan aplikasi harus menyertakan nomor port ini, misalnya http://localhost:8080, atau ganti settingan ini menjadi default Apache yaitu 80.
• settingan PHP.INI, allow_call_time_pass_reference defaultnya Off, sehingga aplikasi PHP perlu menyesuaikan yaitu tidak bisa mengirimkan parameter function langsung menggunakan variabel tetapi harus menggunakan refference variable tersebut, atau ganti settingan ini menjadi On (tidak direkomendasikan oleh PHP/Zend karena option ini bakalan dimatikan )