Accessing Fusion Data From BI Reports Using Java

3/3/2020 Accessing Fusion Data from BI Reports using Java | Oracle Angelo Santagata's Blog
Angelo Santagata's Blog


Angelo Santagata's Blog
Try Oracle Cloud Platform For Free
PAAS 4 SAAS
April 30, 2016
Accessing Fusion Data from BI Reports using

Java
Angelo Santagata
ARCHITECT
Introduction
In a recent article by Richard Williams on A-Team Chronicles, Richard explained how you can execute
a BI publisher report from a SOAP Service and retrieve the report, as XML, as part of the response of
the SOAP call. This blog article serves as a follow on blog article providing a tutorial style walk
through on how to implement the above procedure in Java.
This article assumes you have already followed the steps in Richard's blog article and created your
report in BI Publisher, exposed it as a SOAP Service and tested this using SOAPUI, or another SOAP
testing tool.
Following Richards guidance we know that he correct SOAP call could look like this
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope"
xmlns:pub="http://xmlns.oracle.com/oxp/service/PublicReportService">
<soap:Header/>
<soap:Body>
<pub:runReport>
<pub:reportRequest>
<pub:reportAbsolutePath>/~angelo.santagata@oracle.com/Bi
report.xdo</pub:reportAbsolutePath>
<pub:reportRawData xsi:nil="true" >true</pub:reportRawData>
<pub:sizeOfDataChunkDownload>-1</pub:sizeOfDataChunkDownload>
<pub:flattenXML>true</pub:flattenXML>
<pub:byPassCache>true</pub:byPassCache>
</pub:reportRequest>
<pub:appParams/>
</pub:runReport>
</soap:Body>
</soap:Envelope>
https://blogs.oracle.com/angelo/accessing-fusion-data-from-bi-reports-using-java 1/8
Tip :One easy way to determine the reports location is to run the report and then examine the URL in the browser.

Implementing the SOAP call using JDeveloper 11g

We can now need to implement the Java SOAP Client to call our SOAP Service. For this blog we will
use JDeveloper 11g, the IDE recommended for extending Oracle Fusion, however you are free to use
your IDE of choice, e.g. NetBeans, Eclipse, VI, Notepad etc, the steps will obviously be different.
Creating the project

Within JDeveloper 11g start by creating a new Application and within this application create two
generic projects. Call one project “BISOAPServiceProxy” and the other
“FusionReportsIntegration”. The "BISOAPServiceProxy" project will contain a SOAP Proxy we are
going to generate from JDeveloper 11g and the "FusionReportsIntegration" project will contain our
custom client code. It is good practice to create separate projects so that the SOAP Proxies resides in
its own separate project, this allows us to regenerate the proxy from scratch without affecting any
other code.
Generating the SOAP Proxy

For this example we will be using the SOAP Proxy wizard as part of JDeveloper. This functionality
generates a static proxy for us, which in turn makes it easier to generate the required SOAP call later.
. 1. With the BISOAPService project selected, start the JDeveloper SOAP Proxy wizard.
File-> New-> Business Tier-> Web Services-> Web Service Proxy
.
.
. 2. Click Next
. 3. Skipping the first welcome screen, in step 2 enter the JAX-WS Style as the type of SOAP Proxy
you wish to generate in step 3 enter the WSDL of your Fusion Application BI Publisher
webservice WSDL. It’s best to check this URL returns a WSDL document in your web browser
before entering it here. The WSDL location will normally be something like : http://<your fusion
Applications Server>/xmlpserver/services/ExternalReportWSSService?wsdl
.
. It's recommended that you leave the copy WSDL into project check-box selected.
. 4. Give a package name, unless you need to it's recommended to leave the Root Package for
generated types to be left blank
.
. 5. Now hit Finish
Fixing the project dependencies

We now need to make sure that the “FusionReportsIntegration” is able to see classes generated by
the “BISOAPServiceProxy” proxy. To resolve this in JDeveloper we simply need to setup a
dependency between the two projects.
. 1. With the FusionReportsIntegration project selected, right-mouse click on the project and select
“Project properties”
. 2. In the properties panel select Dependencies
. 3. Select the little pencil icon and in the resulting dialog select “Build Output”. This selection tells
JDeveloper that “this project depends on the successful build output” of the other project.
. 4. Save the Dialog
. 5. Close [OK] the Project Properties dialog

