AquaLogic Service Bus v3.0 is here!
Chris Tomkins' Blog |
March 3, 2008 5:52 AM
|
Comments (4)
The new version of AquaLogic Service Bus, v3.0, is finally here - I've been playing around with early versions for a while now internally, but have not been able to write about it, but now I can! Some of the key new features are: Eclipse-based design tools for WorkSpace Studio Before v3.0 the design of all AquaLogic Service Bus assets (such as business services and proxy services) took place in the web-based console. In v3.0 you can still choose to use the console, but you can now choose to design all your assets in WorkSpace Studio using the new Eclipse plugin. Those of you familiar with previous versions of AquaLogic Service Bus should find it pretty easy to understand - plus existing service bus configurations can be imported into WorkSpace Studio which will give you a real headstart and the opportunity to see what older configurations look like in the new tool. Business Service Overload Protection (Throttling) Some business services, typically legacy ones, are often not designed to cope with the high throughputs demanded by today's SOA environments. In order to protect these services from being overloaded, AquaLogic Service Bus v3.0 has introduced business service overload protection, or throttling, capabilities. Using these you can define the maximum number of messages that can be handled concurrently by your business service. If this limit is exceeded, additional messages are placed on a queue until the number of messages being handled by the business service has fell below the maximum concurrent message limit or you have chosen to expire them after a set period of time. Throttling metrics such as maximum, minimum and average throttling time can be used to generate alerts and also in the construction of service level agreements. Read more about throttling here. Large Message Processing If you have a proxy service which expects to receive large messages then you may want to take a look at the new streaming mode option AquaLogic Service Bus v3.0 provides. This allows large message content to be streamed rather than all loaded into memory - an expensive option for very large messages, especially if you only need limited access to the payload (e.g. if you are performing header based routing). Options are provided to allow you to stream the content to memory or to disk. Read more about the streaming capabilities here.
Split/Join A common business integration use case is to take a service request, split it up into a number of parts, perform one or more service invocations for each part concurrently, and then aggregate (or join) the responses from these invocations into a single response message. A good example of this is an order processing service which might well perform the following steps: - Receive an order
- Check whether each item in the order is in stock (by invoking a stock check service)
- Return a summary of the item availability
AquaLogic Service Bus v3.0 now provides support for both static (the number of parts is known at design time) and dynamic (the number of parts is only known at runtime) split/join patterns. Read more here. Service Pooling and Endpoint Failover If you have a business service which has multiple endpoints AquaLogic Service Bus v3.0 will automatically remove non-responding endpoints from the pool and automatically add them back in when available. Alerts are also generated when this happens, so you can quickly see when a problem has occurred and deal with it rapidly. Improved standard support and connectivity In AquaLogic Service Bus v3.0 we now support WS-ReliableMessaging and have new transports for native MQ Series connectivity, secure FTP and an improved custom transport SDK (read more on the transports page). We also now have enhanced support for native ERP transports (such as SAP and Siebel) through our new product SmartConnect. Check out Quinton Wall's introductory video to SmartConnect on YouTube. In addition to these there is improved integration with other products in the AquaLogic family and numerous performance improvements and bug fixes. If you haven't got hold of a copy yet - what are you waiting for?
Comments
Comments are listed in date ascending order (oldest first) | Post Comment
-
Hi krokodylowy - please raise any specific issues you are seeing with Workspace Studio at support.bea.com so that they can be addressed by our support team.
Posted by: ctomkins on April 24, 2008 at 8:27 AM
-
I see few problems in ALSB 3.0
- Eclipse 3.2 based IDE hangs and terminate very often
- in message flow I cannot remove not necessery xmlns definitions from xml body, which comes after Assign to variable operation.
- in business service I cannot see and log original response from external Webservices like from Axis2 which sometimes return error 500 with non standard response The endpoint reference (EPR) for the Operation not found
Posted by: krokodylowy on April 24, 2008 at 7:37 AM
-
Thanks for the comment. Projects can be exported from the IDE as an ALSB configuration jar file which can be deployed to the server via a WLST script without using the IDE. The export process (i.e. creation of the configuration jar) cannot currently be automated although this has been accepted by the development team and they are working on fixing this for a later release.
Posted by: ctomkins on March 31, 2008 at 3:26 AM
-
Eclipse based IDE development is very helpful feature to have !!However when we tried to automate the publishing of an alsb project created using IDE to an alsb server, we could not find any way to do so. Now that the developement of ALSB project can be done in Workspace studio, we are planning to use Teamprise plugin to upload the project to Microsft TFS for source control management and the team would directly check out/check in proxy services/business services etc.. from the workspace studio itself (rather than using ALSB change center for team development). Now when i want to take the ALSB project from the source control and deploy to an ALSB server, i can take latest version from source control, open the project in Workspace studio and export the project to ALSB server. Is there anyway to automate this ? We have seen lot of samples on how to export a project from one ALSB server and import into another alsb server. How can i import an ALSB project created using workspace studio into an alsb server without using the IDE ?
Posted by: S.Saravana.Prasad on March 13, 2008 at 8:28 AM
|
