APAR status
Closed as requirement.
Error description
In ACE v12 ibmint command doesn't have an option to specify external vault parameters while creating/starting a node or server. /temp>ibmint create node --help BIP15198I: Create an integration node. Syntax: ibmint create node <nodeName> [--node-conf-yaml <filePath>] [ --queue-manager <queueManagerName> ] [--shared-work-path <directory>] [--vault-key <key> | --vaultrc-location <directory>] [--work-path <directory>] [--trace <filePath>] Command Options: '<nodeName>' The name of a locally defined integration node. '--node-conf-yaml <filePath>' The location of a node.conf.yaml file containing the required configuration information. This file will be copied to workdirectory/components/nodeName/node.conf.yaml. '--queue-manager <queueManagerName>' The name of the Websphere MQ queue manager associated with the node. '--shared-work-path <directory>' The directory in which registry and configuration data is shared between multiple instances of this integration node. '--work-path <directory>' The directory in which internal data, such as installation logs, component details, and trace output are written. '--vault-key <key>' The vault key to be used to access the vault owned by the integration node. '--vaultrc-location <directory>' The directory path containing the .mqsivaultrc file used to locate the vault key and external directory vault key. '--trace <filePath>' Send verbose internal trace to the specified file. /temp>ibmint start node --help BIP15194I: Start an integration node. Syntax: ibmint start node <nodeName> [--vault-key <key> | --vaultrc-location <directory>] [--timeout-seconds <seconds>] [--trace <filePath>] Command Options: '<nodeName>' The name of a locally defined integration node. '--timeout-seconds <seconds>' The maximum number of seconds to wait for the integration node to be started (default is 60). '--vault-key <key>' The vault key to be used to access the vault owned by the integration node. '--trace <filePath>' Send verbose internal trace to the specified file.
Local fix
Problem summary
**************************************************************** USERS AFFECTED: All Users of IBM App Connect Enterprise v12 using ibmint command Platforms affected: MultiPlatform **************************************************************** PROBLEM DESCRIPTION: The 'ibmint' command does not have an option to specify external vault parameters while creating/starting a node
Problem conclusion
The product has been modified to support external vault parameters '--external-directory-vault-key' on the ibmint command while creating/starting a node.
Temporary fix
Comments
IBMINT COMMAND DOESN'T SUPPORT EXTERNAL VAULT PARAMETERS.
APAR Information
APAR number
IT44675
Reported component name
APP CONNECT ENT
Reported component ID
5724J0560
Reported release
C00
Status
CLOSED REQ
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2023-10-06
Closed date
2023-10-16
Last modified date
2023-10-16
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSDR5J","label":"IBM App Connect Enterprise"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"C00","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
17 October 2023