Getting background information on wsadmin
- wsadmin scripting environment
The wsadmin tool contains facilities so that you can manage
and customize the scripting environment. The wsadmin launcher
utility is used to launch a scripting process.
- For Windows® platforms:
- For UNIX® platforms
This launch utility accepts arguments to specify the scripting language,
any properties files to read, any profiles to execute, connection
information, and optionally the name of a script to execute. Instead of
entering a large amount of information at the command line when invoking
wsadmin (especially if it is static information) you can specify
information in a property file.
- Property files
There are four levels of property files used by wsadmin:
- System:
Located by $WAS_HOME
- User:
Located by Java™ system property user.home
- Environment Variable:
Governed by environment variable WSADMIN_PROPERTIES
- Invocation:
Located by the -p option on the command line
- Starting wsadmin
- Interactive
- -f (from a script file)
- -c (from command line)
- -profile (loads more than 1 script file)
- -conntype NONE (local mode)
- There are 3 ways to connect to
myServer
- Edit the wsadmin.properties file to reflect myServer
information:
com.ibm.ws.scripting.connectionType=SOAP
com.ibm.ws.scripting.port=myServer_SOAP_PORT
com.ibm.ws.scripting.host=myServer_hostName |
|
- Create new properties (for example,
myserver.properties and use the -p
option):
profile_root\bin>
wsadmin -p myserver.properties |
|
- Use the -port option:
profile_root\bin>
wsadmin -port myServer_SOAP_PORT |
|