user manual

258 BES Developer’s Guide
Configuring admin objects
userPassword=String
address=String
Service management for supported and other JMS
providers
Service management is handled by the BES service control infrastructure.
JMS service processes like starting, stopping and server configuration are
provided in the managed object configuration for supported (Tibco and Sonic)
JMS providers out of the box. This level of pluggability for other JMS providers
can be achieved with some configuration.
Other JMS providers
The following steps are required for introducing a JMS server other than Tibco
or Sonic into BES:
1 If the main entry into the JMS server is through a Java class, and you are
required to shut down the server using a management API, proceed to step
2 (to create a runner). Otherwise, go to step 3 (to create a launcher).
2 A runner works in conjunction with BES, a launcher to provide a graceful
shutdown. Refer to the Sonic5Runner class as an example implementation
of a runner. A runner is required to implement the two methods below:
■
public static main(String[] argv): starting the server
■
public static cleanup(boolean b): shutting down the server
3 A launcher is consisted of an executable and a config file. The executable
files are all identical. In Windows, you can make a copy of partition.exe and
give it a new name.
4 Make a config file with the same name as the executable created in step 3.
5 Populate the config file with the required runtime properties for the JMS
server. The runtime properties are usually in a .bat file. Refer to
launcher.html in \JSoft\IAS\src\share\native for more details. You can also
refer to sonicmq.config (in <install_dir>\bin) for an example of runtime
properties.
6 Create a config file similar to tibco.config or sonic.config, which are located
in <install_dir>\bin\. Include all the client and admin JARs for the JMS
server.
7 Modify the jms.config file, located in <install_dir>\bin, setting the JMS
provider as the new one being added.
8 Create a Managed Object and include it in the configuration.xml file. If the
new JMS server is a native server, use Tibco MO as an example. The Tibco
MO is located in <install_dir>\var\templates\managed_objects\jms. If the new
JMS server is an all Java server, use the Sonic MO as an example, which is
located in the same file as Tibco MO.