What is a Namespace?

XML namespace is a unique identifier that holds information about the creator of the document, in other words it is like a signature. This identifier could avoid problems when we want to reuse an XML that somebody else wrote. Let’s take a look at the following example:

<roomService>
     <hotelid>SUNSET-3</hotelid>
     <room>1001</room>
     <guest>
          <name>Fred</name>
          <lastName>Davis</lastName>
     </guest>
     <order>
          <item>Cheese Burger</item>
          <id>203</id>
          <price>10.99</price>
          <quantity>1</quantity>
     </order>
</roomService>

This is an XML of a reservation, very simple, but let’s suppose that we have to merge the reservation XML with the room service XML:

<roomService>
     <hotelid>SUNSET-3</hotelid>
     <room>1001</room>
     <guest>
          <name>Fred</name>
          <lastName>Davis</lastName>
     </guest>
     <order>
          <item>Cheese Burger</item>
          <id>203</id>
          <price>10.99</price>
          <quantity>1</quantity>
     </order>
</roomService>

At the beginning it looks fine, but hold on, take a closer look. We have a collision in 6 and 12 lines, both contain the same element with a different content. The same happens with the element in lines 7 and 13, but in this case they have the same content.

<reservation id="123456789">
     <arrivingDate>03-09-2012</arrivingDate>
     <departureDate>03-15-2012</departureDate>
     <guestName>Fred</guestName>
     <guestLastName>Davis</guestLastName>
     <hotelID>03</hotelID>
     <room>1001</room>
     <oceanView>true</oceanView>
     <smokingArea>false</smokingArea>
</reservation>
<roomService>
     <hotelID>SUNSET-3</hotelID>
     <room>1001</room>
     <guest>
          <name>Fred</name>
          <lastName>Davis</lastName>
     </guest>
     <order>
          <item>Cheese Burger</item>
          <id>203</id>
          <price>10.99</price>
          <quantity>1</quantity>
     </order>
</roomService>

Avoiding Collisions in Namespaces

To avoid these collisions we have to identify the XML fragments using a namespace.

<res:reservation id="123456789" xmlns:res=”https://marcotello.com/hotel/reservation”>
     <res:arrivingdate>03-09-2012</res:arrivingdate>
     <res:departuredate>03-15-2012</res:departuredate>
     <res:guestname>Fred</res:guestname>
     <res:guestlastname>Davis</res:guestlastname>
     <res:hotelid>03</res:hotelid>
     <res:room>1001</res:room>
     <res:oceanview>true</res:oceanview>
     <res:smokingarea>false</res:smokingarea>
</res:reservation>
<room:roomService xmlns:room=”https://marcotello.com/hotel”>
     <room:hotelid>SUNSET-3</room:hotelid>
     <room:room>1001</room:room>
     <room:guest>
          <room:name>Fred</room:name>
          <room:lastName>Davis</room:lastName>
     </room:guest>
     <room:order>
          <room:item>Cheese Burger</room:item>
          <room:id>203</room:id>
          <room:price>10.99</room:price>
          <room:quantity>1</room:quantity>
     </room:order>
</room:roomService>

As you can see now the elements with conflicts have different names and they are using a prefix. Notice that the prefix is declared in the root node of the XML fragment.

The correct way to name your namespaces is first using the key word xmlns which means that a namespace is declared.

xmlns:res=”https://marcotello.com/reservation”

Then declare a prefix to refer the namespace in the elements

xmlns:res=”https://marcotello.com/reservation”

And at the end declare an URI to identify your XML fragments in a document, an URI means Uniform Resource Identifier and could be any string of characters that are considered unique, for example:

https://marcotello.com/hotels/reservation
java.lang
UUID:550e8400-e29b-41d4-a716-446655440000

These three URI’s are a fully qualified name for a namespace. According to IETF an URI is a case sensitive sequence of characters from a very limited set: the letters of
the basic Latin alphabet, digits, and a few special characters.

Best Practices to Name Your Namespaces

The best practices state that your namespaces should provide information about the owner of the XML, the most frequently used names are:

1. A unique name to identify your XML, this is not so common in the real world but is useful for tests, like ORDERS_XML.
2. The name of an organization or product, like Sunset-Hotels.
3. The domain name of an organization or company, this is the most widely used name, it’s simple and very descriptive, like com.ibm.xml, http://www.opentravel.org/OTA/2003/05/common

The last kind of URI is usually the best because you can describe a component in a hierarchical order, lets go back to the example https://marcotello.com/hotels/reservation as you can see here that reservation belongs to hotels and hotels belong to the domain or the organization, and this an easy way to have an order of the elements that you are representing.

The prefix that refers to your namespace in the document could be anything you like, some parsers don’t allow special characters so the best way is just to choose 3 letters like res. The keywords xmlns and xml are not allowed as prefixes.

A prefix is linked to the namespace with the namespace binding xmlns:prefix=”URI” like in the example xmlns:res=”https://marcotello.com/hotel/reservation” res is linked to https://marcotello.com/hotel/reservation namespace and you can use the prefix in your elements to distinguish as part of it.

03-09-2012

Could be read like this:

