Service Oriented Architectures: Technology, Products & Best Practices for Designing SOAs

Venue: Holiday Inn Kensington

Location: London, United Kingdom

Event Date/Time: Mar 23, 2006 End Date/Time: Mar 24, 2006
Report as Spam


High on the agenda of many organisations is the integration of their vast number of isolated information systems. Many integration technologies have been introduced in the last decennium. The technology for the coming era is based on XML, (web)services, and other standards: the Service Oriented Architecture (SOA). SOA will become the backbone of many IT departments and with that it will become the information backbone of organisations themselves. All information exchange will pass through this architecture.

Due to mergers, new regulations and market changes, companies are looking at what SOA could mean for them. For some, SOA will be the basis for the automation of business processes. Others see it as a means to gradually remove their legacy systems, and others see it as a means to transform their organisation into an agile organisation – one that can adapt quicker to market changes and opportunities.

Day 1 of this seminar presents an in-depth overview of the products and the technologies that are available today to develop SOA. The main product for implementing SOA is the Enterprise Service Bus (ESB). This new generation of products is based on widely adopted standards such as XML and SOAP and comprises most of the technologies needed for SOA including a BPEL engine, adaptors, content based routers and business rules engines.

Day 2 will describe the crucial guidelines when designing SOA. It is based on experiences gained at several SOA projects. Several issues need to be addressed when designing SOAs. Products need to be selected and a global architecture must be designed. How will existing applications, that at first were not meant to be integrated, be linked to the SOA? What does a document oriented interface for services mean? Management of SOA should also be organised carefully. Should Business Activity Monitoring be considered or not? How should billing, service level agreements and security be dealt with? These, and many more questions need to be answered before SOA can be designed and built.