Verifying IB9

To verify that the IB9 administration command work, we will create a broker, run it and then delete it Setting up the environment. To make the IB command available, we will use a pre-defined script that we will add the path to the IB command scripts into the .bash_profile file, so that when we log in as mqm the path will automatically be set.

In the example above, since this is a new installation we have an error. The error code us BIP8081:

Message BIP8081 is issued when creating a broker Scenario: Message BIP8081E is displayed when you are creating a broker, the inserted message does not format correctly, and the broker is not created. Explanation: This problem occurs because you are not a member of the correct group. Solution: Read the explanation of message BIP8081, and ask your WebSphere® Message Broker administrator to give your user ID access to the mqbrkrs group.

We now need to go switch back to root and add the appropriate group and add mqm to that group

If you remove a broker by just using the command mqsideletebroker it will only remove the broker, not the queue manager associated. To remove the broker, the QM and trace files use the following command

[mqm@localhost ~]$ mqsilist \BIP1281I: No brokers have been defined on this machine. BIP8071I: Successful command completion.

Verify that the QM was also deleted

[mqm@localhost ~]$ dspmq [mqm@localhost ~]$

If there is no result then we have verified that the QM has been removed as well Congratulations, you have now completed the module.

Summary

In this chapter, we have learned how to install IIB9.0 on a Linux CentOS 7 server. The product we used as the free demo known as IBM Integration Bus for Developers. We covered how to solve installation issues with Integration Bus, Integration Toolkit and Integration Explorer and we also learned how to verify the components to ensure they were all working as intended. This module is a sample chapter which is included in the IIB 9.0 course which will be released 2015. To learn more about the courses available from The Middleware Shop, please go to http://www.themiddlewareshop.com/products to see a full list of the current courses available.

Installing IIB 9.0 silently

To begin the installation silently, all we have to do is run the following script called installAllSilent.sh which is locate in the sample-scripts folder of the integrationbus_developer installation set (please use root for local learning, it is much easier, but you can use any account that has the correct elevated privileges).

Note: Before we run the script, we need to edit the response.properties file to ensure that the License is set to TRUE

You will see that when WMQ installed it is given an instance: 'Installation1' (/opt/mqm) set as the Primary Installation. This is important to note as you can in fact have more than one installation of WMQ now on the same machine.

Verifying Installation

We have now completed the installation. Since this is an installation which presumes you are using IIB 9.0 on a Linux desktop for learning, I am going to log into a remote session using X2Go client and test the GUI's. I am using a MATE XSession, and we can now see that we have the following:

IBM Installation Manager has been installed, this is the IBM interface to manage GUI installs. IBM Integration Toolkit can also be seen in the menu. Launching the IBM Installation Manager (IM), we see the following:

If we click on modify, we can see what has been installed and managed by IM

.

Running IB Explorer

After installing IBM Integration Explorer you must complete the following step: To initialize the new installation of IBM Integration Explorer, run the following command from a command line in which the mqsiprofile command has not run: Note: You must be in a terminal within an XSession or have a display set i.e. to a local XServer like Xming.

Initialise IB Explorer

/usr/bin/strmqcfg-i

To run this command, you must be the administrator or root user. Once the command is run, you can now run the following command to start IB Explorer

Start IB Explorer

/usr/bin/strmqcfg

Once you have verified that IB Explorer is working, we just need to verify that WMQ is installed and working.

Verifying WMQ

The majority of these commands are run as the mqm (or equivalent) user. By default these commands are in /opt/mqm/bin It is recommended that you add this path to the mqm users PATH. Now since we are using root still at this time, we will find that there is not path set. You can set the path for the root profile or you can start using the mqm user. I would recommend using the mqm user now that we have WMQ installed.

Introduction

The IBM Integration Bus, formerly known as the IBM WebSphere Message Broker Family, provides a variety of options for implementing a universal integration foundation based on an enterprise service bus (ESB)

In this module we discuss the installation of IBM Integration Bus (IIB) 9.0 components for starting IIB 9.0 Administration. The various components are

WebSphere MQ

IBM Integration Bus Component

IBM Integration Bus Toolkit

IBM Integration Bus Explorer

