ActuateOne on VMware vsphere 5.0 and vcloud Director 1.5

Transcription

1 ActuateOne on VMware vsphere 5.0 and vcloud Director 1.5 Revision 1.1 March 2012 DEPLOYMENT AND TECHNICAL CONSIDERATIONS GUIDE

2 Table of Contents Revision Summary... 3 Introduction... 4 VMware and ActuateOne Overview... 5 ActuateOne Overview... 5 VMware vsphere... 6 vcloud Director... 7 vfabric Data Director... 8 ActuateOne Architecture and Deployment Strategy Testing Process and Results Testing Methodology and Overview Hardware and System Host Configuration Installed Software Virtual Machine Configuration Workload Used Results Observed ActuateOne Scalability Test: Scalability Testing Process and Results Hardware and System Host Configuration Workload Used Results Observed Deployment Best Practices Licensing Technical Support Conclusions Acknowledgements Resources D E P L OY M EN T A N D T E C HN I C A L C O N SI D ER A T I ON S G U I D E II

3 Revision Summary This version of documents includes the follow ing additional topics: ActuateOne horizontal scalability testing performed using vcloud Director 1.5 and vsphere 5.0 VMw are vfabric Data Director w as used to provision vpostgres Database and horizontal scalability tests w ere executed using both Postgres and vpostgres database D E P L OY M EN T A N D T E C HN I C A L C O N SI D ER A T I ON S G U I D E 3

4 Introduction This document provides direction for those interested in running ActuateOne on VMw are vsphere 5.0 and VMw are vcloud Director 1.5. It provides basic guidance on the architecture of ActuateOne, and the value of utilizing the VMw are platform for private cloud deployment of ActuateOne behind a corporate firew all. This paper covers the results of recent testing done jointly by VMw are and Actuate, and also describes performance and functionality of ActuateOne on VMw are virtual infrastructure. In addition, it also outlines some best practices in utilizing the tw o product sets together for your private cloud deployment of ActuateOne. D E P L OY M EN T A N D T E C HN I C A L C O N SI D ER A T I ON S G U I D E 4

5 VMware and ActuateOne Overview The ActuateOne Platform w ith VMw are vsphere gives enterprises the ability to deploy their Business Intelligence (BI) applications in a unified cloud environment w ith built-in security and role-based access control. Together, the joint solution delivers three unique capabilities to the enterprise: An efficient and secure approach to using shared infrastructure for servicing highly frequent requests A standardized, portable, and extensible approach to enable w orkloads to be deployed w ithout manual configuration and across multiple clouds Agile access to shared infrastructure for provisioning w orkloads w hen in demand. ActuateOne Overview Recognizing the need for seamless, dynamic and accessible Business Information solutions, Actuate the co-founder and co-leader of the premier BIRT open source development project presents ActuateOne. This innovative suite of integrated BI products and services features a common architecture for development and deployment that meets the dynamically changing needs of information consumers. ActuateOne enables any organization to build and deploy mission critical Business Intelligence and rich information applications. These applications can be built for any user, anyw here, w ith a variety of tools based on one user experience, supported by one server and built w ith one design using BIRT. Using value-add design tools: End users can modify their view s of data to suit their needs Business users can develop their ow n data visualizations, based on templates created by IT and/or developers IT and developers can create templates and data visualizations that can be used by business and end users Users can customize the BIRT content received in any format, including rich visualizations and dashboards, to meet their ow n needs. Using value-added deployment options, depending on project size, requirements and budget, deployments can be Scaled to support any number of employees, customers or partners, using a pre-built platform Set up and running in less than an hour Cloud ready, providing clustering and elastic provisioning w ith support for a stateless image that allow s administrators to make changes at runtime w ithout service interruptions. D E P L OY M EN T A N D T E C HN I C A L C O N SI D ER A T I ON S G U I D E 5

