Unable to start integration node <insert_1>. The integration node contains an external directory vault and a valid external directory vault key must be supplied.
Severity
10 : Warning
Explanation
Supply the external directory vault key via one of these methods: 1. Use the --ext-vault-key argument when starting the integration node; 2. Set the environment variable MQSI_EXT_VAULT_KEY with the value of the external directory vault key before starting the integration node; 3. Store the external directory vault key in an .mqsivaultrc file. If using a .mqsivaultrc file, this can be located via one of these methods: A. Use the --vaultrc-location to specify the location of the directory containing the .mqsivaultrc file; B. Set the environment variable MQSI_VAULTRC_LOCATION with the location of the directory containing the .mqsivaultrc file; C. Store the .mqsivaultrc file in the users home directory.
BIP10001
The external directory vault access key must be supplied to administer credentials in an external directory vault with "mqsicredentials" and "mqsivault --decode".
Severity
20 : Error
Explanation
This command requires the external directory vault key to be supplied as a command line argument, in the environment or in the mqsivaultrc file. If "--ext-vault-key" is specified without an argument, the external directory vault key will be prompted for and not displayed. For "mqsivault --decode", only the command line argument or the prompt may be used.
BIP10002
Cannot open encrypted store at location <insert_1> because it is being destroyed.
Severity
20 : Error
Explanation
An "mqsivault --destroy" or "mqsideletebroker" is in progress for the external directory vault or broker related to the encrypted store in this directory.
Response
Wait until the "mqsivault --destroy" or "mqsideletebroker" command completes, and then issue "mqsivault --create" or "mqsicreatebroker" if appropriate.
BIP10003
Cannot open encrypted store at location <insert_1>.
Severity
20 : Error
Explanation
An encrypted store was expected in this directory but was not found.
Response
Use the 'mqsivault --create' or 'ibmint create vault' command to create either an integration server vault, an integration node vault, or an external directory vault. The required encrypted store is created by these commands.
BIP10004
The external directory vault in directory <insert_1> does not exist or is corrupted.
Severity
20 : Error
Explanation
This integration server is configured with an external directory vault, but the external directory vault does not exist or has been corrupted.
Response
Create the external directory vault or restore it from backup. If the credentials in the vault can be recreated, you may as an alternative use "mqsivault --destroy" to destroy the corrupted external directory vault and then "mqsivault --create" to create a new empty one.
BIP10005
The external directory vault key that is required for administration of the vault was not found.
Severity
20 : Error
Explanation
To administer the vault, this command requires the external directory vault key to be supplied in either an environment variable, the vaultrc file, or a command line argument.
Response
Provide the external directory vault key by specifying it in the MQSI_EXT_VAULT_KEY environment variable, the vaultrc file in the user's home directory, or by using the --prompt or --external-directory-vault-key argument on the command.
BIP10006
The external directory vault key, vault key or passphrase must be at least <insert_1> characters in length.
Severity
20 : Error
Explanation
This command requires the external directory vault key, vault key or passphrase to be at least <insert_1> characters in length.
Response
Provide the external directory vault key, vault key or passphrase of at least <insert_1> characters in length.
BIP10007
The <insert_1> was not supplied in response to the command prompt.
Severity
20 : Error
Explanation
To administer the vault, this command requires the <insert_1> to be supplied on the command line.
Response
Provide the <insert_1> in the --prompt argument on the command line.
BIP10098
The file <insert_1> is not supported for conversion back to its source format because it contains inline subflows.
Severity
10 : Warning
Explanation
The file at location <insert_2> is not supported for conversion back to its source format because it contains inline subflows.
BIP10099
The file <insert_1> is not supported for conversion back to its source format because it contains inline ESQL with multiple broker schema.
Severity
10 : Warning
Explanation
The file at location <insert_2> is not supported for conversion back to its source format because it contains inline ESQL with multiple broker schema.
BIP10100
The file <insert_1> is not supported for conversion back to its source format.
Severity
10 : Warning
Explanation
The file at location <insert_2> is not supported for conversion back to its source format.
BIP10101
The directory <insert_1> is not supported for conversion back to its source format.
Severity
10 : Warning
Explanation
The directory at location <insert_2> has been identified as a <insert_3>, which is not supported for conversion back to its source format.
BIP10102
An unexpected directory <insert_1> was encountered while regenerating a BAR file from deployed resources.
Severity
10 : Warning
Explanation
The directory at location <insert_2> is unexpected, so can not be converted back to its source format.
BIP10103
Using integration server vault.
Severity
0 : Information
BIP10104
Using external directory vault <insert_1>.
Severity
0 : Information
BIP10105
Vault lock held by <insert_1>.
Severity
10 : Warning
BIP10106
Process <insert_1> terminated holding vault lock.
Severity
10 : Warning
BIP10107
Unable to establish correct environment for specified JRE.
Severity
20 : Error
Explanation
For use of the specified JRE in this process, a selection of environment variables should be set. This was unsuccessful, but the original environment variables could not be fully restored.
Response
Use the "ibmint specify jre" command with the "--default" option to fully revert to using the default Java installed with App Connect Enterprise.
BIP10108
Unable to adjust environment for the specified JRE.
Severity
10 : Warning
Explanation
For use of the specified JRE in this process, a selection of environment variables should be set. This was unsuccessful, so the original environment variables have been restored. The process will continue to operate, but may not be able to access all facilities of the specified JRE.
Response
Monitor for Java-related problems. If any are suspected, use the "ibmint specify jre" command with the "--default" option to fully revert to using the default Java installed with App Connect Enterprise.
BIP10109
Using integration node vault.
Severity
0 : Information
BIP10110
Timeout (<insert_1> milliseconds) expired waiting for lock on credential vault.
Severity
20 : Error
Explanation
More than 30 seconds elapsed with another thread holding the credential vault lock.
Response
If the vault is on NFS, check for a network or server problem. Then restart the affected process.
BIP10111
Message flow <insert_2> has a reference to an object of type <insert_3> that requires the component <insert_4>. This component is not available; the cause lies in <insert_5>.
Severity
20 : Error
Explanation
The message flow <insert_2> has a reference to an object of type <insert_3> that requires the component <insert_4>. Component <insert_4> is not available in integration server <insert_1> due to <insert_5>.
Response
Possible solutions include re-configuring the integration server or the environment in which it runs, or redeploying applications to a different integration server.
BIP10112
The resources from <insert_1> have not been loaded because the runtime component <insert_2> has not been enabled. Reason: <insert_3>. Further detail: <insert_4>.
Severity
0 : Information
BIP10200
Unable to create the directory <insert_2> that is required to store the Change Data Capture offset information for node <insert_1>.
Severity
20 : Error
Explanation
An IO exception occurred while trying to create the offset store.
Response
Check the file permissions and available space for the specified directory.
BIP10201
No database tables were specified in the Change Data Capture node <insert_1> in the flow <insert_2>.
Severity
20 : Error
Explanation
At least one database table must be specified in the List of Database Tables property.
Response
Add the database table name, or names, to the List of Database Tables property on the Basic tab of the Change Data Capture node.
BIP10202
Debezium class <insert_1> could not be located under directory <insert_2>.
Severity
20 : Error
Explanation
The Debezium connector class failed to load because it was not found in the expected location.
Response
Add the Debezium connector JAR files to the <insert_2> directory, as described in 'Configuring the Change Data Capture node' in the IBM App Connect Enterprise documentation.
BIP10203
The Debezium engine ended with a failure message <insert_1>.
Severity
20 : Error
Explanation
The Debezium engine has failed.
Response
Fix the problem detailed in the message. For information about how to resolve the problem, refer to the Debezium documentation: https://debezium.io/documentation/reference/stable/index.html.
BIP10204
The Debezium engine has thrown an exception <insert_1>.
Severity
20 : Error
Explanation
The Debezium engine has encountered an error and has thrown an exception.
Response
Fix the problem detailed in the message. For information about how to resolve the problem, refer to the Debezium documentation: https://debezium.io/documentation/reference/stable/index.html.
BIP10205
<insert_1>
Severity
20 : Error
Explanation
Log Entry
BIP10206
<insert_1>
Severity
0 : Information
Explanation
Log Entry
BIP10207
<insert_1>
Severity
0 : Information
Explanation
Log Entry
BIP10208
The mapped Status Code <insert_1> from the message flow node <insert_2> in message flow <insert_3> is not an integer or was not in the range 100 - 999.
Severity
20 : Error
BIP10209
The Status Code from the message flow node <insert_1> in message flow <insert_2> did not map to a value.
Severity
20 : Error
BIP10210
Loading Designer integration accounts.
Severity
0 : Information
Explanation
The integration server is loading accounts from a configuration object of type Accounts and making them available as policies and credentials.
Response
None.
BIP10211
Error loading Designer integration account name <insert_1> type <insert_2>. Please see following messages for further details.
Severity
20 : Error
Explanation
The integration server is loading accounts from a configuration object of type Accounts and has encountered an error with one of the account entries. See following messages for more details.
Response
Review the error messages and ensure the Accounts configuration is correct. Contact your IBM support center if you are unable to determine the cause of the problem.
BIP10212
Loading of Designer integration accounts into policy project <insert_1> has finished.
Severity
0 : Information
Explanation
The integration server has completed the loading of accounts from a configuration object of type Accounts and making them available as policies and credentials.
Response
Review any messages issued whilst loading the accounts and resolve any errors.
BIP10213
Error updating Designer integration account name <insert_1> type <insert_2>. (action <insert_3>). Please see following messages for further details.
Severity
20 : Error
Explanation
The integration server is processing updates for accounts from a configuration object of type Accounts and has encountered an error with one of the account entries. See following messages for more details.
Response
Review the error messages and ensure the Accounts configuration is correct. Contact your IBM support center if you are unable to determine the cause of the problem.
BIP10214
Updating Designer integration accounts.
Severity
0 : Information
Explanation
The integration server is has detected a change to the configuration object of type Accounts and is starting to process the updates.
Response
None.
BIP10215
Updating of Designer integration accounts in policy project <insert_1> has finished.
Severity
0 : Information
Explanation
The integration server has completed the updating of accounts from a configuration object of type Accounts and making them available as policies and credentials. Where loading was successful all integrations have been updated to use the updated account details.
Response
Review any messages issued whilst updating the accounts and resolve any errors.
BIP10216
Error loading or creating Designer integration account name <insert_1> type <insert_2> because a policy of the same name and type already exists in the policy project <insert_3>.
Severity
20 : Error
Explanation
The integration server is loading or processing updates for accounts from a configuration object of type Accounts and has encountered an error with one of the account entries due to an existing policy already being present with the same name in the policy project. The account will be ignored and the original will remain.
Response
Review the error messages and ensure the Accounts configuration is correct. Contact your IBM support center if you are unable to determine the cause of the problem.
BIP10217
Error loading Designer integration account name <insert_1> type <insert_2>, error message <insert_3>.
Severity
20 : Error
Explanation
The integration server is loading accounts from a configuration object of type Accounts and has encountered an error with one of the account entries.
Response
Review the error messages and ensure the Accounts configuration is correct. Contact your IBM support center if you are unable to determine the cause of the problem.
BIP10218
Error updating Designer integration account name <insert_1> type <insert_2> (action <insert_3>), error message <insert_4>.
Severity
20 : Error
Explanation
The integration server is processing updates for accounts from a configuration object of type Accounts and has encountered an error with one of the account entries.
Response
Review the error messages and ensure the Accounts configuration is correct. Contact your IBM support center if you are unable to determine the cause of the problem.
BIP10219
The node of type <insert_1> named <insert_2> requires server component <insert_3> to be enabled.
Severity
20 : Error
Explanation
Check previous messages to see why component <insert_3> was disabled.
Response
You may need to re-optimize the integration server, or specify a different level of JRE.
BIP10220
Node <insert_1> has been configured with policy <insert_2>, which has been configured with a securityIdentity property value of <insert_3>. This security identity has not been defined by using the mqsisetdbparms or mqsicredentials command.
Severity
20 : Error
Explanation
The node has been configured with a policy that defines a security identity to be used when connecting to an external system, but the security identity has not been configured for the server that it was deployed to.
Response
Either create the security identity in the vault (by using the mqsicredentials command) or change the value in the policy to refer to an identity that has been defined.
BIP10221
After executing the JSONata map for the <insert_2> node, the "messageType" value is not either "TEXT" or "BINARY", <insert_1> found.
Severity
20 : Error
BIP10222
After executing the JSONata map for the <insert_2> node, no value for <insert_1> was found.
Severity
20 : Error
BIP10223
The Debezium plug-in <insert_1>, which is specified by a policy for node <insert_2>, is at version <insert_4>, but the version of the embedded Debezium Engine is <insert_5>. The Debezium plug-in is installed at <insert_3>.
Severity
10 : Warning
Explanation
The version of the Debezium plug-in that was selected for the node is different from the version of the embedded Debezium Engine. The plug-in selected for the node might be compatible with the embedded engine, but it is preferable to use a plug-in of the same version.
Response
Download the matching version of the plug-in, as described in "Configuring the Change Data Capture node" in the IBM App Connect Enterprise documentation (https://www.ibm.com/docs/en/app-connect).
BIP10224
Designer Flow Editor starting initialization; version <insert_1> (64-bit)
Severity
0 : Information
Explanation
The designer flow editor is starting.
Response
No user action required.
BIP10225
Designer Flow Editor has finished initialization.
Severity
0 : Information
Explanation
The Designer Flow Editor has finished initialization.
Response
No user action required.
BIP10226
The value provided for MQMD header property <insert_1> is not a valid base64 encoded value.
Severity
20 : Error
Explanation
The MQMD header property <insert_1> must be provided as a base64 encoded value.
Response
Ensure the value provided is a valid base64 value.
BIP10227
An exception occurred invoking runtime function <insert_1> for connector <insert_2> and account <insert_3>.
Severity
20 : Error
Explanation
An exception occurred when invoking runtime function <insert_1>.
Response
Determine the cause of the problem by reviewing the following error messages. If the problem persists, contact your IBM support representative.
BIP10228
The application <insert_1> cannot start as it contains a Designer flow which requires processing before it can run on IBM App Connect Enterprise
Severity
20 : Error
Explanation
The application <insert_1> was created in a format that is suitable for deploying to IBM App Connect. This application requires additional processing before it can be deployed to IBM App Connect Enterprise, by using the mqsibar command.
Response
Use the mqsibar command to convert the BAR file used to deployed the application to a format that is suitable for deploying to App Connect Enterprise.