Provisioning the subscriber into the subscription framework

Configure the subscription framework with your subscribers class name. Optionally, you can configure an initialization string and an investigation to event mapping table.

To provision the subscriber into the subscription framework:

1. Run the following SQL commands on the IBM FCI for Insurance system:

   INSERT INTO CFCONFIG.SUBSCRIBE (NAME, DESCRIPTION, SUBSCRIBE_TARGET, AUDIT, INIT_STRING, AUTOSTART) VALUES 
   ('Subscriber Name','Subscriber Desc','fully.qualified.class.name.of.subscriber.in.jar.file',1,'Initialization String passed 
   to this Subscriber. Could be in form: host=some_host;port=some_port;interval=15;etc...','1');

   NAME

   Specifies the name of your subscriber. This value does not have to be unique.

   DESCRIPTION

   Specifies the description for your subscriber. This value does not have to be unique.

   SUBSCRIBE_TARGET

   Must match the fully qualified Java™ class name of your subscriber class.

   AUDIT

   Must be the value 1.

   INIT_STRING

   Specifies the initialization string that is passed to your subscriber. Your subscriber has access to this string by using the getInitializationString() method. You can pass connection data that your subscriber needs in this string.

   AUTOSTART

   Enables automatic startup of subscribers when IBM FCI for Insurance Management is started. For individual subscribers, the SUBSCRIBE_ID or SUBSCRIBE_TARGET must be known. Valid values are as follows:

   1

   Enables subscribers in the IBM FCI for Insurance database to start automatically. For example, to enable a subscriber to start during IBM FCI for Insurance startup:

   UPDATE CFCONFIG.SUBSCRIBE SET AUTOSTART = '1' WHERE SUBSCRIBE_ID = n
   UPDATE CFCONFIG.SUBSCRIBE SET AUTOSTART = '1' WHERE SUBSCRIBE_TARGET = 'classname' 

   0 or NULL or no value specified

   Disables subscribers in the IBM FCI for Insurance database from starting automatically. For example, to prevent all subscribers from starting during Counter Fraud Management startup:

   UPDATE CFCONFIG.SUBSCRIBE SET AUTOSTART = '0' WHERE SUBSCRIBE_ID = n

2. Run the SQL script, which inserts a record into the CFCONFIG.SUBSCRIBE table. A unique subscriber ID is generated for the SUBSCRIBE_ID column.
   Attention: If your subscriber uses the investigation mapping capability of the subscription framework, you must provision the investigation to event mapping. The investigation to event mapping is configured on a per-subscriber basis. You must know the SUBSCRIBE_ID created for your subscriber to create an investigation to event mapping. To view the list of subscribe IDs and the associated Java class names, run the following SQL statement:

   SELECT SUBSCRIBE_ID,SUBSCRIBE_TARGET FROM CFCONFIG.SUBSCRIBE;

   You can use either of the following SQL command formats to provision the investigation to event mapping for your subscriber. If you know the event and investigation ID, use the ID-based format. If you prefer to use stereotypes, use the stereotype-based format.

   The sample SQL assumes that your subscribe_id is 47, and that you want to map a fire investigation to an accident event. Adjust the values according to the events and investigations that are configured on your IBM FCI for Insurance system. A subscriber's investigation to event map can have multiple entries. Run the SQL script for each mapping.

   -- ID version:
   INSERT INTO CFCONFIG.SUBSCRIBE_ALERTS (SUBSCRIBE_ID,ALERT_TYPE_ID,RESULTING_EVENT_TYPE_ID) VALUES (47, 1, 2);
   
   -- Stereotype version:
   INSERT INTO CFCONFIG.SUBSCRIBE_ALERTS (SUBSCRIBE_ID,ALERT_TYPE_ID,RESULTING_EVENT_TYPE_ID) VALUES (
   47,
   (SELECT ALERT_TYPE_ID FROM CFCONFIG.ALERT_TYPE WHERE STEREOTYPE = 'fire'),
   (SELECT EVENT_TYPE_ID FROM CFFACT.EVENT_TYPE   WHERE STEREOTYPE = 'accident')
   );