Data Quality Guide for Oracle Customer Hub > Universal Connector API >

Session Initialization and Termination Functions


The Siebel Server works in multi-threaded mode to serve multiple users. To allow for user and invocation-specific parameters, there is the concept of a session context where such values can be stored. The session ID is supplied for all data matching or data cleansing functions. Upon completion of data cleansing or data matching the session is closed.

This topic describes the functions that are used for session initialization and termination:

sdq_init_session Function

This function is called when the current session is initialized. This allows the vendor to initialize the parameters of a session or perform any other initialization tasks required.

Syntax

int sdq_init_session (int * session_id)

Parameters

session_id: A unique value provided by the vendor that is used in function calls while the session is active. The value 0 is reserved as an invalid session ID. The Siebel CRM code calls this function with a session ID of 0, so the session ID must be initialized to a nonzero value.

Return Value

A return value of 0 indicates successful execution. Any other value is a vendor error code. The error message details from the vendor are obtained by calling the sdq_get_error_message function.

sdq_close_session Function

This function is called when a particular data cleansing or data matching operation is finished and it is required to close the session. Any necessary cleanup tasks are performed.

Syntax

int sdq_close_session (int * session_id)

Parameters

session_id: The session ID obtained by initializing the session.

Return Value

A return value of 0 indicates successful execution. Any other value is a vendor error code. The error message details from the vendor are obtained by calling the sdq_get_error_message function.

Data Quality Guide for Oracle Customer Hub Copyright © 2018, Oracle and/or its affiliates. All rights reserved. Legal Notices.