Object naming conventions for WebSphere MQ Managed File Transfer

Use the following naming conventions for your WebSphere® MQ Managed File Transfer objects:

  • Agent names can be a maximum of 28 characters long and are not case-sensitive. Agent names entered in lowercase or mixed case are converted to uppercase. Agent names must conform to standard IBM® WebSphere MQ object naming conventions. These conventions are detailed as follows: Rules for naming IBM WebSphere MQ objects.
  • In addition to the IBM WebSphere MQ object naming conventions, the forward slash (/) character cannot be used in agent names.
  • In addition to the IBM WebSphere MQ object naming conventions, the percent (%) character cannot be used in agent names.
  • The names of properties in the properties files are case-sensitive.
  • Queue manager names are case-sensitive.
  • File names are case-sensitive for some platforms.
  • Resource monitor names are not case-sensitive. Resource monitor names entered in lowercase or mixed case are converted to uppercase. Resource monitor names must not contain asterisk (*), percent (%) or question mark (?) characters.
  • Protocol file server names must be a minimum of 2 characters long but there is no maximum length limit, they are not case-sensitive. Protocol server names must conform to standard IBM WebSphere MQ object naming conventions. These conventions are detailed as follows: Rules for naming IBM WebSphere MQ objects.

Web Gateway names

  • Web Gateway names can be a maximum of 28 characters long and are not case-sensitive. Web Gateway names entered in lowercase or mixed case are converted to uppercase. Web Gateway names must conform to standard IBM WebSphere MQ object naming conventions. These conventions are detailed in: Rules for naming IBM WebSphere MQ objects. In addition to the IBM WebSphere MQ object naming conventions, the forward slash (/) character and percent (%) character cannot be used in Web Gateway names.
  • If you deploy multiple instances of the same Web Gateway, use the same name for each instance.
  • If you deploy more than one separate Web Gateway, use different names for each gateway. Do not create more than one Web Gateway with the same name.
  • Give a web agent that is a component of a Web Gateway a similar name to the name of the Web Gateway. For example, if the Web Gateway is named WG1_GTWY, name the web agent WG1_AGNT_QM1.