IIB V9 and V10 Differences , REST API ,WSDL ,DFDL ,Shared library - Static library Difference Interview queations

 --IIB V9 -V10--

1. Removal of the WebSphere MQ prerequisite

2. Shared libraries

3. Web UI for the broker

4. Test your message flows by using the Flow Exerciser

5. mqsireportdbparms command

6. Using the Environment tree as input data to your transformations

7. Develop integration solutions by using REST APIs

8.Creating message flows that use the Group nodes to provide stateless aggregation scenarios

-- REST API --

1.Creating a REST API from scratch by using the IBM Integration Toolkit.(Create a REST API and define resources and operations yourself.)

- If we create REST API from scracth then we need to define, header ,Resource and definations

-Header contaions the URL and base path for the APIs

-resource contaions the method of the REST API(GET,POST,DELETE..etc)

-definations includes basically message types like element in xml message

2.Creating a REST API from an imported Swagger document

- IBM Integration Bus supports version 2.0 of the Swagger specification

-The Swagger document must be saved in either JSON format with a .json file extension, or in YAML format with a .yaml or .yml file extension.

-You must enter a value for the operationId field in the Operation Object, and the value of the operationId field must be unique across all operations that are defined in this REST API

-The base paths of all REST APIs deployed to a single integration server must be unique. You cannot deploy a REST API to an integration server if there is already another REST API deployed with the same base path.

-The "file" JSON schema type is permitted in Swagger documents but is not supported by IBM Integration Bus; you cannot import a Swagger document that includes a reference to the "file" JSON schema type.

---WSDL --

-WSDL is an XML notation for describing a web service

-A WSDL definition tells a client how to compose a web service request and describes the interface that is provided by the web service provider.

-Contains

1.<types> Defines the (XML Schema) data types used by the web service

2.<message> Defines the data elements for each operation

3.<portType> Describes the operations that can be performed and the messages involved.

4.<binding> Defines the protocol and data format for each port type

--DFDL-

-The DFDL domain can be used to parse and write a wide variety of message formats, and is intended for general text and binary message formats, including industry standards.

-Because the DFDL parser is model-driven, it can perform validation of messages against the message model that is defined in the DFDL schema file.

Delemeter

- Saperate 

- Initiator

- terminator

- Output New line

-- Shared library - Static library

Shared :

1.Shared libraries are introduced in IBM Integration Bus Version 10.0.

2.If multiple applications reference a shared library, when the applications are deployed, each application uses the artifacts directly from the deployed shared library.

3.If you update and redeploy a shared library, all applications that reference that shared library see the updates automatically.

4.Shared libraries can be deployed directly to the integration server, or they can be deployed in the same BAR file as the applications that reference them.

5. we can view the shared libraries in referenced libraries  in toolkit

Static :

1.The libraries that were introduced in WebSphere® Message Broker Version 8.0 are renamed as static libraries.

2.If multiple applications reference a static library, when the applications are deployed, each application has its own private copy of the library and the resources that are contained in it

3.If you update a static library, you must repackage and redeploy each application that references that library, unless applications need to use different versions of that library.

4.Static libraries are packaged and deployed in the same BAR file as the applications that reference them.

5.we can view the Static libraries in included libraries project in toolkit