How to Drop and Generate Triggers in Siebel

If there are changes to a Workflow policy, you might be asked to either 'Generate' the triggers or 'Recreate' them for the changes to take effect. This task can be accomplished in two ways, one through the Siebel Application and the other via Server Manager command line.

The main parameter to consider to Generate or Drop the triggers is 'Remove' which can be set to TRUE or FALSE depending upon the purpose.

Server Manager Commands:

1. Drop Triggers
run task for comp GenTrig with EXEC=True,Remove=True,PrivUser=SIEBEL,PrivUserPass=<siebelpassword>

2. Generate Triggers
run task for comp GenTrig with EXEC=True,Remove=False,PrivUser=SIEBEL,PrivUserPass=<siebelpassword>



Siebel Application:

Login to the Siebel application and navigate to the 'Administration - Server Management' and then 'Jobs'.
Create a new job 'Generate Triggers' and add the parameters as shown:

Change the parameter value of 'Remove' to 'True' if you want to drop the triggers. The ideal sequence for re-creating the triggers is to drop them first and then create. So you would have to run the job with the 'Remove' parameter set to 'True' first and then run the job again with the parameter set to 'False'.

You can also include additional logging parameters like 'ErrorFlags', 'SQLFlags','TraceFlags' etc for capturing additional information in the logs.

Oracle bookshelf link related to this topic:

http://docs.oracle.com/cd/E14004_01/books/BPFWorkflow/administering_policies4.html

Thanks,
Shyam

Raising log levels for SWSE - Siebel Web Server Extension

NOTE: Starting in Siebel version 7.7.x, the Log parameter in the eapps.cfg file is no longer used by the SWSE. You only need to set the environment variables documented below to trace the SWSE connections. Bug <strong< a="">12-JP45TC>> has been logged to address the documentation defect to request the Log parameter be removed from the eapps.cfg file. This parameter has been removed from the Siebel Bookshelf starting with Siebel version 7.7.</strong<>


To troubleshoot further, the logging can be increased to include Siebel Internet Session API (SISNAPI) and Session Manager tracing. The following information details how to turn up logging for the SWSE on the Microsoft Windows and UNIX Operating Systems to include SISNAPI and Session Manager Information.

Be aware that by increasing the logging levels on the Web Server, this may cause performance degradation, the extent of which will depend on your specific implementation (mostly this is insignificant). Additionally, increasing the logging levels will require more available disk space in the SIEBEL_HOME\SWEApp\LOG directory as the log files will be bigger. It is always a good practice to test out these settings in your test environment first and then move these settings to production only if specifically requested by Siebel Technical Support. Once the behavior has been resolved, it is a good practice to unset the environment variables and reset the default logging for the SWSE in the production environment.


For Windows Environments

Perform the following steps to enable tracing for the SWSE:

1. Set the following System Environment Variables:

SIEBEL_LOG_EVENTS=4 (or higher)
SIEBEL_SESSMGR_TRACE=1
SIEBEL_SISNAPI_TRACE=1

To set up environment variables perform the following steps:

o Start > Settings > Control Panel > System.

o Click on the Advanced tab and then click on the Environment Variables button.

o Under the System variables view, click the New button and add the variable names and values mentioned above. Click the Ok button when finished.

2. In the eapps.cfg file located on the web server machine under the directory SIEBEL_HOME\SWEApp\BIN folder, make the following changes under the [swe] section:

Log = details (only for 7.5.3 or earlier)
SessionMonitor = TRUE

3. Restart the IIS Admin Service and its dependent services for the changes to take effect. NOTE: The inetinfo.exe process has to be restarted for the new environment variables to take effect.

NOTE: If SWSE is installed on a Windows 2003 Server, it is necessary to reboot the machine otherwise logging will not be enabled.

For a UNIX Environment except Linux

Perform the following steps to enable tracing for the SWSE:

1. Set the following environment variables:

SIEBEL_LOG_EVENTS=4 (or higher)
SIEBEL_SESSMGR_TRACE=1
SIEBEL_SISNAPI_TRACE=1

To set up environment variables for the user who starts the web server, perform the following steps (for Bourne and Korn Shell):

$ =value; export

For example:

$ SIEBEL_LOG_EVENTS=4; export SIEBEL_LOG_EVENTS

