ess

New m-orchestra mini-album A Blessing out today

What better time for some spooky music than Halloween week? And so today I am pleased to say the new m-orchestra mini-album A Blessing has been released for your listening delight! It features seven tracks, including the two singles that...




ess

Michigan Democrats’ top priority has been special business favors

Party platform calls corporate welfare ‘unsustainable,’ but its policies are a different story




ess

What is an "open source business"?

Paul recently wrote a great article on what it really means to be an "open source business." Its now posted on SDTimes! Read it and you'll be able to tell the fakes apart :-).




ess

Growing the WSO2 business

I wrote a blog on the WSO2 Corporate Blog on growing WSO2. Check it out!




ess

API Management: The missing link for SOA success

Nearly 2 years ago I tweeted:



Well, unfortunately, I had it a bit wrong.

APIs and service do have a very direct and 1-1 relationship: an API is the interface of a service. However, what is different is that one's about the implementation and is focused on the provider, and the other is about using the functionality and is focused on the consumer. The service of course is what matters to the provider and API is what matters to the consumer.

So its clearly more than just a new name.

Services: If you build it will they come?

One of the most common anti-patterns of SOA is the one service - one client pattern. That's when the developer who wrote the service also wrote its only client. In that case there's no sharing, no common data, no common authentication and no reuse of any kind. The number one reason for SOA (improving productivity by reusing functionality as services) is gone. Its simply client-server at the cost of having to use interoperable formats like XML, JSON, XML Schema, WSDL and SOAP. 

There are two primary reasons for this pattern being so prevalent: first is due to a management failure whereby everyone is required to create services for whatever they do because that's the new "blessed way". There's no architectural vision driving proper factoring. Instead its each person or at least each team for themselves. The resulting services are only really usable for that one scenario - so no wonder no one else uses them!

Writing services that can service many users requires careful design and thinking and willingness to invest in the common good. That's against human intuition and something that will happen only if its properly guided and incentivized. The cost of writing common services must be paid by someone and will not happen by itself.

That's in effect the second reason why this anti-pattern exists: the infrastructure in place for SOA does not support or encourage reuse. Even if you had a service that is reusable how do you find out how well it works? How do you know how many people are using it? Do you know what time of day they use it most? Do you know which operations of your service get hit the hardest? Next, how do others even find out you wrote a service and it may do what they need? 

SOA Governance (for which WSO2 has an excellent product: WSO2 Governance Registry) is not focused on encouraging service reuse but rather on governing the creation and management of services. The SOA world has lacked a solution for making it easy to help people discover available services and to manage and monitor their consumption. 

API Management

What's an API? Its the interface to a service. Simple. In other words, if you don't have any services, you have no APIs to expose and manage.

API Management is about managing the entire lifecycle of APIs. This involves someone who publishes the interface of a service into a store of some kind. Next it involves developers who browse the store to find APIs they care about and get access to them (typically by acquiring an access token of some sort) and then the developers using those keys to program accesses to the service via its interface.

Why is this important? In my opinion, API Management is to SOA what Amazon EC2 is to Virtualization. Of course virtualization has been around for a long time, but EC2 changed the game by making it trivially simple for someone to get a VM. It brought self service, serendipitous consumption, and elasticity to virtualization. Similarly, API Management brings self service & serendipitous consumption by allowing developers to discover, try and use services without requiring any type of "management approval". It allows consumers to not have to worry about scaling - they just indicate the desired SLA (typically in the form of a subscription plan) and its up to the provider to make it work right. 

API Management & SOA are married at the hip

If you have an SOA strategy in your organization but don't have an API Management plan then you are doomed to failure. Notice that I didn't even talk about externally exposing APIs- even internal service consumption should be managed through an API Management system so that everyone has clear visibility into who's using what service and how much is used when. Its patently obvious why external exposition of services requires API Management.

Chris Haddad, WSO2's VP of Technology Evangelism, recently wrote a superb whitepaper that discusses and explain the connection between SOA and API Management. Check out Promoting service reuse within your enterprise and maximizing SOA success and I can guarantee you will leave enlightened.

In May this year, a blog on highscalability.com talked about how "Startups Are Creating A New System Of The World For IT". In that the author talked about open source as the foundation of this new system and SOA as the load bearing walls of the new IT landscape. I will take it to the next level and say that API Management is the roof of the new IT house.

WSO2 API Manager

We recently introduced an API Management product: WSO2 API Manager. This product comes with an application for API Providers to create and manage APIs, a store application for API Developers to discover and consume APIs and a gateway to route API traffic through. Of course all parts of the product can be scaled horizontally to deal with massive loads. The WSO2 API Manager can be deployed either for internal consumption, external consumption or both. As with any other WSO2 product, this too is 100% open source. After you read Chris' whitepaper download this product and sit it next to your SOA infrastructure (whether its from us or not) and see what happens!





ess

WordPress, el mejor amigo para tu emprendimiento

En la meetup de abril en Valladolid, descubrimos por qué WordPress es el mejor amigo para tu emprendimiento. Mauricio Gelves nos contó […]




ess

Y tú, ¿para qué usas WordPress?

Una vez más nos encontramos en la meetup de WordPress Valladolid para compartir qué usos le damos a nuestro sistema de gestión […]




ess

Introduction to WSO2 Message Broker


Introduction to WSO2 Message Broker

Introduction
WSO2 Message Broker (MB) is a new Open Source project and product from WSO2 that provides messaging functionality within the WSO2 Carbon platform and to other clients in various languages. It works either standalone or in conjunction with products and components such as the WSO2 ESB and WSO2 Complex Event Processing Server.

MB is based on the Apache Qpid/Java project (http://qpid.apache.org). From Apache Qpid, MB gets core support for the AMQP protocol and JMS API. On top of that WSO2 has added support for Amazon SQS APIs and WS-Eventing support.

Understanding how the MB broker fits into Enterprise Architecture
The Message Broker provides three main capabilities into an overall Enterprise Architecture:
·               A queueing/persistent message facility
·               An event distribution (pub/sub) model
·               An intermediary where multiple systems can connect irrespective of the direction of messages.

To give some concrete examples of these benefits, here are some scenarios:
1)   In the WSO2 ESB, a common pattern is to persist the message from an incoming HTTP request into a persistent message queue, and then process onbound from there. MB can provide the persistent queue.
2)   The WSO2 ESB already has an event distribution model and eventing support, but the QPid-based broker provides higher performance as well as supporting the JMS API.
3)   For example, you may wish to send messages from outside a firewall to a server inside. You could connect an ESB or Service Host within the firewall to a Message Broker running outside the firewall (for example on Amazon EC2). This model is used by the WSO2 Cloud Services Gateway.