6 Figure 1: ActuateOne Suite VMware vsphere VMw are s leading virtualization solutions based on our flagship product, VMw are vsphere provides multiple benefits to IT administrators and users. VMw are virtualization creates a layer of abstraction betw een the resources required by an application and operating system, and the underlying hardw are that provides those resources. A summary of the value of this abstraction layer includes the follow ing: Consolidation: VMw are technology allow s multiple application servers to be consolidated onto one physical server, w ith little or no decrease in overall performance. Ease of Provisioning: VMw are virtualization encapsulates an application into an image that can be duplicated or moved, greatly reducing the cost of application provisioning and deployment. Manageability: Virtual machines may be moved from server to server w ith no dow ntime using VMw are VMotion, w hich simplifies common operations like hardw are maintenance and reduces planned dow ntime. Availability: Unplanned dow ntime can be reduced and higher service levels can be provided to an application. VMw are High Availability (HA) ensures that in the case of an unplanned hardw are failure, any affected virtual machines are restarted on another host in a VMw are cluster. D E P L OY M EN T A N D T E C HN I C A L C O N SI D ER A T I ON S G U I D E 6

7 Figure 2: Applications in a Virtual Environment vcloud Director VMw are vcloud Director enables enterprises to build secure, multi-tenant private clouds by pooling infrastructure resources into virtual datacenters. vcloud Director enables users to access these resources through w eb based portals and programmatic interfaces as fully automated, catalog-based services. For more information on vcloud Director, see the Resources section later in this paper. For ActuateOne, vcloud Director provides the management capability for importing the BIRT application as a virtual appliance also called a vapp. vcloud Director is also used to provision and de-provision the vapp in a manner that is very consistent and repeatable, w hich significantly reduces ActuateOne set-up time and simplifies deployment. Additionally, ActuateOne deployment can be scaled by continually adding or removing iserver as a virtual machine (also know n as - scaling unit) to a running vapp, w hich contains ActuateOne w orkload in a consistent and secure manner. D E P L OY M EN T A N D T E C HN I C A L C O N SI D ER A T I ON S G U I D E 7

8 Figure 3: VMw are vcloud Director vfabric Data Director VMw are s vfabric Data Director pow ers database-as-a-service for your cloud, thereby reducing the database spraw l and drastically accelerating application development cycles w ith a self-service database provisioning and operations platform. vfabric Data Director is an enterprise solution that extends the benefits of VMw are s leading virtualization platform to the database tier and lets administrators securely automate and delegate routine tasks, including database provisioning, backup, and cloning. The first database supported on Data Director is VMw are vfabric Postgres 9.0 (vpostgres), a new offering from VMw are based on and fully compatible w ith PostgreSQL. vpostgres is a vsphere-optimized ACID and ANSI-SQL relational database and is the first of a broad range of commercial and open source databases to be supported by Data Director. These capabilities enable vfabric Data Director to offer the agility of public cloud database services w ith enterprise-grade security, flexibility, control, and compliance. Actuate bundles a PostgreSQL database in their standard distribution for evaluation and small business deployments. It also supports other major databases such as Oracle, IBM DB2, and Microsoft SQL Server. Instead of using this Postgres DB instance, w e used VMw are vfabric Data Director to provision a vfabric Postgres 9.0 for our test. By doing this, there w as an option to provision our Postgres DB instance from existing Postgres DB templates, w hich define the scale of deployments from small, medium to large. How ever, the focus of this test w as to primarily observe at the compatibility and performance aspects of how vpostgres served as the backend database for Actuate iserver. The parameters like usability, manageability, and overall cost savings vfabric vpostgres could pass onto our customers w ere not discussed in this document. For more information on vfabric Data Director, you can visit the site w w.vmw are.com/products/application-platform/vfabric-data-director/overview.html D E P L OY M EN T A N D T E C HN I C A L C O N SI D ER A T I ON S G U I D E 8

9 Figure 4: VMw are vfabric Data Director D E P L OY M EN T A N D T E C HN I C A L C O N SI D ER A T I ON S G U I D E 9

