2. The queue manager hostname corresponds to the internal DNS value of the Cloud Pak for  Integration Cluster since the Integration Server is running in the same cluster. If for some  reason the queue manager would be running outside the cluster, you use the  corresponding value here. 3. The same applies to the listener port. Inside the cluster the queue manager is listening in  the default 1414 port. But if you wanted to access the same queue manager from a  different location you would need to use the corresponding Node Port value. 4. The security identity corresponds to the secret that was defined in 6.5.3, “Securing the  API” on page 264. The properties for the JDBC Provider are the following shown in Figure 6-126. Figure 6-126 JDBC Provider policy properties In this case, the highlights are as follows: GLYPH<SM590000> The name of the policy must match the name of the database, as required by the GDM. GLYPH<SM590000> The server name used is the one used inside the cluster, similar to what we did with the  queue manager. If you wanted to access the server from outside the cluster, then the  cluster IP address or equivalent DNS must be used. GLYPH<SM590000> The port value is the same, internally Db2 is listening in the default port, but if your  integration server would be running outside the cluster you must use the Node Port value  instead. GLYPH<SM590000> For the initial scenario we have not enabled global transaction coordination. In the next  section we will discuss when you might want to enable this feature. Chapter 6. Practical agile integration  251