{https://marcotello.com/hotel/reservation} arrivingdate

I’m going to list all the best practices for the DeveloperWorks article Plan to use XML namespaces written by the XML expert David Marston, which in my opinion is the most complete guide of namespaces best practices:

Planning your namespaces

• Establish logical and consistent prefix names to boost developer productivity.
• Use prefixes everywhere or at least use them on all items except those that are the real content being delivered to the end user.
• Apply namespaces to your own vocabulary, even when there is just one.
• Treat namespaces as a way to separate or isolate terms that may otherwise seem similar.
• When designing two vocabularies that have some elements in common, choose one namespace (possibly separate from the original two) to hold the common items.
• Use HTTP URLs for your URIs, without fragment identifiers.
• Coordinate URI naming under your domain name just as you do for names of machines on your network and your Web URLs.
• Change the namespace URI for every substantive change to the vocabulary, including the addition of new elements forming a strict superset of the old vocabulary.

Usage inside XML documents

• If possible, use one prefix for one namespace throughout all XML documents in a system.
• Declare namespaces explicitly within each document, reducing assumptions and dependencies.
• Make all namespace declarations up in the start tag of the document element if at all possible.
• For W3C-defined elements and attributes, use the prefixes that the W3C uses.
• Use the xml:lang attribute to declare that the content of the element is in a particular natural language.

Documentation and conversational usage

• Refer to a “namespace declaration” as distinct from an “attribute” when discussing entries in a start tag.
• Avoid the term “namespace name” or only use it in a context where it’s clear what you mean.
• Use the domain names example.com, example.net, or example.org for examples in your documentation.

Following some of these best practices to merge our XML documents, we’ll get something like this:

<res:reservation id="123456789" xmlns:res=”https://marcotello.com/hotel/reservation” 
xmlns:rs=”https://marcotello.com/hotel”>
     <res:arrivingdate>03-09-2012</res:arrivingdate>
     <res:departuredate>03-15-2012</res:departuredate>
     <res:guestname>Fred</res:guestname>
     <res:guestlastname>Davis</res:guestlastname>
     <res:hotelid>03</res:hotelid>
     <res:room>1001</res:room>
     <res:oceanview>true</res:oceanview>
     <res:smokingarea>false</res:smokingarea>
     <rs:roomService>
          <rs:hotelid>SUNSET-3</rs:hotelid>
          <rs:room>1001</rs:room>
          <rs:guest>
               <rs:name>Fred</rs:name>
               <rs:lastName>Davis</rs:lastName>
          </rs:guest>
          <rs:order>
              <rs:item>Cheese Burger</rs:item>
              <rs:id>203</rs:id>
              <rs:price>10.99</rs:price>
              <rs:quantity>1</rs:quantity>
          </rs:order>
     </rs:roomService>
</res:reservation>

As you can see namespaces are so important in XML documents because they can avoid collisions between elements with the same name, and also make it possible to catalog information across the enterprise, so next time you have to build an XML consider including a namespace in your root node.

Resources:

• http://www.ibm.com/developerworks/library/x-nmspace2.html
• http://www.ibm.com/developerworks/xml/library/x-nmspace/index.html
• http://www.w3.org/XML/

Before we can start first you have to configure the UMS to work with Gmail in the SOA Infra, follow the instructions here.

These are the steps that we will follow to process an email through the UMS Adapter.

1. Create a new Project in JDeveloper.
2. Configure the UMS to Send an Email.
3. Poll a Gmail Account.
4. Add text to the message in BPEL.

1.- Create a new Project in JDeveloper.

Open JDeveloper and create a new generic application – call it SOA_Projects

Follow the wizard and call your project UMSTest and don’t forget to select SOA as the default project technology

At the end select an Empty Composite and you’re done.

2.- Configure the UMS to Send an Email.

Drag and drop an UMS Adapter to the External References section.

Follow the wizard and set the following values:

3.- Poll a Gmail Account.

Drag and drop an UMS Adapter to the Exposed Services section.

Follow the wizard and set the following values:

4.- Add text to the message in BPEL.

Drag and drop a BPEL Process Component to the Components section.

Fill in the popup with the default Name and Namespace, select Asynchronous BPEL Process and uncheck Expose as a SOAP service, leave the Input and Output with the default variables.

Connect the EmailReceiver Reference to BPELProcess1 Service in a different Service than the default.

then connect BPELProcess1 Reference to EmailSender Service.

Open BPELProcess1 and delete the Request and the Response Partner Links Connections.

Then delete the BPELProcess1 Partner Link.

Connect the receiveInput Activity to EmailReceiver Partner Link and when the Edit Receive Popup appears leave the default values.

Connect the callbackClient Activity to EmailSender and leave the default values in the Edit Invoke Popup.

Edit inputVariable and click in the magnifying glass of the Message Type, select Message Types > Partner Links > EmailReceiver > EmailReceiver.wsdl > Message Types > ReceiveNotification_msg in the Type Chooser Popup.

And now edit outputVariable and click in the magnifying glass of the Message Type, select Message Types > Partner Links > EmailSender > EmailSender.wsdl > Message Types > SendNotification_msg in the Type Chooser Popup.

Add a new variable and call it emailText

Then drag and drop an Assign Activity and call it payloadAssign.

In the Assign Activity Popup right click in the Drag objects here section in the center and select Expression.

Create an expression like this concat(bpws:getVariableData(‘inputVariable’,’body’,’/ns3:message/ns3:payload’), ‘ Some text added by BPEL’)  to add some text at the end of the message. Notice that if you want to extract, evaluate or add text n a different position you may want to use a

Drag a line from the expression to Variables/Process/Variables/outputVariable/body/ns4:message/ns4:payload, with this you are assigning the Email’s body from the original email and the added text to the new email that the UMS Adapter is going to send. Click OK and you are ready to deploy.

Deploy your application and send an email to your incoming email account, you will receive the same email in the outgoing account with the added text.
You can find the project in Github here.
Here is the jar file of the project

If you found this useful please drop me a comment.

These are the steps that we will follow to configure the UMS Adapter:

1. Get Gmail SSL certificates.
2. Import the certificates into Weblogic’s default Keystore.
3. Send a test email.
4. Configure Email Driver
5. Important Notes
6. Common Exceptions

1.- Get Gmail SSL certificates.

Before configuring anything in the SOA Suite we have to get the Gmail SSL certificate first, to do that we need Open-SSL installed in our system, if you are running Linux you can run the following commands:

UBUNTU

#sudo apt-get install openssl

RHEL/CENTOS

#yum install openssl

WINDOWS

Download the full package from OpenSSL for Win32 and install it.
Once you have Open-SSL installed, store the certificates in your local machine. Run the following command:

#openssl s_client -connect imap.gmail.com:993

That will connect you to gmail imap service and in the trace printed you’ll find the certificate. Copy all the lines between:

-----BEGIN CERTIFICATE-----
...
-----END CERTIFICATE-----

Paste them in notepad and save everything in a file named gmail-imap.cert

Do the same to get the smtp certificate running the following command.

#openssl s_client -connect smtp.gmail.com:465

Copy all the lines between BEGIN CERTIFICATE and END CERTIFICATE and save it in a file named gmail-smtp.cert

2.- Import the certificates into Weblogic’s default Keystore.

To import the certificates we will use the default Java tool named Keytool, just run the following commands:

#keytool -import -alias gmail-imap -keystore [ORACLE_HOME]/wlserver_10.3/server/lib/DemoTrust.jks -file gmail-imap.cert

The password for DemoTrust.jsk Keystore is DemoTrustKeyStorePassPhrase

Also you need to import the Gmail SMTP certificate, run the following command:

#keytool -import -alias gmail-smtp -keystore [ORACLE_HOME]/wlserver_10.3/server/lib/DemoTrust.jks -file gmail-smtp.cert

Note that for development purposes we are using the Weblogic’s default keystore but in production you might want to use a custom keystore with your own password and passphrase.

And that’s all, check if the certificates are listed in the keystore.

#keytool -list -keystore  [ORACLE_HOME]/wlserver_10.3/server/lib/DemoTrust.jks

You will see gmail-imap and gmail-smtp listed.

3.- Send a test email.

To ensure that the certificates have been imported correctly send a test email, to do that we have to configure the Workflow Notification Properties in the SOA Infra.

Right click on soa-infra then go to SOA Administration > Workflow Notification Properties

Select  email as the Notification Mode and in the Notification Service section, configure the following email addresses:

• Email From Address: The email address from which you want to send email notifications.
• Email Actionable Address: The email address for actionable incoming messages. This is not required.
• Email Reply To Address: The email address to include in the Reply To field of the outgoing email notification header.

Click Apply to save the changes and re start SOA server.

Once the server starts again right click on  soa-infra then go to Service Engines > Human Workflow

Then open the Notification Management Tab

and click on the “Send Test Notification” button at your right hand, you will prompt with this popup

 Fill the fields in with the following information:

• Send to: some_email_to_test@email.com
• Channel: email
• Subject: Test
• Content: the email’s body.

Click the Send button and wait to get a SENT notification, if everything goes well you will receive an email from the outgoing email account that you configured before.

4.- Configure Email Driver

This is the most important step in the configuration so pay attention, you can commit many errors by configuring wrong the driver.

Go to User Messaging Service and right click on usermessagingdriver-email then go to Email Driver Properties

Then go to Email Driver Properties and set up the next configuration:

Click Apply to save the changes, re start SOA server and that’s it, now you have the UMS Adapter up and running for use in your SOA projects.

5.- Important Notes

In this section we will review some important notes that you will have to consider.

Where to find the Email Driver Configuration XML File

The driver configuration is very sensitive and a bad configuration could stop SOA Server from starting up, so if you are in that situation you still can make corrections to your configuration, go to [Oracle_Home]/Middleware/user_projects/domains/soa_domain/config/fmwconfig/servers/
soa_server1/applications/usermessagingdriver-email/configuration and you will find a file named driverconfig.xml which holds all the drivers properties.

Cleartext Password usage

You might want to use cleartext password for development purposes but for production I strongly recommend to use an indirect password, remember that cleartext password is stored in an XML file and its anyone could read the file.

6.- Common Exceptions

In this section we will cover the common exceptions that you could face.

Could not initialize Email Store

'
<Nov 20, 2013 2:12:03 PM COT> <Error> <oracle.sdp.messaging.driver.email> <SDP-2
6123> <Could not initialize Email Store for user account@yourdomain.com >
<Nov 20, 2013 2:12:03 PM COT> <Error> <oracle.sdp.messaging.driver.email> <SDP-2
5700> <An unexpected exception was caught.
javax.mail.MessagingException: sun.security.validator.ValidatorException: PKIX p
ath building failed: sun.security.provider.certpath.SunCertPathBuilderException:
 unable to find valid certification path to requested target;
  nested exception is:
        javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorExc
eption: PKIX path building failed: sun.security.provider.certpath.SunCertPathBui
lderException: unable to find valid certification path to requested target
        at com.sun.mail.imap.IMAPStore.protocolConnect(IMAPStore.java:571)
        at javax.mail.Service.connect(Service.java:288)
        at javax.mail.Service.connect(Service.java:169)
        at oracle.sdpinternal.messaging.driver.email.ImapEmailStore.initStore(Im
apEmailStore.java:183)
'

This exception is related to the SMPT or IMAP certificates, you will have to erase them from the keystore and re import again, Gmail changes their certificates almost every year so you will have to import the certificates again.

Could not connect to SMTP host 

'
<25-nov-2013 23H23 COT> <Error> <oracle.sdp.messaging.driver.email> <SDP-25700>
 <An unexpected exception was caught.
javax.mail.MessagingException: Could not connect to SMTP host: localhost, port:
25;
  nested exception is:
        java.net.ConnectException: Connection refused: connect
        at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:1391)
        at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:41
2)
        at javax.mail.Service.connect(Service.java:288)
        at javax.mail.Service.connect(Service.java:169)
        at javax.mail.Service.connect(Service.java:118)
        at oracle.sdpinternal.messaging.driver.email.EmailDriver.send(EmailDrive
r.java:774)
'

When this exception is thrown, it means that the server is not reaching Gmail’s SMTP, it could be a closed port or a firewall that is blocking communication.

Invalid credentials

'
<An unexpected exception was caught.
javax.mail.AuthenticationFailedException: [AUTHENTICATIONFAILED] Invalid credent
ials (Failure)
        at com.sun.mail.imap.IMAPStore.protocolConnect(IMAPStore.java:566)
        at javax.mail.Service.connect(Service.java:288)
        at javax.mail.Service.connect(Service.java:169)
        at oracle.sdpinternal.messaging.driver.email.ImapEmailStore.initStore(Im
apEmailStore.java:183)
        at oracle.sdpinternal.messaging.driver.email.ImapEmailStore.initStore(Im
apEmailStore.java:132)
        at oracle.sdpinternal.messaging.driver.email.EmailResourceAdapter.create