10 ActuateOne Architecture and Deployment Strategy Figure 5 illustrates a typical customer solution architecture deploying ActuateOne w ith multi-instance and multi-tenancy in a physical environment. Figure 5: ActuateOne Architecture Design in a Physical Environment The architecture includes all components found in a real-w orld ActuateOne deployment, beyond the iserver: Application Server Tier: The ActuateOne Information Console, running on an application server, relays requests to the Actuate BIRT iserver. iserver Tier: For BI content generation requests, the Actuate iserver retrieves data from a database. Encyclopedia Tier: For BI content view ing requests, the Actuate iserver retrieves the report document from the iserver Encyclopedia and renders it in HTML. The Information Console then presents the results to the end user on the Internet. Storage Tier: SAN or shared disk arrays can be used to house the iserver Encyclopedia w ith 24x7 reliability. If ActuateOne is deployed in a virtual environment using vcloud Director, the architecture remains the same. The main difference is that the physical servers w ould be virtualized in a cloud environment. This offers more agility and flexibility to ActuateOne w orkloads as they can be easily scaled out and scaled back on demand. Figure 6illustrates the ActuateOne architecture in a virtual environment. D E P L OY M EN T A N D T E C HN I C A L C O N SI D ER A T I ON S G U I D E 10

11 Figure 6: ActuateOne Architecture Design in a Virtual Environment D E P L OY M EN T A N D T E C HN I C A L C O N SI D ER A T I ON S G U I D E 11

12 Testing Process and Results To characterize the performance of ActuateOne on VMw are Infrastructure, performance tests w ere carried out jointly by VMw are and Actuate. The configuration tested and the results are summarized below. Testing Methodology and Overview The primary testing objective w as to determine w hether ActuateOne BIRT iserver and Information Console products could run more resiliently on VMw are platform. ActuateOne w as deployed in a virtual environment, and four tests w ere conducted to validate BI content generation and view ing during the vmotion, VMw are DRS and VMw are HA features. Hardware and System Host Configuration The follow ing table describes the configuration of ESX host servers and storage in the test configurations. Table 1: ESX Host Hardw are H AR D W AR E Server C ON F I GU R ATI ON One HP Proliant DL980 G7 server equipped w ith: Intel Xeon 2.26 GHz Sockets: 8 Number of Cores per socket: 8 Hyperthreading: Enabled 512 GB RAM 6 x 1GBPS NICs 2 x 10GBPS NICs Tw o HP Proliant DL380 G7 servers equipped w ith: Intel Xeon 3,332 GHz Sockets: 2 Number of Cores per socket: 6 Hyperthreading : Enabled 98 GB RAM 6 x 1GBPS NICs 2 x 10GBPS NICs Storage HP P4600 iscsi SAN Storage RAID 10 Netw ork RAID 10 D E P L OY M EN T A N D T E C HN I C A L C O N SI D ER A T I ON S G U I D E 12

13 Installed Software The follow ing table lists the softw are used in the Actuate solution. Table 2: Installed Softw are I N STAL L ED SOF TW AR E VMw are ESX 5.0 vcenter 5.0 vcloud Director 1.5 vshield 1.5 vfabric Data Director 1.5 Actuate ActuateOne BIRT iserver 11 SP2 ActuateOne Information Console 11 SP2 Database Postgres SQL 8.4 Virtual Machine Configuration The follow ing table describes the configuration of virtual machines running on ESX host servers in the Actuate test configurations. Table 3: Virtual Machine Configuration VI R TU AL MAC H I N E ActuateOne BIRT iserver ActuateOne Information Console PostgreSQL H AR D W AR E C ON F I GU R ATI ON 4 vcpus 16 GB RAM 2 vcpu 4GB RAM 2 vcpu 4GB RAM Workload Used The view ing load test simulated multiple users simultaneously logging in and conducting different types of view ing requests on randomly selected pages of pre-generated BIRT designs. It is conducted w ith a constant load of user view ing requests to the ActuateOne Information Console and BIRT iserver. All systems w ere utilized w ith a steady operational w orkload pattern, w here each system stayed at around 50 percent CPU utilization. With the load test in effect, a VMw are feature (vmotion, DRS, or HA) w as activated and given enough time to complete w ithin a predetermined length of time. Results Observed Test 1: Load Test With vmotion Activation A 15-minute load test w as conducted w ith one ActuateOne BIRT iserver and one Information Console instance. At the five-minute mark of the load test, vmotion w as activated to move the iserver VM to another ESXi host. For both configurations, the average response time and throughput remained w ithin the expected timeframe. D E P L OY M EN T A N D T E C HN I C A L C O N SI D ER A T I ON S G U I D E 13

