Adding inbound bindings

Specify the message format and protocol for inbound messages that are received from an HTTP or JMS endpoint.

About this task

Use the completion menu of the Connectivity Definition editor to specify the message format and protocol in the .cdef file. The following definition is an example of how you specify the inbound binding for inbound messages.

define inbound binding 'binding_name' 
   with 
      description "description",
   using 
      message format message_format,
   protocol protocol_type,
   accepting events: 
      - event
      - event.

Inbound bindings are part of a solution, so the .cdef file that you create is stored in the connectivity folder of the solution project. After you complete your binding, you must repeat steps 2 - 6 for each additional binding in your solution.

There are several ways in which you can create and maintain endpoint and binding definitions in .cdef files, depending on the complexity of your project. You can define all related assets in a single .cdef file, but you must define assets that require partitioning in separate .cdef files:

  • For simple projects, you can create one .cdef file for inbound assets, and one .cdef file for outbound assets. Because inbound and outbound assets never reference each other, the use of two .cdef files provides a simple way of partitioning.
  • For more complex projects that contain several bindings, you can define each binding in its own .cdef file. You also include the endpoint assets that use that binding, in the same .cdef file.

Procedure

  1. Open the .cdef file.
  2. Specify the binding name.
  3. Optional: Specify the description.
  4. Specify the message format. You can specify application/json, application/xml, or text/xml.
  5. Specify the protocol. You can specify JMS or HTTP.
  6. Specify the inbound messages to be received over this binding.
  7. Save your work.

Example

define inbound binding 'incomingQuotes' 
   with 
      description "Incoming quotes",
   using 
      message format application/xml, 
   protocol HTTP, 
   accepting events: 
      - Existing quote 
      - New quote. 

What to do next

Classify inbound messages for transformation.