IBM SmartCloud Control Desk Version 7 Release 5 › support › knowledgecenter › SSWT9A... · Virtualization executive (hypervisor) VMware vSphere 4.1 ... v VMware vCenter Server

IBM SmartCloud Control DeskVersion 7 Release 5

Installation Guide(VM Image)

��

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

Contents

Installing the IBM SmartCloud ControlDesk VMImage . . . . . . . . . . . . 1Planning for deployment . . . . . . . . . . 1

Roles and responsibilities . . . . . . . . . 1Hardware requirements. . . . . . . . . . 2Software requirements . . . . . . . . . . 3Virtual machine images . . . . . . . . . . 4Deployment process . . . . . . . . . . . 5Deployment dependencies . . . . . . . . . 5Deployment sequence . . . . . . . . . . 6Changing the product edition. . . . . . . . 6Post-deployment verification . . . . . . . . 7Planning for language support . . . . . . . 8Deployment worksheets . . . . . . . . . 9

Deployment worksheet for the DB2 virtualmachine . . . . . . . . . . . . . . 9Deployment worksheet for the WebSphereApplication Server virtual machine . . . . 11

Deploying the solution . . . . . . . . . . 13Prerequisites for deployment . . . . . . . 14Connecting to the VMware vCenter server . . . 14Deploying the virtual machine images . . . . 15

Preparing the virtual images. . . . . . . 15Deploying DB2 . . . . . . . . . . . 16Deploying WebSphere Application Server . . 19

Configuring initial data . . . . . . . . . . 23Configuring security . . . . . . . . . . . 24Importing data . . . . . . . . . . . . . 25

Notices . . . . . . . . . . . . . . 27Trademarks . . . . . . . . . . . . . . 29

Index . . . . . . . . . . . . . . . 31

© Copyright IBM Corp. 2012 iii

iv IBM SmartCloud Control Desk: Installation Guide (VM Image)

Installing the IBM SmartCloud Control Desk VMImage

The following topics describe what you must do to install the IBM SmartCloudControl Desk VMImage solution.

The functional components of the IBM SmartCloud Control Desk VMImagesolution are delivered as virtual machine (VM) images. These images can bedeployed on hardware provided by the customer.

Because IBM SmartCloud Control Desk VMImage is delivered as virtual machineimages, some aspects of the underlying operating system and product stack can beconfigured before deployment.

Deployment of the VMs is completed with an intuitive user interface that requestssome additional configuration parameters that cannot be determined beforedeployment.

After VMs are deployed and activation is completed, manual configuration ofcustomer-specific processing logic across multiple applications (for example, eventcorrelation) is performed using the user interfaces of the component products.

Before you attempt to deploy and configure IBM SmartCloud Control DeskVMImage, obtain the required hardware and software and then use theappropriate deployment checklist for each virtual machine to guide you throughthe installation process.

Planning for deploymentPlanning for deployment is critical to the success of an IBM SmartCloud ControlDesk VMImage implementation.

Successful planning includes analyzing how you are going to use the solution,obtaining the required hardware and software for deployment, and preparing thedeployment infrastructure.

Use this information to understand and effectively deploy IBM SmartCloudControl Desk VMImage in your environment to suit your business needs. Onceyou are comfortable with deployment concepts and planning material, you can usedeployment worksheets included with the documentation to record values you useduring the deployment process.

Roles and responsibilitiesAn IBM SmartCloud Control Desk VMImage solution implementation requirescoordination of the deployment across multiple roles.

Depending on your implementation, solution architects, designers, analysts,developers, and IBM® service team members can be key contributors in thedeployment of your IBM SmartCloud Control Desk VMImage solution.

System administrators and their counterparts are responsible for deploying andmaintaining the IBM SmartCloud Control Desk VMImage implementation.Administrators are expected to have technical skill in the following areas:

© Copyright IBM Corp. 2012 1

v Using the 64 bit SUSE Linux 11 operating system.v Using VMware technology and tools.v Working with virtual machines (VMs) and configuring VM connectivity.v Providing system administration for the component products that comprise the

IBM SmartCloud Control Desk VMImage solution.

Hardware requirementsReview the hardware requirements and ensure that your environment meets theminimum standards before you attempt to install IBM SmartCloud Control DeskVMImage.

The hardware requirement for your installation depends on how you plan toimplement the solution. Servers are required to house the VMware products thatdeploy the solution and to host the virtual machine images. When planning yourimplementation, ensure that you have adequate server capacity to host the virtualmachine images and to deploy the solution.

Requirement for virtual machine images

The following specification describes the minimum hardware required to host thevirtual machine images:v Four Intel or AMD x86 CPU-based server class computers where each server has

the following capacity:– 64-bit CPU architecture– Minimum of 6 cores for each hardware device– Minimum of 12 GB of RAM for each hardware device– Minimum of 250 GB of hard drive disk capacity for each hardware device

If your implementation requires a large number of sensors, generates a largenumber of events, or serves a large number of users, more hardware might berequired.

The following table shows the minimum hardware capacity required for eachvirtual image.

Table 1. Resources required for each virtual machine

Virtual imageNumber ofphysical cores

Disk space(GB) Memory (GB)

DB2® 4 100 4

WebSphere® Application Server 4 100 6

Requirement for deployment server

VMware vSphere 4.1 must be installed and configured before the virtual machinescan be deployed. For a list of hardware configurations supported by VMwaretechnology, see the compatibility guide available at the VMware Technical ResourceCenter.

Note that VMware ESXi supports only x86 architectures; therefore it requires AMDor Intel processors.

VMware vCenter Server can be installed on physical hardware running a Windowsoperating system that is supported by VMware vSphere. It can also be installed on

2 IBM SmartCloud Control Desk: Installation Guide (VM Image)

http://www.vmware.com/resources/techresources/cat/119

http://www.vmware.com/resources/techresources/cat/119

a virtual machine that runs a VMware vSphere-supported Windows operatingsystem as a guest. The virtual machine can run on one of the provisioned VMwareESXi hypervisors.

For information about the system requirements for VMware vCenter Server, see theESXi Installable and vCenter Server Setup Guide at the following link:http://www.vmware.com/pdf/vsphere4/r41/vsp_41_esxi_i_vc_setup_guide.pdf .

Software requirementsReview the software requirements and ensure that your environment meets theminimum standards before you attempt to install IBM SmartCloud Control DeskVMImage.

Table 1 summarizes the software requirements for IBM SmartCloud Control DeskVMImage.

Table 2. Software requirements

Software required Software version

Operating system SUSE Linux Enterprise Server 11 (64-bit).This operating system is provided with thevirtual machines in the IBM SmartCloudControl Desk VMImage solution.

Microsoft Windows. VMware vSphererequires a Windows operating system. Seethe link that follows to determine whichWindows operating system to use.

Virtualization executive (hypervisor) VMware vSphere 4.1

Internet browser Mozilla Firefox 3.5Microsoft Internet Explorer 7 or 8

For more information about database, middleware, and web browser support forthe component products delivered with the IBM SmartCloud Control DeskVMImage solution, see the information centers for the individual components.

Operating systems

Each virtual machine in the solution requires the 64-bit SUSE Linux EnterpriseServer (SLES) 11 operating system. The operating system is delivered as part of thevirtual machine images. All products comprising the IBM SmartCloud ControlDesk VMImage solution support SUSE Linux Enterprise Server 11.

Servers that are used to deploy the solution must use the Windows operatingsystem required by VMware vSphere 4.1.

Virtualization executive (hypervisor)

Because IBM SmartCloud Control Desk VMImage is delivered as virtual machineimages, VMware vSphere 4.1 is required to implement the solution.

VMware vSphere 4.1 and associated tools must be installed and configured beforeyou deploy the virtual machine images. This tooling should include the followingcomponents:v VMware vSphere 4.1. VMware vSphere includes the VMware ESXi 4.1

hypervisor that is required for deployment.

Installing the VMImage solution 3

http://www.vmware.com/pdf/vsphere4/r41/vsp_41_esxi_i_vc_setup_guide.pdf

v VMware vCenter Server 4.1.0. VMware vCenter Server is a required, separatelylicensed component of a VMware vSphere implementation. VMware vCenterServer can be installed on physical hardware running a Windows operatingsystem that is supported by VMware vSphere. It can also be installed on avirtual machine that runs a VMware vSphere-supported Windows operatingsystem as a guest. The virtual machine can run on one of the provisionedVMware ESXi hypervisors.

v VMware vSphere client. Install the client on a Windows-based administrativeworkstation that is supported by VMware. The client is used to connect directlyto a VMware ESXi host or to the central VMware vCenter Server installation andmanage the virtual infrastructure.

For information about the system requirements for VMware vCenter Server, see theESXI Installable and vCenter Server Setup Guide.

Note: You should be familiar with the installation and configuration of virtualmachines when using the VMware ESXi hypervisor software.

Virtual machine imagesIBM SmartCloud Control Desk VMImage includes two virtual machine images thatmust be deployed to implement the solution.

The virtual machine images are packaged in Open Virtualization Format (OVF)templates. Each OVF template contains the following files:v OVF descriptor file. OVF descriptor files are used to deploy the virtual machine

into the hypervisor.v VMDK (Virtual machine disk) file. Each virtual machine image contains one or

more files that encapsulate the entire virtual machine environment.v Resource .xml files. Each image contains multiple files that support the localized

messages displayed when the OVF appliance is deployed and present the licenseterms and conditions.

Each OVF template is deployed into the VMware virtual infrastructure using theVMware vCenter Server. A particular physical VMware vCenter Server host can bechosen to be the target of the deployment. All deployment activities are carried outby signing into VMware vCenter Server using the VMware vSphere client.

The OVF standard is maintained by the Distributed Management Task Force(DMTF). For information about the OVF standard, see the Open VirtualizationFormat (OVF) page on the DMTF web site: http://www.dmtf.org/standards/ovf.

Table 1 describes the virtual machine images.

Table 3. Virtual machine images

Virtual machine Product/component

DB2 virtual machine IBM DB2 9.7 database for IBM SmartCloud Control DeskVMImage

WebSphere ApplicationServer virtual machine

IBM SmartCloud Control Desk VMImage 7.5


http://www.vmware.com/pdf/vsphere4/r41/vsp_41_esxi_i_vc_setup_guide.pdf

http://www.dmtf.org/standards/ovf

Deployment processIBM SmartCloud Control Desk VMImage provides installation instructions andvarious checklists that can be used to guide you through the deployment process.It is important to understand the entire deployment process before attempting toimplement the solution.

The wizard that is provided with IBM SmartCloud Control Desk VMImage guidesyou through deployment of the solution's virtual machines (VMs). The wizard islaunched from the VMware vSphere client. The steps required to deploy eachvirtual machine image for the IBM SmartCloud Control Desk VMImage solutionare similar. Some steps are identical for each virtual machine. Other steps requireparameters that are specific to the virtual machine. In addition, some VMs requirepost-deployment configuration.

Because some products in the solution have dependencies on other products orcomponents, the virtual machine images must be deployed and configured in aspecific sequence.

Review the following steps, which describe the general process for deploying thevirtual machine images:1. Perform the preliminary steps needed to prepare the host machines and the

VMware deployment environment.2. Gather the network configuration information that will be requested during

deployment of the VMs.3. Copy or transfer the QI_SCCD_DB2.ovf and QI_SCCD_WAS.ovf templates into

a file system that is accessible to the VMware vSphere client, which is used todeploy the VMs.

4. Perform the following steps for each virtual machine.a. Use the deployment wizard to deploy the VM to the host machine.b. After the VM is deployed to the host, use the VMware vSphere client to

power on the VM. This turns on the machine and configures it for first use.c. Perform the post-deployment verification checks.d. If necessary, perform the post-deployment configuration steps required by

the VM.

Additional detail about these steps is provided in the deployment section of theinformation center. The following deployment aids are available to assist in thedeployment process.v Deployment worksheets that you can use to gather the individual parameters

that are needed for the specific VMs.v Detailed instructions for installing each VM.

Deployment dependenciesThe component products in the IBM SmartCloud Control Desk VMImage solutionwork together to provide smart building data. Some components havedependencies on other products in the solution.

The dependencies between components affects deployment and maintenance of thevirtual machines included in the solution. Deployment must be performed in aspecific sequence. You must first deploy the DB2 virtual machine and then deploythe Websphere Application virtual machine. The WebSphere Application virtualmachine is dependent on the DB2 virtual machine. Upgrades to the product shouldalso take into account the component dependencies.


Because the products and components are interdependent, all virtual machinesmust have the same time zone setting.

The WebSphere Application Server virtual machine is dependent on the DB2virtual machine. The WebSphere Application Server virtual machine accesses theMaximo database to post or retrieve IBM SmartCloud Control Desk VMImagedata.

Deployment sequenceBecause of dependencies that exist between some of the products included in theIBM SmartCloud Control Desk VMImage solution, the virtual machine images forthe products must be deployed and configured in a specific sequence.

The following deployment sequence is required for IBM SmartCloud Control DeskVMImage:1. DB2 virtual machine for the Maximo® database on IBM DB22. WebSphere Application Server virtual machine for IBM SmartCloud Control

Desk VMImage 7.5

Changing the product editionThe product edition contained in the VM images is IBM SmartCloud Control Desk- Entry Edition. If you have purchased a different edition, you can modify the VMimage after you have installed it.

About this task

