1. Install Development Tools
2. Install required packages
3. Modify the System Configuration and Kernel (don’t panic)
4. Create Required Users
5. Install Oracle Apps

Install Development Tools

yum groupinstall "Development Tools"

Install required packages

You can either install the following packages using yum or download this file which include all the files.

1. openmotif21-2.1.30-11.EL5.i386.rpm
2. xorg-x11-libs-compat-6.8.2-1.EL.33.0.1.i386.rpm
3. elfutils-libelf-devel-0.125
4. elfutils-libelf-devel-static-0.125
5. libaio-devel-0.3.106
6. unixODBC-2.2.11
7. unixODBC-devel-2.2.11

Note: You need to make the following modifications after installing openmotif

$ unlink /usr/lib/libXtst.so.6
$ ln -s /usr/X11R6/lib/libXtst.so.6.1 /usr/lib/libXtst.so.6

Modify the System Configuration and Kernel

Open /etc/sysctl.conf as root

$ su - root
$ vi  /etc/sysctl.conf

then add the following lines at the end of the file

#Oracle EBS R12.1.1 Kernel Settings
kernel.shmall = 2097152
kernel.shmmax = 4294967295
kernel.shmmni = 4096
kernel.sem = 256 32000 100 142
fs.file-max = 327679
net.ipv4.ip_local_port_range = 10000 65000
net.core.rmem_default=262144
net.core.rmem_max=262144
net.core.wmem_default=262144
net.core.wmem_max=4194304

Now lets apply the new settings

$ /sbin/sysctl –p

Add the following lines to the /etc/security/limits.conf file:

* hard nofile 65535

* soft nofile 4096

* hard nproc 16384

* soft nproc 2047

Add the following lines to the /etc/resolv.conf file:

options attempts:5
options timeout:15

Now we need to restart the system so the above modifications gets applied.

Create Required Users

We’ll need to create one group dba and two users, oracle and applmgr. The oracle users will be the owner of the database tier folders and services, while the applmgr user will be the owner of the applications tier.

You can either create the group and the users using GUI or use the following commands:

$ su - root
$ groupadd dba
$ useradd –g dba  –d  /home/oracle oracle
$ useradd –g dba  –d  /home/applmgr applmgr

Install Oracle Apps

Before we start the installation we need first to create the installation directory. We will name the directory ebs and create at root /.

$ su - root
$ cd /
$ mkdir ebs
$ chown oracle:dba ebs
$ chmod 777 ebs

Now we can start the rapid install wizard. I’ll not be using a staging area but the following applies to both installing from a staging area or from Oracle’s EBS media pack DVDs.
I’ll assume that the DVD-Rom is mounted at /media/cdrom.

// run the following as the oracle user, not root
$ cd /media/cdrom/Disk/rapidwiz
$ ./rapidwiz

That’s it, below are some screen shots of the installation using a fresh database. Have fun.

Installation Screen 01

Installation Screen 02

Installation Screen 03

Installation Screen 04

Installation Screen 05

Installation Screen 06

Installation Screen 07

Installation Screen 08

Installation Screen 09

Installation Screen 10

Installation Screen 11

Installation Screen 12

]]> http://sandbox-ws.com/oracle/how-to-install-oracle-ebs-r12-on-redhat-enterprise-linux-5-5/feed 0 http://sandbox-ws.com/firefox/firefox-extensions-every-developer-should-use http://sandbox-ws.com/firefox/firefox-extensions-every-developer-should-use#comments Wed, 26 Aug 2009 22:46:07 +0000 Ahmed El.Hussaini http://sandbox-ws.com/?p=427 There are a lot of factors that makes Firefox the best browser currently available, but what makes Firefox really stands out is it support for extensions. A Firefox extension is an addon feature to the browser. There are thousands of available addons and in this post I’ll list some of the most used extensions by developers, in fact every developer should be using them.

Firebug

Firebug integrates with Firefox to put a wealth of web development tools at your fingertips while you browse. You can edit, debug, and monitor CSS, HTML, and JavaScript live in any web page.

