Tracing Inputs and Outputs to the Siebel Configurator API via Sniffer Code to Assist Debugging
(Doc ID 2037936.1)
Last updated on JUNE 03, 2018
Applies to:Siebel eConfigurator - Version 7.8  and later
Information in this document applies to any platform.
Area(s):eConfigurator / Siebel Product Configurator
Database(s):All Supported Databases
App Server OS(s):All Supported Platforms
Latest release tested against:V7 (Enterprise)
The eConfigurator API methods are a set of well-defined and exposed methods that provide the ability to use the eConfigurator and manipulate or validate a configuration session without using the customizable runtime UI. They are methods of the business service 'Complex Object Instance Service' and 'Remote Complex Object Instance Service' and are used extensively by other services (Configurator UI services) within the Siebel application. They can be accessed by external applications or via script
There can be times when it is necessary to trace the inputs and outputs to the methods to understand why the calls are performing as they are, or to understand what calls you need to make in script to automate a process i.e. add an attribute to a customizable product. This document discusses the implementation of sniffer code to provide this information and how to test to see the results.
Please note that this document is focused on eConfigurator but the technique can be used with any business service to trace inputs/outputs.
This document is informational and intended for any user.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document