These components can be installed separately on different operating systems and in various modes i.e. Graphical, Console and Silent modes. Graphical or GUI mode presents a series of screens i.e. a wizard that guides you through the installation process. It is suitable for developers who are used to GUI based applications. Note for Linux/Unix that the GUI mode requires an appropriate X Windows systems installed on the machine. Console mode is suitable when you are installing the product from a remote machine over telnet or SSH, or when security policies of an environment do not allow for a GUI approach. It presents a character based interface (CUI) and is interactive in nature. Silent mode is a non-interactive and non-GUI based way to install. In this course, we follow the simplest technique, where we install all the required IIB 9.0 components in one go, using silent mode. The installation process, at a high level involves

Downloading the required software from IBM web site

Preparing the machine for installation

Extracting the downloaded archives and creating install images

Installation using installAllSilent.sh script

Preparing a Virtual Machine

In this course, I have decided to use a Virtual Box VM, because it is free to download and use. I then prepared a CentOS 7 virtual machine with 4GB Ram and 100GB disk space. I used a bridged networking setting to ensure that the VM could be access from another client machine on the same network. By installing X2GoServer on the CentOS 7 VM using yum, I was then able to install the X2Go Client on my Windows 8 client machine. This allowed be to remotely access the VM for the purposes of installing and configuring the Linux VM from my Windows Desktop. In a commercial production environment it may not be possible to install or use a GUI, so we will cover GUI actions only make life easier for training and learning purposes. It is important to note than any server-side configuration or administration would typically be done via an SSH session. I use PuTTY to access the server via the SSH protocol

Deciding on the location of downloads

Depending on how well your Linux VM is built i.e. it has a GUI desktop, you may wish to download the required files onto a client i.e. your own workstation. Once downloaded you can SCP (using Wins SCP or equivalent via SSH) these files easily to the Linux Server. IBM doesn't easily publish the download locations of files so that you can use a server-side command i.e. what traditional Linux admins would do. So be aware that you may have to try more than one methods to get the required files onto your actual server VM.

Downloading the required software from IBM web site

Different flavours of the IBM Integration Bus product

IBM Integration Bus is available in different flavours. Based on our requirement we need to procure the product.

IBM Integration Bus Advanced: Is a full-featured ESB product for any size deployment. It enables the integration of data sources from a wide range of platforms throughout service-oriented architecture (SOA) and non-SOA environments.

IBM Integration Bus Express: Is designed to meet the needs of small and midsize businesses. This entry-level ESB for simple integration projects has restricted features and is limited to one process. It can grow with your business as your integration needs evolve.

Select the download type. In our example we selected Linux for System x86-64 as a single file. You can choose to download a package of multiple files if you wish.

Click continue.

Fill out the questionnaire form from IBM if one is presented.

Read and accept the license agreement

Note: IBM's website is constantly changing, so if it prompts for a required IBM ID, provide your IBM ID. If you do not have an IBM ID, register yourself and obtain an IBM ID.

At this point you can either choose to download the file using Download Director or HTTP. It is recommended to use Download Director for downloading the file. Using the download director allows for a download to be resumed if a connection to the internet is lost during the download. It saves you having to download the entire download again. It all depends on how good your internet connection is.

Note: If you have never installed a JRE on your desktop, the download director will not work and you may be prompted to install a Java Runtime Environment. If for some reason you cannot get the JRE to work on your client, then resort to using the HTTP option.

Select IBM Integration Bus for Linux on x86-64 9.0.0-IIB-LINUXX64-DEVELOPER.tar.gz (3.1GB) and then click the Download now button

Downloading multiple files (Scenario 2).

Alternatively if you find IBMs site crashing or downloads not completing when using the single download scenario, as I often experience myself, you can choose the multiple download option. However understand that this download option is HTTP and can take longer and your registration session can time out.

When using the multiple download option, you can download the following components individually.

IBM Integration Bus (Runtime) for Windows 64 Bit 9.0.0-IIB-WINX64-DEVELOPER-RUNTIME.zip (1.24GB)IBM Integration Bus (Toolkit) for Windows 64 Bit 9.0.0-IIB-WINX64-DEVELOPER-TOOLKIT.zip (1.96GB)Note: In this course we are using Linux, however you can see that there are also windows downloads.

Installing IIB 9.0 for Developers (Free version)

Once you have completed downloading the installation files, Copy the installation files to an appropriate location on your Linux server. In the context of this training course, I have installed the installation media on the file system in the following location:

/var/apps

Note: I used WinSCP a free Windows based SCP tool that allows me to easily transfer files to the Linux Server (Linux VM sunning in Virtual Box). You could employ any other SCP (Secure Copy Protocol) tools which you are familiar with, I just so happen to use WinSCP when I am using a Windows desktop. One such example is Cygwin which is a large collection of GNU and Open Source tools which provide functionality similar to a Linux distribution on Window and then use the scp Linux shell command. Cygwin can be downloaded from the following site:

