New features and changes for IBM InfoSphere Information Server, Version 8.7

New features and changes were introduced for IBM® InfoSphere® Information Server, Version 8.7 along with documentation updates. The new and changed features and documentation updates are described in the following sections.

Table of contents

InfoSphere Information Server, Version 8.7, new features and changes:

• Common capabilities across the InfoSphere Information Server suite
  • Administering
  • Connecting to external sources
  • InfoSphere Blueprint Director
  • InfoSphere Metadata Asset Manager
  • Managing security
• InfoSphere Business Glossary
• InfoSphere DataStage
• InfoSphere Information Analyzer
• InfoSphere Metadata Workbench
• InfoSphere QualityStage

Documentation changes included in the Version 8.7 release:

• Documentation introduced with Version 8.7

Top  |  Next

Administering

---

Bottom

Maintenance mode

Using a new command-line tool, the suite administrator can place InfoSphere Information Server into maintenance mode. While in maintenance mode, only users with the suite administrator role can log in. This feature simplifies the way that administrators can quiesce the system when they require exclusive access. For more information, refer to Maintenance mode.

Command-line administration of user and roles

Administrators in some organizations standardize the way that they establish the InfoSphere Information Server environment for new projects. In order to support that process from beginning to end, the command-line interfaces are expanded to allow the assignment of users and roles for InfoSphere DataStage® and QualityStage™ projects. For more information, refer to Managing assets by using the command line.

IPv6 Support

For organizations that need to migrate their networks to the newer, expanded set of Internet Protocol addresses. InfoSphere Information Server, Version 8.7 is fully compatible with IPv6 addresses. Also, it supports dual-stack protocol implementations that are mixed between IPv4 and IPv6. For more information, refer to Configuring your network.

New backup and restore functionality

To prevent the loss of data and to prepare for disaster recovery, organizations need robust backup strategies. InfoSphere Information Server, Version 8.7 introduces a new administration tool called isrecovery, which provides capabilities to backup and restore the databases, profiles, and directories that are associated with InfoSphere Information Server. The isrecovery tool supports all three server tiers: the services tier, the engine tier, and the metadata repository tier. When you run a backup or recovery, all tiers that are installed on the computer are backed up simultaneously.

Top  |  Next

Connecting to external sources

---

Previous  |  Bottom

Connectivity in InfoSphere Information Server, Version 8.7 includes the following new features and changes.

Netezza® connector

Provides native connectivity to the Netezza appliance, and offers improved and consolidated support for greater performance and functionality. For more information, refer to Netezza Performance Server®. The Netezza connector includes the following features.

• Uses the massively parallel, highly scalable, and dynamically configurable framework of InfoSphere DataStage to access each SPU in the Netezza appliance for optimum performance. For example, the connector supports performance loading by using the external table load method, which can be on the same database or on an external database.
• Supports the update then insert operation to speed up writing to disk.
• Creates tables by using random or user-defined distribution keys.
• Row-selected SQL operation, which dynamically chooses the SQL operation at run time based on the actual data.
• Supports two-level and three-level reference object naming.
• Uses various write modes, table actions, and transaction modes.
• Uses user-defined SQL. You can use a user-defined UDX in the SQL statement by loading from a flat file or you can use SQL that is pre-defined.
• Uses properties for before and after SQL statements that can run across all the runtime nodes, or just one node. Various post actions are available if the statement fails.
• Outstanding out of box performance rates for loading and unloading data. Lab performance tests measured rates comparable to Netezza command-line bulk load utilities.

Big Data and Hadoop support

