Siebel Service Window Script - Simple

Following Script will start the windows service if the status is stopped.

================================================================

for /F "tokens=3 delims=: " %%H in ('sc query "Windows_Service Name" ^| findstr "        STATE"') do (

  if /I "%%H" NEQ "RUNNING" (

   REM Put your code you want to execute here

   REM For example, the following line

   net start "Windows_Service Name"

  )

)

Comments:

Please change the name of the service as per your services details.

Refer the Image here for Name of the Service : 

Configure Email Notification about Component Job Fail

Configure Email Notification about Component Job Fail

• Navigate to Administration - Server Configuration > Enterprises > System Alerts.
• Select Administrator Email Alerts and select Copy Record from the applet-level menu.
• Enter the following details as shown in below image.

• Set the Workflow Process Manager component to use this event notification profile. [Change the Parameter Value: to Profile You Just Created It. 
•  Parma Name: Notification Handler

•  Param Name: Notification Action on Task Ex     Value = 1

• Now create a job for this component without any parameter to generate an error message.

•  See the Result in Outlook express.
•  

How to create a Constraint PickList?

Today, I am going to share a very basic, and I would say a, "unique feature" in Siebel by which we can restrict values being displayed inside the PickList.

Here you go, "lets assume I need to create two fields a) Country b) State, on Opportunity business Component, along with their respective pick-lists, in such a way that system will display the list of States in the drop-down which belongs to the 'Country' selected in the Country Field."

Here below are the steps need to follow:

1. Check for the available columns (Characters Length: 30) in S_OPTY table, which is not being used by any of the field in Opportunity Business Component. Lets assume two fields for the purpose are ATTRIB_01, ATTRIB_02.

2. Create two PickLists for Country & State fields.
a) For Country

PickList Name: Country PickList
Project: Oppty
Bounded : TRUE
Business Component : PickList Generic
Static : TRUE
Type Field : Type
Type Value : COUNTRY_LIST

b) For State

PickList Name : State PickList
Project : Oppty
Bounded : TRUE
Business Component : PickList Generic
Static : TRUE
Type Field : Type
Type Value : STATE_LIST

3. Create LOV values in "Administration - Data -> List of Values" view, with the following values (I am assuming you know how to create LOV values)

a) For Country : (Type = COUNTRY_LIST)
Values = US, India

b) For State : (Type = STATE_LIST)
Values = Georgia, Ohio, Texas, NewYork, NewJersey (Put Description = US, for all)
Values = Uttar Pradesh, Madhya Pradesh, Karnatka, Gujrat (Put Description = India, for all)

4. Create two fields on Opportunity Business Component.
a) For Country

Name : Country
Column : ATTRIB_01
PickList : Country PickList

Country's Field PickMap

1. Field: Country
PickList Field: Value
Constrain: FALSE

b) State

Name : State
Column : ATTRIB_02
PickList : State PickList

State's Field PickMap

1. Field: State
PickList Field: Value
Constrain: FALSE

2. Field : Country
PickList Field : Description
Constrain: TRUE

5. Create two fields on Opportunity List Applet :
a) For Country

Name : Country
Field : Country
Display Name - StringOverride : Country
Runtime : TRUE

b) For State

Name : State
Field : State
Display Name - StringOverride : State
Runtime : TRUE

6. Expose the two fields created on the Edit List webapplet layout of the Opportunity List Applet.

7. Compile the SRF with all the configuration done so far and see the magic on the UI.

Siebel Diagnostic Data Collector

1 – Collect the Gateway Server Details with the following Command.

             Note: Ensure that you gateway server is up and running state.

 A.     Open the command prompt and change the working directory.

 %Siebel Installation Dir% Gateway Server Dir / Bin Folder

              B.     Type the following command to run SDDC.

Siebsnap.exe     –g     –u SADMIN     –p SADMIN

                  -g  :   Stand for Gateway Server

                  -u  :    Stand for User ID

                  -p  :    Stand for User Password

Note:  This command will generate the following directory with all the details:  Refer the Image here.

 2 – Collect the Siebel Server Details with the following Command.

            Note: Ensure that you siebel server is up and running state.

C.     Open the command prompt and change the working directory.

%Siebel Installation Dir% Gateway Server Dir / Bin Folder

            D.     Type the following command to run SDDC.

Siebsnap.exe     –s     –u SADMIN     –p SADMIN

                  -g  :   Stand for Siebel Server

                  -u  :    Stand for User ID

                  -p  :    Stand for User Password

 Note:  This command will generate the following directory with all the details: Refer the Image here.

 3 – Collect the Siebel Web Server Extension Details with the following Command.

            Note: Ensure that you web server is up and running state.

E.      Open the command prompt and change the working directory.

%Siebel Installation Dir% Gateway Server Dir / Bin Folder

            F.      Type the following command to run SDDC.

Siebsnap.exe     –w

                  -g  :   Stand for Siebel Web Server Extension

