Starting and stopping Websphere express

Orb Data - TWS and WebSphere

TWS and TDWC eWAS Start, Stop and Status Commands

The twsuser is the user used to install (execute) TWS, probably maestro or twsuser.

$TWS_HOME is the installation directory for TWS, by default this is /opt/ibm/TWA/TWS. $TDWC_HOME is the installation directory for TDWC, by default this is $TWS_HOME/../TDWC

Start command (run as twsuser user)

StartUp script now starts eWAS by default, if -appsrv is specified it is ignored.

conman startappserver

or

$TWS_HOME/../wastools/startWas.sh

or (run as root user)

$TWS_HOME/../eWAS/profiles/twaprofile/bin/startServer.sh twaserver

Stop command (run as twsuser user)

conman stopappserver

or

$TWS_HOME/../wastools/stopWas.sh

or (run as root user)

$TWS_HOME/../eWAS/profiles/twaprofile/bin/stopServer.sh twaserver 
			-user twsuser -password twsuser

Using the conman commands to start and stop eWAS does not require specification of a user and password. To enable stopping of eWAS using the eWAS scripts without specifying user and password see later in the article.

Status command (run as twsuser user)

To check if the eWAS server is currently executing use the command below

$TWS_HOME/../eWAS/profiles/twaprofile/bin/serverStatus.sh twaserver 
			-user twsuser -password twsuser

			

Configuring WAS instances to start and stop without specifying a user and password

The WebSphere instances need to have a user and password specified when certain actions are performed, usually when stopping or verifying the status of the application server. The IBM Redbook Getting Started with IBM Tivoli Workload Scheduler V8.3 (SG24-7237-00) provides a solution for achieving this for the TWS 8.3 embedded application server.

Using this same technique, it is possible to configure the TDWC instance of WAS in the same way. The most important consideration when making these configuration changes is to ensure that you are editing the files for the correct instance of WebSphere. Use the information in the previous sections of this article to determine the WebSphere instance that you want to configure.

To supress the requirement for user and password on the WebSphere scripts for starting, stopping, etc. you need to edit the properties file for the specific WebSphere instance. Using the path as determined by the previous sections of this article, change to the WAS instance properties directory. The table below lists the default directories based upon the TWS version and WAS function.

Version	WAS	Path to properties directory
8.3	embedded	$TWS_HOME/appserver/profiles/twsprofile/properties
	TDWC	$TDWC_HOME/AppServer/profiles/tdwcserver/properties
8.4	embedded	$TWS_HOME/appserver/profiles/twsprofile/properties
	TDWC	$TDWC_HOME/AppServer/profiles/tdwcserver/properties
8.5	both	$TWS_HOME/../eWAS/profiles/twaprofile/properties

Before starting this procedure, ensure that you have stopped the WebSphere instance using the appropriate command from the earlier sections.

From a shell command prompt, change into the WAS properties directory and make a backup of the files we are about to modify in case we encounter problems. Use the commands shown below to copy the files.

cp -p sas.client.props sas.client.props.original
cp -p soap.client.props soap.client.props.original

Edit the sas.client.props file using your favourite editor and locate the following lines in the file.

com.ibm.CORBA.loginSource=prompt # RMI/IIOP user identity com.ibm.CORBA.loginUserid= com.ibm.CORBA.loginPassword=

Change the lines to the following, specifying the appropriate user (as identified in the earlier sections) and the password for that user. After completing the updates we will encrypt the password prior to it being used.

com.ibm.CORBA.loginSource=properties # RMI/IIOP user identity com.ibm.CORBA.loginUserid=twsuser com.ibm.CORBA.loginPassword=orbdata

Save the changes to the file. Now open the file soap.client.props in your favourite editor and locate the lines shown below.

com.ibm.SOAP.securityEnabled=false com.ibm.SOAP.loginUserid= com.ibm.SOAP.loginPassword=

Change the lines to the following, specifying the appropriate user (as identified in the earlier sections) and the password for that user. After completing the updates we will encrypt the password prior to it being used.

com.ibm.SOAP.securityEnabled=false com.ibm.SOAP.loginUserid=twsuser com.ibm.SOAP.loginPassword=orbdata

