Home Library Cognos Series7 Functionality Comparison Against Cognos 8
Follow us on Twitter


Countries

50.1%United States United States
7.6%India India
7%United Kingdom United Kingdom
5.1%Australia Australia
4.8%Canada Canada

Visitors

Today: 40
Yesterday: 573
This Week: 40
Last Week: 3348
This Month: 9425
Last Month: 15365
Total: 383512


Cognos Series7 Functionality Comparison Against Cognos 8 PDF Print E-mail
Written by Martijn Christenhusz   
Wednesday, 20 May 2009 20:04

Cognos Series 7 functionality comparison against Cognos 8

 

BI Function

Series7 Technical Summary

Cognos8 Technical HighlightsCognos8 Benefits
Architecture·     Client / Server based architecture
·     Different architectures by product (E.g. IWR, PPES)
·     Proprietary application servers and storage formats
·     Open architecture built using modern Web standards such as XML, SOAP, and WSDL
·     Single query engine for all BI capabilities
·     Windows, Unix, and Linux operating systems all supported in uniform and mixed platform deployments
·     Central relational database (Oracle, IBM, Microsoft, Sybase) stores all application content
·     UNICODE architecture and complete multilingual support
·     Support for simple or complex
environments with equal simplicity for
reduced costs
·     Single query engine ensures data
consistency
·     Simplify maintenance and administration
·     Cover all end user information needs
·    Supports enterprise BI consolidation
& convergence
·     Deploy to department, division,
globally or to the extended enterprise
with equal ease
Metadata·     Different metadata by product
·     Limit to 1 DB per model
·     Not centrally located/shared
·     Single metadata layer for all BI capabilities
·     Support multiple, heterogeneous sources in a single model
·     Enterprise Information Integration (EII) support
·     Data caching and query governor control
·     Impact analysis to identify query impact
·     Import metadata directly from 3rd party sources
·    Centrally located metadata means no
client side requirements, replication, or
redundancy
·    Impact analysis allows administrators
to know exactly which reports will be
impacted
·    Metadata import enables re-use
(E.g., Impromptu, Architect, Erwin,
Ascential, Informatica, others...)
Security ·     Requires the use of Cognos Access Manager
·     User information must be replicated in Access Manager
·     Leverage existing security providers directly (E.g., Active Dir., LDAP, NTLM, Netegrity, Access Manager, custom)
·     Authentication and Authorization centrally administered
·     Supports multiple security providers simultaneously
·     Internal data encryption up to 168 bits
·      No required replication of user/pw
information makes administration and
maintenance easier
·      Single signon with existing
applications enhances end user experience
·      Different apps can have different
security providers
Data Access·     Impromptu for relational
·     PowerPlay for OLAP
·     “Open Data Access” strategy removes the 1:1 line between front end UI and back end data source type
·     Report off any data source including: OLAP, relational, legacy, flat file, XML, Web Svcs, LDAP, Cognos EP and CF
·     Perform “analysis” against ROLAP or MOLAP sources
·    Supports numerous modern
standards and data sources without
coding or data migration
·    Leverage Cognos or 3rd party cubes
with a common UI
·    Hides complexity from users and
ensures consistency, integrity and
accuracy of information
Client vs. Web·     Client required for report authoring (PowerPlay and Impromptu)
·     Content is published to the Web after dev. in client
·      Zero-footprint, browser-based environment requires no desktop installs, plug-ins, or applets
·      Enables remote access to the system; log on from anywhere for remote Web-based administration and report authoring
·      BI content is consumed, saved and scheduled via the web
·      No maintenance of end user
desktop software
·      Point-and-click, task-based UI
improves user adoption, increases
self-service, and reduces dependence
on IT
·    Deploy BI content and system
changes to all users simultaneously
Integration·     Different APIs per product
·     API is a Web Services ‘wrapper’
·      Leverages an open application server (IBM WebSphere, BEA WebLogic, Oracle 10G, SAP, Tomcat)
·      Integrates seamlessly with Web portals such as IBM WebSphere, SAP, Plumtree, and WSRP-compliant portals
·      Single, fully published API (XML, SOAP, WSDL)
·    Easily integrate into existing env. for
greater ROI
·    Leverages your existing IT assets
and infrastructure
·    Cognos8 was built using the API,
so all Cognos UI functionality (and
more) is available via the API
·    Tight integration with MS Office fits
everyday usage
Scalability /
Stability
 
·    Single threaded report processing
·    Fewer server deployment options
·     Peer-to-peer, multi-threaded architecture provides a distributed environment with automatic load balancing, no single point of failure, and server independence
·      Component-based, with the flexibility to distribute components geographically, across servers, firewalls, etc.
·      Scalable to >100k users to support the enterprise
·    Start with any number of users and
easily add server resources to scale to
larger deployments
·    Leverage existing servers with more
deployment options
·    Confidence with mission critical BI
application stability
Administration·   Misc – Different administrative consoles and tools for each product·      Administration can be centralized or distributed
·      Multiple administrative product roles can be utilized
·      Web based server tuning, administration, and monitoring

·      Supports delegated administration
·      Single administrative interface simplifies
admin requirements and efforts

Last Updated on Wednesday, 26 August 2009 11:37
 
 

Login

For more content en features!



CogKnowHow Newsletter

Season's Greetings


Receive HTML?

Polls

How many users are working on your Cognos environment?