Creating user IDs

When you plan the administration of your integration node configuration, you might have to define one or more user IDs for the tasks associated with particular roles.

About this task

Some operating systems, and other products, impose restrictions on user IDs:

On Windows systems, user IDs can be up to 12 characters long, but on Linux®, UNIX, and z/OS® systems, they are restricted to eight characters.
Database products might also restrict user IDs to eight characters; for example DB2® has this restriction. If you have a mixed environment, ensure that the user IDs that you use are limited to a maximum of eight characters.
Ensure that the case (upper, lower, or mixed) of user IDs is consistent. In some environments, uppercase and lowercase user IDs are considered the same, but in other environments, user IDs of different case are considered unique.
For example, on Windows systems, the user IDs 'tester' and 'TESTER' are identical; on Linux and UNIX systems, they are recognized as different user IDs.
Check the validity of spaces and special characters in user IDs to ensure that, if used, these characters are accepted by all relevant systems and products that you install.

Consider the following roles:

Procedure

Administrator user IDs that can issue mqsi* commands.
Ensure that all these user IDs are members of the mqbrkrs group.
If you enable integration node administration security, you must set up additional authorization for user IDs for the commands listed in Commands and authorizations for administration security. For more information about integration node administration security, see Administration security overview.
On Windows only, service user IDs under which integration nodes run.
For further information, see Deciding which user account to use for the integration node service ID.
IBM® App Connect Enterprise Toolkit users.
See Security for the IBM App Connect Enterprise Toolkit for information about checking and securing connections from the IBM App Connect Enterprise Toolkit.