Organizations are increasingly adopting Big Data tooling to address the most challenging data volumes in their business. InfoSphere Information Server, Version 8.7 adds the new Big Data File stage so that these organizations can make the most of this data through the user-friendly InfoSphere DataStage development paradigm. With support for the Hadoop Distributed File System (HDFS), users can access the data directly on this distributed file system. The Big Data File stage mirrors the Sequential File stage experience so that users will find it intuitive to get started. In that way, the Big Data File stage provides reading from multiple files in parallel (either listed specifically or through file patterns) to simplify how data is merged into a common transformation process. Additionally, the InfoSphere DataStage parallel engine can mimic the same degree of partitioning as the Big Data file, or the engine can dynamically repartition that data "on the fly" based on different business requirements. These features offer both flexibility and optimization as organizations address their Big Data challenges.

Other new connectivity features

DRS connector

Allows the database type to be dynamically chosen at run time, which enables jobs to be reused in various deployment scenarios. Supports this flexible connectivity between Oracle, IBM DB2®, and ODBC.

CDC Transaction stage

Allows information that is captured from log-based sources by using InfoSphere Change Data Capture (InfoSphere CDC) to be delivered in near real-time to InfoSphere DataStage. By using our unique bookmarking technology, this solution architecture provides guaranteed data delivery and transaction integrity through a complex set of data transformation and cleansing tasks to one or more targets.

Teradata Connector TMSM and Dual Load support

Provides native support to the Teradata Multi-System Manager (TMSM) and Dual Load capability.

Enhanced SQL logging for connectors

Increased coverage in connectors for writing executed SQL statements to the job log, which provides better support for exception research.

DB2 connector performance enhancement

Improved DB2 connector performance when loading to IBM DB2.

Other new database connectivity enhancements include support for the following data sources

• IBM DB2 for Linux, UNIX, and Microsoft Windows, Version 9.7 and 9.8 (pureScale®)
• IBM DB2 for z/OS®, Version 10
• IBM WebSphere® MQ, Version 7.0
• IBM Informix®, Version 11.7
• Teradata Database 13.10 and 14.0
• Oracle Database 11g Release2
• Sybase ASE, Version 15.5
• Sybase IQ, Version 15.2
• Netezza 4.6, 6
• DataDirect ODBC, Version 6.1

Top  |  Next

InfoSphere Blueprint Director

---

Previous  |  Bottom

InfoSphere Blueprint Director Version 8.7 includes the following new capabilities. For more information, refer to InfoSphere Blueprint Director.

Milestone planning support

Most information projects are implemented and deployed in multiple iterations. For example, data warehousing and MDM projects have multiple milestones at which new data sources and new information consumers are added. Milestone planning support:

• Enables you to specify the milestone at which an element becomes effective or remains effective. For example, you could specify that a new data source and load process into the warehouse will be deployed at a milestone called 1Q12, the first quarter of the year. Another data source and corresponding load process could then be deployed at the start of the second quarter of the year, when the first data source and load process will be undeployed. In addition to specifying when a milestone element becomes effective, InfoSphere Blueprint Director gives you the ability to visualize the milestones so that the team can view the evolution of the information landscape in the blueprint definition.
• Enhances one of the key differentiators of InfoSphere Blueprint Director, which is the support of the entire life cycle. InfoSphere Blueprint Director can specify how the landscape evolves over time in multiple agile iterations.

Task management integration

In addition to providing method guidance for information projects, InfoSphere Blueprint Director enables you to select steps from the method guidance that can be tracked as tasks. The method documentation shows which roles are required, what their tasks are, in which sequence these tasks should be performed, and which artifacts will be delivered. Task management integration gives you the ability to:

• Assign tasks that are either derived from the method or created manually
• View assigned tasks for a person and allows that person to articulate that the task is complete
• Have a sample and basic dashboard of task completion for a project

Top  |  Next

InfoSphere Metadata Asset Manager

---

Previous  |  Bottom

The new InfoSphere Metadata Asset Manager, which is installed as a part of InfoSphere Information Server, provides centralized import and management of common metadata, including database and data file assets, logical and physical data models, and business intelligence assets. For more information, refer to Importing and managing assets by using IBM InfoSphere Metadata Asset Manager.

