Can I use Bursting Control file in BIP Standalone/Enterprise Release?

Raj is not the first person, who asked this question, this question was raised many times and the answer is no, because Bursting Control file functionality is not integrated with Enterprise Release.

But every time, when I reply no, I don't feel very comfortable; because there is YES for some one who can go few extra miles to make it happen.

If you ever try HTTP Notification functionality, you can invoke custom code as after
Report process. We can use the same functionality to kick the Control file based bursting process. Not only this, we can kick any post process

Snap5.jpg

Here are the steps to implement Bursting control file based report within enterprise release.

1) Create normal BI Publisher Report, which generate the XML data for Bursting process.

2) Write a servlet similar to one available

here
.

When HTTP Notification invoke this servlet, it will pass the jobid, report_url, and status parameter values along with request.
Capture these parameter and use the BIP web service to get the xml data file/output file for this jobid. If your servlet is running on the same server, use the same logic as in sample servlet to get the XML data file.

Implement your control file based bursting logic within the servlet. You can hard code the bursting control file and temp directory location or use some configuration file to get these values. Please refer previous blog posts on how to implement the bursting process.


For testing, I deployed my servlet on the same server. I added following entries to my web.xml and restart the server. Please set the values according to your servlet and its location.

Snap4.jpg

3) Once your servlet is up, please register your url as HTTP delivery from Admin UI.
In my test case, I register the HTTP Server as "BurstingPostProcess" with the URL as http://localhost:8988/xmlpserver/service/scheduling/HttpNotification

Snap3.jpg

4) Submit your report. On submission UI, select the output type as data. This will generate the XML data.

Check the HTTP Notification and provide all required details.

At the end of the report completion, Scheduler will invoke the HTTP Notification with the registered URL and your servlet will do rest of the job for you.

These are very high level instructions for implementation. Please apply your own J2EE expertise to make it a success.

Please share your successful implementation with me and I will be happy to share your success story with other readers.

Also, if you want to share any of your unique BIP implementation with other BIP community, please feel free to send those details to me and I will publish it to this Blog with due credit to you.

Best of luck.

Comments:

Post a Comment:
  • HTML Syntax: NOT allowed
About

bocadmin_ww

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today