webMethods Deployer 10.3 | webMethods Deployer Documentation 10.3 | Starting Deployer and Connecting to Servers | Connecting to webMethods Servers
 
Connecting to webMethods Servers
 
Connecting to Target ActiveTransfer Server Instances
Connecting to Target API Gateway Servers
Connecting to Target Digital Event Services Servers
Connecting to Integration Servers and Trading Networks Servers
Connecting to Optimize Servers
Connecting to Target Application Platform Servers
Connecting to My webMethods Servers
Connecting to Target Event Servers
Connecting to Broker Servers
Connecting to Target Task Engine Servers
Connecting to BPM Process Model Servers
Connecting to Target AgileApps Cloud Servers
Connecting to Target Universal Messaging Servers
Connecting to Target EDA Deployment Endpoints
Connecting to Target Business Rules Integration Servers
Connecting to Target Business Rules My webMethods Servers
You can perform the tasks in this section to connect to the source and target webMethods servers.
For runtime-based deployment projects, the source servers are those servers from which you select assets for deployment. For repository-based deployment you do not connect to source servers. The source for repository-based deployment is always the repository on which the composites are built. For more information about adding a source repository, see Connecting to a Repository for Repository-Based Deployment.
For both runtime- and repository-based deployment, you can perform the tasks in this section to map the assets from the source servers or repository to target servers. You define target servers to define the location to which Deployer deploys assets from the source server or repository.
For every source and target server you add, you select the version of the webMethods runtime for that server. For example, if you are adding a target Integration Server that is running version 8.2 SP1, you would select 8.2 for the version. The version you select affects the source and target servers you can include in the project as follows:
*For runtime-based deployment projects, after you select the source servers, Deployer displays only servers running compatible versions for selection as target servers. For example, if you select source servers of version 8.0, Deployer displays only target servers and target groups with a version of 8.0 or 8.2 for mapping.
The following table lists all version compatibilities:
Source Version
Compatible Target Versions
7.1
7.1
8.0
8.0, 8.2
8.2 targets support only the following runtimes from 8.0 sources:
*Integration Server
*Trading Networks
*BPM process models
8.2
8.2
9.0
9.0
9.5
9.5
9.6
9.6
9.7
9.7
9.8
9.8
9.9
9.9
9.10
9.10
9.12
9.12
10.0
10.0
10.1
10.1
10.2
10.2
10.3
10.3
Additionally, you can import builds from projects created with Deployer version 8.2 or earlier to Deployer 9.0 or later for deployment. For example, you could import a build from a version 8.0 project into Deployer 9.0.
*For repository-based deployment projects, each project includes sources and targets of only one version. You cannot include source repositories or target servers of different versions.
*For repository-based deployment projects, Deployer deploys only target servers and target groups of version 8.2 SP1 and later. Because repository-based deployment does not use source servers, Deployer limits the version of the targets in your project according to the first target server or target group you select for mapping. For example, if you select a target server of version 8.2, Deployer displays only target servers and target groups of version 8.2 for mapping.
You can connect to the following webMethods servers:
To connect to...
See...
ActiveTransfer
API Gateway
Digital Event Services
Integration Servers or Trading Networks servers
Optimize servers
Application Platform servers
My webMethods Servers
Event Servers
Broker servers
Task Engine servers
BPM process models
AgileApps Cloud
Universal Messaging servers
EDA deployment endpoints
Business Rules Integration Servers
Business Rules My webMethods Servers

Copyright © 2013-2018 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.