Siebel Security Guide > Web Single Sign-On Authentication > Configuring Siebel CRM and Oracle BI Publisher for Web Single Sign-On >

Enabling Reports Scheduling with Web Single Sign-On

This topic describes how to enable Siebel Reports scheduling when Web Single Sign-On authentication is implemented for Siebel CRM and when the Siebel Security Model is implemented for Siebel Reports.

Oracle BI Publisher issues an inbound Web service call (BIPDataService) to retrieve data from the Siebel application when reports are scheduled and executed. During this process, report users are authenticated against the EAI Application Object Manager. You must, therefore, use a non-SSO security adapter for reports scheduling.

To enable Siebel Reports scheduling when Web SSO is implemented

1. Create a new custom Siebel Server component based on the EAI Object Manager component, and name the new component BIP EAI Object Manager.

   For information about creating custom Siebel Server component definitions, see Siebel System Administration Guide.

2. Create a new Siebel enterprise profile (named subsystem) by copying the security adapter profile used by the Application Object Manager.
   • If the Siebel application is using the LDAPSecAdpt security adapter profile, create a copy of the profile and name it LDAPSecAdpt_NoSSO.
   • If the Siebel application is using the ADSISecAdpt security adapter profile, create a copy of the profile and name it ADSISecAdpt_NoSSO.

     For information about creating Siebel Enterprise Server named subsystems, see Siebel System Administration Guide.

3. Set the Single Sign On profile parameter for the new security adapter profile you created in Step 2 to False.
4. For the BIP EAI Object Manager component you created in Step 1, specify values for the parameters shown in the following table.

   Parameter	Value (LDAP Authentication)	Value (AD Authentication)
   Security Adapter Name	LDAPSecAdpt_NoSSO	ADSISecAdpt_NoSSO
   Security Adapter Mode	LDAP	ADSI

5. Synchronize the new component definitions, then restart the Siebel Server and the Siebel Gateway Name Server services.

   For information about synchronizing components on a Siebel Enterprise Server, see Siebel System Administration Guide.

6. Create a new virtual directory in the Siebel Web server and name it bipeai_lang.

   Refer to the Siebel Web server product documentation for information on creating a virtual directory and making it accessible. Configure the new virtual directory in exactly the same way as the existing eai_lang virtual directory.

7. Edit the eapps.cfg file to add a section for the [/bipeai_lang] virtual directory, and add parameters similar to the following:

   [/bipeai_lang]
   ConnectString = ConnectString
   EnableExtServiceOnly = TRUE
   WebPublicRootDir = SWSE_Installation_Directory\PUBLIC\language
   SiebEntSecToken = security_token

   NOTE:  Do not add Web SSO-related parameters to this section.

   For additional information, see About Parameters in the eapps.cfg File.

8. Restart the Siebel Web server service for the changes to take effect.
9. Launch the Siebel Web Client and log into the Siebel application as a Siebel administrator.
10. Navigate to the Administration - Web Services screen, then the Inbound Web Services view.
11. In the Name field of the Inbound Web Services list, query for BIPDataService.
12. In the address URL for the BIPDataService, change the value eai_lang to bipeai_lang. For example:

    http://SiebelWebServerName/bipeai_lang/start.swe?SWEExtSource=WebService&SWEExtCmd=Execute&WSSOAP=1

13. Click the Generate WSDL button to generate a WSDL file, then save the file with the name dataservice.wsdl.
14. Copy the dataservice.wsdl file to the Oracle BI Publisher home directory. By default, this is the OraHome_X\oc4j_bi\bin directory on the Oracle BI Publisher server.
15. Restart the Oracle BI Publisher OC4J instance.