WaveMaker Visual Ajax Studio is an easy-to-use visual builder that enables the drag & drop assembly of scalable, web-applications using Ajax widgets, web services and databases.

Key Features:

• Drag & Drop Assembly
• LiveLayout™
• Push to Deploy™: One-touch application deployment
• Visual Data Binding
• SOAP, REST and RSS web services
• Leverage existing CSS, HTML and Java
• Deploys a standard Java .war file
• Free

Video Demo

GWT-Ext is a powerful widget library that provides rich widgets . It uses GWT and Ext.

Hello there ,

I think the best way to Do a CVS ( Concurrent versions system )  are using a CMS(Blog) on your local web server, like ” WordPress ” by creating categories (your projects) and writing articles every update  ( what did you do on this update ?) and joining a zipped file of your updated project , doing this you got a lovely version control system

1- you can find it easily ( tag , date , categories (project name))

2- clients , colleagues or project manager can comment your update

…

Data staging

Most data in OLAP applications originates in other systems. However, in some applications (such as planning and budgeting), the data might be captured directly by the OLAP application. When the data comes from other applications, it is usually necessary for the active data to be stored in a separate, duplicated, form for the OLAP application. This may be referred to as a data warehouse or, more commonly today, as a data mart. For those not familiar with the reasons for this duplication, this is a summary of the main reasons:

Performance
OLAP applications are often large, but are nevertheless used for unpredictable interactive analysis. This requires that the data be accessed very rapidly, which usually dictates that it be kept in a separate, optimized structure which can be accessed without damaging the response from the operational systems.

Multiple data sources
Most OLAP applications require data sourced from multiple feeder systems, possibly including external sources and even desktop applications. The process of merging these multiple data feeds can be very complex, because the underlying systems probably use different coding systems and may also have different periodicities. For example, in a multinational company, it is rare for subsidiaries in different countries to use the same coding system for suppliers and customers, and they may well also use different ERP systems, particularly if the group has grown by acquisition.

Cleansing data
It is depressingly common for transaction systems to be full of erroneous data which needs to be ‘cleansed’ before it is ready to be analyzed. Apart from the small percentage of accidentally mis-coded data, there will also be examples of optional fields that have not been completed. For example, many companies would like to analyze their business in terms of their customers’ vertical markets. This requires that each customer (or even each sale) be assigned an industry code; however, this takes a certain amount of effort on the part of those entering the data, for which they get little return, so they are likely, at the very least, to cut corners. There may even be deliberate distortion of the data if sales people are rewarded more for some sales than others: they will certainly respond to this direct temptation by ‘adjusting’ (ie distorting) the data to their own advantage if they think they can get away with it.

Adjusting data
There are many reasons why data may need adjusting before it can be used for analysis. In order that this can be done without affecting the transaction systems, the OLAP data needs to be kept separate. Examples of reasons for adjusting the data include:

• • Foreign subsidiaries may operate under different accounting conventions or have different year-ends, so the data may need modifying before it can be used.
  • The source data may be in multiple currencies that must be translated.
  • The management, operational and legal structures of a company may be different.
  • The source applications may use differenrt codes for products and customers.
  • Inter-company trading effects may need to be eliminated, perhaps to measure true added value at each stage of trading.
  • Some data may need obscuring or changing for reasons of confidentiality.
  • There may be analysis dimensions that are not part of the operational data (such as vertical markets, television advertising regions or demographic characteristics).

Timing
If the data in an OLAP application comes from multiple feeder systems, it is very likely that they are updated on different cycles. At any one time, therefore, the feeder applications may be at different stages of update. For example, the month-end updates may be complete in one system, but not in another and a third system may be updated on a weekly cycle. In order that the analysis is based on consistent data, the data needs to be staged, within a data warehouse or directly in an OLAP database.