In addition to the VM images, you received a set of product DVDs, or theentitlement to download product images. These DVDs or images contain theinstallable copy of the product edition that you purchased. If you purchased IBMSmartCloud Control Desk or IBM SmartCloud Control Desk - Service ProviderEdition, you can use the installable copy of the product to modify the VM imageafter you have deployed it.

You can use the same procedure if you have purchased and installed the Entryedition and later purchase a different edition.

Procedure1. Complete the deployment of the VM image as described in this guide. If you

are changing editions as part of your initial deployment, do not perform initialdata configuration.

2. Mount the product DVD or installable image for the edition that you purchasedon the VM where you deployed the WebSphere ApplicationServer/administrative workstation image.

3. Invoke the product installer. It recognizes that the Entry edition is installed andmodifies the current deployment to the edition that it contains.

4. You can use the default configuration or change it to suit your needs. If youplan to install the Advanced Content package after your edition change, deferthe EAR deployment and the updatedb actions at this time, and let theAdvanced Content package installation execute those actions.

5. After the successful installation of the new edition, stop MXServer onWebSphere, go to the opt/ibm/WebSphere/AppServer/profiles/ctgAppSrv01/temp/ctgNode01/MXServer directory and delete the MAXIMOIEHS folder.After deleting the folder, start MXServer.


6. Perform the post-deployment verification steps.

Results

Your new edition is ready for use. If you have not yet performed initial dataconfiguration, do it now.Related concepts:“Deploying the solution” on page 13Use this information to deploy and configure the IBM SmartCloud Control DeskVMImage solution.“Post-deployment verification”After deployment, it is important to verify that the virtual machine images aredeployed as expected.“Configuring initial data” on page 23Before using the product, you must configure several options.

Post-deployment verificationAfter deployment, it is important to verify that the virtual machine images aredeployed as expected.

After the virtual machines are deployed, perform the following checks todetermine whether deployment was completed successfully:v Check that the OVF activation engine successfully executed the virtual machine

activation scripts. To perform this check, review the activation logs available in adesignated folder in the virtual machine.

v Check that the services that are set to start automatically start as expected. Toperform this check, execute the appropriate commands in the Linux console.

v Check that the associated web application for a product or component isavailable. To perform this check, launch a web browser, access the webapplication, and log into the web application using the appropriate user ID andpassword.

Detailed post-deployment verification steps for each virtual machine are providedin the deployment documentation.

Activation engine, scripts, and logs

The activation engine is the runtime enablement framework that IBM uses forcustomization of virtual images when the machines are initially turned on. In theIBM SmartCloud Control Desk VMImage solution, the activation engine isembedded in each of the virtual images and executes once during the deploymentof the OVF templates. For each virtual image, the activation engine executes a setof activation scripts that configure the virtual machine and the IBM SmartCloudControl Desk VMImage solution products or components within the virtualmachine.

For the IBM SmartCloud Control Desk VMImage solution, the activation enginecreates log files in the /opt/IBM/AE/log folder in the Linux file system of thevirtual machine. If the activation engine encounters any execution errors, anerror.log file is written to this folder. An additional trace.log file is written withoutregard to failure or success of the deployment. If an error.log file is created, reviewthe contents of the log file to identify any activation errors.


Each activation script run by the activation engine produces its own log file in the/opt/IBM/AE/AR folder. Review the contents of this log file to check that noerrors were encountered during the execution of the particular script.

Startup services

The IBM SmartCloud Control Desk VMImage solution activation scripts configureeach virtual machine to start key server processes automatically. Once each virtualmachine is turned on, a Linux console can be launched and the Linux ps commandcan be run to verify whether the server processes are executing. For someproducts, product-specific commands are executed to verify process status.

Web applications

The IBM SmartCloud Control Desk VMImage solution delivers a number of webapplications that execute in the WebSphere Application Server. Once the virtualmachine is turned on and server processes started, a workstation can be used toverify whether the web applications are available. Entering the application URL ina web browser should open the application's home page.

Planning for language supportIBM SmartCloud Control Desk VMImage supports multiple languages. The virtualmachine images are configured for English. Post-deployment configuration to addtranslated content is required for implementations that require a differentlanguage.

Supported languages

The following languages are supported:v Arabic (ar)v Brazilian Portuguese (pt_BR)v Chinese, Simplified (zh_CN)v Chinese, Traditional (zh_TW)v Croatian (hr)v Czech (cs)v Danish (da)v Dutch (nl)v Finnish (fi)v French (fr)v German (de)v Hebrew (he)v Hungarian (hu)v Italian (it)v Japanese (ja)v Korean (ko)v Norwegian (no)v Polish (pl)v Russian (ru)v Slovak (sk)v Slovenian (sl)


v Spanish (es)v Swedish (sv)v Turkish (tk)

Translation availability when deploying the virtual machines

When you deploy the virtual machine images, the language that you see in thedeployment wizard is determined by the locale configured for the Windowsoperating system of the VMware vSphere client. For example, if the operatingsystem locale is French, the panels in the wizard will be displayed in French.

There are three license agreements presented during deployment. In some cases,the license agreements are available only in English. The VMware license isavailable only in English. The license agreement for SUSE Linux is not available inHebrew. The license agreement for IBM SmartCloud Control Desk VMImage is notavailable in Hebrew or Arabic.

Post-deployment tasks for language updates

If you use a language other than English, immediately after you deploy the virtualmachines you must change the base language for the product. If your languagepreference is not English, you must change the base language settings before youload data to the Maximo database or perform any configuration. When you changethe base language, you also have the option to add languages.

Deploying translated information

The information center provided at the initial availability of the product is inEnglish only. A news announcement will be posted on the product support sitewhen the translated copy is available for download. When it is available, you candownload the translated information and deploy it in your environment.

Deployment worksheetsUse the virtual machine deployment worksheets to record information that youmust supply when you deploy the IBM SmartCloud Control Desk VMImagevirtual images.

The worksheets can be used to provide the values that are requested by the IBMSmartCloud Control Desk VMImage deployment wizard.

Deployment worksheet for the DB2 virtual machineUse this worksheet to record information that is needed to deploy the DB2 virtualmachine.

Table 4. Deployment worksheet for the DB2 virtual machine

Item Description Value

Inventory location Location of the virtual machine in theVMware vSphere infrastructure.

Resource pool Used to allocate host-provided CPU andmemory to the virtual machines residentto the host or cluster.


Table 4. Deployment worksheet for the DB2 virtual machine (continued)


Data store Logical containers that store virtualmachine files and other files necessaryfor virtual machine operations.This is a virtualized representation of theunderlying physical storage.

