Configure bindings to support synchronous invocation patterns

Connectivity
Websphere Integration Developer v612
Contact us...

1. Configure bindings to support synchronous invocation patterns (JMS, MQ, Web Services, HTTP)
   1. Invocation Patterns
   2. JMS binding configuration
   3. MQ binding configuration
   4. Web Service binding configuration
   5. HTTP configuration
   6. Related links

Configure bindings to support synchronous invocation patterns (JMS, MQ, Web Services, HTTP)

Invocation Patterns

SCA provides four invocation patterns.

1. Synchronous
   Client issues a request and waits for the response.
2. Asynchronous one-way
   Client issues a request and a response is not expected.
3. Asynchronous deferred response
   Client issues a request and the response will be requested by the client at a later point in time.
4. Asynchronous call back
   Client issues a request and the target will call a service implemented by the client with the response.

JMS binding configuration

Use JMS binding when you need to access a messaging system.

The following must be configured to support synchronous invocation (Client issues a request and waits for the response)

1. JMS Messaging domain
   Set to Point-to-Point
2. Managed connection factory
   A factory used to create the connection to the messaging provider
3. Send Destination Properties
   The destination where the message would be sent
4. Receive Destination Properties
   The destination where the response message would be received. This value is specified in the JMSReplyTo field of the sent message.

MQ binding configuration

Use MQ binding when you need to access a WebSphere MQ messaging system and need to use the MQ native functions.

The following must be configured to support synchronous invocation (Client issues a request and waits for the response)

1. Request Queue Manager
2. Send Destination Queue
3. Receive Destination Queue

Web Service binding configuration

Use Web Service binding when you need to access an external service over the Internet or provide a service over the Internet.

The following must be configured to support synchronous invocation (Client issues a request and waits for the response)

1. JMS Messaging domain
   Set to Point-to-Point
2. Managed connection factory
   A factory used to create the connection to the messaging provider
3. Send Destination Properties
   The destination where the message would be sent
4. Receive Destination Properties
   The destination where the response message would be received. This value is specified in the JMSReplyTo field of the sent message.

HTTP configuration

Use HTTP binding when you need to access an external service over the Internet or provide a service over the Internet and you are working with other Web services based on the HTTP model; that is, using well-known HTTP interface operations like GET, PUT, DELETE, and so on.

The following must be configured to support synchronous invocation (Client issues a request and waits for the response)

1. JMS Messaging domain
   Set to Point-to-Point
2. Managed connection factory
   A factory used to create the connection to the messaging provider
3. Send Destination Properties
   The destination where the message would be sent
4. Receive Destination Properties
   The destination where the response message would be received. This value is specified in the JMSReplyTo field of the sent message.

Related links

Connectivity
1. Accessing services 
2. Selecting appropriate bindings  
3. Asynchronous invocation qualifier
4. SCA asynchronous invocation patterns in depth
5. Working with JMS bindings
6. Creating applications with JMS bindings
7. JMS features
8. Java Message Service (JMS)  
9. Service import and export binding types
10. Working with MQ bindings
11. WebSphere MQ (WMQ)
12. WebSphere MQ programming model

Configure bindings to support asynchronous invocation patterns

Connectivity

Websphere Integration Developer v612

Contact us...

1. Configure bindings to support asynchronous invocation patterns (JMS, MQ)
   1. Invocation Patterns
   2. JMS binding configuration
   3. MQ binding configuration
   4. Related links

Configure bindings to support asynchronous invocation patterns (JMS, MQ)

Invocation Patterns

SCA provides four invocation patterns.

1. Synchronous
   Client issues a request and waits for the response.
2. Asynchronous one-way
   Client issues a request and a response is not expected.
3. Asynchronous deferred response
   Client issues a request and the response will be requested by the client at a later point in time.
4. Asynchronous call back
   Client issues a request and the target will call a service implemented by the client with the response.

JMS binding configuration

Consider a JMS binding when these factors are applicable:

 

1. You need to access a messaging system
2. The services are loosely coupled
3. Reliability is more important than performance; that is, asynchronous data transmission is preferred over synchronous.
4. Note: There are several types of JMS bindings. If you are using the Web Service binding, only the SOAP/JMS transport protocol is supported. See Service import and export binding types. 

 

The following must be configured to support asynchronous invocation

