Full Compile Sequence in Siebel Tools

Today I was waiting impatiently for the full compile to finish...

So I just took a note of the sequence in which compile happens

this is the observation;I just noted major milestone objects and left out others ;)

Compile Sequence
Tables --> Applet --> Link --> Business Component --> Screen ---> Setting Up Application --> Closing SRF

Verifying Classpath in Siebel

It has been observerd that lot of time is spent in issues related to troubleshooting classpath issues.

After configuring the classpath values open the Business service Simulator and use the 'EAI JMS

Transport'


There are a couple of handy methods in this Business Service.

eg: method : CheckClasspath


On running this  you get an ouput telling the result.

<?xml version="1.0" encoding="UTF-8" ?>

  <?Siebel-Property-Set EscapeNames="true"?>

  <PropertySet>Input property set: > Value = > Type = > SendPassword = > ConnectionPassword = > CommitTransaction = true > ReceiveUsername = > TopicUsername = > PreserveString = true > ConnectionUsername = > ConnectionFactory = > ReceivePassword = > TopicPassword = > SendUsername = java.class.path = /u01/app/siebel/jms:/u01/app/siebel/jms/Siebel.jar:/u01/app/siebel/jms/SiebelJI_enu.jar:/u01/app/siebel/jms/jndi.jar:/u01/app/siebel/jms/adminclient.jar:/u01/app/siebel/jms/bcel.jar:/u01/app/siebel/jms/dms.jar:/u01/app/siebel/jms/ejb.jar:/u01/app/siebel/jms/jms.jar:/u01/app/siebel/jms/optic.jar:/u01/app/siebel/jms/pcl.jar:/u01/app/siebel/jms/oc4jclient.jar:/u01/app/siebel/jms/javax77.jar:/u01/app/siebel/jms/ojdbc14dms.jar:/u01/app/siebel/jms/mail.jar:/u01/app/siebel/jms/jta.jar:. Found directory /u01/app/siebel/jms NOTE: A jndi.properties file is present in /u01/app/siebel/jms Found jar file /u01/app/siebel/jms/Siebel.jar with 638 entries. Found jar file /u01/app/siebel/jms/SiebelJI_enu.jar with 25 entries. Found jar file /u01/app/siebel/jms/jndi.jar with 123 entries. Found jar file /u01/app/siebel/jms/adminclient.jar with 1307 entries. Found jar file /u01/app/siebel/jms/bcel.jar with 399 entries. Found jar file /u01/app/siebel/jms/dms.jar with 192 entries. Found jar file /u01/app/siebel/jms/ejb.jar with 37 entries. Found jar file /u01/app/siebel/jms/jms.jar with 61 entries. Found jar file /u01/app/siebel/jms/optic.jar with 32 entries. Found jar file /u01/app/siebel/jms/pcl.jar with 270 entries. Found jar file /u01/app/siebel/jms/oc4jclient.jar with 850 entries. Found jar file /u01/app/siebel/jms/javax77.jar with 39 entries. Found jar file /u01/app/siebel/jms/ojdbc14dms.jar with 638 entries. Found jar file /u01/app/siebel/jms/mail.jar with 259 entries. Found jar file /u01/app/siebel/jms/jta.jar with 20 entries. Found directory /u01/app/siebel/siebsrvr/bin/. SUCCESSFUL TEST</PropertySet>

Cleaning the File System in Siebel

During normal operation of Siebel Business Applications software, it is likely that orphaned files will be stored in the Siebel File System and that orphaned records will exist in the Siebel Database.

Here comes in the handy SFS cleanup utility.....

Periodically run the SFSCLEANUP utility to remove orphaned files from the Siebel File System. This utility is located in the bin subdirectory within the Siebel Server root directory.

Run this and be a best practice compliant and responsible siebel  consultant :)

Cheers

Fix C028: “Unable to Connect to the Siebel Gateway Name Server”

Symptoms

The Server Configuration wizard has logged the following error message:

C028: Unable to Connect to the Siebel Gateway Name Server

Cause

Database Authentication failed.

Gateway authentication is a new feature in Siebel 8.1.1.  If the Configuration Wizard fails due to authentication it will log the error messages, above.

Solution

Follow these steps to resolve the issue:

