Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
Database Servers
DB2InformixIngresMS SQLOraclePervasive.SQLPostgreSQLProgressSybase
Desktop Databases
FileMakerFoxProMS AccessParadox
General
General DB TopicsDatabase Theory
Related Topics
Java Development.NET DevelopmentVB DevelopmentMore Topics ...

Database Forum / Informix Topics / November 2005

Tip: Looking for answers? Try searching our database.

Re: Connecting (IConnect) Solaris machine to a Linux server

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Martin Fuerderer - 24 Nov 2005 15:25 GMT
Ciao,

explanation by example:

scenario:
machine A (Solaris), IDS server name A1
machine B (Linux), IDS server name B1

Configuration machine A:

 onconfig file:
 ...
 SERVERNAME A1
 ...

 sqlhosts file:
 A1  ontlitcp  A  portA
 B1  ontlitcp  B  portB

 /etc/services file:
 ...
 portA    87341/tcp
 portB    87342/tcp

 ~informix/.rhosts file (.rhosts file of user informix):
 ...
 B  informix  # short host name
 B.domain...   informix  # long hostname

Configuration machine B:

 onconfig file:
 ...
 SERVERNAME  B1
 ...

 sqlhosts file:
 A1  onsoctcp  A  portA
 B1  onsoctcp  B  portB

 /etc/services file:
 ...
 portA    87341/tcp
 portB    87342/tcp

 ~informix/.rhosts file (.rhosts file of user informix):
 ...
 A  informix  # short host name
 A.domain...   informix  # long hostname

With this you should be able to connect from
IDS server A1 on machine A to IDS server B1 on
machine B and vice versa.

Note:
 - no changes are needed to the environments
   (environment variable seetings) on the machines.
 - rlogin is not used by IDS itself. But it can be used
   to test connectivity between machines, i.e. that
   login without password is working.
 - remote login without password for user
   informix is achieved by the entries in respective
   .rhosts files.
 - this remote connectivity without password (trusted
   user) is necessary for IDS remote queries to work.
 - for other users to be able to do remote queries
   I think you also have to do these entries.
   Alternatively you can use the mechanism of
   /etc/hosts.equiv (trusted hosts) for whole machines.
 - port numbers in /etc/services have to match. They
   are like telephone numbers ...
 - port numbers in /etc/services need to be unique,
   above I just picked arbitrary examples.

Saluti a Italia,  :)
Martin
--
Martin Fuerderer
IBM Informix Development Munich, Germany
Information Management

owner-informix-list@iiug.org wrote on 11/24/2005 12:08:45 PM:

> Hi there, I have a question for you smart guys.
>
> I have Sun Solaris 9 machine where Informix IConnect 10.0 is installed.
> The machine should make use of the database server (IDS 10.0) installed
> on a Red Hat EL4 Linux server.
>
> By default Linux does not provide 'rlogin' functionality, which is the
default
> method used by Informix to make the connectivity. Now it is installed on
my box.

> AFAIU 'sqlhosts' files are different between the two platforms (Solaris
uses
> 'oltlitcp' protocol, while Linux uses 'olsoctcp').
>
> Furthermore (but don't know if this is an issue), the default Informix
install
> directory is different on the wto platforms ('/usr/informix' for Solaris
VS
> '/opt/informix' on Linux).
>
> How should I configure the 'sqlhosts' file on the two boxes in order to
obtain
> the connectivity?
>
> Anyhing else I should take care of?
>
> Any help would be really appreciated.
>
>    Rupan3rd (Italy)
sending to informix-list
Abhishek Mathur - 24 Nov 2005 15:27 GMT
Hi,
       First of all a small clarification with the product versioning
that you have posted here. There is no Informix IConnect version 10.0 in
the market so far. The latest release of Informix IConnect was version
2.90 which was bundled with IDS 10.00 server. I hope you are talking about
the same product.

       Assuming that the above statement is true, there should really be
no problems about setting up a connection from a solaris box to an IDS
server on a Linux host. You can follow these simple steps --
- Configure the IDS server on the Linux box, and bring up the server using
the 'onsoctcp' protocol. A typical sqlhost file for IDS on Linux would
look like this -
       <servername>    <protocol>      <hostname/IP address> <port
number/service_name>
i.e.    test_10         onsoctcp        myhost 3478

       If you are using the service name option in the sqlhosts, you
would need to provide a corresponding entry in the file /etc/services on
both the host machines - the client and the server.

       Now install the Informix IConnect on the solaris machine, and
ensure that the sqlhosts typically matches the one that has been used for
the server, except of course the protocol. For any platform, the protocol
used in the sqlhosts file should be the one that the particular platform
understands. It is not necessary for the sqlhosts entry to be the same, in
terms of the protocol, for connectivity.
i.e.    test_10         ontlitcp                myhost 3478

       Make sure that all the applications that are going to be running
using the libraries from IConnect use this sqlhosts on the solaris box.
This should work perfectly and you should not be facing any issues at all.
The default installation location for the two products should not be a
cause of concern for you. Just so that you know - these default
installation locations can be changed and point to a more customized
location.

       Hope this helps.

Thanks and Regards,
Abhi

Rupan3rd <rupan.nospam.3rd@hotmail.com>
Sent by: owner-informix-list@iiug.org
11/24/2005 05:14 AM
Please respond to
Rupan3rd <rupan.nospam.3rd@hotmail.com>

To
informix-list@iiug.org
cc

Subject
Connecting (IConnect) Solaris machine to a Linux server hosting IDS

Hi there, I have a question for you smart guys.

I have Sun Solaris 9 machine where Informix IConnect 10.0 is installed.
The machine should make use of the database server (IDS 10.0) installed
on a Red Hat EL4 Linux server.

By default Linux does not provide 'rlogin' functionality, which is the
default
method used by Informix to make the connectivity. Now it is installed on
my box.

AFAIU 'sqlhosts' files are different between the two platforms (Solaris
uses
'oltlitcp' protocol, while Linux uses 'olsoctcp').

Furthermore (but don't know if this is an issue), the default Informix
install
directory is different on the wto platforms ('/usr/informix' for Solaris
VS
'/opt/informix' on Linux).

How should I configure the 'sqlhosts' file on the two boxes in order to
obtain
the connectivity?

Anyhing else I should take care of?

Any help would be really appreciated.

  Rupan3rd (Italy)
sending to informix-list
Jonathan Leffler - 30 Nov 2005 07:53 GMT
On 11/29/05, Art S. Kagel <kagel@bloomberg.net> wrote:
> Rupan3rd wrote:
> > Hi there, I have a question for you smart guys.
[quoted text clipped - 10 lines]
> Not to worry, the underlying rcmd() interface is included in the Linux
> libraries which is all that Informix requires.  This works so...

I am under the illusion that IDS does not use the rcmd() interface -
whatever that is - and in fact does not require the r-commands
installed on the machine to operate, unless you are doing ontape
archives to a remote device.  The communications between client and
server or between server and server use the r-commands configuration
files but that's all.  The rest is in IDS.

Do you have any evidence that the r-commands actually must be
installed for IDS to work?

> > AFAIU 'sqlhosts' files are different between the two platforms (Solaris
> > uses
[quoted text clipped - 21 lines]
>
> Nope.

--
Jonathan Leffler                   #include <disclaimer.h>
Email: jleffler@earthlink.net, jleffler@us.ibm.com
Guardian of DBD::Informix v2005.02 -- http://dbi.perl.org/
sending to informix-list
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.