Network Virtualized network configuration that isused by the virtual machine tocommunicate with other virtual machinesor the physical network outside of thevirtual infrastructure. The networkspecified in the OVF template must bemapped to an available networkconfiguration.This includes vNetwork StandardSwitches (vSwitches) and vNetworkDistributed Switches. vNetwork StandardSwitches are associated with a single hostand are discovered when hosts are addedto the vSphere environment. vNetworkDistributed Switches span multiple hosts.

Locale Locale setting for the guest operatingsystem that runs on the virtual machine.The locale setting drives locale-sensitivebehaviors of applications and processes.The locale parameter is broken out intothree fields:

v Language (defaults to en)

v Territory (defaults to US)

v Encoding (defaults to UTF-8)

Language:

Territory:

Encoding:

Networkconfiguration

Various network-related aspects of thevirtual machine must be configured.

v Boot protocol Specify whether the internal networkdevice is initialized with a static orDHCP protocol. Defaults to ‘static'.

v Host name Host name of the virtual machine. Do notuse the fully qualified name. Forexample, use myhost rather thanmyhost.example.com.

v Domain The fully qualified domain name (FQDN)for the virtual machine. For example, forthe virtual machine myhost.example.comthe FQDN is example.com.

v IP address (staticor DHCP)

If using the static boot protocol, specifythe IP address of the virtual machine.Specify a host address within a networkor specify that IPv4 or IPv6 DHCP serveris available on the network.

v Netmask If using the static boot protocol, specifywhich portion of the IP address specifiesthe subnetwork number and whichportion specifies the host. In mostnetworks, the value is 255.255.255.0.


Table 4. Deployment worksheet for the DB2 virtual machine (continued)


v Gateway Configure gateways for the serviceconsole and the VMkernel to allownetwork connectivity to machines not onthe same IP subnet.If using the static boot protocol, specifythe IP address of the machine that servesas the gateway to the network.

v Primary DNS If using the static boot protocol, specifythe primary Domain Name System IPaddress.

v Secondary DNS If using the static boot protocol, specifythe secondary Domain Name System IPaddress.

v Root password The password for the root(administrator) account of operatingsystem on the virtual machine.

v Virtual userpassword

The password for the virtuser account.This account is the defaultnon-administrator account for theoperating system on the virtual machine.

Deployment worksheet for the WebSphere Application Servervirtual machineUse this worksheet to record information that is needed to deploy the WebSphereApplication Server virtual machine.

Table 5. Deployment worksheet for the WebSphere Application Server virtual machine


Inventory location Location of the virtual machine in theVMware vSphere infrastructure.

Resource pool Used to allocate host-provided CPU andmemory to the virtual machines residentto the host or cluster.

Data store Logical containers that store virtualmachine files and other files necessaryfor virtual machine operations.This is a virtualized representation of theunderlying physical storage.


Table 5. Deployment worksheet for the WebSphere Application Server virtual machine (continued)


Network Virtualized network configuration that isused by the virtual machine tocommunicate with other virtual machinesor the physical network outside of thevirtual infrastructure. The networkspecified in the OVF template must bemapped to an available networkconfiguration.This includes vNetwork StandardSwitches (vSwitches) and vNetworkDistributed Switches. vNetwork StandardSwitches are associated with a single hostand are discovered when hosts are addedto the vSphere environment. vNetworkDistributed Switches span multiple hosts.

Locale Locale setting for the guest operatingsystem that runs on the virtual machine.The locale setting drives locale-sensitivebehaviors of applications and processes.The locale parameter is broken out intothree fields:

v Language (defaults to en)

v Territory (defaults to US)

v Encoding (defaults to UTF-8)

Language:

Territory:

Encoding:

Networkconfiguration

Various network-related aspects of thevirtual machine must be configured.

v Boot protocol Specify whether the internal networkdevice is initialized with a static orDHCP protocol. Defaults to ‘static'.

v Host name Host name of the virtual machine. Do notuse the fully qualified name. Forexample, use myhost rather thanmyhost.example.com.

v Domain The fully qualified domain name (FQDN)for the virtual machine. For example, forthe virtual machine myhost.example.comthe FQDN is example.com.

v IP address (staticor DHCP)

If using the static boot protocol, specifythe IP address of the virtual machine.Specify a host address within a networkor specify that IPv4 or IPv6 DHCP serveris available on the network.

v Netmask If using the static boot protocol, specifywhich portion of the IP address specifiesthe subnetwork number and whichportion specifies the host. In mostnetworks, the value is 255.255.255.0.


Table 5. Deployment worksheet for the WebSphere Application Server virtual machine (continued)


v Gateway Configure gateways for the serviceconsole and the VMkernel to allownetwork connectivity to machines not onthe same IP subnet.If using the static boot protocol, specifythe IP address of the machine that servesas the gateway to the network.

v Primary DNS If using the static boot protocol, specifythe primary Domain Name System IPaddress.

v Secondary DNS If using the static boot protocol, specifythe secondary Domain Name System IPaddress.

v Root password The password for the root(administrator) account of operatingsystem on the virtual machine.

v Virtual userpassword

The password for the virtuser account.This account is the defaultnon-administrator account for theoperating system on the virtual machine.

v IP address for theMaximo databasehost

The IP address for the host running theMaximo database.

v Hostname for theMaximo databasehost

The fully qualified hostname for the hostrunning the Maximo database.

Note: The virtual machine that hosts the Maximo database must be running andthe server processes must also be running when you configure the WebSphereApplication Server OVF template. If this is not the case, IBM SmartCloud ControlDesk VMImage will not start successfully.

Deploying the solutionUse this information to deploy and configure the IBM SmartCloud Control DeskVMImage solution.

Deploying the solution includes the following tasks:1. Complete the preliminary steps that are needed to obtain the appropriate

hardware and software and the prepare the deployment environment.2. Deploy the virtual machine images for the products and components in the

solution, in the required sequence.3. Verify that the virtual machine has been deployed correctly.4. Perform post-deployment configuration steps that are needed to customize

your implementation.

For complete deployment instructions, see the deployment procedures provided foreach individual virtual machine in the solution.


Prerequisites for deploymentBefore you begin to deploy the IBM SmartCloud Control Desk VMImage solution,you must create the infrastructure needed to deploy the virtual machine images.

You must purchase and install the hardware and software required to deploy thesolution and to host the virtual machine images. After you install the requireddeployment infrastructure, additional steps are required to prepare the hostmachines for the virtual image deployment.

Before you start the installation process, complete the following prerequisite tasks:1. Identify, purchase, and install the hardware required to deploy the solution and

to host the virtual machine images.2. Identify, purchase, and install the software products that are required for

deployment. Make sure that you apply any patches that are required for thesoftware. To configure your infrastructure for deployment, ensure that youpurchase and install the following software:v VMware vSphere 4.1. VMware vSphere includes the VMware ESXi 4.1

hypervisor that is required for deployment.v VMware vCenter Server 4.1.0. VMware vCenter Server is a required,

