wso2 / wso2/docs-mi

[Documentation] IBM MQ latest and MI 4.x integration to reflect current versions

Open
#92 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Area/InstallSetup Effort/DeepFocus Type/Improvement
Dominant language
CSS
Stars
15
Forks
118
Avg merge
8d 4h
Merged PRs (30d)
32

Description

Upon reviewing our current documentation, I've observed that it does not accurately reflect the latest IBM MQ product stack, with the most recent look, feel, and user experience differing significantly from what is described (as highlighted in ref [1]). This discrepancy suggests that our documentation is outdated and not aligned with the current capabilities and interface of IBM MQ.

IMO shall we re-look an end-to-end scenario that is ready to be executed, preferably utilizing Docker, to mirror contemporary development practices. Although there are existing resources, such as a blog referenced in [2], the information within these sources also seems to be outdated.

fyi, the latest version of IBM MQ is 9.x.x or above ref [3] (with sleek web UI experience rather IBM MQ explorer)

IMO again, we should encourage developers to set up the MQ runtime environment using Docker, considering its widespread adoption and the efficiency it offers for development workflows. Also, rather having some instruction we can have setup ready with docker to run
(i managed to make it work for producer-consumer scenario, but not referring to the WSO2 doc but referring to SO referrals)
[1] https://mi.docs.wso2.com/en/latest/install-and-setup/setup/brokers/configure-with-ibm-webspheremq/[2] https://medium.com/@madhukaudantha/wso2-ei6-6-0-with-ibm-websphere-mq-and-jms-properties-21e1baa700bc[3] https://developer.ibm.com/tutorials/mq-connect-app-queue-manager-containers/

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No documentation file, test, or entry point is identified in the issue. Start by reviewing the existing IBM MQ integration documentation and the linked Docker and IBM MQ references, then define the end-to-end scenario and the current versions it must cover. Done means the documentation provides a runnable Docker-based setup for the producer-consumer scenario.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker
Domain
devops, documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.