Siebel Architecture Best Practices

Siebel Architecture Best Practices, principles and practices.

Use dedicated hardware for Siebel Applications
For production environments and to some extent development & test environments, the hardware must be dedicated to a single Siebel eBusiness Enterprise.

Hardware requirements
It is strongly recommended to use a Siebel Expert Services Sizing Review to achieve an informed estimate of the likely hardware requirements for the Siebel Enterprise.See also the Siebel Bookshelf documentation “Siebel System Requirements and Supported Platforms” for version 8.x.

Conduct benchmark testing
To finalise hardware requirements for the Siebel eBusiness application, it is strongly recommended to conduct benchmark testing. Before conducting benchmark testing, establish the criteria, goals and scenarios for the testing effort.

Employ known hardware and platforms
As far as is practical, it is recommended to utilize hardware and systems software that is already known to the organization.Implement production architecture in a development or test environment.To ensure that all functionality is supported and performs well within the production architecture, ensure that an environment exists that mirrors the production architecture for testing.

Design scalability into the solution
When devising the structure of the Siebel eBusiness Enterprise, include the potential to scale the environment to support more users, higher transaction volumes or more complex processing.
 
Review the Performance Tuning Guide
Review “Performance Tuning Guide” in the System Administration section of Siebel Bookshelf.

The following summarizes the principle best practices related to implementing Siebel eBusiness architecture.

• Utilize dedicated hardware for each Siebel Enterprise.
• Implement the same architecture as Production in one of the development or test environments
• Conduct a Siebel Expert Services Sizing Review for an informed estimate of hardware.
• Carry out benchmark tests and include the client environment and network infrastructure.
• Design the architecture for scalability from the outset.
• Document the current network infrastructure including latency and available bandwidth
• Ensure staff are Siebel trained and certified (mandatory for Siebel SupportWeb access)
• Establish regular occurrences of downtime for maintenance.
• Establish administrative and maintenance procedures and toolsets.
• Employ a hardware cluster for each production Siebel Gateway server.
• Use dedicated Resonate Schedulers for concurrent user populations above 1,000.
• Establish clear backup strategies for each element of the Siebel Enterprise.
• Implement Resonate Central Dispatch from the outset to avoid re-installation.
• Maintain central control of the Siebel Data Model and consult DBAs regarding change.
• Treat the development environment as almost a production environment.
• Ensure that the development environment is a volume environment

Related Posts