separately licensed component of a VMware vSphere implementation.v VMware vSphere client. Install the client on a Windows administrative

workstation that is supported by VMware. A minimum of 250 GB of freedisk space is required on the VMware vSphere client to process the virtualmachine template files. Ensure that there is sufficient disk space on the clientsystem.

3. Install the VMware ESXi 4.1 hypervisor on the machines that will host thevirtual images.

4. Add the VMware ESXi-installed host machines to the VMware vCenter Serverinventory.

5. Create administrative user IDs and passwords as required for yourimplementation.

6. Collect the properties and network configuration information that will berequested as you deploy the virtual machines. The deployment documentationincludes worksheets for the specific virtual machines. You can use theworksheets to record information that will be requested by the deploymentwizard.

Note: If you plan to use static IP addresses for the virtual machines, it isrecommended that you obtain addresses for all of the virtual machines at once.This can save time as you proceed with sequential deployment.

Connecting to the VMware vCenter serverThis topic describes how to connect to the VMware vCenter server to select yourdatastore and target host.

About this task

To connect to the VMware vCenter server:

Procedure1. Start the VMware vSphere client.


2. Enter your IP address or host name. To manage multiple hosts, enter the IPaddress or name of the vCenter server.

3. Enter your username and password, and click the Login button.

Deploying the virtual machine imagesThe following topics explain how to deploy the virtual machine images for theproducts and components provided in the IBM SmartCloud Control DeskVMImage solution.

IBM SmartCloud Control Desk VMImage virtual machines are packaged as OpenVirtualization Format (OVF) templates. Each OVF template is deployed into theVMware vSphere virtual infrastructure using the VMware vCenter Server. Aspecific physical VMware ESXi host can be the target of the deployment. Alldeployment activities are carried out by logging into the VMware vCenter Serverenvironment using the VMware vSphere client.

Before you attempt to deploy the virtual machines, check that you have completedall the deployment prerequisites and have prepared the virtual machine images fordeployment.

Preparing the virtual imagesThis topic describes how to prepare the IBM SmartCloud Control Desk VMImageimages for use in the VMware environment. Complete this procedure before youdeploy the virtual machines.

Before you begin

The following procedure requires that you install the VMware vSphere client on aWindows computer that can connect to VMware vCenter Server. You can use anyWindows operating system that is supported by VMware vSphere client. Thecomputer must have at least 50 GB of free disk space.

About this task

Before you can deploy the virtual images on the target hypervisor, prepare the IBMSmartCloud Control Desk VMImage virtual images obtained from the physicalmedia as follows.

Procedure1. On the machine where you have installed the VMware vSphere client, create a

folder to receive the virtual machine files. The files require 50 GB of free space.2. Copy the files SCCD_EE_<n>of<m>_V750_VMImage.part from the Quick Start DVD

or Passport Advantage® into the folder.3. Run the following command to merge the split files into the complete zip file:

v Windows: copy /b f1.part+f2.part+f3.part SCCD_QI_V75.zip, where f1, f2,and so on refer to the names of the files in the folder. Be sure to specify thefile names in numeric order, so that they will be concatenated in the properorder.

v Other platforms: cat SCCD*.part >> SCCD_QI_V75.zip

4. Confirm that the zip file is assembled correctly by verifying its checksumvalues:a. Run the following command to generate the checksum values for the zip

file: md5sum -b SCCD_QI_V75.zip


b. Compare your generated checksum values with the values in the providedMD5SUMS text file.

Deploying DB2The DB2 virtual machine provides the database repository for the IBM SmartCloudControl Desk VMImage product.

The DB2 OVF template encapsulates a virtual machine that contains IBM DB2version 9.5, which serves as the IBM SmartCloud Control Desk VMImagerepository.

Deploying the DB2 virtual machine:

This procedure explains how to deploy the DB2 virtual machine.

About this task

The following instructions explain how to deploy the DB2 virtual machine image.

Procedure

1. Log in to the VMware vSphere client and navigate to Home > Inventory >Hosts and Clusters.

2. Select File > Deploy OVF Template.3. On the Source panel in the deployment wizard, select one of the following

options:v Click Browse, select the QI_SCCD_DB2.ovf OVF template from the file

system, and click Next.v Type the absolute path and file name for the OVF template, and click Next.

4. On the OVF Template Details panel, review the OVF template details andclick Next.

5. On the End User License Agreement panel, accept the end user licenseagreements. There are 3 license agreements associated with the IBMSmartCloud Control Desk VMImage.

Option Description

To accept the license agreement for IBMSmartCloud Control Desk VMImage,

Review the license agreement and clickAccept.

To accept the license agreement forVMware tools,


To accept the license agreement for theSUSE Linux operating system that runs asthe guest operating system in the virtualmachine,


6. Click Next.7. On the Name and Location panel, complete the following steps:

a. Specify a name for the virtual machine that you are creating.b. Select an Inventory location.c. Click Next.

8. On the Host/Cluster panel, select the stand-alone host or cluster on which todeploy the OVF template and click Next.


9. Optional: In the Resource Pool panel, select the resource pool where thedeployed OVF template will run and click Next. This step is displayed only ifthe virtual infrastructure is clustered and contains a resource pool.

10. Optional: In the Datastore panel, select a data store and click Next. If multipledata stores have been set up in the virtual infrastructure, choose the specificdata store that will hold the virtual storage for the virtual machine. The datastore for the DB2 virtual machine requires 100 GB free.

11. On the Disk Format panel, specify a disk format for the virtual disks that arecreated to store the virtual machine and click Next. The default selected isThick Provisioned Format.

12. Specify a network and click Next. If multiple networks exist in the virtualinfrastructure, choose the specific network to use for the virtual machine.

13. Enter the specific properties that are required for the virtual machine that youare deploying and click Next. See the worksheets created when planning yourdeployment for the required parameters.

14. In the Ready to Complete panel, review the summary of the parameters thatyou have configured and click Finish. For troubleshooting purposes, take ascreen capture of the data in the Ready to Complete panel to provide a recordof the properties and values that you specified.

Results

After the deployment is complete, a new entry for the DB2 virtual machine isdisplayed in the Hosts and Clusters view for the host that was selected.

What to do next

Turn on the virtual machine by right-clicking the new entry for the DB2 virtualmachine and selecting Power > Power On.

Verifying deployment of the DB2 virtual machine:

This procedure explains how to verify deployment of the DB2 virtual machine.

About this task

The following steps explain how to verify the deployment.

Procedure

1. Log in to the Linux console as root using the password that you specified forthe virtual machine. Successful login confirms that the password functionscorrectly.

2. After a successful login, open a command prompt shell window.3. To verify that the host name that was specified during deployment is accurate,

complete the following steps:a. On the command line, type hostname and press Enter.b. Check that the host name is correct.