EmailStore(EmailResourceAdapter.java:1290)
        at oracle.sdpinternal.messaging.driver.email.MailboxPollingWorker.getIni
tializedEmailStore(MailboxPollingWorker.java:104)
        at oracle.sdpinternal.messaging.driver.email.MailboxPollingWorker.run(Ma
ilboxPollingWorker.java:47)'

Check the user or password and re start the server.

IMAP Read timed out

'
<Nov 20, 2013 4:25:20 PM COT> <Error> <oracle.sdp.messaging.driver.email> <SDP-2
6123> <Could not initialize Email Store for imap-account@yourdomain.com >
<Nov 20, 2013 4:25:20 PM COT> <Error> <oracle.sdp.messaging.driver.email> <SDP-2
5700> <An unexpected exception was caught.
javax.mail.MessagingException: Read timed out;
  nested exception is:
        java.net.SocketTimeoutException: Read timed out
        at com.sun.mail.imap.IMAPStore.protocolConnect(IMAPStore.java:571)
        at javax.mail.Service.connect(Service.java:288)
        at javax.mail.Service.connect(Service.java:169)
        at oracle.sdpinternal.messaging.driver.email.ImapEmailStore.initStore(Im
apEmailStore.java:183)
'

To solve this try to enter the IMAP account credentials again and re start the server.

7.- References

http://docs.oracle.com/cd/E28280_01/user.1111/e23486/hcfp_notifications.htm

http://docs.oracle.com/cd/E23943_01/core.1111/e12037/managing.htm#WCEDG392

In this tutorial we’ll extend Bugzilla with Testopia extension.

1.- Prerequisites.

• Basic Knowledge of Linux Shell Commands.
• Bugzilla properly installed in your system. You can follow this tutorial to install Bugzilla here.
• Download the latest version of Testopia here.

2.- Pre Installation Activities.

Copy testopia-2.5-BUGZILLA-4.2.tar.gz to Bugzilla’s directory:

#cp testopia-2.5-BUGZILLA-4.2.tar.gz /var/www/html/bugzilla/

Untar the testopia-2.5-BUGZILLA-4.2.tar.gz file:

#tar xzvf testopia-2.5-BUGZILLA-4.2.tar.gz

Verify that extensions/Testopia/ directory was created:

# ls -l extensions/Testopia/
total 984
-rw-r----- 1 root apache 87959 May 28 2012 ChangeLog
-rw-r----- 1 root apache 1110 May 28 2012 Config.pm
drwxr-x--- 3 root apache 4096 May 28 2012 contrib
drwxr-x--- 2 root apache 4096 May 28 2012 css
drwxr-x--- 4 root apache 4096 May 28 2012 doc
-rw-r----- 1 root apache 318 May 28 2012 environment.dtd
-rw-r----- 1 root apache 94940 May 28 2012 Extension.pm
drwxr-x--- 10 root apache 4096 Oct 1 2010 extjs
drwxr-x--- 2 root apache 4096 May 28 2012 img
-rw-r----- 1 root apache 1838 May 28 2012 import_example.csv
drwxr-x--- 2 root apache 4096 May 28 2012 js
drwxr-x--- 4 root apache 4096 May 28 2012 lib
-rw-r----- 1 root apache 9359 May 28 2012 README
-rwxr-x--- 1 root apache 1139 May 28 2012 run_unit_tests.pl
drwxr-x--- 4 root apache 4096 May 28 2012 t
drwxr-x--- 3 root apache 4096 May 28 2012 template
-rw-r----- 1 root apache 418766 May 28 2012 testopia.all.js
-rw-r----- 1 root apache 206950 May 28 2012 testopia.all.ycomp.js
-rw-r----- 1 root apache 10954 May 28 2012 testopia.xsd
-rwxr-x--- 1 root apache 2063 May 28 2012 testrunner.pl
drwxr-x--- 2 root apache 4096 May 28 2012 tools

#

3.- First try to Install Testopia.

Run the  ./checksetup.pl command to install Testopia:

# ./checksetup.pl
* This is Bugzilla 4.2.4 on perl 5.8.8
* Running on Linux 2.6.18-308.24.1.el5 #1 SMP Tue Dec 4 17:42:30 EST 2012

Checking perl modules...
Checking for CGI.pm (v3.51) ok: found v3.62
Checking for Digest-SHA (any) ok: found v5.80
Checking for TimeDate (v2.21) ok: found v2.24
Checking for DateTime (v0.28) ok: found v0.78
Checking for DateTime-TimeZone (v0.71) ok: found v1.56
Checking for DBI (v1.41) ok: found v1.623
Checking for Template-Toolkit (v2.22) ok: found v2.24
Return::Value is deprecated at lib/Return/Value.pm line 13
require Return/Value.pm called at lib/Email/Send.pm line 11
Email::Send::BEGIN() called at lib/Return/Value.pm line 0
eval {...} called at lib/Return/Value.pm line 0
require Email/Send.pm called at (eval 95) line 1
eval 'require Email::Send;' called at Bugzilla/Install/Requirements.pm line 668
Bugzilla::Install::Requirements::have_vers('HASH(0x8d25ec4)', 1) called at Bugzilla/Install/Requirements.pm line 445
Bugzilla::Install::Requirements::_check_missing('ARRAY(0x8ce3264)', 1) called at Bugzilla/Install/Requirements.pm line 409
Bugzilla::Install::Requirements::check_requirements(1) called at ./checksetup.pl line 86
Checking for Email-Send (v2.00) ok: found v2.198
Checking for Email-MIME (v1.904) ok: found v1.911
Checking for URI (v1.37) ok: found v1.60
Checking for List-MoreUtils (v0.22) ok: found v0.33
Checking for Math-Random-ISAAC (v1.0.1) ok: found v1.004
Checking for JSON (v2.10) ok: found v2.53
Checking for Text-Diff (v0.35) not found
Checking for GD-Graph3d (v0.63) not found

Checking available perl DBD modules...
Checking for DBD-Pg (v1.45) not found
Checking for DBD-mysql (v4.001) ok: found v4.022
Checking for DBD-SQLite (v1.29) ok: found v1.37
Checking for DBD-Oracle (v1.19) not found

The following Perl modules are optional:
Checking for GD (v1.20) ok: found v2.46
Checking for Chart (v2.1) ok: found v2.4.6
Checking for Template-GD (any) ok: found v1.56
Checking for GDTextUtil (any) ok: found v0.86
Checking for GDGraph (any) ok: found v1.44
Checking for MIME-tools (v5.406) ok: found v5.503
Checking for libwww-perl (any) ok: found v6.04
Checking for XML-Twig (any) ok: found v3.26
Checking for PatchReader (v0.9.6) ok: found v0.9.6
Checking for perl-ldap (any) ok: found v0.52
Checking for Authen-SASL (any) ok: found v2.16
Checking for RadiusPerl (any) ok: found v0.22
Checking for SOAP-Lite (v0.712) ok: found v0.715
Checking for JSON-RPC (any) ok: found v1.03
Checking for JSON-XS (v2.0) ok: found v2.33
Checking for Test-Taint (any) ok: found v1.06
Checking for HTML-Parser (v3.40) ok: found v3.55
Checking for HTML-Scrubber (any) ok: found v0.09
Checking for Encode (v2.21) ok: found v2.47
Checking for Encode-Detect (any) ok: found v1.00
Checking for Email-MIME-Attachment-Stripper (any) ok: found v1.316
Checking for Email-Reply (any) ok: found v1.202
Checking for TheSchwartz (any) ok: found v1.10
Subroutine File::Slurp::O_RDWR redefined at lib/File/Slurp.pm line 11
Subroutine File::Slurp::O_CREAT redefined at lib/File/Slurp.pm line 11
Subroutine File::Slurp::O_EXCL redefined at lib/File/Slurp.pm line 11
Checking for Daemon-Generic (any) ok: found v0.82
Checking for mod_perl (v1.999022) ok: found v2.000004
Checking for Apache-SizeLimit (v0.96) ok: found v0.96
Checking for Text-CSV (v1.06) not found
Checking for XML Schema Validator (v1.10) not found
Checking for XML Schema Parser (any) ok: found v1.01
Checking for XML Twig (any) ok: found v3.26
Checking for mod_headers (any) ok
Checking for mod_expires (any) ok
Checking for mod_env (any) ok
***********************************************************************
* REQUIRED MODULES *
***********************************************************************
* Bugzilla requires you to install some Perl modules which are either *
* missing from your system, or the version on your system is too old. *
* See below for commands to install these modules. *
***********************************************************************
* OPTIONAL MODULES *
***********************************************************************
* Certain Perl modules are not required by Bugzilla, but by *
* installing the latest version you gain access to additional *
* features. *
* *
* The optional modules you do not have installed are listed below, *
* with the name of the feature they enable. Below that table are the *
* commands to install each module. *
***********************************************************************
* MODULE NAME * ENABLES FEATURE(S) *
***********************************************************************
* Text-CSV * CSV Importing of test cases *
* XML Schema Validator * XML Importing of test cases and plans *
***********************************************************************
COMMANDS TO INSTALL OPTIONAL MODULES:

