API project build in the z/OS Connect Designer hangs

When the IBM® z/OS Connect Designer container is started, the API Project is built and then deployed to z/OS Connect Designer. In some instances, container networking issues that are often caused by proxies, can cause this build to get stuck while it attempts to resolve dependencies. As a result, the API is not made available for testing.

zosConnect-3.0 Applies to zosConnect-3.0.

Containers Applies to z/OS Connect container deployments.

About this task

Within the API Project, the following changes can be made to give preference to local dependencies packaged within the z/OS Connect Designer image for the API Project build.

Procedure

  1. Stop the z/OS Connect Designer. For more information, see Starting and stopping IBM z/OS Connect Designer.
  2. Open /myApiProject/build.gradle and move mavenCentral() to the end of the repositories section. Save and exit.
    Note: /myApiProject/ is the project workspace directory.
  3. Open /myApiProject/settings.gradle and move the gradlePluginPortal() to the end of the repositories section. Save and exit.
  4. Start the z/OS Connect Designer container again and review apiproject.log to see whether the build is successful. For more information, see Starting and stopping IBM z/OS Connect Designer.
    Note: The Gradle Daemon can take 60 - 90 seconds to start.