https://www.cygwin.com/

Or you may choose to download and use File-Zilla which is an Open-source (GNU GPL) FTP client for Windows, Mac OS X and GNU/Linux

https://filezilla-project.org/

Use the following command to expand the files:

tar -zxvf 9.0.0-IIB-LINUXX64-DEVELOPER-RUNTIME.tar.gz

tar -zxvf 9.0.0-IIB-LINUXX64-DEVELOPER-TOOLKIT.tar.gz

Or

gunzip ./ 9.0.0-IIB-LINUXX64-DEVELOPER-RUNTIME.tar.gz

tar -xvf

We can see below a directory listing of the decompressed installed files on my Linux Server

.

Install Using GUI

We have two choices to install IIB. We can use a GUI-based wizard, or we can install silently. In this section will look at installing the product components using the GUI. Then later we will remove this installation, then install using a silent non-GUI, automated approach To install using the GUI, we must have a Linux XWindows Session available i.e. a valid Linux GUI desktop. In my examples, I am using X2Go client to remotely access a MATE XWindows session. The server is running a standard default installation of X2GoServer. I personally find that at the time of writing of this chapter, the MATE desktop seems best for CentOS 7 remote sessions (as Gnome is not working for X2Go clients at this time) but it is up to you to choose. It is after a user-preference.

Change to the installation directory and run the following command:

./setuplinuxx64

Note: I have decided to use the root user as this is a local desktop VM, and not a production server. So I am not interested in Linux security settings, as these just get in the way of learning IIB. If you are installing on a commercial/production environment, I would consult the local administrators as to the correct policy for installing software i.e. sudo groups etc. The JRE, will load and the IBM Integration Bus installer will launch as seen below.

Click OK to continue

Click Next to continue the installation

Next, we will be presented with a warning that we have not yet installed WMQ. IIB requires WebSphere MQ as its underlying message transport. We now have to install WMQ. Looking into the expanded installation files we can see that there is folder that contains the required WMQ installation files. What will do now is exit the installation and install WMQ, then re-run the GUI installation. Note: Since in this document, we are not really concerned with describing all installation methods to the nth-degree, we will not come back and complete the GUI installation, once WMQ is installed. By following the instruction for a complete total silent install of IBM 9.0 for developers, you will be able to deduce enough information to help you with a GUI based install. If you need further help, then you can consult the chapter called IIB9Admin_Chapter1_FullVersion_Installation_howto which covers the correct installation methods for both GUI and command line as allowed by the full licensed version of the IIB 9.0 product. It is important to note that WMQ cannot be installed using a GUI method as such. You can also consult my WMQ courses available on line from our site: http://www.themiddlewareshop.com/products

Installing WMQ

Included in the installation pack is WebSphere MQ 7.5 and IBM has provided an install all. Now a point to note is that when installing on a production system, you would likely not want to install IB Explorer (formerly WMQ Explorer) and the IB Toolkit (Formerly WMB Toolkit), which are both GUI that allows to you to manage IIB and Develop IIB applications. However since we are dealing with a development version of the product, we will most likely use a Linux desktop. Now in my writing I often refer to a Linux Server that is just my enterprise experience thinking as if I was doing an administration role. Please understand that this guide is to allow you to install a demo version, and the installation is not exactly the same process you would use for the full IIB product. In an enterprise i.e. commercial sense, we would most likely install WMQ and IIB with no GUI's of any type. We would instead administer from the command line on a server via SSH or use a remote desktop which has the GUI's installed. Note: It is possible to install WMQ separately using an automated response file i.e. a silent installation, which is covered in the Full Version chapter which covers the variance of process as required if you have the fully licensed products. See the chapter called IIB9Admin_Chapter1_FullVersion_Installtion_howto. There is no WMQ GUI option in the development version of IIB, so we have to resort to a silent installation. Which just so happens to be all prepared ready by IBM.

APPENDIX A: Troubleshooting

This section discusses some of the common issues that occur during installation of Message Broker Components.

Download Director

Download Director does not work in Chrome.

If you find that after installing a JRE that the IBM Download Director still does not work, then click on the Red X in the right-hand-top corner of the Chrome window. This will allow you to tell Chrome to allow this IBM plugin to be installed.

