Strict Standards: Non-static method JLoader::import() should not be called statically in /home/content/19/13966119/html/adivanew/libraries/joomla/import.php on line 29

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/content/19/13966119/html/adivanew/libraries/loader.php on line 71

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/content/19/13966119/html/adivanew/libraries/joomla/import.php on line 32

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/content/19/13966119/html/adivanew/libraries/loader.php on line 71

Strict Standards: Non-static method JLoader::load() should not be called statically in /home/content/19/13966119/html/adivanew/libraries/loader.php on line 161

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/content/19/13966119/html/adivanew/libraries/loader.php on line 138

Strict Standards: Non-static method JRequest::clean() should not be called statically in /home/content/19/13966119/html/adivanew/libraries/joomla/import.php on line 33

Strict Standards: Non-static method JRequest::_cleanArray() should not be called statically in /home/content/19/13966119/html/adivanew/libraries/joomla/environment/request.php on line 463

Strict Standards: Non-static method JRequest::_cleanArray() should not be called statically in /home/content/19/13966119/html/adivanew/libraries/joomla/environment/request.php on line 464

Strict Standards: Non-static method JRequest::_cleanArray() should not be called statically in /home/content/19/13966119/html/adivanew/libraries/joomla/environment/request.php on line 465

Strict Standards: Non-static method JRequest::_cleanArray() should not be called statically in /home/content/19/13966119/html/adivanew/libraries/joomla/environment/request.php on line 466

Strict Standards: Non-static method JRequest::_cleanArray() should not be called statically in /home/content/19/13966119/html/adivanew/libraries/joomla/environment/request.php on line 467

Strict Standards: Non-static method JRequest::_cleanArray() should not be called statically in /home/content/19/13966119/html/adivanew/libraries/joomla/environment/request.php on line 468

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/content/19/13966119/html/adivanew/libraries/joomla/import.php on line 35

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/content/19/13966119/html/adivanew/libraries/loader.php on line 71

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/content/19/13966119/html/adivanew/libraries/joomla/import.php on line 38

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/content/19/13966119/html/adivanew/libraries/loader.php on line 71

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/content/19/13966119/html/adivanew/libraries/joomla/import.php on line 39

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/content/19/13966119/html/adivanew/libraries/loader.php on line 71

Strict Standards: Non-static method JLoader::load() should not be called statically in /home/content/19/13966119/html/adivanew/libraries/loader.php on line 161

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/content/19/13966119/html/adivanew/libraries/loader.php on line 138

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/content/19/13966119/html/adivanew/libraries/joomla/import.php on line 46

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/content/19/13966119/html/adivanew/libraries/loader.php on line 71

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/content/19/13966119/html/adivanew/libraries/joomla/import.php on line 47

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/content/19/13966119/html/adivanew/libraries/loader.php on line 71

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/content/19/13966119/html/adivanew/libraries/joomla/import.php on line 50

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/content/19/13966119/html/adivanew/libraries/loader.php on line 71

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/content/19/13966119/html/adivanew/libraries/joomla/import.php on line 53

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/content/19/13966119/html/adivanew/libraries/loader.php on line 71

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/content/19/13966119/html/adivanew/libraries/joomla/import.php on line 54

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/content/19/13966119/html/adivanew/libraries/loader.php on line 71

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/content/19/13966119/html/adivanew/libraries/joomla/import.php on line 57

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/content/19/13966119/html/adivanew/libraries/joomla/import.php on line 58

Warning: session_start(): Cannot send session cookie - headers already sent by (output started at /home/content/19/13966119/html/adivanew/libraries/joomla/import.php:29) in /home/content/19/13966119/html/adivanew/libraries/joomla/session/session.php on line 423

Warning: session_start(): Cannot send session cache limiter - headers already sent (output started at /home/content/19/13966119/html/adivanew/libraries/joomla/import.php:29) in /home/content/19/13966119/html/adivanew/libraries/joomla/session/session.php on line 423

Warning: Cannot modify header information - headers already sent by (output started at /home/content/19/13966119/html/adivanew/libraries/joomla/import.php:29) in /home/content/19/13966119/html/adivanew/libraries/joomla/session/session.php on line 426
Blog Joomla! - the dynamic portal engine and content management system http://adivaconsulting.com Fri, 18 Sep 2020 08:41:09 +0000 Joomla! 1.5 - Open Source Content Management en-gb BI Publisher for JD Edwards EnterpriseOne : Associating Report Definitions with Batch Versions http://adivaconsulting.com/adiva-blog/item/105-associating-report-definitions-with-batch-versions.html http://adivaconsulting.com/adiva-blog/item/105-associating-report-definitions-with-batch-versions.html