14 %Used ActuateOne on VMware vsphere 5.0 and vcloud Director 1.5 Table 4: Test 1- Load Test With vmotion Activation TI ME PER I OD AC TI ON AVER AGE R ESPON SE TI ME TH R OU GH PU T Minute 1-5 Load without vmotion 0.1 seconds 50 requests/sec Minute 6-9 vmotion being activated 4.7 seconds 39 requests/sec Minute Load with vmotion 0.1 seconds 49 requests/sec Figure 7: Test 1- Load Test With vmotion Activation iserver CPU Utilization during vmotion %Used Test 2: Load Test With VMw are DRS A 30-minute load test w as conducted w ith tw o ActuateOne BIRT iserver and tw o Information Console instances. At the 20-minute mark of the load test, the DRS feature w as activated. For both configurations, the average response time and throughput remained w ithin the expected timeframe. Table 5: Test 2 - Load Test With VMw are DRS TI ME PER I OD AC TI ON AVER AGE R ESPON SE TI ME TH R OU GH PU T Minute 1-17 Load without DRS 0.2 seconds 150 requests/sec Minute DRS being activated 7.7 seconds 75 requests/sec Minute Load with DRS 0.8 seconds 144 requests/sec D E P L OY M EN T A N D T E C HN I C A L C O N SI D ER A T I ON S G U I D E 14

15 Test 3: Load Test With VMw are HA A 15-minute load test w as conducted w ith tw o ActuateOne BIRT iserver and tw o Information Console instances. Each iserver and Information Console pair ran on a different ESX host. At the five-minute mark of the load test, one ESX host w as forcibly restarted to simulate a crash. Table 6: Test 3- Load Test With VMw are HA TI ME PER I OD AC TI ON AVER AGE R ESPON SE TI ME TH R OU GH PU T Minute 1-5 Load without HA 0.2 seconds 150 requests/sec Minute 6-10 HA being activated 8.7 seconds 42 requests/sec Minute Load with HA 0.2 seconds 150 requests/sec Test 4: BIRT Content Generation w ith vmotion The final test simulated BIRT content generation w ith and w ithout the operation of vmotion. A long-running generation job w as submitted and w as expected to finish in approximately 30 minutes. At the five-minute mark, the iserver executing this job w as moved via vmotion. The job continued to run before, during, and after vmotion w as activated. The w hole job finished successfully, w ithout any issues, in 30 minutes. The generated BIRT document w as complete w ithout any issues. D E P L OY M EN T A N D T E C HN I C A L C O N SI D ER A T I ON S G U I D E 15

16 ActuateOne Scalability Test: The primary testing objective w as to determine w hether ActuateOne BIRT iserver and Information Console products could scale vertically as w ell as horizontally on VMw are Virtual platform. ActuateOne w as deployed in a VMw are vcloud Director environment, and tests w ere conducted to validate BI content view ing. The hardw are used for the validation w as different than used in the previous tests. The Workload used remains same as before as mentioned in Table 1. The Virtual Machine configurations w ere changed for the vertical scalability tests but for the horizontal scalability tests, same configuration w as used. We also validated the use of VMw are vfabric Data Director to provision and configure vpostgres Database for ActuateOne BIRT application. Also, Scalability tests w ere performed to verify Actuate BIRT performance w hile using vpostgres Database. Scalability Testing Process and Results The follow ing tests w ere executed to check the ActuateOne scalability on VMw are vsphere platform: 1. iserver horizontal scalability tests: For the first test, ActuateOne application components w ere deployed to vcloud director catalog. The iserver cluster w as configured using VMs mentioned in the table below. The number of iserver VMs in the cluster w as increased to 2, 4, and 6 for different tests. Table 7: Virtual Machine Configuration VI R TU AL MAC H I N E ActuateOne BIRT iserver ActuateOne Information Console PostgreSQL H AR D W AR E C ON F I GU R ATI ON 2 vcpus 16 GB RAM 2 vcpu 4GB RAM 2 vcpu 4GB RAM 2. Factory Scalability Test: VMw are recommends starting one Java factories per vcpu for the iserver VM. This test evaluates the impact of starting more than 4 factories on a 4 vcpu iserver VM. F AC TOR I ES MEMOR Y 2 4 GB 4 16 GB 8 16 GB GB D E P L OY M EN T A N D T E C HN I C A L C O N SI D ER A T I ON S G U I D E 16

