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.

Differentiating between OTA and LAN

3 posts in General Last posting was on 2008-09-11 09:08:42.0Z
Andy Creer Posted on 2008-09-08 07:39:26.0Z
Sender: 33de.48bbc140.1804289383@sybase.com
From: Andy Creer
Newsgroups: ianywhere.public.afaria.general
Subject: Differentiating between OTA and LAN
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <48c4d6ae.4b08.1681692777@sybase.com>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 8 Sep 2008 00:39:26 -0700
X-Trace: forums-1-dub 1220859566 10.22.241.41 (8 Sep 2008 00:39:26 -0700)
X-Original-Trace: 8 Sep 2008 00:39:26 -0700, 10.22.241.41
Lines: 4
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.afaria.general:138
Article PK: 298

Can Afaria differentiate between the LAN and OTA (GPRS/3G)?

In other words can it be configured to run a channel only if
the receiving device is on the LAN or vice a versa?


Frontline Newsgroups Posted on 2008-09-08 17:16:25.0Z
From: "Frontline Newsgroups" <SybaseiAnywhere@Live.com>
Newsgroups: ianywhere.public.afaria.general
References: <48c4d6ae.4b08.1681692777@sybase.com>
Subject: Re: Differentiating between OTA and LAN
Lines: 1
Organization: Sybase iAnywhere
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Newsreader: Microsoft Windows Live Mail 12.0.1606
X-MimeOLE: Produced By Microsoft MimeOLE V12.0.1606
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <48c55de9$1@forums-1-dub>
Date: 8 Sep 2008 10:16:25 -0700
X-Trace: forums-1-dub 1220894185 10.22.241.152 (8 Sep 2008 10:16:25 -0700)
X-Original-Trace: 8 Sep 2008 10:16:25 -0700, vip152.sybase.com
X-Authenticated-User: techsupp
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.afaria.general:139
Article PK: 303

Andy,

What type of Client is this for? (Win32? Windows Mobile? etc.).
Are you using Channel Schedules?

Using Channel Schedules you can differentiate between the type of network
connection is available, but this may not be granular enough to meet your
requirement of knowing the difference between a GPRS/3G connection and a LAN
connection. In general a GPRS/3G might be detected as a specific Dial-Up
connection, but you would need to test with your device/carrier.

Here is an excerpt from the Afaria Reference Manual - Platform guide about
how to set network parameters on a Channel Scheudule(p.118 - 119):

Specify network access parameters
On this page of the Schedule Wizard,
you specify how the schedule will run
based on the network parameters set for
the Clients to connect to the Server. For
example, you may have different
schedules created for Clients who
connect over the LAN, versus Clients
who connect through a Dial-up
connection.

The following connections apply:
. Dial-up: Modem, CD WAN card
. Non-Dial up: AS-USB, AS-IR, AS-Serial,
LAN, WLAN

You can select from the following options:

. Always run, no network selection required. This option runs the scheduled
task whether
or not Clients connect to the network. The XCGSTask.exe assumes that a
connection exists,
and will not check any LAN or dial-up connection settings. The Afaria Client
is invoked and
will fail if a connection is not available.

. Run if any network connection is available. This option runs the scheduled
task whether
Clients connect to the Server over the LAN or via a modem. If a connection
to the LAN or
modem exists, the Afaria Client is invoked and the channel is run and Afaria
should not
disconnect. If a connection to the LAN or modem does not exist, the Afaria
Client is not
invoked and the channel is not run and the Next Scheduled Time is updated.

. Run if a non-Dial-up connection is available. This option runs the
scheduled task only
when Clients connect via TCP/IP or other broadband options. You should
select this if you
are running large amounts of data or running time-consuming applications. If
a connection to
the LAN exists, the Afaria Client is invoked and the channel is run. If a
connection to the
LAN or modem does not exist, the Afaria Client is not invoked and the
channel is not run and
the Next Scheduled Time is updated.

. Use a specific Dial-up connection. This option runs the scheduled task if
Clients connect
via modem only over a specific phone line. For instance, if many Clients
will connect at one
time, you may want them to call on different lines so they will not tie up
the network
connections, so you would create different schedules to run using specific
modem
connections and assign the schedule to the appropriate channel.

You can select the Initiate connection if not already connected option to
enable Clients
using this Dial-up connection to connect to the Server automatically. If
connected through
the specified dial-up connection, the Afaria Client is invoked and the
channel runs and Afaria
should not disconnect. If not connected, the XCGSTask.exe initiates the
dial-up connection,
the Afaria Client is invoked, and the channel runs. Afaria should
disconnect.

If multiple connection paths are
available on a Client, to ensure that
your schedules run, ensure that the
desired connection path is the only
path available.

You can select the Wait up to n hours and n minutes for network access to
determine the
interval during which the Client should try to connect to the Server.

If you do not select the Initiate connection if not already connected
option, and you are
connected through the specified dial-up connection, the Afaria Client is
invoked, the channel
runs. Afaria should not disconnect. If you are not connected through the
specified dial-up
connection, the Afaria Client is not invoked and the channel is not run and
the Next
Scheduled Time is updated.

(Afaria Reference Manual | Platform 5.5 119
Schedules)



Thanks,
Chris

