This action might not be possible to undo. Are you sure you want to continue?
x and BI Publisher - Part 1 (Updated)
With all those Siebel projects that are currently upgrading to or already live on Siebel CRM 8.1.1 many of the weary administrators have applied the patch set 184.108.40.206. And then found out to their dismay that they have to patch BI Publisher as well (to 10.1.3.4.1 that is). This is the start of a hopefully short series of posts on the steps that have to be executed in order to successfully install Siebel BI Publisher reporting 8.1.1.x in order to ease the workday for you out there a bit ;-) Let's begin with an overview. The following is the to-do list to get full reporting functionality in Siebel 220.127.116.11 and above (up until 8.2 - I am just speculating because most of the stuff should be included in the next major release's repository and seed data anyway). If you already installed BI Publisher in earlier versions, you might feel like skipping some of the steps. But if you're just about to use these long winter evenings and install the whole bunch from scratch, here's your list:
Import Fix Pack SIF files Create a new outbound web service Import inbound web services Create XMLP responsibilities Copy jar files Enable external references for BI Publisher Enable Siebel server components Configure the Siebel Java subsystem Set BI Publisher security Upload preconfigured reports Configure the BIP Scheduler
An impressive list indeed. But hey, it's a new year. So let's get started! In the remainder of this post, we'll discuss the steps that have to be carried out right after applying the patch set 18.104.22.168 to all (yes "all") your Siebel software. For your convenience, I have included links to the Siebel Reports Guide because it's all documented. But one of the reasons for this post was the order of tasks in the guide (have you ever tried this yourself guys?). Importing Fix Pack SIF files
Importing Siebel inbound web services . we navigate to the following URL and save the WSDL file: http://bip_host:port/xmlpserver/services/PublicReportService_v11?wsdl No.The 8. Furthermore.sif has to be imported.4. Again.sif files into the REPPATCH directory of our Siebel Tools installation. after ensuring that we have BI Publisher 10. you might want to rename and deactivate or at least archive them but there are lots of 'em. But wait! Here we go: In Siebel Tools we delete the existing PublicReportService business service (so says bookshelf. namely 8111FP_new_feature.3. If you're more of a timid nature then you might just want to rename it and deactivate it). that's not tricky.1. ensure that the project named XMLP Integration is compiled into the Siebel server's srf. One of these . We have to replace the outbound web service definition for the PublicReportService.1. we delete ALL integration objects that are in the XMLP Integration project.1 patch set places a bunch of . Creating a new Siebel outbound web service Now comes the tricky bit. Now we're ready to import the brand new WDSL file using the Siebel Tools WSDL import wizard. After importing...sif files. First. Don't forget to compile.1.1 (ONE!) installed.
1 or later (again.1. but not yet . It does so by using another new inbound web service.1..xml file.3.1 comes with a brand new security model named "Siebel Security".xml and the BIPDataService. When BI Publisher executes a scheduled report (one of the key features of Siebel 8.1.2 onwards).1. The BIPDataService is definitely worth a second look. my assumption is that these will be part of the seed data from 8.1.4.. So if we're on 8.1.-) Creating XMLP responsibilities As previously indicated. I know it feels interruptive but I hope you stay tuned for the next part of this series. In order to be able to assign different roles to users.BI Publisher 10. we have to import these precious little services..1).1.1. import the BIPSiebelSecurityWS.. there is a new security model which utilizes Siebel responsibilities. you should have them all.1 or later.x and BI Publisher .1. XMLP_ADMIN XMLP_DEVELOPER XMLP_SCHEDULER XMLP_SIEBEL_GUEST To allow viewing of scheduled reports.. Phew. Siebel 8. It allows us to store the XMLP roles as responsibilities in Siebel and let BI Publisher look it up. so much for today. we have to create the following new responsibilities in Siebel 8.Part 2 Welcome back to the second part of the "Installing BI Publisher for Siebel 8. it has to retrieve the data on behalf of the user.x" series (and thanks for your patience .1. there are things to be done: . Both files are located in the REPPATCH directory of Siebel Tools. In the Inbound Web Services view. As an administrator. assign the freshly imported Report Job List View to the XMLP_SCHEDULER responsibility.1..-) Let's get on with it and continue with our list.
XSLFunctions. Copying jar files If you installed BI Publisher before. Enabling external references for BI Publisher Another standard task.jar iSignBmp. Copy jar files Enable external references for BI Publisher Enable Siebel server components Configure the Siebel Java subsystem Set BI Publisher security Upload preconfigured reports and test As you can see.and final . It's a straightforward activity and goes like this: Copy the following files from the Siebel Server's CLASSES directory to the *taking a deep breath* oc4j_bi\j2ee\home\applications\xmlpserver\xmlpserver\WEB-INF\lib *taking a deep breath again* folder. This time it's all about setting the Disable External Reference parameter in the BI Publisher Runtime Configuration settings to "False". we'll discuss most of the "standard" setup tasks and keep the BI Publisher scheduler setup for the next .jar InkToolsLib.jar files provided by Oracle.post of this miniseries.jar SiebelCustomXMLP_SIA. Enabling Siebel server components .jar SiebelCustomXMLP.jar Never heard of the last two files? They implement some special functions for displaying signatures in reports. you have already completed this step. This is necessary to allow BI Publisher to use the .
SIEBSRVR_ROOT\CLASSES\Siebel. SIEBSRVR_ROOT\CLASSES\fix6312772. SIEBSRVR_ROOT\CLASSES\xmlparserv2-904. SIEBSRVR_ROOT\CLASSES\versioninfo. SIEBSRVR_ROOT\CLASSES\jdbc12. SIEBSRVR_ROOT\CLASSES\bicmn.jar. SIEBSRVR_ROOT\CLASSES\share.jar.jar.dll for named subsystem xmlpjvmsubsys change parameter classpath= SIEBSRVR_ROOT\CLASSES\SiebelXMLP. SIEBSRVR_ROOT\CLASSES\XSLFunctions. Time for a piece of script: change parameter dll=C:\BIP\jdk\jre\bin\client\jvm. .jar.jar.jar.Two server components must be enabled on at least one Siebel server in the enterprise.jar.jar.jar. SIEBSRVR_ROOT\CLASSES\jewt4. SIEBSRVR_ROOT\CLASSES\collections. SIEBSRVR_ROOT\CLASSES\bipres. SIEBSRVR_ROOT\CLASSES\i18nAPI_v3.jar. XMLP Report Server EAI Object Manager XMLP Report Server is the core component of the BI Publisher integration with Siebel and provides connectivity to the Siebel business layer (where it fetches the data using EAI Siebel Adapter) and the BI Publisher (where it sends the XML formatted data to using outbound web services).jar. EAI Object Manager must be online when we use the Siebel Security model of BI Publisher and/or want to use the scheduling functionality.jar. Configuring the Siebel Java subsystem Those among you who have already set up BI Publisher integration or other Java based mechanisms are surely familiar with the Java named subsystems (aka Enterprise Profiles). The XMLP Report Server component uses Java classes on the Siebel server and therefore we must configure both the named subsystem and the component parameter.jar.jar. SIEBSRVR_ROOT\CLASSES\xdoparser. SIEBSRVR_ROOT\CLASSES\xdocore.jar.
Click the Security Configuration Link. And yes. we reached the point where we upload the preconfigured Siebel BIP reports. it's a good test for the Siebel-BIP marriage. you should modify it to reflect the correct paths on your system. . Set BI Publisher security Now it's time to configure the BI Publisher server for the new Siebel security model. Upload preconfigured reports and test So finally. After all these changes. my tired little monsters.jar for named subsystem xmlpjvmsubsys set server Server_1 change parameter jvmsubsys=XMLPJvmSubsys for component xmlpreportserver Before running this script against the srvrmgr command line. The Siebel Web Service Endpoint is the address of the inbound web service named "BIPSecurityService" and should definitely point to the correct web server. the classpath is a lengthy one and has been broken into separate lines to accommodate your browser and eyes. This is done in the Admin tab of BI Publisher Enterprise. it's time to restart both the BI Publisher server and the Siebel Servers. What the script does is setting the parameters for the XMLPJvmSubsys and then point the XMLP Report Server component to the freshly reconfigured subsystem. create a super user (to allow administrative login in case the Siebel environment is offline) and set the Security Model to "Siebel Security" along with the other parameters (click on the screenshot for details). the web based front end of the BI Publisher.SIEBSRVR_ROOT\CLASSES\SiebelCustomXMLP. Even if we never intend to use them.
Maybe it's just me... In the un-magnificent situation of failure. not even the "obese" client. So we can go and check there: And of course. select Tables and query for any table you like.In the Siebel Web Client (yes the "Web" client. Consider yourself officially BIPed only if there is no error message. .Administration screen. Report Template Registration view. Then cross your fingers and press the Upload Files button (not easy with fingers crossed. they are all useless because they don't let you click the button. do you get it now?) we navigate to the Administration .. Then click the Reports button and select the Tables Report. no. Maybe we switch to timid mode once again and only select the Tables Report and the EIM Tables Report because they are most likely the ones that you don't want to build yourself. nor the "dedicated" client and don't even think of the "developer" web client. but in all the Siebel SIA installations there were some missing preconfigured report templates which was quite an obstacle to simply press CTRL+A and the then the button. not the "fat" client. we can run a report: I always choose the Tables Report because it puts some nice load on the system and there's always data at hand even if you have just installed a blank Siebel database. you have to verify all the steps again.BIP screen. The first file upload creates the SiebelCRMReports folder in the BI Publisher repository.. In the Application . but it does help).
One of the major enhancements that was published in the 8.Part 3 This is the third post on a mini-series on how to configure the full BI Publisher reporting feature set for Siebel CRM 8. It's an admittedly lengthy procedure and full of pitfalls.Summary We have now successfully finished the task of configuring BI Publisher reporting for Siebel CRM 8.1.1.wsdl file So let's get it on (as in the previous posts.1.1 and above. so that end users can run reports from the Siebel client. Setting up BIP scheduling involves the following steps Create the BI Publisher scheduler schema Enter List Of Values data Create a symbolic URL definition Create the dataservice. In the first two posts of this series we discussed the steps to set up basic reporting. that is setting up the BI Publisher scheduler. Siebel 8.1. I have included links to the Oracle documentation library in the headers).1 patch set is report scheduling.1. One thing is still left.1. That'll be the topic of the final post of this series.x.1.x and BI Publisher . Creating the BI Publisher scheduler schema .1.
Click Test Connection and if the connection is successful. in the BIP Admin tab.1 patch set.1. Next.1. Enter the the parameters according to your database. create a new schema owner for BIP in your database. This view hosts a portal applet and needs an accompanying symbolic URL for the end users to marvel at their scheduled reports. navigate to Scheduler Configuration. we enter the following new LOV Type and three values: XMLP_RPT_SCHEDULE_MODE Run Immediately Run Once Run Daily/Weekly Beware of typos! Creating the symbolic URL to enable the Report Job List View A new view named Report Job List View is among the sif archive for the 8. click Install Schema.This is a task of the BIP post-installation. The example above is for Oracle 10g. The URL creation process is described in the bookshelf (link on the header of this topic) and this is what it looks like. we have to add the respective LOV data. . Here is the short version: If you have not done so already. Using either Siebel Tools or the Siebel client. Entering LOV data for BIP Scheduler Because the new scheduler form applet has a picklist for the report frequency.
Create the dataservice. Once the report is scheduled. Basically. you have to download the wsdl file for the BIP Data Service (if it's not present.wsdl file One of the most interesting new building blocks for Siebel and BIP integration is the BIP Data Service. It's a new Siebel inbound web service that allows BIP to access the Siebel data for a scheduled report. Test It is recommendable to restart both BIP and Siebel and give it a try using one of the Tables Reports. we can navigate to the BIP Reports Server My Jobs view and verify that it is either in a running or completed state. import it from the BIPDataService.xml file in the REPPATCH directory of Siebel Tools) and copy the file to the oc4j_bi/bin directory of the BI Publisher installation folder. Summary . We can now click the Schedule Report option in the Report button's menu and enter the scheduling data.
A parameter declaration has to start with <?param@begin: followed by the name of the parameter (no spaces allowed).1. However. the documentation could be a bit juicier than it is now.1 or later.Part 4 the story continues. Open the report template Navigate to the Administration .x and BI Publisher . 2. It can be in clear text or inside a form field. Parameterized BI Publisher reports are documented in the Reports Guide of Siebel bookshelf (an invitation to all who use the offline version to download the updated guide . 1. Many of my readers asked for some clarification on parameterized BI Publisher reports in Siebel CRM.BIP Reports screen and select the Report Template Registration view.1.-). Separated by semicolons (.1. Click the aclist. So let's create a parameterized report. This feature is introduced by the patch release 8.1. The important thing is the parameter syntax (also described here and here).Setting up scheduling completes the BI Publisher setup for Siebel CRM with patch set 8. In this threefold series we outlined the necessary steps. Add a parameter declaration We can place parameter declarations in any place of the report template.1 and I'll report in the following how it works. Siebel 8.rtf file link to open the report template in Microsoft Word (with the BI Publisher Desktop plugin installed).1. There are a lot of steps and they are error prone.1.1.1. The below example uses the existing Account List report..) we can specify the default value the data type .1. We'll try to add a parameter which allows the user to display the location information or not.. So take your time and... It is worth mentioning that parameterized BI Publisher reports are only supported in connected mode (that is via the Siebel Web Client) in 8.
No'?> This defines a parameter named "Show_Location" with a default value of "Yes". The following is the syntax for a conditional section. For example if we wish to show the location data of an account only when the Show_Location parameter has a value of 'Yes'. Refer to the parameter in the template We can use the parameter name preceded by a dollar sign ($) to refer to the parameter all across the template. 3.No". the list of values to be displayed in the Report Parameter list applet This is the parameter declaration for our example: <?param@begin:Show_Location. a data type of "string" and a list of values of "Yes.'Yes'. <?if:$Show_Location='Yes'?> .'Yes.'string'.
The report template is automatically saved in the Siebel file system but needs to be uploaded to the BI Publisher repository. If you know how to define parameter values in the BIP Desktop preview. As we can not overwrite existing reports. The C field defines the condition. Save and upload the report template Save the report template in MS Word and close it. we have to log in to the BI Publisher Enterprise web front end and delete the report manually. Not quite intuitive but you have to click the icon to the left of the report to see the report commands. . please let me know. Use the known procedures to preview and test the report. the "EC" field simply defines the end of the conditional section using <?end if?>. click the Upload Files button in the Siebel Web Client to upload the new version of the report.Please note the ssLocation field is surrounded by the "C" and "EC" fields. 4. After deleting the report from the BI Publisher repository.
. The parameter list applet should now display the parameter along with its list of values. then the location information should be shown. And of course. This simple example should give you a clue how to use parameters in BI Publisher reports for Siebel CRM. If we select "No" for the Show_Location parameter. if we select "Yes". we should receive a report without location information. then select an output type and click Submit. Of course there are better uses for parameters such as Displaying a custom report title Sorting or grouping based on user input Showing additional charts etc and much more..5. Test Now let's navigate wet-handedly to the Account List view and select the report. .
Those among you who have worked with Actuate reports for Siebel CRM might feel a kind of relief as there is no need to create a parameter applet in the Siebel repository. .
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 listening from where you left off, or restart the preview.