This action might not be possible to undo. Are you sure you want to continue?
Integrating Siebel CRM with BI Publisher reports is simple when using SQL based report generation.1. pass a ROW_ID for the current selected Siebel record into the SQL statement).1.1013/e10416/bip_misc_10134.htm#CHDGIJHH In all cases when configuring BI Publisher reports using Inbound Web Services to Siebel it is recommended that BI Publisher 10. requires wrapping of the Siebel Web Service with Java code so that it appears as a Web Service with the desired parameters as simple type parameters.Integrating with BI Publisher release 10. It is also possible to pass through parameters from the Siebel application to a SQL based report (i.3. 2 . SQL based reports are easily created in BI Publisher and can retrieve data from the Siebel base tables. This is because Siebel CRM exposes web services with complex type parameters and BI Publisher 10.com/docs/cd/E10383_01/doc/bip.e.3. Note that writing SQL based reports against Siebel CRM can be difficult if you need to restrict user access to the data.3. The out-of-the-box view and position based visibility used by Siebel CRM can be very complex to write manually.1.1.1013/e10416/bip_webservice_1013 31.it does support web services with parameters of simple type.2 does not support web services with complex type parameters .3.oracle.4 and later supports complex type Web Services as a data source and therefore you do not need to complete the java wrapping step.3. since visibility and other business logic is preserved by the underlying Integration Objects.htm# BABIJJHD For details on the BI Publisher web services available see the following document section “23 Oracle Business Intelligence Publisher Web Services”: http://download. http://download.4 or higher is used.oracle.com/docs/cd/E10415_01/doc/bi.2 and earlier. For this reporting requirement a Siebel Web Service is preferable. BI Publisher 10.3.
0c release.4. Note BI Publisher will need to be licensed to use it with Siebel CRM. 7. 3. 2. Generate the Siebel WSDL.1. 2. Go to Site Map > Administration . Set the address and modify credentials to use ClearText. The „ResponseData XPath‟ parameter is available after the 10. Create a new BI Publisher report with a Web Service connection using the edited WSDL. Modify the Siebel generated WSDL (to specify mandatory fields) so it can be used with BI Publisher. „WC_Account_BS‟ in the Name column. Configure an Inbound Web Service in Siebel. 1.Web Services > Inbound Web Services and query for example.The high level steps to retrieve data from the Siebel application using BI Publisher and Inbound Web Services are detailed below. 6. Ensure the Siebel Server is running and the EAI component group is enabled. Here are detailed configuration steps in the Siebel application using the Account entity as an example: 1. Add parameters as required. Add the „ResponseData XPath‟ parameter value if you wish to view the report output in other formats such as PDF. 3 . 4. Upload a report template. 5.3. Test the WSDL and endpoint using SOAP UI or similar to ensure a valid connection returns data.
For Operations of the Web Service set the Authentication Type „Username/Password –clear text‟ for the Execute and QueryPage method.siebel. 4 . 5.com” can be replaced by any host provided it has EAI running. Under Service Ports in the Address column add the following URL for the Secure WSDL for example: http://siebelhost. Now we can generate the WSDL by pressing „Generate WSDL‟ on the top of the Applet.3.swe?SWEExtSource=SecureWebServices &SWEExtCmd=Execute “siebelhost. 4. It is important to test the WSDL and endpoint using SoapUI or similar application to make sure the WSDL returns data.siebel.com/eai_anon_enu/start.
5 .To ensure the WSDL generated from Siebel is correct. Enter the WSDL path to the Siebel generated WSDL file. Open SOAP UI and start a new project. Replace the text in the window with the following example:- 4. Edit username/password and click the Green arrow to run the SOAP request. 1. Expand the tree and method WC_Account_BSQueryPage Double click on Request. 3. 2. use an application such as SoapUI to test the endpoint.
You can easily test a new endpoint and test the connection.5. If you are getting connection errors the SOAP endpoint at the end of the WDSL might be incorrect. Change the WSDL if the endpoint is invalid:- Once the endpoint and connection have successfully been tested with a sample SOAP request. the Siebel generated WSDL needs to be edited for use with BI Publisher. 6 .
In this example. It would be very hard for a user to scroll through all these fields.The WSDL file generated from Siebel has to be altered for use with BI Publisher. which can cause BI Publisher usability issues. from Siebel's WSDL definition. if the parameter is “Account Name” in the Siebel Web Service. which is: This field alone is not sufficient to query Account. we allow a user to modify the filter value to generate a different query for the report based on the parameter. If non-mandatory fields are generated from the WSDL. To make a field mandatory we set the minOccurs parameter from minOccurs=0 to minOccurs=1. you need to edit the WSDL generated from Siebel. All these fields are translated in BI Publisher as editable fields on the UI data source. For example. The way BI Publisher works with Siebel Web Services is to parse the WSDL and then obtain the list of fields to be used in conjunction with the filtering parameters. the WC_Account_BSQueryPage only has one mandatory field. In order to make a few fields mandatory. Fields related to the Account entity are under the „Account‟ element:- 7 . In order to make the "WC_Account_BSQueryPage_Input" element that contains "ListOfWc_Account_Io" fields as mandatory. 1. we change the WSDL as follows: 2. then there would be thousands of non-mandatory fields and attributes the in SOAP Request. if the SOAP request only allows non-mandatory fields. All fields that are required for use in the report need to be set to mandatory in the WSDL. The WSDL generated from Siebel can contain thousands of optional Integration Object fields. For example. the Account list object and two related fields are set to mandatory for use with a BI Publisher report that uses Inbound Web Services.
Next step is to make the Account element mandatory. set them to mandatory. to get fields from Account we need to make ListOfWc_Account_Io mandatory. scroll down a bit and make the change below. 4. 5. To include fields in the report output. We can see from the WSDL that „WC_Account_BSQueryPage‟ has "xsdLocal3" as namespace.3. so all the related fields should have a prefix of "xsdLocal3:". Once we have located this section of the WSDL. Make the „Name‟ field mandatory for xsd:string and also xsdLocal3:queryType: 8 .
If the endpoint needs to be edited. Once the WSDL file has been edited. we can use it with BI Publisher. then the result would include "Name".6. if we send "Name" as the query field. the "Name" field won't exist in the result. this resides at the end of the WSDL e. For example. Otherwise. By sending the request with the mandatory Integration Object fields to Siebel.g. in query request. the query result will include those defined Integration Object fields. 9 .
Pick the right “Web Service” Pick the right “Method” i. If the mandatory fields/parameters do not have a value then an error will be displayed when running the report.g. follow these steps: 1. set the “ResponseData XPath” parameter accordingly for example:/WC_Account_BSQueryPage_Output/ListOfWc_Account_Io NOTE: The "ResponseData XPath" parameter only appears after the 10. then the Web Service data source is determined from the SOAP response generated from the Siebel Web Service. ensure the Record Count. 6. The RTF template renders the XML data from the root level. e. Viewing the report in data format does not require the XPath parameter.To create a report in BI Publisher that uses Inbound Web Services.1. 10 . which starts from the SOAP response root element. Login to BI Publisher and create a new report Create datasource as “Web Service” Select “Complex Type” as “True”. 4. the RTF template has to be used to render the report data and without the root element. 8. Page Size and Start Row Num have values.3. 3. 5. e. the report won't be able to generate in this format.g. 2. 9. The reason for specifying "ResponseData XPath" is for the RTF template to render the report data. because it always should generate report data in XML format.0c release and it is necessary if you wish to render a report in certain formats. 7. However for viewing a report in PDF format.4.e QueryPage Parameters will be automatically filled in for you from the WSDL. WS-Security = 2002 Enter Username/Password credentials Type in “WSDL URL” location (select the WSDL xml file) If required. PDF. If you don't specify a value for this field.
10. Default parameters can also be added in left menu pane to appear at runtime on the report.NOTE: When navigating between pages within BI Publisher always click the Save button to make sure any edits/values are not lost. 11 . Sometimes this can happen when navigating away from the Data Model > Data Set page because the values are loaded from the WSDL each time this view is accessed.
e. Click View to see the Data output. and execute the report by clicking the View button. If no data is returned from the query or the right parameters have not been entered. LIKE „A*‟ for the Name field.11. the following output may be displayed:- 12 . for a field parameter i. you can enter dynamic query strings for the report as shown in the image below: In the image above a value for the Search Spec parameter has been specified [Name] LIKE „A*‟. It is also possible to enter default values. Save.
msutil. Copy them into your $OC4J_HOME/j2ee/home/applib if you have installed XMLP under OC4J otherwise put them in the common apps libraries directory of your J2EE container. Now login as Administrator to BI Publisher Enterprise server and go to the Admin > JDBC and enter the details required for the data connection: 14 . msbase. If you only want them loaded for the xmlp server application. 4.jar 2.1. Once installed look in the <INSTALL DIR>/lib directory there will be three jar files mssqlserver. separate JDBC drivers are also required. Now restart the server. For other databases. then copy the jar files to the directory below and restart the server.jar. For MS SQL Server connections download the SQL Server JDBC drivers from Microsoft. 3. For Oracle database these are shipped with the application server. The jdbc libraries will be loaded automatically for all applications on the instance.jar. OC4J_HOME/j2ee/home/applications/xmlpserver/xmlpserver/WEB-INF/lib 5.
1.databaseName=dbname e. 15 .g. 7.111:1133. Database Driver Class: com. The data source will now be available in the report builder to build queries against.11. Now hit the test button to check the connection works. jdbc:sqlserver://111.SQLServerDriver Connection String: Enter the url to connect to the database: jdbc:sqlserver://server:port.jdbc. Test the SQL.microsoft.Data Source Name: give the connection a name Driver Type: Enter the database classification or „Other‟.databaseName=AdventureWorks Username: Enter value Password: Enter value 6. If it fails check your connection string is valid and the class definition above. Create a new report using SQL connection.sqlserver.
Upload a report template or select generate template. Run the report by selecting „View‟.8. 16 .
there are two options: 1.this can be enabled via the server configuration file. any report in this folder is open for all to view and execute. This way you can call any report via a URL and as long as the user has rights to view/execute the report then BI Publisher will render it without the need for the user to log in.The BI Publisher server can connect to an SSO server as a partner application to the calling application and use LDAP for both applications to minimize the user maintenance.Once a report has been created in BI Publisher to extract data from the Siebel CRM application it is possible to add UI context integration in which a user can invoke the report. 2. If the report is not sensitive then this solution is possible to implement. Detailed below are some Siebel CRM configuration options that could be applied to either SQL or Web Service based reports:- This method simply invokes a URL to a report on the BI Publisher server and is executed from a button on an applet. 17 . Use Single Sign On (SSO) . rather than manually logging into the BI Publisher server to execute the report. Use the Guest folder . To avoid the user having to login to the BI Publisher server see the report.
3. Compile the applet and the button should now display. When the user clicks it. the URL will not be invoked correctly. 2. 18 .1. a new IE window should open displaying the URL link to the BI Publisher report. HTML Display Mode: DontEncodeData HTML Type: MiniButton Method Invoked: ExecuteBIP NOTE: If the syntax on the Caption is not correct. Add the new Button to the applet.xdo' target=_blank>Execute BIP</a> Replace the URL with the path to your BI Publisher server report. Edit the Applet Server Script and add the following code to enable the Button: 4. With the following properties: Name: ExecuteBIP Caption String Override: <A HREF='http://bipserver:9704/xmlpserver/%7Eadministrator/Siebel+SQL+Report/Siebel +SQL+Report. Create a new Control for the Applet. Ensure the quotes are exactly correct as above.
but passes the highlighted applet records‟ ROW_ID as a parameter in the URL.htm #4498862 1. Add the new Button to the applet.com/docs/cd/E10415_01/doc/bi.1013/e12187/T518230T518233.oracle. For more information on URL switches and parameters please review the BI Publisher documentation. “Accessing Reports via a URL” http://download. With the following properties: Name: LaunchBIP Caption String Override: Launch BIP HTML Display Mode: DontEncodeData HTML Type: MiniButton Method Invoked: LaunchBIP 2.This method invokes a URL from behind a button to a report on the BI Publisher server similar to the static URL example. 19 . Create a new Control for the Applet.
Add the following and click Save: 6. a new IE window should open displaying the URL link to the BI Publisher report with the ContactId included as a URL parameter. When the user clicks it. 7. Edit the Applet Browser Script and add the following code: 5. The following steps use a SQL report as an example.3. Edit the Applet Server Script and add the following code to enable the button: 4. select Edit > Parameters > click New. 20 . Navigate to the BI Publisher report. The BI Publisher report needs to be modified to accept this parameter as an input in the query. Compile the applet and the button should now display.
8. 9. modify the SQL query as follows: The ROW_ID from Siebel will now be included in the SQL query when the report is executed. To reference the parameter in the SQL. The report should only display the corresponding record. you should be able to enter a valid ROW_ID in the report execution. Save and Test the BI Publisher report. 21 .
xdo?_xpf=&_xpt=0&_xdo=/~administrat or/Siebel+SQL+Report+with+Parameter/Siebel+SQL+Report+with+Parameter. Create new Calculated Field in the BusComp. 1.This method invokes a URL from a hyperlink in a calculated field to a report on the BI Publisher server similar to the dynamic example. depending on the string length. but passes the highlighted applet records ROW_ID as a parameter in the URL. it may be necessary to create more than one field. For example with the Contact BusComp create the following new records: Name: BI Publisher Report 1 Calculated: True Calculated Value: "<A HREF='http://bipserver:9704/xmlpserver/~administrator/Siebel+SQL+Report+with+Pa rameter/Siebel+SQL+Report+with+Parameter.xdo&" Data Type: DTYPE_TEXT Name: BI Publisher Report 2 Calculated: True 23 .
When clicking the hyperlink a new browser should open.xdo&ContactId=6 SIA-4Y6E3&_xf=pdf&_xmode=4 24 . The report can display in a window without the headers and directly in PDF due to the other URL string parameters passed. or the URL will not be invoked correctly.xdo?_xpf=&_xpt=0&_xdo=/~administrator/Siebel +SQL+Report+with+Parameter/Siebel+SQL+Report+with+Parameter. passing the ContactId parameter (ROW_ID) to the report. you should see the new field in the list applet. Compile the changes.Calculated Value: "&_xf=pdf&_xmode=4' target=_blank>" + "Execute BIP" + "</a>" Data Type: DTYPE_TEXT Name: BI Publisher Report Calculated: True Calculated Value: [BI Publisher Report 1] + "ContactId=" + [Id] + [BI Publisher Report 2] Data Type: DTYPE_TEXT 2. Complete URL example: http://bipserver:9704/xmlpserver/~administrator/Siebel+SQL+Report+with+Parameter/ Siebel+SQL+Report+with+Parameter. 3. Create a new List Column record in the Applet definition: Name: BI Publisher Report Field: BI Publisher Report Display Name: Report HTML Type: Caption NOTE: Be sure to enter the calculated field expressions exactly as above with the right quotes.
The URL should specify '?' for the first parameter and '&' for subsequent ones. Test the URL string in IE first before invoking from Siebel CRM. 25 .
This action might not be possible to undo. Are you sure you want to continue?
We've moved you to where you read on your other device.
Get the full title to continue reading from where you left off, or restart the preview.