New function added in Version 12.0 modification packs and fix packs

Discovery connector request nodes

The following additional IBM App Connect Enterprise discovery connector request nodes have been provided:

Google Analytics Request node

Use the Google Analytics Request node to connect to Google Analytics and issue requests to perform actions on objects such as custom data sources, custom metrics, filters, account user links, and goals.

Google Chat Request node

Use the Google Chat Request node to connect to Google Chat and issue requests to perform actions on objects such as members, messages, and spaces.

Google Groups Request node

Use the Google Groups Request node to connect to Google Groups and issue requests to perform actions on objects such as groups, group members, and group aliases.

Google Tasks Request node

Use the Google Tasks Request node node to connect to Google Tasks and issue requests to perform actions on objects such as tasks and task lists.

IBM FileNet Content Manager Request node

Use the IBM FileNet Content Manager Request node to connect to IBM FileNet Content Manager and issue requests to perform actions on objects such as documents and folders.

IBM Food Trust Request node

Use the IBM Food Trust Request node to connect to IBM Food Trust and issue requests to perform actions on objects such as certificates, basic party registrations, EPCIS aggregation events, EPCIS object events, or purchase orders.

IBM Sterling Inventory Visibility Request node

Use the IBM Sterling Inventory Visibility Request node to connect to IBM Sterling Inventory Visibility and issue requests to perform actions on objects such as demands, distribution groups, jobs, safety stocks, and supplies.

IBM Watson Discovery Request node

Use the IBM Watson Discovery Request node to connect to IBM Watson Discovery and issue requests to create, retrieve, update, delete, or add documents.

IBM Weather Company Data Limited Edition Request node

Use the IBM Weather Company Data Limited Edition Request node to connect to IBM Weather Company Data Limited Edition and issue requests to perform actions on objects such as current conditions, forecasts, and historical observations.

LDAP Request node

Use the LDAP Request node to connect to LDAP and issue requests to create, retrieve, update, or delete objects such as devices, entries, organization units, persons, and rooms.

Salesforce Commerce Cloud Digital Data Request node

Use the Salesforce Commerce Cloud Digital Data Request node to connect to Salesforce Commerce Cloud Digital Data and issue requests to perform actions on objects such as campaigns, catalogs, customers, inventory lists, products, site promotions, and stores.

Yapily Request node

Use the Yapily Request node to connect to Yapily and issue requests to perform actions on objects such as account statements, applications, authorization requests, institutions, payments, and transactions.

Discovery connector input nodes

The following additional IBM App Connect Enterprise discovery connector input nodes have been provided:

GitLab Input node

Use the GitLab Input node to monitor and receive input from GitLab.

LDAP Input node

Use the LDAP Input node node to monitor and receive input from LDAP.

Microsoft Entra ID Input node

Use the Microsoft Entra ID Input node to monitor and receive input from Microsoft Entra ID.

Salesforce Commerce Cloud Digital Data Input

Use the Salesforce Commerce Cloud Digital Data Input node to monitor and receive input from Salesforce Commerce Cloud Digital Data.

HTTP proxy support for discovery connector nodes

HTTP proxy support for discovery connector nodes

You can use an HTTP Proxy policy to specify an HTTP proxy to be used for connections between the following discovery connector nodes and their endpoints:

• Amazon S3 Request node
• Microsoft Azure Blob Storage Request node
• Microsoft Entra ID Input node
• Microsoft Entra ID Request node

For more information, see Configuring an HTTP proxy for discovery connector nodes.

HTTPRequest node error-handling enhancements

Error handling on the HTTPRequest node

The error-handling options on the HTTPRequest node have been extended to include the option to throw an exception when a non-success response is returned from the HTTP server.

For more information, see HTTPRequest node.

mqsivault command enhancements

Vault options on the mqsivault command

You can choose to prevent the display and export of credentials from a vault by specifying the --vault-options no-export parameter on the mqsivault command.

For more information, see mqsivault command.

OAuth support for Email nodes

OAuth support for EmailInput and EmailOutput nodes

Support for the Open Authorization (OAuth) standard has been provided for EmailInput and EmailOutput nodes.

For more information, see Using OAuth to authenticate with an email server.

Log node and activity log enhancements

Log node

Use the Log node to define an entry to be added to the activity log. You can customize activity log entries by adding one or more Log nodes to a flow, with a variety of log levels, custom messages, and custom fields.

For more information, see Adding entries to the activity log by using a Log node.

Activity log enhancements

You can configure the destination of activity log output and apply filtering to the entries that are written, by deploying an Activity Log policy or by setting properties in the ActivityLog section of the server.conf.yaml file.

For more information, see Activity Log policy (ActivityLog) and Configuring activity log output.

HTTP Request policy

HTTP Request policy for HTTPRequest and HTTPAsyncRequest nodes

You can use an HTTP Request policy to define the security operations that are completed by an HTTPRequest or HTTPAsyncRequest node in a message flow. Use an HTTP Request policy when you want to configure the connection to use basic authentication or API key credentials provided by a credentials provider such as the App Connect Enterprise vault or the mqsisetdbparms command.

For more information, see HTTP Request policy.

Retrieve BAR files using the web user interface

Support for retrieving BAR files by using the web user interface

Support has been provided for retrieving BAR files for deployed applications by using the App Connect Enterprise web user interface.

For more information, see Retrieving a deployed BAR file.

MQTTSubscribe node enhancement

Support for subscribing to multiple topics from an MQTTSubscribe node

The MQTTSubscribe node has been extended to include support for subscribing to multiple topics from a single MQTTSubscribe node.

For more information, see MQTTSubscribe node.

Discovery connector request nodes

The following additional IBM App Connect Enterprise discovery connector request nodes have been provided:

Amazon DynamoDB Request node

Use the Amazon DynamoDB Request node to connect to Amazon DynamoDB and issue requests to perform actions on objects such as backups, items, regions, tables, and tags.

Amazon SNS Request node

Use the Amazon SNS Request node to connect to Amazon SNS and issue requests to perform actions on objects such as subscriptions, tags, and topics.

BambooHR Request node

Use the BambooHR Request node to connect to BambooHR and issue requests to perform actions on objects such as employees, employee dependents, employee files, benefit deduction types, custom reports, list fields, and time tracking records.

CMIS Request node

Use the CMIS Request node to connect to CMIS and issue requests to perform actions on objects such as documents, folders, and repositories.

