Newbie NetUI question -- where is client propath set?

D

dp74

New Member
Hello, I inherited a smallish EB2.1 NETUI 2.81.4.87 Progress 10C setup in which there is currently no test code directory. I want to make the NETUI Test client point to my new test code directories, but I haven't had to deal with this before -- where is the propath set for NETUI clients? Is this only done in the setup utility? I'm a little leery of playing with that, but I guess if I have to...

Sorry, this is probably a really obvious question. I've been stuck working mostly on ridiculously antiquated 8.6E systems in QAD.
 
Ah, looks like this happens in ubroker.properties in DLC/properties. Will try this tomorrow.

qad.com/Documents/TrainingGuides/printondemand/70-2831A.pdf
 
Well, apparently that wasn't it, and neither were the connmgr/telnet scripts that mfgutil generates. Any ideas? Also checked web-disp.p.

The webspeed broker claims to have the test directory at the front when I check it from IE, but it won't actually run anything there. Also tried opening permissions on us/xx, but the NETUI client just refuses to see any code in there.
 
Aha, apparently it IS connmgr. Not sure why it didn't seem to work before, but I have Prod and Test pointing to different code now so good enough,
 
Disclaimer: I am completely oblivious to QAD's MFG/PRO - but the first OpenEdge release to support the .NET GUI was OE10.2. I would speculate that the .NET GUI uses the .NET open client to access the OpenEdge 10.1c AppServer directly. If that's the case you would usually find the PROPATH for the AppServer in the ubroker.properties file. You will need to restart the AppServer to pick up the changes in it's agents PROPATH settings.

Heavy Regards, RealHeavyDude.
 
dp74 said:
Aha, apparently it IS connmgr. Not sure why it didn't seem to work before, but I have Prod and Test pointing to different code now so good enough,
Click to expand...

So, surprise surprise, changing connmgr back did not change the propath back, even after restarting the broker (I modified a QAD program to display the propath). And it's not using the ubroker.properties propath either -- it's definitely using the old connmgr propath that I successfully changed it to before.

I was able to get by using another fix (it's only Test thank God) , but this is very irritating. Surely QAD/Progress must have some better documentation on how propath is set in NetUI?
 
There are 4 components in .NETUI -
  • AS - App Server
  • WS - Webspeed Broker
  • connmgr - Connection Manager Script
  • telnet - Telnet Connection Script

AS & WS definition is located in ubroker.properties. This file is normally located in $DLC/properties. $DLC normally points to PROGRESS install directory. Please make a copy of ubroker.properties before you attempt to change it any ways so that you have something to rollback.

Assuming your App Server name is "proddb", you will have a definition proddb_AS in ubroker.properties. In this definition you will have a section indicating PROPATH. You can alter the PROPATH here.
Assuming your WS Broker name is "proddb", you will have a definition proddb_WS in ubroker.properties. In this definition you will have a section indicating PROPATH. You can alter the PROPATH here. Be sure that PROPATH for AS and WS are same.

Normally, connection manager & telnet scripts are located in MFG/PRO Install directory. Again assuming your instance name is "proddb" you will have connmgr.proddb & telnet.proddb. In both the scripts there is a section where PROPATH is defined. You can alter it here. Here too be sure that PROPATH is same as that for AS & WS.

Shutdown & Start AS & WS -
  • $DLC/bin/wtbman -name proddb -stop - Stop WS Broker
  • $DLC/bin/asman -name proddb -stop - Stop AS Broker
  • $DLC/bin/asman -name proddb -start - Start AS Broker
  • $DLC/bin/wtbman -name proddb -start - Start WS Broker
  • $DLC/bin/asman -name proddb -q - Query Status for AS Broker
  • $DLC/bin/wtbman -name proddb -q - Query Status for WS Broker

Open Connection Manager - Click on Restart Connection Manager. Verify that you view Idle sessions.

Connect using .NETUI

Let me know if you need further assistance.
 
Thanks, but that's what I tried originally and it didn't work. Maybe I'll try it again though, in case I missed something.

We actually rebooted the entire box (for unrelated reasons) and it still didn't pick up the new propath from connmgr or ubroker.properties. Very odd.

I think next I might try re-installing the client, that's the only other thing I can think of that we did before (when it was sucessfully changed) that I haven't done again yet.
 
YES! Finally figured it out.

1) change the propath in connmgr.[env]
2) go into Connection Manager in [env] and choose Restart Connection Manager
3) enjoy your new propath

I was able to replicate this a few times, very confident now.

The literature is very misleading, the ubroker.properties propath is completely ignored.

Thanks all for suggestions.
 
You must log in or register to reply here.
Back
Top