General Tab
Table 19: WSDL Interface
Description Field
The name of the service.
Default: Servicen, where n is an integer.
Name
The port type of the service.
Port Type
The location of the WSDL file that defines the port type. Read-only.
WSDL Location
Table 20: Context Parameters Description Column
The name of the context parameter.
Name
The operations in the port type of the service or reference to which the parameter applies.
Operations
The direction of the message to which the parameter applies: Input, Output, Fault. If Fault, the list of fault messages.
Direction
The type of the parameter:
Type
• Basic - a basic property.
• Message - a message associated with the binding. The binding cannot reference a message used by an operation in the port type.
• Bag - a collection of properties.
Definition • Basic - the definition of the property. If the Direction is Input or Output, one of string, int, long, or boolean. If the Direction is Fault, one of string, int, long, boolean, QName, or URI.
• Message - the definition of the message, consisting of a message and a message part.
Table 21: Advanced
Description Field
Indicate that there is a sequence of operations in the port type that must be called in order to achieve some higher level goal. Supported only when WS-Reliable Messaging is enabled for a SOAP binding.
Default: False.
Conversational
Bindings Tab
See SOAP Binding Reference on page 91 and JMS Binding Reference on page 110.
Policies Tab
Policy Management on page 129.
Appearance Tab
Description Field
Specifies the font and color.
Fonts and Colors
Specifies the style of lines and arrows.
Lines and Arrows
Specifies the color gradient.
Gradient
Reference Reference
General Tab
Table 22: WSDL Interface
Description Field
The name of the reference.
Default: Referencen, where n is an integer.
Name
The port type of the reference.
Port Type
The location of the WSDL file that defines the port type. Read-only.
WSDL Location
Table 23: Context Parameters Description Column
The name of the context parameter.
Name
The operations in the port type of the service or reference to which the parameter applies.
Operations
The direction of the message to which the parameter applies: Input, Output, Fault. If Fault, the list of fault messages.
Direction
The type of the parameter:
Type
• Basic - a basic property.
• Message - a message associated with the binding. The binding cannot reference a message used by an operation in the port type.
• Bag - a collection of properties.
Definition • Basic - the definition of the property. If the Direction is Input or Output, one of string, int, long, or boolean. If the Direction is Fault, one of string, int, long, boolean, QName, or URI.
• Message - the definition of the message, consisting of a message and a message part.
Table 24: Advanced
Description Field
Indicate that the implementation will dynamically wire the reference to a service when the component runs.
Default: False.
Wired by Implementation
Indicate that there is a sequence of operations in the port type that must be called in order to achieve some higher level goal. Supported only when WS-Reliable Messaging is enabled for a SOAP binding.
Default: False.
Conversational
Description Field
The operation that signifies the end of the conversation. Enabled when Conversational is checked.
End Operation
Bindings Tab
See SOAP Binding Reference on page 91 and JMS Binding Reference on page 110.
Policies Tab
Policy Management on page 129
Appearance Tab
Description Field
Specifies the font and color.
Fonts and Colors
Specifies the style of lines and arrows.
Lines and Arrows
Specifies the color gradient.
Gradient
6
Bindings
TIBCO ActiveMatrix supports the following binding types:
• Virtualization
• REST
• SOAP
• JMS
• EJB
• Adapters
Virtualization bindings connect services and references to the Messaging Bus. Virtualization bindings are
automatically created for every composite service and every wired component service and reference. At design-time, Virtualization bindings of component services and references are implicit; their properties cannot be viewed.
There are two types of Virtualization bindings: internal and external. An internal binding is associated with a component service or reference. An external binding is associated with a service or reference promoted to the root composite. Administrators can create or modify wires connected to external bindings and can monitor, start, and stop external bindings.
SOAP, EJB, Adapters, and JMS bindings are explicitly created by architects and developers only on promoted services and references.
TIBCO Business Studio and TIBCO ActiveMatrix Administrator provide the option to choose between TIBCO's SOAP/JMS and W3C SOAP/JMS on SOAP binding type and a target service while adding a binding to a service.
Figure 6: Bindings on page 88 illustrates the different types of bindings. In the figure, bindings are indicated by a icon. The promoted service HelloWorldPT has a SOAP and external Virtualization binding. The components have internal Virtualization bindings. The promoted reference DateManagerPT has a SOAP binding. In addition, any time a service or reference has a binding of type other than Virtualization, a pair of proxy (Virtualization) bindings are created to connect the service or reference to the component to which the service or reference service is wired.
Figure 6: Bindings Topics
• Viewing Service and Reference Bindings
• Adding a Binding to a Service or Reference
• SOAP Bindings
• JMS Bindings
• Context Parameters
• Enabling Transactions in SOAP and JMS Bindings