Expensify Request node

Use the Expensify Request node to connect to Expensify and issue requests to perform actions on objects such as receipts, expense reports, and vendor invoices.

GitLab Request node

Use the GitLab Request node to connect to GitLab and issue requests to perform actions on objects such as epics, issues, branches, milestones, pipelines, commits, and merge requests.

Google Cloud BigQuery Request node

Use the Google Cloud BigQuery Request node to connect to Google Cloud BigQuery and issue requests to perform actions on objects such as datasets, jobs, tables, and views.

Greenhouse Request node

Use the Greenhouse Request node to connect to Greenhouse and issue requests to perform actions on objects such as applications, candidates, jobs, job posts, job stages, prospects, and scheduled interviews.

HubSpot CRM Request node

Use the HubSpot CRM Request node to connect to HubSpot CRM and issue requests to perform actions on objects such as companies, contacts, deals, line items, owners, and products.

HubSpot Marketing Request node

Use the HubSpot Marketing Request node to connect to HubSpot Marketing and issue requests to perform actions on objects such as contacts, contact lists, email campaigns, and marketing events.

IBM Cloud Object Storage S3 Request node

Use the IBM Cloud Object Storage S3 Request node to connect to IBM Cloud Object Storage S3 and issue requests to perform actions on objects such as CORS, buckets, and objects.

IBM Supply Chain Intelligence Suite Request node

Use the IBM Supply Chain Intelligence Suite Request node to connect to IBM Supply Chain Intelligence Suite and issue requests to perform actions on objects such as catalogs, demand plans, inventories, orders, and products.

Insightly Request node

Use the Insightly Request node to connect to Insightly and issue requests to perform actions on objects such as contacts, events, leads, opportunities, or tasks.

Microsoft Active Directory Request node

Use the Microsoft Active Directory Request node to connect to Microsoft Active Directory and issue requests to perform actions on objects such as computers, contacts, entries, groups, organizational units, and users.

Microsoft OneNote Request node

Use the Microsoft OneNote Request node to connect to Microsoft OneNote and issue requests to perform actions on objects such as pages, notebooks, sections, and section groups.

Microsoft Viva Engage Request node

Use the Microsoft Viva Engage Request node to connect to Microsoft Viva Engage and issue requests to perform actions on objects such as files, groups, messages, topics, and users.

Square Request node

Use the Square Request node to connect to Square and issue requests to perform actions on objects such as customers, invoices, orders, and payments.

SurveyMonkey Request node

Use the SurveyMonkey Request node to connect to SurveyMonkey and issue requests to perform actions on objects such as collectors, contact lists, and surveys.

Wufoo Request node

Use the Wufoo Request node to connect to Wufoo and issue requests to perform actions on objects such as forms, form entries, reports, and users.

Discovery connector input nodes

The following additional IBM App Connect Enterprise discovery connector input nodes have been provided:

CMIS Input node

Use the CMIS Input node to monitor and receive input from CMIS.

Coupa Input node

Use the Coupa Input node to monitor and receive input from Coupa.

Insightly Input node

Use the Insightly Input node to monitor and receive input from Insightly.

Microsoft Active Directory Input node

Use the Microsoft Active Directory Input node to monitor and receive input from Microsoft Active Directory.

Microsoft Viva Engage Input node

Use the Microsoft Viva Engage Input node to monitor and receive input from Microsoft Viva Engage.

Oracle Human Capital Management Input node

Use the Oracle Human Capital Management Input node to monitor and receive input from Oracle Human Capital Management.

SurveyMonkey Input node

Use the SurveyMonkey Input node to monitor and receive input from SurveyMonkey.

Wufoo Input node

Use the Wufoo Input node to monitor and receive input from Wufoo.

Mapping support for discovery connector request nodes

Support for mapping input data on discovery connector request nodes

You can use mapping during connector discovery to build an input message, by configuring a map inputs table on the request node. You configure the request properties and the payload fields, which you can populate either by setting static values or by using a JSONata expression to select input data from any of the available inputs.

For more information, see Configuring mapping for discovery connector request nodes.

Change Data Capture node

Change Data Capture node

You can use the Change Data Capture node to capture all the changed data from a database into IBM App Connect Enterprise. You can use the node for extracting or subscribing to changes that occur on a particular database server, without incurring an extra cost in each transaction.

For more information, see Change Data Capture node.

ibmint specify jre command

ibmint specify jre command

You can use the ibmint specify jre command to specify which Java Runtime Environment (JRE) to use for a specified integration server.

For more information, see ibmint specify jre command.

ibmint display supported-jre-versions command

ibmint display supported-jre-versions command

You can use the ibmint display supported-jre-versions command to display the Java versions that are supported for your installation of IBM App Connect Enterprise.

For more information, see ibmint display supported-jre-versions command.

Support for PostgreSQL

Support for PostgreSQL databases on Windows and Linux® x86-64 platforms

IBM App Connect Enterprise provides DataDirect ODBC drivers for interfacing with PostgreSQL databases on Windows and Linux x86-64 platforms.

For more information, see Connecting to a database from Windows systems and Connecting to a database from Linux and UNIX systems by using the IBM Integration ODBC Database Extender.

Importing and exporting credentials

Support for importing or exporting credentials to or from a vault

The mqsivault command has been extended to include --import and --export parameters, which you can use to import and export credentials to or from an IBM App Connect Enterprise vault. You can use the --import parameter to import a .zip archive file and extract the contents into an existing vault. You can use the --export parameter to copy the contents of a vault into a .zip archive file.

For more information, see mqsivault command.

Toolkit enhancements

Restarting an independent integration server from the Toolkit

You can use a menu option in the IBM App Connect Enterprise Toolkit to restart a local, independent integration server. For more information, see Restarting a local, independent integration server by using the Toolkit.

Opening your workspace location in the Toolkit

You can open your workspace location from the IBM App Connect Enterprise Toolkit, either by clicking an icon in the taskbar or by selecting an option in the File menu. For more information, see Opening the workspace location in the IBM App Connect Enterprise Toolkit.

Filtering policy types in the policy editor

You can filter the list of policy types displayed in the policy editor by entering text in the Policy Types field. For more information, see Creating policies with the IBM App Connect Enterprise Toolkit.

Enhanced support for OpenTelemetry trace

Support for OpenTelemetry trace on AIX® and Linux on POWER® Systems - Little Endian

