
Explore IBM AppConnect Enterprise, an integration platform that connects applications, systems, and data across on-premises, cloud, and hybrid environments, with data transformation, enrichment, and diverse protocol and connector support.
Learn to create an integration server for a locally defined integration node using the legacy mqsi create execution group and the new IBM int command.
Create an integration server using a .broker connection file with ssl mode disabled, detailing legacy mqsi create execution group and the new ibm int create server commands.
Learn to change http and https connector ports with mqsi change properties. Explore integration node and integration server properties, syntax, sample commands, and required restarts.
IBM App Connect Enterprise (ACE) version 13.x.x.x for Windows provides a comprehensive framework for managing integration nodes and servers, with a strong emphasis on secure configuration and flexible topologies. After downloading and verifying the installation package from IBM Fix Central, administrators can set up integration nodes, which act as controllers for multiple integration servers, and define external directory vaults to securely store sensitive credentials. Configuration files play a central role in tailoring both node-level and server-level properties, while integration connection files are particularly important when SSL is enabled to ensure secure communication between components.
The platform supports different deployment topologies, ranging from simple single-node setups to distributed multi-node or hybrid environments that combine local and cloud-based servers. Port configuration is another critical aspect: the RestAdminListener port provides access to the REST-based administration API, the NodeHttpListener port handles HTTP endpoints for flows and administrative tasks, and a dedicated debug port allows developers to troubleshoot message flows effectively.
Security is built around SSL, with a default self-signed certificate provided out of the box. Administrators can either trust this certificate by importing it into the appropriate trust store or replace it with their own certificate to establish a custom SSL configuration. For environments requiring stronger authentication, mutual TLS (MTLS) can be enabled, ensuring that both client and server validate each other’s certificates. Commands such as mqsicreatebroker or mqsicreateworkdir help create locally defined integration nodes, while mqsicreateconnection supports building SSL-enabled connection files. To manage and adjust properties dynamically, mqsireportproperties allows administrators to view current configurations, while mqsichangeproperties allows them to update them without restarting services.