UCCX 5/7 or 8 - Database access - How does the UCCX engine use the DB connection
I was asked the following question by a customer:
"How does UCCX manage it’s database connections – a connection pool manager / single connection / single connection for each call"
Does anyone actually know ? Is it documented anywhere?
Based on how the steps work I'd guess that the UCCX engine makes a new single DB connection each time the DB step reaches out the DB for a read/write. I assume it would do this independently for every instance of a script running. Hence the importance of the DB release step I'm guessing.
I know in the DB subsystem you can configure the maximum number of DB connections to be used but this doesn't imply how they are used.
I'm not a DB guy, but I think the concern stems from the potential load on a DB server with the constant opening and closing of the DB connections. I'm assuming that if it used a connection pool the UCCX engine would open, and keep open, a group of DB connections to be used by the UCCX engine. This would lessen the load on the DB server I'm assuming.
Is there any fundamental difference with UCCX 8 and the DB access ? It obviously not ODBC anymore. It JDBC right ? But again how does the UCCX engine use the DB connection?
Re: UCCX 5/7 or 8 - Database access - How does the UCCX engine u
To my knowledge, this is not documented; however, at least through 7.0 the MIVR subsystem will open a pool of ODBC connections equal to the maximum you defined and keep them open. If you set it to 50, you will see 50 open connections on the SQL server. Each script that is triggered will attach to one of the available connections as soon as you use a DB-related step and keep it until you use a DB Release step. Once that script instance releases it, the connection is available for another script.
The behavior should not change with 8.0 as it is the same MIVR subsystem that is doing the work. My first CCX 8.0 project that needs database integration is still about 30 days away so I can't guarantee that though.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.