Siebel Installations >  Deploy new release to an existing Siebel environment

This explains how to deploy a new development release in an existing environment

Importing repository

cd /folder_where_siebel_is_installed/siebel/8.1/siebsrvr 

. ./siebenv.sh

cd /folder_where_siebel_is_installed/siebel/8.1/siebsrvr/bin

repimexp /A I /G ALL /K Y /u sadmin /p password /d SIEBEL /c SIEBELSERVER_DSN /F /folder_where_repository_file_iskept/repository.dat /R "Siebel Repository new" /L /folder_where_siebel_is_installed/siebel/8.1/siebsrvr/log/imprep/output/imprep_prim.log

to run it in nohup

nohup repimexp /A I /G ALL /K Y /u sadmin /p password /d SIEBEL /c SIEBELSERVER_DSN /F /folder_where_repository_file_iskept/repository.dat /R "Siebel Repository new" /L /folder_where_siebel_is_installed/siebel/8.1/siebsrvr/log/imprep/output/imprep_prim.log &

to check nohup type tail -f nohup.out

after the repository import completes

cd /folder_where_siebel_is_installed/siebel/8.1/siebsrvr

. ./siebenv.sh

and then more nohup.out
nohup.out will be created in the folder where you typed the nohup command.

Gateway Server backup
cd /folder_where_siebel_gateway_is_installed/siebel/8.1/siebsrvr 

. ./siebenv.sh
go to the bin folder
/folder_where_siebel_gateway_is_installed/siebel/8.1/siebsrvr/bin

srvrmgr /g I.P.:2320 /u SADMIN /p password /e SIEBEL_ENTERPRISE_SERVERNAME
backup nameserver backup_gateway_versionname
the format for gateway backup is backup nameserver backup_gateway_<date>

Stop Siebel servers
cd /folder_where_siebel_is_installed/siebel/8.1/siebsrvr

. ./siebenv.sh

stop the servers in any order

./stop_server -r /folder_where_siebel_gateway_is_installed/siebel/8.1/siebsrvr -e SIEBEL_ENTERPRISE_SERVERNAME

Repository change
Siebel TOOLS Uat - change and rename "Siebel Repository new" to “Siebel Repository”and inactive old (rename old Siebel Repositiry to Siebel Repository V xx)
The last and active repository should be named "Siebel Repository". In the comments section,add the version

DDLSync
This step is needed if the database structure has been changed, this step may be optional

cd /folder_where_siebel_is_installed/siebel/8.1/siebsrvr/bin
srvrupgwiz /m master_ddlsync.ucf

DDLsynch updates for all servers, the ddl sync
While DDL sync is running, you can copy browser scripts to the web server.

SRF Update

chmod +w /folder_where_siebel_is_installed/siebel/8.1/siebsrvr/objects/enu/siebel_sia.srf
cp /new_srf_folder/siebel_sia.srf /folder_where_siebel_is_installed/siebel/8.1/siebsrvr/objects/enu/siebel_sia.srf
chmod -w /folder_where_siebel_is_installed/siebel/8.1/siebsrvr/objects/enu/siebel_sia.srf

Repeat this for all servers which contain active SRFs

Copy Browser Scripts

Browser scripts are normally kept where the web server is installed.

It just means that any new files provided are copied in this folder or the whole set of scripts
are replaced (overwrite)

After this is done, start the server

Starting Siebel Servers
This should be done from the bin directory /folder_where_siebel_is_installed/siebel/8.1/siebsrvr/bin
Remember to load siebenv.sh before doing this

./start_server -r /folder_where_siebel_is_installed/siebel/8.1/siebsrvr -e SIEBEL_ENTERPRISE_SERVERNAME -L ENU -g i.p. SIEBEL_ENTERPRISE_SERVERNAME
start all the siebel servers

After the command is run, it still takes some time for the Siebel server to actually function.
Keep checking on both servers using ps –ef | grep Siebel
There should be between 2 to 4 processes of Siebel running. This is when the server is actually up.
Try prstat command. The memory usage will go up slowly and then come down. When it is below 2 % try to log in