27 Feb

How the Start or Stop a IBM Websphere Profile

Using: WAS 6.1, Eclipse 2.31.1, Windows XP


Start > All Programs > Websphere Installation > Profiles

Start: Select “Start the Server”

Stop: Select “Stop the Server”


Go to: Configure Server

From Servers select Websphere 6.1

Specify Websphere Home Directory, which should point to the “AppServer” location

Specify the required Profile

Specify the Node Name

Press Apply

Press OK

Start: Select “Start”

Stop: Select “Stop”


Start: startServer [serverName] -profile [profileName]

Stop: stopServer [serverName] -profile [profileName]

26 Feb

How to Use WAS profiles to create multiple independent user configurations: IBM Websphere

How to Use WAS profiles to create multiple independent user configurations sharing the same install binaries. This is almost like having multiple servers.

Server: IBM Websphere Application Server 6.1

Tool Used: Use the Profile Management Tool

Note: WAS instances in version 5 are Profiles in v 6

In WAS 6 files are divided into 2 parts Product files and User Data. Hence in order to have multiple instances for different purposed we can have separate User Data sets and these are called as profiles in WAS 6.

By doing this you escape the need of installing multiple servers on the same machine and especially in development environment you can easily control which profile to start (saves lot of resources)

The command is in the following directory:

<was_root>/bin/pmt.sh on UNIX/LINUX

<was_root>binpmt.bat for WINDOIWS

Select “Application Server”

Click “Next”

Select “Advanced Profile Creation”

Don’t Deploy Default Application

Provide an appropriate Name and the default location of the profile

Select the option ” Create the server using development template” if you are not deploying this to a production server and for dev purpose else keep this unchecked.

Give a node name or keep it as it is

Change the Host name to the network name of the server if required

Don’t Select “Enable Administrative Security”

Change the port values as required. (Don’t forget to keep a copy of the port number assigned)

Unselect the “Run the application server process as window service” if you want to have a manual control on the server. As I am using this in development environment I don’t want my server to eat all resources on startup.

Skip this screen

Press “Create”

Select “Launch the first steps console” and verify the profile.

Recommended Reading*

04 Feb

Error on IBM Websphere: SSLHandshakeException, No trusted certificate found

If you are getting an error similiar to the one mentioned below the problem is with the signer as the signer may need to be added to local trust store.

Stack trace: javax.net.ssl.SSLHandshakeException: com.ibm.jsse2.util.h: No trusted certificate found
at com.ibm.jsse2.n.a(n.java:18)
at com.ibm.jsse2.jc.a(jc.java:463)
at com.ibm.jsse2.db.a(db.java:179)
at com.ibm.jsse2.db.a(db.java:107)
at com.ibm.jsse2.eb.a(eb.java:83)
at com.ibm.jsse2.eb.a(eb.java:237)
at com.ibm.jsse2.db.m(db.java:56)
at com.ibm.jsse2.db.a(db.java:174)
at com.ibm.jsse2.jc.a(jc.java:579)
at com.ibm.jsse2.jc.g(jc.java:168)

On WAS 6.1 : SSL certificate and key management > Key stores and certificates > NodeDefaultTrustStore > Signer certificates > Retrieve from port
On WAS 6.0 and below: You will need to run ikeyman to export/ import the signer certificates to the trust store.

Also, set JVM property javax.net.debug=true in order to get more detailed info on the error.