Database connection per environment

Hello,

Unfortunately this is a known bug and we are working on fixing it. Bug tracking number: SOAP-1210. Below is a work around that you can place in one of the event handlers on the Project level. If you have further questions please let me know.

   /* Work with more than one JDBC connection set per environment, also does not modify connection strings when JDBC TestStep is not configured using a Project-Level JDBC connection */

    // Iterate all test steps in the test case and change connectionString for all ProJdbcRequestTestStep to the selected environment connectionString.

    for(testStep in context.testCase.getTestStepList())
    {

    // Set the connectionString for all ProJdbcRequestTestStep
    if(testStep instanceof com.eviware.soapui.impl.wsdl.teststeps.ProJdbcRequestTestStep)
    {
    // Get databaseName
    def databaseName = testStep.getJdbcRequestTestStepConfig().getDbConnectionName()
    if(databaseName != null)
    { 

// Get connectionString of active environment 
 
 def connectionString = context.testCase.testSuite.project.activeEnvironment.databaseConnectionContainer.getDatabaseConnectionByName(databaseName).getConnectionString() testStep.setConnectionString(connectionString) 
 
 // Get connection password of active environment 
 
 def connectionPassword = context.testCase.testSuite.project.activeEnvironment.databaseConnectionContainer.getDatabaseConnectionByName(databaseName).getPassword() testStep.setPassword(connectionPassword) }

    }
    }

Regards,
Temil