Share this page

# Generic JMS agent settings

This dialog box enables you to configure the Service VirtualizationGeneric JMS agent. The agent handles communication between a client and a real or virtual service.

To access | From the main menu, select Tools > Options. Click Agents. Under JMS Generic, select a configuration.
Important information | For additional important configuration information, see the task Configure the Generic JMS agent. There are several instances of the JMS Generic agent pre-configured for connecting to the JMS of common Java application servers. You can define multiple configurations for each agent.
Relevant tasks | Configure agents Forward HTTP agent communication through an HTTP proxy
See also | Service Virtualization agents Examples:

User interface elements are described below (unlabeled elements are shown in angle brackets):

UI Element | Description
--- | ---
<left pane> | Displays the server configured for your project. Expand the server to display the available agents and configurations.
Add | Enables you to define additional configurations of the agent.
Delete | Deletes the selected configuration.
Duplicate | Creates an additional configuration of the agent by copying the selected configuration. You can then modify the configuration settings. Note: By default, the configuration is created with a sequential unoccupied port number.
Export | Saves the selected agent configuration as a file. The file is saved in the .agce file format, and can be imported to any Service Virtualization Server.
Export All | Exports all agent configurations on the selected server. The file is saved in the .agce file format, and can be imported to any Service Virtualization Server.
Import | Enables you to select an exported agent configuration file stored on the file system. The file is saved in the .agce file format, and can be imported to any Service Virtualization Server. If the configuration file you are importing contains multiple configurations, you can select which configurations you want to import. If you choose to import an agent configuration that is identical to a configuration that already exists on your server, you can choose to overwrite your existing configuration, or create a new, additional configuration.
Agent State | The current status of the agent. Values include Running, Not Running.
Test Configuration link | Tests the configuration based on the settings you select. If Service Virtualization identifies any problems in your configuration, the details are displayed.
Is Enabled | Turns the agent on and off.
Name | Enter a name for the configuration or accept the default name.
JNDI URL | The URL where the JNDI provider and the JNDI context with JMS resources is located, or parameters for non-JNDI connection.
Context Factory | The provider specific context factory class or a name of the class implementing com.hp.sv.jmsagent.impl.JmsProvider for non-JNDI connection. Sample values: JBoss AS: org.jnp.interfaces.NamingContextFactory Tibco JMS: com.tibco.tibjms.naming.TibjmsInitialContextFactory Weblogic AS: weblogic.jndi.WLInitialContextFactory WebSphere AS: com.ibm.websphere.naming.WsnInitialContextFactory Tibco JMS (non-JNDI): com.hp.sv.jmsagent.impl.ext.TibcoJmsProvider Amazon Simple Queue Service (non-JNDI): com.hp.sv.jmsagent.impl.ext.SqsJmsProvider
Class Path | The class path with all necessary JMS provider specific libraries for JMS implementation. Note: To ensure maximum compatibility, use the same JMS/J2EE jar libraries for the agent class path that are in use by the client application. If not possible, follow your application server documentation for selection of the correct J2EE/JMS libraries.
Username/Password | Optional credentials for the JNDI provider/registry. Select Show Password to display the password in this dialog box.
Trust Store File | Enables mutual SSL authentication. Enter the location of the JMS server's certificate, or certification authority which issued the server's certificate. The certificate must be in a Java key store (.jks) file. Available for JMS on a WebLogic server only.
Key Store File | Enables mutual SSL authentication. Enter the location of the single certificate and corresponding private key to use as the client certificate by Service Virtualization during communication. The certificate must be in a Java key store (.jks) file. Available for JMS on a WebLogic server only.

Examples:

Agent configuration for WebLogic 10.3

- JNDI URL: t3://czvm58.devlab.ad:7001/

- Context Factory: weblogic.jndi.WLInitialContextFactory

- Class Path:

  `C:\Temp\WL103\wlthint3client.jar`

  Note: The above sample used WebLogic Thin T3 Client. In case of issues, please use other Weblogic Client libraries (e.g. “WebLogic Full Client” using “wlfullclient.jar”). See chapter 2 of “Overview of Stand-alone Clients” in your “Oracle® Fusion Middleware Programming Stand-alone Clients for Oracle WebLogic Server 11g Release 1” documentation for more details.

Agent configuration for MQ-7.0.1.3 on WAS-6.1.0

- JNDI URL: corbaloc::czvm24.devlab.ad:2809/NameServiceServerRoot

- JNDI URL: corbaloc::czvm24.devlab.ad:2809/NameServiceServerRoot

- JNDI URL: corbaloc::czvm24.devlab.ad:2809/NameServiceServerRoot

- Class Path:

  `C:\Temp\WAS6\com.ibm.mq.jar;`

  `C:\Temp\WAS6\com.ibm.mq.jmqi.jar;`

  `C:\Temp\WAS6\com.ibm.mqjms.jar;`

  `C:\Temp\WAS6\com.ibm.ws.admin.client_6.1.0.jar;`

  `C:\Temp\WAS6\com.ibm.ws.runtime_6.1.0.jar;`

  `C:\Temp\WAS6\connector.jar;`

  `C:\Temp\WAS6\dhbcore.jar;`

  `C:\Temp\WAS6\fscontext.jar;`

  `C:\Temp\WAS6\ibmorb.jar;`

  `C:\Temp\WAS6\jms.jar;`

  `C:\Temp\WAS6\jndi.jar;`

  `C:\Temp\WAS6\ldap.jar;`

  `C:\Temp\WAS6\providerutil.jar`