Text-CSV: /usr/bin/perl install-module.pl Text::CSV
XML Schema Validator: /usr/bin/perl install-module.pl XML::Validator::Schema

COMMANDS TO INSTALL REQUIRED MODULES (You *must* run all these commands
and then re-run checksetup.pl):

/usr/bin/perl install-module.pl Text::Diff
/usr/bin/perl install-module.pl GD::Graph3d

To attempt an automatic install of every required and optional module
with one command, do:

/usr/bin/perl install-module.pl --all

*** Installation aborted. Read the messages above. ***

As you can see there some Perl dependencies that we need to install first, so lets do it.

4.- Install Perl Dependencies

Test::Diff.

To Install Test::Diff run the following command:

#/usr/bin/perl install-module.pl Text::Diff

GD::Graph3d.

To Install GD::Graph3d run the following command:

#/usr/bin/perl install-module.pl GD::Graph3d

Text::CSV.

To Install Text::CSV run the following command:

#/usr/bin/perl install-module.pl Text::CSV

XML::Validator::Schema.

To Install XML::Validator::Schema run the following command:

#/usr/bin/perl install-module.pl XML::Validator::Schema

5.- Second Try to Install Testopia.

At this time we have all the Perl missing libraries that we need to install Testopia, so run the ./checksetup.pl again:

#./checksetup.pl

checksetup.pl complete.

#

Voilà! Your Testopia installation is complete, as simple as that.

6.- Restart Apache

Restart Apache to reflect the changes.

#service httpd restart

7.- Test Testopia Installation

Go to http://localhost/bugzilla/ in your browser to the Bugzilla’s home page.

At first you may not see any changes but once you are logged in, you’ll see a new toolbar with the Testopia functionality.

Enjoy!

In this tutorial we’ll install Bugzilla in CentOS 5.

1.- Prerequisites.

• Basic Knowledge of Linux Shell Commands.
• Download latest version of Bugzilla. You can download it here.

2.- Install Perl.

Before installing Perl, check if it’s already installed with the following command.

#perl -v

If you see the following output Perl is properly installed in your machine.

This is perl, v5.8.8 built for i386-linux-thread-multi

Copyright 1987-2006, Larry Wall

Perl may be copied only under the terms of either the Artistic License or the
GNU General Public License, which may be found in the Perl 5 source kit.

Complete documentation for Perl, including FAQ lists, should be found on
this system using "man perl" or "perldoc perl". If you have access to the
Internet, point your browser at http://www.perl.org/, the Perl Home Page.

Otherwise you have to install Perl running this command:

#yum install perl

3.- Install MySQL.

Maybe you want to install MySQL as Yum Group Installation to get all the available packages including the server, the client, python and perl libraries. First run the following command to check the availability:

#yum grouplist | grep -i mysql
   MySQL Database

Then run this command to check what is inside the “MySQL Database” Bundle:

#yum groupinfo "MySQL Database"

Loaded plugins: fastestmirror, security
Setting up Group Process
Loading mirror speeds from cached hostfile
* base: mirror.nsc.liu.se
* extras: mirror.nsc.liu.se
* updates: centosx4.centos.org

Group: MySQL Database
Description: This package group contains packages useful for use with MySQL.
Mandatory Packages:
mysql
Default Packages:
MySQL-python
libdbi-dbd-mysql
mysql-connector-odbc
mysql-server
perl-DBD-MySQL
unixODBC
Optional Packages:
mod_auth_mysql
mysql-bench
mysql-connector-odbc64
mysql-devel
php-mysql
qt-MySQL

As you can see, this bundle installs all additional packages that maybe you will want to add in the future. (If you want to restrict the installation to just certain packages, this list is useful too).

Install “MySQL Database” Bundle

#yum groupinstall "MySQL Database"

Start the MySQL Service.

#service mysqld start

Change the root password.

#mysql -u root

Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 4
Server version: 5.0.95 Source distribution

Copyright (c) 2000, 2011, Oracle and/or its affiliates. All rights reserved.

Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

mysql> select host, user from mysql.user;
+-----------------------+------+
| host | user |
+-----------------------+------+
| 127.0.0.1 | root | 
| localhost | | 
| localhost | root | 
| localhost.localdomain | | 
| localhost.localdomain | root | 
+-----------------------+------+
5 rows in set (0.00 sec)

mysql> set password for 'root'@'localhost' = PASSWORD('your_password_here');
Query OK, 0 rows affected (0.00 sec)

mysql> set password for 'root'@'127.0.0.1' = PASSWORD('your_password_here');
Query OK, 0 rows affected (0.00 sec)

4.- MySQL post installation activities.

Once you have MySQL installed, you need to do the next steps that are listed in the Bugzilla’s documentation to avoid errors in runtime.

Update /etc/my.cnf file with the following lines in the [mysqld] section:

max_allowed_packet=4M
ft_min_word_len=2

Create a database and its user named bugs as follows:

mysql -u root -p
mysql>create database bugs;
mysql>grant all privileges on bugs.* to bugs@localhost identified by 'bugs_password';
mysql> flush privileges;

Restart MySQL service:

#service mysqld restart

5.- Install Apache.

To install Apache you just have to run the following command as root:

#yum install httpd mod_ssl

This will install Apache in its latest version with SSL suppport.

6.- Check dependencies before installing Bugzilla.

Copy Bugzilla tar file to /var/www/html/ directory.

#cp bugzilla-4.2.4.tar.gz /var/www/html/

Extract the bugzilla-4.2.4.tar.gz file

#tar xvfz bugzilla-4.2.4.tar.gz

Run the bugzilla checksetup.pl command to check if the required and optional modules are available.

# cd bugzilla-4.2.4
# ./checksetup.pl --check-modules
* This is Bugzilla 4.2.4 on perl 5.8.8
* Running on Linux 2.6.18-308.24.1.el5 #1 SMP Tue Dec 4 17:42:30 EST 2012

Checking perl modules...
Checking for CGI.pm (v3.51) ok: found v3.62
Checking for Digest-SHA (any) not found
Checking for TimeDate (v2.21) not found
Checking for DateTime (v0.28) not found
Checking for DateTime-TimeZone (v0.71) not found
Checking for DBI (v1.41) ok: found v1.52
Checking for Template-Toolkit (v2.22) not found
Checking for Email-Send (v2.00) not found
Checking for Email-MIME (v1.904) not found
Checking for URI (v1.37) found v1.35
Checking for List-MoreUtils (v0.22) not found
Checking for Math-Random-ISAAC (v1.0.1) not found

Checking available perl DBD modules...
Checking for DBD-Pg (v1.45) not found
Checking for DBD-mysql (v4.001) found v3.0007
Checking for DBD-SQLite (v1.29) not found
Checking for DBD-Oracle (v1.19) not found

The following Perl modules are optional:
Checking for GD (v1.20) not found
Checking for Chart (v2.1) not found
Checking for Template-GD (any) not found
Checking for GDTextUtil (any) not found
Checking for GDGraph (any) not found
Checking for MIME-tools (v5.406) not found
Checking for libwww-perl (any) ok: found v2.033
Checking for XML-Twig (any) not found
Checking for PatchReader (v0.9.6) not found
Checking for perl-ldap (any) not found
Checking for Authen-SASL (any) not found
Checking for RadiusPerl (any) not found
Checking for SOAP-Lite (v0.712) not found
Checking for JSON-RPC (any) not found
Checking for JSON-XS (v2.0) not found
Checking for Test-Taint (any) not found
Checking for HTML-Parser (v3.40) ok: found v3.55
Checking for HTML-Scrubber (any) not found
Checking for Encode (v2.21) found v2.12
Checking for Encode-Detect (any) not found
Checking for Email-MIME-Attachment-Stripper (any) not found
Checking for Email-Reply (any) not found
Checking for TheSchwartz (any) not found
Checking for Daemon-Generic (any) not found
Checking for mod_perl (v1.999022) not found
Checking for Apache-SizeLimit (v0.96) not found
Checking for mod_headers (any) ok
Checking for mod_expires (any) ok
Checking for mod_env (any) ok
***********************************************************************
* REQUIRED MODULES *
***********************************************************************
* Bugzilla requires you to install some Perl modules which are either *
* missing from your system, or the version on your system is too old. *
* See below for commands to install these modules. *
***********************************************************************
* DATABASE ACCESS *
***********************************************************************
* In order to access your database, Bugzilla requires that the *
* correct "DBD" module be installed for the database that you are *
* running. See below for the correct command to run to install the *
* appropriate module for your database. *
***********************************************************************
* OPTIONAL MODULES *
***********************************************************************
* Certain Perl modules are not required by Bugzilla, but by *
* installing the latest version you gain access to additional *
* features. *
* *
* The optional modules you do not have installed are listed below, *
* with the name of the feature they enable. Below that table are the *
* commands to install each module. *
***********************************************************************
* MODULE NAME * ENABLES FEATURE(S) *
***********************************************************************
* GD * Graphical Reports, New Charts, Old Charts *
* Chart * New Charts, Old Charts *
* Template-GD * Graphical Reports *
* GDTextUtil * Graphical Reports *
* GDGraph * Graphical Reports *
* MIME-tools * Move Bugs Between Installations *
* XML-Twig * Move Bugs Between Installations, Automatic Update Notifications *
* PatchReader * Patch Viewer *
* perl-ldap * LDAP Authentication *
* Authen-SASL * SMTP Authentication *
* RadiusPerl * RADIUS Authentication *
* SOAP-Lite * XML-RPC Interface *
* JSON-RPC * JSON-RPC Interface *
* JSON-XS * Make JSON-RPC Faster *
* Test-Taint * JSON-RPC Interface, XML-RPC Interface *
* HTML-Scrubber * More HTML in Product/Group Descriptions *
* Encode * Automatic charset detection for text attachments *
* Encode-Detect * Automatic charset detection for text attachments *
* Email-MIME-Attachment-Stripper * Inbound Email *
* Email-Reply * Inbound Email *
* TheSchwartz * Mail Queueing *
* Daemon-Generic * Mail Queueing *
* mod_perl * mod_perl *
* Apache-SizeLimit * mod_perl *
***********************************************************************
COMMANDS TO INSTALL OPTIONAL MODULES:

