Siebel And Its Integrations

How many 'Products' or 'Applications' (Internal or 3rd Party), you know which could be integrated with Siebel Application. I Hope to see your comments. It would be great if you share some knowledge on -

1. How the specific Product or Application you might be suggesting could be integrated (Out-Of-Box, Inbuilt API's, 3rd parth integration techniques etc)?

2. What all 'Applications' or 'Products' you wish see, integrated with forecomming releases of Siebel?

3. Why you want the 'Applications' or 'Products' mentioned in Point# 2 should be integrated with Siebel?

How CTI work?

Well, most of us might have heard of this three alphabet word "CTI". What does it means and how is it intergrated with Siebel application? Lets share our thoughts.

: CTI stands for "Customer Telephoney Integration". Basically, most of the companies which carters services to their customers use this product integrated with siebel call center application to make/recieve calls.

CTI+Siebel involves a mix of infrastructure and archichecture planning requirments.

The general architecture is as shown below:

Communication Server - CTI flow:

Why not move to BI Publisher?

Its very much clear that oracle already expressed its intention of moving all its report from Actuate to BI Publisher.

 

Siebel 8.1.1 has already inhoused BI publisher solution which you could get integrated with this package.

 

Few things that comes to my mind:

 

1. What will happen to the customers who are on old versions of Siebel (say 7.5, 7.7, 7.8 etc) and not planning to upgrade?

 

   <Arun>: I haven't heard of BIP integrating with 7.x right now (may be I don't have that information,keep finding and post here), I think they can continue with the existing version of Actuate (but Siebel is not going to provide any support).

 

2. What will happen to existing Actuate report for the customer who are planing to upgrade siebel to 8.x?

 

   <Arun>:  If customer upgrading to 8.x, there is a converion strategy devloped by oracle for moving all Actuate report to BIP. So, no worries.  get your TAM involved for further discussions.

 

3. Don't know much about Siebel BIP.  Where should I get information from?

 

   <Arun>:  Hey, METALINK is there. Brushup your Grey Cells

 

 

Let me know if you have any questions. I could be reached at arunhudiya@in.com

Oracle CBO and Siebel Business Applications

Summary

 

A query optimizer determines the best Execution Path for performing each query. The Oracle Rule Based Optimization (RBO) method chooses its plans based on a set of fixed rules. While the Cost Based Optimization method leverages a costing model based on statistics, which evaluates all of the different access and join methods for the specific query and uses the most efficient one.

 

RBO enumerates a deterministic, ordered (fixed rank) set of plans based on a pre-defined set of rules and always picks the first applicable plan in the order. For example, if you have a query of the form:

 

SELECT * from EMP where EMPNO > 50

 

and if there is an index on column EMPNO, then one of the RBO's rules specifies that this query will always be executed using the index. The behavior of the RBO is entirely fixed; the execution plan for the sample query remains the same regardless of whether the EMP table has 10 rows or 10 million rows, and regardless of whether the "EMPNO > 50" predicate will return 2 rows or 2 million rows.

 

On the other hand, the cost-based optimization strategy generates multiple execution plans for a given query, with each having an estimated cost computed for each plan. The query optimizer chooses the plan with the most efficient cost (for example, the highest performance and lowest cost). The CBO requires accurate statistics in order to deliver good query performance. Hence, it is crucial that the statistics the CBO uses are available and accurately maintained.

 

 

Preparing and Administrating the Siebel Database for CBO

 

When using Oracle's Cost Based Optimization with the Siebel database, there are some requirements that should be followed regarding the database parameters configuration and the Optimizer statistics generation on tables, columns and indexes, as specified below:

 

Database Parameters

 

Oracle Parameter	9i Default Value	10g Default Value
HASH_JOIN_ENABLED	True	** Obsolete
OPTIMIZER_FEATURES_ENABLE	9.2.0	10.1.0 *
OPTIMIZER_INDEX_CACHING	0	0
OPTIMIZER_MODE	CHOOSE	ALL_ROWS
PARTITION_VIEW_ENABLED	False	** Obsolete
QUERY_REWRITE_INTEGRITY	Enforced	Enforced
STAR_TRANSFORMATION_ENABLED	False	False

 

In addition, for the Siebel application to work effectively and efficiently, the following parameters need to be set to the recommended values other than default values.

 

Oracle Parameter	Description	9i Default Value	10g Default Value	Recommended Value
OPTIMIZER_DYNAMIC_SAMPLING	This parameter controls the level of dynamic sampling performed by the optimizer.	1	2	1
OPTIMIZER_MAX_PERMUTATIONS	This parameter restricts the number of permutations of the tables the optimizer will consider in queries with joins. A higher value result in higher parse time, a lower value carries the risk of overlooking a good plan.   NOTE: Starting with Oracle Database 10g, this parameter has been made obsolete. Refer to the Oracle documentation for further information.	2000	** Obsolete	100
OPTIMIZER_INDEX_COST_ADJ	Controls the access path selection to be more or less index friendly.	100	100	1
QUERY_REWRITE_ENABLED	Enable or disable query rewriting globally for the database	False	True	False

 

Remember - More details could be found on Oracle Metalink.

Need advice - poor performance - customer is upgrading to 7.8.2.11, running on 10g

My customer is upgrading to 7.8.2.11, running on 10g. They are experiencing some poor performance. When researching this for them I came upon the statement below. Does this mean that these are the recommended settings? They currently have _b_tree_bitmap_plans=TRUE. I am going to need some basis for suggesting this change if it is indeed the recommended setting.

Thanks

Julie

For better performance in Siebel versions 7.8 and 8.0 connecting to Oracle 10.1.x or 10.2.x, with optimizer mode set as CBO, it has been observed that SQL query performance is satisfactory with the following two parameter settings in the init.ora file:

• _b_tree_bitmap_plans = FALSE

• _no_or_expansion = FALSE

Dear arunhudiya.siebelspecialist! Get Yourself a cool, short @in.com Email ID now!