This repository has been archived by the owner on Sep 9, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
556881b
commit 2ddf248
Showing
2 changed files
with
71 additions
and
82 deletions.
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,92 +1,80 @@ | ||
| # agents-webmethods | ||
| # Prerequisites | ||
|
|
||
| * You need an Axway Platform user account that is assigned the AMPLIFY Central admin role | ||
| * Your Wemethods API Gateway should be up and running and have APIs to be discovered and exposed in AMPLIFY Central | ||
|
|
||
| Let’s get started! | ||
|
|
||
| ## Getting started | ||
| ## Prepare AMPLIFY Central Environments | ||
|
|
||
| To make it easy for you to get started with GitLab, here's a list of recommended next steps. | ||
| In this section we'll: | ||
|
|
||
| Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)! | ||
| * [Create an environment in Central](#create-an-environment-in-central) | ||
| * [Create a service account](#create-a-service-account) | ||
|
|
||
| ## Add your files | ||
| ### Create an environment in Central | ||
|
|
||
| - [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files | ||
| - [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command: | ||
| * Log into [Amplify Central](https://apicentral.axway.com) | ||
| * Navigate to "Topology" then "Environments" | ||
| * Click "+ Environment" | ||
| * Select a name | ||
| * Click "Save" | ||
| * To enable the viewing of the agent status in Amplify see [Visualize the agent status](https://docs.axway.com/bundle/amplify-central/page/docs/connect_manage_environ/environment_agent_resources/index.html#add-your-agent-resources-to-the-environment) | ||
|
|
||
| ``` | ||
| cd existing_repo | ||
| git remote add origin https://git.ecd.axway.org/apigov/agents-webmethods.git | ||
| git branch -M main | ||
| git push -uf origin main | ||
| ``` | ||
|
|
||
| ## Integrate with your tools | ||
|
|
||
| - [ ] [Set up project integrations](https://git.ecd.axway.org/apigov/agents-webmethods/-/settings/integrations) | ||
|
|
||
| ## Collaborate with your team | ||
|
|
||
| - [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/) | ||
| - [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html) | ||
| - [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically) | ||
| - [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/) | ||
| - [ ] [Automatically merge when pipeline succeeds](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html) | ||
|
|
||
| ## Test and Deploy | ||
|
|
||
| Use the built-in continuous integration in GitLab. | ||
|
|
||
| - [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html) | ||
| - [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing(SAST)](https://docs.gitlab.com/ee/user/application_security/sast/) | ||
| - [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html) | ||
| - [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/) | ||
| - [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html) | ||
|
|
||
| *** | ||
|
|
||
| # Editing this README | ||
| ### Create a service account | ||
|
|
||
| When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thank you to [makeareadme.com](https://www.makeareadme.com/) for this template. | ||
| * Create a public and private key pair locally using the openssl command | ||
|
|
||
| ## Suggestions for a good README | ||
| Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information. | ||
|
|
||
| ## Name | ||
| Choose a self-explaining name for your project. | ||
|
|
||
| ## Description | ||
| Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors. | ||
|
|
||
| ## Badges | ||
| On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge. | ||
|
|
||
| ## Visuals | ||
| Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method. | ||
|
|
||
| ## Installation | ||
| Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection. | ||
|
|
||
| ## Usage | ||
| Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README. | ||
|
|
||
| ## Support | ||
| Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc. | ||
|
|
||
| ## Roadmap | ||
| If you have ideas for releases in the future, it is a good idea to list them in the README. | ||
|
|
||
| ## Contributing | ||
| State if you are open to contributions and what your requirements are for accepting them. | ||
| ```sh | ||
| openssl genpkey -algorithm RSA -out private_key.pem -pkeyopt rsa_keygen_bits: 2048 | ||
| openssl rsa -in private_key.pem -pubout -out public_key.pem | ||
| ``` | ||
|
|
||
| For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self. | ||
| * Log into the [Amplify Platform](https://platform.axway.com) | ||
| * Navigate to "Organization" then "Service Accounts" | ||
| * Click "+ Service Account" | ||
| * Select a name | ||
| * Optionally add a description | ||
| * Select "Client Certificate" | ||
| * Select "Provide public key" | ||
| * Select or paste the contents of the public_key.pem file | ||
| * Select "Central admin" | ||
| * Click "Save" | ||
| * Note the Client ID value, this and the key files will be needed for the agents | ||
|
|
||
| ## Prepare Webmethods APIM | ||
|
|
||
| * Create an webmethods account | ||
| * Note the username and password used as the agents will need this to run | ||
| * Add a developer that will be the owner of all applications created by the agent | ||
|
|
||
| ## Setup agent Environment Variables | ||
|
|
||
| The following environment variables file should be created for executing both of the agents | ||
|
|
||
| ```ini | ||
| CENTRAL_ORGANIZATIONID=<Amplify Central Organization ID> | ||
| CENTRAL_TEAM=<Amplify Central Team Name> | ||
| CENTRAL_ENVIRONMENT=<Amplify Central Environment Name> # created in Prepare AMPLIFY Central Environments step | ||
|
|
||
| CENTRAL_AUTH_CLIENTID=<Amplify Central Service Account> # created in Prepare AMPLIFY Central Environments step | ||
| CENTRAL_AUTH_PRIVATEKEY=/keys/private_key.pem # path to the key file created with openssl | ||
| CENTRAL_AUTH_PUBLICKEY=/keys/public_key.pem # path to the key file created with openssl | ||
|
|
||
| WEBMETHODS__URL=<Webmethods API Gateway UI URL> # created in Prepare Webmethods agent step | ||
| WEBMETHODS_MATURITYSTATE=<Webmethods Maturity State> # created in Webmethods agent step | ||
| WEBMETHODS_FILTER=<Webmethods Tag filter> # created in Webmethods agent step | ||
| WEBMETHODS_AUTH_USERNAME=<Webmethods Username> # created in Prepare Webmethods agent step | ||
| WEBMETHODS_AUTH_PASSWORD=<Webmethods Password> # created in Prepare Webmethods agent step | ||
|
|
||
| LOG_LEVEL=info | ||
| LOG_OUTPUT=stdout | ||
| ``` | ||
|
|
||
| You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser. | ||
| ## Discovery Agent | ||
|
|
||
| ## Authors and acknowledgment | ||
| Show your appreciation to those who have contributed to the project. | ||
| Reference: [Discovery Agent](README_discovery.md) | ||
|
|
||
| ## License | ||
| For open source projects, say how it is licensed. | ||
| ## Traceability Agent | ||
|
|
||
| ## Project status | ||
| If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers. | ||
| Reference: [Traceability Agent](README_traceability.md) |
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