Create an integration node |
mqsicreatebroker command
|
- Member of mqbrkrs.
- If administration security is made active, and if the
authorization mode is mq, the user ID
that runs this command must be a member of the mqm group. If you do not want
to run with mqm authority, you must work
with your WebSphere® MQ administrator
to create or delete the appropriate authority queue prior
to running the command. For information about creating the
system queues, see Creating the default IBM Integration Bus queues on a WebSphere MQ queue manager.
- If you use the mqsicreatebroker command
with the -d parameter (to configure the integration
node to start and stop with the queue manager that is associated with
the integration node), the user ID that runs the command must be a
member of the mqm group.
|
Delete an integration node |
mqsideletebroker command
|
|
Migrate an integration node |
mqsimigratecomponents command
|
|
Change an integration node |
mqsichangebroker command
|
- Member of mqbrkrs.
- If administration security is made active, and if the
authorization mode is mq, the user ID
that runs this command must be a member of the mqm group. If you do not want
to run with mqm authority, you must work
with your WebSphere MQ administrator
to create or delete the appropriate authority queue prior
to running the command. For information about creating the
system queues, see Creating the default IBM Integration Bus queues on a WebSphere MQ queue manager.
|
Add or remove an integration node instance |
mqsiaddbrokerinstance command
mqsiremovebrokerinstance command
|
- Member of mqbrkrs.
- Make the
uid and gid for this
user ID the same on all the systems, and the user ID needs to be the
same one that created the first instance of the multi-instance integration
node, using the mqsicreatebroker command.
Change the uid and gid with
caution, as it affects the permission levels of files on the system.
Changing a uid or gid causes the
ownership of all the files previously owned by that user or group
to change to the integer of the previous owner of the file. Therefore,
you must ensure that your system administrator manually restores the
ownerships of the affected files and directories.
|
Backup or restore an integration node |
mqsibackupbroker command
mqsirestorebroker command
|
|
Start an integration node, or verify an integration
node |
mqsistart command
mqsicvp command
|
|
Stop an integration node |
mqsistop command
|
- Member of mqbrkrs.
However, the root user ID can stop an integration node without membership
of mqbrkrs.
- The user ID must be the same as the user ID that started
the integration node.
|
Create an integration server |
mqsicreateexecutiongroup command
|
- Member of mqbrkrs.
- If administration security is active, and if the authorization
mode is mq, the user ID that the integration node
runs under must be a member of the group mqm. If
you do not want your integration node to run with mqm authority, you must work with your WebSphere MQ administrator to create or delete
the appropriate authority queue when you create or delete an integration
server.
|
Delete an integration server |
mqsideleteexecutiongroup command
|
|
Start or stop a message flow |
mqsistartmsgflow command
mqsistopmsgflow command
|
|
Create or delete a configurable service |
mqsicreateconfigurableservice command
mqsideleteconfigurableservice command
|
|
List integration nodes |
mqsilist command
|
|
Show integration node properties |
mqsireportbroker command
mqsireportproperties command
mqsireportflowmonitoring command
mqsireportflowstats command
mqsireportflowuserexits command
mqsireportresourcestats command
|
|
Change properties |
mqsichangeproperties command
mqsichangeflowmonitoring command
mqsichangeflowstats command
mqsichangeflowuserexits command
mqsichangeresourcestats command
|
|
Set and update passwords |
mqsisetdbparms command
|
|
List set parameters that are on an integration
node |
mqsireportdbparms command
|
|
Report or update an integration node mode |
mqsimode command
|
|
Deploy an object to an integration node |
mqsideploy command
|
|
Reload an integration node, integration servers
or security |
mqsireload command
mqsireloadsecurity command
|
|
Trace an integration node |
mqsichangetrace command
mqsireporttrace command
mqsireadlog command
mqsiformatlog command
|
|
Set up symbolic links needed for coordinated
transactions |
mqsimanagexalinks command
|
- Root user.
- The user ID must have write access to the MQ_installation_directory/exits and MQ_installation_directory/exits64 directories.
|
Add the mqbrkrs group |
mqsisetsecurity command
|
|
Global cache administration |
mqsicacheadmin command
|
|
Package a BAR file |
mqsipackagebar command
|
- Member of mqbrkrs.
- The user ID must have WRITE access to the -w (root
location), -a (BAR file location), and -v (trace
file location) directories.
|
Create or modify a web user account |
mqsiwebuseradmin command
|
|
Change the administration security authorization
mode |
mqsichangeauthmode command
|
- Member of mqbrkrs
- If administration security is made active, and if the
authorization mode is mq, the user ID
that runs this command must be a member of the mqm group. If you do not want
to run with mqm authority, you must work
with your WebSphere MQ administrator
to create or delete the appropriate authority queue prior
to running the command. For information about creating the
system queues, see Creating the default IBM Integration Bus queues on a WebSphere MQ queue manager.
|
Show the current administration security authorization
mode |
mqsireportauthmode command
|
|
Change file-based permissions |
mqsichangefileauth command
|
|
Show the current file-based permissions |
mqsireportfileauth command
|
|