Sun realigns software around GlassFish Portfolio
February 10, 2009 —
(Page 1 of 2)
Related Search Term(s): GlassFish, Sun
Over the past four years, Sun Microsystems has recast itself as a company focused on open source. With open-source Java, Solaris, NetBeans and application server GlassFish, the company has come up with a product lineup to support that claim. Today, Sun expanded its open-source offerings even further by releasing four GlassFish-focused products based on popular open-source software.
The additions that make up GlassFish Portfolio are priced based on levels of service and support. The first product, the GlassFish Web Stack is a snapshot of Apache Web server, MySQL and PHP that Sun will update and support for US$999 per server per year. That stack, which also includes Java EE, is supported on either Linux or Solaris, and according to Karen Tegan Padir, vice president of Sun's MySQL and Software Infrastructure Group, the stack is designed to allow developers to write once for either operating system.
“Things will evolve in the community, and there will be new packages, new features and new things we will add to it," said Tegan Padir. "It's not this frozen stack you're going to get once a year."
Pricing on the Web Stack also extends to higher levels of support, which are available for $2,999, $5,999 and $8,999 per server per year.
“The beauty of GlassFish Portfolio is that both [GlassFish and Java EE] are included with a single subscription,” said Kevin Schmidt, director of strategy for software infrastructure marketing at Sun.
“You can begin working with Java EE. Where it makes sense to use BPEL for orchestration, you can do that in a very incremental way.”
Those prices are also extended to the three other new GlassFish components from Sun.
Get on the service bus
The second component is GlassFish ESB. “GlassFish ESB is taking components that have been developed in the OpenESB community, along with GlassFish and the associated tooling in NetBeans,” said Schmidt. “It has transformation and routing capabilities.”
Schmidt said that the key difference here is the inclusion of “core adapters for HTTP and Web services. The ESB itself has at its core a [Java Business Integration] implementation that uses a normalized message router so it's doing everything in memory.” Schmidt said that this improves speed and responsiveness.