| RE: [cosmos-dev] Query reg Configuration Tests |
|
Srinivas Check
your <tomcat>\webapps\cosmos\WEB-INF\classes\domainEPR.xml on Windows. It
should contain the Linux domain. Hubert,
with the automatic registration, do we still need the “broker register”
anymore? Regards Bill From:
cosmos-dev-bounces@xxxxxxxxxxx [mailto:cosmos-dev-bounces@xxxxxxxxxxx] On Behalf Of Doma, Srinivas Reddy Bill, Thanks once again, I just check this and
it seems ‘broker register’ from windows did not register my linux
broker. When I tried to list the broker EPR using ‘domain
getBrokers’ I still see local broker only where I am expecting remote
broker(linux). I think there is some problem with
‘broker register’ over here? Does this work, because with tomcat
deployment I can see broker and Data Managers getting registered to
Management Domain automatically. Why do we still have ‘broker
register’ over here? Thanks, Srinivas From:
cosmos-dev-bounces@xxxxxxxxxxx [mailto:cosmos-dev-bounces@xxxxxxxxxxx] On Behalf Of Muldoon, William H Srinivas
The broker EPR resides in the domain. To show it, use the “domain
getBrokers” command from the cosmos-client and enter the domainEPR. Regards Bill From: cosmos-dev-bounces@xxxxxxxxxxx
[mailto:cosmos-dev-bounces@xxxxxxxxxxx] On
Behalf Of Bill, Thank you for clarifying on my missing step, I even tried
doing that changes but still I don't see any Data Managers (empty page). I guess there is still some configuration is missing over
here ? Where does broker EPR resides ? I mean is there any configuration file where we could see broker EPR ? I could only see
domainEPR.xml files. Thanks, Srinivas From:
cosmos-dev-bounces@xxxxxxxxxxx on behalf of Muldoon, William H Srinivas
I think you are missing a step to configure the COSMOS UI on Windows. Try
changing the <tomcat-dir>/webapps/COSMOSUI/web-inf/web.xml from: <c <param-name>MANAGEMENT_DOMAIN_EPR</param-name> <<param-value>http://localhost:8080/cosmos/services/domain</param-value>
To use port 8090: <p <param-name>MANAGEMENT_DOMAIN_EPR</param-name> < <param-value>http://localhost:8090/cosmos/services/domain</param-value>
Also, I suggest that you open a bug that the COSMOS UI didn’t display an
appropriate message indicating that it could not contact the domain. Regards Bill From:
cosmos-dev-bounces@xxxxxxxxxxx [mailto:cosmos-dev-bounces@xxxxxxxxxxx] On Behalf Of Hi, Can
some one let me know how to test the following scenario, as I am not
able to configure and test it properly? Operational
Efficiency Tests: Configuration Tests Scenario
1: Management Domain running on Windows, Data Broker
and Data Managers running on Linux Test Steps ======== On Windows 1. Unzip COSMOS demo zip file and copy only cosmos and COSMOSUI
folders from <cosmos-demo>/webapps into <tomcat-dir>/webapps 2. Run <cosmos-demo>/bin/ConfigDemo.bat with valid default
configuration data (with port as 8090) 3. Start tomcat (<tomcat-dir>/bin/startup.bat) On Linux 1. Unzip COSMOS demo zip file and copy all folders from
<cosmos-demo>/webapps into <tomcat-dir>/webapps 2. Run <cosmos-demo>/bin/ConfigDemo.bat with valid default
configuration data 3. Start tomcat (<tomcat-dir>/bin/startup.bat) On Windows 1. Open <cosmos-demo>/cosmos-client/cosmosClient.sh and type
'broker register', provide broker EPR from linux broker component Expected Result: 1. COSMOS UI on windows should show all Linux COSMOS Components and
all it's operations should work normally 2. COSMOS Command line client on windows should list all 5 Data
Managers which is running on Linux With
above steps, COSMOS Command line client is working as expected, but not able to
view anything over COSMOS UI? Did I missed any thing
in
above setup steps ? Thanks, Srinivas |