java.lang.UnsatisfiedLinkError: Could not load SWT library. Reasons: /opt/IBM/IntegrationToolkit90/configuration/org.eclipse.osgi/bundles/5918/1/.cp/libswt-pi-gtk-3659.so (libgtk-x11-2.0.so.0: cannot open shared object file: No such file or directory) swt-pi-gtk (Not found in java.library.path) /tmp/swtlib-32/libswt-pi-gtk-3659.so (libgtk-x11-2.0.so.0: cannot open shared object file: No such file or directory) /tmp/swtlib-32/libswt-pi-gtk.so (/tmp/swtlib-32/liblibswt-pi-gtk.so.so: cannot open shared object file: No such file or directory) at org.eclipse.swt.internal.Library.loadLibrary(Unknown Source) at org.eclipse.swt.internal.Library.loadLibrary(Unknown Source) at org.eclipse.swt.internal.gtk.OS.<clinit>(Unknown Source) at java.lang.J9VMInternals.initializeImpl(Native Method) at java.lang.J9VMInternals.initialize(Unknown Source) at org.eclipse.swt.internal.Converter.wcsToMbcs(Unknown Source) at org.eclipse.swt.internal.Converter.wcsToMbcs(Unknown Source) at org.eclipse.swt.widgets.Display.<clinit>(Unknown Source) at java.lang.J9VMInternals.initializeImpl(Native Method) at java.lang.J9VMInternals.initialize(Unknown Source) at org.eclipse.ui.internal.Workbench.createDisplay(Unknown Source) at org.eclipse.ui.PlatformUI.createDisplay(Unknown Source) at org.eclipse.ui.internal.ide.application.I DEApplication.createDisplay(Unknown Source) at org.eclipse.ui.internal.ide.application.IDEApplication.start(Unknown Source) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(Unknown Source) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(Unknown Source) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(Unknown Source) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(Unknown Source) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.equinox.launcher.Main.invokeFramework(Unknown Source) at org.eclipse.equinox.launcher.Main.basicRun(Unknown Source) at org.eclipse.equinox.launcher.Main.run(Unknown Source) at org.eclipse.equinox.launcher.Main.main(Unknown Source)

Solution We did not look at the dependencies required for IIB 9.0 to run on a supported platform. Below is a quick fix, however it is recommended that when you use a non-certified platform that you look up on the IIB site to find the nearest operating system that matches for example If Using CentOS 7.x then look for Redhat Enterprise Linux Enterprise (RHEL) 7. If 7 is not available then go to the next lowest OS version i.e. RHEL 6.x Note: Here is a link to the IBM Knowledge Centre for example: http://www-01.ibm.com/support/knowledgecenter/ You can drill down the link index to find to the Integration Broker 9.0 landing page as seen in the screen capture below.

It can be hard to find a list of dependencies as IBM are certifying platforms and you have chosen to install on a non-supported platform. Though this is true, there are often many blogs on solutions and also the IBM forums can help. But let's not deceive ourselves, it can take some time to find a solution and you have to be prepared to try and try again. Unless you have [paid for support. then blood sweat and of course hands-on experience is required. Note: Most of the GUI issues such as when the IBM Installation Manager fails to load is because Installation Manager is a 32-bit application and requires 32-bit versions of OS system libraries. These libraries are not installed on RHEL 6.0/6.1 x86_64 (64-bit) by default. You must install these 32-bit libraries on your system before you run Installation Manager.

In this article we learn how to download an install the IBM Packaging Utility so we can use it to download WAS source files to create a local file repository. We will use an existing IBM Installation Manager in this example. Launch the IIM (IBM Installation Manager) File-Preferences, then click Repositories

In my case all I want is the WAS 8 ND Trial Click Next Read and Accept License, fill out the survey form. Click Next Select a location where you would like the repository to be created

Click Next and confirm then click Copy. The IBM PU will then download the source files

.

For WebSphere Application Server Network Deployment you are normally looking to download about 2.8 Gig of source files into your repository Once downloaded you can use the IBM Installation Manager to install WebSphere ND trial

Note: This is part of the $299 special deal as this course was released before December 2015.

Have you ever wondered how to install and configure a federated repository (LDAP and internal file-based repository)?

Have you ever had trouble creating a custom stand-alone LDAP configuration?

Have you wondered how to automate the creation of a LDAP configuration using Jython scripting?

Would you like to know how to configure SSL for IBM HTTP Server?

Learn how to use your own self-signed certificates with an internal Certificate Authority

Like to know how to automate SSL Certificate Management?

