-
Notifications
You must be signed in to change notification settings - Fork 144
Dividing mvd-configuration.md file into smaller topics #4787
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Dividing mvd-configuration.md file into smaller topics #4787
Conversation
Signed-off-by: arooshlele <[email protected]>
|
😺 Thank you for creating this PR! To publish your content to Zowe Docs, follow these required steps.
Need help? Contact the Doc Squad in the #zowe-doc Slack channel. |
…ork_Configuration_Page
Signed-off-by: arooshlele <[email protected]>
Signed-off-by: arooshlele <[email protected]>
Signed-off-by: arooshlele <[email protected]>
Signed-off-by: arooshlele <[email protected]>
Signed-off-by: arooshlele <[email protected]>
Signed-off-by: arooshlele <[email protected]>
Signed-off-by: arooshlele <[email protected]>
…ion-layer-client.md, setting-up-terminal-app-plugins.md Signed-off-by: arooshlele <[email protected]>
…plugin-configuration.md, logging-configuration.md Signed-off-by: arooshlele <[email protected]>
…trolling-access-to-apps.md Signed-off-by: arooshlele <[email protected]>
…plugins.md Signed-off-by: arooshlele <[email protected]>
Signed-off-by: arooshlele <[email protected]>
Signed-off-by: arooshlele <[email protected]>
Signed-off-by: arooshlele <[email protected]>
Signed-off-by: arooshlele <[email protected]>
Signed-off-by: arooshlele <[email protected]>
Signed-off-by: arooshlele <[email protected]>
Signed-off-by: arooshlele <[email protected]>
Signed-off-by: arooshlele <[email protected]>
anaxceron
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left comments for edits, lmk if you have questions
docs/user-guide/accessing-zss.md
Outdated
|
|
||
| Although you access the ZSS server via the Gateway port, the ZSS server still needs a port assigned to it which is the value of the *components.zss.port* variable in the Zowe configuration file. | ||
|
|
||
| If the mediation layer is not used, ZSS directly at `https://<zowe.externalDomain>:<components.zss.port>/`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If "mediation layer" = API ML, we should say "API ML" (w/o the "the")
| @@ -0,0 +1,28 @@ | |||
| # Administering the servers and plugins using an API | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
plug-ins -- please fix all use of "plugins" in this PR
| @@ -0,0 +1,28 @@ | |||
| # Administering the servers and plugins using an API | |||
| The App Server has a REST API to retrieve and edit both the App Server and ZSS server configuration values, and list, add, update, and delete plugins. Most of the features require RBAC to be enabled and for your user to have RBAC access to utilize these endpoints. For more information see documentation on how to [use RBAC](https://docs.zowe.org/stable/user-guide/mvd-configuration.html#controlling-access-to-dataservices) | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
comma after "For more information"
| The API returns the following information in a JSON response: | ||
|
|
||
| | API | Description | | ||
| | --------------------------------------------------------- | ------------------------------------------------------------ | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No need to keep saying "Returns" if we're saying "returns" in Line 4. I would rewriter either Line 4 or the descriptions for each of these items.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@anaxceron I agree. It has been edited accordingly.
|
|
||
| Swagger API documentation is provided in the `<zowe.runtimeDirectory>/components/app-server/share/zlux-app-server/doc/swagger/server-plugins-api.yaml` file. To see it in HTML format, you can paste the contents into the Swagger editor at https://editor.swagger.io/. | ||
|
|
||
| **Note:** The "agent" end points interact with the agent specified in the zowe configuration file. By default this is ZSS. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Use the docusaurus syntax for the note
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@anaxceron I agree with Ana. Done.
| @@ -0,0 +1,59 @@ | |||
| # ZSS configuration | |||
|
|
|||
| ZSS provides APIs that any server or client can use. By default, the Zowe Desktop includes Apps which rely upon ZSS APIs, and therefore it's recommended that whenever the `app-server` is enabled in the Zowe YAML, that `zss` is also enabled. | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Apps shouldn't be capitalized
- spell out "it's"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done.
|
|
||
| ### Verifying which ZSS mode plugins support | ||
|
|
||
| You can check if a ZSS plugin supports 64 bit or 31 bit ZSS by reading the pluginDefinition.json file of the plugin. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
pluginDefinition.json should be in backticks
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done.
|
|
||
| You can check if a ZSS plugin supports 64 bit or 31 bit ZSS by reading the pluginDefinition.json file of the plugin. | ||
| In each component or extension you have, its manifest file will state if there are `appFw` plugin entries. | ||
| In each folder referenced by the `appFw` section, you will see a pluginDefinition.json file. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
backticks
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done.
|
|
||
| In a standard Zowe installation, all Zowe servers utilize the API Mediation Layer's token-based, single-sign on authentication. This authentication in turn cooperates with z/OSMF, and the session duration is typically that of z/OSMF's, which defaults to 8 hours before the session expires. In that situation, customization of session duration is best done by customizing z/OSMF's session duration, as a part of its Liberty configuration. | ||
|
|
||
| If you are not using the API Mediation Layer, or are trying to contact ZSS directly, then ZSS's own session logic is used. When authenticated directly to ZSS, it will respond to authenticated HTTP requests with a cookie which is valid by default for 1 hour. This can be customized by creating and editing a file named "timeouts.json" within ZSS's instance directory. The default location is `<zowe.workspaceDirectory>/app-server/serverConfig/timeouts.json`, because the default instance directory is `<zowe.workspaceDirectory>/app-server`, but can be customized by editing the value of `components.zss.instanceDir`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"timeouts.json" should be in backticks
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done.
|
|
||
| If you are not using the API Mediation Layer, or are trying to contact ZSS directly, then ZSS's own session logic is used. When authenticated directly to ZSS, it will respond to authenticated HTTP requests with a cookie which is valid by default for 1 hour. This can be customized by creating and editing a file named "timeouts.json" within ZSS's instance directory. The default location is `<zowe.workspaceDirectory>/app-server/serverConfig/timeouts.json`, because the default instance directory is `<zowe.workspaceDirectory>/app-server`, but can be customized by editing the value of `components.zss.instanceDir`. | ||
|
|
||
| The timeouts.json file has the following layout: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
backticks
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done.
@anaxceron @gauravs-20 Signed-off-by: ArooshLele <[email protected]>
I made some minor edits. Signed-off-by: ArooshLele <[email protected]>
Yes, I edited plugin to plug-in wherever applicable. In the table: -In the Description (right side) column, I removed "Returns" from the rows. -In the API (left side) column, I did not change plugin to plug-ins as that's the API's unique name, wherever applicable. Thanks ! Signed-off-by: ArooshLele <[email protected]>
Plugin changed to plug-in. Signed-off-by: ArooshLele <[email protected]>
Changed plugin to plug-in. Signed-off-by: ArooshLele <[email protected]>
I edited plugin to plug-in, enclosed variable in backticks, rewrote Components as "components". (from Uppercase to Lowercase). Signed-off-by: ArooshLele <[email protected]>
Edits are done. Signed-off-by: ArooshLele <[email protected]>
Variables are enclosed in backticks. Signed-off-by: ArooshLele <[email protected]>
Edits Signed-off-by: ArooshLele <[email protected]>
Edits Signed-off-by: ArooshLele <[email protected]>
Signed-off-by: ArooshLele <[email protected]>
Edits Signed-off-by: ArooshLele <[email protected]>
Edits. Signed-off-by: ArooshLele <[email protected]>
Edits Signed-off-by: ArooshLele <[email protected]>
Signed-off-by: ArooshLele <[email protected]>
Edits Signed-off-by: ArooshLele <[email protected]>
Signed-off-by: arooshlele <[email protected]>
The Docsaurus syntax is applied on the note. Signed-off-by: ArooshLele <[email protected]>
Signed-off-by: ArooshLele <[email protected]>
The Note is now as per Docasaurus's syntax. Signed-off-by: ArooshLele <[email protected]>
…ork_Configuration_Page
List the file(s) included in this PR:
mvd-configuration.md
Describe your pull request here:
The mvd-configuration.md file has the Advanced Application Framework Configuration topic.
It is a large topic.
Following my discussion with Sean @1000TurquoisePogs , this large topic could be divided into smaller chunks/subtopics. The content stays the same.
The subtopic files would be as follows:
After creating the PR, follow the instructions in the comments.
@gauravs-20 @ArooshLele