Why wsadmin creates only some (but not all) of the endpoints for Application Servers
 Technote (troubleshooting)
 
Problem(Abstract)
An endpoint provides host and port specifications for an Application Server. When using wsadmin to create an Application Server, not all the endpoints are created.
 
Cause
The current design of wsadmin allows the creation of an Application Server with only four of the eight possible types of endpoints to be created.
 
Resolving the problem

Background

When a new Application Server is created from the administrative console, the following eight endpoints are created:

  • BOOTSTRAP_ADDRESS
  • CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS
  • CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS
  • DRS_CLIENT_ADDRESS
  • JMSSERVER_DIRECT_ADDRESS
  • JMSSERVER_QUEUED_ADDRESS
  • SAS_SSL_SERVERAUTH_LISTENER_ADDRESS
  • SOAP_CONNECTOR_ADDRESS

When using wsadmin, not all endpoints are created. There are three options when creating an Application Server with wsadmin. All options result in the creation of the same four of eight endpoints.

Use the following for examples in this technote:

Replace: With:
Cell_Name your Cell Name
Host_Name your Host Name
Node_Name your Node Name
server1 the server you want to use as your template
new_server_name the name of the new server you are creating
EP_Name the endpoint name you are wanting to create
ENTER indicates the end of the command where you press Enter to process the command

Creating an Application Server

wsadmin createUsingTemplate option
Use the "wsadmin createUsingTemplate" option to create the new Application Server from an existing Application Server.

Example:
set nodeid [$AdminConfig getid /Node:Node_Name/] ENTER
set template [$AdminConfig getid /Node:Node_Name/Server:server1/] ENTER
$AdminConfig createUsingTemplate Server $nodeid {{new_server_name}} ENTER
$template ENTER
$AdminConfig save ENTER

Resulting endpoints:
  • BOOTSTRAP_ADDRESS
  • JMSSERVER_DIRECT_ADDRESS
  • JMSSERVER_QUEUED_ADDRESS
  • SOAP_CONNECTOR_ADDRESS

wsadmin createUsingTemplate using listTemplates option
Use "wsadmin createUsingTemplate using listTemplates" to create a new Application Server from an existing Application Server and specify the specific Application Server's template.

Example:
set nodeid [$AdminConfig getid /Node:Node_Name] ENTER
set template [ $AdminConfig listTemplates Server server1 ] ENTER
$AdminConfig createUsingTemplate Server $nodeid {{new_server_name}} ENTER
$template ENTER
$AdminConfig save ENTER

Resulting endpoints:
  • BOOTSTRAP_ADDRESS
  • JMSSERVER_DIRECT_ADDRESS
  • JMSSERVER_QUEUED_ADDRESS
  • SOAP_CONNECTOR_ADDRESS

wsadmin create option
This option uses the "wsadmin create" where you are not using an existing Application Server as a template.

Example:
set nodeid [$AdminConfig getid /Node:Node_Name/] ENTER
$AdminConfig create Server $nodeid {{new_server_name}} ENTER
$AdminConfig save ENTER

Resulting endpoints:
  • BOOTSTRAP_ADDRESS
  • JMSSERVER_DIRECT_ADDRESS
  • JMSSERVER_QUEUED_ADDRESS
  • SOAP_CONNECTOR_ADDRESS

Security

If your environment has security enabled you must manually create the four SSL endpoints by using one of two possible options.


Create the endpoints using the administrative console
The location for SSL endpoints is at each server. The following port names are defined in the End Points panel and are used for object request broker (ORB) security:

  • CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS - CSIv2 Client Authentication SSL Port
  • CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS - CSIv2 SSL Port
  • SAS_SSL_SERVERAUTH_LISTENER_ADDRESS - SAS SSL Port
  • ORB_LISTENER_PORT - TCP/IP Port

The End Points panel displays for the specified server. For a node agent:
  1. Go to System Administration > Node Agents > node_name
  2. Under Additional Properties, click End Points.
    The end points for the node agent and deployment manager already are fixed. However, it might be necessary to reassign the ports to avoid conflict.
  3. For the deployment manager, click System Administration > Deployment Manager.
  4. Under Additional Properties, click End Points.

For more information, refer to the Information Center.

Create the endpoints via wsadmin
Create the new endpoint entries into the serverindex.xml file for the server created with wsadmin. The following is only three entries because in this example, the lines wrap. Each line ends with the ENTER to help clarify where the line ends.

Example:
set se [$AdminConfig getid /ServerIndex:/ServerEntry:/] new_server_name(cells/Cell_Name/nodes/Node_Name:serverindex.xml#ServerEntry_1) ENTER
$AdminConfig create NamedEndPoint $se {{endPointName EP_Name}
{endPoint {{host Host_Name} {port 7777}}}} ENTER
$AdminConfig save ENTER

Notes
  • The port 7777 is only an example, select an available port number.
  • wsadmin commands will need to be repeated for each of the four SSL endpoints.
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Administrative Console (all non-scripting)
Operating system(s): Windows
Software version: 5.0
Software edition:
Reference #: 1175270
IBM Group: Software Group
Modified date: Jul 27, 2004