My usual use case for IBM InfoSphere Information Server is ETL, where we take data from one source to another data warehouse solution.
IBM InfoSphere Information Server integrates seamlessly with both structured and unstructured data environments, offering advanced ETL capabilities and efficient data handling for large-scale enterprise applications.
| Product | Mindshare (%) |
|---|---|
| IBM InfoSphere Information Server | 0.9% |
| Informatica Intelligent Data Management Cloud (IDMC) | 3.7% |
| SSIS | 3.6% |
| Other | 91.8% |
| Company Size | Count |
|---|---|
| Small Business | 4 |
| Midsize Enterprise | 1 |
| Large Enterprise | 4 |
| Company Size | Count |
|---|---|
| Small Business | 39 |
| Midsize Enterprise | 36 |
| Large Enterprise | 75 |
IBM InfoSphere Information Server is designed for enterprise-level data integration with a focus on efficient ETL processes. It excels in moving data between sources and data warehouses, particularly valuable in sectors such as retail banking. Users leverage its robust Parallel Extender for improved processing efficiency and DataStage administration for comprehensive task management. However, areas like technical support and scalability require growth, especially for cloud-based deployments. While the Cloud Pak for Data enables acceleration on the cloud, the on-premises approach often remains tied to traditional hardware configurations.
What are the crucial features?IBM InfoSphere Information Server is widely implemented in industries that require heavy data transformation, such as retail and financial services. Its robust ETL processes are essential for moving critical data between systems, ensuring streamlined data flow and integration across various platforms.
IBM InfoSphere Information Server was previously known as InfoSphere Information Server, IBM Information Server.
| Author info | Rating | Review Summary |
|---|---|---|
| Senior Data Engineer at Mohammed Mansour Alrumiah | 4.0 | I've used IBM InfoSphere Information Server for over 12 years mainly for ETL; it's stable and capable, but cloud scalability, documentation, and community support need improvement, and better customer relationship management would enhance its overall value. |
| Technical Data Analyst at Swedish Armed Forces | 4.0 | I've used IBM InfoSphere Information Server for seven to eight years; setup was easy, but development feels cloud-focused. Metadata management lacked value for us, and while support is decent, we mainly see bug fixes, not new features. |
| Lead Software Engineer at a financial services firm with 10,001+ employees | 4.0 | I use IBM InfoSphere Information Server in retail banking primarily for its valuable DataStage administration feature, which aids in upgrades. However, the solution lacks sufficient private cloud support, prompting exploration of alternatives like IBM Cloud Data Lake and Snowflake Data Cloud. |
| Business Analyst Team Lead at Accenture | 3.5 | I have used IBM InfoSphere Information Server for five years as an integration tool. It's stable, and support is prompt, but I find it needs improved scalability and configuration options, leading to my 7/10 rating. |
| Developer at a computer software company with 1,001-5,000 employees | 3.5 | I find its integration with various technologies invaluable. While its stability is good, technical support needs improvement. I rate it a 7/10, as it's reliable but less user-friendly than alternatives. |
| Data Analytics Architect at Covenant Technology Partners LLC | 4.5 | We use this solution for enterprise data integration, valuing its Parallel Extender and scalability. It drastically reduced our ETL time. While excellent, we desire a server version and a more lightweight engine. |
| Principal Consultant at a tech services company with 201-500 employees | 4.5 | I've used this solution for seven years, appreciating its data connections, flexibility, and performance. However, I found customer service poor and technical support fair, noting room for improvement in reporting and training. |
| Architect at a tech services company with 51-200 employees | 5.0 | I value its features, reducing ETL time, and excellent support. I've encountered issues with index handling, scratch disk use, and job locks, but note no scalability problems. |
| Director of Architecture/Design at a tech company with 51-200 employees | 4.0 | No summary available |
My usual use case for IBM InfoSphere Information Server is ETL, where we take data from one source to another data warehouse solution.
The most valuable features of IBM InfoSphere Information Server that I have found over the years include it being a good, solid ETL tool. We have started working on the cloud with Cloud Pak for Data from IBM, which is now in acceleration mode, so we will move slowly from this to Cloud Pak for Data.
With the ability to handle structured and unstructured data sources, we are mostly working on structured data, but unstructured data is also in our scope, so we will explore that if the organization needs it.
As for utilizing the platform's metadata management feature, I have not worked on that feature yet, but personally, I have done that.
To evaluate the effectiveness of IBM InfoSphere Information Server's data integration capabilities, if IBM is providing all the solutions we are using, then it is definitely a helpful thing. Mostly, the other thing is that it is a big area including data governance, data lineage, data management, and metadata, but every customer is not putting that much effort and money on that. They mostly migrate the data, use it, and forget it, but slowly things are changing. I am working in Saudi Arabia, so here also data governance, data management, and those kinds of things are getting attention.
Regarding how scalable IBM InfoSphere Information Server is, I need to learn how to tune performance and scalability on the cloud. I am familiar with localized hardware, but on the cloud, I still have to do the work around it. In the beginning, we estimate the load and based on that, we put the hardware, but if there is continuous increase, I believe IBM also faces problems. Scalability needs to be improved because once the demand comes, you should be able to improve it, but for that, documentation on how to add hardware or resources to the software needs to be proper. I do not have much hands-on experience with that.
I have been working with this solution for more than 12 years.
IBM InfoSphere Information Server is generally stable, and I find it stable. The product is generally stable, but support issues come into play, and that falls under customer management. If there is a problem, then the person should get support. Unlike other tools, IBM tools do not provide much help from the internet, so additional support should be available.
Regarding how scalable IBM InfoSphere Information Server is, I need to learn how to tune performance and scalability on the cloud. I am familiar with localized hardware, but on the cloud, I still have to do the work around it. In the beginning, we estimate the load and based on that, we put the hardware, but if there is continuous increase, I believe IBM also faces problems. Scalability needs to be improved because once the demand comes, you should be able to improve it, but for that, documentation on how to add hardware or resources to the software needs to be proper. I do not have much hands-on experience with that.
IBM InfoSphere Information Server is generally stable, and I find it stable. The product is generally stable, but support issues come into play, and that falls under customer management. If there is a problem, then the person should get support. Unlike other tools, IBM tools do not provide much help from the internet, so additional support should be available.
Neutral
Before using IBM InfoSphere Information Server, I have seen Informatica ETL, which is a big contender, and I have seen Talend and open sources too. People sometimes think why they should put that much money because many customers say there are open sources available, so why should they not use that. The time and technology are changing with AI and those kinds of things coming into the picture, so technology has to take shape towards that, allowing to handle both. I am even doing my MSc in AI and ML. I know IBM is a good vendor, but if we merge things correctly with the time and technology, definitely your market share will be there.
I have participated in the initial setup and deployment of IBM InfoSphere Information Server. I have done the deployment and installation previously and currently I have to migrate ETL jobs from DB2 to Informix, so I need to find out how I can do that easily. Those kinds of challenges are all the time there once you are in the jobs.
Regarding the initial setup of IBM InfoSphere Information Server, I see that the guidelines for the installation and all in the topology to select are fair enough. The only thing is that I am not finding much on the internet for IBM products outside of IBM. I am not getting that much help, but IBM itself is providing a good knowledge base. If it is on the public network, finding the solution is easier when facing problems. There should be some help available from the community for those who face problems.
Regarding the pricing of IBM InfoSphere Information Server, I cannot comment on that much because I am not directly dealing with the price side. I know the licensing is costly, but I will not be in a right position to give you something on that.
Frankly speaking, I see a good prospect in Cloud Pak if that is one solution because it will be really great to see the data lineage, data governance, and everything in one without having to import things separately. However, I see that due to the lack of customer management and interest, I think the other partners are also getting affected. They understand that IBM is a very strong tool, but due to the local management and relationship management, I believe they are losing some customers. This is my view, so I would say you should focus on that.
Currently, IBM InfoSphere Information Server is deployed on-premises in my organization. Mostly it is on-premises only, but slowly things are changing towards pro-cloud. It will not be a public cloud, it will be an intranet kind of thing, but slowly things are changing towards that.
Over the years of working with IBM InfoSphere Information Server, I see basically the strength of the tool, capability, and load balancing, which I see is really good. I believe that the IBM team produces a reliable product. We are using even DB2 also here currently, and we are using database solution DB2, alongside Cognos. In the current organization, we have Cognos, IBM InfoSphere, and DB2 as a database, but now they are going towards Informix or something, so I see that customer management is important.
Of course, I use the data lineage feature in this solution.
Basically, regarding how data lineage has helped in understanding my data ecosystem, if you see the data lineage wise, currently, the IBM tool was not used for the data lineage. In one bank, I used another tool, I mean, there is the Informatica tool, but here Cloud Pak for Data, I still have to see that one. I understand what data lineage is, but currently, I have not worked on the complete solution.
This review reflects a customer service rating of 3 out of 5.
The ability to handle structured and unstructured data sources helps my company, but that is difficult for me to answer because other persons completed that work.
The best features for me personally in IBM InfoSphere Information Server are my plans.
We have decided to decrease the usage of metadata management because we did not see any significant advantages.
We are using the on-premises version of IBM InfoSphere Information Server, but we feel that all new development is mainly for the cloud. We receive corrections of errors, but we do not see new functionality.
I have been using IBM InfoSphere Information Server for maybe seven or eight years.
I would rate the technical support of IBM as a seven.
Positive
An installation of the solution may take less than one day to complete, but then there needs to be some tweaking afterwards to adjust.
Deploying the solution is straightforward for me.
I completed the implementation by myself.
We are about to change our platform from IBM AIX to SUSE Linux, as our whole platform is changing, so everyone should change from IBM to SUSE Linux. It would be very difficult for us to have a different operating system than everybody else.
Regarding pricing, we do not see the cost of IBM InfoSphere Information Server as it is billed to another department.
We had a team assembled to evaluate the effectiveness of IBM InfoSphere Information Server, and we looked at what was necessary for us and we looked at what was accomplished by DataStage.
I do not use the data lineage feature with IBM InfoSphere Information Server.
I have utilized the platform's metadata management to some extent.
I would rate this review an eight overall.
I use IBM InfoSphere Information Server in retail banking for transformation purposes.
IBM InfoSphere DataStage administration is something that I found to be the most valuable feature of the product. I use IBM InfoSphere DataStage administration for upgrade-related information, and I found it to be very useful.
There are certain shortcomings in the cloud side of the solution, where improvements are required. In our company, we are presently in the process of doing a PoC phase since we have the solution currently deployed on an on-premises model. My company expects to deploy the solution on a private cloud, but most of the options that we get to see are from public clouds, like AWS, Azure, and Google.
The challenge related to the solution stems from the fact that it is difficult to find private cloud support for the product.
I have been using IBM InfoSphere Information Server for two years. My company has a partnership with IBM.
Stability-wise, I rate the solution a ten out of ten.
Scalability-wise, I rate the solution a seven out of ten.
A few of the new features and some of the information are still areas of concern when compared with a tool like Informatica.
My company does have access to a dedicated IBM support team that supports us when we face issues.
My company was using Informatica before switching to IBM DataStage.
The product's initial setup is quite easy.
In my company, we are dealing with the PoC phase of the product. Currently, in my company, we don't have any timelines by which the PoC phase should be completed.
Right now, my company deals with a set of different scenarios. My company is looking into the PoC phases connected to multiple products like IBM Cloud Data Lake, IBM Cloud Pak, and Snowflake Data Cloud. Though my company looks at different products from multiple angles, nothing has been finalized yet.
I rate the overall tool an eight out of ten.

