Help with Connected Environmets

Hi Duncan,

I've been having the same difficulties. Disconnecting the environments

is not as easy as connecting them.

Sometimes, you simply get an error while trying to disconnect.

Sometimes the nodemanager simply crashes when trying to disconnect.

Sometimes disconnecting is successfull, but reconnecting is no longer

possible.

Sometimes it works fine.

The best solution is to export the environment definition, throw away

the environment repository and bootstrap the nodemanager with this

exported file. This gets rid of all invisible, corrupted links that are not

cleaned away by Forte.

One more thing. When you connect an environment and you use

named objects (ObjectLocationManager), you need to supply a base

path. Your base path is "/", which Forte allows, but which does cause

several problems. Better is to give each environment its own, unique

root. I was very disappointed by that.

> --Original Message--

> From: Duncan Kinnear [SMTP:duncanmccarthy.co.nz]

> Sent: donderdag 13 januari 2000 23:40

> To:kamranaminyahoo.com

> Subject:(forte-users) Help with Connected Environmets

>

> Hi folks!

>

> Happy new year to you all.

>

> We are having a bit of a 'fiddle' with connected environments (there's not

>

> much documentation out there!), and we seem to have stuffed

> something up.

>

> In our 'CentralEnv' environment we connected another environment

> called 'TestEnv' using the command:

>

> connectenv TestEnv server2:5001 /

>

> After having a 'play' with this configuration (and not really getting

> anywhere!) we tried to disconnect the connected environment. However,

> we are getting the following error which we don't really understand:

>

> SYSTEM ERROR: Cannot disconnect environment <UUID> which is not

> a subordinate or superior environment of the current environment.

> [ .. rest of error information ...]

>

> Can anyone tell us what we've done wrong? The 'showenv' command

> gives the following output:

>

> BF778FC0-A8E3-11D2-A603-A8999D9EAA77 CentralEnv

>EnvironmentSet:

>Locations:

>Location Descriptor for protocol: Forte!TCP/IP

> Attribute string is: server1:5000

> BE1109A0-B8AC-11D3-9B50-3B443B15AA77 testenv

>EnvironmentSet:

>Locations:

>Location Descriptor for protocol: Forte!TCP/IP

> PortNumber 5001

> HostNameserver2

>

> Can anyone point us in the direction of some GOOD documentation on

> connected environments?

>

>

> Cheers,

>

> Duncan Kinnear,

> McCarthy and Associates,Email:

> duncanMcCarthy.co.nz

> PO Box 764, McLean Towers, Phone: +64 6 834 3360

> Shakespeare Road, Napier, New Zealand.Fax:+64 6 834

> 3369

> --

> --

> Providing Integrated Software to the Meat Processing Industry for over 10

> years

>

> --

> For the archives, go to: <a href=

"http://lists.sageit.com/forte-users">http://lists.sageit.com/forte-users< ;/a> and use

> the login: forte and the password: archive. To unsubscribe, send in a new

> email the word: 'Unsubscribe' to: forte-users-requestlists.sageit.com

at 2007-6-29 9:16:05 >

A couple of things:

1 We had a problem with a corrupt connected environment, where each

environment thought the other was the super environment. The symptom for

this was that the system would run okay until suddenly the environment

managers would go "ape", allocate as much memory as possible and crash. We

tried "bootstrapping" by exporting the environment and blowing away the

btx/btd files, but it didn't solve our problem. The cure was to blow away

the environment and remake it from scratch.

2 When we tried to disconnect our corrupted environment, there seemed to be

some communication take place between the environments (which of course

crashed the system for us). In your case, I would make sure that the other

partner(s) of the connected environment are visible, otherwise I guess the

environment will hang.

Nick.

--Original Message--

From:Amin, Kamran [<a href=

"mailto:kamran.aminframeworkinc.com">mailto:kamran.aminframeworkinc.com</ a>]

Sent:Friday, January 14, 2000 7:14 AM

To: 'Rottier, Pascal'; 'kamranaminyahoo.com';

'duncanMcCarthy.co.nz'

Subject:RE: (forte-users) Help with Connected

Environmets

Instead of using escript to connect the environment try

using econsole. You

will have to select View/Application outline in the menu

options and then

select the NameService component. Then use the Utility menu

to do the rest.

If you want to disconnect an environment do the following:

1. Select Utility/Show Administration. This will show the

connected

environment in your log of the launch server. It should

look something like

this.

EnvironmentName:MMAKER

SearchPath:

MMAKER(BAC1FD20-92E1-11D3-9E2E-0A859908AA77)(a)

EnvironmentId:BAC1FD20-92E1-11D3-9E2E-0A859908AA77

SupEnvironmentId:<none>

SubEnvironmentIds:

<none>

LastNsPartitionId: 0x775

LastPartitionId:0x87f

Attributes: DELETE_ON_COMM_FAIL

