Home » HP Manuals » Desktops » HP Xw460c » Manual Viewer

HP Xw460c Administrator's Guide HP Session Allocation Manager (HP SAM) v.3.0 - Page 22

SQL Database Considerations, SAM_data.mdf, SAM_log.ldf

Add to My Manuals
Save this manual to your list of manuals

Page 22 highlights

SQL Database Considerations The HP SAM SQL database can be installed on the same server as the HP SAM Web Server to keep from buying another hardware platform and another Server OS license, however HP recommends separating them onto two different servers for the following reasons: ● Recovery times from hardware failures will be faster. ● As deployments grow in size and number of locations, there will likely be multiple HP SAM Web Servers but only one centralized HP SAM SQL database. Most Administrators already know how to size a SQL database based upon amount of data captured, however, simultaneous HP SAM log-ins and log-offs can impact performance because these events have to be written to the database. Therefore, the platform sizing for the SQL should take this into account as user populations grow. HP SAM is a multi-tier application and the actual user never logs into the database directly at any time. HP SAM only needs one login, which is the HP SAM service account. You may want have more than one login if you want manual access to the HP SAM database without using the HP SAM service account. HP SAM needs many concurrent connections. HP SAM does not have control over the number of connections. Instead, the .NET Framework database engine decides whether it is more efficient to wait for a connection, re-use an existing connection, or create a new connection. Normally, the busier the database, the more connections are created. They are automatically destroyed once the operations are complete. You should not need to limit the concurrent connections. If you must set a limit, we recommend that you set it for at least 200-300. The HP SAM database consists of two files: ● SAM_data.mdf: Location of the HP SAM tables ● SAM_log.ldf: Location of transaction log information. SQL server uses this file to keep track of SQL transactions. The default size is 100MB for each file, but the actual data inside each file is about 10MB. This leaves about 90MB free for each to grow before SQL has to expand the file. The SAM_data.mdf file holds several HP SAM tables, including History and AuditLog tables. These two tables store the HP SAM history data and events, and over time these two tables will grow larger. If you disable history and audit logs, you will not outgrow the 100MB default with 100 users. If you do not disable them, SAM_data.mdf will grow by at least 100MB a day. The busier the database, the more transactions will be added to the SAM_log.ldf file. When a transaction is complete, it is removed from the file. The maximum size of the file, therefore, is when the concurrent transactions peak. For 100 users, the average size of this file should be less than 2 GB. 14 Chapter 2 Requirements ENWW

Section	Page
Introduction	9
What's New in This Release	10
Resource Reservations (AKA Access Restrictions)	10
Authenticate Before Allocation	11
Switch To, Move, Minimize, and Minimize All Functions on HP SAM Connection Bar	12
Support for RGS Senders Running on a Non-default Port	12
Logoff Scheduler	12
Key Features	12
Overview	13
How HP SAM Works	14
HP SAM Software Components	16
Remote Graphics Software (RGS)	16
Common Tasks	17
Setting up HP SAM	17
Setting up a User with a Dynamic Resource	17
Setting up a User with Static (Dedicated) Resources	18
Configuring a Monitor Layout for a User	19
Requirements	21
HP SAM Hardware and Software Requirements	21
Architectural Considerations and Best Practices for Setting up an HP SAM Environment	21
Server Sizing	21
SQL Database Considerations	22
Number of HP SAM Servers	23
Regionalization of Data Centers	23
Multiple SQL Databases	24
Domain Environment Requirements for HP SAM	24
HP SAM Web and SQL Server Requirements	24
HP SAM Web Server Hardware Requirements	24
HP SAM Web Server Software Requirements	24
HP SAM SQL Database Server Hardware Requirements	25
HP SAM SQL Database Server Software Requirements	29
HP SAM Registration Service Requirements	29
Access Device Requirements	30
Thin Client	30
Mobile Thin Client	30
Desktop or Notebook PC	30
Blade Workstation Clients	31
Personal Workstation Clients	31
Other requirements	32
Create a Service Account	32
Obtain Administrative Rights	32
Change the Firewall	32
Active Directory	32
Installation	33
Order of Installation	33
New Installation	33
Upgrade	33
Install the HP SAM Web Server and SQL Software	35
Grant Users HP SAM Administrator Access	37
Configure HP SAM System Settings	37
Configure Secure Socket Layer (SSL)	37
Install and Validate the HP SAM Registration Service Software	37
Install the HP SAM Registration Service	38
Create the HP SAM Registration Service Configuration File	39
[WebServerList]	39
[RolesList]	40
[AssetGroupList]	40
ServicePort	40
DnsDomain	40
Start/Restart the HP SAM Registration Service	41
Test the HP SAM Registration Service	41
Install and Validate the HP SAM Client Software	41
Internet Explorer-Based Client	42
HP SAM ActiveX Controls	43
Windows XPe-Based Client	43
Customization Steps	44
Linux-Based Client	44
HP Blade Workstation Client Series	44
Customization Steps	44
HP ThinPro GT Client for the HP gt7725 Thin Client	45
Red Hat Enterprise Linux (RHEL) Client	46
Customization Steps	46
Configuration Settings	46
Options	46
Smart Card Settings	49
User Interface Customization Settings	50
Policy Entries	52
Global and Local Client Configuration Files	55
Legal Banner	56
Deploy the HP SAM Registration Service to All HP SAM Computing Resources	57
Deploy HP SAM Client Software to All HP SAM Access Devices	57
Administration	59
Log In	59
General Navigation and User Interface Design	59
Display More (or Fewer) Items Per Page	59
Move Columns	59
Sort Result List	59
Select More Than One Item	59
Managing the HP SAM Administrator Access List	60
Add Individual Users to the HP SAM Administrator Group	60
Add Security Groups or Organizational Units to the HP SAM Administrator Group	60
Remove Users or Groups From the HP SAM Administrator Group	61
HP SAM Administrator Console Tabs	62
Home Tab	62
Users and Roles Tab	62
Manage Resource Roles	62
Manage Asset Groups	63
Manage Administrative Permissions	64
Manage Users	65
Operation	65
To Assign Attributes	65
To Assign Resources	66
To Assign Resources Manually	66
To Assign Resources Automatically from Template User	67
To Assign Resources Automatically from Role	68
To Assign and Configure a Monitor Layout for the User	68
To Change the Monitor Layout Configuration for the User	68
To Delete a Monitor Layout ID for the User	69
To Delete a User	69
Add New Users	69
To Grant Access to Individual Users	69
To Grant Access to Security Groups or Organization Units	70
Resources tab	70
Manage Resources	70
Auto Refresh Feature	71
View Details	71
Operations	71
Operations	71
Customize View	72
Manage Access Devices	72
To Add an Access Device Manually	72
To Change an Access Device	72
To Delete an Access Device	73
Manage Monitor Layout	73
To Create a Monitor Layout	73
To Modify a Monitor Layout	73
To Delete a Monitor Layout	73
Manage Data Centers	73
To Create a Data Center	74
To Change a Data Center	74
To Add Enclosures into a Data Center	74
To Delete Enclosures from a Data Center	74
To Delete a Data Center	74
Policies Tab	74
Create or Update a Policy	76
View Effective Policy	76
System Settings Tab	77
General	77
Web client	78
Active Directory	79
Auto Schedules	80
Resource Synchronization Scheduler	80
Audit Log Clean Up Scheduler	80
Logoff User from Resource Scheduler	81
Licensing	81
Reports Tab	81
Resource Capacity Consumption Report	82
Filters	82
Display Options	82
Output Report	82
Resource Capacity Consumption Trend Report	82
Filters	83
Display Options	83
Output Report	83
Resource Utilization Report	84
Filters	84
Display Options	84
Output Report	84
Log Tab	84
Setting Up Smart Card Login on the Access Device	85
Configuring Session Time Limits for Remote Sessions	87
Firewall Rules	89
Web Server	89
Clients	89
Resources	90
SQL Server	90
Frequently Asked Questions	91
Registration Service Error Codes	95
Glossary	98

Match case Limit results 1 per page

SQL Database Considerations

The HP SAM SQL database can be installed on the same server as the HP SAM Web Server to keep

from buying another hardware platform and another Server OS license, however HP recommends

separating them onto two different servers for the following reasons:

●

Recovery times from hardware failures will be faster.

●

As deployments grow in size and number of locations, there will likely be multiple HP SAM Web

Servers but only one centralized HP SAM SQL database.

Most Administrators already know how to size a SQL database based upon amount of data captured,

however, simultaneous HP SAM log-ins and log-offs can impact performance because these events

have to be written to the database. Therefore, the platform sizing for the SQL should take this into

account as user populations grow.

HP SAM is a multi-tier application and the actual user never logs into the database directly at any time.

HP SAM only needs one login, which is the HP SAM service account. You may want have more than

one login if you want manual access to the HP SAM database without using the HP SAM service account.

HP SAM needs many concurrent connections. HP SAM does not have control over the number of

connections. Instead, the .NET Framework database engine decides whether it is more efficient to wait

for a connection, re-use an existing connection, or create a new connection. Normally, the busier the

database, the more connections are created. They are automatically destroyed once the operations are

complete.

You should not need to limit the concurrent connections. If you must set a limit, we recommend that you

set it for at least 200–300.

The HP SAM database consists of two files:

●

SAM_data.mdf

: Location of the HP SAM tables

●

SAM_log.ldf

: Location of transaction log information. SQL server uses this file to keep track of

SQL transactions.

The default size is 100MB for each file, but the actual data inside each file is about 10MB. This leaves

about 90MB free for each to grow before SQL has to expand the file.

The SAM_data.mdf file holds several HP SAM tables, including History and AuditLog tables. These two

tables store the HP SAM history data and events, and over time these two tables will grow larger. If you

disable history and audit logs, you will not outgrow the 100MB default with 100 users. If you do not

disable them, SAM_data.mdf will grow by at least 100MB a day.

The busier the database, the more transactions will be added to the SAM_log.ldf file. When a transaction

is complete, it is removed from the file. The maximum size of the file, therefore, is when the concurrent

transactions peak. For 100 users, the average size of this file should be less than 2 GB.

Chapter 2

Requirements

ENWW