IBM InfoSphere Information Server has multiple tools in that product suite. However, we mainly use it as an integration tool.
I have been using IBM InfoSphere Information Server for approximately five years.
IBM InfoSphere Information Server is stable.
IBM InfoSphere Information Server should be more scalable. It should have the option to change the configuration to run on a single, non-multiple node, or multi-threading processing.
We have approximately 60 users using this solution in my organization.
We have contacted IBM multiple times where we find issues in a job migration. Sometimes the job gets locked out and we are not able to troubleshoot the issues. In that way, we open a ticket with IBM, and they're very prompt in fixing the problem.
The initial IBM InfoSphere Information Server is straightforward. However, You can choose what type of installation you want, such as a customized installation. There's clear-cut documentation, if we follow them then we are fine. The installation has not given us issues.
The implementation of the IBM InfoSphere Information Server can be done in-house. We did not need a consultant.
We have a team that does the maintenance and support for the solution. They will monitor the application for any failures, et cetera. The amount of people needed depends on the size of the application.
The licensing cost of IBM InfoSphere Information Server depends on how many users there are.
I rate IBM InfoSphere Information Server a seven out of ten.
The integration with different technologies is the most valuable feature.
Their technical support needs improvement.
I have been using this solution for around six months.
The stability is good.
I would rate it a seven out of ten. It's a reliable solution.
Not a ten because it's not as user friendly as other solutions.
We use this solution for enterprise-level Data Integration.
This solution has reduced the time it takes for ETL. We took an existing Teradata ETL application from three days to eight minutes.
The most valuable feature of this solution is the Parallel Extender.
We would like to have a server version of this solution.
This solution would benefit from the engine being made more lightweight.
This solution is extremely flexible and scalable.
No improvements to the organization have been noticed so far.
I've used it over seven years in various versions.
No issues encountered.
No issues encountered.
No issues encountered.
It's poor.
Technical Support:It's fair.
It was medium complexity as there are many options available, and you need to know the license limitations.
We used an IBM partner who were good.
Look at TCO not just the sticker price. Don't run on Unix if the primary database is a SQL Server.
No other options were evaluated.
One of the selling points of the IBM InfoSphere data management suite is that its modules share the “XMETA repository” (a common metadata repository). This is useful in supporting two key data governance functions: data lineage reporting and the linking of metadata assets to business term definitions. Its 2005 acquisition of Ascential Software Corporation provided IBM with most of the modules it would later use in InfoSphere. IBM has invested considerable effort in integrating those modules with data management products acquired elsewhere as well as ones they developed. Their integration has been fairly successful, but in some cases they were forced to design “bridges” between modules which have separate repositories (e.g., Metadata Workbench and Information Analyzer). Therefore, it is important to understand the structure of InfoSphere’s various repositories when designing your data management platform.
The following list of modules is an example of only one of the possible ways to combine IBM products to support a data governance program.
INFOSPHERE METADATA WORKBENCH
Metadata Workbench can be used by administrators to maintain the XMETA repository. In addition, it also functions as the user interface for displaying data lineage (after the repository is populated with metadata assets). With their release of Infosphere 8.7, IBM introduced Metadata Asset Manager (IMAM), a new suite function. This was a considerable improvement over the original import/export functions. After some initial implementation difficulties, IMAM has proved useful in implementation of the Metadata SDLC. Metadata Workbench also allows the linking of metadata assets (e.g., column names) to business term definitions (see Business Glossary).
INFOSPHERE BUSINESS GLOSSARY
Business Glossary uses the XMETA repository. Note that there are other IBM glossary products (particularly in the Rational suite) that are not integrated with the InfoSphere product. It is also important to keep in mind that the repository is empty when the “Information Server” (the InfoSphere platform) is built. The glossary is structured in a user-defined searchable hierarchy. A formal workflow can be constructed within the product to secure the maintenance of both hierarchies and the definitions to authorized users. Although Information Server is LDAP compliant, some modules, especially Business Glossary, may require additional user setup to implement some user roles.
BUSINESS GLOSSARY ANYWHERE
Business Glossary Anywhere is a Windows workstation client that first requires the end user to supply an Information Server user ID when starting the client on the workstation. Using key sequences or a simple right mouse click, the user invokes the client to begin a search of the Business Glossary by entering criteria into a search text box or by selecting a word or phrase from a document displayed on the workstation. Almost any document type can be employed (HTML, text, BI reports and dashboards, etc.).
INFOSPHERE DATA ARCHITECT
Data Architect is IBM’s data modeling tool. Models at all levels (conceptual, logical, or physical) contain metadata (and, indeed, are themselves metadata assets) that are stored in the XMETA repository. Whenever a user’s SDLC calls for change control at the model level, the XMETA repository will reflect updates to the production models. If change control is handled in the database directly, Data Architect allows the user to reverse engineer tables to update the XMETA repository.
INFOSPHERE DATASTAGE
Datastage is the IBM ETL system. All Datastage jobs contain metadata assets that will be stored in the XMETA repository. If Datastage jobs are used to transport data from an OLTP database to a data warehouse, then that transport will appear in lineage reports. In an Inmon architecture, then Datastage should also be used to transport the data from the enterprise data warehouse to the data marts. If external data is brought on board to the OLTP using Datastage (possibly as a web service call), the lineage reporting will also include that transport.
INFOSPHERE QUALITYSTAGE
Qualitystage’s purpose is to perform data cleansing operations. As the functionality of Qualitystage jobs are built on the Datastage model, the XMETA repository also serves as its metadata storage. An optional module, it should be implemented either by a data governance directive or to serve as part of an MDM program to be of use.
INFOSPHERE INFORMATION ANALYZER
Used for data profiling, Information Analyzer does not use XMETA. Instead, Information Analyzer stores information in “IADB”, its own repository. It enables information from IADB to be imported into Xmeta. Like Qualitystage, Information Analyzer is optional, and, ideally, it also requires either a data governance directive or to serve as part of an MDM program.
COGNOS
Cognos is IBM’s business intelligence tool. We can bridge between its repository and the InfoSphere Business Glossary, allowing it to complete the lineage reporting from the database through the Cognos abstraction layer, and to the report asset.
Reporting capabilities from data management products have been traditionally dreadful and InfoSphere is really no exception. While recent versions have made improvements, especially in data lineage reporting, there is vast room for improvement. I have suggested to IBM that I would like to see the schemas published for both XMETA and IADB. In an organization that also owns (or is buying) Cognos, I would further suggest that it should be possible to define a data management datamart which would leave the actual report design (or other BI artifact) to the discretion of the user’s BI development staff. This would relieve IBM from trying to improve the reporting capability and get back to integrating the products more fully.