jump to navigation

JDBC driver for Microsoft SQL Server November 16, 2008

Posted by essamabdelaziz in JAVA.
add a comment

jTDS is an open source 100% pure Java (type 4) JDBC 3.0 driver for Microsoft SQL Server (6.5, 7, 2000 and 2005) and Sybase (10, 11, 12, 15). jTDS is based on FreeTDS and is currently the fastest production-ready JDBC driver for SQL Server and Sybase. jTDS is 100% JDBC 3.0 compatible, supporting forward-only and scrollable/updateable ResultSets, concurrent (completely independent) Statements and implementing all the DatabaseMetaData and ResultSetMetaData methods. Check out the feature matrix for more details.

Quite a few of the commercial JDBC drivers out there are based on jTDS (or FreeTDS), even if they no longer acknowledge this. jTDS has been tested with virtually all JDBC-based database management tools and is the driver of choice for most of these (recommended for DbVisualizer and SQuirreL SQL, distributed with Aqua Data Studio and DataDino). jTDS is also becoming a common choice for enterprise-level applications: it passes both the J2EE 1.3 certification and Hibernate test suites, and is recommended for JBoss, Hibernate, Atlassian JIRA and Confluence and Compiere.

http://jtds.sourceforge.net/

Design pattern (Part 1) February 25, 2008

Posted by essamabdelaziz in JAVA.
add a comment

Nowadays I’m so interested in Design pattern

So will start to blog regarding the same starting

Today I will start to give a small introduction about design pattern later on i will go in depth to

talk about every pattern one by one in details

*What is design pattern?

If a problem occurs over and over again, a solution to that problem has been used effectively. That solution is

described as a pattern.

*design pattern VS Framework?

A framework is a product and

a design pattern is a specification.

Therefore a design pattern is part of your system design and a framework is part of your system.

The two could be looked at different contexts.

A design pattern suggests a solution for a recurring design problem in an application and the solution is generally open for future extensions.

A framework is a suite of packages using which applications (or the logical layers of applications), with all the functional and non-functional requirements, can be developed and hosted.

A design pattern it is the best solution for your problem like SingleTone,etc..

A framework like JSF,Struts,Spring,Hibernate

Do I have to use the design pattern?

If you want to be a professional Java developer, you should know at least some popular solutions to coding

problems. Such solutions have been proved efficient and effective by the experienced developers. These

solutions are described as so-called design patterns. Learning design patterns speeds up your experience

accumulation in OOA/OOD. Once you grasped them, you would be benefit from them for all your life and

jump up yourselves to be a master of designing and developing. Furthermore, you will be able to use these

terms to communicate with your fellows or assessors more effectively.

Many programmers with many years experience don’t know design patterns, but as an Object-Oriented

programmer, you have to know them well, especially for new Java programmers. Actually, when you solved

a coding problem, you have used a design pattern. You may not use a popular name to describe it or may not

choose an effective way to better intellectually control over what you built. Learning how the experienced

developers to solve the coding problems and trying to use them in your project are a best way to earn your

experience and certification.

Remember that learning the design patterns will really change how you design your code; not only will you

be smarter but will you sound a lot smarter, too.

How many design patterns?

Many. A site says at least 250 existing patterns are used in OO world, including Spaghetti which refers to

poor coding habits. The 23 design patterns by GOF are well known, and more are to be discovered on the

way.

Note that the design patterns are not idioms or algorithms or components

What is the relationship among these patterns?

Generally, to build a system, you may need many patterns to fit together. Different designer may use different

patterns to solve the same problem. Usually:

• Some patterns naturally fit together

• One pattern may lead to another

• Some patterns are similar and alternative

• Patterns are discoverable and documentable

• Patterns are not methods or framework

• Patterns give you hint to solve a problem effectively

 

http://www.javacamp.org/designPattern/index.html

The real reason of success “Teamwork” February 16, 2008

Posted by essamabdelaziz in JAVA.
2 comments

Teamwork is Cooperative effort by the members of a group or team to achieve a common goal or missions and as we all know that it is not used just in work but we can find it in all the needs of life.

Nowadays most of projects require that people work together, so teamwork has become an important concept everywhere. Effective teams are an intermediary goal towards getting good, sustainable results.

It is so deep field and I can got everything about it but there is two questions took my attention

How we apply the teamwork concept?

1- Listen to other people’s ideas. When people are allowed to freely express their ideas, these initial ideas will produce other ideas.
2- Ask questions, interact, and discuss the objectives of the team.
3- Treat others with respect and to support their ideas.
4- All the members should trust each other.
5- Help one’s coworkers, which is the general theme of teamwork.
6- Share with the team to create an environment of teamwork.
7- For a team to work effectively it is essential team members acquire communication skills and use effective communication channels between one another.
8- Be diplomat and tolerant.

There is a wonderful saying says “A Teamworker is the oil that keeps the machine running…the yeast that helps the dough rise. They are good listeners and diplomats, talented at smoothing over conflicts and helping parties understand each other without becoming confrontational” and unfortunately it is rarely in our society this days.

What are the laws of successful teamwork?

1- The Significance: One Is Too Small a Number to Achieve Greatness
2- The Big Picture: The Goal is More Important Than the Role
3- The Niche: All members Have a Place Where They Add the Most Value
4- The Great Challenge: As the Challenge Escalates, the Need for Teamwork Elevates
5- The Chain: The Strength of the Team Is Impacted by Its Weakest Link
6- The Bad Apple: Rotten Attitudes Ruin a Team
7- The Countability: Team-mates Must Be Able to Count on Each Other When It Counts
8- The Identity: Shared Values Define the Team
9- The Communication: Interaction Fuels Action

Amazing things could be accomplished today if we could get members and leaders to trust and commit to the teamwork process of joint problem solving, consensus decision making and shared leadership.

The lack of teamwork’ is blamed for such a wide variety of everyday business dilemmas — dilemmas like late delivery, poor quality, a blown budget or poor customer management. That because the people in businesses do not understand the real meaning of teamwork concept.

http://sarahhamidmahmoud.blogspot.com/2008/01/real-reason-of-success-teamwork.html

LDAP AND JNDI February 13, 2008

Posted by essamabdelaziz in JAVA.
add a comment

My Dears,

I have collected a few tips regarding LDAP and how to deal with Active Directory in java.

I will blog whatever I get Whenever I have the chance .

Here I will start with LDAP .

LDAP:

 

  • Lightweight Directory Access Protocol (LDAP)
  • was developed in the early 1990s as a standard directories protocol.
  • LDAP defines how clients should access data on the server
  • JNDI does for LDAP what JDBC does for Oracle — it provides a standard API for interacting with naming and directory services using a service provider interface (SPI)
  • LDAP is a standard way to provide access to directory information
  • An LDAP directory entry is a collection of attributes with a name, called a distinguished name (DN). The various types of additional data obout that DN, (e.g. phone number, email address, mailing address, security access code) may have restricted access to a subset of users of the database.

eads from right to left. Here is an example of an DN:

uid=styagi,ou=people,o=myserver.com

o

Organization

ou

Organizational unit

cn

Common name

sn

Surname

givenname

First name

uid

Userid

dn

Distinguished name

mail

Email address

Some common LDAP attributes


*Any attribute can have one or more values, depending on how it is defined the schema.

 

have alook here

to find a very useful article regarding the same .

 

 

JAR ,WAR ANd EAR October 21, 2007

Posted by essamabdelaziz in JAVA.
1 comment so far


JAR is Java Archive
WAR is an Web Aapplication archive
EAR is an Enterprise Aapplication archive

all 3 formats are zip files.. rename thm to .zip and you will be able to open them.

 in the J2ee world they are used accordingly.:
.jar files usually will java class files and maybe some config files.. acts like a include library.. files referenceable by your app if the file is in the classpath..
.war files usually contains a web application ..i.e a servlet with jsp files, classes and stuff..
.ear files usually includes enterprise stuff, beans etc.


What Is Logging June 16, 2007

Posted by essamabdelaziz in JAVA.
add a comment

Logging in any application generally means some way to indicate the state of the system at runtime

This definition of logging highlights the following important points:

·         It is systematic.

·         It is controlled.

·         It represents an application’s state.

Logging Is Systematic

Logging should be a systematic approach rather than an arbitrary way of producing information. More often than not, we will need to define a strategy for our logging activity. We need to decide beforehand what information to log, yet these decisions are not always easy. We should look at this problem from more than one angle. Typically, we need to produce logs for debugging and day-to-day maintenance of an application. We may also need to produce detailed logs for system administrators monitoring the performance of the system. Again, we may need to distribute logging information to various remote places to facilitate remote management of the application. The issues are endless. Hence, we need a logging strategy before we embark on writing an application.

Logging Is Controlled

There is one and only one way to log the information we require: We have to write some logging code within our applications. The logging code needs to go through the same controls as the main application code. Like every piece of application code, the logging code can be well written or badly written. Keep in mind that logging is there to support and improve the quality of the application being written. Therefore, the logging code should be written in such a way that it has least impact on the overall performance of the system.

Also, we need to exercise some control over where the logging information is stored and the format of the logging information. The logging information needs to be structured so that is easily readable and can be processed at a future date with the least effort. One example is to prefer logs in XML format rather than in simple text format. Although text format for logging may be desirable in the development stage, XML format is much more reusable and portable when the application is deployed. In other situations, we may need to store logging information in a database to maintain a history of the logs produced.

Logging Information Represents the Application State

The logging information produced may be quite useless if sufficient care is not taken about what to log. To make logging activity most effective, we should aim to represent the internal state of the system wherever required and also to present a clear idea of what stage of control the application is at and what it is doing. If you can visualize your system as a collection of distinct components performing several related and sequential tasks, you may well need to log the state of the system before and after each task is performed.

 Benefits of Logging

In short, logging within an application can offer the following benefits:

·         Problem diagnosis: No matter how well written our code is, there may be some problems hidden in it. As soon as the triggering conditions occur, the hidden problems come to the surface. If our applications have well-written code for logging the internal state of the system, we will be able to detect the problems precisely and quickly.

