Bookshelf v8.1/8.2: Impact of Service Failures

Table 6 summarizes the impact of failure of services in the Siebel deployment. The table includes information about specific services that were not already covered. This topic is part of How Service Failures Affect the Siebel Deployment.

Table 6. How Service Failures Affect the Siebel Deployment
Service Failed	Affected Component	Impact
Siebel Gateway Name Server	Siebel Server components	You cannot start or add any new components. Users can continue to log in and out of Siebel applications. Existing user sessions are not interrupted. Server requests continue to be processed successfully, with some exceptions, as follows.
	Server administration functions	Unavailable.
	Siebel Product Configuration Object Manager	You can still launch product configuration sessions, as long as the connection information has been cached. By default, the connection information is cached when the first connection is made.
	Gateway Name Server database (siebns.dat)	This database maintains server configuration information for the Siebel Enterprise Server. If this database is corrupted or lost, then you must reinstall all of the Siebel Enterprise Server software.
Siebel Server	Application Object Manager components	The Siebel application is unavailable. Siebel Connection Broker (SCBroker) failure: You cannot create new user sessions. If the SISNAPI connection between the Web server and the Object Manager fails, then the SWSE retries the connection. If, after a certain number of attempts, the connection is still not available, then the connection completely fails and the user gets an error message. Existing user sessions are unaffected by SCBroker failures.
	EAI	Interface to external application unavailable.
	Batch components	Loss of functionality (components such as Assignment Manager or Workflow unable to process server requests).
Siebel File System	Attachments	Unavailable.
	Correspondence	Unavailable.
	Shared user preference files	Unavailable.
	Docking transaction files from Siebel EIM	Unavailable.
	Email Response	Unable to process inbound messages. Unable to send outbound messages with attachments.
File System Manager (FSM)	Components that access the FSM	Current requests fail.
File System Manager (FSM)	Attachments	Unavailable.
Web server	Siebel Web Clients accessing Application Object Managers	The Siebel application is unavailable to Web Clients. Mobile Web Clients are unaffected.
Web server	EAI inbound HTTP adapter	Unavailable.
Siebel database	Client access, background tasks, batch tasks	Unable to access Siebel Business Applications. Siebel Servers cannot function. Only the Mobile Web Client is not immediately affected by a Siebel database failure.
Siebel database	Batch and interactive components	Unavailable.

Siebel Deployment Planning Guide		Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.