Before you run a JMS Adapter broker instance as a service, you must configure AdminServer with the appropriate JMS Adapter plugin entries. These entries allow AdminServer to identify the broker instance and manage it using the adaptman utility.

To configure AdminServer plugin entries for running the JMS Adapter broker instance as a service, complete the following steps:
  1. Stop the AdminServer if it is running. For details on checking the AdminServer status, see Query the AdminServer and for details on stopping the AdminServer, see Stop the AdminServer.
  2. Create a text file with a .delta extension (for example, jmsadapter-adminserver.delta), and then add the required JMS Adapter plugin and plugin policy entries to it. For example, if you are using SonicMQ as a JMS provider, add the appropriate JMS Adapter plugin entries as follows: 
    #
# JMS Adapter AdminServer plugin configuration
#
 
[Plugin.SonicMQAdapter]
 dependency=Plugin.System,Plugin.UBPropMgr
 pluginpolicy=PluginPolicy.Progress.SonicMQ
 uniquetype=AD
 license=1048577
 classname=com.progress.ubroker.tools.adapter.AdapterGuiPlugin
 pluginargs=SonicMQ Adapter
 
[PluginPolicy.Progress.SonicMQ]
pluginclasspath=${DLC}/sonic/MQ14.0/lib/sonic_Client.jar,${DLC}/sonic/MQ14.0/lib/mgmt_client.jar,${DLC}/java/progress.jar
classpath=${DLC}/sonic/MQ14.0/lib/sonic_Client.jar,${DLC}/java/progress.jar,${DLC}/java/schema.jar,${DLC}/java/messages.jar,${DLC}/java/ext/bcpkix-jdk18on-*.jar,${DLC}/java/ext/bcprov-jdk18on-*.jar,${DLC}/java/ext/bcutil-jdk18on-*.jar
 
  3. Merge the text file into the AdminServer plugin configuration file, AdminServerPlugins.properties, using the mergeprop utility. For example:
    mergeprop -type plugin -action update -target
 AdminServerPlugins.properties -delta /path/to/jmsadapter-adminserver.delta
 
    Where /path/to/jmsadapter-adminserver.delta specifies the full path to the text file you created earlier.
  4. Open AdminServerPlugins.properties file and verify that the JMS Adapter plugin and its associated policy entries are present.
  5. Start the AdminServer so it picks up the new or modified broker instance. For details, see Start the AdminServer
AdminServer is now set up to identify the JMS Adapter broker instance and manage it as a service. You can proceed with starting and managing the broker instance using the adaptman utility.