Siebel CRM 8.1 and OBIEE11g Integration Steps

To integrate OBIEE11g with CRM 8.1 --

Step1:

Create a common database user which should have access both in OLAP and OLTP schema

Step2:

Go to Sitemap --> Administration Marketing --> Servers

Step3:

Set the userid and password for:-

Analytics Web

Default Analytics Web Server

Default KPI Analytics Server

Step4:

Select Defauly Analytics Web Server and then define the OBIEE11g uer for the following parameters:

Authentication Service

Catalog Service

Job Execution Service

Step5:

Similarly set the OBIEE11g url for all the parameters.

If you face any authentication issue during segment/list format association or campaign run then follow the steps below:

Step1:

Go to OBIEE11g EM --> Coreapplication under Business Intelligence --> Security --> Configure and Manage Application Policies --> select application stripe obi --> Principal Type as Application Role --> click on search button --> It should display the followings:

BIAdministrator

BISystem

BIConsumer

BIAuthor

if not create then select the Principal Type as 'Group' --> click on search button --> It should display the followings:

Administrator

Marketing Analytics Administrator

BIAdministrator

BIConsumers

if not create then select each of the goups and click on Edit --> permission should be given to the following resource names:

oracle.bi.server.manageRepositories

oracle.bi.scheduler.manageJobs

oracle.bi.presentation.catalogmanager.manageCatalog

oracle.bi.server.impersonateUser

if not added then select the Principal Type as 'User' --> click on search button --> It should display the following:

Impersonator

select the 'Impersonator' user and click on Edit --> permission should be given to the following resource name:

oracle.bi.server.impersonateUser

Step 2:

Given the Siebel user has 8 character password (8 character was not mandatory on earlier versions) and necessary analytics credentials, follow the below steps to apply the new dll.

1. Stop Siebel server in services;

2. Back up the srf file in the corresponding Siebel object folder;

3. Back up the existing objects in Siebel Tools (Integration Object: readObjectResult, getSubItems

and WorkFlow: Marketing Campaign Load, Marketing Create Response, Marketing Create Lead);

4. Import sif file shipped and verify the changes documented in section Siebel Repository Changes;

5. Compile the repository changes and publish the work flow changes after revising;

6. Start the Siebel server in services;

7. Bring up the Siebel Marketing application and activate ‘Marketing Campaign Load’, ‘Marketing

Create Lead’,’ Marketing Create Response’ workflow to pick up the latest changes.

Step 3:

Replace marketing system defaults file (Analytics side)

Stop all OBIEE processes, backup marketingsystemdefaults file in OBIEE web

catalog (the location is given below) :

<INSTALL_DIRECTORY>/instances/instance1/bifoundation/OracleBIPresentationServicesComponent/

coreapplication_obips1/catalog/<CATALOG_NAME>/root/system/mktgdefaults/

marketingsystemdefaults

Copy the marketingsystemdefaults file from the package and restart OBIEE processes

Step 4:

Change the OBIEE Password to Solve the Authentication Error

11g OBIEE requires a user with 8 character password with a number included. The user should have the necessary/required credentials in Analytics side which can be provided as below,

1. Login in to http:// <Analytics server machine:Port>/em URL with the new 8 character password

user.

2. Expand the tree left hand side and click on "Farm_bifoundation_domain"

3. Open the "Weblogic Domain --> bi foundation", from the top left hand side, click on the web

logic domain menul and choose "Security -->Application Policies"

4. Select the "obi" application (Select Application Stripe to Search) and press the ">" button

5. Click "Create..."

6. Under permissions, click "Add"

7. Click the ">" button when the dialog comes up

8. Choose the line that has "oracle.bi.server.impersonateUser" and click "Ok" on the dialog. Note: if you can't use _ ALL _, choose "*" instead. This is an EM bug in certain builds.

9. Under Grantee, click "Add User"

10. Click the ">" button when the dialog comes up

11. Choose BIImpersonatorUser (8 character password user) and click the "Move>" button to

shuttle the user to the right‐handle panel. Click "Ok"

12. Click "Ok" on the main screen.

Step 5:

Make the Following Changes in Siebel

1. In Site Map, locate Administration à Integration à WI Symbolic URL List à Host Administration,

Query for NQHOST in virtual name field and give the analytics server machine name as

<Analytics server machine: Port>.

2. In Site Map, locate Administration à Integration à WI Symbolic URL List à Symbolic URL

Administration. Query for ‘Marketing Segmentation’ in Web application name and change URL

field.

http://NQHOST/Analytics/saw.dll --> http://NQHOST/analytics/saw.dll

3. In Site Map, locate Administrationà Marketing à servers

Give impersonate user name and password for Default Analytics Web Server record.

4. In Site Map, locate Administration-->Webservices --> outbound Web services

In that for the below services,

jobManagementService

SAWSessionServiceSoap

WebCatalogServiceSoap

Change the CHANGEME field to the analytics server name <Analytics server machine: Port>.

And then do clear cache without fail.

Step 6:

Close the application session and start it again, the integration is complete.

Step 7:

Update leads/response Generation Default Analytics Load Format.

1. In Program ‘Lead generation’ setup, when a new record is created‘/shared/Marketing/Example

List Formats/Galena ‐ Analytics Data Load ‐ Leads example’ is defaulted for Lead format. In 11g

