Summary of Siebel Architecture Best Practices

5/30/2016 1 Comment

Siebel Administration and Architecture Best Practices Summary

We have discussed in detail before about the best practices to be followed by a Siebel Administrator for optimal performance of a Siebel application. Here we are presenting a summary if the client , application server, gateway server and database server best practices.

Client Best Practices

Functional Testing
Test the application using every type of client that is expected to access it.

Performance Testing
Include the client environment in performance tests and establish configuration requirements for the client environment as part of benchmark testing.

Select the appropriate client
Ensure that the appropriate client is selected for deployment based upon requirements, both in terms of functionality and performance.

Set Expectations
When preparing to deploy the Siebel eBusiness application, ensure the user community understands the functionality delivered by the chosen client(s).

Use performance benchmark testing to understand the network requirements of the customized Siebel eBusiness application.When designing the application, ensure that the design caters for the differing likely network connection quality depending on the channel being used.

Gateway Server Best Practices

High Availability
Employ a high-availability solution for the Name server to provide a failover in the event this component fails.

Ensure that the Name server files are part of the regular system back strategy.

When a clustered Name server is utilised, the Resonate Central Dispatch schedulers must be installed onto different machines. Use dedicated scheduler machines when the user community is to exceed 1,000 concurrent users.

Scheduling Rules
Always preserve the supplied scheduling rules in order to facilitate an easy recovery should an error be made. Adjust the scheduling rules carefully and in a controlled and orderly fashion, making small incremental adjustments.

Benchmark Testing
Deployments of many thousands of users, either concurrent or in total should be benchmark tested to ensure the hardware resources for the scheduler service is adequate.

Application Server Best Practices

High Availability
Use load balancing to achieve high availability of those components that support load balancing. Use hardware cluster solutions for those servers hosting components that are not load balance enabled.

Resonate Central Dispatch
Include resonate Central Dispatch if it is likely to be needed in the future, regardless of whether load balancing is required from inception.

Ensure the SRF, CFG and application specific files are secured in such a way that they can easily be reinstated should they be lost or corrupted.The directories that are used to support Siebel Remote should be held on a resilient disk array, such as RAID-5, in addition to being secured by backup.

Benchmark Testing
It is essential to conduct performance and scalability testing of all components, including the client environment and network.

Regression Testing
Test a number of scenarios that will give rise to errors. Use results of these errors and the accompanying log files as a knowledge base to assist support personnel.

Since the volume of data can be very high, it is recommended to run production servers with minimal logging and only increase the logging level if problems are encountered.

Capacity Planning
It is recommended to continually or at least periodically monitor the resource usage of the Siebel Application server.

Automation and Procedures
Ensure that the regular maintenance and administration tasks are automated through scripts and that fully tested procedures are in place.

Database Server Best Practices

Ongoing regular maintenance
Establish maintenance windows to provide for conducting regular maintenance of the database.

Performance testing & tuning
Conduct the testing and necessary tuning effort on a database instance that is representative of the production volume, especially data volumes and distribution.

Resource and database monitoring
Establish procedures and solutions for the ongoing monitoring of the database and the database server, including response times.

Backup strategy
Prior to going into production, establish the backup strategy and solution for the database.

Scalable platform
Ensure a scalable solution is employed for the database solution.

Control data model
Maintain control of the Siebel data model and consider carefully any changes.
Review the chapter “Adding Custom Extensions to the Data Model” in the Siebel Tools Reference document within Siebel Bookshelf before embarking on any changes to the data model.


When implementing Siebel eBusiness applications, there are a number of aspects and best practices that should be considered with reference to the architecture. This document has presented many of the recommendations and best practices that are generally applicable to a Siebel eBusiness Enterprise architecture.

It is important to also consider best practices and recommendations related to other aspects of the Siebel eBusiness application, such as configuration, SmartScript implementation and use of eScript.
In addition to the details contained within this document, Siebel Bookshelf should also be consulted for more complete details, including but not limited to:
  • Performance Tuning Guide
  • Siebel Web Client Administration Guide
  • Siebel Wireless Administration Guide
  • Implementing Load-Balancing with Central Dispatch
  • Setting Up Your Siebel Environment
  • Server Installation Guide (there are Windows and UNIX documents)
  • Server Administration Guide
  • Configuration Guidelines
  • Application services integration reference

1 comment :

  1. Please also post scripting and configuration best practices



Aired | The content is copyrighted and may not be reproduced on other websites. | Copyright © 2009-2016 | All Rights Reserved 2016

Contact Us | About Us | Privacy Policy and Disclaimer