[Info-Ingres] The never ending database name, JDBC and other stories.

[Paul Mason]

On 18/04/07, martin.bowes at ctsu.ox.ac.uk <martin.bowes at ctsu.ox.ac.uk> wrote:
>
>
> Ooh thats interesting. I always thought the Bridge Server was only to be
> used when connecting to non-Ingres databases.


It's really for when you want to bridge two networks with different
protocols. However it can be used, such as in the case I described, where
the networks are simply distinct and you've got a machine on both.

Thats a whole new manual to read!
> >
> >     I can post a guide to setting up the bridge server if anyone's
> >     interested.
> Tah!
>

OK. This is something I wrote for the customer concerned. References to r3
would apply to 2006.


Suppose we have three machines A, B and C and we want to connect from A to C
via B using the bridge server.

1) The first thing we need to do is create a vnode on B pointing to the
installation on C - call it B2C.

2) Next make sure that the bridge server is installed on B and setup.

3) On machine B, configure the bridge server via CBF. First important thing
is to set a listen address which is not in use by anything else - Net
server, JDBC, DAS if r3. For this example let's assume we choose 'BR' for
the listen address. To configure in CBF highlight the Bridge server and
choose configure then:

for 2.6 - choose 'Bridge Protocols', highlight the line for tcp_ip and make
sure it's ON and use 'EditListen' to set the listen address to BR. There
should be two lines one with nothing in the vnode box, and one with 'vnode'
in there. Highlight that line and make sure it's ON and set the listen
address to 'BR' Set the vnode with 'EditVnode' to B2C.

If there is only one line for tcp_ip - choose 'EditVnode' and enter B2C.
Next time you enter this screen you'll see an extra line with the vnode in.

for r3 - choose 'Protocols' (from the configure Bridge Server screen). There
are 2 lines for each protocol - status and port. Make sure that tcp_ip is
status ON and port (i.e. listen address) BR. Once this is done choose 'End'
to return to the previous screen and then choose 'Vnodes'. Choose 'Create'
and enter 'tcp_ip', 'BR', and 'B2C' for Protocol, Listen Address and Vnode
respectively.

4) Once you're happy that the Bridge server is configured as above then set
the Startup count to 1 and either restart ingres or start the Bridge server
with:

         ingstart -iigcb

5) On machine A create a vnode, A2B. Make sure that the listen address is
'BR' rather than the listen address for the Net server on B. Also, the
username and password needs to be valid for the installation on C not on B.

6) You should now be able to connect from A using sql A2B::mydb where mydb
is a database on C.

You can, if you wish, add more machines by point one bridge server to the
next. If B2C points to the listen address of a bridge server on C whose
vnode points to D then you can go A->B->C->D in that way.

Disclaimer: at the time I wrote this (mid-2005), I had tested this to make
sure it worked. I assume/hope Ingres 2006 works the same way as r3 in this
respect. I haven't had time to test this, just cut and paste.

-- 
Paul Mason
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.kettleriverconsulting.com/mailman/private/info-ingres/attachments/20070418/f8313d16/attachment-0001.html