Save the changes to the file. For TWS 8.5 the changes to the soap.client.props file were already present (with the password already encrypted).

Encrypting the password in the properties files

The method to encrypt the password in the properties files varies depending upon the WAS instance and the version of TWS being used. TWS supplies a utility script (encryptProfileProperties.sh) to encrypt the password fields of the properties files for the embedded WAS application server, but not for the TDWC WebSphere instance. Consequently, for the TDWC 8.3 or 8.4 the individual property files will need to be encrpyted using the command line WebSphere utility PropFilePasswordEncoder.sh. If you are using the common embedded eWAS instance for TWS and TDWC in 8.5 the encryptProfileProperties.sh script will be sufficient. If you have installed TDWC 8.5 in a separate WAS instance you will need to use the PropFilePasswordEncoder.sh script instead.

encryptProfileProperties.sh

The encryptProfileProperties.sh script can be found in the $TWS_HOME/wastools directory. The script must be executed as root user and does not require any parameters. It can be executed as shown below.

Version	Command
8.3/8.4	$TWS_HOME/wastools/encryptProfileProperties.sh
8.5	$TWS_HOME/../wastools/encryptProfileProperties.sh

You will receive output similar to that shown below.

[root@linkwood properties]# /opt/ibm/TWA/wastools/encryptProfileProperties.sh NOTE: all specified passwords already encoded in target file == /opt/ibm/TWA/eWAS/profiles/twaprofile/properties/sas.stdclient.properties NOTE: all specified passwords already encoded in target file == /opt/ibm/TWA/eWAS/profiles/twaprofile/properties/sas.tools.properties [root@linkwood properties]#

Make sure that the files listed are NOT the files you have just edited!

PropFilePasswordEncoder.sh

The PropFilePasswordEncoder.sh script can be found in the $TDWC_HOME/AppServer/bin directory. The script must be executed as root user once for each file containing a password to encrypt. It should be executed as shown below.

Version	Command
8.3/8.4	$TDWC_HOME/AppServer/bin/PropFilePasswordEncoder.sh <path_to_properties_file>/soap.client.props com.ibm.SOAP.loginPassword
	$TDWC_HOME/AppServer/bin/PropFilePasswordEncoder.sh <path_to_properties_file>/sas.client.props -SAS
8.5	$TDWC_HOME/../eWAS/bin/PropFilePasswordEncoder.sh <path_to_properties_file>/soap.client.props com.ibm.SOAP.loginPassword
	$TDWC_HOME/../eWAS/bin/PropFilePasswordEncoder.sh <path_to_properties_file>/sas.client.props -SAS

You will not receive any output from the command unless there is an error. If you receive output similar to that shown below, the password is already encrypted in the properties file.

[root@linkwood properties]# /opt/ibm/TWA/eWAS/bin/PropFilePasswordEncoder.sh soap.client.props com.ibm.SOAP.loginPassword NOTE: all specified passwords already encoded in target file == /opt/ibm/TWA/eWAS/profiles/twaprofile/properties/soap.client.props

All of the above information was taken during testing for this article using TWS/TDWC versions 8.3, 8.4 and 8.5 running on Linux x86 and x64.

Etc

Society

Groupthink : Two Party System as Polyarchy : Corruption of Regulators : Bureaucracies : Understanding Micromanagers and Control Freaks : Toxic Managers :   Harvard Mafia : Diplomatic Communication : Surviving a Bad Performance Review : Insufficient Retirement Funds as Immanent Problem of Neoliberal Regime : PseudoScience : Who Rules America : Neoliberalism  : The Iron Law of Oligarchy : Libertarian Philosophy

Quotes

War and Peace : Skeptical Finance : John Kenneth Galbraith :Talleyrand : Oscar Wilde : Otto Von Bismarck : Keynes : George Carlin : Skeptics : Propaganda  : SE quotes : Language Design and Programming Quotes : Random IT-related quotes :  Somerset Maugham : Marcus Aurelius : Kurt Vonnegut : Eric Hoffer : Winston Churchill : Napoleon Bonaparte : Ambrose Bierce :  Bernard Shaw : Mark Twain Quotes

Bulletin:

