Sccm User Guide

IBM SmartCloud Cost ManagementVersion 2.3

User's Guide

NoteBefore using this information and the product it supports, read the information in Notices on page 701.

Edition notice

This edition applies to IBM SmartCloud Orchestrator Version 2 Release 3 Fix Pack 1 (program number 5725-H28),available as a licensed program product, and to all subsequent releases and modifications until otherwise indicatedin new editions.

The material in this document is an excerpt from the IBM SmartCloud Orchestrator 2.3 information center and isprovided for convenience. This document should be used in conjunction with the information center.

Copyright IBM Corporation 2013, 2014.US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

ContentsTables . . . . . . . . . . . . . . . xi

Preface . . . . . . . . . . . . . . xvWho should read this information . . . . . . . xv

Chapter 1. Installing SmartCloud CostManagement 2.1.0.3. . . . . . . . . . 1Installation overview . . . . . . . . . . . 1Supported hardware and software requirements . . 1

Requirements for Linux servers . . . . . . . 2Installation dependencies . . . . . . . . . . 2Installing from the product DVD . . . . . . . 3

Installing using the installation script . . . . . 3Uninstalling SmartCloud Cost Management . . . . 4

Chapter 2. Configuration required formetering . . . . . . . . . . . . . . 5Automated configuration . . . . . . . . . . 5Logging in to the Administration Console . . . . 6Accepting the security certificate. . . . . . . . 7Configuring the JDBC Driver . . . . . . . . . 7

Adding a JDBC driver . . . . . . . . . . 7SmartCloud Cost Management Command LineInterface . . . . . . . . . . . . . . . . 8

Using the Command Line Interface to managedata sources . . . . . . . . . . . . . 9Using the Command Line Interface to manageload tracking . . . . . . . . . . . . . 10

Configuring the SmartCloud Cost Management datasources . . . . . . . . . . . . . . . . 11

Adding a Database data source . . . . . . . 12Setting the Default Admin and Processingdata source . . . . . . . . . . . . 14

Adding a Web service data source . . . . . . 14Adding a Server data source. . . . . . . . 15Adding a Message Broker data source . . . . 16

About initializing the database . . . . . . . . 17Initializing the database . . . . . . . . . 17

Loading the database with sample SmartCloudOrchestrator data . . . . . . . . . . . . 18Security overview . . . . . . . . . . . . 19

Account Code security for SmartCloudOrchestrator . . . . . . . . . . . . . 19

SmartCloud Orchestrator Account codestructure . . . . . . . . . . . . . 20

User management . . . . . . . . . . . 20Configuring Keystone as a Central UserRegistry . . . . . . . . . . . . . 20

Defining Tivoli Common Reporting securitypermissions . . . . . . . . . . . . . 21

Managing Jazz for Service Management rolesfor users . . . . . . . . . . . . . 21Configuring security permissions . . . . . 23Constraining access to reports . . . . . . 24

Chapter 3. Administering the system 25Defining offerings and rate groups . . . . . . 25

Adding offerings . . . . . . . . . . . 25Deleting offerings . . . . . . . . . . . 26Adding rate groups. . . . . . . . . . . 26Changing the rate group sequence. . . . . . 27Deleting rate groups . . . . . . . . . . 27

Defining rates using the Rate Tables panel . . . . 27Adding rate tables . . . . . . . . . . . 28Removing rate tables . . . . . . . . . . 28Defining rates . . . . . . . . . . . . 29

Viewing rates. . . . . . . . . . . . 29Adding rates . . . . . . . . . . . . 30

Adding rates with tiers . . . . . . . 31Adding rates with shifts . . . . . . . 33

Importing rates . . . . . . . . . . . 34Importing rates from an existing rate table 34

Moving rates between rate groups. . . . . 36Changing the rate sequence . . . . . . . 36Modifying rates . . . . . . . . . . . 37Deleting rates and rate group rates . . . . 40

Defining rate templates . . . . . . . . . . 40Resource elements for the rate template . . . . 41Modifying the sample rate templates . . . . . 43Importing the rate template . . . . . . . . 44Deleting the rate template . . . . . . . . 45

Defining the calendar . . . . . . . . . . . 45Calendar considerations . . . . . . . . . 45Setting up the calendar . . . . . . . . . 45

Defining configuration options . . . . . . . . 47Adding a JDBC driver . . . . . . . . . . 47Setting logging options . . . . . . . . . 48Adding organization information . . . . . . 48Setting processing options . . . . . . . . 49Setting reporting options . . . . . . . . . 50

Stopping and starting the Application Server . . . 50

Chapter 4. Administering dataprocessing . . . . . . . . . . . . . 51Data processing architecture . . . . . . . . . 51

Job Runner . . . . . . . . . . . . . 51Job files. . . . . . . . . . . . . . . 51Job file XML schema . . . . . . . . . . 52Collection files . . . . . . . . . . . . 52Log files . . . . . . . . . . . . . . 53

Message and trace log files . . . . . . . 53Job log files . . . . . . . . . . . . 53Embedded Web Application Server log files 54Installation log files. . . . . . . . . . 55

Processing programs . . . . . . . . . . 55Process definitions . . . . . . . . . . . 56Date keywords . . . . . . . . . . . . 57

Data processing overview . . . . . . . . . 58Data processing frequency . . . . . . . . 58

Copyright IBM Corp. 2013, 2014 iii

Required directory permissions for dataprocessing . . . . . . . . . . . . . . 59SmartCloud Cost Management Processing Engine 59

Acct . . . . . . . . . . . . . . . 60Bill . . . . . . . . . . . . . . . 61DBLoad . . . . . . . . . . . . . 63ReBill . . . . . . . . . . . . . . 64

SmartCloud Cost Management Integrator . . . 66Setting up and running job files . . . . . . . 67

Creating job files . . . . . . . . . . . 67Job file structure . . . . . . . . . . . . 68

Jobs element . . . . . . . . . . . . 68Job Element . . . . . . . . . . . . 70Process element . . . . . . . . . . . 72Steps Element . . . . . . . . . . . 74Step Element . . . . . . . . . . . . 74Parameters Element . . . . . . . . . 77Parameter element . . . . . . . . . . 77

Acct specific parameter attributes . . . . 78Bill specific parameter attributes . . . . 80Cleanup specific parameter attributes. . . 82Console parameter attributes . . . . . 82Console specific parameter attributes . . . 83DBLoad specific parameter attributes . . . 84DBPurge specific parameter attributes . . 86FileTransfer specific parameter attributes . 86Rebill specific parameter attributes . . . 90Scan specific parameter attributes . . . . 91WaitFile specific parameter attributes . . . 92

Defaults Element . . . . . . . . . . 93Default Element . . . . . . . . . . . 93Integrator job file structure . . . . . . . 95

Input element . . . . . . . . . . 95Stage elements . . . . . . . . . . 98

Running job files . . . . . . . . . . . 159Running job files in batch mode . . . . . 160

Viewing job file logs . . . . . . . . . . 161Viewing sample job files. . . . . . . . . 162

Setting accounting dates . . . . . . . . . . 162Account codes and account code conversion . . . 162

Setting up account codes and performingaccount code conversion. . . . . . . . . 163

Defining the account code structure . . . . 163Defining the account code . . . . . . . 163

Defining the account code input fieldusing the Integrator program . . . . . 164Defining the account code input fieldusing the Acct program . . . . . . . 164

Converting account code input field valuesto uppercase. . . . . . . . . . . . 165Setting the account code conversion options(Acct program) . . . . . . . . . . . 165

Enabling account code conversion . . . 166Defining the identifier values for accountcode conversion . . . . . . . . . 166Defining optional move fields . . . . . 166Defining the account code conversiontable . . . . . . . . . . . . . 167Enabling exception processing . . . . . 168Creating the account code conversiontable (Acct program) . . . . . . . . 168

Account code conversion example (Acctprogram) . . . . . . . . . . . . 170Advanced account code conversionexample (Acct program) . . . . . . . 171

Setting the account code conversion options(Integrator program) . . . . . . . . . 174

Enabling account code conversion . . . 174Defining the identifier values for accountcode conversion . . . . . . . . . 174Defining optional move fields . . . . . 175Defining the account code conversiontable . . . . . . . . . . . . . 177Enabling exception processing . . . . . 177Creating the account code conversiontable (Integrator program) . . . . . . 178Account code conversion example(Integrator program) . . . . . . . . 179

Setting up conversion mappings . . . . . . 181Adding conversion mappings . . . . . . 181

About exception file processing . . . . . . 181Setting up shifts . . . . . . . . . . . . 181Transferring files . . . . . . . . . . . . 182

Sample FTP file transfer job file . . . . . . 184Sample SSH file transfer job file . . . . . . 185Sample local file transfer job file . . . . . . 186Using an encrypted password to connect to aremote system . . . . . . . . . . . . 188

File encoding . . . . . . . . . . . . . 188Default file encoding . . . . . . . . . . 189Overriding default file encoding . . . . . . 189

Chapter 5. Administering reports . . . 191Working with Cognos based Tivoli CommonReporting . . . . . . . . . . . . . . 191

About the Tivoli Common Reporting application 191Running reports . . . . . . . . . . . 193Using the Cognos toolbar . . . . . . . . 193Printing reports . . . . . . . . . . . 194Saving reports . . . . . . . . . . . . 194Report properties . . . . . . . . . . . 194Creating Dashboard reports . . . . . . . 194

Creating a sample dashboard report . . . . 195Creating Page dashboard reports . . . . . 196

Working with custom reports . . . . . . . 197Creating, editing, and saving custom reports 197

Creating or updating a custom report . . 197Saving a custom report . . . . . . . 198

Using report parameters. . . . . . . . 198Simple parameters. . . . . . . . . 199Existing parameters . . . . . . . . 200

Using report filters . . . . . . . . . 203Template reports . . . . . . . . . . 204

Template Account Code Date . . . . . 205Template Account Code Year . . . . . 206

Rebranding reports . . . . . . . . . 206Working with the SmartCloud CostManagement Cognos model . . . . . . 207

Accessing the Cognos model . . . . . 207Adding custom objects to the Cognosmodel . . . . . . . . . . . . . 208Publishing the custom model . . . . . 208