Support for OpenTelemetry trace has been extended to include integration servers on AIX and Linux on POWER Systems - Little Endian platforms, which is in addition to the existing support for integration servers on the Linux x86-64, Linux zSeries, and Windows platforms.

For more information, see Configuring OpenTelemetry trace for an integration server.

Discovery connector request nodes

The following additional IBM App Connect Enterprise discovery connector request nodes have been provided:

Amazon EventBridge Request node

Use the Amazon EventBridge Request node to connect to Amazon EventBridge and issue requests to send events or to create, retrieve, or delete event buses.

Amazon RDS Request node

Use the Amazon RDS Request node to connect to Amazon RDS and issue requests to perform actions on objects such as database clusters, database instances, database snapshots, exports, and tags.

Amazon SES Request node

Use the Amazon SES Request node to connect to Amazon SES and issue requests to perform actions on objects such as contacts, contact lists, configuration sets, emails, email identities, and email templates.

DocuSign Request node

Use the DocuSign Request node to connect to DocuSign and issue requests to create, retrieve, update, or delete objects such as documents, attachments, envelopes, and recipients.

Google Contacts Request node

Use the Google Contacts Request node to connect to Google Contacts and issue requests to perform actions on objects such as contacts and contact groups.

Google Sheets Request node

Use the Google Sheets Request node to connect to Google Sheets and issue requests to create or retrieve objects such as spreadsheets, worksheets, and rows.

Google Translate Request node

Use the Google Translate Request node to connect to Google Translate and issue requests to detect languages, retrieve locations, translate text, or translate documents.

IBM Engineering Workflow Management Request node

Use the IBM Engineering Workflow Management Request node to connect to IBM Engineering Workflow Management and issue requests to perform actions on objects such as attachments, project areas, URI resolvers, and work items.

Microsoft Dynamics 365 for Finance and Operations Request node

Use the Microsoft Dynamics 365 for Finance and Operations Request node to connect to Microsoft Dynamics 365 for Finance and Operations and issue requests to create, retrieve, update, or delete objects such as applicants, customers, employees, operations, projects, prospects, sales agreements, user groups, and vendors.

Microsoft Power BI Request node

Use the Microsoft Power BI Request node to connect to Microsoft Power BI and issue requests to perform actions on objects such as datasets, gateway data sources, goals, push datasets, and workspaces.

Microsoft To Do Request node

Use the Microsoft To Do Request node to connect to Microsoft To Do and issue requests to perform actions on objects such as lists, tasks, checklist items, or file attachments.

Salesforce Account Engagement Request node

Use the Salesforce Account Engagement Request node to connect to Salesforce Account Engagement and issue requests to perform actions on objects such as prospects, users, and visitors.

SAP SuccessFactors Request node

Use the SAP SuccessFactors Request node to connect to SAP SuccessFactors and issue requests to perform actions on objects such as job applications, job application interviews, job requisitions, candidates, and onboarding candidate information.

Shopify Request node

Use the Shopify Request node to connect to Shopify and issue requests to perform actions on objects such as customers, inventory items, orders, products, and transactions.

Twilio Request node

Use the Twilio Request node to connect to Twilio and issue requests to perform actions on objects such as calls, incoming phone numbers, messages, and message services.

Discovery connector input nodes

The following additional IBM App Connect Enterprise discovery connector input nodes have been provided:

Asana Input node

Use the Asana Input node to monitor and receive input from Asana.

Google Calendar Input node

Use the Google Calendar Input node to monitor and receive input from Google Calendar.

Google Sheets Input node

Use the Google Sheets Input node to monitor and receive input from Google Sheets.

IBM Engineering Workflow Management Input node

Use the IBM Engineering Workflow Management Input node to monitor and receive input from IBM Engineering Workflow Management.

MailChimp Input node

Use the MailChimp Input node to monitor and receive input from MailChimp.

Microsoft Exchange Input node

Use the Microsoft Exchange Input node to monitor and receive input from Microsoft Exchange.

Shopify Input node

Use the Shopify Input node to monitor and receive input from Shopify.

Scheduler node

Scheduler node

You can use a Scheduler node to configure a message flow to run at specified intervals or at set times on specified days.

For more information, see Scheduler node.

Support for configuring a vault to be used by any integration server

External directory vault

An external directory vault is an App Connect Enterprise vault that can be used by any integration server, and can be accessed concurrently by any number of integration servers. The external directory vault is created in a directory that is external to the integration server, rather than the integration server's work directory. You choose the location in the file system in which to create the vault, and then configure each integration server to use it by specifying its unique location.

For more information, see Configuring an IBM App Connect Enterprise vault and Configuring an external directory vault.

Enhanced support for viewing, retrieving, and importing deployed resources

Support for viewing and retrieving compiled message flows (.cmf)

You can now view and retrieve .cmf files into the IBM App Connect Enterprise Toolkit. The .cmf files are automatically converted into .msgflow files when you import them.

For more information, see Viewing the active flow layout of a deployed message flow in the IBM App Connect Enterprise Toolkit.

Support for viewing and retrieving migrated message flows

You can now view and retrieve message flows that have been migrated from previous releases into the IBM App Connect Enterprise Toolkit. The migrated message flows are automatically converted into .msgflow files when you import them.

For more information, see Viewing the active flow layout of a deployed message flow in the IBM App Connect Enterprise Toolkit.

Support for retrieving deployed BAR files

Support has been added for retrieving a BAR file from a deployed application. In a previous release of IBM App Connect Enterprise, support was provided for retrieving resources from within a deployed BAR file. In V12.0.9.0, this support has been extended to enable you to retrieve the entire BAR file so that you can redeploy it to a different integration server.

For more information, see Retrieving a deployed BAR file.

Support for retrieving Java resources used by message flows

Support has been extended for retrieving deployed message flows that use Java. If the resources that you retrieve include a message flow that uses Java, such as a Mapping, Compute, or JavaCompute node, the .jar file that was compiled when the message flow was deployed is imported and added to the application containing the message flow. This enables you to rebuild the application in the IBM App Connect Enterprise Toolkit and deploy it to an integration server.

For more information, see Retrieving and importing deployed resources into your workspace.

Support for importing policies automatically

Support has been extended for retrieving deployed message flows that reference policies. The Retrieve and Import wizard automatically detects which deployed policy projects are referenced by the application, and they are selected in the wizard. When the wizard finishes, the policy projects are imported into the workspace. This enables you to import policies that were migrated from configurable services that were in a previous release of App Connect Enterprise.

