| Main -> Support Zone -> InSite Archives -> May 1997 Issue |
Issue # 2 May 7, 1997 Contents
InSite is intended to create discussion about the use and implementation of Open SiteSearch software and explore the technology used by its components. The newsletter will be distributed to the SiteSearch list on a regular basis and is designed as an informational resource for SiteSearch system administrators. It is brought to you by the SiteSearch support team. Any suggestions or comments are appreciated. Top StorySetting up a development environment for release 3.1Since the distribution of release 3.1, we have received several questions regarding the setup and use of a development environment. Creating a development area is beneficial for testing new features, customizing the software tools, and troubleshooting problems. It is important to remember that this installation will be completely independent of your production environment, in a different directory, and making use of different ports. General steps to follow:
To keep current with the most recent release, we recommend that you use the new executables in your production SiteSearch environment even if you are not yet planning to implement the new features. Upgrade your executables when your production system is not running by following these steps:
If you have not received your Release 3.1 Software Package, please contact SiteSearch Support (). [return to menu][return to top] FAQsUsing the profile serverIn each issue of InSite, we will highlight some questions frequently asked of the support team. As a reminder, be sure to send all SiteSearch problem reports to for tracking and assignment. Q: I am using IP authorization together with autho/password access control via the profile server. Can I grant direct access to SiteSearch with a valid IP address thus avoiding the autho/password page? A: When the IP authorization is valid, you can grant automatic access with seamless autho/password entry by adding an entry to your profile database that identifies the ip address and adds a valid autho/password that can be sent through at time of login. Note: the autho and password should have their own entries in the database. For example: ip:aut=xxx.xxx.xxx.xxx,autho=automatic1,password=autopassword - in pro_labels.ini in the [httpgate] section, add: var<n>=autho Q: What is the purpose and how do I use the optional variable, utyp=, in the pro_labels.ini file? A: Variable names mentioned in the [Common] section of pro_labels.ini (including "utyp") become available to an httpgate process as an entity with the same name. For example, you could add these lines to an HTML page to display what type of authorization the user had: <STRONG>User Classification: &utpy;</STRONG> This allows information about the user to be available to the httpgate process, by simply adding variable names to the [Common] section, and then assigning values to these variables in their profile entry. This can be especially useful when using CGI scripts to access external authorization servers. [return to menu][return to top] Tips & TechniquesSetting up a virtual catalog of 2 local databasesThe setup of a virtual catalog containing 2 or more local SiteSearch databases requires additional configuration. This is required because only one irpserv process is started when the virtual catalog is searched, and to maintain individual server results, two irpservs must be started. The following changes will start up two irpservs when you perform a search of this virtual catalog. To do this, you will have to 'hardcode' a server_port for irpserv. Next, add server sections for 'irpserv' and 'irpserv2' and point your database ini files toward these server names. Sample changes: From irpserv.ini:
[IRPSERV]
application_name=irpserv
exec=./irpserv
ini=irpserv.ini
#server_port=0
server_port=2100 (you can use a different port number if
you wish)
....
From httpgate.ini: ....
# z3950 server application name
DefaultZ39Server=irpserv
....
# define any external Z39.50 servers
#
[irpserv]
hostname=localhost
port=2100
[irpserv2]
hostname=localhost
port=2100
....
[ABCD]
name=ABCD
LongName=ABCD Database
ServerName=irpserv
inifile=db_ini/ABCD.ini
....
[EFGH]
name=EFGH
LongName=EFGH Database
ServerName=irpserv2
inifile=db_ini/EFGH.ini
....
From your ini files in /db_ini:
[ABCD]
name=ABCD
LongName=ABCD Database
ServerName=irpserv
....
- From EFGH.ini:
[EFGH]
name=EFGH
LongName=EFGH Database
ServerName=irpserv2
....
[return to menu][return to top] Web Sites of InterestSiteSearch information and Z39.50 resourcesSiteSearch Support page: SiteSearch Online Problem Report: InSite Archive: Z39.50 Resources:
Z39.50 Documentation: "Z39.50 Maintenance Agency Official Text for Z39.50-1995" is available via ftp from the directory /pub/z3950/official. The four parts are available in PDF, ASCII, PostScript, and WordPerfect. "Z39.50 in a Nutshell : An Introduction to Z39.50" by John A. Kunze and R.P.C. Rodgers. "The Z39.50 Protocol in Plain English" by Clifford A. Lynch. "An Overview of the Z39.50 Information Retrieval Standard" by Fay Turner. [return to menu][return to top] Software Fixes for Release 3.1Bookmarking and stats_for_gate.fcl
[return to menu][return to top] SiteSearch Training Class Schedule
Note: Training class schedules are subject to change. For more information or to register for upcoming classes, please contact . Questions or comments regarding InSite should be sent to with 'InSite' in the subject line., |
| [Main][Documentation][Support][Technical Reference][Glossary][Search] |