iv IBM SmartCloud Cost Management 2.3: User's Guide

Additional resources . . . . . . . . . . 209

Chapter 6. Administering the database 211Tracking database loads . . . . . . . . . . 211Administering database objects . . . . . . . 212Administering database tables . . . . . . . . 213

Loading table dependencies . . . . . . . 214DataAccessManager command-line utility . . . . 216

DDL extraction . . . . . . . . . . . . 217Populate tables . . . . . . . . . . . . 218Setting the database version . . . . . . . 218Importing data into a database table. . . . . 219Exporting data into a database table . . . . . 220

Chapter 7. Administering datacollectors . . . . . . . . . . . . . 221Universal Collector overview . . . . . . . . 221

Creating a new collector using XML. . . . . 221Creating new collectors using Java . . . . . 232

IBM SmartCloud Cost Management Core datacollectors . . . . . . . . . . . . . . . 234

AIX Advanced Accounting data collector . . . 234Process data collected (Advanced Accountingrecord type 1) . . . . . . . . . . . 234System data collected (Advanced Accountingrecord type 4) . . . . . . . . . . . 235File system data collected (AdvancedAccounting record type 6) . . . . . . . 236Network data collected (AdvancedAccounting record type 7) . . . . . . . 236Disk data collected (Advanced Accountingrecord type 8) . . . . . . . . . . . 237Virtual I/O server data collected (AdvancedAccounting record type 10) . . . . . . . 237Virtual I/O client data collected (AdvancedAccounting record type 11) . . . . . . . 238ARM transaction data collected (AdvancedAccounting record type 16) . . . . . . . 238WPAR system data collected (AdvancedAccounting record type 36) . . . . . . . 239WPAR file system data collected (AdvancedAccounting record type 38) . . . . . . . 239WPAR disk data collected (AdvancedAccounting record type 39) . . . . . . . 240Setting up AIX Advanced Accounting datacollection . . . . . . . . . . . . . 241

HPVMSar data collector . . . . . . . . . 241Identifiers and resources collected byhpvmsar collector . . . . . . . . . . 241Deploying the SmartCloud Cost Managementhpvmsar collector . . . . . . . . . . 242

Installing the SmartCloud CostManagement hpvmsar Collector from theSmartCloud Cost Management Server . . 242Manually installing the hpvmsar collector 243Following the installation of the hpvmsarcollector . . . . . . . . . . . . 244Uninstalling the hpvmsar collector . . . 244

OpenStack data collector . . . . . . . . 245Configuring the OpenStack data collector . . 245

Manually configuring the OpenStack datacollector . . . . . . . . . . . . 246

OpenStack identifiers and resources . . . . 254Compute identifiers and resources . . . 254Volume identifiers and resources . . . . 258

OpenStack job file . . . . . . . . . . 261Context job file . . . . . . . . . . 261VM Instances job file . . . . . . . . 265Volumes job file . . . . . . . . . 269OpenStack REST volume job file . . . . 271SmartCloud Orchestrator 2.2 job file . . . 273

IBM PowerVM HMC data collector . . . . . 274Configuring HMC to enable SmartCloudCost Management HMC collection . . . . 274HMC collector log file format . . . . . . 274Identifiers and resources defined by HMCcollector . . . . . . . . . . . . . 279Setting up SmartCloud Cost Management forHMC data collection . . . . . . . . . 281HMC data commands . . . . . . . . 285

KVM data collector . . . . . . . . . . 285Identifiers and resources collected by theKVM collector . . . . . . . . . . . 286Deploying the SmartCloud Cost ManagementKVM collector . . . . . . . . . . . 287

Installing the SmartCloud CostManagement KVM collector from theSmartCloud Cost Management Server . . 287Manually installing the SmartCloud CostManagement KVM collector . . . . . 288Following the installation of theSmartCloud Cost Management KVMcollector . . . . . . . . . . . . 289Uninstalling the SmartCloud CostManagement KVM collector . . . . . 290

Linux, z/Linux, UNIX, and AIX operatingsystem and file system data collectors . . . . 290Sar data collector . . . . . . . . . . . 290

Identifiers and resources collected by sarcollector . . . . . . . . . . . . . 291Deploying the sar collector . . . . . . . 291

Installing the SmartCloud CostManagement sar Collector from theSmartCloud Cost Management Server . . 292Manually installing the SmartCloud CostManagement sar collector . . . . . . 293Following the installation of the sarcollector . . . . . . . . . . . . 293Uninstalling the sar collector . . . . . 294

Tivoli Data Warehouse data collector . . . . 294Setting up Tivoli Data Warehouse datacollection . . . . . . . . . . . . . 294Configuring the Tivoli Data Warehouse jobfile . . . . . . . . . . . . . . . 295Active Energy Manager identifiers andresources . . . . . . . . . . . . . 298AIX Premium identifiers and resources . . . 302Eaton identifiers and resources . . . . . 309HMC identifiers and resources . . . . . 311ITCAM/SOA identifiers and resources . . . 312Linux OS identifiers and resources . . . . 314

Contents v

UNIX OS identifiers and resources . . . . 316Windows OS identifiers and resources . . . 319

Universal data collector . . . . . . . . . 330Setting up the Universal data collector . . . 330

Virtual I/O Server data collector . . . . . . 330Identifiers and resources defined by theVirtual I/O Server data collector . . . . . 330Transferring usage logs from the Virtual I/OServer to the SmartCloud Cost Managementapplication server for processing . . . . . 333Setting up Virtual I/O Server data collection 337

VMware data collector . . . . . . . . . 337Configuring VMware server systems toenable SmartCloud Cost ManagementVMware collection . . . . . . . . . 337VMware usage metrics collected . . . . . 338Identifiers and resources defined by theVMware collector . . . . . . . . . . 342Setting up SmartCloud Cost Management forVMware data collection . . . . . . . . 344Mapping of VMware Identifiers andresources to VMware InfrastructureEquivalents . . . . . . . . . . . . 347

Vmstat data collector . . . . . . . . . . 348Identifiers and resources collected by vmstatcollector . . . . . . . . . . . . . 348Deploying the vmstat collector . . . . . 349

Installing the SmartCloud CostManagement vmstat Collector from theSmartCloud Cost Management Server . . 349Manually installing the vmstat collector 350Following the installation of the vmstatcollector . . . . . . . . . . . . 351Uninstalling the vmstat collector . . . . 352

Windows Disk data collector . . . . . . . 352Identifiers and resources collected by theWindows Disk collector . . . . . . . . 352Setting up Windows Disk data collection . . 354File system collection . . . . . . . . . 358Physical and logical disk collection . . . . 358

Windows Process data collector . . . . . . 360Creating a log on user account for theWindows Process collector service (optional) . 360

Assigning Polices at the domain level . . 361Assigning Polices at the local level . . . 361

System configuration options for theWindows Process collector . . . . . . . 362Installing the Windows Process collector . . 363

Installing remotely . . . . . . . . 363Installing manually . . . . . . . . 366

Windows Process collector log file format 368Identifiers and resources defined by theWindows Process collector . . . . . . . 372Setting up Windows Process data collection 374Troubleshooting . . . . . . . . . . 377

z/VM data collector . . . . . . . . . . 378z/VM standard billable items collected . . . 378z/VM Accounting Records Processed . . . 378Creating a process definition directory . . . 379Installing the z/VM collector . . . . . . 380

Binding the CIMSCMS program . . . . 380

Running the z/VM Collector . . . . . . 380CIMSCMS Control Statements . . . . . . 382About the Z/VM collector output CSR file 385Transferring output CSR files from the z/VMsystem . . . . . . . . . . . . . 386Setting up z/VM data collection . . . . . 386

Setting up for data collection on a Linux or UNIXsystem . . . . . . . . . . . . . . . 386

Installing SmartCloud Cost Management DataCollectors for UNIX and Linux . . . . . . 386Linux and UNIX data collection architecture . . 391Setting the sharable library path . . . . . . 393Setting the environment variables for datacollection and consolidation . . . . . . . 393Setting up operating and file system datacollection: starting Linux or UNIX processaccounting . . . . . . . . . . . . . 398

Identifiers and resources defined fromprocess accounting data (operating systemand file system) . . . . . . . . . . 399

Setting up AIX Advanced Accounting datacollection . . . . . . . . . . . . . . 401

Installing the UNIX/Linux AIX AdvancedAccounting Collector . . . . . . . . . 402

Installing the UNIX/Linux AIX AdvancedAccounting Collector Manually . . . . 402Installing the UNIX/Linux AIX AdvancedAccounting Collector using RXAdeployment . . . . . . . . . . . 402Post Install Configuration . . . . . . 402

Creating Advanced Accounting data files . . 403Configuring AIX Advanced Accounting . . 403Setting up Advanced Accounting datacollection . . . . . . . . . . . . . 404Scheduling Advanced Accounting datacollection . . . . . . . . . . . . . 406Advanced Accounting metrics collected andSmartCloud Cost Management rate codes . . 406

Setting up Virtual I/O Server data collection 410About the Configuration Parameter file onthe Virtual I/O Server . . . . . . . . 410

Configuring and starting the SmartCloudCost Management Agent . . . . . . 411Collecting and Converting Virtual I/OServer data files . . . . . . . . . 412Transferring Virtual I/O Server usage logsto the SmartCloud Cost Managementapplication server . . . . . . . . . 413Virtual I/O Server metrics collected andSmartCloud Cost Management rate codes . 415

Schedule the data collection and consolidationscripts . . . . . . . . . . . . . . . 417Collecting data: setting up the data collectionscripts . . . . . . . . . . . . . . . 418

Check pacct File Script (check_pacct) . . . 419Nightly Accounting Script (ituam_uc_nightly) 419Turn Accounting Script (turnacct). . . . . 420Run Account Script (runacct) . . . . . . 420Sampler Script (sampler) . . . . . . . 421Database Storage Scripts (get_odb_storageand get_db2_storage) . . . . . . . . . 422

vi IBM SmartCloud Cost Management 2.3: User's Guide

Redo Nightly Script (redo_nightly) . . . . 422Consolidating data: setting up the dataconsolidation scripts . . . . . . . . . . 423

Nightly Consolidation Script(CS_nightly_consolidation) . . . . . . . 423

Running a UNIX script file from within a jobfile . . . . . . . . . . . . . . . . 423CSR file types . . . . . . . . . . . . 425Transferring CSR files to the SmartCloud CostManagement application server . . . . . . 426Transferring log files to the SmartCloud CostManagement application server . . . . . . 429

Chapter 8. Troubleshooting andsupport . . . . . . . . . . . . . . 431Troubleshooting information . . . . . . . . 431

Using Technotes . . . . . . . . . . . 431Common problems and solutions. . . . . . 431Troubleshooting installation . . . . . . . 432

Manually uninstalling . . . . . . . . 432Manually uninstalling SmartCloud CostManagement . . . . . . . . . . 432Manually uninstalling Windows ProcessCollector . . . . . . . . . . . . 432

Unable to connect to the AdministrationConsole . . . . . . . . . . . . . 433

Troubleshooting administration . . . . . . 433Server instance ports in use . . . . . . 433Active Reports do not open or are incorrectlydisplayed when rendered in Japanese,Chinese, or Korean . . . . . . . . . 434Administration Console runs slowly, hangs,or will not connect to the database . . . . 434Unable to run Tivoli Common Reportingreports that use account code prompts . . . 435Report data not updated when runningreports . . . . . . . . . . . . . 435Issues when using the SmartCloud CostManagement rate template . . . . . . . 436

Troubleshooting database applications . . . . 436Troubleshooting for Exception: DB2 SQLerror: SQLCODE: -964, SQLSTATE: 57011,SQLERRMC: null . . . . . . . . . . 436Stored Procedure performance issues on DB2 437

Using log files . . . . . . . . . . . . . 438Message and trace log files . . . . . . . . 438Job log files . . . . . . . . . . . . . 438Embedded Web Application Server log files . . 440Installation log files . . . . . . . . . . 440

Getting SmartCloud Cost Management systeminformation . . . . . . . . . . . . . . 440Disabling Internet Explorer Enhanced SecurityConfiguration . . . . . . . . . . . . . 441Resolving the FileNotFound Exception error onUNIX and Linux systems . . . . . . . . . 441Support information . . . . . . . . . . . 442

Receiving weekly support updates . . . . . 442Contacting IBM Software Support . . . . . 443

Determining the business impact . . . . . 443Describing problems and gatheringinformation . . . . . . . . . . . . 444

Submitting problems . . . . . . . . . 444

Chapter 9. Reference . . . . . . . . 445Encryption information . . . . . . . . . . 445FIPS Compliance . . . . . . . . . . . . 445

Enabling FIPS on the Application Server . . . 445Enabling Tivoli Common Reporting for FIPS 446

Schema updates for the 2.1.0.3 release . . . . . 446Setting the SmartCloud Cost Managementprocessing path. . . . . . . . . . . . . 447REST API reference . . . . . . . . . . . 447

Symbols and abbreviated terms . . . . . . 447REST API reference overview . . . . . . . 448Operations . . . . . . . . . . . . . 449Protocol resource elements . . . . . . . . 452Using Apache Wink to access SmartCloud CostManagement REST Resources . . . . . . . 454Clients Rest API . . . . . . . . . . . 456

GET Resource clients . . . . . . . . . 456GET{id} Resource clients. . . . . . . . 458POST Resource clients . . . . . . . . 459PUT Resource clients . . . . . . . . . 460DELETE Resource clients . . . . . . . 461

Users REST API . . . . . . . . . . . 462GET Resource users . . . . . . . . . 462GET{id} Resource users . . . . . . . . 463POST Resource users . . . . . . . . . 464PUT Resource users . . . . . . . . . 465DELETE Resource users . . . . . . . . 467

Usergroups REST API . . . . . . . . . 467GET Resource usergroups . . . . . . . 467Get{id} Resource usergroups . . . . . . 469POST Resource usergroups . . . . . . . 471PUT Resource usergroups . . . . . . . 473DELETE Resource usergroups . . . . . . 476

AccountCodeStructrues REST API . . . . . 477GET Resource accountCodeStructrues . . . 477GET{id} Resource accountCodeStructrues . . 479POST Resource accountCodeStructrues . . . 481PUT Resource accountCodeStructrue . . . 483DELETE Resource accountCodeStructrues 486

Job file structure . . . . . . . . . . . . 487Jobs element. . . . . . . . . . . . . 487Job Element . . . . . . . . . . . . . 490Process element . . . . . . . . . . . 492Steps Element . . . . . . . . . . . . 493Step Element . . . . . . . . . . . . 494Parameters Element . . . . . . . . . . 497Parameter element. . . . . . . . . . . 497

Acct specific parameter attributes. . . . . 498Bill specific parameter attributes . . . . . 500Cleanup specific parameter attributes . . . 502Console parameter attributes . . . . . . 502Console specific parameter attributes . . . 503DBLoad specific parameter attributes . . . 504DBPurge specific parameter attributes . . . 506FileTransfer specific parameter attributes . . 506Rebill specific parameter attributes . . . . 510Scan specific parameter attributes. . . . . 511WaitFile specific parameter attributes . . . 512

Defaults Element . . . . . . . . . . . 513

Contents vii

Default Element . . . . . . . . . . . 513Integrator job file structure . . . . . . . . 515

Input element . . . . . . . . . . . 515Stage elements . . . . . . . . . . . 518

Aggregator . . . . . . . . . . . 518CreateAccountRelationship . . . . . . 521CreateIdentifierFromIdentifiers . . . . 524CreateIdentifierFromRegEx . . . . . . 526CreateIdentifierFromTable . . . . . . 527CreateIdentifierFromValue . . . . . . 532CreateResourceFromConversion . . . . 533CreateResourceFromDuration . . . . . 536CreateResourceFromValue . . . . . . 539CreateUserRelationship . . . . . . . 540CSROutput . . . . . . . . . . . 542CSRPlusOutput. . . . . . . . . . 542DropFields . . . . . . . . . . . 543DropIdentifiers . . . . . . . . . . 544DropResources . . . . . . . . . . 545ExcludeRecsByDate . . . . . . . . 546ExcludeRecsByPresence . . . . . . . 547ExcludeRecsByValue . . . . . . . . 548FormatDateIdentifier . . . . . . . . 550IdentifierConversionFromTable . . . . 551IncludeRecsByDate . . . . . . . . 557IncludeRecsByPresence . . . . . . . 558IncludeRecsByValue . . . . . . . . 560MaxRecords . . . . . . . . . . . 562PadIdentifier . . . . . . . . . . 563Prorate . . . . . . . . . . . . 564RenameFields . . . . . . . . . . 565RenameResourceFromIdentifier . . . . 566ResourceConversion . . . . . . . . 568Sort . . . . . . . . . . . . . 570TierResources . . . . . . . . . . 571TierSingleResource . . . . . . . . 574UpdateConversionFromRecord . . . . 576

Control statements . . . . . . . . . . . 579Acct Program Control Statements. . . . . . 580

ACCOUNT CODE CONVERSION {SORT} 580ACCOUNT FIELD . . . . . . . . . 580DATE SELECTION . . . . . . . . . 581DEFINE FIELD . . . . . . . . . . . 582DEFINE MOVEFLD . . . . . . . . . 583EXCEPTION FILE PROCESSING ON . . . 583PRINT ACCOUNT NO-MATCH . . . . . 584SHIFT . . . . . . . . . . . . . . 584UPPERCASE ACCOUNT FIELDS . . . . 585

Bill Program Control Statements . . . . . . 585BACKLOAD DATA . . . . . . . . . 586CLIENT SEARCH ON . . . . . . . . 586DATE SELECTION . . . . . . . . . 587DEFAULT CLOSE DAY . . . . . . . . 588DEFINE . . . . . . . . . . . . . 589DYNAMIC CLIENT ADD ON. . . . . . 590EXCLUDE . . . . . . . . . . . . 591INCLUDE . . . . . . . . . . . . 592KEEP ORIGINAL CPU VALUES . . . . . 592NORMALIZE CPU VALUES . . . . . . 593REPORT DATE . . . . . . . . . . . 593USE SHIFT CODES . . . . . . . . . 595

Reports . . . . . . . . . . . . . . . 595Cognos based Tivoli Common Reporting reports 596

Account reports . . . . . . . . . . 597Account Summary YTD report . . . . 597Account Total Invoice report . . . . . 598Application Cost report . . . . . . . 599Daily Charges - Charges report . . . . 601Daily Crosstab - Usage report . . . . . 602Monthly Crosstab - Charges report . . . 604Monthly Crosstab - Usage report . . . . 605Percentage report . . . . . . . . . 606Summary Crosstab - Charges report . . . 607Summary Crosstab - Usage report . . . 609Weekly Crosstab - Charges report . . . 610Weekly Crosstab - Usage report . . . . 611

Budget reports . . . . . . . . . . . 612Client Budget report . . . . . . . . 612Line Item Budget report . . . . . . . 613

Cloud reports . . . . . . . . . . . 614Project Summary report . . . . . . . 614

Dashboard reports. . . . . . . . . . 617Top N Account Charges report . . . . 617Top N Account Charges Pie Chart report 618Top N Rate Group and Rate ResourceUsage report . . . . . . . . . . 619

Invoice reports . . . . . . . . . . . 620Invoice by Account Level report . . . . 620Invoice Detail Line Item Resource Unitsby Identifiers report . . . . . . . . 623Invoice Drill Down for Rate Group byDate report . . . . . . . . . . . 623Run Total Invoice report. . . . . . . 624Run Total Rate Group Percent report . . 626

Other reports . . . . . . . . . . . 627Client report. . . . . . . . . . . 627Configuration report . . . . . . . . 628Rate report . . . . . . . . . . . 628

Resource Detail reports . . . . . . . . 629Batch report . . . . . . . . . . . 629Charges by Identifier report . . . . . 630Detail by Identifier report . . . . . . 633Detail by Multiple Identifiers report . . . 634Usage by Identifier report . . . . . . 635