For more information, see Retrieving and importing deployed resources into your workspace.

Support for accessing credentials from user Java code

Accessing credentials from user Java code

You can access credentials from user Java code by editing the Java Compute Node class in a JavaCompute node.

For more information, see Accessing credentials from user Java code.

Discovery connector request nodes

The following additional IBM App Connect Enterprise discovery connector request nodes have been provided:

Amazon Kinesis Request node

Use the Amazon Kinesis Request node to connect to Amazon Kinesis and issue requests to perform actions on objects such as applications, data streams, data stream records, delivery streams, shards, and tags.

Amazon SQS Request node

Use the Amazon SQS Request node to connect to Amazon SQS and issue requests to perform actions on objects such as messages, queues, and tags.

Box Request node

Use the Box Request node to connect to Box and issue requests create, retrieve, update, and delete objects such as files, folders, bookmarks, and comments.

Calendly Request node

Use the Calendly Request node to connect to Calendly and issue requests to create, retrieve, and update objects such as expense reports, exchange rates, and invoices.

Eventbrite Request node

Use the Eventbrite Request node to connect to Eventbrite and issue requests to create, retrieve, update, or delete objects such as events, attendees, contact lists, organizers, and orders.

Google Calendar Request node

Use the Google Calendar Request node to connect to Google Calendar and issue requests to perform actions on objects such as calendars, calendar sharing, and events.

Jenkins Request node

Use the Jenkins Request node to connect to Jenkins and issue requests to perform actions on objects such as builds and projects.

MailChimp Request node

Use the MailChimp Request node to connect to MailChimp and issue requests to create, retrieve, or delete objects such as campaigns, campaign folders, campaign reports, files, folders, and interests.

Microsoft Dynamics 365 for Sales Request node

Use the Microsoft Dynamics 365 for Sales Request node to connect to Microsoft Dynamics 365 for Sales and issue requests to create, retrieve, update, or delete accounts, contacts, invoices, leads, orders, and products.

Microsoft Entra ID Request node

Use the Microsoft Entra ID Request node to connect to Microsoft Entra ID and issue requests to create, retrieve, update, or delete objects such as devices, groups, and users.

Microsoft Excel Online Request node

Use the Microsoft Excel Online Request node to connect to Microsoft Excel Online and issue requests to perform actions on objects such as tables, rows, columns, ranges, workbooks, and worksheets.

Microsoft Exchange Request node

Use the Microsoft Exchange Request node to connect to Microsoft Exchange and issue requests to perform actions on objects such as attachments, calendars, contacts, conversations, emails, groups, mail folders, organizations, and users.

Microsoft OneDrive for Business Request node

Use the Microsoft OneDrive for Business Request node to connect to Microsoft OneDrive for Business and issue requests to perform actions on objects such as drives, files, folders, folder items, permissions, shared links, and users.

Microsoft SharePoint Request node

Use the Microsoft SharePoint Request node to connect to Microsoft SharePoint and issue requests to perform actions on objects such as files, folders, folder items, lists, list items, list item attachments, sites, and users.

Microsoft Teams Request node

Use the Microsoft Teams Request node to connect to Microsoft Teams and issue requests to perform actions on objects such as channels, chats, groups, members, messages, owners, teams, and users.

SAP Ariba Request node

Use the SAP Ariba Request node to connect to SAP Ariba and issue requests to perform actions on objects such as contract workspaces, organizations, sourcing projects, suppliers, and users.

Snowflake Request node

Use the Snowflake Request node to connect to Snowflake and issue requests to perform actions on objects such as custom SQL queries, pipes, rows, stages, stored procedures, tables, and tasks.

WordPress Request node

Use the WordPress Request node to connect to WordPress and issue requests to perform actions on objects such as authors, blogs, comments, feeds, followers, posts, site statistics and more.

Discovery connector input nodes

The following additional IBM App Connect Enterprise discovery connector input nodes have been provided:

Gmail Input node

Use the Gmail Input node to monitor and receive input from Gmail.

IBM OpenPages with Watson Input node

Use the IBM OpenPages with Watson Input node to monitor and receive input from IBM OpenPages with Watson.

Microsoft Dynamics 365 for Sales Input node

Use the Microsoft Dynamics 365 for Sales Input node to monitor and receive input from Microsoft Dynamics 365 for Sales.

Microsoft Excel Online Input node

Use the Microsoft Excel Online Input node to monitor and receive input from Microsoft Excel Online.

Microsoft SharePoint Input node

Use the Microsoft SharePoint Input node to monitor and receive input from Microsoft SharePoint.

Microsoft Teams Input node

Use the Microsoft Teams Input node to monitor and receive input from Microsoft Teams.

Zendesk Service Input node

Use the Zendesk Service Input node to monitor and receive input from Zendesk Service.

Visualization of deployed message flows

Support for visualization of deployed message flows in the IBM App Connect Enterprise Toolkit

You can view the active flow layout of a deployed message flow in the IBM App Connect Enterprise Toolkit by double-clicking a deployed flow or by using the Context menu to see a visualization of the deployed flow.

For more information, see Viewing the active flow layout of a deployed message flow in the IBM App Connect Enterprise Toolkit.

Retrieving and importing deployed resources

Support for retrieving and importing deployed resources into the IBM App Connect Enterprise Toolkit

You can retrieve and import some types of deployed resources into your workspace in the IBM App Connect Enterprise Toolkit. You can use this facility to check the contents of the deployed message flow against the contents in your version control system, and to run problem determination on your message flows.

For more information, see Retrieving and importing deployed resources into your workspace.

Publishing Admin logs over MQTT and IBM MQ

Support for publishing Admin logs over the MQ Telemetry Transport (MQTT) messaging and IBM MQ

You can publish Admin logs over the MQ Telemetry Transport (MQTT) messaging and IBM MQ by configuring the integration node's node.conf.yaml file to enable publishing, and then creating an MQTTServer or an MQEndpoint policy and subscribing to the relevant topics.

For more information, see Publishing admin logs over MQTT and IBM MQ.

Transport Layer Security (TLS) authentication for Connect:Direct nodes

Support for Transport Layer Security (TLS) authentication on IBM Sterling Connect:Direct nodes

