Zero downtime Siebel SRF Migration

Hi Guys,

Tapan is back with more useful stuff. Today he is talking about procedure to change SRF without restarting Siebel server or as the title of the post said Zero downtime SRF Migration.

(This is quite enlightening, even I didn’t knew that It was possible)


Here are the steps to migrate SRF without bouncing the servers:

1.  Copy the new .srf in the <Siebel server>/ object/<language> directory.

2.  Using a Siebel Web Client, Navigate to Site Map > Server Administration > Enterprise Configuration.
administrationserverconfiguration

3. Click the Component Definitions view tab.
 servercomponenttab

4. In the Component Definitions list applet (top applet), select the Object Manager you want to reconfigure.
serverobjectmanager
 
 5. Click the menu button in the Component Definitions list applet (the top Applet) and then Start Reconfiguration the Object Manager definition. State field will change to Reconfiguring.
serverstartconfiguration
 
6. In the Component Definitions parameters list applet (the lower applet), change the Application Repository File parameter to the new repository file name.
serversrfname
 
7. Commit the new configuration by clicking the menu button in the Component Definitions list applet (the top applet) and then “Commit Reconfiguration”. The new parameter values will be merged at the enterprise level. To cancel the reconfiguration before it has been committed, click the menu button and then Cancel Reconfiguration.
servercommitconfiguration
 
That’s it, now new users logging in to the application will use the new .srf file. Existing users will
continue to use the old .srf file until they log in again.