As you can see in the above image Firebug adds the option “Inspect Element” which appears when you right click on any element in a web page. When clicked it will display the source code of the select item along with the css styles applied on that element (see below).

Web Developer

The Web Developer extension adds a menu and a toolbar to the browser with various web developer tools. It is designed for Firefox, Flock and Seamonkey, and will run on any platform that these browsers support including Windows, Mac OS X and Linux.

Firecookie

Firecookie is a an extension for Firebug that makes possible to view and manage cookies in your browser. Apart from all the other cookie managers and viewers available as Firefox extensions, this one is made as an extension for Firebug, so web developer has the functionality accessible within familiar Firebug’s UI.

Live HTTP Headers

View HTTP headers of a page and while browsing.

Page Speed

Page Speed is an open-source Firefox/Firebug Add-on. Webmasters and web developers can use Page Speed to evaluate the performance of their web pages and to get suggestions on how to improve them.

Firefinder

Firefinder is an extension to Firebug (in Firefox) and offers the functionality to, in a quick way, find HTML elements matching chosen CSS selector(s) or XPath expression. It allows you to instantly test your CSS selectors in the page while seeing the content at the same time, and matching elements will be highlighted.

FCBKcomplete

Fancy facebook-like dynamic inputs with auto complete & pre added values. If you have any comments or requests, please post them and I will try to include all the requested features in the upcoming release.

Usage

<script language="JavaScript">
$(document).ready(function() {
$.facebooklist('#elem', '#list', '#complete',{url:'ajax-url',cache:1}, height, {userfilter:1,casesensetive:0});
});
</script>

elem – input element id or object
list – preadded elements
complete – autocomplete div id or object
ajax – object with two parametrs a) url to fetch json object b) use cache
height – maximum number of element shown before scroll will apear
filter – object with two parametrs a)case sensitive b) show/hide filtered items
newel – show typed text like a element

Facebox

Facebox is a jQuery-based, Facebook-style lightbox which can display images, divs, or entire remote pages.
It’s simple to use and easy on the eyes. Download the tarball, view the examples, then start enjoying the curves.

A WordPress plugin is simply one or more PHP files that adhere to certain rules and conventions. All you need to understand and complete this tutorial is a basic understanding of PHP programming.

Before we get started, let me explain what does the plugin we’re going to write will do. It simply displays the most commented 5 posts. Pretty simple and straight forward plugin which makes it an ideal example to explore the concept behind a WordPress plugin. We will call the plugin “WP Most Commented”.

Plugin Folder Structure

WordPress doesn’t enforce a strict folder structure unlike most frameworks available, basically all you have to do is create a folder with the desired name (wp_most_commented in our case) under the plugins folder located in /wp-content/

Let’s create the plugin folder:

In this folder we will create the plugin main PHP file, let’s call it “wp-most-commented.php”.

Activating/Deactivating the Plugin

In order for WordPress to be able to activate/deactivate a plugin, we need to add PHP comments to the main file that tells WordPress about our plugin. Just copy and paste the following in the main file.

<?php
/*
Plugin Name: WP Most Commented
Plugin URI: http://sandbox-ws.com
Description: Displays Most Commented Posts
Version: 1.0
Author: Ahmed El.Hussaini
Author URI: http://sandbox-ws.com
*/
?>

As you can see that the above comments tells WordPress some meta data about the plugin like the plugin’s name, author, version, and so on. Those meta data are used to display some info about the plugin in the Admin panel of WordPress. After saving the main file goto WordPress’ admin panel, then click “Plugins” in the left side bar and you should find that our plugin was detected by WordPress.

Now you can activate and deactivate the plugin, although it will make no difference since we haven’t added any logic to the plugin main file.

Most Commented SQL Query

The MySQL query we will use to retrieve the most commented 5 posts is:

SELECT ID, post_title, comment_count FROM $wpdb->posts WHERE post_status = 'publish' and comment_count > 0 ORDER BY comment_count DESC LIMIT 5

