IBM SmartCloud Control Desk Version 7 Release 5. Installation Guide. (VM Image)

Transkript

1 IBM SmartCloud Control Desk Version 7 Release 5 Installation Guide (VM Image)

2 Note Before using this information and the product it supports, read the information in Notices on page 27.

3 Contents Installing the IBM SmartCloud Control Desk VMImage Planning for deployment Roles and responsibilities Hardware requirements Software requirements Virtual machine images Deployment process Deployment dependencies Deployment sequence Changing the product edition Post-deployment verification Planning for language support Deployment worksheets Deployment worksheet for the DB2 virtual machine Deployment worksheet for the WebSphere Application Server virtual machine Deploying the solution Prerequisites for deployment Connecting to the VMware vcenter server Deploying the virtual machine images Preparing the virtual images Deploying DB Deploying WebSphere Application Server.. 19 Configuring initial data Configuring security Importing data Notices Trademarks Index Copyright IBM Corp iii

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

5 Installing the IBM SmartCloud Control Desk VMImage Planning for deployment The following topics describe what you must do to install the IBM SmartCloud Control Desk VMImage solution. The functional components of the IBM SmartCloud Control Desk VMImage solution are delivered as virtual machine (VM) images. These images can be deployed on hardware provided by the customer. Because IBM SmartCloud Control Desk VMImage is delivered as virtual machine images, some aspects of the underlying operating system and product stack can be configured before deployment. Deployment of the VMs is completed with an intuitive user interface that requests some additional configuration parameters that cannot be determined before deployment. After VMs are deployed and activation is completed, manual configuration of customer-specific processing logic across multiple applications (for example, event correlation) is performed using the user interfaces of the component products. Before you attempt to deploy and configure IBM SmartCloud Control Desk VMImage, obtain the required hardware and software and then use the appropriate deployment checklist for each virtual machine to guide you through the installation process. Planning for deployment is critical to the success of an IBM SmartCloud Control Desk VMImage implementation. Successful planning includes analyzing how you are going to use the solution, obtaining the required hardware and software for deployment, and preparing the deployment infrastructure. Use this information to understand and effectively deploy IBM SmartCloud Control Desk VMImage in your environment to suit your business needs. Once you are comfortable with deployment concepts and planning material, you can use deployment worksheets included with the documentation to record values you use during the deployment process. Roles and responsibilities An IBM SmartCloud Control Desk VMImage solution implementation requires coordination 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 the deployment of your IBM SmartCloud Control Desk VMImage solution. System administrators and their counterparts are responsible for deploying and maintaining the IBM SmartCloud Control Desk VMImage implementation. Administrators are expected to have technical skill in the following areas: Copyright IBM Corp

6 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 requirements Review the hardware requirements and ensure that your environment meets the minimum standards before you attempt to install IBM SmartCloud Control Desk VMImage. The hardware requirement for your installation depends on how you plan to implement the solution. Servers are required to house the VMware products that deploy the solution and to host the virtual machine images. When planning your implementation, ensure that you have adequate server capacity to host the virtual machine images and to deploy the solution. Requirement for virtual machine images The following specification describes the minimum hardware required to host the virtual 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 large number of events, or serves a large number of users, more hardware might be required. The following table shows the minimum hardware capacity required for each virtual image. Table 1. Resources required for each virtual machine Virtual image Number of physical cores Disk space (GB) Memory (GB) DB WebSphere Application Server Requirement for deployment server VMware vsphere 4.1 must be installed and configured before the virtual machines can be deployed. For a list of hardware configurations supported by VMware technology, see the compatibility guide available at the VMware Technical Resource Center. Note that VMware ESXi supports only x86 architectures; therefore it requires AMD or Intel processors. VMware vcenter Server can be installed on physical hardware running a Windows operating system that is supported by VMware vsphere. It can also be installed on 2 IBM SmartCloud Control Desk: Installation Guide (VM Image)

