In this scenario you have three logically distinct machine types making up your total solution, the first machine hosts your Applications and Virtuoso client components (Client Machine), the second hosts your Virtuoso server, (Middle Tier Server Machine) and the third machine your back end Database Server (Database Server Machine). This installation configuration format will allow Windows client machines to communicate with non Windows middle-tier server machines running Virtuoso, as well as allowing Virtuoso clients on non Windows client machines to connect to Virtuoso servers on windows based middle-tier server machines.
2.2.3.3.1. Client Components:
-
Move the Virtuoso installation archive into a temporary
installation folder on your Client machine
-
Choose the Client install option.
No further component selection will be required.
Figure: 2.2.3.3.1.1. Setup Screens -
The installer will now extract and install your Virtuoso Client components
2.2.3.3.2. Middle-Tier Server Components:
You need to install both the Virtuoso client and server components on this machine. This is due to the fact that in many cases this server will double as an Application Server, which entails having clients connecting to an application service that uses Virtuoso for data access.-
Move the Virtuoso installation archive into a temporary
installation folder on your Server machine.
-
Choose the Server install option.
Figure: 2.2.3.3.2.1. Setup Screens -
At the component selection, uncheck the "Sample Application" check-box then the
"Virtuoso Driver for ODBC" and "Virtuoso Drivers for JDBC"
check-boxes since you are only installing Virtuoso's Server components on this machine.
-
The installer will now extract and install your Virtuoso Server components.
Referecene:
http://docs.openlinksw.com/virtuoso/installwin32.html
0 comments:
Post a Comment