Issue WTO message on API Mediation Layer startup

[balhar-jakub]

Describe your pull request here: One of the common requests is issuing the specific message when the API Mediation Layer properly starts in the Syslog. This article explains all the configuration and pieces needed to achieve this goal with the current functionality.

List the file(s) included in this PR: wto-message-on-startup.md

After creating the PR, follow the instructions in the comments.

[github-actions[bot]]

:smiley_cat: Thank you for creating this PR! To publish your content to Zowe Docs, follow these required steps.

• [ ] Add the label review: doc.
• [ ] Identify your content topic with a label. (Examples: area: apiml, area: cli, area: install and config, etc.)
• [ ] Specify the major Zowe release(s) for your content. (Examples: release: V1, release: V2, release: V3)
  • [ ] If adding content that needs to be removed from V3 documentation, add the V3 N/A tag.
• [ ] Select the master branch if your PR updates content that is on the live site. Select docs-staging if your PR updates content for a future release.
• [ ] Notify the Doc Squad about this PR. If you don't know whom should review your content, message the #zowe-doc Slack channel. If you know which Doc Squad writer should approve your content, add that person as a reviewer.

Need help? Contact the Doc Squad in the #zowe-doc Slack channel.

[github-actions[bot]]

🚀 Deployed on https://66fbdb7a1ba9900b20489e15--zowe-docs-master.netlify.app

[1000TurquoisePogs]

It looks like ZWEAM001I is a new message that is better than ZWEAM000I for detecting readiness. That's great!

Please see the PRs I made to implement this. Also note, I do not see this message in v3, only in v2. Since this is going into master, check to see if it will show up in v2.18 documentation, where it is appropriate, versus v3 documentation, where it appears to not exist yet. If it is a v3.1 feature, perhaps docs-staging is more appropriate?

[balhar-jakub]

It's been implemented only for V2 by now I believe. It should be in 2.x documentation.

As for v3 we originally intended something better, but it's probably good enough and we should bring it to the v3 as well at least.