4. To verify that the IP address that was specified during deployment is accurate,complete the following steps:a. On the command line, type ifconfig and press Enter.b. Check that the IP address is correct.

5. On the command line, type ps -ef | grep db2 and press Enter.


6. Check that the following processes are running:v Db2sysc. This is the DB2 system controller process.v Db2dasrrm. This is the DB2 administrative server process.v Db2fmd. This is the fault monitor daemon for db2inst1.

7. To verify that the database schema is active, complete the following steps:a. At the command line, type the su - ctginst1 command and press Enter.b. Type db2 and press Enter.c. At the db2 command prompt, type list active databases and press Enter.d. Check that the single active database schema maxdb71 is returned.

8. To verify that the database is populated, check the database for a known value:.a. To connect to the database, at the db2 command prompt, type connect to

maxdb71.b. Type select count(*) from maximo.maxvars

c. Check that the preceding command ran successfully and returned a valuegreater than zero.

What to do next

After you verify the deployment of the DB2 virtual machine, you can optionallysynchronize the time clock on the machine and then deploy the WebSphereApplication Server virtual machine.

Synchronizing the time clock:

After the IBM SmartCloud Control Desk VMImage virtual machine is deployed,you can optionally synchronize the time clock on the virtual machine to ensureaccuracy.

About this task

To synchronize the time clock for the virtual machine, complete the followingsteps.

Procedure

1. Log in to the Linux OS console as root.2. Open the following file in an editor:

/etc/ntp.conf.3. The ntp.conf file contains one or more properties named server. Select one of

the following options:v Locate the server property that specifies timeserver.com and change the

timeserver.com property to an external time server such as time.nist.gov.v If there is no server property that specifies timeserver.com, add a new line

that has the following property:server hostname of external time server.

4. Save the file.5. In a command shell, execute the netconfig update -m ntp command. This

command updates daemon.6. To verify the synchronization, open the /var/log/ntp file, scroll to the bottom

of the file, and check that the time synchronization was successful. A successfulresult is similar to the following example.


19 May 08:21:55 ntpd[7302]: synchronized to 192.43.244.18, stratum 119 May 08:21:55 ntpd[7302]: kernel time sync status change 2001

Resetting passwords on the DB2 virtual machine using setPasswords.sh:

This procedure details how to reset passwords on the DB2 virtual machine usingsetPasswords.sh

About this task

You can use the setPasswords.sh shell script to reset all users' passwords in theDB2 Tivoli®'s process automation engine (TPAE) database, and some otheradministration passwords in DB2, WebSphere Application Server and Maximo. Thescript is located in the /opt/IBM/SMP/maximo/nvsfiles/deployscripts/adminScripts directory.

To use this script you must create an ini file to contain the new passwords. The inifile must reside in the same location as the script. This ensures that the ini file isdetected by the script when the script is executed. A sample ini file is provided in/opt/IBM/SMP/maximo/nvsfiles/deployscripts/adminScripts/admin-config.ini.sample. Copy this sample ini file and edit it to contain the desiredpasswords. Once the ini file is successfully processed it is automatically deleted.This is a precautionary step to avoid having active passwords remaining accessibleon the disk.

You can assign an individual password to each user in the MAXUSER table. Also,an ALLUSERS setting provides a way to reset all users' password with the samevalue. MAXADMIN is not affected by the ALLUSERS setting.

The DB2 administrator password for ctginst1 is one of the passwords that can bereset. The default password is passw0rd.

Deploying WebSphere Application ServerThe WebSphere Application Server virtual machine provides the WebSphereApplication Server component in the IBM SmartCloud Control Desk VMImageproduct.

Use the WebSphere Application Server OVF template to deploy IBM SmartCloudControl Desk VMImage, which is built on WebSphere Application Server version 6.

Install this virtual machine after you have installed the DB2 virtual machine.

Deploying the WebSphere Application Server virtual machine:

This procedure explains how to deploy the WebSphere Application Server virtualmachine.

Before you begin

Before you deploy the WebSphere Application Server virtual machine, you mustdeploy the DB2 virtual machine.

About this task

The following instructions explain how to deploy the WebSphere ApplicationServer virtual machine image.


Procedure

1. Log in to the VMware vSphere client and navigate to Home > Inventory >Hosts and Clusters.

2. Select File > Deploy OVF Template.3. On the Source panel in the deployment wizard, select one of the following

options:v Click Browse, select the QI_SCCD_WAS.ovf OVF template from the file

system, and click Next.v Type the absolute path and file name for the OVF template, and click Next.

4. On the OVF Template Details panel, review the OVF template details andclick Next.

5. On the End User License Agreement panel, accept the end user licenseagreements. There are 3 license agreements associated with the IBMSmartCloud Control Desk VMImage.

Option Description

To accept the license agreement for IBMSmartCloud Control Desk VMImage,


To accept the license agreement forVMware tools,


To accept the license agreement for theSUSE Linux operating system that runs asthe guest operating system in the virtualmachine,


6. Click Next.7. On the Name and Location panel, complete the following steps:

a. Specify a name for the virtual machine that you are creating.b. Select an Inventory location.c. Click Next.

8. On the Host/Cluster panel, select the stand-alone host or cluster on which todeploy the OVF template and click Next.

9. Optional: In the Resource Pool panel, select the resource pool where thedeployed OVF template will run and click Next. This step is displayed only ifthe virtual infrastructure is clustered and contains a resource pool.

10. Optional: In the Datastore panel, select a data store and click Next. If multipledata stores have been set up in the virtual infrastructure, choose the specificdata store that will hold the virtual storage for the virtual machine. The datastore for the WebSphere Application Server virtual machine requires 100 GBfree.

11. On the Disk Format panel, specify a disk format for the virtual disks that arecreated to store the virtual machine and click Next. The default selected isThick Provisioned Format.

12. Specify a network and click Next. If multiple networks exist in the virtualinfrastructure, choose the specific network to use for the virtual machine.

13. Enter the specific properties that are required for the virtual machine that youare deploying and click Next. See the worksheets created when planning yourdeployment for the required parameters.

14. In the Ready to Complete panel, review the summary of the parameters thatyou have configured and click Finish. For troubleshooting purposes, take a


screen capture of the data in the Ready to Complete panel to provide a recordof the properties and values that you specified.

Results

After the deployment is complete, a new entry for the WebSphere ApplicationServer virtual machine is displayed in the Hosts and Clusters view for the hostthat was selected.

What to do next

Turn on the virtual machine by right-clicking the new entry for the WebSphereApplication Server virtual machine and selecting Power > Power On.

Verifying deployment of the WebSphere Application Server machine:

This procedure explains how to verify deployment of the WebSphere ApplicationServer virtual machine.

About this task

The following steps explain how to verify the deployment.

Procedure