The WebSphere Application Server 8.5.5.x - Essential Security Concepts course provides the student with a detailed example-based guide which takes the student through how to configure Global Security for Federated Repositories. This course also covers how to set up IHS administration and other Global security insights, along with SSL management sercrets often not addressed in most WAS courses. Jython scripts are also provided to automate the configuration of LDAP use in Global Security.

The course has been written by Steve Robinson who is a well known internationally acclaimed WebSphere Consultant and the author of several published WebSphere related books.

The course provides over 250 pages of information covering the following topics and more:

JEE Security

Global Security

An Unsecured Console

Turning On Global Security

Security Configuration Wizard

Virtual Member Manager

Role Management

Administrative Roles

Disabling Global Security

Setting The Internal Repository Using Scripting

Adding Ldap To A Federated Repository

Federated Repositories Recap

Apacheds

Installing Apacheds

Install Apache Directory Studio

Adding A New Partition

Importing An Ldif File

Ldap Security Settings

Wimconfig.xml

Changing The OU For Ldap Bind

Looking at User Groups

Standalone Ldap

Configuring The Standalone Ldap Server

Testing The Connection

Review Of Security.Xml

Starting The Administrative Server

Permissions

Starting And Stopping IBM HTTP Server

Starting And Stopping IBM Administration Server

Creating A Web Server In WAS Admin Console

Testing A Connection From WAS Console To IBM Administration Server

Configuring Web Servers In WAS Admin Console

Generating the plugin-cfg.xml File

Propagating the plugin-cfg.xml File

Configure IBM HTTP Server to load the Plugin Module

Verify Default application Targets

Configuring SSLFor Communication

Creating a Self-Signed Digital Certificate

Adding SSL To The IHS Virtual Host Configuration

Propagating Keyring File From WAS To Web Server

Configuring Virtual Hosts

Automating Self-Signed Certificates

Creating a New Key Database

Setting The Database Password

Registering A Key Database With The Server

Creating A Self-Signed Certificate

Managing Certificate Signing From A Certificate Authority

Basic SSLOverview

Digital Certificates

Objective

Install OpenSSL

Create A CSRUsing Ikeyman Tool

Using gskcmd Utility To Create A New Keyring Database To Store A CSR

Verifying a Certificate Request via Command-Line

Verifying a Certificate Request Using Ikeyman

Listing Available Signers

Create a New CA

Signing The CSR Using The New CA

Check The CSR Using OpenSSL

Receive The Signed Certificate Into The Key Database Using Command-Line

Receive The Signed Certificate Into The Key Database Using Gui

Configure IBM HTTP Server With A Certificated Signed By A CA

Adding The CA’s Certificate To The Key Database

Firefox Example Error

Internet Explorer Example Error

Adding CA’s Certificate To The Browsers Trust Key Store/Database

Configure /etc/hosts File

Automating Web Server Definitions

Understanding The Plugin-Cfg.Xml File

Appendix A: Additional Information On OpenSSL Tool

Appendix B: Creating A Key Pair Using OpenSSL

Generate a Private Key

Generate a Public Key

Create A New CA Using Ca.Pl (CA Script)

Duration: 3-5 Days Self Study Audience:

Experienced JEE Developers and Administrators having good experience with WebSphere Application Servers.

People looking to upgrade their skills to use the WebSphere Application Server and configure LDAP and other forms of user-registries and fully understand how configure security for WAS environments

This course follows a simple “Do-it-yourself” style that is unique to
The Middleware Shop’s courses. Containing > 650 pages and slides,
the student learns through doing WebSphere Message Queue 7.5
Administration. IBM is recognized as providing the best enterprise
message solution available in the market, WMQ has survived over a
decade which shows its relevance and demand in market place. This course
represents one of the big three, most common Enterprise products in the
IBM WebSphere brand. WebSphere Application Server, WebSphere Message
Broker and WebSphere MQ are often found working together. It is
fundamental that you understand the WebSphere MQ product.

The following are the topics covered:

Module 1 – WebSphere Message Queue 7.5 Introduction

Module 2 – Installation

Module 3 – Queue Manager

Module 4 – Queue

Module 5 – Channels, Listeners & Bindings

Module 6 – Clustering

Module 7 – Publish Subscribe

Module 8 – Application Programming Basics

Module 9 – Security

Module 10 – MQ Client

Module 11 – Logging, Backup & Restore

Module 12 – Troubleshooting

By completing this course, the student will understand all WMQ 7.5
Administration concepts and the basics of WMQ application programming.
Powered with this knowledge the student will be able to design and
implement WMQ solutions.

