Obtaining the IBM App Connect Enterprise server image from the IBM Cloud Container Registry

You can obtain the IBM® App Connect server Docker image from the IBM Cloud Container Registry and run it in other platforms such as Microsoft Azure. Separate images are available for IBM App Connect Enterprise and IBM App Connect Enterprise for Developers.


Obtaining an IBM App Connect Enterprise server image

To obtain your required version of an IBM App Connect Enterprise server image, you require an IBM entitlement key for pulling the image from the IBM Cloud Container Registry. You need to obtain this key once only.

Procedure

Complete the following steps:

  1. Obtain an IBM entitlement key from the following location: https://myibm.ibm.com/products-services/containerlibrary.
  2. Log in to the IBM Cloud Container Registry by running this command, using cp as the username, cp.icr.io as the Docker server, and your entitlement key as the password: 
    docker login cp.icr.io -u cp -p myEntitlementKey

    For more information about the Container Registry, see the IBM Cloud Container Registry documentation.

  3. Use Docker to pull the required version, where imageLocation represents one of the listed image locations in the following table: 
    docker pull imageLocation
    Version Image location
    11.0.0.18-r1-eus cp.icr.io/cp/appc/ace-server-prod@sha256:44ae60b637b094de9f783e6e48d080b9163a6af5f6d106a458d3d1ced8aa091a
    11.0.0.17-r2-eus cp.icr.io/cp/appc/ace-server-prod@sha256:0fb5e38fa724c8944ee24b00b792985b72238a25b29ef980cf8c94af72ceb8cc
    11.0.0.17-r1-eus cp.icr.io/cp/appc/ace-server-prod@sha256:bc6243287af7274883e50690bb02eecc9ebc0bbe6338a1213ff2fa39e03f5c23
    11.0.0.16-r1-eus cp.icr.io/cp/appc/ace-server-prod@sha256:9d0a32db3c371753af087f8c715eae9b54516251616b99444c67c3814f4ce9dc
    11.0.0.15-r2-eus cp.icr.io/cp/appc/ace-server-prod@sha256:12c18f534fb755add1c20d6ae71398858022a373376054f434419d4ce9403cba
    11.0.0.15-r1-eus cp.icr.io/cp/appc/ace-server-prod@sha256:c18dfecd10dc7cddfb8eebdfdc4a2d5f97aad5e9344a7176bd758a8027995031
    11.0.0.14-r1-eus cp.icr.io/cp/appc/ace-server-prod@sha256:891841a6a7e6996bd23fb8910972cd73005d2ffb507a1e8adea4319b322536fa
    11.0.0.13-r2-eus cp.icr.io/cp/appc/ace-server-prod@sha256:fad57087e71d4630e9321ea9f913f8d3bc7ab41ae6287ac1d8fb69bafab23159
    11.0.0.13-r1-eus cp.icr.io/cp/appc/ace-server-prod@sha256:a51fa639c8235ca1f1af696d7f7616ce31c15f9a4a0991f526c80edff4b0772b
    11.0.0.12-r1-eus cp.icr.io/cp/appc/ace-server-prod@sha256:8372beb29cd95d0d3de1b6587248e9997e69ef13bc77caffd6ca3f7068d7779a
    11.0.0.10-r3-eus cp.icr.io/cp/appc/ace-server-prod@sha256:b218a2daec93b8e4555f58a3fd658c3d7b30893b6bff69ec92f81d946c4d1ab3
    11.0.0.10-r2 cp.icr.io/cp/appc/ace-server-prod@sha256:bdeb8b839be9e095bf3c74be8b9f02f54cf6c0a740b8f45f93d01265549d9e83
    11.0.0.10-r1 cp.icr.io/cp/appc/ace-server-prod@sha256:dd3c1e8d204b37775b792fc25a0bad4daba4fa35cd5aad996b29b1db63959baf
    11.0.0.9-r3 cp.icr.io/cp/appc/ace-server-prod@sha256:8df2fc5e76aa715e2b60a57920202cd000748476558598141a736c1b0eb1f1a3
    11.0.0.9-r2 cp.icr.io/cp/appc/ace-server-prod@sha256:04bc376391a00ff1923d9122f93911b0f8e9700c7dda132f24676e383c0283cc
    11.0.0.9-r1 cp.icr.io/cp/appc/ace-server-prod@sha256:2771ba69f5871c37979576389f5a2040213b913f4d46bfbcafdabdea808f5bad
  4. Re-tag the image appropriately and then push it to your preferred registry.

    You can run the image by using an example command such as:

    docker run --name aceserver -p 7600:7600 -p 7800:7800 -p 7843:7843 --env LICENSE=accept --env ACE_SERVER_NAME=ACESERVER cp.icr.io/cp/appc/ace-server-prod@sha256:2771ba69f5871c37979576389f5a2040213b913f4d46bfbcafdabdea808f5bad

    For additional configuration options, see http://ibm.biz/ot4iaceserver.

Obtaining an IBM App Connect Enterprise for Developers server image

The IBM App Connect Enterprise for Developers server images are freely available, so no login credentials are required for pulling an image.

Procedure

Complete the following steps:

  1. Use Docker to pull the required version, where imageLocation represents one of the listed image locations in the following table: 
    docker pull imageLocation
    Version Image location
    11.0.0.18-r1-eus icr.io/appc-dev/ace-server@sha256:981964587a3c9a863ac242c5f9e62b831a40a7de1cdb76172513e5568901161e
    11.0.0.17-r2-eus icr.io/appc-dev/ace-server@sha256:5c5765a667e514f41f85c7533308ecc79930c71f5a56430f9a5b450635553da0
    11.0.0.17-r1-eus icr.io/appc-dev/ace-server@sha256:9a801836461e25823390fb4ba6b935895f6beb3a6a17d980797dce43e587e8f9
    11.0.0.16-r1-eus icr.io/appc-dev/ace-server@sha256:167b13d9a2817755ef6229c3f604f2bcc9f67aa3652490e116d855cc24e9fc33
    11.0.0.15-r2-eus icr.io/appc-dev/ace-server@sha256:f16c062ce3cf3e48d74387273797dd09885c6abb6789ccf827770e8473e5c391
    11.0.0.15-r1-eus icr.io/appc-dev/ace-server@sha256:dc4dc73cde456f1a95ab09a0dcea19d325613f69d4b296760e0547f37ac36334
    11.0.0.14-r1-eus icr.io/appc-dev/ace-server@sha256:6f35b1193d9ffff705f1f311a957def702096d8c6d6628091bef8cfafd7ad30d
    11.0.0.13-r2-eus icr.io/appc-dev/ace-server@sha256:1511135262a37beb03aad655f9be5f8281a7c39e19cfe72f5a91ab0afddbae0f
    11.0.0.13-r1-eus icr.io/appc-dev/ace-server@sha256:980a561ba72fcc53f46e909f9f94c521aa66bf11a3e286480c8074d4e8bb40fe
    Tip: If you observe errors when pulling the image, ensure that you are logged out from the Container Registry by running the following command, which should eliminate issues pertaining to stale tokens:
    docker logout icr.io
  2. Re-tag the image appropriately and then push it to your preferred registry.

    You can run the image by using an example command such as:

    docker run --name aceserver -p 7600:7600 -p 7800:7800 -p 7843:7843 --env LICENSE=accept --env ACE_SERVER_NAME=ACESERVER icr.io/appc-dev/ace-server@sha256:980a561ba72fcc53f46e909f9f94c521aa66bf11a3e286480c8074d4e8bb40fe

    For additional configuration options, see http://ibm.biz/ot4iaceserver.