You can test the query if you like but make sure to replace $wpdb->posts with your post’s table which is probably wp_posts.

Let’s add the function that will retrieve the most commented posts and displays them in a list. Just copy and paste the following to the plugin’s main file.

function wp_most_commented() {
	global $wpdb;

	// select top most commented posts that have comment count > 0 and are published
	$sql = "SELECT ID, post_title, comment_count FROM $wpdb->posts WHERE post_status = 'publish' and comment_count > 0 ORDER BY comment_count DESC LIMIT 5";

	// execute query
	$posts = $wpdb->get_results($sql);

	$html = '';

	$html .= '<ul>';

	foreach ($posts as $post) {

		$title = $post->post_title;

		$permalink = get_permalink($post->ID);

		$comment_count = $post->comment_count;

		$html .= '<li>';

		$html .= '<a href="'.$permalink.'" title="'.$title.'">'.$title.'</a>';

		$html .= '</li>';

	}

	$html .= '</ul>';

	echo $html;

}

Testing the Plugin

Open the sidebar.php file in your current active theme and place the following snippet:

<?php if(function_exists('wp_most_commented')): ?>
	<div id="most_commented">
		<h3>Most Commented Posts</h3>
		<?php wp_most_commented() ?>
	</div>
<?php endif; ?>

In your sidebar you should see something similar to the following screenshot:

You’d probably want to customize the plugin main function to allow users to specify the number of posts to be displayed instead of the hard coded 5 limit, also you can add the ability to pass css classes, but I’ll this task to you.

Use the links below to download the bundles:

• CSS Bundle
• Ruby on Rails 2 Bundle

Files Needed

• Tomcat6 for Oracle Workshop

After downloading the above file, extract it and copy the contents of the debugger folder to BEA_WORKSHOP_HOMEworkshop_10.3workshop4WPeclipsepluginscom.m7.nitrox.debugger_3.5.100.200807251738 and the contents of the serverdef folder to BEA_WORKSHOP_HOMEworkshop_10.3workshop4WPeclipsepluginscom.m7.nitrox.serverdef_3.5.100.200807251738

Now open the cmd and change to the directory BEA_WORKSHOP_HOMEworkshop_10.3 and run the following command

workshop.exe -clean

Now you can create dynamic web projects and add JSF 1.2 support to it with Apache Tomcat 6 as the run time server.

I’m assuming that because you’re reading this article then you probably have some general info about Subversion and maybe some other version control system like CVS. If not, then no problem, this article will still help you to get started using Subversion.

This article assumes that you’re running windows xp/vista, but the concept is the same and should work just fine on linux and mac os x systems as well, the only difference will be in the installation which you’ll find a lot of guides on the internet.

So lets get started, here is an overview of the guide:

1. Downloading and Installing Subversion for Windows
2. Creating a Repository
3. Initializing Repository Structure
4. Creating A New Project
5. Checking Out a Project
6. Adding Files to the Working Copy
7. Committing Changes

Downloading Subversion for Windows

Subversion for windows can be downloaded from here. After downloading is finished, install the package. If it asks to restart, please do so. In order to verify that the installation was successful open the command line prompt and type svn then hit enter on the keyboard. If you get an output similar to the following then the installation was successful.

Type 'svn help' for usage.

Creating a Repository

Now that we have subversion installed we want to create out first repository. Normally you’ll want to store the repository on the root of a drive, for example c:\repo, so lets use this path to store our repository.

To create a new repository we use the following command:

cd c:\
svnadmin create repo

Initializing Repository Structure

Defining the structure of your repository is completely up to you, there’s no restrictions in subversion that forces you to structure your repository in a certain way but most developers around the world uses the same structure as a global convention. This structure states that the repository will be divided into three main folders: Tags, Branches, and Trunk. I’ll not dive into why this structure was agreed upon between developers around the world. I’ll leave that for another article. Maybe that reason will make you visit my blog again .

So lets create the repository initial structure.