1. Log in to the Linux console as root using the password that you specified forthe virtual machine. Successful login confirms that the password functionscorrectly.

2. After a successful login, open a command prompt shell window.3. To verify that the host name that was specified during deployment is accurate,

complete the following steps:a. On the command line, type hostname and press Enter.b. Check that the host name is correct.

4. To verify that the IP address that was specified during deployment is accurate,complete the following steps:a. On the command line, type ifconfig and press Enter.b. Check that the IP address is correct.

5. On the command line type /etc/init.d/DeploymentManager_was.init statusand press Enter.

6. Check that you receive a response indicating that dmgr is running onWebSphere Application Server. If you do not see that response, complete thefollowing steps to start the process manually:a. Enter /etc/init.d/DeploymentManager_was.init start.b. Press Enter.

7. On the command line type /etc/init.d/NodeManager_was.init status andpress Enter.

8. Check that you receive a response indicating that nodeagent is running onWebSphere Application Server. If you do not see that response, complete thefollowing steps to start the process manually:a. Enter /etc/init.d/NodeManager_was.init start.b. Press Enter.

9. On the command line type /etc/init.d/MXServer_was.init status and pressEnter.


10. Check that you receive a response indicating that MXServer is running onWebSphere Application Server. If you do not see that response, complete thefollowing steps to start the process manually:a. Enter /etc/init.d/MXServer_was.init start.b. Press Enter.

Note: The MXServer server does not run unless the nodeagent is successfullystarted.

11. To verify that IBM SmartCloud Control Desk VMImage is running, completethe following steps:a. Navigate to the following location: https://hostname:9043/ibm/console/

logon.jsp.b. To log in, enter the user ID wasadmin and the password wasadmin

c. Check that you successfully logged in to the WebSphere IntegratedSolutions Console.

d. Navigate to the following location: http://hostname:9080/maximo.e. To log in, enter the user ID maxadmin and the password maxadmin

f. Verify that the IBM SmartCloud Control Desk VMImage application isdisplayed.

g. Navigate to the following location: http://hostname/maximo.h. To log in, enter the user ID maxadmin and the password maxadmin

i. Verify that the IBM SmartCloud Control Desk VMImage application isdisplayed.

j. If you can reach IBM SmartCloud Control Desk VMImage athttp://hostname:9080/maximo but not at http://hostname/maximo,complete the following steps:1) Log into the Linux console as root.2) On the command line, type: /etc/init.d/ibm-httpd start.3) Try to access the http://hostname/maximo URL again.

What to do next

After you verify the deployment of the WebSphere Application Server virtualmachine, you can optionally synchronize the time clock on the machine.

Synchronizing the time clock:

After the IBM SmartCloud Control Desk VMImage virtual machine is deployed,you can optionally synchronize the time clock on the virtual machine to ensureaccuracy.

About this task

To synchronize the time clock for the virtual machine, complete the followingsteps.

Procedure

1. Log in to the Linux OS console as root.2. Open the following file in an editor:

/etc/ntp.conf.


3. The ntp.conf file contains one or more properties named server. Select one ofthe following options:v Locate the server property that specifies timeserver.com and change the

timeserver.com property to an external time server such as time.nist.gov.v If there is no server property that specifies timeserver.com, add a new line

that has the following property:server hostname of external time server.

4. Save the file.5. In a command shell, execute the netconfig update -m ntp command. This

command updates daemon.6. To verify the synchronization, open the /var/log/ntp file, scroll to the bottom

of the file, and check that the time synchronization was successful. A successfulresult is similar to the following example.19 May 08:21:55 ntpd[7302]: synchronized to 192.43.244.18, stratum 119 May 08:21:55 ntpd[7302]: kernel time sync status change 2001

Resetting passwords on the WebSphere Application Server virtual machineusing setPasswords.sh:

This procedure details how to reset passwords on the WebSphere ApplicationServer virtual machine using setPasswords.sh

About this task

You can use the setPasswords.sh shell script to reset all users' passwords in theDB2 Tivoli's process automation engine (TPAE) database, and some otheradministration passwords in the WebSphere Application Server, DB2 and Maximo.The script is located in the /opt/IBM/SMP/maximo/nvsfiles/deployscripts/adminScripts directory.

To use this script you must create an ini file to contain the new passwords. The inifile must reside in the same location as the script. This ensures that the ini file isdetected by the script when the script is executed. A sample ini file is provided in/opt/IBM/SMP/maximo/nvsfiles/deployscripts/adminScripts/admin-config.ini.sample. Copy this sample ini file and edit it to contain the desiredpasswords. Once the ini file is successfully processed it is automatically deleted.This is a precautionary step to avoid having active passwords remaining accessibleon the disk.

You can assign an individual password to each user in the MAXUSER table. Also,an ALLUSERS setting provides a way to reset all users' password with the samevalue. MAXADMIN is not affected by the ALLUSERS setting.

The WebSphere Application Server administrator password for wasadmin is one ofthe passwords that can be reset. The default password is passw0rd. Even thoughthe password for wasadmin can be modified at the same time as the passwords ofother users, it is highly recommended to do so separately.

Configuring initial dataBefore using the product, you must configure several options.

Configure the following items:


1. Optional: Create any currency codes that you need . The product provides adefault set of currency codes. You can create your own currency codes if youneed additional ones.

2. Configure at least one organization and site. Before you use the service, youmust create at least one organization and site. Organizations and sites arelogical divisions of a company determined by what types of operations areperformed at different locations, and what data can be shared among them. Anorganization is a major division of a company that contains one or more sites.

3. Create work types. A work type specifies the level of work that is involvedwith a change request. You must create one or more work types for eachorganization that you create.

4. Optional: Configure Service Catalog content. Use this task to specify theorganization, site, set, and vendor that you want to associate with ServiceCatalog content. Service Catalog content is an optional package that includesbase content such as security groups, users, and persons, and service-specificcontent such as catalogs, fulfillment options, and job plans.

5. Recommended: Configure SMTP. You can configure an SMTP server to send anadministrator, or other users, e-mail notifications of system events.

For more information about these tasks, see the product information center.

Additional information to help with configuration

If you are new to the product and to Tivoli's process automation engine, you mightfind it helpful to review the following documents. Some of the documents mentionother product names. However, the content of the document is applicable toSmartCloud Control Desk.

Job Aid - Effective Use of Classifications in Tivoli Service Request ManagerClassifications are extremely important for the effective use of the productand need careful consideration as part of any deployment. This documentprovides key considerations for creating classifications that save labor andmaximize value.

Job Aid - Tivoli Service Request Manager Priority Matrix - Use or UpdateYou use the priority matrix application to support internal priorities forService requests, Incidents and Problem records. This document explainshow to use the priority matrix and customize it to suit specific businessneeds.