Template reports . . . . . . . . . . 638Template report . . . . . . . . . 638Template Account Code Date report . . . 638Template Account Code Year report . . . 639

Top Usage reports . . . . . . . . . . 640Top 10 Bar Graph report. . . . . . . 640Top 10 Cost report. . . . . . . . . 641Top 10 Pie Chart report . . . . . . . 643

Trend reports . . . . . . . . . . . 644Cost Trend report . . . . . . . . . 644Cost Trend by Rate report . . . . . . 645Cost Trend Graph report . . . . . . 646Resource Usage Trend report . . . . . 647Usage Trend Graph report . . . . . . 649

Variance reports . . . . . . . . . . 650Cost Variance report . . . . . . . . 650Resource Variance report . . . . . . 651

Tables . . . . . . . . . . . . . . . . 652

viii IBM SmartCloud Cost Management 2.3: User's Guide

CIMSAccountCodeConversion Table. . . . . 652CIMSCalendar Table . . . . . . . . . . 653CIMSClient Table . . . . . . . . . . . 653CIMSClientBudget Table. . . . . . . . . 653CIMSClientContact Table . . . . . . . . 654CIMSClientContactNumber Table. . . . . . 655CIMSConfig Table . . . . . . . . . . . 655CIMSConfigAccountLevel Table . . . . . . 656CIMSConfigOptions Table . . . . . . . . 656CIMSCPUNormalization Table . . . . . . 657CIMSDetailIdent Table . . . . . . . . . 657CIMSDIMClient Table . . . . . . . . . 658CIMSDIMClientContact Table . . . . . . . 658CIMSDIMClientContactNumber Table . . . . 659CIMSDIMUserRestrict Table . . . . . . . 660CIMSIdent Table . . . . . . . . . . . 660CIMSLoadTracking Table . . . . . . . . 661CIMSProcDefinitionMapping Table . . . . . 661CIMSProcessDefinition Table . . . . . . . 662CIMSProrateSource Table . . . . . . . . 662CIMSProrateTarget Table . . . . . . . . 663CIMSRateGroup Table . . . . . . . . . 663CIMSRateIdentifiers Table . . . . . . . . 664CIMSReportCustomFields Table . . . . . . 664CIMSReportDistribution Table . . . . . . . 664CIMSReportDistributionParm Table . . . . . 665CIMSReportDistributionType Table . . . . . 665CIMSReportGroup Table . . . . . . . . 665CIMSReportToReportGroup Table . . . . . 666CIMSSummaryToDetail Table . . . . . . . 666CIMSTransaction Table . . . . . . . . . 666CIMSUser Table . . . . . . . . . . . 668CIMSUserConfigOptions Table . . . . . . 668CIMSUserGroupAccountCode Table . . . . . 669CIMSUserGroupAccountStructure Table . . . 669

CIMSUserGroupConfigOptions Table . . . . 669CIMSUserGroupReport Table . . . . . . . 670CIMSUserGroup Table . . . . . . . . . 670CIMSUserGroupProcessDef Table. . . . . . 671CIMSUsertoUserGroup Table . . . . . . . 671SCDetail Table . . . . . . . . . . . . 672SCDIMCalendar Table . . . . . . . . . 673SCDIMRate Table . . . . . . . . . . . 673SCDIMRateShift Table . . . . . . . . . 678SCRate Table . . . . . . . . . . . . 683SCRateTable Table . . . . . . . . . . . 685SCRateShift Table . . . . . . . . . . . 686SCResourceUtilization Table . . . . . . . 686SCSummaryDaily Table . . . . . . . . . 687SCSummary Table . . . . . . . . . . . 687SCUnits Table . . . . . . . . . . . . 689

SmartCloud Cost Management files . . . . . . 690CSR file . . . . . . . . . . . . . . 690CSR+ file . . . . . . . . . . . . . . 692Ident file . . . . . . . . . . . . . . 695Resource file. . . . . . . . . . . . . 695Detail file. . . . . . . . . . . . . . 696Summary file . . . . . . . . . . . . 698

Notices . . . . . . . . . . . . . . 701

Trademarks and service marks . . . . 703

Privacy policy considerations . . . . 705

Accessibility features for SmartCloudOrchestrator . . . . . . . . . . . . 707

Contents ix

x IBM SmartCloud Cost Management 2.3: User's Guide

Tables1. . . . . . . . . . . . . . . . . . 22. Access for users . . . . . . . . . . . 193. Normal rate patterns in reports . . . . . . 314. Non-billable rate patterns in reports . . . . 315. Monetary flat fee rate patterns in reports 316. Tier individual rate patterns in reports . . . 327. Tier highest rate patterns in reports . . . . 328. Tier monetary individual (%) rate patterns in

reports . . . . . . . . . . . . . . 329. Tier monetary highest (%) rate patterns in

reports . . . . . . . . . . . . . . 3310. IaaS style Offering . . . . . . . . . . 4011. Virtual Server Service style Offering . . . . 4112. License Charges Offering . . . . . . . . 4113. Infrastructure Charges Offering . . . . . . 4114. Hosting Charges Offering . . . . . . . . 4115. Hosting Charges with VM Sizes Offering 4116. Properties of the Offering resource element 4117. Properties of the RateDimension resource

element . . . . . . . . . . . . . . 4218. Properties of the RateDimensionElement

resource element . . . . . . . . . . . 4219. Logging options . . . . . . . . . . . 4820. Organization information . . . . . . . . 4921. Processing options . . . . . . . . . . 4922. Reporting options . . . . . . . . . . 5023. SmartCloud Cost Management Processing

Engine Components. . . . . . . . . . 5924. Acct Input . . . . . . . . . . . . . 6025. Acct Output . . . . . . . . . . . . 6126. Bill Input . . . . . . . . . . . . . 6227. Bill Output. . . . . . . . . . . . . 6328. DBLoad Input. . . . . . . . . . . . 6329. ReBill Input . . . . . . . . . . . . 6430. Bill Output. . . . . . . . . . . . . 6531. Jobs Element Attributes . . . . . . . . 6832. Job Element Attributes . . . . . . . . . 7033. Process Element Attributes . . . . . . . 7334. Steps Element Attribute . . . . . . . . 7435. Step Element Attributes . . . . . . . . 7436. Acct specific parameter attributes . . . . . 7837. Bill specific parameter attributes . . . . . 8038. Cleanup specific parameter attributes . . . . 8239. Console parameter attributes . . . . . . . 8340. Console specific parameter attributes . . . . 8341. DBLoad specific parameter attributes . . . . 8442. DBPurge specific parameter attributes. . . . 8643. FileTransfer specific parameter attributes 8744. FileTransfer parameters . . . . . . . . 8745. FileTransfer parameters . . . . . . . . 8946. Rebill specific parameter attributes . . . . . 9047. Scan specific parameter attributes . . . . . 9148. WaitFile specific parameter attributes . . . . 9249. Default Element Attributes . . . . . . . 9350. Defined thresholds . . . . . . . . . . 15251. Defined thresholds . . . . . . . . . . 153

52. User identifier values . . . . . . . . . 17053. User identifier values . . . . . . . . . 18054. Date Ranges . . . . . . . . . . . . 19255. Predefined filters . . . . . . . . . . 20356. Load table dependencies . . . . . . . . 21457. Elements and attributes specific to DELIMITED 22258. Elements and attributes specific to FIXEDFIELD 22359. Elements and attributes specific to REGEX 22360. Elements and attributes specific to DATABASE 22461. Elements and attributes specific to Parameters 22662. Elements and attributes specific to

InputFields for the DELIMITED collector . . . 22663. Elements and attributes specific to

InputFields for the FIXEDFIELDS collector . . 22764. Elements and attributes specific to

InputFields for the REGEX collector . . . . 22865. Elements and attributes specific to

InputFields for the DATABASE collector . . . 22866. Elements and attributes specific to

QueryParameters . . . . . . . . . . 22967. Elements and attributes specific to

OutputFields . . . . . . . . . . . 23168. Elements and attributes specific to Files 23269. HPVMSar Identifiers . . . . . . . . . 24170. HPVMSar Resources . . . . . . . . . 24271. Standard fields . . . . . . . . . . . 25472. Ownership Identifiers . . . . . . . . . 25473. Placement identifiers . . . . . . . . . 25574. Pattern identifiers . . . . . . . . . . 25675. History identifiers . . . . . . . . . . 25676. Virtual Machine identifiers . . . . . . . 25777. Virtual Machine Resources - Output for each

ID. . . . . . . . . . . . . . . . 25778. Standard fields . . . . . . . . . . . 25879. Ownership Identifiers . . . . . . . . . 25880. Placement identifiers . . . . . . . . . 25981. History identifiers . . . . . . . . . . 26082. Volume identifiers . . . . . . . . . . 26083. Volume Resources - Output for each VOL_ID 26084. Log File Format LPAR Sample Records 27485. HMC Log File Format Memory Pool

Sample Records . . . . . . . . . . . 27686. HMC Log File Format Processor Pool

Sample Records . . . . . . . . . . . 27787. HMC Log File Format System Sample

Records . . . . . . . . . . . . . 27888. Default HMC Identifiers and Resources

LPAR Sample . . . . . . . . . . . 27989. Default HMC Identifiers and Resources

Memory Pool Sample . . . . . . . . . 28090. Default HMC Identifiers and Resources

Processor Pool Sample . . . . . . . . 28091. Default HMC Identifiers and Resources

System Sample . . . . . . . . . . . 28192. HMC Parameters . . . . . . . . . . 28393. HMCINPUT Parameters . . . . . . . . 284

Copyright IBM Corp. 2013, 2014 xi

94. KVM Identifiers. . . . . . . . . . . 28695. KVM resources . . . . . . . . . . . 28696. Sar Identifiers . . . . . . . . . . . 29197. Sar Resources . . . . . . . . . . . 29198. . . . . . . . . . . . . . . . . 29599. . . . . . . . . . . . . . . . . 295100. . . . . . . . . . . . . . . . . 296101. . . . . . . . . . . . . . . . . 296102. . . . . . . . . . . . . . . . . 296103. . . . . . . . . . . . . . . . . 296104. . . . . . . . . . . . . . . . . 297105. . . . . . . . . . . . . . . . . 297106. . . . . . . . . . . . . . . . . 297107. . . . . . . . . . . . . . . . . 297108. . . . . . . . . . . . . . . . . 297109. . . . . . . . . . . . . . . . . 298110. SmartCloud Cost Management identifiers and