BI Publisher for JD Edwards Enterpriseone - Online Training

Objectives

• After completing this lesson, you will be able to:

– Use Object Management Workbench to associate a report definition with a batch version.

– Use the Batch Versions application to associate a report definition with a batch version.

Report Definitions and Batch Versions

• A report definition can be submitted from the Batch Versions application if it has been associated with a version.

This is an example of the Work With Batch Versions form on the web client.

Associate Report Definitions with Batch Versions

• To associate a report definition with a batch version, the version must first be checked out.

Check Out Version

A version can be checked out from:

• Object Management Workbench.

• Batch Versions on the Microsoft Windows client.

Object Management Workbench

 

Batch Versions

 Default Report Definition Form

• After the version is checked out, use either OMW or Batch Versions to access the Default Report Definition form.

Access Default Report Definition from OMW

• The Revise Version button provides access to the Version Detail form, which has a form exit to the Default Report Definition.

Access Default Report Definition from OMW

1. In an OMW project, select a version and then click the Design button.

2. On the Batch Version Design form, click the Revise Version button. 

Follow these steps to associate a report definition with a checked-out batch version through OMW:

3. On the Version Detail form, select Report Definition from the Form menu.

4. Enter the name of a report definition in the Report Definition field and click OK.

5. Promote the batch version through the OMW project life cycle. 

Access Default Report Definition from Batch Versions

• Batch Versions has a Version Detail row exit. The Version Detail form has a form exit to the Default Report Definition

 Access Default Report Definition from Batch Versions

1. Locate the version in Batch Versions and select Version Detail from the Row menu.

2. On the Version Detail form, select Report Detail from the Form menu.

Follow these steps to associate a report definition with checked-out batch version:

3. On the Default Report Definition form, select Report Definition from the Form menu.

4. Enter the name of a report definition in the Report Definition field and click OK.

5. Promote the batch version through the OMW project life cycle.

Assessment

The following assessment tests your knowledge of associating a report definition with a batch version.

Assessment (1)

• Question: The Default Report Definition form enables users to associate a report definition with a batch version.

Assessment (2)

• Question: The Default Report Definition form can be accessed through either Batch Versions or through the Report Definitions application.

 

Review

• In this lesson, you learned how to:

– Use Object Management Workbench to associate a report definition with a batch version.

– Use the Batch Versions application to associate a report definition with a batch version.

]]>
prakash.ss@naipunya.com (Administrator) JD Edwards - BI Publisher Mon, 25 Feb 2013 15:15:46 +0000
BI Publisher for JD Edwards EnterpriseOne : Submitting Report Definitions http://adivaconsulting.com/adiva-blog/item/104-submitting-report-definitions.html http://adivaconsulting.com/adiva-blog/item/104-submitting-report-definitions.html

BI Publisher for JD Edwards Enterpriseone - Online Training

Objectives

• After completing this lesson, you will be able to:

– Submit report definitions from the Report Definitions application (P95620).

– Select batch versions when submitting report definitions.

Submit from Report Definitions(P95620)

• Report definitions can be submitted directly from the Report Definitions (P95620) application on either the Microsoft Windows client or the web client.

This example shows the EnterpriseOne Menu selection for the web version of the Report Definitions application.

BI Publisher Report Definitions

• When you select Report Definitions, the BI Publisher Report Definitions form appears:

Version Prompting Form

• If the report definition was defined with a designated version, the Version Prompting form appears.

Click the Submit button to continue.

Batch Version Search & Select

• A report definition without a designated version displays the Batch

Version Search & Select form, which enables users to select a version:

Submit Report Definition

• If the report definition is not a blind submission, the Submit Report Definition form appears.

BI Publisher Report Definitions

• After a report definition has been submitted, the BI Publisher

Report Definitions form reappears:

Submitted RD Jobs

• Select Submitted RD Jobs to monitor the report definition job, or

select Close to exit the Report Definitions application.

Assessment

The following assessment tests your knowledge of submitting report definitions from the Report Definitions application.

Assessment

• Question: If a report definition was defined without a designated batch version, users will have to select a version when submitting the report definition.

Assessment

• Question: If a report definition was defined as a blind submission, users are not given an opportunity to change output types, delivery options, and languages when they submit the report definition.

Review

• In this lesson, you learned how to:

– Submit report definitions from the Report Definitions application (P95620).