"Andy Creer" wrote in message news:48c4d6ae.4b08.1681692777@sybase.com...
> Can Afaria differentiate between the LAN and OTA (GPRS/3G)?
>
> In other words can it be configured to run a channel only if
> the receiving device is on the LAN or vice a versa?


Andy Creer Posted on 2008-09-11 09:08:42.0Z
Sender: 5b22.48c52642.1804289383@sybase.com
From: Andy Creer
Newsgroups: ianywhere.public.afaria.general
Subject: Re: Differentiating between OTA and LAN
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <48c8e01a.6bb2.1681692777@sybase.com>
References: <48c55de9$1@forums-1-dub>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 11 Sep 2008 02:08:42 -0700
X-Trace: forums-1-dub 1221124122 10.22.241.41 (11 Sep 2008 02:08:42 -0700)
X-Original-Trace: 11 Sep 2008 02:08:42 -0700, 10.22.241.41
Lines: 138
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.afaria.general:142
Article PK: 599

Hi Chris,

Thanks for that - I thought that would be the case as I had
tried the "run if a non-Dial-up connection is available"
option.

In the end I went down the route of checking if the IP
address was from the pool allocated by the PAS and if it was
stopping the channel from running.

Ta for your help.

Andy

> Andy,
>
> What type of Client is this for? (Win32? Windows Mobile?
> etc.). Are you using Channel Schedules?
>
> Using Channel Schedules you can differentiate between the
> type of network connection is available, but this may not
> be granular enough to meet your requirement of knowing
> the difference between a GPRS/3G connection and a LAN
> connection. In general a GPRS/3G might be detected as a
> specific Dial-Up connection, but you would need to test
> with your device/carrier.
>
> Here is an excerpt from the Afaria Reference Manual -
> Platform guide about how to set network parameters on a
> Channel Scheudule(p.118 - 119):
>
> Specify network access parameters
> On this page of the Schedule Wizard,
> you specify how the schedule will run
> based on the network parameters set for
> the Clients to connect to the Server. For
> example, you may have different
> schedules created for Clients who
> connect over the LAN, versus Clients
> who connect through a Dial-up
> connection.
>
> The following connections apply:
> . Dial-up: Modem, CD WAN card
> . Non-Dial up: AS-USB, AS-IR, AS-Serial,
> LAN, WLAN
>
> You can select from the following options:
>
> . Always run, no network selection required. This option
> runs the scheduled task whether
> or not Clients connect to the network. The XCGSTask.exe
> assumes that a connection exists,
> and will not check any LAN or dial-up connection settings.
> The Afaria Client is invoked and
> will fail if a connection is not available.
>
> . Run if any network connection is available. This option
> runs the scheduled task whether
> Clients connect to the Server over the LAN or via a modem.
> If a connection to the LAN or
> modem exists, the Afaria Client is invoked and the channel
> is run and Afaria should not
> disconnect. If a connection to the LAN or modem does not
> exist, the Afaria Client is not
> invoked and the channel is not run and the Next Scheduled
> Time is updated.
>
> . Run if a non-Dial-up connection is available. This
> option runs the scheduled task only
> when Clients connect via TCP/IP or other broadband
> options. You should select this if you
> are running large amounts of data or running
> time-consuming applications. If a connection to
> the LAN exists, the Afaria Client is invoked and the
> channel is run. If a connection to the
> LAN or modem does not exist, the Afaria Client is not
> invoked and the channel is not run and
> the Next Scheduled Time is updated.
>
> . Use a specific Dial-up connection. This option runs the
> scheduled task if Clients connect
> via modem only over a specific phone line. For instance,
> if many Clients will connect at one
> time, you may want them to call on different lines so they
> will not tie up the network
> connections, so you would create different schedules to
> run using specific modem
> connections and assign the schedule to the appropriate
> channel.
>
> You can select the Initiate connection if not already
> connected option to enable Clients
> using this Dial-up connection to connect to the Server
> automatically. If connected through
> the specified dial-up connection, the Afaria Client is
> invoked and the channel runs and Afaria
> should not disconnect. If not connected, the XCGSTask.exe
> initiates the dial-up connection,
> the Afaria Client is invoked, and the channel runs. Afaria
> should disconnect.
>
> If multiple connection paths are
> available on a Client, to ensure that
> your schedules run, ensure that the
> desired connection path is the only
> path available.
>
> You can select the Wait up to n hours and n minutes for
> network access to determine the
> interval during which the Client should try to connect to
> the Server.
>
> If you do not select the Initiate connection if not
> already connected option, and you are
> connected through the specified dial-up connection, the
> Afaria Client is invoked, the channel
> runs. Afaria should not disconnect. If you are not
> connected through the specified dial-up
> connection, the Afaria Client is not invoked and the
> channel is not run and the Next
> Scheduled Time is updated.
>
> (Afaria Reference Manual | Platform 5.5 119
> Schedules)
>
>
>
> Thanks,
> Chris
>
> "Andy Creer" wrote in message
> > news:48c4d6ae.4b08.1681692777@sybase.com... Can Afaria
> differentiate between the LAN and OTA (GPRS/3G)? >
> > In other words can it be configured to run a channel
> > only if the receiving device is on the LAN or vice a
> versa?
>