Most of what Germain monitors for Siebel is preconfigured. We recommend fine tuning every monitoring features that Germain is preconfigured for, to make it a perfect fit to your environments and needs.
Errors Seen by Siebel Users (Automated analysis)
Build a list of Siebel User Errors to watch out for
Germain UX allows to map all Siebel custom error codes to their corresponding display messages visible to your end users. To configure this mapping please follow the below steps:
Extract all of your Siebel Error codes using
errmsg.exeSiebel’s utility (available only on Windows platforms). Siebel keeps these codes in the resource catalogs (core.cat, apps.cat, vsia.cat, inst.cat, …) in the %SIEBEL_ROOT%\bin\%language_folder%. Example below shows how to extract these codes from Siebel resource catalog in English language format:CODE
%SIEBEL_ROOT%\bin\errmsg.exe /l ENU enu\core.cat > errors.txt
errors.txtoutput file and find all of your custom errors, e.g.CODE
... SBL-GEN-02011 Error parsing Siebel message file header: incorrect facility name ...
Once all custom error code extracted from the
errors.txtfile, insert them into
SIEBEL_ERROR_CODE_MAPPINGtable available in your Germain UX Datastore. Example below for MySQL database:
INSERT INTO SIEBEL_ERROR_CODE_MAPPING (CODE,MESSAGE) VALUES ('SBL-GEN-02011','Error parsing Siebel message file header: incorrect facility name');
Crashes of Siebel Object Manager (Automated Analysis)
Exclude Siebel Components from Monitoring
You will not always be using all components available to you in Siebel, so you may need to exclude some from monitoring.
To exclude Siebel components we will need to create a reference called “ExcludedComponents” on the monitor.
Go to you monitor and click the to the right of “References”
Enter the name as “ExcludedComponents” and enter the names of the components is a comma seperated list as you see below.
Feature Availability: 8.6.0 or later