How to Pre-Configure Siebel/Siebel DB Diagnostics

This task describes the pre-configuration steps to be performed by the ALM administrator which allow the performance tester to enable and run Siebel diagnostics.

1. Prerequisite

   Make sure that the ERP/CRM mediator is installed and configured. For more information, see How to Add ERP/CRM Mediators.

2. If connecting to a UNIX server with a remote shell (RSH/RCP) connection

   • Verify that the RSH and RCP daemons are running on the UNIX server.

   • Verify that the UNIX user has permission to run remote shell commands. To check this, type the following at the DOS command prompt:

     rsh <server machine name> -l <UNIX user login name> -n <command>

     Example:

     rsh my_unix -l my_name -n "cd ~;pwd"

     Note: You can use only RSH commands that work from the DOS command prompt window.

   • Verify that no output is generated after executing the RSH command.

     Note: You should not generate output from the .login, .profile, and .cshrc files (for example, by echo, or in any other way, including commands that generate output indirectly, such as biff). Where an existing user generates output in the RSH step that cannot be deleted, you should create a new user that does not generate output, and who has permissions to run RSH and RCP commands on the server machine.

3. Configure the server machine to enable diagnostics

   To configure Siebel application and Web servers for diagnostics data collection:

   1. Enable Siebel Diagnostics on all Siebel application and Web servers involved in the test.

      Set the environment variable on the Siebel server to:

      SIEBEL_SarmEnabled=true 
      

      Then restart the server.

   2. Optimize the server performance settings.

      You change the maximum memory caching and file size using the following variables:

      SIEBEL_SarmMaxMemory= <bytes>SIEBEL_SarmMaxFileSize = <bytes>

      The SIEBEL_SarmMaxMemory value controls the size of the buffer that Siebel keeps in the memory before writing the information to the Siebel log files. You can improve server performance by increasing the parameter value. However, information from the end of the run will be missing from the Analysis graphs.

      We recommend the following settings:

      • SIEBEL_SarmMaxMemory

        Value	Number of Vusers
        5000	Less than 20 (low loads)
        1000000	More than 100 (high loads)

      • SIEBEL_SarmMaxFileSize

        Value	Number of Vusers
        5000000	Less than 20 (low loads)
        25000000	More than 100 (high loads)

      If more than one Siebel log file is generated on the server every 10 seconds, you should increase the SIEBEL_SarmMaxFileSize.

   3. Generate a list of Siebel Server IDs.

      On the Siebel server, open a command window and run the following command:

      <Siebel bin directory>\srvrmgr /u <username> /p <password> /g <gateway server> /e <entrpr server> /c "list servers show SBLSRVR_NAME, SV_SRVRID"

      where:

      /u <username> is the server administrator username.

      /p <password> is the server administrator password.

      /g <gateway server> is the gateway server address.

      /e <entrpr server> is the enterprise server name.

      /c <command> is the execute a single command.

      This command generates a list of all the Siebel application servers and their IDs. Keep a record of the server IDs, since this information is required in the Siebel Server Configuration dialog box.

4. Copy files from the Siebel Application Server to the Mediator

   After configuring the application server, copy the files listed below from the Siebel Application server \bin directory to either the <Mediator Root>\bin directory, <Windows>\System32 directory, or any other directory in PATH on the Mediator machine:

   For Siebel 7.53, copy the following files:

   sarmanalyzer.exe sslcver.dll sslcsym.dll

   sslcshar.dll sslcosa.dll

   For Siebel 7.7, copy the following files:

   sarmanalyzer.exe libarm.dll msvcp70.dll msvcr70.dll sslcacln.dll sslccore.dll sslcevt.dll sslcos.dll

   sslcosa.dll sslcosd.dll sslcrsa.dll sslcscr.dll sslcshar.dll sslcsrd.dll sslcsym.dll sslcver.dll

5. Synchronize clocks

   • On Windows Siebel Servers: Ensure that all the machines' clocks in the Siebel system are synchronized. This ensures that the correlation of SQLs to transactions is correct.

     Synchronize the Siebel Gateway and load generators' clocks by running the following command from the load generator:

     net time \ <Gateway name> /set /y

     Replace <Gateway name> with the name of the Siebel Gateway.

   • On Unix Siebel Servers: Ensure that all the machines' clocks in the Siebel system are synchronized. This ensures that the correlation of SQLs to transactions is correct.

     You can synchronize the clocks on a UNIX system in one of the following ways:

     • Use the date command on the UNIX Siebel Gateway server to change the time manually, so it will be synchronized with the Load Generator's clock.

     • Change the time on the load generator so that it will be synchronized with the UNIX Siebel Gateway server.

     • Configure the time difference in Analysis. For more information, see the chapter about Siebel DB Diagnostics Graphs in the HPE LoadRunner Analysis User Guide.

6. (Siebel DB) Enable logging on the Siebel Server

   For task details, see How to Enable and Disable Logging on the Siebel Server.