17 3. vpostgres Test: VMw are vfabric Data Director w as used to provision vpostgres Database for the Actuate Cluster. The same horizontal scalability tests w ere executed using the new database. A midsize vpostgres database w ith 2 vcpu and 4GB RAM w as deployed and the Database configurations for iserver Cluster w ere done using the Data Director UI. Hardware and System Host Configuration The follow ing table describes the configuration of ESX host servers and storage in the test configurations. Table 7: ESX Host Hardw are H AR D W AR E Server C ON F I GU R ATI ON Two HP Proliant BL460 G7 servers equipped with: Intel Xeon 2.6 GHz Sockets: 2 Number of Cores per socket: 6 Hyperthreading : Enabled 64 GB RAM Storage EMC VNX Aggregate of 15 SSD disks RAID 10 8 Gbps fibre connectivity 15K RPM disks FC protocol. Workload Used The view ing load test simulated multiple users simultaneously logging in and conducting different types of view ing requests on randomly selected pages of pre-generated BIRT designs. It is conducted w ith a constant load of user view ing requests to the ActuateOne Information Console and BIRT iserver. All systems w ere utilized w ith a steady operational w orkload pattern, w here each system stayed at around 50 percent CPU utilization. With the load test in effect, a VMw are feature (vmotion, DRS, or HA) w as activated and given enough time to complete w ithin a predetermined length of time. D E P L OY M EN T A N D T E C HN I C A L C O N SI D ER A T I ON S G U I D E 17

18 Results Observed Test1: iserver Scalability Test 30-minute load tests w ere conducted w ith various combinations of A ctuateone BIRT iserver and one Information Console instance cluster. For all configurations, the average response time and throughput remained w ithin the expected timeframe. The table below show s the Throughput for ActuateOne Application and the resource utilization for all the virtual machines in the cluster. Table 8: Test 1- iserver Scalability Test TH R OU GH PU T N OD ES W I TH TH I N K TI ME N O TH I N K TI ME Figure 8: iserver Scalability Test (With Think time) Figure 9: iserver Scalability Test (No Think time) D E P L OY M EN T A N D T E C HN I C A L C O N SI D ER A T I ON S G U I D E 18

19 The iserver VM s 2 vcpu w ere completely saturated during the test execution but there w ere no bottlenecks and ready time observed. The table below show s the VM resource utilization for the entire duration of the tests Table 9: 6 Node iserver Cluster Esxtop resource Utilization CPU Memory Network Disk (%) (mb) Packets/sec I/O sec Latency(ms) Ready Read Write VM Avg Max (Avg/Max) Avg Max Recd Txmitted Avg Max Avg Max Avg Max iserver / iserver / iserver / iserver / iserver / iserver / ActuateNFS / D E P L OY M EN T A N D T E C HN I C A L C O N SI D ER A T I ON S G U I D E 19

