Architecture Difference between SAP Business Objects and IBM Cognos part1

Lets understand how Cognos product works internally

Most of BI product Architecture are almost similar internally.
BI Bus: Enterprise service Bus which surrounds all the services/servers which tool provide.
Typical ESB from Oracle BEA Aqualogic Stack engulfing many Web services looks like:
ESB_archNow you can compare this popular ESB with BI internal Architecture.
you can read more about ESB at : http://docs.oracle.com/cd/E13171_01/alsb/docs20/concepts/overview.html
Under 4 tier system: A client connects the Web server  (which is protected by firewall) using dispatcher. Dispatcher connects to Enterprise Service Bus (ESB) which surrounds all the application server services (Web services). ESB in case of cognos is Cognos BI Bus surrounds Web services Servers (like Report Server, Job server, Content Management server etc ). Mediation Layer Cognos BI Bus interacts with Non Java , C++ code which could not to converted or purposefully kept in C++ for may be more flexibility and speed
Cognos BI Bushttp://pic.dhe.ibm.com/infocenter/cbi/v10r1m1/index.jsp?topic=%2Fcom.ibm.swg.ba.cognos.crn_arch.10.1.1.doc%2Fc_arch_themulti-tierarchitecture.html

In case of SAP Business Objects (BO) ESB was not properly developed so an intermediate layer was created which works for interfacing between multiple servers like Job server, report server, page server etc. BO XI R2 came in pervius version was more in C++ to C++ to java bridge was created in ESB layer. Since Java was preferred language for coarse grain interoperability  provided by web services. Each server was developed using web services.
interaction between web server was routed through BI Bus.
BO-xi-r3.1-infrastructureIn latest version here u find a pipe connecting all components call Business Objects XI 3.1 Enterprise Infrastructure. Earlier version had different names. here you can see its connecting all server like Crystal report server, IFRS input file repository server( storing template of reports), OFRS Output file repository services, Program Job server(storing all programs which can be published on Portal (Infoview) ). This ESB does mediation between different server and achieves interoperability yet control of different components of products. This is in competitor product Cognos is called Cognos BI Bus.
http://bobi.blog.com/2013/06/02/sap-business-object-architecture-overview-and-comparatice-analysis/
For latest BO uses in memory product SAP HANA more about its competitors follow:
https://sandyclassic.wordpress.com/2011/11/04/architecture-and-sap-hana-vs-oracle-exadata-competitive-analysis/

In Micro-strategy there are two important server Intelligent server which creates cubes

More I will cover in later issues:
Oracle BI Architecture:
http://www.rittmanmead.com/2008/02/towards-a-future-oracle-bi-architecture/

Implementation OF BI system is not related to these product Architecture :
A  typical BI system under implementation haveing componets of ETL, BI, databases, Web server, app server, production server, test/development server looks like:
typical BI ArchtectureMore details: http://www.ibm.com/developerworks/patterns/bi/product-s390-web.html
Big Data Architecture:
From components perspective of ETL to BI implementation Aspect is little different
bigdata-scalein-architecture

Hadoop Architecture layers:
hadoop-architecturehttps://sandyclassic.wordpress.com/2011/10/19/hadoop-its-relation-to-new-architecture-enterprise-datawarehouse/
http://codemphasis.wordpress.com/2012/08/13/big-data-parallelism-and-hadoopbasics/

Just like UDDI registry is repository of Web

20 Comments

  1. Pingback: Enterprise service Bus ESB, BPM orchestration and Process Re-engineering | sandyclassic

  2. Pingback: A day in Life of Business Intelligence Engineer | sandyclassic

  3. Pingback: A Day in Life of Business Intelligence (BI) Architect- part 1 | sandyclassic

  4. Pingback: Coke Vs Pepsi of :Datawarehousing ETL Vs ELT | sandyclassic

  5. Pingback: SAP Business Objects Architecture | sandyclassic

  6. Pingback: SAP Business Objects Architecture, Reporting product Stack, ETL | Business Architect View

  7. Pingback: A Day in Life of Business Intelligence (BI) Architect- part 1 | sandyclassic

  8. Pingback: BI and Enterprise service Bus ESB, BPM orchestration and Process Re-engineering | sandyclassic

  9. Pingback: A Day in Life of Business Intelligence (BI) Architect- part 1 | Business Intelligence Technology Trends

  10. Pingback: SAP Business Objects Architecture, Reporting Infrastructure and BODI ETL | Business Intelligence Technology Trends

  11. Pingback: Coke Vs Pepsi of :Datawarehousing ETL Vs ELT | Datawarehouse View

  12. Pingback: A Day in Life of Business Intelligence (BI) Architect- part 1 | Datawarehouse View

  13. Pingback: A day in Life of Business Intelligence Engineer | Datawarehouse View

  14. Pingback: Use Case: Big data Analytics: Cisco,Machine to Machine,image processing,economics | Trends from Data Science

  15. Pingback: Architecting analysis of Structured and unstructured data | sandyclassic

  16. Pingback: Data war noSQL vs SQL vs NewSQL | Datawarehouse View

  17. Pingback: Data war SQL vs noSQL vs newSQL | Data Architect View

  18. Pingback: CLoud war: SQL vs noSQL vs newSQL | The Cloud View

  19. Pingback: Cloud BI/DW war : SQL vs noSQL vs newSQL | Business Intelligence Technology Trends

  20. Pingback: RDBMS war: SQL vs noSQL vs newSQL | sandyclassic

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s