Duration:

Ideal duration for an instructor lead course: 3 days.

Duration for self-learning: 3 weeks

Audience:
Basic knowledge of Windows or Linux Operating system. An appreciation for the need of enterprise messaging systems.

Since I am installing in a 64 bit Windows VM, I use the 64 bit launch pad

IBM Integration Designer for IBM Business Monitor

For
Windows only, this installation configuration includes IBM Business
Monitor, the Monitor Model editor (a feature in IBM Integration
Designer), and a IBM Business Monitor test environment. The following
packages are selected for installation:

WebSphere Application Server Network Deployment

Business Monitor

IBM Cognos

DB2 Express

Integration Designer

A
default stand-alone profile for Business Monitor is selected on the
Features page. This profile enables you to begin using the test
environment immediately.

IBM Integration Designer for WebSphere DataPower

This
installation configuration works directly with the WebSphere DataPower
Appliance, and does not include a test environment. Only the Integration
Designer package is selected for installation.

IBM Integration Designer

This
installation configuration does not include a test environment. Only
the Integration Designer package is selected for installation.

I
chose the option to install the Process Server Test Environment and
start working with the IBM Process Center first, all this check box does
is auto prompt to connect to an existing Process Center. This is
covered in another separate article.

Click "install Selected" and the IBM installation manager will start.

As the IIM (IBM Installation manager) loads it will validate the local install repository.

As
you can see above the installer has already pre-selected the individual
component. We are installing WAS 8.0.0.5 ND, IID, IBM Process Server
Advanced (Both Process Server and ESB) DB2 Express to fulfill a complete
developer environment.

Click Next

You will see the repository already contains several fix packs.

Read and Accept License

I choose to install in was8nd as it is not a protected folder.

Review

Click Next and the wizard will prompt for some profile & DB/2 settings

We use profile settings as administrative security will be turned on for this profile. Click Next

Review the installation summary and click Install

At
this point the IIM is asking you to create a Process Center, we do this
using a Process Center profile. But since I want to verify that the
process server profile has installed let's look at that first. Later we
will create the Process Center server (Process Center Profile).

When
the install is completed, select none as seen below. We do not need to
create a profile because we are going to use the WTE (WebSphere Test
Environment) from within IBM Integration Designer.

Click finish to and close the Launchpad installer.

Since I have installed on Windows, there is a new entry in the IBM program group

Process Center

We
need to create a Process Center Server. We cannot do this with the same
media that was used to install IID. You see Process Server Center comes
with the full version of IBM BPM and is designed to be an actual
server. You would not have a local dev IDE and a local Process Center on
the same machine. Reason is resources locally and what is the point. A
Process center is supposed to be shared.

Search my site for the article on how to create a Process Center.

Once the Process Center server is available we can switch to the Process Center perspective and connect.

This is using the GUI approach. My IBM BPM courses for dev and admin should be available sometime in Q3 2013.

For this install I am using the flowing three media files

BPM_ADV_8.0.1_LNX_X86_32_64B-2_3.tar

BPM_ADV_8.0.1_LNX_X86_32_64B-3_3.tar

BPM_ADV_8.0.1_LNX_X86_32_64B-1_3.tar

Once de-compressed this is the file list.

-rw-rw-r--. 1 bpmadmin 500 1148 Nov 3 01:07 launchpad.ini

-rw-rw-r--. 1 bpmadmin 500 1148 Nov 3 01:07 launchpad64.ini

drwxrwxr-x. 10 bpmadmin 500 4096 Nov 3 16:03 .

drwxrwxr-x. 8 bpmadmin 500 4096 Nov 3 16:04 repository

drwxr-xr-x. 4 bpmadmin 500 4096 Nov 3 17:23 properties

drwxr-xr-x. 2 bpmadmin 500 4096 Nov 3 17:23 LICENSES

drwxr-xr-x. 38 bpmadmin 500 4096 Nov 3 17:23 launchpad

drwxr-xr-x. 7 bpmadmin 500 4096 Nov 3 17:23 dbscripts

drwxrwxr-x. 12 bpmadmin 500 4096 Nov 3 17:26 IM

drwxrwxr-x. 12 bpmadmin 500 4096 Nov 3 17:26 IM64

drwxrwxr-x. 3 bpmadmin 500 4096 Nov 3 17:26 responsefiles

-rwxr-xr-x. 1 bpmadmin 500 6081 Nov 3 17:26 launchpad.sh

drwxr-xr-x. 4 root root 4096 Feb 25 11:05 ..

