Being the Product Manager of, and having worked with webMethods.io Integration since its launch, I’ve developed many complex integrations internally at Software AG to automate application processes, as well as working with our customers, Professional Servcices and Partners to help them in their cloud journeys. Along the way I’ve amassed considerable knowledge as to what works well, what doesn’t, and where users and developers of the platform can find themselves at a junction, not knowing which direction to approach or which way to turn in order to reach their goal.
Today, I’d like to share with you my first attempt at creating a set of community guidelines for developers of webMethods.io Integration based on these experiences.
Where can I find the guidelines?
What information do they contain?
- Explanation and comparison of the different types of integration and automation in webMethods.io Integration
- Implementation recommendations for each of the approaches
- When and when NOT to use the different approaches
- Do and Don’t checklists to avoid making the wrong design decisions or simple mistakes
- Samples of integrations
- Implementation patterns and approaches
- API implementation and security
- Connector creation options and guidance
- Hybrid integration approaches
Why are the guidelines in GitHub?
- I created this based on my experience - but there are MANY others out there who are also experienced in implementing integrations in the platform, from our customers, partners and also others inside Software AG.
- These guidelines belong to the community - they are a living community document that YOU can and should contribute to, to help and assist your fellow developers to get a faster start and avoid making the same mistakes you might have done when you were starting out!
- Also as the product evolves further, these guidelines will need to be evolved to take into account these changes.
How can you contribute?
- Fork the git repository
- Edit/add markdown files/images/etc.
- Commit/push to your repo
- When you’re ready, create a pull request back to the main repository, where your contributions will be considered and merged where appropriate for the rest of the community. All contributors will be added to the README to highlight their input!