CL 5.6 Master site question

[Rich Durkee]

I have 5.6 installed and am playing around with this master site feature and on the surface it doesn’t see to be of much value. On 5.4.1 I had NetConfigs stored in the site directories and everything else (Xlates, tcls, etc.) stored in a dummy site. Then I created logicals in the sites that pointed to the dummy site Xlate dir, tcl dir, etc.. That way I could connect to any site and edit the NetConfig and any of the Xlates, tcls in one IDE session.

On 5.6 I stored all the Xlates, tcls, etc in the master site, and the NetConfig in the site directory, but without the logicals I can’t see everything from one IDE session.

I am having difficulty determining the value of the master site the way Quovadx implemented it.

Of course there is a distinct possibility I could be doing something wrong.

Topic

[James Cobane]

Rich,

As you say, I think the master site feature emulates what you and many of us have done; that is, have configurations outside of the normal site structure and linked back to existing sites for access across sites.

[Rich Durkee]

The problem is that it does NOT emulate what I had before – unless I am doing something wrong. Under 5.6 my NetConfigs are in sites s02, s03 and s04  and the Xlates, tcls, etc and in the master site – s99. In the IDE, if I set the master site as s99, then set the environment to one of the other three sites, I can’t see any of the Xlates, tcls etc.. If I set the master site as s99 and then set the environment to s99, I can’t see any of the three NetConfigs.

[Bob Richardson]

Greetings,

Folks, we conducted an evaluation of Cloverleaf Integrator 5.6 on AIX 5.2 and found that the master site objects will not be available for update in the non-master sites.  This is by design: you must be current in the master site to update any of the shared objects – tcl procs, Xlates, Tables, etc.  We turned the master site off and kept our one site with the soft links to the common directories in that site from our other sites.

Works fine for us – you turn off the Master Site feature in the IDE at

options -> root options -> blank out the Master Site text box and save.

Enjoy.

[Rich Durkee]

Thanks, I think I will do the same. Too bad. Someone probably put a lot of work into this “feature”.

[Rob Abbott]

As Bob says this is by design.  Master site objects can only be edited when you are in the master site.  

They can be referenced (read-only) by any other site.  For example, if in another site’s netconfig, you will be able to see all the master site xlates when configuring an xlate route.  The master site xlates will be in italics, so you can tell the difference between “local” and “master site” objects.

Hope this helps clear this up.

Rob Abbott
Cloverleaf Emeritus

[James Cobane]

Rich,

So it sounds like your situation was the inverse of the master site; i.e. you look at all of your underlying sites configurations from your global site.  Many of us have configurations that are used across sites, so they exist outside of any one site (or perhaps a ‘global’ site), but are soft-linked into the sites to be accessed by those sites; essentially emulating a root-level definition – which could be considered a ‘master site’.

Jim Cobane

Henry Ford Health

[Author]

Replies