Agent configuration for JBoss 6.0

- JNDI URL: jnp://[machine-name]:1099/

- Context Factory: org.jnp.interfaces.NamingContextFactory

- Class Path:

  `C:\Temp\JBAS6\concurrent.jar;`

  `C:\Temp\JBAS6\hornetq-core-client.jar;`

  `C:\Temp\JBAS6\hornetq-jms-client.jar;`

  `C:\Temp\JBAS6\jboss-client.jar;`

  `C:\Temp\JBAS6\jboss-ejb3-core-client.jar;`

  `C:\Temp\JBAS6\jboss-ejb3-ext-api.jar;`

  `C:\Temp\JBAS6\jboss-jms-api_1.1_spec.jar;`

  `C:\Temp\JBAS6\jboss-logging.jar;`

  `C:\Temp\JBAS6\jnp-client.jar;`

  `C:\Temp\JBAS6\netty.jar`

Agent configuration for Tibco EMS

- JNDI URL: tibjmsnaming://[machine-name]:7222

- Context Factory: com.tibco.tibjms.naming.TibjmsInitialContextFactory

- Class Path:

  `C:\Temp\tibco\lib\tibjms.jar;`

  `C:\Temp\tibco\lib\jms.jar;`

  `C:\Temp\tibco\lib\tibjmsadmin.jar`

Agent configuration for Tibco EMS - dynamic queues

- JNDI URL: tcp://[machine-name]:7222

- Context Factory: com.tibco.tibjms.naming.TibjmsInitialContextFactory (not used)

- Class Path:

  `C:\Temp\tibco\lib\tibjms.jar;`

  `C:\Temp\tibco\lib\jms.jar;`

  `C:\Temp\tibco\lib\tibjmsadmin.jar`

  Note: To enable support for Tibco EMS dynamic queues, open VirtualServiceDesigner.exe.config or HP.SV.StandaloneServer.exe.config and change the value of the jms.agent.extensions.enable option to true:

  `<add key="jms.agent.extensions.enable" value="true"/>`

Agent configuration for Tibco JMS (non-JNDI)

- JNDI URL: tcp://localhost:7222

- Context Factory: com.hp.sv.jmsagent.impl.ext.TibcoJmsProvider

- Class Path:

  `C:\temp\jms.jar;`

  `C:\temp\tibjms.jar`

Agent configuration for Amazon Simple Queue Service (non-JNDI)

- JNDI URL: eu-central-1

- Context Factory: com.hp.sv.jmsagent.impl.ext.SqsJmsProvider

- Class Path:

  `C:\temp\amazon-sqs-java-messaging-lib-1.0.5.jar;`

  `C:\temp\aws-java-sdk-core-1.11.106.jar;`

  `C:\temp\aws-java-sdk-sqs-1.11.106.jar;`

  `C:\temp\jmespath-java-1.11.106.jar;`

  `C:\temp\jms.jar;c:\temp\jackson-databind-2.9.8.jar;`

  `C:\temp\jackson-core-2.9.8.jar;`

  `C:\temp\jackson-annotations-2.9.8.jar;`

  `C:\temp\httpcore-4.4.10.jar;`

  `C:\temp\httpclient-4.5.3.jar;`

  `C:\temp\joda-time-2.8.1.jar`

Note: Use a region name as JNDI URL

Agent configuration for Software AG Universal Messaging

- JNDI URL: nsp://host:9000

- Context Factory: com.pcbsys.nirvana.nSpace.NirvanaContextFactory

- Class Path:

  `C:\sag-um-jms-lib\genericra.jar;`

  `C:\sag-um-jms-lib\javax.jms-api-2.0.1.jar;`

  `C:\sag-um-jms-lib\nClient.jar;`

  `C:\sag-um-jms-lib\nJMS.jar`

Agent configuration for Apache ActiveMQ Artemis

- JNDI URL: tcp://host:61616

- Context Factory: org.apache.activemq.artemis.jndi.ActiveMQInitialContextFactory

- Class Path:

  `c:\artemis-client\artemis-jms-client-all-2.17.0.jar`

  `c:\artemis-client\jndi.jar`

Note: Apache ActiveMQ Artemis does not have a JNDI Server. Instead, it relies on a client-side JNDI provider. To make this work, you need to create a properties file and add it to the jar file, which you then add to the classpath. For more details, see the Apache ActiveMQ Artemis documentation.

Agent configuration for Solace JMS

Supported in versions: 5.4.1 and later

- JNDI URL: host:55555

- Context Factory: com.solacesystems.jndi.SolJNDIInitialContextFactory

- Class Path:

  `c:\solace-cli\commons-lang-2.6.jar`

  `c:\solace-cli\commons-logging-1.1.3.jar`

  `c:\solace-cli\org.apache.servicemix.bundles.jzlib-1.0.7_2.jar`

  `c:\solace-cli\org.osgi.annotation-6.0.0.jar`

  `c:\solace-cli\sol-common-10.11.0.jar`

  `c:\solace-cli\sol-jms-10.11.0.jar`

  `c:\solace-cli\jms-1.1.jar`

- Username: user@VPN

Back to top

https://admhelp.microfocus.com Service Virtualization 8942
Tips to improve your search results... Service Virtualization Help Center SV Help 5.4-5.4.1 All View Local Help Center View Online Help Center back Go back in browser history forward Go forward in browser history Remove search highlights next topic Go to next topic previous topic Go to previous topic Print the current topic Version: