Running Multiple Siebel Enterprises Against the Same Schema
(Doc ID 477829.1)
Last updated on DECEMBER 18, 2019
Applies to:Siebel System Software - Version 7.5.3  and later
Information in this document applies to any platform.
Release(s):V7 (Enterprise), V7 (Professional), V7 (MidMarket), V8 (Enterprise), V8 (Professional)
Database(s):All Supported Databases
App Server OS(s):All Supported Platforms
Latest release tested against:V8 (Enterprise)
Keywords:multiple, enterprise, database
This document was previously published as Siebel Technical Note 544.
Deploying Multiple Enterprises Against One Schema Using the Same Table Owner
- Selected a deployment topology that maps to the most common deployment combination.
- Selected a deployment topology that covers the greatest number of features and functionality.
- Due to resource limitations, used only a limited number of servers for the certification test:
- This certification does not address the scalability aspects in such a deployment. The same scalability and performance requirements and limitations still apply to the multiple-Enterprise environments.
- Running multiple Siebel Enterprises does not, by itself, add scalability overhead to the deployment. The number of concurrent users and number of Siebel Servers required are still the primary factors when sizing your deployment.
When To Consider Running Multiple Enterprises
- (Siebel version 7.5.x and earlier). When multiple Enterprise Virtual IP addresses are needed:
- When there is one Enterprise serving both internal and external users, and security policy dictates complete separation of application servers and networking infrastructure between internal and external users.
- To overcome the limitation imposed by Resonate Central Dispatch when load balancing Siebel Servers. Central Dispatch imposes an upper limit of 64 load-balanced Siebel Servers per Enterprise. Furthermore, it was observed that Central Dispatch rule registration performance degrades when the number of servers exceeds the 32 server limit as described in the previous bullet point. Resonate Central Dispatch is no longer supported nor required in Siebel version 7.7 for Siebel Server load balancing.
- When there are multiple logical groups of Siebel Servers, and the following is true:
- Each group should be administered separately to reduce administration overhead.
- Each group has different load balancing policies or schemes. While the default load balancing policy works well in most situations, there may be cases where a group of Siebel Servers works better with a different load balancing scheme.
- Each group has different maintenance schedules.
- Each group has different availability requirements, which require different high availability architectures.
This document is informational and intended for any user.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|Deploying Multiple Enterprises Against One Schema Using the Same Table Owner|
|When To Consider Running Multiple Enterprises|
|Known Technical Limitations and Recommendations|
|Use of the zero downtime feature (component reconfiguration).|