7 a virtual machine that runs a VMware vsphere-supported Windows operating system as a guest. The virtual machine can run on one of the provisioned VMware ESXi hypervisors. For information about the system requirements for VMware vcenter Server, see the ESXi Installable and vcenter Server Setup Guide at the following link: Software requirements Review the software requirements and ensure that your environment meets the minimum standards before you attempt to install IBM SmartCloud Control Desk VMImage. Table 1 summarizes the software requirements for IBM SmartCloud Control Desk VMImage. Table 2. Software requirements Software required Operating system Software version SUSE Linux Enterprise Server 11 (64-bit). This operating system is provided with the virtual machines in the IBM SmartCloud Control Desk VMImage solution. Microsoft Windows. VMware vsphere requires a Windows operating system. See the link that follows to determine which Windows operating system to use. Virtualization executive (hypervisor) VMware vsphere 4.1 Internet browser Mozilla Firefox 3.5 Microsoft Internet Explorer 7 or 8 For more information about database, middleware, and web browser support for the component products delivered with the IBM SmartCloud Control Desk VMImage solution, see the information centers for the individual components. Operating systems Each virtual machine in the solution requires the 64-bit SUSE Linux Enterprise Server (SLES) 11 operating system. The operating system is delivered as part of the virtual machine images. All products comprising the IBM SmartCloud Control Desk VMImage solution support SUSE Linux Enterprise Server 11. Servers that are used to deploy the solution must use the Windows operating system required by VMware vsphere 4.1. Virtualization executive (hypervisor) Because IBM SmartCloud Control Desk VMImage is delivered as virtual machine images, VMware vsphere 4.1 is required to implement the solution. VMware vsphere 4.1 and associated tools must be installed and configured before you deploy the virtual machine images. This tooling should include the following components: v VMware vsphere 4.1. VMware vsphere includes the VMware ESXi 4.1 hypervisor that is required for deployment. Installing the VMImage solution 3

8 v VMware vcenter Server VMware vcenter Server is a required, separately licensed component of a VMware vsphere implementation. VMware vcenter Server can be installed on physical hardware running a Windows operating system that is supported by VMware vsphere. It can also be installed on a virtual machine that runs a VMware vsphere-supported Windows operating system as a guest. The virtual machine can run on one of the provisioned VMware ESXi hypervisors. v VMware vsphere client. Install the client on a Windows-based administrative workstation that is supported by VMware. The client is used to connect directly to a VMware ESXi host or to the central VMware vcenter Server installation and manage the virtual infrastructure. For information about the system requirements for VMware vcenter Server, see the ESXI Installable and vcenter Server Setup Guide. Note: You should be familiar with the installation and configuration of virtual machines when using the VMware ESXi hypervisor software. Virtual machine images IBM SmartCloud Control Desk VMImage includes two virtual machine images that must 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 v OVF descriptor file. OVF descriptor files are used to deploy the virtual machine into the hypervisor. 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 license terms and conditions. Each OVF template is deployed into the VMware virtual infrastructure using the VMware vcenter Server. A particular physical VMware vcenter Server host can be chosen to be the target of the deployment. All deployment activities are carried out by 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 Virtualization Format (OVF) page on the DMTF web site: Table 1 describes the virtual machine images. Table 3. Virtual machine images Virtual machine DB2 virtual machine WebSphere Application Server virtual machine Product/component IBM DB2 9.7 database for IBM SmartCloud Control Desk VMImage IBM SmartCloud Control Desk VMImage IBM SmartCloud Control Desk: Installation Guide (VM Image)

9 Deployment process IBM SmartCloud Control Desk VMImage provides installation instructions and various checklists that can be used to guide you through the deployment process. It is important to understand the entire deployment process before attempting to implement the solution. The wizard that is provided with IBM SmartCloud Control Desk VMImage guides you through deployment of the solution's virtual machines (VMs). The wizard is launched from the VMware vsphere client. The steps required to deploy each virtual machine image for the IBM SmartCloud Control Desk VMImage solution are similar. Some steps are identical for each virtual machine. Other steps require parameters that are specific to the virtual machine. In addition, some VMs require post-deployment configuration. Because some products in the solution have dependencies on other products or components, the virtual machine images must be deployed and configured in a specific sequence. Review the following steps, which describe the general process for deploying the virtual 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 to deploy 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 the information center. The following deployment aids are available to assist in the deployment process. v v Deployment worksheets that you can use to gather the individual parameters that are needed for the specific VMs. Detailed instructions for installing each VM. Deployment dependencies The component products in the IBM SmartCloud Control Desk VMImage solution work together to provide smart building data. Some components have dependencies on other products in the solution. The dependencies between components affects deployment and maintenance of the virtual machines included in the solution. Deployment must be performed in a specific sequence. You must first deploy the DB2 virtual machine and then deploy the Websphere Application virtual machine. The WebSphere Application virtual machine is dependent on the DB2 virtual machine. Upgrades to the product should also take into account the component dependencies. Installing the VMImage solution 5

