Architecture of IBM InfoSphere Information Server
It is a client-server architecture built with administration, operation tools and client based design that access set of server data linking through same service layer as shown below
Here we discuss the following topics briefly:-
- Component Overview
- Topologies supported
Component Overview
Client tier
IBM Information Server provides various client interfaces enhanced to various positions within a company. The client tier contains IBM InfoSphere DataStage and QualityStage clients such as the Designer, Administrator and Director; and IBM Information Server and Server Web console.
There are 2 broad categories of clients: Administrative clients and User clients
1. Administrative Clients
This allows managing the areas of security, licensing, logging and scheduling.
- Administration works are achieved in the respective Server Web Console. The IBM Information Server Web Console is a browser-based interaction for administrative tasks like managing security and generating views of scheduled work.
- For IBM Infosphere DataStage and IBM Infosphere QualityStage mission administration, IBM InfoSphere DataStage Administrator Client is used. It governs IBM InfoSphere DataStage projects and does maintenance on the server. It’s used to mention general server defaults, add and delete projects, also to set mission properties.
2. User Clients
These clients help to do client tasks, for example, managing, creating and designing jobs and also validate, run, schedule and monitor jobs. The IBM Information Server console is a rich user-based interaction for actions for as profiling data and developing service-oriented apps.
- The IBM InfoSphere DataStage and QualityStage designer help you manage, create, and design jobs.The Designer client can also be used to define tables and can access metadata services.
- The IBM InfoSphere DataStage and QualityStage Director client that validates, schedules, runs and monitor jobs on the InfoSphere DataStage Server.
Note: Users are braced on 32-bit Microsoft Windows XP Pro, Server 2003 and Vista.
B. Server tiers
This Information Server Platform that includes the Services, Working Areas, Repository, and Information Services Director Resource Providers as below:
Service tier
IBM Information Server is built completely on the bundle of shared services that centralize core tasks across platforms. Shared services will permit these works to be managed and controlled in a single place, regardless of which suit the part being used.
The Server tiers comprise both service and product-specific services.
- The common servers are helpful for tasks such as security, logging, administration, metadata and reporting.
- Product services give tasks for specific products within Information server suite.
IBM Information server products have authorized access to three general categories:
- Design
- Execution
- Metadata
Layer |
Description |
Architectural Notes |
Client |
Analysis, Administration and development user interfaces and optional Bridges and Metabrokers. |
If client and server version match, multiple clients can access a single InfoSphere Information Server.
Using MultiClientManager, On a single workstation, multiple clients can be installed.
32-bit versions of Windows XP, Vista or 2003 is required |
Metadata Repository |
Database stores InfoSphere Information Server configuration, Settings, design, and runtime metadata. |
For each InfoSphere Information Server Installation, single metadata repository database is defined.
DB2 (included or customer supplied) v9.5 for 64 bit and v9.1 for 32-bit.
SQL Server 2005 and
Oracle 10g R2
(customer supplied) |
Domain |
InfoSphere Information Server common and product-specific services |
Requires WebSphere App Server (included or customer supplied) Release 6.0.2 Fix Pack 27 or later fix packs only
A single domain is defined for each InfoSphere Server Installation.
Standalone (non-network) profile only |
Engine |
Runtime engine which includes engine, PACK, connector and service agents. |
Multiple engines can be registered in single InfoSphere Information Server domain provided they are in different server environments.
Only one v8 engine but can co-exist with multiple v7 DataStage engines can be installed on a single server. |
Repository tier
The repository is used to store all the IBM Information Server product module objects and can be shared with other apps in the suite.
Clients are given an opportunity to access metadata and results of data analysis from their service layers.
Engine Tier
This parallel runtime engine executes IBM Information Server tasks.
It comprises of Information Server engine, Server agents, and Connectors & PACKS.
- IBM Information Server engine consists of products you install such as Information Server DataStage and QualityStage. It runs ETL and Standardizes tools.
- Service agents are Java processes that run behind on each system that hosts IBM InfoSphere DataStage. They give communication between Services and Engine Tiers.
- Connectors and Packaged Application Connectivity Kits; The Server connects to different sources without regard to they are structured or unstructured on the mainframe or apps. The connectors provide design-time interaction of data, such as browsing, runtime access, error handling and high performance.
Topologies Supported
IBM Information Server is created with a large scalable parallel software architecture that outputs high-level outcomes and performance. The IBM Information Server components completely dig on SMP, Grid, Clusters and MPP platforms to make use of all obtainable hardware resources.
IBM Information Server supports multiple topologies to reduce the thirst of your data addition and hardware desires, as
- Two-tier
- Three-tier
- Cluster
- Grid
Topology can be flexible in terms of adding clients and engines on additional systems.
Read these Top Trending Data Stage Interview Question’s now that helps you grab high-paying jobs !