Getting started

On this page, you will go through :

Installing Microcks

Microcks may be installed in many ways depending your preferred environment. Basically, it can be installed on Kubernetes, on OpenShift, using Docker-Compose or directly using binary and source of Microcks.

Installing on Kubernetes

We provide basic Kubernetes manifest for simple needs but also a Chart for using with Helm Packet Manager. This is definitely the preferred way of installing apps on Kubernetes.

Have a look on this page for more informations.

Installing on OpenShift

We provide OpenShift templates in many flavors for rapid deployment onto OpenShift. We will basically have different installation options:

  • Ephemeral or Persistent setup,
  • Embedding Keycloak or using an external mutualized instance,
  • With or without HTTPS Routes setup.
Have a look on this page for more informations.

Installing using Docker Compose

Docker Compose is really easy for a laptop or single demonstration server. You'll find instructions on how to use Docker Compose for installation here.

Using this deployment solution, we also provide one-click deployment to Microsoft Azure Cloud with this sub-project.

Using Microcks

Now you are ready to use Microcks for deploying your own services and API mocks! Before that let's have the look at the application home screen and introduce the main concepts. Using the application URL after installation, we should land on this page with 2 main entry points : Services and Jobs.

As you may have guessed, API | Services is about browsing your [micro]-services and API repository, discovering and accessing documentation, mocks and tests. Importers is another concept dedicated on how to fill this repository: it allows to define Jobs periodically scan your Git or Subversion repository for checking new definition files that will be parsed and integrated as part of your [micro]-services and API repository. Indeed Importers help discover new or modified Services. Before creating your own service definition files, let load some samples into Microcks for a test ride.

Loading samples

We provide different samples that illustrate different ways of creating service definitions. The 2 firsts are definition files realized using SoapUI and demonstrating SOAP and REST services. The third one is a definition file built using Postman and demonstrating the famous Petstore API. Using the Importers entry point from home screen or top navigation bar, use the Importers management page to add 3 new jobs. For each, you will be asked a name and a repository URL. Use the informations below:

  • Hello SOAP Service :
  • Hello REST API :
  • Petstore API :
Now that you have created your Jobs, you have to Activate them (this make them eligible to a periodically check) and to Force import them (this make a forced refresh right now). After some moments and a page refresh, you should see the status of Jobs changed like in screenshot below:

Viewing services

Once sample jobs have been loaded, new Services has been discovered and added to your repository. You can now visit the API | Services entry point from top navigation bar or home screen. You should see 3 new services with basic informations on version and operations/resources handled by this services.

Viewing details

Now choosing the Petstore API REST API, you'll be able to access details, documentation and request/response samples for each operation/resource in the screen below. One important information here is the Mocks URL field: this is the endpoint where Microcks automatically deploy a mock for this operation. The table just below show request/response couples and a detailed URL with the HTTP verb showing how to invoke this mock.

Using this URL, you can call the exposed mock for Petstore API using the following curl command :

curl ""

And you should receive the following response :


Ta Dam !

What's next?

Now that you have basic information on how to setup and use Microcks, you can go further with :