In our project a normal Siebel release cycle is of 3 months. This means that we develop for three months and then it goes live in production. Now during our development phase of 3 months we run Full Compile of SRF almost on daily basis and it is usually somebody’s responsibility to start the Full compile.
Now, like most of the clients our client is also US based which means during the last phases of development cycle client tests (UAT) the changes we have done their morning and our evening. During that time the time it is very important to start full compile on time otherwise it could impact client’s testing. After couple of incidents where the person responsible to start full compiles couldn’t do so due to some problem. We decided to automate the process of full compile to get rid of this problem.
And here is how we did it.
We created a batch file which was as following
cd "c:\program files\siebel\7.8\tools\bin\
siebdev.exe /c tools.cfg /d SERVER /u USERNAME /p PASSWORD /bc "Siebel Repository" "FullCompile.srf"
(Replace the username and password with your Siebel Username and Password)
Details fo switches used are as following
/C: Tells the configuration file to use
/D: Data source which should be used
/U: Username to start full compile
/P: Password to start full compile
/BC: Repository which should be used for full compile
Last parameter is the SRF Name
Now to automate the running of this batch file. The steps are valid for Windows 2000 OS
- Goto Control Panel > Scheduled Tasks
- Double click on Add Scheduled Tasks
- Click > Next. (You will see the window shown below)

- Click > Browse (Select the batch file you have created)
- Click > Next and then select Daily Option and Click Next
- Select the Time at which you want to start he full compile
- Click Next and provide the password and confirm password for username you use to login to Windows OS
- Click > Next and then Click > Finish
This full compile will create SRF in Siebel Tools\Objects\ENU folder.
You will now see a scheduled task created in the control panel. In this way your full compile will always start on time.
To automate on unix or Solaris systems you can create a Shell Script and cron job.


(6 votes, average: 3.83 out of 5)
5 Comments at "How to Automate Siebel Full Compile"
Hi Neel,
I have one question regd Constraint & Hierarchical Picklists. What is the difference between those two and when to go for Constraint and when to go for Hierarchical, which is the best approach if we have three levels of LOV’s [Parent/Child/Grand Child] where Child is constrained based on Parent and Grand Child is constrained based on Child.
How add the the new LOV’s later point of time and will there be any difficulties in later if at all we want to add more LOV’s under Child and Grand Child.
Can you explain me with an example.
Thanks for your time.
Thanks,
Pavan
Hi Neel,
The post is fantastic,It helps us to learn a lot.
I have one doubt.
When I am developing something in my siebel tools(local ) i do compile and test it in the client application(local).
if i want the changes to be reflected in the server i need to do check in and check out.
Please explain me the concept of check in and check out?
What are the things i need to mention to connect the local to server.
For example the DB instances,ODBC all those things?
Explain me this concept clearly.
Thanks in advance.
Regards,
Sail
Neel,
I want to subscribe in siebelunleashed.com and share Siebel knowledge with Siebel professionals. Can you please help regarding this.
I am sorry to send this request to you in the comments for the above post.
I appreciate your help in advance.
Thanks,
Joy
What problem are you facing when you try to subscribe??
“To automate on unix or Solaris systems you can create a Shell Script and cron job.”
Hi Neel, are you sure about this? Please explain if possible.
thx in advance!
Comment Now!