Where does AMQP fit?

AMQP (www.amqp.org) is an open protocol for messaging. Whilst the AMQP protocol is still under development, it has released three stable releases (0-8, 0-9-1, and 0-10), with a 1.0 due during 2011. There are a number of implementations of the AMQP standard in production, including Apache Qpid (both Java and C++ versions), RabbitMQ, OpenAMQ and others.

WSO2 has been a member of the AMQP working group for several years, and we strongly support AMQP as the way to introduce interoperability and greater openness into the messaging space.

The Qpid broker supports a variety of clients on top of the AMQP protocol. The most useful of these for Carbon is the Java JMS 1.1 API, which provides a portable API as well as the main interface with the WSO2 ESB. In addition there are C# and other APIs. WSO2 MB also extends these with WS-Eventing and Amazon SQS APIs for interoperability using HTTP, REST and SOAP.

Installing the WSO2 MB

You can download the WSO2 MB Beta from:

Once you have downloaded and unzipped, simply switch to the install directory

            cd wso2mb-1.0.0-SNAPSHOT
            binwso2server.bat  [ON WINDOWS]
            bin/wso2server.sh [ON LINUX/MACOSX]

Let’s refer to the install directory as from now on.

You should see the server startup:
[2011-03-16 14:00:12,471]  INFO {org.wso2.carbon.server.Main} -  Initializing system...
[2011-03-16 14:00:12,840]  INFO {org.wso2.carbon.server.TomcatCarbonWebappDeployer} -  Deployed Carbon webapp: StandardEngine[Tomcat].StandardHost[defaulthost].StandardContext[/]
[2011-03-16 14:00:14,147]  INFO {org.wso2.carbon.atomikos.TransactionFactory} -  Starting Atomikos Transaction Manager 3.7.0
[2011-03-16 14:00:19,952]  INFO {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Starting WSO2 Carbon...
[2011-03-16 14:00:19,983]  INFO {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Operating System : Mac OS X 10.6.6, x86_64
[2011-03-16 14:00:19,984]  INFO {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Home        : /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
[2011-03-16 14:00:19,984]  INFO {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Version     : 1.6.0_24
[2011-03-16 14:00:19,985]  INFO {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java VM          : Java HotSpot(TM) 64-Bit Server VM 19.1-b02-334,Apple Inc.
[2011-03-16 14:00:19,985]  INFO {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Carbon Home      : /Users/paul/wso2/wso2mb-1.0.0-SNAPSHOT
[2011-03-16 14:00:19,985]  INFO {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Temp Dir    : /Users/paul/wso2/wso2mb-1.0.0-SNAPSHOT/tmp
[2011-03-16 14:00:19,986]  INFO {org.wso2.carbon.core.internal.CarbonCoreActivator} -  User             : paul, en-US, Europe/London
2011-03-16 14:00:12,471]  INFO {org.wso2.carbon.server.Main} -  Initializing system...

some logs deleted

[2011-03-16 14:00:41,691]  INFO {org.wso2.carbon.core.transports.http.HttpsTransportListener} -  HTTPS port       : 9443
[2011-03-16 14:00:41,691]  INFO {org.wso2.carbon.core.transports.http.HttpTransportListener} -  HTTP port        : 9763
[2011-03-16 14:00:42,422]  INFO {org.wso2.carbon.ui.internal.CarbonUIServiceComponent} -  Mgt Console URL  : https://192.168.1.100:9443/carbon/
[2011-03-16 14:00:42,499]  INFO {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -  Started Transport Listener Manager
[2011-03-16 14:00:42,500]  INFO {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -  Server           :  WSO2 MB -1.0.0-SNAPSHOT
[2011-03-16 14:00:42,506]  INFO {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -  WSO2 Carbon started in 27 sec
2011-03-16 14:00:12,471]  INFO {org.wso2.carbon.server.Main} -  Initializing system...

WSO2 Message Broker is installable in more ways for production systems. Typically it is either registered as a Linux Daemon or as a Windows Service – but for now we will stick with the command-line version for simplicity.

Once the server is running you can access the management console. Point your browser at:
            https://localhost:9443

Initially you will see a browser screen warning you about the certificates. Please tell your browser to continue (For a production server you would normally install a proper SSL/TLS certificate, but for initial install we generate a self-signed certificate that you need to agree to use).

Once you have accepted the certificate, you should see a screen like:


You can login using the default user/password which is admin/admin.

Once you login you should see the following screen:


Before we examine the admin console, lets first create a simple JMS client that will communicate with the server via AMQP on TCP/IP.

Getting Started with JMS
The Java Message Service (JMS) specification - http://www.oracle.com/technetwork/java/index-jsp-142945.html - is a specification for talking to message brokers. It is unfortunately poorly named: the word “service” implies this is an implementation, but JMS does not define an actual messaging service, instead just the API which is used to access JMS providers. “Java Messaging API” would more accurately express what JMS is. The result is that there are a variety of JMS providers, and they often have quite different approaches to their core model.

The WSO2 Message Broker is based on the Apache Qpid project (http://qpid.apache.org) and is a compliant implementation of the JMS specification, as well as various levels of the AMQP specification (0-8, 0-9-1, 0-10). 

To write completely standard portable JMS code, you need to use a JNDI provider to gain access to the JMS connection, queues, etc. In this example we will use a Qpid JNDI provider backed by a simple set of properties. This makes the overall system simple and highly portable.

Here is a sample JMS application that can be used to test access to the Message Broker.  You can find this code here:



First are some required imports.

import javax.jms.*;
import javax.naming.Context;
import javax.naming.InitialContext;
import java.util.Properties;

Next is a simple “main” class definition:

public class JMSExample {

public static void main(String[] args) {
       JMSExample producer = new JMSExample();
       producer.runTest();
}

      
private void runTest() {

Since this is just an example, we will place the complete logic in a try/catch block.

try {

Normally the JNDI is configured by a properties file, but you can also do it from an in-memory set of properties. To see a similar setup with a properties file, take a look at the ESB example below.  Here is a properties object to store the properties:

Properties properties = new Properties();

In order to bootstrap the JNDI entries for the connection factory and queue, we set name/value pairs into the simple properties object:                   

properties.put("connectionfactory.cf",
       "amqp://admin:admin@carbon/carbon?brokerlist='tcp://localhost:5672'");

The property name “connectionfactory.cf” denotes that we are creating an object of type ConnectionFactory with name “cf”. The value is a URL that is used to bootstrap the ConnectionFactory: this URL points to the AMQP broker. The syntax is broken up as follows:
       amqp://               Indicates this is an AMQP URL
       admin:admin@  This is the username/password
       carbon/carbon The client ID and virtual host
       ?                     separator for options
       brokerlist=’tcp://localhost:5672’          A list of broker URLs to use

For more information on this URL syntax please see:

The virtual host name is part of the definition in:
/repository/conf/qpid/etc/virtualhosts.xml

This file also defines aspects such as the maximum number of messages in a queue and the queue depth (maximum size in bytes of the queue).

Now we need to create a JNDI entry for the queue we are going to talk to:

properties.put("destination.samplequeue", "samplequeue; {create:always}");

The property name “destination.samplequeue” indicates creating a destination with a JNDI name of “samplequeue”. The property value “samplequeue; {create:always}” indicates a queue named “samplequeue” with an attribute which tells the broker to create the queue if it doesn’t exist.

These properties are specific to the particular JNDI implementation we are using, which is the Qpid “PropertiesFileInitialContextFactory”. So now we need to configure JNDI to use this implementation:
                     
                     
properties.put("java.naming.factory.initial", "org.apache.qpid.jndi.PropertiesFileInitialContextFactory");

Now we can do our JNDI lookups:

Context context = new InitialContext(properties);

ConnectionFactory connectionFactory =
(ConnectionFactory) context.lookup("cf");

Having “found” a JMS Connection Factory in the JNDI, we can now create a connection to the broker:

Connection connection = connectionFactory.createConnection();
connection.start();

And now we can create a JMS Session:

Session session = connection.createSession(false,
                                    Session.AUTO_ACKNOWLEDGE);

One more lookup from JNDI will lookup our queue:

Destination destination = (Destination) context
                                    .lookup("samplequeue");


Now we can create a Producer, and send a message:
                     
MessageProducer producer = session.createProducer(destination);
TextMessage outMessage = session.createTextMessage();
outMessage.setText("Hello World!");
producer.send(outMessage);

Of course, in real life you would most likely NOT now retrieve that same message from the same application, but for this example we will now retrieve the message:                      
MessageConsumer consumer = session.createConsumer(destination);
Message inMessage = consumer.receive();
System.out.println(((TextMessage)inMessage).getText());

And close up the connection and the initial context:
                     
connection.close();
context.close();
} catch (Exception exp) {
       exp.printStackTrace();
}

To try out this client you need the correct client JARs.

In the beta release you will find:
/jms-client-lib/geronimo-jms_1.1_spec-1.1.0.wso2v1.jar
/jms-client-lib/qpid-client-0.9.wso2v2.jar

You also need to reference
/lib/log4j-1.2.13.jar





Once you have those in your classpath you can run the program. You should see some simple output:

log4j:WARN No appenders could be found for logger (org.apache.qpid.jndi.PropertiesFileInitialContextFactory).
log4j:WARN Please initialize the log4j system properly.
Hello World!

If you got that far, congratulations!

In the next section we are going to look at using the ESB with the Message Broker.

There are two approaches for this:
1) If you are using the existing WSO2 ESB 3.0.1 or similar, you can deploy the MB client libraries and communicate using the network.

2) As of the next WSO2 ESB release (3.1.0) it will include the Qpid/MB features as part of the release and you can utilize the Message Broker/JMS runtime locally in the same JVM.

WSO2 MB and WSO2 ESB together
In this first instance we are going to get the WSO2 ESB and MB to work together.
Assuming that you already have the MB installed and running, you will first need to install the ESB and change the ports of the admin console so that they don’t clash. You can download WSO2 ESB 3.0.1 from:
            http://wso2.org/downloads/esb

The install procedure is similar: unzip the ESB, but don’t start it up yet. Let’s name (for this guide) the directory where you installed the ESB as .

First let’s edit the ports on which the ESB listens. (Alternatively you could do the same to the MB instead).

Edit the epositoryconfmgt-transports.xml

This file defines which ports the management console runs (HTTP and HTTPS).

Please change:

<transport name="http" class="org.wso2.carbon.server.transports.http.HttpTransport">
        <parameter name="port">9763</parameter>

to read:
<transport name="http" class="org.wso2.carbon.server.transports.http.HttpTransport">
        <parameter name="port">9764</parameter>

Similarly change the HTTPS port to be 9444.

Now the next step is to ensure that the ESB has the right drivers to talk to the MB. Copy the following JARs into the epositorycomponentslib directory:
/jms-client-lib/geronimo-jms_1.1_spec-1.1.0.wso2v1.jar
/jms-client-lib/qpid-client-0.9.wso2v2.jar


We also need to configure the JMS transport correctly. To do this we edit the axis2.xml file:
  epositoryconfaxis2.xml

This file has the JMS transport commented out. It also needs the settings updated to use the Qpid libraries. Change the file so that the JMS receiver and sender sections look like this:
  
       <transportReceiver name="jms" class="org.apache.axis2.transport.jms.JMSListener">
        <parameter name="myTopicConnectionFactory" locked="false">
         <parameter name="java.naming.factory.initial" locked="false">org.apache.qpid.jndi.PropertiesFileInitialContextFactory</parameter>
         <parameter name="java.naming.provider.url" locked="false">resources/jndi.properties</parameter>
         <parameter name="transport.jms.ConnectionFactoryJNDIName" locked="false">TopicConnectionFactory</parameter>
<parameter name="transport.jms.ConnectionFactoryType" locked="false">topic</parameter>
        </parameter>


        <parameter name="myQueueConnectionFactory" locked="false">
         <parameter name="java.naming.factory.initial" locked="false">org.apache.qpid.jndi.PropertiesFileInitialContextFactory</parameter>
         <parameter name="java.naming.provider.url" locked="false">resources/jndi.properties</parameter>
         <parameter name="transport.jms.ConnectionFactoryJNDIName" locked="false">QueueConnectionFactory</parameter>
<parameter name="transport.jms.ConnectionFactoryType" locked="false">queue</parameter>
        </parameter>


        <parameter name="default" locked="false">
         <parameter name="java.naming.factory.initial" locked="false">org.apache.qpid.jndi.PropertiesFileInitialContextFactory</parameter>
         <parameter name="java.naming.provider.url" locked="false">resources/jndi.properties</parameter>
         <parameter name="transport.jms.ConnectionFactoryJNDIName" locked="false">QueueConnectionFactory</parameter>
<parameter name="transport.jms.ConnectionFactoryType" locked="false">queue</parameter>
        </parameter>
    </transportReceiver>
You can find my copy of the edited axis2.xml here:

If you have looked through the JMS config you will notice it references a JNDI resource: resources/jndi.properties.

This is used to do the same thing the hard-coded properties we used above do – configure the local JNDI that the JMS client inside the ESB will use. In a future release of the ESB we expect to automatically configure this JNDI, but in the meantime, we can simply create a file in the /resources directory.




ess

Internet of Things - protocols and access keys

I've just read this article from Mark O'Neill on the 10 concerns for the Internet of Things. Mark brings up some very interesting aspects and concerns. I'd like to comment on two of those: protocols and access keys.

His primary concern is protocol proliferation. I agree this is an issue. Mark explicitly mentions CoAP, MQTT, AMQP and XMPP. Interestingly he doesn't mention HTTP, which I have found to be heavily used by devices, especially the new generation of Raspberry Pi based systems. Many Arduino's also use HTTP.

I will admit to a strong bias. I think that MQTT is the best of these protocols for IoT devices, with CoAP a distant second.

Let's get XMPP out of the way. I love XMPP. I think its a fantastic protocol. Do I want to create XML packets on my Arduino? Er... nope. Even on 32-bit controllers, there is still the network traffic to consider: suppose I'm using a GPRS connection and I have thousands of devices deployed: minimizing network traffic is important for cost and efficiency, and XMPP was not designed for that.

AMQP is not an appropriate protocol for IoT devices and was not designed for that. It is designed for "the efficient exchange of information within and between enterprises". It was certainly not designed for lightweight, non-persistent, non-transactional systems. To that end, my own system (WSO2) will be providing efficient bridging for AMQP and MQTT to enable lightweight systems to get their data into wider enterprise contexts. I also demonstrated HTTP to MQTT bridging with the WSO2 ESB at the MQTT Interop held last week at EclipseCon.

How about CoAP vs MQTT. Firstly, CoAP is more appropriate to compare to MQTT-SN. It is UDP only, and designed to emulate a RESTful model over UDP. My biggest concern with CoAP is this: most people don't actually understand REST - they understand HTTP. If I had a dollar for every time I've come across supposedly RESTful interfaces that are really HTTP interfaces, I'd be a rich man! 

Interestingly, despite MQTT having been around for 10 years, the Google Trend shows that it has only recently hit the public notice:
However, as you can see, it has quickly overtaken CoAP. In terms of traffic, it is a clear winner: every Facebook mobile app uses MQTT to communicate with the Facebook servers.

The other area I'd like to comment on is access keys. I agree this is a big issue, and that is the reason I've been working on using OAuth2 access keys with MQTT and IoT devices. I recently gave talks about this at FOSDEM, QCon London, and EclipseCon.  The EclipseCon talk also covered a set of wider security concerns and the slides are available here. OAuth2 and OpenID Connect are important standards that have got incredible traction in a short period of time. They have evolved out of 10+ years of trying to solve the distributed, federated identity and access control problems of the Internet. 

In my presentation I strongly argued that passwords are bad for users, but worse for devices. Tokens are the correct model, and the OAuth2 token is the best available token to use at this point. There was considerable interest in the MQTT interop session on standardizing the use of OAuth2 tokens with the protocol. 

My personal prediction is that we will see MQTT and HTTP become the most-used IoT protocols, and I strongly urge (and hope) that OAuth2 tokens will become the de-facto model across both of these.







ess

L’Argentine sur le chemin de la liberté derrière le « professeur Milei »

JAVIER MILEI, UN AN APRES (1/7). Depuis l'arrivee de l'economiste a la presidence, le pays a enregistre son premier excedent budgetaire et l'inflation, qui atteignait 25 % par mois, est tombee a 2,7 %.




ess

Marc Fesneau : « Que chacun cesse d’avoir en ligne de mire son agenda personnel en vue de 2027 »

INTERVIEW. Pour le patron du groupe MoDem a l'Assemblee, il faut d'urgence sortir du bal des ego qui mine le << socle commun >> de Barnier et << etre utile aux Francais >>.




ess

Jean-Marie Le Pen hospitalisé à la suite d’un état de faiblesse général

Le fondateur du Front national, age de 96 ans et qui a mis un terme a sa vie politique, est hospitalise afin de passer plusieurs examens, par << souci de securite >>.




ess

Impact of CPU-bound Processes on IP Forwarding of Linux and Windows XP

These days, commodity-off-the-shelf (COTS) hardware and software are used to build high-end and powerful workstations and servers to be deployed in today's local area networks of private homes and small- to medium-sized business. Typically, these servers are multipurpose and shared - running networking functionalities involving IP packet forwarding in addition to other CPU intensive applications. In this paper we study and investigate the impact of running CPU-bound applications on the performance of IP packet forwarding. We measure and compare the impact and performance for the two operating systems of choice for home and small-business users, namely Linux and Windows XP. The performance is studied in terms of key performance metrics which include throughput, packet loss, round-trip delay, and CPU availability. For our measurements, we consider today's typical home network hosts of modern processors and Gigabit network cards. We also consider different configuration setups and utilize open-source tools to generate relatively high traffic rates. Our empirical results show that Linux exhibits superior performance over Windows XP in terms of IP forwarding performance. Results also show that, unlike Windows XP, the IP forwarding performance of Linux is not significantly impacted by running CPU-bound applications.




ess

Nabuco - Two Decades of Document Processing in Latin America

This paper reports on the Joaquim Nabuco Project, a pioneering work in Latin America on document digitalization, enhancement, compression, indexing, retrieval and network transmission of historical document images.




ess

Developing a Mobile Collaborative Tool for Business Continuity Management

We describe the design of a mobile collaborative tool that helps teams managing critical computing infrastructures in organizations, a task that is usually designated Business Continuity Management. The design process started with a requirements definition phase based on interviews with professional teams. The elicited requirements highlight four main concerns: collaboration support, knowledge management, team performance, and situation awareness. Based on these concerns, we developed a data model and tool supporting the collaborative update of Situation Matrixes. The matrixes aim to provide an integrated view of the operational and contextual conditions that frame critical events and inform the operators' responses to events. The paper provides results from our preliminary experiments with Situation Matrixes.




ess

Let Me Tell You a Story - On How to Build Process Models

Process Modeling has been a very active research topic for the last decades. One of its main issues is the externalization of knowledge and its acquisition for further use, as this remains deeply related to the quality of the resulting process models produced by this task. This paper presents a method and a graphical supporting tool for process elicitation and modeling, combining the Group Storytelling technique with the advances of Text Mining and Natural Language Processing. The implemented tool extends its previous versions with several functionalities to facilitate group story telling by the users, as well as to improve the results of the acquired process model from the stories.




ess

Leveraging Web 2.0 in New Product Development: Lessons Learned from a Cross-company Study

The paper explores the application of Web 2.0 technologies to support product development efforts in a global, virtual and cross-functional setting. It analyses the dichotomy between the prevailing hierarchical structure of CAD/PLM/PDM systems and the principles of the Social Web under the light of the emerging product development trends. Further it introduces the concept of Engineering 2.0, intended as a more bottom up and lightweight knowledge sharing approach to support early stage design decisions within virtual and cross-functional product development teams. The lessons learned collected from a cross-company study highlight how to further developblogs, wikis, forums and tags for the benefit of new product development teams, highlighting opportunities, challenges and no-go areas.




ess

Au moins 22 personnes tuées dans des frappes au Liban et à Gaza, et le cessez-le-feu au point mort

Au moins 22 personnes tuées dans des frappes au Liban et à Gaza, et le cessez-le-feu au point mort




ess

An efficient edge swap mechanism for enhancement of robustness in scale-free networks in healthcare systems

This paper presents a sequential edge swap (SQES) mechanism to design a robust network for a healthcare system utilising energy and communication range of nodes. Two operations: sequential degree difference operation (SQDDO) and sequential angle sum operation (SQASO) are performed to enhance the robustness of network. With equivalent degrees of nodes from the network's centre to its periphery, these operations build a robust network structure. Disaster attacks that have a substantial impact on the network are carried out using the network information. To identify a link between the malicious and disaster attacks, the Pearson coefficient is employed. SQES creates a robust network structure as a single objective optimisation solution by changing the connections of nodes based on the positive correlation of these attacks. SQES beats the current methods, according to simulation results. When compared to hill-climbing algorithm, simulated annealing, and ROSE, respectively, the robustness of SQES is improved by roughly 26%, 19% and 12%.








ess

Premiers résultats de la grande enquête nationale « Contexte des sexualités en France 2023 - Inserm (salle de presse)

  1. Premiers résultats de la grande enquête nationale « Contexte des sexualités en France 2023  Inserm (salle de presse)
  2. La sexualité des Français a connu de gros changements en dix ans  L'Union
  3. Plus de partenaires, pratiques variées, numérique... Une grande étude dévoile les dessous de la sexualité...  BFMTV
  4. La vie sexuelle des Français, une journée spéciale sur France Inter, jeudi 14 novembre 2024  France Inter




ess

Senators make short work of listless Leafs in a flat Battle of Ontario - The Globe and Mail

  1. Senators make short work of listless Leafs in a flat Battle of Ontario  The Globe and Mail
  2. Tavares on Maple Leafs’ lifeless loss to Senators: ‘We should be disappointed’  Sportsnet.ca
  3. Ullmark records first shutout of season as Senators smother Maple Leafs  TSN
  4. TAKEAWAYS: Ottawa Senators draw first blood in Battle of Ontario  Ottawa Citizen
  5. Wednesday FTB: Lose to the Sens, why not?  Pension Plan Puppets





ess

Un été avec Jean d’Ormesson (4)

Ouvrons, cette fois, le livre C’est une chose étrange à la fin que le monde, roman que Jean d’Ormesson publié en 2010. On y trouve, comme toujours, des réflexions et des phrases magnifiques. Savourons-les cet été !

« J’ai beaucoup dormi. J’ai perdu beaucoup de temps. J’ai commis pas mal d’erreurs. Ce qu’il y avait de moins inutile sous le soleil, c’était de nous aimer les uns les autres. »

« Naître est toujours un bonheur. Il y a dans tout début une surprise et une attente qui seront peut-être déçues mais qui donnent au temps qui passe sa couleur et sa vigueur. »

« Nous sommes ...




ess

Un été avec Jean d’Ormesson (5)

Voici quelques extraits délicieux et profonds de C’est une chose étrange à la fin que le monde, roman de Jean d’Ormesson. Histoire de savourer quelques instants hors du temps, cet été !

« Ceux qui découvrent détruisent le système qui le précède. Ceux qui inventent de détruisent pas les oeuvres qui les précèdent. »

« Le passé s’éclaire à mesure qu’il s’éloigne. Ce n’est qu’à l’extrême fin du monde qu’une partie au moins des secrets de ses débuts obscurs pourront être révélés. »

« Ce monde est inépuisable, il n’existe que deux voies pour tenter d’en rendre compte : l’art et la science. »

« La poésie est ...




ess

Un été avec Jean d’Ormesson (6)

Tous les livres de Jean d’Ormesson doivent être lus et relus. L’auteur nous propose une littérature de vérité, d’empathie, de compréhension de ce que nous sommes. Voici quelques phrases picorées dans C’est une chose étrange à la fin que le monde.

« Chaque amoureux a dans l’amour le sentiment de posséder le monde entier à travers l’être aimé.

Toute la beauté de l’univers lui est enfin révélée. L’art et la littérature ne sont peut-être rien d’autre que la traduction sublimée d’une pulsion sexuelle. »

« Le monde inépuisable dont nous faisons partie, aucun ouvrage de génie, aucune théorie unifiée, aucune formule de ...




ess

Pakistan: retour progressif de l'électricité après une panne géante

Une gigantesque panne d'électricité a affecté lundi une large partie du Pakistan, dont ses plus grandes villes Lahore et Karachi, avant que les autorités n'annoncent en soirée le retour progressif du courant.

Les coupures d'électricité sont fréquentes au Pakistan, englué depuis des années dans de graves problèmes budgétaires et énergétiques, et dont le système de distribution est complexe et vétuste.

La panne a été causée par un dysfonctionnement survenu à 07H30 locales (02H30 GMT) à la suite de mesures d'économies prises sur le réseau.

"Nous espérons que le courant sera rétabli partout dans le pays d'ici ce (lundi) soir", a déclaré dans un communiqué vidéo le ministre de l'Energie, Khurram Dastagir Khan.

La nuit avançant, il a assuré sur Twitter que l'électricité commençait à être rétablie progressivement.

Le ministère a tweeté que le courant était revenu dans le centre d'Islamabad et à Gujranwala, à quelque 200 km au sud-est de la capitale.

M. Khan a également retweeté le message d'un usager qui se félicitait qu'il y ait à nouveau "de la lumière à Lahore", la deuxième ville la plus peuplée du pays, avec plus de 10 millions d'habitants.

La panne a été causée par une variation de la fréquence électrique sur le réseau national, au redémarrage des unités de production électrique lundi matin.

Ces unités sont temporairement éteintes la nuit en hiver pour économiser du carburant, a expliqué M. Khan à la presse.

La plupart des hôpitaux, industries et institutions gouvernementales sont équipées de générateurs. Mais les ménages et petits commerces n'ont souvent pas les moyens de s'offrir un tel équipement.

Dans le nord du Pakistan, les températures devaient tomber lundi soir en dessous de 0°. Le chauffage au gaz est le plus répandu, mais n'est pas non plus toujours très fiable, les délestages étant fréquents en raison d'une pénurie de gaz.

Les réseaux de téléphonie mobile ont été également perturbés par la panne, selon un tweet du régulateur pakistanais des télécoms.

L'économie pakistanaise est déjà chancelante avec une inflation galopante, une devise nationale - la roupie - en chute libre et des réserves de change au plus bas. Une telle coupure d'électricité ne fait qu'accroître la pression sur les petits commerces.

A Rawalpindi, ville voisine de la capitale, Muhammad Iftikhar Sheikh, 71 ans, un vendeur d'électroménager, a déploré ne pas pouvoir tester ses appareils devant les clients.

"Les clients n'achètent jamais sans essayer d'abord", pestait-il. Du coup, "on est tous assis là, à ne rien faire".

Dans les écoles, les cours ont souvent eu lieu dans la pénombre, pour celles ne disposant pas d'éclairage sur batterie.

A Karachi (sud), où les températures étaient plus élevées, un commerçant a indiqué à l'AFP craindre que son stock entier de produits laitiers ne soit perdu, sans réfrigération.

Et Khurrum Khan, un imprimeur de 39 ans, voyait les commandes s'empiler, sans pouvoir y répondre. Les problèmes d'électricité sont "une malédiction permanente dont nos gouvernements n'ont pas réussi à se débarrasser", regrettait-il.

Une panne similaire en janvier 2021 avait plongé l'essentiel de ce pays de 220 millions d'habitants dans le noir pendant plusieurs heures, après qu'un dysfonctionnement technique dans le sud eut déclenché une réaction en chaîne dans plusieurs centrales électriques.

Les coupures d'électricité sont un problème récurrent au Pakistan. Mais la situation s'est encore détériorée ces derniers mois, la situation financière dramatique du pays aggravant un peu plus ses difficultés d'approvisionnement énergétique.

Les ménages ont été touchés, mais l'industrie également, notamment le textile, qui représente environ 60% des exportations pakistanaises.




ess

La reine Mathilde et la princesse Élisabeth en voyage en Égypte du 14 au 16 mars

(Belga) La reine Mathilde et la princesse Élisabeth effectueront une visite de travail en Égypte du 14 au 16 mars, a indiqué le Palais royal dans un communiqué lundi soir.

"Cette visite marquera l'intérêt historique de la famille royale pour l'Égypte antique et rendra hommage à la reine Élisabeth, dont l'intérêt et la passion sont à l'origine de l'épanouissement de l'égyptologie en Belgique. La Reine et la Princesse visiteront plusieurs sites que la reine Élisabeth a elle-même visités lors de ses voyages en Égypte, notamment le tombeau de Toutankhamon. Au Caire, elles assisteront également au vernissage d'une exposition consacrée à la reine Élisabeth et à l'égyptologie belge", peut-on lire dans le communiqué. La Reine et la Princesse visiteront aussi différents sites archéologiques à Louxor et ses environs, où des institutions et des universités belges effectuent des fouilles. Cette visite de travail commémore par ailleurs plusieurs anniversaires célébrés en 2022 et 2023: le 200e anniversaire du déchiffrement des hiéroglyphes par Jean-François Champollion, les centenaires de la découverte du tombeau de Toutankhamon et de sa visite par la reine Élisabeth, le 125e anniversaire de l'émergence de l'égyptologie belge et le 75e anniversaire de la mort de l'égyptologue belge Jean Capart. (Belga)




ess

Crᅵation de 3000 postes de "gendarmes verts" : la fausse promesse de Darmanin

A chaque jour, une nouvelle annonce. Cet ᅵtᅵ, le ministre de l'Intᅵrieur, Gᅵrald Darmanin, a multipliᅵ les dᅵplacements sur le terrain et les annonces. Pour lutter contre les pyromanes ᅵ...




ess

An effectiveness analysis of enterprise financial risk management for cost control

This paper aims to analyse the effectiveness of cost control oriented enterprise financial risk management. Firstly, it analyses the importance of enterprise financial risk management. Secondly, the position of cost control in enterprise financial risk management was analysed. Cost control can be used to reduce the operating costs of enterprises, improve their profitability, and thus reduce the financial risks they face. Finally, a corporate financial risk management strategy is constructed from several aspects: establishing a sound risk management system, predicting and responding to various risks, optimising fund operation management, strengthening internal control, and enhancing employee risk awareness. The results show that after applying the proposed management strategy, the enterprise performs well in cost control oriented enterprise financial risk management, with a cost accounting accuracy of 95% and an audit system completeness of 90%. It can also help the enterprise develop emergency plans and provide comprehensive risk management strategy coverage.




ess

International Journal of Electronic Business




ess

The Impact of Physics Open Educational Resources (OER) on the Professional Development of Bhutanese Secondary School Physics Teachers




ess

Trends and development of workplace mindfulness for two decades: a bibliometric analysis

This systematic literature study employed bibliometric analysis to identify workplace mindfulness-related methods and practices in literature published from 2000 to 2020 by leading nations, institutions, journals, authors, and keywords. We also assessed the impact of workplace mindfulness research papers. Scopus analysis tools provided a literature report for 638 Scopus articles used in the study. Using VOSviewer, leading nations, institutions, articles, authors, journals, and keyword co-occurrence network maps were constructed. PRISMA was used to identify 56 publications to recognise workplace mindfulness literature's significant achievements. The research's main contribution is a deep review of neurological mindfulness and psychological measuring tools as workplace mindfulness tool categories. The study is the first to use the PRISMA technique to capture the essential contributions of workplace mindfulness papers from 2000 to 2020.




ess

Does brand association, brand attachment, and brand identification mediate the relationship between consumers' willingness to pay premium prices and social media marketing efforts?

This study investigates the effects of social media marketing efforts (SMME) on smartphone brand identification, attachment, association, and willingness to pay premium prices. A survey of 320 smartphone users who followed official social media handles managed by smartphone companies was conducted for this purpose. PLS-SEM was used to analyse the collected data. The findings demonstrated importance of SMME dimensions. According to the study's findings, the smartphone brand's SMMEs had significant impact on brand identification, brand association, and brand attachment. The results revealed that SMMEs had significant impact on willingness to pay the premium price. The findings also show that brand identification, attachment, and association mediated the relationship between SMMEs and willingness to pay a premium price. The findings of this study will be useful in developing social media marketing strategies for smartphones. This study demonstrates the use of social media marketing to promote mobile phones, particularly in emerging markets.




ess

What drives mobile game stickiness and in-game purchase intention? Based on the uses and gratifications theory

Despite the considerable growth potential predicted for mobile games, little research explored what motivates users to be sticky and make purchases in the mobile game context. Drawing on uses and gratifications theory (UGT), this study evaluates the influencing effects of players' characteristics (i.e., individual gratification and individual situation) and the mobile game structure (i.e., presence and governance) on players' mobile game behaviour (i.e., stickiness and purchase intention). Specifically, the model was extended with factors of the individual situation and governance. After surveying 439 samples, the research model was examined using the Partial least squares structural equation modelling (PLS-SEM) approach. The results indicate that stickiness is a crucial antecedent for users' in-game purchase intention. The individual situation plays an essential role in influencing user gratification, and individual gratification is the most vital criterion affecting stickiness. Finally, except for incentives, presence, and integration positively affect stickiness. This study provides further insights into both mobile game design and governance strategies.




ess

Enhanced TCP BBR performance in wireless mesh networks (WMNs) and next-generation high-speed 5G networks

TCP BBR is one of the most powerful congestion control algorithms. In this article, we provide a comprehensive review of BBR analysis, expanding on existing knowledge across various fronts. Utilising ns3 simulations, we evaluate BBR's performance under diverse conditions, generating graphical representations. Our findings reveal flaws in the probe's RTT phase duration estimation and unequal bandwidth sharing between BBR and CUBIC protocols. Specifically, we demonstrated that the probe's RTT phase duration estimation algorithm is flawed and that BBR and CUBIC generally do not share bandwidth equally. Towards the end of the article, we propose a new improved version of TCP BBR which minimises these problems of inequity in bandwidth sharing and corrects the inaccuracies of the two key parameters RTprop and cwnd. Consequently, the BBR' protocol maintains very good fairness with the Cubic protocol, with an index that is almost equal to 0.98, and an equity index over 0.95.




ess

Application of integrated image processing technology based on PCNN in online music symbol recognition training

To improve the effectiveness of online training for music education, it was investigated how to improve the pulse-coupled neural network in image processing for spectral image segmentation. The study proposes a two-scale descent method to achieve oblique spectral correction. Subsequently, a convolutional neural network was optimised using a two-channel feature fusion recognition network for music theory notation recognition. The results showed that this image segmentation method had the highest accuracy, close to 98%, and the accuracy of spectral tilt correction was also as high as 98.4%, which provided good image pre-processing results. When combined with the improved convolutional neural network, the average accuracy of music theory symbol recognition was about 97% and the highest score of music majors was improved by 16 points. This shows that the method can effectively improve the teaching effect of online training in music education and has certain practical value.




ess

International Journal of Wireless and Mobile Computing




ess

Logics alignment in agile software design processes

We propose that technological, service-dominant and design logics must interplay for an IT artefact to succeed. Based on data from a project aiming at a B2B platform for manufacturing small and medium enterprises (SMEs) in Europe, we explore these three logics in an agile software design context. By using an inductive approach, we theorise about what is needed for the alignment of the three logics. We contribute with a novel theoretical lens, the Framework for Adaptive Space. We offer insights into the importance of continuously reflecting on all three logics during the agile software design process to ensure mutual understanding among the agile team and the B2B platform end-users involved.




ess

Business intelligence in human management strategies during COVID-19

The spread of COVID-19 results in disruption, uncertainty, complexity, and ambiguity in all businesses. Employees help companies achieve their aims. To manage human resources sustainably, analyse organisational strategy. This thorough research study attempts to find previously unidentified challenges, cutting-edge techniques, and surprising decisions in human resource management outside of healthcare organisations during the COVID-19 pandemic. The narrative review examined corporate human resource management measures to mitigate COVID-19. Fifteen publications were selected for the study after removing duplicates and applying the inclusion and exclusion criteria. This article examines HR's COVID-19 response. Human resource management's response to economic and financial crises has been extensively studied, but the COVID-19 pandemic has not. This paper reviewed the literature to reach its goal. The results followed the AMO framework for human resource policies and procedures and the HR management system. This document suggests COVID-19 pandemic-related changes to human resource management system architecture, policies, and practises. The study created a COVID-19 pandemic human resource management framework based on the literature. The COVID-19 pandemic had several negative effects, including social and behavioural changes, economic shock, and organisational disruption.




ess

Access controllable multi-blockchain platform for enterprise R&D data management

In the era of big data, enterprises have accumulated a large amount of research and development data. Effective management of their precipitated data and safe sharing of data can improve the collaboration efficiency of research and development personnel, which has become the top priority of enterprise development. This paper proposes to use blockchain technology to assist the collaboration efficiency of enterprise R&D personnel. Firstly, the multi-chain blockchain platform is used to realise the data sharing of internal data of enterprise R&D data department, project internal data and enterprise data centre, and then the process of construction of multi-chain structure and data sharing is analysed. Finally, searchable encryption was introduced to achieve data retrieval and secure sharing, improving the collaboration efficiency of enterprise research and development personnel and maximising the value of data assets. Through the experimental verification, the multi-chain structure improves the collaboration efficiency of researchers and data security sharing.




ess

An empirical study on construction emergency disaster management and risk assessment in shield tunnel construction project with big data analysis

Emergency disaster management presents substantial risks and obstacles to shield tunnel building projects, particularly in the event of water leakage accidents. Contemporary water leak detection is critical for guaranteeing safety by reducing the likelihood of disasters and the severity of any resulting damages. However, it can be difficult. Deep learning models can analyse images taken inside the tunnel to look for signs of water damage. This study introduces a unique strategy that employs deep learning techniques, generative adversarial networks (GAN) with long short-term memory (LSTM) for water leakage detection i shield tunnel construction (WLD-STC) to conduct classification and prediction tasks on the massive image dataset. The results demonstrate that for identifying and analysing water leakage episodes during shield tunnel construction, the WLD-STC strategy using LSTM-based GAN networks outperformed other methods, particularly on huge data.




ess

Natural language processing-based machine learning psychological emotion analysis method

To achieve psychological and emotional analysis of massive internet chats, researchers have used statistical methods, machine learning, and neural networks to analyse the dynamic tendencies of texts dynamically. For long readers, the author first compares and explores the differences between the two psychoanalysis algorithms based on the emotion dictionary and machine learning for simple sentences, then studies the expansion algorithm of the emotion dictionary, and finally proposes an extended text psychoanalysis algorithm based on conditional random field. According to the experimental results, the mental dictionary's accuracy, recall, and F-score based on the cognitive understanding of each additional ten words were calculated. The optimisation decreased, and the memory and F-score improved. An <i>F</i>-value greater than 1, which is the most effective indicator for evaluating the effectiveness of a mental analysis problem, can better demonstrate that the algorithm is adaptive in the literature dictionary. It has been proven that this scheme can achieve good results in analysing emotional tendencies and has higher efficiency than ordinary weight-based psychological sentiment analysis algorithms.




ess

Dual network control system for bottom hole throttling pressure control based on RBF with big data computing

In the context of smart city development, the managed pressure drilling (MPD) drilling process faces many uncertainties, but the characteristics of the process are complex and require accurate wellbore pressure control. However, this process runs the risk of introducing un-modelled dynamics into the system. To this problem, this paper employs neural network control techniques to construct a dual-network system for throttle pressure control, the design encompasses both the controller and identifier components. The radial basis function (RBF) network and proportional features are connected in parallel in the controller structure, and the RBF network learning algorithm is used to train the identifier structure. The simulation results show that the actual wellbore pressure can quickly track the reference pressure value when the pressure setpoint changes. In addition, the controller based on neural network realises effective control, which enables the system to track the input target quickly and achieve stable convergence.




ess

Application of digital twin virtual design and BIM technology in intelligent building image processing

Intelligent digital virtual technology has become an indispensable part of modern construction, but there are also some problems in its practical application. Therefore, it is necessary to strengthen the design of intelligent building image processing systems from many aspects. Starting from image digital processing methods, this paper studies the digital twin virtual design scene construction method and related algorithms, converts the original image into a colour digital image through a greyscale algorithm, and then combines morphological knowledge and feature point extraction methods to complete the construction of a three-dimensional virtual environment. Finally, through the comparison of traditional image processing effects with smart building images based on digital twins and BIM technology, the results show that the optimised image processing results have higher clarity, sharper contrast, and a sensitivity increased by 5.84%, presenting better visual effects and solving the risk of misjudgement caused by inaccurate image recognition.




ess

Uncovering the keys to well-being: calling, mindfulness, and compassion among healthcare professionals in India amidst the post-COVID crisis

This study investigates the well-being of healthcare professionals in India, with a specific focus on the detrimental effects of the pandemic on their mental and physical health, including stress, burnout, and fatigue. This research examines the roles played by calling, mindfulness, and compassionate love as essential resources in promoting the well-being of healthcare professionals. Utilising structural equation modelling (SEM), the results reveal a significant cause and effect relationship between calling, mindfulness, and compassionate love and their influence on overall well-being. Furthermore, the study identifies a noteworthy parallel mediation effect, demonstrating that mindfulness and compassionate love serve as mediators in the relationship between calling and well-being. This research offers practitioners invaluable insights into the effective utilisation of mindfulness and compassionate love practices to enhance the overall well-being of healthcare professionals.