Job aid - Configuring Service Catalog without optional contentThis document provides instructions for configuring the product afterService Catalog has been installed without optional content.

Configuring securityAfter you configure the initial data, create any additional users you need, and addthem to the appropriate security groups.

You can create new users with the Users application or by importing user data in aCSV file. You may want to add the user to additional security groups dependingon the user's role. Being a member of a security group gives the user theappropriate level of access to various applications, which enables the user toperform the duties of the role. To learn more about these tasks, read the securityinformation in the product information center. This information describes thedefault users that exist on the system, the security group associated with each user,


http://www.ibm.com/developerworks/wikis/display/tivolisrm/Job+Aid+-+Effective+Use+of+Classifications+in+Tivoli+Service+Request+Manager

http://www.ibm.com/developerworks/wikis/display/tivolisrm/Job+Aid+-+Tivoli+Service+Request+Manager+Priority+Matrix+-+Use+or+Update

http://www.ibm.com/developerworks/wikis/display/tivolisrm/Job+aid+-+Configuring+Service+Catalog+without+optional+content

and the purpose of the users belonging to each security group. You can log in asthe default users to work as the role of the user before assigning real users to theappropriate roles.

Importing dataBefore you import data for the first time, review the basic concepts aboutimporting data.

You can enter assets, configuration items (CIs), person users, licenses, and locationsinto the product by importing data in a CSV file into the Quick Configurationapplication. By default the assets, CIs and person users data is imported orupdated using the sequential queue. They are imported one at a time in order, andwill stop when an error is found. This is done because there may be dependencieson the order that the data is imported. The locations and licenses data is importedusing the continuous queue. More information on the use of sequential andcontinuous queues can be found in the Integration Guide.

The overall data import process is as follows:1. Review the documentation about the structure of CSV files.2. Review the best practices for data import.3. Configure at least one organization and site.4. Create at least one work type for each organization you created.5. Create a CSV file that contains the data to be entered. You can create your own

CSV file or edit one of the sample files that are included with the product.6. Preview the import using the Quick Configuration application and review and

correct any errors that occur.7. Import the data using the Quick Configuration application.

For more information about these tasks, see the product information center.

You can enter assets, configuration items (CIs), person users, licenses, and locationsinto the product by importing data in a CSV file into the Quick Configurationapplication. By default the assets, CIs and person users data is imported orupdated using the sequential queue. They are imported one at a time in order, andwill stop when an error is found. This is done because there may be dependencieson the order that the data is imported. The locations and licenses data is importedusing the continuous queue. For more information on the use of sequential andcontinuous queues, go to the Modules and applications section of the informationcenter and consult the topics in the Integration module.

The overall data import process is as follows:1. Review the documentation about the structure of CSV files.2. Review the best practices for data import.3. Configure at least one organization and site.4. Create at least one work type for each organization you created.5. Create a CSV file that contains the data to be entered. You can create your own

CSV file or edit one of the sample files that are included with the product.6. Preview the import using the Quick Configuration application and review and

correct any errors that occur.7. Import the data using the Quick Configuration application.

Each of these steps is discussed more fully in the topics that follow.



Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user's responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not grant youany license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBMIntellectual Property Department in your country or send inquiries, in writing, to:

IBM World Trade Asia CorporationLicensing 2-31 Roppongi 3-chome, Minato-kuTokyo 106-0032, Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law:INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express orimplied warranties in certain transactions, therefore, this statement may not applyto you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM Web sites are provided forconvenience only and do not in any manner serve as an endorsement of those Websites. The materials at those Web sites are not part of the materials for this IBMproduct and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.


Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

IBM CorporationSoftware Interoperability Coordinator, Department 49XA3605 Highway 52 NRochester, MN 55901U.S.A.

Such information may be available, subject to appropriate terms and conditions,including in some cases, payment of a fee.

The licensed program described in this information and all licensed materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement, or any equivalent agreementbetween us.

Any performance data contained herein was determined in a controlledenvironment. Therefore, the results obtained in other operating environments mayvary significantly. Some measurements may have been made on development-levelsystems and there is no guarantee that these measurements will be the same ongenerally available systems. Furthermore, some measurements may have beenestimated through extrapolation. Actual results may vary. Users of this documentshould verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

All statements regarding IBM's future direction or intent are subject to change orwithdrawal without notice, and represent goals and objectives only.

All IBM prices shown are IBM's suggested retail prices, are current and are subjectto change without notice. Dealer prices may vary.

This information is for planning purposes only. The information herein is subject tochange before the products described become available.

This information contains examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples include thenames of individuals, companies, brands, and products. All of these names arefictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, whichillustrate programming techniques on various operating platforms. You may copy,modify, and distribute these sample programs in any form without payment toIBM, for the purposes of developing, using, marketing or distributing applicationprograms conforming to the application programming interface for the operating


platform for which the sample programs are written. These examples have notbeen thoroughly tested under all conditions. IBM, therefore, cannot guarantee orimply reliability, serviceability, or function of these programs.

Each copy or any portion of these sample programs or any derivative work, mustinclude a copyright notice as follows:

© IBM Corp. 2012. Portions of this code are derived from IBM Corp. SamplePrograms. © Copyright IBM Corp. 2012. All rights reserved.

If you are viewing this information softcopy, the photographs and colorillustrations may not appear.

TrademarksFor trademark attribution, visit the IBM Terms of Use Web site(http://www.ibm.com/legal/us/)

The following terms are trademarks of International Business MachinesCorporation in the United States, other countries, or both:

IBM, the IBM logo, AIX, Tivoli, the Tivoli logo, and WebSphere are trademarks orregistered trademarks of International Business Machines Corporation in theUnited States, other countries, or both.

Intel, the Intel logo, and Pentium are trademarks of Intel Corporation in the UnitedStates, other countries, or both.

Microsoft, Windows, the Windows logo, and Internet Explorer are trademarks ofMicrosoft Corporation in the United States, other countries, or both.

Linux is a trademark of Linus Torvalds in the United States, other countries, orboth.

UNIX is a registered trademark of The Open Group in the United States and othercountries.

Java and all Java-based trademarks and logos are trademarks or registeredtrademarks of Sun Microsystems, Inc. in the United States and other countries.

Other company, product, and service names may be trademarks or service marksof others.

Notices 29


Index

Cclock 18, 22

Eeditions 6

Hhardware requirements 2

Iimporting data 25

Ppasswords 19, 23

Rrequirements

hardware 2software 3

Ssecurity 24software requirements 3

Vverifying 7virtual machine images 4

deploying 15

Wworksheets 9



��

Printed in USA

Documents

IBM SmartCloud Control Desk Version 7 Release 5 › support › knowledgecenter › SSWT9A... · Virtualization executive (hypervisor) VMware vSphere 4.1 ... v VMware vCenter Server