– Select batch versions when submitting report definitions.

]]>
prakash.ss@naipunya.com (Administrator) JD Edwards - BI Publisher Mon, 25 Feb 2013 15:10:41 +0000
BI Publisher for JD Edwards EnterpriseOne : Creating Report Definitions http://adivaconsulting.com/adiva-blog/item/103-creating-report-definitions.html http://adivaconsulting.com/adiva-blog/item/103-creating-report-definitions.html

BI Publisher for JD Edwards Enterpriseone - Online Training

Objectives

After completing this lesson, you will be able to:

Create report definition objects.
Define output types and languages.
Define bursting and delivery methods.
Modify report definitions.
Describe BI Publisher and Object Management Workbench integration.

Report Definitions

Report definitions define the information that BI Publisher requires to process and deliver output.

The details in a report definition include:

Create Report Definitions

Creating report definitions is a three-step process:

Enter report definition details through BI Publisher Report Definitions (P95620).

Define language and output types.

Define bursting and delivery options.

BI Publisher Report Definitions

This example shows how to access Report Definitions (P95620) from JD Edwards Solution Explorer:

Add Report Definitions

This is an example of the Add Report Definition form. Use this form to enter the name, description, source UBE, version, and templates for the report definition:

Define Languages and Output Types
This is an example of the Add Report Definition - Languages and Output Types form.
 
Define Delivery Options
This is an example of the Add Report Definition – Bursting and Delivery form. 

Define Bursting (Optional)

This example shows how to define bursting options on the Add Report Definition – Bursting and Delivery form:

Modify Report Definition Parameters

These report definition parameters can be modified:

Modify Report Definitions

To modify a report definition, first select it on the  BI Publisher Report Definitions form:

Update Report Definition Form

This example shows the Update Report Definition form:

BI Publisher and OMW Integration

If created outside Object Management Workbench, BI Publisher template objects and report definitions are automatically added to your Default Project in OMW.

Add Templates and Report Definitions in OMW

This example shows the OMW selections for adding report definitions and BI Publisher template objects:

Assessment

The following assessment tests your knowledge of report definitions.

Assessment (1)

Question: At the time a report definition is created, all the templates, translations, localizations, and transformations that will be attached to the report definition must exist in the BI Publisher Object Repository.

 

Assessment (2)

Question: If Blind Submission is selected in a report definition, the users are not given an opportunity to change the output, delivery, or language options when submitting the report definition to BI Publisher. 

Assessment (3)

Question: When creating or modifying templates and report definitions, you can use OMW to access the BI Publisher Object Repository (P95600) and BI Publisher Report Definitions (P95620).

 

Review

In this lesson, you learned how to:

Create report definition objects.
Define output types and languages.
Define bursting and delivery methods.
Modify report definitions.
Describe BI Publisher and Object Management Workbench integration.

]]>
prakash.ss@naipunya.com (Administrator) JD Edwards - BI Publisher Mon, 25 Feb 2013 07:32:55 +0000
BI Publisher for JD Edwards EnterpriseOne : Creating BI Publisher Objects http://adivaconsulting.com/adiva-blog/item/102-creating-bi-publisher-objects.html http://adivaconsulting.com/adiva-blog/item/102-creating-bi-publisher-objects.html

BI Publisher for JD Edwards Enterpriseone - Online Training

Objectives

After completing this lesson you will be able to:

Upload templates to create JD Edwards EnterpriseOne objects.
Add Translations and Localizations.
Modify template objects.

BI Publisher Objects

Templates are uploaded to the BI Publisher Object Repository to create JD Edwards EnterpriseOne objects.

The BI Publisher Object Repository (P95600) is used to upload templates and all of the translations, localizations, and transformations that are associated with them.Each template and all of its associated translations, localizations, and transformations have the same object name.

BI Publisher Object Repository Access

Use the JD Edwards Solution Explorer or the EnterpriseOne Menu to access the BI Publisher Object Repository.

BI Publisher Object Repository

This example shows the BI Publisher Object Repository form on the Microsoft Windows

 

Adding BI Publisher Objects

 This example shows the Add BI Publisher Object to Repository form:

BI Publisher Object Types

This table shows the file types that you can upload for each

 

Microsoft Windows XMLP Object Browser

This example shows the XMLP Object Browser form for uploading templates on the Microsoft Windows client:

Web Client File Upload

This example shows the File Upload form on the web client:

When using the web client to create objects, the File Upload form is used instead of the XMLP Object Browser to locate and upload templates.

Effective Dates

This example shows the Effective Dates fields for a template:

Start and End Dates

Effective dates enable a company to have multiple, slightly different versions of the same template.

