EsiObjects Installation for GT.M

[Terry]

I'm moving the installation discussion from the Slipstream discussion
group to EsiObjects since key EsiObjects people are not on the
Slipstream discussion group. I cut the thread from the Slipstream ins
pasted it below for reference.

I have some questions regarding where to actually put EsiObjects.
Currently it hardwired into /usr/local/esiobjects. Since EsiObjects is
really just routines and globals stored in ./source and ./data
respectively, why can't I just drop them into $gtm_dist/esiobjects
(along with relevant scripts)? What are the objections to this? Keep
in mind that we are pushing EO as OO extensions to GT.M.

Terry
-------------

Terry,

As per Bhaskar's April 14th posting on the fis-gtm developer list on
SourceForge:

"To install GT.M versions in compliance with lanana.org standards,
please
install in /opt/lsb-gtm/<ver>_<platform> e.g., /opt/lsb-gtm/
V5.3-003_i686"

To get the xinetd-based server working I also had to edit
/usr/local/esiobjects/xinetd_startup

This file made two references to the GT.M install directory, both hard-
coded
to /usr/local/gtm rather than using the path I typed in when prompted
by
your installer.

I think you can reduce it to one reference by changing the
gtmroutines= line
to specify $gtm_dist instead.

Your install script doesn't seem to do anything with the path it gets
from
the user, other than verifying that a file named 'mumps' exists there.
Maybe
you should output it to a file in /usr/local/esiobjects that just sets
up
gtm_dist. Then your xinetd_startup and esiobjects scripts can use that
file
to set up their gtm_dist environment variable.

I suggest you note in the doc that /etc/xinetd.d/esiobjects starts the
server processes as 'root', and the security-conscious might want to
adjust
this.

Regards,

John

> > -----Original Message-----
> > From: outofthes...@googlegroups.com
> > [mailto:outofthes...@googlegroups.com] On Behalf Of
> > Terry L. Wiechmann
> > Sent: 03 July 2009 01:20
> > To: outofthes...@googlegroups.com
> > Cc: nanth...@verizon.net
> > Subject: [Slipstream] Re: Announcing the new EsiObjects
> > V4.2.0.9 RC2 relea se...
> >
> >
> > Thanks John:
> >
> > 1. Welcome to the Linux Tower of Babel - the hardest part of is
> > trying to find a common path for all the Linux
> > implementation that
> > have evolved. Ubuntu uses 'sudo', others use 'su'... now I know
> > why the creators of MUMPS buried the OS - I think they call it
> > "hiding the complexity"
> > 2. Two things
> > * First, gtm.sh was in the original kit and got
> > transfered. I
> > have no idea why it was in the original kit. I
> > will resolve it.
> > * I assumed (wrongly obviously) that /usr/local/gtm was the
> > default. However, the installers are putting GT.M in
> > opt/lsb-gtm (inconsistently). Bhaskar - is there
> > a default?
> >
> > Terry L. Wiechmann
> > 978-779-0257
> > http://www.esitechnology.com
> >
> >
> >
> > John Murray wrote:
>> > > Terry,
>> > >
>> > > I just tried the installer, once I worked out how to navigate the
>> > > repository. I was testing on a fresh CentOS 5.3 install. A
> > couple of
>> > > observations so far:
>> > >
>> > > 1. readme_GTM_Linux.txt says 'use the "sudo" command to become the
>> > > super user' but perhaps means "su".
>> > >
>> > > 2. I had used Jonathan Tai's RPM installer for GT.m, downloaded rom
>> > >
> > http://launchpad.net/openvista-gtm-integration/mainline/phase1-alpha/+
>> > > downlo ad/fis-gtm-5.3003-5.3003-1.i386.rpm as per his posting at
>> > >
> > http://groups.google.com/group/Hardhats/tree/browse_frm/thread/df4a85c
>> > > fb3616
>> > >
> > 376/0251aba48685f99f?rnum=1&q=gtm+rpm&_done=%2Fgroup%2FHardhats%2Fbrow
>> > > se_frm
>> > >
> > %2Fthread%2Fdf4a85cfb3616376%2F0d78d70025bd37f4%3Flnk%3Dgst%26q%3Dgtm%
>> > > 2Brpm%
>> > > 26#doc_0d78d70025bd37f4 which put GT.M into
>> > > /opt/lsb-gtm/V5.3-003_i686/ so I told your installer this
> > and it was
>> > > happy. But it seems you put a file called gtm.sh into
> > /etc/profile.d
>> > > which defines gtm_dist="/usr/local/gtm", and this file also defines
>> > > gtm_log="/var/logs" but my fresh install doesn't have this
> > (it does have /var/log).
>> > >
>> > > I hope this is useful. I'll let you know if I find more issues.
>> > >
>> > > John

[Terry]

OK, bad suggestion. Jerry needs to apply for a LSB Package Name 'lsb-
esiobjects' (and LSB Provider Name?) (www.lanana.org) and put it
under /opt/lsb-esiobjects/<version>. If there are any objections,
raise them now because I'm going to modify the install to do this.

Terry

[K.S. Bhaskar]

Terry --

It would be good to look at the Filesystem Hierarchy Standard
(http://www.pathname.com/fhs/) which the Linux Standard Base adopts (see

http://refspecs.linux-foundation.org/LSB_3.2.0/LSB-Core-generic/LSB-Core-generic/execenvfhs.html).
Note that /opt is where optional add-on software packages such as
EsiObjects, GT.M and VistA belong. However, /opt should be used for
files that are part of the package distribution, and variable files
should go under /var/opt. It may seem complicated at first, but there
is a certain logic to it, and once you internalize the logic, everything
falls into place.

If you look at how I have installed VistA in the Four slice Toaster, the
invariant files go in /opt/WorldVistAEHR/VOE10, but the "variable"
files for Clinic P, an individual clinic, go in
/var/opt/WorldVistAEHR/VOE10/clinicp.

To that end, it would be good to differentiate the installation of
EsiObjects, which is common to all on the system, from specific
instances (such as a Clinic) that use EsiObjects and of which there can
be many.

Regards
-- Bhaskar

[Terry]

I have a little problem that maybe someone can give me guidance on.
I'm learning bash so don't laugh too loudly :-)

I have a file named esiobjects.sh (listed below) that resides in the /
etc/profile.d directory so that it will execute when someone logs in.
The /opt/lsb-esiobjects/dist.sh file sets the esiobjects_dist variable
and the two variables are created and exported properly. However, the
alias does not create the esiobjects command. This worked on RH but
not Ubuntu 9.04. What am I missing here?

# .bashrc
# EsiObjects Variable Set Script
# Copyright (c) Stormwoods LLC, Eugene, OR
#

. /opt/lsb-esiobjects/dist.sh

alias esiobjects="$esiobjects_dist/esiobjects"

export EsiObjects_Source=$esiobjects_dist/user

export esiobjectsdir=$esiobjects_dist

On Jul 4, 11:57 am, Terry <tlwiechm...@esitechnology.com> wrote: