I've added a couple of AppServers in ubroker.properties by manually editing them. Now the nameserver has failed because of an invalid uuid on them. What do I need to do?
I always create unique uuids for each new broker. Either by asking my cat to cross the keyboard or Progress’ genuuid tool from “proenv”.
Thanks Mike - genuuid did the trick as I don't have a cat. My guinea pig isn't heavy enough to depress the keys. :(
James,
There was a conversation on the PEG back in April last year about adding stuff to the ubroker. I've pasted an email from that exchange below. The top comment is from David Craven.
<peg email>
For 3a) I use
uuid=!{newValue:UUID}
No need to run genuuid, mergeprop will take care of that for you when
you load you new entry via the create or update options.
Added bonuses of the mergeprop approach:
0) mergeprop will create a backup before it applies your changes --
you can fall back if something goes wrong.
1) You can use mergeprop to extract and clone entries
2) You can use mergeprop to validate entries
3) You can maintain your template properties in the source control of
your choosing
One caveat: you may need to launch your proenv window with "run as
administrator"
On 4/25/2013 8:41 AM, Peter Judge wrote:
> If you need to edit ubroker-style files by hand, I would recommend the
following approach.
> 0) DO NOT EDIT THE $DLC UBROKER.PROPERTIES FILE BY HAND. EVER. NEVER
EVER. You run the risk of messing it up and also, having your stuff
overwritten if the Admin Server happens to be running while you are making
your changes. The approach below helps mitigate the former and removes the
latter.
> 1) If you're an ABL person, and are 1-based, see (0)
> 2) Create smaller files in which you have the stuff you want to change.
If you want to change/add an AppServer, say, copy an existing AppServer
from $DLC/properties/ubroker.properties or
$DLC/properties/ubroker.samples.
> 3) Change what you want/need to.
> 3a) If you need a uuid value (and you will, for new entries), open
> ProEnv and run "genuuid". Copy& past the results of that into the new text file.
> 4) Now you can use the mergeprop tool (via ProEnv) to merge your new
> properties file into the runtime one (typically the one in $DLC). The
> output of the command without parameters is below. Take note of the
> VALIDATE option. I don't know when this command was introduced but I know
> it's been there since at least 10.1 and I think since 10.0.
>
> proenv>mergeprop
> OpenEdge Release 11.2 as of Wed Feb 13 19:01:30 EST 2013
> A property file type must be specified. (PRPMsg039)
> Usage: mergeprop<parameter> ...
> <parameter>:
> -action<list|listall> <property group>
> or
> -action<update|create|delete>
> -delta<file>
>
> -type<database|ubroker|plugin|tools|none>
> -target<file>
> -validate
> -nobackup
> -recurse (-type database only)
> -silent
</peg email>
Thanks Peter - very useful.