Configuration
The Configuration tab has the following fields.
Field |
Global Var? |
Description |
Name |
No |
The name to appear as the label for the resource. |
Description |
No |
Short description of the resource. |
Partner Links |
No
Yes
No
No
|
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 up and down in the list. Specify the following in the columns of the table for each partner:
|
Attachment Style |
No |
This field allows you to choose the attachment style for the outbound/response messages. Two attachment styles are available: SwA and MTOM. |
Operations |
No |
The operation that this process definition implements. The drop down list in this field is populated with the operations contained in the specified port type in the specified WSDL. You can choose one operation to implement per process definition. If you want to implement multiple operations, you must create a process definition for each. |
SOAP Action |
Yes |
The soapAction that is expected from incoming SOAP requests. This field is required, and by default, the operation name is used as the soapAction. Each operation in an interface must have a unique value for SOAP Action. For more information about soapAction, see the SOAP specification. Note: When Partner Link Configuration is created, these fields get populated with the values from concrete WSDL. You can override these values in Partner Link Configuration. If the concrete WSDL is changed after configuring Partner Link Configuration, the changes are not visible in the Partner Link Configuration.
|
Additional Configuration for HTTP Endpoints |
||
EndPoint URI |
No |
It has the endpoint of the service populated from the concrete WSDL. Note: When Partner Link Configuration is created, this field get populated with the values from concrete WSDL. You can override these values in Partner Link Configuration. If the concrete WSDL is changed after configuring Partner Link Configuration , the changes will are not visible in the Partner Link Configuration.
|
Use HTTP Proxy |
No |
Specifies to use a proxy server to gain access outside of a firewall. |
Proxy Name |
No |
Host name or IP address of the proxy server. |
HTTP Authentication |
No |
Specifies what authentication should be used. An authentication can be of the following three types:
|
Identity |
No |
When Basic and NTLM authentication (username and password) is required, provide an Identity resource in this field that contains the appropriate username and password. For more information, see TIBCO Designer™ Palette Reference. |
Domain |
No |
Specifies the domain to be used for Authentication. The user name and password specified in the Identity field must exist in the domain. |
SSL |
No |
When SSL is required for authentication to the service, click the Configure SSL button to supply the appropriate properties. For more information, see HTTP SSL Configuration Fields. |
HTTP SSL Configuration Fields |
||
Trusted Certificates Folder |
No |
Folder in the project containing one or more certificates from the 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. |
Identity |
No |
This is an identity resource that contains the client’s digital certificate and private key. For more information, see TIBCO Designer™ Palette Reference. |
Strong Cipher Suites Only |
No |
Specifies that only cipher suites with strong encryption should be used, if they are available on the host you are connecting to. |
Additional Configuration for JMS Endpoints |
||
JNDI Tab |
||
Context URL |
Yes |
Th URL for the JNDI connection to the JMS server ( |
User Name |
Yes |
The user name for logging into the JNDI server ( |
Password |
Yes |
The password for logging into the JNDI server ( |
Connection Factory |
Yes |
The QueueConnectionFactory or TopicConnectionFactory object stored in JNDI. This object is used to create a queue connection with a JMS application. The value for this field is taken from the WSDL file, if it is available in the For more information about creating and storing QueueConnectionFactory objects, see your JNDI provider documentation. |
SSL |
No |
When SSL is required for authentication to the service, click the Configure SSL button to supply the appropriate SSL information. For more information, see JMS SSL Configuration Fields. |
JMS Tab |
||
Use Shared JMS Configuration |
No |
Check this field if you want to specify a JMS Connection shared configuration resource to override the JMS transport parameters in the concrete WSDL. When checked, the JMS Connection field appears. Note: When selected, the JNDI fields get disabled.
|
JMS Connection |
No |
This field only appears when the Use Shared JMS Configuration field is selected. This field allows you to specify a JMS Connection shared configuration resource that contains the connection information you want to use. |
User Name |
Yes |
User name to use when logging into the JMS server. If the JMS provider does not require access control, this field can be empty. |
Password |
Yes |
Password to use when logging into the JMS server. If the JMS provider does not require access control, this field can be empty. |
JMS Destination |
Yes |
This field is available when a JMS transport is selected. This field specifies the name of the destination for incoming JMS messages for this service. The syntax of the destination name is specific to the JMS provider you are using. For more information about destination names, see your JMS provider documentation. Note: If you are using TIBCO Enterprise Message Service as your JMS provider, you can use the Browse button next to this field after specifying a valid connection in the JMS Connection field. The Browse button displays a list of configured destinations in the JMS server that are appropriate for this activity.
|
Delivery Mode |
No |
The delivery mode of the message. It can be one of the following:
|
Expiration |
No |
Corresponds to JMSExpiration property that specifies how long the message can remain active (in seconds). If set to 0, the message does not expire. This field is set in seconds, but the JMSExpiration property is displayed in milliseconds. |
Priority |
|
Priority of the message. You may set the priority to a value from 0-9. The default value is 4. |
Enable W3C SOAP JMS 1.0 Compliance |
No |
This is a read-only field that displays whether the service is W3C SOAP Over JMS 1.0 compliant or not. |
Target Service |
No |
This field is available only when the check box Enable W3C SOAP JMS 1.0 Compliance is selected. Specify the target service value, if any. Note: If Target Service is configured, the value is reflected in the WSDL as a query parameter.
|
Note: When Partner Link Configuration is created, these fields get populated with the values from concrete WSDL. You can override these values in Partner Link Configuration. If the concrete WSDL is changed after configuring Partner Link Configuration, the changes are not visible in the Partner Link Configuration.
|
||
JMS SSL Configuration Fields |
||
Basic Tab Trusted Certificates Folder |
No |
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. |
Basic Tab Identity |
No |
This is an identity resource that contains the client’s digital certificate and private key. For more information, see TIBCO Designer™ Palette reference. |
Advanced Tab Trace |
No |
Specifies whether SSL tracing should be enabled during the connection. If checked, the SSL connection messages are logged and sent to the console. |
Advanced Tab Debug Trace |
No |
Specifies whether SSL debug tracing should be enabled during the connection. Debug tracing provides more detailed messages than standard tracing. |
Advanced Tab Verify Host Name |
No |
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.
|
Advanced Tab Expected Host Name |
No |
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. This prevents hosts from attempting to impersonate the host you are expecting to connect to. |
Advanced Tab Strong Cipher Suites Only |
No |
When checked, this field specifies that the minimum strength of the cipher suites used can be specified with the When this field is unchecked, only cipher suites with an effective key length of up to 128 bits can be used. |