Apr 24, 2015

Java ME 8 and the Internet of Things

Because recently I started to work with Java mostly, I have read a lot of Java Documentation and a lot of news regarding Java. Following these I just found out that the Twitter uses Java and no Ruby anymore.

Last year I've worked a bit with Java ME. And I just read this: Internet of Thinks.

An overview and resource guide for developers new to embedded Java and IoT

Embedded systems are computer systems embedded into complete devices, whose dedicated functions reside within a larger mechanical or electrical system. Typically used in both industrial and consumer applications, embedded systems are entering the limelight with the Internet of Things (IoT). For developers just getting started with IoT, this article is a guide for learning more about the technologies that comprise Oracle's IoT platform: Java ME 8, Java ME Embedded, Java SE Embedded, and Java Embedded Suite.

In 1991, Mark Weiser, then head of Xerox's Palo Alto Research Center (PARC), attempted to capture the coming age of ubiquitous computing. Noting that "[t]he most profound technologies are those that disappear," Weiser described the various thought and technical experiments conducted by his colleagues at PARC, as they sought a new way of thinking about computers as embedded systems. Their vision, which might have seemed as fantastic as a hovercraft in 1991, is quickly becoming more commonplace today:
Sal awakens: she smells coffee. A few minutes ago her alarm clock, alerted by her restless rolling before waking, had quietly asked, "Coffee?," and she had mumbled, "Yes." "Yes" and "no" are the only words it knows [...]
At breakfast Sal reads the news. She still prefers the paper form, as do most people. She spots an interesting quote from a columnist in the business section. She wipes her pen over the newspaper's name, date, section, and page number and then circles the quote. The pen sends a message to the paper, which transmits the quote to her office [...]
Once Sal arrives at work, the foreview (in her car) helps her to quickly find a parking spot. As she walks into the building the machines in her office prepare to log her in ...

The embedded devices in Weiser's workday morning scenario use sensors to track a human user's interactions, and wireless connectivity to orchestrate a response: Sal's bed, alarm clock, and coffee maker are all connected to ensure that her first cup of coffee is underway before she rolls out of bed. For Weiser and his colleagues, this was calm computing; today we might call it the Internet of Things (IoT).

IoT overview

