What's new in IBM Optim Archive
See what new features and improvements are available in the latest release of IBM® Optim Archive.
What's new in Version 2.0.0
IBM Optim Archive Version 2.0.0 contains a number of new and updated capabilities.
Explore the key capabilities introduced in this release of IBM Optim Archive:
- Connect to more types of data sources and targets
- Switch to your preferred language across the IBM Optim Archive interface
- Restore flow configurations by importing JSON files
- Create flows faster with reusable node templates
- Edit nodes directly in your IBM Optim flows
- Consolidate multiple database sources in a single access definition node
- Export data to multiple databases in a single flow
- Access your existing InfoSphere Optim archives without migration
- Reuse archive and extract files across workflows to maintain current datasets
- Control how long archived data is available by defining retention policies
- Query archived data directly by using SQL, without restoring to production
- Permanently remove archived data from production databases
- Filter archive files by type, source, creator, and date
- Rerun archive and extract jobs without recreating configurations
- Test emerging database connections before production release
- Insert constant values into database columns during data transformation
Connect to more types of data sources and targets
- AlloyDB for PostgreSQL
- Amazon RDS for PostgreSQL
- Amazon RDS for MySQL
- Amazon RDS for Oracle
- Amazon Aurora PostgreSQL
- Amazon Aurora MySQL
- Apache Cassandra
- DataStax Enterprise
- IBM Cloud® Databases for PostgreSQL
- IBM Db2® on Cloud
- IBM Db2 for IBM i
- IBM Db2 Warehouse
- MariaDB
- Microsoft Azure PostgreSQL
- Microsoft Azure SQL
For a full list of supported data sources, see Supported data sources and targets.
Switch to your preferred language across the IBM Optim Archive interface
- Brazilian Portuguese
- Chinese (Simplified)
- Chinese (Traditional)
- Esperanto
- French
- German
- Italian
- Japanese
- Korean
- Polish
- Spanish
- Swedish
Set your preferred language in your browser settings, and IBM Optim Archive automatically displays all menus, labels, messages, and help text in that language. Your language choice persists across sessions, so you only need to set it once.
Restore flow configurations by importing JSON files
You can now import previously exported flow definitions directly from JSON files into the IBM Optim Archive flow canvas. This feature eliminates the need to manually recreate flows. Simply select a JSON file, review the flow details, and choose whether to open it in a new canvas or replace your current flow. The system automatically validates the file structure, verifies connection compatibility, and preserves all node relationships and connections during import.
For details, see Importing and exporting a flow.
Create flows faster with reusable node templates
You can now save any configured node as a reusable template and instantly create new nodes from your template library. Instead of manually reconfiguring access definitions, subset rules, or masking policies for each flow, drag a template onto your canvas and create a fully configured node in seconds. Save your newly configured nodes as templates to give yourself a head start the next time you need to create similar nodes. This eliminates repetitive configuration work, ensures consistency across your flows, and helps you to standardize data privacy policies and access controls across projects.
For details, see Creating and working with template nodes.
Edit nodes directly in your IBM Optim flows
You can now edit existing nodes in your flows without having to delete and recreate them. Simply right-click any access definition, subset, mask, or target database node and select Edit to modify table mappings, subset conditions, masking policies, or insert definitions. The system automatically validates your changes against access definition constraints and filters out any incompatible elements, displaying clear warnings so you can resolve issues before running the flow.
For details, see Editing a node in a flow.
Consolidate multiple database sources in a single access definition node
You can now connect to multiple database sources within a single access definition node, eliminating the need to create separate flows for each database. When you add multiple sources, the system automatically identifies and disables related tables to prevent circular dependencies, reducing configuration errors. If you remove an access definition node, all associated source connections are automatically cleaned up, maintaining your flow's integrity. This streamlines complex data workflows while remaining compatible with your existing single-source configurations.
For details, see Creating an access definition.
Export data to multiple databases in a single flow
You can now distribute your data to multiple database destinations in a single flow. When you create a target node and select a database as the export option, you can add multiple target databases instead of being limited to just one. The improved flow builder interface shows you all source and destination mappings on the screen and displays all target connections in a flow diagram.
For details, see Defining a target.
Access your existing InfoSphere Optim archives without migration
You can now browse and restore data from archives created in the IBM InfoSphere® Optim product directly within the new IBM Optim platform. This eliminates the need to re-archive years of historical data when adopting the modern platform. Simply register your existing archives using the same storage location, and you can query and restore data using the same workflows as newly created archives.
For details, see Registering InfoSphere Optim archives.
Reuse archive and extract files across workflows to maintain current datasets
You can now create archive and extract files that multiple workflows can write to, ensuring your data stays current rather than creating separate files for each workflow run. When you configure a new archive or extract file, enable the allow overwrite option to let subsequent workflows update the same file location with fresh data. Later, when building additional workflows, you can select any file marked for overwriting and reuse both its configuration settings and its file location. This approach helps you maintain a single, up-to-date dataset instead of managing multiple snapshot files, while also streamlining workflow creation by eliminating redundant file configuration.
For details, see Defining a target.
Control how long archived data is available by defining retention policies
You can now define retention policies that help you to manage the lifecycle of your archived data. Set either a specific expiration date or a retention period based on when the archive was created. Once a retention policy expires, the archive remains accessible, but you can no longer modify the policy. This feature helps you to meet regulatory, legal, and operational requirements by providing clear visibility into retention periods and expiration dates for all archived data.
For details, see Exploring archives.
Query archived data directly by using SQL, without restoring to production
You can now explore and analyze archived data using familiar SQL queries without restoring the archive to your production database. Write custom SQL queries in an integrated editor with syntax highlighting to filter, validate, and analyze data at the collection, archive file, or table level. Results appear instantly in a paginated view, letting you quickly find the information you need while keeping your archived data secure and your production systems free from unnecessary load.
For details, see Exploring archives.
Permanently remove archived data from production databases
You can now delete archived data from your production database directly from the Archives page with a single action. After successfully archiving data, select the delete option from any archive's menu to permanently remove that data from production. This strategy reduces storage costs and helps you to comply with data retention policies. The system automatically creates a deletion workflow based on your original archive configuration, and you can choose to delete either with validation for safer execution or without validation for faster processing.
For details, see Exploring archives.
Filter archive files by type, source, creator, and date
You can now quickly locate specific archive files by applying multiple filters simultaneously on the Archive files page. Filter by file type, source, source type, creator, or creation date to narrow down large archive collections. Active filters can be reviewed, modified, or cleared at any time, and work alongside existing search and sorting features to help you find the archives you need faster.
For details, see Exploring archives.
Rerun archive and extract jobs without recreating configurations
You can now rerun completed archive and extract jobs directly from the Jobs page when the target configuration allows overwriting. Instead of creating a new job definition, simply select the Run action from the job actions menu to execute the same configuration again. This streamlines repetitive operations like testing with updated source data, validation activities, or operational reruns by eliminating the need to recreate job configurations each time.
For details, see Viewing job details, logs, and process reports.
Test emerging database connections before production release
You can now connect to new data sources in IBM Optim Archive before they're fully validated for production use. When you enable tech preview connections, you gain early access to emerging database integrations with clear indicators showing their preview status. This lets you evaluate and test new connectivity options in your development environment while IBM completes end-to-end validation.
For details, see Exploring and defining connections.
Insert constant values into database columns during data transformation
You can now insert fixed values directly into target database columns without copying from source data. When transforming data in IBM Optim Archive pipelines, you can set constant values like default flags, status indicators, or standard text across all rows. This simplifies data migration by eliminating the need to prepopulate source columns with repetitive values.
For details, see Literal column mapping (API).
Literal column name (API feature)