After you install vCenter Server, consider these postinstallation options before adding inventory for the vCenter Server to manage.

Install the vSphere Web Client and make sure that you can access the vCenter Server instance.

When vCenter Server and the database are installed on the same machine, after you reboot the machine, you might need to restart the VMware VirtualCenter Management Webservices service. See VMware vCenter Management Webservices Service Fails to Start.

Review the subtopics in this section for other postinstallation options.

For the Oracle Instant client, copy ojdbc14.jar to the vCenter Server tomcat directory vCenter install location\Infrastructure\tomcat\lib.

The Oracle 11g client and Oracle 12c client include ojdbc14.jar at: Install location\oracle\product\10.2.0\instance_name\jdbc\lib or Install location\app\Administrator\product\11.1.0\instance_name\sqldeveloper\jdbc\lib. The vCenter Server installer copies the file from the Oracle client installation location to the vCenter Server tomcat directory vCenter install location\Infrastructure\tomcat\lib.

If neither the ojdbc14.jar file nor the ojdbc5.jar file is found in the Oracle 11g or Oracle 12c client location, the vCenter Server installer prompts you to copy the file manually. You can download the file from the Oracle.com Web site.

After you install or upgrade the Oracle database and, if necessary, copy the ojdbc14.jar file or ojdbc5.jar file manually, restart the VMware VirtualCenter Management Webservices service. The VMware VirtualCenter Management Webservices service is located in the Services section of the Windows Administrative Tools control panel.

For environments that require strong security, VMware recommends that you replace the default certificates on your vCenter Server system with certificates signed by a commercial Certificate Authority (CA). See the information on increasing security for session information in the vSphere Examples and Scenarios documentation.