Customer 360 for Healthcare > Configuring Customer 360 for Healthcare for source system integration > Configuring Customer 360 to process data from NPPES in batches
  

Configuring Customer 360 to process data from NPPES in batches

Configure Customer 360 to integrate Customer 360 with NPPES and process data from NPPES in batches. Import the assets related to NPPES into your organization.
Note: Before you import the assets related to NPPES, ensure that you import the data model related to the extension, the predefined custom pages, and the source system.
To configure Customer 360, perform the following tasks:
    1Import the Cloud Data Integration assets related to NPPES.
    2Import the job assets.
    3Add the lookup files related to NPPES in the Secure Agent machine.
    4Import the parameter files.
    5Configure the flat file connection.
    6Configure the Business 360 FEP connector.

Importing the Cloud Data Integration assets

Import the Cloud Data Integration assets related to the source system, such as predefined taskflows, mapping tasks, and mappings. Create import and export jobs based on the predefined taskflows.
    1In Data Integration, click Explore > Import.
    2Navigate to the following file:
    <Extracted extension package>/2_DI_Assets/<Source system>_DI_Assets.zip
    3Click Open.
    The Import Assets page lists the assets in the file.
    4Ensure that all the assets are selected, and then select Publish Taskflow(s) after import.
    5Click Import.
    6On the My Import/Export Logs page, verify whether the import job is successful.

Importing the job assets

After you import the Cloud Data Integration assets, import the job assets related to the source system. Use batch jobs to ingress records from and egress the processed records to the source system.
    1In Business 360 Console, click Explore > Import.
    2Navigate to the following file:
    <Extracted extension package>/3_MDM_Job_Assets/<Source system>_Job_Assets.zip
    3Click Open.
    The Import Assets page lists the assets in the file.
    4Ensure that all the assets are selected, and click Import.
    5On the My Import/Export Logs page, verify whether the import job is successful.

Adding lookup files

Add the lookup files related to NPPES in the Secure Agent machine.
    1Navigate to the following directory:
    <Extracted extension package>\Secure Agent Files\Lookup Files\NPPES
    2Copy the following files to the local directory where you store the flat file connection:

Importing parameter files

Import the list of user-defined parameters and their associated values for Cloud Data Integration mappings.
To import parameter files, save the parameter files in the Secure Agent Installation directory.
Copy the parameter files from the source directory to the target Secure Agent installation directory:
Source: <Extracted extension package>\Secure Agent Files\Parameter Files\<Source System>
Target: <Secure Agent Installation Directory>\apps\Data_Integration_Server\data\userparameters
Optionally, if you want to use a configured path for the target location, see Parameter file location.

Using the parameter files

A parameter file is a list of user-defined parameters and their associated values. Use parameter files to define values that you want to update without having to edit the mapping task. The parameter values are applied when the task runs.
The Customer 360 for Healthcare package contains the following parameter files in the Secure Agent files directory for the Cloud Data Integration mappings:
For more information about importing the parameter files, see Importing parameter files.

Configuring the flat file connection

To access flat files from the Secure Agent, configure the flat file connection.
    1In Administrator, click Connections.
    2Click infac360ls_conn_flatfile.
    3Verify the directory to store the flat file.
    Default is C:\ReferenceData.
    4Test the connection, and ensure that the connection is successful.

Configuring Business 360 FEP connection

You can use the Business 360 FEP Connector to write data from the source system into MDM SaaS. If the input values for source system integer fields are null, the Business 360 FEP Connector converts the null values to 0 in MDM SaaS.
    1In Administrator, click Connections.
    2Click infac360hc_conn_customer360.
    3Test the connection.
    The connection might fail with the following error:
    The test connection for infac360hc_conn_customer360 failed. Unable to fetch connector attributes, Ensure adapter ID is valid[com.infa.adapter.mdmflat].
    4If the connection fails, verify and ensure that the connection is successful.
    1. aVerify the license used.
    2. bEnsure that the connector is enabled for the Secure Agent group.
    3. cRestart the Secure Agent.