Summary 

V2 Receivers are GenRocket Receivers that share the following features:

  1. They have the character V2 just before the word Receiver (e.g., GenericSQLInsertV2Receiver).

  2. They have been updated with two new specific parameters to manage better how they access resources on a local computer.
    • resourcePath
    • resourceSubDir

Detailed Explanation

By observing our GenRocket users, we noticed that many users often need to connect to multiple databases within their testing environments, adding new global resources within their organization. This creates two negative challenges to our platform and the user experience.

  1. Adding a new resource affects all users within an organization; not all users need to use the additional resource.

  2. Adding new resources unnecessarily complicates the management of the given resources when the resources are meant to accomplish the same task.

For example, if a user needs to connect to three different databases on their local computer, they would have to add two more global resources (e.g., resource.jdbc2.config and resource.jdbc3.config). A user would need to know which resource to use within a given Receiver, which binds the Receiver to a specific path and file on their local computer. 


But, what if the user has two different Project Versions, A and B respectively, and in Project Version B, the user wants to reference a different set of configuration files that were referenced in Project Version A? Well, the user can't modify the resources without affecting all Receiver database connections in Project Version A. The user would have to create three more resources, which won't scale.


So, enter the new V2 Receivers to resolve this issue. All V2 Receivers contain the following two new parameters: resourcePath and resourceSubDir.


resourcePath

By default, the resourcePath parameter references the new global resource variable, #{resource.jdoe.directory}. The global resource variable, resource.jdbc.directory, should only contain a base path where all configuration files are located. For example, you might define a path on your computer as /Users/userName/dbConfigs.


resourceSubDir

For best practices for defining and structuring resources subdirectories, see: 

How do I Structure Resource Subdirectories to Store Config Files?


The power of the V2 Receivers is that you will have the flexibility to create the directory structure you want with no significant management overhead to setting or modifying V2 Receiver parameters.


Lastly, we will eventually deprecate all Receiver V1 versions from our platform. It doesn't mean we're going to remove the V1 Receiver from our GenRocket Receiver Jar; it just means the V1 Receivers will no longer appear on our platform to be selected for use. Thus, all Scenarios that are currently using any V1 version Receiver will not be affected by the deprecation.