For example, to customize a newsletter with different logos for each month, you can design a master template and upload it to the BI Publisher Object Repository with a start date, but no end date. Then you can created twelve copies of the original template, add a monthly logo to each one, and upload them with the same name as the original template but with different start and end dates for each copy.
Add Translations and Localizations
This example shows the Row menu selections for adding a translation or localization to an existing template:

Modifying Template Objects

There are several ways in which BI Publisher objects can be modified:

Modifying Object Properties

Complete these steps to modify the object description, product code, or product system code for an object

 

1.Find and select the object in the BI Publisher Object Repository.

2.On the Update BI Object in Repository form, change the desired information and then click OK.

3.On the Upload File form, click No in answer to the question, “Would you like to upload the file again?”

4.Click Close.

Modifying Effective Dates

To modify effective dates:

1.Select a record on the BI Publisher Object Repository form.

2.From the Row menu, select Effective Dates.

3.Add, modify, or delete the start date.

4.Add, modify, or delete the end date.

5.Click OK.

Revising Templates

To revise a template, translation, localization, or transformation:

1.Select an object on the BI Publisher Object Repository form.

2.From the Row menu, select Download.

3.On the Microsoft Windows client, the file downloads automatically.

4.On the web client, select either Open or Save on the File Download form.

5.Modify the object using the appropriate editor, and save the object to your local machine.

6.Close the editor.

7.On the BI Publisher Object Repository form, select the object that you just modified , and click Select.

8.On the Update BI Publisher Object in Repository form, modify the object information and click OK.

9.On the Upload File form, click Yes in response to the question, “Would you like to upload the file again?”.

10.Click the object name to upload the modified version.

11.Click Close

Assessment

The following assessment tests your knowledge of JD Edwards EnterpriseOne template objects.

Assessment (1)

Question: A translation is associated with a base template when it is uploaded into the BI Publisher Object Repository.

 

Assessment (2)

Question: If you specify a start date for template, you must also specify an end date.

 

Assessment (3)

Question: Modifying a template that has been uploaded to the  BI Publisher Object Repository requires that it be downloaded before changes can be made. 

Review

In this lesson, you learned how to:

Upload templates to create JD Edwards EnterpriseOne objects.
Add Translations and Localizations.
Modify template objects.

]]>
prakash.ss@naipunya.com (Administrator) JD Edwards - BI Publisher Mon, 25 Feb 2013 05:03:59 +0000
Understanding BI Publisher for JD Edwards EnterpriseOne http://adivaconsulting.com/adiva-blog/item/101-understanding-bipublisher-for-jdedwards-enterpriseone.html http://adivaconsulting.com/adiva-blog/item/101-understanding-bipublisher-for-jdedwards-enterpriseone.html

BI Publisher for JD Edwards Enterpriseone - Online Training

Objectives

After completing this lesson you will be able to:

Describe BI Publisher for JD Edwards EnterpriseOne.
Describe the benefits of BI Publisher.
Describe embedded BI Publisher reports.
Describe interactive BI Publisher reports.

Introduction to BI Publisher

JD Edwards uses Oracle’s BI Publisher to create custom documents based on data from JD Edwards EnterpriseOne.

Custom documents can have features such as:

JD Edwards EnterpriseOne Reports

This example shows typical JD Edwards reports:

BI Publisher Documents

This example shows documents generated by BI Publisher using JD Edwards EnterpriseOne data:

Separation of Report Layout and Data

The flexibility of BI Publisher is a result of the separation of the report layout from the data.

 The data is still provided by JD Edwards Enterprise One.

 However, customized report templates control how the report  outputs are presented.

BI Publisher Report Types

You can create two types of reports with BI Publisher and JD Edwards EnterpriseOne:

Embedded BI Publisher Reports

Embedded BI Publisher reports are driven by a JD Edwards EnterpriseOne batch application.

Use embedded reports when:

•A JD Edwards EnterpriseOne event initiates the requirement for the report.
•The report needs to update, insert, or delete JD Edwards EnterpriseOne data.
•The report needs to perform JD Edwards EnterpriseOne business logic.

Creating BI Publisher output for embedded reports requires a:

Template
XMLP Object
Report or batch process
Report Definition

Embedded BI Publisher Process Overview

This example illustrates the embedded BI Publisher report process:

Steps for Creating Embedded BI Publisher Reports

To create new embedded BI Publisher reports:

