learn siebel

Optimizing Enterprise Integration Manager

Use below process to capture/find out where problem exist.

1. Turn on 'Level 8' EIM logging.
2. Turn on SQL Profiler for the run.
3. Run an EIM batch.
4. Load the EIM log into Excel. Sort the log on execution time to find what is the longest execution time. Find this event In the unsorted EIM log.
5. Load the SQL Profile trace into Excel. Sort on the longest duration, then on reads. These queries should match those in the EIM log.
6. Review the execution plans. Isolate the problem. Determine how the problem can be fixed. Keep in mind that a combination of solutions may bring about the most improvement.

Optimization TIPs.

Here are the few factors to optimize EIM performance.

• The loading strategy
• Indexes
• Turn off optimizer hints
• Fragmentation

The loading strategy: This is the one of the most important factor to load data in EIM tables. Before inserting data into EIM tables you should analyze what data is being change and how date will be updated. What base tables are updated. It’s better to separate data into batches before loading into EIM tables. Suppose you have data to insert and you have executed EIM process with default parameters. When EIM executed its check whether records exit or not if not insertion will be performed otherwise existing record will be update and this is more costly operations. Think and organize when you have heavy data to process. Divide data into batches based on operation (insert, update, delete & merge).

Index:

• Consider dropping all non-clustered indexes on the EIM_ tables. EIM performance usually improves when there is only a clustered index on the EIM_ table.
• You may be able to drop indexes on base tables and put the indexes back selectively.
• Try to optimize indexes using tools comes with your DBMS.

Turn off optimizer hints: Performance can be optimized but turning off hint optimizer. Testing should tell you if this strategy is effective or not.

Syntax:
USEINDEXHINTS,FALSE
USEESSENTIALHINTS,FALSE

Avoid updates: Ensure configuration (.IFB) file that no updates are performed (if not required).

Syntax:
INSERT ROWS=S_CONTACT,TRUE
UPDATE ROWS=S_CONTACT,FALSE

Fragmentation: During database load; data can be fragmented resulting poor performance because of more data pages must be read by SQL. To avoid fragmentation try to use index options FILLFACTOR and PAD_INDEX reduce fragmentation. The FILLFACTOR option reserves space on each leaf page of an index, while the PAD_INDEX option reserves space in the intermediate index pages.

Note: I have written above after reading technical notes from www.siebelonmicrosoft.com and EIM Administration Guide from Siebel bookshelf.

For Thick/Dedicated Client
Goto Startup >> Settings >> Control Panel >> Regional and Language Options.
Select required item and Customize.


For Thin/Web Client

Goto Sitemap >> Administration - Data >> Locale
Select required item and customize.

Query:
Changed the logo in the login page (Not Home page) SWELogin.swt web template using tools or thirdparty editor.

Placed the image in the D:\Sea78\tools\PUBLIC\ENU\IMAGES folder.

Comments:
1- Clear the cache
2- You may need to cycle the Siebel services on app servers

Query: I have pick applet(Address).When I select the record,it shows the selected address records on applet. but when i reopen the pick applet, it highlights the 1st record of the pick applet rather than my selected record. It should come up with the current record highlighted

Comments: Configured the LONG LIST Property of picklist to FALSE

Access control is the term used to describe the set of Siebel application mechanisms that control user access to data and application functionality.

Access control elements include the following:

• Application-level access control The set of screens that a user has access to are determined by the applications that your company has purchased. Each application is made of a set of available screens.
• View-level access control Within the available screens, you can control the views that areavailable to a particular user through responsibilities. A responsibility defines a collection ofviews that represent the data and functionality needed to perform a job function.
• Record-level access control You can control data records that each user can see through avariety of mechanisms, including direct record ownership by a user, being on a team working with the record, or being a member of the same organization as the record owner.

The sections that follow examine access control further:

• Parties People, entities representing people, and collections of people are unified as parties.Different party types have different access control mechanisms available.
• Data The type of data and whether the data is categorized determines which access controlmechanisms can be applied.
• Access control mechanisms Access control mechanisms you apply to parties and data determines what data a user sees.
  

Parties are categorized into the following party types: Person, Position, Organization, Household, User List, and Access Group.

Groupings of data

Customer data:

• Customer data includes contacts and transactional data such as opportunities, orders, quotes, service requests, and accounts.
• Access is controlled at the data item level, through a mechanism such as individual record ownership or ownership by an organization.

Master data:

• Master data includes the following referential data: products, literature, solutions, resolutionitems, decision issues, events, training courses, and competitors.
• Master data can be grouped into categories of similar items—for example, hard drives. Categories can then be organized into catalogs—for example, computer hardware—which arehierarchies of categories. Access can be controlled at the catalog and category levels throughaccess groups, which is the recommended strategy for controlling access to master data.
• Master data can be associated with organizations. By associating master data withorganizations, access can be controlled at the data item level. This strategy requires more administration than the access group strategy.

Other data

• Other data includes referential data that is not master data, such as price lists, cost lists, rate lists, and SmartScripts.
• Access is controlled at the data item level.

Access Control Mechanisms

• Personal access control.
• Position access control. This includes single-position, team, and manager access control.