Setting the Local Development Server

Trading Networks 10.3 | Administering and Monitoring B2B Transactions | Service Development Help | Using the Local Service Development Feature | Setting the Local Development Server

A local development server can be one of the following server instances:

On-premise Integration Server

On-premise Microservices Runtime

Integration Server running inside a Docker container

Microservices Runtime running inside a Docker container

Note:
On-premise Integration Server and on-premise Microservices Runtime are referred to as Integration Server and Microservices Runtime respectively in this document, unless specifically stated otherwise.

The local service development feature works with the local development server only.

By default, a new Designer installation includes a single server definition named Default. This server is marked as the default server and is configured to use localhost:5555.

If your Designer installation needs to connect to more Integration Servers, you can configure additional Integration Server instances on the Window > Preferences > Software AG > Integration Servers page. If there are multiple Integration Server instances configured, only one instance will be active at a time. The default Integration Server instance will be treated as the default local development server. However, you can set any of the available local Integration Server instances as the local development server. Perform the following step to set an Integration Server instance as the local development server.

In Package Navigator view, right-click the Integration Server instance that you want to use as a local development server and select Use as Local Version Control Integration Server

The server icon changes to

indicating that it is an active local development server.

Note:
The Use as Local Version Control Integration Server option is available only if the selected Integration Server is connected and is installed in the same installation directory as the Designer instance.

Setting an Integration Server or Microservices Runtime as the Local Development Server

In versions prior to 9.10, Designer used only the Integration Server instance named “default” as the local development server. However, from version 9.10 release, you can set any Integration Server instance as the local development server as long as the selected instance is installed in the same installation directory as the Designer instance you are using.

Setting an Integration Server or Microservices Runtime Running inside a Docker container as the Local Development Server

To setup Integration Server or Microservices Runtime running inside a Docker container as local development server, ensure the following prerequisites are met:

Docker and Designer reside on the same host.

Docker daemon is up and directly listens to the Docker Remote API requests using a TCP socket without authentication and decryption.

Root storage area of the server instance in the Docker container is available on the host.

To do this, set Dtarget.configuration=localdev when creating a Dockerfile to build the Docker image for Integration Server or Microservices Runtime. This configuration creates a mount point using the volume instructions in the Dockerfile. For information on creating a Docker file and Docker image, see webMethods Integration Server Administrator’s Guide.

The volume is mounted as named volume while starting up the container.

For example, consider the following sample container startup command:

docker run -i -t -d \
--name $[container_name] \
-v $[container_named_volume]: [Install_Dir]/IntegrationServer/instances/[instance_Name] \
-p [host_primary_port:]primary_port \
[image_name] \
/bin/bash

Where...	Specify...
container_name	Name of the Integration Server or Microservices Runtime in the Docker for running the Integration Server orMicroservices Runtime image. For example, IS_Default.
container_named_volume	Named volume of the Docker.
Install_Dir	Installation directory of Integration Server or Microservices Runtime.
host_primary_port :	A port on the container host machine that you want to explicitly map to an exposed port on the Integration Server or Microservices Runtime, specifically the primary port.
primary_port	Port number for the primary port on Integration Server orMicroservices Runtime.
image_name	Name of Integration Server or Microservices Runtime image. For example, is:microPkg.