resources that are collected from Tivoli DataWarehouse by the Active Energy Manageragent . . . . . . . . . . . . . . 299

111. SmartCloud Cost Management identifiers andresources that are collected from Tivoli DataWarehouse by the AIX Premium agent . . . 303

112. SmartCloud Cost Management identifiers andresources that are collected from Tivoli DataWarehouse by the Eaton agent . . . . . . 310

113. Identifiers and resources that are collectedfrom Tivoli Data Warehouse by the HMCagent. . . . . . . . . . . . . . . 312

114. Identifiers and resources that are collectedfrom Tivoli Data Warehouse by theITCAM/SOA agent. . . . . . . . . . 313

115. Identifiers and resources that are collectedfrom Tivoli Data Warehouse by the Linux OSagent. . . . . . . . . . . . . . . 314

116. Identifiers and resources that are collectedfrom Tivoli Data Warehouse by the UNIX OSagent . . . . . . . . . . . . . . 317

117. Identifiers and resources that are collectedfrom Tivoli Data Warehouse by the WindowsOS agent. . . . . . . . . . . . . . 320

118. SampleSecureGetVIOS.xml Parameters 335119. cpu . . . . . . . . . . . . . . . 338120. net . . . . . . . . . . . . . . . 340121. disk. . . . . . . . . . . . . . . 341122. mem . . . . . . . . . . . . . . 341123. VMware Parameters . . . . . . . . . 346124. Identifiers. . . . . . . . . . . . . 347125. Resources . . . . . . . . . . . . . 347126. Vmstat Identifiers . . . . . . . . . . 348127. Vmstat Resources . . . . . . . . . . 349128. Default Windows Disk Identifiers and

Resources (File System Collection) . . . . 352129. Default Windows Disk Identifiers and

Resources (Physical Disk Collection) . . . . 353130. Default Windows Disk Identifiers and

Resources (Logical Disk Collection) . . . . 353131. WinDisk Attributes . . . . . . . . . 354132. SampleDeployProcessCollector.xml Job File

Parameters . . . . . . . . . . . . 364

133. Windows Process Collector Log File Format -Process Records . . . . . . . . . . . 369

134. Windows Process Collector Log File Format System CPU Records . . . . . . . . . 370

135. Windows Process Collector Log File Format System Memory Records. . . . . . . . 371

136. Default Windows Process Identifiers andResources - Process . . . . . . . . . 372

137. Default Windows Process Identifiers andResources - System CPU . . . . . . . . 373

138. Default Windows Process Identifiers andResources - System Memory . . . . . . 373

139. Step attributes . . . . . . . . . . . 375140. Input element attributes . . . . . . . . 375141. Collector element attributes . . . . . . . 375142. Template element attributes . . . . . . . 376143. Feed parameter attributes . . . . . . . 376144. LogDate parameter attributes . . . . . . 376145. File parameter attributes . . . . . . . . 377146. z/VM resources that are collected for

chargeback . . . . . . . . . . . . 378147. Sample job files . . . . . . . . . . . 388148. Deployment Job File Parameters . . . . . 388149. Administration Utilities . . . . . . . . 392150. Environment Variables in the A_config.par

File . . . . . . . . . . . . . . . 394151. UNIX Operating System Identifiers . . . . 399152. UNIX Operating System Rate Codes . . . . 400153. File System Identifiers . . . . . . . . 401154. File System Rate Codes . . . . . . . . 401155. Advanced Accounting Process Metrics

Collected . . . . . . . . . . . . . 406156. Advanced Accounting System Metrics

Collected . . . . . . . . . . . . . 406157. Advanced Accounting File System Metrics

Collected . . . . . . . . . . . . . 408158. Advanced Accounting Network Metrics

Collected . . . . . . . . . . . . . 408159. Advanced Accounting Disk Metrics Collected 408160. Advanced Accounting Virtual I/O Server

Metrics Collected . . . . . . . . . . 408161. Advanced Accounting Virtual I/O Client

Metrics Collected . . . . . . . . . . 408162. Advanced Accounting ARM Transaction

Metrics Collected . . . . . . . . . . 408163. Advanced Accounting WPAR System Metrics

Collected . . . . . . . . . . . . . 409164. Advanced Accounting WPAR File System

Metrics Collected . . . . . . . . . . 409165. Advanced Accounting WPAR Disk I/O

Metrics Collected . . . . . . . . . . 409166. Environment Variables in the A_config.par

File . . . . . . . . . . . . . . . 410167. Variables for File Transfer to SmartCloud Cost

Management application server . . . . . 414168. Advanced Accounting Process Metrics

Collected . . . . . . . . . . . . . 415169. Advanced Accounting System Metrics

Collected . . . . . . . . . . . . . 415170. Advanced Accounting File System Metrics

Collected . . . . . . . . . . . . . 416

xii IBM SmartCloud Cost Management 2.3: User's Guide

171. Advanced Accounting Network MetricsCollected . . . . . . . . . . . . . 417

172. Advanced Accounting Disk Metrics Collected 417173. Advanced Accounting Virtual I/O Server

Metrics Collected . . . . . . . . . . 417174. CSR Files Produced by the CS_gen_sum

Script . . . . . . . . . . . . . . 425175. Process Definition Folders and CSR Files 427176. Variables for File Transfer to the SmartCloud

Cost Management Application Server . . . 427177. Problems and solutions for common problems 431178. DB2Utility.sh -h . . . . . . . . . . . 437179. Updated tables . . . . . . . . . . . 446180. Example of REST resources and HTTP

methods . . . . . . . . . . . . . 449181. Example of Links included in payload

elements . . . . . . . . . . . . . 450182. Properties of client resource element . . . . 452183. Properties of user resource element . . . . 452184. Properties of usergroup resource element 452185. Properties of accountCodeStructure resource

element . . . . . . . . . . . . . 453186. Properties of accountLevel resource element 453187. GET Resource clients . . . . . . . . . 456188. GET Resource clients . . . . . . . . . 458189. Post Resource clients . . . . . . . . . 459190. PUT Resource clients . . . . . . . . . 460191. DELETE Resource clients . . . . . . . 461192. GET Resource users . . . . . . . . . 462193. GET{id} Resource users . . . . . . . . 463194. POST Resource users . . . . . . . . . 464195. PUT Resource users . . . . . . . . . 465196. DELETE Resource users . . . . . . . . 467197. GET Resource usergroups . . . . . . . 467198. GET{id} Resource usergroups . . . . . . 469199. POST Resource usergroups . . . . . . . 471200. PUT Resource usergroups . . . . . . . 473201. DELETE Resource usergroups . . . . . . 476202. GET Resource accountCodeStructrues 477203. GET{id} Resource accountCodeStructrues 479204. POST Resource accountCodeStructrues 481205. PUT Resource accountCodeStructrue 483206. DELETE Resource accountCodeStructrues 486207. Jobs Element Attributes . . . . . . . . 488208. Job Element Attributes . . . . . . . . 490209. Process Element Attributes . . . . . . . 492210. Steps Element Attribute . . . . . . . . 494211. Step Element Attributes . . . . . . . . 494212. Acct specific parameter attributes . . . . . 498213. Bill specific parameter attributes . . . . . 500214. Cleanup specific parameter attributes 502215. Console parameter attributes . . . . . . 503216. Console specific parameter attributes 503217. DBLoad specific parameter attributes 504218. DBPurge specific parameter attributes 506219. FileTransfer specific parameter attributes 507220. FileTransfer parameters . . . . . . . . 507

221. FileTransfer parameters . . . . . . . . 509222. Rebill specific parameter attributes . . . . 510223. Scan specific parameter attributes . . . . . 511224. WaitFile specific parameter attributes 512225. Default Element Attributes . . . . . . . 513226. Defined thresholds . . . . . . . . . . 572227. Defined thresholds . . . . . . . . . . 573228. Date Ranges . . . . . . . . . . . . 595229. Account Summary YTD details . . . . . 597230. Account Total Invoice report details . . . . 598231. Application Cost report details. . . . . . 599232. Daily Charges - Charges report details 601233. Daily Crosstab - Usage report details 602234. Monthly Crosstab - Charges report details 604235. Monthly Crosstab Usage details . . . . . 605236. Percentage report details . . . . . . . . 606237. Summary Crosstab - Charges report details 607238. Summary Crosstab - Usage report details 609239. Weekly Crosstab - Charges report details 610240. Weekly Crosstab - Usage report details 611241. Client Budget report details . . . . . . . 612242. Line Item Budget report details . . . . . 613243. Project Summary report details . . . . . 615244. Top N Account Charges report details 617245. Top N Account Charges Pie Chart report

details . . . . . . . . . . . . . . 618246. Top N Rate Group and Rate Resource Usage

report details . . . . . . . . . . . 619247. Invoice by Account Level report details 620248. Invoice Detail Line Item Resource Units by

Identifiers report details . . . . . . . . 623249. Invoice Drill Down for Rate Group by Date

report details . . . . . . . . . . . 623250. Run Total Invoice details . . . . . . . . 624251. Run Total Rate Group Percent details 626252. Client report details . . . . . . . . . 627253. Configuration report details. . . . . . . 628254. Rate report details . . . . . . . . . . 628255. Batch report details . . . . . . . . . 629256. Charges by Identifier report details . . . . 630257. Detail by Identifier details . . . . . . . 633258. Detail by Multiple Identifier details . . . . 634259. Usage by Identifier report details . . . . . 635260. Template report details . . . . . . . . 638261. Template Account Code Date report details 638262. Template Account Code Year report details 639263. Top 10 Bar Graph report details . . . . . 640264. Top 10 Cost report details . . . . . . . 641265. Top 10 Pie Chart report details . . . . . . 643266. Cost Trend report details. . . . . . . . 644267. Cost Trend by Rate report details . . . . . 645268. Cost Trend Graph report details . . . . . 646269. Resource Usage Trend details . . . . . . 647270. Usage Trend Graph report details . . . . . 649271. Cost Variance report details . . . . . . . 650272. Resource Variance report details . . . . . 651

Tables xiii

xiv IBM SmartCloud Cost Management 2.3: User's Guide

PrefaceThis publication documents how to use IBM SmartCloud Cost Management..

Who should read this informationThis information is intended for administrators who install and configure IBMSmartCloud Cost Management, and for users who work with this product.

Copyright IBM Corp. 2013, 2014 xv

xvi IBM SmartCloud Cost Management 2.3: User's Guide

Chapter 1. Installing SmartCloud Cost Management 2.1.0.3Use the procedures in this section to install SmartCloud Cost Managementcomponents on a Linux operating system .

Installation overviewThis section describes the installation and configuration options available inSmartCloud Cost Management.

SmartCloud Cost Management 2.1.0.3 uses the following for reporting:v Cognos based Tivoli Common Reporting A list of the Cognos reports is available in the related Reference Reports section. Refer to the related links when installing Tivoli Common Reporting 3.1.0.1.

Installation options

The following install methods are available when installing SmartCloud CostManagement products on Linux operating systems:v Install using the DVD in the product package.v Downloading installation images from the IBM Passport Advantage site, if youare licensed to do so.

Use the provided installation script to perform the installation.

Note: To download SmartCloud Cost Management from Passport Advantage, seethe download instructions on the Passport Advantage website.

Installation configuration

The standard configuration for SmartCloud Cost Management is a distributedinstallation with SmartCloud Cost Management, Tivoli Common Reporting, andDB2 database each on their own system. The DB2 database is shared with otherOpenStack components. The Jazz for Service Management server that is used tohost Tivoli Common Reporting can also be shared with other components of IBMSmartCloud Orchestrator.

Supported hardware and software requirementsBefore you install the SmartCloud Cost Management application server, review thesoftware and hardware requirements for Linux platforms.

Note: For the complete listing of software product compatibility reports, see thefollowing link: at: http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity/index.htmlRelated reference:Installation dependencies on page 2This topic explains the dependencies for installing SmartCloud Cost Management2.1.0.3. Make sure that you understand the dependencies outlined in this topicbefore you install SmartCloud Cost Management 2.1.0.3.

Copyright IBM Corp. 2013, 2014 1

Requirements for Linux serversThis topic describes prerequisites for installing SmartCloud Cost Management on aLinux operating system.

Linux platforms

Note: For the complete listing of software product compatibility reports, see thefollowing link: at: http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity/index.html

Table 1.Software and hardware Requirements

Operating system v RHEL 5 and 6 for x64 (AMD64/EM64T).Note: RHEL 5 and 6 is supported byTivoli Common Reporting 3.1.0.1.

v SLES 10 and 11 for x64 (AMD64/EM64T)Browser Mozilla Firefox ESR 10, ESR 17

Hard disk drive space 5 GB minimum, 40 GB recommended(available hard disk drive space)Note: The hard disk drive spacerequirements for your organization mightvary.

Processor speed 3 GHz minimumNote: To ensure best performance withTivoli Common Reporting, processor speedsshould be at least 1 GHz for RISCarchitectures and 2 GHz for Intelarchitectures. Choosing faster processorsshould result in improved response time,greater throughput, and decreased processorutilization.

Memory 2 GB minimum

Installation dependenciesThis topic explains the dependencies for installing SmartCloud Cost Management2.1.0.3. Make sure that you understand the dependencies outlined in this topicbefore you install SmartCloud Cost Management 2.1.0.3.

Ensure that the software and hardware requirements have been satisfiedMake sure that you have your system setup correctly. For the latestupdates on hardware and software requirements, see the related referencetopic.

The user who is installing SmartCloud Cost Management has the requiredprivileges

SmartCloud Cost Management can be installed as root or a non-root user.If installing as a non-root user, ensure the user has permissions to write tothe directory you want to install into, and that you do not specify any portnumbers less than 1024.

Ensure that the 32-bit libstdc++ package is installedTo check if the package is installed, run the following command:# rpm -q libstdc++.i686

2 IBM SmartCloud Cost Management 2.3: User's Guide

If the package is not installed, run the following command:# yum install libstdc++.i686

Related concepts:Supported hardware and software requirements on page 1Before you install the SmartCloud Cost Management application server, review thesoftware and hardware requirements for Linux platforms.

Installing from the product DVDThis topic describes how to install SmartCloud Cost Management version 2.1.0.3from the product DVD.

About this task

The SmartCloud Cost Management Product DVD includes the product installationfiles and the corequisite files in the root directory. Run the installation files directlyfrom the product DVD to ensure that all of the corequisite files are in the requiredlocation. Copy the installation files and all corequisite files to a directory on theserver and run the installation files from that location. However, you must ensurethat all required files are in the same directory as they are on the DVD.

Procedure1. Log in to the system using the login credentials required for installing on a

Linux platform.2. Insert the DVD into the drive. If you are installing SmartCloud Cost

Management on a Linux platform, mount the DVD according to therequirements for your operating system. Contact your Linux administrator formore information about this procedure.

What to do next

The product is ready to install using the installation script.

Installing using the installation scriptThe installation for SmartCloud Cost Management is provided as a console modeinstall only. This may be used regardless of whether a GUI environment isavailable or not.

About this task

Installation of SmartCloud Cost Management 2.1.0.3 requires you to choose aninstallation directory, and optionally to choose the http and https ports that theserver will be available on. If not specified, the ports will default to 9080 and 9443respectively.

Procedure1. Log in to the system using the login credentials required for installing on a

Linux platform .2. Enter one of the following commands:

./sccm_install.sh /opt/ibm/sccm

or./sccm_install.sh sccm_install.properties

Chapter 1. Installing SmartCloud Cost Management 2.1.0.3 3

Note: The sccm_install.properties file can be modified as required.3. Follow the directions presented on the screen to complete the installation.4. If the installation was run as a non-root user, the SmartCloud Cost

Management Application Server is not automatically configured to run onsystem boot, as the installer would not have had permissions to do so. If youwant to manually configure this autostart, run the following script as root:SCCM_install_dir/bin/configure_autostart.sh

5. Launch the browser: https://host:port/Blaze/Console. For example,https://servername:9443/Blaze/Console

Uninstalling SmartCloud Cost ManagementIf required, you can uninstall SmartCloud Cost Management using the stepsdescribed in this section.

Before you begin

Ensure you back up any files you need to keep before running the uninstall script.

About this task

The installation process places an uninstall.sh script in the SCCM_install_dirdirectory.

Procedure1. Go to the SCCM_install_dir directory and run the uninstall.sh script as the

same user that was used to do the install, or as the root user.2. If you ran the script as a non-root user, you must remove the automatic startup

scripts from SmartCloud Cost Management. To do this, execute the followingcommands as root user:chkconfig --del ibm-sccmrm /etc/init.d/ibm-sccm

Results

The script stops the SmartCloud Cost Management and Metering Control Serviceservers and removes the software, along with any configuration or other itemsunder SCCM_install_dir.

Note: If required, you can also do a manual uninstallation of the product. Seerelated topic for more information.


Chapter 2. Configuration required for meteringThis section describes the configuration tasks required before using SmartCloudCost Management for metering.

Automated configurationMost of the post-installation configuration of SmartCloud Cost Management forSmartCloud Orchestrator is automated. This automation process is controlled byrunning the sco_configure.sh script as the same user that installed SmartCloudCost Management.

Prerequisites

Before running the sco_configure.sh script, you must ensure that the followingconditions are satisfied:v SmartCloud Orchestrator is installed and configured. For more information, referto the related installation section.

v The compute nodes are registered in DNS and are resolvable. For moreinformation about configuring the DNS while preparing the central server andthe region server, refer to the related topic.

v Jazz for Service Management 1.1.0.1 is installed with Tivoli Common Reporting3.1.0.1.

Run the sco_configure.sh script as follows:cd /bin/postconfig./sco_configure.sh --cs1 cs1host --keystonepass kspass --sccmuser smadmin --sccmpass smpass --jazz jazzsmhost --jazzuser smadmin --jazzpass smpass

Note: Running this script to configure Tivoli Common Reporting secures theAuthoring (Report Studio) and Administration functions with Tivoli CommonReporting. This may affect other products installed that use Tivoli CommonReporting. You must check that the security access in Tivoli Common Reporting isappropriate for all products after installation.Where:v cs1host is the host name of Central Server 1.v kspass is the password for the default Keystone admin user.v smadmin is the default admin user name for the SmartCloud Cost Managementor Jazz for Service Management Administration Console.

v smpass is the password for the default admin user for the SmartCloud CostManagement or Jazz for Service Management Administration Console.

v jazzsmhost is the host name of the Jazz for Service Management server.You may be prompted for the root passwords to Central Server 1, Central Server 2,and the Jazz for Service Management server during execution of this script. Thescript automatically completes the following configuration steps:v Creates the SmartCloud Cost Management DB2 database on Central Server 1.v Configures the sco_db2 data source in SmartCloud Cost Management andinitializes the database.

v Configures the os_keystone data source in SmartCloud Cost Management andruns the OpenStackContext.xml job file.

Copyright IBM Corp. 2013, 2014 5

v Sets up a cronjob to automatically run the various OpenStack job files to collectcontext and metering data from SmartCloud Orchestrator.

v Configures the Central User Registry to allow Keystone admin users to log in toSmartCloud Cost Management Administration Console.

v Enables metering notifications for all registered regions.v Configures the data sources for all registered SmartCloud Orchestrator regions inSmartCloud Cost Management.

v Enables SmartCloud Cost Management to listen to metering events fromSmartCloud Orchestrator.

v Imports the offering templates for SmartCloud Orchestrator which are used tocreate default rate codes and values.

v Imports the SmartCloud Cost Management reporting package into Jazz forService Management reporting.

v Configures the SmartCloud Cost Management data source in Jazz for ServiceManagement reporting.

v Assigns all Jazz for Service Management users access to run the reports.v Restricts Tivoli Common Reporting Administration and Authoring capabilities tothe Jazz for Service Management Admin user.

