!Unexpected End of Formula2.Owning Group23.Siebel Architecture Diagram34.Siebel Start/Stop steps:-9Stop & start of application for PSP/UAT/eUAT/eSIT:9Steps to stop Siebel, Batch server and gateway server9Stop the Gateway server:9Steps to start Siebel, Batch server and gateway server10Stop start of application for DEV 1,2,310Stop start of application for Prod and SVP115.Common issues while stopping / Starting Siebel:-12Siebel Server is not coming up...What should we check?126.Real Time Framework14

Document Revision

DateAuthorVersionChange Reference

16-Oct-2013Kapilraj Bele & Om Prakash RoutDraftInitial Draft

Owning GroupOwning GroupOMCS Apps team

Siebel Architecture Diagram

Development archicture in Westpac

SIT environment Archicture

Web Server

Siebel Architecture Consists of :-

1. Siebel web Clients: The ones which access Business data

2. Web Server: The one which handles interactions with web clients

3. Siebel Server(s): The one that manages Business data and provide batch and interactive services for clients.

4. Database Server: The one, which stores Business data and files.

5. File System: Shared Directory stores compressed literature used by siebel

1. Siebel Web Client: There are different kinds of clients available for accessing business data in Siebel.

Dedicated Client Web Client/Thin Client/Zero foot print Client - eg: IE, Netscape etc., Mobile Web Client - eg: Laptop/ Configurators terminal Wireless web Client - eg: Mobile Phones Hand Held web Client - eg: PDAs

2. Web Server:

Web server identifies and passes Siebel requests from Siebel web clients to Siebel server. Passes html application with Business data back to Siebel web clients.

If we get into more detail (s) of what Web Server Internally does:

Actually Web Server is not part of Siebel, we need use a web server like IIS, Apache, etc.,

In the Web Server, the following additional Siebel components will be available:

Virtual directories Siebel Web Server Extension (swse) Config. File (Eapps.cfg)

Virtual directories (VDs): VDs exists on the Web Server to receive inbound Siebel web Client Requests for each installed Siebel Application and forwards these requests to swse.

Eg: /esales_enu , /eservice_enu, /emarketing_fra etc., (In this _enu refers language English, _fra French etc.,)

Siebel Web Server Extension (swse):

swse receives and parses(sends) inbound request from Siebel Web clients.

Creates and maintains TCP/IP connections to the Siebel server.

Routes requests to appropriate Siebel Server Component.

Configuration File (Eapps.cfg):

Eapps.cfg is the Single Configuration file for all Siebel web Applications

It contains Configuration information, like connectivity info, login and security settings

It allows swse to communicate with Siebel Server

It contains Connect String for each of Siebel Applications installed on Web server.

3. Siebel Server: Executes tasks to manage business data

Siebel Server is a Windows Service or Unix Daemon process

Is the platform that supports Interactive, Batch and Background processing for all clients

i. Handles Interactive Processing (Eg: Synchronization)ii. Handles Batch Processing (Eg: Generate database, Generate Triggers)iii. Handles Background processing (Eg: workflow and Assignment Mgr)

Controls server components running on a machine

Various entities we find in Siebel server are : Siebel Repository File Configuration File Siebel Web Template Files Server Components

4. Database Server (Relational Database): Database Server stores data used by Siebel application in a predefined database schema.

Theres a component called Data Manager, which resides in Database server and handles all requests to database.

It supports variety of third party relational databases like:

OracleSQL ServerSybaseInformixGupta SQL etc.,

File System : File System is a shared directory that stores compressed files used by Siebel applicationsTheres a component in File system called File system Manager, which handles read/write access to user.Note:- Siebel Web Client displays the Siebel application in a standard web browser A third-party Web Server has the Siebel Web Server Extension (SWSE) installed and the Siebel application virtual directories created The Siebel Gateway Name Server holds the parameters and connection information for Siebel Servers Siebel Enterprise is a logical collection of Siebel Servers Siebel Servers execute tasks to manage business data via programs called server componentsSiebel Start/Stop steps:- 1.Stop/Start steps of Siebel,batch and gateway server for PSP/UAT/eUAT/eSIT instances 2. Stop/Start steps of Siebel and gateway server for Dev1,Dev2,Dev3 instances 3. Stop/Start steps of Siebel and gateway server for Prod and SVP instances.

Stop & start of application for PSP/UAT/eUAT/eSIT:Steps to stop Siebel, Batch server and gateway server 1>Login to each of the Application server a>stop Siebel server cd $HOME/81/siebsrvr . ./.siebenv.sh cd bin ./stop_server all b> Stop the batch server cd $HOME/81/batchServer/siebsrvr . ./.siebenv.sh Cd bin ./ stop_server e For PSP: ./ stop_server e twbc62 For UAT: ./ stop_server e swbc62 For euat: ./ stop_server e swbc32 For esit: ./ stop_server e twbc32 Stop the Gateway server: cd $HOME/../gtway/gtwy_xag_script/bin ./agctl stop siebel_gateway For PSP: ./agctl stop siebel_gateway twbc62 For UAT: ./agctl stop siebel_gateway swbc62 For euat: ./agctl stop siebel_gateway swbc32 For esit: ./agctl stop siebel_gateway twbc32

Steps to start Siebel, Batch server and gateway server 1>Login to each of the Application server Start the Gateway server: cd $HOME/../gtway/gtwy_xag_script/bin ./agctl start siebel_gateway For PSP: ./agctl start siebel_gateway twbc62 For UAT: ./agctl start siebel_gateway swbc62 For euat: ./agctl start siebel_gateway swbc32 For esit: ./agctl start siebel_gateway twbc32 Check:list_ns ps ef|grep gtw b>start Siebel server cd $HOME/81/siebsrvr . ./.siebenv.sh Cd bin ./start_server all Check:list_server all ps ef|grep sieb c> Start the batch server cd $HOME/81/batchServer/siebsrvr . ./.siebenv.sh Cd bin ./ start_server e For PSP: ./ start_server e twbc62 For UAT: ./ start_server e swbc62 For euat: ./ start_server e swbc32 For esit: ./ start_server e twbc32 Ps ef|grep batch Stop start of application for DEV 1,2,3