I will start by running the launchpad.sh file

I
have chosen to install the typical installation which allows me to
choose the type of installation I want to perform. I then selected the
Install Process Center option.

Click Next

Fill in the appropriate username and password. I have used wasasdmin/wasadmin

Choose use DB/2 Express

I used the following username/password combinations to start with:

bpminst/bpminst

bpmfenc/bpmfenc

bpmadmin/bpmadmin

Click Next

I
then opted not to connect with my support account. This is a test
environment, so need for that. I also like to be in control of updates. I
am unsure what this option actually does, so I am leaving it out.

Click Install software

Take note of the Schema names

If you get the following error, then it is because you have not set some of the prerequisites

Then I added the following lines to the end of the /etc/security/limits.conf file:

# - stack - max stack size (KB)

* soft stack 32768

* hard stack 32768

# - nofile - max number of open files

* soft nofile 65536

* hard nofile 65536

# - nproc - max number of processes

* soft nproc 16384

* hard nproc 16384

I then rebooted CentoOS.

First
the installer installs IBM Installation Manager, then uses the
repository from the install media as outlined at the beginning of this
article.

If you get and error like:

It
is most likely just errors being reported that your user for DB/2
already exists due to a previous trial of the install. Might be best to
delete the users and groups mentioned earlier and start again.

I clicked Yes to launch the First Steps Console

A dialog will pop up detailing verification information

Now click the Administration link.

use the username and password you entered earlier on during the installation.

I am using wasadmin/wasadmin

If
we navigate to the Server's view, we can see that we have a server and
the profile that this server belongs to has been augmented for BPM.

If we navigate to the Applications view we will be able to see many applications that have been installed.

We will now go back to the first steps console and click on the Process Centre console link

We can see from the screen capture below that the context root is:"ProcessCenter"

We can also see that there is a download link to download IBM Process Designer. We will cover this in a separate document.

Lets look in to which application is serving the Process Center Console?

If
you locate and find the app called IBM_BPM_Repository, and look at it's
web-modules context root u will see it is the Process Center Console
Application.

Click Context Root for Web Modules

Well
that's all for this article, I hope this gives you some insights on a
basic installation on a Process Center. In my course which is due for
release in Q2/Q1 2013, you will get a complete guide on how to install
BMP silently. I am also building a course on how to develop using IBM
Integration Developer.

Prep work:

As
you can see above I have opened the IBM WebSphere Message Broker
Information Center. We do this because it is best practice to ensure
that you complete the prerequisites

We will be dealing with installing several components:

IBM WebSphere Message Broker

IBM WebSphere Message Broker Tookit

IBM WebSphere MQ 7.5

IBM WebShere MQ Explorer

WebSphere Message Broker Explorer Plugin

Normally I get some fix packs from IBM FixCentral, but it was down as I was writing this article

I will validate this later

Windows Prerequisites

Essential
for windows all need is local admin rights as per your domain or local
security policies. This can be tricky in some organisation where
workstations are locked down. Being a developer you may have special
privileges?

The only other thing we need to do is prepare security users/groups for MQ and Broker

On
Windows systems, user IDs can be up to 12 characters long, but on
Linux, UNIX, and z/OS® systems, they are restricted to eight characters.
Database products, for example DB2®, might also restrict user IDs to
eight characters. If
you have a mixed environment, ensure that the user IDs that you use
within the broker environment are limited to a maximum of eight
characters. This is rally important if you are going to
deploy to a Linux Broker. I have several MessageBroker/WMQ
Explorer/Security articles on my blog: http://blog.webspheretools.com and on my Courseware site: http://www.themiddlewareshop.com/blog

Ensure
that the case (upper, lower, or mixed) of user IDs in your broker
environment is consistent. In some environments, uppercase and lowercase
user IDs are considered the same, but in other environments, user IDs
of different case are considered unique. For example, on Windows the
user IDs 'tester' and 'TESTER' are identical, but on Linux and UNIX
systems they are recognized as different user IDs.

Check the
validity of spaces and special characters in user IDs to ensure that, if
used, these characters are accepted by all relevant systems and
products in your broker environment.

Set up the required security on Windows

Before
you install the Broker component, the WebSphere Message Broker Toolkit,
or the WebSphere Message Broker Explorer, log on with a user ID that
has Administrator authority.

If you are installing the Broker
component, the installation wizard calls the mqsisetsecurity command
which completes the following tasks:

Creates a new security group called mqbrkrs.

