Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Description

In this scenario, we will illustrate the sequence of events necessary to prepare our data integration for local-based development which is the first step in performing customizations.

The following are the list of steps for this scenario:

 

Table of Contents

Prerequisites

In order to be able to complete this laboratory exercise, please complete the prerequisite lab(s) before proceeding.

  • PlatformManager access

  • An existing IM instance

  • Access privileges for:

    • Partition creation

    • Git repository

    • Pricefx Maven repository

  • Partition Connection

  • SFTP Connection

  • One functioning Route

  • WinSCP FTP Client or equivalent

Step 1: Connect to IM Instance

Prior to local development, we will need to follow the path from the IM instance within PlatformManager to the Git repository that contains the contents of our integration project. Our goal will be the to open the Git repository linked to our IM instance.

  1. Go to platform.pricefx.com and choose the Login with O365 option:

...

Image Added

 2. Click on the Integrations option (left-hand side):

...

Image Added

3. From the list of integration instances, create a filter to locate your IM instance:

Image Modified

4. Locate your IM instance and click on it, this will open the IM instance page:

Image Modified

On the left-hand navigation, we will see all options related to this instance:

Image Modified
Info

NOTE: We have selected our single IM instance and all of this options (Routes, Mappers, Connections, etc) are reflective of this single instance.

5. Next, we will open the Git repository linked to this IM instance:

Image Modified
Info

NOTE: The creation of IM instance will automatically build a corresponding Git repository that will then contain all of the generated elements that are linked to this instance.

6. Click on the Git repository link to open the Git project:

...

Image Added

Examine what is provided, click on the src/main folder and then open the resources folder:

...

Image Added
Info

NOTE: These are the properties files that will provide values for numerous variables that are then used in the different generated XML files that are performing our integration processes.

7. Click repo folder, this will show all of the folders for the different types of integration elements that are components (connections, routes, etc) of this IM instance:

Image Modified

Step 2: Clone to Local

Our objective in this step is to customize the generated XML and Json code associated with our IM instance and the first step in that process is to clone this project to our local machine.

  1. Click on the Clone option:

Image Added

2. Next, click on the Copy URL option to copy the URL path.

3. Then, we will open IntelliJ and use the File | New | Project from Version Control to connect to our remote Git repository:

Image Added

4. Next, this will display the Get from Version Control panel and we will paste the URL path:

Image Added

Click on the Clone button.

5. The project has now been cloned to our local machine and this local instance is connected to our remote repository in gitlab.pricefx.eu.

6. Next, we need to switch to the dev branch within Git and in that branch we will perform all of our updates and modifications to the code. In the lower right-hand corner we can select the remote dev branch:

Image Added

Then we will choose the Checkout option.

7. Next, lets verify that we have successfully cloned the dev branch from the remote repository to our local machines. So, within Intellij lets open folder path of src/resources/repo and it will appear as:

Image Added

8. Next, open the Connections folder to view our connection files:

Image Added

9. As an example, we can open one of the connection Json files. It will appear as:

Image Added

10. Next, open the Routes folder to view our route files:

Image Added

11. It does appear that we have successfully cloned our IM instance Git project to our local machine. We can verify this by comparing the Git folders in src/main/resources/repo to those in Git:

Image Added

Image Added