1.Create a blank template file.
2.Add an object to the Object Repository, using the template name.
3.Create a report definition, associating the batch application and the template.
4.Submit the report definition to generate an XML data file.
5.Download the XML data and design the template.
6.Upload the completed template into the Object Repository.
7.Update the report definition with output types and other criteria.
8.Submit the report definition to BI Publisher to produce the desired output.
Review
In this lesson you learned how to:
Describe BI Publisher for JD Edwards EnterpriseOne.
Describe the benefits of BI Publisher.
Describe embedded BI Publisher reports.
]]>
prakash.ss@naipunya.com (Administrator) JD Edwards - BI Publisher Sun, 24 Feb 2013 03:26:36 +0000
OBIEE 11g Installation http://adivaconsulting.com/blog-obiee/item/100-obiee-11g-installation.html http://adivaconsulting.com/blog-obiee/item/100-obiee-11g-installation.html

Prerequisites - JDK

http://www.oracle.com/technetwork/java/javase/downloads/jdk-6u29-download-513648.html

Prerequisites-Loopback Adaptor

http://www.windowsreference.com/windows-7/how-to-install-a-loopback-adapter-in-windows-7/

Prerequisites - Database

http://www.oracle.com/technetwork/database/enterprise-edition/downloads/index.html

Prerequisites - RCU

http://www.oracle.com/technetwork/middleware/bi-enterprise-edition/downloads/biee-111150-393613.html

OBIEE 11g Installer Download

http://www.oracle.com/technetwork/middleware/bi-enterprise-edition/downloads/biee-111150-393613.html

RCU

  • Stands for Repository Creation Utility
  • OBIEE 11g stores certain types of metadata in RCU created schemas
    • Scheduler tables : S_NQ%
    • Scorecard tables : ANNOT%
  • The schemas are a prerequisite for OBIEE 11g installation

RCU Installation

Navigate to RCU BIN Directory

RCU Welcome Screen

Create Repository Schema

Provide Database Details and SYS Password

Warning

Schema Prefix

Select the Repository Type

PLATFORM and MDS Schema Passwords

Tablespace metadata summary

Tablespace metadata summary

Tablespace check

Pre-Creation Summary

Schema creation in progress

Schema Creation Summary

Install OBIEE

Admin username and password

Select Components

Provide RCU Schema Details

Security update registration

Pre-Installation Summary

Installation in Progress

Installation Success

]]>
prakash.ss@naipunya.com (Administrator) OBIEE Sun, 13 Jan 2013 18:46:06 +0000
JD Edwards Enterprise One 9.1 & BI Publisher Integration http://adivaconsulting.com/adiva-blog/item/98-jd-edwards-enterprise-one-91-bi-publisher-integration.html http://adivaconsulting.com/adiva-blog/item/98-jd-edwards-enterprise-one-91-bi-publisher-integration.html

BI Publisher for JD Edwards Enterpriseone - Online Training

There are three ways, JDE users can use the BI Publisher

  • Embedded BI Publisher Reporting
  • BI Publisher Reporting with JD Edwards Data Access Driver
  • EnterpriseOne One View Reporting

Embedded BI Publisher Reporting

Embedded BI Publisher reporting is driven by a JD Edwards EnterpriseOne batch application (UBE)

When to use Embedded BI Publisher Reporting

  • The report needs to update, insert, or delete JD Edwards EnterpriseOne data.

    Examples of report processes that update JD Edwards EnterpriseOne data are: updating the product shipped date, advancing the sales order status, and updating the statement print date.
  • The report needs to perform JD Edwards Enterprise One business logic.

    Examples of business logic include: determining the correct pricing for a product, computing an employee's salary or benefits, and calculating commissions for sales staff.

BI Publisher Reporting with JD Edwards Data Access Driver

When to use BI Publisher Reporting with JD Edwards Data Access Driver

BI Publisher reporting with JD Edwards Data Access Driver should be used under the following circumstances:

The requested report is not part of a standard JD Edwards EnterpriseOne business process, or the requirements for the report change over time. The following are examples of these types of reports:

  • The CIO requests a list of current open Account Receivables.
  • A manager wants to review year-to-date budget amounts compared to actuals.
  • A manager requests a report showing current inventory levels.
  • Requests for other typical ad-hoc reports.

JD Edwards EnterpriseOne One View Reporting

  • Oracle's JD Edwards EnterpriseOne One View Reporting is a real time operational reporting solution.
  • One View Reporting is all about delivering the right data to the right person, right now
  • One View Reporting enables users to access and personalize transaction data into lists, charts, graphs and tables thus simplifying the consumption of information.

One View Reporting Across the Enterprise

  • Total 178 Prebuilt Reports available across all the applications.
  • User can add new custom reports based on the requirements
  • These Report can be accessed through …
    1. Standard Enterprise One Applications
    2. Data Browser
    3. Custom Enterprise Applications

