Beruflich Dokumente
Kultur Dokumente
discuss
the
physical
architecture
of
Siebel
setup
and
the
basic
Web browsers
WML devices
Identifies and passes Siebel requests from Web clients to the Siebel
servers Passes completed HTML application pages back to Web clients
Virtual directories
Server Manager.
Supports sharing of common configuration information
and
connectivity
information.
Stored
in siebns.dat file
located
in\\sea**\gtwysrvr\ADMIN
Includes the connection broker and name server for a single server
data.
Stores the data and physical files used by Siebel clients and Siebel
Enterprise Server.
Physical Architecture:
The Siebel Gateway Name Server, Siebel Server, Database Server, and File
System can be implemented on one machine or spread across multiple machines
The Siebel Server(s) should have a high-speed LAN connection to the Database
Server
DDL Sync
DDL sync is used to have a sync between your Siebel Repositories & physical
schema in Oracle DB. ddlsync compares the logical schema (schema definitions
in your repository) with your physical schema (i.e. physical db table/column
definitions) and applies the differential changes on the physical schema so that
they are both in sync
Steps involved
DDL Sync is 3 steps process which includes
sake of simplicity we are assuming that Siebel is installed in C Drive you can
change the path according to your installation
Open command prompt (in Run command field type CMD or command)
cd c:\program files\siebel\7.8\web client\bin
genbscript C:\Program Files\Siebel\7.8\Web Client\BIN\ENU\uagent.cfg
C:\Program Files\Siebel\7.8\Web Client\PUBLIC\ENU
dont append \ after ENU you will get an error. \ is automatically appended by
siebel when you run that utility.
Genbscript has the following syntax:
Genbscript your path to cfg file path where browser script should be
generated
You can also automate generation of browser script with the help of batch file.
But that is subject of another post.
6. Explain performance tuning steps?
7. Which authentication method are you using?
Authentication is the process of verifying the identity of the user before he
gains access to the application. The process consists of collection of user
credentials (such as User Id and Password) and comparing them with pre-stored
values.
Following three general authentication methods are supported by Siebel:
1)
2)
Database Authentication
A separate database login for each user.
Users will provide credential details to DBA. DBA will add/modify/delete
those users to database.
Directory Server Authentication
Single database login can be shared among multiple users.
3)
Users can directly modify their credentials within Siebel application. It will
automatically be synchronized with the directory server.
Third party directory server is required.
The Apply and Activate buttons appear in the Table and Index sections
of Siebel Tools. They are a means to synchronize the logical and physical
schema and alert other users that changes have been made to the schema.
The logical schema is stored in the following tables in the Siebel database.
S_TABLE
S_COLUMN
S_INDEX
S_INDEX_COLUMN
The physical schema is defined in the RDBMS (IBM DB2, Microsoft SQL
Server or Oracle) that is being used.
There are a limited number of things that can be done that cause changes to the
schema. They are adding a new column, table or index or deleting an extension
column, table or index. Each of these actions require an update to the logical
schema and a change to the physical schema. This can be done
through Siebel Tools or using the Database Server Configuration Utility
Next, the Apply button is clicked, which prompts you to connect to the
database using ODBC and to log in as the table owner. This is required
since Data Definition Language (DDL) is being performed bySiebel Tools.
Here is a sample SQL statement that Siebel Tools runs against the database.
DROP INDEX S_CONTACT_JOHN1
After applying changes to the schema is completed, the changes have been
made to the database. You can take advantage of these changes once a
new Siebel repository file (.srf) has been distributed. If an index has been
added, the database may start using this regardless of whether or not a new .srf
file has been distributed. The database works independently from the .srf file.
Clicking the Activate button simply updates the schema version in
the S_APP_VER table. The schema version signals clients, mobile clients and
server components that a schema change has been made and that they need to
update their own logical or physical schemas. Server components use the
dictionary cache or diccache.dat to reference objects in the Siebel database
quickly. Diccache.dat is loaded into memory and shared by all server
components. Whenever a server component runs, it validates the schema by
querying S_APP_VER and comparing the schema version against that which is
stored in the diccache.dat. If a newer schema exists, the Siebel application
rebuilds the diccache.dat.
Compile a new .srf file after making schema changes to ensure that you are
working with the proper schema.
If instead of dropping a custom index, an extension column were being added,
the SQL would be slightly different. Instead of DELETE statements, there would
be INSERTS and instead of the DROP statement, there would be CREATE or
ALTER statements.
In summary, a schema change in Siebel Tools needs to be propagated to
the Siebel database and applied to the physical database. The final step is to
activate the changes, or increment the schema version in
the S_APP_VER table.
NOTE: When clicking the Apply button to apply data model changes, you will be
prompted for the Privileged User Id / Password. This must be the table-owner
name/table-owner password. BeforeSiebel 7.7, this was typically DBA/SQL.
With Siebel 7.7, this has changed to SIEBEL/local user password. For example,
suppose your login id is JSMITH and password is DB2. When you apply schema
changes to the local database, your Privileged User Id / Password would be
SIEBEL/DB2.
9. How to troubleshoot server busy error?
Server Busy Error in SIEBEL
3)
1)
2)
3)
4)
5)
6)
7)
8)
9)
df -hk
top n 0
prstat a 5 5
10) Try using vanilla Siebel.srf file
11) Try using backu[ copy of siebns.dat file
13) Check lbconfig.txt file & eapps.cfg to make sure requests are reaching
to SCbroker
a)
Make sure that all the mounts including File system are available.
gateway and your siebel servers. If you are reconfiguring your components in
Server Administration an commit this configurations, the siebns.dat file is
updated.
Or
Pls don't edit your Siebns.dat file manually. Use your Server Configuration
Screen to update it by enabling components and component definition as
required.
11. Briefly explain Siebel server installation pre-requisites & installation
steps.
12. How to generate lbconfig.txt file?
using generate lbconfig command from server manger at enterprise level, b4
generating lbconfig make sure all the servers in your enterprise is running.
Or
14. Steps to extract local database and to set up Siebel tools & mobile
clients?
a) create user in application with responsibility & position assigned.
b) create user in DB and grant required previlages.
c) register user for mobile clients under Administration --> Siebel Remote,based
on your client user needs select appropriate routing model here(Extract only or
Standard)
d) run generate new database job
e) run DB Extract job, here choose client db password encryption as false or you
may end up with mess nothing like that u can get encryption key also.. but not
preferable
f) intialize local DB extract
15. What is the difference between position and responsibility?
Responsibility is used to control access to views
and
Position is used to control access to Data.
16. How to cleanup Siebel file system?
using sfscleanup utility Syntax: sfscleanup /u sadmin /p secret /f <siebelfs
path> /x sfscleanup.log