The testenv should show up as a SubEnvironmentIds if you

have chosen

CentralEnv as the root.

2. Select Utility/Disconnect environment and put in the

environment name.

This should disconnect the environment. You have to make

sure before you

connect that the name of all the environments are unique.

3. Do step one again and the testenv should not be there.

I have seen it crash many time when connecting the

environments using the

UUID. I think that was a bug. Also remember to enter the

EnvSearchPath by

double clicking on the NameService to complete the connected

environments.

All this can be found in the Forte System Management Guide

page 75.

Good luck.

ka

Kamran Amin

Framework, Inc.

303 South Broadway

Tarrytown, NY 10591

(914) 631-2322x121

kamran.aminframeworkinc.com

<a href=

"http://www.frameworkinc.com/">http://www.frameworkinc.com/</a>

--Original Message--

From: Rottier, Pascal [<a href=

"mailto:Rottier.Pascalpmintl.ch">mailto:Rottier.Pascalpmintl.ch</a>]

Sent: Friday, January 14, 2000 4:04 AM

To: kamranaminyahoo.com

Subject: RE: (forte-users) Help with Connected Environmets

Hi Duncan,

I've been having the same difficulties. Disconnecting the

environments

is not as easy as connecting them.

Sometimes, you simply get an error while trying to

disconnect.

Sometimes the nodemanager simply crashes when trying to

disconnect.

Sometimes disconnecting is successfull, but reconnecting is

no longer

possible.

Sometimes it works fine.

The best solution is to export the environment definition,

throw away

the environment repository and bootstrap the nodemanager

with this

exported file. This gets rid of all invisible, corrupted

links that are not

cleaned away by Forte.

One more thing. When you connect an environment and you use

named objects (ObjectLocationManager), you need to supply a

base

path. Your base path is "/", which Forte allows, but which

does cause

several problems. Better is to give each environment its

own, unique

root. I was very disappointed by that.

> --Original Message--

> From: Duncan Kinnear [SMTP:duncanmccarthy.co.nz]

> Sent: donderdag 13 januari 2000 23:40

> To:kamranaminyahoo.com

> Subject:(forte-users) Help with Connected

Environmets

>

> Hi folks!

>

> Happy new year to you all.

>

> We are having a bit of a 'fiddle' with connected

environments (there's not

>

> much documentation out there!), and we seem to have

stuffed

> something up.

>

> In our 'CentralEnv' environment we connected another

environment

> called 'TestEnv' using the command:

>

> connectenv TestEnv server2:5001 /

>

> After having a 'play' with this configuration (and not

really getting

> anywhere!) we tried to disconnect the connected

environment. However,

> we are getting the following error which we don't really

understand:

>

> SYSTEM ERROR: Cannot disconnect environment <UUID> which

is not

> a subordinate or superior environment of the current

environment.

> [ .. rest of error information ...]

>

> Can anyone tell us what we've done wrong? The 'showenv'

command

> gives the following output:

>

> BF778FC0-A8E3-11D2-A603-A8999D9EAA77 CentralEnv

>EnvironmentSet:

>Locations:

>Location Descriptor for protocol: Forte!TCP/IP

> Attribute string is: server1:5000

> BE1109A0-B8AC-11D3-9B50-3B443B15AA77 testenv

>EnvironmentSet:

>Locations:

>Location Descriptor for protocol: Forte!TCP/IP

> PortNumber 5001

> HostNameserver2

>

> Can anyone point us in the direction of some GOOD

documentation on

> connected environments?

>

>

> Cheers,

>

> Duncan Kinnear,

> McCarthy and Associates,Email:

> duncanMcCarthy.co.nz

> PO Box 764, McLean Towers, Phone: +64

6 834 3360

> Shakespeare Road, Napier, New Zealand.Fax:

+64 6 834

> 3369

>

--

> --

> Providing Integrated Software to the Meat Processing

Industry for over 10

> years

>

> --

> For the archives, go to:

<a href=

"http://lists.sageit.com/forte-users">http://lists.sageit.com/forte-users< ;/a> and use

> the login: forte and the password: archive. To

unsubscribe, send in a new

> email the word: 'Unsubscribe' to:

forte-users-requestlists.sageit.com

--

For the archives, go to: <a href=

"http://lists.sageit.com/forte-users">http://lists.sageit.com/forte-users< ;/a>

and use

the login: forte and the password: archive. To unsubscribe,

send in a new

email the word: 'Unsubscribe' to:

forte-users-requestlists.sageit.com

--

For the archives, go to: <a href=

"http://lists.sageit.com/forte-users">http://lists.sageit.com/forte-users< ;/a>

and use

the login: forte and the password: archive. To unsubscribe,

send in a new

email the word: 'Unsubscribe' to:

forte-users-requestlists.sageit.com

at 2007-6-29 9:16:05 >