When you create a new Mediator, you can specify an interface template that generates a basic set of default files in the Mediator project. These files provide a framework from which you can design and configure the Mediator. You can create a Mediator with the following interface options:

• Mediator with no interface definition

  This creates an empty Mediator and does not create a WSDL file. This method provides you with the flexibility to create the SOA components in the order you want.

  After you create a Mediator without an interface definition, you must create a service or an event that starts the component. You can also define the interface implicitly by dragging and dropping a service, or the output interface from another component, to the Mediator input.

• Mediator with the interface defined by a WSDL file

  This bases the interface definition on a WSDL file, which describes the interfaces of a Mediator, such as port type, operations, services, and schemas. The WSDL file can already exist or you can generate one from a schema file.

• Mediator with a one-way interface

  This defines an interface with a one-way interaction, where the client sends a message to a service and the service does not need to reply.

• Mediator with a synchronous interface

  This creates an interface with synchronous request-response interactions. In a synchronous interaction, a client sends a request to a service and receives an immediate response. The client does not proceed further until the response arrives.

• Mediator with an asynchronous interface

  This creates an interface with asynchronous request-response interactions. In an asynchronous interaction, a client sends a request to a service, but does not block and wait for a reply.

• Mediator that subscribes to events

  This creates a Mediator that subscribes to a business event generated when a situation of interest occurs. A business event consists of message data sent as the result of an occurrence in a business environment. For information about business events, see Using Business Events and the Event Delivery Network.

  To subscribe to events, the events must be defined in an Event Definition (EDL) file.