Logical data model and physical data model support

The suite tools and metadata repository of InfoSphere Information Server now support logical data models along with physical data models and their contents, including logical entities and attributes, and design tables and columns. On import, relationships between logical and physical data models and the schemas that implement them are set automatically, when it is possible to do so. You can use the Repository Management tab of InfoSphere Metadata Asset Manager to set additional implementation relationships. For more information, refer to Logical data model assets.

Import

InfoSphere Metadata Asset Manager centralizes the metadata import in Information Server into a web interface. You can import metadata to a staging area where you can inspect it before you share it with others. For more information, refer to Importing and sharing assets.

This centralized import functionality has the following benefits:

• You can use both bridges and connectors for metadata imports.
• You can analyze and manually compare, reimport, and preview the effect the import will have on existing metadata assets before you share it.
• You have one-click access to InfoSphere Metadata Workbench (if installed) to view specific existing assets that might be affected by the import.
• You can maintain the metadata throughout its life cycle, keeping a record of the contents of all imports and reimports to the staging area and to the metadata repository.
• You can eliminate any problem assets, such as duplicates, before they are shared.
• You can run express imports that automate the analysis and preview, and automatically import directly without first staging the metadata.

In InfoSphere Information Server Version 8.7, InfoSphere Metadata Asset Manager is the preferred tool for importing metadata into InfoSphere Information Server.

Repository Management

The Repository Management tab was moved into InfoSphere Metadata Asset Manager from its former location in the web console. For more information, refer to Managing common metadata assets.

In addition to the ability to browse and search common metadata in the metadata repository, the Repository Management tab contains the following new functionality:

• Improved management of duplicate assets, including the ability to merge or delete duplicates.
• You can display and delete any assets that have been disconnected from their parent assets.
• You can set implementation relationships between logical data models, physical data models, and database schemas or data files. These relationships let you trace a column that is used by an InfoSphere DataStage and QualityStage job back to the design column and logical entity that originally defined the column.

Top  |  Next

Managing security

---

Previous  |  Bottom

Strongly encrypted credential files for command-line utilities

Provide a unified means for handling and encrypting credential arguments for the command-line tools, such as istool and dsjob commands. This option provides encryption "at rest" for the login credentials. For more information, refer to The credentials file.

Strongly encrypted job parameter files for dsjob command

Version 8.7 extends the existing encryption capability of InfoSphere Information Server by adding encryption to the dsjob command-line paramfile option, which specifies that a file contains strongly encrypted parameter values. This option provides encryption "at rest" for job parameters. For more information, refer to Securing credentials and parameter values in dsjob commands.

Encryption algorithm customization

Although the AES-128 symmetric-key encryption algorithm provided by InfoSphere Information Server is compliant with many government and industry standards, administrators of some organizations might want to use their own standard encryption variant. For those customers, InfoSphere Information Server, Version 8.7 provides the means to override the AES-128 algorithm. For more information, refer to Adding a custom encryption provider.

Mixed LDAP and operating system support by using PAM

Version 8.7 leverages Pluggable Authentication Module (PAM) as a means to mix the existing authentication protocols of LDAP and the local operating system to support both individual and "functional" accounts simultaneously. Functional users can represent a role that can be shared by more than one person within an organization, or a role that can be assigned to a scripted process. For more information, refer to Shared user registry overview.

Automated audit trail for all DBMS access with InfoSphere Guardium®

This feature is provided to satisfy regulatory mandates that require an organization to know which people and processes are accessing sensitive or personally identifiable information (PII). Connectors for InfoSphere Information Server, Version 8.7 can be configured to automatically register entries for an audit trail into InfoSphere Guardium, which provides a complete view of the origin of any data integration activity that affects the database.

Top  |  Next

InfoSphere Business Glossary

---

Previous  |  Bottom

InfoSphere Business Glossary Version 8.7 includes the following new capabilities. For more information, refer to IBM InfoSphere Business Glossary.