If there is one defining characteristic of IoT, it is interoperability, or the coordination of multiple devices. As observed in the above scenario, IoT uses sensors to collect data (in that case about Sal's interactions in her environment) and wireless connectivity to orchestrate a response. IoT is built on a confluence of technologies, including new and old hardware platforms, big data, cloud computing, and machine-to-machine (M2M) computing. APIs are the necessary glue, bringing all of these moving parts together.

Most importantly for Java developers, Java is key to many of the emerging IoT technologies already, and Oracle has committed to making Java a leading platform (if not the platform) for IoT. Java ME 8 breathes new life into Java's small device technology, extending it with a differentiated line of embedded Java platforms.
The next sections will introduce the technologies that comprise Oracle's IoT platform; follow the links to learn more about Java ME, Java ME 8, and the three embedded frameworks: Java ME Embedded, Java SE Embedded, and Java Embedded Suite.


Java ME

Java Micro Edition was originally intended to address the constraints associated with building applications for small devices. Based on Java SE, Java ME (or J2ME, as we knew it in 1999) was the platform for Java applications running on small devices with limited memory, display, and power capacity. Today it is used to develop embedded systems, ranging from industrial controls to mobile phones (especially feature phones), to set-top boxes and Blu-ray players.
Developers working in Java ME can choose from multiple configurations, profiles, and optional packages:
  • A configuration provides the most basic set of libraries and virtual machine capabilities for a broad range of devices.
  • A profile is a set of APIs that support a narrower range of devices.
  • An optional package is a set of technology-specific APIs. The Wireless Messaging API is one example. Check out Oracle's optional package primer to learn more about optional packages.

Configurations and profiles

In time two configurations have emerged: Connected Limited Device Configuration (CLDC) is the configuration for small devices, and Connected Device Configuration (CDC) is the configuration for more capable mobile devices such as smartphones and set-top boxes.
Java ME profiles sit on top of configurations, defining higher-level APIs of use to particular applications. Mobile Information Device Profile (MIDP), for instance, sits on top of CLDC and provides user interface, networking, and persistent storage APIs. Applications that run in a CLDC/MIDP environment (such as games) are known as MIDlets.

Java ME 8

In late 2012, Oracle embarked on an ambitious project to deliver a major update of the Java ME platform standard. Two Java Specification Requests (JSRs) were designed to meet current market requirements for embedded devices and prepare Java ME for future Java platform specifications: JSR 360 (CLDC 8), an evolutionary update to CLDC 1.1.1, would bring the virtual machine, Java language, and libraries up to date with Java SE 8. JSR 361 (Java ME Embedded Profile/MEEP 8) would update Information Module Profile - Next Generation (IMP-NG).

CLDC 8 and MEEP 8

CLDC 8 is based on JSR 139 (CLDC 1.1) and aligns the core Java ME virtual machine, language support, libraries, and other features with Java SE 8:
  • The virtual machine has been updated to comply with version 2 of the JVM specification.
  • Newer Java SE language features such as generics, assertions, annotations, and try-with-resources are now supported.
  • New libraries such as Collections, NIO subset, and Logging API subset are now supported.
  • A consolidated and enhanced Generic Connection Framework for multi-protocol I/O is supported.
MEEP 8 updates the original IMP-NG specification to provide a powerful and flexible application environment for small embedded Java platforms. The specification builds on CLDC 8 with the following features:
  • A new, lightweight component and services model
  • Shared libraries
  • Multi-application concurrency, inter-application communication, and event system
  • Application management
  • API optionality to address low-footprint use cases

The long, strange life, death, and rebirth of Java

Java at 20: Where do we go from here?


 May 23, 1995 saw the fruits of a four-year project at Sun Microsystems called Java. The new language with a C-like syntax promised the ability to write once and run anywhere through the use of virtual machines that compiled the code on the native platform at runtime.

The project began in 1991 when a small group of Sun engineers called the "Green Team," led by James Gosling, began working on a language and networking system for the next generation of digital consumer devices and computers.

In the 20 years since its launch, Java has exploded in use, been the subject of lengthy litigation with Microsoft, grew and died on the desktop, moved to the server, then jumped to feature phones, only to have its lunch eaten by smartphones, fallen into such disarray that the Department of Homeland Security said not to use it, and is now enjoying a renaissance under the stewardship of Oracle.
What other programming language can claim such drama?

When the project began, Sun saw a collision of the computer industry and non-computer industry technologies like cell phones to stereo systems to railroads to whatever. Sun noticed that they were all, in some form or another, reinventing computer science.

"The unifying theme was networking," said Gosling, now chief software architect for Liquid Robotics. "When we looked at these companies, they were designing their own networking and doing a really bad job of it. A lot of it was predictable. They were repeating a number of experiments we'd had in computer science 30 years ago."

The problem was the consumer electronics people didn't take networking into account, like common APIs across multiple platforms, or code reuse. "There was essentially no software reuse. Everybody was reinventing everything over and over again. We were trying to get to a place where we had models to help them get out of that," said Gosling.

"I really think Java's future is in IoT. I'd like to see Oracle and partners focused on a complete end-to-end storage solution for Java, from devices through gateways to enterprise back-ends. Building that story and making a success of it will help cement the next 20 years for Java. Not only is that a massive opportunity for the industry, but also one I think Java can do quite well." - Mike Milinkovich, executive director of the Eclipse Foundation

Read more here: http://www.javaworld.com/article/2912380/java-platform/the-long-strange-life-death-and-rebirth-of-java.html

No more Security fixes for Java 7

Oracle to end publicly available security fixes for Java 7 this month

Users are advised to migrate to Java 8

Public updates for Java 7 -- including bug and security fixes -- will end this month, a situation that one security advocate says could impact millions of applications.

"As outlined in the Oracle JDK [Java Development Kit] Support Roadmap, after April 2015, Oracle will not post further updates of Java SE [Standard Edition] 7 to its public download sites," Oracle's Java SE Support Roadmapstates. "Customers who need continued access to critical bug fixes and security fixes as well as general maintenance for Java SE 7 or older versions can get long-term support through Oracle Java SE Support. The process of migrating users from Java 7 to Java 8 through the auto update feature is expected to take place after the January 2015 CPU release."

Oracle released Java SE 7 in July 2011; Java SE 8 was released in March 2014. Java, particularly on the client side, has been beset by security issues in recent years. But Oracle has taken many steps to address the issues and stressed that most of the problems dated back several years, before Oracle took over Java from Sun in 2010.

Still, the impact of Oracle's cessation of public updates could be severe, an official at security firm Waratek, believes. Oracle's "rapid" end-of-life schedule for Java versions is great for innovation and language evolution, Waratek CTO John Matthew Holt said in an emailed statement. "However, there is a dangerous tradeoff; now millions of Java 7 applications will have to defend themselves against code-level vulnerabilities without the benefit of future fixes." Holt advocates either upgrades to Java 8 or use of Java Run-time Application Self Protection (RASP) technologies (Waratek is a RASP vendor).

This week's security update from Oracle, meanwhile, marks the "proverbial 'end of the road' for Java 7 application security, Holt said. "After today, the only version of the Java Platform which will receive public security updates is Java 8.  This is huge news, and it is going to cause enormous headache and disruption to millions of application owners around the world."
Contacted Tuesday afternoon for a comment on the end of public updates for Java SE 7, by late evening Oracle had not yet responded.

The April 2015 Critical Patch Update released Tuesday by Oracle provides 98 new fixes for security issues across a wide range of product families, said Eric Maurice in an Oracle blog post. These range from Oracle Database to Oracle Fusion Middleware, Java SE, and MySQL. Fourteen of the security fixes are for Java SE.

This story, "Oracle to end publicly available security fixes for Java 7 this month" was originally published by InfoWorld.



Apr 21, 2015

Java - check if file exists

When you try to see if a file exists then you can use
File.exists()
as here:

  public int existsFile(){
            /**
             *  @author     Me
             *  @descr      This function check if the file exists
             */
            
            int x = 0;      //      0 - file doesn't exist
                            //      1 - file do exists 
            String name_path_file = "C:/temp/myFile.tmp";
            File fisier = new File(name_path_file);
            if(fisier.exists()){
                x = 1;
            }            
            return x;   

        }

Mar 31, 2015

MySQL Conference at Oslo

A couple of weeks ago I went to a MySQL Conference which has been kept in Lysaker, Oslo at ORACLE Office.

17 March 2015, Lysaker, Oslo

It was a database conference at Oracle building about MySQL and MySQL News and the rest.

They develop more InnoDB for a better transactional operations.

Replication for a better scalability.

Swedish Police uses MySQL; also, Facebook, Booking.com, Linkedin, CISCO and others.


They, I mean these two guys, brought infos about MEM (MySQL Enterprise Monitor). I have to admit that I didn't know about that.

And, also, they said something about MySQL Query Analiser.

MySQL has a developers team at Trondheim.


MEM (MySQL Enterprise Monitor)

MEM (MySQL Enterprise Monitor) works on Apache. It is a Java Application. To monitorize a
MySQL Server you need to put an agent on your Database Server.



HADOOP

I have to see what they did about this. (80% big data platform).


MAX 2 TB for MySQL

SQL and NoSQL access to data.


SSD optimization




DUMP and RESTORE

mysql> SET innodb_buffer_pool_dump_at_shutdown=ON;


Transportable TABLES

FLUSH date for EXPORT;

Optimizer
EXPLAIN (this is used at the beginning and is not so precise)
….
OPTIMISER ( this is used at the end of a query and it has a better presentation as a result)
EXPLAIN [FORMAT=____] FOR CONNECTION ;
SERVER-SIDE STATEMENT TIMEOUT;
SELECT M;

MySQL Fabric

This is for using more databases, using mirrors. This is helping us not to do manual work when one of the servers is down. :(
There is a farm of MySQL Servers and they work like a team.

I'll be back with documentation. Here I've put only a short sketch of mine made into Conference.