Install a custom inbound integration

PolicyCenter uses a custom inbound integration to read information that an external system creates and that is neither a file nor a JMS message. This integration can be either a message reply plugin or a startable plugin.

Procedure

  1. In the Project window, navigate to configuration > config > integration, and open the file inbound-integration-config.xml.
  2. Configure the thread pools.
    You can use a thread pool element in the base configuration as a template.
  3. In the list of integrations, create one <integration> element of type <custom-integration>.
    You can use a <custom-integration> element in the base configuration as a template.
  4. Set configuration parameter subelements.
  5. Create the custom inbound integration plugin.
    1. In Studio, in the Plugins registry, add a new .gwp file.
    2. Studio prompts for a plugin name and plugin interface. For the plugin name, use a name that represents the purpose of this specific inbound integration. For the Interface field, enter one of the following values.
      • For a message reply plugin, type InboundIntegrationMessageReply.
      • For a startable plugin for non-messaging use, type InboundIntegrationStartablePlugin.
    3. Click the plus (+) symbol to add a plugin implementation and choose the class type that you implemented.
    4. For a Gosu or Java plugin, in the Gosu class or Java class field, type the fully qualified name of your plugin implementation class. For an OSGi plugin, in the Service PID field, type the fully qualified Java class name of your OSGi implementation class.
    5. Add a plugin parameter with the key integrationservice. For the value, type the unique name for your integration that you used in inbound-integration-config.xml for this integration.
  6. Start the server and test your new inbound integration. Add logging code as appropriate to confirm the integration.

What to do next

See also