Kbase P124974: How to transfer ubroker.properties from windows to unix
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
17/10/2007 |
|
Status: Verified
GOAL:
How to transfer ubroker.properties from windows to unix
GOAL:
How to transfer ubroker.properties from one server to an_other
GOAL:
Will Progress Explorer generate my ubroker.properties for Unix where no connection is available?
FACT(s) (Environment):
Progress 8.x
Progress 9.x
OpenEdge 10.x
All Supported Operating Systems
FIX:
Typically this question is asked at configuration and setup time.
If there is a connection to the AdminServer running on the remote server, then the ubroker.properties will be created in the correct place on the remote server, there is no need for transfer.
Transferring a ubroker.properties from one server to an_other should not be an issue if the major minor version is the same (the format changes, new values are added) and if the previous server is no longer going to be in use (so that the uuid will be valid).
Often however, there are issues connecting from the Progress Explorer to the remote AdminServer due to site firewall policies and for example ssh or VPN connections are disallowed.
The following outlines a method whereby the ubroker.properties can be created through the Progress Explorer tool, using the Local AdminServer then transferred to the remote server and further edited. It is assumed that familiarity with these utilities and their methods are known.
[Windows]
1. From the Progress Explorer interface to the local AdminServer, add all the ubroker information/ modifications.
NOTE: it is assumed that the directories etc on the remote server are known. Since there is no connection to the remote system, these will not be known.
2. Transfer the ubroker.properties to the remote server
[UNIX]
3. Open the ubroker.properties in vi editor (for example):
- Verify that this file does not have the ^M character. (alternatively: run dos2unix ubroker.properties > ubroker.properties2 and compare)
- Replace the Windows back-slash "\" with the Unix forward-slash separator "/"
- Delete the Windows .exe extension on executables
- Check the directory references are vaild
4. When Progress Explorer was used to create broker instances, a uuid was generated automatically. In the ubroker.properties a 'uuid' parameter will exist for every broker instance, which contains the IP information of the Windows machine (along with other information), when running the file on another machine or even a machine which has a different network, the broker(s) may startup fine, but fail to register to NameServer for example. A UUID is there to identify the various Progress processes on a specific system. Unless certain of the uuid's uniqueness, re-generate the uuid for each broker as a safety net with the genuuid utility: $DLC/bin/genuuid
5. As a final check, validate the ubroker.properties file with the ubconfig utility
$DLC/bin/ubconfig -f /<fullpath>/dlc/properties/ubroker.properties >> ubconf.out
Review any "VALIDATION MESSAGE" output that results.
Note: the ubconfig utility will not detect errors if the version of the ubroker.properties file is different. For example, an OpenEdge 10.1A ubroker.properties file will not have the new properties that were added in OpenEdge 10.1B for AppServer Keep-Alive functionality.