EMC® VoyenceControl version 4.0.1

Hi Ravinder,

Thanks a lot. But I have only Application Programming Interface Cookbook P/N 300-007-475 REV A01. It book has a short description only how to connect to this service via RMI or WS. Nothing about available classes, methods, etc. And where I can find appropriate JAR with this API?

Thanks in advance,

Oleg

Thanks you very much!

Oleg

ravinder.battu wrote: DSAPI samples and Javadoc can be found under $TOMCAT_HOME/webapps/web/dsapi on the Reporting Server. Thanks

Hello Ravinder,

I'm downloading  all needed goods from the server. I generate the JAR from WSDL and attach one to samples sources as library. I also take following JARs from sevrer:
VCApiCore2.jar
acegi-security-1.0.7.jar
client-4.0.1.697.RA.HF1.Patch.jar
jbossall-client.jar
jbossjmx-ant.jar

Also I generated the VoyenceDataAPI.jar from WSDL which gotten via http://your-report-server:8882/ws/dsapi/20/services/DataApiService?wsdl

But DataApiService.JNDI_NAME was not found out in any case. And I have troubles in AttributedModelQuerySample with Param.class definition.

What's is wrong? Please, help me

Thanks you in advance,

Oleg

Hi Oleg,

To clarify, there are two separate, distinct ways to access the DSAPI:

1. using Web Services (WS)
2. using Java RMI

From your last comments, it looks like you are referencing the documentation for both, which would explain any confusion.  If you are integrating with Voyence using Java, I would recommend using the RMI interface just to keep everything in the Java ecosystem.

Connecting to the DSAPI's RMI interface is simple. If you have connected to the VoyenceControl API using the J2EE interface before, you are 99% there!  The method of connecting to the VoyenceControl API J2EE interface is identical to connecting to the DSAPI RMI interface with one small exception: when you make the context.lookup("...") call, use the DataApiService.JNDI_NAME field like this:

Context context = ... // See the DSAPI RMI samples for retrieving the context. There is a standard way. Also, this is the same context used for connecting to the VoyenceControl API (J2EE)

DataApiService dsapi = (DataApiService) context.lookup(DataApiService.JNDI_NAME);

... // make your calls to the DSAPI

If you haven't already seen the "Overview" javadoc page, take a look.  It gives a full description of how to connect to the two different API interfaces.

Don't forget to look at the samples for some easy cut-and-paste boilerplate code to save you some time and trouble.

If you still have trouble, I'm here to help

Thanks,

Reid

Purrrrrrfect

Have a good weekend,

Ravinder

Sent from my iPhone

Hi Reid,

I found needed JARs for me and successfully complied test from provided sources. But I'm permanently getting following error:

Exception in thread "main" javax.naming.NameNotFoundException: 20DataApiService not bound
        at org.jnp.server.NamingServer.getBinding(NamingServer.java:491)
        at org.jnp.server.NamingServer.getBinding(NamingServer.java:499)
        at org.jnp.server.NamingServer.getObject(NamingServer.java:505)
        at org.jnp.server.NamingServer.lookup(NamingServer.java:278)
(lot of lines skipped.....)

I'm using following JARs in CLASSPATH:

VCApiCore2.jar
acegi-security-1.0.7.jar
client-4.0.1.697.RA.HF1.Patch.jar
javax.jar
javax.jws-1.0.jar
jaxb-api-2.0.jar
jaxws-api-2.1.jar
jbossall-client.jar
jbossjmx-ant.jar
voyence-dsapi-client-2.1.0.159.jar

PS How can I do myself reports? I'm extremely need get MAC addresses per each one interface...

Thanks you in advance,

Oleg

Hi Friends,

I am trying this RMI interface.

But getting compiler error at this -   DataApiService.JNDI_NAME

I have generate the java classes from axis tool. It also generates the DataApiService class. But this class would not have JNDI_NAME parameter.

Can someone please help ?