Difference between seat and concurrent licenses

Seat license

  • Installed locally on machinewith desired product(QTP / ST / UFT).
  • Also referred to as a "stand-alone" or "local license".
  • Works on physical machines (not virtual)
  • There are trial/demo license
  • Not supported when connecting to Windows servers (2000, 2003) via Remote desktop. Not supported with Windows 2008 server machines.

Concurrent license

  • Installed on machine withLicense Serversoftware (no need to be same machine where products is)
  • Also known as "Floating license"
  • There are no trial/demo license
  • Allows multiple users to access a pool of available licenses.

    : The Concurrent License Server will regulate the number of copies of product that are allowed to run concurrently/in-parallel/same-time, by allowing to run the number of copies (licenses) of product purchased at one time. Is possible to increase number of copies of products to run concurrently by purchasing additional licenses from Hewlett-Packard and receiving a new license code.
  • Works with virtualized workstations with installed products (QTP / ST / UFT), such as Citrix or VMware can get licenses from the License Server (which is not virtualized)
  • Allows using products via Terminal Server on Windows Server with Remote Desktop.

Procedure when moving the License Server to another machine

When it is needed to move the License Server to another machine, it will be needed to request a new license key code. Keep in mind that the new license key code could take a couple of days (usually two business days) to be generated.

1. Install the License Server software on the new machine.

2. Get the locking code for the new machine.

3. Submit a new case with HP License team, to request a new license for the new machine. providing new machine’s locking code

4. Once received from HP License team, install the license key code on the new machine.

5. Uninstall the old license server.

Which user to supply in dmconfig during BSAE 9.10 dataminer installation

During a Business Server Automation Essentials (BSAE) 9.10 installation, the dmconfig.sh script is run in order to configure a dataminer. During its execution, the script will prompt for a logon to be used for the dataminer. What is the appropriate user to supply in order for the script to execute properly?

When prompted for the user by the dmconfig.sh script, make sure to supply the oracle user that is configured on the Model Repository. Chapter 5 of the BSAE Installation Guide goes into the various methods of pre-registering users and their passwords for use by the script.

The default user is cmdb_admin. This user is defined in the /opt/opsware/omdb/bin/dmconfig.properties file.

Oracle ARCHIVELOG mode creates excess activity / excess disk usage

In an SA (Server Automation) or BSAE (Business Service Automation Essentials) installation, on reviewing the Oracle activities/performance, you notice what appears to be excessive archiving of the redo log files.

You see this as a possible sign of incorrect SA / BSAE performance and/or as a threat to excessive use of system resources, such as disk usage which might lead it to exhausting the free space on a partition.

By default, neither SA nor BSAE require ARCHIVELOG mode to be enabled for product functionality. Certainly when using the included Oracle installer for SA (or for BSAE prior to v9.10), ARCHIVELOG is not enabled.

If it was enabled, then the most likely cause for this is that your organization’s DBA has a policy which requires ARCHIVELOG mode to be enabled. Again, this is not a requirement for SA / BSAE to function correctly.

We do understand that by enabling ARCHIVELOG mode that you will quite likely see a sudden increase in Oracle DB instance activity over what it was like prior to enabling ARCHIVELOG mode. This is normal and expected. No corrective action is required, although you might want to discuss with your DBA regarding ensuring that neither the database’s performance nor the database server’s free disk space is being pushed to critical limits.

If database performance or disk space utilization is a concern, please disable ARCHIVELOG mode.

To check whether your database instance is running in ARCHIVELOG mode, please run the following commands from the Oracle user shell:

$ sqlplus ‘/ as sysdba’

SQL> select log_mode from v$database;


Dataminer is not passing data to Service Automation Reporter

Error Messages from the dataminer.log file:

INFO – – – – – "Configuration Path = /opt/opsware/dataminer"

INFO – – – – – "Using configuration file /opt/opsware/dataminer/dataminer.conf"

INFO – – – – – "Initializing …"

INFO – – – – – "Running on Linux"

INFO – – – – – "Cached Configuration file has been updated, reloading"

INFO – – – – – "Data Miner is already active"

DEBUG – – – – -"Sleeping 180000ms"

DEBUG – – – – -"Sleeping 180000ms"

If SAR is reinstalled, the dataminer must be reconfigured as well or will become orphaned.

If the original dataminer registration was successful and SAR is reinstalled, the dataminer will have the requisite crypto, Extract, Transform and Load (ETL), and source information but will not function due to:

Data Mining suspended while is_active flag cleared

Follow these step-by-step instructions:

On the dataminer server:

1. /etc/init.d/opsware-dataminer stop

2. cd /opt/opsware/dataminer

3. rm -rf *.ser

4. rm -rf work/

5. rm -rf collect/

6. rm -rf DMSettingsCache.properties

7. rm -rf dataminer.keystore

8. check that you have the correct “RegistrationToken=” setting in dataminer.conf

9. check that dmboot.pem exists

On the SAR/BSAE Server:

10. cd /opt/opsware/omdb/bin

11. to obtain the name: dmconfig -list

12. dmconfig.sh -reset -name <NAME> # where <NAME> is the correct name of the dataminer you wish to reset

On the dataminer server:

13. /etc/init.d/opsware-dataminer start

Query will not run/refresh data

While running a report in BSAE, the following oracle error appears:

"ORA-01013:user requested cancel of current operation (wis 10901)" when trying to refresh the information.

This is a known issue. The Business Objects (BO) reporting engine has a default setting that can cause this problem.

1.) Go the edit query screen and click on the properties pane there is an option to "Retrieve duplicate rows" that is checked by default, uncheck this box.

2.) Use a date filter. On the data pane under general there is a "Single Date Filter" and a "Date Range Filter". Depending on what users want from the report, they should use one of this filters to help BO make a good decision when it creates the SQL. The "Single Date Filter" is like saying show me the data that was current as of this date. This is what most reports want. The "Date Range Filter" is like saying show me the data that was current between these two dates.