Message associated with number <insert_1> was not found: data supplied <insert_2>.
Severity
30 : Severe error
Explanation
A message number was used for which no associated message text could be found.
Response
This is an internal error. Contact your IBM support center.
BIP1014
You cannot view integration node <insert_1>.
Severity
30 : Severe error
Explanation
Administrative security has been enabled on this integration node, and you do not have read authority on it. This is required in order to view the integration node's properties or to see its list of available integration servers.
Response
Contact your integration node administrator.
BIP1017
A backup archive called <insert_1> was created successfully.
Severity
0 : Information
BIP1018
Unexpected exception in utility <insert_1>; method <insert_2>.
Severity
30 : Severe error
Explanation
An exception was caught by the <insert_1> utility in method <insert_2>. The exception text is: <insert_3>. The current operation will end.
Response
For XML parser errors check the XML is well-formed and the correct encoding is specified.
Retry the operation if possible. If the exception still occurs, contact your IBM support center.
BIP1019
Resource <insert_1> of type <insert_4> could not be found in <insert_2> of type <insert_5> in parent <insert_3> of type <insert_6>.
Severity
20 : Error
Explanation
The utility was asked to access the named resource <insert_1>, but this is not deployed in the specified location.
Response
Check that the (case-sensitive) message flow name has been entered correctly. Use the App Connect Enterprise Toolkit to ensure that the message flow has been deployed successfully.
Command Options:
'connectionSpec' is one of:
(a) '[--integration-node] <integrationNodeName>' : Name of a locally defined integration node
(b) '--integration-node-file (-n) <integrationNodeFileName>' : File containing remote integration node connection parameters (*.broker)
(c) '[[--integration-node] <integrationNodeName>] --admin-host (-i) <host> --admin-port (-p) <port>' : hostname/ipAddress and port of a remote integration node. 'integrationNodeName' optional for validation.
(d) '--admin-host (-i) <host> --admin-port (-p) <port>' : hostname/ipAddress and port of an independent integration server.
'--integration-server (-e) <server>' integration server name
'--all-integration-servers' indicates all integration servers
'--application (-k) <application>' application name
'--all-applications' indicates all applications
'--library (-y) <library>' static library name
'--flow (-m) <messageFlow>' message flow name
'--all-flows' indicates all message flows
'--timeout-seconds (-w) <timeout>' the amount of seconds before aborting the action.
'--detail-level <level> control detail level of response messages.
0 = display summary information
1 = display standard information (default)
2 = display detailed information
'--trace (-v) <traceFileName>' : send verbose internal trace to the specified file.
Command Options:
Command Options:
'connectionSpec' is one of:
(a) '[--integration-node] <integrationNodeName>' : Name of a locally defined integration node
(b) '--integration-node-file (-n) <integrationNodeFileName>' : File containing remote integration node connection parameters (*.broker)
(c) '[[--integration-node] <integrationNodeName>] --admin-host (-i) <host> --admin-port (-p) <port>' : hostname/ipAddress and port of a remote integration node. 'integrationNodeName' optional for validation.
(d) '--admin-host (-i) <host> --admin-port (-p) <port>' : hostname/ipAddress and port of an independent integration server.
'--integration-server (-e) <server>' integration server name
'--all-integration-servers' indicates all integration servers
'--application (-k) <application>' application name
'--all-applications' indicates all applications
'--library (-y) <library>' static library name
'--flow (-m) <messageFlow>' message flow name
'--all-flows' indicates all message flows
'--timeout-seconds (-w) <timeout>' the amount of seconds before aborting the action.
'--detail-level <level> control detail level of response messages.
0 = display summary information
1 = display standard information (default)
2 = display detailed information
'--trace (-v) <traceFileName>' : send verbose internal trace to the specified file.
BIP1026
Modifying the security cache of integration node <insert_1> integration server <insert_2>...
Severity
0 : Information
BIP1027
Starting message flow with URI <insert_1> ...
Severity
0 : Information
BIP1028
Stopping message flow with URI <insert_1> ...
Severity
0 : Information
BIP1029
Unable to load translated strings resource bundle <insert_1>.
Severity
20 : Error
Response
Please ensure that the product is installed correctly and that the translated strings resource bundles are available.
BIP1030
Message flow with URI <insert_1> is reported as started.
Severity
0 : Information
BIP1031
Message flow with URI <insert_1> is reported as stopped.
Severity
0 : Information
BIP1032
Invalid parameters.
Severity
20 : Error
Explanation
A parameter without a flag is not allowed on this command: <insert_1>.
Response
Reissue the command specifying valid options and flags.
BIP1033
Invalid parameters: <insert_1>.
Severity
20 : Error
Explanation
The following flag(s) are invalid, missing, or cannot be used together: <insert_1>.
Response
Reissue the command specifying valid options and flags.
BIP1034
Properties file <insert_1> could not be read.
Severity
20 : Error
Explanation
A utility was requested to read connection parameters from the properties file <insert_1>, but this file was not found, or contains invalid information.
Response
Reissue the command specifying a valid path and file name. If such a file is not available, Use the App Connect Enterprise Toolkit to generate one, or supply the connection parameters individually.
BIP1035
Property <insert_1> missing from properties file <insert_2>.
Severity
30 : Severe error
Explanation
The property named <insert_1> was expected to exist in the properties file <insert_2> but was not found.
Response
Include the property named <insert_1> in the properties file, and reissue the command.
BIP1036
Integration node port is not a number (<insert_1>).
Severity
30 : Severe error
Explanation
The supplied port value (<insert_1>) is not valid port number. This must be an integer value.
Response
Retry the command specifying a valid port number in the configuration or properties file.
BIP1037
The force option had an invalid value (<insert_1>). Valid values are 'normal' or 'restartExecutionGroup'.
Severity
30 : Severe error
Explanation
The supplied value for the force option is invalid. It must be either 'normal' or 'restartExecutionGroup' where normal stops the flow using the normal non-forced actions and restartExecutionGroup restarts the integration server.
Response
Retry the command specifying a valid value.
BIP1038
The integration server <insert_1> does not exist in integration node <insert_2>.
Severity
30 : Severe error
Response
Reissue the command specifying a valid integration server name.
BIP1039
Deploying BAR file <insert_3> to integration node <insert_1> (integration server <insert_2>) ...
Severity
0 : Information
BIP1040
Deploying BAR file <insert_2> to integration server <insert_1> ...
Severity
0 : Information
BIP1041
Integration node connection parameters could not be found
Severity
20 : Error
Explanation
A custom integration application could not connect to an integration node because no connection parameters were provided. Furthermore, no default connection parameters could be determined.
Response
Reissue the command, specifying a valid set of integration node connection parameters.
BIP1042
Command deprecated, please use policy projects instead.
Severity
0 : Information
BIP1044
Connecting to the queue manager...
Severity
0 : Information
BIP1046
Unable to connect with the queue manager (<insert_1>).
Severity
20 : Error
Explanation
The utility encountered a problem while attempting to connect to the queue manager to put a message to the integration node's request queue.
Response
Ensure that the correct connection parameters have been supplied to the utility. Also ensure that the queue manager is running and that the current user is able to access the queues beginning SYSTEM.BROKER. If this error text includes an MQ reason code, look up the meaning behind the error in the Application Programming Reference guide and proceed as appropriate.
BIP1047
The operation timed out waiting for a response from <insert_1>.
Severity
20 : Error
Explanation
The utility did not receive an expected response from the integration node or integration server at <insert_1> within a designated amount of time. The operation might have completed successfully, even though the response was not received.
Response
Ensure that the integration node or integration server is running and that the correct connection parameters have been supplied to the utility. Use the -w flag to increase the amount of time to wait for responses.
BIP1048
This command displays information about a BAR file.
Command options:
'-b barFileName' The name of the BAR file to display.
'-r' Recursively display the contents of applications and libraries.
'-v traceFileName' Verbose internal trace is sent to the specified file.
BIP1049
The BAR file does not exist.
Severity
20 : Error
Explanation
The bar file <insert_1> could not be found on the file system.
Response
Reissue the command specifying the location of a valid bar file.
BIP1050
The BAR file could not be read from the file system.
Severity
20 : Error
Explanation
While the file was being read, the following error occurred: <insert_1>
Response
Ensure that the file can be read by the current user, and that it is a valid BAR file. Correct the problem and reissue the command.
BIP1051
Reading Bar file using toolkit mqsireadbar...
Severity
0 : Information
BIP1052
Reading Bar file using runtime mqsireadbar...
Severity
0 : Information
BIP1053
The operation could not be completed by the integration node: <insert_1>
Severity
20 : Error
Response
Ensure that the correct parameters are supplied to the integration node and that the user is authorized to complete the operation. If the problem persists, contact your IBM support center.
BIP1054
The integration node <insert_1> is not running.
Severity
20 : Error
Explanation
In order for the commandline utility to work, the integration node needs to be running.
Response
Ensure that the integration node is running and that the correct connection parameters have been supplied to the utility.
BIP1055
The BAR file did not contain a top-level deployment descriptor.
Severity
10 : Warning
Explanation
The BAR file did not contain a top-level deployment descriptor. The command-line options that were supplied to the command were not set to search for application or library level deployment descriptors. Any overrides have not been applied.
Response
Ensure the bar file contains a top-level deployment descriptor or repeat the command with either the -k, -y, or -r flags set.
BIP1058
The integration node supplied the following message(s):
Severity
0 : Information
BIP1059
The operation could not be completed: <insert_1>
Severity
20 : Error
Response
Ensure that the correct parameters are supplied to the command, the user is authorized to complete the operation, and the installation files are correct. If the problem persists, contact your IBM support center.
BIP1060
Connecting to the integration node...
Severity
0 : Information
BIP1062
Removing the following objects from integration server <insert_2>: <insert_1>
Severity
0 : Information
BIP1063
Objects with the following name(s) could not be found on integration server <insert_2>: <insert_1>
Severity
10 : Warning
BIP1064
Removing message set <insert_1> from integration server <insert_2> ...
Severity
0 : Information
BIP1065
The CLASSPATH is incorrectly configured
Severity
30 : Severe error
Explanation
The utility was unable to start because a required set of Java classes could not be loaded from the CLASSPATH (<insert_1>).
Response
Add <insert_2> (from the installed product's classes directory) to the CLASSPATH environment variable and reissue the command.
BIP1071
The specified archive <insert_1> already exists.
Severity
30 : Severe error
Response
Reissue the command specifying a different archive name for the backup.
BIP1089
Ignoring the following name(s) as they are ambiguous on integration server <insert_2>: <insert_1>
Severity
10 : Warning
BIP1092
The deployment request was processed successfully.
Severity
0 : Information
BIP1093
The integration node rejected the deployment request.
Severity
20 : Error
BIP1095
The integration node has not yet responded to the deployment request.
Severity
10 : Warning
Explanation
The integration node did not respond to the deployment request within a reasonable amount of time. The request is queued for processing and will be completed when the integration node is able to do so.
Response
It is not usually necessary to repeat the deployment action. Increasing the value of the timeout period (-w) will allow the utility to wait for a longer period of time before this message is displayed.
BIP1096
The source <insert_1> has been deployed but there were one or more failures which may mean the deployed resources will be unable to execute.
Severity
20 : Error
Response
Use the proceeding messages to identify the cause of the failure(s).
BIP1097
An exception occurred while attempting to delete deployed resources from the integration server.
Severity
20 : Error
Response
Use the proceeding messages to identify the cause of the failure(s).
BIP1098
Message validation may be limited as XML schema compilation has been disabled.
Severity
10 : Warning
Explanation
Message validation may not be possible since deployed XML schema models will not be compiled. Message flow nodes may not be able to perform validation and cause a message flow failure.
Response
If message validation is required, ensure that property 'disableXMLSchemaCompilation' is set to 'false' in the integration server configuration.
BIP1113
The utility could not open file <insert_1> for writing trace output.
Severity
10 : Warning
Explanation
An attempt was made to open the file <insert_1> so that internal utility trace could be written there, but this was not successful.
Response
If the file already exists, ensure that it is not locked or in use by another application, and that the current user can write to it. If the file does not exist, ensure that the current user has the authority to write to the specified directory. Try specifying a different filename. If the problem persists, please contact your IBM support center.
BIP1115
Connected to the integration node <insert_1>.
Severity
0 : Information
BIP1117
The integration server was created successfully.
Severity
0 : Information
Explanation
The integration node has initialized the integration server.
Command options:
'integrationNodeSpec' is one of:
(a) '[--integration-node] <integrationNodeName>' : Name of a locally defined integration node
(b) '--integration-node-file (-n) <integrationNodeFileName>' : File containing remote integration node connection parameters (*.broker)
(c) '[[--integration-node] <integrationNodeName>] --admin-host (-i) <host> --admin-port (-p) <port>' : hostname/ipAddress and port of a remote integration node. 'integrationNodeName' optional for validation.
'--integration-server (-e) <integrationServerName>' : name of the new integration server
'--timeout-seconds (-w) <timeoutSecs>' : maximum number of seconds to wait for the integration server to be created (default is 60)
'--trace (-v) <traceFileName>' : send verbose internal trace to the specified file.
BIP1122
Deletes an integration server and all resources that are deployed to it.
Command options:
'integrationNodeSpec' is one of:
(a) '[--integration-node] <integrationNodeName>' : Name of a locally defined integration node
(b) '--integration-node-file (-n) <integrationNodeFileName>' : File containing remote integration node connection parameters (*.broker)
(c) '[[--integration-node] <integrationNodeName>] --admin-host (-i) <host> --admin-port (-p) <port>' : hostname/ipAddress and port of a remote integration node. 'integrationNodeName' optional for validation.
'--integration-server (-e) <integrationServerName>' : name of the new integration server
'--timeout-seconds (-w) <timeoutSecs>' : maximum number of seconds to wait for the integration server to be deleted (default is 60)
'--trace (-v) <traceFileName>' : send verbose internal trace to the specified file.
BIP1123
The integration server already exists.
Severity
20 : Error
Explanation
The utility was asked to create integration server <insert_2> on integration node <insert_1>, but it already exists.
Response
Check that the names of the integration server and integration node are correct and reissue the command.
BIP1124
Creating integration server <insert_2> on integration node <insert_1>...
Severity
0 : Information
BIP1125
The integration server could not be created.
Severity
20 : Error
Explanation
The utility was asked to create integration server <insert_2> on integration node <insert_1>, but it was not completed successfully by the integration node.
Response
Determine the cause of the problem by reviewing the following error messages. If the problem persists, contact your IBM support representative.
BIP1127
This command will implicitly remove the following resource(s): <insert_1>
Severity
0 : Information
BIP1128
A duplicate definition for message flow <insert_1> has been detected in the deployment. The message flow configuration file <insert_2> has been replaced with file <insert_3>.
Severity
10 : Warning
Explanation
The deployment contains a message flow with name <insert_1> that is defined by more than one configuration source file. The message flow has been deployed using the most recent configuration file.
Response
Check the files that are packaged in the deployment and ensure there is only one configuration file that defines the message flow.
BIP1129
The integration server could not be deleted.
Severity
20 : Error
Explanation
The utility was asked to delete integration server <insert_2> on integration node <insert_1>, but it was not completed successfully.
Response
Determine the cause of the problem by reviewing the following error messages. If the problem persists, contact your IBM support representative.
BIP1130
Deleting the integration server from integration node <insert_1>...
Severity
0 : Information
BIP1134
The overrides file does not exist.
Severity
20 : Error
Explanation
The overrides file <insert_1> could not be found on the file system.
Response
Reissue the command specifying the location of a valid overrides file.
BIP1135
The overrides file could not be read from the file system.
Severity
20 : Error
Explanation
While the file was being read, the following error occurred: <insert_1>
Response
Ensure that the file can be read by the current user, and that it is a valid overrides file. Correct the problem and reissue the command.
BIP1136
This command overrides properties in a BAR file.
Severity
0 : Information
Explanation
Syntax:
mqsiapplybaroverride -b barFileName [-p overridesFile] [-m manualOverrides] [-k applicationName] [-y libraryName] [-r] [-o outputFile] [-v traceFileName] Command options:
'-b barFileName' The name of the BAR file (in zip format) to be overridden.
'-p overridesFile' The file name of the plain text file that contains one of these items: the integration node properties to be overwritten, the entire new deployment descriptor, or a BAR file that contains the entire new deployment descriptor.
'-m manualOverrides' A comma separated list of key=value pairs that describe the overrides to apply. On Windows systems, the list must be enclosed in quotation marks (""). If used in conjunction with -p, the overrides that are specified with the -m parameter are performed after all overrides that are specified by the -p parameter have been made.
'-k applicationName' The name of the application to which the overrides will be applied.
'-y libraryName' The name of the static library or shared library to which the overrides will be applied.
'-r' requests that overrides are applied recursively through applications and libraries.
'-o outputFile' The name of the output bar file to which the bar file changes are to be made. If this name is not specified, the input file is overwritten.
'-v traceFileName' Verbose internal trace is sent to the specified file.
Note: Overrides must be supplied either in the form FLOW#NODE.PROPERTY=NEWVALUE or in the form OLDVALUE=NEWVALUE. If the latter form is used, OLDVALUE must already be an overridden value in the deployment descriptor. Specify FLOW#NODE.PROPERTY on its own to remove an override.
BIP1137
Applying overrides using toolkit <insert_1>...
Severity
0 : Information
BIP1138
Applying overrides using runtime <insert_1>...
Severity
0 : Information
BIP1139
Replacing <insert_2> with <insert_1>...
Severity
0 : Information
BIP1140
Overriding property <insert_1> with <insert_2> in <insert_3> ...
Severity
0 : Information
BIP1141
Replacing <insert_3> occurrence(s) of value <insert_1> with <insert_2> in <insert_4> ...
Severity
0 : Information
BIP1142
Removing override for property <insert_1> in <insert_2> ...
Severity
0 : Information
BIP1143
Saving Bar file <insert_1>...
Severity
0 : Information
BIP1144
Ignoring property override <insert_1> in <insert_2>
Severity
10 : Warning
Explanation
The property override <insert_1> was ignored because it does not correspond to an existing property value that can be replaced, nor is it in the correct format for a property identifier.
Response
If the override was intended to be a property identifier, ensure that the format of the identifier is 'flow#node.property' or 'flow#property'. Use the mqsireadbar command to list the property names that can be overridden in a specific BAR file. . If the override was intended to be a an existing property value, ensure that the property value is currently set in the deployment descriptor. If the value exists in the deployment descriptor, it may not have been found because it had already been set to something else earlier in the override processing. For example, if using mqsiapplybaroverride with both the -p and -m flags set, note that overrides specified through -p are made before overrides specified through -m. This means that the manual overrides will be made to a deployment descriptor that has already had any substitutions from the overrides file made.
BIP1145
The file <insert_1> could not be found in <insert_2>.
Severity
20 : Error
Explanation
A request was made to access the file <insert_1> in <insert_2> and this file could not be found.
Response
Check that the file is available in the target resource.
BIP1146
Failed to apply override <insert_1> because the deployment descriptor <insert_2> does not exit.
Severity
20 : Error
Explanation
A deployment descriptor will not exist for extract migration from an earlier version.
Response
Migrate the source of the resources and redeploy to enable applying overrides.
BIP1147
The BAR file <insert_1> could not be written.
Severity
20 : Error
Explanation
The system tried to update the BAR file, but could not write to the bar file. This might be because the file, if it already exists, is read-only, or because the file system is write-protected.
Response
Ensure that the bar file can be written to, and reissue the command.
BIP1148
The BAR file <insert_1> could not be read.
Severity
20 : Error
Response
Ensure that the bar file can be read, and reissue the command.
BIP1150
<insert_1> is an invalid server name. Server could not be created.
Severity
20 : Error
BIP1151
Server <insert_1> already exists with the same name for node <insert_2>. Server could not be created.
Severity
20 : Error
Explanation
The specified Integration Server with name <insert_1> already exists for node <insert_2>.
Response
Ensure that the specified Integration Server name is unique. On some platforms upper case and lower case characters are considered equivalent.
BIP1180
The application or library <insert_1> cannot be deployed as its name contains invalid characters.
Severity
20 : Error
Explanation
The application or library with name <insert_1> cannot be deployed as the name contains invalid characters.
Response
Ensure that the name of the application or library only contains valid characters.
BIP1181
Started all message flows on integration server <insert_1> (Application <insert_2>, Library <insert_3>).
Severity
0 : Information
BIP1182
All message flows on integration server <insert_1> started.
Severity
0 : Information
BIP1183
Stopped all message flows on integration server <insert_1> (Application <insert_2>, Library <insert_3>).
Severity
0 : Information
BIP1184
All message flows on integration server <insert_1> stopped.
Severity
0 : Information
BIP1185
You cannot view integration server <insert_2> on integration node <insert_1>.
Severity
30 : Severe error
Explanation
Administrative security has been enabled on this integration node, and you do not have read authority to the integration server <insert_2>. This is required in order to view the integration server's properties or to see its list of available message flows.
Response
Contact your integration node administrator.
BIP1186
Starting the integration server with URI <insert_1>...
Severity
0 : Information
BIP1187
The integration server with URI <insert_1> is reported as started.
Severity
0 : Information
BIP1188
Stopping the integration server with URI <insert_1>...
Severity
0 : Information
BIP1189
The integration server with URI <insert_1> is reported as stopped.
Severity
0 : Information
BIP1190
The file <insert_1> is not a valid BAR file.
Severity
20 : Error
Explanation
The utility was asked to deploy <insert_1> but the file is not in the correct format. The file was not deployed.
Response
Use the App Connect Enterprise Toolkit, ibmint command or mqsicreatebar command to generate a Bar file and try the command again.
BIP1191
The file <insert_1> could not be read.
Severity
20 : Error
Explanation
The utility was asked to deploy <insert_1> but the file could not be read. The file was not deployed.
Response
Ensure that the file exists and that the current user has authority to read it.
BIP1192
Starting application with URI <insert_1> ...
Severity
0 : Information
BIP1193
Stopping application with URI <insert_1>...
Severity
0 : Information
BIP1194
Application with URI <insert_1> is reported as started.
Severity
0 : Information
BIP1195
Application with URI <insert_1> is reported as stopped.
Severity
0 : Information
BIP1196
One or more applications on integration server <insert_1> failed to start fully.
Severity
20 : Error
BIP1197
All applications on integration server <insert_1> started.
Severity
0 : Information
BIP1198
One or more applications on integration server <insert_1> failed to stop.
Severity
20 : Error
BIP1199
All applications on integration server <insert_1> stopped.
Severity
0 : Information
BIP1200
The requested resource <insert_1> does not exist in the RDF store.
Severity
30 : Severe error
Explanation
An attempt to access a resource failed because the resource does not exist in the RDF store.
Response
Check that the name of the resource was correctly entered and try again.
BIP1231
Integration node <insert_1> is an active multi-instance or high availability integration node with administration URI <insert_3>
The multi-instance or High Availability integration node <insert_1> has stopped.
Severity
0 : Information
Response
Start the integration node for more information.
BIP1236
The managed application <insert_1> of type <insert_2> cannot be deployed to integration server <insert_4> on integration node <insert_5>. A managed application of type <insert_3> with the same name is already deployed.
Severity
20 : Error
Explanation
A managed application cannot be replaced with a managed application of a different type.
Response
To deploy the managed application <insert_1>, you must undeploy the managed application <insert_1>.
BIP1237
The unmanaged application <insert_1> cannot be deployed to integration server <insert_3> on integration node <insert_4>. A managed application of type <insert_2> with the same name is already deployed.
Severity
20 : Error
Explanation
A managed application cannot be replaced with an unmanaged application.
Response
To deploy the unmanaged application <insert_1>, you must undeploy the managed application <insert_1>.
BIP1238
The managed application <insert_1> of type <insert_2> cannot be deployed to integration server <insert_3> on integration node <insert_4>. An unmanaged application with the same name is already deployed.
Severity
20 : Error
Explanation
An unmanaged application cannot be replaced with a managed application.
Response
To deploy the managed application <insert_1>, you must undeploy the unmanaged application <insert_1>.
BIP1239
Application <insert_1> references shared library <insert_2>, which is not deployed to the integration server.
Severity
20 : Error
BIP1240
Shared library <insert_1> references shared library <insert_2>, which is not deployed to the integration server.
Severity
20 : Error
BIP1241
The application <insert_1> cannot be deployed to integration server <insert_2> on integration node <insert_3>. A shared library with the same name is already deployed.
Severity
20 : Error
Explanation
A shared library cannot be replaced with an application.
Response
To deploy the application <insert_1>, you must undeploy the shared library <insert_1>.
BIP1242
The shared library <insert_1> cannot be deployed to integration server <insert_2> on integration node <insert_3>. An application with the same name is already deployed.
Severity
20 : Error
Explanation
An application cannot be replaced with a shared library.
Response
To deploy the shared library <insert_1>, you must undeploy the application <insert_1>.
BIP1243
The static library <insert_1> cannot be deployed to integration server <insert_2> on integration node <insert_3>. A shared library with the same name is already deployed.
Severity
20 : Error
Explanation
A shared library cannot be replaced with a static library.
Response
To deploy the static library <insert_1>, you must undeploy the shared library <insert_1>.
BIP1244
The shared library <insert_1> cannot be deployed to integration server <insert_2> on integration node <insert_3>. A static library with the same name is already deployed.
Severity
20 : Error
Explanation
A static library cannot be replaced with a shared library.
Response
To deploy the shared library <insert_1>, you must undeploy the static library <insert_1>.
BIP1245
The application <insert_1> cannot be deployed to integration server <insert_2> on integration node <insert_3>. The application <insert_1> has been marked as do not deploy.
Severity
20 : Error
Explanation
The 'deployable' attribute in the application descriptor file for application <insert_1> is set to 'false'. The application cannot be deployed until the 'deployable' attribute is set to 'true'.
Response
Investigate why the application <insert_1> has been marked as do not deploy. If it was marked in error, modify the application descriptor for application <insert_1> so that the 'deployable' attribute is set to 'true'.
BIP1246
The library <insert_1> cannot be deployed to integration server <insert_2> on integration node <insert_3>. The library <insert_1> has been marked as do not deploy.
Severity
20 : Error
Explanation
The 'deployable' attribute in the library descriptor file for library <insert_1> is set to 'false'. The library cannot be deployed until the 'deployable' attribute is set to 'true'.
Response
Investigate why the library <insert_1> has been marked as do not deploy. If it was marked in error, modify the library descriptor for library <insert_1> so that the 'deployable' attribute is set to 'true'.
BIP1247
The shared library <insert_1> cannot be deployed to integration server <insert_2> on integration node <insert_3>. The shared library <insert_1> has been marked as do not deploy.
Severity
20 : Error
Explanation
The 'deployable' attribute in the library descriptor file for shared library <insert_1> is set to 'false'. The shared library cannot be deployed until the 'deployable' attribute is set to 'true'.
Response
Investigate why the shared library <insert_1> has been marked as do not deploy. If it was marked in error, modify the library descriptor for shared library <insert_1> so that the 'deployable' attribute is set to 'true'.
BIP1248
The library <insert_1> in application <insert_2> cannot be deployed to integration server <insert_3> on integration node <insert_4>. The library <insert_1> has been marked as do not deploy.
Severity
20 : Error
Explanation
The 'deployable' attribute in the library descriptor file for library <insert_1> is set to 'false'. The library cannot be deployed until the 'deployable' attribute is set to 'true'.
Response
Investigate why the library <insert_1> has been marked as do not deploy. If it was marked in error, modify the library descriptor for library <insert_1> so that the 'deployable' attribute is set to 'true'.
BIP1249
Shared library <insert_1> is referenced by application <insert_2>.
Severity
0 : Information
BIP1250
Shared library <insert_1> is referenced by shared library <insert_2>.
Severity
0 : Information
BIP1251
Creates a backup file for the specified integration node.
Command Options:
'integrationNodeName' name of integration node to backup.
'-d directory' name of the directory the backup file will be written to.
'-a archiveName' name of the file (defaults to 'integrationNodeName_yyMMdd_HHmmss.zip')
'-f' force incomplete backup files to be created if any part of the integration node's configuration cannot be read
'-v traceFileName' send verbose internal trace to the specified file.
BIP1252
Creating backup file <insert_2> for integration node <insert_1>.
Severity
0 : Information
BIP1253
Failed to backup the integration node <insert_1> (error <insert_2>)
Severity
30 : Severe error
Explanation
At least one file in the integration node's configuration could not be backed up.
Response
Check user access to the backup or restore directory and reissue the command. If this problem persists contact your IBM support center.
BIP1254
The integration node <insert_1> cannot be found.
Severity
30 : Severe error
Explanation
In order to backup or restore an integration node's configuration, an integration node of that name must first exist on the machine on which the command is run.
Response
Check that the name of the integration node has been entered correctly and that the integration node has been created successfully.
BIP1255
The specified directory <insert_1> cannot be located.
Severity
30 : Severe error
Response
Reissue the command specifying a valid directory that exists and has write access to create the backup file in.
BIP1256
A backup of the integration node's configuration could not be created because the integration node is using an external system database (FADLevel=<insert_1>)
Severity
20 : Error
Explanation
A backup of the integration node's configuration cannot be taken because the integration node is not of the required version. The command was run against a version of the integration node that requires a system database, which cannot be backed up using this command.
Response
Consult the documentation for the existing version of the integration node for information on how to back it up.
BIP1257
Could not back up the file <insert_1>. (Error: <insert_2>)
Severity
10 : Warning
BIP1258
The backup file that was created for integration node <insert_1> is incomplete; the following number of files are missing: <insert_2>
Severity
10 : Warning
Explanation
A backup file was created but it might not contain sufficient information to allow it to be successfully restored.
Response
Previous messages show which files could not be backed up. If you are sure that these files are not a necessary part of the integration node's configuration, this error can be ignored. If any of the missing files are required, or if you are unsure as to whether they are required, determine why the file cannot be read and retry the command. If possible, stop the integration node before retrying the command.
BIP1259
A backup for integration node <insert_1> could not be created because the following number of files could not be backed up: <insert_2>
Severity
20 : Error
Explanation
A backup file was not created because it might not contain sufficient information to allow it to be successfully restored.
Response
Previous messages show which files could not be backed up. Investigate why these files could not be backed up, fix the problem and try again. If you are sure that the failed files are not a necessary part of the integration node's configuration, rerun the command using the -f flag to force the creation of an incomplete backup. If possible, stop the integration node before retrying the command.
BIP1260
Restoring from an incomplete backup.
Severity
10 : Warning
Explanation
When the backup file was created, the following files were not backed up: <insert_1> The integration node might not work as expected.
BIP1261
Restores an integration node's configuration from a backup file.
Command Options:
'[--integration-node] <integrationNodeName>' : name of the integration node that will be overwritten
'--directory (-d) <directory>' : name of the directory the backup file will be read from
'--archive-name (-a) <archiveName>' : name of the backup file to restore
'--config-restore (-c)' : restore common configuration. If this flag is specified, the command will additionally restore configuration from the backup file which might be shared with other integration nodes on the same machine (for instance, profiles)
'--trace (-v) traceFileName' send verbose internal trace to the specified file.
BIP1262
Could not delete the existing configuration of integration node <insert_1>.
Severity
30 : Severe error
Explanation
In order to restore the integration node's configuration, it is first necessary to delete any existing configuration files for the integration node. At least one file from this configuration could not be deleted. Previous message(s) describe which file(s) could not be deleted.
Response
Check that the integration node is not running. Check that the current user has authority to read the file and write to the directory described by the environment variable MQSI_REGISTRY and try the command again. If the problem persists contact your IBM support center.
BIP1263
Failed to restore the integration node <insert_1>. (Error = <insert_2>)
Severity
30 : Severe error
Explanation
At least one file in the integration node's configuration could not be restored. The integration node might be in an inconsistent state.
Response
Check that the integration node is not running. Check that the current user has authority to read the file and write to the directory described by the environment variable MQSI_REGISTRY and try the command again. If the problem persists contact your IBM support center.
BIP1264
The file <insert_1> cannot be found or is not a valid integration node backup file.
Severity
30 : Severe error
Response
Reissue the command specifying a valid path and file name for the backup file.
BIP1265
An error occurred while restoring the file <insert_1>: <insert_2>
Severity
30 : Severe error
Explanation
It was not possible to restore the integration node's configuration. The integration node might be in an inconsistent state.
Response
Ensure that the integration node is not running. Check that the current user has the necessary permissions to write to the filesystem and that there is sufficient disk space available. Correct the problem and run the command again.
BIP1266
Deleting the existing configuration of integration node <insert_1> ...
Severity
0 : Information
BIP1267
Restoring all configuration information from backup archive <insert_1>...
Severity
0 : Information
BIP1268
Restoring integration node configuration information from backup archive <insert_1>...
File <insert_1> is deployed to integration server <insert_2>. (Shared library <insert_7>)
Severity
0 : Information
Explanation
Deployed: <insert_3> in Bar file <insert_4>
Last edited: <insert_5>
Keywords: <insert_6>
BIP1273
Shared library <insert_1> is deployed to integration server <insert_2>.
Severity
0 : Information
Explanation
Deployed: <insert_3> in BAR file <insert_4>
Last edited: <insert_5>
Long description: <insert_6>
Keywords: <insert_7>
BIP1274
Library <insert_1> is deployed to integration server <insert_2>. (Application <insert_8>)
Severity
0 : Information
Explanation
Deployed: <insert_3> in BAR file <insert_4>
Last edited: <insert_5>
Long description: <insert_6>
Keywords: <insert_7>
BIP1275
Application <insert_1> on integration server <insert_2> is running.
Severity
0 : Information
Explanation
Deployed: <insert_3> in Bar file <insert_4>
Last edited: <insert_5>
UUID <insert_8>
Start mode: <insert_9>
Java isolation: <insert_10>
Long description: <insert_6>
Keywords: <insert_7>
BIP1276
Application <insert_1> on integration server <insert_2> is stopped.
Severity
0 : Information
Explanation
Deployed: <insert_3> in Bar file <insert_4>
Last edited: <insert_5>
UUID <insert_8>
Start mode: <insert_9>
Java isolation: <insert_10>
Long description: <insert_6>
Keywords: <insert_7>
BIP1277
Message flow <insert_1> on integration server <insert_2> is running. (Application <insert_10>, Library <insert_11>)
Severity
0 : Information
Explanation
Additional thread instances: <insert_3>
Deployed: <insert_4> in Bar file <insert_5>
Last edited: <insert_6>
Start mode: <insert_13>
UUID: <insert_12>
Long description: <insert_9>
User-defined property names: <insert_7>
Keywords: <insert_8>
BIP1278
Message flow <insert_1> on integration server <insert_2> is stopped. (Application <insert_10>, Library <insert_11>)
Severity
0 : Information
Explanation
Additional thread instances: <insert_3>
Deployed: <insert_4> in Bar file <insert_5>
Last edited: <insert_6>
Start mode: <insert_13>
UUID: <insert_12>
Long description: <insert_9>
User-defined property names: <insert_7>
Keywords: <insert_8>
BIP1279
A backup of the integration node's configuration specifies an invalid version (FADLevel=<insert_1>)
Severity
20 : Error
Explanation
A backup of the integration node's configuration cannot be used because the version of the integration node is not recognized.
Response
For information about how to back up the integration node, consult the documentation for the version of IBM Integration Bus or App Connect Enterprise in which the integration node was created.
BIP1280
The number of IBM App Connect Enterprise installations on this machine is <insert_1>.
Severity
0 : Information
Explanation
<insert_2>
BIP1281
No integration nodes have been defined on this machine.
Severity
0 : Information
BIP1282
No integration servers have been defined on integration node <insert_1>.
Severity
0 : Information
BIP1283
There is nothing deployed to integration server <insert_1>.
Severity
0 : Information
BIP1284
Integration node <insert_1> with default queue manager <insert_2> and administration URI <insert_9> is running.
Command Options:
'-all-integration-nodes (-a)' list integration nodes of all versions on this machine
'integrationNodeSpec' list integration servers configured for an integration node; is one of:
(a) '[--integration-node] <integrationNodeName>' : Name of a locally defined integration node
(b) '--integration-node-file (-n) <integrationNodeFileName>' : File containing remote integration node connection parameters (*.broker)
(c) '[[--integration-node] <integrationNodeName>] --admin-host (-i) <host> --admin-port (-p) <port>' : hostname/ipAddress and port of a remote integration node. 'integrationNodeName' optional for validation.
(d) '[[--integration-node] <integrationNodeName>] -i uri' : URI for the remote integration node in the form tcp://[<user>[:<password>]@]<host>:<port>
If a user name and password are supplied, any URI Reserved characters in the password must be percent-encoded.
'--integration-server (-e) <integrationServerName>' list deployed objects configured for an integration server.
'--application (-k) <applicationName>' list deployed objects configured for an application.
'--library (-y) <libraryName>' list deployed objects configured for a shared library, or static library when application (-k) also specified.
'--recursive (-r)' recursive (display information on subcomponents, ignored for -d 0)
'--detail-level (-d) <detailLevel>' control how much information to display. Valid values are:
0 = display minimal information (identical to older versions of mqsilist)
1 = display one-line summary per object (default)
2 = display detailed information
'--timeout-seconds (-w) <timeoutSecs>' : maximum number of seconds to wait for any integration node to respond (default is 60)
'--trace (-v) <traceFileName>' : send verbose internal trace to the specified file.
BIP1292
The multi-instance or High Availability integration node <insert_1> on queue manager <insert_2> has stopped.
Severity
0 : Information
Response
Start the integration node for more information.
BIP1293
Integration node <insert_1> is a multi-instance integration node running in standby mode on queue manager <insert_2>.
Severity
0 : Information
BIP1294
The integration server <insert_1> is not available.
Severity
20 : Error
Explanation
The specified integration server could not be found in the backup.
Response
Check you have backed up the correct integration node. For information about how to back up the integration node, consult the documentation for the version of IBM Integration Bus or App Connect Enterprise in which the integration node was created.
BIP1295
Integration node <insert_1> is an active multi-instance or High Availability integration node that is running on queue manager <insert_2>.
Integration node <insert_1> is stopped. It is a multi-instance integration node and will be started as a IBM MQ service by queue manager <insert_2>.
Severity
0 : Information
BIP1297
The integration server <insert_1> is not available. Available integration servers are: <insert_2> .
Severity
20 : Error
Explanation
The specified integration server could not be found in the backup.
Response
Check you have backed up the correct integration node. For information about how to back up the integration node, consult the documentation for the version of IBM Integration Bus or App Connect Enterprise in which the integration node was created.
BIP1298
Integration node <insert_1> is stopped. It will be started as a IBM MQ service by queue manager <insert_2>.
Severity
0 : Information
BIP1299
File <insert_1> is deployed to integration server <insert_2>. (Application <insert_7>, Library <insert_8>)
Severity
0 : Information
Explanation
Deployed: <insert_3> in Bar file <insert_4>
Last edited: <insert_5>
Keywords: <insert_6>
BIP1301
The application <insert_1> cannot be deployed because it depends on the shared library <insert_2>, which is not deployed to the integration server.
Severity
20 : Error
Response
Deploy the shared library <insert_2> to the integration server. Alternatively, remove the dependency on the shared library <insert_2> from the application <insert_1>.
BIP1302
The shared library <insert_1> cannot be deployed because it depends on the shared library <insert_2>, which is not deployed to the integration server.
Severity
20 : Error
Response
Deploy the shared library <insert_2> to the integration server. Alternatively, remove the dependency on the shared library <insert_2> from the shared library <insert_1>.
BIP1303
The shared library <insert_1> cannot be undeployed from the integration server because the deployed application <insert_2> depends on it.
Severity
20 : Error
Response
To undeploy the shared library <insert_1>, you must also undeploy the application <insert_2>.
BIP1304
The shared library <insert_1> cannot be undeployed from the integration server because the deployed shared library <insert_2> depends on it.
Severity
20 : Error
Response
To undeploy the shared library <insert_1>, you must also undeploy the shared library <insert_2>. <insert_1>.
BIP1305
The application <insert_1> is attempting to use shared library <insert_2>, but the application <insert_1> does not reference the shared library <insert_2> explicitly.
Severity
20 : Error
Response
Update the application <insert_1> so that it explicitly references the shared library <insert_2>.
BIP1306
The shared library <insert_1> is attempting to use shared library <insert_2>, but the shared library <insert_1> does not reference the shared library <insert_2> explicitly.
Severity
20 : Error
Response
Update the shared library <insert_1> so that it explicitly references the shared library <insert_2>.
BIP1307
The shared library <insert_1> is being updated. The application <insert_2> references this shared library and will be updated automatically to reflect the changes in the shared library.
Severity
0 : Information
BIP1308
The shared library <insert_1> is being updated. The shared library <insert_2> references this shared library and will be updated automatically to reflect the changes in the shared library.
Severity
0 : Information
BIP1309
An invalid configuration request to create a library <insert_1> as a child of library <insert_2> was received.
Severity
20 : Error
Explanation
A library cannot be created as a child of another library.
Response
Remove the child library <insert_1> from the library <insert_2>.
BIP1310
One or more shared libraries are being deployed, but a circular dependency involving shared library <insert_1> was detected.
The invalid dependency chain for this shared library is <insert_2>.
Severity
20 : Error
Explanation
A shared library cannot depend on itself.
Response
Alter one or more of the shared libraries in the invalid dependency chain to remove the circular dependency. If the dependencies between the shared libraries are being modified, ensure that all the modified shared libraries are deployed at the same time.
BIP1311
The node <insert_1> in message flow <insert_2> cannot be started because it specifies the message domain <insert_3> and an invalid message model <insert_4>. The message model <insert_4> is invalid because it specifies a message model for a shared library <insert_5> that is not available.
Severity
20 : Error
Explanation
The specified node specifies a message model for a shared library that is not available.
Response
Check that the shared library specified exists and is deployed to the integration server, and that the application or shared library containing the specified message flow explicitly references that shared library.
BIP1312
A parser for the message domain <insert_1> is trying to use an invalid message model <insert_2>. The message model <insert_2> is invalid because it specifies a message model for a shared library <insert_3> that is not available.
Severity
20 : Error
Explanation
A parser is trying to use a message model for a shared library that is not available.
Response
Check that the specified shared library exists and is deployed to the integration server. Also check that the application or shared library that contains the specified message flow references that shared library explicitly.
The invalid message model might be set as a property on a node, as the value of the 'MessageSet' element in the 'Properties' tree, or as a method parameter in custom ESQL, Java or .NET transformation code.
If the parser is being created by a node in a subflow within a shared library and you want to use the message model for that shared library, then do not specify a message model.
When no message model is specified, the message model for the container that owns the current message flow or subflow is used.
BIP1313
A node in the shared library <insert_1> is attempting to use resources in the same library by specifying the name of that shared library.
Severity
20 : Error
Explanation
Shared libraries cannot explicitly refer to themselves.
Response
When you configure a node in a shared library to use resources in that same library, do not specify the name of the shared library.
BIP1314
The SOAP node <insert_1> in message flow <insert_2> cannot be deployed because it specifies the WSDL file <insert_3> in shared library <insert_4>. The shared library <insert_4> is not available.
Severity
20 : Error
Explanation
The specified SOAP node specifies a WSDL file in a shared library that is not available.
Response
Check that the specified shared library exists and is deployed to the integration server. Also check that the application or shared library that contains the specified message flow references that shared library explicitly.
BIP1315
The Java compute node <insert_1> in message flow <insert_2> cannot be deployed because it specifies a Java class in shared library <insert_3>. The shared library <insert_3> is not available.
Severity
20 : Error
Explanation
The specified Java compute node specifies a Java class in a shared library that is not available.
Response
Check that the specified shared library exists and is deployed to the integration server. Also check that the application or shared library that contains the specified message flow references that shared library explicitly.
BIP1316
The PHP compute node <insert_1> in message flow <insert_2> cannot be deployed because it specifies a PHP file <insert_3> in shared library <insert_4>. The shared library <insert_4> is not available.
Severity
20 : Error
Explanation
The specified PHP compute node specifies a PHP file in a shared library that is not available.
Response
Check that the specified shared library exists and is deployed to the integration server. Also check that the application or shared library that contains the specified message flow references that shared library explicitly.
BIP1317
The node <insert_1> in message flow <insert_2> cannot be deployed because it specifies the message domain <insert_3> and an invalid message model <insert_4>. The message model <insert_4> is invalid because it specifies a message model for the same shared library <insert_5> that contains the node.
Severity
20 : Error
Explanation
Shared libraries cannot explicitly refer to themselves.
Response
When you configure a node in a shared library to use resources in that same library, do not specify the name of the shared library.
BIP1318
A parser for the message domain <insert_1> is trying to use an invalid message model <insert_2>. The message model <insert_2> is invalid because it specifies a message model for the same shared library <insert_3> that contains the node that created the parser.
Severity
20 : Error
Explanation
Shared libraries cannot explicitly refer to themselves.
Response
The invalid message model might be set as a property on a node, as the value of the 'MessageSet' element in the 'Properties' tree, or as a method parameter in custom ESQL, Java or .NET transformation code.
If you want to use the message model for the shared library that contains the node that created the parser, then do not specify a message model.
When no message model is specified, the message model for the container that owns the current message flow or subflow is used.
BIP1319
The SOAP node <insert_1> in message flow <insert_2> cannot be deployed because it specifies the WSDL file <insert_3> in the same shared library <insert_4> that contains the node.
Severity
20 : Error
Explanation
Shared libraries cannot explicitly refer to themselves.
Response
When you configure a node in a shared library to use resources in that same library, do not specify the name of the shared library.
BIP1320
The Java compute node <insert_1> in message flow <insert_2> cannot be deployed because it specifies a Java class in the same shared library <insert_3> that contains the node.
Severity
20 : Error
Explanation
Shared libraries cannot explicitly refer to themselves.
Response
When you configure a node in a shared library to use resources in that same library, do not specify the name of the shared library.
BIP1321
The PHP compute node <insert_1> in message flow <insert_2> cannot be deployed because it specifies a PHP file <insert_3> in the same shared library <insert_4> that contains the node.
Severity
20 : Error
Explanation
Shared libraries cannot explicitly refer to themselves.
Response
When you configure a node in a shared library to use resources in that same library, do not specify the name of the shared library.
BIP1322
The shared library <insert_1> is being deleted. The application <insert_2> references this shared library and will be updated automatically to reflect the deletion of the shared library.
Severity
0 : Information
BIP1323
The shared library <insert_1> is being deleted. The shared library <insert_2> references this shared library and will be updated automatically to reflect the deletion of the shared library.
Severity
0 : Information
BIP1324
The mapping node <insert_1> in message flow <insert_2> cannot be deployed because it specifies a map <insert_3> in shared library <insert_4>. The shared library <insert_4> is not available.
Severity
20 : Error
Explanation
The specified mapping node specifies a map in a shared library that is not available.
Response
Check that the specified shared library exists and is deployed to the integration server. Also check that the application or shared library that contains the specified message flow references that shared library explicitly.
BIP1325
Integration node <insert_1> with administration URI <insert_3> is running.
The mapping node <insert_1> in message flow <insert_2> cannot be deployed because it specifies a map <insert_3> in the same shared library <insert_4> that contains the node.
Severity
20 : Error
Explanation
Shared libraries cannot explicitly refer to themselves.
Response
When you configure a node in a shared library to use resources in that same library, do not specify the name of the shared library.
BIP1328
The Java method <insert_1> cannot be loaded because the ESQL definition specifies that the Java method must be loaded from the classloader for shared library <insert_2>. The shared library <insert_2> is not available.
Severity
20 : Error
Explanation
The ESQL definition for the specified Java method specifies that the Java method must be loaded from a classloader for a shared library that is not available.
Response
Check that the specified shared library exists and is deployed to the integration server. Also check that the application or shared library that contains the specified message flow references that shared library explicitly.
BIP1329
The Java method <insert_1> cannot be loaded because the ESQL definition specifies that the Java method must be loaded from the classloader for the same shared library <insert_2> that contains the ESQL definition.
Severity
20 : Error
Explanation
Shared libraries cannot explicitly refer to themselves.
Response
When you configure a node in a shared library to use resources in that same library, do not specify the name of the shared library.
BIP1330
The subflow <insert_1> in shared library <insert_2> cannot be deployed because it is in the default integration node schema.
Severity
20 : Error
Explanation
Subflows in shared libraries cannot be in the default integration node schema.
Response
Modify the shared library <insert_1> so that none of its subflows are in the default integration node schema.
BIP1331
One or more subflows in shared library <insert_1> are in the default integration node schema.
Severity
20 : Error
Explanation
Subflows in shared libraries cannot be in the default integration node schema.
Response
Modify the shared library <insert_1> so that none of its subflows are in the default integration node schema.
BIP1332
The application <insert_1> is trying to use subflows from shared library <insert_2>. However, shared library <insert_2> has subflows in the integration node schema <insert_3>, which is already defined by subflows in application <insert_1>.
Severity
20 : Error
Explanation
When an application is referencing shared libraries, all the subflows for an integration node schema must be in a single container.
Subflows for an integration node schema must not be in both an application and a shared library that is referenced by that application.
Additionally, subflows for an integration node schema must not be in two or more shared libraries that are referenced by a single application.
Response
Move all the subflows in the integration node schema <insert_3> into the application <insert_1>.
Alternatively, move all the subflows in the integration node schema <insert_3> into one of the shared libraries that are referenced by application <insert_1>.
BIP1333
The application <insert_1> is trying to use subflows from shared library <insert_2>. However, shared library <insert_2> has subflows in the integration node schema <insert_3>, which is already defined by subflows in shared library <insert_4>.
Severity
20 : Error
Explanation
When an application is referencing shared libraries, all the subflows for an integration node schema must be in a single container.
Subflows for an integration node schema must not be in both an application and a shared library that is referenced by that application.
Additionally, subflows for an integration node schema must not be in two or more shared libraries that are referenced by a single application.
Response
Move all the subflows in the integration node schema <insert_3> into the application <insert_1>.
Alternatively, move all the subflows in the integration node schema <insert_3> into one of the shared libraries that are referenced by application <insert_1>.
BIP1334
The shared library <insert_1> is trying to use subflows from shared library <insert_2>. However, shared library <insert_2> has subflows in the integration node schema <insert_3>, which is already defined by subflows in shared library <insert_4>.
Severity
20 : Error
Explanation
When a shared library is referencing other shared libraries, all the subflows for an integration node schema must be in a single container.
Subflows for an integration node schema must not be in both an application or shared library and a shared library that is referenced by that application or shared library.
Additionally, subflows for an integration node schema must not be in two or more shared libraries that are referenced by a single application or shared library.
Response
Move all the subflows in the integration node schema <insert_3> into the shared library <insert_1>.
Alternatively, move all the subflows in the integration node schema <insert_3> into one of the shared libraries that are referenced by shared library <insert_1>.
BIP1335
The application <insert_1> cannot be started because it depends on the shared library <insert_2>, which is not deployed to the integration server.
Severity
20 : Error
Response
Deploy the shared library <insert_2> to the integration server. Alternatively, remove the dependency on the shared library <insert_2> from the application <insert_1>.
BIP1336
JDEdwards node <insert_1>, in subflow <insert_2>, cannot be deployed in shared library <insert_3>.
Severity
20 : Error
Explanation
JDEdwardsInput and JDEdwardsRequest nodes are not supported in shared libraries.
Response
Remove all JDEdwardsInput and JDEdwardsRequest nodes from all subflows in the specified shared library.
BIP1337
PeopleSoft node <insert_1>, in subflow <insert_2>, cannot be deployed in shared library <insert_3>.
Severity
20 : Error
Explanation
PeopleSoftInput and PeopleSoftRequest nodes are not supported in shared libraries.
Response
Remove all PeopleSoftInput and PeopleSoftRequest nodes from all subflows in the specified shared library.
BIP1338
SAP node <insert_1>, in subflow <insert_2>, cannot be deployed in shared library <insert_3>.
Severity
20 : Error
Explanation
SAPInput, SAPReply, and SAPRequest nodes are not supported in shared libraries.
Response
Remove all SAPInput, SAPReply, and SAPRequest nodes from all subflows in the specified shared library.
BIP1339
Siebel node <insert_1>, in subflow <insert_2>, cannot be deployed in shared library <insert_3>.
Severity
20 : Error
Explanation
SiebelInput and SiebelRequest nodes are not supported in shared libraries.
Response
Remove all SiebelInput and SiebelRequest nodes from all subflows in the specified shared library.
You cannot deploy message flows to the integration server <insert_2> on integration node <insert_1>.
Severity
20 : Error
Explanation
The integration node <insert_1> was created by using the 'iibswitch' command.
The integration node is hosting one or more of the following components:
1. A switch server for secure connectivity and callable flows.
2. A secure connectivity agent for on-premises systems.
3. A secure connectivity agent for cloud systems.
You cannot deploy message flows or other resources to integration nodes that are hosting one or more of these components.
Response
Deploy the message flows to a different integration node.
BIP1356
Inconsistencies were found in the deployed configuration some applications are unable to start
Severity
20 : Error
Explanation
Some dependent resources were not found.
Response
Ensure all of the resources that the application depends on are deployed.
BIP1357
Source file <insert_1> could not be processed.
Severity
20 : Error
Explanation
The source file <insert_1> could not be processed. The failure to process this file has not prevented the processing of other files in the deployment.
Response
Use the preceding error messages to ascertain the cause of the failure to process the file.
BIP1358
Source file <insert_1> could not be processed and has been deleted.
Severity
20 : Error
Explanation
The source file <insert_1> could not be processed. The failure to process this file has not prevented the processing of other files in the deployment. To prevent reprocessing of the file it has been deleted.
Response
Use the proceeding error messages to ascertain the cause of the failure to process the file.
BIP1359
Unable to resolve <insert_1> connection in <insert_2><insert_3> between <insert_4> and <insert_5>.
Severity
20 : Error
Explanation
While resolving connections for a deployed resource, the connection between <insert_2> and <insert_3> in resource <insert_3> could not be completed.
Response
Correct the error before redeploying the resource.
BIP1360
Message flow node <insert_1>, <insert_2> in message flow <insert_3> in <insert_4><insert_5> requires subflow <insert_6> which is not deployed.
Severity
20 : Error
Explanation
While resolving the subflow definitions for message flow or subflow <insert_3>, the definition for the subflow <insert_4> could not be found. The top level message flow will be unable to start until the subflow is deployed.
Response
Correct the error and redeploy the application or library which contains the subflow.
BIP1361
Message flow node <insert_1>, <insert_2> in Message flow <insert_3>, <insert_4> requires Policy <insert_5> of type <insert_6> which is not deployed.
Severity
20 : Error
Explanation
The identified resource requires a policy which has not been deployed. If this message is reported while the message flow is being deployed then this will not cause the deploy operation to fail however the message flow will be unable to start until the missing policy is deployed.
Response
Deploy the missing policy, or update the message flow to remove the dependancy on the policy.
BIP1362
Message flow <insert_1>, <insert_2> requires Policy <insert_3> of type <insert_4> which is not deployed.
Severity
20 : Error
Explanation
The identified resource requires a policy which has not been deployed. If this message is reported while the message flow is being deployed then this will not cause the deploy operation to fail however the message flow will be unable to start until the missing policy is deployed.
Response
Deploy the missing policy, or update the message flow to remove the dependancy on the policy.
BIP1363
The policy project <insert_1> cannot be deleted because it contains non-dynamic policies.
Severity
20 : Error
Explanation
The changing or deletion of policies within a policy project is only supported for certain types of policy.
Response
In order to delete a policy project which contains non-dynamic policies, it is necessary to delete all deployed resources from the integration server and then redeploy all resources.
BIP1364
The policy project <insert_1> cannot be deleted because the application <insert_2> depends on policies contained within the project.
Severity
20 : Error
Explanation
The deployed resources within the application <insert_2> are dependent upon one or more policies contained within the policy project <insert_1>.
Response
In order to delete a policy project it is necessary to also delete all deployed resources which are dependent upon the policies contained within the policy project.
BIP1365
Integration node <insert_1> is a multi-instance integration node running in standby mode on queue manager <insert_2>. The administration is <insert_3>
Severity
0 : Information
BIP1366
Integration node <insert_1> is an active multi-instance or High Availability integration node that is running on queue manager <insert_2>. The administration URI is <insert_3>
Integration node <insert_1> is stopped. It is a multi-instance integration node and will be started as a IBM MQ service by queue manager <insert_2>. The administration is <insert_3>
Severity
0 : Information
BIP1368
Processing of the source file <insert_1> cannot continue as it contains a resource with name <insert_2> of type <insert_3> but a resource with this name already exists within the parent <insert_4>.
Severity
20 : Error
Explanation
While loading resources two resources were found with the same resource name.
Response
Correct the error before re-attempting the operation.
BIP1369
The subflow <insert_1> in shared library <insert_2> cannot be defined within the default broker schema.
Severity
20 : Error
Explanation
Resources within a shared library must be defined within a broker schema which is not the default broker schema.
Response
Modify the subflow definition to define it in a schema other than the default before redeploying the shared library.
BIP1370
<insert_1><insert_2> cannot be validated as it requires the shared library <insert_3> which has failed validation.
Severity
20 : Error
Explanation
The identified resource cannot be validated as it is dependant upon the shared library <insert_2> but it has failed validation.
Response
Investigate and correct the failure to validate the shared libraries using the preceding error messages.
BIP1371
Test project <insert_1> references application <insert_2>, which is not deployed to the integration server.
Severity
20 : Error
BIP1372
Test project <insert_1> references shared library <insert_2>, which is not deployed to the integration server.
Severity
20 : Error
BIP1373
The mandatory property <insert_1> is missing from policy <insert_2>/<insert_3> required by message flow node <insert_4>/<insert_5>.
Severity
20 : Error
Explanation
A value must be supplied for the <insert_1> property. The message flow will be unable to start until this is resolved.
BIP1374
The credential <insert_4> of type <insert_5> is required by the policy <insert_3> used by message flow node <insert_1>/<insert_2> but it is not defined.
Severity
20 : Error
Explanation
The identified resource requires a credential which has not been defined. The message flow will be unable to start until the missing credential is defined.
Response
Define the credential and restart the message flow.
BIP1375
Integration node <insert_1> is a multi-instance integration node running in standby mode on queue manager <insert_2>. Web administration will be enabled when the node is active.
Severity
0 : Information
BIP1376
Integration node <insert_1> is an active multi-instance or High Availability integration node that is running on queue manager <insert_2>. The administration URI is <insert_3>
Integration node <insert_1> is stopped. It is a multi-instance integration node and will be started as a IBM MQ service by queue manager <insert_2>. Web administration will be enabled when the node is active.
Severity
0 : Information
BIP1378
Integration node <insert_1> is running in standby mode on queue manager <insert_2>. Web administration will be enabled when the node is active.
Severity
0 : Information
BIP1379
The default application name <insert_1> has been specified on server start-up but this is an existing deployed resource. The default application name will be ignored.
Severity
10 : Warning
Explanation
The default application name <insert_1> has been specified on server start-up. The application content for this default application has a deployed resource structure and so cannot be used as the default application. The default application name <insert_1> will be ignored and independent resources can no longer be deployed to this server.
Response
Use the --default-application-name parameter on integration server start up or defaultApplication configuration yaml file to specify a different default application name.
BIP1380
The integration server has detected independent resources in work directory <insert_1> but no default application name has been specified on server start-up.
Severity
20 : Error
Explanation
The work directory <insert_1> contains the independent resource <insert_2>. IBM App Connect Enterprise no longer supports independent resources.
Response
Use the --default-application-name parameter on integration server start up to specify a default application name. The integration server will transfer any independent resources into the default application on start-up.
BIP1381
The independent resources in work directory <insert_1> are being transferred to the default application <insert_2>.
Severity
0 : Information
BIP1382
The integration server has detected independent resources in work directory <insert_1> but the default application <insert_3> already exists.
Severity
20 : Error
Explanation
The work directory <insert_1> contains the independent resource <insert_2>. The default application name <insert_3> has been specified but this application already exists.
Response
Use the --default-application-name parameter on integration server start up to specify a different default appliction name.
BIP1383
The integration server has detected independent resources in BAR file <insert_1> but no default application name has been specified on server start-up.
Severity
20 : Error
Explanation
The BAR file <insert_1> contains the independent resource <insert_2>. IBM App Connect Enterprise no longer supports independent resources.
Response
Use the --default-application-name parameter on integration server start up to specify a default application name. After the integration server has been restarted with this option redeploy the BAR file.
BIP1384
The independent resources in BAR file <insert_1> are being transferred to the default application <insert_2>.
Severity
0 : Information
BIP1385
No class name for message flow node <insert_1>, <insert_2>.
Severity
20 : Error
Explanation
While processing a message flow the definition for a message flow node did not contain a class name for the node. Processing of the message flow cannot complete.
Response
Correct the error before redeploying the message flow.
BIP1386
Files within the directory <insert_1> will not be loaded as multiple descriptor files have been found <insert_2>.
Severity
20 : Error
Explanation
While attemting to load deployable resources from the directory <insert_1> multiple descriptor files were found when only 1 descriptor file is permitted. This will prevent any resources within the directory from being loaded.
Response
Correct the error by removing the incorrect descriptor file(s).
BIP1387
The library <insert_1> is part of a recursive list of shared library references [ <insert_2> ] which cannot be resolved.
Severity
20 : Error
Explanation
The references for shared library <insert_1> cannot be resolved as the shared library references form a circular dependency chain back to itself.
Response
Correct the error by removing the invalid shared library reference.
BIP1388
Policy <insert_1> of type <insert_2> is required for server startup, but is not present. Policies of all types present in the work directory: <insert_3>.
Severity
20 : Error
Explanation
The server requires a policy which has not been deployed, and will not start successfully until the missing policy is provided.
Response
Deploy the missing policy, or update the server configuration to remove the dependancy on the policy.
BIP1389
Policy<insert_1> is required for server startup, but is of the wrong type ('<insert_2> instead of <insert_3>)
Severity
20 : Error
Explanation
The server requires a policy of the correct type, and the deployed policy is of a different type; the server will not start successfully until the correct policy is provided.
Response
Deploy a policy of the correct type, or update the server configuration to remove the dependancy on the policy.
BIP1390
Policy project <insert_1> is deployed to integration server <insert_2>.
Severity
0 : Information
Explanation
Deployed: <insert_3> in Bar file <insert_4>
Last edited: <insert_5>
BIP1391
Policy <insert_1> type <insert_3> is deployed as <insert_4> to integration server <insert_2>.
Severity
0 : Information
Explanation
Last edited: <insert_5>
BIP1392
.NET AppDomain <insert_1> is deployed as <insert_4> to integration server <insert_2>.
Severity
0 : Information
Explanation
Last edited: <insert_5>
BIP1393
Policy <insert_1> was requested, but is not present in the server work directory. Policies of all types present in the work directory: <insert_2>.
Severity
20 : Error
Explanation
The server has been asked to load a policy which has not been deployed.
Response
Deploy the missing policy, or update the server configuration to remove the dependancy on the policy.
BIP1802
This IBM App Connect Enterprise installation is in <insert_2> mode.
Severity
0 : Information
BIP1803
The trial period for this IBM App Connect Enterprise installation expires on <insert_2>.
Severity
0 : Information
BIP1804
This IBM App Connect Enterprise installation does not have mode information set (assuming <insert_2>).
Severity
0 : Information
BIP1805
The mode for this IBM App Connect Enterprise installation has been changed to <insert_2>.
Severity
0 : Information
BIP1806
Please restart all integration nodes to apply the operation mode change.
Severity
0 : Information
BIP1809
Changing the mode of this IBM App Connect Enterprise installation from <insert_1> to <insert_2>...
Severity
0 : Information
BIP1810
The mode of the integration node <insert_1> has not yet changed; the mode is currently being reported as <insert_2>.
Severity
10 : Warning
Explanation
The integration node was not able to process the request to change the mode within a reasonable amount of time. The request is queued for processing and will be completed when the integration node is able to do so.
Response
It is not usually necessary to repeat the command. Increasing the value of the timeout period (--timeout-seconds) will allow the utility to wait for a longer period of time before this message is displayed.
BIP1815
This IBM App Connect Enterprise installation is set to mode of operation <insert_2>, which is not valid. Correct the mode of operation.
Severity
20 : Error
BIP1821
WARNING: Integration node <insert_1> is in <insert_2> mode but has <insert_3> integration servers, which exceeds the allowed maximum for this mode.
Severity
10 : Warning
BIP1822
WARNING: Integration node <insert_1> is in <insert_2> mode but has <insert_3> message flows deployed, which exceeds the allowed maximum for this mode.
Severity
10 : Warning
BIP1823
WARNING: Integration node <insert_1> has a message flow called <insert_4> (Application <insert_6>, Library <insert_7>) in integration server <insert_5> , which contains one or more nodes that are not valid in this mode: <insert_3>.
Severity
10 : Warning
BIP1824
WARNING: The trial period for this IBM App Connect Enterprise installation expired on <insert_2>.
Severity
10 : Warning
BIP1825
Cannot create integration server <insert_2> on integration node <insert_1> because the integration node is running in <insert_3> mode, which supports a maximum of <insert_4> integration servers.
Severity
20 : Error
Explanation
The integration server cannot be created because the maximum number of integration servers for the mode of the target integration node has been reached, and creating the integration server causes this limit to be exceeded.
Response
Reuse an existing integration server, or delete an existing integration server and try the command again. Alternatively, contact your IBM representative to upgrade your license.
BIP1826
You attempted to deploy a BAR file to integration server <insert_2> on integration node <insert_1>, but the integration node is running in <insert_3> mode which limits the number of message flows that can exist at any one time. The bar file cannot be deployed.
Severity
20 : Error
Explanation
The bar file cannot be deployed because it causes the integration node to run more message flows than are valid for the current mode of the target integration node.
Response
Delete message flows from the integration node and try the command again. Alternatively, contact your IBM representative to upgrade your license.
BIP1827
You attempted to deploy a BAR file to integration server <insert_2> on integration node <insert_1>, but the integration node is running in <insert_3> mode which has a restriction on the types of node that can be deployed. The bar file cannot be deployed. The set of node types found in the bar file that are not valid are: <insert_4>.
Severity
20 : Error
Explanation
The bar file cannot be deployed because it contains nodes that are not valid for the current mode of the target integration node.
Response
Rework your message flow to use nodes that are valid in the current mode. Alternatively, contact your IBM representative to upgrade your license.
BIP1829
You attempted to deploy a BAR file to integration server <insert_2> on integration node <insert_1>, but the integration node is running in <insert_3> mode which limits the number of integration servers that can exist at any one time. The bar file cannot be deployed.
Severity
20 : Error
Explanation
The bar file cannot be deployed because the maximum number of integration servers for the mode of the target integration node has been reached.
Response
Delete an existing integration server and try the command again. Alternatively, contact your IBM representative to upgrade your license.
BIP1830
Changing the mode extensions of this IBM App Connect Enterprise installation to <insert_2>...
Severity
0 : Information
BIP1831
This IBM App Connect Enterprise installation has mode extensions <insert_2>.
Severity
0 : Information
BIP1832
WARNING: Integration node <insert_1> has a message flow called <insert_3> (Application <insert_5>, Library <insert_6>) in integration server <insert_4> which requires integration node extension <insert_2> to be enabled.
Severity
10 : Warning
BIP1833
WARNING: Integration node <insert_1> has a message flow called <insert_4> (Application <insert_6>, Library <insert_7>) in integration server <insert_5>, which contains one or more nodes that are not valid with integration node extensions <insert_2>: <insert_3>.
Severity
10 : Warning
BIP1834
You attempted to deploy a BAR file to integration server <insert_2> on integration node <insert_1>, but a flow (name <insert_4>) within the bar file requires extension <insert_3> to be enabled in the integration node. The bar file cannot be deployed.
Severity
20 : Error
Explanation
The bar file cannot be deployed because it contains a flow that is not valid for the current mode of the target integration node.
Response
Rework your message flow to use nodes that are valid in the current mode. Alternatively, contact your IBM representative to upgrade your license.
BIP1835
You attempted to deploy a BAR file to integration server <insert_2> on integration node <insert_1>, but a flow within the bar file contains a node of type <insert_4> that requires extension <insert_3> to be enabled in the integration node. The bar file cannot be deployed.
Severity
20 : Error
Explanation
The bar file cannot be deployed because it contains a flow that is not valid for the target integration node.
Response
Rework your message flow to use nodes that are valid in the current mode. Alternatively, contact your IBM representative to upgrade your license.
BIP1836
You attempted to deploy a BAR file to the $servername named <insert_2> on the integration node named <insert_1>. The integration node is running in <insert_3> mode, which restricts the types of resources that can be deployed to it. The BAR file could not be deployed because it contains the following restricted resources types: <insert_4>.
Severity
20 : Error
Explanation
The BAR file could not be deployed to the target integration node because it contains resources that are not valid for your runtime operation mode.
Response
Rework your message flow to use resources that are valid in your runtime operation mode. Alternatively, contact your IBM representative to upgrade your license.
BIP1837
WARNING: The integration server <insert_3> on integration node <insert_1> contains the resource <insert_2> (Application <insert_5>, Library <insert_6>). This resource is not valid in the current operation mode of the integration node. The operation mode of the integration node is currently set to <insert_4>.
Command options:
'--bar-file (-a) <barName>' bar file name to create or replace (Mandatory).
'--root-locations (-w) <rootLocation>' root locations. Multiple locations can be specified. If not specified, the default working directory is used.
'--deployable-files (-o) <filePath>' relative path (including the project) of deployable files to add to the BAR file. (optional; multiple files can be specified)
'--application-names (-k) <applicationName>' specify application projects containing files to link (optional; multiple projects can be specified).
'--test-project-names (-t) <testProjectName>' specify test projects containing files to link (optional; multiple projects can be specified).
'--library-names (-y) <libraryName>' specify static library or shared library projects containing files to link (optional; multiple projects can be specified).
'--app-domain-names (-n) <appDomainName>' specify .NET application domain projects containing files to link (optional; multiple projects can be specified).
'--policy-project-names (-x) <policyProjectName>' specify policy project (optional; multiple projects can be specified).
'--compile (-c)' Compile runtime resources for XMLNSC/DFDL schema and Graphical Data Maps into binaries ready for execution in the runtime.
'--recompile (-r)' Remove/rebuild runtime resources for XMLNSC/DFDL schema and Graphical Data Maps.
'--update (-u)' update an existing bar file. If the bar file does not exist, a new one is created. Use with -o, -k, -t, -y, -n, or -x options.
'--delete (-d)' delete elements from an existing bar file. Use the -k, -t, -y, -n, and -x options to specify the elements to delete.
'--include-all (-i)' include all supported and unsupported element types.
If requested by IBM Service, you may need to use the following option.
'--trace (-v) <traceFileName>' send verbose internal trace to the specified file.
BIP1839
<insert_1> not specified.
Severity
30 : Severe error
BIP1840
No valid resources found to add to the BAR file. Check that rootLocation is correct and specify at least one resource by using one or more of the -o, -k, -t, -y, -n, or -x options.
Severity
30 : Severe error
BIP1841
<insert_1> is not a valid trace file path.
Severity
30 : Severe error
BIP1842
Cannot open trace file <insert_1>. Error: <insert_2>.
Severity
30 : Severe error
BIP1843
The trace file <insert_1> is read-only.
Severity
30 : Severe error
BIP1844
Unexpected end of argument reached.
Severity
30 : Severe error
BIP1845
Command completed successfully.
Severity
0 : Information
BIP1846
The update option (-u) and the delete option (-d) cannot be used simultaneously.
Severity
30 : Severe error
BIP1847
The BAR file <insert_1> does not exist.
Severity
30 : Severe error
BIP1848
The <insert_1> file contains an unsupported node: <insert_2>.
Severity
30 : Severe error
Explanation
The node type is not supported in a message flow.
Response
Remove the node from the message flow and try again.
BIP1849
The application <insert_1> references project <insert_2> which does not exist.
Severity
10 : Warning
BIP1850
Running command: mqsipackagebar
Severity
0 : Information
BIP1851
Command arguments: <insert_1>
Severity
0 : Information
BIP1852
Processing file <insert_1>.
Severity
0 : Information
BIP1853
Application file <insert_1> successfully added to the BAR file.
Severity
0 : Information
BIP1854
Application contents:
Severity
0 : Information
BIP1855
Library file <insert_1> successfully added to the BAR file.
Severity
0 : Information
BIP1856
Library contents:
Severity
0 : Information
BIP1857
Application domain file <insert_1> successfully added to the BAR file.
Severity
0 : Information
BIP1858
Application domain contents:
Severity
0 : Information
BIP1859
Successfully added file <insert_1> to the BAR file.
Severity
0 : Information
BIP1860
Successfully deleted file <insert_1> from the BAR file.
Severity
0 : Information
BIP1861
Elapsed time: <insert_1> second(s).
Severity
0 : Information
BIP1862
Ignoring invalid or missing resource: <insert_1>
Severity
10 : Warning
BIP1863
Command completed with warnings.
Severity
10 : Warning
BIP1864
The generated BAR file does not contain any IBM App Connect Enterprise deployable files.
Severity
10 : Warning
BIP1865
<insert_1> is not added to the BAR file because it contains no deployable resources. To create deployable resources for Java code or message sets, use the mqsicreatebar -compileOnly command or the ibmint command.
Severity
10 : Warning
BIP1866
The referenced project <insert_1> contains no deployable resources. To create deployable resources for Java code or message sets, use the 'ibmint package' or 'ibmint compile' commands.
Severity
10 : Warning
BIP1867
Cannot add <insert_1> to the BAR file, because this flow is already in the BAR file as a compiled (.cmf) file. Delete <insert_2> from the BAR file by using the -d option and try again.
Severity
10 : Warning
BIP1868
Ignoring <insert_1>, which is in application <insert_2>. Use the -k option to include the application.
Severity
10 : Warning
BIP1869
Ignoring <insert_1>, which is in static library <insert_2>. Use the -y option to include the static library.
Severity
10 : Warning
BIP1870
Ignoring <insert_1>, which is in .NET application domain project <insert_2>. Use the -n option to include the application domain project.
Severity
10 : Warning
BIP1871
Shared library file <insert_1> successfully added to the BAR file.
Severity
0 : Information
BIP1872
Shared library contents:
Severity
0 : Information
BIP1873
Ignoring <insert_1>, which is in shared library <insert_2>. Use the -y option to include the shared library.
Severity
10 : Warning
BIP1874
Cannot add message flow <insert_1> to the BAR file as part of shared library <insert_2>.
Severity
20 : Error
Explanation
Shared libraries cannot contain message flows.
Response
Remove all the message flows from shared library <insert_2>.
BIP1875
Service <insert_1> on integration server <insert_2> is running.
Severity
0 : Information
Explanation
Deployed: <insert_3> in Bar file <insert_4> Last edited: <insert_5>
UUID <insert_8>
Start mode: <insert_9>
Java isolation: <insert_10>
Long description: <insert_6>
Keywords: <insert_7>
BIP1876
Service <insert_1> on integration server <insert_2> is stopped.
Severity
0 : Information
Explanation
Deployed: <insert_3> in Bar file <insert_4>
Last edited: <insert_5>
UUID <insert_8>
Start mode: <insert_9>
Java isolation: <insert_10>
Long description: <insert_6>
Keywords: <insert_7>
BIP1877
REST API <insert_1> on integration server <insert_2> is running.
Severity
0 : Information
Explanation
Deployed: <insert_3> in Bar file <insert_4> Last edited: <insert_5>
UUID <insert_8>
Start mode: <insert_9>
Java isolation: <insert_10>
Long description: <insert_6>
Keywords: <insert_7>
BIP1878
REST API <insert_1> on integration server <insert_2> is stopped.
Severity
0 : Information
Explanation
Deployed: <insert_3> in Bar file <insert_4>
Last edited: <insert_5>
UUID <insert_8>
Start mode: <insert_9>
Java isolation: <insert_10>
Long description: <insert_6>
Keywords: <insert_7>
BIP1880
The operation timed out waiting for a response.
Severity
20 : Error
Explanation
The utility did not receive an expected response from the integration node within a designated amount of time. The operation might have completed successfully, even though the response was not received.
Response
Ensure that the integration node is running and that the correct connection parameters have been supplied to the utility.
Command options:
'integrationNodeSpec' is one of:
(a) 'integrationNodeName' : Name of a locally defined integration node
(b) '-n integrationNodeFileName' : File containing remote integration node connection parameters (*.broker)
(c) '[integrationNodeName] -i ipAddress -p port' : hostname and port of a remote integration node. 'integrationNodeName' optional for validation.
(d) '[integrationNodeName] -i uri' : URI for the remote integration node in the form tcp://[<user>[:<password>]@]<host>:<port>
If a user name and password are supplied, any URI Reserved characters in the password must be percent-encoded.
'-t policyType' the type of policy to create, for example 'WorkloadManagement'
'-l policyName' the name of the policy
'-f policyDocument' a file containing the policy document
'-w timeoutSecs' maximum number of seconds to wait for the policy to be created (default is 60)
'-v traceFileName' send verbose internal trace to the specified file.
Syntax 3 version of the command relates to attached policies.
Command options:
'integrationNodeSpec' is one of:
(a) 'integrationNodeName' : Name of a locally defined integration node
(b) '-n integrationNodeFileName' : File containing remote integration node connection parameters (*.broker)
(c) '[integrationNodeName] -i ipAddress -p port' : hostname and port of a remote integration node. 'integrationNodeName' optional for validation.
(d) '[integrationNodeName] -i uri' : URI for the remote integration node in the form tcp://[<user>[:<password>]@]<host>:<port>
If a user name and password are supplied, any URI Reserved characters in the password must be percent-encoded.
'-t policyType' the type of policy to create, for example 'WorkloadManagement'
'-l policyName' the name of the policy
'-e integrationSereverName' the name of the integration server
'-m flowName' the name of the flow
'-k application' the name of the application containing the message flow
'-y staticLibrary' the name of the static library containing the message flow
'-f policyDocument' a file containing the policy document
'-a' display as a single level list all policies
'-r' display all policies and the contents
'-w timeoutSecs' maximum number of seconds to wait for the policy to be reported (default is 60)
'-v traceFileName' send verbose internal trace to the specified file.
Command options:
'integrationNodeSpec' is one of:
(a) 'integrationNodeName' : Name of a locally defined integration node
(b) '-n integrationNodeFileName' : File containing remote integration node connection parameters (*.broker)
(c) '[integrationNodeName] -i ipAddress -p port' : hostname and port of a remote integration node. 'integrationNodeName' optional for validation.
(d) '[integrationNodeName] -i uri' : URI for the remote integration node in the form tcp://[<user>[:<password>]@]<host>:<port>
If a user name and password are supplied, any URI Reserved characters in the password must be percent-encoded.
'-t policyType' the type of policy to create, for example 'WorkloadManagement'
'-l policyName' the name of the policy
'-f policyDocument' a file containing the policy document
'-w timeoutSecs' maximum number of seconds to wait for the policy to be updated (default is 60)
'-v traceFileName' send verbose internal trace to the specified file.
BIP1887
Deletes a policy with the specified type and name.
Command options:
'integrationNodeSpec' is one of:
(a) 'integrationNodeName' : Name of a locally defined integration node
(b) '-n integrationNodeFileName' : File containing remote integration node connection parameters (*.broker)
(c) '[integrationNodeName] -i ipAddress -p port' : hostname and port of a remote integration node. 'integrationNodeName' optional for validation.
(d) '[integrationNodeName] -i uri' : URI for the remote integration node in the form tcp://[<user>[:<password>]@]<host>:<port>
If a user name and password are supplied, any URI Reserved characters in the password must be percent-encoded.
'-t policyType' the type of policy to create, for example 'WorkloadManagement'
'-l policyName' the name of the policy
'-w timeoutSecs' maximum number of seconds to wait for the policy to be deleted (default is 60)
'-v traceFileName' send verbose internal trace to the specified file.
BIP1888
Failed to create a policy
Severity
0 : Information
Explanation
An error has occurred while the command was running.
Response
Investigate why the policy could not be created, correct the problem and retry the command. If the problem still occurs, contact your IBM support center.
BIP1889
Failed to report a policy
Severity
0 : Information
Explanation
An error has occurred while the command was running.
Response
Investigate why the policy could not be reported, correct the problem and retry the command.
If the problem still occurs, contact your IBM support center.
BIP1890
Failed to update a policy
Severity
0 : Information
Explanation
An error has occurred while the command was running.
Response
Investigate why the policy could not be updated, correct the problem and retry the command. If the problem still occurs, contact your IBM support center.
BIP1891
Failed to delete a policy
Severity
0 : Information
Explanation
An error has occurred while the command was running.
Response
Investigate why the policy could not be deleted, correct the problem and retry the command. If the problem still occurs, contact your IBM support center.
BIP1892
Policy document <insert_1> not found
Severity
30 : Severe error
Explanation
An error has occurred attempting to open the specified policy document.
Response
Investigate why the policy could not be opened, correct the problem and retry the command. If the problem still occurs, contact your IBM support center.
BIP1893
Policy document <insert_1> could not be opened
Severity
30 : Severe error
Explanation
An error has occurred attempting to open the specified policy document.
Response
Investigate why the policy could not be opened, correct the problem and retry the command. If the problem still occurs, contact your IBM support center.
BIP1894
Policy document could not be opened
Severity
0 : Information
Explanation
An error has occurred attempting to open the specified policy document.
Response
Investigate why the policy could not be opened, correct the problem and retry the command. If the problem still occurs, contact your IBM support center.
BIP1895
Policy type <insert_1> Policy name <insert_2> Policy URI <insert_3>
Policy content <insert_4>
Command options:
'integrationNodeSpec' is one of:
(a) 'integrationNodeName' : Name of a locally defined integration node
(b) '-n integrationNodeFileName' : File containing remote integration node connection parameters (*.broker)
(c) '[integrationNodeName] -i ipAddress -p port' : hostname and port of a remote integration node. 'integrationNodeName' optional for validation.
(d) '[integrationNodeName] -i uri' : URI for the remote integration node in the form tcp://[<user>[:<password>]@]<host>:<port>
If a user name and password are supplied, any URI Reserved characters in the password must be percent-encoded.
'-e integrationServerName' the name of the integration server
'-k application' the name of the application containing the message flow
'-y staticLibrary' the name of the static library containing the message flow
'-m messageFlow' the name of the message flow
'-l policyName' the name of the policy
'-t policyType' the type of the Policy to change
'-w timeoutSecs' maximum number of seconds to wait for the policy to be attached (default is 60)
'-v traceFileName' send verbose internal trace to the specified file.
Command options:
'integrationNodeSpec' is one of:
(a) 'integrationNodeName' : Name of a locally defined integration node
(b) '-n integrationNodeFileName' : File containing remote integration node connection parameters (*.broker)
(c) '[integrationNodeName] -i ipAddress -p port' : hostname and port of a remote integration node. 'integrationNodeName' optional for validation.
(d) '[integrationNodeName] -i uri' : URI for the remote integration node in the form tcp://[<user>[:<password>]@]<host>:<port>
If a user name and password are supplied, any URI Reserved characters in the password must be percent-encoded.
'-e integrationServerName' the name of the integration server
'-m messageFlow' the name of the message flow
'-k application' the name of the application containing the message flow
'-y staticLibrary' the name of the static library containing the message flow
'-w timeoutSecs' maximum number of seconds to wait for the policy to be detached (default is 60)
'-v traceFileName' send verbose internal trace to the specified file.
BIP1898
Invalid value <insert_1> for parameter -f.
Severity
20 : Error
Explanation
The flag -f has the invalid value <insert_1>. Valid values are: normal or restartExecutionGroup.
Response
Reissue the command specifying valid options and flags.
BIP1900
Failed to detach a policy
Severity
0 : Information
Explanation
An error has occurred while the command was running.
Response
Investigate why the policy could not be detached, correct the problem and retry the command. If the problem still occurs, contact your IBM support center.
BIP1901
Failed to attach a policy
Severity
0 : Information
Explanation
An error has occurred while the command was running.
Response
Investigate why the policy could not be attached, correct the problem and retry the command. If the problem still occurs, contact your IBM support center.
BIP1905
Message flow <insert_1> does not exist in integration server <insert_2>
Severity
0 : Information
Explanation
A message flow can be used only if it has already been created
Response
No user action required.
BIP1906
Static library <insert_1> does not exist in integration server <insert_2>
Severity
0 : Information
Explanation
A static library can be used only if it has been created already.
If the specified library is a shared library, this command cannot be used with the shared library.
Response
No user action required.
BIP1907
Application <insert_1> does not exist within integration server <insert_2>
Severity
0 : Information
Explanation
An application can be used only if it has already been created
Response
No user action required
BIP1908
Failed to attach a policy
Severity
0 : Information
Explanation
Library <insert_1> does not exist for application <insert_2> within integration server <insert_3>
Response
A library can be used only if it has already been created
BIP1909
Policy name <insert_1>
Severity
0 : Information
BIP1910
A policy has not been attached
Severity
0 : Information
Explanation
A policy has not been attached to the specified message flow, application or library
Response
No user action required.
BIP1919
The integration node or server <insert_1> cannot be reached. Check that the integration node or server is running. The message was <insert_2>.
Severity
30 : Severe error
Explanation
The utility encountered a problem while attempting to connect to the integration node or server.
Response
Check that the integration node or server is running.
BIP1920
The integration node <insert_1> cannot be reached. Check that the integration node is running, and that the HTTP listener for the web administration port is running.
Severity
30 : Severe error
Explanation
The utility encountered a problem while attempting to connect to the integration node.
Response
Check that the integration node is running. Check also that the HTTP listener that is used for the web administration port is running by searching for BIP3132 in the integration node system log.
BIP1921
The integration node or integration server cannot be reached. Check that the integration node or integration server is running. Check that the TCP/IP address <insert_1> matches the address of the machine where the integration node or integration server is running, and that port <insert_2> matches the Administration REST API port that is configured for the integration node or integration server. See the following messages for details of the error.
Severity
30 : Severe error
Explanation
The utility encountered a problem while attempting to connect to the integration node or integration server.
Response
Check that the integration node or integration server is running, and check that TCP/IP address <insert_1> and port <insert_2> are correct. The TCP/IP address <insert_1> must be the address of the machine where the integration node or integration server is running. The port <insert_2> must be the same value as the Administration REST API port that is used by the integration node or integration server. Check that the HTTP listener that is used for the Administration REST API port is running by checking for BIP3132 in the integration node system log.
BIP1922
The value <insert_1> was specified for the -q parameter. This parameter is not used to connect to the integration node, so it will be ignored.
Severity
10 : Warning
BIP1923
The integration node cannot be reached. Check that the integration node is running, and that the HTTP listener for the web administration port is running. Check that the specified TCP/IP address matches the address of the machine where the integration node is running, and that the specified port matches the web administration port that is configured for the integration node.
Severity
30 : Severe error
Explanation
The utility encountered a problem while attempting to connect to the integration node.
Response
Check that the integration node is running. The connection to the integration node requires that the HTTP listener that is used by the integration node is running. Check that the HTTP listener is running by searching for BIP3132 in the integration node system log.
BIP1924
This command manages IBM App Connect Enterprise extensions.
'command' is one of:
'install' install an extension package
'remove ' remove an installed extension
'list' list all installed extensions
'install' command arguments are one of:
'url' URL of extension package to download and install
'file' path to downloaded extension package to install
'remove' command arguments are one of:
'name' installed extension package to remove
'-v logFileName' send verbose internal trace to the specified file
'-h' display this help message
BIP1925
Listing installed extensions ...
Severity
0 : Information
BIP1926
Removing installed extension <insert_1> ...
Severity
0 : Information
BIP1927
Extension <insert_1> was removed successfully.
Severity
0 : Information
BIP1928
The installed extension <insert_1> cannot be removed. The error is: <insert_2>.
Severity
20 : Error
BIP1929
Downloading and installing extension from specified URL <insert_1> ...
Severity
0 : Information
BIP1930
Installing extension from specified file <insert_1> ...
Severity
0 : Information
BIP1931
Extension <insert_1> was successfully installed.
Severity
0 : Information
BIP1932
The extension <insert_1> cannot be installed. The error is: <insert_2>.
Severity
20 : Error
BIP1933
Cannot list all installed extensions. The error is: <insert_1>.
Severity
20 : Error
BIP1934
Installed extensions were listed successfully.
Severity
0 : Information
BIP1935
Invalid protocol <insert_1> specified in integration node URI. Valid values are 'tcp' or 'ssl'.
Severity
20 : Error
Explanation
A URI can be used on a command to connect to a remote integration node. This URI is of the form '<protocol>://[<user>[:<password>]@]<hostname>:<port>'. Valid protocols are 'tcp' or 'ssl'.
BIP1936
Authentication failure when connecting to the secured remote integration node <insert_1>. Please specify a valid userid and password.
Severity
20 : Error
Explanation
The remote integration node has administration security enabled. Security credentials must be supplied to the command in any of the following:- (a) A URI provided as the -i hostname parameter including the username and password in the form <protocol>://<user>:<password>@<host>:<port> (b) A .broker connection definition file, provided as a -n parameter. Note that the username and password must match web user accounts defined to the integration node with mqsiwebuseradmin. If a user name is supplied without a password using one of the above methods, then the caller will be prompted to provide the password.
BIP1937
Connection established to incorrect integration node. Expected/Actual: <insert_1>.
Severity
20 : Error
Explanation
The command is attempting to connect to a remote integration node using the supplied connection details, but a different integration node has responded on that port. Ensure that the intended integration node is configured to use the specified port and that the port was not already in use.
BIP1938
Unable to retrieve interface files for service <insert_1> on integration server <insert_2>. <insert_1> is stopped.
Severity
20 : Error
Explanation
In order to retrieve the service interface files, both the integration server <insert_2> and service <insert_1> must be running.
BIP1939
Invalid URI specified for remote integration node. Exception text was <insert_2>.
Severity
20 : Error
Explanation
The URI specified for the remote integration node is invalid. The URI must be of the form: <protocol>://<user>:<password>@<host>:<port> Where: '<protocol>' can be 'tcp' or 'ssl'. '<user>' refers to a web user account defined to the remote integration node. ':<password>' is the password for the remote web user. If not provided, then the password can be provided via interactive prompt '<host>' is the hostname of the machine hosting the remote integration node. '<port>' is the web administration port for the remote integration node.
BIP1940
Unable to retrieve interface files for service <insert_1> on integration server <insert_2>. <insert_1>' does not have a Web service binding.
Severity
20 : Error
Explanation
In order to retrieve the service interface files, the service <insert_1> must have a Web service binding.
Response
In IBM Integration Studio, generate a web service binding (eg. SOAP/HTTP) for the service <insert_1>, and then re-deploy the service.
BIP1941
Zero length archive file <insert_1> cannot be processed.
Severity
10 : Warning
Explanation
The archive file <insert_1> is zero bytes in length so cannot be processed.
BIP1942
Failed to set the property <insert_1> as the character string <insert_2> cannot be cast to a <insert_3> value.
Severity
20 : Error
Explanation
The provided value <insert_2> cannot be converted to a <insert_3> type which is the required type for the <insert_1> property.
BIP1943
No "Defaults" section present in the configuration.
Severity
20 : Error
Explanation
There is no "Defaults" section present in the configuration (server.config.yaml or node.config.yaml), so default values cannot be obtained.
BIP1944
No default policy project configured.
Severity
20 : Error
Explanation
The "Defaults" section present in the configuration (server.config.yaml or node.config.yaml) does not contain a value for 'policyProject'. A consequence of this is that unqualified policy names cannot be resolved.
BIP1945
No defaults configured for <insert_1>.
Severity
20 : Error
Explanation
The "Defaults" section present in the configuration (server.config.yaml or node.config.yaml) does not contain a subsection for <insert_1>.
BIP1946
No default policy configured for type <insert_1>.
Severity
20 : Error
Explanation
The "Defaults/Policies" section in the configuration (server.config.yaml or node.config.yaml) does not contain a value for policy type <insert_1>.
BIP1947
Misformatted policy name <insert_1>.
Severity
20 : Error
Explanation
Policies may be specified in the format '{PolicyProject}:Policy'. The policy specified as <insert_1> does not conform to this format. As such it is searched for in the default project named literally as <insert_1>, but such a policy does not exist.
BIP1948
The query paramaters <insert_1> and <insert_2> are mutually exclusive and cannot be specified together.
Severity
20 : Error
BIP1949
The value <insert_2> supplied for the query paramater <insert_1> is invalid.
Severity
20 : Error
BIP1950
Analysing impact of deploying BAR file <insert_3> to integration node <insert_1> (integration server <insert_2>) ...
Severity
0 : Information
BIP1951
Analysing impact of deploying BAR file <insert_2> to integration server <insert_1> ...
Severity
0 : Information
BIP1952
The impact analysis request is complete.
Severity
0 : Information
BIP1953
The UNIX domain socket for the administrative API has a pathname of <insert_1> with length of <insert_2> that exceeds the platform length of <insert_3>
Severity
30 : Severe error
Response
Either change the work directory or set "ipcSocket" in the .conf.yaml file
BIP1954
An Administration API request was made with a parameter <insert_1> that has an invalid value <insert_2>.
Severity
20 : Error
Explanation
An Administration API request was made which contained a parameter <insert_1> which was invalid. Refer to the knowledge center topic on "Admin Log" and the Administration API Documentation.
Response
Correct the property value and attempt the request again. If the problem persists, contact your IBM support center.
BIP1955
Unable to open trace file <insert_1>.
Severity
20 : Error
Explanation
The trace file <insert_1> could not be opened. Check the path to the file exists and the user has write permission to the directory.
BIP1956
An Administration API resource name of <insert_1> is invalid because it contains the following characters <insert_2>.
Severity
20 : Error
Explanation
An Administration API request was made but the resource name contains invalid characters
Response
Correct the name and attempt the request again. If the problem persists, contact your IBM support center.
BIP1957
An Administration API resource name must contain at least one character
Severity
20 : Error
Explanation
An Administration API request was made but an empty string is not valid for the resource name
Response
Correct the name and attempt the request again. If the problem persists, contact your IBM support center.
BIP1958
The JRE specification generated at version <insert_1> is invalid for ACE version <insert_2>. An integration server with an invalid JRE specification may not start.
Severity
20 : Error
Explanation
Each version of App Connect Enterprise has a different level of support for Java versions, so individual product components in one version that work with a specific Java version might not work at another level. Therefore the JRE specification needs to be regenerated.
Response
Remove or recreate the JRE specification using the command "ibmint specify jre ...".
BIP1975
The expired log file, <insert_1>, could not be deleted.
Severity
20 : Error
Response
The log file, <insert_1>, could not be deleted. If storage space is a concern, you may want to consider deleting the file manually.
BIP1976
Created compiled 'DFDL' schema file <insert_1>. Integration server <insert_2> has been optimized. Schema resources should be compiled before the server is started.
Severity
10 : Warning
Explanation
Integration server <insert_2> has been optimized to reduce server start-up time. The deployed schema resources for 'DFDL' have been compiled into their runtime format during server start-up. Schema resources should be compiled before the server is started.
Response
The 'ibmint package' or 'mqsibar' command should be used to compile schema resources for 'DFDL' into their runtime format prior to server start-up.
BIP1977
Created compiled 'XMLNSC' schema file <insert_1>. Integration server <insert_2> has been optimized. Schema resources should be compiled before the server is started.
Severity
10 : Warning
Explanation
Integration server <insert_2> has been optimized to reduce server start-up time. The deployed schema resources for 'XMLNSC' have been compiled into their runtime format during server start-up. Schema resources should be compiled before the server is started.
Response
The 'ibmint package' or 'mqsibar' command should be used to compile schema resources for 'XMLNSC' into their runtime format prior to server start-up.
BIP1978
The map file <insert_1> has been compiled in <insert_2>. Integration server <insert_3> has been optimized. Map files should be compiled before the server is started.
Severity
10 : Warning
Explanation
Integration server <insert_3> has been optimized to reduce server start-up time. The deployed map resources for <insert_2> have been compiled into their runtime format during server start-up. Deployed map resources should be compiled before the server is started.
Response
The 'ibmint package' or 'mqsibar' command can be used to compile mapping resources into their runtime format prior to server start-up.
BIP1979
The file <insert_1> has an invalid version of <insert_2> in the version property <insert_3>.
Severity
20 : Error
Explanation
The version property <insert_3> has a value of <insert_2> in the file <insert_1>. This is either an invalid value or unsupported at this version of the product.
Response
Correct the version property so that it has a valid version.
BIP1980
The integration server detected an incomplete configuration transaction. The configuration transaction will be rolled back.
Severity
20 : Error
Explanation
The integration server detected an incomplete configuration transaction. The configuration transaction must be rolled back in order to ensure the consistency of the resources deployed to the integration server.
An incomplete configuration transaction can occur if the integration server experienced an unexpected error, crash, or loss of power during a deployment or other configuration change.
Response
Investigate the cause of the incomplete configuration transaction. If the problem was caused by an unexpected error or crash as a result of a deployment or other configuration change, contact your IBM Support Center.
BIP1981
The integration server detected an incomplete configuration transaction. The configuration transaction will be rolled forward.
Severity
20 : Error
Explanation
The integration server detected an incomplete configuration transaction. The configuration transaction must be rolled forward in order to ensure the consistency of the resources deployed to the integration server.
An incomplete configuration transaction can occur if the integration server experienced an unexpected error, crash, or loss of power during a deployment or other configuration change.
Response
Investigate the cause of the incomplete configuration transaction. If the problem was caused by an unexpected error or crash as a result of a deployment or other configuration change, contact your IBM Support Center.
BIP1982
The integration server successfully rolled back an incomplete configuration transaction. The integration server will now restart.
Severity
10 : Warning
Explanation
The integration server detected an incomplete configuration transaction, and successfully rolled back the configuration transaction.
An incomplete configuration transaction can occur if the integration server experiences an unexpected error, crash, or loss of power during a deployment or other configuration change.
Response
Investigate the cause of the incomplete configuration transaction. If the problem was caused by an unexpected error or crash as a result of a deployment or other configuration change, contact your IBM Support Center.
BIP1983
The integration server successfully rolled forward an incomplete configuration transaction. The integration server will now restart.
Severity
10 : Warning
Explanation
The integration server detected an incomplete configuration transaction, and successfully rolled forward the configuration transaction.
An incomplete configuration transaction can occur if the integration server experiences an unexpected error, crash, or loss of power during a deployment or other configuration change.
Response
Investigate the cause of the incomplete configuration transaction. If the problem was caused by an unexpected error or crash as a result of a deployment or other configuration change, contact your IBM Support Center.
BIP1984
The integration server <insert_1> failed to commit a configuration transaction whilst processing an administration request. The integration server will now restart.
Severity
20 : Error
Explanation
The specified integration server failed to commit a configuration transaction. The integration server will now restart in order to recover the transaction and ensure the consistency of the resources deployed to the integration server.
Response
Investigate the cause of the commit failure. If the problem was caused by an unexpected error as a result of a deployment or other configuration change, contact your IBM Support Center.
BIP1985
The integration server <insert_1> failed to roll back a configuration transaction whilst processing an administration request. The integration server will now restart.
Severity
20 : Error
Explanation
The specified integration server failed to roll back a configuration transaction. The integration server will now restart in order to recover the transaction and ensure the consistency of the resources deployed to the integration server.
Response
Investigate the cause of the roll back failure. If the problem was caused by an unexpected error as a result of a deployment or other configuration change, contact your IBM Support Center.
BIP1986
The integration server successfully rolled back an incomplete configuration transaction. The integration server will now start normally.
Severity
10 : Warning
Explanation
The integration server detected an incomplete configuration transaction, and successfully rolled back the configuration transaction.
An incomplete configuration transaction can occur if the integration server experiences an unexpected error, crash, or loss of power during a deployment or other configuration change.
Response
Investigate the cause of the incomplete configuration transaction. If the problem was caused by an unexpected error or crash as a result of a deployment or other configuration change, contact your IBM Support Center.
BIP1987
The integration server successfully rolled forward an incomplete configuration transaction. The integration server will now start normally.
Severity
10 : Warning
Explanation
The integration server detected an incomplete configuration transaction, and successfully rolled forward the configuration transaction.
An incomplete configuration transaction can occur if the integration server experiences an unexpected error, crash, or loss of power during a deployment or other configuration change.
Response
Investigate the cause of the incomplete configuration transaction. If the problem was caused by an unexpected error or crash as a result of a deployment or other configuration change, contact your IBM Support Center.
BIP1988
MQ node <insert_1> in message flow <insert_2> cannot be deployed because it is configured to use a queue manager that cannot participate in a coordinated transaction. Only the queue manager associated with the integration node can participate as a global resource.
Severity
20 : Error
Explanation
Only the queue manager associated with the integration node can participate in a coordinated transaction.
Response
Either remove the coordinated transaction option from the message flow, or configure the MQ node <insert_1> to not participate in the transaction by setting the transaction mode to 'no'.
BIP1989
Integration server is terminating due to a shutdown event.
Severity
0 : Information
Explanation
The integration server has received a shutdown event and will now terminate.
Response
No user action required.
BIP1990
Integration server <insert_1> starting initialization; version <insert_2> (64-bit)
Severity
0 : Information
Explanation
The integration server is starting.
Response
No user action required.
BIP1991
Integration server has finished initialization.
Severity
0 : Information
Explanation
The integration server has finished initialization.
Response
No user action required.
BIP1992
Integration server <insert_1> stopped.
Severity
0 : Information
Explanation
The integration server has stopped.
Response
No user action required.
BIP1993
Monitoring directory <insert_1> every <insert_2> second(s) for deployable files.
Severity
0 : Information
Explanation
The integration server is monitoring directory <insert_1> for deployable files.
Response
No user action required.
BIP1994
Loading deployable files from directory <insert_1>.
Severity
0 : Information
Explanation
The integration server is loading the contents of the directory <insert_1>.
Response
No user action required.
BIP1995
Deploy finished.
Severity
0 : Information
Explanation
The integration server has completed deploying a file.
Response
No user action required.
BIP1996
Listening on HTTP URL <insert_1>.
Severity
0 : Information
Explanation
The integration server is receiving HTTP traffic on URL <insert_1>.
Response
No user action required.
BIP1997
Deployments will not be possible as the deploy directory was not specified or could not be accessed.
Severity
10 : Warning
Explanation
Deployments will not be possible as the deploy directory was not specified or could not be accessed.
Response
To avoid seeing this warning, use the --deploy-directory command line parameter to specify a deploy directory that exists and is not already being used by another Integration Server.
BIP1998
Deployments will not be possible because the deploy directory <insert_1> could not be accessed.
Severity
10 : Warning
Explanation
Deployments will not be possible because the deploy directory could not be accessed.
Response
Specify a deployment directory using the --deploy-directory startup parameter.
BIP1999
Development UI started at URL <insert_1>
Severity
0 : Information
Explanation
The integration server is serving a web development UI on URL <insert_1>.