Siebel UCM and CRM Integer at Ion Guide

Siebel UCM and CRM
Integration Guide
Version 8.1 QF0009
December, 2009
Copyright © 2005, 2009 Oracle and/or its affiliates. All rights reserved.
Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be
trademarks of their respective owners.
This software and related documentation are provided under a license agreement containing restrictions
on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in
your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast,
modify, license, transmit, distribute, exhibit, perform, publish or display any part, in any form, or by any
means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for
interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-
free. If you find any errors, please report them to us in writing.
If this software or related documentation is delivered to the U.S. Government or anyone licensing it on
behalf of the U.S. Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS. Programs, software, databases, and related documentation and technical
data delivered to U.S. Government customers are "commercial computer software" or "commercial
technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific
supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall
be subject to the restrictions and license terms set forth in the applicable Government contract, and, to
the extent applicable by the terms of the Government contract, the additional rights set forth in FAR
52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle
Parkway, Redwood City, CA 94065.
This software is developed for general use in a variety of information management applications. It is not
developed or intended for use in any inherently dangerous applications, including applications which may
create a risk of personal injury. If you use this software in dangerous applications, then you shall be
responsible to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe
use of this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused
by use of this software in dangerous applications.
The Programs may provide links to Web sites and access to content, products, and services from third
parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites.
You bear all risks associated with the use of such content. If you choose to purchase any products or
services from a third party, the relationship is directly between you and the third party. Oracle is not
responsible for: (a) the quality of third-party products or services; or (b) fulfilling any of the terms of
the agreement with the third party, including delivery of products or services and warranty obligations
related to purchased products or services. Oracle is not responsible for any loss or damage of any sort
that you may incur from dealing with any third party.
Contents
Siebel UCM and CRM Integration Guide 1
Chapter 1: About Siebel CRM and Siebel UCM Integration

Siebel CRM and Siebel UCM Integration 5
Scenarios for Using Siebel CRM with Siebel UCM 6
Scenario for Manually Creating a New Customer Record and Synchronizing with Siebel
UCM 7
Scenario for Using Match and Request Functionality to Create an Account Record 7
Scenario for Using Match and Request Functionality to Create a Person Record 8
Scenario for Manually Creating a New Customer Record and Synchronizing with Siebel
UCM 8
Scenario for Synchronizing Account or Customer Changes to Siebel UCM 9
Scenarios for Siebel UCM Merge Operations 9
Scenario for Manually Merging Two Accounts in Siebel UCM and Publishing a Merge
Message 9
Scenario for Sending Contact Information to Third Party Provider for Enrichment 10
Chapter 2: Siebel UCM Web Services

About UCM Web Services and Oracle CRMML 11
Reasons to Deprecate CRMML 12
Overview of Siebel UCM Web Services 12
Process for Configuring Siebel UCM Web Services 13
Enabling or Disabling Siebel UCM Services 22
Verifying Merge Publish Settings 23
Configuring Publish/Subscribe with Middleware 24
Recommended Practices for Deploying Siebel UCM Web Services 25
Siebel UCM Web Services Reference 25
OrganizationService 25
PersonService 34
GroupService 44
Financial Account Service 51
OrganizationMatchService 58
Siebel UCM and CRM Integration Guide Version 8.1 QF0009 3

Contents ■
PersonMatchService 60
OrganizationCrossReferenceService 62
PersonCrossReferenceService 66
GroupCrossReferenceService 70
FinancialAssetCrossReferenceService 73
Chapter 3: Siebel UCM Data Enrichment Web Services

Overview of Siebel UCM Data Enrichment Web Services 79
Process for Configuring Data Enrichment 79
Appendix A: Appendix
Roadmap for Manually Importing Siebel UCM Web Services 85
Process for Manually Creating Organization CRUD Web Services 86
Process for Manually Creating Person CRUD Web Services 89
Process for Manually Creating Group CRUD Web Services 92
Process for Manually Creating Financial Account CRUD Web Services 95
Process for Manually Creating Organization Cross Reference Web Services 98
Process for Manually Creating Person Cross Reference Web Services 100
Process for Manually Creating Group Cross Reference Web Services 103
Process for Manually Creating Financial Account Cross Reference Web Services 105
Process for Manually Creating Organization Match Web Services 108
Process for Manually Creating Person Match Web Services 110
4 Siebel UCM and CRM Integration Guide Version 8.1 QF0009

1 About Siebel CRM and Siebel
UCM Integration
This chapter contains information about Siebel CRM and Siebel UCM integration as well as user
scenarios. It contains the following topics:
■ “Siebel CRM and Siebel UCM Integration” on page 5
■ “Scenarios for Using Siebel CRM with Siebel UCM” on page 6
■ “Scenarios for Siebel UCM Merge Operations” on page 9
Siebel CRM and Siebel UCM Integration

Siebel Universal Customer Master (UCM) allows organizations to manage the administration of
products and customers by creating a complete collection of consolidated data including all
subordinate entities, such as phone numbers, addresses, and so on. For Siebel Business applications
to use the capabilities of Siebel UCM, there is a need to synchronize the customer, product and
related records from Siebel UCM to the Siebel Business application. You can enable your Siebel
application to integrate these different types of data within Siebel UCM and Siebel CRM through the
standards-based Oracle Application Integration Architecture (AIA) format. Additionally, the
integration process can span Siebel UCM and a third party data enrichment provider.
Business Process Description

There are two broad types of customer master business processes that you will use when using your
Siebel Business application with Siebel UCM. These modes are: Push Mode and Pull Mode. These
different business processes are described below:
■ Pull Mode. The customer record is pulled from Siebel UCM by the Siebel Business application
either for returning a set of matched candidates or for requesting a complete profile.
■ Push Mode. The customer record (either updated or newly created) is pushed from the Siebel
Business application to Siebel UCM for synchronization. The newly created or updated record is
then pushed back to the Siebel Business Application.
Match Customer & Request Customer

Match Request processes are pull-type operations which allow a Siebel application user with authority
to create and update customer information to have the golden Master version of the customer record
at any point in time. The Match-Request process enables the user to first fetch from within the Siebel
application a list of closely matching candidates from Siebel UCM. This is an example of the Match
process. Using this list of candidates, the user may then select a record that exactly matches the
desired customer, and then retrieve the entire record for further processing. This is an example of
the Request Process.

About Siebel CRM and Siebel UCM Integration ■ Scenarios for Using Siebel CRM with
Siebel UCM
These two sub-processes do not depend on the Siebel Business application having constant access
to Siebel UCM records. The Siebel database may query for the desired record, and if the query
returns no results, then the Match and Request process can be made to Siebel UCM. The local version
of customer record is independent of the Match and Request process to Siebel UCM. The Match and
Request process is done to refresh customer data, and may only be called during such a requirement.
Sync Customer
Sync Customer processes allow a Siebel application user who has the authority to create and update
customer information to have the golden master version of the customer record, and also to
synchronize any new Create or Update operations from the Siebel Business application to Siebel
UCM. This is a push-type operation either from the Siebel Business application to Siebel UCM
(synchronizing the new or updated records from the application to Siebel UCM), or from Siebel UCM
to the Siebel Business application (synchronizing the new or updated processed records from Siebel
UCM to the Siebel Business application).
Sync Customer processes allow a Siebel application user who has the authority to create and update
customer information to have the golden Master version of the customer record, and also that any
new Create or Update operations to the Siebel Business application to be synchronized to Siebel
UCM.
Merge Customer
The Merge Customer process allows Siebel Business applications to consume a merge operation that
was performed and initiated in Siebel UCM. The merge operation involves merging two customer
records (two accounts or two contacts) to create a single record in Siebel UCM. This merge operation
in Siebel UCM results in invoking a Merge Customer Oracle Application Integration Architecture
process, which indicates which two original records were merged and which is the resulting record.
This process assumes that the merge operation always originates in Siebel UCM.
Scenarios for Using Siebel CRM with

Siebel UCM
This topic provides scenarios of how to perform merge operations between Siebel Business
applications and Siebel UCM. You may use the process differently, depending on your business
requirements.
■ “Scenario for Manually Creating a New Customer Record and Synchronizing with Siebel UCM” on
page 7
■ “Scenario for Using Match and Request Functionality to Create an Account Record” on page 7
■ “Scenario for Using Match and Request Functionality to Create a Person Record” on page 8
■ “Scenario for Manually Creating a New Customer Record and Synchronizing with Siebel UCM” on
page 8
■ “Scenario for Synchronizing Account or Customer Changes to Siebel UCM” on page 9

Siebel UCM
Scenario for Manually Creating a New Customer Record

and Synchronizing with Siebel UCM
This topic gives one example of how to create a new customer record Siebel Call Center and
synchronize the record to Siebel UCM. You may use the process differently, depending on your
business requirements.
A customer service representative (CSR) using Siebel Call Center receives an incoming call from a
prospective customer representing an organization who is requesting product information. The CSR
records information about the customer including the organization name, address, and contact
information.
The CSR uses Account Type or Account Class to flag the customer as a Prospect, then creates an
Opportunity record as required to fulfill the product information request. The CSR manually invokes
a Sync process to push the newly created records to Siebel UCM.
Siebel UCM then synchronizes the record and applies any additional data quality or cleansing
processes to record. Siebel UCM then calls an automatic synchronization process to send the record
back to the Siebel Business application. The Siebel Business application receives the updated record
(if Siebel UCM has applied changes to the original record that was submitted).
Scenario for Using Match and Request Functionality to

Create an Account Record
This topic gives one example of how the Match and Request process may be used. You may use the
process differently, depending on your business requirements.
representative of an organization who is a potential customer. The CSR enters the organization name
in the Account screen and clicks the Match button, triggering the Match flow.
The Match flow passes the input data to Siebel UCM through Oracle Application Integration
Architecture. Siebel UCM invokes fuzzy matching logic functionality as part of its Data Matching
algorithm and returns a list of matching candidate Organization records based on the provided input
criteria.
The list of matching candidates is displayed to the CSR in the Accounts screen. The CSR selects a
specific Organization record from the list. After selecting the record, the CSR wishes to get a
complete profile of the Organization record to perform other tasks, such as issue resolution, order
capture and so on. To get a complete profile, the CSR clicks the Fetch button to initiate the Fetch
Customer process.
The Fetch Customer process requests the identified organization customer from Siebel UCM to
retrieve the entire customer profile. Siebel UCM queries the selected organization customer and
invokes a discrete Sync customer service to push the entire Account profile to the Siebel Business
application. The synchronization process occurs in the background requiring no CSR or UI interaction.
Upon successful synchronization, the Siebel Business application must put the retrieved Account
record in focus to eliminate the need for CSR to re-query the record.

Siebel UCM
Scenario for Using Match and Request Functionality to

Create a Person Record
This topic gives one example of how the Match and Request process may be used to create a Person
record. You may use the process differently, depending on your business requirements.
A customer service representative (CSR) using Siebel Call Center has received an incoming call from
a customer. The CSR enters the customer information, such as first name, last name, address and
so on, into the Siebel Contact screen, and then clicks the Match button, triggering the Match flow
process.
The Match flow passes the input data to Siebel UCM through Oracle Application Integration
Architecture. Siebel UCM invokes fuzzy matching logic functionality as part of its Data Matching
algorithm and returns a list of matching candidate Person records based on the input criteria. The
list of matching candidates is displayed in the Contact screen. The CSR selects a specific Contact
record from the list.
After selecting the record, the CSR wishes to get the complete profile of the Contact record to
perform other tasks, such as issue resolution, order capture, and so on. To get a complete profile,
the CSR clicks the Fetch button to initiate the Fetch Person Customer process.
The Fetch Person Customer process requests the identified person customer from Siebel UCM to
retrieve the entire customer profile. Siebel UCM queries the selected person customer record and
invokes a discrete Sync customer service to push the entire Account profile to the Siebel Business
application. The synchronization process occurs in the background requiring no user or user interface
interaction. Upon successful synchronization, the Siebel Business application must put the retrieved
Organization (Account) record in focus to eliminate the need for the CSR to re-query the record.
Scenario for Manually Creating a New Customer Record

and Synchronizing with Siebel UCM
This topic gives one example of how to create a new customer record and synchronize to Siebel UCM.
You may use the process differently, depending on your business requirements.
prospective customer representing an Organization who is requesting product information. The CSR
records information about the customer including the organization name, address, contact
information. The CSR uses Account Type or Account Class to flag the customer as a Prospect. The
CSR creates an Opportunity as required to fulfill the product information request. The CSR manually
invokes a Sync process to push created records to Siebel UCM.
Siebel UCM synchronizes the record and applies any additional data quality or cleansing processes
to record. Siebel UCM calls an automatic synchronization process to send the record back to the
Siebel Business application. The Siebel Business application receives the updated record (if Siebel
UCM has applied changes to the original record that was submitted).

