Need to know what files should be updated with JNDI and DB connection info for Call Studio DB connection to work

[Intellione01]

I am working on a new install of CVP Call Studio and trying to setup the environment correctly.  

Need to know what files should be updated in order for the Database element to connect to external database.  What files should the JNDI name be inserted?

I have in the Catalina_Home /context.xml, in the Server.xml, and the web.xml but not connecting.  Error: cannot find JNDI datasource

[bill.king1]

Did you restart the VXML services after making the changes?

[Intellione01]

this is a pc that only has the call studio application loaded Not connected to a lab where the vxml services would have been loaded. Will load all necessary services today. thanks much.

[janinegraves · Accepted solution]

Modify vxmlserver/tomcat /conf/context.xml and download the jdbc driver jar file from the internet, and put that into vxml server/tomcat/lib.

Restart vxml server.

[Intellione01]

thanks very much Janine. We were running this on a pc that did not have the vxml services running and this instance of Call Studio not connected to the vxml server. So it looks like I need to go thru the entire configuration and make sure it is connected to the vxml server/vxml services/tomcat/ and all services that should be running.

[janinegraves]

If using just Call Studio debugger to test the app, then modify context.xml and place the jdbc driver into:  c/cisco/callstudio/eclipse/plugins /com.audiumcorp.studio.debug.runtime/CATALINA_HOME/conf and lib directories. 

[Intellione01]

I did that: added the database attributes to the context.xml, server.xml and web.xml, and placed the drivers in the correct place. but getting error about not finding JNDI datasource:

context.xml

<Resource name="TELECOM_CC"
auth="Container"
type="javax.sql.Datasource" maxActive="50" minidle="30"
driverClassname="com.miscrosoft.sqlserver.jdbc.SQLServerDriver"
url="jdbc:sqlserver://TeleSTmgr_LSNR.mdco.health-partners.org:1433;databaseName=TELECOM_CC;user=;password;multiSubnetFailover=true"
/>
</Context>*** removed user and password for security***

[Intellione01]

here is snapshot of error.

[Intellione01]

what about the server.xml?  this is what I have for that:

  <Global JNDI resources
<Resource name="jdbc:sqlserver://TeleSTmgr_LSNR.mdco.health-partners.org:1433/TELECOM_CC;user=;password"
 auth="Container"
              type="javax.sql.DataSource"
              description="test Scheduling DB"
              factory="driverClassname="com.miscrosoft.sqlserver.jdbc.SQLServerDriver""
              pathname="conf/tomcat-users.xml" />

-->
  <GlobalNamingResources>
    <!-- Editable user database that can also be used by
         UserDatabaseRealm to authenticate users
    -->
 <Resource name="jdbc:sqlserver://TeleSTmgr_LSNR.mdco.health-partners.org:1433/TELECOM_CC;user=;password"
 auth="Container"
              type="javax.sql.DataSource"
              description="test Scheduling DB"
              factory="driverClassname="com.miscrosoft.sqlserver.jdbc.SQLServerDriver""
              pathname="conf/tomcat-users.xml" />

[janinegraves]

You shouldn't need to edit the server.xml file. Just context.xml

[janinegraves]

In the context.xml file, the attribute called name must begin with jdbc/ so... name="jdbc/TELECOM_CC".
Then in Call Studio, just use the part after the slash (TELECOM_CC)

[Intellione01]

Did a restart of the machine, after making changes to the context.xml files and getting same error:

[janinegraves]

1. There may be more information in the error log, please post the error log. CallStudio/eclipse/plugins/com.audiumcorp.studio.debug.runtime/AUDIUM_HOME/applications/appname/logs/errorlog

2. You may have to go and remove the custom info that you added to server.xml

3. You do NOT need to restart Studio, just stop/restart the Debugger when you make the changes

4. What version of Studio are you using? 12.0? 12.5?
I recall that in 11.6 there was a workaround needed to connect to SqlServer from the Debugger.

[Intellione01]

12.0

[Intellione01]

that error log is not writing.  folder is empty