One View Reporting for Customer Ledger Enquiry Application

 

 

 

 

 

 

Add Custom Report to One View...

 

 

 

Creating a Embedded BI Publisher Report…

Report Definitions

  • Report definitions specify the information that BI Publisher requires to process and deliver output.
  • The details in a report definition include:
    • The UBE and optional version to use as the source of data
    • Associated templates, transformations, and localizations
    • Output types
    • Language options
    • Bursting options
    • Delivery options

Creating customized reports using BI Publisher involves these steps:

Step 1 – Use Oracle’s BI Publisher Template Builder, Microsoft Excel, Microsoft Word, or Adobe Acrobat to create a blank template file. In Word, this would be a blank .rtf file.

Step 2 – Add an object to the JD Edwards XML Publisher Object Repository (P95600), using the template name for the object name.
After clicking OK, you will be prompted to upload the rtf file.
Then you need to set the Effective dates for the template. Pick the current date/time for start, and leave the end date blank to specify no expiration.

Step 3 Using a FAT client, create a report definition in the JD Edwards XML Publisher Report Definition application (P95620), associating the source batch application (UBE) and the template. Use Blind Submission here as an option.
Name and description
Source UBE that will extract the data
Optionally select a version if the Report Definition is limited to one specific version

Step 3 (cont)
After clicking “Next”, set the types of outputs you want to allow, and which one is the default.
Set the Language preference to use.

Step 3 (cont)
After clicking “Next”, set the bursting and delivery options. These are actually optional, NOT required.
Select whether to burst
Select which field to burst on
Requires full XPath to be typed Typically want to burst based on a level break header section
Printing: only supported for PDF output & PostScript printers
Email: based on single email address, Addr. Book number, or by data from the report (via Xpath)
Finally, click “End” to finish the RD

 


Step 6 – Use the XML data to design the template in the desktop application that you used to create the template (such as Word).
In Word, after loading your blank document, from the BI Publisher Ribbon, “Load Data” section, click “Sample XML” to load the XML the server generated in the previous step.
Proceed with template design. (*part of the next session)

BIP Embedded Output Repository

Creating Oracle BI Publisher Reports with JD Edwards Data Access Driver

To implement JD Edwards EnterpriseOne reporting using the Data Access Driver with Oracle Business Intelligence (BI) Publisher

  • Install Oracle Business Intelligence Enterprise Edition (OBIEE) 11g.
  • Install the JD Edwards EnterpriseOne Data Access Driver.
  • Register the JD Edwards EnterpriseOne Data Access Driver in Server Manager.
  • Configure the JDBC Driver (Data Access Driver) in Oracle BI Publisher

Configuring the JDBC Driver in Oracle Business Intelligence Publisher

To configure the JDBC Driver in Oracle BI Publisher:
Start the Oracle BI Publisher server.
Sign in to Oracle BI Publisher Enterprise Console.
Click the Administration tab.
Under the Data Sources section, select JDBC Connection.
The Data Sources form appears, with the JDBC tab selected.
Click Add Data Source.
Enter the following values on the Add Data Source form:

Data Sources list displays newly added data source

Naming Conventions

]]>
prakash.ss@naipunya.com (Administrator) JD Edwards - BI Publisher Tue, 08 Jan 2013 16:38:48 +0000
BI Publisher for JD Edwards Enterpriseone - Online Training http://adivaconsulting.com/blog-bi-publisher/item/96-bipjde.html http://adivaconsulting.com/blog-bi-publisher/item/96-bipjde.html

"BI Publisher for JD Edwards Enterpriseone"  online course designed for those professional who are working on JD Edwards earlier releases and wants learn BI Publisher JDE integration reporting available with recent releases (8.96, 8.98, 9.1).

This course also provides a good opportunity for those developers, who are experts in BI Publisher but want to learn BIP-JD Edwards Integration. 

Duration : 32 hours, 4 weekends (Saturday and Sunday 9 AM EST to 1 PM EST)

Contact: training@adivaconsulting.com or   +1 408-361-8194

Next Batch : March 2nd 2013.  Conatct us to Join free demo session.

Course Contents

 

Understanding BI Publisher

·         BI Publisher overview
·         Describing the Oracle BI Publisher Applications Architecture and components
·         BI Publisher for JD Edwards overview
·         Embeded BI Publisher Reports
·         One View Reports          
·         Adhoc Reporting
·         Understanding XML basics
Designing BI Publisher Templates using BI Publisher Word Template Builder      
                    Describing BI Publisher templates
                    Designing templates with BI Publisher Template Builder
                    Create Simple Listing Report
                    Working with Groups
                    Working with Tables, Forms
                    Implementing conditional logic to handle complex layout
                    Formatting Numbers, Date and Currencies.
                    Defining Headers and Footers
                    Inserting Images and Charts
                    Implementing XPATH Commands in RTF
                    Check Printing
                    Invoice Printing
                    Working with Sub-Templates
                    Advance Report Layout
