|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
How to create WSRR definition in WAS 7.0.0.11 |
« View previous topic :: View next topic » |
Author |
Message
|
swarna.prava.mohanty |
Posted: Fri May 04, 2012 2:26 am Post subject: How to create WSRR definition in WAS 7.0.0.11 |
|
|
Novice
Joined: 29 Aug 2010 Posts: 15
|
How to create WSRR definition in WAS 7.0 , "WSSRR definitions" is not found under ServiceIntegration in admin console |
|
Back to top |
|
 |
mqjeff |
Posted: Fri May 04, 2012 3:06 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
|
Back to top |
|
 |
swarna.prava.mohanty |
Posted: Sun May 06, 2012 5:04 am Post subject: |
|
|
Novice
Joined: 29 Aug 2010 Posts: 15
|
No, I mean .After installing WSRR and WAS server, I created WSRR standAlone server profile, then augmented this into WAS deployment manager profile. Now I want to use WSRR from Message Broker 7.0 using Endpoint lookup nodes. But before that I have to run some configuration commands for endpoints address of WSRR. E.g: mqsichangeproperties broker name
-c ServiceRegistries -o DefaultWSRR -n endpointAddress
-v http://hostname:9080/WSRRCoreSDO/services/WSRRCoreSDOPort
But before that we have create WSRR definition in WAS server
# Expand Service integration > WSRR definitions, in the navigation pane. The WSRR definitions page is displayed in the content pane, which shows a list of all the WSRR definitions.
# Click New. The WSRR definitions configuration page displays.
# Complete the following property fields:
WSRR definition name
This is required and must be unique inside the cell. It is the administrative name for this WSRR definition.
Description
You have the option to enter a description for the definition.
Default WSRR definition
This indicates whether this definition is the default. If this is the first definition you have created, it will automatically be set as the default. You cannot update the default from this page.
Timeout of cache
The time (in seconds) after which the results in the WSRR cache expire and will be refreshed. This can be changed from the default value. If you specify a value of 0 (zero), then results are never cached. The cache is used for storing information about service endpoints and mediation policies, retrieved from the registry.
Connection type
Your only choice is Web service.
# Click Apply to save these properties.
# Click Connection properties, under Additional properties in the content pane. The Connection properties configuration page displays.
# Complete the following property fields:
Connection type
This is set when the registry definition is created, and cannot be changed.
Registry URL
The URL to be used to connect to the WSRR instance. The default value is: http://localhost:9080/WSRRCoreSDO/services/WSRRCoreSDOPort
If you want to retrieve endpoints from WSDL that has SOAP 1.2 bindings, you must use Version 6.2 or later versions of the Web service interface URL, which is generally: http://<server>:<port>/WSRR6_2/services/WSRRCoreSDOPort.
Note: If you call the Version 6.2 URL from a client generated for a previous version of WSRR, the client might fail if it cannot correctly process the data that is returned.
You must use Version 7.0 or later versions of the Web service interface URL if you want to look up any of the following endpoint types:
* Manually defined MQ endpoints with associated interfaces
* Manually defined JMS endpoints with associated interfaces
* Manually defined HTTP endpoints with associated interfaces
In this case, the interface URL is generally: http://<server>:<port>/WSRR7_0/services/WSRRCoreSDOPort, where WSRR7_0 is the version number.
But in my WAS admin console , I am not able to find WSRR definition under Service Integration tab.Can anyone please help. |
|
Back to top |
|
 |
mqjeff |
Posted: Sun May 06, 2012 8:26 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
swarna.prava.mohanty wrote: |
But in my WAS admin console , I am not able to find WSRR definition under Service Integration tab.Can anyone please help. |
The only reason I can think that this would be the case is because you did not SUCCESSFULLY
Quote: |
.After installing WSRR and WAS server, I created WSRR standAlone server profile, then augmented this into WAS deployment manager profile. |
.
That something went wrong.
Or there's additional steps you have to take to add it in to the was admin console,but the only place I know that would talk about that is in the links i gave you. |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|
|