Question 1 : Are you using IIS or oc4j for BI Publisher? Answer: BI Publisher can never work on IIS.

It needs Oracle containers for Java(oc4j) for its deployment. However, you can configure IIS as a listener for oc4j. And this can be done via IIS Proxy Plug-in which comes with OBIEE Installation files. When configured, the requests are routed from IIS to oc4j so that it appears to the user that everything is being executed by IIS. Question 2: How many types of security model is possible in BI Publisher? Answer: There are 5 types of security model in BI Publisher 1. 2. 3. 4. 5. Oracle BI Server BI Publisher Security LDAP Oracle Database Oracle E-Business suite

Question 3: Which type of Security model are you using in your Project? Answer: That depends on your project. Generally first 2 types are used. For Oracle BI server security model, users are defined in repository. For BI Publisher Security, users are defined in BI Publisher Application Admin tab>Security Center Question 4: What is super user and where do you create it?

Answer: Super User is independent of security model. He can login to the BI Publisher application with any type of security model. We can create super user from BI Publisher application Admin tab>Security Center>Security Configuration

Tag: http://knoworacle.wordpress.com/2010/05/20/oracle-bi-publisher-xml-publisher-general-questions/

XML/BI Publisher gives the flexibility to users inorder to select the output type in EXCEL/HTML/PDF/FO, etc as per their requirement. If a User ran a report in PDF and wants to get the same in EXCEL, its not required for them to re-run the report, Instead they can republish it using RePublish option in Tools and can select the output type whatever is required. XML/BI Publisher reports gives you additional features for Reports 6i. You can get the XML Report in EXCEL/HTML/PDF etc as per the output type selected. Data Model in Reports 6i RDF will be the same but you dont require a Layout model in the RDF File. You instead create the Layout in a Word Document using the XML Publisher Destop installed. You can directly implement XML Publisher and is not required to implement Discoverer again. Before the release of Discoverer 10g, Discoverer is a license free version and after its release the license has become too costly due to which the clients are going for XML Publisher reports ignoring Discoverer.

Advantages of XML/BI Publisher: * Cost for implementing is very less compared to the license of Discoverer. * Can create complex layouts same as we do it in Report 6i, where as complex reporting is not possible in Discoverer. * Can run the report in 5 different Output Formats and export them. * If you require the report in 3 different output types, You dont need to run the report 5 times. You can run the report once and can republish it again in other types. * You dont require any different web browser for running the report, It can be directly run on the Concurrent Environment itself. * You can code the report to dynamically select the layouts (templates) in XML Publisher, Similar to the functionality of Format Trigger in Reports 6i which is not possible in Discoverer. Limitations/Disadvantages of XML/BI Publisher: * Its not recommended for ad-hoc reporting like Discoverer. * Its very hard to debug a report unlike Discoverer. * We cant draw Pie Charts/Graphs as like in Discoverer.

It is the result of the Siebel Answers query using the Supplier SalesCatalog. ABC Company has employed more than 200 sales reps in the year 1998 and 1999.Which of the following is NOT true of the Exhibit? A. The query was filtered by the sales reps' first names B. The results' layout includes Title, Chart, and T able views C. The query was sorted by the Dollars (ascending) D. The SQL query issued is "SELECT Customers."Sales Rep" saw_0,Periods."Y ear" saw_1,SalesFacts.Dollars saw_2 FROM SupplierSales WHERE Customers."Sales Rep"< 'D' Answer: C
9985144444-bhart