GD: /usr/bin/perl install-module.pl GD
Chart: /usr/bin/perl install-module.pl Chart::Lines
Template-GD: /usr/bin/perl install-module.pl Template::Plugin::GD::Image
GDTextUtil: /usr/bin/perl install-module.pl GD::Text
GDGraph: /usr/bin/perl install-module.pl GD::Graph
MIME-tools: /usr/bin/perl install-module.pl MIME::Parser
XML-Twig: /usr/bin/perl install-module.pl XML::Twig
PatchReader: /usr/bin/perl install-module.pl PatchReader
perl-ldap: /usr/bin/perl install-module.pl Net::LDAP
Authen-SASL: /usr/bin/perl install-module.pl Authen::SASL
RadiusPerl: /usr/bin/perl install-module.pl Authen::Radius
SOAP-Lite: /usr/bin/perl install-module.pl SOAP::Lite
JSON-RPC: /usr/bin/perl install-module.pl JSON::RPC
JSON-XS: /usr/bin/perl install-module.pl JSON::XS
Test-Taint: /usr/bin/perl install-module.pl Test::Taint
HTML-Scrubber: /usr/bin/perl install-module.pl HTML::Scrubber
Encode: /usr/bin/perl install-module.pl Encode
Encode-Detect: /usr/bin/perl install-module.pl Encode::Detect
Email-MIME-Attachment-Stripper: /usr/bin/perl install-module.pl Email::MIME::Attachment::Stripper
Email-Reply: /usr/bin/perl install-module.pl Email::Reply
TheSchwartz: /usr/bin/perl install-module.pl TheSchwartz
Daemon-Generic: /usr/bin/perl install-module.pl Daemon::Generic
mod_perl: /usr/bin/perl install-module.pl mod_perl2
Apache-SizeLimit: /usr/bin/perl install-module.pl Apache2::SizeLimit

YOU MUST RUN ONE OF THE FOLLOWING COMMANDS (depending on which database
you use):

PostgreSQL: /usr/bin/perl install-module.pl DBD::Pg
MySQL: /usr/bin/perl install-module.pl DBD::mysql
SQLite: /usr/bin/perl install-module.pl DBD::SQLite
Oracle: /usr/bin/perl install-module.pl DBD::Oracle

COMMANDS TO INSTALL REQUIRED MODULES (You *must* run all these commands
and then re-run checksetup.pl):

/usr/bin/perl install-module.pl Digest::SHA
/usr/bin/perl install-module.pl Date::Format
/usr/bin/perl install-module.pl DateTime
/usr/bin/perl install-module.pl DateTime::TimeZone
/usr/bin/perl install-module.pl Template
/usr/bin/perl install-module.pl Email::Send
/usr/bin/perl install-module.pl Email::MIME
/usr/bin/perl install-module.pl URI
/usr/bin/perl install-module.pl List::MoreUtils
/usr/bin/perl install-module.pl Math::Random::ISAAC

To attempt an automatic install of every required and optional module
with one command, do:

/usr/bin/perl install-module.pl --all

*** Installation aborted. Read the messages above. ***

#
#

As you can see there are many libraries that are not installed, so don’t be scared and execute the following command:

# /usr/bin/perl install-module.pl --all

After waiting for a while you may want to run bugzilla checksetup.pl command again to check if all the libraries have been installed.

# ./checksetup.pl --check-modules
* This is Bugzilla 4.2.4 on perl 5.8.8
* Running on Linux 2.6.18-308.24.1.el5 #1 SMP Tue Dec 4 17:42:30 EST 2012

Checking perl modules...
Checking for CGI.pm (v3.51) ok: found v3.62
Checking for Digest-SHA (any) ok: found v5.80
Checking for TimeDate (v2.21) ok: found v2.24
Checking for DateTime (v0.28) ok: found v0.78
Checking for DateTime-TimeZone (v0.71) ok: found v1.56
Checking for DBI (v1.41) ok: found v1.623
Checking for Template-Toolkit (v2.22) ok: found v2.24
Return::Value is deprecated at lib/Return/Value.pm line 13
require Return/Value.pm called at lib/Email/Send.pm line 11
Email::Send::BEGIN() called at lib/Return/Value.pm line 0
eval {...} called at lib/Return/Value.pm line 0
require Email/Send.pm called at (eval 70) line 1
eval 'require Email::Send;' called at Bugzilla/Install/Requirements.pm line 668
Bugzilla::Install::Requirements::have_vers('HASH(0xa4f2310)', 1) called at Bugzilla/Install/Requirements.pm line 445
Bugzilla::Install::Requirements::_check_missing('ARRAY(0xa4c3d48)', 1) called at Bugzilla/Install/Requirements.pm line 409
Bugzilla::Install::Requirements::check_requirements(1) called at ./checksetup.pl line 86
Checking for Email-Send (v2.00) ok: found v2.198
Checking for Email-MIME (v1.904) ok: found v1.911
Checking for URI (v1.37) ok: found v1.60
Checking for List-MoreUtils (v0.22) ok: found v0.33
Checking for Math-Random-ISAAC (v1.0.1) ok: found v1.004

Checking available perl DBD modules...
Checking for DBD-Pg (v1.45) not found
Checking for DBD-mysql (v4.001) found v3.0007
Checking for DBD-SQLite (v1.29) ok: found v1.37
Checking for DBD-Oracle (v1.19) not found

The following Perl modules are optional:
Checking for GD (v1.20) not found
Checking for Chart (v2.1) not found
Checking for Template-GD (any) not found
Checking for GDTextUtil (any) not found
Checking for GDGraph (any) not found
Checking for MIME-tools (v5.406) ok: found v5.503
Checking for libwww-perl (any) ok: found v6.04
Checking for XML-Twig (any) not found
Checking for PatchReader (v0.9.6) ok: found v0.9.6
Checking for perl-ldap (any) ok: found v0.52
Checking for Authen-SASL (any) ok: found v2.16
Checking for RadiusPerl (any) ok: found v0.22
Checking for SOAP-Lite (v0.712) ok: found v0.715
Checking for JSON-RPC (any) ok: found v1.03
Checking for JSON-XS (v2.0) ok: found v2.33
Checking for Test-Taint (any) ok: found v1.06
Checking for HTML-Parser (v3.40) ok: found v3.55
Checking for HTML-Scrubber (any) ok: found v0.09
Checking for Encode (v2.21) ok: found v2.47
Checking for Encode-Detect (any) not found
Checking for Email-MIME-Attachment-Stripper (any) ok: found v1.316
Checking for Email-Reply (any) ok: found v1.202
Checking for TheSchwartz (any) ok: found v1.10
Subroutine File::Slurp::O_RDWR redefined at lib/File/Slurp.pm line 11
Subroutine File::Slurp::O_CREAT redefined at lib/File/Slurp.pm line 11
Subroutine File::Slurp::O_EXCL redefined at lib/File/Slurp.pm line 11
Checking for Daemon-Generic (any) ok: found v0.82
Checking for mod_perl (v1.999022) not found
Checking for Apache-SizeLimit (v0.96) not found
Checking for mod_headers (any) ok
Checking for mod_expires (any) ok
Checking for mod_env (any) ok
***********************************************************************
* OPTIONAL MODULES *
***********************************************************************
* Certain Perl modules are not required by Bugzilla, but by *
* installing the latest version you gain access to additional *
* features. *
* *
* The optional modules you do not have installed are listed below, *
* with the name of the feature they enable. Below that table are the *
* commands to install each module. *
***********************************************************************
* MODULE NAME * ENABLES FEATURE(S) *
***********************************************************************
* GD * Graphical Reports, New Charts, Old Charts *
* Chart * New Charts, Old Charts *
* Template-GD * Graphical Reports *
* GDTextUtil * Graphical Reports *
* GDGraph * Graphical Reports *
* XML-Twig * Move Bugs Between Installations, Automatic Update Notifications *
* Encode-Detect * Automatic charset detection for text attachments *
* mod_perl * mod_perl *
* Apache-SizeLimit * mod_perl *
***********************************************************************
COMMANDS TO INSTALL OPTIONAL MODULES:

