How To Create Separate Named Datasource For Siebel BI Publisher Reports With Large Data Volume

Please follow the step-by-step instructions given below:

1. Create a New Profile (Named Subsystem) by cloning the existing Server Datasource Profile. (You can  use the Siebel Copy Record feature to do that)

Refer: Siebel Bookshelf: Siebel System Administration Guide > Configuring Siebel Servers > Configuring the Siebel Enterprise Server >Creating Siebel Enterprise Server Named Subsystems

2. Enter the following values for the new profile:

Name	Value
Profile	Report Datasource
Alias	RptDataSrc
Subsystem Type	InfraDatasources
Description	Reports Datasource used for BIP Reporting

3. In the Profile Parameters specify all the parameters same as the Server Datasource profile. 

Name	Alias	Value
Chart Image Format	DSChartImageFormat	$(ChartImageFormat)
Chart Server	DSChartServer	$(ChartServer)
Database current SQLID	DSCurrentSQLID	$(CurrentSQLID)
Data source Connect String	DSConnectString	<ODBC Connect String>
DB Connector DLL	DSDLLName	<DB Connector DLL Name> e.g. sscdms80 for MS SQL Server
Datasource Docked Flag	DSDockedFlg	True
Datasource Table Owner	DSTableOwner	<Table Owner Name>

Click on the Advanced button and set the following parameters:

Name	Alias	Value
SQL Style	DSSQLStyle	<Sql Style> e.g. MSSqlServer for Windows SQL Server
Datasource Enterprise Server	DSEnterpriseServer	<Enterprise Server Name>
Datasource maximum fetch array size	DSMaxFetchArraySize	-1

Click on the Hidden button and set the following parameters:

Name	Alias	Value
Datasource Gateway Server	DSGatewayAddress	<siebelgatewayhostname>:2320

4. Navigate to the Administration - Server Configuration > Enterprises > Component Definitions view. Query for XMLP Report Server component.

5. Click on the pull down menu and select Start Reconfiguration.

6. In the Component Parameters list applet set following parameters:

Parameter	Value
OM - Data Source	RptDataSrc
OM - Named Data Source name	RptDataSrc,GatewayDataSrc

7. Click on the pull down menu in the Component Definitions applet and select Commit Configuration.

8. Hit the Synchronize button under the Component Definitions.

9. Restart Siebel Server and Gateway Services.

10. Log into the Siebel CRM Application as Siebel Administrator and ensure that the XMLP Report Server component is 'Online'.

11. Verify that the new parameters are in effect:    

• Navigate to Site Map > Administration - Server Configuration > Servers > Components
• In the Component Parameters list applet verify the following parameter values:
• OM - Data Source : RptDataSrc
• OM - Named Data Source name : RptDataSrc,GatewayDataSrc

   
Report Scheduling and Large Data Volume

Siebel BI Publisher Reports Scheduling feature makes use of the EAI Object Manager to fetch the report data from Siebel by invoking the inbound web service named BIPDataService. For scheduled reports to run on large data sets, the EAI Object Manager component should also be configured to use the Reports Data Source (as mentioned above).

Follow the steps given below in case you are using the Siebel BI Publisher Reports Scheduling feature:

1. Log into Siebel CRM Application as Siebel Administrator.

2. Navigate to the Administration - Server Configuration > Enterprises > Component Definitions view.

3. Query for EAI Object Manager component.

4. Click on the pull down menu and select Start Reconfiguration.

5. In the Component Parameters list applet set following parameters:

Parameter	Value
OM - Data Source	RptDataSrc
OM - Named Data Source name	RptDataSrc,GatewayDataSrc

6. Click on the pull down menu in the Component Definitions applet and select Commit Configuration.

7. Hit the Synchronize button under the Component Definitions.

8. Restart Siebel Server and Gateway Services.

Improving the performance of Siebel BI Publisher Report generation

Improving the performance of Siebel BI Publisher Report generation

1) Increasing the amount of heap memory available to the Java Virtual Machine (JVM)

Increasing the memory available to the JVM can improve the performance of the report generation and ensure that this error is not encountered.

 "C:\OraHome_1\jdk\bin\java" -XX:MaxPermSize=128m -Xms512m -Xmx512m -Duser.language=en -Duser.dir=C:\OraHome_1\oc4j_bi\bin -Duser.country=US -jar "%OC4J_JAR%" %CMDARGS%

OS	Memory Value
Windows (32-Bit)	Any value of up to 1.4GB (based on available RAM)
Windows (64-Bit)	1.4 GB or higher (based on available RAM

2) Changing the Server Request Processor DB Polling Interval

