Siebel EIM – USING SYNONYMS
Performance is always a major issue in most of the Siebel Intallations. In a project where large scale EIM Processing is needed, rest assured, Performance would be the from amongst the most discussed topics, at least from the Acceptance Testing phase, if not before!
EIM Data loads can turn out to be for millions of records, and many tens of GBs of Data being imported is a common sight (talking in terms of the Oracle Database Data File footprint). The customer has to be around that size, if he is actually going in for a Siebel CRM implementation I guess!
Siebel Server Verification – EVT Tool
Verifying the health of our Siebel Server Environment is the primary concern of any sane Project Manager to have spent such large sums of money in setting it up in the first place. We have already introduced a couple of very useful tools to analyse performance and other bottlenecks in the past. Here, I will try to cover one of the prominent tools used extensively in the process.
It is called the Siebel EVT Tool, or the Environment Verification Tool in Siebel. It helps Siebel Administrators verify the configuration, of Siebel Business Environment. Errors and Potential problems in a Siebel Implementation can readily be found out through this tool.
Siebel – EAI Siebel Adapter – Looping Multiple Records
This is a follow-up post on the post, Siebel – Looping Multiple Records – III. We are looking at possibly more conventional methods to loop through multiple records in Siebel, than the SIA BC Utility Service.
We will make use of EAI Siebel Adapter’s QueryPage method to achieve the same. Knowledge of Siebel Workflow processes is essential to understanding this post.
The QueryPage method allows us to input an additional parameter, NumOutputObjects, to define the number of records that we want to output. Why not set this value to ‘1′?
Following is an outline of the Dummy Workflow I used to achieve this.
netstat command
Hi all,
All of us have faced huge performance related issues. When it comes to Siebel, things can only be called murky! The OOB solution itself puts up a few questions. I say this as per my naive understanding and experience
Siebel – EAI Queue – a Critique’
I had introduced the Siebel EAI Queue and its usage in my last articles. Though Siebel EAI Queue is a very good Siebel feature, there are some serious shortcomings as well. An architect would, thus, need to critically evaluate all the pros and cons before deciding to implement the OOB EAI Queue or a custom solution in a Siebel EAI project.
First let’s look at all the areas where Siebel EAI Queues stand strong.
1) No customisation needed
This is an OOB fucntionality. So, no custom coding is necessary. The vanilla BS can directly be called from the WF to help operate the EAI Queues. Custom code comes with its own sets of problems – dedicated human resources, architecting, implementing, testing, debugging, performance, scalability, expandability, robustness.
Siebel Assets List view – Performance issue / Cannot display records
Assets Screen Load is a major problem in Siebel, and a major pain area for the concerned developer. I am sure many of you would have come across it in one implementation or the other.
If there are more than 10,000 records in Assets screen, vanilla Siebel Application will not load the screen.