About Siebel CRM and Siebel UCM Integration ■ Scenarios for Siebel UCM Merge
Operations
Scenario for Synchronizing Account or Customer

Changes to Siebel UCM
This topic gives one example of how to synchronize account or customer changes to Siebel UCM. You
may use the process differently, depending on your business requirements.
A customer service representative (CSR) using Siebel Call Center has updated an address and phone
number record of an Account based on newly obtained information. The CSR invokes a real-time Sync
process in the Siebel Business application to synchronize the changes to Siebel UCM.
Siebel UCM accepts the changes from the Siebel Business application and updates the master
Account record in Siebel UCM. Siebel UCM may make additional updates to incoming record based
on embedded Data Quality services.
Updates to the Account profile are synchronized from Siebel UCM to the Siebel Business application.
Account profiles are updated the Siebel Business application.
Scenarios for Siebel UCM Merge

Operations
This topic gives examples of how to perform merge operations between Siebel CRM and Siebel UCM.
You may use the process differently, depending on your business requirements.
■ “Scenario for Manually Merging Two Accounts in Siebel UCM and Publishing a Merge Message” on
page 9
■ “Scenario for Sending Contact Information to Third Party Provider for Enrichment” on page 10
Scenario for Manually Merging Two Accounts in Siebel

UCM and Publishing a Merge Message
This topic gives one example of how to manually merge two accounts in Siebel UCM. You may use
the process differently, depending on your business requirements.
A data steward performs periodic review of duplicate account records that have not been auto-
merged. Auto-merges may not take place to a record falling between the upper and lower match
confidence thresholds of the data matching engine.
The data steward logs into Siebel UCM and navigates to the Account Data Management tab. The data
steward sees two account records in the duplicate queue that have been flagged for review based on
automated match criteria.
The two account records have the following characteristics that make them candidates for merge:
■ Existing Account: Oracle Corp, 101 Main Street, San Francisco, CA 94104
■ Potential duplicate Account (sent by Siebel CRM): Oracle Corporation, 123 Main Street, San
Francisco, CA 94111

About Siebel CRM and Siebel UCM Integration ■ Scenarios for Siebel UCM Merge
Operations
The data steward decides that the second record is the same record as the existing record. The data
steward invokes Link and Update button to combine the two records.
Survivorship Rules that have been setup determine which record takes precidence. The same
survivorship rule dictates that the original Address field from Siebel Business application has a higher
confidence level so therefore this field remains unchanged.
The duplicate record is removed (but retained in the audit history). The updated existing record now
has the following best version profile:
Existing Account: Oracle Corporation, 101 Main Street, San Francisco, CA 94104
The merge record is published (in real-time or during a batch process) to synchronize the Surviving
record profile and the Victim record Id.
Scenario for Sending Contact Information to Third Party

