Respository Export

I've always been wondering how complicated is it to do a repository migration. To experience that I decided to do a repository migration myself in my system. To start with the repository export was pretty straight forward. Here are the steps

Enviroment:Windows XP, Oracle 10g ,Siebel
> Created a batch file with the following set of commands
c:cd "C:\sba80\siebsrvr\BIN"repimexp -a e -c siebel -u sadmin -p sadmin -d siebel -f c:\Repository.dat -l c:\repexpimp.log

-a e repository export
-c Database instance
-u sadmin userid
-p sadmin password

Save the file as batch file and click on it.The process will start and export a repository file Repository.dat to C:\ drive .Now the repository needs to be imported to the destination instance and will post the steps for the same in the next blog. L8r

Why Workflows ?

In the last couple of projects I have used more workflow than scripting.Probably scripting has all possible ways to customize siebel application but it's always not the best way to approach. Here are MY reasons why I would not prefer scripting as my first choice for customization.The points listed below are based on what I learnt from Good Siebel folks out there or from siebel knowledge base
> Scripting impacts performance.
Most of the scripting on Business components ,applets and Business service is to create new records or query for existing records to retireve data and all these can be done from the workflow as well. Workflow or workflow policy program would peform better for these..Invoking OOB Business service from workflow always perform better than invoking it from script.
> Deployment
Any change in server side scripting would require a srf deployment and this makes it hard whenever scripting is part of major release. Usually I have seen it take sometime to staibilize big customization or an upgrade. Since workflow is based on XML, it makes small changes deployment to other environment easy.
> Fusion future.
Saw that escripting will be obsolete in Siebel Fusion version and everything will be based on Java Programming. So if you are part of new implementation less scripting would make the client life much easier.

Cons of Workflow
There are few times that you would opt for scripting and here are few reasons to list atleast off the top of my head.
> Cannot retrive the calculated field value from workflow.
>Requirements that needs to create many to many associations. Siebel has the inbuilt PickRecord() method that would establish Many to Many relationship.Same is possible in wokflow as well by having a BC on intersection table and creating the aassociation. But this is not RECOMMENDED by Siebel.
>Some escript or string functions cannot be used on workflows


That's all for now.Rest in next.. Cannot wait to watch the game this week..My favorite is Colts now that Cowboys are out..Let's see.

Siebel Essentials - 4

Wow! we are into year 2010 and was good to see that I have 14 posts in the last year. One of my resolutions for this year is to post more regularly . Let me list the resolutions for this year.
-Blog more regularly
-Less TV more books.Ok I hesitated before writing this but would be a hard one.
-Learn swimming
Ok that's a pretty short list , let me see if I keep up to my few resolutions. Getting back to basics in Siebel

There was a requirement to display My Teams view on home page. When queried on supportweb it was listed as Product enhancements. Spent sometime to see if I can find a workaround in tools.There is a visibility over ride property for applets on View Web Template Items. Changed this to Manager and that seems to work . When Sales rep logs in they see My View but when a Manager logs in they see My Team's view on the homepage. So far so good but if it did break some thing will update here for the same. L8r