svn mkdir file:///c:/repo/tags file:///c:/repo/trunk file:///c:/repo/branches -m "initialized repo structure"

The above command should result in the following output

Committed out revision 1.

Lets explain what happened now, first we used the svn command mkdir to create three folders and we also added a message using the parameter -m.

After running the mkdir command svn reports that the repository revision number is now (1). Each time you modify the repository whether by adding, modifying, or deleting, the revision number increase by one. So the repo revision number is an indication of the number of changes made to the repository since it was created.

Creating A New Project

Now that our repo structure is ready lets create our first version controlled project. For sake of testing we will name the project sandbox-ws. The sandbox-ws project will be added to the trunk folder. We will use the same mkdir command

svn mkdir file:///c:/repo/trunk/sandbox-ws -m "created sandbox-ws project"

Checking Out a Project

The figure below outlines the basic operations done on a subversion repository. First we create the repository, then initialize the project structure, then create one or more projects in the repository, and last but not least, the developers checks out a project, modifies it, and then commits the changes back to the repository so other developers can update their working copies to reflect those changes.

If sandbox-ws was a PHP project for example, then the working copy will be in your web server’s documents root, htdocs for example if you’re using Apache. But for sake of testing we will create our working copy on the Desktop.

To check out the sandbox-ws project run the following command(NOTE: I assume that you’ve changes the cmd path to your desktop):

svn co file:///c:/repo/trunk/sandbox-ws

The above command should result in the following output

Checked out revision 1.

Now we move to the sandbox-ws project:

cd sandbox-ws

Adding Files to the Working Copy

Now that we have checked out the sandbox-ws project, it’s time to add some files to it. We will start with a simple php file, see below

// index.php
<?php echo 'Hello World!' ?>

What we have done by adding a new file to the working copy is that we simply modified it. Lets see what subversion have to say now, run the following command from the sandbox-ws project folder

svn status

The above command output should be similar to the following:

?     index.php

The (?) next to the index.php file indicates that svn detected that the index.php status is unknown i.e. it’s new and has not been added to the working copy yet.

Since svn doesn’t know the status of the index.php file, we should add it to the working copy, to do this run the following command:

svn add index.php

The output of the following command should be similar to the following:

A      index.php

As you may have guessed, (A) means that the file has been added to the working copy, the next step would be committing the changes to the repository which would result in incrementing the repository revision number by one.

Committing Changes

After adding new the index.php file to the repository, we’ll want to commit it to the repository for other developers to be able to update their working copies and take advantage of our newly added file. To do so run the following command:

svn ci -m "added index.php"

The output of the following command should be similar to the following:

Adding         index.php
Transmitting file data .
Committed revision 2.

I think that the above doesn’t need any explanation, but the following does, run the following command:

svn info

The output of the following command should be similar to the following:

Path: .
URL: file:///c:/repo/trunk/sandbox-ws
Repository Root: file:///c:/repo
Repository UUID: 50729929-acbb-d647-b00b-4f3555a6f6a3
Revision: 1
Node Kind: directory
Schedule: normal
Last Changed Author: Sandbox
Last Changed Rev: 1
Last Changed Date: 2009-01-23 16:52:06 +0200 (Fri, 23 Jan 2009)

Of course some of the data displayed by the following command will differ between you and me but what is interesting about the command is that it indicates that the revision number of the working copy is less than the current revision number of the repository which is currently is 2. The reason of this is that after our commit the repository revision number as we have said increments by one but the our working copy is now out dated, we need to update it so the revision number of the working copy is similar to the repository. To do so run the following command:

svn update

The output of the following command should be similar to the following:

At revision 2.

I hope that this article successfully cleared what subversion is and how to start using it, in upcoming articles we will dive into more advanced topics.

Before starting I strongly recommend reading part one, and two if you haven’t done so already. OK lets get started, we will be modifying the following files:

• CategoryForm.class.php which represents the parent model
• SubcategoryI18nForm.class.php which represents the form of the i18n model of the child model
• Subcategory.class.php which represents the child model

Files need for this article

• sfWidgetFormInputDelete

