Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 4 of 4 total
Thread Accessing a second DBISAM remote server
Thu, May 29 2008 11:34 AMPermanent Link

Kyle Boatwright
I have a project and I would like to use the DBISAM server to provide remote procedures for client applications via the internet.  This application will reside in a DMZ on the
network.  I would like it to be able to connect to another DBISAM server for data and other procedures I do not want exposed in the DMZ.  This application currently has a
server component and data modules created when a remote procedure is called.  However I cannot get the session in the data module to connect to the second DBISAM server
by name or ip address.  This server is up and I can connect from a project that does not contain the server component.  It seems the server component prevents connections
other than local for the application in which it is created.  Is this the case or is there something I am missing?

Thanks,
Kyle
Thu, May 29 2008 12:07 PMPermanent Link

"Raul"
Hi Kyle,

I'm a newbie at this and hence following might be totally off.

However as i understand your application acts as a DBSIAM server.  Manual
does mention that "You cannot activate remote sessions in an application
whose TDBISAMEngine component is configured as a database server via the
EngineType property."

Raul


"Kyle Boatwright" <kkb@signalpointsolutions.com> wrote in message
news:88EE01BD-AE90-4721-A5AA-7B30D1D474AD@news.elevatesoft.com...
>I have a project and I would like to use the DBISAM server to provide
>remote procedures for client applications via the internet.  This
>application will reside in a DMZ on the
> network.  I would like it to be able to connect to another DBISAM server
> for data and other procedures I do not want exposed in the DMZ.  This
> application currently has a
> server component and data modules created when a remote procedure is
> called.  However I cannot get the session in the data module to connect to
> the second DBISAM server
> by name or ip address.  This server is up and I can connect from a project
> that does not contain the server component.  It seems the server component
> prevents connections
> other than local for the application in which it is created.  Is this the
> case or is there something I am missing?
>
> Thanks,
> Kyle
>

Thu, May 29 2008 12:16 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Kyle,

<< However I cannot get the session in the data module to connect to the
second DBISAM server by name or ip address.  This server is up and I can
connect from a project that does not contain the server component.  It seems
the server component prevents connections other than local for the
application in which it is created.  Is this the case or is there something
I am missing? >>

Unfortunately yes, this is the case.  I'll have to double-check as to the
reasoning behind this, but I believe there is a valid technical limitation
that prevents the use of a remote session in a server engine.  If not, I'll
put this on the list for DBISAM 4.27, which will probably be available
shortly after EDB 2.0 is released.

--
Tim Young
Elevate Software
www.elevatesoft.com

Thu, May 29 2008 12:17 PMPermanent Link

Kyle Boatwright
Thanks Raul, I guess I missed that (or forgot it)...


"Raul" <raul@raul.ca> wrote:

Hi Kyle,

I'm a newbie at this and hence following might be totally off.

However as i understand your application acts as a DBSIAM server.  Manual
does mention that "You cannot activate remote sessions in an application
whose TDBISAMEngine component is configured as a database server via the
EngineType property."

Raul


"Kyle Boatwright" <kkb@signalpointsolutions.com> wrote in message
news:88EE01BD-AE90-4721-A5AA-7B30D1D474AD@news.elevatesoft.com...
>I have a project and I would like to use the DBISAM server to provide
>remote procedures for client applications via the internet.  This
>application will reside in a DMZ on the
> network.  I would like it to be able to connect to another DBISAM server
> for data and other procedures I do not want exposed in the DMZ.  This
> application currently has a
> server component and data modules created when a remote procedure is
> called.  However I cannot get the session in the data module to connect to
> the second DBISAM server
> by name or ip address.  This server is up and I can connect from a project
> that does not contain the server component.  It seems the server component
> prevents connections
> other than local for the application in which it is created.  Is this the
> case or is there something I am missing?
>
> Thanks,
> Kyle
>
Image