Академический Документы
Профессиональный Документы
Культура Документы
Siebel on Microsoft
Siebel has run on Microsoft servers since first released Siebel is optimised and stable on the Microsoft platform All tiers of Siebel architecture supported on Microsoft platform Database Server - SQL Server Application Server - Windows Server Web Server Client - IIS - Internet Explorer
Integrated with Siebel CRM client or standalone client All tiers supported on Microsoft platform
Includes SQL Server 2000 for database Originally developed on Microsoft platform Analytics is optimised and stable on the Microsoft platform
PDA
Mobile Client
Browser UI Object Manager Data Manager
SIEB SYNC
Local DB
Web Server
Siebel Web Server Extension
External Applications Siebel Enterprise Siebel eAI Object Manager Siebel Replication Data Manager
Regional Siebel DB Server
Siebel Remote
Voice Interaction
Email Interaction
Mobile Client
Has local copy of Siebel database Local server functionality Uses High Interactivity interface
SWSE
Enterprise Server Siebel Server Component Component Siebel Server Component Component
Framework for running server components Obtains configuration information from the Gateway Name Server
Enterprise Server
Siebel Server
Component Component
Server Program executed as Task Examples: Object Manager - User Sessions Workflow Process Manager - Business Processes
Component Component
Component Component
Stores component definitions, parameters, and connectivity information Stored in siebns.dat file
Dynamically registers Siebel Server and component availability
Enterprise Server Siebel Server Component Component Siebel Server Component Component
Multi-Threaded
Multi-threaded components have multiple execution streams within a single process. So each operating system process can support multiple Siebel Tasks. i.e. Object Managers
Ensure Empty Temporary Internet Files Folder when browser is closed option is not enabled.
Uncached
GET: icon.gif
25KB
icon.gif DATE: 10/08/03 07:14
Cached
2KB
icon.gif icon.gif DATE: 10/10/03 09:25 DATE: 10/08/03 07:14 RESPONSE: Not-modified
0KB
icon.gif DATE: 10/10/03 09:25 EXPIRES: 10/12/03 14:13:08 icon.gif DATE: 10/08/03 07:14
May not have all content available from all web servers
i.e. Different object managers accessed through different groups of web servers In this case the load balancer will need to support layer 7 (content) switching
Handheld Client
Mobile DB
SQL CE
Load Balancer
Load Balancers
Server Manager
Siebel Database
Handheld Client
Mobile DB
SQL CE
Load Balancer
Load Balancers
Server Manager
Siebel Database
Siebel 7.5 and prior integrates with Resonate Central Dispatch for Server Load Balancing Required for any customer load balancing 2 or more web servers OR application servers Siebel 7.7 supports two mechanisms for Server Load Balancing Siebel-Provided load balancing Third Party (Standard) HTTP Load Balancers
F5 Big-IP initial solution for certification
New Component Siebel Connection Broker (SCB) Accepts all connections for Object Managers Listens on a single static port
Default: 2321
No need for many dynamic ports Simplifies connectivity between web servers and Siebel Servers
Web Browser
HTTP HTTPS
HTTP HTTPS
Web Server
Web Server
VIP/VPort
SISNAPI
OM
OM
OM
OM
OM
OM
Siebel Server
SRB
SISNAPI
SRB
HTTP HTTPS
Web Server
Web Server
Web Server
SWSE
SISNAPI
VIP/VPort
Siebel Server OM
SCBroker
OM
OM SRB
OM
OM Comp .
HTTP HTTPS
Web Server
Web Server
Siebel Server
SCBroker
Siebel Server
SCBroker
OM
OM
OM SRB
SISNAPI
OM SRB
OM
OM Comp .
Web Server
Web Server
SWSE
OM
OM
OM
OM
OM
OM
Implementation Retry
Web Server
Web Server
SWSE
OM
OM
OM
OM
OM
OM
Implementation Reconnect
Web Server
Web Server
SWSE
OM
OM
OM
OM
OM
OM
<VirtualServer>=<ID>:<Host>:<Port>; <ID>:<Host>:<Port> i.e. VirtualServer1=1:SiebSrvr1:2321;2:SiebSrvr2:2322 VirtualServer2=1:SiebSrvr1:2321;2:SiebSrvr3:2321 OM Connect Strings (eapps.cfg) Use Virtual Servers as Enterprise hosts Call Center: siebel.TCPIP.none.none://VirtualServer1/Siebel/SCCObjMgr Sales: siebel.TCPIP.none.none://VirtualServer2/Siebel/SSEObjMgr
Load balancing
Security Management and Monitoring Size of the deployment does not necessarily matter
Central Dispatch Installation/ Sometimes Configuration complex Load balancing Monitoring Resourcebased
Third Party Varies by customer Response & Resourcebased Extensive 3rd party int. support Limited by HW capacity
Scalability
Proprietary Part of Siebel Resonate Server Admin Interface Up to 64 node No hard limit per site
Component Scalability
Scaling within a server
Multi-threaded components Siebel Connection Broker Scaling across servers Load balancing Focus on Object Managers (user sessions)
Can be started manually, through Server Request Broker, or automatically (Default Tasks parameter)
Multi-Threaded Components
Can have multiple processes as well as multiple threads
Important to control ratio of threads to processes Can have major impact on performance Determined primarily by rate of switches between threads 100:1 good starting point for Client Object Managers
Assumes 30sec think time, for 15 sec think time use 50:1
Can set additional processes to spawn on demand Will always start minimum number specified Will start additional processes as needed to maintain process:thread ratio Limit on maximum number of processes
Object Manager
MaxMTServers 10
MinMTServers 10
Memory Scalability
Multi-Process, Multi-Threaded model
Multi-threaded components support many concurrent operations in a single process All threads in a process share the same memory space Multiple processes can be deployed, each with multiple threads Each Process has a separate memory space
If a single Siebel process needs more than 1.5GB theres normally something wrong No need for large process memory model (/3GB switch)
No benefit for Siebel software Siebel will always use 2GB allocation regardless
4GB
1GB Object Manager 1GB Object Manager 1GB Object Manager 1GB Object Manager 0.5GB System/Misc.
/PAE Switch
1GB Object Manager 1GB Object Manager 1GB Object Manager 1GB Object Manager 0.5GB System/Misc.
Web Server
Sales OM
Siebel Server
Web Server
Sales OM
Siebel Server
Web Server
Service OM
Siebel Server
Vertical Scalability
Horizontal Scalability
Enterprise-Wide Scalability
Web Client Web Client Web Client Web Client Web Client Web Client
Load Balancing
Web Server + SWSE Web Server + SWSE
Load Balancing
SCB
SCB
Siebel Server
Enterprise Server
Siebel Server
Some of the same features which provide scalability can also enhance availability
Handheld Client
Mobile DB
SQL CE
Load Balancer
Load Balancers
Server Manager
Siebel Database
Handheld Client
SQL CE
Server Manager
Siebel Database
Handheld Client
Mobile DB
SQL CE
Load Balancer
Load Balancers
Server Manager
Siebel Database
Distributed Services
Web Client Web Server Siebel Enterprise Server
Web client requests Assignment task Service Request Broker determines if Assignment Task is available locally
Object Manager
SRBroker
Assignment Manager
Distributed Services
Web Client Web Server
Web client requests Workflow task Service Request Broker determines if Workflow Process Mgr is available locally
Object Manager
SRBroker
No, tasks are assigned on a round-robin basis to servers SRBroker Workflow that have Process Mgr. running
Workflow Process Manager
Assignment Manager
Distributed Services
Web Client Web Server Siebel Enterprise Server
Web client requests Assignment task Service Request Broker determines if Assignment Task is available locally
Object Manager
SRBroker
Local Assignment Manager component is unavailable, so request routed to other SRBroker Assignment Manager
Workflow Process Manager
Assignment Manager
Siebel Remote
Workflow Policies Dynamic Assignment And others.. Siebel Database Server
Can be accessed through same network name / IP address on either physical server Failover is transparent and automatic
Processes
Network
Storage
Shared Storage
Logical Server
Processes Network Storage Processes Network Storage
Physical Server
Physical Server
Logical Physical
Physical
Logical Physical
Logical Physical
Get service name from Registry or service properties [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servi ces] Gateway : gtwyns Server : siebsrvr_<Ent>_<Srvr> i.e. siebsrvr_EntSieb752_srvr1
Pending Timeout 300 seconds Allows 300 seconds for a Siebel Server to shutdown before being marked as failed
Any Questions.
Controlled through:
User Preferences > Behaviour > View Cache Size Default: 10
Background component
Multi-threaded component Need to set MaxTasks accordingly
Assignment Manager
Assignment Manager
available on Server this server? WhichRequest other Broker servers server Choose haveWorkflow on roundworkflow basis robin Process online? Manager
Processes asynchronous requests Request submitted by creating record in table S_SRM_REQUEST Server Request Processor reads from table Request must:
Be active (reached activation time) Not be specified for a different Siebel Server Not being processed by other Server Request Processor
S_SRM_REQUEST
SRProc
Sleep Interval
Request Queue
SRBroker
Task
Connection Pooling
Controlled by component parameter: Number of Sessions per SISNAPI Connection Siebel Object Manager to Database
Object Managers
Siebel 7 supports its own database connection pooling Used for connections from Object Managers
Shared
Shared
Specialized
Siebel Database
Processes (components)