Deployment Planning Guide > Siebel Infrastructure Planning >
Defining a Test and Transition Plan for the Siebel Deployment
It is important that you define a test plan to verify that the proposed deployment infrastructure functions correctly and is sized correctly. Equally important is defining a plan that transitions the Siebel deployment to production.
This topic is a step in Process of Infrastructure Planning.
Observe the following best-practices guidelines for testing the Siebel deployment and transitioning it to production:
- Separate production environment. Keep the development and test environments physically separate from the production environment. Never conduct development and test activities on the production Siebel Database and preferably not on the production database server.
- Server stress testing. Test Siebel Enterprise Server performance under average and peak workloads. Siebel Expert Services finds that performance problems at customer sites are frequently caused by the following things:
- Servers were tested at much less than average or peak workloads. This prevents configuration and tuning problems from being uncovered.
- Siebel Server components are either incorrectly distributed across servers or are not configured correctly.
- The load balancing strategy is ineffective under typical workloads. This can be caused by stress-testing the servers with a workload that has characteristics different than the production environment.