Related reference:Configuring the connection to OpenStack on page 248The Metering Control Service (MCS) uses an Advanced Message Queuing Protocol(AMQP) listener to collect notification events, such as Nova Compute notificationsfrom the OpenStack Apache Qpid message broker.

Logging in to the Administration ConsoleLog in to the Administration Console to set up and configure the SmartCloud CostManagement.

About this task

To log in to the Administration Console:

Procedure1. Start an Internet Explorer or Firefox Web browser, and type

https://:9443/Blaze/Console/ in the address bar. In this case defines the server that is running the Administration Console suchas server name or IP address.

Note: The port number should be substituted with the correct port number ifthe default port is not used.

2. On the Administration Console Welcome page, enter your login credentials andlog in.


Accepting the security certificateWhen logging in, you might see a security alert with a message that says there is aproblem with the security certificate. This indicates that the browser application isverifying the security certificate of the application server.

Self-signed or CA-signed certificate

The application server uses a self-signed security certificate. You might see aSecurity Alert when you first connect to the portal that alerts you to a problemwith the security certificate. You might be warned of a possible invalid certificateand be recommended to not log in.

Although this warning appears, the certificate is valid and you can accept it. Or, ifyou prefer, you can install your own CA-signed certificate. For information oncreating your own CA-signed certificate, go to: http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/tsec_sslcreateCArequest.html

For more information about certificates, go to the IBM WebSphere ApplicationServer Community Edition Documentation Project at http://publib.boulder.ibm.com/wasce/V2.1.1/en/overview.html, and search for Managingtrust and Managing SSL certificates.

Configuring the JDBC DriverJDBC is an application program interface (API) specification for connectingprograms written in Java to the data in a wide range of databases. To enableSmartCloud Cost Management Processing Engine to access a DB2 database, theappropriate JDBC drivers must be available on the server running SmartCloudCost Management.

Note: As part of the IBM SmartCloud Orchestrator release, the JDBC drivers forDB2 are available and automatically configured by the installation.

Adding a JDBC driverThe appropriate JDBC driver must be available for the SmartCloud CostManagement database and any databases from which data is collected bySmartCloud Cost Management Data Collectors. JDBC is an application programinterface (API) specification for connecting programs written in Java to the data ina wide range of databases. The appropriate JDBC drivers must be available on theserver running SmartCloud Cost Management.

About this task

The database used to store SmartCloud Cost Management data must use thefollowing driver:v For DB2 for Linux db2jcc.jar and db2jcc_license_cu.jar (license JAR file), wherethe version is appropriate for the database to be used in the data source forSmartCloud Cost Management.

You can use other drivers for databases used by SmartCloud Cost ManagementData Collectors.

Chapter 2. Configuration required for metering 7

Procedure

To add a new JDBC driver, copy the jar file to /wlp/usr/servers/sccm/dbLibs.

Note: Restarting the server is not required.

SmartCloud Cost Management Command Line InterfaceThe SmartCloud Cost Management Command Line Interface (CLI),/bin/sccmCLI.sh, is a generic tool that is used for querying andupdating various aspects of SmartCloud Cost Management configuration.

The CLI currently supports management of data sources and data loads, which isalso referred to as load tracking. The tool is Jython based and is usable bothinteractively and from scripts for automation. For specific details of the operationsthat are supported for individual areas, see the relevant sub topic for that area.

Before using the CLI, you must ensure that access credentials are provided for theAdministration Console. There are two methods to do this:v Set the relevant environment variables before running sccmCLI.sh:

export SCCM_USER=smadminexport SCCM_PASSWORD=password

v When running the sccmCLI.sh script, pass the credentials on the command line:./sccmCLI.sh --username smadmin --password password

Note: If neither of these options are specified, the CLI defaults to trying to connectwith a user of "smadmin" and a password of "password".

The following examples show general usage for both interactive and script usage:

Interactive usage./sccmCLI.shPython 2.5.3 (2.5:c56500f08d34+, Aug 13 2012, 14:54:35)[IBM J9 VM (IBM Corporation)] on java1.7.0Type "help", "copyright", "credits" or "license" for more information.(InteractiveConsole)>>> sccm.dataSources()[mydatasource].update({host: myhost})True>>> exit(0)

Usage from a shell script./sccmCLI.sh

Using the Command Line Interface to manage data sourcesThe Command Line Interface (CLI) can be used to manage data sources inSmartCloud Cost Management.

Where feasible, calls return True for success or False for failure. In the case of afailure, the error that is returned by the API call is displayed. Thesccm.dataSources() object supports the following methods:v refresh() - request the SmartCloud Cost Management server to reload the

registry.tuam.xml file.v createDatabaseDataSource({identifier:value, property:value, ...}) - createa new Database data source.

v createWebServiceDataSource({identifier:value, property:value, ...}) -create a new Web Service data source.

v createMessageBrokerDataSource({identifier:value, property:value, ...}) -create a new Message Broker data source.

v createServerDataSource({identifier:value, property:value, ...}) - create anew Server data source.

v keys() - return the identifiers of all available data sources

Individual data sources can be accessed by accessing dataSources() as a hash.Individual data sources must support the following methods:v test() - test the data source.v delete() - delete the data source.v update({property:value, ...}) - update the given properties of the data source.v initialise() - initialize the data source. This is only applicable for the Databasedata source that is used by the Administration Console UIs.

v upgrade() - upgrade the datasource. This is only applicable for the Databasedata source that is used by the Administration Console UIs.

Additionally, the following references are available:v sccm.databaseTypes - an array of database types available when creating adatabase data source.

v sccm.webServiceTypes - a hash of web service types available when creating aWeb Service data source.

The following example shows a sample run:$ cd etc/install/bin./sccmCLI.shPython 2.5.3 (2.5:c56500f08d34+, Aug 13 2012, 14:54:35)[IBM J9 VM (IBM Corporation)] on java1.6.0Type "help", "copyright", "credits" or "license" for more information.(InteractiveConsole)>>> ds = sccm.dataSources()>>> print ds{os_keystone: WebService, os_qpid_default: MessageBroker, SCCM: Database}>>> print ds[SCCM]{about: https://localhost:9443/sccmOslc/dataSources/databases/SCCM,actionTestDataSource: https://localhost:9443/sccmOslc/dataSources/databases/SCCM?oslc_ua.action=Test,database: None,databaseType: 4,host: localhost6,identifier: SCCM,isAdministrationDataSource: True,isDriverLoaded: True,isProcessingDataSource: True,


isTestable: True,objectPrefix: DB2INST1.,port: 1234,type: Database,userName: db2inst1}>>> ds[SCCM].test()400: Error getting connectionAUCCM5022E An error was detected in the data layer. The following information was provided:Connection refused. Review the trace log to get detailed information.False>>> ds[SCCM].update({port:60004})True>>> ds[SCCM].test()True>>> ds.refresh() # Ask server to reload registry.tuam.xml if manually modified>>> ds[SCCM].delete()

>>> print sccm.databaseTypes[Microsoft SQLServer, Oracle on Windows, Oracle on Linux/Unix, DB2 on Windows, DB2 on Linux/Unix, DB2 on zOS]>>> print sccm.webServiceTypes{Other: OTHER, VMware: VMWARE, REST: REST}

