Advanced Software Component for IBM Integration Bus Advanced Pattern Type for IBM PureApplication® System

The IBM® Integration Bus Advanced software component allows deployment of an integration node with specific configuration. You would typically use the Advanced pattern for production environments.

Depending on the operating system, the Advanced software component installs the following runtime components:

Linux®	AIX®
IBM Integration Bus IBM Integration Toolkit VNC Server The VNC server is installed on display :1. Note: The VNC server is installed by using the Linux `yum` command, which requires that the cloud group is configured with the Red Hat Satellite Service shared service. If the property to enable VNC is selected and installation of VNC fails, then deployment of the IBM Integration Bus Advanced software component fails.	IBM Integration Bus Note: To deploy IBM Integration Bus on AIX, you must create a custom operating system image. For more information, see Preparing an AIX operating system image for IBM Integration Bus.

Linux®

AIX®

IBM Integration Bus
IBM Integration Toolkit
VNC Server
The VNC server is installed on display :1.

Note: The VNC server is installed by using the Linux yum command, which requires that the cloud group is configured with the Red Hat Satellite Service shared service. If the property to enable VNC is selected and installation of VNC fails, then deployment of the IBM Integration Bus Advanced software component fails.

IBM Integration Bus

Note: To deploy IBM Integration Bus on AIX, you must create a custom operating system image. For more information, see Preparing an AIX operating system image for IBM Integration Bus.

The operating system node to which the IBM Integration Bus software component is added must satisfy the system requirements for IBM Integration Bus. For more information, visit the IBM Integration Bus system requirements web page.

The IBM Integration Bus Advanced software component properties include the integration node and queue manager names, and other properties that control HTTP and HTTPS configuration for access applications. The full list of properties for the IBM Integration Bus Advanced Software component is described in Properties of the IBM Integration Bus Advanced Software Component.

If you include a virtual machine with the IBM Integration Bus in a pattern, the pattern installs IBM Integration Bus, and creates the named integration node and a single integration server ("default").

If a queue manager name is specified, the IBM MQ software must already be installed on the virtual machine as a primary installation. The named queue manager must be created and configured in advance, otherwise the IBM Integration Bus Advanced software component fails to deploy. You can create the IBM MQ installation and queue manager in the virtual machine by using the software component from the IBM MQ Advanced Pattern Type. If you cannot use that pattern type because of version or platform restrictions, you can install IBM MQ manually into the operating system image, as described in Preparing an AIX operating system image for IBM Integration Bus. If the queue manager is available, the objects and authorities that are required by IBM Integration Bus are configured automatically.

You can extend the configuration; for example, you can create extra integration servers and deploy BAR files.

Start of change Note that use of the supplied script packages assumes that the created components are managed by the script packages. Deleting these components manually by logging into the system on the console might cause the scripts to display errors. End of change

If the virtual machine has an enabled firewall, you must open access to the ports that are used by IBM Integration Bus to connect remotely, other than by SSH. To open the ports that are used by IBM Integration Bus, use the IIB: Open firewall ports script package.