20 Test 2: Factory Scalability Test The view ing tests w ere run for a 4 vcpu iserver VM w ith different number of factories for different configurations. Due to more number of factories per vcpu, the 8 and 16 factory tests did not scale properly as expected. VMw are recommends starting one Java factory per vcpu for BIRT iserver VMs. Table 10: Test 2: Factory Scalability Test F AC TOR I ES TH R OU GH PU T Test3: vpostgres Test: vpostgres performed w ell w ith iserver and compared to Postgres, there w as some improvement in the throughput for larger deployments. For the horizontal scalability tests (Test1), the Postgres DB w as installed w ithin the iserver1. As VMw are vfabric Data Director provisioned another VM for vpostgres, the performance for 4 and 8 node tests w as better w hile using vpostgres DB. Table 11: Test 2: Factory Scalability Test N OD ES TH R OU GH PU T VPOSTGR ES POSTGR ES D E P L OY M EN T A N D T E C HN I C A L C O N SI D ER A T I ON S G U I D E 20

21 Figure 10: Factory Scalability Test w ith vpostgres Table 12: 8Node iserver Cluster w ith vpostgres Esxtop resource Utilization CPU Memory Network Disk (%) (mb) Packets/sec I/O sec Latency(ms) Ready Read Write VM Avg Max (Avg/Max) Avg Max Recd Txmitted Avg Max Avg Max Avg Max iserver-vpost / iserver / iserver / iserver / iserver / iserver / iserver / iserver / D E P L OY M EN T A N D T E C HN I C A L C O N SI D ER A T I ON S G U I D E 21

22 Deployment Best Practices Actuate and VMw are relentlessly w orked closely together to determine how IT data centers can best meet service requirements w hen deploying ActuateOne in VMw are virtualized environments. Results from the testing described earlier in this paper show s that running ActuateOne on VMw are virtual machines can provide an effective production-ready platform. With added benefits such as management and administrative flexibility, strong isolation and higher availability, VMw are platform can serve as an ideal platform for ActuateOne Server consolidation. Specific recommendations include: Carefully design storage configurations and evaluate external storage choices, RAID levels, and latency of IO operations. High spindle count on LUNs to ensure I/O capacity available. Use Thick Eager Zeroed disks for better I/O performance. Consider Nehalems or Westmeres w ith EPT for maximum performance. Consider using server-class netw ork interface cards (NICs) for the best performance and configure paravirtualized vmxnet3 adapters for better netw ork throughput. Disconnect or disable unused or unnecessary physical hardw are devices, such as o o o o o COM ports LPT ports USB controllers Floppy drives Optical drives (that is, CD or DVD drives) Disconnecting or disabling these devices w ill help free up interrupt resources, because traditionally some devices such as USB controllers operate using a polling scheme that consumes extra CPU resources. Lastly, some PCI devices reserve blocks of memory, making that memory unavailable to ESX. Install VMw are tools on the virtual machines. The VMw are Tools package provides support required for shared folders and for drag and drop operations. Other tools in the package support synchronization of time in the guest operating system w ith time on the host, automatic grabbing and releasing of the mouse cursor, copy and paste operation betw een guest and host, and improved mouse performance in some guest operating systems Use VMw are vmotion w ith VMw are DRS to balance the load. Scale out versus scale up: Determine w hat components of the architecture w ork w ell w ith more than one virtual machine, and how large each virtual machine should be. Adding capacity: Determine how you could extend the configuration tested by adding more virtual machines or increasing the size of virtual machines to allow a higher user count or larger batch jobs to be run. Availability: Plan use of VMw are HA and VMw are FT as w ell as other availability solutions (such as other clustering technologies). Consider use of other disaster recovery options such as VMw are s Site Recovery Manager (SRM). For better performance, ensure that the vcloud Organization vdc is configured to Thick Provision the vapps w hile deploying from the Catalog. D E P L OY M EN T A N D T E C HN I C A L C O N SI D ER A T I ON S G U I D E 22