Provider for Enrichment
This topic gives one example of how to send contact information to a third party provider for
enrichment. You may use the process differently, depending on your business requirements.
A data steward decides to utilize a third party data enrichment services to enrich the information of
an existing Contact with whom the company conducts business. The data steward initiates a process
to send first name, last name and address information to third party provider by way of Oracle
Application Integration Architecture.
Depending on the data enrichment services that the organization has subscribed to, the third party
provider consumes the message parameters and passes back additional attributes, such as privacy
information and, or cleansed address information.
Siebel UCM contact information is updated by the contact message returned from the third party
provider by way of Oracle Application Integration Architecture. The data steward refreshes the
screen view to reveal updated contact information. The data steward manually invoke a Sync service
to update the record in the Siebel Business application with updated information (if those
applications have been setup to handle enriched attributes.

2 Siebel UCM Web Services
This chapter includes process topics on how to use Siebel Tools and the Siebel Mobile Web client to
automatically configure Create, Read, Update and Delete (CRUD) Web services to work with Person,
Group, Financial Account, and Organization records. The chapter also includes topics on how to
manually configure each UCM Web service. Topics include:
■ “About UCM Web Services and Oracle CRMML” on page 11
■ “Overview of Siebel UCM Web Services” on page 12
■ “Process for Configuring Siebel UCM Web Services” on page 13

■ “Enabling or Disabling Siebel UCM Services” on page 22
■ “Verifying Merge Publish Settings” on page 23
■ “Configuring Publish/Subscribe with Middleware” on page 24
■ “Recommended Practices for Deploying Siebel UCM Web Services” on page 25
■ “Siebel UCM Web Services Reference” on page 25
■ “OrganizationService” on page 25
■ “PersonService” on page 34
■ “GroupService” on page 44
■ “Financial Account Service” on page 51
■ “OrganizationMatchService” on page 58
■ “PersonMatchService” on page 60
■ “OrganizationCrossReferenceService” on page 62
■ “PersonCrossReferenceService” on page 66
■ “GroupCrossReferenceService” on page 70
■ “FinancialAssetCrossReferenceService” on page 73
About UCM Web Services and Oracle

CRMML
With the release of Oracle Customer Hub (UCM) 8.2, Service Oriented Architecture and Web service
enablement of Oracle Customer Hub (UCM) features is taking the place of Oracle’s CRMML
propriatary format.

Siebel UCM Web Services ■ Overview of Siebel UCM Web Services
Oracle Customer Hub (UCM) uses industry standard Web Services Definition Language (WSDL) for
publishing Web services to external systems. In earlier version of Oracle Customer Hub (UCM)
Oracle’s CRMML, an XML based markup language, provided the means for data exchange. CRMML
was used for communication within Oracle Customer Hub (UCM). For example it was used for inbound
request/response and in Publish/Subscribe types of message delivery.
CRMML constitutes of two parts header and body.
The header contains:
■ Information identifying the sending and receiving systems
This information was used by Oracle Customer Hub (UCM) for security verifications
■ A message descriptor identifying the message
The body contains one or more message elements representing:
■ Inbound requests from an external application to insert, query, update or delete a database
object
■ Outbound response to a requested transaction
■ Outbound publication messages to be sent to an external subscribing application.
Reasons to Deprecate CRMML

Oracle UCM is deprecating CRMML for following reasons:
■ CRMML prohibits Web Service support
■ Will align closer to Core messaging infrastructure
■ CRMML is proprietary to Oracle UCM and not part of Oracle|Siebel messaging standards
In the proposed solution of replacing CRMML with Siebel SOAP messages the following will be
accomplished:
■ Alignment to the open standards of XML over SOAP which allows UCM to be closer to Core
messaging infrastructure
■ Harmonizes the Web services with Siebel Order to Cash, AIA EBO’s and Oracle Fusion services
Overview of Siebel UCM Web Services

Siebel UCM Web services are SOA complaint services shipped out of the box with Siebel UCM. Coarse
services are exposed on top of all supported objects in UCM hub to perform CRUD operations both
for composite and granular operations. Outbound Web services are also enhanced to keep
participating applications in synch with any changes taking place with UCM data.

Siebel UCM Web Services ■ Process for Configuring Siebel UCM Web Services
Process for Configuring Siebel UCM Web

Services
To configure Siebel UCM Web services automatically, perform the following tasks:
■ “Applying the Siebel Tools QuickFix” on page 13
■ “Additional Step for Non-ENU Setups” on page 13
■ “Importing the Seed Data” on page 13
■ “Importing the SIF files” on page 15
■ “Activating Workflows” on page 19
■ “Compiling the SRF and Restarting the Server” on page 20
■ “Registering the Siebel UCM Web Services” on page 21
Applying the Siebel Tools QuickFix

This step is part of “Process for Configuring Siebel UCM Web Services” on page 13.
■ Apply the Siebel QuickFix, version 8.1.1 [QF0009].
Additional Step for Non-ENU Setups

If your implemented language code is non-ENU you will need to import the non-ENU symbolic strings
that came with your QF0009 installation. Perform the following task:
To import the non-ENU symbolic strings

1 In Siebel Tools, navigate to Tools, Utilities, and then Locale Management.
2 Choose the following values:
Field Value
Select Source Language English American
Target Language <Specific Language>
3 Click the Import tab.
4 Browse to the QF0009 installation directory, and locate the desired LMU file.
5 Click Import.
Importing the Seed Data


You must now import the System Preferences and the List of Values data from the Seed Data folder
located in your QF0009 installation directory.
To import the seed data in an ENU implementation

1 From the Windows Start menu, select Control Panel, Administrative Tools, then Data Sources
(ODBC).
2 Click the System DSN tab.
3 Click Add, then choose the appropriate database driver.
4 Enter a datasource name, and enter the server name you will be connecting to.
TIP: For an Oracle database, enter the TNS service name that you created to connect your tools
to the database.
5 Navigate to the Siebel Tools installation directory and change the directory to
REPPATCH\ACR437_UCM.
6 Run the following command:
<Tools Install Directory>\bin\dataimp /u <user> /p <pass> /f <Tools Install

Directory>\REPPATCH\ACR437_UCM\SeedData\UCMMST811_Seed.dat /l <Tools Install
Directory>\temp\UCMMST811_Seed.log /c <ODBC Source Name> /d <Table Owner> /i <Tools
Install Directory>\REPPATCH\ ACR437_UCM\SeedData\UCMMST811_seedimp.inp /e n /h log
NOTE: The /h log will log in case of unique constraint violations and not error out. The /e n will
enforce the dataimp to look at only tables in inp file.
■ Replace <Tools Install Directory> with your Siebel Tools installation directory.
■ Replace <ODBC Source Name> with the ODBC you created in Step 3.
■ Replace <user> with your database user Id.
■ Repleace <pass> with your database password.

7 Review the log file <Siebel Tools Install Directory>\temp\UCMMST811\Seed.log file to make sure
that the import was completed successfully.
To import the seed data in a non-ENU implementation

1 Perform Step 1 through Step 5.
2 Import two additional .dat files (seed.dat and seed_locale_<lang code>.dat) and two .inp files
(UCMMST811_seedimp.inp and UCMMST811_seedimp_locale.inp).
3 Run the following command to import the seed.dat file:
■ <Tools Install Directory>\bin\dataimp /u <user> /p <pass> /f <Tools Install

Directory>\REPPATCH\ACR437_UCM\SeedData\UCMMST811_Seed.dat /l <Tools Install
Directory>\temp\ UCMMST811_Seed.log /c <ODBC Source Name> /d <Table Owner> /i
<Tools Install Directory>\REPPATCH\ACR437_UCM\SeedData\ UCMMST811_seedimp.inp
4 Run the following command for seed_locale_xxx.dat, where xxx is the language.

■ <Tools Install Directory>\bin\dataimp /u SADMIN /p sadmin /f <Tools Install

Directory>\REPPATCH\ACR437_UCM\SeedData\
ACR437_NON_ENU_Seed_Locale\seed_locale_XXX.dat /l <Tools Install
Directory>\temp\dataimp_seed_XXX.log /c <ODBC Source Name> /d <Table Owner> /i
<Tools Install Directory>\REPPATCH\ACR437_UCM\SeedData\
UCMMST811_seedimp_locale.inp
5 Replace the following values:
■ Replace <Tools Install Directory> with your Siebel Tools installation directory.
■ Replace <ODBC Source Name> with the ODBC you created in Step 3 on page 14.
■ Replace <user> with your database user Id.
■ Replease <pass> with your database password.
6 Review the log file <Siebel Tools Install Directory>\temp\UCMMST881_Seed.log file to make
sure that the import was completed successfully.
Importing the SIF files

SIF files contain Siebel object definitions that can be imported into Siebel Tools to replace existing
definitions. Following successful application of QF0009, you will then locate and import the .sif file
that came with the QuickFix into Siebel Tools. This .sif file contains object definitions that are
different from those contained in your present repository.
To import the .sif files

1 Navigate to the Siebel Tools installation directory <Siebel Tools Install Directory>\REPPATCH.
2 Unzip the .sif files from the Tools\ACR437_UCM.zip file.

3 The unzipped directory contains the following structure:
■ Non-ENU Symbolic Strings
■ Schemas
■ SeedData
■ Sifs
■ WebServices_XML
4 Open the Sifs folder, and verify that the following .sif files are present:
■ BusinessComponents.sif
■ BusinessServices\BusinessServices.sif
■ Business Services\OracleAIA-PROXYBusinessServices.sif
CAUTION: Import the OracleAIA-PROXYBusinessServices.sif only if you are setting up

Oracle AIA-Siebel UCM Integration.

■ BusinessServices\OracleAIA-AcxiomPROXYBusinessService.sif
CAUTION: Import OracleAIA-AcxiomPROXYBusinessService.sif only if you are setting up

Oracle AIA-Acxiom Integration.
■ IntegrationObjects.sif
■ Tables\Tables.sif
CAUTION: Be sure to import Tables\Tables.sif first, then Tables\EIMTables.sif. Not importing

in this order will result in an error.
■ Tables\EIMTables.sif
■ Applets.sif
■ Class.sif
■ PickLists.sif
■ SymbolicStrings.sif
■ Workflow.sif
5 After verifying that the .sif files are all present, log on to Siebel Tools.
6 Lock the following projects:
■ Account
■ Contact
■ DeDuplication
■ Employee
■ FINS Portfolio
■ Household
■ List Mgmt (UI)

■ Symbolic Strings
■ Table Asset
■ Table CIF
■ Table Household
■ Table Organization
■ Table Person
■ UCM CDM Child
■ UCM Data Management

■ UCM Merge
■ UCM Privacy Management
■ UCM SDH
■ UCM Survivorship

■ VEAI UCM CIF
■ VEAI UCM CIF UI
■ VERT CUT Address
■ Web Service Integration
■ Web Service
■ EIM Organization
■ EIM Person
■ EIM Asset
■ EIM CIF
■ EIM Household
7 Import all the listed .sifs to the server database choosing the Merge option.
NOTE: Before importing the SymbolicStrings.sif file, make sure the following parameter value is
set in tools.cfg file: SymStrPrefix = SBL_.
CAUTION: Import Business Services\OracleAIA-PROXYBusinessServices.sif only if you have

OracleAIA-UCM Integration. Import Business Services\OracleAIA-
AcxiomPROXYBusinessService.sif only if you have OracleAIA-Acxiom Integration.
8 In Siebel Tools navigate to Screens, System Administration, and then List Of Values.
9 In the List of Values screen, query for the values shown in Figure 1, then activate the values if
they are not already active.
NOTE: If these values are not found they must be added before proceeding.
Figure 1. List of Values list
10 In Siebel Tools Object Explorer, navigate to Tables and query for the tables that have been
modified by selecting the query with the Changed flag set.
11 Make sure that the query returns to following values:

■ S_ADDR_PER
■ S_ADDR_PER_UCMX
■ S_ASSET
■ S_CONTACT
■ S_CON_ADDR
■ S_ORG_EXT

■ S_ORG_GROUP
■ S_ORG_GRP_UCMX
■ S_PRIVACY
■ S_UCM_ADDR_PER
■ S_UCM_ASSET
■ S_UCM_CONTACT
■ S_UCM_ORGGRP
■ S_UCM_ORG_EXT
■ S_UCM_PRIVACY
■ S_USER
■ EIM_ACCOUNT1
■ EIM_ADDR_PER
■ EIM_ASSET
■ EIM_CONTACT2
■ EIM_FN_CIF_SYST
■ EIM_GROUP
■ EIM_GROUP_DTL
■ EIM_PRIVACY
■ EIM_UCM_ADRPER
■ EIM_UCM_ASSET
■ EIM_UCM_CON
■ EIM_UCM_ORG
■ EIM_UCM_ORGGRP
■ EIM_UCM_PRIVCY
■ EIM_USER
12 Select a modified table then click the Apply/DLL button.

The Choose Option window appears.
13 Choose Apply, then click OK.

A prompt appears requiring login credentials. Enter the information which follows based on your
database:
MSSQL
❏ Database user

❏ Database user password and the correct ODBC data source
ORACLE
❏ Table space
❏ Index space
❏ Database user
❏ Database user password
❏ Correct ODBC data source
DB2
❏ Table space
❏ 16K table space
❏ 32K table space
❏ Index space
❏ Database user
❏ Database user password
❏ Correct ODBC data source
14 Click Apply.
The modification process may take a moment.
15 Once the process is finished Click OK to finish the table schema changes.
16 Repeat Step 12 through Step 15 until all required tables have been modified.
TIP: You can apply the schema changes to all the tables in one pass by selecting the Current
Query in the Tables drop-down in the Apply Schema window. To perform this you have to have
executed a query with changed flag set.
Activating Workflows
To activate the workflows

1 From the Site Map, select Administration-Business Process, then Workflow Deployment.
2 Query for the following workflows:
■ UCM Financial Asset Customer Profile Integration SOAP Process
■ UCM Financial Asset Customer Profile Integration SOAP Query Process
■ UCM Group Customer Profile Integration SOAP Process
■ UCM Group Customer Profile Integration SOAP Query Process
■ UCM Organization Customer Profile Integration SOAP Process

■ UCM Organization Customer Profile Integration SOAP Query Process
■ UCM Person Customer Profile Integration SOAP Process
■ UCM Person Customer Profile Integration SOAP Query Process
■ UCM Async Realtime Publish Workflow
■ UCM Daily Publish
3 For each workflow, click Activate button in the top of the Repository Workflow Processes view.
4 Verify that the Activation Date/Time and Expiration Date fields display a valid date and time. If
not, change the Expiration Date time to a future date and time.
Compiling the SRF and Restarting the Server

To compile and restart the server

1 Stop the Siebel Server.
2 Compile the following projects:
■ Account
■ Contact
■ DeDuplication
■ Employee
■ FINS Portfolio
■ Household
■ List Mgmt (UI)

■ Symbolic Strings
■ TableAsset
■ TableCIF
■ TableHousehold
■ TableOrganization
■ TablePerson
■ UCM CDM Child
■ UCM Data Management
■ UCM Merge
■ UCM Privacy Management
■ UCM SDH
■ UCM Survivorship

■ VEAI UCM CIF
■ VEAI UCM CIF UI
■ VERT CUT Address
■ Web Service Integration
■ Web Service
■ EIM Organization
■ EIM Person
■ EIM Asset
■ EIM CIF
■ EIM Household
3 In the Object Explorer, navigate to Integration Objects.
4 Query for the Integration Objects which were imported from the .sif files.
For example: use the query Swi* to see all the relevant Integration Objects.
5 For each of the four Integration Objects for CRUD, choose Undeploy from the right-click menu,
then refresh.
6 From the right-click menu, choose Deploy to Runtime database.
7 Start your server using this newly compiled .srf file.
Registering the Siebel UCM Web Services

To register the newly created Web services

1 From the Site Map in the Siebel Mobile Web client, choose Administration-Web Services.
2 In the Deployed Integration Objects view verify that all the Integration Objects you deployed in
Siebel Tools are showing the correct time of deployment.
This will allow you to make sure the Integration Objects displayed are those you imported.
NOTE: If you have Oracle AIA-Siebel UCM Integration see Step 3, if not see Step 5.
3 From the Outbound Web Services view Query for the Oracle AIA Web services:
■ SyncOrganizationUCMJMSProducer
■ SyncPersonUCMJMSProducer
4 Change the Address of the ports corresponding to these Web services to point to the appropriate
Oracle AIA end point.
5 If non Oracle AIA integration, navigate to the Outbound Web Services view and query for the
Web service that was created in “To create the proxy business service” on page 80.

Siebel UCM Web Services ■ Enabling or Disabling Siebel UCM Services
6 Change the address of the ports corresponding to the Web services to point to the appropriate
middleware end point.
Enabling or Disabling Siebel UCM

Services
After configuring the Services they must be enable. The following two tasks allow you enable or
disable the Web services.
Configuring Publish/Subscribe System Preferences

You must set Publish/Subscribe settings to allow you to use the UCM ReadTime Publish/Subscribe
service.
To configure Publish/Subscribe system preferences

1 Navigate to Administration-Application, then System Preferences.
2 In the System Preferences screen, query for Enable Realtime PubSub.
3 If not found, create new records for each of the parameters displayed in in the following table:
Parameter Value
Enable Realtime PubSub 1 Account
Enable Realtime PubSub 2 Contact
Enable Realtime PubSub 3 Household
Enable Realtime PubSub 4 FINCORP Account
Enabling or Disabling Survivorship and Data Quality Settings

You must set survivorship and CDI match system settings to allow you to use the UCM ReadTime
Publish/Subscribe service.
To configure survivorship settings

2 In the System Preferences screen, query for Enable Survivorship Engine.
3 If not found, add the parameters displayed in the following table:
Parameter Value
Enable Survivorship Engine 1 Account
Enable Survivorship Engine 2 Contact

Siebel UCM Web Services ■ Verifying Merge Publish Settings
To configure data quality Settings

1 From the System Preferences screen, create new records the parameters displayed in the
following table:
Parameter Value
Enable CDM Cleanse 1 Account
Enable CDM Cleanse 2 Contact
Enable CDM EM 1 Account
Enable CDM EM 2 Contact
Enable CDM Match 1 Account
Enable CDM Match 2 Contact
Verifying Merge Publish Settings

There is no additional configuration needed for these settings, though you must verify the
configurations.
To verify the Merge Publish settings

1 In the Siebel Tools Object Explorer, choose Business Components.
2 In the Business Components screen, query for UCM DeDuplication Results.
3 Verify that the query has returned the following values:
■ UCM DeDuplication Results (Account)
■ UCM DeDuplication Results (Contact)

4 Select UCM DeDuplication Results (Account) and in the Object Explorer, navigate to Business
Component User Prop.
5 Verify that the following values are present:
Business Component User Property Name User Property Value
UCM DeDuplication Results MERGE_PUBLISH_IO SwiOrganizationPublishIO

(Account)
PUBLISH_METHOD_TYPE PublishMethod
VICTIM_OPERATION_TYPE Delete
SURVIVOR_OPERATION_TYPE Upsert
6 Select UCM DeDuplication Results (Contact) and in the Object Explorer, navigate to Business
Component User Prop.

Siebel UCM Web Services ■ Configuring Publish/Subscribe with Middleware
7 Verify that the following values are present:
Business Component User Property Name User Property Value
UCM DeDuplication Results MERGE_PUBLISH_IO SwiPersonPublishIO

(Contact)
PUBLISH_METHOD_TYPE PublishMethod
VICTIM_OPERATION_TYPE Delete
SURVIVOR_OPERATION_TYPE Upsert
Configuring Publish/Subscribe with

Middleware
To complete a middleware-UCM Integration, you should configure UCM publish/subscribe to call the
Middleware outbound webservices.
To verify the Merge Publish settings

1 Navigate to Administartion-Universal Customer Master, then the System Registrations view.
2 Register a new system as a Middleware System by checking the Middleware check-box, and
provide a convenient name for the newly created system.
3 For the Middleware system select the Protocol Type as PROXY.
4 Click the Publish/Subscribe tab.
5 Make entries of the object types of interest in the lower applet.
6 Select the appropriate Business Service Name and Method Name by clicking the PickList button
on the two columns: Business Service Name and Business Service Method and choose the values
listed in the following table:
Object Name Business Service Name Business Service Method
Account SyncOrganizationUCMJMSProducerService SyncOrganization
Contact SyncPersonUCMJMSProducerService SyncPerson
CAUTION: These are the Business Service names and Business Service method names that are
required if Oracle AIA is your middleware. For any other non-AIA middleware provider choose the
Web Service Names and Method Names that were created as part of “To create the proxy business
service” on page 80.

Siebel UCM Web Services ■ Recommended Practices for Deploying Siebel UCM Web
Services
Recommended Practices for Deploying

Siebel UCM Web Services
This topic provides recommended practices for deploying Siebel UCM Web Services. These practices
should be considered when planning your deployment.
■ Always use the WSDL files provided in the Quick Fix installation folder:
...\ACR437_UCM\Schemas\wsdls
■ Note that all UCM Web services specify an external system which requests the operation as an
attribute in the SOAP request. For more information, see the schema definition in the Quick Fix
installation folder: ...\ACR437_UCM\Schemas\xsd.
■ For all UCM Web services a requesting operation is specified as an attribute in the SOAP request.
For more information, see the schema definition in the Patch folder:
...\ACR437_UCM\Schemas\xsd.
■ Always perform the required UCM operation invoking the respective UCM Web Services. For
instance, executing an Update request invoking the UCM Create Web service is not advised as
unreliable output will result.
Siebel UCM Web Services Reference

Siebel UCM 8.1 includes the following Web services which work in conjunction with Siebel CRM 8.0.
■ “OrganizationService” on page 25
■ “PersonService” on page 34
■ “GroupService” on page 44
■ “Financial Account Service” on page 51
■ “OrganizationMatchService” on page 58
■ “PersonMatchService” on page 60
■ “OrganizationCrossReferenceService” on page 62
■ “PersonCrossReferenceService” on page 66
■ “GroupCrossReferenceService” on page 70
■ “FinancialAssetCrossReferenceService” on page 73
OrganizationService
Use this Web service to perform all operations related to the Organization and or the Account object
in the Siebel Business application. This Web service is used for all party operations. UCM organization
messages are used in insert, query, update and delete operations to maintain Organization
information.

Siebel UCM Web Services ■ OrganizationService
OrganizationService Operations
For a list of operations associated with this Web service, see Table 1.
Table 1. OrganizationService Operations
Name Description
createOrganization Creates an organization record
updateOrganization Updates an existing organization record.
deleteOrganization Deletes an organization record.
getOrganization Retrieves organization records based on user query

entry.
Request Message Description: createOrganization

For a description of this request message, see Table 2.
Table 2. Request Message Description: createOrganization
Node Description Type
SwiOrganizationIO Required. An instance of the Integration Integration

Object SwiOrganizationIO. Object
Account is the parent header and the

following are the child.
The following nodes apply to SwiOrganizationIO
Id Row Id of the record in the requesting String

system cross reference Id.
AccountStatus Status of the account. String

AccountValue Value of the account. String
CurrencyCode Currency code being used by the account. String
DUNSNumber Dun and Bradstreet data universal String

numbering system, number.
IntegrationId Integration Id. String
Location Account location. String
MainPhoneNumber Phone contact of the account. String
Name Account name. String
NumberofEmployees Number of employees in the organization. String

PartyTypeCode Party Type code. String
PartyUId Party unique Id. String
Status Status. string

Table 2. Request Message Description: createOrganization
AIAUCMIntegrationId Oracle Application Integration Architecture String

and Siebel UCM Integration Id.
ListOfAccount_BusinessAddress Optional. Account business address. Integration

Component
ListOfFincorpDepositAccount Optional. Financial corporation deposit Integration

account. Component
ListOfFincorpLoanAccount Optional. Financial corporation account loan Integration

details. Component
ListOfContact Optional. Contact details of account. Integration

Component
ListOfUcmAccountPrivacy Optional. Privacy details of account. Integration

Component
ListOfRelatedSalesRep Optional. Details of related sales Integration

representatives. Component
ListOfSubAccount Optional. Details of subordinate accounts Integration

associated with the parent account, if any. Component
ListOfRelatedOrganization Optional. Details of the related Integration

organization. Component
ListOfRelatedIndustry Optional. Details of related industries to the Integration

account. Component
Response Message Description: createOrganization

For a description of this response message, see Table 3.
Table 3. Response Message Description: createOrganization
SwiOrganizationIO An instance of the Integration Object Integration

SwiOrganizationIO with the list of operated Object
records.
Error Code Error code, if any. String
Error Message Error message, if any. String
Error Symbol Error symbol, if any. String

Request Message Description: updateOrganization

Table 4. Request Message Description: updateOrganization







Component
ListOfFincorpDepositAccount Optional. Financial corporation deposit Integration

account. Component
ListOfFincorpLoanAccount Optional. Financial corporation account loan Integration

details. Component

Component

Component

Table 4. Request Message Description: updateOrganization




account. Component
Response Message Description: updateOrganization

Table 5. Response Message Description: updateOrganization

records.
Request Message Description: deleteOrganization

Table 6. Request Message Description: deleteOrganization




Table 6. Request Message Description: deleteOrganization



Component
ListOfFincorpDepositAccount Optional. Fincorp deposit account. Integration

Component
ListOfFincorpLoanAccount Optional. Fincorp account loan details. Integration

Component

Component

Component




account. Component

Response Message Description: deleteOrganization

Table 7. Response Message Description: deleteOrganization
SwiOrganizationIO The same request instance of the Integration

Integration Object SwiOrganizationIO. Object
Error Symbol Error symbol, if any String
Request Message Description: getOrganization

Table 8. Request Message Description: getOrganization






Table 8. Request Message Description: getOrganization


Component
ListOfFincorpDepositAccount Optional. Fincorp deposit account. Integration

Component
ListOfFincorpLoanAccount Optional. Fincorp account loan details. Integration

Component

Component

Component




account. Component
Response Message Description: getOrganization

Table 9. Response Message Description: getOrganization

records.
OrganizationService Application Interface

This topic describes the application objects called by this Web service. For more information on
application implementation, refer to your application development documentation on Oracle
Technology Network.

Service Object (Business Service or Workflow)

For a description of the service objects for this Web service, see Table 10.
Table 10. OrganizationService Service Object
Siebel Repository Name Boundary Object Type Class
OrganizationService Workflow: UCM Organization CSSFACIFTransMgrService

Customer Profile Integration
SOAP Process.
Data Object (Integration Object)

For a description of data objects for this Web service, see Table 11.
Table 11. OrganizationService Data Object
Siebel Repository Name External Name
SwiOrganizationIO Account
Methods
For a description of the methods for this Web service, see Table 12.
Table 12. OrganizationService Methods
Operation Method
createOrganization RunProcess
updateOrganization RunProcess
deleteOrganization RunProcess
getOrganization RunProcess
Example Package for OrganizationService

To view an example of messages for this Web service, navigate to the WebServices_XML folder in the
QuickFix [QF0009] installation directory.
Request
See the following file to view the sample code:
...WebServices_XML\CRUDServices\OrganizationService\Request.xml
Response
......WebServices_XML\CRUDServices\OrganizationService\Response.xml

Siebel UCM Web Services ■ PersonService
WSDL and Message Schema for OrganizationService

To view an example of messages for this Web service, navigate to the WebServices_WSDL folder in
the QuickFix [QF0009] installation directory.
WSDL:
...WSDL\OrganizationService.wsdl
Schema:
..WSDL\ListofSwiOrganizationServiceIO.xsd
..WSDL\ListofSwiOrganizationServicePublishIO.xsd
PersonService
Use this Web service to create, update, retrieve and delete Person records.
PersonService Operations
Table 13. FetchAccountSiebelReqABCSImpl Operations
Name Description
createPerson Creates a person record.
updatePerson Updates an existing person record.
deletePerson Deletes a person record.
getPerson Retrieves person records based on user query.
Request Message Description: createPerson

Table 14. Request Message Description: createPerson
SwiPersonIO Required. An instance of the Integration Object Integration

SwiPersonIO. Object
Contact is the parent header and the following

are the child.
Id Row Id of the record in the requesting system String

cross reference Id.
CellularPhone Contact’s mobile phone number. String

BirthDate Contact’s birth date. String
EmailAddress Contact’s email address. String
FaxPhone Contact’s fax number. String
FirstName Contact’s first name. String
HomePhone Contact’s home phone number. String
Income Contact’s income. String
IncomeCurrencyCode Income currency code. String
LastName Contact’s last name. String
MF Male or Female. String
MM Mr. or Ms. String
ManagerIntegrationId Manager’s Integration Id. String
MaritalStatus Contact’s marital status. String
MiddleName Contact’s middle name. String
MotherMaidenName Contact’s mothers’ maiden name String
PartyUId Party Unique Id. String
PersonUId Person user Id. String
PreferredCommunications Contact’s preferred communication method. String
PreferredLanguageCode Contact preferred language code. String

SocialSecurityNumber Contact’s Social security number. String
Status Status. String
AIAUCMIntegrationId Oracle Application Integration Architecture and String

Siebel UCM Integration Id.
ListOfContact_Account Optional. Account associated with the contact. Integration

Component
ListOfUcmContactPrivacy Optional. Contact’s privacy details. Integration

Component
ListOfContact_Communication Optional. Contact’s communication address. Integration

Address Component
ListOfContact_AlternatePhone Optional. Contact’s alternate phone details. Integration

Component
ListOfContact_Position Optional. Contact’s positions. Integration

Component

ListOfContact_Households Optional. Contact’s household. Integration

Component
ListOfContact_INSPersonalAdd Optional. Contact’s personal address details. Integration

ress Component
ListOfContact_Organization Optional. Contact’s organization details. Integration

Component
ListOfFINCORPAccount Optional. Details of the associated FINCORP Integration

account. Component
Response Message Description: createPerson

Table 15. Response Message Description: createPerson
SwiPersonIO An instance of the Integration Object Integration

SwiPersonIO with the list of operated records Object
Contact is the parent header.
Request Message Description: updatePerson

Table 16. Request Message Description: updatePerson

SwiPersonIO. Object

are the child.

cross reference Id.



Component

Component

Address Component

Component

Component

Component


ress Component

Component

account. Component
Response Message Description: updatePerson

Table 17. Response Message Description: updatePerson

Request Message Description: deletePerson

Table 18. Request Message Description: deletePerson

SwiPersonIO. Object

are the child.

cross reference Id.



Component

Component

Address Component

Component

Component

Component


ress Component

Component

account. Component
Response Message Description: deletePerson

Table 19. Response Message Description: deletePerson
SwiPersonIO Required. The same request instance of the Integration

Integration Object SwiPersonIO. Object
Request Message Description: getPerson

Table 20. Request Message Description: getPerson

SwiPersonIO. Object

are the child.

cross reference Id.




Component

Component

Address Component

Component

Component

Component

ress Component


Component

account. Component
Response Message Description: getPerson

Table 21. Response Message Description: getPerson

PersonService Application Interface

Technology Network.

Table 22. PersonService Service Object
PersonService Workflow: UCM Person CSSFACIFTransMgrService

Customer Profile Integration
SOAP Process.


Table 23. FetchAccountSiebelReqABCSImpl Data Object
SwiPersonIO Contact
Methods
Table 24. PersonService Methods
Operation Method
createPerson RunProcess
updatePerson RunProcess
deletePerson RunProcess
getPerson RunProcess
Example Package for PersonService

Request
...WebServices_XML\CRUDServices\PersonService\Request.xml
Response
...WebServices_XML\CRUDServices\PersonService\Response.xml
WSDL and Message Schema for PersonService

WSDL:
...WSDL\FetchAccountSiebelReqABCSImpl.wsdl
Schema:
...WSDL\SwiPersonIO.wsdl

Siebel UCM Web Services ■ GroupService
...WSDL\SwiPersonPublishIO.wsdl
GroupService
Use this Web service to perform all operations related to Households (Groups). UCM Household
messages are used in insert, query, update and delete operations to maintain Household information.
GroupService Operations
Table 25. GroupService Operations
Name Description
createGroup Creates a new group record.
updateGroup Updates and existing group record.
deleteGroup Deletes a group record.
getGroup Retrieves group records based on user query.
Request Message Description: createGroup

Table 26. Request Message Description: createGroup
SwiGroupIO Required. An instance of the Integration Integration

Object SwiGroupIO. Object
Household is the parent header and the

following are the child
The following nodes apply to SwiGroupIO

Id Row Id of the Record in the Requesting String
HouseholdName Name of the household. String
HouseholdNumber Household number. String
Name Household name. String
PhoneNumber Phone Number. String
PrivacyCode Privacy code String

Table 26. Request Message Description: createGroup

and Siebel UCM Integration Id
HouseholdLink Household link String
LengthOfResidence Length of residence String
HomeOwnerRenter Rental home owner String
ListOfHousehold_HouseholdAddress Optional. Household address Integration

Component
ListOfHousehold_Position Optional. Positions of household Integration

Component
ListOfUCMFINCORPAccountPrivacy Optional. Privacy details of FINCORP Integration

account Component
ListOfContact Optional. Contact details of household Integration

Component
ListOfHousehold_Organization Optional. Organizations details related to Integration

household Component
Response Message Description: createGroup

Table 27. Response Message Description: createGroup
SwiGroupIO An instance of the Integration Object SwiGroupIO Integration

with the list of records operated Household is the Object
parent header.

Request Message Description: updateGroup

Table 28. Request Message Description: updateGroup


Id Row Id of the Record in the Requesting String



Component

Component

account Component

Component

household Component

Response Message Description: updateGroup

Table 29. Response Message Description: updateGroup

parent header.
Request Message Description: deleteGroup

Table 30. Request Message Description: deleteGroup






Table 30. Request Message Description: deleteGroup

Component

Component

account Component

Component

household Component
Response Message Description: deleteGroup

Table 31. ResponseMessage Description: deleteGroup
SwiGroupIO Required. The same request instance of the Integration

Integration Object SwiGroupIO. Object
Request Message Description: getGroup

Table 32. Request Message Description: getGroup




Table 32. Request Message Description: getGroup


Component

Component

account Component

Component

household Component
Response Message Description: getGroup

Table 33. Response Message Description: getGroup

parent header.

GroupService Application Interface

Technology Network.

Table 34. GroupService Service Object
GroupService Workflow: UCM Group Customer UCM Group Customer

Profile Integration SOAP Profile Integration SOAP
Process. Process

Table 35. GroupService Data Object
SwiGroupIO Household
Methods
Table 36. GroupService Data Object
Operation Method
createGroup RunProcess
updateGroup RunProcess
deleteGroup RunProcess
getGroup RunProcess
Example Package for GroupService

Request
......WebServices_XML\CRUDServices\GroupService\Request.xml

Siebel UCM Web Services ■ Financial Account Service
Response
......WebServices_XML\CRUDServices\GroupService\Response.xml
WSDL and Message Schema for GroupService

WSDL:
...WSDL\GroupService.wsdl
Schema:
...WSDL\SwiGroupIO.wsdl
...WSDL\SwiGroupPublishIO.xsd
Financial Account Service

Use this Web service to create new financial service account records, and to perform update, delete
and retrieval operations.
Financial Account Service Operations

Table 37. Financial Account Service Operations
Name Description
createFinancialAsset Creates a new financial account record.
updateFinancialAsset Updates an existing financial account record.
deleteFinancialAsset Deletes a financial account record.
getFinancialAsset Retrieves financial account records based on user

query.

Request Message Description: createFinancialAsset

Table 38. Request Message Description: createFinancialAsset
SwiFinancialAssetIO Required. An instance of the Integration Object Integration

SwiFinancialAssetIO. Object
FINCORP. Account is the parent header and the

following are child nodes.
The following nodes apply to SwiFinancialAssetIO
Id Row Id of the Record in the Requesting system String

cross reference Id.
AccountName Account Name. String
AccountNumber Number of the Account. String
Name FINCORP Account Name. String

Siebel UCM Integration Id
ListOfCutAddress Optional. Business Address. Integration

Component
ListOfFINCORPAccountContact Optional. Contacts of FINCORP Account. Integration

Component
ListOfUCMFINCORPAccountPriv Optional. Privacy Details of FINCORP Account. Integration

acy Component
ListOfFinsCfFinancialAssetAddr Optional. Address details of FINCORP Account. Integration

ess Component
ListOfFINCORPAccountContact Optional. Contact details of FINCORP Account. Integration

Component
ListOfContact Contact details. Integration

Component

Response Message Description: createFinancialAsset

Table 39. Response Message Description: createFinancialAsset
SwiFinancialAssetIO An instance of the Integration Object Integration

SwiFinancialAssetIO with the list of operated Object
records.
Financial Corporation. Account is the parent

header.
Request Message Description: updateFinancialAsset


SwiFinancialAssetIO. Object
FINCORP Account is the parent header and the

following are child nodes.

cross reference Id.
AccountName Account Name. String
AccountNumber Number of the Account. String
Name FINCORP Account Name. String

ListOfCutAddress Optional. Business Address. Integration

Component

Component
ListOfUCMFINCORPAccountPriv Optional. Privacy Details of FINCORP Account. Integration

acy Component

ListOfFinsCfFinancialAssetAddr Optional. Address details of FINCORP Account. Integration

ess Component
ListOfFINCORPAccountContact Optional. Contact details of FINCORP Account. Integration

Component

Component
Response Message Description: updateFinancialAsset

Table 41. Response Message Description: updateFinancialAsset

SwiFinancialAssetIO with the list of operated records. Object
FINCORP Account is the parent header
Request Message Description: deleteFinancialAsset

Table 42. Request Message Description: deleteFinancialAsset
SwiFinancialAssetIO Required. An instance of the Integration Integration

Object SwiFinancialAssetIO. Object
FINCORP.Account is the parent header and

the following are child nodes.
Id Row Id of the Record in the requesting String

AccountName Account Name String
AccountNumber Number of the Account String
IntegrationId Integration Id String
Name FINCORP Account Name String

Table 42. Request Message Description: deleteFinancialAsset

ListOfCutAddress Optional. Business Address Integration

Component

Component
ListOfUCMFINCORPAccountPrivacy Optional. Privacy Details of FINCORP Integration

Account Component
ListOfFinsCfFinancialAssetAddress Optional. Address details of FINCORP Integration

Account Component
ListOfFINCORPAccountContact Optional. Contact details of FINCORP Integration

Account Component

Component
Response Message Description: deleteFinancialAsset

Table 43. Response Message Description: deleteFinancialAsset
SwiFinancialAssetIO Required. The same request instance of Integration

the Integration Object Object
SwiFinancialAssetIO.
Request Message Description: getFinancialAsset

Table 44. Request Message Description: getFinancialAsset

SwiFinancialAssetIO. FINCORP Account is the Object
parent header and the following are child nodes.

Table 44. Request Message Description: getFinancialAsset

cross reference Id.
AccountName Account Name String
AccountNumber Number of the Account String
IntegrationId Integration Id String
Name FINCORP Account Name String
AIAUCMIntegrationId Oracle Application Integration Architecture (AIA) String

ListOfCutAddress Optional. Business Address Integration

Component

Component
ListOfUCMFINCORPAccountPriv Optional. Privacy Details of FINCORP Account Integration

acy Component
ListOfFinsCfFinancialAssetAddr Optional. Address details of FINCORP Account Integration

ess Component
ListOfFINCORPAccountContact Optional. Contact details of FINCORP Account Integration

Component

Component
Response Message Description: getFinancialAsset

Table 45. Response Message Description: getFinancialAsset

SwiFinancialAssetIO with the list of operated Object
records
FINCORP. Account is the parent header


FinancialAssetService Application Interface

Technology Network.

Table 46. FinancialAssetService Service Object
FinancialAssetService Workflow: UCM Financial Not applicable

Asset Customer Profile
Integration SOAP
Process.

Table 47. FinancialAssetService Data Object
SwiFinancialAssetIO FINCORP Account
Methods
Table 48. FinancialAssetService Data Object
Operation Method
createFinancialAsset RunProcess
updateFinancialAsset RunProcess
deleteFinancialAsset RunProcess
getFinancialAsset RunProcess
Example Package for FinacialAccountService

Request
......WebServices_XML\CRUDServices\FinancialAssetService\Request.xml

Siebel UCM Web Services ■ OrganizationMatchService
Response
......WebServices_XML\CRUDServices\FinancialAssetService\Response.xml
WSDL and Message Schema for FinacialAccountService

WSDL:
...WSDL\FinancialAssetService.wsdl
Schema:
...WSDL\ListofSwiFinancialAssetIO.xsd
...WSDL\ListofSwiFinancialAssetPublishIO.xsd
OrganizationMatchService
Use this Web service to find similar Accounts and Organizations in designated databases, such as
UCM database, corresponding to the one being sent in a request message. The similarity is based on
advanced algorithms (as opposed to a plain search where a user would input A* and receive all
Account records beginning with A) and depends on the matching engine (such as ISS, SSA and so
on) used at the back-end with the match strategies, rules, and configurations in place.
OrganizationMatchService Operations
Table 49. OrganizationMatchService Operations
Name Description
OrganizationMatch Locates similar accounts based on predefined rules

and algorithms.
Request Message Description:

Table 50. Request Message Description:
SwiOrganizationMatchInputIO An instance of the SwiOrganizationMatchInputIO Integration

Integration Object Object

Siebel UCM Web Services ■ OrganizationMatchService
Response Message Description:

Table 51. Response Message Description:
SwiOrganizationMatchOutputIO An instance of the Integration

SwiOrganizationMatchOutputIO Integration Object
Object
OrganizationMatchService Application Interface

Technology Network.

Table 52. OrganizationMatchService Service Object
DeDuplication Business Service CSSDeDupService

Table 53. OrganizationMatchService Data Object

SwiOrganizationMatchInputIO SwiOrganizationMatchInputIO
SwiOrganizationMatchOutputIO SwiOrganizationMatchOutputIO
Methods
Table 54. OrganizationMatchService Methods
Operation Method
OrganizationMatch Organization Match Web service
Example Package for OrganizationMatchService


Siebel UCM Web Services ■ PersonMatchService
Request
......WebServices_XML\OrganizationMatchService\Request.xml
Response
...WebServices_XML\OrganizationMatchService\Response.xml
WSDL and Message Schema for OrganizationMatchService

...WSDL\OrganizationMatchService.wsdl
...WSDL\SwiOrganizationMatchInputIO.xsd
...WSDL\SwiOrganizationMatchOutputIO.xsd
PersonMatchService
Use this Web service to find similar Contacts in designated databases, such as UCM database,
corresponding to the one being sent in a request message. The similarity is based on an advanced
algorithms (as opposed to a plain search where a user would input A* and receive all Account records
beginning with A) and depends on the matching engine (such as ISS, SSA and so on) used at the
back-end with the match strategies, rules, and configurations in place.
PersonMatchService Operations
Table 55. OrganizationMatchService Operations
Name Description
PersonMatch Finds out similar Contacts based on predefined rules

and algorithms.
Request Message Description: PersonMatch

Table 56. Request Message Description:
SwiPersonMatchInputIO An instance of the SwiPersonMatchInputIO Integration

Integration Object. Object

Siebel UCM Web Services ■ PersonMatchService
Response Message Description: PersonMatch

Table 57. Response Message Description:
SwiPersonMatchOutputIO An instance of the Integration

SwiPersonMatchOutputIO Integration Object
Object.
PersonMatchService Application Interface

Technology Network.

Table 58. PersonMatchService Service Object
DeDuplication Business Service CSSDeDupService

Table 59. PersonMatchService Data Object

SwiPersonMatchInputIO SwiPersonMatchInputIO
SwiPersonMatchOutputIO SwiPersonMatchOutputIO
Methods
Table 60. PersonMatchService Methods
Operation Method
PersonMatch Person Match Web service
Example Package for PersonMatchService


Siebel UCM Web Services ■ OrganizationCrossReferenceService
Request
....WebServices_XML\PersonMatchService\Request.xml
Response
...WebServices_XML\PersonMatchService\Response.xml
WSDL and Message Schema for PersonMatchService

...WSDL\PersonMatchService.wsdl
...WSDL\SwiPersonMatchInputIO.xsd
...WSDL\SwiPersonMatchOutputIO.xsd
OrganizationCrossReferenceService
Use this Web services to create explicit links between organization records within UCM and those in
participating applications.
OrganizationCrossReferenceService Operations
Table 61. FetchAccountSiebelReqABCSImpl Operations
Name Description
createOrganizationCrossReference Creates a cross reference Id to a Organization

record.
updateOrganizationCrossReference Updates a cross reference Id to a Organization

record.
deleteOrganizationCrossReference Deletes a cross reference Id to a Organization

record.
getOrganizationCrossReference Retrieves a cross reference Id to a Organization

record.

Request Message Description: createOrganizationCrossReference

Table 62. Request Message Description: createOrganizationCrossReference
SwiOrganizationPublishIO An instance of the Integration Object Integration

SwiOrganizationPublish. The main component is Object
Account, and CIF Account Reference.
Response Message Description: createOrganizationCrossReference

Table 63. Response Message Description: createOrganizationCrossReference

Request Message Description: updateOrganizationCrossReference

Table 64. Request Message Description: updateOrganizationCrossReference

Response Message Description: updateOrganizationCrossReference

Table 65. Response Message Description: updateOrganizationCrossReference


Request Message Description: deleteOrganizationCrossReference

Table 66. Request Message Description: deleteOrganizationCrossReference

Response Message Description: deleteOrganizationCrossReference

Table 67. Response Message Description: deleteOrganizationCrossReference

Request Message Description: getOrganizationCrossReference

Table 68. Request Message Description: getOrganizationCrossReference

Account.
Response Message Description: getOrganizationCrossReference

Table 69. Response Message Description: getOrganizationCrossReference

Account.
OrganizationCrossReferenceService Application Interface

Technology Network.


Table 70. OrganizationCrossReferenceService Service Object
UCM Cross Reference Service Business Service CSSUCMXRefService

Table 71. OrganizationCrossReferenceService Data Object
SWIOrganizationPublishIO Account
Methods
Table 72. OrganizationCrossReferenceService Methods
Operation Method
createOrganizationCrossReference RunProcess
updateOrganizationCrossReference RunProcess
deleteOrganizationCrossReference RunProcess
getOrganizationCrossReference RunProcess
Example Package for OrganizationCrossReferenceService

Request
...WebServices_XML\CrossReferenceServices\OrganizationCrossReferenceService\Request.xml
Response
...WebServices_XML\CrossReferenceServices\OrganizationCrossReferenceService\Response.xml

Siebel UCM Web Services ■ PersonCrossReferenceService
WSDL and Message Schema for OrganizationCrossReferenceService

WSDL:
...WSDL\OrganizationCrossReferenceService.wsdl
Schema
...WSDL\ListofSwiOrganizationIO.xsd
...WSDL\ListofSwiOrganizationPublishIO.xsd
PersonCrossReferenceService
Use this Web services to create explicit links between person records within UCM and those in
PersonCrossReferenceService Operations
Table 73. PersonCrossReferenceService Operations
Name Description
createPersonCrossReference Creates a cross reference Id to a Person record.
updatePersonCrossReference Updates a cross reference Id to a Person record.
deletePersonCrossReference Deletes a cross reference Id to a Person record.
getPersonCrossReference Retrieves a cross reference Id to a Person record.
Request Message Description: createPersonCrossReference

Table 74. Request Message Description: createPersonCrossReference
SwiPersonPublishIO An instance of the Integration Object Integration

SwiPersonPublishIO. The main components are Object
Contact and CIF Contact Reference.

Response Message Description: createPersonCrossReference

Table 75. Response Message Description: createPersonCrossReference

Request Message Description: updatePersonCrossReference

Table 76. Request Message Description: updatePersonCrossReference

Response Message Description: updatePersonCrossReference

Table 77. Response Message Description: updatePersonCrossReference

Request Message Description: deletePersonCrossReference

Table 78. Request Message Description: deletePersonCrossReference


Response Message Description: deletePersonCrossReference

Table 79. Response Message Description: deletePersonCrossReference

Request Message Description: getPersonCrossReference

Table 80. Request Message Description: getOrganizationCrossReference

SwiPersonPublishIO. The main components are Object.
Contact.
Response Message Description: getPersonCrossReference

Table 81. Response Message Description: getPersonCrossReference

Contact.
PersonCrossReferenceService Application Interface

Technology Network.

Table 82. PersonCrossReferenceService Service Object



Table 83. PersonCrossReferenceService Data Object
SWIPersonPublishIO Contact
Methods
Table 84. PersonCrossReferenceService Methods
Operation Method
createPersonCrossReference CreatePersonCrossReference
updatePersonCrossReference UpdatePersonCrossReference
deletePersonCrossReference DeletePersonCrossReference
getPersonCrossReference GetPersonCrossReference
Example Package for PersonCrossReferenceService

Request
...WebServices_XML\CrossReferenceServices\PersonCrossReferenceService\Request.xml
Response
...WebServices_XML\CrossReferenceServices\PersonCrossReferenceService\Response.xml
WSDL and Message Schema for OrganizationCrossReferenceService

WSDL:
...WSDL\PersonCrossReferenceService.wsdl
Schema:
...WSDL\ListofSwiPersonIO.xsd

Siebel UCM Web Services ■ GroupCrossReferenceService
...WSDL\ListofSwiPersonPublishIO.xsd
GroupCrossReferenceService
Use this Web services to create explicit links between Group records within UCM and those in
GroupCrossReferenceService Operations
Table 85. GroupCrossReferenceService Operations
Name Description
createGroupReference Creates a cross reference Id to a Group record.
updateGroupReference Updates a cross reference Id to a Group record.
deleteGroupReference Deletes a cross reference Id to a Group record.
getGroupReference Retrieves a cross referene Id to a Group record.
Request Message Description: createGroupCrossReference

Table 86. Request Message Description: createGroupCrossReference
SwiGroupPublishIO An instance of the Integration Object Integration

SwiGroupPublishIO. Object
Response Message Description: createGroupCrossReference

Table 87. Response Message Description: createGroupCrossReference


Request Message Description: updateGroupCrossReference

Table 88. Request Message Description: updateGroupCrossReference

Integration ObjectResponse Message Description: updateGroupCrossReference

Table 89. Response Message Description: updateGroupCrossReference

Request Message Description: deleteGroupCrossReference

Table 90. Request Message Description: deleteGroupCrossReference

Response Message Description: deleteGroupCrossReference

Table 91. Response Message Description: deleteGroupCrossReference

Request Message Description: getGroupCrossReference

Table 92. Request Message Description: getGroupCrossReference


Response Message Description: getGroupCrossReference

Table 93. Response Message Description: getGroupCrossReference

GroupCrossReferenceService Application Interface

Technology Network.

Table 94. GroupCrossReferenceService Service Object

Table 95. GroupCrossReferenceService Data Object

SWIGroupPublishIO
Methods
Table 96. GroupCrossReferenceService Methods
Operation Method
createGroupCrossReference CreateGroupCrossReference
updateGroupCrossReference UpdateGroupCrossReference
deleteGroupCrossReference DeleteGroupCrossReference
getGroupCrossReference GetGroupCrossReference

Siebel UCM Web Services ■ FinancialAssetCrossReferenceService
Example Package for GroupCrossReferenceService

Request
...WebServices_XML\CrossReferenceServices\GroupCrossReferenceService\Request.xml
Response
....WebServices_XML\CrossReferenceServices\GroupCrossReferenceService\Response.xml
WSDL and Message Schema for GroupCrossReferenceService

WSDL:
...WSDL\GroupCrossReferenceService.wsdl
Schema:
...WSDL\ListofSwiGroupIO.xsd
...WSDL\ListofSwiGroupPublishIO.xsd
FinancialAssetCrossReferenceService
Use this Web services to create explicit links between financial account records within Siebel
AccountUCM and those in participating applications.
FinancialAssetCrossReferenceService Operations
Table 97. FinancialAssetCrossReferenceService Operations
Name Description
createFinancialAssetReference Creates a cross reference Id to a FinancialAsset

record.
updateFinancialAssetReference Updates a cross reference Id to a FinancialAsset

record.

Table 97. FinancialAssetCrossReferenceService Operations
Name Description
deleteFinancialAssetReference Deletes a cross reference Id to a FinancialAsset

record.
getFinancialAssetReference Retrieves a cross reference Id to a FinancialAsset

record.
Request Message Description: createFinancialAssetCrossReference

Table 98. Request Message Description: createFinancialAssetCrossReference
SwiFinancialAssetPublishIO An instance of the Integration Object Integration

SwFinancialAssetPublishIO. Object
Response Message Description: createFinancialAssetCrossReference

Table 99. Response Message Description: createFinancialAssetCrossReference

Request Message Description: updateFinancialAssetCrossReference

Table 100. Request Message Description: updateFinancialAssetCrossReference

Response Message Description: updateFinancialAssetCrossReference

Table 101. Response Message Description: updateFinancialAssetCrossReference


Request Message Description: deleteFinancialAssetCrossReference

Table 102. Request Message Description: deleteFinancialAssetCrossReference

Response Message Description: deleteFinancialAssetCrossReference

Table 103. Response Message Description: deleteFinancialAssetCrossReference

Request Message Description: getFinancialAssetCrossReference

Table 104. Request Message Description: getFinancialAssetCrossReference

Response Message Description: getFinancialAssetCrossReference

Table 105. Response Message Description: getFinancialAssetCrossReference

FinancialAssetCrossReferenceService Application Interface

Technology Network.


Table 106. FinancialAssetCrossReferenceService Service Object

Table 107. FinancialAssetCrossReferenceService Data Object
SWIFinancialAssetPublishIO FINCORP Account
Methods for FinancialAssetCrossReferenceService

Table 108. FinancialAssetCrossReferenceService Methods
Operation Method
createFinancialAssetCrossReference CreateFinancialAssetCrossReference
updateFinancialAssetCrossReference UpdateFinancialAssetCrossReference
deleteFinancialAssetCrossReference DeleteFinancialAssetCrossReference
getFinancialAssetCrossReference GetFinancialAssetCrossReference
Example Package for FinancialAssetCrossReferenceService

Request
...WebServices_XML\CrossReferenceServices\FinancialAssetCrossReferenceService\Request.xml
Response
...WebServices_XML\CrossReferenceServices\FinancialAssetCrossReferenceService\Response.xml

WSDL and Message Schema for FinancialAssetCrossReferenceService

WSDL:
...WSDL\FinancialAssetCrossReferenceService.wsdl
Schema:
...WSDL\ListofSwiFinancialAssetPublishIO.xsd


3 Siebel UCM Data Enrichment
Web Services
This chapter includes processes on topics on how to configure Siebel Outbound Web Services for
integration with Siebel UCM. Topics include:
■ “Overview of Siebel UCM Data Enrichment Web Services” on page 79
■ “Process for Configuring Data Enrichment” on page 79
Overview of Siebel UCM Data Enrichment

Web Services
Siebel UCM provides integration with third party data enrichment providers, such as Acxiom. Siebel
UCM uses Oracle Application Integration Architecture to provide a pre-build set of enrichment APIs
to enrich consumer records in UCM. This service also enriches household and address information
for consumer records. The service infrastructure can be extended by small configuration changes to
support other third party customer data enrichment vendors.
Process for Configuring Data Enrichment

To configure for data enrichment, perform the following tasks:
■ “Creating the Proxy Business Service” on page 79
■ “Modifying the Newly Created Proxy Business Service” on page 80
■ “Modifying Data Enrichment Business Service User Properties” on page 81
■ “Registering the Data Enrichment Web Services” on page 81
■ “Configuring the Run-time Event” on page 82
Creating the Proxy Business Service

This step is part of “Process for Configuring Data Enrichment” on page 79.
NOTE: You only perform this step if you are creating proxy business services using WSDL files
provided by a third party data enrichment Web service.
CAUTION: This configuration step is not required for OracleAIA-UCM Integration. There is a
prerequisite requirement for a middleware provider to be installed and set up to handle outbound
data enrichment calls. If you are setting up an Oracle AIA-Siebel UCM Integration, make sure Oracle
AIA is set up and functioning. If Siebel UCM is integrated with any other middleware, make sure the
middleware installation is completed before proceeding with the following steps.]