GD: /usr/bin/perl install-module.pl GD
Chart: /usr/bin/perl install-module.pl Chart::Lines
Template-GD: /usr/bin/perl install-module.pl Template::Plugin::GD::Image
GDTextUtil: /usr/bin/perl install-module.pl GD::Text
GDGraph: /usr/bin/perl install-module.pl GD::Graph
XML-Twig: /usr/bin/perl install-module.pl XML::Twig
Encode-Detect: /usr/bin/perl install-module.pl Encode::Detect
mod_perl: /usr/bin/perl install-module.pl mod_perl2
Apache-SizeLimit: /usr/bin/perl install-module.pl Apache2::SizeLimit
To attempt an automatic install of every required and optional module
with one command, do:

#/usr/bin/perl install-module.pl --all

#

At this point the command installed all the libraries it could, but there are some libraries that couldn’t be installed because of the dependencies that the libraries might need. So you’ll need to install them one by one before continuing.

At the end of the post I’ve added a Missing Libraries Installation Section to cover those problems.

7.- Check dependencies once again.

If you have all the missing libraries already installed run checksetup.pl again just to be sure everything is OK.

#./checksetup.pl --check-modules

* This is Bugzilla 4.2.4 on perl 5.8.8
* Running on Linux 2.6.18-308.24.1.el5 #1 SMP Tue Dec 4 17:42:30 EST 2012

Checking perl modules...
Checking for CGI.pm (v3.51) ok: found v3.62
Checking for Digest-SHA (any) ok: found v5.80
Checking for TimeDate (v2.21) ok: found v2.24
Checking for DateTime (v0.28) ok: found v0.78
Checking for DateTime-TimeZone (v0.71) ok: found v1.56
Checking for DBI (v1.41) ok: found v1.623
Checking for Template-Toolkit (v2.22) ok: found v2.24
Return::Value is deprecated at lib/Return/Value.pm line 13
require Return/Value.pm called at lib/Email/Send.pm line 11
Email::Send::BEGIN() called at lib/Return/Value.pm line 0
eval {...} called at lib/Return/Value.pm line 0
require Email/Send.pm called at (eval 71) line 1
eval 'require Email::Send;' called at Bugzilla/Install/Requirements.pm line 668
Bugzilla::Install::Requirements::have_vers('HASH(0x9c54198)', 1) called at Bugzilla/Install/Requirements.pm line 445
Bugzilla::Install::Requirements::_check_missing('ARRAY(0x9c27140)', 1) called at Bugzilla/Install/Requirements.pm line 409
Bugzilla::Install::Requirements::check_requirements(1) called at ./checksetup.pl line 86
Checking for Email-Send (v2.00) ok: found v2.198
Checking for Email-MIME (v1.904) ok: found v1.911
Checking for URI (v1.37) ok: found v1.60
Checking for List-MoreUtils (v0.22) ok: found v0.33
Checking for Math-Random-ISAAC (v1.0.1) ok: found v1.004

Checking available perl DBD modules...
Checking for DBD-Pg (v1.45) not found
Checking for DBD-mysql (v4.001) ok: found v4.022
Checking for DBD-SQLite (v1.29) ok: found v1.37
Checking for DBD-Oracle (v1.19) not found

The following Perl modules are optional:
Checking for GD (v1.20) ok: found v2.46
Checking for Chart (v2.1) ok: found v2.4.6
Checking for Template-GD (any) ok: found v1.56
Checking for GDTextUtil (any) ok: found v0.86
Checking for GDGraph (any) ok: found v1.44
Checking for MIME-tools (v5.406) ok: found v5.503
Checking for libwww-perl (any) ok: found v6.04
Checking for XML-Twig (any) ok: found v3.42
Checking for PatchReader (v0.9.6) ok: found v0.9.6
Checking for perl-ldap (any) ok: found v0.52
Checking for Authen-SASL (any) ok: found v2.16
Checking for RadiusPerl (any) ok: found v0.22
Checking for SOAP-Lite (v0.712) ok: found v0.715
Checking for JSON-RPC (any) ok: found v1.03
Checking for JSON-XS (v2.0) ok: found v2.33
Checking for Test-Taint (any) ok: found v1.06
Checking for HTML-Parser (v3.40) ok: found v3.55
Checking for HTML-Scrubber (any) ok: found v0.09
Checking for Encode (v2.21) ok: found v2.47
Checking for Encode-Detect (any) ok: found v1.00
Checking for Email-MIME-Attachment-Stripper (any) ok: found v1.316
Checking for Email-Reply (any) ok: found v1.202
Checking for TheSchwartz (any) ok: found v1.10
Subroutine File::Slurp::O_RDWR redefined at lib/File/Slurp.pm line 11
Subroutine File::Slurp::O_CREAT redefined at lib/File/Slurp.pm line 11
Subroutine File::Slurp::O_EXCL redefined at lib/File/Slurp.pm line 11
Checking for Daemon-Generic (any) ok: found v0.82
Checking for mod_perl (v1.999022) ok: found v2.000004
Checking for Apache-SizeLimit (v0.96) ok: found v0.96
Checking for mod_headers (any) ok
Checking for mod_expires (any) ok
Checking for mod_env (any) ok

8.- Install Bugzilla.

Run ./checksetup.pl once again but this time without any argument to create the ./localconfig file in which we have to change some options to configure MySQL as the DB Server.

#./checksetup.pl

Update ./localconfig file changing the following lines:

$db_driver = 'mysql';
$db_host = 'localhost';
$db_user = 'bugs';
$db_pass = 'your_password';

Then run ./checksetup.pl for the last time, in this occasion the database will be created and the admin user information is requested:

Looks like we don't have an administrator set up yet. Either this is

your first time using Bugzilla, or your administrator's privileges
might have accidentally been deleted.

Enter the e-mail address of the administrator: contact@marcotello.com
Enter the real name of the administrator: Marco Tello
Enter a password for the administrator account:
Please retype the password to verify:
contact@marcotello.com is now set up as an administrator.
Creating initial dummy product 'TestProduct'...

Now that you have installed Bugzilla, you should visit the 'Parameters'
page (linked in the footer of the Administrator account) to ensure it
is set up as you wish - this includes setting the 'urlbase' option to
the correct URL.
checksetup.pl complete.

9.- Bugzilla post installation activities.

Go to /var/www/html directory.

#cd /var/www/html

Delete bugzilla-4.2.4.tar.gz file to save space.

#rm -rf bugzilla-4.2.4.tar.gz

Move bugzilla-4.2.4 directory to a folder called just bugzilla.

#mv bugzilla-4.2.4 bugzilla

Make apache user the owner of bugzilla directory

#chown -R apache:apache bugzilla

Configure MySQL to accept larger attachments in bugs database:

#mysql -u bugs -p
mysql> use bugs
mysql> ALTER TABLE attachments AVG_ROW_LENGTH=1000000, MAX_ROWS=20000;

10.- Configure Apache to run Bugzilla.

Create a file named bugzilla.conf in /etc/httpd/conf.d/ directory with the following content:

<Directory "/var/www/html/bugzilla">
   AddHandler cgi-script .cgi
   Options +Indexes +ExecCGI
   DirectoryIndex index.cgi
   AllowOverride Limit FileInfo Indexes

Restart Apache.

#service httpd restart

11.- Run Bugzilla.

Open a browser and go to http://localhost/bugzilla.

That’s it, Bugzilla is up and running.

12.- Missing Libraries Installation Section.

DBD-mysql (v4.001) is missing

The DBD-mysql (v4.001) is missing

Solution: install mysql-dlevel library.

To set up properly DBD-mysql (v4.001) you need to install mysql-devel first. Run the following command:

#yum install mysql-devel

Once installed run the following command:

#/usr/bin/perl install-module.pl DBD::mysql

Can’t install GD (v1.20).

There’s an option to install GD when we get the following error:

#/usr/bin/perl install-module.pl GD

**UNRECOVERABLE ERROR**
Could not find gdlib-config in the search path. Please install libgd 2.0.28 or higher.
If you want to try to compile anyway, please rerun this script with the option --ignore_missing_gd.

Solution: install gd-level package.

#yum install gd-devel

then run the following command to install GD:

#/usr/bin/perl install-module.pl GD

XML-Twig is missing.

The XML-Twig library is missing. It doesn’t matter how many times you want to run:

#/usr/bin/perl install-module.pl XML::Twig

XML-Twig will not be installed in your system.

Solution: install XML Twig via yum.

Just run the following command:

#yum install perl-XML-Twig

Encode::Detect is missing.

This library is hard to find in the repositories, the best option is to install it manually. You can download the rpm here.

Solution: install manually perl-Encode-Detect rpm.

#rpm -Uvh perl-Encode-Detect-1.00-1.el5.rf.i386.rpm

