Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

Jaguar CTS 3.0.1 and Connection Caches

2 posts in General Discussion (old) Last posting was on 2000-03-10 03:10:53.0Z
Brad McLeod Posted on 2000-03-10 03:06:21.0Z
Newsgroups: sybase.public.easerver
From: "Brad McLeod" <brad.mcleod@worldnet.att.net>
Subject: Jaguar CTS 3.0.1 and Connection Caches
Date: Thu, 9 Mar 2000 21:06:21 -0600
Lines: 40
X-Newsreader: Microsoft Outlook Express 4.72.3155.0
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0
NNTP-Posting-Host: 224.tulsa-01-02rs.ok.dial-access.att.net 12.74.160.224
Message-ID: <347_O9fsQ5ji$GA.111@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:26725
Article PK: 154430

We have migrated all of our EA Studio components and developed applications
to a new server and are in the process of establishing a connection cache
via an ODBC connection. Jag Mgr. cannot recognize nor 'Ping' the backend
(ASE 11.9.2). Although this worked fine on the old server, we have
partitioned the new server with 4 different mapped drives and now there
seems to be some conflict in addressing Sybase EA Studio components across a
mapped drive scenario. Here's the current configuration:

Drive C contains IIS, PowerDynamo and Sybase Central - This was done due to
a previous issue where IIS and PD couldn't recognize/talk to each other over
mapped drives:( We further found that without having Sybase Central - which
has the ASE, ASA and PD plugins installed - none would work with IIS.

Our Jaguar component was installed on our 'D' partition and initially we
could connect - read that ping - to the ASE backend through a System 11 ODBC
connection. For some strange reason, that quit working after about 24
hours. I have checked, re-checked and cross checked the CLASSPATH and PATH
variables and nothing has changed from when the initial connection was
successful. I have even gone to the extreme of uninstalling Jaguar from 'D'
and reinstalling on 'C' so that all of the Sybase components could exist
within the same partition environment. Result - No go!!

Based upon previous threads I have posted, I realize the one can expect some
unexpected results when putting various EA Studio or for that matter any
Sybase components on different partitions within the same server - IMHO ESD
and IAD should REALLY get on the same page here when it comes to product
development!! However, having said this, I am at a total loss as to why -
when every component is on the same partition, that the Jaguar ODBC
connection fails!!

Any advice would be welcome as this is an Internet application that needs to
be deployed for our client shortly and they are questioning our choice of
technology!! HELP!!

TIA

Brad McLeod
StoneHenge Partners, Inc.


Dave Wolf [Sybase] Posted on 2000-03-10 03:10:53.0Z
Newsgroups: sybase.public.easerver
From: "Dave Wolf [Sybase]" <dwolf@sybase.com>
Subject: Re: Jaguar CTS 3.0.1 and Connection Caches
Date: Thu, 9 Mar 2000 22:10:53 -0500
Lines: 61
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
NNTP-Posting-Host: vpn-eme-024.sybase.com 130.214.8.24
Message-ID: <347_$jNWU7ji$GA.74@forums.sybase.com>
References: <347_O9fsQ5ji$GA.111@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:26724
Article PK: 157710

What error do you get? What shows up in the log?

Dave Wolf
Internet Applications Division

"Brad McLeod" <brad.mcleod@worldnet.att.net> wrote in message
news:O9fsQ5ji$GA.111@forums.sybase.com...
> We have migrated all of our EA Studio components and developed
applications
> to a new server and are in the process of establishing a connection cache
> via an ODBC connection. Jag Mgr. cannot recognize nor 'Ping' the backend
> (ASE 11.9.2). Although this worked fine on the old server, we have
> partitioned the new server with 4 different mapped drives and now there
> seems to be some conflict in addressing Sybase EA Studio components across
a
> mapped drive scenario. Here's the current configuration:
>
> Drive C contains IIS, PowerDynamo and Sybase Central - This was done due
to
> a previous issue where IIS and PD couldn't recognize/talk to each other
over
> mapped drives:( We further found that without having Sybase Central -
which
> has the ASE, ASA and PD plugins installed - none would work with IIS.
>
> Our Jaguar component was installed on our 'D' partition and initially we
> could connect - read that ping - to the ASE backend through a System 11
ODBC
> connection. For some strange reason, that quit working after about 24
> hours. I have checked, re-checked and cross checked the CLASSPATH and
PATH
> variables and nothing has changed from when the initial connection was
> successful. I have even gone to the extreme of uninstalling Jaguar from
'D'
> and reinstalling on 'C' so that all of the Sybase components could exist
> within the same partition environment. Result - No go!!
>
> Based upon previous threads I have posted, I realize the one can expect
some
> unexpected results when putting various EA Studio or for that matter any
> Sybase components on different partitions within the same server - IMHO
ESD
> and IAD should REALLY get on the same page here when it comes to product
> development!! However, having said this, I am at a total loss as to
hy -
> when every component is on the same partition, that the Jaguar ODBC
> connection fails!!
>
> Any advice would be welcome as this is an Internet application that needs
to
> be deployed for our client shortly and they are questioning our choice of
> technology!! HELP!!
>
> TIA
>
> Brad McLeod
> StoneHenge Partners, Inc.
>
>