10 Because the products and components are interdependent, all virtual machines must have the same time zone setting. The WebSphere Application Server virtual machine is dependent on the DB2 virtual machine. The WebSphere Application Server virtual machine accesses the Maximo database to post or retrieve IBM SmartCloud Control Desk VMImage data. Deployment sequence Because of dependencies that exist between some of the products included in the IBM SmartCloud Control Desk VMImage solution, the virtual machine images for the products must be deployed and configured in a specific sequence. The following deployment sequence is required for IBM SmartCloud Control Desk VMImage: 1. DB2 virtual machine for the Maximo database on IBM DB2 2. WebSphere Application Server virtual machine for IBM SmartCloud Control Desk VMImage 7.5 Changing the product edition The 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 VM image after you have installed it. About this task In addition to the VM images, you received a set of product DVDs, or the entitlement to download product images. These DVDs or images contain the installable copy of the product edition that you purchased. If you purchased IBM SmartCloud Control Desk or IBM SmartCloud Control Desk - Service Provider Edition, you can use the installable copy of the product to modify the VM image after you have deployed it. You can use the same procedure if you have purchased and installed the Entry edition and later purchase a different edition. Procedure 1. 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 initial data configuration. 2. Mount the product DVD or installable image for the edition that you purchased on the VM where you deployed the WebSphere Application Server/administrative workstation image. 3. Invoke the product installer. It recognizes that the Entry edition is installed and modifies the current deployment to the edition that it contains. 4. You can use the default configuration or change it to suit your needs. If you plan to install the Advanced Content package after your edition change, defer the EAR deployment and the updatedb actions at this time, and let the Advanced Content package installation execute those actions. 5. After the successful installation of the new edition, stop MXServer on WebSphere, 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 IBM SmartCloud Control Desk: Installation Guide (VM Image)

11 6. Perform the post-deployment verification steps. Results Your new edition is ready for use. If you have not yet performed initial data configuration, do it now. Related concepts: Deploying the solution on page 13 Use this information to deploy and configure the IBM SmartCloud Control Desk VMImage solution. Post-deployment verification After deployment, it is important to verify that the virtual machine images are deployed as expected. Configuring initial data on page 23 Before using the product, you must configure several options. Post-deployment verification After deployment, it is important to verify that the virtual machine images are deployed as expected. After the virtual machines are deployed, perform the following checks to determine whether deployment was completed successfully: v v Check that the OVF activation engine successfully executed the virtual machine activation scripts. To perform this check, review the activation logs available in a designated folder in the virtual machine. Check that the services that are set to start automatically start as expected. To perform this check, execute the appropriate commands in the Linux console. v Check that the associated web application for a product or component is available. To perform this check, launch a web browser, access the web application, and log into the web application using the appropriate user ID and password. Detailed post-deployment verification steps for each virtual machine are provided in the deployment documentation. Activation engine, scripts, and logs The activation engine is the runtime enablement framework that IBM uses for customization of virtual images when the machines are initially turned on. In the IBM SmartCloud Control Desk VMImage solution, the activation engine is embedded in each of the virtual images and executes once during the deployment of the OVF templates. For each virtual image, the activation engine executes a set of activation scripts that configure the virtual machine and the IBM SmartCloud Control Desk VMImage solution products or components within the virtual machine. For the IBM SmartCloud Control Desk VMImage solution, the activation engine creates log files in the /opt/ibm/ae/log folder in the Linux file system of the virtual machine. If the activation engine encounters any execution errors, an error.log file is written to this folder. An additional trace.log file is written without regard to failure or success of the deployment. If an error.log file is created, review the contents of the log file to identify any activation errors. Installing the VMImage solution 7

