Configuring execution units (XU) to connect to a TCP/IP management server

After you configure the Rule Execution Server management EAR to activate the TCP/IP management mode, you configure Java™ SE or Java EE XU instances to connect to the server.

About this task

To configure an instance of a Java SE or Java EE execution unit so that it connects to the started TCP/IP management server, you edit the ra.xml deployment descriptor to locate the Management plug-in.

Procedure

  1. Open the file <InstallDir>/executionserver/bin/ra.xml file in a text editor.
  2. Modify the Plugins section:
    Replace the config-property-value element:
    <config-property>
      <config-property-name>Plugins</config-property-name>
    	  <config-property-type>java.lang.String</config-property-type>
      <config-property-value>
          {pluginClass=Management,xuName=default,
          {pluginClass=DVS},{pluginClass=HTDS}
      </config-property-value>
    </config-property>
    with the following code:
    <config-property-value>
       {pluginClass=Management,xuName=default,
        protocol=tcpip,tcpip.port=TCPIP_PORT,
        tcpip.host=RES_CONSOLE_HOST,
        tcpip.retryInterval=INTERVAL},
       {pluginClass=DVS},
       {pluginClass=HTDS}
    </config-property-value>
    where
    • RES_CONSOLE_HOST is the host on which the Rule Execution Server console is deployed.
    • TCPIP_PORT is the TCP/IP port on which the Rule Execution Server console management server is listening.
    • INTERVAL is the interval of time, in milliseconds, during which the console waits before trying to reconnect to the management server if a connection fails.

    For ease of use, the XU-related plug-ins are identified by their corresponding aliases.

    For a runtime configuration, the build file is likely to include global variables:
    <res-setup XUConfigInput="${project.build.directory}/ra.xml" XUConfigOutput="${ra.copy.directory}/ra.xml">
       <property name="plugins"
                 value="{pluginClass=DVS},{pluginClass=Management,xuName=default,protocol=tcpip,tcpip.port=PORTNUMBER,tcpip.host=HOSTNAME,tcpip.retryInterval=1000}" />
    </res-setup>
    Note:

    The Hostname parameter must refer to the host name of the server where the console is deployed.

  3. Declare xu.plugins in <InstallDir>/executionserver/bin/ressetup.xml as follows:
    <target name="setup">
      .
      .
      <property name="xu.plugins" value=""/>
      .
      <res-setup...
      .
      .
        <property name="plugins" value="${xu.plugins}"/>
      </res-setup>
    </target
  4. Run the following Ant task:
    ant -Dxu.in= {IN_rar}
        -Dxu.out={OUT_rar}
        -Dxu.plugins="{pluginClass=DVS},{pluginClass=Management,xuName=default,protocol=tcpip,tcpip.port=PORT_NUMBER,tcpip.host=HOSTNAME,tcpip.retryInterval=1000}"
        -f ressetup.xml setup

    where IN_rar is the location of the original XU in <InstallDir>/executionserver/applicationservers and OUT_rar the new XU to deploy.