WAS v8.5 > Script the application serving environment (wsadmin) > Use properties files to manage system configuration > Manage specific configuration objects using properties files > Work with server properties files

Work with end point properties file

We can use properties files to change the end points of a server.

Determine the changes to make to your end point configuration.

Start the wsadmin scripting tool. To start wsadmin using the Jython language, run the wsadmin -lang jython command from the bin directory of the server profile. Using a properties file, we can modify end point properties.

Run administrative commands using wsadmin to extract a properties file for an end point, validate the properties, and apply them to your configuration.

Actions for end point properties files. We can modify end point properties.

Action	Procedure
create	Not available
modify	Edit properties and then run the applyConfigProperties command.
delete	Not available

Optionally, we can use interactive mode with the commands:

AdminTask.command_name('-interactive')

1. Edit end point properties under a server.

   Open an editor on a properties file. Example properties for an EndPoint under a server follow. The example specifies three different host names in the Environment Variables section: myHostName,* and localhost. We can copy the example properties into an editor and modify them as needed for the situation.

   #
   # Header
   #
   ResourceType=EndPoint
   ImplementingResourceType=Server
   ResourceId=Cell=!{cellName}:Node=!{nodeName}:Server=!{serverName}
   #
   #
   #Properties
   #
   SOAP_CONNECTOR_ADDRESS=8888:!{hostName} # integer 
   SIP_DEFAULTHOST_SECURE=5067:!{hostName1} # integer 
   SIP_DEFAULTHOST=5066:!{hostName1} # integer 
   SIB_ENDPOINT_ADDRESS=7283:!{hostName1} # integer 
   WC_defaulthost_secure=9447:!{hostName1} # integer 
   DCS_UNICAST_ADDRESS=9364:!{hostName1} # integer 
   SIB_MQ_ENDPOINT_SECURE_ADDRESS=5582:!{hostName1} # integer 
   WC_adminhost_secure=9052:!{hostName1} # integer 
   CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS=9424:!{hostName} # integer 
   ORB_LISTENER_ADDRESS=0:!{hostName} # integer 
   BOOTSTRAP_ADDRESS=2813:!{hostName} # integer 
   CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS=9423:!{hostName} # integer 
   IPC_CONNECTOR_ADDRESS=9634:!{hostName2} # integer 
   SIB_ENDPOINT_SECURE_ADDRESS=7291:!{hostName1} # integer 
   WC_defaulthost=9084:!{hostName1} # integer 
   SIB_MQ_ENDPOINT_ADDRESS=5562:!{hostName1} # integer 
   SAS_SSL_SERVERAUTH_LISTENER_ADDRESS=9422:!{hostName} # integer 
   WC_adminhost=9069:!{hostName1} # integer
   #
   EnvironmentVariablesSection
   #
   #Environment Variables
   hostName2=localhost
   hostName1=*
   hostName=myHostName
   cellName=WASCell06
   serverName=myServer
   nodeName=WASNode04

2. Run the applyConfigProperties command.

   Running the applyConfigProperties command applies the properties file to the configuration. In this Jython example, the optional -reportFileName parameter produces a report named report.txt:

   AdminTask.applyConfigProperties(['-propertiesFileName myObjectType.props -reportFileName report.txt'])

Results

We can use the properties file to manage the end point properties.

Save the changes to your configuration.

Related

Extracting properties files using wsadmin.sh
Create server, cluster, application, or authorization group objects using properties files and wsadmin scripting
Delete server, cluster, application, or authorization group objects using properties files

Reference:

PropertiesBasedConfiguration command group for AdminTask using wsadmin.sh

+

Search Tips   |   Advanced Search