Discoverer Best Practices

Hi all,
I would like to know wich is the best practice on discoverer (admin and desktop)... I have to create new report on discov. And I was thinking what is the best, to create on dscvr admin a new folder (as custom or from data base) with all the conditions I need, applied on it. Or create a general folder and then create all the conditions I need on discoverer desktop?.
I really don't know exactly how discov works internally... so I thought that maybe there are some best practices for performance
Regards,
Belen

Yes, I've read both Manuals... but what I need is different opinions about the experience of anyone that works with discov. There are some kind of things to perform as a Discov administrator and discov report developer that I cannot perform because of the way the Company is organized.
So, for me is usefull if someone could help me with expirience.
Regards,
Belen

Similar Messages

  • BEST PRACTICES FOR CREATING DISCOVERER DATABASE CONNECTION -PUBLIC VS. PRIV

    I have enabled SSO for Discoverer. So when you browse to http://host:port/discoverer/viewer you get prompted for your SSO
    username/password. I have enabled users to create their own private
    connections. I log in as portal and created a private connection. I then from
    Oracle Portal create a portlet and add a discoverer worksheet using the private
    connection that I created as the portal user. This works fine...users access
    the portal they can see the worksheet. When they click the analyze link, the
    users are prompted to enter a password for the private connection. The
    following message is displayed:
    The item you are requesting requires you to enter a password. This could occur because this is a private connection or
    because the public connection password was invalid. Please enter the correct
    password now to continue.
    I originally created a public connection...and then follow the same steps from Oracle portal to create the portlet and display the
    worksheet. Worksheet is displayed properly from Portal, when users click the
    analyze link they are taken to Discoverer Viewer without having to enter a
    password. The problem with this is that when a user browses to
    http://host:port/discoverer/viewer they enter their SSO information and then
    any user with an SSO account can see the public connection...very insecure!
    When private connections are used, no connection information is displayed to
    SSO users when logging into Discoverer Viewer.
    For the very first step, when editing the Worksheet portlet from Portal, I enter the following for Database
    Connections:
    Publisher: I choose either the private or public connection that I created
    Users Logged In: Display same data to all users using connection (Publisher's Connection)
    Users Not Logged In: Do no display data
    My question is what are the best practices for creating Discoverer Database
    Connections.
    Is there a way to create a public connection, but not display it in at http://host:port/discoverer/viewer?
    Can I restrict access to http://host:port/discoverer/viewer to specific SSO users?
    So overall, I want roughly 40 users to have access to my Portal Page Group. I then want to
    display portlets with Discoverer worksheets. Certain worksheets I want to have
    the ability to display the analyze link. When the SSO user clicks on this they
    will be taken to Discoverer Viewer and prompted for no logon information. All
    SSO users will see the same data...there is no need to restrict access based on
    SSO username...1 database user will be set up in either the public or private
    connection.

    You can make it happen by creating a private connection for 40 users by capi script and when creating portlet select 2nd option in Users Logged in section. In this the portlet uses there own private connection every time user logs in.
    So that it won't ask for password.
    Another thing is there is an option of entering password or not in ASC in discoverer section, if your version 10.1.2.2. Let me know if you need more information
    thnaks
    kiran

  • Multi-Language support in Discoverer? Best-Practice?

    Dear experts,
    wondering if there is a best practice to provide workbooks/EULs in different languages? Actually we use Business Objects (BO 5.xx) but want to switch to Discoverer. As BO also does not support multiple languages we use as a workaround the VB-interface to translate the text and labels in our reports and universes (EUL) regarding to particular label numbers. Is there some kind of similar interface for browsing/changing Discoverer EULs?
    Do you think the following could work:
    In the "genuine" EUL you specify a unique number to any attibute of an element and after each you start a kind of translation procedure generating two new EULs (e.g. EUL_EN (english) and EUL_DE (german)) with translated labels (Name and Headline attibute of an element).
    As far as I understood the structure of Discoverer's EULs, all attibutes are stored in the database, so it should be possible to find out, which holds the "Name" and which the "Headline" attribute...
    Got what I want?
    At least I need to understand the data model of the EULs...
    Regards,
    Ralf

    Hi Ralf,
    There are 2 types of translations you might want to do: the names and descriptions of your Business Areas,Folders and Items etc in the EUL and the labels and titles in the workbooks.
    To translate the Descriptions in the EUL the easiest approach will be to export the EUL into an .eex file or each component into a .eex file using a script. These .eex files are in fact XML files and the names and descriptions are attributes of the XML BA, folder and item elements. You can then translate these and then import the eex file(s) into a new EUL for the new language.
    Another approach to consider (especially if you are using Discoverer with Oracle Applications and your translations are already held in the database) is to create a language specific EUL. You will need to use the command line to do this and specify the EUL language when you create the EUL. Then import your EUL into the new language specific EUL and use the folder refresh to pick up the translated text from the database. You will probably need to write a EUL_TRIGGER$REFRESH_NEW_COLUMN to do this. If you are using the Business Intelligence views some translations may be done for you when you refresh. I think taking this approach will be a challenge.
    I am afraid there is no easy way to translate the labels and titles in the workbooks. You will have to manually open each workbook in the new EUL, translate the text and save it.
    Hope that helps,
    Rod West

  • Discoverer Adm. Best Practices

    Hi All,
    I'm doing a consultancy job for this Company and when they heard I know Oracle Discoverer, they asked me to create some kind of document to evaluate what they have developed here using Discoverer. Plus they want me to create a "Best Practices" document for creating business areas.
    Well... I must confess I don't know discoverer that well ;-).
    So, I'd like to hear from experienced users how you guys do this kind of job. What should I look for to see what is right, what is wrong, what can we do to make it better.. The usual stuff.
    I've been looking for security issues (they grant privileges to users, instead of having roles, etc). But I guess I won't be able to do any report without talking to end-users (those who develop reports using Discoverer Desktop/Plus/whatever...).
    Please, tell me what you think about it and what else shoul I look for. At this moment, I'm not sure where should I point my efforts to...
    Thanks in advance,
    Marcos

    Hey Marcos.
    Big #1 question - are they running Oracle Apps (Enterprise Suite) or not. I'm guessing not as you mentioned roles instead of responsibilities?
    Otherwise - regardless if it's roles or responsibilities (and all my experienced opinion).
    1. Do not grant privs or share bus areas with users - only roles or responsibilites. Why? There's lots of reasons, but for a few, it's way cleaner to have job assignments (roles, etc.) so that when someone moves jobs, promoted, etc., all the existing privs, security keeps on working PLUS you don't have to share workbooks with numerous people, but just their role / resp. Also, when someone leaves, you have have a problem in getting rid of any workbooks they've created - as not even the admin can see a user's report in the database if not shared with them.
    2. Are they using Disco desktop, plus or viewer?
    Now I know some may prefer it differently (had this discussion before on this forum), but if there's lots of users, I try to give Disco Viewer to the vast majority of end users because end users (99% of the time - and I'm sure I'll get slammed for this) - SHOULD NOT BE WRITING REPORTS. Most of the time, they'll screw up and choose too many folders and wonder what a fan trap means, do dumb conditions (such as multiple not ins, multiple queries with %, etc.) and their reports run like a dog.
    For the couple in each department who are tech savvy and want to help others in their department, these ones become power users and they can have Disco Plus or Desktop to create the reports.
    3. Create one user called something like: CORP. This user is (for example), you. With your Discoverer brilliance, you are in charge of creating workbooks that are the CORP standard that work corerctly, look pretty (with corp approved logos, colors, etc.) and are shared with the correct roles / resp. If a power user creates a good report, get them to share it with CORP, you CORP-orize it, check it and it becomes the CORP standard. This alone has worked great in all the Disco contracts I've been on - once the company buys into it.
    4. In the EUL, you try and set up business areas that are logical (ie: either by geographical area (ie: US AR, MX AR, etc.), or by business job (ie: AR, AP, GL), or a combination of both (usually what it evolves to over time).
    5. In the EUl, - if possible - identify the indexes. This makes a huge difference if users can be taught to limit workbooks if at all possible to indexes in a condition. I leanred this long ago with working for years with NoetixViews (a Disco view product) where indexes in folders (ie: pointing to views in the database) are identified with a prefix of A$.
    6. Always, always ... sort your items in the folders in the business area. Sure, if you're using 10+, you can do it automatically, but if a product before (ie: 4i), then do it manually. It sounds dumb, but makes a huge difference for you - and end users - creating reports as you find items way, way quicker.
    That's the first 6. I'm sure more'll be added.
    Russ

  • Best Practice regarding using and implementing the pref.txt file

    Hi All,
    I would like to start a post regarding what is Best Practice in using and implementing the pref.txt file. We have reached a stage where we are about to go live with Discoverer Viewer, and I am interested to know what others have encountered or done to with their pref.txt file and viewer look and feel..
    Have any of you been able to add additional lines into the file, please share ;-)
    Look forward to your replies.
    Lance

    Hi Lance
    Wow, what a question and the simple answer is - it depends. It depends on whether you want to do the query predictor, whether you want to increase the timeouts for users and lists of values, whether you want to have the Plus available items and Selected items panes displayed by default, and so on.
    Typically, most organizations go with the defaults with the exception that you might want to consider turning off the query predictor. That predictor is usually a pain in the neck and most companies turn it off, thus increasing query performance.
    Do you have a copy of my Discoverer 10g Handbook? If so, take a look at pages 785 to 799 where I discuss in detail all of the preferences and their impact.
    I hope this helps
    Best wishes
    Michael Armstrong-Smith
    URL: http://learndiscoverer.com
    Blog: http://learndiscoverer.blogspot.com

  • Best practice for upgrading from ADS 9.1 to ADS 11

    So we will need start upgrading installs from Advantage Database Server (ADS) version 9 to ADS version 11. Is there a set of best practices? Certain procedures? How do we gracefully fall back if it doesn't work? Does anyone have experience with the dual install setup of ADS 9 and ADS 11? Did anyone else run into any issues with this upgrade path?
    Thanks in advance!
    Rodney

    Rodney,
      My first recommendation is to read the "Effects of Upgrading" section of the help file. I put the links below.
    Effects of Upgrading to Version 10
    Effects of Upgrading to Version 11
    Effects of Upgrading to Version 11.1
      The server will always work with an older client so I would recommend upgrading the server and testing it with your current application. The next step would be to upgrade the client and re-compile your application. I wouldn't anticipate any issues other than those outlined in the effects of upgrading.
      You can install multiple instances of Advantage, beginning with version 10, on the same machine. Keep in mind that only one instance, the first one installed, will be discoverable. To connect to other instances you will need to use <IP Address>:<Port> in the connection string. Details on installing additional instances of Advantage are here
    Chris

  • Best Practices for creating PDFs using PLPDF?

    Does anyone have any suggestions for Best Practices in making PDF files using PLPDF?
    I have been using it for about a month now, and the best that I have come up with is to use MS Access to prototype the layout of a report. Once I have all the graphics areas and text areas lined up how I would want them, I then write PLSQL code to create a procedure which is called from an HTMLDB page. MS Access is handy in that it provides the XY coordinates for each text area and graphics area. It also provides the dimensions of the respective cells. So long as I call plpdf.Init('P', 'in', 'letter') at the beginning of the procedure, both my MS Access prototype and my plpdf code are both using inches - this makes the translation relatively easy.
    Has anybody found anything else easier/better?
    Regards,

    You can make it happen by creating a private connection for 40 users by capi script and when creating portlet select 2nd option in Users Logged in section. In this the portlet uses there own private connection every time user logs in.
    So that it won't ask for password.
    Another thing is there is an option of entering password or not in ASC in discoverer section, if your version 10.1.2.2. Let me know if you need more information
    thnaks
    kiran

  • Best Practices for Creating eLearning Content With Adobe

    As agencies are faced with limited resources and travel restrictions, initiatives for eLearning are becoming more popular. Come join us as we discuss best practices and tips for groups new to eLearning content creation, and the best ways to avoid complications as you grow your eLearning library.
    In this webinar, we will take on common challenges that we have seen in eLearning deployments, and provide simple methods to avoid and overcome them. With a little training and some practice, even beginners can create engaging and effective eLearning content using Adobe Captivate and Adobe Presenter. You can even deploy content to your learners with a few clicks using the Adobe Connect Training Platform!
    Sign up today to learn how to:
    -Deliver self-paced training content that won't conflict with operational demands and unpredictable schedules
    -Create engaging and effective training material optimized for knowledge retention
    -Build curriculum featuring rich content such as quizzes, videos, and interactivity
    -Track program certifications required by Federal and State mandates
    Come join us Wednesday May 23rd at 2P ET (11A PT): http://events.carahsoft.com/event-detail/1506/realeyes/
    Jorma_at_RealEyes
    RealEyes Connect

    You can make it happen by creating a private connection for 40 users by capi script and when creating portlet select 2nd option in Users Logged in section. In this the portlet uses there own private connection every time user logs in.
    So that it won't ask for password.
    Another thing is there is an option of entering password or not in ASC in discoverer section, if your version 10.1.2.2. Let me know if you need more information
    thnaks
    kiran

  • What are the best practices for the RCU's schemas

    Hi,
    I was wondering if there is some best practices about the RCU's schemas created with BIEE.
    I already have discoverer (and application server), so I have a metadata repository for the Application Server. I will upgrade Discoverer 10g to 11, so I will create new schema with RCU in my metada repository (MR) of the Application Server. I'm wondering if I can put the BIEE's RCU schemas in the same database.
    Basically,
    1. is there a standard for the PREFIX ?
    2. If I have multiple components of Fusion in the same Database, I will have multiples PREFIX_MDS schema ? Can they have the same PREFIX ? Or They all need to have a different prefix ?
    For exemple: DISCO_MDS and BIEE_MDS or I can have DEV_MDS and this schema is valid for both Discoverer and BIEE.
    Thank you !

    What are the best practices for exception handling in n-tier applications?
    The application is a fat client based on MVVM pattern with
    .NET framework.
    That would be to catch all exceptions at a single point in the n-tier solution, log it and create user friendly messages displayed to the user. 

  • Scheduled Tasks - Administrator Best Practices

    Hi all,
    I've gotten assistance this week with a couple scripts and scheduling them as tasks. I actually have well over a dozen running on our Exchange server using a special user with a complex password. This user is not used for logging into any machine, but it
    is a member of 'Administrators' group and can be used for tasks requiring elevated privileges.
    What I am interested in learning is what the best practice is for running scheduled tasks. We have several, such as querying AD for members of select OUs or users who meet certain criteria. We also have automated emails regarding certain mailbox metrics,
    etc. You get the idea.
    Despite the complex credentials, this account is still discoverable and could be used in nefarious ways. Is it possible be running tasks on Server 2008 R2 (2012 possibly) without administrator credentials? Are there certain restrictions for the tasks (like
    is a scheduled reboot allowed by a standard account, but not querying Active Directory?).
    I also have noticed a checkbox with 'Run with  highest privileges' and do not fully understand what this means.
    When I try to run the task as a regular user (no remote permissions) and it says 'Logon failure: the user has not been granted the requested logon type as this computer.'
    In short, can I safely remove our special user account from 'Administrators' and place into regular users without breaking all of our tasks?

    Hi KSI-IT,
    Firstly, based on my research, if you want to run the task scheduler with a user account, the user account must have the corresponding permission, in other words, you can also manually run the script with the user account.
    1.  For the error you posted 'Logon failure: the user has not been granted the requested logon type as this computer', please make sure the task account has "logon as a batch job" privilege.
    To add the privilege of the account, please go to
    [Local Security policy\Local Policies\User Rights Assignment]
    -Log on as a batch job.
    Add the domain\username account and any others you may need and retry.
    2.  For the setting 'Run with  highest privileges', this means that it runs with the highest privileges available to that user. This is different from the context menu's 'Run As Admin'.
    It generates the highest privilege token for the specific user, however, it cannot run as a different user, for a standard user with no elevated permissions, 'Run with highest privileges' does not do anything.
    Reference from:
    What
    effect does "run with highest priviledges" in task scheduler have on powershell scripts?
    I hope this helps.

  • Best Practices Java 1.6.0.24 Runtime parameters

    Hi,
    We're deploying Java 1.6.0.24 for 300 end-users on ERP 11.5.10 CU2 on Linux.
    We would like to know what are the Best Practices for Java 1.6.0.24 Runtime parameters.

    Please also see these docs.
    Recommended Client Java Plug-in (JVM/JRE) For Discoverer Plus 10g (10.1.2) [ID 465234.1]
    Diagnosing Forms Mouse Focus Problems Using JRE [ID 760250.1]
    Login Loop on Internet Explorer after Session Timeout using JRE 1.6.0_18 [ID 1078228.1]
    How Are The Forms JAR Files Stored with Sun JRE [ID 1058882.1]
    Thanks,
    Hussein

  • Logical level in Fact tables - best practice

    Hi all,
    I am currently working on a complex OBIEE project/solution where I am going straight to the production tables, so the fact (and dimension) tables are pretty complex since I am using more sources in the logical tables to increase performance. Anyway, what I am many times struggling with is the Logical Levels (in Content tab) where the level of each dimension is to be set. In a star schema (one-to-many) this is pretty straight forward and easy to set up, but when the Business Model (and physical model) gets more complex I sometimes struggle with the aggregates - to get them work/appear with different dimensions. (Using the menu "More" - "Get levels" does not allways give the best solution......far from). I have some combinations of left- and right outer join as well, making it even more complicated for the BI server.
    For instance - I have about 10-12 different dimensions - should all of them allways be connected to each fact table? Either on Detail or Total level. I can see the use of the logical levels when using aggregate fact tables (on quarter, month etc.), but is it better just to skip the logical level setup when no aggregate tables are used? Sometimes it seems like that is the easiest approach...
    Does anyone have a best practice concerning this issue? I have googled for this but I haven't found anything good yet. Any ideas/articles are highly appreciated.

    Hi User,
    For instance - I have about 10-12 different dimensions - should all of them always be connected to each fact table? Either on Detail or Total level.It not necessary to connect to all dimensions completely based on the report that you are creating ,but as a best practice we should maintain all at Detail level only,when you are mentioning any join conditions in physical layer
    for example for the sales table if u want to report at ProductDimension.ProductnameLevel then u should use detail level else total level(at Product,employee level)
    Get Levels. (Available only for fact tables) Changes aggregation content. If joins do not exist between fact table sources and dimension table sources (for example, if the same physical table is in both sources), the aggregation content determined by the administration tool will not include the aggregation content of this dimension.
    Source admin guide(get level definition)
    thanks,
    Saichand.v

  • Best practices for setting up users on a small office network?

    Hello,
    I am setting up a small office and am wondering what the best practices/steps are to setup/manage the admin, user logins and sharing privileges for the below setup:
    Users: 5 users on new iMacs (x3) and upgraded G4s (x2)
    Video Editing Suite: Want to connect a new iMac and a Mac Pro, on an open login (multiple users)
    All machines are to be able to connect to the network, peripherals and external hard drive. Also, I would like to setup drop boxes as well to easily share files between the computers (I was thinking of using the external harddrive for this).
    Thank you,

    Hi,
    Thanks for your posting.
    When you install AD DS in the hub or staging site, disconnect the installed domain controller, and then ship the computer to the remote site, you are disconnecting a viable domain controller from the replication topology.
    For more and detail information, please refer to:
    Best Practices for Adding Domain Controllers in Remote Sites
    http://technet.microsoft.com/en-us/library/cc794962(v=ws.10).aspx
    Regards.
    Vivian Wang

  • Add fields in transformations in BI 7 (best practice)?

    Hi Experts,
    I have a question regarding transformation of data in BI 7.0.
    Task:
    Add new fields in a second level DSO, based on some manipulation of first level DSO data. In 3.5 we would have used a start routine to manipulate and append the new fields to the structure.
    Possible solutions:
    1) Add the new fields to first level DSO as well (empty)
    - Pro: Simple, easy to understand
    - Con: Disc space consuming, performance degrading when writing to first level DSO
    2) Use routines in the field mapping
    - Pro: Simple
    - Con: Hard to performance optimize (we could of course fill an internal table in the start routine and then read from this to get some performance optimization, but the solution would be more complex).
    3) Update the fields in the End routine
    - Pro: Simple, easy to understand, can be performance optimized
    - Con: We need to ensure that the data we need also exists (i.e. if we have one field in DSO 1 that we only use to calculate a field in DSO 2, this would also have to be mapped to DSO 2 in order to exist in the routine).
    Does anybody know what is best practice is? Or do you have any experience regarding what you see as the best solution?
    Thank you in advance,
    Mikael

    Hi Mikael.
    I like the 3rd option and have used this many many times.  In answer to your question:-
    Update the fields in the End routine
    - Pro: Simple, easy to understand, can be performance optimized  - Yes have read and tested this that it works faster.  A OSS consulting note is out there indicating the speed of the end routine.
    - Con: We need to ensure that the data we need also exists (i.e. if we have one field in DSO 1 that we only use to calculate a field in DSO 2, this would also have to be mapped to DSO 2 in order to exist in the routine). - Yes but by using the result package, the manipulation can be done easily.
    Hope it helps.
    Thanks,
    Pom

  • Temp Tables - Best Practice

    Hello,
    I have a customer who uses temp tables all over their application.
    This customer is a novice and the app has its roots in VB6. We are converting it to .net
    I would really like to know the best practice for using temp tables.
    I have seen code like this in the app.
    CR2.Database.Tables.Item(1).Location = "tempdb.dbo.[##Scott_xwPaySheetDtlForN]"
    That seems to work, though i do not know why the full tempdb.dbo.[## is required.
    However, when i use this in the new report I am doing I get runtime errors.
    i also tried this
    CR2.Database.Tables.Item(1).Location = "##Scott_xwPaySheetDtlForN"
    I did not get errors, but I was returned data i did not expect.
    Before i delve into different ways to do this, i could use some help with a good pattern to use.
    thanks

    Hi Scott,
    Are you using the RDC still? It's not clear but looks like it.
    We had an API that could piggy back the HDBC handle in the RDC ( craxdrt.dll ) but that API is no longer available in .NET. Also, the RDC is not supported in .NET since .NET uses the framework and RDC is COM.
    Work around is to copy the temp data into a data set and then set location to the data set. There is no way that I know of to get to the tempdb from .NET. Reason being is there is no CR API to set the owner of the table to the user, MS SQL Server locks the tempdb to that user has exclusinve rights on it.
    Thank you
    Don

Maybe you are looking for