History
The majority of OLAP applications include time as a dimension, and many useful results are obtained from time series analysis. But for this to be useful it may be necessary to hold several years’ data on-line in this way — something that the operational systems feeding the OLAP application are very unlikely to do. This requires an initial effort to locate the historical data, and usually to adjust it because of changes in organizational and product structures. The resulting data is then held in the OLAP database.

Summaries
Operational data is necessarily very detailed, but most decision-making activities require a much higher level view. In the interests of efficiency, it is usually necessary to store merged, adjusted information at summary level, and this would not be feasible in a transaction processing system.

Data Updating
If the application allows users to alter or input data, it is obviously essential that the application has its own separate database that does not over-write the ‘official’ operational data.

Storing active OLAP data

Given the necessity to store active OLAP data in an efficient, duplicated form, there are essentially three options. Many products can use more than one of these, sometimes simultaneously. Note that ’store’ in this context means holding the data in a persistent form (for at least the duration of a session, and often shared between users), not simply for the time required to process a single query.

Relational database
This is an obvious choice, particularly if the data is sourced from an RDBMS (either because a data warehouse has been implemented using an RDBMS or because the operational systems themselves hold their data in an RDBMS). In most cases, the data would be stored in a denormalized structure such as a star schema, or one of its variants, such as snowflake; a normalized database would not be appropriate for performance and other reasons. Often, summary data will be held in aggregate tables.

Multidimensional database
In this case, the active data is stored in a multidimensional database on a server. It may include data extracted and summarized from legacy systems or relational databases and from end-users. In most cases, the database is stored on disk, but some products allow RAM based multidimensional data structures for greater performance. It is usually possible (and sometimes compulsory) for aggregates and other calculated items to be pre-computed and the results stored in some form of array structure. In a few cases, the multidimensional database allows concurrent multi-user read-write access, but this is unusual; many products allow single-write/multi-read access, while the rest are limited to read-only access.

Client-based files
In this case, relatively small extracts of data are held on client machines. They may be distributed in advance, or created on demand (possibly via the Web). As with multidimensional databases on the server, active data may be held on disk or in RAM, and some products allow only read access.

These three locations have different capacities, and they are arranged in descending order. They also have different performance characteristics, with relational databases being a great deal slower than the other two options.

Processing OLAP data

Just as there are three possible locations for OLAP data, exactly the same three options are available for processing the data. As will be seen, the multidimensional calculations do not need to occur in the place where the data is stored.

SQL
This is far from being an obvious choice to perform complex multidimensional calculations, even if the live OLAP data is stored in an RDBMS. SQL does not have the ability to perform multidimensional calculations in single statements, and complex multi-pass SQL is necessary to achieve more than the most trivial multidimensional functionality. Nevertheless, this has not stopped vendors from trying. In most cases, they do a limited range of suitable calculations in SQL, with the results then being used as input by a multidimensional engine, which does most of the work, either on the client or in a mid-tier server. There may also be a RAM resident cache which can hold data used in more than one query: this improves response dramatically.

Multidimensional server engine
This is an obvious and popular place to perform multidimensional calculations in client/server OLAP applications, and it is used in many products. Performance is usually good, because the engine and the database can be optimized to work together, and the availability of plenty of memory on a server can mean that large scale array calculations can be performed very efficiently.

Client multidimensional engine
On the assumption that most users have relatively powerful PCs, many vendors aim to take advantage of this power to perform some, or most, of the multidimensional calculations. With the expected rise in popularity of thin clients, vendors with this architecture are having to move most of the client based processing to new Web application servers.

Source

L’API Ext 2.0 est très vaste , se souvenir de toutes les fonctions, propriétés ou des configurations disponibles est pratiquement impossible. La documentation de l’API est très poussé, mais il serait bien que si Des IDEs permettrait d’assister a fournir du code en javascript comme ils le font dans d’autres langages tels que Java et C #. Heureusement, il existe des IDE et plugins disponibles avec aussi un soutien direct de Ext 2.0 .

Voici quelques-uns :

Aptana Studio :

Spket Eclipse Plugin & IDE

Komodo Edit