12 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 no errors were encountered during the execution of the particular script. Startup services The IBM SmartCloud Control Desk VMImage solution activation scripts configure each virtual machine to start key server processes automatically. Once each virtual machine is turned on, a Linux console can be launched and the Linux ps command can be run to verify whether the server processes are executing. For some products, product-specific commands are executed to verify process status. Web applications The IBM SmartCloud Control Desk VMImage solution delivers a number of web applications that execute in the WebSphere Application Server. Once the virtual machine is turned on and server processes started, a workstation can be used to verify whether the web applications are available. Entering the application URL in a web browser should open the application's home page. Planning for language support IBM SmartCloud Control Desk VMImage supports multiple languages. The virtual machine images are configured for English. Post-deployment configuration to add translated content is required for implementations that require a different language. 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) 8 IBM SmartCloud Control Desk: Installation Guide (VM Image)

13 v v v Spanish (es) Swedish (sv) Turkish (tk) Translation availability when deploying the virtual machines When you deploy the virtual machine images, the language that you see in the deployment wizard is determined by the locale configured for the Windows operating system of the VMware vsphere client. For example, if the operating system 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 is available only in English. The license agreement for SUSE Linux is not available in Hebrew. The license agreement for IBM SmartCloud Control Desk VMImage is not available in Hebrew or Arabic. Post-deployment tasks for language updates If you use a language other than English, immediately after you deploy the virtual machines you must change the base language for the product. If your language preference is not English, you must change the base language settings before you load data to the Maximo database or perform any configuration. When you change the 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 in English only. A news announcement will be posted on the product support site when the translated copy is available for download. When it is available, you can download the translated information and deploy it in your environment. Deployment worksheets Use the virtual machine deployment worksheets to record information that you must supply when you deploy the IBM SmartCloud Control Desk VMImage virtual images. The worksheets can be used to provide the values that are requested by the IBM SmartCloud Control Desk VMImage deployment wizard. Deployment worksheet for the DB2 virtual machine Use this worksheet to record information that is needed to deploy the DB2 virtual machine. Table 4. Deployment worksheet for the DB2 virtual machine Item Description Value Inventory location Resource pool Location of the virtual machine in the VMware vsphere infrastructure. Used to allocate host-provided CPU and memory to the virtual machines resident to the host or cluster. Installing the VMImage solution 9

14 Table 4. Deployment worksheet for the DB2 virtual machine (continued) Item Description Value Data store Logical containers that store virtual machine files and other files necessary for virtual machine operations. This is a virtualized representation of the underlying physical storage. Network Virtualized network configuration that is used by the virtual machine to communicate with other virtual machines or the physical network outside of the virtual infrastructure. The network specified in the OVF template must be mapped to an available network configuration. This includes vnetwork Standard Switches (vswitches) and vnetwork Distributed Switches. vnetwork Standard Switches are associated with a single host and are discovered when hosts are added to the vsphere environment. vnetwork Distributed Switches span multiple hosts. Locale Locale setting for the guest operating system that runs on the virtual machine. The locale setting drives locale-sensitive behaviors of applications and processes. The locale parameter is broken out into three fields: Language: Territory: Encoding: v Language (defaults to en) v Territory (defaults to US) v Encoding (defaults to UTF-8) Network configuration Various network-related aspects of the virtual machine must be configured. v Boot protocol Specify whether the internal network device is initialized with a static or DHCP protocol. Defaults to static'. v Host name Host name of the virtual machine. Do not use the fully qualified name. For example, use myhost rather than myhost.example.com. v Domain The fully qualified domain name (FQDN) for the virtual machine. For example, for the virtual machine myhost.example.com the FQDN is example.com. v IP address (static or DHCP) If using the static boot protocol, specify the IP address of the virtual machine. Specify a host address within a network or specify that IPv4 or IPv6 DHCP server is available on the network. v Netmask If using the static boot protocol, specify which portion of the IP address specifies the subnetwork number and which portion specifies the host. In most networks, the value is IBM SmartCloud Control Desk: Installation Guide (VM Image)

