Prerequisites for Setting Up External Search/Match

While your current Search/Match setup can remain unchanged, it is recommended that you review it to maximize the search capabilities offered by the external system. For example, if the external system that integrates with External Search/Match does not store National ID information, you could remove this information from your search parameters.

• Search Parameter: Additional Search Parameter codes may need to be created for external system integrations with data hubs to accommodate how the transformation layer evaluates the search parameter used and the various Search Order Numbers.

  Note: External Search/Match includes in the Match Request only the Search Order Numbers for which potential matches can be found (this is the same concept used by Search/Match).

• Search Results: If your results code(s) contain fields that are not stored inside your integrated external system, and if the person returned has an EmplID in the CS system, the Results Engine fetches the data inside the CS database to populate the Results tab.

  For example, a user uses a Search Results code that contains the Aid Year field. If your external system does not store that information, the Results Engine uses the returned EmplID to fetch the CS database and retrieve the information. This is also true for matching candidates returned with an EmplID. If the matching candidate is not stored in the CS database (no EmplID exists), then the Aid Year column remains blank for that candidate.

• Search Results code masking configuration: The system reuses the existing setup when you use a Search Results code with masking configuration and the external system returns results for display.

In addition, you must set up Integration Broker to trigger the following web services:

• SCC_SM_FETCH (Search/Match fetch service).

• SCC_SM_SERVICE (External Search/Match service).

Finally, you must grant users security to the Search/Match Integrated component.