Understanding JD Edwards Environment                          
                    Quick overview of JDE architecture
                    Overview of Data Dictionary
                    Working with Object Management Workbench (OMW)
                    Creating & Managing Project
                    Working with Tables & Business Views
                   Modifying template objects
Creating JD Edwards EnterpriseOne Embedded BI Publisher Objects
                    Understanding the BI Publisher Object Repository (Template, Transformation, Translation & Localization)
                    Creating, Updating, and Deleting JD Edwards BI Publisher Objects
                    Modifying template objects
 
Creating JD Edwards BI Publisher Report Definitions
                    Creating report definition objects
                    Defining output types and languages
                    Defining bursting and delivery methods
                    Modifying report definitions
                    Describing BI Publisher and Object Management Workbench integration
Working with Report Designer Aid (RDA) to generate BI Publisher friendly XML.
                    Overview of RDA
                    Overview to Report and Report Components
                    Sections (Column, Tabular, Group Sections)
                    Report Header Footer Sections
                    Page Header & Footer Sections
                    Level Breaks
                    Batch Versions
                    Working with Report Director
Submitting Report Definitions
•             Submitting report definitions from the Report Definitions application
Associating Report Definitions with Batch Versions
•             Associating a report definition with a batch version
Submitting Report Definitions from the Batch Versions Application
•             Submitting report definitions from Batch Versions
Monitoring Report Definition Processing
·         Describing the Report Definitions Job Control Search form
·         Accessing report definition jobs from View Submitted Jobs
Utilizing Report Definition Output
                    Viewing report definition source
                    Describing the Report Definition Output Repository (P95630)
                    Viewing report definition output
                    Viewing report definition output delivery details
                    Republishing report definition output
Managing Report Definition Output
                    Setting up security for report definition jobs and output
                    Deleting UBE and report definition output
                    Archiving BI Publisher report definition output
Working with Oracle BI Publisher Enterprise for Interactive Reporting
                    Configuring Oracle BI Publisher Enterprise to access JD Edwards EnterpriseOne data
                    Creating Data Model against JDE data
                    Creating Interactive BI Publisher Report
                    Scheduling BI Publisher Interactive Report
One View Reporting Overview
                    Review the existing prebuilt One View Reports
                    Add Custom Report to One View
]]>
prakash.ss@naipunya.com (Administrator) BI Publisher Sat, 05 Jan 2013 10:37:07 +0000
OBIEE 11g - Configuring LDAP Server to provide OBIEE users http://adivaconsulting.com/adiva-blog/item/95-obiee-ldap.html http://adivaconsulting.com/adiva-blog/item/95-obiee-ldap.html

OBIEE 11g - Configuring LDAP Server to provide OBIEE users

Prerequisites and best practices before starting any LDAP related changes

·         LDAP Server is installed and running

·         Users and groups and configured within the LDAP

·         Backup is taken for the following files :

o    C:\OBIEE11G\user_projects\domains\bifoundation_domain\config\config.xml

o    C:\OBIEE11G\user_projects\domains\bifoundation_domain\config\fmwconfig\*.XML   (i.e. All xml files in that directory)

o    Some developers prefer to take the backup of the whole domain folder C:\OBIEE11G\user_projects\domains\bifoundation_domain , instead of just a few XML's if massive security changes are being tested.

·         Post the LDAP related changes if the weblogic server fails to bootup (which means an Administrator is locked out of whe WLS Console), the above files can be restored back (which is a last known good configuration) and previous state is restored.  The errors look somewhat like this :

####<Sep 30, 2012 8:04:35 AM IST> <Notice> <WebLogicServer> <my-laptop> <AdminServer> <main> <<WLS Kernel>> <> <> <1354242875438> <BEA-000365> <Server state changed to FAILED>

####<Sep 30, 2012 8:04:35 AM IST> <Error> <WebLogicServer> < my-laptop> <AdminServer> <main> <<WLS Kernel>> <> <> <1354242875440> <BEA-000383> <A critical service failed. The server will shut itself down>

####<Sep 30, 2012 8:04:35 AM IST> <Notice> <WebLogicServer> < my-laptop> <AdminServer> <main> <<WLS Kernel>> <> <> <1354242875445> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>