Siebel UCM Data Enrichment Web Services ■ Process for Configuring Data Enrichment
To create the proxy business service

1 From the Siebel Tools File menu, select New Object.
2 In the New Object wizard click the EAI tab and select the Web Service Icon.
3 Lock the project Web Service Integration and and lock the Project name.
4 Browse to the location of the WSDL file provided by the third party data enrichment Web service.
The run-time data file and log file entries are automatically created.
CAUTION: Do not check the Process Fault Schema check box.
5 Click Next.
6 Check the Deploy Integration Objects and Proxy Business Services check box.
7 Click Finish.
8 Check in the logs for the entry Outbound proxy business service definitions to be generated. At
the end of the definition, you will see the name of the proxy business service you created.
For example:
Outbound proxy business service definitions to be generated:

ProcessPersonUCMReqABCSImpl
In this example, ProcessPersonUCMReqABCSImpl is the name of the proxy service that was
created.
9 Once the proxy business service is created, click the Business Services object in the Object
Explorer.
Modifying the Newly Created Proxy Business Service

NOTE: You only perform this step if you are creating proxy business services using WSDL files
provided by a third party data enrichment Web service.
To modify the newly created business service

1 In Siebel Tools Business Services screen, query for the newly created proxy business service.
2 In the Object Explorer, navigate to Business Service Method Arguments.
3 Search for arguments of type Integration Object.
4 Note the Integration Object names, then using the Object Explorer, locate and delete these
objects.
The default Integration Objects will not be used, instead the newly imported Integration Objects
will take their place.

