Setup of EdumetNT

Steps to implement Paul’s Client side Client/Server Oracle

A directory needs to be created on the NTServer and shared out to the proper groups. I recommend creating a directory called "OCSM_95" for the Windows 95 machines, and "OCSM_NT" for the Windows NT workstations. The groups that should be allowed access to the directory’s are "oracle_end_user", as read-only, and "oracle_admin", as full-control. (The only exception to this is for the first "donor" client, on initial install. That client needs to have full-control access. This is only an issue on Windows 95, because the Windows NT workstations installs REQUIRE the "Administrator" id to perform these functions).

With these two new shared directories created, we can begin the installation of the client side workstation software.

For Initial Installations :

Windows NT :

Log onto the workstation as Administrator
Map a virtual drive (network connection) to the NTServers newly shared directory. I recommend Letter X:
Map a virtual drive (network connection) to the NTServers oracle forms/reports directory that we keep our forms in. I recommend O:
Insert the Developer 2000 CD into the drive
VERY IMPORTANT : choose an Oracle Home of X:\orant !!!!!!!!!!!!!
Choose a deployment installation (Runtimes only).
Let the rest go until finished. This will have the effect of the software running over the network from the NTServer to the client workstation. The workstation really doesnt know that the software is not installed locally.
After the software load is complete, run the "regedit" utility. (Note that you must still be administrator)
Create a new directory called x:\Reg_Keys
Search for the string "ora" and everywhere you find it, export the registry key into the new Reg_Keys directory. (As long as it is not words like tempORArary, or stORAge !!)
When you get out of the Hkey_Local_Machine hive, you can just export the whole Oracle key (in the software key) and skip down to the next key, but all the HKLM keys must be done individually (about 25).
Create another new directory x:\misc.
Copy a valid hosts file into this location. If the current pc doesnt have one, then either get it from the server or build it from scratch. Either way, make sure that it is left in the x:\misc directory upon completion.
Logout of the machine as Administrator, and log back in as the regular user.
Create a shortcut for the Master menu and test it out. The drives should already be mapped, and path set, so it should work.

Windows 95 :

Log onto the workstation
Map a virtual drive (network connection) to the NTServers newly shared directory. I recommend Letter X:
Map a virtual drive (network connection) to the NTServers oracle forms/reports directory that we keep our forms in. I recommend O:
Insert the Developer 2000 CD into the drive
VERY IMPORTANT : choose an Oracle Home of X:\orawin95 !!!!!!!!!!!!!
Choose a deployment installation (Runtimes only).
Let the rest go until finished. This will have the effect of the software running over the network from the NTServer to the client workstation. The workstation really doesnt know that the software is not installed locally.
After the software load is complete, run the "regedit" utility.
Create a new directory called x:\Reg_Keys
Search for the string "ora" and everywhere you find it, export the registry key into the new Reg_Keys directory. (As long as it is not words like tempORArary, or stORAge !!)
When you get out of the Hkey_Local_Machine hive, you can just export the whole Oracle key and skip down to the next one, but all the HKLM keys must be done individually (about 65).
Create another new directory x:\misc.
Copy a valid hosts file into this location. If the current pc doesnt have one, then either get it from the server or build it from scratch. Either way, make sure that it is left in the x:\misc directory upon completion.
Copy the c:\windows\system\olepro32.dll file into the x:\misc directory.
Create a file in the x:\misc directory called "path" that has the following as its only line : PATH %PATH%;x:\orawin95\bin
There is a special registry key called step99.reg that needs to be imported. This key allows ’95 to do persistent drive connections.
Shutdown and restart, and make sure that the machine shows the two new drives and that you can run the forms runtime.
Create a shortcut for the Master menu and test it out. The drives should already be mapped, and path set, so it should work.