The best way to log traffic between Siebel and EDQ is to enable logging in the EDQ Siebel Connector and then examine the connector log files. You will then see requests and responses here - it is the best place as it will work across several EDQ servers if you have many in use.
See Section 4, item 3 in this document:
3. (Optional) If detailed trace information on connector requests is required (for example, for temporary debugging purposes) add the following lines to the
dnd.parmsfile to enable logging:
logfile: sdq%05d.log jlogfile: jsdq%05d.log "
It is also possible to enable logging by writing data out of EDQ itself, for example to append to a text file the data sent into match by adding a writer just before the match processor and configuring an export task to a text file in append mode, but this is server specific and less easy to disable later.
We set up the users in EDQ and gave them access to the projects with the webservices (the CDS project in this instance). We gave the user the permissions specified in the "Customer Data Services Pack siebel integration Guide (E40741-02)":
- System: Connect to Messaging System
- Server Console: Execute Job
- Director: Execute Job
Hope this helps
Thanks for the update.
I checked the link you sent me for setting up user permissions.
I was able to locate where the permissions are set for EDQ project mentioned in the document.
Where do i have to set the permissions for
System: Connect to Messaging Systems
Server Conse: Execute Job
Director : Execute Job
Could you please help me with the navigation path