|
|||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||
This MacOS X Installer package allows installation and start up of the servers without using the command line and Terminal.app. [0] SystemPreferences > Sharing, and turn off "Personal Web Sharing" (Turn off the check mark.) This package will install and use a completely different Apache web server, which will conflict with the factory-installed Apache used for "Personal Web Sharing". [1] Download the Installer [2] Install the package Double-click on PMpdf-XAMPP-Wiki-Mac-E#.##.pkg and follow the instructions. [3] Start upp XAMPP
on the Dock or double click on it directly. Script Editor will start up. Press the "Run" button. You will be asked for administrator password via a panel, because it is necessary to start the severs as root. Wait briefly for successful startup message to be displayed in the lower part of the window. Then, you can quit Script Editor.If you feel comfortable with command line, you may alternatively start XAMPP up by:
If you got the startup messages, verify the operation
by accessing:
After the XAMPP servers (Apache and MySQL has been
started as above, the user may log out. The server
processes will continue to run in the background.
A new user may login and use the Mac normally without
even being aware that these servers are running.
Remember to disable Sleep timeouts via SystemPreferences >
Energy Saver, since the server machine should be awake.
One more note: If your LAN is connected to the global Internet via a HTTP Proxy, you need to set up PubMedPDF XOOPS module to use the proxy. Login as XOOPS administrator and open the configuration for PubMedPDF from Administrative menu. If your LAN is using NAT/DHCP which is typical these days, then don't worry about this. Items below should not necessarily be done in numerical order. This is just an itemized list.
[4] Stopping XAMPP Place
on the Dock or double click on it directly.
Script Editor will start up. Press the "Run" button.
You will be asked for administrator password via a
pannel, because you need to be root to terminate the
servers. Wait briefly for successful stop message
to be displayed in the lower part of the window.
Then, you can quit Script Editor.
[5] Accessing from other computers on a LAN XAMPP/XOOPS/PukiWiki package allows you to run the servers immediately. There is no need to change configurations, if you just need to use the system on the machine itself. After verifications that servers are running on the local machine, you will need to make the following change to the XOOPS component, if you wish to access the server from other computers on the LAN. Open the file:
using a text editor such as TextEdit.app and change the setting for "XOOPS Virtual Path (URL)" as follows:
In the above line, IP address "192.168.0.69" is just an example. Actual numbers are different for each installation. The IP address may be obtained by opening SystemPreferences > Network and make a note of the IP address assigned to the "Built-in Ethernet". Use that IP address for the modification of file, mainfile.php. To access the Lab Portal server from other computers on the LAN, you should use the URL of the form below, with the IP number for your own server from the Network SystemPreferences panel as shown above. If there is a DNS (Domain Name Service) server for the LAN, of course, it is possible to use that hostname instead of the numeric URL.
Caution: If you have enabled the built-in Firewall (available in SystemPreferences > Sharing > Firewall), you have to put a NEW entry for passing TCP port 80. This is because we are not using the Apache web server that is built into MacOS X, and the default Apache firewall setting (uneditable anyway) will not be active. If you do not do this, none of the ohter machines, local LAN or WAN, will not be able to reache the server. [6] Security [7] XOOPS (eXtensible Object Oriented Portal System)
XOOPS is configured such that a new user account may be created immediately without administrator review or mail confirmation. Of course, these settings may be changed by logging into XOOPS as administrator. [8] PukiWiki [9] MySQL related account and passwords (You will need these if you want to tighten security or change MySQL configuration.)
Synching iPapers and PubMedPDF/XOOPS iPapers works like iTunes for managing journal paper reprints. It is able to search the PDF reprint collection by keyword or authors, year range, etc. "Favarites" folders may be created and used just like "Playlists" in iTunes. It is also similar to iTunes in that you do not use a web browser at all for searching articles and downloading the PDF files. iPapers searches the PubMed site, and via links to specific articles, it will download the desired PDF reprint, names the file with its PubMedID automatically, and add it to the library. The end result for us is that we can forget about nameing downloaded PDF files. Download the latest version of iPapers from: http://homepage.mac.com/toshihiro_aoyama/iPapers/download.html By following steps explained here, PubMedPDF/XOOPS database also benefit from the above features of iPapers: we don't have to worry about PubMedID-based file names for PDF reprints. iPapers Setup (a) iPapers: SystemPreferences > General Set the "iPapers Article Folder Location" as follows:
(b)For importing new papers registered on PubMedPDF/XOOPS, do from iPapers menu:
(c) Login on XOOPS as an administrator. Click on the menu item "PubMedPDF". This will open submenus for PubMedPDF. Click on "Reg. with PMID". The third item on the page that appears is "Automatic registraion" Press the "submit" button there. That's it. Since the PDF folder for PubMedPDF and iPapers' article folder are shared, papers downloaded by iPapers are registered without copying any PDF files. (d)Further automating "Automatic registraion" Wrap the following one line (folded for this documention) in a shell script, and run the script via "cron" or the new "launchd" periodically (e.g., twice a day).
This is Unix stuff. Ask your local Unix expert for setting this up for you. man crontab (for all versions of MacOS X) In this way, if you use iPapers on the same machine,
all papers downloaded by iPapers will automagically appear
in PubMedPDF without anyone touching anything.
The following is a memo. Normally, you do not need to read further. Procedures and notes about installing XAMPP/XOOPS/PubMedPDF/PukiWiki from individual distributions.
[1] XAMPP for MacOS X Go to: http://www.apachefriends.org/en/xampp-macosx.html Unpack the above file by double-clicking on it. Then, xampp-macosx-0.4.pkg will be created. Double-clicking on the .pkg file will open it in Installer. Proceed as directed, and you will be asked to authenticate. Apache, PHP, Perl, MySQL etc. will be installed into /Application/xampp # Part of the following information is from Dr. Ikeno.
(b) Make XAMPP use PHP4
(c) Start XAMPP
[2] XOOPS (eXtensible Object Oriented Portal System)
Change the owner to nobody for newly copied files:
While consulting http://pcweb.mycom.co.jp/column/yetanother/006/
Using a web browser, access: http://localhost/xoops/ set up XOOPS. If necessary, edit
manually using a text editor. [3] Installation of PubMedPDF
Change the owner to nobody for newly copied files:
[4] PukiWiki Install the folder as:
Edit using a text editor:
and change the top page title etc. Change the lock/unlock password to: vision Change the owner to nobody for newly copied files:
Acknowledgement: The main unique content of this package, PubMedPDF module for XOOPS, has been developed by the group led by Prof. Hidetoshi Ikeno at University of Hyogo, inspired by features and scripts developed for Visiome Platform. Please see the PubMedPDF module developer site indicated above for details. We are also very much thankful for the dedicated developers of XAMPP (Apache, Perl, PHP, MySQL), XOOPS, PukiWiki and other components contained in this package. No Warranty: There is absolutely no warranty
for this software package. All the components come from other
sources, and we are merely providing the package with a belief
that it may be useful. However, we do not warrant that it will
do anything useful or it will function at all in any desired manner. Any
responsibility for damages or liabilities resulting from the use
of this package is entirely upon the user. Use it at your own risk.
|
|||||||||||||||||||||||||||||||||||||||||||||||||
| © Copyright 2004-2005 Ohzawa Lab. All Rights Reserved. | |||||||||||||||||||||||||||||||||||||||||||||||||