####<Sep 30, 2012 8:04:35 AM IST> <Info> <WebLogicServer> < my-laptop> <AdminServer> <main> <<WLS Kernel>> <> <> <1354242875473> <BEA-000236> <Stopping execute threads.>

C:\OBIEE11g>

 

The above log can be found at :

C:\OBIEE11G\user_projects\domains\bifoundation_domain\servers\AdminServer\logs\ AdminServer.log

 

In the same folder bifoundation_domain.log and AdminServer-diagnostic.log files provide further trouble shooting information which is quite self explanatory and can be googled in case of errors. These are all weblogic server logs.

 

The current document describes integration with an OpenLDAP directory. However it would be same for other kinds of LDAP directories.

 

OpenLDAP for windows can be downloaded from :

http://www.userbooster.de/en/download/openldap-for-windows.aspx

 

A LDAP browser can be downloaded from :

http://jxplorer.org/downloads/index.html

This can be used for browsing through the LDAP directory entries


 

The following snap shows the users in a LDAP explorer tool

 

 

Login to Weblogic Server Admin Console and Navigate to your Security Realm

 

 

 

Go to the provider tab. This tab is used to add a new provider, e,g, a new LDAP Server that will "provide" users for OBIEE system. Click on Lock and edit and New under the providers table, to add a new Provider, which in this case is an OpenLDAP Directory

 

 

Name the LDAP provider as "OpenLDAPAuthenticator" (or whatever you wish) and select the Type of Authenticator as " OpenLDAPAuthenticator" and Click OK.

 

 

This authenticator now appears in the list of WLS authenticators as shown below. This must be reordered to be the first Authenticator.

 

Reorder by using the up keys

 

 

This is how it looks post reorder

 

And the below snap shows how this looks in the Authenticator Providers Table:

Click on the newly created Provider to configure it for handshaking with our OpenLDAP Server

 

 

 

 

 

 

An important step here, Mark control flag as OPTIONAL. This step is not to be missed else the Administrator will be locked out of Weblogic Server. Do the same for the other Authenticator.(i.e. mark control flag as OPTIONAL)                 DefaultAuthenticator(WebLogic Authentication Provider). Skipping this step will prove to be disastrous J

 

 

 Next in the "Provider Specific" Tab the LDAP specific configurations will be applied. Enter the Host,Port,Principal(admin user of LDAP),Password to connect to LDAP,User Base DN (Distinguished Name), Group Base DN etc. Note: The LDAP admin is the best person to talk to and get it filled as deemed appropriate.

 

 

 

 

 

 

 

Say OK to Save and Click on Release Cofiguration. Then Reboot the whole BI System (Stop BI Services--> Start BI Services) from Start menu

                            

 

 

Once booted up, login to EM. In the EM, Navigate to Security Provider Configuration as shown below

 

 

Go to Identity store click Configure as shown below

 

Add a property as

Property Name : virtualize
Value : true

 

 

Reboot the whole BI System from Windows Start Menu (Not just the BI server using opmnctl stopall/startall)

 

Check that LDAP users are available now in Weblogic server

 

Try to login now

 

Login should be successful

]]>
prakash.ss@naipunya.com (Administrator) Blog Thu, 20 Dec 2012 16:55:36 +0000
ADF : Configuring KeyStore credentials in JDeveloper for consuming https services http://adivaconsulting.com/adiva-blog/item/94-adf_configuring_keystore.html http://adivaconsulting.com/adiva-blog/item/94-adf_configuring_keystore.html

This blog will be useful for people trying to consume https web services from JDeveloper and had trouble configuring the key store.

In order to authenticate to https services, the server side public certificate must be acquired and added as a trusted cert entry to a keystore used by the client.  This certificate can be imported using the browser as shown in the screen shot below. This keystore stores a reference to the public certificate of the service and will be using some alias. The certificate for a web service can be obtained from the service WSDL url. Save the imported certificate to local drive.

Import Service certificate to a keystore file


• keytool -importcert -alias testkey -file servicecertificatefile.cer  -keystore  .\my-keystore.jks -storepass keystorepassword

Tip:  keytool utility can be found the path <jdk_install_dir>/bin

List the contents of a keystore

• keytool -list -keystore ".\my-keystore.jks"

Steps to specify the keystore that JDeveloper should use for handling https traffic:


• Go to Tools -> Preferences
• In the LHS tree node select credentials
• Configure the Client Trusted Certificate Keystore pointing to the my-keystore.jks location created earlier and provide the key store password
 

Hope this helps readers.

Happy Reading!!

]]>
ADF Sun, 14 Oct 2012 15:33:04 +0000