You can configure TLS server authentication for your IBM Sterling Connect:Direct nodes by setting up a public key infrastructure, creating or modifying a policy, and specifying a value for the Connect Direct protocol property.

For more information, see Configuring IBM Sterling Connect:Direct nodes to use TLS.

Enhanced support for OpenTelemetry trace

Support for OpenTelemetry trace on Linux zSeries and Windows

Support for OpenTelemetry trace has been extended to include integration servers on the Linux zSeries and Windows platforms, in addition to the support for Linux x86-64 that was added in IBM App Connect Enterprise V12.0.7.

For more information, see Configuring OpenTelemetry trace for an integration server.

Discovery connector request nodes

The following additional IBM App Connect Enterprise discovery connector request nodes have been provided:

Amazon CloudWatch Request node

Use the Amazon CloudWatch Request node to connect to Amazon CloudWatch and issue requests to perform actions on objects such as composite alarms, log events, metrics, and export tasks.

For more information, see Amazon CloudWatch Request node.

Amazon EC2 Request node

Use the Amazon EC2 Request node to connect to Amazon EC2 and issue requests to perform actions on objects such as Amazon machine images, availability zones, instances, key pairs, launch templates, and security groups.

For more information, see Amazon EC2 Request node.

Anaplan Request node

Use the Anaplan Request node to connect to Anaplan and issue requests to perform actions on objects such as files, cell data, list items, processes, imports, and exports.

For more information, see Anaplan Request node.

Asana Request node

Use the Asana Request node to connect to Asana and issue requests to create, retrieve, update, or delete objects such as projects, tasks, stories, and workspaces.

For more information, see Asana Request node.

AWS Lambda Request node

Use the AWS Lambda Request node to connect to AWS Lambda and issue requests to create, retrieve, update, delete, or invoke functions.

For more information, see AWS Lambda Request node.

Confluence Request node

Use the Confluence Request node to connect to Confluence and issue requests to create, retrieve, update, delete, download, or publish objects such as blog posts, pages, attachments, and comments.

For more information, see Confluence Request node.

Dropbox Request node

Use the Dropbox Request node to connect to Dropbox and issue requests to retrieve files, folders, and paper docs, create, retrieve or revoke shared links, or download file content.

For more information, see Dropbox Request node.

flexEngage Request node

Use the flexEngage Request node to connect to flexEngage and issue requests to create or retrieve order events.

For more information, see flexEngage Request node.

GitHub Request node

Use the GitHub Request node to connect to GitHub and issue requests to create, retrieve, update, delete, or merge objects such as branches, issues, organizations, pull requests, and repositories.

For more information, see GitHub Request node.

Gmail Request node

Use the Gmail Request node to connect to Gmail and issue requests to send, delete, or retrieve emails, or update email labels.

For more information, see Gmail Request node.

Google Cloud PubSub Request node

Use the Google Cloud PubSub Request node to connect to Google Cloud Pub/Sub and issue requests to create, retrieve, update, or delete objects such as subscriptions, topics, and messages.

For more information, see Google Cloud PubSub Request node.

Google Cloud Storage Request node

Use the Google Cloud Storage Request node to connect to Google Cloud Storage and issue requests to perform actions on objects such as buckets, bucket ACLs, object ACLs, and object versioning.

For more information, see Google Cloud Storage Request node.

Google Drive Request node

Use the Google Drive Request node to connect to Google Drive and issue requests to retrieve objects such as files, folders, revisions, and comments.

For more information, see Google Drive Request node.

IBM OpenPages with Watson Request node

Use the IBM OpenPages with Watson Request node to connect to IBM OpenPages with Watson and issue requests to create, retrieve, update, or delete objects such as business entities, controls, files, issues, and processes.

For more information, see IBM OpenPages with Watson Request node.

Jira Request node

Use the Jira Request node to connect to Jira and issue requests to create, retrieve, update, or delete objects such as projects, issues, filters, and users.

For more information, see Jira Request node.

Marketo Request node

Use the Marketo Request node to connect to Marketo and issue requests to create, retrieve, update, or delete objects such as campaigns, leads, lists, or opportunities.

For more information, see Marketo Request node.

monday.com Request node

Use the monday.com Request node to connect to monday.com and issue requests to perform actions on objects such as boards, item files, items, subitems, and users.

For more information, see monday.com Request node.

Oracle Human Capital Management Request node

Use the Oracle Human Capital Management Request node to connect to Oracle Human Capital Management and issue requests to create, retrieve, update, or delete objects such as absence records, candidates, job requisitions, payrolls, and time records.

For more information, see Oracle Human Capital Management Request node.

Salesforce Marketing Cloud Request node

Use the Salesforce Marketing Cloud Request node to connect to Salesforce Marketing Cloud and issue requests to perform actions on objects such as assets, campaigns, contacts, event definitions, journeys, and locations.

For more information, see Salesforce Marketing Cloud Request node.

Trello Request node

Use the Trello Request node to connect to Trello and issue requests to create, retrieve, update, or delete objects such as actions, boards, cards, checklists, and teams.

For more information, see Trello Request node.

UKG Request node

Use the UKG Request node to connect to UKG (Ultimate Kronos Group) and issue requests to retrieve, reset, or create objects such as attendance records, employee schedules, job preferences, people, and leave records.

For more information, see UKG Request node.

Zendesk Service Request node

Use the Zendesk Service Request node to connect to Zendesk Service and issue requests to create, retrieve, update, or delete objects such as articles, tickets, ticket attachments, and users.

For more information, see Zendesk Service Request node.

Discovery connector input nodes

The following additional IBM App Connect Enterprise discovery connector input nodes have been provided:

GitHub Input node

Use the GitHub Input node in a message flow to accept input from GitHub. For example, you can use the GitHub Input node to monitor GitHub for new or updated objects such as issues, commits, comments, and review comments.

For more information, see GitHub Input node.

Google Cloud PubSub Input node

Use the Google Cloud PubSub Input node in a message flow to accept input from Google Cloud Pub/Sub. For example, you can use the Google Cloud PubSub Input node to monitor Google Cloud Pub/Sub for new messages.

For more information, see Google Cloud PubSub Input node.

Jira Input node

Use the Jira Input node in a message flow to accept input from Jira. For example, you can use the Jira Input node to monitor Jira for new or updated issues.

For more information, see Jira Input node.

monday.com Input node

