IIB 10 new features

IIB 10 new features as listed in knowledge center given below for reference.

I was recently working on a migration for IBM integration Bus v10 and found the new way of Installing IIB. Below content is taken directly from IBM Integration Bus v10 Knowledge center. I have listed content only that is relevant to me at my work and worked on 3-4 new features that are listed below.

1. Simplified process for installation
The process to deploy and configure IBM Integration Bus so that an integration developer can use the IBM Integration Toolkit to start creating applications is simplified and quicker to complete. The installation process includes the following improvements:

The installation process is simplified. On Windows and Linux, there is a single installation process that deploys both the runtime environment and IBM Integration Toolkit. On Windows, you run the installer, accept the license, and (optionally) change the location for the installation. On Linux, the installation is a simple unpack of the code into an appropriate directory.
On Linux and UNIX, the installation automatically includes the IBM Integration ODBC Database Extender code; you do not have to install this manually after you install IBM Integration Bus.
A local integration node and integration server are automatically created the first time that you start the IBM Integration Toolkit. There is no need to run the Default Configuration Wizard that is provided with previous versions of the IBM Integration Toolkit.
The local integration node and integration server are automatically started whenever the IBM Integration Toolkit is started.
Language packs for the IBM Integration Toolkit are available online and can be downloaded and installed separately

2. Shared libraries
Shared libraries are introduced to share resources between multiple applications. Libraries in previous versions of IBM Integration Bus are static libraries.
If you use a static library to contain resources, each application that references that static library is deployed with its own private copy of that library. If a static library is updated, each application that references it must be redeployed with the updated static library. A shared library is deployed directly to an integration server. Any application can reference the resources in that deployed shared library. If that shared library is updated, the changes are immediately visible to all referencing applications.

3. Removal of the WebSphere MQ prerequisite
WebSphere MQ is no longer a prerequisite for using IBM Integration Bus on distributed platforms, which means that you can develop and deploy applications independently of WebSphere MQ. You can also run and administer integration nodes without requiring the WebSphere MQ Explorer.
When you purchase a license for IBM Integration Bus, your license entitles you to install and use WebSphere MQ with IBM Integration Bus, enabling you to use the IBM Integration Bus capabilities that require MQ functionality, such as the MQ nodes and event driven processing capabilities such as message aggregation and sequencing.
If you are not using WebSphere MQ with IBM Integration Bus, you can use the built-in MQTT pub/sub broker or an external MQTT server to publish integration node event messages. If you have installed WebSphere MQ, you can use the built-in MQTT broker, an external MQTT server, or a queue manager as your pub/sub broker.

4. Flexible interaction with WebSphere MQ
On distributed systems, support for WebSphere MQ has been extended, introducing greater flexibility in the interactions between IBM Integration Bus and WebSphere MQ. You can configure local or client connections to WebSphere MQ, enabling your integration nodes to get messages from or put messages to queues on any local or remote queue manager.     You can specify a connection from an MQ node to a specific local or remote queue manager by using connection properties on the MQ node, including the destination queue manager name, host name, port, and channel. Alternatively, you can specify a queue manager on the integration node to be used for MQ processing that is required by flows in the integration node; the queue manager that you specify is then used for all message flow nodes that do not have queue manager connections explicitly defined or policies attached.
You can also create message flows that contain multiple MQInput and MQOutput nodes, each of which can access different queue managers as specified in the node; this enables you to adapt your message flows to your existing WebSphere MQ topologies.

5. Flexible administration security
You can choose between two modes of authorization when you enable administration security on an integration node: file-based authorization (file mode) or queue-based authorization (mq mode). You can specify your chosen authorization mode by using the mqsichangeauthmode command. If you configure the integration node to use file mode, you can set file-based permissions for accessing integration nodes and resources. These permissions are set using the mqsichangefileauth command. Alternatively, if you have installed WebSphere MQ and specified a queue manager on the integration node, you can control access to the integration node and its resources by setting permissions on WebSphere MQ authorization queues.

6. mqsireportdbparms command
You can return a list of parameters that are set on an integration node. In addition, you can use the mqsireportdbparms to check if security credentials are set, or identify if you are using the correct password for an integration node.

7. Secured connections to WebSphere MQ
When you configure a connection from an MQ node to a WebSphere MQ queue manager, you can optionally configure the connection to use a security identity for authentication, SSL for confidentiality, or both. The security identity, which passes user name and password security credentials to the queue manager, can be used on connections to local or remote queue managers. For connections to remote queue managers, you can choose whether to use the SSL protocol to provide confidentiality on the client connection. IBM Integration Bus supports a subset of the SSL functionality that is supported by WebSphere MQ.

8. Additional administration tasks can be configured by using the web user interface
In addition to the administration tasks that were available in IBM Integration Bus Version 9.0, you can now perform the following tasks by using the web user interface:
Create, rename, start, stop, and delete integration servers.
Deploy integration solutions.
Start, stop, manage, and delete deployed resources.
View, create, edit, and delete configurable services.
Create, retrieve, update, and delete operational policies.
Collect and view resource statistics for your integration servers.