The wasprofile command line tool creates all Application Server run-time environments in Version 6. The command creates a profile, which is the set of files that define the run-time environment for a stand-alone Application Server.
The wasprofile command is also referred to as the profile creation tool.
The wasprofile command creates the run-time environment for a WebSphere Application Server process in a set of files called a profile. The profile defines the run-time environment and includes all of the files that the server processes in the run-time environment can change. The profile creation tool and its graphical user interface, the Profile creation wizard, are the only ways to create run-time environments in V6.
The Profile creation wizard is an InstallShield for Multiplatforms (ISMP) application. You can use the wizard to enter most of the parameters that are described in this topic. Some parameters, however, require you to use the wasprofile command. You must use the wasprofile command to delete a profile, for instance, because the Profile creation wizard does not provide a deletion function.
However, the Profile creation wizard also performs tasks that the wasprofile command does not. For instance, the wizard can create a Windows service for each profile that it creates. It can also assign non-conflicting ports based on previous Version 6 port assignments.
The wasprofile command line tool defines each Application Server instance of a Version 6 product.
You must run the wizard or the command line tool each time that you want to create a stand-alone Application Server. A need for more than one stand-alone Application Server on a machine is common.
Administration is greatly enhanced when using V6 profiles instead of multiple product installs. Not only is disk space saved, but updating the product is simplified when you only maintain a single set of product core files. Also, creating new profiles is faster and less prone to error than full product installs, allowing a developer to create new disposable profiles of the product for development and testing.
You can run the Profile creation wizard or the profile creation tool to create a new Application Server environment on the same machine as an existing one. Simply define unique characteristics (such as profile name and node name) for the new profile. Each profile has its own administrative console and administrative scripting interface. Each Application Server process shares all run-time scripts, libraries, the Software Development Kit, and other core product files.
The installation program for WebSphere Application Server - Express uses the profile creation tool to create an Application Server profile named default.
/opt/IBM/WebSphere/AppServer/profiles/devhost1Profile01 /opt/IBM/WebSphere/AppServer/profiles/devhost1Profile02
/opt/profiles/devhost1Profile01 /opt/profiles/devhost1Profile02
The profile repository is the default location of profile-related metadata. The repository is the default location for new profiles, which is often referred to as the profiles installation root directory.
/opt/IBM/WebSphere/AppServer/profiles/devhost1Profile01 /opt/IBM/WebSphere/AppServer/profiles/devhost1Profile02
/opt/profiles/devhost1Profile01 /opt/profiles/devhost1Profile02
The command file is located in the install_root/bin directory. The command file is a script named wasprofile.sh for Linux and UNIX platforms or wasprofile.bat for Windows platforms.
The Profile creation wizard is the graphical user interface to the command line tool. The file name of the command that calls the Profile creation wizard varies per operating system platform. See Using the Profile creation wizard for more information.
The wasprofile command creates a log for every profile that it creates. The logs are in the install_root/logs/wasprofile directory. The files are named in this pattern: wasprofile_create_profile_name.log.
The command also creates a log for every profile that it deletes. The logs are in the install_root/logs/wasprofile directory. The files are named in this pattern: wasprofile_delete_profile_name.log.
Manually verify that the required space
for creating a profile is available on AIX. A known problem in the underlying
InstallShield for Multiplatforms (ISMP) code prevents proper space checking
on AIX systems at the time that the product disc was created.
An error can occur when you have not provided enough system temporary space to create a profile. Verify that you have a minimum of 40 MB of temp space available before creating a profile.
You must have 200 MB of available disk space in the directory where you create an Application Server profile.
The length of the wasprofile command can exceed the normal shell window limit for one line of 256 characters. If your command is longer than the limit, issue the command on multiple lines by ending a line with a backward slash, pressing Enter, and continuing the command on the next line.
./wasprofile.sh \ -create -profileName bladetcb6profile \ -profilePath /usr/IBM/WebSphere/AppServer/profiles/bladetcb6profile \ -templatePath /usr/WebSphere/AppServer/profileTemplates/default \ -nodeName bladetcb6node \ -cellName bladetcb6Cell \ -hostName bladetcb6.rtp.raleigh.ibm.com
Omit the line continuation character from the last line to signal the end of the command to the operating system.
# ./wasprofile.sh -help # ./wasprofile.sh -augment -help # ./wasprofile.sh -create -help # ./wasprofile.sh -delete -help # ./wasprofile.sh -getName -help # ./wasprofile.sh -getPath -help # ./wasprofile.sh -unaugment -help # ./wasprofile.sh -validateRegistry -help # ./wasprofile.sh -validateAndUpdateRegistry -help
# ./wasprofile.sh -listProfiles [-debug]
# ./wasprofile.sh -delete -profileName profile_name | -profilePath profile_path [-debug]
wasprofile.sh -create -profileName profile_name -profilePath fully_qualified_profile_path -templatePath template_path -nodeName node_name -cellName cell_name -hostName host_name -serverName server_name [-startingPort starting_port | -portsFile filepath] -winserviceCheck true | false -winserviceAccountType specifieduser | localsystem -winserviceUserName yourusername -winservicePassword yourpassword -winserviceStartupType manual | automatic | disabled [-debug]
# ./wasprofile.sh -getName -profilePath profile_path [-debug]
# ./wasprofile.sh -getPath -profileName profile_name [-debug]
# ./wasprofile.sh -validateRegistry [-debug]
# ./wasprofile.sh -validateAndUpdateRegistry [-backup file_name] [-debug]
wasprofile.sh -augment -profileName profile_name -templatePath fully_qualified_template_path
wasprofile.sh -unaugment -profileName profile_name
# ./wasprofile.bat -help # ./wasprofile.bat -augment -help # ./wasprofile.bat -create -help # ./wasprofile.bat -delete -help # ./wasprofile.bat -getName -help # ./wasprofile.bat -getPath -help # ./wasprofile.bat -unaugment -help # ./wasprofile.bat -validateRegistry -help # ./wasprofile.bat -validateAndUpdateRegistry -help
wasprofile.bat -listProfiles [-debug]
wasprofile.bat -delete -profileName profile_name | -profilePath profile_path [-debug]
wasprofile.bat -create -profileName profile_name -profilePath fully_qualified_profile_path -templatePath template_path -nodeName node_name [-cellName cell_name] -hostName host_name -serverName server_name [-startingPort starting_port | -portsFile filepath] -winserviceCheck true | false -winserviceAccountType specifieduser | localsystem -winserviceUserName yourusername -winservicePassword yourpassword -winserviceStartupType manual | automatic | disabled [-debug]
When the -startingPort parameter is not used, the profile creation tool uses the default port settings specified in the serverindex.xml file.
wasprofile.bat -getName -profilePath fully_qualified_profile_path [-debug]
wasprofile.bat -getPath -profileName profile_name [-debug]
wasprofile.bat -validateRegistry [-debug]
wasprofile.bat -validateAndUpdateRegistry [-backup file_name] [-debug]
wasprofile.bat -augment -profileName profile_name -templatePath fully_qualified_template_path
wasprofile.bat -unaugment -profileName profile_name
When the augment action is invoked, wasprofile attempts to access the actionRegistry.xml file in the specified template path. The operations defined in the Config Actions stanza in the action registry file are then applied against the specified profile.
Specify the fully qualified file path for -templatePath. Specifying a relative file path for the -templatePath parameter results in the specified profile not being fully augmented.
See also the unaugment parameter.
This is an optional parameter for WebSphere Application Server - Express.
If you omit the parameter, a default cell name is assigned.
Do not use this parameter when using the startingPort parameter.
If the fully qualified path contains spaces, enclose
the value in quotation marks.
When the unaugment action is invoked, wasprofile attempts to access the deleteRegistry.xml file in the template path that was specified in the augment command. The operations defined in the Config Actions stanza in the delete registry file are then applied against the specified profile.
Specify the fully qualified file path for -templatePath.
See also the augment parameter.
See WASService command for more information about Windows services.
Use cases are a description of common tasks for which the tool is used.
wasprofile.sh -delete -profileName shasti
When you use the wasprofile tool without the -startingPort parameter, the tool uses the /profileTemplates/profile_type /actions/portsUpdate/bin/portdef.props file to set the initial ports.
Example of using the -portsFile parameter
wasprofile.bat -create -profileName Wow_Profile -profilePath C:\ExpressV6\IBM\WebSphere\AppServer\profiles\Wow_Profile -templatePath C:\ExpressV6\IBM\WebSphere\AppServer\profileTemplates\default -nodeName Wow_node -cellName Wow_cell -hostName loyAllen -portsFile C:\temp\ports\portdef.props
WC_defaulthost=39080 WC_adminhost=39060 WC_defaulthost_secure=39443 WC_adminhost_secure=39043 BOOTSTRAP_ADDRESS=32809 SOAP_CONNECTOR_ADDRESS=38880 SAS_SSL_SERVERAUTH_LISTENER_ADDRESS=39401 CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS=39403 CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS=39402 ORB_LISTENER_ADDRESS=39100 DCS_UNICAST_ADDRESS=39353 SIB_ENDPOINT_ADDRESS=37276 SIB_ENDPOINT_SECURE_ADDRESS=37286 SIB_MQ_ENDPOINT_ADDRESS=35558 SIB_MQ_ENDPOINT_SECURE_ADDRESS=35578
replaceRegExpAllInstancesOfGivenTokenWithGivenValueForTheGivenFile: [echo] File C:\ExpressV6\IBM\WebSphere\AppServer\profiles\ Wow_Profile/config/templates/default/serverentry-template.xml: setting CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS to 39403 ... replaceRegExpAllInstancesOfGivenTokenWithGivenValueForTheGivenFile: [echo] File C:\ExpressV6\IBM\WebSphere\AppServer\profiles\ Wow_Profile/config/templates/default/serverentry-template.xml: setting CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS to 39402 ...
<?xml version="1.0" encoding="UTF-8"?> <serverindex:ServerIndex xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" ... <specialEndpoints xmi:id="NamedEndPoint_..." endPointName="BOOTSTRAP_ADDRESS"> <endPoint xmi:id="EndPoint_..." host="IBMmachine" port="32809"/> </specialEndpoints> <specialEndpoints xmi:id="NamedEndPoint_..." endPointName="SOAP_CONNECTOR_ADDRESS"> <endPoint xmi:id="EndPoint_..." host="IBMmachine" port="38880"/> </specialEndpoints> <specialEndpoints xmi:id="NamedEndPoint_..." endPointName="SAS_SSL_SERVERAUTH_LISTENER_ADDRESS"> <endPoint xmi:id="EndPoint_..." host="IBMmachine" port="39401"/> </specialEndpoints> <specialEndpoints xmi:id="NamedEndPoint_..." endPointName="CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS"> <endPoint xmi:id="EndPoint_..." host="IBMmachine" port="39403"/> </specialEndpoints> <specialEndpoints xmi:id="NamedEndPoint_..." endPointName="CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS"> <endPoint xmi:id="EndPoint_..." host="IBMmachine" port="39402"/> </specialEndpoints> <specialEndpoints xmi:id="NamedEndPoint_..." endPointName="WC_adminhost"> <endPoint xmi:id="EndPoint_..." host="*" port="39060"/> </specialEndpoints> <specialEndpoints xmi:id="NamedEndPoint_..." endPointName="WC_defaulthost"> <endPoint xmi:id="EndPoint_..." host="*" port="39080"/> </specialEndpoints> <specialEndpoints xmi:id="NamedEndPoint_..." endPointName="DCS_UNICAST_ADDRESS"> <endPoint xmi:id="EndPoint_..." host="IBMmachine" port="39353"/> </specialEndpoints> <specialEndpoints xmi:id="NamedEndPoint_..." endPointName="WC_adminhost_secure"> <endPoint xmi:id="EndPoint_..." host="*" port="39043"/> </specialEndpoints> <specialEndpoints xmi:id="NamedEndPoint_..." endPointName="WC_defaulthost_secure"> <endPoint xmi:id="EndPoint_..." host="*" port="39443"/> </specialEndpoints> <specialEndpoints xmi:id="NamedEndPoint_..." endPointName="SIB_ENDPOINT_ADDRESS"> <endPoint xmi:id="EndPoint_..." host="*" port="37276"/> </specialEndpoints> <specialEndpoints xmi:id="NamedEndPoint_..." endPointName="SIB_ENDPOINT_SECURE_ADDRESS"> <endPoint xmi:id="EndPoint_..." host="*" port="37286"/> </specialEndpoints> <specialEndpoints xmi:id="NamedEndPoint_..." endPointName="SIB_MQ_ENDPOINT_ADDRESS"> <endPoint xmi:id="EndPoint_..." host="*" port="35558"/> </specialEndpoints> <specialEndpoints xmi:id="NamedEndPoint_..." endPointName="SIB_MQ_ENDPOINT_SECURE_ADDRESS"> <endPoint xmi:id="EndPoint_..." host="*" port="35578"/> </specialEndpoints> <specialEndpoints xmi:id="NamedEndPoint_..." endPointName="ORB_LISTENER_ADDRESS"> <endPoint xmi:id="EndPoint_..." host="IBMmachine" port="39100"/> </specialEndpoints> </serverEntries> </serverindex:ServerIndex>
The wasprofile command creates a copy of the current portdefs.props file in the install_root\profiles\profile_name\logs directory.
Do not use the portsFile parameter when using the startingPort parameter. The two parameters are mutually exclusive.
The wasprofile command can assign port numbers based on a starting port value that you give on the command line, using the -startingPort parameter. The tool assigns port numbers sequentially from the starting port number value.
The order of port assignments is arbitrary. Predicting assignments is not possible.
For example, ports created with -startingPort 20002 would appear similar to the following example:
Assigned ports for an Application Server profile
WC_defaulthost=20002 WC_adminhost=20003 WC_defaulthost_secure=20004 WC_adminhost_secure=20005 BOOTSTRAP_ADDRESS=20006 SOAP_CONNECTOR_ADDRESS=20007 SAS_SSL_SERVERAUTH_LISTENER_ADDRESS=20008 CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS=20009 CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS=20010 ORB_LISTENER_ADDRESS=20011 DCS_UNICAST_ADDRESS=20012 SIB_ENDPOINT_ADDRESS=20013 SIB_ENDPOINT_SECURE_ADDRESS=20014 SIB_MQ_ENDPOINT_ADDRESS=20015 SIB_MQ_ENDPOINT_SECURE_ADDRESS=20016
Example of startingPort parameter use
wasprofile.bat -create -profileName shasti -profilePath G:\shasti\WebSphere -templatePath template_path -nodeName W2K03 -cellName W2K03_Cell01 -hostName planetnt -startingPort 20002
startServer.sh server1 -profileName Profile02
netstat -a
http://hostname_orIP_address:20003/ibm/console/
./wasprofile.sh -create -profileName profile01 -profilePath install_root/profiles/profile01
chown -R user1 install_root/profiles/profile01
chown -R user1 install_root/logs/wasprofile
mkdir /opt/IBM/WebSphere/AppServer/logs/wasprofile
chgrp profilers /opt/IBM/WebSphere/AppServer/logs/wasprofile chmod g+wr /opt/IBM/WebSphere/AppServer/logs/wasprofile chgrp profilers /opt/IBM/WebSphere/AppServer/properties chmod g+wr /opt/IBM/WebSphere/AppServer/properties chgrp profilers /opt/IBM/WebSphere/AppServer/properties/fsdb chmod g+wr /opt/IBM/WebSphere/AppServer/properties/fsdb chgrp profilers /opt/IBM/WebSphere/AppServer/properties/profileRegistry.xml chmod g+wr /opt/IBM/WebSphere/AppServer/properties/profileRegistry.xml
You might have to change the permissions on additional /opt/IBM/WebSphere/AppServer directories if you encounter permission problems.
If the non-root user does not have write access to any directories, it is up to the root user to change that situation. If the non-root user does not have write access to the /tmp directory, it is up to the root user to change that as well.
The commands listed in step 6 give users assigned to the profilers group the ability to write to the /opt/IBM/WebSphere/AppServer/logs/wasprofile directory and to the /opt/IBM/WebSphere/AppServer/properties directory. It is not necessary to write to any other directories in the installation root of your WebSphere Application Server product.
Have non-root users create a profiles directory in their own area, not in the installation root directory of the product.
Related tasks
Using the Profile creation wizard
Deleting a profile