• Provides a new integrated user interface for authoring, administering, and viewing the glossary
• Supports a workflow process for collaborative glossary content development. For more information, refer to Administering the glossary.
• Enables an InfoSphere Business Glossary administrator to assign permissions for authoring the glossary. For more information, refer to Authoring glossary content.
• Enables an InfoSphere Business Glossary administrator and author to assign labels to assets and terms. For more information, refer to Labels.
• Enables an InfoSphere Business Glossary administrator to export specific subcategories. For more information, refer to Importing and exporting glossary content.
• Provides enhanced search and filtering capabilities
• Support for physical data models, logical data models, and implemented data resources
• Provides a utility that generates a glossary from a logical data model
• Enables an InfoSphere Business Glossary administrator to configure external asset types
• Enables client-driven multilingual support for user interface labels and for support for right-to-left languages. For more information, refer to Configuring a specific locale.
• Provides a new user role, Business Glossary Asset Assigner, that enables you to assign assets to terms from other InfoSphere Information Server tools. For more information, refer to Security roles.
• Support for logical data models in InfoSphere Business Glossary Client for Eclipse:
  • Importing term assignments to a logical data model package.
  • Exporting term assignments from a logical data model package.
• Supports integration with IBM InfoSphere Warehouse Design Studio and with IBM Optim™ Development Studio

Top  |  Next

InfoSphere DataStage

---

Previous  |  Bottom

InfoSphere DataStage contains the following new features.

The InfoSphere DataStage Debugger

The following screen capture shows a job where a breakpoint is established to debug the job. For more information, refer to The IBM InfoSphere DataStage Debugger.

Figure 1. A job that shows the menu and window of the InfoSphere DataStage Debugger

• InfoSphere Information Server, Version 8.7 extends existing debugging capabilities for parallel jobs through an interactive debugger in the Designer client. Through this capability, you can establish breakpoints on the data flow links of jobs in order to interrogate the values as they are being transformed at job run time by the various components.
• The debugging process is straightforward. Right-click any link to toggle the breakpoint on or off. Once a breakpoint is established, the default mode causes a debug run to pause at every row passing through that link. You can edit the breakpoint and change this default behavior so that the job pauses at a different frequency or upon a certain data condition, for example account_id = ‘12345’.
• When the debug run is paused at a break condition, you can view the individual nodes where any of the stages are running, the data on each of those nodes, and the number of rows that already passed through that link. During investigation, you can examine the properties of any of the stages that compose the job design and then alter the breakpoints based on new information that you learn by investigating the data. You can also add specific fields to the watch list in order to focus attention on only the set of fields you are most interested in.
• Because the debug mode of the job runs with the same configuration file as the standard run, debug mode catches any specific data conditions that exist based on how data is being partitioned and distributed across the infrastructure. So, regardless of whether the job is running on a small computer or across an enterprise class grid, or whether the databases accessed by the job are partitioned out to 128 nodes, the debug results mimic the way the job will be deployed in your standard environment.

InfoSphere DataStage Operations Console for accessing operational metadata and monitoring the runtime environment

The new InfoSphere DataStage Operations Console contains the following features. For more information, refer to Monitoring jobs.

The following screen capture shows the InfoSphere DataStage Operations Console main dashboard.

Figure 2. The InfoSphere DataStage Operations Console

• Production operators, development teams, and other stakeholders need access to the operational metadata of their data integration environment. Whether they are confirming that the environment is live, reviewing job run history, or working to troubleshoot system failures, these users need direct access to the most relevant information in order to perform their jobs efficiently.
• The Operations Console provides a view-only client that allows simple, web-based access to the runtime environment of InfoSphere Information Server. High-level graphs provide a summary view of the current state of the environment, such as what is running, how much resource is being consumed, and whether the environment is healthy. With several clicks, you can find the supporting details that you need to answer questions and achieve higher levels of productivity. Key features of this interface include:
  • Dashboard style graphs representing current job activity
  • Indications of successful or failed jobs statuses
  • System health information
  • Resource consumption views
  • Server-wide and project-specific access based on the privileges of a particular user
  • High-level summary and detailed statistics for the job run history, including job start date/time, elapsed run time, record counts, parameter detail, and control and error messages
  • Utilities to compare multiple job runs and to filter relevant differences
