Use the IBM InfoSphere Master Information Hub Workbench to distribute and deploy new hubs

This article describes how to deploy Master Data Management solutions developed in the IBM® InfoSphere™ Master Data Management (MDM) Workbench. The approach provides a quick and easy method that enables successful deployments with a minimum of effort. Learn how to use the accompanying tools to package your solution in a single deployable archive, removing the manual steps currently required. The article also applies to solutions developed using the InfoSphere Master Information Hub (MIH) Workbench, a subset of the MDM Workbench.

Share:

John Beaven (beavenj@uk.ibm.com), Software Engineer, IBM

John Beaven photoJohn Beaven is a senior software engineer and team leader based at IBM's Hursley Laboratory. John has been involved in the development of a range of products including CICS, WebSphere, and more recently IBM's InfoSphere technology. John joined IBM in 1996 after graduating from Southampton University.



Barry N. Dow (barry_dow@uk.ibm.com), Software Engineer, IBM

Barry Dow photoBarry Dow has worked for IBM since 2000. He is currently a software engineer in the IBM Software Group Information Management Division working on Eclipse-based tooling for the InfoSphere Master Data Management product, and is also the build lead for the Hursley-based team. Previously he worked in IBM's Voice Systems division and filed several patents and achieved his first invention plateau.



Robert Maddison (bob_maddison@uk.ibm.com), Software Engineer, IBM

Bob Maddison photoBob Maddison is a senior software engineer based at the IBM Hursley Laboratory. Over the past twenty years he has been involved with a number of major IBM products including CICS, Java Virtual Machines, and more recently with development of tooling for IBM Master Information Hub product.



Rebecca Schaller (rebecca.schaller@uk.ibm.com), User Experience, IBM

Rebecca Schaller photoRebecca Schaller is a user experience professional based at the IBM Hursley Laboratory. She is responsible for the usability and consumability of the Eclipse-based tooling for the InfoSphere Master Data Management product in the IBM Software Group Information Management Division. She has filed 10 patents and achieved her second invention plateau.



09 September 2010

Also available in Chinese

Introduction

The IBM InfoSphere Master Information Hub (MIH) provides a runtime framework that can be customized to create information management solutions for a wide range of applications. This process is referred to as creating a new hub.

New hubs created on a development system using the MIH Workbench can be packaged for installation on a production environment or supplied to a third party for further customization.

Hubs can be built on preceding hubs, and there is no practical limit to the number of new hubs that may be created in this way.

This article describes the process by which hubs are packaged using the accompanying tools. It assumes the reader is familiar with both the Master Information Hub platform and the MIH Workbench.


Customization of the MIH tar.gz file

Packaging hubs involves customization of the original MIH tar.gz file supplied with the product. The hub export tool accompanying this article combines the tar.gz file with the new hub to create a replacement tar.gz. This file can then be used to install the new hub in the same way as the original MIH application.

Two types of installation are supported:

  • Normal installation of the hub to a production system using the product installer
  • Installation to Rational® Application Developer (RAD) or Rational Software Architect (RSA) using the Development Environment and Test Wizard, known as DEST. This allows third parties to introduce their own customizations.

HubExport.zip archive

Supplied with this article is an archive named HubExport.zip that contains an Eclipse project in project interchange format. This project contains an ANT task that can generate the new tar.gz file.


Prerequisites

In order to use the export tool, you should have used the MIH Workbench to develop and test a new hub application.


Running the MIH Workbench Hub Export Tool

Follow these steps to run the export tool:

  1. From RAD or RSA, open the Import Project Interchange wizard by selecting File > Import and then selecting Other > Project Interchange as shown in Figure 1:
    Figure 1. Import the Hub Export Tool
    Shows explorer interface with Project Interchange selected
  2. Click the Browse... button and select the HubExportTool.zip archive supplied with this article.
  3. Confirm the HubExport project is selected as shown in Figure 2, and click Finish to import the HubExport project into the workspace.
    Figure 2. Import HubExport Project
    shows HubExport selected in Import Projects screen
  4. Before the new tar.gz file can be created, the supplied utility must be configured. Open the export.properties file located in the HubExport project and modify the following settings:
    • source.tar.gz.file - The tar.gz file that was originally used to prepare the development environment with DEST (for example, c:\\install\\MIH900_WAS_AIX.tar.gz)
    • target.tar.gz.file - The name and location of the tar.gz file to be generated by the script (for example, c:\\temp\\NewHub.tar.gz)
    • plugins.folder - The folder containing the installed workbench plugins (for example, c:\\ibm\\SDPShared\\plugins\\plugins)
  5. Once the configuration is complete, the ANT script can be executed to generate the new tar.gz file. Right click the export.xml file located in the HubExport project and select Run As > Ant Build...
  6. From the JRE tab ensure the Run in the same JRE as the workspace option is selected, then click Run to execute the task. The new tar.gz file will be created.
    Figure 3. Run the Hub Export Tool to generate new tar.gz file
    Shows selected: Run in the same JRE as the workspace

