Sun Server Setup for Unicorn
Operating System requirements
Install the new Solaris operating system if necessary. Install any patches that are required, and make any security configuration changes that you deem necessary.
Set Solaris kernel parameters as follows:
forceload: sys/msgsys
set msgsys:msginfo_msgmax=8192
set msgsys:msginfo_msgmnb=65535
set msgsys:msginfo_msgmni=2000
set msgsys:msginfo_msgtql=8000
set rlim_fd_cur=5120
****For Oracle *****
set shmsys:shminfo_shmmax=4294967295
set shmsys:shminfo_shmmin=100
set shmsys:shminfo_shmmni=2000
set shmsys:shminfo_shmseg=400
set semsys:seminfo_semmni=2000
set semsys:seminfo_semmns=2500
set semsys:seminfo_semmsl=2000
set semsys:seminfo_semopm=2500
Create the Unicorn filesystem using the same path structure as on the old server. For example, if the old system used /s/sirsi, create the same /s filesystem on the new server. The path must remain the same because there are files within Unicorn which are path specific. Make sure that the Unicorn filesystem is large enough to hold the catalog and allow for future expansion.
*Note for Rutgers: Since the test system will be housed temporarily on the new server, create a partition as you mentioned, something like s1_test. When those files are brought over from the current test server, I’ll just edit the path files accordingly. At this time you can also create s1-s4 for the production server.
User accounts
Create a "sirsi" account. The home directory should be the same as the old server (example: /s/sirsi). The shell is /bin/ksh.
*Note for Rutgers: If s1_test will be the only partition for now, make that the sirsi home directory. It can always be changed to s1 (or whatever it is currently on the production server) later on. Both the test and production instances can reside on the same server without using zones. The production server will be setup as the default instance, the way it is now. For the test server, we’ll use a set file to switch to that environment.
BRS files
The following files need to be present in /usr/lib: brssearch and brsvalid. Copy or ftp the brs files from the old system to the new one, or just cut and paste the contents. Make sure that the permissions (rw-r-r) and ownership (sirsi and correct group) are set. For a system using /s/sirsi as its Unicorn directory, the brsvalid and brssearch files will each contain the same line:
/s/sirsi/Unicorn/Config/brspath
*Note for Rutgers: As long as the permissions are set, I can edit these files to include the paths to both Unicorn instances.
Perl
Transfer the Perl directory from the sirsi home directory on the old server. Under /usr/local, duplicate the sirsi directory, the links within, and ownerships located under /usr/local on the old server. After the Unicorn directory has been transferred, test Perl by running “perl –v” and then “perl –V”. At the end of the perl –V output, the “Characteristics of this binary” section should point to /usr/local/sirsi.
*Note for Rutgers: Since both the test and production systems are at the same level of Unicorn and Perl, these links only need to point to one Perl/Unicorn location, whether it’s the test system or the production system. Since the production system will be permanent, it may be easier to just point them to that location if those partitions will be present. In that case, you’d only need a copy of the Perl directory, and an empty Unicorn directory with an empty Bin directory underneath. I can then copy perl* from Perl/bin to Unicorn/Bin.
Web server configuration
If you're using Apache, the httpd.conf file will need to contain an additional entry for ScriptAlias:
ScriptAlias /uhtbin/ "/var/apache/cgi-bin/" (or whatever the path to cgi-bin is).
If the web catalog uses any perl or cgi scripting, make any necessary configuration changes in httpd.conf to allow this.
1