Setting IBM MQ library paths for a BINDINGS connection

The connection between the FTM SWIFT enterprise applications and the queue manager they use can be either done with transport type CLIENT or BINDINGS.

If you plan to use transport type BINDINGS:

Log on to the administrative console as the WebSphere® Application Server administrator. The recommended user ID of this user is UWASA1. The access rights of this user are described in Table 1.
Click Servers > Server Types > WebSphere application servers > server_name > Process Definition > Java Virtual Machine (where server_name represents the name of the application server on which the FTM SWIFT enterprise application runs).
In the Generic JVM arguments field, insert one of the following values:
- If you are using a 64-bit application server:
```
-Djava.library.path=mq_install_dir/java/lib64
```
- Otherwise:
```
-Djava.library.path=mq_install_dir/java
```
where mq_install_dir represents the IBM MQ installation directory, for example:
```
/usr/mqm
```
Click OK and save your changes.
If you are using a 64-bit application server, add the IBM MQ library path to the JVM:
1. Click Servers > Server Types > WebSphere application servers > server_name > Server Infrastructure > Java and Process Management > Process Definition > Additional Properties > Environment Entries (where server_name represents the name of the application server on which the FTM SWIFT enterprise application runs)
2. Click New...
3. Create a new variable with the following properties:
  - Name:
    - On Linux: LD_LIBRARY_PATH
    - On other platforms: LIBPATH
  - Value: mq_install_dir/lib64:mq_install_dir/java/lib64
4. Click OK to save your changes
5. Click Save to directly save your changes to the master configuration