Schema

  category:
      _attributes: { phpName: Category }
      id: { type: INTEGER, size: '11', primaryKey: true, autoIncrement: true, required: true }
      name: { type: VARCHAR, size: '255', required: true }
      created_at: { type: TIMESTAMP, required: false }
      updated_at: { type: TIMESTAMP, required: false }
  subcategory:
      _attributes: { phpName: Subcategory, isI18N: true, i18nTable: subcategory_i18n }
      id:          { type: integer, required: true, primaryKey: true, autoincrement: true }
      category_id: { type: INTEGER, size: '11', required: true, foreignTable: category, foreignReference: id, onDelete: CASCADE}
      created_at: { type: TIMESTAMP, required: false }
      updated_at: { type: TIMESTAMP, required: false }

  subcategory_i18n:
    _attributes: { phpName: SubcategoryI18n }
    id:          { type: integer, required: true, primaryKey: true, foreignTable: subcategory, foreignReference: id, onDelete: CASCADE }
    culture:     { isCulture: true, type: varchar, size: 7, required: true, primaryKey: true }
    name:        { type: varchar, size: 50 }

SubcategoryI18nForm

public function configure() {
    unset($this['culture'], $this['id']);
}

Subcategory

public function getI18nObject($culture = 'en') {

    $this->setCulture($culture);

    $i18ns = $this->getSubcategoryI18ns();

    if (isset($i18ns[0])) {

        return $i18ns[0];

    }

    return null;

}

CategoryForm

public function configure() {

// remove timestamps
unset($this['created_at'], $this['updated_at']);

	// embed forms only when editing
	if (!$this->isNew()) {

		$user_culture = sfContext::getInstance()->getUser()->getCulture();

		// embed all subcategory forms
		foreach ($this->getObject()->getSubcategorys() as $subcategory) {

			// get the subcategory_i18n model object relative to the current user culture
			$subcategory_i18n_object = $subcategory->getI18nObject($user_culture);

			// create a new subcategory_i18n form for the current subcategory model object
			$subcategory_i18n_form = new SubcategoryI18nForm($subcategory->getI18nObject('en'));

			// get widget schema of subcategory_i18n form
			$subcategory_i18n_form_widget_schema = $subcategory_i18n_form->getWidgetSchema();

			// set the input delete widget
			$subcategory_i18n_form_widget_schema['name'] = new sfWidgetFormInputDelete(array(
			'url' => 'category/deleteSubcategory',      // required
			'model_id' => $subcategory->getId(),        // required
			'confirm' => 'Sure???',                     // optional
			));

			// create a new subcategory form for the current subcategory model object
			$subcategory_form = new SubcategoryForm($subcategory);

			// embed the i18n form
			$subcategory_form->embedForm('subcategory_i18n'.$subcategory_i18n_object->getId(), $subcategory_i18n_form);

			// subcategory form widget schema
			$subcategory_form_widget_schema = $subcategory_form->getWidgetSchema();

			// disable label
			$subcategory_form_widget_schema['subcategory_i18n'.$subcategory_i18n_object->getId()]->setLabel(false);

			// embed the subcategory form in the main category form
			$this->embedForm('subcategory'.$subcategory->getId(), $subcategory_form);

			// set a custom label for the embedded form
			$this->widgetSchema['subcategory'.$subcategory->getId()]->setLabel('Subcategory: '.$subcategory->getName());

		}

		// create a new subcategory form for a new subcategory model object
		$subcategory_form = new SubcategoryForm();

		// create a new subcategory form for a new subcategory_i18n model object
		$subcategory_i18n_form = new SubcategoryI18nForm();

		// embed the subcategory_i18n form in the parent subcategory form
		$subcategory_form->embedForm('subcategory_i18n', $subcategory_i18n_form);

		// subcategory form widget schema
		$subcategory_form_widget_schema = $subcategory_form->getWidgetSchema();

		// disable label
		$subcategory_form_widget_schema['subcategory_i18n']->setLabel(false);

		// embed the subcategory form in the main category form
		$this->embedForm('subcategory', $subcategory_form);

		// set a custom label for the embedded form
		$this->widgetSchema['subcategory']->setLabel('New Subcategory');

	}
}
public function bind(array $taintedValues = null, array $taintedFiles = null) {

		if(!$this->isNew()) {

			$user_culture = sfContext::getInstance()->getUser()->getCulture();

			// remove the embedded new form if the name field was not provided
			if (is_null($taintedValues['subcategory']['subcategory_i18n']['name']) || strlen($taintedValues['subcategory']['subcategory_i18n']['name']) === 0 ) {

				unset($this->embeddedForms['subcategory'], $taintedValues['subcategory']);

				// pass the new form validations
				$this->validatorSchema['subcategory'] = new sfValidatorPass();

			} else {

				// set the category of the new subcategory form object
				$this->embeddedForms['subcategory']->getObject()->setCategory($this->getObject());

				// get subcategory embedded forms
				$subcategory_embedded_forms = $this->embeddedForms['subcategory']->getEmbeddedForms();

				// set subcategory parent of the subcategory_i18n model object
				$subcategory_embedded_forms['subcategory_i18n']->getObject()->setSubcategory($this->embeddedForms['subcategory']->getObject());

				// set the culture of the subcategory_i18n model object
				$subcategory_embedded_forms['subcategory_i18n']->getObject()->setCulture($user_culture);
			}

		}

		// call parent bind method
		parent::bind($taintedValues, $taintedFiles);

	}

