Sunday, May 30, 2010

Its not just standalone BPM that is dead!

0 comments

Written by Sanjiva Weerawarana

There was a thread recently on InfoQ asking whether standalone BPMS is dead.

Yes it is dead.

But, that's not the only standalone thing that is dead! Standalone Business Rules Systems is dead. Standalone Application Servers are dead. Standalone ETL products are dead. Standalone Messaging products are dead. Standalone ESBs are dead. Standalone Enterprise Content Management systems are dead. Standalone Security products are dead. Yes, they're all dead.

They're all dead because customers are tired of being integration companies. What happens when a customer buys one of these standalone BPMS/BRS/ETL/etc. products is that the customer has to figure out how to integrate it to the other standalone products they've bought from other vendors. How does that help the customer's IT shop deliver business value to their organization?

Enterprise problems don't come neatly packaged into BPM problems or Business Rules problems or Data Transformation problems or any one such well defined category. Instead, enterprise problems are complex problems that require an entire repertoire of tools which can be combined nicely to solve the problem at hand. Attempting to build solutions to these complex problems with a single sledgehammer approach is one of the reasons why many IT projects take so long to complete and end up being so expensive.

The customer's IT shop is like the place which maintains the vehicle that the enterprise's IT is. What happens after a few years of taking standalone products and trying to live by their rules (not to mention their expensive consultants) and creating hodge-podge solutions is that the car ends up looking like this:
That's why enterprise middleware needs to be 100% internally self-consistent and fully integrated. Without that, every turn may drive the IT shop into a wall. Behind every dark spot on the road could be a pot hole. Or, at best, the IT shop is not able to drive the car down the freeway with cruise control turned on .. instead its constantly hitting speedbumps.

Don't like that? Well then you need middleware that can scale up and offer exactly the features that you need to solve the problem cleanly. Your IBM/Oracle/Tibco/JBoss middleware can't do that? Well then you have to try WSO2 Carbon based products .. and your car will end up looking like this :-).
The best part of course is that all of our products are 100% open source under Apache license and free for you to use. If you want absolutely world class enterprise support, call us and we'll sell it to you at $8000/server. All very simple.

See original post

Tuesday, May 25, 2010

Enter Platform-as-a-Service (PaaS) !

0 comments

Written by Sami

Paul's contention is this:
You need a PaaS that supports the same core services that a modern Enterprise architecture has: ESB, BPMS, Authentication/Authorization, Portal, Data, Cache, etc.And you need a PaaS that works inside your organization as well as in a public Cloud. And if you really don't want any lock-in.... hadn't that PaaS better be Open Source as well? And yes, this is a hint of things coming very soon!

See original post

Monday, May 24, 2010

Webinar: PHP Web Services: Why You Should Care

0 comments

Written by Sami

I will be presenting a Webinar on Webinar: PHP Web Services: Why You Should Care

WSO2 is hosting this Webinar, in collaboration with Zend.

We will explore why PHP is becoming more and more popular in the SOA and integration space as well as why we need advanced standards such as WS-Security, when it comes to using PHP in the enterprise.

See original post

Friday, May 21, 2010

ESB Development Best Practices – Life-cycle Management

0 comments

Written by Sami

Scenario:
Multiple developers are working on their own instance of the ESB.
Developers want to deploy what they develop to a central QA server or staging server. Merging the individually developed artifacts with those developed by others is challenging. Sometimes this is done using copy/paste, and then hand it over to other developers. This seems to be error prone. What are the best practice for this scenario?

Solution:
1. Use WSO2 ESB 3.0.0
2. It has support for having individual configuration file for each artifact. For example, proxy services, endpoints, sequences and tasks all have separate configuration files
3. Use a configuration management system, like Subversion (svn), and ask all developers to commit their artifacts into svn
4. From QA/staging server, get an svn up of all the artifacts
5. If there are settings that are not portable like absolute paths etc, you can script those to be changed, using a
shell script (e.g. sed) or a simple scripting language (e.g. Perl, PHP, Python)
5. Boot up (or reboot) the WSO2 ESB on QA/staging server with the updated configuration checked out from svn

See original post

Wednesday, May 19, 2010

PHP Web Services: Webinar From WSO2 And Zend

1 comments

WSO2 and Zend jointly present a webinar titling “PHP Web Services: Why You Should Care” on 26th of May, 2010. The webinar will mainly focus on the following aspects,

• Understand Web services development best practices

• Discuss Web service myths and pitfalls

• Learn about prominent PHP Web services extensions

• Watch a demo of building Web Services with both the Zend Framework and WSO2 Web Services Framework for PHP.


You can find more information about the webinar and the link to registration here, http://wso2.org/library/webinars/2010/05/webinar-php-web-services-you-should-care.

See original post

Tuesday, May 4, 2010

Start SOA governance with WSO2 governance Registry

1 comments

