Configuring App Connect Enterprise to run on premises (on a physical or virtual machine)

You can create one or more integration nodes on one or more computers, and configure them on your test and production systems to process messages that contain your business data.

About this task

On Linux® and Windows systems, you can install IBM® App Connect Enterprise and the IBM App Connect Enterprise Toolkit, and start developing your applications. You can also configure an environment for more advanced application development and unit test, as described in Configuring the IBM App Connect Enterprise Toolkit.

Use the information in this section to plan and configure the resources that you need to run on premises. Alternatively, you can configure App Connect Enterprise to run in a container or in Docker.

Procedure

  1. Plan your system; see Planning an IBM App Connect Enterprise environment.
  2. Ensure that you have the correct authorization and permissions to create and access components.
  3. Create the components, as described in Configuring integration nodes and Configuring integration servers.
  4. If you want to ensure that you are using the correct operation mode for your license, see Configuring the operation mode of your IBM App Connect Enterprise installation.
  5. Create and configure the databases.
  6. If you want to ensure the data integrity of transactions, Configure global coordination of transactions.
  7. If you want to connect to external resources such as Enterprise Information Systems, IMS, or JMS, Configure properties to connect to external resources.
  8. If you want to configure the storage of events for aggregation, Collector, resequence, or timeout nodes, or configure monitoring event sources, Configure internal resources that are required by message flows.
  9. If you want to view objects in a different language or code page, Change the locale.
  10. If you want to operate your IBM App Connect Enterprise instances in a highly available configuration; see Configuring integration nodes for high availability.
  11. If you want to operate your integration node as an IBM MQ service; see Configuring an integration node as an IBM MQ service.