As you can see this is a lot of code to copy and paste every time you need the functionality, that’s why I’m currently working on extending the Admin Generator in order to have this functionality available when you generate an admin module by default.

Before we get started here’s a sneak peak of the CategoryForm after the modifications to be done.

Files need for this article

• sfWidgetFormInputDelete

Ok, lets get started, consider the following schema:

category:
    _attributes: { phpName: Category }
    id: { type: INTEGER, size: '11', primaryKey: true, autoIncrement: true, required: true }
    name: { type: VARCHAR, size: '255', required: true }
    created_at: { type: TIMESTAMP, required: false }
    updated_at: { type: TIMESTAMP, required: false }
subcategory:
    _attributes: { phpName: Subcategory }
    id: { type: INTEGER, size: '11', primaryKey: true, autoIncrement: true, required: true }
    name: { type: VARCHAR, size: '255', required: true }
    category_id: { type: INTEGER, size: '11', required: true, foreignTable: category, foreignReference: id, onDelete: CASCADE, onUpdate: RESTRICT }
    created_at: { type: TIMESTAMP, required: false }
    updated_at: { type: TIMESTAMP, required: false }

Steps needed to achieve the required result

1. Modify the CategoryForm to include embedded forms for all available subcategories of the current category.
2. Modify the widget of the name field in the subcategory
3. Modify the CategoryForm to add a new blank subcategory form
4. Override the bind method of the sfForm class to skip saving and validating the new subcategory form if the name field was left blank
5. Remove fields from SubcategoryForm

Embedded forms for all available subcategories of the current category [step 1, 2, and 3]

// lib/forms/CategoryForm.class.php
public function configure() {

  // remove timestamps
  unset($this['created_at'], $this['updated_at']);

  // embed forms only when editing
  if (!$this->isNew()) {

    // embed all subcategory forms
    foreach ($this->getObject()->getSubcategorys() as $subcategory) {

    // create a new subcategory form for the current subcategory model object
    $subcategory_form = new SubcategoryForm($subcategory);

    // embed the subcategory form in the main category form
    $this->embedForm('subcategory'.$subcategory->getId(), $subcategory_form);

    // set a custom label for the embedded form
    $this->widgetSchema['subcategory'.$subcategory->getId()]->setLabel('Subcategory: '.$subcategory->getName());

    // change the name widget to sfWidgetFormInputDelete
    $this->widgetSchema['subcategory'.$subcategory->getId()]['name'] = new sfWidgetFormInputDelete(array(
    'url' => 'category/deleteSubcategory',      // required
    'model_id' => $subcategory->getId(),        // required
    'confirm' => 'Sure???',                     // optional
    ));

  }

  // create a new subcategory form for a new subcategory model object
  $subcategory_form = new SubcategoryForm();

  // embed the subcategory form in the main category form
  $this->embedForm('subcategory', $subcategory_form);

  // set a custom label for the embedded form
  $this->widgetSchema['subcategory']->setLabel('New Subcategory');

  }
}

