Monitors Role in WLS 7.0

Question

Hello Bea-community,
I'm a relative newbie so please excuse my simple question.
I've granted some users to the group monitors - but when they try
to check/monitor the server-status of the managed servers, they
are getting erros, such as
Access not allowed for subject: principals=[miran, Monitors], on ResourceType:
Server Action: execute, Target: lookupServerLifeCycleRuntime.
As I anderstand this, the group / role monitos should be enough.
Did I miss something or is this a bug?
TIA!
Kind regards,
Miran

Answer 1

Thanks,
My client is UDDI v 1, which explains the problem. Can you recommend a dev
tool that uses UDDI v 2 to find services ?
Dave
"Babak Mozaffari" <[email protected]> wrote:
>
Dear Dave,
As Bruce mentioned, you will be able to make standard UDDI calls to the
said url.
I would only like to add that our UDDI registry is UDDI v2.0 compliant,
so make
sure that any UDDI client you use is v2.0 and not v1.0. The UDDI spec
provides
for registries to verify version information and simply return an error
if the
call uses a different version. Look at the generic attribute (generic="1.0"
or
generic="2.0") to find out which version your client is using.
Regards,
Babak
"Dave" <[email protected]> wrote:
I've set up a UDDI registry using uddiexplorer in WLS 7.0. I want to
be able to
do inquiries aginst this registry from other development tools, such
as the CapeClear
Developer Studio. When I used this particular tool it couldn't findany
of the
services I registered in the WLS UDDI registry.
Is the problem with CapeClear, WLS, or me ? Can the BEA UDDI registry
be interrogated
from other Developer Tools ?
We want to build a large UDDI registry, but it must be on a platform
that works
with other vendor's products.
Dave