The Partner Link Configuration associates abstract partner portTypes with concrete port bindings. This allows you to easily link to new partner services without changing orchestration processes that invoke the partners.
See Partners for more information about partners and Partner Link Configuration resources.
|
|
|
|
|
|
|
Use the + button to add partner links to the list, use the X button to delete partner links from the list, use the arrow buttons to move partner links in the list.
|
|
|
|
|
|
|
|
|
When basic authentication (username and password) is required, provide an Identity resource in this field that contains the appropriate username and password.
See TIBCO Designer Palette Reference for more information.
|
|
When SSL is required for authentication to the service, click the Configure SSL button to supply the appropriate properties. See HTTP SSL Configuration Fields information more information.
|
|
|
Folder in the project containing one or more certificates from trusted certificate authorities. This folder is checked when an invocation is made to the partner service to ensure that the server is trusted. This prevents connections to rogue servers.
|
|
See TIBCO Designer Palette Reference for more information.
|
|
Specifies that only cipher suites with strong encryption should be used, if they are available on the host you are connecting to.
|
|
|
|
|
User name for logging into the JNDI server ( javax.naming.Context.SECURITY_PRINCIPAL). If the JNDI provider does not require access control, this field can be empty.
|
|
Password for logging into the JNDI server ( javax.naming.Context.SECURITY_CREDENTIALS). If the JNDI provider does not require access control, this field can be empty.
|
|
When SSL is required for authentication to the service, click the Configure SSL button to supply the appropriate SSL JMS SSL Configuration Fields information. See for more information.
|
|
Some application servers store the security context on the thread used to establish the JNDI connection (at the time of this release, only the WebLogic application server does this). In that case, the first activity to use this resource establishes the security context, then subsequent activities use the same security context, unless this field is checked. Checking this field ensures that each activity that uses this resource examines the security context to determine if the activity uses the same security context as the security context established on the thread. If they are different, the activity’s configured security context is used.
Checking this field causes additional overhead for activities that use this resource. Therefore, only check this field when necessary.
|
|
|
|
|
|
• TIBCO EMS Reliable— this mode is only available when using TIBCO Enterprise Message Service. See the TIBCO Enterprise Message Service documentation for more information about this mode.
|
|
Corresponds to JMSExpiration property that specifies how long the message can remain active (in seconds). If set to 0, the message does not expire.
|
|
|
|
|
Folder in the project containing one or more certificates from trusted certificate authorities. This folder is checked when an invocation is made to the partner service to ensure that the server is trusted. This prevents connections to rogue servers.
|
|
See TIBCO Designer Palette Reference for more information.
|
|
Specifies whether SSL tracing should be enabled during the connection. If checked, the SSL connection messages are logged and sent to the console.
|
|
Specifies whether SSL debug tracing should be enabled during the connection. Debug tracing provides more detailed messages than standard tracing.
|
|
This field specifies to check the host name of the server against the host name listed in the server’s digital certificate. This provides additional verification that the host name you believe you are connecting to is in fact the desired host.
If the host name specified in the endpoint binding is not an exact match to the host name specified in the server’s digital certificate, the connection is refused.
Note: If an equivalent host name (for example, an IP address) is specified in the endpoint binding, but the name is not an exact match of the hostname in the host’s digital certificate, the connection is refused.
|
|
Specifies the name of the host you are expecting to connect to. This field is only relevant if the Verify Host Name field is also checked.
If the name of the host in the host’s digital certificate does not match the value specified in this field, the connection is refused.
|
|
When checked, this field specifies that the minimum strength of the cipher suites used can be specified with the bw.plugin.security.strongcipher.minstrength custom engine property. See TIBCO ActiveMatrix BusinessWorks Administration for more information about this property. The default value of the property disables cipher suites with an effective key length below 128 bits.
|