mod_perl is missing.

mod_per is not installed in your computer.

Solution: install mod_perl via yum.

#yum install mod_perl

Can’t install Apache2::SizeLimit.

When you try to install Apache Size Limit it returns the following error:

#Can't find the mod_perl include dir (reason: path /usr/include/httpd doesn't exist) at /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi/Apache2/Build.pm line 2030.

Solution: create the /usr/include/httpd directory.

#mkdir /usr/include/httpd

#/usr/bin/perl install-module.pl Apache2::SizeLimit

1.- Prerequisites.

• Eclipse IDE.
• Eclipse ADT plugin (Android Development Tools) installed.
• At least one  Android Virtual Device configured.

2.- Create the Android Project.

Select File > New > Android Application Project.

Then fill in the inputs with the following information:

• Application Name: HelloWorld (The name that will be displayed in the phone).
• Project Name: HelloWorld (The name of the project in Eclipse)
• Package Name: com.marco.tello.android (The package where your code will go)
• Minimum Required SDK: API 10: Android 2.3.3 (Gingerbread) (Here you are selecting the minimum version of Android in which your application will run)
• Target SDK: API 16 Android 4.1 (Jelly Bean) (The Target SDK)
• Compile With: API 16 Android 4.1 (Jelly Bean) 
• Theme: Holo light with Dark Action Bar 

Click Next and click Next again leaving the default options. The next screen introduces us the Icon launcher configuration, leave as default and click Next.

In the next screen check Create Activity and choose “Blank Activity” and click Next.

Name your Activity as “HelloAndroid”. The Activity is the default screen your application shows when it’s initialized.

Click Finish and wait for the magic to end.

That’s it, your Hello World App is already created, you only have to run it.

2.- Run the App in a Virtual Device

If you don’t have a Virtual Device configured yet, here are the instructions to configure one.

You need to start your Virtual Device before you run the app. Open Android Virtual Device Manager and click the Start button.

The emulator will start but it doesn’t have your app yet.

To install the app in the Virtual Device emulator you have to select the project in the Package Explorer, right click on it and select Run as > Android application.

And voilá! Your Hello World Application is up and running.

Enjoy!

For this example we’ll use the XSLT transformation described here.

All we need is an input XML like this:

Reservation.xml

<?xml version="1.0" encoding="UTF-8"?>
 
<Reservation>
     <reservation id="123456789" />
     <arrivingDate>03-09-2012</arrivingDate>
     <departureDate>03-15-2012</departureDate>
     <guestName>Fred</guestName>
     <guestLastName>Davis</guestLastName>
     <hotelID>03</hotelID>
     <room>1001</room>
     <oceanView>true</oceanView>
     <smokingArea>false</smokingArea>
</Reservation>

Github

We want to transform it into an output like this:

ReservationInfo.xml

<?xml version="1.0" encoding="UTF-8"?>
 
<ReservationInfo>
     <reservation id="123456789" 
                  arrivalDate="03-09-2012" 
                  departureDate="03-15-2012" />
     <guest>
          <name>Fred</name>
          <lastName>Davis</lastName>
     </guest>
     <room number="1001">
         <oceanView>true</oceanView>
         <smokingArea>false</smokingArea>
     </room>
</ReservationInfo>

It’s the same data with different structure.

To get this, we need to run an XSL transformation in Mule ESB using the XSLT Transformer.

xsltTransformation-config.xml

<?xml version="1.0" encoding="UTF-8"?>

<mule xmlns:file="http://www.mulesoft.org/schema/mule/file" xmlns="http://www.mulesoft.org/schema/mule/core"
	xmlns:http="http://www.mulesoft.org/schema/mule/http" xmlns:mulexml="http://www.mulesoft.org/schema/mule/xml"
	xmlns:ajax="http://www.mulesoft.org/schema/mule/ajax" xmlns:doc="http://www.mulesoft.org/schema/mule/documentation"
	xmlns:spring="http://www.springframework.org/schema/beans" xmlns:core="http://www.mulesoft.org/schema/mule/core"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="CE-3.3.0"
	xsi:schemaLocation="
http://www.mulesoft.org/schema/mule/xml http://www.mulesoft.org/schema/mule/xml/current/mule-xml.xsd 
http://www.mulesoft.org/schema/mule/file http://www.mulesoft.org/schema/mule/file/current/mule-file.xsd 
http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-current.xsd 
http://www.mulesoft.org/schema/mule/core http://www.mulesoft.org/schema/mule/core/current/mule.xsd 
http://www.mulesoft.org/schema/mule/http http://www.mulesoft.org/schema/mule/http/current/mule-http.xsd 
http://www.mulesoft.org/schema/mule/ajax http://www.mulesoft.org/schema/mule/ajax/current/mule-ajax.xsd ">
	<file:connector name="FileConnector" autoDelete="true"
		streaming="false" validateConnections="true" doc:name="File">
		<file:expression-filename-parser />
	</file:connector>
	<flow name="xsltTransformation-configFlow1" doc:name="xsltTransformation-configFlow1">
		<file:inbound-endpoint responseTimeout="10000"
			doc:name="FileInput" connector-ref="FileConnector" path="./file-input-directory">
			<file:filename-wildcard-filter pattern="*.xml" />
		</file:inbound-endpoint>
        <logger message="#[payload]" level="INFO" doc:name="Logger"/>
		<mulexml:xslt-transformer
			maxIdleTransformers="2" maxActiveTransformers="5"
			xsl-file="src/main/resources/xslt/transform.xsl" doc:name="XSLT" />
		<file:outbound-endpoint path="./file-output-directory"
			responseTimeout="10000" doc:name="FileOutput"
			outputPattern="#[function:datestamp]-#[header:originalFilename]" />
	</flow>
</mule>

Github

We need to tell the XSLT Transformer where the XSL transformation is located in our project (line 26).

Transformation.xslt

<?xml version="1.0" encoding="UTF-8"?>
 
<xsl:stylesheet version="1.0"
	xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
	<xsl:output method="xml" indent="yes" />
	<xsl:template match="/">
		<ReservationInfo>
			<reservation>
				<xsl:attribute name="id">
					<xsl:value-of select='Reservation/reservation/@id' />
				</xsl:attribute>
				<xsl:attribute name="arrivalDate">
					<xsl:value-of select='Reservation/arrivingDate' />
				</xsl:attribute>
				<xsl:attribute name="departureDate">
					<xsl:value-of select='Reservation/departureDate' />
				</xsl:attribute> 
			</reservation>
			<guest>
				<name>
					<xsl:value-of select="Reservation/guestName" />
				</name>
				<lastName>
					<xsl:value-of select="Reservation/guestLastName" />
				</lastName>
			</guest>
			<room>
				<xsl:attribute name="number">
					<xsl:value-of select='Reservation/room' />
				</xsl:attribute>
				<oceanView>
					<xsl:value-of select="Reservation/oceanView" />
				</oceanView>
				<smokingArea>
					<xsl:value-of select="Reservation/smokingArea" />
				</smokingArea>
			</room>
			</ReservationInfo>
	</xsl:template>
</xsl:stylesheet>

Github

You might get a warning in Mule’s console, telling you that you are running an XSLT 1.0 in an XSLT 2.0 processor, but its OK, the transformation will work.

You can find the project in Github here.

Here is the source code of the project.

Enjoy!

Prerequisites

I’m assuming that the reader has the following skills:

• XML basic knowledge.
• XPath knowledge.

Basic Transformation

Let’s begin with this XML:
 

Reservation.xml

<?xml version="1.0" encoding="UTF-8"?>
 
<Reservation>
     <reservation id="123456789" />
     <arrivingDate>03-09-2012</arrivingDate>
     <departureDate>03-15-2012</departureDate>
     <guestName>Fred</guestName>
     <guestLastName>Davis</guestLastName>
     <hotelID>03</hotelID>
     <room>1001</room>
     <oceanView>true</oceanView>
     <smokingArea>false</smokingArea>
</Reservation>

And we want to transform it into a different XML, like this:
 

ReservationInfo.xml

<?xml version="1.0" encoding="UTF-8"?>

<ReservationInfo>
     <reservation id="123456789" 
                  arrivalDate="03-09-2012" 
                  departureDate="03-15-2012" />
     <guest>
          <name>Fred</name>
          <lastName>Davis</lastName>
     </guest>
     <room number="1001">
         <oceanView>true</oceanView>
         <smokingArea>false</smokingArea>
     </room>
</ReservationInfo>

 
It’s the same data but in different order. To obtain this result, we need a XSLT transformation like this:
 

Transformation.xslt

<?xml version="1.0" encoding="UTF-8"?>

