mqsireloadsecurity command - Windows, Linux, and AIX systems

Use the mqsireloadsecurity command on Windows, Linux®, and AIX® systems to force the immediate expiry of some or all of the entries in the security cache.

Syntax

Read syntax diagramSkip visual syntax diagrammqsireloadsecurityintegrationNodeName --integration-node-file fileName--admin-host hostname--admin-port port--integration-nodenodeName--integration-server integrationServerName--all-integration-servers--https--cacertcertFile--cacert-passwordcacertPassword--insecure--no-https--application applicationName--all-applications--library libraryName--flow flow

Parameters

integrationNodeName
This parameter identifies the name of a specific integration node. To connect to a remote integration node by name, you must also specify --admin-host (or -i) and optionally, --admin-port (or -p).
--admin-host | -i host
(Optional) This parameter specifies a host. Specify this parameter together with integrationNodeName and --admin-port (or -p). You cannot specify this parameter together with --integration-node-file (or -n).
--admin-port | -p port
(Optional) This parameter specifies the port on which the web user interface HTTP connection listener is listening. It must be used together with --admin-host (or -i) and it can be used together with integrationNodeName. It cannot be used together with --integration-node-file (or -n).
--integration-node-file | -n integrationNodeFileName
(Optional) This parameter is used as an alternative to providing connection parameters in the command. It cannot be used together with --admin-host (-i), --admin-port (-p) , or integrationNodeName.
--integration-server | -e server
(Optional) This parameter specifies an integration server within an integration node. It must be specified together with integrationNodeName or --integration-node-file (-n). It cannot be used with all-integration-servers.
--https
(Optional) Specifies that HTTPS will be used for the connection to the integration node or server. If neither --https nor --no-https is specified, the connection is tried first with HTTPS and then without using HTTPS if the first attempt fails.
--no-https
(Optional) Specifies that HTTPS will not be used for the connection to the integration node or server. If neither --https nor --no-https is specified, the connection is tried first with HTTPS and then without using HTTPS if the first attempt fails.
--cacert cacertFile
(Optional) Specifies the path to the certificate file (in either PEM, P12, or JKS format) to be used to verify the integration node or server. If no cacert file is specified and default admin-ssl is enabled, the cacert file defaults to the default pem file for admin-ssl.
  • The --cacert parameter is valid only if HTTPS is used for the connection, so it cannot be set together with the --no-https parameter. You can set --cacert when the --https parameter has been set or when neither the --https nor --no-https parameter has been set (in which case SSL is used by default).
  • The --cacert parameter can be set only if the --admin-host parameter is specified without a URI, or if a URI is specified that starts with ssl://.
--cacert-password cacertPassword
(Optional) The password for password-protected cacert files.
  • The --cacert-password parameter is valid only if HTTPS is used for the connection and if the --cacert parameter has been set. You cannot set it together with the --no-https parameter.
  • The --cacert-password parameter can be set only if the --admin-host parameter is specified without a URI, or if a URI is specified that starts with ssl://.
--insecure
(Optional) Specifies that the certificate that is returned by the integration node or server will not be verified.
  • The --insecure parameter is valid only if HTTPS is used for the connection, so it cannot be set together with the --no-https parameter. You can set --insecure when the --https parameter has been set or when neither the --https nor --no-https parameter has been set (in which case SSL is used by default).
  • The --insecure parameter can be set only if the --admin-host parameter is specified without a URI, or if a URI is specified that starts with ssl://.
--application | -k applicationName
(Optional) This parameter lists the deployed objects that are configured for an application. You cannot use this parameter together with --all-applications or --all-integration-servers.
--library | -y libraryName
(Optional) This parameter lists the deployed objects that are configured for a library. You cannot reload the security cache of all flows on a library, so this parameter must be used with --flow (-f) or --application (-k).
--flow | -f messageFlow
(Optional) This parameter specifies the name of the message flow. It cannot be used together with --all-applications or --all-integration-servers.
--all-integration-servers
(Optional) This parameter specifies all the integration servers that are associated with an integration node. If you use this parameter, you must also specify either an integrationNodeName or --integration-node-file (-n). It cannot be used together with --flow (-f), --library (-y) , or --application (-k) parameters.
--all-applications
(Optional) This parameter specifies all the applications that are deployed to an integration server. It cannot be used together with --flow (-f), --library (-y), or --application (-k).

Examples

Reload the cache for all applications that are deployed to a specific integration server :
mqsireloadsecurity INODE1 --integration-server server --all-applications