SpketDW (Dreamweaver MX 2004 or higher)

3G Mobile Network Security

White Paper

Executive Summary

Mobile operators need to recognize their newfound role as internet service providers
(ISPs). No longer do they just provide cellular voice services; now they also provide highspeed Internet Protocol-based (IP) data services. So as to offer a wider array of services
and content to their data subscribers, mobile operators are opening up their formerly
closed networks to numerous other mobile operators, data networks and the public
Internet.

As a result, mobile operator’s 3G networks are not only exposed to all the virtual
pathogens already in circulation, but also to mobile-specific viruses and Trojans, as well as
to direct attacks such as Denial of Service (DoS) on their networks from hackers and/or
criminal organizations. These types of attacks employ methods which wired ISPs have
been dealing with for a much longer period of time. There are also variations on these
attacks which exploit weaknesses in the architecture and some of the protocols used in
2.5G/3G cellular data networks.

To protect their networks and customers, then, mobile operators need to:

. Take an architecture approach to implementing security solutions in their network;
point solutions are not sufficient

. Deploy a variety of products in their networks, such as firewalls, intrusion
detection and prevention (IDP) and virtual private networks (VPNs)

. Make client-side anti-virus and firewall software readily available to their
subscribers who use data devices (e.g., feature phones with data capabilities,
smartphones, notebook computers)

. Be vigilant and adopt appropriate security policies that reflect the threats in the
2.5/3G world. This has additional ramifications given the widespread use of WiFi
and the general evolution toward networks based on the IP Multimedia
Subsystem (IMS) standard

. Be aware that their networks are only as secure as the weakest link. Mobile
operators need to work with each other, the ISP community and other telecom
providers to ensure that even the minimum amount of security is quite strong.

. Vigorously protect signaling as the migration of signaling traffic over IP creates
new risks. Mobile operators carry much more signaling traffic than their wired
counterparts and signaling is mission critical traffic.

This whitepaper will explore the following topics:

. Why 2.5/3G wireless networks are now vulnerable and at what points they are
vulnerable

. The types of attacks that can be perpetrated against those networks

. The types of products that can be deployed to help guard 3G networks

. The business implications of a network outage and a revenue impact model to
demonstrate the seriousness of such an outage

. Future threats to mobile operators, specifically regarding IMS which is being
deployed by fixed and mobile carriers around the world.

Finally, this paper also suggests some steps mobile operators can take to minimize the
risk to their networks and their customers.

More on : http://www.igr-inc.com/html/downloads/free_white_papers/3G_MobileSecurity_Jan07.pdf

source : igr-inc.com

Le spoofing ARP est un type de spoofing très simple à mettre en oeuvre. Sa puissance vient du fait qu’il permettra d’obtenir une connection TCP active (blind spoofing). Il repose sur la couche 2 du modèe OSI (liaison).  s’appliquer qu’à des réseaux du fait même du protocole ARP. Dans cette article je vais expliquer comment réaliser un spoof grâce à ARP et aussi les moyen pour lutter contre ce type d’attaque.

Man in the middle attack

Denial of Service

Solution :

Il existe une méthode très simple pour pouvoir se prémunir du spoofing ARP, il suffit d’enregistrer de manière statique les adresse MAC des cartes réseaux. Une autre méthode pour se prémunir, essentiellement si l’on se trouve dans un réseau hétérogène est d’utiliser le programme ARPWATCH. Cette utilitaire vous informe par email dès qu’une adresse IP change d’adresse MAC. On peut télécharger ARPWATCH à http://ftp.su.se/pub/security/tools/audit/arpwatch/arpwatch-1.7.tar.gz

voici quelques démonstration de cette magnifique distribution linux :

WPA2 or WPA Hack with Backtrack V3

WEP Crack w/ Backtrack 2

Solution :

la configuration d’un Freeradius/TLS & PEAP (avec des certificats générés par openssl et windows2000) pour des clients winxp et linux .en gros une WPA/TLS authentication.
voici quelques liens :