<xsl:stylesheet version="1.0"
	xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
	<xsl:output method="xml" indent="yes" />
	<xsl:template match="/">
		<ReservationInfo>
			<reservation>
				<xsl:attribute name="id">
					<xsl:value-of select='Reservation/reservation/@id' />
				</xsl:attribute>
				<xsl:attribute name="arrivalDate">
					<xsl:value-of select='Reservation/arrivingDate' />
				</xsl:attribute>
				<xsl:attribute name="departureDate">
					<xsl:value-of select='Reservation/departureDate' />
				</xsl:attribute> 
			</reservation>
			<guest>
				<name>
					<xsl:value-of select="Reservation/guestName" />
				</name>
				<lastName>
					<xsl:value-of select="Reservation/guestLastName" />
				</lastName>
			</guest>
			<room>
				<xsl:attribute name="number">
					<xsl:value-of select='Reservation/room' />
				</xsl:attribute>
				<oceanView>
					<xsl:value-of select="Reservation/oceanView" />
				</oceanView>
				<smokingArea>
					<xsl:value-of select="Reservation/smokingArea" />
				</smokingArea>
			</room>
			</ReservationInfo>
	</xsl:template>
</xsl:stylesheet>

You can notice a few things about the XSLT above:
 

• You have to write your new XML tree and populate it with the values of the old one.
• The tag xsl:value-of select=”” is the basic selector for getting information about a node or attribute.
• If you want to insert an attribute inside a node, follow the steps from line 29 to 31
• To get the value of an attribute, add an @ before the name of the attribute. Look at line 10

 
Cheers!

1.- Prerequisites

1. Eclipse IDE.
2. GAE Eclipse Plugin for Eclipse.
3. A Google App Engine account (to test the app in GAE)

2.- Create the GAE Project

Once you have installed the GAE Plugin for Eclipse, a new icon (a blue “g”) will be shown in the tool bar. Click it and a menu will be displayed.

Select New Web Application Project.

A new wizard appears and you have to put the information about your project.

Make sure that the Use Google Web Toolkit is unchecked, then click Finish.
 

3.-Code your Project

The created project will have this structure:

The structure of the project is like a typical Web project with some extra libraries and a appengine-web.xml , which we will look into later.

As you can see, a Servlet is created. In this Servlet you will put all the logic for the incoming requests that your application will have.

In this example we will return Hello world from GAE , so let’s take a look into the code.

package com.marco.tello;
import java.io.IOException;
import javax.servlet.http.*;

@SuppressWarnings("serial")
public class HelloWorldGAEServlet extends HttpServlet {
	public void doGet(HttpServletRequest req, HttpServletResponse resp) 
           throws IOException {
		
		resp.setContentType("text/plain");
		resp.getWriter().println("Hello world from GAE");
	}
}

4.- Test your Application Local

At this point you can test your application in your local environment. Right click on HelloWorldGAEServlet.java->Run As->Web Application.

You will see the embedded server starting and when the deploy is ready, something like this will show in the Console tab.

Open a browser and go to http://localhost:8888/. The main Google App Engine screen comes up.

If you click on HelloWorldGAE you will see the greeting from the servlet you just modified.

That’s it!

5- Deploy to Google App Engine

For this step you have to create an account in  https://appengine.google.com/ and register you application. Google will only let you register 10 application, so be careful!

Modify the appengine-web.xml with the name of your registered application. In my case it is marcotello-test.

<?xml version="1.0" encoding="utf-8"?>
<appengine-web-app xmlns="http://appengine.google.com/ns/1.0">
  <application>marcotello-test</application>
  <version>1</version>

  <!--
    Allows App Engine to send multiple requests to one instance in parallel:
  -->
  <threadsafe>true</threadsafe>

  <!-- Configure java.util.logging -->
  <system-properties>
    <property name="java.util.logging.config.file" value="WEB-INF/logging.properties"/>
  </system-properties>

  <!--
    HTTP Sessions are disabled by default. To enable HTTP sessions specify:

      <sessions-enabled>true</sessions-enabled>

    It's possible to reduce request latency by configuring your application to
    asynchronously write HTTP session data to the datastore:

      <async-session-persistence enabled="true" />

    With this feature enabled, there is a very small chance your app will see
    stale session data. For details, see
    http://code.google.com/appengine/docs/java/config/appconfig.html#Enabling_Sessions
  -->

</appengine-web-app>

Once you save the changes, click on the g icon in the tool bar and select Deploy to App Engine… 

At this point you will have to log in with your Google account and the deployment will start.

When the deployment is finished, the following message will show up in the Eclipse console:

Deployment completed successfully

 Test the application in the browser with the name of your registered application followed by appspot.com. In my case it’s http://marcotello-test.appspot.com/

Enjoy!

The following example shows how to deploy a HTML 5 page in Mule ESB.

MuleWebsite-config.xml

<?xml version="1.0" encoding="UTF-8"?>

<mule xmlns="http://www.mulesoft.org/schema/mule/core" xmlns:jetty="http://www.mulesoft.org/schema/mule/jetty"
	xmlns:doc="http://www.mulesoft.org/schema/mule/documentation"
	xmlns:spring="http://www.springframework.org/schema/beans" version="CE-3.3.0"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="
http://www.mulesoft.org/schema/mule/jetty http://www.mulesoft.org/schema/mule/jetty/current/mule-jetty.xsd 
http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-current.xsd 
http://www.mulesoft.org/schema/mule/core http://www.mulesoft.org/schema/mule/core/current/mule.xsd ">
	<description> This project presents the Mule Start Page that shows the
		version and the projects deployed in Mule ESB.</description>
	<jetty:connector name="Jetty" doc:name="Jetty"
		doc:description="This is the conector to Jetty server">
		<jetty:webapps port="8093" host="localhost" directory="${app.home}/webapps" />
	</jetty:connector>
</mule>

Github

You can notice 3 important things in line number 16

• The port parameter: this parameter define the port of your website.
• The host parameter: this parameter could be the host name or the IP.
• The directory parameter: in this directory you have to store your website files including WEB-INF directory as usual in all java application servers and servlet containers. The ${app.home} keyword refers to /PROJECT-FOLDER/ directory in Mule ESB standalone and /PROJECT-FOLDER/src/main/app/webapps directory in Mule Studio.

Index.jsp

<%@ page language="java" contentType="text/html; charset=UTF-8" pageEncoding="UTF-8"%>
<!DOCTYPE html>
<html>
	<head>
		<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
		<title>Mule ESB 3.3.0</title>
		<link rel="stylesheet" type="text/css" href="css/style.css" />
		<link rel="shortcut icon" href="img/esb.ico" />
		<!-- Internet Explorer HTML5 enabling code: -->
		<!--[if IE]>
		<script src="http://html5shiv.googlecode.com/svn/trunk/html5.js"></script>

		<style type="text/css">
		.clear {
		zoom: 1;
		display: block;
		}
		</style>

		<![endif]-->
	</head>
	<body>
		<section id="page">
			<!-- Defining the #page section with the section tag -->
			<header>
				<!-- Defining the header section of the page with the appropriate tag -->
				<hgroup id="logo">
					<a href="http://localhost/mule"><img src="img/MuleESB.png" alt="Mule ESB 3.3.0" /></a>
					<h3>Mule ESB 3.3.0 is up and kicking</h3>
				</hgroup>
				<nav class="clear">
					<!-- The nav link semantically marks your main site navigation -->
					<ul>
						<li>
							<a href="http://www.mulesoft.org/" target="_blank">Mule ESB</a>
						</li>
						<li>
							<a href="http://html5.org/" target="_blank">HTML 5</a>
						</li>
						<li>
							<a href="https://marcotello.com/" target="_blank">Marco Tello</a>
						</li>
					</ul>
				</nav>
			</header>
			<section id="articles">
				<article id="article1">
					<h2>What is Mule ESB?</h2>
					<div class="line"></div>
					<div class="articleBody clear">
						<figure>
							<img src="http://localhost:8093/mule/img/home-diagram.png" />
						</figure>
						<p>
							Mule ESB is the SOA key in the application integration development, adding message routing, endpoint virtualization and transformation capabilities. 
						</p>
					</div>
				</article>
			</section>
			<footer>
				<div class="line"></div>
				<p>
					Marco Tello - 2012
				</p>
				<!-- Change the copyright notice
				<a href="#" class="up">Go UP</a>
				<a href="http://tutorialzine.com/2010/02/html5-css3-website-template/" class="by">Template by Tutorialzine</a> 
				<a href="http://www.mulesoft.org/" class="up"><img src="img/mulehead_large.png" height="45" width="45" alt="" /></a> -->
				<a href="http://www.w3.org/html/logo/" class="up">
                 	<img src="http://www.w3.org/html/logo/badge/html5-badge-h-css3-semantics.png" width="116" height="45" alt="HTML5 Powered with CSS3 / Styling, and Semantics" title="HTML5 Powered with CSS3 / Styling, and Semantics">
				</a>
			</footer>
		</section>
		<script src="http://ajax.googleapis.com/ajax/libs/jquery/1.3.2/jquery.min.js"></script>
		<script src="jquery.scrollTo-1.4.2/jquery.scrollTo-min.js"></script>
		<script src="js/script.js"></script>
	</body>
</html>

Github

Notice that is an HTML 5 compliant web page wrapped in an JSP file.

The Mule Studio project source code is here MuleWebsite.zip or you can find the project on Github