Including custom and hang-off entities for hub and organization-based configuration data (in config-db.xml)

Data Sync determines what configuration data tables to export based on the contents of the config-db.xml file found in the install_dir/database/cdt directory. If you want to include custom hub-level configuration tables, you must add them to the config-db.xml file. These tables are exported as part of the HubConfiguration table group.

1. In the config-db.xml file, add a new <Group> as a child of the existing <Group Name="Hub Data">. For example:

   <Group Name="Custom Tables">
      <Table Name="CUSTOM_CONFIG_TABLE_1">
      <Table Name="CUSTOM_CONFIG_TABLE_2">
   </Group>
   

2. Navigate to the install_dir/bin directory.
3. Create the resource jar by running the following command:

   For Windows: deployer.cmd -t resourcejar

   For Linux/UNIX: deployer.sh -t resourcejar

4. Rebuild and deploy the Enterprise ARchive (EAR) file.

If you want to include a custom organization-based configuration table (that is, extend a table that is itself a child of YFS_ORGANIZATION), you must add it to the config-db.xml file. For example, the following instructions describe how to extend YFS_USER_GROUP.

1. In the config-db.xml file, locate the section <Group Name="Organization Based Configuration Data">
2. Locate YFS_USER_GROUP within this section. For example:

   <Group Name="UserGroup">
      <Table Name="YFS_USER_GROUP">
         <Table Name="YFS_DATA_ACCESS_POL_OVERRIDE"/>
      </Table>
   </Group>

3. Add the new table as a child of YFS_USER_GROUP. For example:

   <Group Name="UserGroup">
      <Table Name="YFS_USER_GROUP">
         <Table Name="YFS_MY_CUSTOM_TABLE"/>
         <Table Name="YFS_DATA_ACCESS_POL_OVERRIDE"/>
      </Table>
   </Group>

4. Navigate to the install_dir/bin directory.
5. Create the resource jar by running the following command:

   For Windows: deployer.cmd -t resourcejar

   For Linux/UNIX: deployer.sh -t resourcejar

6. Rebuild and deploy the Enterprise Archive (EAR) file.