5 Replace the existing Integration Object name in the Business Service Method Arguments of the
proxy service with the new Integration Object name displayed in the following table:
Existing Integration Object Name New Integration Object Name
Person SwiPersonIO
Modifying Data Enrichment Business Service User Properties

CAUTION: This configuration step is not required for OracleAIA-UCM Integrations.
To modify the Data Enrichment business service

1 In Siebel Tools Business Services screen, query for the Data Enrichment business service.
2 In the Object Explorer, navigate to Business Service User Properties.
3 Make the following changes to the user property definitions:
Field New Value
Proxy Business Service Method ProcessPerson
Proxy Business Service Name ProcessPersonUCMReqABCSImpl.
This is the name of the Proxy Business Service

created previously this process.
RequestTypeContact ProcessPersonReqMsg:ListOfSwiPersonIO
This is the name of the input integration object as

mentioned in the method arguments of the proxy
business service.
ResponseTypeContact ProcessPersonRespMsg:ListOfSwiPersonIO
This is the name of the output integration object

as mentioned in the method arguments of the
proxy business service.
UCMIONameContact SwiPersonIO
Registering the Data Enrichment Web Services

To register data enrichment Web services

1 If you have an OracleAIA-Axciom Integration see Step 2, if not see Step 4.
2 From the Outbound Web Services view query for the following OracleAIA webservice:
ProcessPersonUCMReqABCSImpl

