ClientExitPath stanza of the client configuration file
Use the ClientExitPath stanza to specify the default locations of channel exits on the client.
Note: The description of each attribute of this stanza indicates which IBM MQ clients can read that attribute. For a summary table for all IBM MQ MQI client configuration file stanzas, see Which IBM MQ attributes can be read by each client.The following attributes can be included in the ClientExitPath stanza:
- Specifies the location of 32-bit channel exits for clients.
This attribute can be read by C, unmanaged .NET, managed .NET, managed XMS .NET, IBM MQ classes for Java™, and IBM MQ classes for JMS clients. IBM MQ classes for Java and IBM MQ classes for JMS clients use this attribute to locate 32-bit channel exits that are not written in Java.
- Specifies the location of 64-bit channel exits for clients.
This attribute can be read by C, unmanaged .NET, managed .NET, managed XMS .NET, IBM MQ classes for Java, and IBM MQ classes for JMS clients. IBM MQ classes for Java and IBM MQ classes for JMS clients use this attribute to locate 64-bit channel exits that are not written in Java.
- The values to be added to the classpath when a Java exit is run. This is ignored by exits in any other language.
This attribute can be read by IBM MQ classes for Java and IBM MQ classes for JMS clients.
In the JMS configuration file, the JavaExitsClassPath name is given the standard com.ibm.mq.cfg. prefix and this full name is also used on the IBM WebSphere MQ Version 7.0 or later system property. At Version 6.0 this attribute was specified using system property com.ibm.mq.exitClasspath, which was documented in the Version 6.0 readme file. The use of com.ibm.mq.exitClasspath is deprecated. If both JavaExitsClassPath and exitClasspath are present, JavaExitsClassPath is honored. If only exitClasspath usage is present, it is still honored in IBM WebSphere MQ Version 7.0 or later.