By decreasing the polling interval the Server Request Processor can check the S_SRM_REQUEST table more regularly thereby reducing the period before the request processing is started. Once the change has been made it is necessary to shutdown and restart the affected Siebel Server before the change will take effect.It is recommended that this change be made only on the Siebel Servers hosting the XMLPReportServer component as this change will result in an increased number of queries being issued against the S_SRM_REQUEST table in the database.

change param PollIntvl=1 for comp SRProc

3) Minimize the size of Integration Objects/Components 

An excessive number of unrequired fields in the report will lead to increased data generation times from the XMLPReportServer component and will result in an increased data file size for BI Publisher to process.

4) Minimal Force Active fields on  BC- 

Ensuring that a minimal number of fields are flagged as Force Active will help to ensure that the number of fields being returned when querying against the Integration Component for report generation is further reduced.

5) XMLPReportServer PreloadSRF parameter to TRUE 

Prelolading the SRF into the process ensures that any performance overhead during the SRF load is encountered during component startup and not during report processing. This parameter is listed under Advanced tab.

6) Inactive Web Services not used in Enterprise 

Due to Bug 10587893 at present the component will load all of the active webservices configured in the enterprise rather than just those which it may access, such as PublicReportService or PublicReportService_v11. This leads to a performance overhead during the first report request for any process as these can take a significant period of time to load. In order to reduce the impact of this loading process review the webservices configured as 'Active' in the Siebel Enterprise through the Administration - WebServices > Outbound Webservices and Inbound Webservices views.  Set any webservices which are not used in the enterprise to 'Inactive'..

7) Minimize logging levels on all report generation components

This will include the requesting Object Manager, the XMLPReportServer component, the EAI Object Manager, the File System Manager component, and the BI Publisher Server itself.

8) Eliminate any un-necessary scripting during report generation

9) Create Separate Named Datasource For Siebel BI Publisher Reports With Large Data Volume

Generating Large Reports (over 10,000 records) - When running report generation there may be scenarios in which more than 10,000 records need to be retrieved. The standard ServerDataSrc within the Siebel Enterprise has a row limit of 10,000 for any single query and therefore in order to support large report generation a custom data source is required without this restriction. The following post covers this requirement in detail :

How To Create Separate Named Datasource For Siebel BI Publisher Reports With Large Data Volume

How To Add Custom Toolbar In Open UI Mobile

Custom toolbar can be viewed in Open UI Mobile by modifying jqmtoolbarrenderer.js as follows:

Look for an html element with ID like this:

var w = m.replace(/\s+/g, "-").toLowerCase();
var s = $("#siebui-toolbar-" + w);

where m is the custom toolbar name.

Set the Id according to this in the swt file and then custom toolbar can be seen.

How To: BI Publisher 8 Desktop Preview Template does not work

When previewing a vanilla BI Publisher template (srvreqaa.rtf) for "Service Request Activity - All" report that comes with the Siebel installation in BI Publisher Desktop the following error is thrown :

ConfFile: C:\Program Files\Oracle\BI Publisher\BI Publisher Desktop\Template Builder for Word\config\xdoconfig.xml
Font Dir: C:\Program Files\Oracle\BI Publisher\BI Publisher Desktop\Template Builder for Word\fonts
Run XDO Start
Template: C:\Documents and Settings\Administrator\Desktop\aclist_sample.rtf
RTFProcessor setLocale: en-us
FOProcessor setData: E:\Sia811\siebsrvr\XMLP\DATA\BIP Accounts Sample.xml
FOProcessor setLocale: en-us
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at oracle.apps.xdo.common.xml.XSLT10gR1.invokeProcessXSL(Unknown Source)
at oracle.apps.xdo.common.xml.XSLT10gR1.transform(Unknown Source)
at oracle.apps.xdo.common.xml.XSLT10gR1.transform(Unknown Source)
at oracle.apps.xdo.common.xml.XSLTWrapper.transform(Unknown Source)
at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(Unknown Source)
at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(Unknown Source)
at oracle.apps.xdo.template.FOProcessor.createFO(Unknown Source)
at oracle.apps.xdo.template.FOProcessor.generate(Unknown Source)
at RTF2PDF.runRTFto(RTF2PDF.java:629)
at RTF2PDF.runXDO(RTF2PDF.java:442)
at RTF2PDF.main(RTF2PDF.java:289)
Caused by: oracle.xdo.parser.v2.XPathException: Extension function error: Class not found 'com.siebel.xmlpublisher.reports.XSLFunctions'
at oracle.xdo.parser.v2.XSLStylesheet.flushErrors(XSLStylesheet.java:1534)
at oracle.xdo.parser.v2.XSLStylesheet.execute(XSLStylesheet.java:521)
at oracle.xdo.parser.v2.XSLStylesheet.execute(XSLStylesheet.java:489)
at oracle.xdo.parser.v2.XSLProcessor.processXSL(XSLProcessor.java:271)
at oracle.xdo.parser.v2.XSLProcessor.processXSL(XSLProcessor.java:155)
at oracle.xdo.parser.v2.XSLProcessor.processXSL(XSLProcessor.java:192)