1. In the ‘$SIEBEL_ROOT/gtwysrvr/siebenv.sh’ environment sourcing script, check the following environment variables and  set them appropriately before starting the Gateway server.

1a. For all servers: ORACLE_HOME must be declared before any library paths are declared.
Example:

ORACLE_HOME=/export/home/ora10g/10203 ; export ORACLE_HOME

1b. NOTE: For the following library paths, Oracle 32-bit libraries must be referenced before 64-bit libraries. An example is provided for each library path per Unix system, as follows:

For AIX: LIBPATH

LIBPATH=${SIEBEL_ROOT}/lib:${MWHOME}/lib:${SQLANY}/lib:/usr/lib:${LIBPATH}:${ORACLE_HOME}/lib32:${ORACLE_HOME}/lib

For HP-UX:  SHLIB_PATH

SHLIB_PATH=/usr/lib/hpux32:${SIEBEL_ROOT}/lib:${MWHOME}/lib:${SQLANY}/lib:${ORACLE_HOME}/lib32:${ORACLE_HOME}/lib

For Linux and Solaris:  LD_LIBRARY_PATH

LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${ORACLE_HOME}/lib32:
${ORACLE_HOME}/lib

2. Open the ‘gateway.cfg’ file, which is located in the ‘$SIEBEL_ROOT/gtwysrvr/bin’ directory.
Check the ‘ServerDataSrc’ section and confirm the parameters are correct, particularly:

ConnectString
TableOwner
GatewayAddress
EntepriseServer

3. Test Siebel database connectivity using the Oracle odbcsql utility for the ‘sadmin’ user.  This is typically located in the ‘$IEBEL_ROOT/siebsrvr/bin’ directory.

For example:

odbcsql /s sia811_DSN /u sadmin /p sadmin

where:

/s = the source ODBC DSN (the Siebel ConnectString parameter) for the database connection.
/u = the user ID.
/p = the password.

If connection is possible, continue with step 4.

4. Restart the Gateway server, and then try configuring the Siebel Server.

Hope that helps !!!! have a nice day

Measuring the performance of Workflows in Siebel

You can get performance tracing of workflows by setting the event WfPerf for the component in which your workflow is running.

Setting the event to level 4 gives timing for the execution of the overall process.

Setting the event to level 5 provides timing for each step as well.

You can set this event level for any Siebel Server component that invokes a workflow process as part of Siebel eAI functionality. For example, to set this event level for the MQ Receiver using srvmgr, enter the following:

change evtloglvl WfPerf=5 for comp MqSeriesSrvRcvr

These events can be useful not just for measuring workflow performance but also for measuring the performance of business services executed within these workflows.

Hope this helps!!!!!

How to stop a Workflow Process Instance via eScript

This can be achieved using the  _StopInstance method of Worflow Process Manager BS

An example usage of this technique occurs when you have an interactive workflow which needs to be cancelled but which is suspended in a Wait step. In this scenario, the Process Instance Id is already known.

To stop a workflow process instance from script

Invoke the _StopInstance method on the Workflow Process Manager business service, as in the following example, which uses a hard-coded Process Instance Id:

var bs = TheApplication().GetService("Workflow Process Manager");

var ps_inputs = TheApplication().NewPropertySet();

var ps_outputs = TheApplication().NewPropertySet();

ps_inputs.SetProperty("ProcessInstanceId", "1-IIT");

bs.InvokeMethod("_StopInstance" , ps_inputs, ps_outputs);

Comes in handy while you want to dliberately stop that annoying instance:)

Playing with the SOUNDEX function

Hi All

Have you ever tried the SOUNDEX function for finding phonetically similar words such as querying First Name you vaguely remeber.I read about this in Alex's Siebel Essentials and after a bit of trial/POC I am writing this post.

So I typed in this query and ....

 








got the following results

so here we can see that the soundex value for all the results are same.

The Soundex algorithm is as follows:

1.The soundex return value will always begin with the first letter of string.'P' in our case.

2.The soundex function uses only the first 5 consonants to determine the NUMERIC portion of the return value, except if the first letter of string is a vowel.

3.The soundex function is not case-sensitive. What this means is that both uppercase and lowercase characters will generate the same soundex return value.

Applies to :Oracle 8i, Oracle 9i, Oracle 10g, Oracle 11g

Have a nice day ahead.....