Installation to a production system

The installation procedure for the new hub is essentially the same as for MIH. Follow the steps below to complete the installation.

  1. Unpack the new tar.gz archive created by the script in Step 6 above.
  2. Run the MIH Launchpad application located in the archive to install the new hub (refer to the original product documentation that comes with the product for details).
    Figure 4. Install the new hub from the MIH Launchpad
    Shows launchpad with Install InfoSphere Master Information Hub selected
  3. Open the SetupHub_<DBType>.sql file and modify all the <SCHEMA> tags to match the actual database schema name. These tags appear in a number of places within this file. For example:
    Listing 1. Modifying SCHEMA tags with database name in SetupHub_DB2.sql
    CREATE TABLE <SCHEMA>.PROFILE (
        Profilepk_Id BIGINT  NOT NULL   ,
        name VARCHAR(250)   NOT NULL   ,
        age VARCHAR(250)   NOT NULL   , 
        quality_Code BIGINT   NOT NULL   ,
        category VARCHAR(250)  NOT NULL   ,
        LAST_UPDATE_DT TIMESTAMP  NOT NULL  WITH DEFAULT CURRENT TIME   ,
        LAST_UPDATE_TX_ID BIGINT   ,
        LAST_UPDATE_USER VARCHAR(20)
    );
  4. Open a command prompt and connect to the database.
  5. Run the DB2 or SQLPLUS command (depending on the database being used) to execute the SQL script:
    • db2 -tvf SetupHub_DB2.sql (DB2 on Linux, UNIX, or Windows)
    • db2 -tvf SetupHub_ZOS.sql (DB2 on z/OS)
    • sqlplus userid/password@host @ SetupHub_ORACLE.sql (Oracle)

The SetupHub_<DBType>.sql file combines the SQL scripts generated for each module project in the hub. Using this composite SQL file avoids the need to run the individual module project SQL scripts and simplifies the database configuration process.


Installation to RAD or RSA using DEST

The developer installation procedure for the new hub is essentially the same as for MIH. Follow the steps below to prepare the development environment.

  1. Install the MIH Workbench supplied with the MIH product (refer to original product documentation for details).
    Figure 5. Prepare the MIH Workbench for development
    shows screen where you set up the application development environment
  2. Use the Development and Test Environment Wizard provided by the MIH Workbench to prepare the development environment. When specifying the Application distribution file in the wizard, select the new tar.gz file generated by the hub export tool.
  3. Open the SetupHub_<DBType>.sql and modify all the <SCHEMA> tags to match the actual database schema name. These tags appear in a number of places within this file. As an example, see Listing 1 above.
  4. Open a command prompt and connect to the database
  5. Run the DB2 or SQLPLUS command (depending on the database being used) to execute the SQL script:
    • db2 -tvf SetupHub_DB2.sql (DB2 on Linux, UNIX, or Windows)
    • db2 -tvf SetupHub_ZOS.sql (DB2 on z/OS)
    • sqlplus userid/password@host @ SetupHub_ORACLE.sql (Oracle)

The SetupHub_<DBType>.sql file combines the SQL scripts generated for each module project in the hub. Using this composite SQL file avoids the need to run the individual module project SQL scripts and simplifies the database configuration process.


Conclusion

Creating a deployable archive using the hub export tools outlined in this article enables consistent and straightforward deployment of InfoSphere Master Information Hub based solutions developed using the MIH Workbench. The tools automate and simplify the existing deployment process to reduce the likelihood of any errors occurring. The resulting archive may be used in the same way as the original InfoSphere Master Information Hub install media, to create new servers or enable future development by a third party.


Download

DescriptionNameSize
Master Information Hub Export ToolHubExportTool.zip36KB

Resources

Learn

Discuss

Comments

developerWorks: Sign in

Required fields are indicated with an asterisk (*).


Need an IBM ID?
Forgot your IBM ID?


Forgot your password?
Change your password

By clicking Submit, you agree to the developerWorks terms of use.

 


The first time you sign into developerWorks, a profile is created for you. Information in your profile (your name, country/region, and company name) is displayed to the public and will accompany any content you post, unless you opt to hide your company name. You may update your IBM account at any time.

All information submitted is secure.

Choose your display name



The first time you sign in to developerWorks, a profile is created for you, so you need to choose a display name. Your display name accompanies the content you post on developerWorks.

Please choose a display name between 3-31 characters. Your display name must be unique in the developerWorks community and should not be your email address for privacy reasons.

Required fields are indicated with an asterisk (*).

(Must be between 3 – 31 characters.)

By clicking Submit, you agree to the developerWorks terms of use.

 


All information submitted is secure.

Dig deeper into Information management on developerWorks


static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=Information Management
ArticleID=517732
ArticleTitle=Use the IBM InfoSphere Master Information Hub Workbench to distribute and deploy new hubs
publish-date=09092010