Use the monday.com Input node in a message flow to accept input from monday.com. For example, you can use the monday.com Input node to monitor monday.com for new, updated, or deleted objects, such as items and subitems.

For more information, see monday.com Input node.

OpenTelemetry support

Support for OpenTelemetry trace on an integration server

Support is provided for configuring OpenTelemetry trace for integration servers on the Linux x86-64 platform. You can configure an integration server to enable OpenTelemetry trace and export span data to an OpenTelemetry collector. When OpenTelemetry is enabled for an integration server, spans are created for all message flow nodes that support OpenTelemetry, including callable flow nodes.

For more information, see Configuring OpenTelemetry trace for an integration server.

Compression on the HTTPReply node

Compressing response data on the HTTPReply node

You can configure an HTTPReply node to compress the data in the HTTP response, by setting properties on the node. You can also configure an integration server to enable the compression of response data on all HTTPReply nodes on the server, by using an HTTPReplyWithCompression policy.

For more information, see Configuring compression for the HTTPReply node.

Remote default queue manager for managed file transfers

Support for using a remote default queue manager with IBM MQ Managed File Transfer

You can configure a remote default queue manager on an independent integration server to be used for managed file transfers using IBM MQ Managed File Transfer.

For more information, see Configuring a remote queue manager for managed file transfers using IBM MQ Managed File Transfer.

Toolkit enhancements

Formatting of output messages in the Flow Exerciser

When using the Flow Exerciser to send a message to a message flow using HTTP or MQ, the sent and received messages are automatically formatted in XML or JSON if they are in those formats. If the message cannot be formatted in XML or JSON, it is displayed in its raw format.

Copying values from the message assembly viewer in the Flow Exerciser

When viewing the recorded path of a message through a message flow using the Flow Exerciser, you can view the message tree by selecting the message icon on a highlighted wire between message flow nodes. The message tree at that point in the message flow is shown. You can copy the name, value, or namespace of an element in the message tree so that it can be pasted elsewhere.

Deploying referenced shared libraries for a project

When you deploy an application to an integration server, if the application has a dependency on a shared library, you can choose whether to include the shared library in the BAR file that is generated when the application is deployed. If you select the option to include the shared library, any nested shared libraries are also included in the BAR file. This option is available only if the shared library exists in the Toolkit workspace.

Slack Request node

Slack Request node

You can use the Slack Request node to connect to Slack and issue requests to send or retrieve messages, or to add, delete, or retrieve objects such as files, channels, users, and groups.

The Connector Discovery wizard enables you to discover and set properties for the Slack connector, which are then returned to the Slack Request node in the IBM App Connect Enterprise Toolkit.

For more information, see Using Slack with IBM App Connect Enterprise.

ServiceNow Request node

ServiceNow Request node

You can use the ServiceNow Request node to connect to ServiceNow and issue requests to create, retrieve, update, download, and delete objects such as assets, incidents, and tickets.

The Connector Discovery wizard enables you to discover and set properties for the ServiceNow connector, which are then returned to the ServiceNow Request node in the IBM App Connect Enterprise Toolkit.

For more information, see Using ServiceNow with IBM App Connect Enterprise.

SAP OData Request node

SAP OData Request node

You can use the SAP OData Request node to connect to SAP and issue requests to create, retrieve, update, or delete SAP OData resources.

The Connector Discovery wizard enables you to discover and set properties for the SAP OData connector, which are then returned to the SAP OData Request node in the IBM App Connect Enterprise Toolkit.

For more information, see Using SAP OData with IBM App Connect Enterprise.

Oracle E-Business Suite Request node

Oracle E-Business Suite Request node

You can use the Oracle E-Business Suite Request node to connect to Oracle E-Business Suite and issue requests to create, get, update, or delete objects such as customers, orders, deliveries, invoices, and receipts.

The Connector Discovery wizard enables you to discover and set properties for the Oracle E-Business Suite connector, which are then returned to the Oracle E-Business Suite Request node in the IBM App Connect Enterprise Toolkit.

For more information, see Using Oracle E-Business Suite with IBM App Connect Enterprise.

Salesforce Input node

Salesforce Input node

You can use the Salesforce Input node to monitor and receive input from Salesforce.

The Connector Discovery wizard enables you to discover and set properties for the Salesforce connector, which are then returned to the Salesforce Input node in the IBM App Connect Enterprise Toolkit.

For more information, see Using Salesforce with IBM App Connect Enterprise.

ServiceNow Input node

ServiceNow Input node

You can use the ServiceNow Input node to monitor and receive input from ServiceNow.

The Connector Discovery wizard enables you to discover and set properties for the ServiceNow connector, which are then returned to the ServiceNow Input node in the IBM App Connect Enterprise Toolkit.

For more information, see Using ServiceNow with IBM App Connect Enterprise.

FileIterator node

FileIterator node

You can use the FileIterator node to iterate over a list of files that are produced by the FileExists node, propagating one file at a time, so that it can be processed by the FileRead node.

For more information, see FileIterator node.

Transformation Advisor tool enhancements

Enhancements to the Transformation Advisor tool and the TADataCollector command

The TADataCollector command has been extended to include a --target parameter, which you can use to specify the target of the analysis to be run by the Transformation Advisor tool. As a result of setting this parameter, the advice given by the Transformation Advisor tool is focused on the specified target, which can be ACE Containers, ACEv11 Software, or ACEv12 Software. By default, the specified target is ACE Containers.

For more information, see TADataCollector command.

Amazon S3 Request node

Amazon S3 Request node

You can use the Amazon S3 Request node to connect to Amazon S3 and issue requests to create, retrieve, update, delete, or view buckets and other objects.

The Connector Discovery wizard enables you to discover and set properties for the Amazon S3 connector, which are then returned to the Amazon S3 Request node in the IBM App Connect Enterprise Toolkit.

For more information, see Using Amazon S3 with IBM App Connect Enterprise.

Coupa Request node

Coupa Request node

You can use the Coupa Request node to connect to Coupa and issue requests to create, retrieve, and update objects such as expense reports, exchange rates, and invoices.

The Connector Discovery wizard enables you to discover and set properties for the Coupa connector, which are then returned to the Coupa Request node in the IBM App Connect Enterprise Toolkit.

For more information, see Using Coupa with IBM App Connect Enterprise.

IBM Cloudant Request node

IBM Cloudant Request node

