SAP BTP Cloud Integration Code search tool

[fatima4]

We have looked into SAP documentation and SAP recently recommended using ${body} instead of ${in.body}. In order to identify which artifacts are using this code in an efficient time, especially since we don't yet have a full Git pipeline. (~500 iflows in our current Integration Suite CI capability). We implemented the search code tool. By specifying ${in.body} as the search parameter, the tool scans all iFlows, identifies where this string is used, and returns the names of the relevant iFlows. 

https://help.sap.com/docs/cloud-integration/sap-cloud-integration/using-camel-simple-expression-lang...

This tool is having below features:

• To search a specific code in:
  • Script collection
  • Resources
  • Search function name in message mapping when the iflow uses folder .mmap
• This tool can't search in function libraries types

High level flow:

This tool needs to support multiple packages

Trigger process for this tool execution is based on start timer.

Prerequisites:

1. Cloud integration credentials:
   
   1. Create role collection searchCodeiflows and add roles
      1. 
   2. Create user and assign role connection searchCodeiflows
   3. This user credential is being use to get information about script collection, resources, etc.

To be able to use the tool,

1. Download the SearchCodeTool.zip from the BTP-Integration-Suite repository: https://github.com/FatimaMel/BTP-Integration-Suite 
2. In SAP integration suite, upload the searchCodeTool.zip folder as type Integration Flow in a package
   1. 
3. Create in security material:
   1. User Credentials created earlier at step 1.b in Prerequises
      1.  
4. In configuration of the artifact, set the parameters:
   1. choosePackagesId is for searching in specific packages. Ex: packageId1||packageId2
   2. CIDesignTime with the domain url of the deployment iflow, but remove '-rt' from the url
      1. 
   3. codeToSearch is the specific code to search
   4. searchCodeUserCred is the name of User Credentials created at step 3.a
   5. SearchInResourcesAndMapping and SearchInScriptCollection are for searching in specific areas. If no value is specified, it will be set to true. 
      1. 
5. The result will be in the Monitor Message Processing in the section Attachments
   1. 
6. Performance of the iflow:
   1. The performance depends on the number of packages and integration flow.
      1. For 3 packages and around 85 iflows, it takes around 2 minutes.
      2. For 10 packages and around 154 iflows, it takes around 3 minutes.
      3. For about 50 packages and around 350 iflows, it can take up to 7 minutes.