Adds your current (logged on) user ID to the group mqbrkrs.

Adds your current user ID to the group mqm, if that group exists.

The
mqm group exists if you have already installed WebSphere MQ on this
system. If you have not, call the mqsisetsecurity command when you have
completed WebSphere MQ installation. If you use the Windows Launchpad
(described in Installing by using the Windows Launchpad), it completes
WebSphere MQ installation first.

Note: If you prefer to create
principals before you install WebSphere Message Broker, use the security
facilities provided by the Windows Control Panel.

If you are
running Terminal Services on this computer, change user mode to ensure
that actions taken during installation are completed correctly; for
example, the creation of .ini files and other related files in the
default system directory C:\Windows. If you do not change user mode,
files might be written to other locations and, although the installation
might complete successfully, the product might not work as expected.

Before you install any product components, enter the following command to change user mode:

change user /install

When installation is complete, enter the following command to restore the original user mode:

change user /execute

To
complete verification, your user ID must have Administrator authority.
If you log in with a different user ID from the ID with which you
perform installation, you must add that user ID to the groups mqbrkrs
and mqm. Use either the Windows security facilities or the
mqsisetsecurity command (run this command after you have logged on with
that different ID) to complete these additions.

The Windows Launchpad.

This
program installs prerequisite products if they are not already
installed, and identifies prerequisite products that are not at the
supported level.

We are going to start with running this tool form the installation media and see what it reports to us

As you can see below I am running the Launch pad that is inside the WebSphereMessage Broker (WMB) media folder.

As you can see, when this installation wizard was created WMQ 1.0.1.3 was the latest. I am going to try and use WMQ 7.5 instead.

Installing IBM WebSphere MQ

Before install any WMB tools/Broker etc, I am going to install WMQ 7.5

What is the purpose of the AMQSVC.EXE process on Windows platforms ie the Service called IBM MQSeries?

Well,
the amqsvc.exe is the MQ Service process, which launches amqmsrvn.exe
by way of dcom. It normally runs under SYSTEM account.

MQ needs a
dcom object, because it does not run as a traditional Windows service.
amqsvc.exe is the operating system service that acts as a stub, which
creates the dcom object, and MQ is launched from that dcom object. It is
done this way to enable MQ to run under a user specified account, which
is required for some of the MQ operations.

To stop the amqsvc.exe process (other than by using the 'net stop IBM MQSeries' command), run the command "amqsvc -stop".

The MQSeries (Windows) service (amqsvc) has a few command line options to help should problems arise:

amqsvc.exe

-INSTALL : Reinstalls the registry keys to make the MQ Service defined

I think these are self explanatory and we can have another peek after we have installed WMB.

I think we should launch MQ Explorer one to prove it is OK.

I am creating a Queue Manager called TEST.MQ to see if I can put on a Queue called TEST.Q

I used 2414 as the port in case I forget to remove it and so it doesn't conflict with Broker Default configuration.

Create the QLocal called TEST.Q

Let us put a test message

Let's get the message

We now have a queue depth of 1.

OK I am happy; we have proven WMQ is OK. We should install a Fixpack, bit you can see that in my course.

Completing WebSphere Message Broker now that we have WMQ installed

Installing WMB and MBTK and MBE

We can now see that the next time we run the Launchpad that WMQ is detected. Lists wrong version, but we don't care!

Click Launch Installation for WebSphere Message Broker

Click OK

Click Next

Click Next

I chose to not use IBM default location.

Click Next

Click Done.

Next
you will be asked to find our media for IBM Installation Manager. It
all depends on how your local installation media was unpacked.

Browse for disk 1 etc and continue

Note we will be prompted for the other disks during installation

I changed the install location

Click Next

Note: I skipped a few screen captures; I am sure by now you get the idea.

Click Install

Click finish

Now
it will install the Message Broker Explorer. A bit weird as we already
have WMQ Explorer, so it will just update them both to be the same i.e.
WebSphere MQ Explorer is updated with the MB Explorer plug-in.

Click Next, review summary then Click install

Click Done.

Let us now go an see what has been installed

Loads of WMB goodies.

I will now look at Users/Groups to see what we have. Essentially we have the new mqbrkrs group. Make sure you have access!

When we launch MQ Explorer or Mb Explorer we get

We can see the new WMB plug-in that allows WMA admins to see the Brokers.

I am now going to run Message Broker toolkit (MBTK)

It will prompt for a default workspace

Choose a suitable location, click OK

You can consult my WMB blog articles for how to sort out configuring a default broker.