Mapping Endpoints
Endpoint connections represent the incoming and outgoing connections for each logical server subcomponent. The endpoint connections that are available for a given logical server subcomponent are specified in a definition file on that logical server.
When an environment configuration is deployed, a configuration file containing the server mappings and the endpoint connections goes out to each logical server in the environment.
To map the incoming and outgoing connections for logical server subcomponents
1. In My webMethods: Navigate > Applications > Administration > System-Wide > Environments > Define Environments.
2. In the list of environments, click the Edit icon 
of the environment that you want to define or edit. 3. Click the Map Endpoints tab.
The Map Endpoints page lists the logical servers in the environment, the subcomponents of each logical server, and the default values for the incoming connections and the outgoing connections for each subcomponent.
Note:
The JMS provider for logical servers must match the JMS provider specified on the JNDI Configuration page. For example, if you choose “Broker (deprecated)” as the Naming Factory Type on the JNDI Configuration page, then on Endpoint Configuration panel on the Map Endpoints page, the protocol of JMS Provider must be wmjmsnaming. If you choose “Software AG Universal Messaging” as the Naming Factory Type, then on the Endpoint Configuration panel, the protocol of JMS Provider must be nsp,nsps, nhp, or nhps.
4. If needed, edit the protocol and ports in the Incoming Connections columns.
If you want to configure the My webMethods Server URL with root context, type the root context path in the field next to the protocol and port fields for MWS. For example, if My webMethods Server is running on localhost and you want to set the My webMethods Server URL to http://localhost:8585/mymws, type http, 8585, and mymws in the fields.
Important:
If you want to deploy more than one subcomponent of the same type to the same host, use unique port numbers for the incoming connections of the same subcomponent type. For example, if you want to deploy the configuration agent for the Analytic Engine and the configuration agent for the JMS Server to the same host, use unique port numbers for the incoming connections for both configuration agents. The environment configuration is valid only if each port number is unique for both configuration agents. When you accept the default port numbers, those numbers are unique.
5. If needed, edit the protocol and ports in the Outgoing Connections columns.
The drop-down list for each outgoing connection shows the available options.
6. Click Save.
The next step in configuring an environment is to map the database pools for each database component.
Note:
Configuration agent credentials are also defined from the
Map Endpoints tab. For more information about configuration agent credentials and authentication, see
Security.