Note:  This command will generate the following directory with all the details:  Refer the Image here.

Error While Generating a New Database

Error While Generating a New Database

SBL-GDB-00004: Error in Main function.

Error Details:

Executing  “Generate New Database” Job resulted in following error.

SBL-GDB-00004: Error in Main function

Reason:

We increased the log level for Generate New Database Component and analyzed the generated logs. In logs we found the following information

Trace TracingInfo 3 0 2009-04-28 02:37:54 Copying template /siebdir/sieb78/siebsrvr/dbtempl/sse_utf8.dbf

to /siebdir/sieb78/siebsrvr/dbtempl/db42r53.682/sse_utf8.dbf...

GenericLog GenericError 1 0 2009-04-28 02:37:54 Error creating SQL Anywhere database template file (UTLFileCopy szTemplFileName -> szWatcFileName).

Solution:

Further analysis revealed that sse_utf8.dbf file was not present in  /siebsrvr/dbtempl. After going through bookshelf and metalink we came to conclusion that there are two files that should be present in /siebsrvr/dbtempl/ folder

    sse_utf8.dbf

    sse_encr.dbf

We copied these files from other server and exectued “Generate New Database” Job and it ran successfully.

Siebel License Key Update from Back-End

Siebel License Key Update from Back-End

When one needs to insert license key to Siebel CRM server when the Administration-Application option is not available

after logging in as SADMIN/SADMIN, please log into the Microsoft SQL Server Management studio and then type the following DB queries:

use siebeldb

select * from S_REPOSITORY

select * from S_APP_VER

select * from S_APP_KEY

update S_APP_KEY

set APP_KEY = '7207 0105 7880 5783 3210 3318 0417 3444 2103 3197 3818 7591 8759 1870 0187 5916 1241 8744 1873 2187 5918 7591 8759 8726 2180 4221 032'

Where ROW_ID='1-K53'

OR

I went to Administration Application > License Keys and applied the license keys on my local and was successful. I was able to see all the views related to this key.

I have searched in the Support Web and found the resolution for this issue. You can check for the Doc ID 530845.1. This document was previously published as Siebel SR 38-3279920201. Below steps will resolve the issue.

    * Copy the sse_samp.dbf file from \Webclient\Sample\utf8 folder to the \webclient\local folder.

    * You need to change the connect string parameter under [Local] section of CFG file. In my case it was uagent.cfg file. Your original connect string will look similar to string given below

          ConnectString = C:\PROGRA~1\Siebel\7.8\WEBCLI~1\local\sse_data.dbf -q -m -x NONE -gp 4096 -c15p -ch25p

    * Only change the dbf file name to sse_samp.dbf. This way all the attributes related to the local db is available for the Sample db also. The final connect string parameter after editing should as below.

          ConnectString = C:\PROGRA~1\Siebel\7.8\WEBCLI~1\local\sse_samp.dbf -q -m -x NONE -gp 4096 -c15p -ch25p

    * Now log into the dedicated client as Local with Sadmin/sadmin.

    * Apply license key from here as New button is enabled.

    * Log out and move back the sse_samp.dbf file to original Sample\UTF8 folder to continue to work as usual.

    * Change the Local connect string to the original one.

    * Re-log in to the Sample DB to view the new views.

Apart from this way, we can also add license key from Tools or Inserting the key into S_APP_KEY table under the Sample DB using dbisqlc.exe.

Hope this may be useful to someone.

How to Do Load Balancing on Siebel Server [Manually]

How to Do Load Balancing on Siebel Server [Manually]

Steps:

1.      Connect to Enterprise using the command prompt.

A. Open CMD and change the path to %Siebel Server Installation Directory%BIN

B. Type the following command to connect to enterprise.

Srvrmgr –g gateway_address  -e enterprisename  -u userid  –p password

Example1 :

Srvrmgr –g R0346  -e OUEnt  -u SADMIN –p SADMIN

           

2.      Generate the load balancing file with the following command.

Generate LbConfig

Note: this command will generate a .txt file with all the enterprise server as virtual servers.

%Siebel Server Installation Directory Path%Admin% lbconfig.txt

3.      Now Lets modify our eapps.cfg file to enable the load balance on the web server. [Remember this is done automatically when apply the logical profile on web server but for learning purpose we are going to do it manually].

1. Open the eapps.cfg file and change the following values in it.

Look into the following Section: [ConnMgmt]

EnableVirutalHosts =    TRUE

VirtualHostsFile      =  /SiebSrvr/Admin/lbconfig.txt

2. Locate the following section in eapps.cfg file.

[/callcenter_enu]

3. Change the following lines:

ConnectString = siebel.TCPIP.None.None://R0346:2321/OUEnt/SSASampleComponent

                        Replace the Server Name and Port with [VirtualServer] word.

4. Restart your IIS Admin Service and Login into Application.