No Java sample for Platform SDK?

[victor]

Finally I have got my hands on a long-awaited Platform SDK.

And, for some unknown reason, there is no Java sample for using it. I think t-lib is now called voice platform SDK... And yet I cannot find any sample code for it in Java.  am I missing something here?

Vic

[cavagnaro]

When i install the Java Interface for Desktop Toolkit it also installs some examples on the installation folder. Is this the same tool you mention Victor?

[victor]

Thanks for the pointer, Cavagnaro!

Actually, it is a bit different (at least I think so), because Platform SDK seems to be different from Java Interface for Desktop Toolkit. Of course, as you see, I am still a bit dazzled by what is available out there. They made the whole thing so complex. Is it the same thing?

[Dave]

They're not the same thing.  Vic, have you checked out DevZone?  I can see four application blocks listed under "Platform SDK for Java" showing there...  For raw code samples, you're right that only the .NET code samples are included with the Voice Platform SDK, but if you look at the Agent Interaction, Media Interaction, and Queued Interaction Java Code Samples, they'll do just what you need...

[victor]

Hi, Dave,

thank you for replying.

I have a pretty good knowledge of t-lib and was able to get things running based on that; however, I am still dazzled by all the different "platforms". Agent Interaction SDK,  Media Interaction and Queued Interactions ...

I did not think about looking into Agent Interaction because I thought it was very different from Platform SDK. It's like looking into DDK (device driver kit) for samples to how to use DirectX SDK. At least I thought so... So, the coding in Agent Interaction and other SDKs are identical to each other?

As for application blocks is there some document to summarizes all of them? Like, what is genji?

Interestingly enough, Java Platform SDK comes with two application blocks: warm-standby and config. I am perplexed as to why only these two application blocks are offered. I can think of a myriad of features that probably have a much higher priority than these two. I guess it depends on how you look at it - do these blocks come as part of SDK (in which case I find it very lacking) or are they added as a sample of how to use SDK (in which case I am perplexed because I did not know that Voice Platform also allowed for access to configuration later and on top of having something more relevant to what majority of users would need).

If so, then, why are they broken up into different SDKs and not offered as one? Am I the only one who feels that Genesys is trying to squeeze more money from users and exercise more control over custom development by taking what used to be t-lib and splitting it into limited versions?

The last question is beyond the topic of this post, but can't stop wondering...

Thanks for the heads up.

[René]

Hi Victor,

I agree with you that the licensing policy of Genesys SDKs is pretty strange (would use different word but trying to be polite ) and it really seems to be a way how to squeeze more money...

To your question of different SDKs... There are two main "set" of SDKs - Platform SDK Suite and Interaction SDK Suite. Platform SDK set includes the SDKs used for direct communication with servers like Voice Platform SDK for Java/NET, Configuration Platform Java/NET, Statistics Platform Java/NET etc. The Interaction SDK suite (Genesys Desktop .NET Toolkit, Agent Interaction SDK etc.) doesn't allow direct communication with server and brings some kind of high-level application layer between your code and Genesys servers. The functionality provided by Interaction SDKs could be limited because not all features are implemented. But that isn't the case for Voice platform SDK. It does support more functionality then the standard T-Lib so you can build your own URS using that SDKs if you want .

Cheers,
René