Note: This document describes the steps to take manually to fix the integration issues between
Oracle BI EE 11.1.1.5 and Siebel Marketing 8.1.1.6 and 8.1.1.7 for campaign management.
Step 1. Replace Siebel Code Files and Change Repository
Given the Siebel user has 8 character password 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 2: 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/OracleBIPresentationServicesCompon
ent/coreapplication_obips1/catalog/<CATALOG_NAME>/root/system/mktgdefaults/marketings
ystemdefaults
Copy the marketingsystemdefaults file from the package and restart OBIEE
processes
Step 3. 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 4. 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 5. Close the application session and start it again, the integration is complete.
Step 6. 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.
Siebel Repository Changes
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.
Part I 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
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
Part II 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
Step 2. Locate in Siebel Tools,
Project: Marketing Workflows
Work Flow: Marketing Create Lead
a. Work Flow Step: Get List Format System Data
Change the input argument "‐ Contact Profile".ROW_ID to "‐ Contact Profile"."ROW_ID"
(add quotes around ROW_ID field).
b. Work Flow Step: Create Lead
Add a new input argument with the below specification
Input Argument: UserName
Type: Process Property
Property Name: User Name
Step 3. Locate in Siebel Tools,
Project: Marketing Workflows
Work Flow: Marketing Create Response
a. Work Flow Step: Get List Format System Data
Change the input argument "‐ Contact Profile".ROW_ID to "‐ Contact Profile"."ROW_ID"
(add quotes around ROW_ID field).
b. Work Flow Step: Create Response
Add a new input argument with the below specification
Input Argument: UserName
Type: Process Property
Property Name: User Name