2. In the eapps.cfg file found on the web server machine under SIEBEL_ROOT/sweapps/bin folder make the following changes:

Under the [swe] section:

Log = details (only for 7.5.3 or earlier)
SessionMonitor = TRUE

3. Restart the web server process for the changes to take effect.

For Linux Environment
For increasing the logging for SWSE when using Oracle HTTP Server (OHS) add the environment variables to a file named envvars under ohs/bin directory.

envvars-std - default environment variables for apachectl
#

This file is generated from envvars-std.in
#
LD_LIBRARY_PATH=
export LD_LIBRARY_PATH

SIEBEL_SESSMGR_TRACE=1
SIEBEL_SISNAPI_TRACE=1
SIEBEL_LOG_EVENTS=5

export SIEBEL_SESSMGR_TRACE
export SIEBEL_SISNAPI_TRACE
export SIEBEL_LOG_EVENTS
To Reverse the Default Logging Levels on the Web Server

1. Remove all three environment variable settings.
2. In the eapps.cfg file set Log = errors (only for 7.5.3 or earlier).
3. Restart the web server processes.

NOTE: For information about unsetting the environment variables, see the appropriate operating system documentation.

Siebel Database upgrade from 8.1.1.0 to 8.1.1.11 Fails - upgrep

Environment:
OS - Windows 2012
Siebel - 8.1.1.11 SIA
Upgrading from - 8.1.1.0 SEA
Database - Oracle 11.2.0.3

Issue:
While running the 'upgrep' process in the Database configuration for the upgrade from 8.1.1.0 SEA to 8.1.1.11 SIA, the process fails at step 27 with the following error:

[Item 27]
Status = Error
Item Name = File Execute Entry 26
SecondaryLanUpgrade = 3611514Unable to get schema version.Please verify that you have specified the correct Table Owner (siebel) and you have select access to the S_APP_VER table.

Upon checking the database permissions, everything looked okay and the user SIEBEL did have all the needed privileges on the table.

Solution:
The workaround is to replace the number in the master_upgrep_dev_81110 file by the installed languages :

Repeat For Language = 3611519
replace with
Repeat For Language = DEU,ENU for example.

If  the unique language installed is ENU:
Repeat For Language = ENU

Re-execute the upgrade wizard from siebsrvr/bin/master_*.ucf file.

This is a known product bug documented in 'Bug 18614385 - DATABASE CONFIGURATION WIZARD FAILS BECAUSE OF INCORRECT LANGUAGE 0ENU'

Oracle support document reference - 1668300.1

Unable to Configure Enterprise Siebel 8.1.1.0 64-bit - SES/OUI Installer

Environment

OS - Windows 2008 R2 64-bit

Siebel version - 8.1.1.0

I was trying to setup a Siebel 8.1.1.0 environment on Windows 2008 R2 (64-bit) server and the Siebel Enterprise configuration was failing each time while attempting to connect to the Gateway Name server. The software for the setup was downloaded from Oracle e-Delivery and looking up Siebel 64-bit installer for Windows.

The software that is available currently in eDelivery is the SES or OUI (Oracle Universal Installer) type of installer which has been in place since OpenUI was introduced. The previous version of the Siebel installer for the base 8.1.1.0 version was the InstallSheild one which I had successfully installed on many Windows 2008 servers. 

Upon further investigation with running the installer in verbose mode, it is found that many files are missing from the gtwysrvr\bin directory (eg, commonutil) which is breaking the configuration process. It has been confirmed by Oracle that the SES or OUI version of the Siebel 8.1.1.0 (base) installer is not supported as a standalone installer for Siebel anymore. If you need to setup the OUI installer, it has to be patched to a version 8.1.1.8 or higher before starting the Enterprise Configuration.

Solution:

Login to Oracle support (support.oracle.com) with your credentials and search for the patch number '15892740'. Download the required version of software depending upon your OS, this is the Install Shield version of Siebel 8.1.1.0 Base version which needs to be installed in case you are setting up a Base standalone environment.

IBM LDAP Client 6.0 Installation for Siebel on Linux - Part 2

Continuing the install screens from Part 1:








 

Once the installation is complete, navigate to the IBM LDAP client installed directory which will be '/opt/ibm/ldap' and check for the files created within the folder

Once the contents of the folder are verified, you should be all set!

Thanks,
Shyam Varma