8-42 Developers Guide for Oracle Business Intelligence Publisher
The following elements are supported for server type=ipp_printer and server type=ipp_fax
■
host
■
port
■
printerName
■
uri
■
username
■
password
■
authType
■
encType
■
proxyHost
■
proxyPort
■
proxyUsername
■
proxyPassword
■
proxyAuthType
■
filter
■
filterOutputContentType The following elements are supported for server type=smtp_email
■
secureConnection
■
host
■
port
■
username
■
password
■
authType
■
filter The following elements are supported for server type=rightfax
■
host
■
port
■
uri
■
username
■
password
■
authType
■
encType
■
proxyHost
■
proxyPort
■
proxyUsername
■
proxyPassword
Using the Delivery Manager Java APIs 8-43
■
proxyAuthType
■
filter
■
filterOutputContentType The following elements are supported for server type=printer
■
host
■
filter
■
filterOutputContentType The following elements are supported for server type=webdav
■
host
■
port
■
uri
■
username
■
password
■
authType
■
encType
■
proxyHost
■
proxyPort
■
proxyUsername
■
proxyPassword
■
proxyAuthType
■
filter The following elements are supported for server type=ftp
■
host
■
port
■
username
■
password
■
filter
■
passiveMode The following elements are supported for server type=sftp
■
host
■
port
■
username
■
password
■
filter
■
authType The following elements are supported for server type=http
■
host
8-44 Developers Guide for Oracle Business Intelligence Publisher
■
port
■
uri
■
username
■
password
■
authType
■
encType
■
proxyHost
■
proxyPort
■
proxyUsername
■
proxyPassword
■
proxyAuthType The following elements are supported for server type=as2
■
host
■
port
■
uri
■
username
■
password
■
authType
■
encType
■
proxyHost
■
proxyPort
■
proxyUsername
■
proxyPassword
■
proxyAuthType The following elements are supported for server type=external
■
command
■
filter
Part III
Part III
Other Topics
This part contains the following chapters:
■
Chapter 9, Making a View Object Available to BI Publisher as a Data Source
■
Chapter 10, Setting Up After-Report Triggers
9
Making a View Object Available to BI Publisher as a Data Source 9-1
9
Making a View Object Available to BI Publisher as a Data Source
This chapter describes the required set up to use your view object as a data source in BI Publisher. This chapter contains the following sections:
■
Section 9.1, Prerequisites
■
Section 9.2, Configuring the Application Module
■
Section 9.3, Updating web.xml
■
Section 9.4, Updating weblogic.xml
■
Section 9.5, Deploying the Application Module
■
Section 9.6, Updating the providers.xml File
9.1 Prerequisites
Oracle BI Publisher provides a mechanism to extract data from a remote server using Web service calls to a view object. Applications developers can define data sources as
view objects in their application and then create a data model in BI Publisher to retrieve the data to use in their reports.
Following are the prerequisites for using the information in this chapter:
■
BI Publisher is deployed to the WebLogic Server where the application will be running. The library oracle.xdo.webapp is required. The Oracle BI Platform
Installer deploys this library.
■
In JDeveloper, you have created the entity-based view object.
■
In JDeveloper, the name of the database connection data source must be ApplicationDB.
Note: This chapter assumes familiarity with Oracle Application
Development Framework ADF and Oracle JDeveloper. For more information about these see:
■
Oracle Fusion Middleware Fusion Developers Guide for Oracle Application Development Framework
■
Oracle JDeveloper 11g Online Help
9-2 Developers Guide for Oracle Business Intelligence Publisher
9.2 Configuring the Application Module
Using Oracle JDeveloper, configure the application module that contains the view object by following the steps in the remaining sections of this chapter.
9.3 Updating web.xml
1.
In JDeveloper, navigate to the web.xml file under your Project Web Content WEB-INF folder.
Figure 9–1 Updating the web.xml File in JDeveloper
2.
In the Source view, update the web.xml file with the following: filter-mapping
filter-nameadfBindingsfilter-name servlet-nameoracle.xdo.vo.webservice.VODataSourceServiceservlet-name
dispatcherFORWARDdispatcher dispatcherREQUESTdispatcher
filter-mapping servlet
servlet-nameoracle.xdo.vo.webservice.VODataSourceServiceservlet-name servlet-classoracle.j2ee.ws.server.provider.ProviderServletservlet-class
init-param param-nameOracle.JAX-WS.ServiceEndpointBeanparam-name
param-valueoracle.xdo.vo.webservice.VODataSourceServiceparam-value init-param
load-on-startup1load-on-startup servlet
servlet-mapping
Making a View Object Available to BI Publisher as a Data Source 9-3
servlet-nameoracle.xdo.vo.webservice.VODataSourceServiceservlet-name url-patternservicesvoServiceurl-pattern
servlet-mapping
9.4 Updating weblogic.xml
1.
In JDeveloper, navigate to the weblogic.xml file under your Project Web Content WEB-INF folder.
2.
Update the weblogic.xml file located in the WEB-INF directory with the following library reference:
library-ref library-nameoracle.xdo.webapplibrary-name
library-ref
Figure 9–2 Updating the weblogic.xml File in JDeveloper
9.5 Deploying the Application Module
Deploy the application module to the WebLogic Server where BI Publisher is installed. Note the application context path.
9.6 Updating the providers.xml File
1.
In your BI Publisher installation, navigate to the providers.xml file. The providers.xml file is located in
{xdo.server.config.dir}repositoryAdminConfiguration.
2.
Update the providers.xml file by providing a name for this data source and supplying the application context path in the nonSSOUri attribute as shown:
9-4 Developers Guide for Oracle Business Intelligence Publisher
provider name=MyWSVOTest uri = nonSSOUri=http:example.com:7101Application-VOTestWS-ViewController-context-
root
3.
Save the providers.xml file.
4.
Restart the BI Publisher application. The view object data source will now be available from the data model editor.
For instructions on how to create a data model for this data source, see the topic Defining a View Object as a Data Set Type in the Oracle Fusion Middleware Report
Designers Guide for Oracle Business Intelligence Publisher.