I am a little late in writing this series of articles on installing and using Sonar: it was Semana Santa in Spain, a week of holidays and so I wanted to enjoy it for the first time this year. And as the next week has been short but intense, I could not catch up.
Fortunately, we’re done with long articles on Oracle, and as the installation of Sonar is not very complicated – if you take the time to carefully observe every step – I hope to write posts shorter but more frequent. Continue reading
The most recent posts in our series about Installing Sonar were focused on Oracle, and everything you need to know about this database to install a platform dedicated to code analysis with Sonar (and Jenkins, and Tomcat).
At the end of the post about Oracle installation, I told you to note the address of the administration console of Oracle.
Today we will use this console to create an Oracle User that will allow us to have a SONAR schema in our database.
After seeing how to install Oracle and install a Loopback Adapter in order to use Oracle on a laptop or a workstation without a network connection, I will present in this article some tips and tricks very useful when you need to manage the complex database that can be sometimes (or most times) Oracle..
For example, there is nothing more frustrating than having a problem during the installation of Oracle, and not be able to uninstall it. It’s very hard to get rid of it: it is even more difficult to remove it than to install it.
We’ll see also some basic tools and commands to verify that Oracle is working properly.
The last post of our serie ‘Install Sonar’ described the installation and configuration of Oracle.
As it was already long enough, we could not see some tips and tricks that can be useful to verify that Oracle is installed and usable.
If your installation was a on a computer of you company, with a network connection, then your Oracle should already be working correctly.
In fact, Oracle requires an IP address in order to work. And without going into details, if your PC is running on a network, you already have an IP address. If you’re not always – if ever – connected to a corporate network, you will need a local IP address. It is the role of the Loopback Adapter, which simulates a network loop on your computer.
We will discuss in this post how to install a Loopback Adapter needed to use Oracle on a standalone station, such as a laptop for example. Continue reading
Another milestone: 15 000 unique visitors on the blog Qualilogy, 3 months after the last one: 10 000 in one year.
On 26th of february, more than 15 000 people did more than 21 000 visits and have seen more that 38 000 pages.
So, the growth is steady, although the end of the year showed a slowdown due to the holidays, but also to the reorganization of the site that did cause some interruptions. Continue reading
Let’s continue our series of posts on installing SONAR with this article on installing Oracle.
Why Oracle? Why not an Open Source database such as MySQL, widespreadly used?
Simply because, once again, our goal is to allow people without a technical background to install a platform for analyzing application quality with SONAR. And these people often work in companies where Windows and Oracle are mostly used. Continue reading
We have seen how to install a JDK in our environment (Windows 7 Professional Edition), we will now look at how to install Tomcat.
But first, what is Tomcat? As before, I will not go into a detailed description of each tool that we install, you can find all the literature you want on Internet. Continue reading
First post on the installation of a platform to measure the quality of applications with SONAR: the installation of a JDK or Java Development Kit.
But first, a word about our environment.
When you look at the SONAR installation documentation, you can see that it is possible to use it in a lot of different environments and configurations: Windows, AIX, Solaris, Linux, with Maven or Ant (or not), as a Windows service (or not), etc. Continue reading
Everyone knows the famous principle edicted by Tom DeMarco: “You can not control what you cannot measure”. Everyone does of course agree with this sentence. Yet many people who work in software engineering – responsible for projects, managers, stakeholders, and even quality consultants – make decisions in terms of budget, schedule and teams without the necessary measures that could enable them to control their projects.
These people know that a code analysis tool could produce these measures, but they do not have a technical background and they think that such a tool is complex to install and to use, so they will reserve its use to ‘specialists’. Continue reading
We have seen previously SONAR ‘Blockers’ for ABAP, whose name indicates that any such violation cannot be tolerated, and ‘Critical’ defects, severe enough to require immediate correction, but for which an exception can be accepted, if it is very rigourosly justified.
In our SONAR Quality Profile, ‘Blockers’ focus on anything that can stop a transaction or program and ‘Critical’ on programming practices that pose a risk to the performance.
We will conclude this series on best practices of ABAP programming with the remaining rules, which will mainly affect the maintainability of the code.