Hi,
 
I have used the Cisco Database Action Element and is works fine.
I have added an entry to Cisco docwiki on how to set this up to work with an SQL 2005 server.
http://docwiki.cisco.com/wiki/Unified_CVP_VXML_Server_JNDI_Resources
 
However if there is a failure to the DB the CVP application will exit with a failure.
This could happen if their database connection has an issue (network, DB server issue etc.) or if there is any authentication issues etc.
 
I do not know why this element was not designed as a Decision Element so you could
have a sucess or fail exit states, you could then decide how to handle the error better.
 
Question:
Am I missing anything here in trying to handle an error such as the ones outlined above?
Does anyone have a better database integration element that the default out of the box one that they would like to share?
 
Gerard.

Just code it as an action element and call a backend java class which calls your database and catches related exceptions. You could also do it using hibernate etc. Here is some code for a very simple class.....
Hemal



String conURL = "........";
// connection string based on your db, ip, username and password

try {

// Load the Driver class.
Class.forName("....");
// If you are using any other database then load the right driver here.

//Create the connection using the static getConnection method
Connection con = DriverManager.getConnection (conURL);

//Create a Statement class to execute the SQL statement
Statement stmt = con.createStatement();

//Execute the SQL statement and get the results in a Resultset
ResultSet rs = stmd.executeQuery("select..........");

// Iterate through the ResultSet

while (rs.next()){
rs.getString("var1");
............

}
}
//Add all the exceptions here.....

catch (SQLException e) {
e.printStackTrace();
}
catch (Exception e) {
e.printStackTrace();
}
finally {
// Close the connection
con.close();
}
}
}




________________________________
From: Cisco Developer Community Forums [cdicuser@developer.cisco.com]
Sent: Saturday, May 05, 2012 12:55 AM
To: cdicuser@developer.cisco.com
Subject: New Message from Gerard O'Rourke in Customer Voice Portal (CVP) - General Discussion - All Versions: RE: CVP Database Action Element

Gerard O'Rourke has created a new message in the forum "General Discussion - All Versions":

--------------------------------------------------------------
Trying again....

Anyone have a Database decision Element they want to 'share' that handles DB failures, to use instead of the 'out of the box' Database Action Element which does not.handle DB failures?

Gerard.
--
To respond to this post, please click the following link:

<http://developer.cisco.com/web/cvp/forums/-/message_boards/view_message/5563266>

or simply reply to this email.

If you want something very simple, you could compile this - it's just the Studio Database element with a catch handler to catch all exceptions.
It creates element data named 'status' with the value 'success' or 'failure'

//These classes are used by custom configurable elements.
import com.audium.server.AudiumException;
import com.audium.server.voiceElement.ElementInterface;
import com.audium.server.voiceElement.Setting;
import com.audium.server.voiceElement.ElementData;
import com.audium.server.voiceElement.ElementException;
import com.audium.server.xml.ActionElementConfig;

// This class is used by action elements.
import com.audium.server.action.database.DatabaseAction;
import com.audium.server.session.ActionElementData;

public class JaninesDatabaseElement extends DatabaseAction implements ElementInterface
{
public String getElementName()
{
return "JaninesDatabase";
}

public String getDisplayFolderName()
{
return "Janines Elements";
}
public String getDescription()
{
return "This element executes the Studio Database Element but catches Java Exceptions.\n" +
"It creates Element data named 'status' with value 'success' or 'failure' ";
}

public void doAction(String name, ActionElementData actionData) throws AudiumException
{
String status = "success";
try {
super.doAction(name,actionData);
} catch (Exception e) {
status = "failure";
}
actionData.setElementData("status",status);
}
}