[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: How we use SCA at Siemens
Hi, we use SCA in Siemens for building distributed embedded systems. In a recent project, we used Trentino (trentino.sourceforge.net) to build a highly available distributed system for Smart Grid. 1.
Custom Bindings
a.
We make use of binding to implement Service Discovery for SCA Services located different devices
b.
We make use of binding to implement a custom KNX and ModbusTCP Binding for specific batteries
c.
SCA provides a clear separation of communication and business logic and helped us to simplify the integration of custom bindings. Making
it possible to implement a very variable/extensible system 2.
We make use of the SCA Assembly model to modularize the application. The use of SCA made communication between Teams easier. Non Functional Requirements in the embedded domain are quite different from the ones in Enterprise Applications, this is why we decided to implement
Trentino instead of joining prominent projects like Apache Tuscany. Finally there is no interest for us to use Web Services in embedded apps, we prefer BACNET, KNX, …, or REST Binding for vertical integration. It is very constraining to have to implement WS Binding to be a conform SCA Spec implementation, it restrict the usage of SCA in my opinion. Best regards Emeric Von: sca-bindings@lists.oasis-open.org [mailto:sca-bindings@lists.oasis-open.org]
Im Auftrag von Wolfgang Bäck Hi, Some questions have been raised about market interest in SCA. I would like to share our experiences. In the past several years, I have worked on a hugh government project that uses SCA for a highly-available tax processing system. The system also uses a very large
Oracle RAC installation for data availability. The success of the project has been a direct result of capabilities provided by SCA. Without them, the project would have taken much longer and been a lot more complex, making it more likely to fail. Here are some of the SCA features that we have found invaluable: 1. Web Services and security policy. The tax processing system connects to many legacy systems that are accessed using secure web services (WS-*). The SCA Web Services binding and capability to define
security policy resulted in our application being able to connect to those systems without having to write complex Java code. We have tried JAX-WS and .NET for other applications and SCA was much easier and simpler to use. We also completed our tasks in record
time. 2. Asynchronous services with callbacks. The legacy systems are often very slow and offline for maintenance (some are mainframe). We did not want to tie up application threads waiting for responses since
this would not scale. As a solution, we used SCA asynchronous services with callbacks. This has made our application very performant and able to handle latencies efficiently. While .NET has a callback feature (duplex services), I am not aware of one provided
by a Java standard without having to write custom application code. Without callbacks, would have had to develop a solution ourselves. 3. Modularity The application uses SCA composition (promotion) and OSGi integration for modularity. The module that connects to the legacy systems is an SCA composite that composes
a number of services. After a year, we created another implementation of the composite that has different logic and connects to an ESB instead of the legacy systems. Modularity was so successful that we did not have to modify any other parts of the system
when we made the switch. We are also able to switch implementations at deployment. Without composites, we would not have this modularity. 4. Wire re-injection Part of the application is a rules engine we implemented using SCA Java components. Rules are services that are wired to the engine. An important business requirement
is that tax rules can be updated without taking the system down. We do this by relying on re-injection and deploying new composites with additional rules. 5. Custom bindings The tax system receives requests and publishes responses as files over a highly available geographically distributed SAN. We use SCA's feature to create a custom
file binding to handle this. I am not aware of any other standard that specifies custom communications extensions. Wolfgang 2013/7/12 Eric Johnson <eric@tibco.com> Hi Jeff, On 7/12/13 1:11 PM, Jeff Mischkinsky wrote: yeah, but if it doesn't CONFORM, i.e. meet ALL the conformance requirements as set out in the spec(s), then its not SCA, it's something that is maybe kind of like SCA --I haven't looked at this specific project to know how close it comes to conforming, just making a general comment about the confusion created when someone say they have implemented part of a spec, and somehow that means that there is now an implementation of that spec.
note: i'm just not being pedantic here. If you carefully read the IPR policy, the IPR protections ONLY kick in for implementations of the complete spec(s), as defined by the conformance clauses. An IPR holder is not required to grant licenses/non-asserts to an implementation that does not conform. As one possible way to change the situation, we could adjust specification and the conformance clauses, for example, making it possible to conform to assembly without requiring all of bindings, implementation
types or policy, and therefore make it easier for more products to conform to the individual parts of the SCA suite. Unfortunately, the opportunities we've given for Oracle TC members to step forward and suggest alternate paths forward have yielded no options
from Oracle participants. --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]