How to run IBM Integration Bus v9 on SoftLayer Servers
SimonHoldsworth 0600017PWM Comment (1) Visits (9598)
You might have seen the announcement a couple of months ago of IBM
In this article I will describe the steps I took to get IBM Integration Bus Version 9 installed and running on SoftLayer servers. You might want to do this as part of establishing an off-premise cloud environment that includes integration capability, or for managing a pool of integration servers for development and testing.
SoftLayer provides several ways to create servers. One way is to create a "Cloud Computing Instance", which is a single server with your choice of operating system, processor, memory, storage etc. Another way is to create a "Bare Metal Computing Instance" which provides a Hypervisor, such as VMWare ESXi, along with the machine and network that you specify. You can then create multiple virtual machines on that Hypervisor using your own images.
SoftLayer provides a variety of different billing methods for servers; you will need a SoftLayer account to follow these instructions. SoftLayer provides a one-
In this article, I cover two approaches to create a server and install and configuring IBM Integration Bus (“IIB”) Version 9:
In a future article, I'll cover automation of the installation and configuration so servers that have IIB and other software can be set up easily and consistently.
Note that this article covers installing and configuring an IIB runtime on a SoftLayer server only. Additional steps are required to connect message flows running on the SoftLayer server to the resources and endpoints that the message flows use if they are outside the SoftLayer network.
You can get more detail on supported platforms in the IBM
Install IBM Integration Bus v9 Developer Edition on a SoftLayer Cloud Computing Instance
In this section I’ll describe how to create a server which is a SoftLayer Cloud Computing Instance and install IBM Integration Bus v9 on that server. In this case the IBM Integration Bus Developer Edition runtime is installed on the SoftLayer server, while the Integration Toolkit and Integration Explorer are assumed to have already been installed on your local machine. When this procedure is complete you will be able to connect to the IBM Integration Bus node on the SoftLayer server from your local Integration Toolkit. The procedure has the following steps:
Create a SoftLayer Server
To create a SoftLayer server, starting from the Soft
Once you have selected the items in the steps, it should take around an hour for the server to be created and set up for you. While you are waiting, you can download the IBM Integration Bus software to install.
Get IBM Integration Bus Developer Edition
You can download the IBM Integration Bus runtime and toolkit as separate packages and for Windows or Linux operating systems. For the purposes of this article, I downloaded the runtime package for Linux and the toolkit package for Windows. If you don't already have IBM Integration Bus Developer Edition installed on your local machine, you can use the toolkit package for your local machine's OS to install the toolkit and Integration Explorer so that you can remotely manage and deploy to the IBM Integration Bus node on the SoftLayer server.
Transfer files to the SoftLayer server
Once you have downloaded the IBM Integration Bus Developer Edition runtime install image to your local machine, you then need to transfer the image to the SoftLayer server you have just created. There are several options, such as SCP, FTP, and Soft
Once your SoftLayer server is ready, log in via SSH using the public IP address and root password given in the server properties page. To find the IP address and password navigate to the Soft
Now that the FTP daemon is running, you can use FTP from your local machine to copy the install image to the SoftLayer server:
Once this is done, use the SSH session to extract the install image on the SoftLayer server:
This extracts the files into a subdirectory named “mes
Install IBM Integration Bus runtime on the SoftLayer server
The next step is to run the Linux installer. I chose to base this on the supplied installAllSilent.sh script which is in the mess
Create a simple MQ and Integration Bus configuration on the SoftLayer server
There are a few steps to set up a default configuration of the MQ and IBM Integration Bus runtime. When connecting from your local machine to the integration node on the SoftLayer server you need to ensure that the user under which you are running the Integration Toolkit has authority to access the MQ resources that are associated with the integration node.
First set up permissions for the root user and the user on your local machine to access MQ. In an SSH session on the SoftLayer server type the following commands:
After you do this you will need to log out of the server and back in again so that MQ can pick up the change in permissions. Next create the Queue manager for the integration node (I chose to name mine "SLIB9QMGR") and enable remote connection for the queue manager, so that you can connect from a local Integration Toolkit or Integration Explorer to the runtime on the SoftLayer server. Note that here I'm creating the MQ and Integration Bus objects under root for convenience; recommended practice is to create them under a separate user to allow greater control over what the products are able to do. Enter these commands in an SSH session on the SoftLayer server:
Finally create the integration node (named "SLIB9NODE") and an integration server (named "FIRST"). The “mqsiprofile” needs to be run first to set up the environment before the mqsi commands will work:
You now have a running integration node and server that is ready for integration applications to be deployed.
Deploy to and manage the IBM Integration Bus runtime
To connect to this integration node from the Integration Explorer running on your local machine:
To connect to the integration node from the Integration Toolkit:
You can now deploy integration applications to the integration server on this node, as well as creating new integration servers on the node and starting/stopping them.
Create an IIB Virtual Machine on a SoftLayer Bare Metal Computing Instance using the IIB v9 Hypervisor Edition
Virtual Machines can be created on a SoftLayer Bare Metal Computing Instance, which allow you to set up multiple identical machines with a fully-specified configuration and set of software. IBM Integration Bus Version 9 provides a Hypervisor Edition which has all of the IBM Integration Bus components (Runtime, Toolkit, Explorer) and MQ prerequisite pre-installed. The following sections describe a way you can set this up, with the following steps:
For the purposes of this article I chose to make the Bare Metal Management server accessible via a public IP address, while the IBM integration Bus virtual machines are on a private network.
Create a new SoftLayer Bare Metal Computing Instance
Set up a SoftLayer Bare Metal Computing instance by starting from the Soft
You will need to also request IP addresses for the Virtual Machines. I chose to request a block of 8 portable addresses on the internal network for my VMs once the Bare Metal Instance provisioning was complete.
When the server is provisioned, it will be listening on a SoftLayer private 10.x.x.x IP address. This is only accessible via the SoftLayer VPN, or another one of your existing SoftLayer hosts which has access to the same private VLAN. In order to connect via VPN you will need to ensure you have SSL access enabled:
I did have some issues doing this from different machines, if this does not work you may need to check your firewall settings to allow Java to run on the web page and to allow the Array Networks VPN processes to connect to the internet
Enable public IP access to the Bare Metal Management Server
The next step is to enable public IP access to the management VM. This is not necessary for every configuration however file upload via the VPN is very slow and the file sizes for the Hypervisor Edition are very large. An alternative approach would be to upload the Hypervisor files to a SoftLayer staging server on the same VLAN as the Bare Metal Instance and then transfer the file to the Bare Metal Instance across that local network.
To enable public IP access you will need to log in to the Bare Metal server through the IPMI server as described below. I did try performing this reconfiguration via the VMWare vSphere client, however when changing the management network IP address I always ended up with an unreachable server. Before you perform these steps, note down the Server Address, Gateway and Netmask values for the Bare Metal instance's public network as you will need to provide these towards the end of the procedure.
Once that procedure has been completed, you can log in to the Management server from the vSphere client via the public IP address.
Install local vSphere client
In order to manage your Virtual Machines, you need the vSphere client installed locally. If you do not have vSphere Client installed, navigate to the public URL of the Bare Metal Instance (http://<Instance IP address>/), which you enabled in the previous step. This will display the ESXi web page prompting you to download the vSphere client and install it. When installed, start the vSphere Client and log in, using the server’s public IP address, vmadmin (not root) id and password.
When you first start the vSphere Client you should be in the “Home” location with an Inventory icon. Click on the Inventory icon and you should then see your ESXi server along a tabbed display. Click on the “Configuration” tab and then select “Networking” in the “Hardware” section. Following the modification done previously via the IPMI interface, the networking configuration on my bare metal server looked like the following:
To complete the network configuration, you need to rename the port groups and attach the internal network physical adapter(s) to vSwitch1. The port group names are just descriptive text but to avoid confusion its best to remove the incorrect vmnic text. The vSwitch1 physical adapter must be added in order to be able to contact the VM through the internal network. Perform the following steps:
Transfer HVE image to datastore
Note: transferring the image to the datastore may take a few hours. The transfer only needs to be done once; after that creation of new VMs is extremely fast.
To upload HVE zip files to the server in the vSphere client application:
Using the public IP address my average transfer speed was approximately 300Kb/s, around 5 hours for both transfers.
To unpack the HVE files ready to create a VM:
You should now have the necessary .vmdk and .vmx files in your datastore. Note that each pair of .vmdk files is shown as a single "Virtual Disk" in the datastore browser:
Note: when deleting any VMs you have created, don't use the delete from disk option or it will delete these vmdk files.
Identify the IP address for the IIB Virtual Machine
Once you have confirmation that the IP addresses you requested have been allocated, you can select one of the IP addresses for the IBM Integration Bus VM and update the notes to indicate it is in use.
Create the IIB Virtual Machine
The instructions for doing this are included in "Dep
d. Register the virtual image on the hypervisor. In the vSphere client Datastore Browser, right-click the file wmbhve.vmx and select Add to inventory, which starts a wizard.
Configure the network settings for the Virtual Machine:
a. In the vSphere Client Inventory view, right-click the virtual machine which has been added, and select Edit Settings from the menu.
Before you power on the Virtual Machine, you should gather the following information required to configure the VM IP network:
Once you have collected this information, you can start up the Virtual Machine:
Once the server is up and running, you can set up a default configuration via the VM remote console as follows:
Once that is complete, you can use the Integration Toolkit on the VM to develop and deploy integration applications. If you have an Integration Toolkit on your local machine you can also connect it to the runtime on the VM, as explained in the previous example. As the VM is on the private network you will need to log in to the SoftLayer VPN first, and also ensure that you've added your local user to the mqm group on the VM to enable MQ connection.
This article shows how to set up a SoftLayer-hosted server and install and run software on it - in this case IBM Integration Bus - either through a traditional product install, or by using a Hypervisor Edition. You can get everything working without leaving your desk, plugging in a cable or hitting a switch.
In a future article I will cover automation of the software install and configuration so that you can create a predictable middleware environment that incorporates IBM Integration Bus and other components. That automation will apply to locally hosted machines as well as off-premise servers, such as those provided by SoftLayer.