Skip to Main Content
Integration


This is an IBM Automation portal for Integration products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.


Status Submitted
Workspace App Connect
Created by Guest
Created on Mar 5, 2024

mqsicvp: Enable odbc testing using credentials in integration node vault, not just integration server vault

The mqsicvp command will complain about ODBC connections not being associated unless you specify the credentials at the integration server, and include the integration server arguments. ACE applications will use the integration vault for the credentials, so this is strictly an issue with mqsicvp.  mqsicvp should be updated to work with node and/or server credentials.

 

Example (setting password at the node level -- this fails but should work):

ibmint create node test_vault_node --vault-key PASSWORD
mqsivault test_vault_node --vaultrc-store-key --vault-key PASSWORD
export MQSI_VAULT_KEY=PASSWORD
mqsicredentials test_vault_node --create --credential-name DSN_NAME --credential-type odbc --username USERNAME --password BUSPASSWORD
ibmint start node test_vault_node
mqsicvp test_vault_node -n DSN_NAME

BIP8272E: Datasource 'DSN_NAME' has not been associated with integration node 'test_vault_node'.
This invocation of the mqsicvp command requires that the datasource name has been associated with the integration node, using the mqsisetdbparms command. If using a vault to store datasource credentials then the integration server name and vault password must also be supplied.
Check that this datasource has been associated with the integration node.

 

Example (setting password at the integration server level -- this works):

ibmint create node test_vault_node --vault-key PASSWORD
mqsivault test_vault_node --vaultrc-store-key --vault-key PASSWORD
export MQSI_VAULT_KEY=PASSWORD
ibmint start node test_vault_node
ibmint create server test_vault_server --integration-node test_vault_node
ibmint stop node test_vault_node
mqsicredentials test_vault_node --all-integration-servers --create --credential-name DSN_NAME --credential-type odbc --username USERNAME --password BUSPASSWORD
mqsicvp test_vault_node -n DSN_NAME --integration-server test_vault_server --vaultrc-location ~/.mqsivaultrc

 

Idea priority Low