Websphere setupcmdline.sh

AppSrv01 or you can just add a profileName attribute to the wsadmin task. In this case the wsadmin task resolves the profile directory for you, because of the wasHome attribute that you must provide. Before we dive into the analyse we need an example project to reproduce the error. For this we need a simple ant script. The problem arises in step 2 when the wsadmin ant task tries to parse the setupCmdLine. The wsadmin ant task delegates the parsing to the com.

WasUtils class. Create a new application server see To create a new application server. Modify setupCmdLine.

Start a telnet session to the AIX machine. If Siebel Analytics had been previously installed, but is not installed now, you may see an error message when starting WebSphere. If you receive an error message, do the steps listed in To modify setupCmdLine. Start a telnet session to the machine on which WebSphere is installed.

Edit the setupCmdLine. Do this using one of the following methods:. Run the Administration Console through X Window. Remove all Siebel Analytics-related services under the Enterprise Applications folder. Right-click on the Analytics Enterprise and choose Stop. Remove the service. While some of the command line parameters define application-specific information, other parameters provide information about the WebSphere Application Server installation and configuration.

After sourcing this shell script, WebSphere Application Server configuration parameters can be specified on the Java command line using the exported environment variables as follows:. Note that only the command parameters required to start the monitored application are shown above. For more information on developing and launching WebSphere thin client applications including information on other WebSphere thin client parameters that are not described here , refer to the WebSphere Application Server Version 5 InfoCenter documentation located at:.