6. Preparing Open Integration Files in Git

You must now create deployment-ready Open Integration files from the starter templates stored in the customer Git repository. You must complete the following procedure before you call the POST /openintegration API:

1. Create a new deployment branch from the branch that contains the starter templates. You must avoid modifying the starter template branch directly unless your project process requires it.
2. Create config.json by using config_template.json as the starting point.
3. Create profile.json by using profile_template.json as the starting point.
4. Update config.json with the configuration required for the target Open Integration runtime.
5. Update profile.json with the configuration required for the target Siebel and Open Integration environment.
6. Add or update any required integration configurations, scripts, mappings, domain configurations, and related starter kit artifacts.
7. Commit the changes to the deployment branch.
8. Push the deployment branch to the customer Git repository.

Note:

• The deployment directory must contain committed Open Integration files, including config.json and profile.json.
• Retain the starter template files for reference unless your project process requires their removal after creating the deployment files.
• Do not store Git access tokens, SSH private keys, keystore passwords, registry passwords, or other customer secrets in the Git repository.
• Store keystore and truststore files in SCM-accessible runtime storage locations, such as Sync Utility output directories, rather than in the customer Git repository.