• To support the innovative paradigm of this interface, InfoSphere Information Server includes a new role called Operations Viewer. This role is restricted to use only the Operations Console read-only views. Administrators can generously assign this role to users and groups, including in production, and trust that no objects within InfoSphere Information Server can be altered or run. Additionally, in situations where operational metadata needs to be shared with other applications in the enterprise, organizations can use the fully documented metadata schema to define those integrations.

Balanced Optimization for Netezza

• The Balanced Optimization capability provides the ability to push transformation into source databases, process in the high performance engine of InfoSphere DataStage, and push processing into target databases. You express the logic of your data integration processes in the current, flow-oriented convention of InfoSphere DataStage, and then that logic is automatically optimized to achieve the benefits of pushing the desired parts of the processing to the database.
• In InfoSphere DataStage Balanced Optimization for Version 8.7, that development paradigm has been extended to interoperate with Netezza through the new Netezza connector. In jobs where you use this functionality, transformation processing is pushed to the Netezza appliance. The job uses the SPUs and parallel capability of the appliance to lessen the data round-trip time by keeping the data in the appliance itself. This capability is particularly useful when data reduction can be achieved at the source DBMS, or when the source and target of a given data integration task derive from the same DBMS.

Top  |  Next

InfoSphere Information Analyzer

---

Previous  |  Bottom

IBM InfoSphere Information Analyzer, Version 8.7 includes the following new features and changes.

Data Rules stage

The following screen capture shows a job that uses the Data Rules stage.

Figure 3. A job that uses the Data Rules stage showing the number and validity of processed records

You use this new feature to invoke InfoSphere Information Analyzer data rules in-stream as part of an InfoSphere DataStage and QualityStage job, or within an InfoSphere Information Services Director web service. You can include rules as part of an ETL or data cleansing process. In these cases, the rule or rule set definitions created in InfoSphere™ Information Analyzer are reusable as a unique rule validation stage to ensure that incoming content meets the prescribed rules, and the outgoing contents can be produced based on defined rule logic. Also, it is now possible to check whether your data is valid in real time, for example, by capturing the changes in real time by using InfoSphere Change Data Capture, and then validating the changes with the Data Rules stage. For more information, refer to Data Rules stage.

Logical data models, physical data models, and implementation models

InfoSphere Information Server and Foundation Tools, including InfoSphere Metadata Asset Manager, are adopting broad support for physical and logical data models. As part of that overall theme, InfoSphere Information Analyzer supports use of physical and logical data model assets in rule definitions and a facilitated approach to discover and bind associated assets. In inferred model generation, the physical data model generation is enhanced for a more integrated approach. For more information, refer to:

• Logical data model assets
• Physical data model assets
• Creating rule logic by using tools in the Tabbed Palette

HTTP API enhancements for flow through processing

Additional APIs are added in this release to form a more complete set of interfaces supporting flow-through processing. For more information, refer to Developing applications with the HTTP API.

The API enhancements include these domains:

• Folder support
• Metrics and benchmarks
• Key and cross-domain analysis
• Public rules

Enhancements on rules output

This enhancement allows distinct records to be generated in rule output when the rule contains only aggregation functions. Only one record is output per grouping value.

Performance enhancements

Performance enhancements for this release include:

• Rules that use join conditions are accelerated by pushing down the join operations to the SQL select statement executed on the analyzed source whenever it is possible, instead of loading all the data and joining them in InfoSphere DataStage and QualityStage.
• Rules that use a sampling are accelerated by reducing the number of rows that must be loaded from the source database to InfoSphere DataStage and QualityStage.
• IBM DB2 compression for Information Analyzer database (IADB). When using IBM DB2 as the analysis database, you can configure IBM DB2 compression to reduce the storage footprint of the analysis database. Query performance is not impacted.
• Internal algorithms refactoring for performance. Column analysis performance enhancements through internal algorithm refactoring, and other internal refactoring take advantage of new infrastructure features.
• The rule execution engine was reengineered and optimized for speed.
• Performance enhancements for key user interface areas including open project, open project properties, and the home page.

Top  |  Next

InfoSphere Metadata Workbench

---

Previous  |  Bottom

InfoSphere Metadata Workbench Version 8.7 includes the following new features and changes. The following screen captures show the browser-based interface of metadata workbench.

Figure 4. The metadata workbench canvas showing a data lineage report

Figure 5. The metadata workbench inventory pane of a data lineage report showing additional information for each asset

Supports logical data models

• The metadata workbench displays logical data models, physical data models, and implemented data resources and their relationships. You can view, search, and query the models, entities, and attributes. The details page of a term displays its navigation (term -> logical data model asset -> physical data model asset -> implemented data resource).
• You can assign logical data model assets and physical data model assets to terms. In addition, you can assign stewards to logical data model assets and to physical data model assets.
• You can use published queries to display the relationships between logical data models, physical data models, and implemented data resources.

Supports Netezza connector

Supports data lineage, impact analysis, and other metadata management functions for the new Netezza connector.

Supports InfoSphere CDC metadata

Metadata for the sources of InfoSphere Change Data Capture (InfoSphere CDC) is integrated into InfoSphere Metadata Workbench. This integration allows for functions like impact analysis and data lineage to extend from the initial log-based replication task, throughout the rest of the information management infrastructure.

Data lineage UI enhancements

Data lineage displays the flow of data, including ETL information, from the data source to the BI report. You can expand an ETL source or a data source and select a database table or a column to display the lineage flow through those selected assets. For more information, refer to Running the Manage Lineage utility.

Supports SAP stages

Data lineage reports include SAP stages.

Supports InfoSphere Warehouse

The metadata workbench provides data lineage and impact analysis reports that are based on design flow metadata. The reports include assets from data sources to InfoSphere Warehouse, and from InfoSphere Warehouse to the data marts. The reports use the mappings of data flows that are created by Informix SQL Warehousing Tool (SQW) and from Design Studio.

Simplified automated services

The following steps in automated services are combined into a single UI called Manage Lineage. For more information, refer to Manage Lineage utility.

1. Detect association between stages and data sources, between databases and database aliases, and between two identical schemas. This step was previously called Stage Binding.
2. Map a database name to an alias name. This step was previously called Database Alias.
3. Set the relationship between stages and data sources, between databases and database aliases, and between two identical schemas.

Displays custom attributes from InfoSphere FastTrack

InfoSphere FastTrack allows custom attributes to be created and assigned to an InfoSphere FastTrack mapping project. The metadata workbench displays these custom attributes in the details page of the mapping project.

Supports custom attributes for implemented data resources, BI Reports, data files, and extended data sources

The metadata workbench displays these custom attributes in the details page of these assets.

Displays folder structure for extension mapping documents and extended data sources

The administrator can create and manage folders for extension mapping documents and extended data sources. These folders can be organized into a hierarchical structure. The folder structure is maintained during import. The administrator can browse the folder structure. In addition, the administrator can move extension mapping documents and extended data sources to a different folder.

Provides home page enhancements

The home page has been simplified to enable you to search for an asset or to run an existing query.

Top  |  Next

InfoSphere QualityStage

---

Previous  |  Bottom

InfoSphere QualityStage, Version 8.7 includes the following new features and changes.

Match Specification Setup Wizard