. 6. Now is a good time to hit compile and make sure the SOAP proxy compiles without any errors,
given we haven't written any code yet it should compile just fine.
Writing the code to execute the SOAP call

With the SOAP Proxy generated, the project dependency setup, we’re now ready to write the code
which will call the BI Server using the generated SOAP Proxy
. 1. With the Fusion Reports Integration selected , right mouse Click -> New -> Java -> Java Class
. 2. Enter a name, and java package name, for your class

. 3. Ensure that “Main Method” is selected. This is so we can execute the code from the
command line, you will want to change this depending on where you execute your code from,
e.g. A library, a servlet etc.
. 4. Within the main method you will need to enter the following code snippet, once this code
snippet is pasted you will need to correct and resolve imports for your project.
.
. 1.
ExternalReportWSSService_Service externalReportWSSService_Service;
2.
// Initialise the SOAP Proxy generated by JDeveloper based on the following WSDL
xmlpserver/services/ExternalReportWSSService?wsdl
3.
externalReportWSSService_Service = new ExternalReportWSSService_Service();
4.
// Set security Policies to reflect your fusion applications

5.
SecurityPoliciesFeature securityFeatures = new SecurityPoliciesFeature(new String[]

6.
{ "oracle/wss_username_token_over_ssl_client_policy" });
7.
// Initialise the SOAP Endpoint

8.
ExternalReportWSSService externalReportWSSService =
externalReportWSSService_Service.getExternalReportWSSService(securityFeatures);
9.
// Create a new binding, this example hardcodes the username/password,

10.
// the recommended approach is to store the username/password in a CSF keystore

11.
WSBindingProvider wsbp = (WSBindingProvider)externalReportWSSService;

12.
Map<String, Object> requestContext = wsbp.getRequestContext();

13.
//Map to appropriate Fusion user ID, no need to provide password with SAML authentication
14.
requestContext.put(WSBindingProvider.USERNAME_PROPERTY, "username");
15.
requestContext.put(WSBindingProvider.PASSWORD_PROPERTY, "password");
16.
requestContext.put(WSBindingProvider.ENDPOINT_ADDRESS_PROPERTY,
"https://yourERPServer:443/xmlpserver/services/ExternalReportWSSService");
17.
// Create a new ReportRequest object using the generated ObjectFactory

18.
ObjectFactory of = new ObjectFactory();

19.
ReportRequest reportRequest = of.createReportRequest();

20.
// reportAbsolutePath contains the path+name of your report

21.
reportRequest.setReportAbsolutePath("/~angelo.santagata@oracle.com/Bi report.xdo");
22.
// We want raw data

23.
reportRequest.setReportRawData("");
24.
// Get all the data

25.
reportRequest.setSizeOfDataChunkDownload(-1);
26.
// Flatten the XML response

27.
reportRequest.setFlattenXML(true);
28.
// ByPass the cache to ensure we get the latest data

29.
reportRequest.setByPassCache(true);
30.
// Run the report
31.
ReportResponse reportResponse = externalReportWSSService.runReport(reportRequest, "");

32.
// Display the output, note the response is an array of bytes, you can convert this to a
String
33.
// or you can use a DocumentBuilder to put the values into a XLM Document object for further
processing
34.
System.out.println("Content Type="+reportResponse.getReportContentType());
35.
System.out.println("Data ");
36.
System.out.println("-------------------------------");
37.
String data=new String (reportResponse.getReportBytes());

38.
System.out.println(data);
39.
System.out.println("-------------------------------");
. Going through the code

