Managing Endpoints with Catalogs, Connectors, APIs and Accounts

IBM App Connect can easily Connect to Many Applications, Systems and Services. How are these managed?

App Connect Catalog Screenshot


Each IBM App Connect Instance has a Catalog

A Catalog contains the Smart Connectors and APIs that IBM App Connect integrations can call.

All Connectors appear automatically in the catalog. As new connectors are released, you’ll see the catalog update.

The Catalog also contains the APIs that have been added to the instance. These are APIs that you wish to call from App Connect and you need to add them in yourself.

In addtion, the Catalog also shows the callable flows that are available to this instance. Callable flows are discussed later.

Smart Connectors

Smart Connectors allow you to connect to many different applications and systems

All of the Connectors are included with IBM App Connect – you don’t need to pay per connector or endpoint

As well as Application connectors to connect to SaaS applications, there are ‘technology’ connectors to connect to endpoints such as HTTP, Databases or Messaging.

Each connector can have multiple accounts – each account is a separate endpoint e.g. for DEV, TEST, UAT versions of an application, or for different regions for example

App Connect Catalog showing multiple connectors

App Connect Catalog showing onpremise network connnections

Smart Connector Accounts

Each Smart Connector can have multiple Accounts to connect to different instances of the application.

Connector accounts store details like URLs, userIDs, Passwords, database names etc.

Connector accounts are stored in an IBM App Connect Instance. If you have more than one instance, you will have more than one set of connector accounts.

APIs have multiple accounts too. These are for details like userIDs, API Keys, HostName Overrides

Connector Accounts have default names like Account1, Account2 – they can be renamed!


APIs are where you store details of REST and WSDL APIs that you want to call

You import the details of your API once and then you can re-use it in your integrations by selecting it from the catalog.

You import APIs using industry-standard WSDL and OpenAPI (Swagger) files

If you want to have different endpoints for the same API e.g. to change the hostname, API key etc you can have multiple accounts for the same API – but you only need to import it once.

App Connect Catalog showing APIs

App Connect Catalog showing onpremise network connnections

Connecting to OnPremise Systems

APIs and some Connectors can connect to On Premise systems as well as Cloud services

IBM App Connect can do this in multiple ways – and it works well with firewalls!

As part of the connector or API account, you can specify a ‘network’ so that the connector knows which endpoint to call.

You can have multiple different networks and connect to multiple on-premise systems

Join The Discussion

Your email address will not be published. Required fields are marked *