Prerequisites
Before you use the local service development feature, you must:
Ensure that
Integration Server is installed in the same installation directory as the
Designer instance you are using. If you selected
Local Version Control Integration (or
Designer Workstation in versions prior to 9.8) from the
Software AG Installer, this was already done for you.
Ensure that the watt.server.ns.lockingMode parameter is set to
system on the
Integration Server used as the local development server. If you set any other value for this parameter, the Local Service Development feature may not work as expected. For more information about this parameter, see
webMethods Integration Server Administrator’s Guide.
Install the Workstation local service development feature as described in
Installing Software AG Products.
Ensure that the VCS Integration feature is not configured on the local development server.
Install the correct version of the VCS client that you want to use, and if necessary, install the correct Eclipse plug-in for that client. For details about supported Eclipse plug-ins and VCS versions, see
Supported Platforms and Eclipse
Plug-ins.
Important: If you are using Subversion as your VCS client, Software AG recommends that you use Subversion 1.7 or higher. Using versions of Subversion prior to 1.7 might cause issues while refreshing web service descriptors and web service connectors.
In
Designer, configure your workspace to be refreshed automatically by selecting the
Refresh using native hooks or polling or
Refresh automatically check box in
Window > Preferences > General > Workspace.
In
Designer, remove .BAK and .bak from the list of resource name patterns to exclude from the VCS. To do this, clear the .BAK and .bak check boxes in
Window > Preferences > Team > Ignored Resources.
If you are using CVS as your VCS client, in
Designer, clear the
Prune empty directories check box in
Window > Preferences >Team > CVS > Files and Folders.
If you are using EGit as your VCS client, clear the
Auto share projects located in a git repository check box in
Window > Preferences >Team > Git > Projects.
If you are using EGit as your VCS client, before creating the local service development project, create a new local Git repository. To create a new local Git repository, select
Create new local Git repository in the
Git Repositories view.
You can also use the Create Repository field in the Configure Git Repository screen of the Share Project wizard to create and select local Git repository while creating the local service development project.
Clear the Move project to Integration Server package as linked resource check box in Window > Preferences > Software AG > Service Development > Local Service Development to set the Integration Server_directory \instances\default\packages directory as the local Git repository. You can use the local Git repository for all further local development operations.
If you are using Team Foundation Server as your VCS client, in
Designer, clear the
Connect mapped projects to TFS automatically check box in
Window > Preferences >Team > Team Foundation Server before sharing the local service development project. Otherwise, Team Foundation Server might throw an exception when sharing the local service development project.
For local development in
Integration Server or
Microservices Container running inside a Docker container, before you start the Docker container, ensure that you mount the corresponding host directory of local Git repository or the TFS project directory in the Docker container. Consider the following sample startup command:
docker run -i -t -d \
--name $[container_name] \
-v $[container_named_volume]: [Install_Dir]/IntegrationServer/instances/ [instance_Name] \
-v [host_git_project_location]:/[container_git_project_location]
-p [host_primary_port:]primary_port \
[image_name] \
/bin/bash