http://oriol.joor.net/blog/?itemid=1631
http://www.dslreports.com/forum/remark,9286052%7Emode=flat
http://www.freeradius.org/doc/EAPTLS.pdf

Débutons cette série d’articles sur les technologies riches par celle que je connais le mieux : Adobe Flex.

Adobe Flex

Historique

Lancé par Macromedia en mars 2004, Flex a ensuite été porté jusqu’à la version 1.5 avant le rachat de Macromedia par Adobe (en décembre 2005). Sentant le fort potentiel de cette technologie, Adobe a poursuivi le développement et en juin 2006 est sortie la version 2.0 de Flex, version enfin mature et présentant de très nombreuses nouveautés ainsi qu’un nouveau langage : l’Action Script 3. De nombreux bugs ont été conrrigés dans la version 2.0.1 sorti en janvier 2007, et déjà Flex 3 est annoncé pour l’année 2007 !

Présentation

Qu’est-ce qu’Adobe Flex ? C’est un ensemble d’outils formant un framework de développement d’applications en Flash. Précision : tout ce qui est fait avec Flex peut être fait avec Flash mais… en dix fois moins de temps. Au moins. Et c’est certainement là la première valeur ajoutée de Flex.

Le principe

Flex est basé sur un langage XML de description : le MXML (pour Macromedia XML). Sur le mode design de Flex Builder (l’IDE d’Adobe pour le Flex), ce xml est construit automatiquement, mais une utilisation plus poussée nécessitera de toucher au code, notamment pour y inclure de l’action script. Le code est ensuite compilé et un fichier .swf est généré.

Les outils

• Flex SDK : le compilateur, gratuit. Il est téléchargeable sur le site d’Adobe.
• Flex Builder : l’IDE : indispensable. Il en existe deux versions : la version stand-alone, et la version Eclipse. Cette dernière version s’intégre à l’environnement de développement J2EE, alors que la première reprend son interface mais ne permet que de développer du Flex.
• Flex Charts : pour produire des graphiques.
• Flex Data Services : ensemble de briques fournissant divers services vers le serveur : binding Hibernate, queue JMS, etc.

Les exemples

Pour bien comprendre Adobe Flex, le mieux est de prendre des exemples :

• Le restaurant finder
• Exemple de boutique en ligne
• Yahoo! Maps
• Amazon
• Picnik : éditeur de photos en lignes

Les points forts

Adobe Flex est une solution pour développer des applications riches. Elle comporte de nombreux points forts : le développement est très rapide grâce à son IDE et son système WYSIWYG de drag’n'drop des composants Flash que l’on retrouve pour toute interface (boutons, liens, combo box, etc.). De nouveaux composants sont ajoutés, comme les accordéons ou les sliders, qui permettent d’enrichir les possibilités. De plus, Flex est maintenant doté du langage Action Script 3, langage objet à mi-chemin entre le Java et le C#. Ses possibilités sont très nombreuses et permettent une extension complète de l’ensemble des composants pré-définis, permettant la création de composant avec une liberté totale, et donc d’une richesse. Les appels à des Web Services sont très simplifiés, ce qui est un avantage à l’époque du Web 2.0.

Il existe évidemment d’autres avantages comme la communauté autour du produit qui commence à prendre de l’ampleur. Pour plus d’informations, veuillez-vous référez aux liens ci-dessous.

Liens, pour en savoir plus

• Livre blanc de Flex 2 (pdf)
• Le centre de développement Adobe
• Flex.org, la référence
• Essayez Flex gratuitement !

Récapitulatif

Flex est basé sur Flash et offre donc visuellement des composants beaux et riches. Les possibilités offertes par l’action script 3 sont énormes et font de cette technologie un véritable instrument puissant pour la création d’applications web, voire d’applications d’entreprises. Flex commence donc à faire de plus en plus parler de lui et l’arrivée d’Apollo offre à Flex un environnement pour s’exprimer pleinement.