Override the bind method

public function bind(array $taintedValues = null, array $taintedFiles = null) {

	// remove the embedded new form if the name field was not provided
	if (is_null($taintedValues['subcategory']['name']) || strlen($taintedValues['subcategory']['name']) === 0 ) {

		unset($this->embeddedForms['subcategory'], $taintedValues['subcategory']);

		// pass the new form validations
		$this->validatorSchema['subcategory'] = new sfValidatorPass();

	} else {

		// set the category of the new subcategory form object
		$this->embeddedForms['subcategory']->getObject()->
                setCategory($this->getObject());

	}

	// call parent bind method
	parent::bind($taintedValues, $taintedFiles);

}

Remove fields from SubcategoryForm

public function configure(){
  unset($this['created_at'], $this['updated_at'], $this['category_id']);
}

Now we create the action deleteSubcategory in category module

// apps/backend/modules/category/actions/actions.class.php
public function executeDeleteSubcategory(sfWebRequest $request) {
  $sub_category = SubcategoryPeer::retrieveByPk($request->getParameter('id'));
  $sub_category->delete();
  $this->redirect('@category_edit?id='.$sub_category->getCategory()->getId());
}

That’s it, I hop that you enjoyed this article.

// test/functional/backend/foobarActionsTest.php
include(dirname(__FILE__).'/../../bootstrap/functional.php');

$browser = new sfTestFunctional(new sfBrowser());
$browser->get('foobar/index')->isStatusCode(200);

Now we run the following command to test the module:

php symfony test:functional backend foobarActions

Since the backend application is secured, the above test will result in the following error:

The 401 response code we got means Unauthorized access, since the user isn’t logged, so this is what we need to make the test successful, we need the user to login first before we try to access the foobar/index action.

The solutions is rather simple, first we create a file called sf_guard.php:

// test/functional/sf_guard.php
function signin($username, $password, $browser) {
  $browser = new sfTestFunctional(new sfBrowser());
  return $browser->
    info(sprintf('Signin user using username "%s" and password "%s"', $username, $password))->
    post('/sfGuardAuth/signin', array('signin' => array('username' => $username, 'password' => $password,)))->
    isRedirected()
  ;
}

Next we modify the foobarActionsTest.php:

include(dirname(__FILE__).'/../sf_guard.php');
include(dirname(__FILE__).'/../../bootstrap/functional.php');

$username = 'admin';
$password = 'admin';
$browser = new sfTestFunctional(new sfBrowser());
signin($username, $password, $browser)->get('/foobar/index')->isStatusCode(200);

Now we run the test again, and it passes gracefully

Now as Niko mentioned in his comment, her is another better and simpler way:
First we create a class sfGuardTestFunctional in lib folder

class sfGuardTestFunctional extends sfTestFunctional {

	public function signin($username, $password) {
		return $this->
			info(sprintf('Signin user using username "%s" and password "%s"', $username, $password))->
			post('/sfGuardAuth/signin', array('signin' => array('username' => $username, 'password' => $password,)))->
			isRedirected()
		;
	}
}

Next we modify the foobarActionsTest.php

include(dirname(__FILE__).'/../../bootstrap/functional.php');

$username = 'admin';
$password = 'admin';

$browser = new sfGuardTestFunctional(new sfBrowser());
$browser->
	get('/foobar/index')->
	isStatusCode(401)->
	signin($username, $password)->
	get('/foobar/index')->
	isStatusCode(200)
;

That way it’s much simpler and more efficient, thanks again Niko