Upgrading from a 32-bit to a 64-bit Release
The OpenROAD runtime, development, and eClient features are 32-bit-only implementations. The OpenROAD Server Pooler and OpenROAD Application Server are 32-bit implementations. The OpenROAD Server Client has a hybrid 32-bit/64-bit .NET client interface, a 32-bit Java Client interface, a 64-bit Java Client interface, and a 64-bit DCOM interface.
64-bit applications can communicate with the 32-bit OpenROAD Server using the hybrid .NET interface, the 64-bit Java client, and the 64-bit DCOM interface.
The following is from the readme.txt file in the %II_SYSTEM%\ingres\bin64 directory.
The files contained in this archive (bin64.zip) can be used to access the OpenROAD Server (32-bit) from 64-bit processes (for example, a Java Virtual Machine) on Windows 64-bit installations. The files ororso.dll, orps.dll, orrsojni.dll, and comtestrso.exe are 64-bit versions of those delivered in %II_SYSTEM%\ingres\bin. The files msvcr90.dll, msvcm90.dll, msvcp90.dll, and Microsoft.VC90.CRT.manifest are the Microsoft Visual C++ runtime redistributables (64-bit).
To install the 64-bit files
1. Create a new %II_SYSTEM%\ingres\bin64 directory in your OpenROAD installation on your Windows 64-bit machine if it does not exist yet.
2. Extract the contained files into the %II_SYSTEM%\ingres\bin64 directory.
3. Register the bin64-DLLs orrso.dll and orps.dll using %windir%\system32\regsvr32 (64-bit version), for example:
%windir%\system32\regsvr32 %II_SYSTEM%\ingres\bin64\orps.dll
%windir%\system32\regsvr32 %II_SYSTEM%\ingres\bin64\orrso.dll
4. Add the %II_SYSTEM%\ingres\bin64 directory in front of the PATH (or other) environment variable(s) where required, when using 64-bit processes. For example, for Tomcat, configure its “Java” settings by adding the Java option:
-Djava.library.path=full path of %II_SYSTEM%\ingres\bin64