September 08 : PEtALS ESB releases

2008-09-25T14:22:39+00:00

September is generally the month of major PEtALS releases. But this year, it is not the case...
We have decided to delay the next major PEtALS release to the end of the year, this is simply because we have lot of things to deal around PEtALS : Customers, French and European research projects (http://www.ebmwebsourcing.com/partenaires/partenaires-recherche.html?lang=en ), ...

So, don't be worry, PEtALS v3.0 will be great, PEtALS v4.0 will be...

While working on these other things, here are some release we have done this month :

Standalone distribution 2.2.1 : Bugfix and stability again
Component Development Kit 4.0.3
Updated JBI components such as SOAP (now with REST support), POJO, XQUARE (JDBC), XSLT, EIP...
Initial release of the BPEL component based on Orchestra (http://orchestra.ow2.org )

The website has been updated, a forum has been added (http://petals.objectweb.org/forum.html).

PEtALS Social Networks

2008-07-21T18:55:55+00:00

Join the PEtALS community on social networks : LinkedIn and FaceBook.

PEtALS ESB 2.2 is out

2008-07-21T15:14:47+00:00

PEtALS ESB 2.2 is finally out some weeks late...
This kernel version is distributed as Standalone and Quickstart distribution.

As a reminder, if you are new to PEtALS you should choose to download the Quickstart distribution.
This distribution comes with the new embedded WebConsole (1.2) Management and Monitoring tool which is launched at PEtALS startup so you do not need to deploy the web application in an external web application server such as Tomcat. Just look at http://localhost:7878 !
You will also find some simple integration usecases in this package, all is fully explained in the Quickstart documentation.

We have also released a new Component Development Kit (CDK 4.0). With this CDK, you will be able to create powerful JBI compliant components (Service Engine or Binding Component) with one or two classes...
The SOAP, FileTransfer, XSLT and EIP components have been updated to the CDK 4.0.
An Eclipse plugin based on new JBI descriptors is coming in the next weeks, so stay tuned!

As main developer of the SOAP Binding Component, I am also happy to announce that I have added REST support in the latest release. I will write a tutorial here in the next days.
I am also working on another nice feature around Web Services and Axis2. More information to come...

Cheers,

Installation d'un SAN sur ESX Server 3.5

2008-06-19T05:48:57+00:00

J'explique rapidement comment installer un SAN de marque EMC serie CX3-80 sur un serveur Vmware ESX 3.5 .

On s'aperçoit via la console de Virtual Center que dans l'onglet Configuration/Storage Adapters de l'ESX Server que les LUNs sont détecter mais
que le SAN nous autorise pas à se connecter (car on récupère bien les paths, l'ID du SAN, mais pas sa capacité).

Au démarrage du serveur nous voyons le message :
---------------------------------------------------------------------------
VMWARE: Device that would have been attached as scsi disk sdg at scsi0, channel 0, id 1, lun 6
Has not been attached because it is a duplicate path or on a passive path
------------------------------------------------------------------------------

En se rendant sur l'outil de management de Navisphere, on ne trouve pas notre ESX Server, tout ça est normal car on doit installer sur l'ESX l'agent Navisphere
qui va nous permettre de déclarer notre Server sur le SAN.

En épluchant différentes docs de ESX Server, il est indiqué qu'il n'est pas souhaitable d'installer des paquets RedHat sur ESX, donc je pensais que l'outil NaviAgent de RedHat n'était pas
compatible,mais après plusieurs tentatives malheureuses , j'ai quand même voulu essayer NaviAgent de RedHat sur ESX et là, dès l'installation terminée nous avons vu apparaître le Server ESX dans l'outil du management du SAN et nous l'avons ajouté dans le LUN souhaité.

Maintenant, il est possible grâce à l'onglet Configuration/Storage/Add Storage d'ajouter le LUN et de le formater en VMFS.

Un petit mot sur Vmware

2008-06-06T10:46:18+00:00

Avec l'expansion de la virtualisation, je vais mettre quelques liens vers des articles
très bien fait sur l'installation de VMware Server sur Debian et Ubuntu.

Pour commencer, il faut s'enregistrer sur le site de VMware pour générer des numéros de série.

Installation sur Debian Etch:

http://www.go2linux.org/vmware-server-on-debian-etch

et

http://www.nemako.net/dc2/?post/2007/01/15/114-installer-vmware-server-sous-debian

Installation sur Ubuntu 7.10:

http://www.taltan.fr/post/2007/11/01/VMware-Server-104-sur-Ubuntu-710-Gutsy-Gibbon

Installation sur Ubuntu 8.04:

http://www.taltan.fr/post/2008/03/24/VMware-Server-105-sur-Ubuntu-804-Hardy-Heron

Message d'erreur possible :

Cannot open the disk 1-000001.vmdk' or one of the snapshot disks it depends on. Reason: Failed to lock the

Si vous avez ce style de message d'erreur en déplaçant une VM d'un serveur à l'autre
il faut absolument faire un Snapshot avant de déplacer l'image et appuyer sur "Revert" de l'interface VMware Server pour
restaurer le Snapshot précédent. La machine virtuelle peut enfin démarrer sans message d'erreur.

PEtALS ESB as part of SOA4ALL architecture

2008-05-21T06:45:09+00:00

PEtALS has been choosen as part of SOA4ALL architecture.
One of the SOA4ALL project goal is to create a new infrastructure composed of billions of services.

Here is a short presentation I gave last week during the SOA4ALL project architecture meeting :

| View | Upload your own

New online tool, OS SCMs as cloud and RSS

2008-04-23T06:39:43+00:00

I jave just registered PEtALS into CodeNotifier, a new online tool which analyzes Open Source SCMs (currently only SVN is supported). A cloud is then generated and you can subscribe to project commits RSS feeds.
The PEtALS project page is available here and the commits RSS feed is available here.

PEtALS Certified by SUN Microsystems

2008-04-18T05:49:02+00:00

It seems that I have forgotten to publish this blog entry, so...

PEtALS 2.1.1.1 Quickstart distribution has been officially JBI certified by SUN Microsystems .
This petals-kernel-2.1.1 based distribution has successfully passed the JBI compatibility test suite (JBI TCK). In other words it means that PEtALS is a complete JSR 208 implementation...
Thanks to all developers and contributors !

New generation service infrastructure and the semantic challenge

2008-04-03T13:09:38+00:00

An article in SOAWorld magazine where I present main objectives of the SEMEUSE project: Next-Generation Service Infrastructure & the Semantic Challenge

Driven by SaaS market momentum, the growth of large service ecosystems involves radical changes in both enterprise Business Process organization and IT infrastructure to fit interoperability and agility requirements.

Many questions associated with the paradigm shift arise: how can we move to a network of services of Internet scale transparently available across the many devices we use to access information? What support will services need from an increasingly ubiquitous Internet? To meet these requirements, we propose to address the service infrastructure itself and provide an open, context-aware service bus, enabling both syntactic and semantic interoperability.

http://soa.sys-con.com/read/523483.htm

PEtALS on Ohloh.net

2008-03-05T14:12:07+00:00

PEtALS project is now available on ohloh.net.
Ohloh is an open source network that connects people through the software they create and use.

This collaborative website provides tons of statistics on PEtALS source code, users, developers... Please visit the PEtALS page on ohloh.net.

PEtALS QuickStart 2.1.1

2008-02-19T08:39:26+00:00

The PEtALS Team is pleased to announce the release of PEtALS Quickstart 2.1.1. This distribution comes with the latest petals-kernel, and provide the latest WebConsole as embedded service.
This distribution also comes with the brand new JBI Component Development Kit and updated JBI Components.

More details in the release notes.

Too many open files IOException with large number of Axis2 Servic

2008-01-10T06:43:42+00:00

This is a problem we met in the PEtALS SOAP Binding Component with large number of Axis2 Service Clients.
In this case, this error happens when too many sockets are open ant are waiting to be closed. Even if I have found some JIRAs about this problem and possible solutions, the only one which work for us is to cleanup the connection after each service call.
It is done like this :

...

ServiceClient client = new ServiceClient(null, service);

Options options = new Options();

...

options.setCallTransportCleanup(true);

client.setOptions(options);

OMElement outBodyElement = null;

try {

outBodyElement = serviceClient.sendReceive(soapAction, inBodyElement);

} catch (AxisFault e) {

throw e;

}

After 10 minutes test with 200 threads creating 'one shot ' ServiceClient and almost 275000 service calls, all worked fine.

Going to JavaPolis 07

2007-12-07T06:39:41+00:00

See you next week JavaPolis '07 on the OW2 Consortium booth to talk about and make some 'demos' of the PEtALS Enterprise Service Bus project.

PEtALS Standalone 1.4.3

2007-12-05T06:23:29+00:00

PEtALS Standalone platform 1.4.3 is out. This is a maintenance release.
Look at the release notes for more details.

CIMERO2 Editor for PEtALS ESB

2007-12-04T21:19:54+00:00

The CIMERO2 editor is an Eclipse plugin originally developed by Bull. This plugin provides features to create a visual representation of your Enterprise Service Bus based architecture. After the design step, the plugin offers the possibility to generate the JBI artifacts (Service Assemblies), and the Ant deployment scripts which will be used to deploy the configuration on the ESB.

We, at eBM WebSourcing, are currently working on better integration of the PEtALS JBI components. You can find a Flash demonstration on how we you can use this plugin on the PEtALS project website demonstration page.

Finally, it is good to notice that this plugin is currently under integration into the Eclipse SOA Tools Platform project (Eclipse STP).

Installing SVN Client on Mac OSX

2007-11-29T06:56:01+00:00

I am happy to see that Fink (http://finkproject.org/) is no more needed to easily install a Subversion client on Mac OSX. A client has been packaged by this guy Martin Ott (http://homepage.mac.com/martinott/).

Installation done by clicking on the package...

I am also happy to see that there is a Subversion GUI client for OSX. Working with terminal is cool but sometimes clicking on the mouse is not so bad...

You can found this client on 'La chose interactive' website (http://www.lachoseinteractive.net/fr/communaute/subversion/).

Configuration seems very intuitive... Going to test it for PEtALS project...

Réparer Grub...

2007-11-21T09:47:46+00:00

Comment réparer Grub après l'installation de Windows.

J'ai découvert un petit utilitaire très intéressant qui permet de réparer très simplement le boot Grub,
ça nous est arrivé à tous de ne plus pouvoir booter sur notre système Linux.
Rendez-vous sur ce site qui propose un utilitaire qui s'appelle Super Grub Disk.

SEMEUSE RNTL project

2007-11-01T22:23:17+00:00

I am very please that a new project call SEMEUSE (SEMantiquE pour BUS de sErvice) has been selected by the French ANR/RNTL research body for funding. This project deals mainly with study and development of a Semantic Entreprise Service Bus. EBM WebSourcing is one of the consortium's members among others big names which are: Thales, France Telecom, Lip6, INSA Lyon, INRIA (Arles and ObjectWeb) and INT.

The SEMEUSE project specifically aims to provide a context-aware semantic service architecture addressing both the design phase, thanks to theoretical context-aware semantic service models and policy-oriented design patterns, and the runtime phase, thanks to a Dynamic Semantic Service Bus (see below figure). This extended service bus is based on a static and dynamic service composition engine so that the current execution context and particular requirements (related for example to nomadic constraints) can be continuously taken into account. A dynamic monitoring system, using CompositeProbes, will also be connected to the orchestration process so that QoS aware late binding can be implemented.

The main objectives of SEMEUSE are then to:

Enable service to be used anywhere from any kind of device (pervasive technologies).

Address non-functional/QoS requirements associated with service provisioning, with a special emphasis on dependability constraints and more specifically reliability and security.

Provide an agile framework supporting business-level Service level Agreements (SLA) definition and monitor system behaviour accordingly in order to enforce required non-functional properties of, potentially composite, service execution.

To meet the target objectives in the project timeframe of 30 months, the SEMEUSE consortium groups complementary competencies, from both academia and industry, bringing together experts in all the areas of relevance, namely middleware development, SOA, ESB, semantic service technologies, SLA management, security policies organisation?

The open-source oriented implementation strategy is further reinforced by the expertise of most of the members of the consortium acting as leaders in the field in particular inside the OW2 (http://www.ow2.org) open-source consortium dedicated to middleware.

Organised in an iterative way (first specifications phase, validation phase, final specification) the work will be organised as follows:

A reference architecture (including both the theoretical design level and the operational ESB platform) provides the necessary integration dimension.
A semantic description work-package support the ?static? semantic context-aware service description (including functional and non functional requirements) and the way service are stored, discovered and selected.
A monitoring and orchestration work-package support the dynamic part of the system, i.e. the way monitoring functions are added in a classical ESB to capture the current execution context, the way this execution context is used to select and orchestrate services?
The necessary tooling functions (design and monitoring tools as well as design by community tools) are developed in a separate work package
Use cases are used to improve requirements definition and to validate the global architecture.

This project will use the OW2 PEtALS (http://petals.objectweb.org) Enterprise Service Bus and contribute to pave the way for next generation ESB.

Ubuntu 7.10

2007-10-25T08:42:14+00:00

Ubuntu 7.10 est arrivé, installation sans problème comme d'habitude.
Petit problème quand même pour installer correctement la carte graphique (NVIDIA). Avec les drivers de chez Nvida à chaque redémarrage, je perdais la résolution.
Le portable est un Dell LATITUDE D820 avec une NVIDIA Quadro NVS 110M 256 Mo
Donc j'ai utilisé le logiciel Envy disponible sur Ubuntu.
Voici le lien et le paquet qu'il faut absolument pour installer Envy.

Envy ici et le paquet module-assistant

Ces deux paquets installés, j'exécute le logiciel en mode console (Ctrl+Alt+F1) et je stoppe le serverX

# sudo /etc/init.d/gdm stop

# sudo envy -t

Désinstaller l'ancien driver, (si déjà une version installée) et aprés installer le driver et répondre "Yes" aux questions posés à la fin de l'installation.

Démarrer le server X

# startx

Dans Applications/Outils systéme un icone NVIDIA est présent, cela va nous permettre de gérer la résolution et surtout de manager les sorties écrans quand on ajoutera un Video Projecteur.

PEtALS PACK 2.0

2007-09-28T17:10:58+00:00

Friday (evening) September 28th 2007

PEtALS ESB 2.0 is finally out!
It is released at the same time as a 'pack' including all new/compatible modules which have been developed since months.
These modules are :

The PEtALS kernel 2.0
A new Web Console for monitoring and administration
The Component Development Kit 3.0 : Library and tools for easily and rapidly create JBI compliant components.
A collection of JBI compliant components (including new ones like XMPP, HTTP binding components, EIP, RMI Service Engines)
An Eclipse plugin for JBI artifacts development and administration
Docbook based documentation
Brand new website & logo

Complete release note will be available on the PEtALS Website.

PEtALS last week releases

2007-08-20T14:19:00+00:00

We have done some releases last week :

1. petals-standalone 1.4 :
    - Integration of a faster message transporter (Dream based)
    - Load balancing
    - Robustness
    - and of course several bug fixes and code optimization

2. petals-component-framework 2.0 :
    - This framework replaces the Component Development Kit (also known as CDK). It allows developers to quickly create powerful JBI components.

3. petals-bc-soap 2.0 :
    - Based on the petals-component-framework.
    - WS security
    - WS notification

Zip archives and documentation are available for download on the PEtALS downloads page.

Road to PEtALS 2.0

2007-07-10T06:45:37+00:00

PEtALS 2.0 is on the way. The beta version will be out in few weeks with cool features :

Eclipse plugin for development, test and integration
Multi-transporter with Dream for synchronous communication and Joram for asynchronous communication
RMI client for direct access to the bus API
UDDI registry Service Engine
EIP Service Engine
Enhanced SOAP Binding Component
Component Development Kit 2.0
JBOSS integration
Failure management / load balancing
Large deployment with Fractal Deployment Framework
Performance optimisations
Enhancements in monitoring tool
New docbook documentation

PEtALS Azalee Pack

2007-06-01T18:57:03+00:00

The PEtALS Azalée Pack is finally out. It includes all the latest stable versions of project artefacts.
You can download it here and get release note here.

Technorati Tags open,source,petals,jbi,soa,esb,webservices

PEtALS community news - May

2007-05-16T16:47:13+00:00

PEtALS news #1, 2007 May 16th

The PEtALS community is growing. Thanks to everyone for the interest you give to the project. Here is the first newsletter dedicated to this great project...

Releases and more

Core release 1.3 has been delayed and is now planned by the end of the month. Finally, we will release what we call a PEtALS Pack. This pack includes all the latest stable versions of PEtALS modules.
We have especially worked on :

New fractal (A component framework) architecture

Add static JNDI configuration : You can now define you PEtALS network topology
Lot of refactoring
Stability and bug fixes

A new component is available on the objectweb forge : The FTP binding component.
CDK 1.3 has been released on April the 25th 2007. It includes new configuration features through JMX during component installation.

More information on the future release note...

Main developments

Marie Sauvage (eBM WebSourcing) is working on the next version of the web administration tool. It will include lot of features to manage and administrate all the platform through a nice interface.
Nicolas Salatge (eBM WebSourcing) who has joined the developers team since a couple of months, has just completed the new PEtALS 'Fractalization'. Most of PEtALS modules are now Fractal components.
Dong Zhao has developped an OSGI version of PEtALS. This will allow to run PEtALS on any OSGI implementation (JOnAS5 and more...)
An eclipse plugin is under validation process. It will be available soon.
We are improving the CDK features again and again
Guillaume Decarnin (Openwide) is working on csv, xquare and forward components. These components will be soon based on the new CDK.

Documentation

Each module will soon have its own mini site (maven generated) in replacement of the wiki pages which are a little boring...
We are also working on a new user guide based on DocBook tools.

Others

A flash version of the travel agency demo of available here.
Artefacts are now available to the maven community on the objectweb maven repository http://maven.objectweb.org

Please do not hesitate to send your comments, ideas, and more...

Technorati Tags news,petals

PEtALS community news - May

2007-05-16T16:47:13+00:00

PEtALS news #1, 2007 May 16th

The PEtALS community is growing. Thanks to everyone for the interest you give to the project. Here is the first newsletter dedicated to this great project...

Releases and more

Core release 1.3 has been delayed and is now planned by the end of the month. Finally, we will release what we call a PEtALS Pack. This pack includes all the latest stable versions of PEtALS modules.
We have especially worked on :

New fractal (A component framework) architecture

Add static JNDI configuration : You can now define you PEtALS network topology
Lot of refactoring
Stability and bug fixes

A new component is available on the objectweb forge : The FTP binding component.
CDK 1.3 has been released on April the 25th 2007. It includes new configuration features through JMX during component installation.

More information on the future release note...

Main developments

Marie Sauvage (eBM WebSourcing) is working on the next version of the web administration tool. It will include lot of features to manage and administrate all the platform through a nice interface.
Nicolas Salatge (eBM WebSourcing) who has joined the developers team since a couple of months, has just completed the new PEtALS 'Fractalization'. Most of PEtALS modules are now Fractal components.
Dong Zhao has developped an OSGI version of PEtALS. This will allow to run PEtALS on any OSGI implementation (JOnAS5 and more...)
An eclipse plugin is under validation process. It will be available soon.
We are improving the CDK features again and again
Guillaume Decarnin (Openwide) is working on csv, xquare and forward components. These components will be soon based on the new CDK.

Documentation

Each module will soon have its own mini site (maven generated) in replacement of the wiki pages which are a little boring...
We are also working on a new user guide based on DocBook tools.

Others

A flash version of the travel agency demo of available here.
Artefacts are now available to the maven community on the objectweb maven repository http://maven.objectweb.org

Please do not hesitate to send your comments, ideas, and more...

Technorati Tags news,petals

3G+ sur ubuntu/opensuse

2007-04-20T15:04:13+00:00

Nous avons reçu une carte 3G+, cette dernière va remplacer la carte 3G.

En quelques mots: la 3G+ est basée sur la technologie HSDPA (High Speed Downlink Packet Access), la 3G+ est une évolution technologique du réseau 3G, cela permet d'augmenter les débits de navigation et de téléchargement.

Il n'y a pas de grandes différences avec la configuration d'une carte 3G simple.

La différence se situe au niveau driver installé par le système, donc cela influe sur le nom du périphérique.

Extrait du fichier messages
# tail -10 /var/log/messages:

Apr 20 15:57:10 test-laptop kernel: [16923.068000] pccard: CardBus card inserted into slot 0
Apr 20 15:57:11 test-laptop kernel: [16923.536000] Initializing Nozomi driver 2.1 (build date: Apr 15 2007 05:40:45)
Apr 20 15:57:11 test-laptop kernel: [16923.540000] nozomi 0000:04:00.0: Card type is: 2048
Apr 20 15:57:11 test-laptop kernel: [16923.540000] PCI: Enabling device 0000:04:00.0 (0000 -> 0002)
Apr 20 15:57:11 test-laptop kernel: [16923.540000] ACPI: PCI Interrupt 0000:04:00.0[A] -> GSI 19 (level, low) -> IRQ 19
Apr 20 15:57:11 test-laptop kernel: [16923.540000] nozomi 0000:04:00.0: Nozomi driver nozomi_tty
Apr 20 15:57:11 test-laptop kernel: [16923.540000] nozomi 0000:04:00.0: Version of card: 3
Apr 20 15:57:11 test-laptop kernel: [16923.540000] nozomi 0000:04:00.0: Initialization OK!

Ici, nous voyons bien que notre système a installé le driver nozomi, il faudra donc mettre /dev/noz0 pour le nom du périphérique du

modem.

En Root :

# vim /etc/wvdial.conf

-------------------------------------------------------------------------------

[Dialer SFR]
Modem = /dev/noz0
Baud = 460800
FLOWCONTROL= NOFLOW
Init1 = ATZ
Init2 = AT&F&D2&C1S0=0
Init3 = AT+CGDCONT=1,"IP","websfr"
Phone = *99***1#
Username = vodafone
Password = vodafone
Ask Password = 0
Dial Command = ATD
Stupid Mode = 1
Idle Seconds = 3000
Auto DNS = 1

--------------------------------------------------------------------------------
Enregistrer puis quitter.

Lancer la connexion:

Toujours en Root:

# wvdial SFR

Creating fully compatible JBI components

2007-04-10T17:05:48+00:00

As JBI container developers (PEtALS), we have created a framework which allows developers to easily create JBI components.

This Component Development Kit (also called PEtALS CDK) is based on the JBI specification and allows to create components which are 100% compatible with the JBI specification. In other words, you can use the CDK to create components that can be installed on all JBI implementations.

Note that most of the PEtALS components (Service Engines and Binding Components) are based on this CDK.
An online documentation is available on the projet wiki here and you can download the CDK here.

Technorati Tags petals,jbi

Creating fully compatible JBI components

2007-04-10T17:05:48+00:00

Carte 3G pcmcia sous Ubuntu/Opensuse

2007-04-04T07:11:18+00:00

Installer une Carte 3G pcmcia
sous Ubuntu/Opensuse

Quelques conseils pour faire fonctionner votre carte 3G (vodafone) PCMCIA sous Ubuntu ou sous Opensuse.

J'ai testé cette carte 3G sous Ubuntu 6.10 et Opensuse 10.2 .

Pour un meilleur résultat, j'ai désactivé dans le bios les ports que je n'utilise pas (ports com), cela me faisait un conflit d'IRQ avec ma carte 3G.
Vérifier la présence du programme wvdial (installé par défaut sur toutes les distri) qui permet de créer la connexion modem.

Sous Root taper "wvdial" si vous n'avez pas de réponse installer le parquet sinon passer au fichier de configuration de wvdial.

Toujours sous Root :

# vim /etc/wvdial.conf

Effacer l'intégralité du fichier (si vous n'avez pas déjà créé une connexion), puis copier cela:

-------------------------------------------------------------------------------

[Dialer SFR]
Modem = /dev/ttyS0
Baud = 460800
FLOWCONTROL= NOFLOW
Init1 = ATZ
Init2 = AT&F&D2&C1S0=0
Init3 = AT+CGDCONT=1,"IP","websfr"
Phone = *99***1#
Username = vodafone
Password = vodafone
Ask Password = 0
Dial Command = ATD
Stupid Mode = 1
Idle Seconds = 3000
Auto DNS = 1

--------------------------------------------------------------------------------
Enregistrer puis quitter.

* Ceci est la configuration pour l'accès au réseau SFR.

Ensuite, mettre la carte 3G dans le port PCMCIA, au bout de quelques secondes
si tout va bien la carte devrait être détectée.
Nous allons le vérifier en faisant :

# tail -10 /var/log/messages

...............

Apr 3 16:42:47 hostname kernel: pccard: PCMCIA card inserted into slot 0
Apr 3 16:42:47 hostname kernel: pcmcia: registering new device pcmcia0.0
Apr 3 16:42:47 hostname kernel: 0.0: ttyS0 at I/O 0x3f8 (irq = 3) is a
16550A
Apr 3 16:42:47 hostname kernel: pcmcia: registering new device pcmcia0.1

.................

Nous voyons bien que la carte s'est installée sur "ttyS0"
( modifier la ligne 2 du fichier "wvdial.conf" si nécessaire)

un voyant devrait clignoter sur la carte :

-clignotement vert un réseau gprs est détecté
-clignotement bleu un réseau 3G est détecté

Maintenant, toujours en Root, il suffit simplement de lancer la connexion:

# wvdial SFR

Résultat:

--> WvDial: Internet dialer version 1.54.0
--> Initializing modem.
--> Sending: ATZ
ATZ
OK
--> Sending: AT&F&D2&C1S0=0
AT&F&D2&C1S0=0
OK
--> Sending: AT+CGDCONT=1,"IP","websfr"
AT+CGDCONT=1,"IP","websfr"
OK
--> Modem initialized.
--> Idle Seconds = 3000, disabling automatic reconnect.
--> Sending: ATD*99***1#
--> Waiting for carrier.
ATD*99***1#
CONNECT 57600
--> Carrier detected. Starting PPP immediately.
--> Starting pppd at Tue Apr 3 16:52:00 2007
--> pid of pppd: 21251
--> Using interface ppp0
--> pppd: Phone
--> pppd: Phone
--> pppd: Phone
--> pppd: Phone
--> pppd: Phone
--> pppd: Phone
--> local IP address 10.162.132.126
--> pppd: Phone
--> remote IP address 10.64.64.64
--> pppd: Phone
--> primary DNS address 172.20.2.10
--> pppd: Phone
--> secondary DNS address 172.20.2.39
--> pppd: Phone
--> Script /etc/ppp/ip-up run successful
--> Default route Ok.

La connexion est établie.