I recently received the following information and wanted to pass this along.

Build Forge has no pre-built automation for Siebel environments, but is capable of running existing Siebel and operating system commands to automate this type of environment.

Using a version control system, such as Rational Team Concert, Build Forge can backup existing Siebel configurations so that redeployments and existing "SRF" files are backed up. Using a performance testing tool, such as Rational Performance tester, Build Forge can load test the newly deployed Siebel configuration.

Here is an example script to use in Build Forge to migrate Siebel SRF configurations:

#! /bin/ksh

echo "Please Enter SRF Name: \c"

read SRFName



cd siebel/siebsrvr

. ./siebenv.sh

echo "Siebel Enviornment Set Successfully"

SRFNewName=`date +%m_%d_%y_%H`



echo "Stopping Server"

stop_server all





cd objects/enu



# /u/dailysrf is the path where we use to upload SRF. copy file from this path to objects folder



cp /u/dailysrf/$SRFName .



if [[ $? -ne 0 ]]

then

echo "Error while copying $SRFName. Exiting Script"

exit 1

else

echo "File Copied Successfully"

fi



echo "Swapping Files....."

mv siebel_sia.srf FC_$SRFNewName.srf

mv $SRFName siebel_sia.srf





if [[ $? -ne 0 ]]

then

echo "Error While Swapping File\n"

exit 1

else

echo "File Swapping Complete.....\n"

fi



echo "Starting Server ...."

start_server all



echo "Generating Browser Script...."

genbscript /sea77/siebel/siebsrvr/bin/enu/fins.cfg /sea77/siebel/sweapp/public/enu



if [[ $? -ne 0 ]]

then

echo "Error in generating Browser Script"

exit 1

else

echo "Browser Script generated successfully"

fi