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

Configuring Customer 360 to process data from MedPro Systems in batches

Configure Customer 360 to integrate Customer 360 with MedPro Systems and process the Customer 360 records with data from MedPro Systems in batches.

Import the assets related to MedPro Systems into your organization. The assets include Data Integration and Application Integration assets. To import the assets, you require the license to access MedPro Systems.

Note: Before you import the assets related to MedPro Systems, ensure that you have imported the data model related to the extension, the predefined custom pages, and the source system.

To configure Customer 360, perform the following tasks:

1Add a user group in Administrator for MedPro Systems.
2Import the Cloud Data Integration assets related to MedPro Systems.
3Import the job assets.
4Import the Cloud Application Integration assets related to MedPro Systems.
5Configure the service connector and the application connection.
6Publish the Application Integration process.
7Add the lookup files related to MedPro Systems in the Secure Agent machine.
8Set the environment variable for the operating system to the extracted folder of the MedproIntegration.zip file.
9Set the Secure Agent parameters.
10Import the parameter files.
11Configure the flat file connection.
12Configure the Business 360 FEP connector.

Adding a user group

Add a user group and enable privileges for the user group.

1In Administrator, click User Groups > Add Group.

2On the New Group page, enter the following name:

Medpro_Api_Group

3In the Group Members section, assign users from the available users.

4In the Assigned Roles section, enable the following privileges:

- Business Manager
- Customer 360 Data Steward
- Data Integration Task Executor
- Data Preview
- Data Viewer
- Deployer
- Designer
- Job Executor
- MDM Business User
- MDM Designer
- Monitor
- Operator
- Reference 360 Business Analyst
- Reference 360 Business Steward
- Reference 360 Planner
- Reference 360 Primary Owner
- Reference 360 Stake Holder
- Reference 360
- Service Consumer

5Click Save.

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.

Importing the Cloud Application Integration processes

After you import the job assets, import the Cloud Application Integration processes related to the source system.

1In Application Integration, click Explore > Import.

2Navigate to the following file:

<Extracted extension package>/4_CAI_Assets/<Source system>_CAI_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.

Configuring connectors

To integrate with the source system, configure the service connector and the application connection.

1In Application Integration, click Explore > Customer360 > Life Sciences Extension.

2Click the infac360ls_connector_medpro_trigger_ingress service connector.

3In the Connection Properties section, update the following details:

- Host name. To get the host name of the application, perform the following steps:

1In Data Integration, click Explore > Customer360 > Life Sciences Extension.
2Select the infac360ls_tf_medpro_read_write_Filename_local taskflow.
3Expand the Actions menu, and select Properties Detail.
4Get the host name from the service URL endpoint.

- User name. The user name to connect to the Informatica Intelligent Cloud Services (IICS).
- Password. The password associated with the user name.

4Click Save.

5Publish the connector.

6In the left pane, click Explore > Customer360 > Life Sciences Extension.

7To publish the following application connections, select the following application connections and repeat steps 3 through 5.

- infac360ls-appConn-medpro-trigger-ingress
- infac360ls-appConn-sftp-medproOutbound-InboundHCP-HCO

Publishing the Cloud Application Integration process

To run the Cloud Application Integration process, publish the process.

1In Application Integration, click Explore > Customer360 > Life Sciences Extension.

2Click the process.

Select the following processes based on how you choose to run the trigger:

Trigger	Process
Auto	infac360ls_process_medpro_auto_trigger_ingress
Manual	infac360ls_process_medpro_manually_trigger_ingress

3Publish the process.

Adding lookup files

To import reference data CSV files to the Secure Agent, add the lookup files related to MedPro Systems in the Secure Agent machine.

1Navigate to the following directory:

<Extracted extension package>\Secure Agent Files\Lookup Files\MedPro

2Copy the following files to the local directory where you store the flat file connection:

- IdentifierStatus.csv
- stateCdConversion.csv

3Navigate to the Medpro file in the following directory:

<Extracted extension package>/Secure Agent Files/Medpro

4Extract the file for your operating system:

- Linux. \Linux\MedproIntegration.zip
- Windows. \Windows\MedproIntegration.zip

Setting up the environment variable

Set the environment variable for the operating system to the extracted folder of the MedproIntegration.zip file.

On Windows, configure the environment variable on the system settings page.

1On the Windows taskbar, right-click the Windows icon and select System.

The Settings page appears.

2Click Advanced system settings.
3On the Advanced tab, click Environment Variables.
4To create the infac360ls_medpro_dir environment variable, perform the following steps:

aClick New.
bAdd the path to the MedproIntegration directory.

For example, C:\MedproIntegration

cClick Apply > OK.

5To modify an existing environment variable, perform the following steps:

aClick Edit and modify the existing environment variable.
bClick Apply > OK.

On Linux, run the following command:

$ export infac360ls_medpro_dir="<MedproIntegration_folder_path>"

Setting up the Secure Agent parameters

After you set the environment variable for the operating system, set the Secure Agent parameters.

1In Administrator, click Runtime Environments.

2Expand the Actions menu for the Secure Agent, and select Edit Secure Agent.

3In the Custom Configuration Details section, enter the following details:

Field Name	Value
Type	DTM
Name	SFTP_MaxWriteSize
Value	8192

4To save the custom configuration of the Secure Agent, click OK.

The Secure Agent restarts automatically within 10 minutes. To apply the properties immediately, you can restart manually. To avoid failure of any running task, ensure that no tasks run .

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 infac360ls_mt_medpro_hcp_inbound.param 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.

aVerify the license used.
bEnsure that the connector is enabled for the Secure Agent group.
cRestart the Secure Agent.