[Openroad-users] OpenROAD Server on Linux
Bodo Bergmann
Bodo.Bergmann at ingres.com
Wed May 30 19:24:29 EST 2007
DCOM on Linux (as on other supported Unix systems)
is handled by the MainWin System Core (MSC) software
(supplied as part of the OpenROAD installation).
"dcomcnfg" is used to configure it (as on Windows).
You can run VASA on the Linux box itself, so you don't have to connect
"unauthenticated".
In addition to the "unauthenticated" connection, you can also use
authentication.
For this purpose a Windows service "remotesa" is provided as part of the
MainWin installation
that needs to be installed on the primary domain controller for the
domain where authentication is used.
Its function is to provide authentication services for the Unix servers
that
are using the Visual MainWin DCOM.
The remotesa provides these authentication services by delegating them
to the Windows domain controller.
Bodo.
Bodo Bergmann
Senior Software Engineer
OpenROAD Worldwide Development
Ingres Corp.
________________________________
From: openroad-users-bounces at peerlessit.com
[mailto:openroad-users-bounces at peerlessit.com] On Behalf Of Pete
Rabjohns
Sent: Wednesday, May 30, 2007 1:07 AM
To: International OpenROAD Users
Subject: Re: [Openroad-users] OpenROAD Server on Linux
Thanks Neil,
No problems yet, I just wondered what handled the DCOM interface and how
you configured it.
I knew it was 'supposed' to work, but I wondered how and whether anybody
was using it in anger - just in case someone asked me the question.
Pete
________________________________
From: openroad-users-bounces at peerlessit.com
[mailto:openroad-users-bounces at peerlessit.com] On Behalf Of
Neil.Warnock at luminary.co.uk
Sent: 29 May 2007 17:22
To: openroad-users at peerlessit.com
Subject: Re: [Openroad-users] OpenROAD Server on Linux
Any specific problems, Pete? 4GL code is identical & VASA setup etc
pretty much the same. Need to put "unauthenticated" in the routing field
of the ASO config screen so that windows clients calling in don't go
through windows authentication. Other than that it's pretty straight
forwards (famous last words!). Simple test is to use appserver client
DOS command:
comtestrso \\machinename <file:///\\machinename> "unauthenticated"
from the remote client (and comtestaso/comtestspo from the server
machine if no joy)
Warning - a common gotcha that means you won't make it to first base is
getting VASA (on windows) to connect to the Linux AppServer machine.
VASA is an AppServer client so, guess what, it needs to connect
"unauthenticated" too (!)
If you come unstuck give me a shout. Be prepared to see a lot of
processes under Linux compared to unix. The way Linux does
'multithreading' involves starting up new processes for each thread (I
think taht's what happens anyway) so you get shedloads of processes in a
real production environment.
Neil Warnock
Luminary Solutions
Tel: +44 (0)845 371 4090
Mob: +44 (0)771 265 0291
Email: Neil.Warnock at luminary.co.uk
For more information on Luminary go to http://www.luminary.co.uk
<http://www.luminary.co.uk/>
Luminary Solutions Limited Registered in England No 4854134 VAT Reg No.
829 3166 13
Registered Office: 16/17 Pavilion Business Park, Royds Hall Road, Leeds
LS12 6AJ
________________________________
From: openroad-users-bounces at peerlessit.com
[mailto:openroad-users-bounces at peerlessit.com] On Behalf Of Pete
Rabjohns
Sent: 29 May 2007 16:26
To: International OpenROAD Users
Subject: [Openroad-users] OpenROAD Server on Linux
Hi,
Just wondered what the differences in calling mechanism were if you run
you're OpenROAD Server on a Linux platform.
Has anyone done this that can give me a few tips on what's involved?
Thanks
Pete
Pete Rabjohns
Technical Manager
Atex
Email: pete.rabjohns at atex.com <mailto:pete.rabjohns at atex.com>
Web: http://www.atex.com <http://www.atex.com/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.peerlessit.com/pipermail/openroad-users/attachments/20070530/2578f185/attachment.html
More information about the Openroad-users
mailing list