. Line What does it do
This is the instantiation of a new class containing the WebService Proxy object. This was
1-3
generated for us earlier
Initialise a new instance of a security policy object, with the correct security policy, for
your Oracle Fusion server . The most common security policy is that of
5
“oracle/wss_username_token_over_ssl_client_policy", however your server maybe setup
differently
8 Calls the factory method to initialise a SOAP endpoint with the correct security features set
These lines setup the SOAP binding so that it knows which endpoint to execute (i.e. the
Hostname+URI of your webservice which is not necessarily the endpoint where the SOAP
Proxy was generated, the username and the password.In this example we are hard coding
9-16
the details because we are going to be running this example on the command line. If this
code is to be executed on a JEE server, e.g. Weblogic, then we recommend this data is
stored in the Credential store as CSF keys.
Here we create a reportRequest object and populate it with the appropriate parameters
17-
for the SOAP call. Although not mandatory its recommended that you use the
19
objectFactory generated by the SOAP proxy wizard in JDeveloper.
21 This set the ReportPath parameter, including path to the report
23 This line ensures we get the raw data without decoration, layouts etc.
By default BI Publisher publishes data on a range basis, e.g. 50 rows at a time, for this
25
usecase we want all the rows, and setting this to -1 will ensure this
27 Tells the webservice to flatten out the XML which is produced
This is an optional flag which instructs the BI Server to bypass the cache and go direct to
29
the database
This line executes the SOAP call , passing the “reportReport” object we previously
30
populated as a parameter. The return value is a reportResponse object
These lines print out the results from the BI Server. Of notable interest is the XML
34- document is returned as a byte array. In this sample we simply print out the results to the
39 output, however you would normally pass the resulting XML into Java routines to generate
a XML Document.
Because we are running this code from the command line as a java client code we need to import
the Fusion Apps Certificate into the Java Key Store. If you run the code from within JDeveloper then
the java keystore is stored in <JDeveloperHome>\wlserver_10.3\server\lib\DemoTrust.jks
Importing certificates

. 1. Download the Fusion Applications SSL certificate, using a browser like internet explorer
navigate to the SOAP WSDL URL
. 2. Mouse click on the security Icon which will bring you to the certificate details
. 3. View Certificate
4. Export Certificate as a CER File
. 5. From the command line we now need to import the certificate into our DemoTrust.jks file using
the following commandkeytool -import -alias fusionKey -file fusioncert.cer -keystore
DemoIdentity.jks
Now ready to run the code!

With the runReport.java file selected press the “Run” button, if all goes well then the code will execute
and you should see the XML result of the BI Report displayed on the console.
Join the discussion
Comments ( 7 )
Recent Content
PAAS 4 SAAS PAAS 4 SAAS GENERAL

Creating custom Fusion Application Using ICS to integrate SaaS Oracle PaaS Part
User Interfaces using Oracle JET Applications?? Forum 2017
Introduction JET is Oracle's new Are you doing SaaS, or Hey all, I'm going
mobile toolkit specifically written for EBS, integrations and using Oracle the Oracle PaaS
developers to help them build client Integration Cloud Service (ICS)? Do Forum 2017 in Sp
slide applications... you need some inspiration? Well this year in March on
is your...
Site Map Legal Notices Terms of Use Privacy Cookie Preferences Ad Choices Oracle Content Marketing Login

Accessing Fusion Data From BI Reports Using Java

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Accessing Fusion Data From BI Reports Using Java

Hochgeladen von

Copyright:

Verfügbare Formate

3/3/2020 Accessing Fusion Data from BI Reports using Java | Oracle Angelo Santagata's Blog

Angelo Santagata's Blog

Angelo Santagata's Blog

Try Oracle Cloud Platform For Free

April 30, 2016

Accessing Fusion Data from BI Reports using

Implementing the SOAP call using JDeveloper 11g

Creating the project

Generating the SOAP Proxy

Fixing the project dependencies

. 5. Close [OK] the Project Properties dialog

Writing the code to execute the SOAP call

. 2. Enter a name, and java package name, for your class

// Set security Policies to reflect your fusion applications

SecurityPoliciesFeature securityFeatures = new SecurityPoliciesFeature(new String[]

// Initialise the SOAP Endpoint

// Create a new binding, this example hardcodes the username/password,

// the recommended approach is to store the username/password in a CSF keystore

WSBindingProvider wsbp = (WSBindingProvider)externalReportWSSService;

Map<String, Object> requestContext = wsbp.getRequestContext();

// Create a new ReportRequest object using the generated ObjectFactory

ObjectFactory of = new ObjectFactory();

ReportRequest reportRequest = of.createReportRequest();

// reportAbsolutePath contains the path+name of your report

// We want raw data

// Get all the data

// Flatten the XML response

// ByPass the cache to ensure we get the latest data

ReportResponse reportResponse = externalReportWSSService.runReport(reportRequest, "");

String data=new String (reportResponse.getReportBytes());

. Going through the code

Now ready to run the code!

Join the discussion

PAAS 4 SAAS PAAS 4 SAAS GENERAL

Das könnte Ihnen auch gefallen