|By Jim Keogh||
|January 1, 2003 12:00 AM EST||
J2ME developers have long desired the opportunity to build sophisticated applications for the personal digital assistant (PDA) market, applications common to resource-rich desktop computers. One thing stood in their way: most PDAs lacked resources to efficiently execute those applications.
However, that's about to change with the introduction of ARM processor-based PDAs and the PDA Profile that's soon to be incorporated in SDKs and VMs.
Improvements in processor design have transformed new PDAs into a powerhouse platform capable of running sophisticated J2ME applications and clients of enterprise Java systems. New PDAs bring higher performance previously known only on desktop computers.
With performance and power barriers removed from the new PDA, a committee of the Java Community Process that included PalmSource, the software division of Palm, defined a new profile called the PDA Profile (PDAP) that introduces classes for building highly responsive J2ME applications.
PDAP is an extension of the Connected, Limited Device Configuration (CLDC) 1.1 and the Mobile Information Devices Profile (MIDP) 1.0. New PDAs powered by an enhanced processor are capable of running both MIDP applications and PDAP applications using a PDAP-enabled VM. There are two key features introduced with the PDAP: the capability to develop sophisticated graphical user interfaces for a PDAP application using the Abstract Windowing Toolkit (AWT - a subset of the J2SE AWT), and the capability to access a PDA's native personal information data. A PDAP application can access data managed by the PDA device's address book, calendar, and to-do list applications.
The New PDA
I use the term "new PDA" to describe the latest incarnation of a PDA, but that doesn't help you know if a PDA can run PDAP applications. A better definition of "new PDA" is to describe the footprint required to run a PDAP application.
A PDA must have a minimum of 1,080KB of memory: 500KB for CLDC and MIDP, 540KB for the PDAP user interface libraries, 20KB reserved for the PIM API, 10KB for the Generic Connection Framework, and another 10KB for the PDAP security model. Table 1 describes other hardware configurations that are required to run a PDAP application.
PDAP and MIDlets
A PDAP application is called a PDAlet, which is a variation of the MIDlet application model. Actually, a PDAlet is a MIDlet that uses the PDAlet API and follows the same principles used in a MIDlet and MIDlet suite.
There isn't a PDAlet class because a PDAlet is a conceptual entity that refers to the capabilities and requirements of a PDAlet. A PDAlet is created by defining a class that extends the MIDlet class. Think of it as an extension of a MIDlet; those rules that apply to a MIDlet also apply to a PDAlet.
Listing 1 shows an empty MIDlet and Listing 2 converts this empty MIDlet into an empty PDAlet by calling the getDefaultToolkit() method within the startApp() method. The default toolkit is a subset of AWT and is used to create a GUI for the PDAlet. The getDefaultToolkit() method makes the PDAP API available to the PDAlet.
Although many developers will use AWT components to build a GUI for their PDAP application, a GUI isn't required for a PDAlet. You can create a PDAlet without having a GUI by calling the Display.setCurrent(null) method within the startApp() method. The PDAlet is then placed in the active-without-UI state, which means the PDAlet is still active but the implementation determines what, if anything, is displayed on the screen.
The PDAlet Suite
A PDAlet suite's functionality is similar to a MIDlet suite's in that both are packages of PDAlets and MIDlets, respectively. Suites make it easy for the developer to group related PDAlets and MIDlets for deployment and installation.
A PDAlet suite is a bundle of PDAlets and MIDlets that's implemented simultaneously on a PDA. All PDAlets (and MIDlets if any) within a PDAlets suite are considered a group and must be installed and uninstalled as a group. Each PDAlet and MIDlet within the PDAlet suite must be listed in the PDAlet suite's manifest, which is also contained in the PDAlet suite.
Members of a PDAlet suite share the same resources from the host environment and share the same Java class instances, and run within the same JVM. This means if three PDAlets from the same PDAlet suite run the same class, only one instance of the class is created. A key benefit of the relationship between PDAlet suite members is that they share the same data, including persistent storage such as that used to store user preferences.
Sharing data among PDAlets exposes each PDAlet to data errors caused by concurrent read/write access to data. However, this risk is reduced because synchronization primitives on the PDAlet suite level restrict access to both volatile and persistent data.
Data cannot be shared between PDAlets that are from another PDAlet suite because the PDAlet suite name is used to identify data associated with the PDAlet suite. A PDAlet from a different PDAlet suite is considered an unreliable source.
A PDAlet suite is installed, executed, and removed by the application manager running on the device (the manufacturer of the PDA provides the application manager).
Once a PDAlet suite is installed, the application manager gives each member of the PDAlet suite access to JVM and CLDC classes. Likewise a PDAlet can access classes defined in the MIDP and PDAP to interact with the user interface, network, and persistent storage.
The application manager also makes the Java Archive File (JAR) file and the Java application descriptor file (JAD) available to members of the PDAlet suite. Note that the JAD file is optional.
All the files that are necessary to implement a PDAlet suite must be contained within a production package called a Java Archive File (JAR). These files include PDAlet classes, graphic images if required by a PDAlet, and the manifest file.
A PDAlet suite is created almost the same way you create a MIDlet suite except PDAlets are identified within the PDAlet suite's manifest using the PDAlet=<name> attribute, where name represents the name of the PDAlet class.
The manifest file contains a list of attributes and related definitions that are used by the application manager to install the files contained in the JAR onto the small computing device. There are 10 attributes that are defined in the manifest file; all but seven of these attributes are optional.
Table 2 lists attributes contained in a manifest file. Of these, the following attributes are required for every manifest file. Failure to include them causes the application manager to halt the installation of the JAR file.
Listing 3 is a manifest file that contains the minimum number of attributes. All these attributes are required for a PDAlet manifest. Create a manifest file as a text file with the .txt file extension using an editor. The manifest file's file extension is changed to .mf when the PDAlet suite is prepared for deployment.
Entries in the manifest are name:value pairs and can therefore appear in any order within the manifest file. Each pair must be terminated with a carriage return. Whitespace between the colon and the attribute value is ignored when the application manager reads the manifest file.
Let's step through the manifest file shown in Listing 3. The MIDlet-Name attribute specifies the name of the PDAlet suite. The MIDlet-Version and MIDlet-Vendor attributes identify the version number of the PDAlet suite and the company or person who provided it.
The MIDlet-n attribute and the PDAlet-n attribute contain information about each MIDlet and each PDAlet that is in the JAR file. The number of the MIDlet and PDAlet replaces the letter n. The MIDlet-n attribute and the PDAlet-n attribute can contain three values that describe the MIDlet/PDAlet. A comma separates each value.
The first value is the name of the MIDlet/PDAlet. Next is an optional value that specifies the icon that will be used with the MIDlet/PDAlet. The icon must be in the Portable Network Graphics (PNG) image format. The last value for the MIDlet/PDAlet attribute is the MIDlet class name. The application manager uses the class name to load the PDAlet.
The next MIDlet/PDAlet attribute is the MicroEdition-Profile, whose value is the J2ME profile that's required to run the PDAlet. In this example the PDAP-1.0 profile is required. And the last MIDlet/PDAlet attribute is the MicroEdition-Configuration, which identifies the J2ME configuration that's necessary to run the MIDlet/PDAlet.
Attributes can be listed in any order in the PDAlet manifest and may contain spaces. The PDAlet manifest cannot have the MIDlet-Jar-URL and MIDlet-Jar-Size attributes. Both these attributes are permitted in the MIDlet manifest.
A PDAlet suite can contain PDAlets and MIDlets, and both are listed in the manifest as illustrated in the previous example. Both a PDAlet and a MIDlet listed in the manifest can provide the same functionality except that the PDAlet uses the PDAP API and the MIDlet uses the MIDP API.
If the implementation doesn't support the PDAP API in the VM, both PDAlets and MIDlets in the PDAlet suite won't run. However, you can specify that a MIDlet should run in place of a PDAlet by assigning the same index number to a PDAlet and a MIDlet. The PDAlet runs if the implementation supports the PDAP API, otherwise the MIDlet runs.
Listing 4 illustrates this technique. Notice there are two poker programs in this manifest. The first is MIDlet-2 and is called poker. The other is PDAlet-2 and is called PDAPoker. Since MIDlet-2 and PDAlet-2 have the same index number, the PDAPoker is the preferred poker program if the device supports the PDAP API. The MIDlet-2 program is used if the device does not support the PDAP API.
It's critical that the numbering sequence of MIDlets and PDAlets remain sequential without duplication except to resolve preferences, as in the case of PDAlet-2. Although there are six programs in the manifest in Listing 4, only five programs are visible to the implementation. Only one program is visible per index number.
Both the PDAP 1.0 and CLDC 1.1 APIs must be present on the device to install and execute the PDAlet suite, because these values are specified in the MicroEdition-Profile and MicroEdition-Configuration attributes in the manifest. The MIDP 1.0 API is implied whenever you specify the PDAP 1.0 profile in the MicroEdition-Profile attribute. However, you can explicitly specify the MIDP 1.0 API and the PDAP 1.0 profile together by including the MIDP 1.0 in the MicroEdition-Profile attribute as shown here:
MicroEdition-Profile: PDAP-1.0 MIDP-1.0
A PDAlet suite that contains both MIDlets and PDAlets requires both the PDAP API- and the MIDP API-compatible VM to install and execute the PDAlet suite. However, there are times when you want the PDAlet suite to be installed and execute only the MIDlets within the PDAlet suite if the VM is only MIDP 1.0. In this situation, you can specify that the PDAP API is optional.
To specify that the PDAP API is optional to run the PDAlet use the MicroEdition-Profile-Opt manifest attribute as shown in the following code segment. The PDAlet suite will install and execute on a MIDP 1.0-only VM. Only MIDlet programs will be installed and executed. PDAlets are considered application-specific attributes and are not available for execution.
Java Application Descriptor File
Application management software uses a Java Application Descriptor File (JAD) to manage the PDAlet, and the JAD can be used by the PDAlet to configure specific attributes. You may include a JAD within the JAR file of a PDAlet suite as a way to pass parameters to a PDAlet without modifying the JAR file. A JAD file is also used to provide the application manager with additional content information about the JAR file to determine if the PDAlet suite can be implemented on the device.
A JAD file is similar to a manifest in that both contain attributes that are name:value pairs. Name:value pairs can appear in any order within the JAD file. There are six required system attributes for a JAD file, see below. A system attribute is an attribute that's defined in the J2ME specification. Table 3 contains a complete list of system attributes. All JAD files must have the .jad extension. Listing 5 illustrates a typical JAD file.
The JAD file shown in Listing 5 contains a few attributes that are also found in the manifest file. The first three attributes in the JAD are identical to attributes in the manifest file.
The MIDlet-Jar-URL attribute contains the URL of the JAR file, which in this example is called bestmidlet.jar. The last required attribute in the JAD file is the MIDlet-n and PDAlet-n attribute that defines a PDAlet and MIDlet of the PDAlet suite that's identical to the PDAlet-n and MIDlet-n attributes of the manifest. A MIDlet-n attribute is required for each MIDlet in the PDAlet suite, and a PDAlet-n attribute is required for each PDAlet in the PDAlet suite.
A word of caution: the values of the MIDlet-Name, MIDlet-Version, and MIDlet-Vendor attributes in the JAD file must match the same attributes in the manifest. If the values are different, the application manager uses the attribute of the JAD file. Failure to include these attributes in the JAD file will prevent the JAR file from loading into the device.
A developer can include application attributes in a JAD file. An application attribute is a name:value pair that contains a value unique to the application. Any name can be given to an application attribute as long as the name does not begin with MIDlet-, PDAlet-, or MicroEdition-.
Abstract Windowing Toolkit
The PDA profile uses common user interface elements of the Java Abstract Windowing Toolkit (AWT) as the user interface solution for PDAlets. These user interface elements are native to many PDAs that use the ARM processor.
The AWT used in the PDA profile is a subset of the J2SE AWT that's designed to utilize the limited display space and memory constraints found in a PDA. This subset contains all the features that you'll require when developing a PDA application.
A subset of AWT is used as the user interface API for two J2ME profiles: Personal Basis Profile (PBP) and Personal Profile (PP). Each is used for a targeted class of devices. As a point of reference, the PDAP AWT is a subset of the Personal Profile.
The PDA Profile subset contains support for all but the following features:
- Serialization of UI components
- Object cloning
- J2SE security model
- Buffered images
- Data transfer APIs
- Alpha composite image manipulation
PDAlets run on a variety of PDA devices, each having support for some set of graphical user interface elements. Fortunately for developers, PDA devices that run PDAP API-capable VMs must adhere to a minimum of GUI elements that enable you to design a PDAlet that can take advantage of these GUI elements.
Color choices for your PDAlet GUI might be limited to black and white since these are the only two colors that an implementation is required to support. Realistically, however, many implementations will support a variety of colors through the RGB constructor for the Color class. Therefore it's wise to test your PDAlet on as many implementations as possible to be assured that your color choices don't negatively impact your application.
You also need to be alerted to the fact that some implementations that support a broad color palette may not permit you to change the colors of standard GUI elements such as menus and title bars. However, this lack of support doesn't prevent you from calling methods to change the color of those elements. The implementation won't throw an error, but will simply ignore your request to change the color of the element.
In some PDAlets you may want to set your own cursor using the AWT Component class. While setting the cursor is commonplace in J2SE applications, you might not be able to do so using the PDAP API because some implementations may prohibit such settings. Attempts to set the cursor will cause a silent error. The implementation will continue to run your PDAlet, but ignore your request to change the cursor.
Avoid using a variety of fonts in your application's graphical user interface because they may not be supported by the implementation. The PDAP only requires support for Font.Plain. Support for other fonts is implementation dependent. You can't assume that a font other than Font.Plain is available unless your application is tailored to run on a specific implementation.
Another limitation of running a PDAlet is thread safety. The PDAP does not mandate that AWT be thread safe. Therefore, avoid concurrent access to GUI objects using different threads. However, you can use a system event thread to enable concurrent access by calling the static invokeLater() method and the invokeAndWait() methods of the EventQueue class.
AWT offers window management capabilities that enable you to instantiate frames, windows, and dialogs from anywhere in the PDAlet and then show them by calling appropriate methods. All PDAP implementations support multiple top-level windows that are visible at any given time.
However, there are window management limitations that restrict windowing. Only one top-level window (window, frame, or dialog classes) can be shown (seen by the user) and active (has input focus) at a time. Some implementations might permit multiple top-level windows to be shown and be active simultaneously.
Tip: The implementation determines the behavior of windowing for the application if your PDAlet does not make a top-level window visible.
Top-level windows may not be resizable by your PDAlet or by the user, and calls to the setSize() method are silently ignored. Therefore, you should assume that resizing is not available unless you're designing an application for a specific PDA that you know enables top-level windows to be resized.
Likewise, you should expect that the implementation might limit or prohibit the resizing of dialogs. Attempts to change the size of a dialog may result in a different size than the size you requested - or no change whatsoever. Implementations that prohibit resizing of dialogs will not notify your application that an attempt to resize has failed. Instead, they ignore your request to resize the dialog.
Always minimize the need to change the size of a dialog within your application. If you must change the dialog size, make sure you test those changes on all the implementations that will be running your application in order to determine the visual effect those changes have on the application's graphical user interface. Failure to do so might result in an unexpected GUI for your PDAlet.
Additional restrictions might apply to the location of dialogs on the screen. Some implementations may limit the location on the screen where you can display the dialog, and other implementations outrightly prohibit the application to determine where the dialog is displayed on the screen. And, as with other prohibitions discussed in this section, your PDAlet continues to run uninterrupted because your request for change is ignored by the implementation.
PDAP does not require that an implementation provide a means to display a title for a dialog. This means that calling the setTitle() method and getTitle() method have no effect on the dialog.
Frames also have many of the restrictions found in dialogs. You can expect that an implementation will support a one-sized frame that can't be resized by a user or an application. An attempt to size or resize a frame causes a silent error to occur without an error message being sent to your application.
Likewise, the location of a frame is determined by the implementation, not by the application or the user of the application. Frames also can't be iconified or titled. As with all the restrictions discussed in this section, an implementation may not have these restrictions.
Personal Information Management
A PDA device has native personal information management (PIM) data that's managed by personal information applications that run on the PDA device. The PDA profile requires that an implementation grant PDAlets access to PIM data. This means that your PDAlet can access data managed by the PDA device's address book, calendar, and to-do list applications. PIM data does not have to reside on the device. Your PDAlet can access the data even if the information is contained on a remote device, such as a PC that's linked to the PDA device.
The PDAP API implementation will handle security management to prevent unauthorized Java applications from accessing PIM databases. The implementation also provides a mechanism to enable a PDAlet to access PIM data efficiently without hindering performance.
PIM data can be imported and exported using a format specified by the Internet Mail Consortium. The vCard 3.0 format is used for address book entries and the vCalendar 1.0 format is used for calendar and to-do entries.
You can access PIM data directly from your PDAlet by using the PDAP PIM API found in the javax.microedition.pim package. All PDAP implementations support the PDAP PIM API.
There are three types of PIM databases supported by the PDAP PIM API: Event, Contact, and ToDo. The Contact Database also supports a photo field that can receive and store data in any of the IANA registered image formats or a nonstandard image format. The Photo field is consistent with the definition of the PHOTO field in the vCard specification and must support the Portable Network Graphics (PNG) format.
Every PDAP implementation must have an HTTP connection for networking devices, which is the same requirement for the MIDP profile. However, some implementations may support the Generic Connection Framework API, the logical serial port connection using CommConnection class, as well as the file systems and/or removable memory cards using the FileConnection class.
Support for the logical serial port connection and for the file systems is dependent on the operating system and hardware support that's available on the device running the PDAP implementation. The device is not necessarily required to have a serial port connection if the device's operating system enables an IR port to be configured as a logical serial port.
The file system of a device that implements PDAP is typically located either in the device's memory or on memory cards, depending on the device and the limits of the operating system. Memory cards that contain file systems include:
- SmartMedia Card (SSFDC)
- CompactFlash Card (CF)
- Secure Digital Card (SD)
- MultiMedia Card (MMC)
- MemoryStick (MS)
There are multiple security features imposed by the PDA profile that protect the user of the application and the device from malicious access and use. The PDA employs the sandbox security model that's implemented in CLDC 1.1 and MIDP 1.0. Security is further enhanced by the authorization security that enforces access privileges on resources of the device. These enhanced security policies will also be found in MIDP 2.0.
The enhanced security policies are hidden from the application and become visible only if a security exception occurs when using the PDAP API privilege functionality. Restrictions and permissible actions are associated with all PDAlets and MIDlets in a PDAlet suite and all code that runs on behalf of a member of the PDAlet suite.
The implementation determines how authorization results and configuration settings are presented to the user in the user interface. However, the implementation will require privileges to:
A Welcome Addition
J2ME developers who design and build applications for PDAs will find the PDA Profile an invaluable addition to their development arsenal, enabling the creation of powerful applications that take advantage of a new PDA footprint. The PDA Profile provides specifications for a rich set of AWT components that are used to implement sophisticated graphical user interfaces for PDA applications, GUIs similar to those found on desktop applications.
The PDA Profile also gives J2ME applications access to information stored on a PDA by proprietary, personal information management software that OEMs supply with the devices. This means your J2ME application can interact with a PDA's address book, calendar, and to-do list, including storing your own information in the databases used by these applications. Combining connectivity and security capabilities with AWT and personal information management, the PDA Profile is the right tool for every J2ME developer.
Building low-cost wearable devices can enhance the quality of our lives. In his session at Internet of @ThingsExpo, Sai Yamanoor, Embedded Software Engineer at Altschool, provided an example of putting together a small keychain within a $50 budget that educates the user about the air quality in their surroundings. He also provided examples such as building a wearable device that provides transit or recreational information. He then reviewed the resources available to build wearable devices at home including open source hardware, the raw materials required and the options available to power s...
Jan. 26, 2015 11:00 AM EST Reads: 1,974
“The age of the Internet of Things is upon us,” stated Thomas Svensson, senior vice-president and general manager EMEA, ThingWorx, “and working with forward-thinking companies, such as Elisa, enables us to deploy our leading technology so that customers can profit from complete, end-to-end solutions.” ThingWorx, a PTC® (Nasdaq: PTC) business and Internet of Things (IoT) platform provider, announced on Monday that Elisa, Finnish provider of mobile and fixed broadband subscriptions, will deploy ThingWorx® platform technology to enable a new Elisa IoT service in Finland and Estonia.
Jan. 26, 2015 11:00 AM EST Reads: 1,520
Advanced Persistent Threats (APTs) are increasing at an unprecedented rate. The threat landscape of today is drastically different than just a few years ago. Attacks are much more organized and sophisticated. They are harder to detect and even harder to anticipate. In the foreseeable future it's going to get a whole lot harder. Everything you know today will change. Keeping up with this changing landscape is already a daunting task. Your organization needs to use the latest tools, methods and expertise to guard against those threats. But will that be enough? In the foreseeable future attacks w...
Jan. 26, 2015 11:00 AM EST Reads: 2,895
As enterprises move to all-IP networks and cloud-based applications, communications service providers (CSPs) – facing increased competition from over-the-top providers delivering content via the Internet and independently of CSPs – must be able to offer seamless cloud-based communication and collaboration solutions that can scale for small, midsize, and large enterprises, as well as public sector organizations, in order to keep and grow market share. The latest version of Oracle Communications Unified Communications Suite gives CSPs the capability to do just that. In addition, its integration ...
Jan. 26, 2015 11:00 AM EST Reads: 2,840
From telemedicine to smart cars, digital homes and industrial monitoring, the explosive growth of IoT has created exciting new business opportunities for real time calls and messaging. In his session at @ThingsExpo, Ivelin Ivanov, CEO and Co-Founder of Telestax, shared some of the new revenue sources that IoT created for Restcomm – the open source telephony platform from Telestax. Ivelin Ivanov is a technology entrepreneur who founded Mobicents, an Open Source VoIP Platform, to help create, deploy, and manage applications integrating voice, video and data. He is the co-founder of TeleStax, a...
Jan. 26, 2015 10:45 AM EST Reads: 2,985
Today’s enterprise is being driven by disruptive competitive and human capital requirements to provide enterprise application access through not only desktops, but also mobile devices. To retrofit existing programs across all these devices using traditional programming methods is very costly and time consuming – often prohibitively so. In his session at @ThingsExpo, Jesse Shiah, CEO, President, and Co-Founder of AgilePoint Inc., discussed how you can create applications that run on all mobile devices as well as laptops and desktops using a visual drag-and-drop application – and eForms-buildi...
Jan. 26, 2015 10:45 AM EST Reads: 2,489
We certainly live in interesting technological times. And no more interesting than the current competing IoT standards for connectivity. Various standards bodies, approaches, and ecosystems are vying for mindshare and positioning for a competitive edge. It is clear that when the dust settles, we will have new protocols, evolved protocols, that will change the way we interact with devices and infrastructure. We will also have evolved web protocols, like HTTP/2, that will be changing the very core of our infrastructures. At the same time, we have old approaches made new again like micro-services...
Jan. 26, 2015 10:30 AM EST Reads: 2,313
ARMONK, N.Y., Nov. 20, 2014 /PRNewswire/ -- IBM (NYSE: IBM) today announced that it is bringing a greater level of control, security and flexibility to cloud-based application development and delivery with a single-tenant version of Bluemix, IBM's platform-as-a-service. The new platform enables developers to build ap...
Jan. 26, 2015 10:30 AM EST Reads: 2,626
Disruptive macro trends in technology are impacting and dramatically changing the "art of the possible" relative to supply chain management practices through the innovative use of IoT, cloud, machine learning and Big Data to enable connected ecosystems of engagement. Enterprise informatics can now move beyond point solutions that merely monitor the past and implement integrated enterprise fabrics that enable end-to-end supply chain visibility to improve customer service delivery and optimize supplier management. Learn about enterprise architecture strategies for designing connected systems tha...
Jan. 26, 2015 10:00 AM EST Reads: 2,870
SYS-CON Events announced today that CodeFutures, a leading supplier of database performance tools, has been named a “Sponsor” of SYS-CON's 16th International Cloud Expo®, which will take place on June 9–11, 2015, at the Javits Center in New York, NY. CodeFutures is an independent software vendor focused on providing tools that deliver database performance tools that increase productivity during database development and increase database performance and scalability during production.
Jan. 26, 2015 10:00 AM EST Reads: 1,618
The Internet of Things is a misnomer. That implies that everything is on the Internet, and that simply should not be - especially for things that are blurring the line between medical devices that stimulate like a pacemaker and quantified self-sensors like a pedometer or pulse tracker. The mesh of things that we manage must be segmented into zones of trust for sensing data, transmitting data, receiving command and control administrative changes, and peer-to-peer mesh messaging. In his session at @ThingsExpo, Ryan Bagnulo, Solution Architect / Software Engineer at SOA Software, focused on desi...
Jan. 26, 2015 10:00 AM EST Reads: 2,108
"For over 25 years we have been working with a lot of enterprise customers and we have seen how companies create applications. And now that we have moved to cloud computing, mobile, social and the Internet of Things, we see that the market needs a new way of creating applications," stated Jesse Shiah, CEO, President and Co-Founder of AgilePoint Inc., in this SYS-CON.tv interview at 15th Cloud Expo, held Nov 4–6, 2014, at the Santa Clara Convention Center in Santa Clara, CA.
Jan. 26, 2015 09:30 AM EST Reads: 2,130
Things are being built upon cloud foundations to transform organizations. This CEO Power Panel at 15th Cloud Expo, moderated by Roger Strukhoff, Cloud Expo and @ThingsExpo conference chair, addressed the big issues involving these technologies and, more important, the results they will achieve. Rodney Rogers, chairman and CEO of Virtustream; Brendan O'Brien, co-founder of Aria Systems, Bart Copeland, president and CEO of ActiveState Software; Jim Cowie, chief scientist at Dyn; Dave Wagstaff, VP and chief architect at BSQUARE Corporation; Seth Proctor, CTO of NuoDB, Inc.; and Andris Gailitis, C...
Jan. 26, 2015 09:00 AM EST Reads: 2,491
Recurring revenue models are great for driving new business in every market sector, but they are complex and need to be effectively managed to maximize profits. How you handle the range of options for pricing, co-terming and proration will ultimately determine the fate of your bottom line. In his session at 15th Cloud Expo, Brendan O'Brien, Co-founder at Aria Systems, session examined: How time impacts recurring revenue How to effectively handle customer plan changes The range of pricing and packaging options to consider
Jan. 26, 2015 09:00 AM EST Reads: 2,461
The Industrial Internet revolution is now underway, enabled by connected machines and billions of devices that communicate and collaborate. The massive amounts of Big Data requiring real-time analysis is flooding legacy IT systems and giving way to cloud environments that can handle the unpredictable workloads. Yet many barriers remain until we can fully realize the opportunities and benefits from the convergence of machines and devices with Big Data and the cloud, including interoperability, data security and privacy.
Jan. 26, 2015 07:45 AM EST Reads: 2,405
Code Halos - aka "digital fingerprints" - are the key organizing principle to understand a) how dumb things become smart and b) how to monetize this dynamic. In his session at @ThingsExpo, Robert Brown, AVP, Center for the Future of Work at Cognizant Technology Solutions, outlined research, analysis and recommendations from his recently published book on this phenomena on the way leading edge organizations like GE and Disney are unlocking the Internet of Things opportunity and what steps your organization should be taking to position itself for the next platform of digital competition.
Jan. 26, 2015 02:00 AM EST Reads: 2,757
In their session at @ThingsExpo, Shyam Varan Nath, Principal Architect at GE, and Ibrahim Gokcen, who leads GE's advanced IoT analytics, focused on the Internet of Things / Industrial Internet and how to make it operational for business end-users. Learn about the challenges posed by machine and sensor data and how to marry it with enterprise data. They also discussed the tips and tricks to provide the Industrial Internet as an end-user consumable service using Big Data Analytics and Industrial Cloud.
Jan. 26, 2015 01:00 AM EST Reads: 2,569
SYS-CON Media announced that Splunk, a provider of the leading software platform for real-time Operational Intelligence, has launched an ad campaign on Big Data Journal. Splunk software and cloud services enable organizations to search, monitor, analyze and visualize machine-generated big data coming from websites, applications, servers, networks, sensors and mobile devices. The ads focus on delivering ROI - how improved uptime delivered $6M in annual ROI, improving customer operations by mining large volumes of unstructured data, and how data tracking delivers uptime when it matters most.
Jan. 26, 2015 12:45 AM EST Reads: 3,504
SYS-CON Events announced today that ActiveState, the leading independent Cloud Foundry and Docker-based PaaS provider, has been named “Silver Sponsor” of SYS-CON's DevOps Summit New York, which will take place June 9-11, 2015, at the Javits Center in New York City, NY. ActiveState believes that enterprises gain a competitive advantage when they are able to quickly create, deploy and efficiently manage software solutions that immediately create business value, but they face many challenges that prevent them from doing so. The Company is uniquely positioned to help address these challenges thro...
Jan. 25, 2015 11:45 PM EST Reads: 1,812
SYS-CON Media announced that Cisco, a worldwide leader in IT that helps companies seize the opportunities of tomorrow, has launched a new ad campaign in Cloud Computing Journal. The ad campaign, a webcast titled 'Is Your Data Center Ready for the Application Economy?', focuses on the latest data center networking technologies, including SDN or ACI, and how customers are using SDN and ACI in their organizations to achieve business agility. The Cisco webcast is available on-demand.
Jan. 25, 2015 07:00 PM EST Reads: 1,302