You can now use a wizard to create basic match specifications for US name and address data. The specifications that you create with the wizard provide criteria for matching records from one or two sources. The specifications support common matching goals for individuals and businesses, such as deduplication and grouping records with similar values. You can use the specifications in the new predefined matching jobs or as models for specifications that meet your matching requirements. For more information, refer to Creating match specifications.

Predefined jobs

InfoSphere QualityStage, Version 8.7 includes predefined standardization and matching jobs for US name and address data. You can use predefined standardization jobs to generate standardized data and the frequency information for that data. You can use predefined matching jobs to match records from one or two sources of input data. Sample data is provided for use with the predefined jobs. For more information, refer to Predefined standardization jobs and Predefined matching jobs.

Match Statistics report

The new Match Statistics report presents summary-level statistics about the matching results and statistics about the matching process for each match pass. For more information, refer to Match Statistics reports.

Indian rule sets

You can use the new Indian rule sets in jobs that standardize Indian address and area data. A shared container is imported with the rule sets to help you design a job that uses the rule sets. For more information, refer to Predefined rule sets and Indian address rule sets.

Rule set enhancements

The predefined rule sets are enhanced in the following ways:

• Some of the domain-specific rule sets now generate improved values for matching.
• The USADDR rule set is enhanced in several ways. For example, the value ONE in ONE CHILDRENS PLACE is identified as a house number.
• The column descriptions in the rule sets provide more information.
• Rule sets now use the REPEAT statement to apply actions repetitively until an action does not match the associated pattern.

Top

Documentation introduced with Version 8.7

---

Previous  |  Bottom

Administration

• Configuring the services tier to use Pluggable Authentication Module (PAM)
• Backing up and restoring InfoSphere Information Server with the new isrecovery tool
• Encrypting user credentials
• Adding users, groups, and roles through the DirectoryCommand tool

Common metadata assets

Added documentation of common metadata assets, the assets that are shared by suite tools. Common metadata assets include logical data models, physical data models, implemented data resources, and business intelligence assets. For more information, refer to Common metadata assets. The documentation includes the following features:

• Definitions of each asset type
• Explanation of how the identity of assets in the metadata repository is established
• Explanation of implementation relationships between logical data model assets, physical data model assets, and implemented data resources
• Delete rules for assets
• Explanation of duplicate assets and disconnected assets

IBM InfoSphere Information Server Guide to Managing Common Metadata

Added a single new PDF guide that includes the content for the following areas, which are grouped under the topic, Managing metadata, in the information center. To download the PDF, refer to IBM InfoSphere Information Server Version 8.7 product documentation.

• Importing and managing assets by using IBM InfoSphere Metadata Asset Manager
• Exchanging metadata by using IBM InfoSphere Metadata Integration Bridges
• Common metadata assets

InfoSphere DataStage

• The InfoSphere DataStage glossary lists and defines terms that administrators and job developers will find useful for lending understanding as they use the software. For more information, refer to InfoSphere DataStage glossary.
• For more information about the methods you can use to examine problematic parallel jobs, refer to Debugging parallel jobs.

InfoSphere Metadata Asset Manager

Added documentation of the new InfoSphere Metadata Asset Manager, including documentation of the following functionality:

• Installation
• Import and administration
• Managing assets on the Repository Management tab

InfoSphere Metadata Integration Bridges

• Revised documentation of bridges to emphasize importing by using InfoSphere Metadata Asset Manager. Also added documentation about importing logical data models and physical data models. For more information, refer to Exchanging metadata by using IBM InfoSphere Metadata Integration Bridges.
• Updated List of supported bridges and System requirements for bridges.

Managing assets by using the command line

Added documentation for the following new functionality:

• Generating glossary content from business intelligence models. For more information, refer to glossary bi2bg command.
• Importing and exporting logical data models, physical data models, and custom attributes. For more information, refer to Common metadata assets.

Top