Sap aem int day 3 #303
Merged
Sap aem int day 3 #303
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Populating content for 3rd day, prereqs mostly done, AEM configuration done, importing iflows done, configuring and deploying iflows in progress
Added more steps for setting up Integration Suite with security credentials etc.
Adjusted time estimates
Added Overall Duration estimate
Finished description and configuration and deployment steps for AEMBusinessPartnerAddressCheck iflow.
fixed typos and formatting
Added configuration and deployment for 2 more flows
Added more details on the LegacyOutputAdapter
Finished basic description of event flows
Finished describing AEM related settings and processing steps
Added takeaways
Fixed formatting
Formatting updates
…ce-dev-codelabs into sap-aem-int-day-3
Formatting
…ce-dev-codelabs into sap-aem-int-day-3
More formatting
…ce-dev-codelabs into sap-aem-int-day-3
Formatting and new AEM adapter version
…ce-dev-codelabs into sap-aem-int-day-3
Fixed queue subs and more formatting
# Conflicts: # codelabs/sap-aem-int-day-3/codelab.json # codelabs/sap-aem-int-day-3/index.html # markdown/sap-aem-int-day-3/sap-aem-int-day-3.md
Restructured code lab to complete configuration and deployment of one iflow at a time.
|
Thanks for opening up a PR and contributing to our open source codelabs! Review process GuidelinesOnce the PR is opened, tag at least one Technical Reviewer Technical Reviewer Responsibilities
Post Technical ReviewA member of the Developer Advocate Team will review overall structure and merge into master which will push it to production |
Restructured to separate into 3 separate iflow deployment scenarios, that can be completed one after the other end to end.
formatting
formatting
Added note to skip over queue configuration for those that used the CI/CD tool in a previous step.
Updates to intro sections and scenario 1
Prepared scenario 2 to slot in changes developed by Scott.
Updates to scenario 2
Added troubleshooting guide
|
Thanks for opening up a PR and contributing to our open source codelabs! Review process GuidelinesOnce the PR is opened, tag at least one Technical Reviewer Technical Reviewer Responsibilities
Post Technical ReviewA member of the Developer Advocate Team will review overall structure and merge into master which will push it to production |
fixed link to CI tool
Updating time estimates
Added security module
formatting
formatting
more formatting
format, format
more formatting testing
HariRangarajan-Solace
approved these changes
Feb 27, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Restructured code labs to complete configuration and deployment of one iflow at a time.