- IDs & Accounts
- Networks / Telephones
- Academic Services
- Information Security
- Web Services
- Bobcat Depot
- OIT Projects
- About OIT
The OAK system has been retired and decommissioned.
This page addresses the migration process for people whose pages were on OAK and are moving to www.ohio.edu/people/; there are separate instructions for working with pages on the new server.
On the new server, we do not automatically create a default home page. You must copy your existing "index.html" or "index.htm" file from OAK during the migration process, if you want to block automatic display of the linked list of all your files and folders; see the discussion in "Using Your Web Files."
All requests for your pages at their old location on OAK will be redirected automatically, so that the browser will ask for them from their new location. Until you upload them, the result will be a "404 -- not found" display. After your pages have been migrated to the new server (people2.ohio.edu, which for brevity is known as, "people2"), everyone whose browser asks for your pages at their old addresses will automatically find the pages at their new addresses.
The people2 server does provide password-protected browsing access control and secure subsites. If you have been using those features on OAK, you will be able to continue to use them on people2.
The OAK server was case-sensitive for both folder names and file names. The people2 server is case-blind for both folder names and file names. If you had on OAK a folder within which there were two files whose names differ only by the case of one or more letters, or within which there were two folders whose names differ only by the case of one or more letters, then you will have to rename one or both, so that their names are different when examined case-blind, and you will have to update your HTML to reference the affected items by their new names (e.g., in anchor tags, image tags, etc.).
The primary differences between publishing web pages from OAK and from people2 are the name of the server, the location of your files on the server, and some related details of the file transfer process. On OAK, you had a folder for all your files, including e-mail and web pages; your public web pages were in a folder called, "public_html," and your secure web pages were in a folder called, "public_shtml." On people2, there are separate folders for the public and the secure subsites, within each of which there is a folder named, "people," and within those folders there is a folder for each person. The file location changes are summarized in the following illustration:
The first step, normally done one time only, is to create your personal subdirectories for public and secure pages on people2 (the two folders shown as "OhioID" on the right side in the illustration above).
For the details, see http://www.ohio.edu/oit/webservices/people/provisionsteps.cfm.
If you don't already have a complete copy of your OAK web files on your personal computer's disk drive, contact firstname.lastname@example.org for assistance.
The next step is to transfer your files to people2. For the details of uploading your files, see http://www.ohio.edu/oit/webservices/people/.
There is no Web-DAV access to people2 (hence no way for your folders on people2 to appear as if they were disk drives attached to your personal computer), but both Fetch and FileZilla do permit mass file transfers between your personal computer and people2.
OAK web files had URLs similar to
where your own Ohio ID was between the tilde ("~") and the following slash.
Your pages on people2 will have tilde-free URLs similar to
where your own Ohio ID will be between the people/ and the following slash.
If you perform the steps listed below in full, and in the order stated, then people who follow links leading to your pages on OAK will always get to the page they wanted:
Perform the general site cut-over steps (that link will open in a new window, to make it easy to return to and complete the rest of the steps listed here).
On Tuesday morning, June 28, 2011, we updated the OAK web server software configuration so that when anyone attempts to get any of your old pages, the browser is redirected to that page on the new server.
You can confirm that the redirect is working correctly by pointing your browser at one of your old OAK pages, and observe that it shows that page from the new server. (If you have not migrated your site, the result will be an error display, when the server fails to find the requested item after the redirect.)
If you encounter any problem, do let us know, by e-mail to email@example.com!
You will be able to restrict access to your secure Web pages, permitting only those people whom you authorize to see your pages, just as you could with your secure site on OAK.
For the details of restricting access to your files, see http://www.ohio.edu/oit/webservices/people/accesscontrolsteps.cfm.
If you want to authorize one or more other people to update your personal web presence (e.g., teaching assistants working with a professor's online instructional materials), please do not tell them your password! Instead, let us know the details: we have configured the people2 server so that we can readily add and remove assistant pagemasters for each person's subsite.
For the details of authorizing assistant pagemasters, see http://www.ohio.edu/oit/webservices/people/.