6Troubleshooting the Integration

Troubleshooting the Integration

This chapter provides information on troubleshooting Siebel CRM Integration to Oracle FLEXCUBE Universal Banking. It contains the following topics:

Siebel CRM Log Files

Within the Siebel CRM environment, logging information is written to log files which can be used to troubleshoot problems. The following log files are available:

  • Siebel Server log files

  • Siebel Web server extension log files

  • Siebel events and event logging files

For information on the log files generated by Siebel CRM, see Siebel System Monitoring and Diagnostics Guide.

How Siebel CRM Handles Errors During Online Data Synchronization

This topic describes how Siebel CRM handles errors that occur during online data synchronization. During online data synchronization, in the event of an error, one of the following occurs:

  • Error messages are written to a log file.

  • Error messages are sent to Oracle FLEXCUBE Universal Banking.

  • Error messages are displayed on the user interface.

The error-handling mechanism that is used depends on the type of Siebel Web service that generates the error, as described in the following table.

Web Service Type Operation Error Handling Mechanism

Synchronous

Inbound Create or Query

The error message in the EBM format is transformed using the EAI XSLT Service and is sent to Oracle FLEXCUBE Universal Banking.

Synchronous

Outbound Query

The error message is retrieved from the response message using the FINS Industry XML Query Service, and is displayed to the user.

Fire-and-forget

Outbound Update

If a workflow failure occurs, then the Siebel Server logs the error message.

Fire-and-forget

Inbound Create or Update

An error message is written to a file using the EAI XML Write to File service. For additional information, see Online Data Synchronization Log Files.

    Online Data Synchronization Log Files

    Log files specific to the online data synchronization process are created if errors occur when inbound fire-and-forget Web services trigger create or update operations. Error messages are written to the files in the siebsrvr\log\ directory where siebsrvr is the Siebel Server installation directory. The name of the log file takes the following format:

    		MessageId EBMShortName Operation.xml
    

    where

    • MessageId is the numeric message identifier

    • EBMShortName is the abbreviation for the EBM

    • Operation is either Create or Update

    For example:

    		9110970000009273DAUpdate.XML
    

    The following table shows the log files created for each integration object if errors occur during create and update operations.

    Integration Object Integration Object Short Name Log File Name of Fire-and-Forget Service

    Deposit Account

    DA

    MessageIdDAUpdate.XML

    MessageIdDACreate.XML

    Loan Account

    LA

    MessageIdLAUpdate.XML

    MessageIdLACreate.XML

    Customer Interaction (Activity)

    CI

    MessageIdCICreate.XML

    Sales Opportunity (Lead)

    SO

    MessageIdSOCreate.XML

    Service Request

    SR

    MessageIdSRUpdate.XML

    Customer Party

    CP

    MessageIdCPUpdate.XML

      Siebel Log Files During Batch Data Loading

      This topic provides information on the Siebel log files generated during batch data loading using Oracle Data Integrator. After performing the batch data loading, check the following log files for errors:

      • Log table BIB_ODI_ERROR_LOG

        If an error occurs while running the packages for the batch data loads, then the error message is logged in the table BIB_ODI_ERROR_LOG in the Siebel database. This table stores the following information about the error:

        • Package name

        • Step name

        • Step type

        • Error code

        • Error message

        • Created date

      • EIM log files

        During the batch data loading, Oracle Data Integrator loads data from Oracle FLEXCUBE Universal Banking staging tables into Siebel EIM tables. Oracle Data Integrator starts the Siebel EIM jobs, using the Siebel Server Manager utility. If an error occurs in a Siebel EIM job, then a log file is created in the location you specified for the variable FINS_BIB_Log_Path. For additional information, see Configuring Integration Variables.

        Check the log files for any errors during the Siebel EIM job processing.

      Errors Generated by Oracle FLEXCUBE Universal Banking

      For information on troubleshooting online data integration errors that result from problems with the way in which the EBO Direct Build Utility was configured, see the FCUBS EBO Direct Build Utility User Guide, which is provided as part of the Oracle FLEXCUBE Universal Banking documentation set.