...

Global JMS Connection Properties

When creating a large test suite with multiple tools, there may be instances where some tools (i.e. SOAP Client, Messaging Client, and Call Back Tool) will use the same JMS Connection Properties. You might want multiple tools to use the same JMS Connection Properties.Rather than manually entering the same information into each tool or copying and pasting settings between tools, it may be easier to create JMS settings that each tool can reference. In this case, you can create global JMS Connection Properties at the test or action suite level. To create global JMS Properties, complete the following:

1. Select the desired node and click the Add Property button.

2. In the Add Global wizard, choose Global Property> JMS Connection Properties and click Finish. A Properties node displays and the JMS Connection Properties panel displays in the right side of the GUI.
3. Specify the settings in the JMS Connection Properties panel:
   1. (Optional) Enter the new name in the Name field. The name will appear in the tools that reference these properties. You can create more than one global reference for JMS Connection Properties, so the names you specify should be intuitive to how it's used.

   2. Click the Add Property to All button. If you don’t click this button, the global properties you add will be ignored by the tools in the suite. If Use Shared Property Only is selected from the drop-down list, the corresponding tools in the suite will be able to only use the global property you added and any properties configured within the individual tooladded.

   3. In the Provider URL field, specify the location of the JMS Administered Objects. 
   4. In the Initial Context field, specify the Java class that contains all the JMS properties mappings.
   5. In the Connection Factory field, specify the key used to look up the MOM-specific factory from the initial context. This can be either a Queue Connection Factory or a Topic Connection Factory.
   6. In the Authentication area, select the Perform Authentication check box and enter the Username and Password to authenticate the request. If the correct username and password are not used, the request will not be authenticated.

...

As with global JMS properties, there may be instances when you have multiple Diff tools that use the same XPath settings.You might want multiple Diff tools to use the same XPath settings.Rather than manually entering the same information into each Diff tool or copying and pasting settings between Diff tools, it may be easier to create XPath settings that each Diff tool can reference. In this case, you can create global XPath Properties at the action or test suite level.

...

When creating a large test suite with multiple tools, there may be instances where SOAP Client tests will use the same SOAP Header Properties.You might want multiple tools to use the same SOAP Header Properties.Rather than manually entering the same information into each tool or copying and pasting settings between tools, it may be easier to create SOAP Headers that each tool can reference. In this case, you can create global SOAP Header Properties at the test or action suite level.

...

Global Database Account Properties

When creating a large test suite with multiple tools, there may be instances where DB tools will use the same Database Properties. You might want multiple tools to use the same Database Properties.Rather than manually entering the same information into each tool or copying and pasting settings between tools, it may be easier to create a Database Account that each tool can reference. In this case, you can create global Database Account Properties at the suite level.

...

1. Select the desired suite and click the Add Property button.

2. In the Add Global wizard, choose Global Property> Database Account and click Finish. A Properties node displays and the Database Account panel displays in the right side of the GUI.
3. Specify the settings in the Database Account  panel as follows:
   1. If you want to change the default name, enter the new name in the Name field.

   2. Click the Add Property to All button (if you don’t click this button, the global properties you add will be ignored by the tools in the suite). Depending on what you select from the drop-down list, one of the following will occur:

      • If Use Shared Property Only is selected from the drop-down list, the corresponding tools in the suite will be able to only use the global property you added.

      If Use Local and Shared Properties is selected from the drop-down list, the corresponding tools in the Action suite will be able to

      • use the global property you added

      and any properties configured within the individual tool itself

      • .

   3. Configure the rest of the Database Account settings as needed.
      • If the account settings are stored in a file, select File then specify the path to that file.
        
        • To refresh/reload the file (e.g., if you edited it externally), click Refresh Configuration Settings.

      • If you want to specify the settings in this panel, enable Local and specify the driver settings. See 

        Database Configuration Parameters in SOAtest or Database Configuration Parameters in Virtualizefor additional information.

        • To export these values to a file, click Export Configuration Settings. Once the values are exported to a file, you can import the file through the File> Input File control (described above). This way, you won’t have to re-type the same values if you want to add this same account to a different suite. 

          Note that exported properties files contain the following properties:

          • driver
          • url
          • username
          • password
          • close.connection

          For example:

          version=1
driver=org.hsqldb.jdbcDriver
url=jdbc:hsqldb:hsql://localhost/parabank username=sa
password=dGVzdA==
close.connection=true

          


...