![]() ![]() So if we focus on regression testing the impact that changes to the RPD have on the data alone then the available methods become clearer and easier. Whenever the RPD changes, the way in which any logical query is handled may change. analysis/dashboard data requests) are compiled into Physical SQL for sending to the data source(s) at runtime only. Because of this abstraction it means that all Logical queries (i.e. How the BI Server responds to data requests (in the form of Logical SQL queries) is governed by the RPD, the metadata model that abstracts the physical source(s) into a logical Business model. Obviously the data gets processed further in graphs, pivot tables, narrative views, and so on - but the actual filtering, aggregation and calculation applied to data is all complete by the time that it leaves the BI Server. The data that it passes back up to Presentation Services for rendering in the user’s web browser is the raw data that feeds into what the user will see. ![]() Looking at the following diagram of a request/response through the OBIEE stack we can see that so far as data is concerned, it is the BI Server doing all the work, handling both logical and physical SQL and data sets: But a system that gives users wrong data, or no data, is fundamentally a failed one. ![]() Obviously, there are other factors in making users happy not least performance and the visual appearance of the data. If it’s wrong, that’s bad, and if it’s right, hopefully they’re going to be happy. ![]() The data should arguably be what is most important to our users. So if not at the front end, then where should we focus our automated regression testing of OBIEE? Answer: the data. “Bring me solutions not problems” goes the mantra, and in the first article all I did was rain on the parade of the de facto regression testing approach, looking at the front end using functional testing tools such as Selenium. Easy Automated RPD regression testing - it’s all about the numbers In this posting, I explore some approaches that lend themselves well to automation for testing that existing analyses and dashboards are not affected by RPD changes. Search Search for: Follow The Data Community on WordPress.In the first article of this series I explored what regression testing is, why it matters, and by breaking down the OBIEE stack into its constituent parts where it is possible to do it for OBIEE. You can then use the interface to browse the catalog and perform other tasks on catalog objects. Accessing Catalog Manager in this way is most likely needed when you need to connect in Online mode.Īnd then of course, you need to enter the URL – which is the full path to the catalog, for example:/instances/instance1/bifoundation/OracleBIPresentationServicesComponent/coreapplication_obips1/catalog/defaultĪssuming everything was entered correctly, you will be connected to the catalog. This will start Catalog Manager, and it will be running on the Linux server, but the screens will be showing on your desktop/laptop.įrom the main Catalog Manager window, you can then click on File –>Open CatalogĪnd then select the Type based on how you want to connect – Online or Offline mode. Then go to the catalog manager directory:Ĭd /instances/instance1/bifoundation/OracleBIPresentationServicesComponent/coreapplication_obips1/catalogmanager Ĭonnect to your Linux server from your desktop/laptop using Putty (or other tool). Start Xming (or another X-Windows type tool) on your local PC or laptop. There are times when it is required that you run the Catalog Manager in offline mode, and at those times you will be required to run it on the server.Īlthough there is a command line option for Catalog Manager, it is easier to work with it in a Graphical User Interface (GUI) mode and at times its necessary to use that mode. OBIEE Catalog Manager can be accessed from a client tool on Windows or from a server side process. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |