Web Monitor Reporting Tool

Dear All,
Having read this post :- Data Load Reporting Tool
I have come to the conclusion that there isn't any such tool for monitoring of daily loads and the like.
Can anyone tell me is it possible to have the underlining tables for RSPCM & RSMON delivered as a Web Page for daily exceptions only?  Would this need to be written in ABAP or some form of javascript ?
We are running BI7 but have yet to install the JAVA stack, so JAVA solutions not really viable at this time.
Any ideas or preferably solutions appreciated.
Thanks
Craig.

Hi JR
No this will not work. The Discoverer J2EE only works against an Oracle application server.
Sorry
Michael

Similar Messages

  • I need  Web based Dynamic Reporting tools

    Hi,
    I need a Web based Dynamic Reporting tool.
    I have to user oracle products and this reporting tools must support OLAP and Data Warehousing.
    thanks,

    Hi Shima,
    Let me quote from Oracle Reports website:
    "Oracle Reports is Oracle's award-winning, high-fidelity enterprise reporting tool. It enables businesses to give immediate access to information to all levels within and outside of the organization in an unrivaled scalable and secure environment. Oracle Reports consists of Oracle Reports Developer (a component of the Oracle Developer Suite) and OracleAS Reports Services (a component of the Oracle Application Server)."
    Since you need a web-based reporting tool, this is what is available with Oracle Reports:- you cannot design reports on the web, but you can use Oracle Reports Developer to design high quality reports that are suitable for viewing on the web.
    Oracle Reports support OLAP as a data source.
    From your requirements, it seems that it might be worthwhile for you to check out Oracle Discoverer which is again a powerful reporting and analysis tool. Oracle Discoverer is more suitable for ad-hoc reporting and web-based analysis of data by the end-users:
    http://www.oracle.com/technology/products/discoverer/index.html
    Navneet.

  • Need assistance in Hyperion Web Analysis Report

    Hi All,
    I am using HFM with Oracle database as the data source for reports and using Hyperion 931 components.
    I have a requirement in Key Performance Indicators reports (KPI)
    1) Need to have a custom column of current year Actuals Vs Plan data
    2) Need to have a custom column of current year Actuals Vs prior year Actuals data
    3) Need to indicate Font colours based on the values derived in columns (1) and (2) - if positive data - green colour
    if negative data - red colour
    I am trying to replicate this in Web Analysis report, but facing issues on
    1)Making this year value dynamic (shd change based on current year or atleast should prompt when we run report)
    2) Since i have fixed the report with 2008 and 2007 year, all the formattig made whiel creating the Report goes away, if i try to run the report with different year values like in 2010 and 2009 year (as current and prior year)
    3) Also, i have hided some coulumns based on our requirement which also no longer exists if i change the year values (available in coulmns)
    Please suggest any comments to resolve these issues, Moreover i am new to Web Analysis reporting tool ,so kindly suggest, if i am not using any of the existing WebAnalysis features to derive my requirement.
    Expecting your earliest response.
    Thanks,
    Siva

    Hi Siva,
    If you are using the Essbase as a data source then you can achieve these things from using the substitution variable in WA report.
    Assume you have a substitution variable in Essbase cube for current year. In WA report in Dimension Browse, right-click a dimension member and select "Substitution Variable”. The Substitution Variable dialog box is displayed. Here select a substitution variable from the list of Essbase substitution variables.
    To get the Prior year, again in Dimension Browse, right-click a dimension member and select the "Also select Previous". Here define the prior year that you want to use in your report.
    Sorry, I have no idea about the substitution variables in the HFM (It might be that we call the substitution variable with another name in HFM).
    Hope it will help you.
    Thanks & Regards,
    Mohit Jain

  • Need assistance in Web Analysis Report

    Hi All,
    I am using HFM as the data source for reports and using Hyperion 931 components.
    I have a requirement in Key Performance Indicators reports (KPI)
    1) Need to have a custom column of current year Actuals Vs Plan data
    2) Need to have a custom column of current year Actuals Vs prior year Actuals data
    3) Need to indicate Font colours based on the values derived in columns (1) and (2) - if positive data - green colour
    if negative data - red colour
    I am trying to replicate this in Web Analysis report, but facing issues on
    1)Making this year value dynamic (shd change based on current year or atleast should prompt when we run report)
    2) Since i have fixed the report with 2008 and 2007 year, all the formattig made whiel creating the Report goes away, if i try to run the report with different year values like in 2010 and 2009 year (as current and prior year)
    3) Also, i have hided some coulumns based on our requirement which also no longer exists if i change the year values (available in coulmns)
    Please suggest any comments to resolve these issues, Moreover i am new to Web Analysis reporting tool ,so kindly suggest, if i am not using any of the existing WebAnalysis features to derive my requirement.
    Expecting your earlier response.
    Thanks,
    Siva

    Hi Siva,
    If you are using the Essbase as a data source then you can achieve these things from using the substitution variable in WA report.
    Assume you have a substitution variable in Essbase cube for current year. In WA report in Dimension Browse, right-click a dimension member and select "Substitution Variable”. The Substitution Variable dialog box is displayed. Here select a substitution variable from the list of Essbase substitution variables.
    To get the Prior year, again in Dimension Browse, right-click a dimension member and select the "Also select Previous". Here define the prior year that you want to use in your report.
    Sorry, I have no idea about the substitution variables in the HFM (It might be that we call the substitution variable with another name in HFM).
    Hope it will help you.
    Thanks & Regards,
    Mohit Jain

  • Web content reporting User information

    HI Guys,
    We have been using the web content reporting tool for a while now.  We however want to have information about WHO logged on.
    If I look into the databse I can see a hashed userid is logged.  Has anyone allready tried to get this information into the reports?  (
    Does anyone has an idea to unhash this userid, or maybe better DO not hash it at all?
    Thanks
    Joachim

    It seems I am blond.  I somehow missed the parameters in the application descriptor.  It now seems to be writing the logon id(unhashed) in te logonid field.
    Hopefully it will appear in the standard reports.....

  • Web Based Reporting Suggestions...

    Hi,
    Can anyone suggest a way to be able to access data from an Oracle database and publish the results to the web (intranet or not) without using Oracle Reports. I have to implement a solution where the turnaround time needs to be fast for requirements. I will appreciate your help.
    Regards
    Mahathi

    Discoverer Viewer is a web based reporting tool that can be called from a URL. Check out the syntax at http://otn.oracle.com/products/ias/tech_tips/july01.html. You can specify query parameters by prefixing the parameter names with "qp_". Reports ("workbooks") can be created very quickly using Discoverer Desktop Edition or Discoverer Plus.

  • Which is the best reporting tools/sw available for J2EE based web app?

    Hi,
    I am looking for best reporting tools/sw available for J2EE based web application.
    Please help in this...
    Regards
    kundan krishna chakraborty

    Hi,
    maybe you can have a try RAQ Report. It is a powerful pure Java reporting tool which is very easy to learn.
    You can get the free version at http://www.raqsoft.com/.
    Good luck!

  • What is the best reporting tool for my web application?

    Hi guys,
    I'm using ADF 11g with EJB 3.0 im my web application. My application is deployed on weblogic server 11g, I want to use a reporting tool in my application that is dynamic and flexible.
    Note: I've tried to use JasperReports but it didn't fulfill my needs.
    Thanks in advance.
    AccadSoft

    There are plenty of them. Oracle has one called BI Publisher, and there are others out there as well, such as BIRT, Business Objects, etc, etc, etc.
    "it didn't fulfil my needs" doesn't give anyone any possibility to comment, because you didn't tell us why, or what was lacking.
    John

  • Web Monitoring Tool

    Hi,
    Can you recommend any tool(s) that does Web monitoring i.e. check if the Website is UP or not.
    This tool must also monitor webServices.
    Thanks.

    I do the same thing, and it's pretty simple to set up:
    What I do is enable the web service on the OS X server. Then I enable the Proxy service. (All through Server Admin)
    Then, I set that server as the proxy on the client machines. (Safari proxy is set in System preferences/Network Settings, and Firefox and Exploder in their respective Preferences. (something like Firefox/Preferences/Network Connection settings.))
    Then your server's web access log will show you by IPs all the accessed web pages.
    You can also block desired websites that way (it's in the proxy settings on the server -- Server Admin).
    Since Safari proxy is controlled via system preferences you can lock it so that users can't change it, but firefox and exploder settings are user acessible, if your users are savvy enough to find them.
    The only problem I've run with this, and it is such a minor issue, is that some websites that use nonstandard ports have trouble getting through proxy. In that case I just bypass the proxy on the browser settings. (It's in the same place where you set those settings in the first place.)
    Hope that helps:)
    There are liability issues involved though, with expectations of privacy and other policies, such as uniformly and randomly applying "keeping a closer eye". I wouldn't recommend firing anyone over that, as they could easily counter-sue.

  • Announcement: Super 4.00 - a suite of EJB/J2EE monitoring/admin tools.

              Announcement: Super 4.00 - a suite of EJB/J2EE monitoring/admin tools.
              Acelet is the leader in J2EE tools area. If you google "j2ee tools",
              "j2ee logging", "j2ee scheduler" or alike, you will find Acelet
              is at the top of the result.
              Super 4.00 comes with:
              SuperEnvironment
              SuperLogging
              SuperPeekPoke
              SuperReport
              SuperScheduler
              SuperStress
              and SuperPatrol, as a schedule job.
              The evaluation edition can be anonymously downloaded from:
              http://www.ACElet.com.
              Super is a component based monitor and administration tool
              for EJB/J2ee. It provides built-in functionality as well as
              extensions, as SuperComponents. Users can install
              SuperComponents onto it, or uninstall them from it.
              Super has the following functions:
              * A J2EE monitor.
              * A gateway to J2EE/EJB servers from different vendors.
              * A framework holding user defined SuperComponents.
              * A full-featured J2EE logging and J2EE tracing tool for centralized,
              chronological logging.
              * An EJB tool for Peeking and Poking attributes from EJBs.
              * An EJB Stress test tool.
              * A J2EE global environment tool.
              * A J2EE report tool.
              * A J2EE Scheduler tool.
              * A J2EE Business patrol tool.
              It is written entirely in the Java(TM) programming language.
              The current version support:
              * JOnAS 2.4 and 2.6
              * SunONE 7.0
              * Universal servers.
              * Weblogic 6.1, 7.0 and 8.1
              * Websphere 4.0 and 5.0.2
              * jBoss 3.0 and 3.2
              ********** What is new:
              Version 4.00 November, 2003
              Enhancement:
              1. Support for both native protocol (RMI-IIOP) mode and HTTP/HTTPS
              (with/without proxy) protocol mode for SuperEnvironment,
              SuperLogging, SuperReport and SuperScheduler.
              2. SuperLogging 4.00: tracing can work on both live database and retired database.
              3. SuperReport 3.00: works for both live database and retired database.
              4. SuperScheduler 3.00: add URL job type (for Servlet/JSP). Add DoerTalker Table
              Panel.
              Bug fix:
              1. SuperScheduler 3.00: Interval change did not take effect until restart Super.
              Version 3.00 July, 2003
              Enhancement:
              1. SuperLoggingLibrary 3.00: New implementation for change scope adding "Smart"
              scope,
              with enhancements and bug fixes.
              2. SuperLoggingLibrary 3.00: Support mail server which requires user name and
              password.
              Add MenuTreePanel.
              3. Improved GUI and document.
              4. Add support to WebLogic 8.1.
              Bug fix:
              1. SuperScheduler 2.0: Fix a bug in FutureView for Hourly and Minutely.
              2. SuperScheduler 2.0: Startup should never be reported as missed.
              3. SuperScheduler 2.0: Could not reset job for existing task in some situation.
              Version 2.20 Jan. 2003
              Enhancement:
              1. Add desktop and start menu shortcuts for MS-Windows.
              2. Add support for SunONE 7, JOnAS 2.6 and jBoss 3.0.
              3. SuperLogging 2.40: Add new sendAlarmEmail() method.
              4. SuperScheduler 1.40: Add SuperSchedulerEJB for managing when
              direct database is not practical; Allow user to choose
              favorite logging software; Add Last day as Monthly
              repeating attribute.
              Change:
              1. Change Unusual to PatrolAlarm. The name "Unusual" was misleading.
              Bug fix:
              1. SuperEnvironment 1.31: Bug fix: if database is broken, could not
              open Environment Manager.
              2. SuperLogging client 1.52: Annoying exception thrown when you use
              JDK 1.4 (the program runs okay).
              3. SuperPeekPoke 1.61: Fix bug where input object contains
              java.lang.Double and alike.
              4. SuperScheduler 1.40: Bug fixes in: Memory leak; Reporting
              PatrolAlarm for SuperPatrol; Composite task with members;
              Non-scheduled run on other host; Around edges of last
              days in Monthly with holiday policy.
              Version 2.10 July 2002
              Enhancement:
              1. SuperScheduler 1.3: Add Future View to check future schedule in
              both text and Gantt-chart mode.
              2. SuperScheduler 1.3: Add graphic Gantt view for monitoring task's
              activities.
              3. SuperEnvironment 1.3: uses new graphic package adding print and
              preference facilities.
              4. SuperPeekPoke 1.6: uses new graphic package adding print and
              preference facilities.
              5. SuperStress 1.21: uses new graphic package.
              Bug fix:
              1. SuperStress 1.21: fixed graphic related bugs.
              Version 2.01 June 2002
              Enhancement:
              1. Add options for Look & Feel.
              2. Preference is persistent now.
              Bug fix:
              1. Installation for WebLogic 7.0: extEnv may not be installed on the
              right place, so SuperLibrar on the server side was not loaded and
              causes other problems.
              Version 2.00 June 2002
              Enhancement:
              1. SuperScheduler 1.2: All copies of SuperScheduler refresh themselves
              when any Doer causes things to change.
              2. SuperScheduler 1.2: Support default HTML browser for reading HTML document.
              3. SuperReport 1.2: Support default HTML browser for reading HTML document.
              4. Support WebLogic 7.0.
              5. SuperEnvironment 1.21: Database Panel appears when it is necessary.
              6. SuperEnvironment 1.21: New SuperEnvironment tour.
              Bug fix:
              1. WebSphere Envoy did not always list all JNDI names.
              Version 1.90 May 2002
              Enhancement:
              1. Rewritten SuperLogging engine. Add Alarm Email on SuperLogging.
              2.Rewritten SuperScheduler allowing multiple Doers. Add support to holiday policy,
              effective period. Add Patrol job type as SuperPatrol.
              3. Add support for both JOnAS and jBoss.
              4. Add more elements on Report criteria.
              Change:
              1. Now, both left and right mouse clicks are the same on Table Panel: toggle ascend
              and descend.
              2. New log database.
              Bug fix:
              1. Alert email should be sent once in the interval, regarding number of servers
              in the clustering.
              2. Minor bug fixes to make errors handled better on SuperLogging.
              3. If withFileInfo or withTimestamp are changed alone, Style Panel did not save
              them.
              4. Rewritten SuperLogging and SuperScheduler with many bug fixes.
              Version 1.80 March 2002
              Enhancement:
              1. Add new component: SuperScheduler
              Bug fix:
              1. SuperLogging: Verbose should ignore class registration.
              2. SuperLogging-tracing: an exception was thrown if the java class without package
              name.
              Version 1.70 January 2002
              Enhancement:
              1. SuperLogging: Scope can dynamically change both for upgrade to downgrade (for
              weblogic 6.1, need download an application).
              2. Add alias names for log threshold as new Java suggests.
              3. New component: SuperReport.
              Change:
              1. SuperLogging: Log database parameters are specified in a properties file, instead
              of EJB's deployment descriptor. It is more convenient and it avoids some potential
              problems. No change for development, easier for administration.
              Bug fix:
              1. Add Source Path Panel now accepts both directory and jar file.
              2. Bug in SuperEnvironment example (for version 1.60 only).
              Version 1.60 December 2001
              Enhancement:
              1. SuperPeekPoke and SuperStress can use user defined dynamic argument list.
              2. Add timeout parameter to logging access.
              3. New installation program with A). Easy install. B). Remote command line install.
              4. Support EJB 2.0 for Weblogic 6.1.
              5. Support SuperPeekPoke, SuperEnvironment and SuperStress for Websphere 4.0 (SuperLogging
              was supported since version 1.5).
              Change:
              1. Poke: argument list is set at define time, not invoke time.
              2. Default log database change to server mode from web server mode, booting performance
              to 10-20 times.
              Bug fix:
              1. If the returned object is null, Peek did not handle it correctly.
              2. If the value was too big, TimeSeries chart did not handle it correctly. Now
              it can handle up to 1.0E300.
              3. Help message was difficult to access in installation program.
              4. Source code panel now both highlights and marks the line in question (before
              it was only highlight using JDK 1.2, not JDK 1.3).
              5. Delete an item on PeekPoke and add a new one generated an error.
              Version 1.50 August, 2001
              Enhancement:
              1. Source code level tracing supports EJB, JSP, java helper and other
              programs which are written in native languages (as long as you
              write correct log messages in your application).
              2. Redress supports JSP now.
              3. New installation with full help document: hope it will be easier.
              4. Support WebSphere 4.0
              Version 1.40 June, 2001
              Enhancement:
              1. Add SuperEnvironment which is a Kaleidoscope with TableView, TimeSeriesView
              and PieView for GlobalProperties.
              GlobalProperties is an open source program from Acelet.
              2. SuperPeekPoke adds Kaleidoscope with TableView, TimeSeriesView and PieView.
              Changes:
              1. The structure of log database changed. You need delete old installation and
              install everything new.
              2. The format of time stamp of SuperLogging changed. It is not locale dependent:
              better for report utilities.
              3. Time stamp of SuperLogging added machine name: better for clustering environment.
              Bug fix:
              1. Under JDK 1.3, when you close Trace Panel, the timer may not be stopped and
              Style Panel may not show up.
              Version 1.30 May, 2001
              Enhancement:
              1. Add ConnectionPlugin support.
              2. Add support for Borland AppServer.
              Version 1.20 April, 2001
              Enhancement:
              1. Redress with option to save a backup file
              2. More data validation on Dump Panel.
              3. Add uninstall for Super itself.
              4. Add Log Database Panel for changing the log database parameters.
              5. Register Class: you can type in name or browse on file system.
              6. New tour with new examples.
              Bug fix:
              1. Redress: save file may fail.
              2. Install Bean: some may fail due to missing manifest file. Now, it is treated
              as foreign beans.
              3. Installation: Both installServerSideLibrary and installLogDatabase can be worked
              on the original file, do not need copy to a temporary directory anymore.
              4. PeekPoke: if there is no stub available, JNDI list would be empty for Weblogic5-6.
              Now it pick up all availble ones and give warning messages.
              5. Stress: Launch>Save>Cancel generated a null pointer exception.
              Changes:
              1. installLogDatabase has been changed from .zip file to .jar file.
              2. SuperLogging: If the log database is broken, the log methods will not try to
              access the log database. It is consistent with the document now.
              3. SuperLogging will not read system properties now. You can put log database
              parameters in SuperLoggingEJB's deployment descriptor.
              Version 1.10 Feb., 2001
              Enhancement:
              1. Re-written PeekPoke with Save/Restore functions.
              2. New SuperComponent: SuperStress for stress test.
              3. Set a mark at the highlighted line on<font size=+0> the Source Code
              Panel (as a work-a-round for JDK 1.3).</font>
              4. Add support for WebLogic 6.0
              Bug fix:
              1. Uninstall bean does physically delete the jar file now.
              2. WebLogic51 Envoy may not always list all JNDI names. This is fixed.
              Version 1.00 Oct., 2000
              Enhancement:
              1. Support Universal server (virtual all EJB servers).
              2. Add Lost and Found for JNDI names, in case you need it.
              3. JNDI ComboBox is editable now, so you can PeekPoke not listed JNDI name (mainly
              for Envoys which do not support JNDI list).
              Version 0.90: Sept, 2000
              Enhancement:
              1. PeekPoke supports arbitrary objects (except for Vector, Hashtable
              and alike) as input values.
              2. Reworked help documents.
              Bug fix:
              1. Clicking Cancel button on Pace Panel set 0 to pace. It causes
              further time-out.
              2. MDI related bugs under JDK 1.3.
              Version 0.80: Aug, 2000
              Enhancement:
              1. With full-featured SuperLogging.
              Version 0.72: July, 2000
              Bug fix:
              1. Ignore unknown objects, so Weblogic5.1 can show JNDI list.
              Version 0.71: July, 2000
              Enhancement:
              1. Re-worked peek algorithm, doing better for concurent use.
              2. Add cacellable Wait dialog, showing Super is busy.
              3. Add Stop button on Peek Panel.
              4. Add undeploy example button.
              Bug fix:
              1. Deletion on Peek Panel may cause error under JDK 1.3. Now it works for both
              1.2 and 1.3
              Version 0.70: July, 2000
              Enhancement:
              1. PeekPoke EJBs without programming.
              Bug fix:
              1. Did not show many windows under JDK 1.3. Now it works for both 1.2 and 1.3
              Changes:
              1. All changes are backward compatible, but you may need to recompile monitor
              windows defined by you.
              Version 0.61: June, 2000
              Bug fix:
              1. First time if you choose BUFFER as logging device, message will not show.
              2. Fixed LoggingPanel related bugs.
              Version 0.60: May, 2000
              Enhancement:
              1. Add DATABASE as a logging device for persistent logging message.
              2. Made alertInterval configurable.
              3. Made pace for tracing configurable.
              Bug fix:
              1. Fixed many bugs.
              Version 0.51, 0.52 and 0.53: April, 2000
              Enhancement:
              1. Add support to Weblogic 5.1 (support for Logging/Tracing and
              user defined GUI window, not support for regular monitoring).
              Bug fix:
              1. Context sensitive help is available for most of windows: press F1.
              2. Fix installation related problems.
              Version 0.50: April, 2000
              Enhancement:
              1. Use JavaHelp for help system.
              2. Add shutdown functionality for J2EE.
              3. Add support to Weblogic 4.5 (support for Logging/Tracing and
              user defined GUI window, not support for regular monitoring).
              Bug fix:
              1. Better exception handling for null Application.
              Version 0.40: March, 2000
              Enhancement:
              1.New installation program, solves installation related problems.
              2. Installation deploys AceletSuperApp application.
              3. Add deploy/undeploy facilities.
              4. Add EJB and application lists.
              Change:
              1.SimpleMonitorInterface: now more simple.
              Version 0.30: January, 2000
              Enhancement:
              1. Add realm support to J2EE
              2. Come with installation program: you just install what you want
              the first time you run Super.
              Version 0.20: January, 2000
              Enhancement:
              Add support to J2EE Sun-RI.
              Change:
              1. Replace logging device "file" with "buffer" to be
              compliant to EJB 1.1. Your code do not need to change.
              Version 0.10: December, 1999
              Enhancement:
              1. provide SimpleMonitorInterface, so GUI experience is
              not necessary for developing most monitoring applications.
              2. Sortable table for table based windows by mouse
              click (left or right).
              Version 0.01 November., 1999:
              1. Bug fix: An exception thrown when log file is large.
              2. Enhancement: Add tour section in Help information.
              Version 0.00: October, 1999
              Thanks.
              

  • Site web analytics report shows no data

    Hi All, 
    A user reported that they could not view the site web analytics report
    in the SharePoint 2013 production server.  It was working fine a few couple of weeks back though.
    I started the troubleshooting for this issue and came cross a few blogs that details the same issue. 
    There were my steps: 
    In Central Admin (CA) >> Service Applications >> Usage and Health data collection was
    started. 
    CA >>
    Monitoring >> Reporting >> "Enable usage and health data collection"
    was checked. 
    CA >> Monitoring >> Timer Jobs > Review job definitions
     >> Microsoft SharePoint Foundation Usage Data Import
    (5 minutes) and Microsoft SharePoint Foundation Usage Data Processing
    was enabled. I clicked on "Run Now" on these job schedules. 
    CA >> Search Service Application >>
    Under  Mange Content Sources page
    the status was Idle.
    We have performed the full crawl a few days back. 
    PowerShell: Read the  Brian
    T. Jackett's blog. Basically, he uses PowerShell to trigger the  Receivers
    for the AnalyticsUsage and PageRequest
    and enable these Receivers for Analytics and Page Requests. In the
    production environment these receivers were already defined and I just executed them again. Ran the
    OWSTimer service for all SharePoint servers. However, after 2 days no data was shown. 
    The only thing we have not checked is WSS_Logging database. 
    We are stuck in this issue and its OOTB feature. 
    Any pointers for this issue will be highly appreciated. 
    Thanks in advance.
    Regards, 
    Aroh
    Aroh Shukla

    Hi Aroh,
    Please refer to the article:
    http://blog.fpweb.net/troubleshooting-sharepoint-2013-web-analytics/#.VNcSsf4fqM8
    There are still some place you could check for general troubleshooting steps, such as:
    1.Did you configure AAM recently that might affect this?
    2.Does related timer jobs run successfully?
    Regards,
    Rebecca Tu
    TechNet Community Support

  • Compare reporting tools

    Hi,
    Could some one point in the right direction - we are trying to finalize the reporting tool.
    We have worked with BI-Publisher(not as dynamic) and Discoverer(formatting a big issue) - trying to find a tool that would overcome the limitations that these 2 tools have.
    We want to be able to use Oracle Db, VPD, set client_id using OPD.Net, integrate with web application as key requirements. By same token would like to be able to create dynamic reports which allows a great deal of flexibility. Is there such a reporting tool?
    Any ideas much appreciated.
    Thanks!

    Hi
    I'll try and answer your questions.
    1. Xml, Sql(either a view or stored proc) as input
    data sourceYou can base an Apex report on a view or mod/plsql procedure, or use xmldb.
    2. support odp.net providerAs I understand it odp.net is a tool used by .net to access Oracle. Apex is a database tool so all the data and code, everything is in the database.
    3. Work with VPD - virtual private database Yes.
    4. single-sign-on, and setting client_identifier on
    connection.Yes
    5. Integrate with existing web application(asp.net
    2.0)Not sure what integration you want.
    6. This tool is free right, to be used with Oracle
    10g database.Free and can be used with 10g or 9i databases.
    Rod West

  • Reporting Tools

    I'm relatively new to BW...I've been supporting it internally for our company for the last year+, but I come from a .NET background.  My questions are in regards to the reporting tools that people use at different implementations.  We use the BEx Analyzer with BW 3.5, but have been relatively disappointed with the user interface and the performance of the queries.  We'll be upgrading to Netweaver BI after the first of the year.
    1.  What other reporting tools (3rd party, web tools, etc.) have people used and how have they performed with BW/BI?
    2.  How much of an improvement, either in performance or the user interface, is there with the upgrade to BI?
    I appreciate any help.
    Thanks,
    Tony

    1. There are few third party reporting tools you can integrate with BW data like Business Object, Cognos Reporting sofware, Hyperion etc. All are pretty good.
    2. If you are upgrading to BI 7.0, there are lots of new features added to BW/BI reporting tools and one new tool added is Report Designer.
    If you are really upgrading to BI 7.0, I don't think you need any third party tools but again it depends on totally what tool you are comfortable with.
    Regards,
    Ashok

  • Reporting tools and SAP BW

    Dear Sirs,
    We have Business Objects BI 4.0 and SAP BW 7.3.
    Actually we are using Web Intelligence and BEx Query to reporting.
    We have not Business Layer (Universe) between BW and BO because BO it's not supported to create universe (unx) on BW. So we create document in WEBI using BEx Query.
    We want to use Xcelsius (Dashboard Design) 2011 and I was thinking that we can use query from universe to connect with BW (new functionality in version 2011). Can we? Or maybe we should to connect to BW using "Connecttion to SAP BW"?
    We want to use Explorer (on iPad and iPhone), but Explorer requires universe (unx).
    Is not possible to create universe (unx, because unv is not supported via Explorer) based on SAP BW, is it true?
    We should we do, when we want to use Explorer with SAP BW?
    Do I understand connection between reporting tools and SAP BW:
    Crystal Reports - can I use cubes or BEx queries
    Xcelsius - using "Connection to SAP BW"
    WEBI - BExqueries or universe (but only UNV - old version).
    Explorer - in my opinion is not possible
    Analysis for OLAP - drirect to cube in SAP BW
    Could you please comment.

    Hi
    With the current version of the BI 4.0 SP2 BI Platform, one cannot create a universe (.UNX format) against BW using the OLAP connection. However you can create a universe (.UNX format) using the Relational connection (see OSS note: 1656905 - How to create UNX universe based on Business Warehourse InfoCubes). One limitation is the use of hierarchies with the relational connection.
    Then you can create the Information spaces based on the universe (.UNX format) that the Explorer can use.
    BO Reporting tools:
    1. Crystal Reports for Enterprise = you can use the OLAP connection (BICS) directly against the BW InfoCubes or Queries, if queries already exist in the BW system then you can leverage these directly (less time spent recreating the entire query in Crystal)
    2. Xcelsius = you can use the BICS or Web Service or Universe to access the data
    3. Web Intelligence = you can use the OLAP Connection (BICS)
    4. Explorer = you can use a universe (.UNX format) via a Relational Connection
    5. Analysis for OLAP = you can use the OLAP connection (BICS) to either a query or InfoCube.
    It is hoped that in Feature Pack 3 which will be released later this year, that missing functionalities will be delivered for BI 4.0.
    Regards
    Derek

  • BW (BEx) and BOBJ Reporting-Tools

    Hi All,
    I'm looking for an article or anything, that describes the difference between SAP BW (BEx) and Business Objects- Reporting tools .
    which tools is suitable for what purpose?
    thanks
    brad

    This isn't mine - it may even be yours - but just in case anyone looks at this thread, here it is
    BO vs BEx 
    Ease of use:
    BO - Very user friendly interface, Minimal requirement for MDX code, Some queries take more time in BO analysis, when compared to BEx Analyzer
    BEx - Difficult self service reporting and analytics, Being Excel based, it needs extensive VBA or Macro programming for a great UI
    Features:
    BO - Export functionality (PDF, MSOffice etc), More chart types, Has more advanced features, Design and Preview Tab in the same page, Provides offline capabilities
    BEx - Is mostly for SAP only but With integration can access BEx query from BO, Web App Designer is effort intensive, Build and preview are separate views
    Support from SAP:
    BO - Part of SAP integration roadmap, All current and future dev. in the BI front-end is focused on the SAP BO BI solutions, Crystal Reports is now main reporting tool, replacing BEx Report Designer
    BEx - BEx is no longer the strategic direction, BEx product line will be phased out completely by 2016
    Compatibility with other data source:
    BO - Able to merge data from various sources in the same report, Can connect to any Database, very flexible in design
    BEx - Gets data from BI
    Implementation effort and ownership cost:
    BO - Longer deployment period compared to BEx, Additional server needed, May require additional components setup for BW, May need separate license for Business Objects Enterprise (BOE) platform, BO uses OLEDB for OLAP API via BEx query, may cause an overhead, BW Accelerator may be needed to improve query response time, scalability and visibility.
    BEx - Only MS office and BEx client are needed for installation, BEx is bundled with NetWeaver

Maybe you are looking for