What is SOA ?

Service-Oriented Architecture (SOA) is an architectural style whose goal is to achieve loose coupling among diverse interacting software applications, enabling organizations to take advantage of existing investments in applications and systems.

SOA facilitates the development of modular business services that can be easily integrated and reused, thus creating a flexible and adaptable infrastructure.

Using a SOA approach, an organization can focus more resources and budget on innovation and on delivering new business services.

Systems that can successfully use SOA can minimize the disruption of planned or unplanned outages in an enterprise.

Some of the advantages of using SOA are:

1. Reduction in development time and cost: SOA services are easily reused and can be rapidly assembled into new, composite applications.
2. Lower maintenance cost: Reusable services reduce the number and internal complexity of enterprise services.
3. High-quality services: Increased service reuse creates high-quality services through multiple testing cycles from different service consumers.
4. Lower integration costs: Standardized services know how to work together, enabling disparate applications to quickly and easily connect.
5. Reduce risk:Fewer, reusable services provide greater control over corporate and IT governance policies, and reduce the overall compliance risk to an enterprise.

How does SOA achieve loose coupling among interacting software agents?

It does so by employing two architectural constraints:

• A small set of simple and widespread interfaces to all participating software agents. Only generic semantics are encoded at the interfaces. The interfaces are universally available for all providers and consumers. 
• Descriptive messages constrained by an extensible schema delivered through the interfaces. No, or only minimal, system activity is prescribed by messages. A schema limits the vocabulary and structure of messages. An extensible schema allows new versions of services to be introduced without breaking existing services.

 

 

 

TIBCO ADB Adapter Error - “Failed to load shared library”

When starting an Adapter Service from the TIBCO Designer Adapter Tester, you might encounter this error: “Failed to load shared library, library name: adb55.dll”.

Fix this error with the following steps:

1. Open up C:\WINDOWS\system32.
2. Open up the TIBCO RV home directory (it might be C:\tibco\tibrv\8.1\bin).
3. Copy the libeay32.dll and the ssleay32.dll from the TIBCO RV home directory to the system32 directory.
4. Say yes if you are prompted to replace the files.

Restart your TIBCO Designer and try again.

TIBCO BusinessWorks On TIBCO Silver Fabric

BusinessWorks can run on  Private Cloud

TIBCO BusinessWorks is powerful enterprise integration technology that enables organizations to expose existing systems as services, build new services, and orchestrate and assemble services into applications – with little or no coding. Deployed by over 1,000 companies world-wide, BusinessWorks provides vital infrastructure for some of the most mission-critical service-oriented business environments in production today.

TIBCO Silver Fabric is a platform for creating a private cloud in your own data center that allows you to automate the provisioning and deployment of critical business applications, such as BusinessWorks, increasing your organization’s efficiency and reducing the risk of critical systems failures.

Cloud computing is being touted as the “next generation of computing” and is seen as vital to many in the IT industry. The many benefits of migrating to a cloud computing model include: increased efficiencies through shared resources, greater flexibility,global accessibility, and reduced expenses compared to standard physical computing. These benefits are offset by a few shortcomings,including loss of control and increased security risk, to name a few.

Manage Your Business, Not Your Environment

TIBCO believes organizations shouldn’t have to choose between efficiency and security. TIBCO Silver® Fabric llows you to setup a private cloud within your existing environment. This private cloud offers the same benefits as the public cloud without the additional risk. TIBCO’s solution comes with additional benefits not seen in public cloud offerings, such as automated dynamic scaling and run-time optimization – intelligent features that enable  TIBCO’s software to manage your environment, so you can manage your business.

EMS vs RV

• EMS is server based while RV uses a communications daemon on every machine.
• Depending on the requirements for speed and bandwidth, flexibility, security,reliability, availability and message passing between sub-nets one might require EMS or RV or a hybrid of both. 
• Both TIBCO RV and TIBCO EMS provide authentication, authorization and secure communication. Tibco RV and TIBCO EMS both provide secure socket layer (SSL) support for all communication. Where Web access is used, HTTPS is supported as well.
• In conclusion the EMS (JMS) hub-and-spoke model provides a better choice for the majority of EAI problems and RV is best left to its niches: high volume, high performance, 1-to-very many. 
• Generally use RV for speed topic / broadcast messages and EMS / JMS the more you are worried about assuring messages get to a receiver.  
• You can tune both products to go faster and more reliable. RV is basically broadcast via UDP, so needs RV Remote Daemons to cross subnets. You can bridge EMS to RV if you have specialised areas which you want to speed up.