- Demand purpose and short description : The purpose of this request is to customize the default MQ objects created when a new queue manager is set up, in order to streamline the testing process for new users.
Currently, default objects are created with prefixes such as 'DEV.' (queues, topics), which are not necessary for production environments.
We propose using a bootstrap installation script to parameterize default objects at creation time.
- Main features of the target solution : The target solution would involve using a script to run a set of MQ commands during queue manager creation, including:
Creating queues (local/remote), channels, aliases, and topics Setting up channel authentication records (chlauth) and authority records (autrec) Configuring basic queue manager properties (e.g., MAXMSGL, MAXUMSGS) Setting up templates (QMODEL, PROCESS, etc.)
Answer to IBM questions :
- How do expect to supply the script to the MQ SaaS service? File upload? Text field in an API call? Link to a source repository containing the script?
We expect to supply the script through a text field in an API call or a file upload mechanism 2) At what scope do you expect the script to be applied? Per queue manager? All queue managers in reserved deployment, All queue managers in a reserved capacity?
We expect the script to be applied per queue manager. This would allow for customization of each queue manager's default objects, channels, and security settings. Applying the script to all queue managers in a reserved deployment or capacity could also be useful, but it may not be necessary in all cases. 3) What configuration behaviour do you expect when a script is configured? It runs on queue manager creation only; it runs every time the queue manager is restarted (e.g. during infrastructure and queue manager upgrades); it can be run at any other time including manually
We expect the script to run on queue manager creation only. This would ensure that the default objects and settings are created and configured correctly when the queue manager is first set up 4) Is there a need to remove or modify the script after it has been initially submitted?
We do not anticipate a need to modify or remove the script after it has been initially submitted and run during queue manager creation. The script is intended to be a one-time configuration step, and any subsequent changes to the queue manager's configuration would be made through standard administration interfaces. Therefore, once the script has been run, it can be considered a static configuration that does not require further modification or management. 3. Cases study pre-implementation : An example script (bp2i_model.mqsc) has been attached, demonstrating the types of commands that would be run during queue manager creation. This script can be used for implementing the proposed solution.
Post-implementation review After implementing the solution, we expect to see a reduced manual configuration efforts. The customized default objects will enable users to start testing quickly, without the need for unnecessary production-related configurations.
General conditions of acceptance / non acceptance The solution will be considered accepted if the script successfully runs during queue manager creation, and the desired default objects are created without errors. Non-acceptance will occur if the script fails to run, or if the created objects do not meet the required specifications.