15 Table 4. Deployment worksheet for the DB2 virtual machine (continued) Item Description Value v Gateway Configure gateways for the service console and the VMkernel to allow network connectivity to machines not on the same IP subnet. If using the static boot protocol, specify the IP address of the machine that serves as the gateway to the network. v Primary DNS If using the static boot protocol, specify the primary Domain Name System IP address. v Secondary DNS If using the static boot protocol, specify the secondary Domain Name System IP address. v Root password The password for the root (administrator) account of operating system on the virtual machine. v Virtual user password The password for the virtuser account. This account is the default non-administrator account for the operating system on the virtual machine. Deployment worksheet for the WebSphere Application Server virtual machine Use this worksheet to record information that is needed to deploy the WebSphere Application Server virtual machine. Table 5. Deployment worksheet for the WebSphere Application Server virtual machine Item Description Value Inventory location Location of the virtual machine in the VMware vsphere infrastructure. Resource pool Used to allocate host-provided CPU and memory to the virtual machines resident to the host or cluster. Data store Logical containers that store virtual machine files and other files necessary for virtual machine operations. This is a virtualized representation of the underlying physical storage. Installing the VMImage solution 11

16 Table 5. Deployment worksheet for the WebSphere Application Server virtual machine (continued) Item Description Value Network Virtualized network configuration that is used by the virtual machine to communicate with other virtual machines or the physical network outside of the virtual infrastructure. The network specified in the OVF template must be mapped to an available network configuration. This includes vnetwork Standard Switches (vswitches) and vnetwork Distributed Switches. vnetwork Standard Switches are associated with a single host and are discovered when hosts are added to the vsphere environment. vnetwork Distributed Switches span multiple hosts. Locale Locale setting for the guest operating system that runs on the virtual machine. The locale setting drives locale-sensitive behaviors of applications and processes. The locale parameter is broken out into three fields: Language: Territory: Encoding: v Language (defaults to en) v Territory (defaults to US) v Encoding (defaults to UTF-8) Network configuration Various network-related aspects of the virtual machine must be configured. v Boot protocol Specify whether the internal network device is initialized with a static or DHCP protocol. Defaults to static'. v Host name Host name of the virtual machine. Do not use the fully qualified name. For example, use myhost rather than myhost.example.com. v Domain The fully qualified domain name (FQDN) for the virtual machine. For example, for the virtual machine myhost.example.com the FQDN is example.com. v IP address (static or DHCP) If using the static boot protocol, specify the IP address of the virtual machine. Specify a host address within a network or specify that IPv4 or IPv6 DHCP server is available on the network. v Netmask If using the static boot protocol, specify which portion of the IP address specifies the subnetwork number and which portion specifies the host. In most networks, the value is IBM SmartCloud Control Desk: Installation Guide (VM Image)

17 Table 5. Deployment worksheet for the WebSphere Application Server virtual machine (continued) Item Description Value v Gateway Configure gateways for the service console and the VMkernel to allow network connectivity to machines not on the same IP subnet. If using the static boot protocol, specify the IP address of the machine that serves as the gateway to the network. v Primary DNS If using the static boot protocol, specify the primary Domain Name System IP address. v Secondary DNS If using the static boot protocol, specify the secondary Domain Name System IP address. v Root password The password for the root (administrator) account of operating system on the virtual machine. v v v Virtual user password IP address for the Maximo database host Hostname for the Maximo database host The password for the virtuser account. This account is the default non-administrator account for the operating system on the virtual machine. The IP address for the host running the Maximo database. The fully qualified hostname for the host running the Maximo database. Deploying the solution Note: The virtual machine that hosts the Maximo database must be running and the server processes must also be running when you configure the WebSphere Application Server OVF template. If this is not the case, IBM SmartCloud Control Desk VMImage will not start successfully. Use this information to deploy and configure the IBM SmartCloud Control Desk VMImage 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 for each individual virtual machine in the solution. Installing the VMImage solution 13