Steps to stop Siebel, Batch server and gateway server 1>Login to each of the Application servera>stop Siebel servercd $HOME/81/siebsrvr. ./.siebenv.shCd bin./stop_server allb> Stop the gateway servercd $HOME/81/gtwysrvr. ./.siebenv.shCd binStop_ns

Steps to start Siebel, Batch server and gateway server 1>Login to each of the Application servera> Start the gateway servercd $HOME/81/gtwysrvr. ./.siebenv.shCd binStart_nsCheck:list_nsPs ef|grep gtw

b>start Siebel servercd $HOME/81/siebsrvr. ./.siebenv.shCd bin./start_server allCheck:list_server all

Stop start of application for Prod and SVPSteps to stop Siebel, Batch server and gateway server 1>Login to each of the Application servera>stop Siebel servercd $HOME/81/siebsrvr. ./.siebenv.shCd bin./stop_server all

Stop the Gateway server:cd $HOME/../gtway/gtwy_xag_script/bin./agctl stop siebel_gateway For Prod: ./agctl stop siebel_gateway pwbco2 For SIT: ./agctl stop siebel_gateway swbco2

Steps to start Siebel, Batch server and gateway server Start the gatewaycd $HOME/../gtway/gtwy_xag_script/bin./agctl start siebel_gateway For Prod: ./agctl start siebel_gateway pwbco2 For SIT: ./agctl start siebel_gateway swbco2 Check:list_nsPs ef|grep gtwSteps to start Siebel and gateway server 1>Login to each of the Application servera>start Siebel servercd $HOME/81/siebsrvr. ./.siebenv.shCd bin./start_server allCheck :list_server allPs ef|grep sieb

Common issues while stopping / Starting Siebel:-Siebel Server is not coming up...What should we check?

1. Validate that the .srf file is not corrupt by testing the srf on a dedicated environment.if the dedicated client is facing issues possibly 2 reasons must be therea.srf file is corruptb.db itself is downTake the necessary action

2. Stop siebel servers after executing ./siebenv.sh and command stop_server allForcefully stop :-Stop_server -f

3. Check that no Siebel processes for the enterprise are still running.

Ensure that all processes for that enterprise are killed.use kill -9 pid to achieve the same

4. Delete any file that exists in directory $SIEBEL_HOME/sys with name like:osdf (it is a binary file that contains boot-up information which gets written to after a core dump.)

5. Delete any file that exists in directory $SIEBEL_HOME/admin with name like:shm (It is the memory which is shared for all siebel processes. Siebel server and components (like SRProc) stores enterprise information in this memory and refersfor processing of requests. It automatically gets created when server starts and gets deleted when the server shut down.

6.Delete fdr and core files as these file eat up large amounts of memory.

7.Cleanup unwanted logarchive and log files so that fresh logs can be monitored and space can be freed up.

8.Try to restart server after executing ./siebenv.sh and command start_server allNote- At this point if the server still does not restart, you need to check the enterprise log for the reason. The enterprise log is located in:$SIEBEL_HOME /enterprises/[SiebelEnterprise]/[SiebelServer]/logThe enterprise log has name with format:[SiebelEnterprise].[SiebelServer].log

9. If no enterprise logs are getting created there are connectivity issues with the database:i.e change of db password for SADMIN userdb server is down(Come to this conclusion only if you skipped the first step)run odbcsql from siebsrvr/bin to check connectivity issuesodbcsql /u SADMIN /p SADMIN /s DSN Name

10. Any changes which lead to the corruption of siebns.dat will also result in the servers not coming up.usually NameSrvr logs tell us connectivity related information and errors like key not found.Try reverting to an old working siebns.dat file.

11.If the environment is LDAP authenticated any changes in the LDAP trees can also affect the environment.please verify the same.

12.Check the SCBroker and SRBroker logs;you would get a hint.

13.Use netstat -an|grep for verifying that the gateway service port is listening.

14.Use netstat -an|grep for verifying that the SRBroker/SCBroker port is listeningSo that is a long list.Thought there can be other reasons too; I have only mentioned those encountered by me.I will keep on updating when I find newer reasons.Till then stay tuned.

Real Time FrameworkBelow is the pictorial flow of the real time messages. The message flows from the external system to the ESB MQ queue. From ESB MQ Queue to the local MQ the message will be passed. From the local MQ the EAI Listeners will pick the messages and pass it to the generic workflows. Generic workflow will then call up the EAI Dispatch service Rule set. Depending up on the Brand in the message the EAI Dispatch rule will call up the component like No Brand or LK001 Components will then process the message and pass back the response.IDVDIG/SIGGSPYDERSOLCARDSCISOTPLocal MQESB MQSiebel Listner ComponentsGeneric WorkflowEAI Dispatch Rule set which decides which Brand the message has to go Specific Workflow Component for the BrandNo BrandWPACLK001GHS

Listeners which polls the Local MQs

Below are the generic Workflow processes which are called from the Listeners.

WBC Web Service Inbound Proxy ProcessWBC UCM Customer Profile Integration Process Real timeWBC Merge Records WorkflowWBC UCM Customer Profile Integration Process

Below is the EAI disptach Serice View which tells which component to call from the message

Authors: Om Prakash Rout and Kapilraj Bele2