Genesys Mobile Services

[DJM]

Hi guys

First off, I am a certified Genesys engineer and have certainly RTFM'd, and been working with the products for >10 years..

I am very familiar with the old ICS, and eServices.  So I'm hopefully not asking any stupid questions here

**But** I am still getting my head around the Mobile Services, and quite frankly am struggling to understand how it fits in with the other components.

ORS asside, I'm just referering to the WebAPI server, MobileServices, WebCallBack server etc.

Hopefully you can can help to clarify a few questions I have:
- I presume it is possible to integrate to a smartphone app using the WebAPI Server - I have used this for chat before with eServices. I guess it just won't be as feature rich??
- In your opinion is the Mobile Services 'worth it'?  any thoughts on it's use?
- The Web API Server - this is still a required component with the Mobile Services for chat? (and/or web callback)

Thanks in advance
DJM

[cavagnaro]

Wondering what comments does Pavel may have here  

[Kubig]

The WebAPI is still required for chat services.Of course the ORS and URS is mandatory. There might be more requirements depending on used functions/modules - for example Genesys Media Server solution for callback services. From my point of view, if you have some own custom solution for these purposes, there is no point for migration to GMS. However, if you want to use Mobile Services strictly from Genesys, you can use box solution -> GMS. Some customers want just Genesys or "official" products, not custom developed. It's just my opinion.

[DJM]

Thanks Kubig.

For a previous chat deployment I built up the chat front-end as a .net web application (using the samples for inspiration of course) using the WebAPI Server so I understand it's use in that scenario. And at the end of the day I found the term 'WebAPI' server a bit confusing - really it's just a custom app utilising the SDK hooking into ChatServer/confserv/message server etc etc.


But from the Mobile Services documentation it looks like WebAPI server is used to LoadBalance between multiple Chat Servers. So it sits between the GMS and the Chat servers (in the case of chat). 

In that scenario, it is an off the shelf Genesys product, or like before is custom?

Thanks

[Adam G]

Nearly... Genesys nearly developed it themselves...

If you want the core product - see HERA from exo dus soft...

[LeeQ]

Hi,
The latest GMS 8.5.1 has built-in load balancing for chat servers, so WebAPI server is no longer required. GMS has its own internal interface to chat servers. WebAPI was previously used for load balancing purposes only.

GMS offers REST API, Cometd support, push notifications, iOS and Android sample code, which are some of the advantages over built your own or WebAPI.

Hope this helps.

-Lee


[quote author=DJM link=topic=8811.msg39233#msg39233 date=1429752436]
Hi guys

First off, I am a certified Genesys engineer and have certainly RTFM'd, and been working with the products for >10 years..

I am very familiar with the old ICS, and eServices.  So I'm hopefully not asking any stupid questions here

**But** I am still getting my head around the Mobile Services, and quite frankly am struggling to understand how it fits in with the other components.

ORS asside, I'm just referering to the WebAPI server, MobileServices, WebCallBack server etc.

Hopefully you can can help to clarify a few questions I have:
- I presume it is possible to integrate to a smartphone app using the WebAPI Server - I have used this for chat before with eServices. I guess it just won't be as feature rich??
- In your opinion is the Mobile Services 'worth it'?  any thoughts on it's use?
- The Web API Server - this is still a required component with the Mobile Services for chat? (and/or web callback)

Thanks in advance
DJM
[/quote]