Vol 25, No.12 (December, 2013) Rational Fools vs. Efficient Crooks The efficient markets hypothesis : Political Skeptic Bulletin, 2013 : Unemployment Bulletin, 2010 :  Vol 23, No.10 (October, 2011) An observation about corporate security departments : Slightly Skeptical Euromaydan Chronicles, June 2014 : Greenspan legacy bulletin, 2008 : Vol 25, No.10 (October, 2013) Cryptolocker Trojan (Win32/Crilock.A) : Vol 25, No.08 (August, 2013) Cloud providers as intelligence collection hubs : Financial Humor Bulletin, 2010 : Inequality Bulletin, 2009 : Financial Humor Bulletin, 2008 : Copyleft Problems Bulletin, 2004 : Financial Humor Bulletin, 2011 : Energy Bulletin, 2010 : Malware Protection Bulletin, 2010 : Vol 26, No.1 (January, 2013) Object-Oriented Cult : Political Skeptic Bulletin, 2011 : Vol 23, No.11 (November, 2011) Softpanorama classification of sysadmin horror stories : Vol 25, No.05 (May, 2013) Corporate bullshit as a communication method  : Vol 25, No.06 (June, 2013) A Note on the Relationship of Brooks Law and Conway Law

History:

Fifty glorious years (1950-2000): the triumph of the US computer engineering : Donald Knuth : TAoCP and its Influence of Computer Science : Richard Stallman : Linus Torvalds  : Larry Wall  : John K. Ousterhout : CTSS : Multix OS Unix History : Unix shell history : VI editor : History of pipes concept : Solaris : MS DOS :  Programming Languages History : PL/1 : Simula 67 : C : History of GCC development :  Scripting Languages : Perl history   : OS History : Mail : DNS : SSH : CPU Instruction Sets : SPARC systems 1987-2006 : Norton Commander : Norton Utilities : Norton Ghost : Frontpage history : Malware Defense History : GNU Screen : OSS early history

Classic books:

The Peter Principle : Parkinson Law : 1984 : The Mythical Man-Month :  How to Solve It by George Polya : The Art of Computer Programming : The Elements of Programming Style : The Unix Hater’s Handbook : The Jargon file : The True Believer : Programming Pearls : The Good Soldier Svejk : The Power Elite

Most popular humor pages:

Manifest of the Softpanorama IT Slacker Society : Ten Commandments of the IT Slackers Society : Computer Humor Collection : BSD Logo Story : The Cuckoo's Egg : IT Slang : C++ Humor : ARE YOU A BBS ADDICT? : The Perl Purity Test : Object oriented programmers of all nations : Financial Humor : Financial Humor Bulletin, 2008 : Financial Humor Bulletin, 2010 : The Most Comprehensive Collection of Editor-related Humor : Programming Language Humor : Goldman Sachs related humor : Greenspan humor : C Humor : Scripting Humor : Real Programmers Humor : Web Humor : GPL-related Humor : OFM Humor : Politically Incorrect Humor : IDS Humor : "Linux Sucks" Humor : Russian Musical Humor : Best Russian Programmer Humor : Microsoft plans to buy Catholic Church : Richard Stallman Related Humor : Admin Humor : Perl-related Humor : Linus Torvalds Related humor : PseudoScience Related Humor : Networking Humor : Shell Humor : Financial Humor Bulletin, 2011 : Financial Humor Bulletin, 2012 : Financial Humor Bulletin, 2013 : Java Humor : Software Engineering Humor : Sun Solaris Related Humor : Education Humor : IBM Humor : Assembler-related Humor : VIM Humor : Computer Viruses Humor : Bright tomorrow is rescheduled to a day after tomorrow : Classic Computer Humor

The Last but not Least Technology is dominated by two types of people: those who understand what they do not manage and those who manage what they do not understand ~Archibald Putt. Ph.D

The statements, views and opinions presented on this web page are those of the author (or referenced source) and are not endorsed by, nor do they necessarily reflect, the opinions of the Softpanorama society. We do not warrant the correctness of the information provided or its fitness for any purpose. The site uses AdSense so you need to be aware of Google privacy policy. You you do not want to be tracked by Google please disable Javascript for this site. This site is perfectly usable without Javascript.

Last modified: March 12, 2019