Creating an integration server

You must create an integration server before you can deploy integration solutions and related resources.

You can create one or more independent integration servers, each with their own identity, and deploy them either to containers in the cloud or in an on-premises environment. If you are planning to run App Connect Enterprise directly on a physical machine or virtual machine image, you are advised to define integration servers under an integration node, which will manage its associated integration servers.

For information about why you might want to create multiple integration servers, see Integration servers and integration nodes.

The mode in which IBM App Connect Enterprise is running can affect the number of integration servers that you can use; see Restrictions that apply in each operation mode.

For an independent integration server, you create the server's work directory and then configure the server's properties, as described in Creating an integration server work directory by using the mqsicreateworkdir command.

You can also create and start a local independent integration server by using the IBM App Connect Enterprise Toolkit, as described in Creating and starting a local, independent integration server by using the Toolkit.

To create an integration server under an integration node, first start the integration node, and then use one of the following methods:

• Creating an integration server that is managed by an integration node, by using the Toolkit
• Creating an integration server that is managed by an integration node, by using the web user interface
• Creating an integration server that is managed by an integration node, by using the mqsicreateexecutiongroup command

You can also use the IBM Integration API to create integration servers on all platforms; see Managing resources by using the IBM Integration API.