Temporarily disabling X-server

Last updated
Save as PDF
Share
1. Share
2. Tweet
3. Share

Article Type: General
Product: Aleph
Product Version: 18.01

Description:
We're planning a failover test next week and want to prevent any transactions being written to the database during this period. We will be running the web OPAC with logins disabled so that patrons can search, but not place holds or renew items. However, we have a student portal that communicates with the www-server via the X-server. We need to be sure that it can't send any transactions. What is the easiest way to block X-server transactions during this period?

Resolution:
The v18 util w/5 "View/Update Global System status" function has the ability to disable particular ue processes and particular pc_server modules, but the www_server (of which the x_server is a part) is either all enabled or all disabled.

There are two ways we can think of handling this:

1. Disable the Aleph staff users (usually just "WWW-X") who have X-server update privileges. Or

2. Disable the www_x program:

> ae (to go to the ./aleph/exe/ directory)
> mv www_x.gnt www_x.gnt.tempdisabled

Restart the www_server to make the change take effect.

When an x-server transaction is attempted, it will fail with a "Program not found" message in the www_server log.

When you are done you can restore the file:

> mv www_x.gnt.tempdisabled www_x.gnt

Restart the www_server to make the change take effect.

Article last edited: 10/8/2013