VMware VS4-ENT-PL-A Setup Guide - Page 31

Create a 64-Bit DSN, Confirm That vCenter Server Can Communicate with the Local Database - client windows 7 download

Get VMware VS4-ENT-PL-A - vSphere Enterprise Plus PDF manuals and user guides View all VMware VS4-ENT-PL-A manuals
Add to My Manuals
Save this manual to your list of manuals

Page 31 highlights

Chapter 3 Before You Install vCenter Server Table 3‑1. Configuration Notes for Databases Supported with vCenter Server (Continued) Database Type Configuration Notes Microsoft SQL Server 2008 Ensure that the machine has a valid ODBC DSN entry. NOTE This database is not supported for the vCenter Server Appliance. Oracle Ensure that the machine has a valid ODBC DSN entry. After you complete the vCenter Server installation, take the following steps: n Apply the latest patch to the Oracle client and server. n Copy the Oracle JDBC driver (ojdbc14.jar or ojdbc5.jar) to the vCenter Server installation directory, in the tomcat\lib subdirectory: vCenter install location\Infrastructure\tomcat\lib. n In the Services section of the Windows Administrative Tools control panel, restart the WMware VirtualCenter Management Webservices service. The vCenter Server installer attempts to copy the Oracle JDBC driver from the Oracle client location to the vCenter Server installation directory. If the Oracle JDBC driver is not found in the Oracle client location, the vCenter Server installer prompts you to copy the file manually. You can download the file from the oracle.com Web site. Create a 64-Bit DSN The vCenter Server system must have a 64-bit DSN. This requirement applies to all supported databases. Procedure 1 Select Control Panel > Administrative Tools > Data Sources (ODBC). 2 Use the application to create a system DSN. If you have a Microsoft SQL database, create the system DSN for the SQL Native Client driver. 3 Test the connectivity. The system now has a DSN that is compatible with vCenter Server. When the vCenter Server installer prompts you for a DSN, select the 64-bit DSN. Confirm That vCenter Server Can Communicate with the Local Database If your database is located on the same machine on which vCenter Server will be installed, and you have changed the name of this machine, make sure the vCenter Server DSN is configured to communicate with the new name of the machine. Changing the vCenter Server computer name impacts database communication if the database server is on the same computer with vCenter Server. If you changed the machine name, you can verify that communication remains intact. The name change has no effect on communication with remote databases. You can skip this procedure if your database is remote. Check with your database administrator or the database vendor to make sure all components of the database are working after you rename the server. Prerequisites n Make sure the database server is running. n Make sure that the vCenter Server computer name is updated in the domain name service (DNS). Procedure 1 Update the data source information, as needed. VMware, Inc. 31

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
Table 3
‑
1.
Configuration Notes for Databases Supported with vCenter Server (Continued)
Database Type
Configuration Notes
Microsoft SQL Server 2008
Ensure that the machine has a valid ODBC DSN entry.
N
OTE
This database is not supported for the vCenter Server Appliance.
Oracle
Ensure that the machine has a valid ODBC DSN entry.
After you complete the vCenter Server installation, take the following steps:
n
Apply the latest patch to the Oracle client and server.
n
Copy the Oracle JDBC driver (ojdbc14.jar or ojdbc5.jar) to the vCenter Server
installation directory, in the
tomcat\lib
subdirectory:
vCenter install
location
\Infrastructure\tomcat\lib
.
n
In the Services section of the Windows Administrative Tools control panel, restart the
WMware VirtualCenter Management Webservices service.
The vCenter Server installer attempts to copy the Oracle JDBC driver from the Oracle client
location to the vCenter Server installation directory. If the Oracle JDBC driver is not found
in the Oracle client location, the vCenter Server installer prompts you to copy the file
manually. You can download the file from the oracle.com Web site.
Create a 64-Bit DSN
The vCenter Server system must have a 64-bit DSN. This requirement applies to all supported databases.
Procedure
1
Select
Control Panel > Administrative Tools > Data Sources (ODBC)
.
2
Use the application to create a system DSN.
If you have a Microsoft SQL database, create the system DSN for the SQL Native Client driver.
3
Test the connectivity.
The system now has a DSN that is compatible with vCenter Server. When the vCenter Server installer
prompts you for a DSN, select the 64-bit DSN.
Confirm That vCenter Server Can Communicate with the Local Database
If your database is located on the same machine on which vCenter Server will be installed, and you have
changed the name of this machine, make sure the vCenter Server DSN is configured to communicate with
the new name of the machine.
Changing the vCenter Server computer name impacts database communication if the database server is on
the same computer with vCenter Server. If you changed the machine name, you can verify that
communication remains intact.
The name change has no effect on communication with remote databases. You can skip this procedure if
your database is remote.
Check with your database administrator or the database vendor to make sure all components of the
database are working after you rename the server.
Prerequisites
n
Make sure the database server is running.
n
Make sure that the vCenter Server computer name is updated in the domain name service (DNS).
Procedure
1
Update the data source information, as needed.
Chapter 3 Before You Install vCenter Server
VMware, Inc.
31