49 Responses to Zero downtime Siebel SRF Migration

  1. Very nice Article!
    Just a question.
    In the Component Definitions parameters list applet, I can’t find the Application Repository File parameter.

    I remember that some parameters are hidden,
    and there is a parameter to show them.

    Can you help me?

    Thank you

  2. Very nice Article!
    Just a question.
    In the Component Definitions parameters list applet, I can’t find the Application Repository File parameter.

    I remember that some parameters are hidden,
    and there is a parameter to show them.

    Can you help me?

    Thank you

  3. Very nice Article!
    Just a question.
    In the Component Definitions parameters list applet, I can’t find the Application Repository File parameter.

    I remember that some parameters are hidden,
    and there is a parameter to show them.

    Can you help me?

    Thank you

  4. The “Application Repository File” parameter is no longer available in Siebel version 7.8. This has become a hidden parameter; however it is still available in the siebns.dat file.

    In order to change the SRF file using the zero downtime feature in Siebel version 7.8, the “Application Repository File” parameter needs to be changed using the Server Manager command line Utility:

    srvrmgr> reconfig compdef
    Command completed successfully.

    srvrmgr > change parameter CFGRepositoryFile= for compdef
    Command completed successfully.

    srvrmgr > commit reconfig compdef
    Command completed successfully.

  5. The “Application Repository File” parameter is no longer available in Siebel version 7.8. This has become a hidden parameter; however it is still available in the siebns.dat file.

    In order to change the SRF file using the zero downtime feature in Siebel version 7.8, the “Application Repository File” parameter needs to be changed using the Server Manager command line Utility:

    srvrmgr> reconfig compdef
    Command completed successfully.

    srvrmgr > change parameter CFGRepositoryFile= for compdef
    Command completed successfully.

    srvrmgr > commit reconfig compdef
    Command completed successfully.

  6. The “Application Repository File” parameter is no longer available in Siebel version 7.8. This has become a hidden parameter; however it is still available in the siebns.dat file.

    In order to change the SRF file using the zero downtime feature in Siebel version 7.8, the “Application Repository File” parameter needs to be changed using the Server Manager command line Utility:

    srvrmgr> reconfig compdef
    Command completed successfully.

    srvrmgr > change parameter CFGRepositoryFile= for compdef
    Command completed successfully.

    srvrmgr > commit reconfig compdef
    Command completed successfully.

  7. Hi all,
    This limitation is limited only to Siebel SBA version, not to SIA versions. This parameter is present in the OM in SIA…

    Reg,
    Ashish

  8. Hi all,
    This limitation is limited only to Siebel SBA version, not to SIA versions. This parameter is present in the OM in SIA…

    Reg,
    Ashish

  9. Hi all,
    This limitation is limited only to Siebel SBA version, not to SIA versions. This parameter is present in the OM in SIA…

    Reg,
    Ashish

  10. Thank you very mutch Tapan.
    Ill’try this procedure as soon as possible in our pre production enviroment.

    bye 😉

  11. Thank you very mutch Tapan.
    Ill’try this procedure as soon as possible in our pre production enviroment.

    bye 😉

  12. Thank you very mutch Tapan.
    Ill’try this procedure as soon as possible in our pre production enviroment.

    bye 😉

  13. Hi,
    I have 9 servers in ly prod environment. Is there any way to change the srfs simulatanesouly in all the machine without a downtime?

  14. Hi,
    I have 9 servers in ly prod environment. Is there any way to change the srfs simulatanesouly in all the machine without a downtime?

  15. Hi,
    I have 9 servers in ly prod environment. Is there any way to change the srfs simulatanesouly in all the machine without a downtime?

  16. Hi Binesh,

    As per your requirement, You want to change the SRF’s on 9 servers simultaneously without a downtime.
    I am not sure that this is the right way but what you can do is create a batch file for each server and shedule them as per your time slot available.

    This Batch file will enable you to do the task without any downtime.

    I haven’t worked upon this scenario and not sure about it either, but as per my understanding it should work.

  17. Hi Binesh,

    As per your requirement, You want to change the SRF’s on 9 servers simultaneously without a downtime.
    I am not sure that this is the right way but what you can do is create a batch file for each server and shedule them as per your time slot available.

    This Batch file will enable you to do the task without any downtime.

    I haven’t worked upon this scenario and not sure about it either, but as per my understanding it should work.

  18. Hi Tapan, this is really a nice solution from Siebel, i’ve used a lot in my last job. There is only one downturn you have to keep in mind, after you Commit Reconfiguration all the request will be served by a new OM, but the existing connections will still be alive using the old OM (and SRF file). This will increase the amount of memory the server will use until all the older sessions are terminated by logoff or timeout. In certain cases (with frequent new logins every minute >100 logins), i’ve seen the amount of memory needed to double.

    Regards,
    Diogo

  19. Hi Tapan, this is really a nice solution from Siebel, i’ve used a lot in my last job. There is only one downturn you have to keep in mind, after you Commit Reconfiguration all the request will be served by a new OM, but the existing connections will still be alive using the old OM (and SRF file). This will increase the amount of memory the server will use until all the older sessions are terminated by logoff or timeout. In certain cases (with frequent new logins every minute >100 logins), i’ve seen the amount of memory needed to double.

    Regards,
    Diogo

  20. Guys,

    Just thought of a question what if we have changes that is based on repository as well. For example a workflow policy column or a new Workflow process which expects the changes to be in repository no in srf. Once we import our new repository should we bring down the server to rename the repository?

  21. Guys,

    Just thought of a question what if we have changes that is based on repository as well. For example a workflow policy column or a new Workflow process which expects the changes to be in repository no in srf. Once we import our new repository should we bring down the server to rename the repository?

  22. I all,

    This available at the Siebel Support Web, but very this post is very well explained, better than the one on the SupportWeb.

    I have a question for all you guys. After the SRF is changed and if we need to generate and change the browser Scripts? Don’t we have to bounce the servers?

    Many thanks

    Jose

  23. I all,

    This available at the Siebel Support Web, but very this post is very well explained, better than the one on the SupportWeb.

    I have a question for all you guys. After the SRF is changed and if we need to generate and change the browser Scripts? Don’t we have to bounce the servers?

    Many thanks

    Jose

  24. Dear Tapan,

    We are on siebel 8.0 (SIA – Ver 8.0.0.5)

    1. I went to /siebsrvr/objects/enu, I overwrote the “siebel_sia.srf” file with the latest SRF file – “siebel_sia.srf”

    2. Then did the “Start Reconfiguration” of the Object Manager definition (Compdef) and then did “Commit Reconfiguration”+.

    This did not reflect the latest changes of the SRF in the thin client.

    I also tried with a different SRF file name “siebel_sia_test.srf” under compdef parameters

    Also put the same name under Compdef – Parameters (CFGRepositoryFile= siebel_sia_test.srf)…

    This also did not help.

    Let me know if you have the exact steps to deploy the SRF without any downtime – ie., without bringing down the siebel enterprise.

    Regards

    Jacob.

  25. Dear Tapan,

    We are on siebel 8.0 (SIA – Ver 8.0.0.5)

    1. I went to /siebsrvr/objects/enu, I overwrote the “siebel_sia.srf” file with the latest SRF file – “siebel_sia.srf”

    2. Then did the “Start Reconfiguration” of the Object Manager definition (Compdef) and then did “Commit Reconfiguration”+.

    This did not reflect the latest changes of the SRF in the thin client.

    I also tried with a different SRF file name “siebel_sia_test.srf” under compdef parameters

    Also put the same name under Compdef – Parameters (CFGRepositoryFile= siebel_sia_test.srf)…

    This also did not help.

    Let me know if you have the exact steps to deploy the SRF without any downtime – ie., without bringing down the siebel enterprise.

    Regards

    Jacob.

  26. Hi Tapan et al,

    I am using siebel 7.7 and i could see that we have other workflow components as well which use the SRF file and not just the object manager. So in that case we would have to take care of all such components and not only the object manager isnt it?

    Please let me know your views on this please…

  27. Hi Tapan et al,

    I am using siebel 7.7 and i could see that we have other workflow components as well which use the SRF file and not just the object manager. So in that case we would have to take care of all such components and not only the object manager isnt it?

    Please let me know your views on this please…

  28. Hi,

    Sorry for Late Reply guys,

    Jose: No you do not have to bounce the siebel services to generate or change Browser script.

    If i am not wrong, We here are talking about the GenB.

    Please correct if i am wrong.

    Jacob: I tried the Same on 8.1.1 due to unavailibilty of 8.0 by following the same steps and it seems to be working fine with me.
    Please let me know what exact steps are you following.

    Nimish: Vanilla component like Workflow Process manager generally use the default SRF file siebel.srf file, If their is something specific, Yes we do need to change the parameter explicitely for each of them.

    It would be great if Neel or someone can put some light on it with better solution.

    Thanks,
    Tapan

  29. Hi,

    Sorry for Late Reply guys,

    Jose: No you do not have to bounce the siebel services to generate or change Browser script.

    If i am not wrong, We here are talking about the GenB.

    Please correct if i am wrong.

    Jacob: I tried the Same on 8.1.1 due to unavailibilty of 8.0 by following the same steps and it seems to be working fine with me.
    Please let me know what exact steps are you following.

    Nimish: Vanilla component like Workflow Process manager generally use the default SRF file siebel.srf file, If their is something specific, Yes we do need to change the parameter explicitely for each of them.

    It would be great if Neel or someone can put some light on it with better solution.

    Thanks,
    Tapan

  30. Hi All

    Tapan

    Yes, it’s genbscript. My version is 7.5.3.16.

    What is the process? Change the SRF as explained in the beginning of this Post. Generate the BS and the Component starts to use the new ones? No need to bounce the Siebel Server or the IIS?

    If it’s that simple, then will be implementing this process at my company. It works also for the eCommunications comp.?

    Many thanks, best regards,

    Jose Ramos

  31. Hi All

    Tapan

    Yes, it’s genbscript. My version is 7.5.3.16.

    What is the process? Change the SRF as explained in the beginning of this Post. Generate the BS and the Component starts to use the new ones? No need to bounce the Siebel Server or the IIS?

    If it’s that simple, then will be implementing this process at my company. It works also for the eCommunications comp.?

    Many thanks, best regards,

    Jose Ramos

  32. Hi Jose,

    After changing the SRF, Just what you need to do is double click the Batch file and work Done.

    The Batch Script that would work is given below.

    A sample GenB Script Batch file creation process:

    1) Open a notepad.
    2) COpy the following script in it.

    ::******************* Genb Script *********************

    ::*****rem this calls the genb script********

    call SIEBEL_ROOT_DIRsiebsrvrbingenbscript.exe “SIEBEL_ROOT_DIRsiebsrvrbinenusiebel.cfg” SIEBEL_ROOT_DIRSWEApppublicenu ENU

    echo “GenB Complete”

    pause

    3) Save the file as “GenB.bat” or any other name on the server mahcine where the OM is installed.

    This process automatically generate your required BS Script at webserver folder(SWEApppublicenu ).

    Yes it works for eCommunications comp, infact for all the application object managers.

    Please let me know if this does not work because i had tried it numerous number of times.

    Thanks,
    Tapan

  33. Hi Jose,

    After changing the SRF, Just what you need to do is double click the Batch file and work Done.

    The Batch Script that would work is given below.

    A sample GenB Script Batch file creation process:

    1) Open a notepad.
    2) COpy the following script in it.

    ::******************* Genb Script *********************

    ::*****rem this calls the genb script********

    call SIEBEL_ROOT_DIR\siebsrvr\bin\genbscript.exe “SIEBEL_ROOT_DIR\siebsrvr\bin\enu\siebel.cfg” SIEBEL_ROOT_DIR\SWEApp\public\enu ENU

    echo “GenB Complete”

    pause

    3) Save the file as “GenB.bat” or any other name on the server mahcine where the OM is installed.

    This process automatically generate your required BS Script at webserver folder(SWEApp\public\enu ).

    Yes it works for eCommunications comp, infact for all the application object managers.

    Please let me know if this does not work because i had tried it numerous number of times.

    Thanks,
    Tapan

  34. I know this is a very old post but curious about something before I shoot myself in the foot.. Can I do this on the Object Manager I’m logged in with? for instance I’m using Public Sector 8.2.. if I click on “start reconfigure” on the public sector object manager.. what will happen? will I get logged out? will I be able to get back in? Just don’t want to screw myself up..

    thanks!

    • Hi Gpinkham,

      Yes you can reconfigure the OM that u r currently using, The only thing to consider is, untill you log out of the current application session you would be still using the old session or say old srf, once you logout and login into the application again you can than use the latest SRF in the new session.

      I havent tested the same scenario myself, but this would definately work.

      Regards,
      Tapan

  35. There is downside of it, siebel OM crash on Reconfiguration at least in 8.1 as I know. Also one should remember to do this reconfiguration on  every component in siebel server across all siebel servers, like EAI, WF etc..

Leave a Reply

Contribute