18 Prerequisites for deployment Before 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 the solution and to host the virtual machine images. After you install the required deployment infrastructure, additional steps are required to prepare the host machines 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 the software. To configure your infrastructure for deployment, ensure that you purchase 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 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 free disk space is required on the VMware vsphere client to process the virtual machine template files. Ensure that there is sufficient disk space on the client system. 3. Install the VMware ESXi 4.1 hypervisor on the machines that will host the virtual images. 4. Add the VMware ESXi-installed host machines to the VMware vcenter Server inventory. 5. Create administrative user IDs and passwords as required for your implementation. 6. Collect the properties and network configuration information that will be requested as you deploy the virtual machines. The deployment documentation includes worksheets for the specific virtual machines. You can use the worksheets to record information that will be requested by the deployment wizard. Note: If you plan to use static IP addresses for the virtual machines, it is recommended 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 server This topic describes how to connect to the VMware vcenter server to select your datastore and target host. About this task To connect to the VMware vcenter server: Procedure 1. Start the VMware vsphere client. 14 IBM SmartCloud Control Desk: Installation Guide (VM Image)

19 2. Enter your IP address or host name. To manage multiple hosts, enter the IP address or name of the vcenter server. 3. Enter your username and password, and click the Login button. Deploying the virtual machine images The following topics explain how to deploy the virtual machine images for the products and components provided in the IBM SmartCloud Control Desk VMImage solution. IBM SmartCloud Control Desk VMImage virtual machines are packaged as Open Virtualization Format (OVF) templates. Each OVF template is deployed into the VMware vsphere virtual infrastructure using the VMware vcenter Server. A specific physical VMware ESXi host can be the target of the deployment. All deployment activities are carried out by logging into the VMware vcenter Server environment using the VMware vsphere client. Before you attempt to deploy the virtual machines, check that you have completed all the deployment prerequisites and have prepared the virtual machine images for deployment. Preparing the virtual images This topic describes how to prepare the IBM SmartCloud Control Desk VMImage images for use in the VMware environment. Complete this procedure before you deploy the virtual machines. Before you begin The following procedure requires that you install the VMware vsphere client on a Windows computer that can connect to VMware vcenter Server. You can use any Windows operating system that is supported by VMware vsphere client. The computer 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 IBM SmartCloud Control Desk VMImage virtual images obtained from the physical media as follows. Procedure 1. 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 the file names in numeric order, so that they will be concatenated in the proper order. v Other platforms: cat SCCD*.part >> SCCD_QI_V75.zip 4. Confirm that the zip file is assembled correctly by verifying its checksum values: a. Run the following command to generate the checksum values for the zip file: md5sum -b SCCD_QI_V75.zip Installing the VMImage solution 15

20 b. Compare your generated checksum values with the values in the provided MD5SUMS text file. Deploying DB2 The DB2 virtual machine provides the database repository for the IBM SmartCloud Control Desk VMImage product. The DB2 OVF template encapsulates a virtual machine that contains IBM DB2 version 9.5, which serves as the IBM SmartCloud Control Desk VMImage repository. 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 and click Next. 5. On the End User License Agreement panel, accept the end user license agreements. There are 3 license agreements associated with the IBM SmartCloud Control Desk VMImage. Option To accept the license agreement for IBM SmartCloud Control Desk VMImage, To accept the license agreement for VMware tools, To accept the license agreement for the SUSE Linux operating system that runs as the guest operating system in the virtual machine, Description Review the license agreement and click Accept. Review the license agreement and click Accept. Review the license agreement and click Accept. 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 to deploy the OVF template and click Next. 16 IBM SmartCloud Control Desk: Installation Guide (VM Image)

21 9. Optional: In the Resource Pool panel, select the resource pool where the deployed OVF template will run and click Next. This step is displayed only if the virtual infrastructure is clustered and contains a resource pool. 10. Optional: In the Datastore panel, select a data store and click Next. If multiple data stores have been set up in the virtual infrastructure, choose the specific data store that will hold the virtual storage for the virtual machine. The data store for the DB2 virtual machine requires 100 GB free. 11. On the Disk Format panel, specify a disk format for the virtual disks that are created to store the virtual machine and click Next. The default selected is Thick Provisioned Format. 12. Specify a network and click Next. If multiple networks exist in the virtual infrastructure, choose the specific network to use for the virtual machine. 13. Enter the specific properties that are required for the virtual machine that you are deploying and click Next. See the worksheets created when planning your deployment for the required parameters. 14. In the Ready to Complete panel, review the summary of the parameters that you have configured and click Finish. For troubleshooting purposes, take a screen capture of the data in the Ready to Complete panel to provide a record of the properties and values that you specified. Results After the deployment is complete, a new entry for the DB2 virtual machine is displayed 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 virtual machine 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 for the virtual machine. Successful login confirms that the password functions correctly. 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. Installing the VMImage solution 17