the same format exists but with a different name, hence the work around would be to change

the default value of Marketing Object Manager component parameter to point to the new 11g

format in Administration – Server configuration --> Components.

Component: Marketing Object Manager

Parameter: Default Lead List Format, for example, users can pick “8.1.1 Analytics Data Load ‐

Leads example”

2. In Program ‘Response Definition’ setup, when a new record is created

‘/shared/Marketing/Example List Formats/Galena ‐ Analytics Data Load ‐Responses example’ is

defaulted for Response format. In 11g the same format exists with a different name, hence the

work around would be to change the default value of Marketing Object Manager component

parameter to point to the new 11g format in Administration – Server configuration ‐>

Components.

Component: Marketing Object Manager

Parameter: Default Response List Format, for example, users can pick“8.1.1 ‐ Analytics Data

Load ‐ Responses example”

3. Open the existing load format ‘8.1.1 ‐ Campaign Load ‐ Contacts and Prospects Example’ and

save as a new list format with purpose = Campaign load found under Options tab.

As the default campaign load format '8.1.1 ‐ Campaign Load ‐ Contacts and Prospects Example'

is created as type ‘Data load’ out of the box in 11.1.1.5 OBIEE , the format is available for Data

load formats selection in case of 'Programs ‐> Lead Setup‐>Choose Lead Format' and 'Programs

‐> Response Definitions ‐> Choose Response Format'. This format should be ignored.

4. Siebel Repository Changes

Integration Component Changes

Step 1:

Locate in Siebel Tools,

Project: SAW Web Service

IO: readObjectResult

IC: /itemInfo

Add the following fields under the integration component:

acl

owner

accessControlTokens

permissionMask

account

accountType

guid

name

Set Name as the name itself, set Data Type as DTYPE_TEXT, set Type as Data, set External Name as the

name itself, set XML Style as Element, XML Tag as the name itself, for example,

Name: acl

Data Type: DTYPE_TEXT

Type: Data

External Name: acl

XML Style: Element

XML Tag: acl

XML and External Sequence: Make sure it’s not used in that IO.

Step 2:

Locate in Siebel Tools,

Project: SAW Web Service

IO: getSubItems

IC: /getSubItems

Add the following IC field.

Name: includeACL

Note: The changes listed below are included in the repository file shipped along with the fix. After

importing the file, please check if the changes below are reflected correctly in Siebel Tools.

Data Type: DTYPE_BOOL

Type: Data

External Name: includeACL

XML Style: Element

XML Tag: includeACL

XML Literal Value: FALSE

XML and External Sequence: Make sure it’s not used in that IO

Workflow Changes

Step 1:

Locate in Siebel Tools,

Project: Marketing Workflows

Work Flow: Marketing Campaign Load

Work Flow Step: Get List Format System Data.

a. Change the input argument "‐ Contact Profile".ROW_ID to "‐ Contact Profile"."ROW_ID"

(add quotes around ROW_ID field).

b. Add a new input argument with the below specification in the same step.

Input Argument: UserName

Type: Process Property

Property Name: User Name

Note: after upgrading to Siebel 8.1.1.7 and integrating with OBI EE 11.1.1.6.7, one bug was found and to mitigate that one Oracle provided QickFix was applied and after applying quick fix following manual changes were required to make the QickFix fully successful:

The below repository changes are required along with fix.

Project: Campaign Execution

BC: Campaign List Distribution

User Property: Parallel Launch

Value: Y

Note: When the user property is turned on, code expects all the below repository changes to exists in srf.

Add the following new table.

Note: The below table schema has been delivered to 822 and is been provided for reference here, please create an extension table similar to the schema and create the new BC and map the fields accordingly as given in the BC section.

Project: Table Marketing

Table: S_CAMP_LST_GEN-->CX_S_CAMPLSTGEN

Column1 Details:

Name: CAMP_LD_WAVE_ID

User Name: Campaign Load Wave ID

Type: Data (Public)

User key Sequence: 2

Required: Y

Foreign Key Table: S_CAMP_LD_WAVE

Physical Type: Varchar

Length: 15

Column2 Details:

Name: CAMP_LST_DISTR_ID

User Name: Campaign List Distribution ID

Type: Data (Public)

User key Sequence: 1

Required: Y

Foreign Key Table: S_CAMP_LSTDISTR

Physical Type: Varchar

Length: 15

Add the following new BC – Map the extension table columns accordingly.

Project: Campaign Execution

BC: Campaign List Generation

Class: CSSBusComp

Type: Non-Transient

Table: S_CAMP_LST_GEN-->CX_S_CAMPLSTGEN

Field1 Details:

Name: Camp List Format Id

Column: CAMP_LST_DISTR_ID

Text Length: 15

Type: DTYPE_ID

Field2 Details:

Name: Camp Wave Launch Id

Column: CAMP_LD_WAVE_ID

Text Length: 15

Type: DTYPE_ID

Add the following new link

Project: Campaign Execution

Name: Campaign List Distribution/Campaign List Generation

Parent BusComp: Campaign List Distribution

Child BusComp: Campaign List Generation

Source Id: Id

Destination Id: Camp List Format Id

Cascade Delete: Delete

Business Object Changes:

Add the below new Business Component Object under Campaign BO.

Project: Campaign

Name: Campaign

Bus Comp: Campaign List Generation