There are two situations where a
broker restart is not necessary:
- If you have created an execution group in the Toolkit, and there is nothing
yet deployed to it, you can add the .lil, .pdb, and .jar file to your chosen
directory.
- If something has already been deployed to the execution group you that
want to use, add the .lil, .pdb, and .jar file to your chosen directory and
then use the mqsireload command to restart the group. It
is not possible to overwrite an existing file on the Windows platform when
the broker is running because of the file lock that is put in place by the
operating system.
These two situations should be used with caution because any execution
group that is connected to the same broker will also detect the new .lil,
.pdb, and .jar files when that execution group is restarted, or when something
is first deployed to that execution group. By using the more conventional
way of restarting the broker, you ensure that anyone with an interest in a
particular execution group is made aware that recent changes have been made
to the broker.
These two situations assume that you have already completed
the previous step, and have therefore used either the mqsichangebroker command
or the mqsicreatebroker command to notify the broker of
the directory in which the user-defined extension files have been placed.
When
you have installed a user-defined node, it is referred to by its schema and
name, just like a message flow.