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.
Go to platform.pricefx.com and choose the Login with O365 option:
2. Click on the Integrations option (left-hand side):
3. From the list of integration instances, create a filter to locate your IM instance:
4. Locate your IM instance and click on it, this will open the IM instance page:
On the left-hand navigation, we will see all options related to this instance:
| 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:
| 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:
Examine what is provided, click on the src/main folder and then open the resources folder:
| 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:
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.
Click on the Clone option:
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:
4. Next, this will display the Get from Version Control panel and we will paste the URL path:
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:
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:
8. Next, open the Connections folder to view our connection files:
9. As an example, we can open one of the connection Json files. It will appear as:
10. Next, open the Routes folder to view our route files:
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:
Step 3: Password Updates
Before we can run our integration processes locally, we will need to update the encrypted passwords with actual clear text passwords.
First, we will need to locate the connections being used by our integration instance. Open the folder path src/main/resources/repo/connections:
2. There are two different types of connection files that will need to be updated. One for the SFTP connection and the other for the partition.
3. When we open our connection JSON file we should find an encrypted password:
4. We will need to update the connection passwords with the clear text versions that were provided (via email) when the integration instance was created.