There are many kinds of nodes in the assembly diagram: components (mediation flow and Java), imports, exports, stand-alone references. Some of them have interfaces, some have references, and some have both. Wires are used to assemble these nodes into an integrated application that can be deployed to the WebSphere Process Server or the WebSphere ESB.
There are two types of wires. The first type of wire comes from a partner reference (the source) that is defined for a component or stand-alone references and goes to a component or import (the target). In this case, the wire identifies the component or import (target) that is accessed when the source component uses that partner reference. By default, a partner reference only allows one wire leading from it unless the partner reference's multiplicity property is changed to 0...n.
The target of a wire should support the interface or interfaces that the source specifies. If the partner reference on a source node cannot find a matching interface on the target node, you will have the option to create an interface map or to add a new interface on the target. Also, a WSDL partner reference cannot be wired directly to a Java interface. (For WSDL and Java interfaces and partner references wiring information, see the "WSDL and Java interfaces and references" topic under related concepts.)
The second type of wire comes from an export (the source) and goes to a component or import (the target). In this case, the wire identifies the (target) component that provides the service. An export can only have one wire leading out of it.
Wiring components and stand-alone references
After opening the mediation module assembly with the assembly editor, select one of these ways to wire two nodes together:
Unwanted wires can be deleted by selecting the wire in the assembly diagram and pressing the Delete key.
For more information, see the assembly editor tutorial under related information.