• Article Type: General
• Product: Aleph
• Product Version: 18.01

Description:
We would like to use a single PDS shared by Aleph 18 and Metalib 4, both systems are installed on dedicated Linux servers. Getting Aleph to connect to the Metalib PDS is not the problem. However, the PDS loginscreens do not lead back to Aleph after logging in.

Is there anyone who has done this succesfully and would be willing to share information?

Resolution:
We have this working (though between Aleph 18 and Primo). There are a number of factors.

For Aleph these two configurations seem to be most relevant (but there is more):

1) You need a line like this in ../alephe/www_server.conf:
setenv pds_backlink " http://${WWW_HOST}:${HTTPD_PORT}/F/&session"

2) some www_f pages (e.g., head-1-nobor-pds copied to

head-1-nobor-ill-02-pds
for us, since we use Aleph ILL), need to have the lines customized, e.g.:
href="&server_pds?func=load-login&calling_system=aleph&institute=USM50&url=&pds_backlink?func="

We have the &institute value set at UMN50 (we are a single ADM site) - see rep_change 1591 for details on this.

From the PDS side of things, here is our tab_service, called tab_service.umn50 (we use the remote cgi method against a central campus directory):

[INSTITUTE_DISPLAY]
code = UMN50
desc = U of M MNCAT Your Account UMN50
lang = ENG
aleph = UMN50
[END]

[LOAD_LOGIN]
program = remote_load_login.pl
params = load-login-aleph
[END]

[REMOTE_LOGIN]
program = remote_login_gen_1.pl
params =
[END]

[BOR_VERIFICATION]
program = get_pds_verification.pl
params =
[END]

[AUTHENTICATE]
program = remote_cgi_hook.pl
params = GET,www.xxx.umn.edu:443,pdsauthtesting/bor-auth-db.phtml
[END]

[BOR_INFO]
program = remote_cgi_hook.pl
params = GET,www.xxx.umn.edu:443,pdsauthtesting/bor-auth-db.phtml,BOR_ID
[END]

• Article last edited: 10/8/2013