You can use the IBM Cloudant Request node to connect to IBM Cloudant® and issue requests to create, retrieve, update, delete, or view documents in a Cloudant database.

The Connector Discovery wizard enables you to discover and set properties for the IBM Cloudant connector, which are then returned to the IBM Cloudant Request node in the IBM App Connect Enterprise Toolkit.

For more information, see Using IBM Cloudant with IBM App Connect Enterprise.

Microsoft Azure Blob Storage Request node

Microsoft Azure Blob Storage Request node

You can use the Microsoft Azure Blob Storage Request node to connect to Microsoft Azure Blob storage and issue requests to perform actions on objects such as blobs and containers.

The Connector Discovery wizard enables you to discover and set properties for the Microsoft Azure Blob storage connector, which are then returned to the Microsoft Azure Blob Storage Request node in the IBM App Connect Enterprise Toolkit.

For more information, see Using Microsoft Azure Blob storage with IBM App Connect Enterprise.

IBM Maximo Request node

IBM Maximo Request node

You can use the IBM Maximo Request node to connect to IBM Maximo® and issue requests to perform actions on objects such as assets, contracts, purchase orders, and service requests.

The Connector Discovery wizard enables you to discover and set properties for the IBM Maximo connector, which are then returned to the IBM Maximo Request node in the IBM App Connect Enterprise Toolkit.

For more information, see Using IBM Maximo with IBM App Connect Enterprise.

Magento Request node

Magento Request node

You can use the Magento Request node to connect to Magento and issue requests to perform actions on objects such as customers, products, sales invoices, and orders.

The Connector Discovery wizard enables you to discover and set properties for the Magento connector, which are then returned to the Magento Request node in the IBM App Connect Enterprise Toolkit.

For more information, see Using Magento with IBM App Connect Enterprise.

Salesforce Request node (new)

Salesforce Request node

You can use the new Salesforce Request node to connect to Salesforce and issue requests to perform actions on objects such as accounts, campaigns, contacts, leads, and orders.

The Connector Discovery wizard enables you to discover and set properties for the Salesforce connector, which are then returned to the Salesforce Request node in the IBM App Connect Enterprise Toolkit.

SalesforceRequest (no discovery) is the new name for the node that was called SalesforceRequest in previous versions of IBM App Connect Enterprise (up to and including V12.0.4.0), and it continues to operate in the same way as in previous versions.

For more information about using the new Salesforce Request node, see Using Salesforce with IBM App Connect Enterprise.

FileExists node

FileExists node

You can use the FileExists node in a flow to poll for the existence of a specified file at a specified location, and to process the file without reading the file contents. The meta-data for the file is propagated down the flow without processing the contents of the file. The file contents can then be read and processed by another node (such as a FileRead node) later in the flow. You can also choose whether to delete the file or leave it in the file directory after it has been propagated through the flow.

For more information, see FileExists node.

Optimized integration server startup

ibmint optimize server command

You can use the ibmint optimize server command to optimize the startup time of an integration server.

For more information, see Optimizing the startup time for an independent integration server and ibmint optimize server command.

Maven support

Adding Maven support to an integration project

You can use Maven to extend the capability of an integration project by enabling the inclusion of dependencies.

For more information, see Using Maven with the IBM App Connect Enterprise Toolkit.

Business transaction monitoring enhancements

Enhanced views of business transaction monitoring data

The business transaction monitoring capability in App Connect Enterprise has been extended to provide graphical displays of business transaction monitoring data, including charts that show the number and duration of transactions by date and status.

The filtering capability has also been extended to enable the filtering of data by transaction ID, status, start time, and the time of the last update.

For more information, see Viewing the results of business transaction monitoring.

Enhanced OpenAPI 3.0 support

Support for consuming or calling a REST API defined in an OpenAPI 3.0 document

IBM App Connect Enterprise 12.0.3.0 can consume or call a REST API defined in an OpenAPI 3.0 or Swagger 2 document.

The RESTRequest and RESTAsyncRequest nodes can now use imported Swagger 2 or OpenAPI 3.0 documents, in JSON or YAML format. For more information, see RESTRequest node and RESTAsyncRequest node.

IBM App Connect Enterprise can also implement a REST API in OpenAPI 3.0 or Swagger 2 format, by creating a REST API project and importing or creating a REST API definition from scratch. For more information, see Creating a REST API.

Redeploying non-dynamic policies

Support for redeploying non-dynamic policies

You can redeploy non-dynamic policies by using the --restart-all-applications parameter on the mqsideploy or ibmint deploy command. This parameter restarts all applications on the integration server as part of the deploy operation.

For more information about dynamic and non-dynamic policies, see Policy properties.

Toolkit enhancements

Toolkit preference for automatically connecting to integration nodes and servers

By default, when you create a connection from the Toolkit to an integration node or server, the Toolkit connects automatically when it is started. However, if you want to create the connection details without automatically connecting the Toolkit to the integration node or server, you can turn off the automatic connection by deselecting the option in the Toolkit preferences.

For more information, see Connecting to an integration node by using the Toolkit and Connecting to an integration server by using the Toolkit.

Integration server console log

When you start an integration server by using the IBM App Connect Enterprise Toolkit, you can view the output in the console log. This file is overwritten when you restart the Toolkit. In IBM App Connect Enterprise 12.0.3.0 you can set a Toolkit preference to create a new console log file when the integration server (TEST_SERVER) is started. You can set this preference by clicking Window > Preferences > Integration Development > Connection Settings, and then selecting Use a new console log file when the TEST_SERVER is started. The filename contains the timestamp from when the file was created.

You can also specify how many console log files to keep on disk, in the Toolkit Preferences. After you start the TEST_SERVER, you can right-click on it at any time and select Open Console Log to view the current console log that contains the output from the integration server.

REST API documentation

You can access the administration REST API documentation for an independent integration server or integration node, by right-clicking on the server or node and selecting Open Administration REST API Documentation from the menu.

Retrieving credentials from an external credential provider

Support for retrieving security credentials from an external source

You can configure an independent or managed integration server to access secured resources by using credentials that are retrieved from an external file or key vault. You configure the integration server to use an external credential provider by setting properties in the ExternalCredentialsProviders section of the integration server's server.conf.yaml file.

For more information, see Configuring an integration server to use security credentials from an external source.

Support for TLS v1.3

TLS v1.3 support in HTTP, SOAP, REST, and Kafka nodes

