• Product: Aleph
• Product Version: 20, 21, 22, 23
• Relevant for Installation Type: Dedicated-Direct, Direct, Local, Total Care

Problem Symptoms:
Although the variable $http_proxy is set correctly in the file $alephe_root/pc_server_defaults on server nnn the procedure adam-05 fails when called from the Aleph GUI.

Cause:

Configuration:  Setting the variable $http_proxy in the file pc_server_defaults makes the Aleph PC server processes aware of the HTTP proxy at URL http://vproxy.dpma.de:80 [example]. 
However, the PC server does not execute the procedure p_adam_05 in a child process therefore does not inherit the variable $http_proxy to that process.
Instead the PC server schedules the procedure p_adam_05 on the batch queue of the relevant Aleph BIB Library.
The background process lib_batch reads its environment variables from the file aleph_start.
If the variable $http_proxy is not specified in the file aleph_start, then the procedure p_adam_05 will subsequently not be aware of an existing HTTP proxy.

Resolution:
The UNIX environment variable $http_proxy needs to be introduced in Aleph and added to the file $alephe_root/aleph_start (as a setenv).
 

• Article last edited: 26-Jun-2016