Skip to content

Handling Non Layered Files

Overview

There are two main types of files in the customer-solution repository. They are,

There two main scenarios where the users have to handle non-layered/core files. They are,

  • When customizing core files.
  • When there are fixes done in core files as a temporary fix for a bug in a core file(s).

Customize core files

There can be scenarios that the user requires to customize files which are not supported for layering. (e.g. deploy.ini, rdf, report, solution set). Those file we called as non-layered files. So the Customer Solution repository can contain both layered and non layered customized files. By using any of the below mentioned options, it is possible to merge the changes that have been done, to resolve the impacts of customized core files in the customer solution repository.

Prerequisites

IFS Update Analyzer downloaded and installed on the users' workstation. The tool can be downloaded from the IFS Developer Portal

Option 1

After doing the analysis using ".upda" file, using the filter options in the update analyzer tool[1,2] user can filter the impacted core files as below(Figure 1.1).

  • Check the "Impacted Only" check box[1]
  • Select only the "Core" option from "Layers" field[2]
upd-filter-option
Figure 1.1 - Impact analysis option

"Copy files to workspace folder" option in the Update Analyzer tool can be used to copy the filtered list of files or all the impacted files to a different location(Figure 1.2).

  • Right click on a selected row
  • Click on the arrow next to "Copy filed to workspace folder" option[1]
  • Choose the "All Filtered Files" option[2]. Then all the impacted core files will be copied to the specified location.
upd-copy-option
Figure 1.2 - Copy files to a different location

Option 2

It is possible to merge the changes using a third-party tool, integrated to the update analyzer tool. User can integrate the third-party merge tool to the update analyzer tool using the gear icon located in the top bar of the tool. Then the users can merge the changes of the non-layered files easily.

integrate-merge-tool
Figure 1.3 - Integrate a merge tool to Update Analyzer tool

To merge using the integrated merge tool

  • Right click on a selected row
  • Select "Open External merge Tool" option
upd-merge-tool-option
Figure 1.3 - Integrate a merge tool to Update Analyzer tool

When there are fixes done in core files as a temporary fix for a bug in a core file(s)

In an unlike scenario where a service update/release update user applied recently, contains a bug in a core file(s). In that sort of a scenario, user can correct that temporary and add that file to customer-solution repository until the actual fix comes with the next service update. Below steps explain how to remove those core files which contains the temporary fixes, from customer-solution repository when the fix has been released in the applying service update. Users can follow this as a part of the “Apply Service Update to Customer Solution Repository” .

  1. Make sure the correct topic branch is checked out. This will be the topic branch created during “Create Topic Branch to Apply Service Update” step.

    topic-branch-validation
    Figure 2.1 - Check the checked out branch

  2. Delete the core file which has the temporary fix, from the checked out local customer-solution repository's topic branch.

  3. Stage and commit the changes with an appropriate commit message.

    git add .

    git commit -m "<commit-message>"

    git push origin <branch-name>