Written by Krishantha

WSO2 has recently announced their new release of WSO2 Governance Registry which is based on WSO2 Carbon framework 3.0.0.

It was packed with some exciting and very useful new features. The product can be used not only to govern you SOA metadata, but also as a registry-repository for your organization. Most interestingly the product is open source and available freely under Apache license. First version (0.1) of the product was released in December, 2007. Thus, the product has been matured over two years and good enough to cater your SOA governance requirement easily.

List of new features of the release as follows.

New Features
============================

* Gadgets for impact analysis on services and registry resources
* WSDL custom view
* Dynamic Handler configuration
* Handler simulator
* Tree-based Resource view
* API to govern SOA artifacts
* Complete Web Services API for Registry
* Improved options for Service discovery
* WS-Discovery support
* Scripting support for lifecycle management
* Improved P2 based provisioning and feature management support
* Support for adding remote mounts
* Platform, and Group/Cluster based deployment model
* Support for multiple server instances
* E-mail verification for subscriptions
* Support for deleting tags and comments
* Support for PostgreSQL DBMS
* Paged activity and resource search
* Hierarchical permission model with granular and extensible permissions
* Ability to upload metadata (in addition to importing)
* Governance Archive for uploading WSDLs and Schemas with imports
* Ability to update resource content by uploading
* Rich text editor for editing text resources
* XML editor for editing handler, lifecycle and service UI configurations

See original post

Sunday, May 2, 2010

WSO2 Governance Registry, WSO2 Identity Server, WSO2 ESB, WSO2 Web Service Application Server Released

0 comments

WSO2 has released new versions of their SOA platform products including WSO2 Governance Registry, WSO2 Identity Server, WSO2 ESB, WSO2 Web Service Application Server. This is a major version upgrade of these products introducing many features.


ESB:



  • Priority based mediation through priority executors

  • WS-Discovery support and dynamic endpoint discovery

  • Message Relay for efficient pass through of messages

  • Component manager to install and uninstall features (provisioning support)

  • Common Internet File System (CIFS) support through the VFS transport

  • File locking functionality in the VFS transport to support concurrent polling

  • Smooks mediator for efficient message transformation

  • Enrich mediator for smart message manipulation

  • OAuth mediator for 2-legged OAuth support

  • Default endpoint UI

  • Hot deploy and hot update configuration elements (sequences, endpoints, proxy services etc)

  • Transport level statistics collection and monitoring

  • POX security support

  • Dependency detection and alerting for mediation configuration elements

  • Mediation statistics API and custom mediation statistics consumers

  • Multiple certificate/identity support in the NHTTP transport sender

  • Improved logging capabilities for the NHTTP transport

  • Templates based proxy service development in the UI

  • Dashboard to monitor server environment and runtime

  • Easy creation and management capabilities for dynamic sequences and endpoints

  • Pagination to service management, endpoint management and sequence management UIs

  • Obtaining resources like WSDL’s through web proxy servers


Governance Registry



  • Gadgets for impact analysis on services and registry resources

  • WSDL custom view

  • Dynamic Handler configuration

  • Handler simulator

  • Tree-based Resource view

  • API to govern SOA artifacts

  • Complete Web Services API for Registry

  • Improved options for Service discovery

  • WS-Discovery support

  • Scripting support for lifecycle management

  • Improved P2 based provisioning and feature management support

  • Support for adding remote mounts

  • Platform, and Group/Cluster based deployment model

  • Support for multiple server instances

  • E-mail verification for subscriptions

  • Support for deleting tags and comments

  • Support for PostgreSQL and DB2 DBMS

  • Paged activity and resource search

  • Hierarchical permission model with granular and extensible permissions

  • Ability to upload metadata (in addition to importing)

  • Governance Archive for uploading WSDLs and Schemas with imports

  • Ability to update resource content by uploading

  • Rich text editor for editing text resources

  • XML editor for editing handler, lifecycle and service UI configurations


Web Service Application Server (WSO2 WSAS):



  • Component Manager – The UI tool to install/uninstall Carbon featrues.

  • Various bug fixes & enhancements including architectural improvements to Apache Axis2, Apache Rampart, Apache Sandesha2 , WSO2 Carbon & other projects.

  • Equinox P2 based provisioning support – extend your WSAS instance by installin new P2 features. See P2 based provisioning in WSO2 Carbon

  • Hierarchical service support for Axis2 services, JAX-WS services, Spring services & Jar services

  • Report generation for deployed services


Identity Server:



  • SAML 2.0 based Single Sign-on support

  • OAuth Support

  • Support for bulk-user import

  • Various bug fixes and enhancements including architectural improvements to Apache Axis2, Apache Rampart, Apache Sandesha2 , WSO2 Carbon and other projects.

See original post

 

Copyright 2009 All Rights Reserved Revolution Two Church theme modified by Milinda Pathirage