3 Change the address of the ports corresponding to this Web service to point to the appropriate
AIA end point.
4 If you do not have Axciom Integration, from the Outbound Web Services view query for the
webservice that you created in the following task: “To create the proxy business service” on
page 80.
5 Change the address of the ports corresponding to the Web services to point to the appropriate
Middleware end point.
Configuring the Run-time Event

To configure the run-time event

1 In the Siebel Web client, navigate to Administration-Runtime Events, then Action Sets.
2 In the Action Sets screen, click New.
3 Enter the following values:
Field Value
Name Choose a name.
Action Type BusService.
Active Y
Sequence 1
Business Service Name DataEnrichment
Business Service Method Data Enrichment

Conditional Expression SystemPreference("Enable Data Enrichment") LIKE 'TRUE' AND (
GetProfileAttr("Disable Data Enrichment") IS NULL OR
GetProfileAttr("Disable Data Enrichment") LIKE 'FALSE' )
4 From the Action Sets menu, choose Save Record.
5 Navigate to the Events view, and click New.
6 Create a new event by entering the following values:
Field Value
Sequence The least sequence number possible.
NOTE: There may be other events for the same Object and Event,
so you must provide a different number from the existing events.
Object Type BusComp
Object Name Contact

Field Value
Event PreWriteRecord
Action Set Name The name you provided in Step 3 on page 82.
7 From the Events menu, select Save Record.
9 Query for: Enable Data Enrichment, and make sure the System Preference Value is set to TRUE.


A Appendix
This appendix contains information about manual import and creation of Siebel UCM Web services.
It contains the following topics:
NOTE: These topics are optional. In the event that your services were not configured during
installation and setup, you may manually create them using the tasks which follow.
■ “Roadmap for Manually Importing Siebel UCM Web Services” on page 85
■ “Process for Manually Creating Organization CRUD Web Services” on page 86
■ “Process for Manually Creating Group CRUD Web Services” on page 92
■ “Process for Manually Creating Financial Account CRUD Web Services” on page 95
■ “Process for Manually Creating Organization Cross Reference Web Services” on page 98
■ “Process for Manually Creating Person Cross Reference Web Services” on page 100
■ “Process for Manually Creating Group Cross Reference Web Services” on page 103
■ “Process for Manually Creating Financial Account Cross Reference Web Services” on page 105
■ “Process for Manually Creating Organization Match Web Services” on page 108
■ “Process for Manually Creating Person Match Web Services” on page 110
Roadmap for Manually Importing Siebel

UCM Web Services
If required, you can manually import UCM Web services using the following topics:
■ “Process for Manually Creating Financial Account CRUD Web Services” on page 95
■ “Process for Manually Creating Organization Cross Reference Web Services” on page 98
■ “Process for Manually Creating Person Cross Reference Web Services” on page 100
■ “Process for Manually Creating Group Cross Reference Web Services” on page 103
■ “Process for Manually Creating Financial Account Cross Reference Web Services” on page 105
■ “Process for Manually Creating Organization Match Web Services” on page 108
■ “Process for Manually Creating Person Match Web Services” on page 110

Appendix ■ Process for Manually Creating Organization CRUD Web Services
Process for Manually Creating

Organization CRUD Web Services
To create CRUD Web services for Siebel UCM, perform the following tasks:
■ “Registering the Organization Web Service” on page 86
■ “Creating Organization Service Ports” on page 86
■ “Creating Organization Operations” on page 88
■ “Generating the WSDL” on page 88
Registering the Organization Web Service

This step is part of “Process for Manually Creating Organization CRUD Web Services” on page 86.
To register Organization Web services

1 From the Site Map, select Administration-Web Services, then Inbound Web Services.
2 From the Inbound Web Services view, click New.
3 Enter the values displayed in the following table:
Field Value
Namespace http://xmlns.oracle.com/apps/mdm/customer.
Name OrganizationService
Status Active
Comment UCM Organization Composite Web Service
Creating Organization Service Ports

To create Organization service ports

1 From the Inbound Web Services view, select the newly created OrganizationService Web service.
2 In the Service Ports view, click New.
3 In the name field enter: OrganizationService
4 Click the Select button in the Type field, and when the applet appears, click New.

5 Enter values displayed in the following table:
Field Value
Name UCM Organization Customer Profile Integration SOAP Process.

Service
Implementation Type Workflow Process
Workflow Process Name UCM Organization Customer Profile Integration SOAP Process
6 Click OK, then in the Service Ports view, enter remaining values displayed in the following table:
Field Value
Transport HTTP
Address Enter the appropriate address.
Binding SOAP_DOC_LITERAL
Comments Organization Service Port
7 Click Save, then click New to make the next entry for Service Port 2.
9 Enter the following name: OrganizationQueryService.
Field Value
Name UCM Organization Customer Profile Integration SOAP Query

Process

Workflow Process Name UCM Organization Customer Profile Integration SOAP Query
Process
Field Value
Transport HTTP
Comments Organization Query Service Port
13 From the Service Ports menu, choose Save Record.

Creating Organization Operations

To create Organization operations

1 In the Service Ports view, select the OrganizationService service port.
2 In the Operations view, click Add, then in the popup applet, click New.
3 Enter the following name: createOrganization.
4 Leave the default value of the Method Display Name to RunProcess.
5 Set the Authentication Type as None.
6 Similarly add the following operations to the service port:
Operation Name Method Display Name Authentication Type
createOrganization RunProcess None
updateOrganization RunProcess None
deleteOrganization RunProcess None
7 In the Service Ports view, select the OrganizationQueryService service port.
9 Enter the following name: getOrganization.’
10 Leave the default value of the Method Display Name to RunProcess

Generating the WSDL

To generate the WSDL

1 From the Inbound Web Services screen, click the Clear Cache button.
2 Select the OrganizationService, and click the Generate WSDL button.
3 Save the WSDL file to a logical directory.
This generated WSDL will not be used, instead the WSDL in the QuickFix installation directory
will be used.

Appendix ■ Process for Manually Creating Person CRUD Web Services
Process for Manually Creating Person

CRUD Web Services
To create Person CRUD Web Services for Siebel UCM, perform the following tasks:
■ “Registering the Person Web Service” on page 89
■ “Creating Person Service Ports” on page 89
■ “Creating Person Operations” on page 91
Registering the Person Web Service

To register the PersonService Web Service

Field Value
Namespace http://xmlns.oracle.com/apps/mdm/customer
Name PersonService
Status Active
Comment UCM Person Composite Web Service
Creating Person Service Ports

To create Person Service Ports

1 In the Inbound Web Services view, select the newly created PersonService web service.
3 Enter the following name: PersonService.

Field Value
Name UCM Person Customer Profile Integration SOAP Process
Workflow Process Name UCM Person Customer Profile Integration SOAP Process
Field Value
Transport HTTP
Comments Person Service Port
9 Enter the following name: PersonQueryService.
Field Value
Name UCM Person Customer Profile Integration SOAP Query Process
Workflow Process Name UCM Person Customer Profile Integration SOAP Query Process
Field Value
Transport HTTP
Comments Person Query Service Port

Creating Person Operations

To create Person operations

1 In the Service Ports view, select the PersonService service port.
3 Enter the following name: createPerson.
4 Leave the default value of the Method Display Name as RunProcess.
createPerson RunProcess None.
updatePerson RunProcess None
deletePerson RunProcess None
7 In the Service Ports view, select the PersonQueryService service port.
9 Enter the following name: getPerson.

Generating the WSDL


2 Select the PersonService from the Inbound Web Services screen, and click the Generate WSDL
button.
This generated WSDL will not be used, instead the WSDL in the QuickFix installation directory will be
used.

Appendix ■ Process for Manually Creating Group CRUD Web Services
Process for Manually Creating Group

CRUD Web Services
To create Group CRUD Web services for Siebel UCM, perform the following tasks:
■ “Registering the Group Web Service” on page 92
■ “Creating Group Service Ports” on page 92
■ “Creating Group Operations” on page 94
Registering the Group Web Service

This step is part of “Process for Manually Creating Group CRUD Web Services” on page 92.
To register Group Web services

Field Value
Name GroupService
Status Active
Comment UCM Group Composite Web Service
Creating Group Service Ports

To create Group service ports

1 In the Inbound Web Services view, select the newly created GroupService Web service.
3 Enter the following name: GroupService

Field Value
Name UCM Group Customer Profile Integration SOAP Process
Workflow Process Name UCM Group Customer Profile Integration SOAP Process
Field Value
Transport HTTP
Comments Group Service Port
9 Enter the following name: GroupQueryService.
Field Value
Name UCM GroupCustomer Profile Integration SOAP Query Process
Workflow Process Name UCM GroupCustomer Profile Integration SOAP Query Process
Field Value
Transport HTTP
Comments Group Query Service Port

Creating Group Operations

To create Group operations

1 In the Service Ports view, select the GroupService service port.
3 Enter the following name: createGroup.
4 Leave the default value of the Method Display Name to Run Process.
5 Set Authentication Type as None.
6 Similarly add the following operations to the GroupService service port:
createGroup RunProcess None
updateGroup RunProcess None
deleteGroup RunProcess None
7 In the Service Ports view, select the GroupQueryService service port.
9 Enter the following name: getGroup.

Generating the WSDL


2 Select the GroupService from the Inbound Web Services screen, and click the Generate WSDL
button.
will be used.

Appendix ■ Process for Manually Creating Financial Account CRUD Web Services
Process for Manually Creating Financial

Account CRUD Web Services
To create Financial Account CRUD Web Services for Siebel UCM, perform the following tasks:
■ “Registering the Financial Account Web Service” on page 95
■ “Creating Financial Account Service Ports” on page 95
■ “Creating Financial Account Operations” on page 97
Registering the Financial Account Web Service

This step is part of “Process for Manually Creating Financial Account CRUD Web Services” on page 95.
To register Financial Account Web service

Field Value
Name FinancialAssetService
Status Active
Comment UCM Financial Asset Composite Web Service
Creating Financial Account Service Ports

To create Financial Account service Ports

1 In the Inbound Web Services view, select the newly created FinancialAssetService Web service.
3 Enter the following name: FinancialAssetService.

Field Value
Name UCM Financial Asset Customer Profile Integration SOAP Process
Workflow Process Name UCM Financial Asset Customer Profile Integration SOAP Process
Field Value
Transport HTTP
Comments Financial Asset Service Port
9 Enter the following name: FinancialAssetQueryService.
10 Click the Select button in the Type field. , and when the popup applet appears, click New.
Field Value
Name UCM Financial Asset Customer Profile Integration SOAP Query

Process

Workflow Process Name UCM Financial Asset Customer Profile Integration SOAP Query
Process
Field Value
Transport HTTP
Comments Financial Asset Query Service Port

Creating Financial Account Operations

To create Financial Account operations

1 In the Service Ports view, select the FinancialAssetService service port.
3 Enter the following name: createFinancialAsset.
createFinancialAsset RunProcess None
updateFinancialAsset RunProcess None
deleteFinancialAsset RunProcess None
7 In the Service Ports view, select the FinancialAssetQueryService service port.
9 Enter the following name: getFinancialAsset.

Generating the WSDL


2 Select the FinancialAssetService from the Inbound Web Services screen, and click the Generate
WSDL button.
will be used.

Appendix ■ Process for Manually Creating Organization Cross Reference Web Services

Organization Cross Reference Web
Services
To create Organization Cross Reference Web services for Siebel UCM, perform the following tasks:
■ “Registering the Organization Cross Reference Web Service” on page 98
■ “Creating Organization Cross Reference Service Ports” on page 98
■ “Creating Organization Cross Reference Operations” on page 99
Registering the Organization Cross Reference Web Service

This step is part of “Process for Manually Creating Organization Cross Reference Web Services” on
page 98.
To register Organization Cross Reference Web services

Field Value
Name OrganizationCrossReferenceService
Status Active
Comment Organization Cross Reference Service
Creating Organization Cross Reference Service Ports

page 98.
To create Organization Cross Reference service ports

1 Select the newly created Organization Cross Reference Web service.

3 Enter the following name: OrganizationCrossReferenceService

Appendix ■ Process for Manually Creating Organization Cross Reference Web Services
Field Value
Name OrganizationCrossReferenceService
Implementation Type Business Service
Business Service Name UCM Cross Reference Service
Field Value
Transport HTTP
Comments Organization Cross Reference Service Port
Creating Organization Cross Reference Operations