>>> ds.createDatabaseDataSource({identifier:dsname, databaseType:Oracle on Windows, title:mydb, host:myhost, userName:myuser, passw

Using the Command Line Interface to manage load trackingThe Command Line Interface (CLI) can be used to manage load tracking inSmartCloud Cost Management.

Where feasible, calls return True for success or False for failure. In the case of afailure, the error that is returned by the API call is displayed. Thesccm.dataLoads() has a single attribute that is called feeds, which contains all theavailable feeds, addressable as a hash map. Each individual field has two attributesthat are called years and loads. Years can be filtered at various levels ofgranularity as follows:v dl.feeds - Available feeds, addressable as a hashmap.v dl.feeds['SCO'] - Detail for the SCO feed.v dl.feeds['SCO'].years[2012] - Filtered for the year 2012.v dl.feeds['SCO'].years[2012][12] - Filtered for accounting period 12 in year2012.

v dl.feeds['SCO'].years[2012][12]['2011-12-28T00:00:00Z'] - Filtered for aspecific date in accounting period 12 in year 2012.

At each filter level, the loads attribute provides all the loads that match that filter.A loads object can be further filtered by load identifier to get more informationabout that load. The loads object also supports a delete method, which takes asingle true or false flag to indicate whether a full delete must be performed. Falsedeletes the database content only. True deletes both the database content and theload tracking entry.

The following example shows a sample run:$ cd /bin./sccmCLI.shPython 2.5.3 (2.5:c56500f08d34+, Aug 13 2012, 14:54:35)[IBM J9 VM (IBM Corporation)] on java1.6.0Type "help", "copyright", "credits" or "license" for more information.(InteractiveConsole)>>> dl = sccm.dataLoads()>>> print dl.feeds.keys()[TSM, LINUXKVM, NODBSIZE, EvtPrt, VMWARE, TPC, MSSQL2K, TUAMHMC, TPCPOOL, SCO]


>>> print len(dl.feeds[SCO].loads)1727>>> print len(dl.feeds[SCO].years[2012].loads)1098>>> print len(dl.feeds[SCO].years[2012][11].loads)90>>> print dl.feeds[SCO].years[2012][11].loads{1880: Summary,1881: Detail,1882: Ident,1883: Summary,...1967: Summary,1968: Detail,1969: Ident}>>> print dl.feeds[SCO].years[2012][11].loads[1968]{accountCodes: [Project Q [email protected] ,

Project N [email protected] ,Project U [email protected] ,

...Project Z [email protected] ,Project Z [email protected] VM189152095 ,Project Z [email protected] VM508743332 ],

groupIdentifier: 1098,identifier: 1968,totalRecords: 282,type: Detail }>>> dl.feeds[SCO].years[2012][11].loads[1968].delete(False)True>>> print dl.feeds[SCO].years[2012][11].loads[1968]/sccmOslc/dataLoads/feeds/SCO/loads/1968{accountCodes: None,groupIdentifier: 1098,identifier: 1968,totalRecords: 282,type: Detail }>>> dl.feeds[SCO].years[2012][11].loads[1968].delete(True)True>>> print dl.feeds[SCO].years[2012][11].loads[1968]None>>> dl.feeds[SCO].years[2012][11].loads.delete(True)True

Configuring the SmartCloud Cost Management data sourcesA data source is required to connect to the SmartCloud Cost Managementdatabase. A data source is also required for SmartCloud Cost Management DataCollectors that collect data from a database or a Web service.

Important: The SmartCloud Cost Management data sources are automaticallyconfigured by running the sco_configure.sh script after SmartCloud CostManagement is installed. For more information about this script, see the relatedtopic. However, if required you can manually create the data sources as explainedin this section.

There are four types of data sources in SmartCloud Cost Management:v Database: For DB2 databases that use the supported default drivers, these arethe data sources that connect to a database that you are collecting data fromusing a SmartCloud Cost Management Data Collector.

v Message broker: These are the data sources that connect to a Message Brokerthat you are collecting data from using a SmartCloud Cost Management DataCollector.


v Server: These are the data sources that connect to a server that you are collectingdata from using a SmartCloud Cost Management Data Collector.

v Web Service: These are the data sources that connect to a Web service that youare collecting data from using a SmartCloud Cost Management Data Collector.

Note: An All option is also available in the Data Source Type menu. Select thisoption if you want to view all data source types. When the All option is selected,the Create Data Source button is disabled.

Creating data sources

Note: Data source information is stored in /config/registry.tuam.xml. Manual editing of this file is not recommended. Triple DESand SHA-1 are used to secure credential information.

Adding a Database data sourceA Database data source is used to connect to a SmartCloud Cost Managementdatabase. A Database data source is used to connect to a DB2 for Linux, UNIX, andWindows; DB2 for z/OS; Oracle; or SQL Server database that you are collectingdata from using a SmartCloud Cost Management Data Collector.

Before you begin

Use the Database data source type to create data sources for DB2 for Linux, UNIX,and Windows; DB2 for z/OS; Oracle; or SQL Server databases that use thesupported default drivers that are described in Configuring the SmartCloud CostManagement data sources on page 11.

Procedure1. In Administration Console, click System Configuration > Data Sources and

select Database as the Data source Type.2. Click Create Data Source.3. Complete the following:

Note: All fields marked with an * are mandatory and must be completed.

Data Source NameType the name that you want to assign to the data source.

Note: The following are invalid characters for a data source name: "/","\",'"',":","?","",".","|",".".

UsernameType the database user ID.

PasswordType the database password.

Host Type the host name, IP address, or IP name where the database resides.

If you are using an Internet Protocol Version 6 (IPv6) address as thehost name, the IP address must be specified as follows:v Enclose the address with square brackets. For example, IPv6 address

aaaa:bbbb:cccc:dddd:eeee:ffff:aaaa:bbbb should be specified as[aaaa:bbbb:cccc:dddd:eeee:ffff:aaaa:bbbb].


Database NameType the name of the database that you want the data source to pointto.

For a DB2 for z/OS data source, the field contains a two-part entry of/. To determine the correct locationname, refer to the DDF configuration that is displayed in the z/OSstartup messages as shown in the following example:13.17.59 STC16980 DSNL003I :D81L DDF IS STARTING13.18.21 STC16980 DSNL004I :D81L DDF START COMPLETE 611

611 LOCATION KSCDB201611 LU USCACO01.DB2D81L611 GENERICLU -NONE611 DOMAIN demomvs.db2.ibm.com611 TCPPORT 446611 RESPORT 5020

In this example, the location is KSCDB201. If you create a DB2 for z/OSdatabase named TUAM71, you would type KSCDB201/TUAM71 in this field.

Database TypeSelect the type of database.

Object PrefixFor all database types other than Microsoft SQL Server, type theschema name for the database. This value is case-sensitive. Therefore, ifthe schema name is SmartCloud Cost Management, type SCCM and notsccm. Database schemas are defined using database administrationtools. If you do not know the schema name, consult your databaseadministrator.

For SQL Server, it is recommended that you type dbo.. This objectprefix sets the owner of the database objects in the database to dbo,which allows any authorized database user to view the objects.

Driver LoadedIf checked, this field Indicates that the database JDBC driver is loadedon the classpath and when the database data source is configured, itwill connect to the database. If unchecked, then the JDBC driver mustbe configured. See the related topic for more information.

Port By default, SmartCloud Cost Management will connect to one of thefollowing ports on the database server: 50000 (DB2 for Linux, UNIX,and Windows); 446 (DB2 for z/OS); 1433 (SQL Server); or 1521 (Oracle).If you are using a port other than one of these default ports, type theport number.

ParametersType any additional parameters that are required to enable connectionto the database.

Database URLType a URL if you want to use a URL other than the default. Forexample, you want to add properties to the URL.

4. Click Create to save the data source information. The new data source name isdisplayed in the Data Source Name menu.

Note: When the data source information is saved, the connection to thedatabase is verified. You should see a message at the top of the screenindicating that the connection was successful.

5. Click Cancel if do not want to create the data source.


Setting the Default Admin and Processing data sourceIf you are using multiple databases to store SmartCloud Cost Management data(for example, you have a production database and a development database) youmust select the data source for one database as the default for administration anddata processing. Note that this process is applicable for Database data sources only.


select Database as the Data Source Type.2. Select the required data source name from the Data Source Name menu.3. Click each of the following:

Default AdminIndicates whether the data source is currently used by the SmartCloudCost Management Administration Console application. If the DefaultAdmin checkbox is checked, this is the data source that theAdministration Console will use.

Default ProcessingIndicates whether the data source is currently used by the SmartCloudCost Management Job Runner utility. If the Default Processingcheckbox is checked, this is the data source that Job Runner will use.

Adding a Web service data sourceA Web Service data source is used to connect to a Web service that you arecollecting data from using a SmartCloud Cost Management Data Collector. Thistopic provides the steps to create Web Service data sources.


select Web service as the Data Source Type.2. Click Create Data Source.3. Complete the following:




UsernameType the Web service user ID.

PasswordType the Web service password.

URL Type the Web service URL as follows, using either the http or httpsprotocol as required:.http://:port

Orhttps://:port

Web Service TypeSelect Other, VMware, or REST as the web service type.


Keystore FileThe Keystore file contains the vCenter or REST server certificate that isused for authentication during the secure connection between thecollector and the vCenter web service. The password is used to accessthe file. Enter a valid path to the file.

Keystore PasswordType the Keystore password.


Note: When the data source information is saved, the connection to thevCenter or REST server is verified. You should see a message at the top of thescreen indicating that the connection was successful.


Adding a Server data sourceA Server data source is used to connect to a server that you are collecting datafrom using a SmartCloud Cost Management Data Collector. This topic provides thesteps to create Server data sources.


select Server as the Data Source Type.2. Click Create Data Source.3. Complete the following:




UsernameType the server user ID.

PasswordType the server password.

Host Type the host name, IP address, or IP name where the database resides.If you are using an Internet Protocol Version 6 (IPv6) address as thehostname, the IP address must be specified as follows:v Enclose the address with square brackets. For example, IPv6 address

aaaa:bbbb:cccc:dddd:eeee:ffff:aaaa:bbbb should be specified as[aaaa:bbbb:cccc:dddd:eeee:ffff:aaaa:bbbb].

ProtocolEnter the connection protocol, SSH or TCP. If this field is left empty, itdefaults to SSH.

Port Enter the port number. If this field is left empty, it defaults to 22. Thisnumber can be updated if you are using the non default Port number.


TimeoutEnter the timeout value. If this field is left empty, it defaults to 180000.This number can be updated if you want to use a non default timeoutvalue.

Private Key FileThe private key file is a file which contains an encrypted key forauthenticating during a secure connection. The passphrase is used toencrypt or decrypt the key file. Enter a valid path to the key file.

Restricted ShellSelect this check box if the connection to the server is a restricted shelltype.


Note: When the data source information is saved, the connection to thedatabase is verified. You should see a message at the top of the screenindicating that the connection was successful.


Adding a Message Broker data sourceA Message Broker data source is used to connect to a Message Broker that you arecollecting data from using a SmartCloud Cost Management Data Collector. Thistopic provides the steps to create Message Broker data sources.


select Message broker as the Data Source Type.2. Click Create Data Source.3. Complete the following:


UsernameType the message broker user ID.

PasswordType the message broker password.

Host Type the host name or IP address where the message broker resides.

Broker TypeSelect the type of message broker that you want to use. The default isQpid as this is currently the only supported message broker.

Client IDType the client id for the message broker. Client id is an identifierproperty stipulated by the JMS API specification which is supported byQpid message brokers.

Virtual HostType the Virtual host for the message broker. The Virtual host is a paththat acts as a namespace that is used to partition the message brokerdata into distinct sets.

ProtocolSelect the transport protocol that the message broker must use. Theprotocol currently defaults to TCP.


Port Type the Port number used by the message broker. This is initially setto the default Qpid Port number of 5672.

TimeoutType the timeout value of how long (in milliseconds) to wait for theconnection to succeed. The default value is 180000.

SSL EnabledSelect this check box if the connection to the message broker is overSecure Sockets Layer (SSL).


Note: When the data source information is saved, the connection to the datasource is verified. You should see a message at the top of the screen indicatingthat the connection was successful.


About initializing the databaseInitializing the database prepares the database for use by SmartCloud CostManagement. Initializing will overwrite any existing data. You will receive aconfirmation message if you attempt to initialize a database that has already beeninitialized.

Important: The database is initialized automatically by running thesco_configure.sh script after SmartCloud Cost Management is installed. For moreinformation about this script, see the related topic. However, if required you canfollow the steps in this section to manually initialize the database.

Initializing the database performs the following tasks:v Creates new database tablesv Populates these tables with an initial set of datav Creates necessary database objects

Initializing the databaseInitializing the database prepares the database for use by SmartCloud CostManagement. Initializing will overwrite any existing data. You will receive aconfirmation message if you attempt to initialize a database that has already beeninitialized.

Before you begin

If you are using multiple databases for SmartCloud Cost Management, make surethat the data source for

Documents

Sccm User Guide