You can configure HTTP, SOAP, REST, and Kafka nodes in the IBM App Connect Enterprise Toolkit to use TLS v1.3.

Business transaction monitoring

Monitoring business transactions through one or more message flows

The business transaction monitoring capability in App Connect Enterprise enables you to track and report the lifecycle of a payload message through an end-to-end enterprise transaction. You can track the outcomes of work passing through multiple message flows, allowing you to see which aspects of your business transaction are working correctly and which aspects are failing.

For more information, see Business transaction monitoring overview.

Subflow user-defined nodes

Enhanced support for creating and packaging subflows as user-defined nodes

You can create a subflow in a static library and then package it as a user-defined node that can be accessed through the IBM App Connect Enterprise Toolkit node palette. The subflow can then be used in a message flow by adding the user-defined node to the flow.

For more information, see Developing subflow user-defined nodes in a static library.

Pushing REST APIs to IBM API Connect 10

Enhanced support for pushing REST APIs to IBM API Connect

The ability to push the definition of deployed REST APIs into IBM API Connect has been extended to enable you to push REST APIs to IBM API Connect 10.

For more information, see Pushing REST APIs to IBM API Connect.

Monitoring enhancements

Writing monitoring events to a file

In addition to publishing integration server monitoring events to MQ and MQTT topics, you can choose to write the events to rotatable log files in the file system.

For more information, see Configuring the publication of event messages.

Publishing monitoring events to an ELK stack

The monitoring capability has been extended to enable the publication of monitoring events to a Logstash input in an Elasticsearch, Logstash, and Kibana (ELK) stack. You can then view the data in a Kibana dashboard.

For more information, see Configuring integration servers to send logs and events to Logstash in an ELK stack.

Monitoring events in JSON format

The ability to publish monitoring events to MQ and MQTT topics has been extended to include options for publishing the events in JSON format, XML format, or both.

For more information, see Configuring the publication of event messages and Subscribing to event message topics.

Activity Log enhancements

Publishing Activity Log events to an ELK stack

In addition to writing your activity logs to a file system, you can configure an Activity Log policy to publish the events to a Logstash input in an Elasticsearch, Logstash, and Kibana (ELK) stack.

For more information, see Writing activity logs to files, to the integration server console, or to an ELK stack and Activity Log policy (ActivityLog).

ibmint command enhancements

ibmint delete node and ibmint generate msgindex commands

Additional ibmint commands have been provided, which you can use to delete an integration node and to generate an index of recorded messages.

For more information, see the following topics:

• ibmint delete node command
• ibmint generate msgindex command

Integration testing

Support for developing unit tests for message flows and message flow nodes

You can create and run unit tests to validate the operation of your IBM App Connect Enterprise flows and message flow nodes. You can create and run unit tests while you are developing your message flows and nodes, or you can generate tests from recorded messages and use them to test flows that have already been deployed.

For information, see Developing integration tests.

JSON validation

JSON schema validation

You can configure a message flow to validate a JSON document in accordance with a JSON schema, which can be either a JSON schema file or an OpenAPI definition file. When parsing, the JSON parser checks that the input document is well-formed JSON, according to the JSON specification. If validation is enabled, the JSON parser also checks that the JSON document obeys the rules in the JSON schema.

For more information, see JSON validation.

ibmint commands

ibmint commands

The ibmint commands enable you to create simple pipelines of artifacts from source into the IBM App Connect Enterprise runtime. These commands are primarily of interest to new users and are not a replacement for existing MQSI commands, which continue to be fully supported.

You can use ibmint commands to create, start, stop, package, and deploy components in IBM App Connect Enterprise, and to generate tests for your message flows.

For more information, see ibmint commands.

REST API enhancements

Support for OpenAPI Specification 3.0

In addition to creating REST APIs from Swagger 2 documents, you can now create a REST API from scratch by creating a new OpenAPI 3.0 document, or you can import an existing OpenAPI 3.0 document. You can edit the REST APIs by using the OpenAPI editor.

For more information, see Creating a REST API.

IBM App Connect Enterprise Toolkit enhancements

Message Assembly Editor

You can view, edit, and create message assemblies for use in your integration tests, by using the Message Assembly Editor. The Message Assembly editor is launched when you open an existing message assembly file, or when you create a new one. You can use the Message Assembly Editor to edit messages that have been recorded and saved by the Flow Exerciser.

For more information, see Message Assembly editor and Editing a message assembly.

Flow Exerciser enhancements

The Flow Exerciser has been updated with additional features, including a blue line view that highlights the path that a message has taken through the flow. You can select the message icon on each blue highlighted path to show the details of the message at that point in the flow. You can save any recorded message on the blue path as a message assembly (.mxml) file in the application that contains the message flow. A new Save all recorded messages button is available in the Flow Exerciser toolbar, which you can use to save all messages that are recorded by the Flow Exerciser. The recorded messages are shown under Recorded Messages in the Send Message window.

After saving the message assembly, you can edit it and send it to the message flow by using the Flow Exerciser, or you can use it in a unit test for the message flow node. For more information, see Editing a message assembly and Developing integration tests.

Tutorials Gallery enhancements

The Tutorials Gallery has been updated and extended to include new tutorials and a search facility, which you can use to explore and learn about the capabilities of IBM App Connect Enterprise.

Eclipse eGit feature

The standard Eclipse eGit feature is now available in the Toolkit, and you can use the eGit perspective to work with your Git repositories.

Message flow node icons

The appearance and organization of message flow nodes in the node palette has been updated to clearly differentiate between connectors and toolbox nodes. You can also use the search tool at the top of the palette to search for a node in either section of the palette.

Layout of nodes and flows in the message flow editor

You can choose how the nodes in the message flow editor are presented, with the message flow node name displayed either in the node or underneath the icon. You can choose your preferred layout in the Application Development view by right-clicking the canvas and clicking Layout, then selecting either Name inside the node or Name below the icon. You can also choose whether to display the message flows from left to right, right to left, top to bottom, or bottom to top, by selecting your preferred Layout options.

By default, new message flows and subflows are shown with the name inside the node. Flows that were created in a previous version are displayed in the way that they were created, with the name below the icon. You can choose to have all new flows and subflows displayed with the name below the icon, by deselecting the Display node name inside the node when creating new message flows option in the preferences settings for the Message Flow editor.

Integration Explorer view

The integration node and integration server icons have been updated in the Integration Explorer view.