|
From: Markus <sed...@ya...> - 2002-03-04 20:07:22
|
> Hi Markus, > > Before I try to add the NPIMethodProvider I'll try to test some of the > supplied Pegasus providers as well as the SBLIM ones not involving methods. > I need some more experience with Pegasus. > > One issue is that (a new) provider registration scheme has been added to > Pegasus quite recently -- will there be problems running the SBLIM providers > due to that? > I did test the latest Pegasus by using/modifying one of their test clients > (`src/Clients/TestClient' I think). Doing `enumerateInstances' didn't give > any of the SBLIM providers... Do you have a two-line test that would make > Pegasus contact the SBLIM providers? (I've used `cimmof' to load SBLIM > providers into the root/cimv2 namespace.) Maybe there are other problems -- > as I said, I need more experience with Pegasus. > > BTW, I did try some other clients: > > * Sun WBEM Services browser: hangs... > > * SNIA cimom 0.7: doesn't compile on JDK 1.4.0. Of course, I can go back to > 1.3 or whatever. Oh well, portability... > > Regards, > Frank Hi Frank, you have to register NPI derived providers instead of using the qualifier; in fact, Pegasus just ignores the qualifier, so you can safely use the mof-files (even the mofs for java). To register your provider you should use the Register.mof files for the linux providers as template. For testing I recommend the CLI command line interface that is part of SBLIM (another cvs module). It uses the pegasus libraries which either have to be somewhere in /usr/lib or in local libraries specified with the PEGASUS_HOME variable. The syntax is CLI <method> <CIMObjectPath>, for example CLI enumInstances http://your_host:5988/root/cimv2:CIM_Process. Regards Markus _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com |