The April 2024 release of ℠ Administrator includes the following new features and enhancements.
New UI experience
The Administrator user interface has a new look and feel that presents the features you'll use in greater clarity.
Advanced clusters
Advanced clusters include the following new features and enhancements:
•The Advanced Clusters page includes performance and visual enhancements.
•On the Advanced Clusters page, sorting has been improved and you can filter the advanced configurations.
•When you create an advanced configuration, the Validate button is enabled for Google Cloud clusters and self-service clusters. It validates whether the configuration contains the necessary information and is in the correct format.
Note: The validation process doesn't validate whether cloud resources have been configured correctly, such as whether cloud roles have all the necessary permissions.
For more information, see Advanced Clusters.
Flat file connections
When you create a flat file connection, you can use the date format MM/dd/yyyy HH24:mm:ss.
Source control
This release includes the following enhancements to source control:
Project-level repositories
You can enable the option to configure Git repositories at the project level. Using different repository branches for your projects can enable parallel development and collaboration across teams in the organization.
When users don't specify a project-level repository, the global repository that you set up in Administrator is used.
Cloud-hosted Bitbucket repositories
You can use a cloud-hosted Atlassian Bitbucket repository for source-controlled Data Integration assets.
For more information, see Organization Administration.
Platform REST API
This release includes the following enhancements to the REST API:
Source control
You can get repository connection details such as the repository connection ID for a given project ID or project name using the repositoryConnection resource.
Additional object specifications in import API resource
In an import POST request, you can use key-value pairs in the additionalProviderFlags field to include additional object specifications such as in-out parameter values and sequence generator values.
For more information, see REST API Reference.
IPU metering for Cloud Data Integration for PowerCenter (CDI-PC)
You can view metering information for tasks that you perform in your organization and sub-organizations on the Metering page in Administrator.
You can view and download metering consumption data from the Cloud Data Integration for PowerCenter metering page. The metering page contains details including the date when the task was run, organization details, environment details, IPU per unit, and the number of IPUs consumed.
For more information about metering, see Organization Administration.
Detailed metering report for PowerCenter Modernization
You can view and download detailed metering usage data for assessment and conversion jobs run from Cloud Data Integration for PowerCenter (CDI-PC). The metering page includes details such as the date and time when the jobs within the organization were run, organization ID, job details, and the number of objects processed during assessment or conversion.
For more information about metering, see Organization Administration.
Overriding properties in the platform.yaml file
You can use a custom YAML file to override the property values in the platform.yaml file.
The platform.yaml file is a configuration file that the Process Server uses to get the configuration details related to Application Integration and communicate with the Secure Agent services.
You can override the property values in the platform.yaml file available on the Secure Agent by using a custom user-platform.yaml. To override the values, create a copy of the platform.yaml file with the required properties and their custom values, name the file as user-platform.yaml, and save it in the following directory:
When the Process Server is up and running, if a property is specified in the user-platform.yaml file, the Process Server uses that specific value. Otherwise, the Process Server uses the values defined in the platform.yaml file.
When the Secure Agent is upgraded to a new version, the properties in the user-platform.yaml file are unchanged.
For more information about configuring custom values for properties in the platform.yaml file, see Secure Agent Services.
Serverless runtime environment
You can use serverless runtime environments configured in Azure Native ISV Services.
For a list of connectors that can use Azure serverless runtime environments, see Runtime environments.
OS Profiles
You can use operating system (OS) profiles to impersonate another user to run tasks with operating system users who differ from the Secure Agent user.
For more information, see "Data Integration Server Properties" in Secure Agent Services.