1. JMS Messaging domain
   Set to Point-to-Point
2. Managed connection factory A factory used to create the connection to the messaging provider
   Send Destination Properties
   The destination where the message would be sent
   Receive Destination Properties
   The destination where the response message would be received. This value is specified in the JMSReplyTo field of the sent message.

MQ binding configuration

Consider an MQ binding when these factors are applicable:

 

• You need to access a WebSphere MQ messaging system and need to use the MQ native functions
• The services are loosely coupled
• Reliability is more important than performance; that is, asynchronous data transmission is preferred over synchronous. 
   

The following must be configured to support asynchronous invocation.

1. JMS Messaging domain
   Set to Point-to-Point
2. Managed connection factory A factory used to create the connection to the messaging provider
   Send Destination Properties
   The destination where the message would be sent
   Receive Destination Properties
   The destination where the response message would be received. This value is specified in the JMSReplyTo field of the sent message.

Related links

1. Connectivity
2. Accessing services 
3. Selecting appropriate bindings  
4. Asynchronous invocation qualifier
5. SCA asynchronous invocation patterns in depth
6. Working with JMS bindings
7. Creating applications with JMS bindings
8. JMS features
9. Java Message Service (JMS)  
10. Service import and export binding types
11. Working with MQ bindings
12. WebSphere MQ (WMQ)
13. WebSphere MQ programming model

 

  

 

 

Create imports from external services

Connectivity
Websphere Integration Developer v612
Contact us...

1. Create imports from external services
   1. Accessing external services

Create imports from external services

 

Accesing external services

This scenario discusses different ways to access services that are external to the application, and provides high level tasks for accessing these external services.

 

 

 

Add, configure, and bind an adapter

Connectivity
Websphere Integration Developer v612
Contact us...

1. Add, configure, and bind an adapter
   1. Resource adapters
   2. Accessing external services with adapters
   3. Configuring and using adapters

Add, configure, and bind an adapter

Resource adapters

Resource adapters, usually referred to as adapters, provide a mechanism that allows for the integration of an existing EIS infrastructure with the WebSphere Process Server or WebSphere Enterprise Service Bus server. They provide a service-oriented approach to EIS integration. Adapters offer a consistent framework for access to back-end systems and their applications.

Accessing external services with adapters

Services and artifacts on external systems can be imported into WebSphere® Integration Developer. A wizard discovers applications and data on an Enterprise Information Systems (EIS) and lets you generate services from the discovered applications and data. The generated artifacts are interfaces and business objects, which can be used by components in a module.

Configuring and using adapters

The following adapters can be configured to work with WebSphere® Integration Developer. In the documentation for each adapter, you will be shown how to use the external service wizard with the adapter as well as additional information that will be helpful such as field level reference information and runtime information

Use and configure the data binding framework

Connectivity
Websphere Integration Developer v612
Contact us...

 

1. Use and configure the data binding framework

Use and configure the data binding framework

 

A data binding takes an incoming stream of data in a native format and converts it to a business object to be used by services created with the service component architecture; for example, data from a Java™ application to a service created with the WebSphere® Integration Developer editors and wizards. A data binding can also take an outgoing stream of data in a business object and convert it to a native format.

A data binding works with a data handler. The data binding delegates the transformation logic to a data handler. The data binding works as a mediator between the transport-dependent protocol (JMS, MQ, HTTP and so on) and the transport-independent protocol of the data handler.

In this section, you are shown how to create a data binding resource configuration and given a list of the predefined data binding resource configurations.

1. Creating a data binding resource configuration
   The steps to create a data binding resource configuration with the binding resource configuration wizard are shown.
2. Email, FTP and Flat Files data bindings configuration
   The configuration of data bindings for the Email, FTP and Flat Files adapters is discussed.
3. JMS, MQ JMS and generic JMS data bindings configuration
   The configuration of JMS, MQ JMS and generic JMS bindings is discussed.
4. MQ data binding configuration
   The configuration of the MQ binding is discussed.
5. HTTP data binding configuration
   The configuration of the HTTP binding is discussed.
6. Creating a data binding resource configuration for WTX
   WebSphere Transformation Extender (WTX) is a universal validation and transformation engine used to exchange business documents in many data formats.

 

Parent topic: Working with configurations that access external services