·         Quick debugging: Once it is easy to diagnose the problem, we know exactly how to solve the problem. The logging trace should be aimed at precisely showing the location of the problem, which means we will be able to debug the application in less time. The overall cost of debugging the application is reduced greatly by well-planned and well-written logging code.

·         Easy maintenance: Applications with a good logging feature are easy to debug and therefore easily maintainable compared to any application without a similar logging feature. The logging information typically contains more information than the debugging trace.

·         History: A good logging feature in an application results in logging information being preserved in a structured way at a desired location. The location may be a file, database, or remote machine. All this enables system administrators to retrieve the logging information at a future date by going through the logging history.

·         Cost and time effective: As explained, well-written logging code offers quick debugging, easy maintenance, and structured storage of an application’s runtime information. This makes the process of installation, day-to-day maintenance, and debugging much more cost and time effective.

Disadvantages of Logging

the following disadvantages can occur with any logging process:

·         Logging adds runtime overhead due to the generation of logging information and the device I/O related to publishing logging information.

·         Logging adds programming overhead due to the extra code required for producing logging information. The logging process increases the size of the code.

·         Badly produced logging information can cause confusion.

·         Badly written logging code can seriously affect the performance of the application.

·         Last not but not the least, logging requires planning ahead, as adding logging code at a later stage of development is difficult.

Online Analysis Processing (OLAP) April 26, 2007

Posted by essamabdelaziz in JAVA.
1 comment so far

OLAP (On-Line Analytical Processing) is a technology that uses multidimensional structures to provide rapid access to data for analysis.

OLAP enables analysts, managers, and executives to gain insight into data through fast, consistent, interactive access to a wide variety of possible views of information. OLAP transforms raw data so that it reflects the real dimensionality of the enterprise as understood by the user.

Multidimensional views are inherently representative of an actual business model. Rarely is a business model limited to fewer than three dimensions. Managers typically look at financial data by scenario (for example, actual vs. budget), organization, line items, and time; and at sales data by product, geography, channel, and time.

How does OLAP organize its data?
OLAP organizes data into cubes, dimensions, and measures. A cube is a set of data that is organized and summarized into a multidimensional structure defined by a set of dimensions and measures.

A dimension is an organized hierarchy of categories (levels) that describe data in the cube. These categories typically describe a similar set of members upon which the user wants to base an analysis. (You can often recognize a dimension by the use of the word “by”—”sales by city” or “sales by year.”). For example, a geography dimension might include levels for Country, Region, State or Province, and City. A time dimension may contain the levels Year, Month, and Day.
A measure is a summation of values in the cube and is usually numeric. Measures are the central values that are aggregated and analyzed.

How does OLAP store its data?
The source data for OLAP is commonly stored in an OLAP database. An OLAP database is a database specifically structured for query and analysis. An OLAP database typically contains information that answers “who?” and “what?” questions about past events. A typical query submitted to an OLAP database is: “What was the total revenue for the eastern region in the third quarter?”

ecm Help

BIRT Step by Step April 22, 2007

Posted by essamabdelaziz in JAVA.
add a comment

from along while i was trying to do some effort in Reporting coz

 it is very important issue for an project mostly all projects should have Reporting Module to provide the end users with statistical reports.

 i started with jasper report and  Ireport but it was booing for me.

 during R&D i found Birt (Business Intelligence and Reporting Tools) 

how to use birt?

 1-download BIRT designernow you can Design your first report the designer is easy to learn the above link provide a flash movie to show you how to build HelloWorld Report

 2-Doenload Birt runtime To Show your Report in your J2EE Application

3-delopy WebViewerExample put this folder under webApps

Now you build your first report and show the report in your j2ee Application

let’s  move to another  another important issue how to pass a parameter to the Report 

·  In your report design add a new Report Parameter ( RP_param ) ·  In your data set Query create your query with something like “WHERE ID = ?” or some other criteria using a ? for the value

. ·  In your data set add a Parameter ( DS_param ) then set the default value of this parameter to the Report Parameter you created earlier (RP_param) to do this click on the default value field then the … button

. In the resulting dialog choose Category ‘Report Parameters’, sub category ‘All’ then double click your Report Parameter to add it and click OK.
 

First about J2ME April 20, 2007

Posted by essamabdelaziz in JAVA.
add a comment

Al salam Alykom,

 That will be isA the first article about J2Me, just to introduce this technology.

J2ME stands for java microedition technology, it is a technology for microcomputers like PDAs, mobiles….etc.

It is mostly used in mobile applications. On using in mobile applications it needs WTK “Wireless tool kit”  instead of JDK with desktop applications, which contains the required APIs to deal with mobile applications.

That was just an overview about J2ME and it will be followed isA by more detailed and useful information about J2ME

What is Domain Naming Service(DNS)? April 18, 2007

Posted by essamabdelaziz in JAVA.
add a comment

It is very difficult to remember a set of numbers(IP address) to connect to the Internet. The Domain Naming Service(DNS) is used to overcome this problem. It maps one particular IP address to a string of characters. For example, www. mascom. com implies com is the domain name reserved for US commercial sites, moscom is the name of the company and www is the name of the