This document would assist the user to export the Siebel data base dump from one environment and import the same into another environment. The source and target database server have Oracle as their databases.
Exporting siebel database from source DB server environment:
Connect to the source DB server as oracle user.
[oracle@celbssdb6 ~]$ expdp system/password@DBname schemas=SIEBEL dumpfile=SBL_DEV_ddmmyyyy.dmp logfile=exp_SBL_DEV_ddmmyyyy.log compression=ALL parallel=4&
<The user need not specify the system password in the expdp command. Without password when the command is run, it would prompt the user to enter the system password>
Copy the DB dump file to the target DB server environment:
scp the file to target DB server as oracle user to the path /app/oracle/admin/<DBname>/<folder>
Connect to sqlplus on the target DB server as the user system.
Run the query
SQL> select * from siebel.dba_directories where directory_name=’DATA_PUMP_DIR’;
SQL>drop user SIEBEL cascade;
Drop the user siebel only if the table space and index space on the source and target environment are same.
And re-create it again:
DROP USER SIEBEL CASCADE;
CREATE USER SIEBEL
IDENTIFIED BY <password>
DEFAULT TABLESPACE SIEBEL_DATA
TEMPORARY TABLESPACE TEMP
— 4 Roles for SIEBEL
GRANT SELECT_CATALOG_ROLE TO SIEBEL;
GRANT SCHEDULER_ADMIN TO SIEBEL;
GRANT SSE_ROLE TO SIEBEL;
GRANT TBLO_ROLE TO SIEBEL;
ALTER USER SIEBEL DEFAULT ROLE ALL;
— 2 Tablespace Quotas for SIEBEL
ALTER USER SIEBEL QUOTA UNLIMITED ON SIEBEL_DATA;
ALTER USER SIEBEL QUOTA UNLIMITED ON SIEBEL_INDEX;
Stop the siebel server, gateway server and SWSE on the target environment.
Import the database dump file on the target DB server as oracle user.
impdp system/password@DBname schemas=SIEBEL dumpfile=SBL_DEV_ddmmyyyy.dmp logfile=imp_SBL_DEV_ddmmyyyy.log parallel=4
<The user need not specify the system password in the imppdp command. Without password when the command is run, it would prompt the user to enter the system password>
After DB import change the password of SIEBEL user to the original password in the target environment. If the password for the SIEBEL is same for both source and target DB server then leave it.
Start the SWSE, gateway and siebel servers on the target environment.
Run a full compile on the target environment and deploy the SRF & generate browser scripts.
Verify the database updates and changes in the target environment.
The client configuration file, such as eapps.cfg, must be changed depending on the type of load balancer being used.
In the release version, the installer and config wizard will prompt the user for the necessary parameters and add them to eapps.cfg. If the config wizard is not used, these parameters must be made manually.
There are three mutually exclusive options for load balancing that may be configured on the client. The options are no load balancing, native load balancing, and third party load balancing.
No load balancer
If using only one server, it may be less work to configure the SWSE client to use no load balancer. The only thing that may need to be modified is the connect strings in eapps.cfg so that the SCBroker listening port is referenced.
The format of the connect string is as follows:
ConnectString = siebel://<hostname>:<SCBroker port>/<enterprise> /<component>
SCBroker port, which defaults to 2321, can be verified by running the following srvrmgr command:
srvrmgr> list param portnumber for comp scbroker show PA_VALUE
Example change for eapps.cfg
ConnectString = siebel://HOSTNAMENAME:2321/siebel/SSEObjMgr_enu
Native load balancer
To use the native round robin load balancing provided by the Siebel session manager, there are 3 changes that must be made.
1. Modify [ConnMgmt] section of eapps.cfg
Create a new section in eapps.cfg called [ConnMgmt]. To enable round robin load balancing, the variables listed in the following table must be set.
[ConnMgmt] variables for round robin load balancing
|Variable name||Acceptable values||Description|
|EnableVirtualHosts||true or false||EnableVirtualHosts is used to enable internal load balancing. A value of true means that the Client has enabled Session Manager based load balancing.|
|VirtualHostsFile||path to LB config||VirtualHostsFile contains the Session manager load balancing configuration file. This file describes virtual server to host mapping|
Example change for eapps.cfg
2. Create virtual hosts file
The load balancer parses a file containing a mapping of virtual servers to hosts.
Each line of VirtualHostsFile must be in the following format:
Details on creating the virtual hosts file
- The first value of each host declaration (server ID) can be determined by running the following srvrmgr command:srvrmgr> list server show SBLSRVR_NAME, SV_SRVRID
- The third value of each host declaration (SCBroker listening port) can be determined by running the following srvrmgr command:srvrmgr> list param portnumber for comp scbroker show PA_VALUE
- Each virtual host declaration should be specified on one line. Each line will be parsed as a separate virtual host.
- A line starting with “#” is ignored.
- If the file has syntax errors and is unable to be parsed, there will be a corresponding error in the client log file after the first connect attempt has been made, and users will not be able to connect to any components through the Web server.
Example load balancer config file (lbconfig.txt)
# Sample session manager load balancing file.
# Format: each line has the format of
3. Modify connect strings in eapps.cfg with virtual hosts
The connect strings in eapps.cfg must be changed to refer to the virtual servers in VirtualHostsFile.
Example change of connect strings in eapp.cfg
ConnectString = siebel://SalesVserver/siebel/SSEObjMgr_enu
ConnectString = siebel://CallCenterVserver/siebel/SCCObjMgr_enu
Upon making these changes to eapp.cfg, the Web server should be restarted.
Third party load balancer
To use a third party load balancer, such as Resonate, first configure the scheduling rules in the third party load balancer, using the appropriate third party configuration tools. Next, modify the connect strings eapps.cfg to reference the virtual IP and virtual port.
For example, if using the Sales application with virtual IP 172.20.74.100 and virtual port 2512, modify eapps.cfg to contain the following:
Example change for eapps.cfg
ConnectString = siebel://172.20.74.100:2512/siebel/SSEObjMgr_enu
After these changes, browser clients can simply connect to
http://<web server hostname>/sales_enu and the load balancer will route the request to an available OM.
Third party load balancer server configuration
When using a third party load balancer, 3 types of rules must be configured for each component:
|Rule type||Rule format||Use of the rule|
|Connect||*/<enterprise>/<component>||Initial connect from the client (SWSE) to the Siebel server|
|Reconnect||*/<enterprise>/<component>/!<server ID>.*||Reconnect to the server where the session was initially established, in case of disconnect or errors.|
|Round robin||*/<enterprise>/<component>/RR||To enable the client to choose another OM process to connect to in case the initial connect fails.|
The same virtual port should be used for each rule, and the physical port for each rule is the listening port of the SCBroker component.
The procedure for configuring the rules in the third party load balancer is as follows:
- Use srvrmgr to connect to the server. Run the following command to determine the SCBroker listening port:srvrmgr> list param portnumber for comp scbroker show PA_VALUE
In this case, the port is 2321. This will be the physical port used for the rules.
- Use srvrmgr to determine the server IDs of the servers for which scheduling rules will be registered.srvrmgr> list server show SBLSRVR_NAME, SV_SRVRID
- Choose an unused port to use as the virtual port, such as 2512.
- Use the appropriate third party load balancer configuration tool to create the scheduling rules. In the Resonate case, use CDAction or DispatchManager can be used.
Suppose the server is to be configured with CallCenter. We already have determined the following using the steps above:
- SCBroker is listing on port 2512
- Srvr1 has server ID 3 and is running on physical host “host1”
- Srvr2 has server ID 5 and is running on physical host “host2”
Suppose we also know:
- The virtual IP for our load balancer is 220.127.116.11, and the virtual port is 2512
Then for the current example, the following rules would need to be registered:
|*/siebel/sccobjmgr_enu||18.104.22.168||2512||host1||2321||Connect rule for srvr1|
|*/siebel/sccobjmgr_enu||22.214.171.124||2512||host2||2321||Connect rule for srvr2|
|*/siebel/sccobjmgr_enu/RR||126.96.36.199||2512||host1||2321||Round robin rule for srvr1|
|*/siebel/sccobjmgr_enu/RR||188.8.131.52||2512||host2||2321||Round robin rule for srvr1|
|*/siebel/sccobjmgr_enu/!3.*||184.108.40.206||2512||host1||2321||Reconnect rule for srvr1|
|*/siebel/sccobjmgr_enu/!5.*||220.127.116.11||2512||host2||2321||Reconnect rule for srvr2|
Once these rules have been registered and the connect strings in eapps.cfg have been modified to use the VIP and VPort, the configuration is done.
Server parameters for SCBroker
In Siebel 7.7 there is a new system component called SCBroker, which will be started along with server. If this component does not start, clients will not be able to connect to any OM processes. The SCBroker has a number of associated parameters which can be configured.
Component parameters for SCBroker
|Parameter name||Description||Default value|
|DfltTasks||Default number of service tasks to start||2|
|MaxTasks||Maximum number of running tasks for a service||2|
|PortNumber||Static TCP/IP port number used by the service or the Siebel Connection Broker||2321|
|AutoRestart||This component is restartable automatically||True|
New server parameters for SCBroker
|Parameter name||Description||Default value|
|ConnectionTimeout||Incoming connection timeout (msec)||500|
|TransferTimeout||Connection Transfer timeout (msec)||500|
SCBroker events can be traced by setting the “SCBroker” event. For example, in srvrmgr:
srvrmgr > change evtloglvl SCBroker=4 for comp scbroker