This document was generated from CDN thread
Created by: Bill Westby on 14-07-2011 02:01:17 PM
I'm thinking of using Global Data as a mini data repository for each call, (key would be callguid) to store report data for each call. At the end of the call I would write out everything to my own SQL DB for reporting purposes...not a big fan of using informix for reporting (CVP Reporting Server).
So my question is...is ther a memory limit for using Global Data during each call, like a kb limit? And is there any limit on total global data in use for a vxml server instance? Like a kb or megabyte limit. We usually do not have a lot of active calls in CVP applications, 80 max concurrently today, might up to 120'ish soon as we validate more callers for screen pop purposes..so lets say 120 max for now.
Any limits anyone can warn against using this approach?
Much thanks,
Bill Westby
Medtronic.
Subject: RE: Global Data Memory usage
Replied by: Hemal Mehta on 14-07-2011 07:49:56 PM
It shouldn't take too much memory. Depending on what all you want to store and how you want to store. You could stores data as a vxml variable/javascript or as a java data structure. (latter is preferable, especially with CVP). The former will be processed by the vxml interpreter and would be faster, however I am somewhat weary of using low level vxml code with CVP. I would do it anyday on the front end with IVR like genesys/voicegenie.
There are several ways to do it in java and store it in session. For example, you could have hashtable key value pair and store values. When the call ends, have a class to dump it all in table. Are you using Tomcat or Websphere ?
Subject: Re: New Message from Hemal Mehta in Customer Voice Portal (CVP) - CVP - All
Replied by: Janine Graves on 14-07-2011 08:37:35 PM
Hemal, bill w is referring to the global data that is available to studio
and vxml server thru custom java. It is maintained as persistent data by
tomcat vxml server. Doesn't go to the gateway. It is different than putting
variables into the root doc.
Janine
Connected by DROID on Verizon Wireless
-----Original message-----
From: Cisco Developer Community Forums <cdicuser@developer.cisco.com>
To: "cdicuser@developer.cisco.com" <cdicuser@developer.cisco.com>
Sent: Thu, Jul 14, 2011 23:49:56 GMT+00:00
Subject: New Message from Hemal Mehta in Customer Voice Portal (CVP) - CVP -
All Versions: RE: Global Data Memory usage
Subject: RE: Re: New Message from Hemal Mehta in Customer Voice Portal (CVP) - CVP -
Replied by: Hemal Mehta on 14-07-2011 10:45:59 PM
Janine,
Sure, I understand. I just listed the two options. Shouldn't be a issue with even 120 concurrent calls. Only thing will be to choose your data structures correctly.
Hemal
Subject: Re: New Message from Hemal Mehta in Customer Voice Portal (CVP) - CVP - All
Replied by: Janine Graves on 14-07-2011 11:23:35 PM
Are you thinking of doing this because you're doing app transfers and/or
subdialog invoke? If so, it makes sense to me. If not, then you could
accomplish the same thing using session data.
On 7/14/2011 5:49 PM, Cisco Developer Community Forums wrote:.
> Hemal Mehta has created a new message in the forum "CVP - All Versions":
>
> --------------------------------------------------------------
> I'm thinking of using Global Data as a mini data repository for each
> call, (key would be callguid) to store report data for each call. At
> the end of the call I would write out everything to my own SQL DB for
> reporting purposes...not a big fan of using informix for reporting
> (CVP Reporting Server).Â
> Â
> So my question is...is ther a memory limit for using Global
> Data during each call, like a kb limit? And is there any limit on
> total global data in use for a vxml server instance? Like a kb or
> megabyte limit.  We usually do not have a lot of active calls in
> CVP applications, 80 max concurrently today, might up to 120'ish soon
> as we validate more callers for screen pop purposes..so lets say 120
> max for now.
> Â
> Any limits anyone can warn against using this approach?
> Â
> Much thanks,
> Bill Westby
> Medtronic.
>
>
> It shouldn't take too much memory. Depending on what all you want to
> store and how you want to store. You could stores data as a vxml
> variable/javascript  or as a java data structure. (latter is
> preferable, especially with CVP). The former will be processed by
> the vxml interpreter and would be faster, however I am somewhat weary
> of using low level vxml code with CVP. I would do it anyday on the
> front end with IVR like genesys/voicegenie.
> There are several ways to do it in java and store it in session. For
> example, you could have hashtable key value pair and store values.
> When the call ends, have a class to dump it all in table. Are you
> using Tomcat or Websphere ?
> Â
> --
> To respond to this post, please click the following link:
>
> <http://developer.cisco.com/web/cvp/forums/-/message_boards/view_message/4228701>
>
> or simply reply to this email.
--
Janine Graves
Subject: RE: Global Data Memory usage
Replied by: Bill Westby on 15-07-2011 01:44:29 PM
Yes, I inherited this particular app and it is 1 central "main" app which invokes 14 possible sub-dialog apps during each call. I'll be re-designing it late this year to move it to a single app or far fewer but regardless I want to build up the history as the call progresses then write it once.
I played with writing the data after each sub-dialog invoke but the risk of hanging the SQL server connection and causing dead-air in the call or a timeout disconnect is too high for such an approach, and not efficient either.
I'm going to start testing the Global Data approach then and see how that works out in my lab, just wanted to find out any memory limitations first before spending time solving a problem with an unsupported solution
Thanks!,
Bill Westby
Medtronic.
Subject: Re: New Message from Bill Westby in Customer Voice Portal (CVP) - CVP - All
Replied by: Janine Graves on 15-07-2011 01:58:47 PM
Until someone from Cisco 'weighs in' - I'd say as with most VxmlServer
functions, there aren't hard and fast size limitations, other than
overflowing tomcat memory allocation.
Let us know how you make out with it.
Janine
On 7/15/2011 1:44 PM, Cisco Developer Community Forums wrote:
> Bill Westby has created a new message in the forum "CVP - All Versions":
>
> --------------------------------------------------------------
> Yes, I inherited this particular app and it is 1 central "main" app
> which invokes 14 possible sub-dialog apps during each call. I'll be
> re-designing it late this year to move it to a single app or far fewer
> but regardless I want to build up the history as the call progresses
> then write it once.
>
> I played with writing the data after each sub-dialog invoke but the
> risk of hanging the SQL server connection and causing dead-air in the
> call or a timeout disconnect is too high for such an approach, and not
> efficient either.
>
> I'm going to start testing the Global Data approach then and see how
> that works out in my lab, just wanted to find out any memory
> limitations first before spending time solving a problem with an
> unsupported solution emoticon
>
> Thanks!,
> Bill Westby
> Medtronic.
> --
> To respond to this post, please click the following link:
>
> <http://developer.cisco.com/web/cvp/forums/-/message_boards/view_message/4231765>
>
> or simply reply to this email.
--
Janine Graves
Created by: Bill Westby on 14-07-2011 02:01:17 PM
I'm thinking of using Global Data as a mini data repository for each call, (key would be callguid) to store report data for each call. At the end of the call I would write out everything to my own SQL DB for reporting purposes...not a big fan of using informix for reporting (CVP Reporting Server).
So my question is...is ther a memory limit for using Global Data during each call, like a kb limit? And is there any limit on total global data in use for a vxml server instance? Like a kb or megabyte limit. We usually do not have a lot of active calls in CVP applications, 80 max concurrently today, might up to 120'ish soon as we validate more callers for screen pop purposes..so lets say 120 max for now.
Any limits anyone can warn against using this approach?
Much thanks,
Bill Westby
Medtronic.
Subject: RE: Global Data Memory usage
Replied by: Hemal Mehta on 14-07-2011 07:49:56 PM
I'm thinking of using Global Data as a mini data repository for each call, (key would be callguid) to store report data for each call. At the end of the call I would write out everything to my own SQL DB for reporting purposes...not a big fan of using informix for reporting (CVP Reporting Server).
So my question is...is ther a memory limit for using Global Data during each call, like a kb limit? And is there any limit on total global data in use for a vxml server instance? Like a kb or megabyte limit. We usually do not have a lot of active calls in CVP applications, 80 max concurrently today, might up to 120'ish soon as we validate more callers for screen pop purposes..so lets say 120 max for now.
Any limits anyone can warn against using this approach?
Much thanks,
Bill Westby
Medtronic.
It shouldn't take too much memory. Depending on what all you want to store and how you want to store. You could stores data as a vxml variable/javascript or as a java data structure. (latter is preferable, especially with CVP). The former will be processed by the vxml interpreter and would be faster, however I am somewhat weary of using low level vxml code with CVP. I would do it anyday on the front end with IVR like genesys/voicegenie.
There are several ways to do it in java and store it in session. For example, you could have hashtable key value pair and store values. When the call ends, have a class to dump it all in table. Are you using Tomcat or Websphere ?
Subject: Re: New Message from Hemal Mehta in Customer Voice Portal (CVP) - CVP - All
Replied by: Janine Graves on 14-07-2011 08:37:35 PM
Hemal, bill w is referring to the global data that is available to studio
and vxml server thru custom java. It is maintained as persistent data by
tomcat vxml server. Doesn't go to the gateway. It is different than putting
variables into the root doc.
Janine
Connected by DROID on Verizon Wireless
-----Original message-----
From: Cisco Developer Community Forums <cdicuser@developer.cisco.com>
To: "cdicuser@developer.cisco.com" <cdicuser@developer.cisco.com>
Sent: Thu, Jul 14, 2011 23:49:56 GMT+00:00
Subject: New Message from Hemal Mehta in Customer Voice Portal (CVP) - CVP -
All Versions: RE: Global Data Memory usage
Subject: RE: Re: New Message from Hemal Mehta in Customer Voice Portal (CVP) - CVP -
Replied by: Hemal Mehta on 14-07-2011 10:45:59 PM
Hemal, bill w is referring to the global data that is available to studio
and vxml server thru custom java. It is maintained as persistent data by
tomcat vxml server. Doesn't go to the gateway. It is different than putting
variables into the root doc.
Janine
Connected by DROID on Verizon Wireless
-----Original message-----
From: Cisco Developer Community Forums <cdicuser@developer.cisco.com>
To: "cdicuser@developer.cisco.com" <cdicuser@developer.cisco.com>
Sent: Thu, Jul 14, 2011 23:49:56 GMT+00:00
Subject: New Message from Hemal Mehta in Customer Voice Portal (CVP) - CVP -
All Versions: RE: Global Data Memory usage
Janine,
Sure, I understand. I just listed the two options. Shouldn't be a issue with even 120 concurrent calls. Only thing will be to choose your data structures correctly.
Hemal
Subject: Re: New Message from Hemal Mehta in Customer Voice Portal (CVP) - CVP - All
Replied by: Janine Graves on 14-07-2011 11:23:35 PM
Are you thinking of doing this because you're doing app transfers and/or
subdialog invoke? If so, it makes sense to me. If not, then you could
accomplish the same thing using session data.
On 7/14/2011 5:49 PM, Cisco Developer Community Forums wrote:.
> Hemal Mehta has created a new message in the forum "CVP - All Versions":
>
> --------------------------------------------------------------
> I'm thinking of using Global Data as a mini data repository for each
> call, (key would be callguid) to store report data for each call. At
> the end of the call I would write out everything to my own SQL DB for
> reporting purposes...not a big fan of using informix for reporting
> (CVP Reporting Server).Â
> Â
> So my question is...is ther a memory limit for using Global
> Data during each call, like a kb limit? And is there any limit on
> total global data in use for a vxml server instance? Like a kb or
> megabyte limit.  We usually do not have a lot of active calls in
> CVP applications, 80 max concurrently today, might up to 120'ish soon
> as we validate more callers for screen pop purposes..so lets say 120
> max for now.
> Â
> Any limits anyone can warn against using this approach?
> Â
> Much thanks,
> Bill Westby
> Medtronic.
>
>
> It shouldn't take too much memory. Depending on what all you want to
> store and how you want to store. You could stores data as a vxml
> variable/javascript  or as a java data structure. (latter is
> preferable, especially with CVP). The former will be processed by
> the vxml interpreter and would be faster, however I am somewhat weary
> of using low level vxml code with CVP. I would do it anyday on the
> front end with IVR like genesys/voicegenie.
> There are several ways to do it in java and store it in session. For
> example, you could have hashtable key value pair and store values.
> When the call ends, have a class to dump it all in table. Are you
> using Tomcat or Websphere ?
> Â
> --
> To respond to this post, please click the following link:
>
> <http://developer.cisco.com/web/cvp/forums/-/message_boards/view_message/4228701>
>
> or simply reply to this email.
--
Janine Graves
Subject: RE: Global Data Memory usage
Replied by: Bill Westby on 15-07-2011 01:44:29 PM
Yes, I inherited this particular app and it is 1 central "main" app which invokes 14 possible sub-dialog apps during each call. I'll be re-designing it late this year to move it to a single app or far fewer but regardless I want to build up the history as the call progresses then write it once.
I played with writing the data after each sub-dialog invoke but the risk of hanging the SQL server connection and causing dead-air in the call or a timeout disconnect is too high for such an approach, and not efficient either.
I'm going to start testing the Global Data approach then and see how that works out in my lab, just wanted to find out any memory limitations first before spending time solving a problem with an unsupported solution
Thanks!,
Bill Westby
Medtronic.
Subject: Re: New Message from Bill Westby in Customer Voice Portal (CVP) - CVP - All
Replied by: Janine Graves on 15-07-2011 01:58:47 PM
Until someone from Cisco 'weighs in' - I'd say as with most VxmlServer
functions, there aren't hard and fast size limitations, other than
overflowing tomcat memory allocation.
Let us know how you make out with it.
Janine
On 7/15/2011 1:44 PM, Cisco Developer Community Forums wrote:
> Bill Westby has created a new message in the forum "CVP - All Versions":
>
> --------------------------------------------------------------
> Yes, I inherited this particular app and it is 1 central "main" app
> which invokes 14 possible sub-dialog apps during each call. I'll be
> re-designing it late this year to move it to a single app or far fewer
> but regardless I want to build up the history as the call progresses
> then write it once.
>
> I played with writing the data after each sub-dialog invoke but the
> risk of hanging the SQL server connection and causing dead-air in the
> call or a timeout disconnect is too high for such an approach, and not
> efficient either.
>
> I'm going to start testing the Global Data approach then and see how
> that works out in my lab, just wanted to find out any memory
> limitations first before spending time solving a problem with an
> unsupported solution emoticon
>
> Thanks!,
> Bill Westby
> Medtronic.
> --
> To respond to this post, please click the following link:
>
> <http://developer.cisco.com/web/cvp/forums/-/message_boards/view_message/4231765>
>
> or simply reply to this email.
--
Janine Graves