Middleware News

Use user trace for debugging your applications; you can trace brokers, execution groups, and deployed message flows. Start user trace facilities using the   mqsichangetrace   command or the   WebSphere® Message Broker   Explorer . Before you start: Before you start to trace a broker, or one of its execution groups or   message flows , the broker must be running, and you must have deployed the message flows by using the   WebSphere Message Broker Explorer . Follow the instructions in the   Packaging and deploying   topic. To start a user trace: Start   WebSphere Message Broker   user trace facilities by using the   mqsichangetrace   command, or, for execution groups and assigned message flows, from the   WebSphere Message Broker   Explorer . You can select only one broker on each invocation of the command, but you can activate concurrent traces for more than one broker, by invoking the command more than once. Specify an individual execution group or   message flow   with

View a summary of the authorizations in a   Linux   or   UNIX   environment. You must add the required user IDs to the appropriate group to enable them to complete the relevant tasks. Note:   If you have enabled broker administration security, you must also set up the authority detailed inTasks and authorizations for administration security. Task Command Authorization Create, delete or migrate a broker mqsicreatebroker mqsideletebroker mqsimigratecomponents Member of   mqbrkrs   and   mqm . Using LDAP: Ensure that the registry is appropriately secured to prevent unauthorized access. The setting of   LdapPrincipal   and LdapCredentials   parameters on mqsichangebroker   is not required for correct operation of the broker. The password is not stored in clear text in the file system. Change a broker mqsichangebroker Member of   mqbrkrs . If you specify the   -s   parameter to activate broker administration security, the user ID used to run this command must b