Please see this very useful whitepaper
www.oracle.com/technetwork/database/features/availability/soa11gstrategy-1508335.pdf
Friday, February 22, 2013
Monday, February 18, 2013
#216 Eloqua update for Oracle CRM partners
Just to remind you...
https://blogs.oracle.com/emeapartnercrmod/entry/live_webcast_oracle_buys_eloqua
https://blogs.oracle.com/emeapartnercrmod/entry/live_webcast_oracle_buys_eloqua
Thursday, February 14, 2013
#215 Oracle Fusion CRM partner integrations
I have been getting some questions about this recently -
here's a good info source -
here's a good info source -
http://www.oracle.com/us/products/applications/fusion/customer-relationship-management/fusion-crm-isv-partners-1848280.html
Also worth checking out is the EMEA CRM Partner Community blog -
EMEA CRM Blog
Tuesday, February 12, 2013
#214 SOA Made Simple Chapter 3
This chapter covers Service Identification and Design - essentially identifying what services you already have and which new ones do you need.
The authors introduced the concept of 3 hierarchical architecture layers in Chapter 1 -
Business / Information and Technical. So essentially you end up with services on all 3 levels, which need to be identified and designed.
The section on Service Design succinctly covers all you need to know in respect of interface, contract and implementation design. It deals with concepts such as granularity, reusability, idempotency, isolation etc. - really a great checklist for you to follow.
Again the link -
SOA made simple
The authors introduced the concept of 3 hierarchical architecture layers in Chapter 1 -
Business / Information and Technical. So essentially you end up with services on all 3 levels, which need to be identified and designed.
The section on Service Design succinctly covers all you need to know in respect of interface, contract and implementation design. It deals with concepts such as granularity, reusability, idempotency, isolation etc. - really a great checklist for you to follow.
Again the link -
SOA made simple
#213 SOA Made Simple Chapter 2
Chapter 2 delves into services - answering well the ubiquitous question -
What is a Service?
It then delves into the elements of a service - contract, interface and implementation.
However, the example used - a US diner breakfast service - is not to my taste (get the pun!).
The authors may have been better off with a more mundane example - such as car rental booking.
However, the more implementation oriented examples in this chapter do illustrate & illuminate the concepts discussed. What I like about the chapter, and the book in general, is the fact the authors always answer the Why - i.e. giving us solid business reasons for what they are offering.
Again the link -
SOA made simple
What is a Service?
It then delves into the elements of a service - contract, interface and implementation.
However, the example used - a US diner breakfast service - is not to my taste (get the pun!).
The authors may have been better off with a more mundane example - such as car rental booking.
However, the more implementation oriented examples in this chapter do illustrate & illuminate the concepts discussed. What I like about the chapter, and the book in general, is the fact the authors always answer the Why - i.e. giving us solid business reasons for what they are offering.
Again the link -
SOA made simple
Monday, February 11, 2013
# 212 SOA Made Simple Chapter 1
as promised, a review of the book - Chapter by Chapter...
Chapter 1 - Understanding the Problem.
Reminds me of - Women are from Venus - Men are from Mars - the mismatch between business requirements and IT infrastructure/implementations.
The authors give a succinct overview of the problem space SOA is addressing.
Process silos - data and functional duplication are the common symptoms of this dichotomy.
They emphasise the role of architecture in addressing this and position SOA within this architectural world.
It details how SOA fits in with Enterprise Architecture, Reference Architecture, Solution Architecture & Project Architecture
Essentially a raison d,être for Service Oriented Architecture.
Again the link...
SOA made simple
Chapter 1 - Understanding the Problem.
Reminds me of - Women are from Venus - Men are from Mars - the mismatch between business requirements and IT infrastructure/implementations.
The authors give a succinct overview of the problem space SOA is addressing.
Process silos - data and functional duplication are the common symptoms of this dichotomy.
They emphasise the role of architecture in addressing this and position SOA within this architectural world.
It details how SOA fits in with Enterprise Architecture, Reference Architecture, Solution Architecture & Project Architecture
Essentially a raison d,être for Service Oriented Architecture.
Again the link...
SOA made simple
Subscribe to:
Posts (Atom)