page 98.
To create Organization Cross Reference operations

1 In the Service Ports view, select the OrganizationCrossReference service port.
3 Enter the following name: createOrganizationCrossReference.
4 Click the Select button in the Method Display Name field, and when the popup applet appears,
pick the following entry:
Display Name Name
Create Organization Cross Reference createOrganizationCrossReference
5 Once the entry is selected, set Authentication Type to None.

Appendix ■ Process for Manually Creating Person Cross Reference Web Services
6 Similarly add the following operations:
Authentication
Method Display Name Name Type
createOrganizationCrossReference Create Organization Cross None.

Reference
updateOrganizationCrossReference Update Organization Cross None

Reference
deleteOrganizationCrossReference Delete Organization Cross None

Reference
getOrganizationCrossReference Get Organization Cross None

Reference
Generating the WSDL

page 98.

2 Select the OrganizationCrossReferenceService from the Inbound Web Services screen, and click
the Generate WSDL button.
will be used.

Cross Reference Web Services
To manually create Person Cross Reference Web services for Siebel UCM, perform the following tasks:
■ “Registering the Person Cross Reference Web Service” on page 100
■ “Creating Person Cross Reference Service Ports” on page 101
■ “Creating Person Cross Reference Operations” on page 102
Registering the Person Cross Reference Web Service

This step is part of “Process for Manually Creating Person Cross Reference Web Services” on page 100.
To register Person Cross Reference Web services

Field Value
Name PersonCrossReferenceService
Status Active
Comment Person Cross Reference Web Service
Creating Person Cross Reference Service Ports

To create Person Cross Reference service ports

1 Select the newly created PersonCrossReference Web service.
3 Enter the following name: PersonCrossReferenceService.
Field Value
Name PersonCrossReferenceService
Field Value
Transport HTTP
Comments Person Cross Reference Service Port
Siebel UCM and CRM Integration Guide Version 8.1 QF0009 10 1

Creating Person Cross Reference Operations

To create Person Cross Reference operations

1 In the Service Ports view, select the PersonCrossReferenceService service port.
3 Enter the following name: createPersonCrossReference.
4 Click the Select button in the Method Display Name field, and when the applet appears, pick the
following entry:
Display Name Name
Create Person Cross Reference CreatePersonCrossReference
5 Once the entry is selected, set Authentication Type to None.
Method Display Authentication

Name Name Type
createPersonCrossReference Create Person Cross None

Reference
updatePersonCrossReference Update Person Cross None

Reference
deletePersonCrossReference Delete Person Cross None

Reference
getPersonCrossReference Get Person Cross None

Reference
Generating the WSDL


2 Select the PersonCrossReferenceService from the In the Inbound Web Services screen, and click
will be used.
Appendix ■ Process for Manually Creating Group Cross Reference Web Services
Process for Manually Creating Group

Cross Reference Web Services
To manually create Group Cross Reference Web service for Siebel UCM, perform the following tasks:
■ “Registering the Group Cross Reference Web Service” on page 103
■ “Creating Group Cross Reference Service Ports” on page 103
■ “Creating Group Cross Reference Operations” on page 104
Registering the Group Cross Reference Web Service

This step is part of “Process for Manually Creating Group Cross Reference Web Services” on page 103.
To register Group Cross Reference Web services

Field Value
Name GroupCrossReferenceService
Status Active
Comment Group Cross Reference Web Service
Creating Group Cross Reference Service Ports

To create Group Cross Reference service ports

1 Select the newly created Person Cross Reference Web service.
3 Enter the following name: GroupCrossReferenceService.

Appendix ■ Process for Manually Creating Group Cross Reference Web Services
Field Value
Name GroupCrossReferenceService
Field Value
Transport HTTP
Comments Group Cross Reference Service Port
Creating Group Cross Reference Operations

To create Group Cross Reference operations

1 In the Service Ports view, select the GroupCrossReferenceService service port.
3 Enter the following name: createGroupCrossReference.
following entry:
Display Name Name
Create Group Cross Reference CreateGroupCrossReference
5 Once the above entry is selected, set Authentication Type to None.
Authentication
Name Method Display Name Type
createGroupCrossReference Create Group Cross Reference None.
updateGroupCrossReference Update Group Cross Reference None
Appendix ■ Process for Manually Creating Financial Account Cross Reference Web Services
Authentication
deleteGroupCrossReference Delete Group Cross Reference None
getGroupCrossReference Get Group Cross Reference None
Generating the WSDL


2 Select the GroupCrossReferenceService from the In the Inbound Web Services screen, and click
will be used.
Process for Manually Creating Financial

Account Cross Reference Web Services
To manually create Financial Account Cross Reference Web services for Siebel UCM, perform the
following tasks:
■ “Registering the Financial Account Cross Reference Web Service” on page 105
■ “Creating Financial Account Cross Reference Service Ports” on page 106
■ “Creating Financial Account Cross Reference Operations” on page 106
Registering the Financial Account Cross Reference Web Service

This step is part of “Process for Manually Creating Financial Account Cross Reference Web Services” on
page 105.
To register Financial Account Cross Reference Web services


Field Value
Name FinancialAssetCrossReferenceService
Status Active
Comment UCM Financial Asset Cross Reference Web Service
Creating Financial Account Cross Reference Service Ports

page 105.
To create Financial Account Cross Reference service ports

1 Select the newly created Financial Asset Cross Reference Web service.
3 Enter the following name: FinancialAssetCrossReferenceService.
Field Value
Name FinancialAssetCrossReferenceService
Field Value
Transport HTTP
Comments Financial Asset Cross Reference Service Port
Creating Financial Account Cross Reference Operations

page 105.
To create Group Cross Reference operations

1 In the Service Ports view, select the GroupCrossReference service port.
3 Enter the following name: createFinancialAssetCrossReference.
following entry:
Display Name Name
Create Financial Asset Cross CreateFinancialAssetCrossReference

Reference
6 Similarly add the following operation:
Authentication
createFinancialAssetCrossReference Create Financial Asset Cross None

Reference
updateFinancialAssetCrossReference Update Financial Asset Cross None

Reference
deleteFinancialAssetCrossReference Delete Financial Asset Cross None

Reference
getFinancialAssetCrossReference Get Financial Asset Cross None

Reference
Generating the WSDL

page 105.

2 Select the FinancialAssetCrossReferenceService from the In the Inbound Web Services screen,
and click the Generate WSDL button.
will be used.

Appendix ■ Process for Manually Creating Organization Match Web Services

Organization Match Web Services
To manually create Organization Match Web services for Siebel UCM, perform the following tasks:
■ “Registering the Organization Match Web Service” on page 108
■ “Creating Organization Match Service Ports” on page 108
■ “Creating Organization Match Operations” on page 109
Registering the Organization Match Web Service

This step is part of “Process for Manually Creating Organization Match Web Services” on page 108.
To register Person Match Web services

Field Value
Namespace http://siebel.com/DataQuality
Name OrganizationMatchService
Status Active
Comment Organization Match Web Service
Creating Organization Match Service Ports

To create Organization Match service ports

1 Select the newly created Organization Match Web service.
3 Enter the following name: OrganizationMatchServicePort.
Appendix ■ Process for Manually Creating Organization Match Web Services
Field Value
Name OrganizationMatchService
Business Service Name DeDuplication
Field Value
Transport HTTP
Comments Organization Match Service Port
Creating Organization Match Operations

To create Organization Match operations

1 In the Service Ports view, select the OrganizationMatchServicePort.
3 Enter the following name: OrganizationMatch.
following entry:
Display Name Name
Organization Match Web Service Organization Match Web Service
Generating the WSDL



Appendix ■ Process for Manually Creating Person Match Web Services
2 Select the OrganizationMatchService from the In the Inbound Web Services screen, and click the
Generate WSDL button.
will be used.

Match Web Services
To manually create Person Match Web services for Siebel UCM, perform the following tasks:
■ “Registering the Person Match Web Service” on page 110
■ “Creating Person Match Service Ports” on page 110
■ “Creating Person Match Operations” on page 111
Registering the Person Match Web Service

To register Financial Account Cross Reference Web services

Field Value
Namespace http://siebel.com/DataQuality
Name PersonMatchService
Status Active
Comment Person Match Web Service
Creating Person Match Service Ports

This step is part of “Process for Manually Creating Person Match Web Services” on page 110.
To create Person Match service ports

1 Select the newly created Person Match Web service.
3 Enter the following name: PersonMatchServicePort.
Field Value
Name PersonMatchService
Business Service Name DeDuplication
Field Value
Transport HTTP
Comments Person Match Service Port
Creating Person Match Operations

To create Person Match operations

1 In the Service Ports view, select the PersonMatchServicePort.
3 Enter the following name: PersonMatch.
following entry:
Display Name Name
Person Match Web Service Person Match Web Service
Generating the WSDL



2 Select the PersonMatchService from the In the Inbound Web Services screen, and click the
Generate WSDL button.
will be used.

Siebel UCM and CRM Integer at Ion Guide

Caricato da

Informazioni sul documento

Descrizione originale:

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Siebel UCM and CRM Integer at Ion Guide

Caricato da

Copyright:

Formati disponibili

Siebel UCM and CRM

Siebel UCM and CRM Integration Guide 1

Chapter 1: About Siebel CRM and Siebel UCM Integration

Chapter 2: Siebel UCM Web Services

Siebel UCM and CRM Integration Guide Version 8.1 QF0009 3

Chapter 3: Siebel UCM Data Enrichment Web Services

4 Siebel UCM and CRM Integration Guide Version 8.1 QF0009

■ “Siebel CRM and Siebel UCM Integration” on page 5

■ “Scenarios for Using Siebel CRM with Siebel UCM” on page 6

■ “Scenarios for Siebel UCM Merge Operations” on page 9

Siebel CRM and Siebel UCM Integration

Business Process Description

Match Customer & Request Customer

Siebel UCM and CRM Integration Guide Version 8.1 QF0009 5

Scenarios for Using Siebel CRM with

6 Siebel UCM and CRM Integration Guide Version 8.1 QF0009

Scenario for Manually Creating a New Customer Record

Scenario for Using Match and Request Functionality to

Siebel UCM and CRM Integration Guide Version 8.1 QF0009 7

Scenario for Using Match and Request Functionality to

Scenario for Manually Creating a New Customer Record

8 Siebel UCM and CRM Integration Guide Version 8.1 QF0009

Scenario for Synchronizing Account or Customer

Scenarios for Siebel UCM Merge

Scenario for Manually Merging Two Accounts in Siebel

Siebel UCM and CRM Integration Guide Version 8.1 QF0009 9

Scenario for Sending Contact Information to Third Party

10 Siebel UCM and CRM Integration Guide Version 8.1 QF0009

■ “About UCM Web Services and Oracle CRMML” on page 11

■ “Overview of Siebel UCM Web Services” on page 12

■ “Process for Configuring Siebel UCM Web Services” on page 13

■ “Verifying Merge Publish Settings” on page 23

■ “Configuring Publish/Subscribe with Middleware” on page 24

■ “Recommended Practices for Deploying Siebel UCM Web Services” on page 25

■ “Siebel UCM Web Services Reference” on page 25

■ “Financial Account Service” on page 51

About UCM Web Services and Oracle

Siebel UCM and CRM Integration Guide Version 8.1 QF0009 11

CRMML constitutes of two parts header and body.

The header contains:

■ Information identifying the sending and receiving systems

■ A message descriptor identifying the message

The body contains one or more message elements representing:

■ Outbound response to a requested transaction

■ Outbound publication messages to be sent to an external subscribing application.

Reasons to Deprecate CRMML

■ CRMML prohibits Web Service support

■ Will align closer to Core messaging infrastructure

Overview of Siebel UCM Web Services

12 Siebel UCM and CRM Integration Guide Version 8.1 QF0009

Process for Configuring Siebel UCM Web

■ “Applying the Siebel Tools QuickFix” on page 13

■ “Additional Step for Non-ENU Setups” on page 13

■ “Importing the Seed Data” on page 13

■ “Importing the SIF files” on page 15

■ “Activating Workflows” on page 19

■ “Compiling the SRF and Restarting the Server” on page 20

■ “Registering the Siebel UCM Web Services” on page 21

Applying the Siebel Tools QuickFix

■ Apply the Siebel QuickFix, version 8.1.1 [QF0009].

Additional Step for Non-ENU Setups

To import the non-ENU symbolic strings

2 Choose the following values: