Configuring Siebel Diagnostics - LoadRunner

Siebel Diagnostics (Siebel Application Response Measurements) supports Siebel application servers version 7.53.
To generate Siebel transaction breakdown data, perform the following:

  • Configure Siebel Diagnostics on the Application and Web Servers
  • Configure Diagnostics (where the Web Server is Inside a DMZ)
  • Copy files from the Siebel server to the ERP/CRM Mediator machine
  • Set Up Siebel Diagnostics from the Controller
  • Enable Siebel Diagnostics from the Controlle
  • Run the Load Tests
  • View Diagnostics Results

Configuring Siebel Diagnostics on the Application and Web Servers

To configure Siebel Application and Web servers for transaction breakdown, you perform the following:

  • enable Siebel diagnostics on all Siebel Application and Web servers involved in the load test
  • optimize server performance settings
  • generate a list of Siebel server IDs (required for Siebel Application servers only)

To enable Siebel diagnostics:

  1. Set the environment variable on the Siebel server to: SIEBEL_SarmEnabled=true
  2. Restart the server.

To optimize server performance:

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

SIEBEL_SarmMaxMemory controls the size of the buffer that Siebel keeps in the memory before writing the information to theSiebel 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 setting SIEBEL_SarmMaxMemory= 50000 for low loads on the server and SIEBEL_SarmMaxMemory= 1000000 for high loads on the server. A low load on the server is 20 Vusers or less, and a high load is more than 100 Vusers.

The recommended file size for SIEBEL_SarmMaxFileSize is from 5000000 for low loads on the server to 25000000 for high loads on the server. If more than one Siebel log file is generated on the server every 10 seconds, you should increase the SIEBEL_SarmMaxFileSize.

Note: Before running a load test, delete Siebel diagnostics logs from all servers involved in the load test.

To generate Siebel Server IDs:

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

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.

Configuring Diagnostics where the Web Server is Inside a DMZ

If you are using an application server in the internal network and a Web (file) server in a DMZ (a "neutral zone" that separates an internal network from a public one that is used to prevent outside access to a company’s private data), you must install the mediator on the internal (over firewall) LAN, and enable SMB/CIFS communication from the internal machine to the file server in the DMZ. SMB/CIFS are the file sharing services that use the NBT (NetBIOS over TCP/IP) as the transport protocol. To enable the NBT protocol between the client (over firewall machine) and the file server, use the following port configuration:

onfiguring Diagnostics where the Web Server is Inside a DMZ

For example, configure the firewall settings as follows:
Service enabled: "nbsession" for TCP 139 connection.
Service enabled: "Microsoft-ds" for TCP 445 connection.

Note: CIFS over TCP 445 (direct SMB over TCP/IP) is optional with Windows 2000 and above(since it is a more secure way of communicating with the file server). To enable CIFS over TCP/IP, you must disable the NetBIOS over TCP/IP protocol using the operating system configuration.

Copying Files from the Siebel Application Server to the Mediator

After configuring the application server, you need to copy the files listed below from the Siebel Application server bin directory to either the <LR mediator installation>bin directory, <Windows>System32 directory, or any other directory in PATH on the Siebel mediator machine:

  • sarmanalyzer.exe
  • sslcver.dll
  • sslcsym.dll
  • sslcshar.dll
  • sslcosa.dll

Setting Up the Siebel Diagnostics Module

To generate transaction breakdown data, you set up the Siebel Diagnostics module to communicate with the mediator machine and define the servers that you want to monitor. You can then enable the diagnostics module and specify the sampling percentage of transaction data to include in the diagnostics graphs, as described in “Enabling Diagnostics”.

Note: The settings that you configure are per scenario. All scripts in the scenario will run under the same diagnostics configuration.

To set up the Siebel Diagnostics module:

  1. From the Controller menu, choose Diagnostics > Configuration > Siebel.The Siebel Configuration dialog box opens.

    To set up the Siebel Diagnostics module

  2. Enter the Mediator information as described in “Understanding the Siebel Configuration Dialog Box” .
  3. If you are monitoring over a firewall, select Enable Firewall and enter the name or IP address of the Mercury listener machine.
  4. To test the connection between the Controller and the mediator, click Test Connection. The Siebel Diagnostics module attempts to connect to the mediator.
    If the connection is not successful, see the Output window for more information. You can view the Output window by clicking the Errors link in the status bar.
  5. Click Add to add Siebel servers. The Siebel Server Configuration dialog box opens.

    To set up the Siebel Diagnostics module

  6. Enter the Siebel server information as described in “Understanding the Siebel Server Configuration Dialog Box” on page 336, and then click OK. The Siebel Configuration dialog box is redisplayed.
  7. To show server information for a selected Siebel server, click Details
  8. Click OK to close the Siebel Configuration dialog box.

Understanding the Siebel Configuration Dialog Box

You use the Siebel Configuration dialog box to define the mediator machine, provide details of the monitored servers, and test the connection between the Controller and the mediator machines.

Mediator

Name: Enter the name of the mediator machine used to collect and process the Siebel diagnostics data. Only one mediator machine is supported for each diagnostics module.

Note: If you are using a mediator that is over a firewall, enter the local machine key of the mediator instead of the mediator machine name.

Enable Firewall: Select if you are monitoring over a firewall.

MI Listener: Enter the name, full name, or IP address of the Mercury listener machine if you are monitoring over a firewall.

Test Connection: Tests the connections between the Siebel Diagnostics module and the mediator machine.

Note: The test connection does not check the connections to the Siebel servers.

Servers

Server Name: The name of the Siebel CRM server.

Server ID: The Siebel server ID (for Siebel application servers only).

Platform: The platform of the Siebel CRM server.

Log Directory: The Siebel server directory where Siebel log files are written.

Add: Opens the Siebel Server Configuration dialog box enabling you to enter Siebel server information.

Delete: Deletes a server from the server list.

Details: Displays information for a selected server.

Understanding the Siebel Server Configuration Dialog Box

You use the Siebel Server Configuration dialog box to enter the Siebel server information.

Server Name: Enter the name of the Siebel server.

Server Type: Select the Siebel server type.

OS: Select the Siebel server platform.

AppServer ID: Enter the Siebel server ID (required for Siebel application servers only).

Log Directory:Enter a location where the Siebel application saves the log files. The log files can be saved in a shared log directory on the Siebel server or in a separate folder.

User Name: Enter the user name of the machine where log files are stored.

Note: For Windows platforms, the user should have administrator privileges.

For UNIX platforms, you should verify the following:

  1. RSH and RCP daemons should be running on the UNIX server.
  2. The user should have 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>. For example: rsh my_unix -l my_name -n “cd ~;pwd”.
  3. No output should be generated after executing the RSH command. Due to a bug in the RCP UNIX command, you should not generate output from the .login, .profile, and .cshrc files, (for example by echo, or by any other form 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 that has permissions to run RSH and RCP commands on the server machine.

User Password: Enter the user password.

Domain: Enter the Siebel server domain.


All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd DMCA.com Protection Status

LoadRunner Topics