Some of the standard Siebel templates contain references to functions that are included in specific .jar files and if these are not loaded prior to opening the RTF template, then the preview will fail with the aforementioned error.

 In order to resolve the behavior the following procedure can be used :

1) Locate the following files which should be available in the %SIEBEL_CLIENT_ROOT%\CLASSES folder :

SiebelXMLP.jar
Siebel.jar
XSLFunctions.jar
SiebelCustomXMLP.jar
SiebelCustomXMLP_SIA.jar

2) Close all Microsoft Word sessions

3) Create a .bat file (startword.bat), and run it before opening the RTF template.
 

The .bat file should contain the following text :

echo %1
set _JAVA_OPTIONS=-Xbootclasspath/a:D:\811\Client\CLASSES\SiebelXMLP.jar;D:\811\Client\CLASSES\Siebel.jar;D:\811\Client\CLASSES\XSLFunctions.jar;D:\811\Client\CLASSES\SiebelCustomXMLP.jar;D:\811\Client\CLASSES\SiebelCustomXMLP_SIA.jar;
"D:\Program Files\Microsoft Office\Office12\Winword.exe" %1

How To Avoid User Preferences (SPF) File Update When EAI Task Completes

Updating the SavePreferences parameter for the EAI Object Manager, the EAI processes run without latency and disk usage since the write to SPF file at the end of EAI processing is prevented.

Potential bottleneck when writing to the SADMIN&Application.spf file

Run the following command for srvrmgr (amend component name as required) :

change param SavePreferences=false for comp eaiobjmgr_enu

(shutdown/startup component required)

How Do You Connect Siebel Tools 8.x and the Mobile Web Client (MWC) to an Encrypted Local Database?

In Siebel version 8.0 and higher, when extracting a local database with the default settings, the local database is now encrypted. This is the standard behavior and differs from the earlier versions when you needed to make changes in order to encrypt the local database.One result is that if you download the local database using Siebel Tools, you will not automatically be able to connect to it using the Siebel Mobile Web Client (MWC).
This FAQ demonstrates how in Siebel 8.0 and higher you can use the Siebel Mobile Web Client (MWC) to connect to a Local Database extracted by Siebel Tools.
Steps
1. Run Generate New Database (GenNewDB).
2. Run Database Extract (DBExtract).
3. Start Siebel Tools and Connect to Local using your USER_ID and PASSWORD.  Due to the fact the local database does not exist on the PC, you will be prompted to download the Local Database.
4. Once the local database had downloaded, please ensure you can connect correctly using Siebel Tools.
5. Copy the file ${Tools}\local\dicdata.dat to ${Client}\local\dicdata.dat
Without this step, you cannot connect to the local database from the Siebel Mobile Web Client.
6.  Locate and copy the following parameters' lines exactly as they are from [Local] section of Tools CFG   (used to Initialize database) to Siebel Mobile Web Client's CFG file:
             DSDockEncryptDB = ...
             DSHashUserPwd    = ...
             DSHashAlgorithm   = ...
7. In the Mobile Web Client CFG file [Local] section, edit the ConnectString parameter to point to where the local database is located.
8. Copy the file ${Tools}\bin\mwc_storage.cfg to ${Client}\bin\mwc_storage.cfg
9. Change the ODBC DataSource for the Client by performing the following steps:-
a. Navigate to Control Panel  > Administrative Tools > Data Source (ODBC)
b. Select the System DSN tab
c. In the list, find the DSN Source called “SSD Local DB default instance”.  Double-click on it or click once and then click the Configure button.
d. Click the Database tab
e. Copy the Server Name (such as: C__SIA_TOOLS_Local_sse_data_dbf).  Click Cancel to close this window and return to the list of System Data Sources.
f. Locate the System Data Source for the client called “SEAW Local DB default instance”. Double-click on it or click once and then click the Configure button.
g. Click the Database tab
h. Paste the data just copied into the Server Name.  Click OK to save the changes.
NOTE: It is possible to extract a local database without encryption but you need to specify the parameters below:-
Encrypt client Db password = False
Client Database encryption method = none
If you create a non-encrypted local database, you will still need to copy the file ‘mwc_storage.cfg’ file from the ${Tools}\bin directory to the ${Client}\bin directory and update the local ODBC section in the client CFG file (assumes extraction took place using Tools)
SBL-SEC-10018, SBL-DAT-00522, SBL-SEC-10001 and SBL-DAT-00565, SBL-DAT-00522, Incorrect, "missing encryption key"