23 Licensing Customers w ho w ant to run multiple instances of the Actuate softw are using VMw are based virtual machines, can license w ith Per Instance Licensing (the default), Multi-Instance Licensing, or Work Unit Licensing. Actuate Multi-Instance licensing allow s customers to deploy an unlimited number of instances of the ActuateOne softw are on the licensed CPU Cores. Multi-Instance licensing is a cost effective option w hen multiple instances of the softw are are being used in a virtualized environment supporting multiple applications and/or large numbers of users. ActuateOne Work Unit licensing model offers flexibility for multi-core, server farm and cloud environments. It enables organizations to effectively plan for the BIRT capacity required, w ith granular licensing options based upon partial CPU usage. Work Unit licensing ensures that customers can enjoy "pay as you grow " agility, know ing that Actuate maintains a vested interest in the success of application development. Furthermore, the Work Unit licensing model facilitates iterative, spontaneous application development and test cycles, since it enables IT departments to conveniently budget and plan w hile responding efficiently to end user requirements. D E P L OY M EN T A N D T E C HN I C A L C O N SI D ER A T I ON S G U I D E 23

24 Technical Support Actuate support w ebsite: ww.actuate.com/support/ D E P L OY M EN T A N D T E C HN I C A L C O N SI D ER A T I ON S G U I D E 24

25 Conclusions Overall, testing results show that running ActuateOne on VMw are Infrastructure performs w ell. Furthermore, it has the potential to reduce cost, increase service levels, and simplify the manageability of the application. The iserver Application can be easily deployed and configured for vcloud environment and due to its scalable architecture, can provide additional CPU/Memory resources on demand. VMw are recommends one iserver Java factory on one vcpu for best performance. Based on the testing, AcutateOne could scale linearly for the VMw are Virtual configuration documented in this guide. Our test setup time w as also significantly reduced due to effortless rapid provisioning of vpostgres database enabled by VMw are vfabric Data Director. D E P L OY M EN T A N D T E C HN I C A L C O N SI D ER A T I ON S G U I D E 25

26 Acknowledgements The follow ing individuals contributed to the creation of this deployment guide: Michael Lee, Actuate ShiHeng Guan, Actuate Manvender Raw at, VMw are Gilbert Lau, VMw are D E P L OY M EN T A N D T E C HN I C A L C O N SI D ER A T I ON S G U I D E 26

27 Resources Customers can find more information about VMw are and Actuate products using the links listed below. VMw are Resources VMw are official w ebsite: w w.vmw are.com/ VMw are Infrastructure Web site: w w.vmw are.com/products/data_center.html VMw are dow nload Web site: ww.vmware.com/dow nload/ VMw are support Web site: w w.vmw are.com/vmtn/ vsphere Installation and Setup Guide are.com/vsphere-50/topic/com.v mw are.icbase/pdf/vsphere-esxi-vcenter-server-50- installation-setup-guide.pdf VMw are vsphere 5 Performance Best Practices: w w.vmw are.com/pdf/perf_best_practices_vsphere5.0.pdf vcloud vcloud Director Installation and Configuration Guide: ww.vmware.com/pdf/vcd_15_install.pdf vcloud Director Administrator's Guide: ww.vmw are.com/pdf/vcd_15_admin_guide.pdf VMw are Performance Tuning Paper: w w.vmw are.com/pdf/vi_performance_tuning.pdf vcloud Director Performance and Best Practices: w w.vmw are.com/files/pdf/techpaper/vmw-performance-vcloud-director-1-0.pdf System Compatibility Guide for a complete list of compatible hardw are: w w.vmw are.com/resources/compatibility/search.php Compatibility Guide for a complete list of compatible storage devices: w w.vmw are.com/pdf/vi35_san_guide.pdf I/O Compatibility Guide for a complete list of compatible netw orking devices: w w.vmw are.com/pdf/vi35_io_guide.pdf D E P L OY M EN T A N D T E C HN I C A L C O N SI D ER A T I ON S G U I D E 27

28 Actuate Resources Actuate official w ebsite: w w.actuate.com/home/ ActuateOne product w ebsite: w w.actuate.com/products/ BIRT Exchange dow nload w ebsite: w w.birt-exchange.com/be/dow nloads/ Actuate support w ebsite: w w.actuate.com/support/ Actuate w hite papers: w w.actuate.com/resources/w hitepapers/ BIRT developer w ebsite: w w.birtexchange.com D E P L OY M EN T A N D T E C HN I C A L C O N SI D ER A T I ON S G U I D E 28