Windows Server

Crasch · Guest

Hi, we need to use the same component on the same server to call into
different remote environments.
We tried creating com+ 1.5 partitions, but when we change the remote
environment on one partition the changes are also applied to the other.

Is there a way to do this with his 2000 and/or 2004?

Thanks
Carlo Folini

Aaron Grady [MSFT] · Guest

Carlo-

The way to do this is programmtically. In HIS 2000 there is a SelectionHint
method you can call to change the RE used at runtime. In HIS 2004 there is
an REOverride property in the Client Context object that you can use to do
this. In fact, I believe that you will also be able to use the Client
Context object in HIS 2000 when SP2 is available (this is in Beta now). For
either of these methods I would recommend you peruse the documentation, but
if you get stuck or have a specific question, please just post.

HTH,
--
Aaron Grady
MCSE + Internet, MCDBA, MCSD
SNA Server/Host Integration Server 2000
Microsoft

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of any included samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

"Crasch" <carlo.folini@gmail.com> wrote in message
news:1107963214.921653.29820@o13g2000cwo.googlegroups.com...

Rob Beardsworth [MSFT] · Guest

Hi Carlo,
I'm a little confused as to what "change the remote environment on one
partition" is supposed to mean. As far as COMTI is concerned there is only
one definition for an object, and only one RE can be associated with it in
the Manager.

However, you can use SelectionHint (2000) or the ClientContext (HIS
2000 SP1 + a DCR or HIS 2000 SP2, HIS 2004) to re-route particular calls to
a different RE (of the same RE Type, so you can't move e.g. from a CICS TCP
RE to an IMS OTMA RE).

Are you trying to do this for load balancing, or can the client software
make the decision at each call and inform the server which RE to use? If
you are trying to do this for load balancing, there is a little hope: If
you are using TCP and all of the host code is on the same IP Address, you
can assign multiple ports to the RE and COMTI will Round-Robin the calls to
the ports listed.

Rob Beardsworth
Microsoft

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of any included samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
--------------------
From: "Crasch" <carlo.folini@gmail.com>
Newsgroups: microsoft.public.hiserver.general
Subject: Partitioning TI components
Date: 9 Feb 2005 07:33:34 -0800

Hi, we need to use the same component on the same server to call into
different remote environments.
We tried creating com+ 1.5 partitions, but when we change the remote
environment on one partition the changes are also applied to the other.

Is there a way to do this with his 2000 and/or 2004?

Thanks
Carlo Folini

Crasch · Guest

Hi Rob,
I tried to use com+ 1.5 partitions to configure the two remote
environment.
It seems that COMTI isn't 'partition aware' and as you and Aaron told
me the only way is to manage this programmatically.

Essentially we used to have only one group of users for our
transactions, now our application have to be used from more groups.
Our os/390 decide to separate the two groups phisically. I mean there's
a separate DB2 and there are different CICS for each group.

So we have to call the same transactions on different CICS.

Ciao
Carlo

Rob Beardsworth [MSFT] wrote:

Rob Beardsworth [MSFT] · Guest

Carlo,
would a solution be to put your COMTI applications on 2 seperate
servers? You have 2 groups of users, so you have to split them some how:
you could do it non-programmatically by using 2 separate servers (sort of
like 2 COM+ partitions, but using machines). I wouldn't say "COMTI is not
partition aware" its just that its model is basically "one object, one RE".
I must go read up on partitions, as I was not aware you could put the same
TLB into multiple places :-).

Rob Beardsworth
Microsoft

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of any included samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
--------------------
From: "Crasch" <carlo.folini@gmail.com>
Newsgroups: microsoft.public.hiserver.general
Subject: Re: Partitioning TI components
Date: 11 Feb 2005 01:25:52 -0800

Hi Rob,
I tried to use com+ 1.5 partitions to configure the two remote
environment.
It seems that COMTI isn't 'partition aware' and as you and Aaron told
me the only way is to manage this programmatically.

Essentially we used to have only one group of users for our
transactions, now our application have to be used from more groups.
Our os/390 decide to separate the two groups phisically. I mean there's
a separate DB2 and there are different CICS for each group.

So we have to call the same transactions on different CICS.

Ciao
Carlo

Rob Beardsworth [MSFT] wrote:

Jakes IV · Guest

Seeing thta I cannot start a new thread I will ask my question here (sorry
Carlo).
We have a Asember TP on z/OS which is allways active (MVS starter task). It
waits for work via APPC and initiates the conversations to another TP running
HIS 2004 (still in testing). We previously used the same TP's with SNA 4.0.
The problem is that in our DEV environment we have a number of TP's running
on the same address space and on the windows 2003 (HIS 2004) server. It seems
that only one of them can negotiate a conversation with HIS. The others get
strange errors. On HIs I have confugures 3 different local LU's and 2
different remote LU's all using the same link. Is this possible or do I have
to create a new link for each remote LU.
Note .. We only use SNA for TP to TP conversation and we only created 1 PU
on z/OS for all LU's.

"Crasch" wrote:

	Windows Server Forum Index -> Host Integration Server	All times are GMT
Page 1 of 1