Issue with Alphablox FastForward and relational cubes.

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • jai83
    New Member
    • Jan 2007
    • 8

    Issue with Alphablox FastForward and relational cubes.

    Hi,
    We are facing a problem with connectivity between Alphablox FastForward and DB2 Cubeviews.(Plat form details are mentioned at the end of message).

    We have created a cube definition on DB2 using cubeviews and imported the same in Alphablox. We can successfully query the cube using Alphablox query builder. Now we want to create some custom reports, for which FastForward Application seems to be a promising and easy approach. But we are unable to get the sample application running. We have modified the timeschema.xml also, but still it gives “timeschema not defined in cube <cubename>” error. One sample template report which does not contain the timeschema blox runs fine but others do not.

    The documentation states a known issue that “FastForward applications do not work with relational cubes” and there is no workaround provided. So, does it mean that we can not use IBM DB2 UDB(with cubeviews) with FastForward applications for OLAP applications?

    If that is the case then there must be some way out to use such pre-built applications/templates or do we need to make the whole application from scratch? Also even if we decide to do it from scratch will the timeschema blox still work(as its not working in fastforward)?

    Please suggest.
    Development Environment:
    Alphablox 8.4.0 on WinXP machine.
    WebSphere Application Server 8.0 on WinXP machine.
    DB2 8.1.10 & CubeViews 8.1.10 on win2000 machine.
  • eddyleesinti
    New Member
    • Apr 2007
    • 1

    #2
    Hi,

    Just to share my Alphablox experience with you, my team already implemented a FastForward-based Alphablox solution driven by Alphablox Cube.

    The sample template that doesn't use TimeschemaBlox should be Interactive Present Blox template right?

    Modification of timeschema.xml can be tricky and error prone, a simple typo error will give you hard time to trace and fix, phew.

    Anyway, make sure cross check your timeschema.xml and your time dimension definition.

    Good luck.

    Comment

    Working...