22 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 value greater than zero. What to do next After you verify the deployment of the DB2 virtual machine, you can optionally synchronize the time clock on the machine and then deploy the WebSphere Application 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 ensure accuracy. About this task To synchronize the time clock for the virtual machine, complete the following steps. 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 successful result is similar to the following example. 18 IBM SmartCloud Control Desk: Installation Guide (VM Image)

23 19 May 08:21:55 ntpd[7302]: synchronized to , stratum 1 19 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 using setpasswords.sh About this task You can use the setpasswords.sh shell script to reset all users' passwords in the DB2 Tivoli 's process automation engine (TPAE) database, and some other administration passwords in DB2, WebSphere Application Server 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 ini file must reside in the same location as the script. This ensures that the ini file is detected by the script when the script is executed. A sample ini file is provided in /opt/ibm/smp/maximo/nvsfiles/deployscripts/adminscripts/adminconfig.ini.sample. Copy this sample ini file and edit it to contain the desired passwords. Once the ini file is successfully processed it is automatically deleted. This is a precautionary step to avoid having active passwords remaining accessible on 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 same value. MAXADMIN is not affected by the ALLUSERS setting. The DB2 administrator password for ctginst1 is one of the passwords that can be reset. The default password is passw0rd. Deploying WebSphere Application Server The WebSphere Application Server virtual machine provides the WebSphere Application Server component in the IBM SmartCloud Control Desk VMImage product. Use the WebSphere Application Server OVF template to deploy IBM SmartCloud Control 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 virtual machine. Before you begin Before you deploy the WebSphere Application Server virtual machine, you must deploy the DB2 virtual machine. About this task The following instructions explain how to deploy the WebSphere Application Server virtual machine image. Installing the VMImage solution 19

24 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 and click Next. 5. On the End User License Agreement panel, accept the end user license agreements. There are 3 license agreements associated with the IBM SmartCloud Control Desk VMImage. Option To accept the license agreement for IBM SmartCloud Control Desk VMImage, To accept the license agreement for VMware tools, To accept the license agreement for the SUSE Linux operating system that runs as the guest operating system in the virtual machine, Description Review the license agreement and click Accept. Review the license agreement and click Accept. Review the license agreement and click Accept. 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 to deploy the OVF template and click Next. 9. Optional: In the Resource Pool panel, select the resource pool where the deployed OVF template will run and click Next. This step is displayed only if the virtual infrastructure is clustered and contains a resource pool. 10. Optional: In the Datastore panel, select a data store and click Next. If multiple data stores have been set up in the virtual infrastructure, choose the specific data store that will hold the virtual storage for the virtual machine. The data store for the WebSphere Application Server virtual machine requires 100 GB free. 11. On the Disk Format panel, specify a disk format for the virtual disks that are created to store the virtual machine and click Next. The default selected is Thick Provisioned Format. 12. Specify a network and click Next. If multiple networks exist in the virtual infrastructure, choose the specific network to use for the virtual machine. 13. Enter the specific properties that are required for the virtual machine that you are deploying and click Next. See the worksheets created when planning your deployment for the required parameters. 14. In the Ready to Complete panel, review the summary of the parameters that you have configured and click Finish. For troubleshooting purposes, take a 20 IBM SmartCloud Control Desk: Installation Guide (VM Image)

25 Results screen capture of the data in the Ready to Complete panel to provide a record of the properties and values that you specified. After the deployment is complete, a new entry for the WebSphere Application Server virtual machine is displayed 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 WebSphere Application 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 Application Server 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 for the virtual machine. Successful login confirms that the password functions correctly. 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 status and press Enter. 6. Check that you receive a response indicating that dmgr is running on WebSphere Application Server. If you do not see that response, complete the following 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 and press Enter. 8. Check that you receive a response indicating that nodeagent is running on WebSphere Application Server. If you do not see that response, complete the following 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 press Enter. Installing the VMImage solution 21