…on WebLogic Server 9.x.

Rough notes…

Steps to Configure SSL:

user@server$ keytool -v -list -keystore servername.jks
Enter keystore password:

***************** WARNING WARNING WARNING *****************

* The integrity of the information stored in your keystore *

* has NOT been verified! In order to verify its integrity, *

* you must provide your keystore password. *

***************** WARNING WARNING WARNING *****************

Keystore type: jks

Keystore provider: SUN

Your keystore contains 1 entry

Alias name: servernamekey

Creation date: Apr 21, 2009

Entry type: keyEntry

Certificate chain length: 1


Owner: CN=servername.domain.com, OU=FINANCE, O=ATT, L=Alpharetta,
ST=Georgia, C=US

Issuer: CN=servername.domain.com, OU=FINANCE, O=ATT, L=Alpharetta,
ST=Georgia, C=US

Serial number: 55ste04k

Valid from: Tue Apr 21 10:03:27 CDT 2009 until: Fri Apr 19 10:03:27 CDT

Certificate fingerprints:

MD5: 34:84:26:a7:20:ad:38:80:75:J4:35:70:55:02:28:2d





Creating trustkeystore:


user@server$ cp servername.jks servername-trust.jks

user@server$ keytool -v -export -alias servernamekey -keystore
servername-trust.jks -file servername-trustcert.pem -storepass The$ecretPaS$w0rd
-keypass The$ecretPaS$w0rd

Certificate stored in file


user@server$ keytool -v -import -keystore servername-trust.jks
-storepass The$ecretPaS$w0rd -alias trustedcert -trustcacerts -file

Certificate already exists in keystore under alias

Do you still want to add it? [no]: yes

Certificate was added to keystore

[Saving servername-trust.jks]

user@server$ rm servername-trustcert.pem

Change server configuration to:

(beahome/weblogicserverhome/server/lib/servername-trust.jks) same pwd

Turn off hostname verifier


Configure NM:



** This is a one time configuration:



If above step fails, you will need to enable ssl debug flags and sort
out SSL issues before proceeding.

Ensure WLST NM connectivity:


- Start Admin server from command line for first time only

- Connect to admin:


** This is a one time configuration:

wls:/dev_domain/serverConfig> nmGenBootStartupProps('Admin_Server')

Successfully generated boot.properties at

Successfully generated startup.properties at


Change Username to lower 'u' as username

Change Password to lower 'p' as password

Kill admin server.

(NM can check status/start/stop only those servers that were started by

If you run into issues, Kill NM java process before killing the server
process. Otherwise, NM will immediately spawn the server process
everytime you kill the server java process.

Restart NM each time you change nodemanager.properties.)




---------------------------- end -----------------------------------

N.B: For each managed server, you have to do a one time process of
generating boot.properties and startup properties.




nmGenBootStartupProps('mgserver2') etc.,

wls:/dev_domain/serverConfig>storeUserConfig('beahome/weblogicserverhome/domains/dev_domain/servers/ss/data/nodemanager/configfile.secure', 'beahome/weblogicserverhome/domains/dev_domain/servers/ss/data/nodemanager/keyfile.secure')
wls:/testdomain/serverConfig>storeUserConfig('/usr/home/user1/configfile.secure', '/usr/home/user1/keyfile.secure')

wls:/offline> connect('weblogic_administrator','An0th3r$ecr3tPaS$w0rd','t3://servername.domain.com:7001')
Connecting to t3://servername.domain.com:7001 with userid weblogic_administrator ...
Successfully connected to Admin Server 'Admin_Server' that belongs to domain 'dev_domain'.

…the scientific consideration of the line of moons along Jupiter that can be seen well in this image. It is interesting Mr. Galilei described the device he invented to observe the truth of planetary motion as a secret weapon for the protection of the state (pun intended).

APOD: 2009 July 14 – Moons and Jupiter
the exposure captures Jupiter’s own Galilean moons lower right as tiny pinpricks of light, lined up and hugging both sides of the solar system’s ruling gas giant

and produces fascinating footage; Easy access via YouTube. I love the Earth rising over the grey, acne-dimpled moon-horizon.

<object width="425" height="344"><param name="movie" value="http://www.youtube.com/v/kcpjWCIQHEE&color1=0xb1b1b1&color2=0xcfcfcf&feature=player_embedded&fs=1"></param><param name="allowFullScreen" value="true"></param><param name="allowScriptAccess" value="always"></param><embed src="&color1=0xb1b1b1&color2=0xcfcfcf&feature=player_embedded&fs=1" type="application/x-shockwave-flash" allowfullscreen="true" allowScriptAccess="always" width="425" height="344"></embed></object>

APOD: 2009 June 29 – Kaguya Spacecraft Crashes into the Moon

Google Chrome OS

20090709, 28

There is some discussion about the operating system from Google; While a windowing system on a Linux kernel may not seem like much to the tech folks, end-users won’t likely know what a windowing system is. Furthermore, the windowing system will  distance them so much from the kernel they will never gain familiarity with it either. They will just get a computer that works, doesn’t break, doesn’t need updates and repairs, and is probably pretty much enormously more cost-efficient for all the things they find themselves doing with a computer.

No matter the operating system, people and communities need flat-rate unrestricted access and bandwidth to innovate and drive economic success going forward.

By the way, I read somewhere Microsoft did not use its anti-competitive strategies against Apple because eliminating even the illusion of competition would have isolated them as the monopoly that they were (are?). Choice is good; Even if we are unlikely to see large companies dump Windows at any time in the near future, a third OS from a market leader provides that most illusive thing–hope!

Google Drops a Bomb: Its Own Operating System | Technomix | Fast Company
Mere hours ago, Google did something that’s pretty surprising, and that will impact the netbook, and maybe PC market: It announced its own operating system, Chrome. It’s open source.

During installation on 2.6.24-24-generic (Ubuntu 8.04 LTS), the VMware-server-2.0.1 asks for a user.
I was running sudo ./vmware-install.pl and it would not accept my Ubuntu login which happens to be one lower-case letter.
I used root as the username, so that the installation would complete.
Of course, I have no interest in actually using root to log in to a web app, nor in creating a password for root–this is Ubuntu!
Upon successful completion I tried to login to the https://localhost:8333/ and it did not allow root to login without a password.
no worries:

Google’s cache of http://www.tipandtrick.net/2008/whats-the-login-user-name-and-password-for-vmware-server-20/ provided the following solution from WillBeen, comment: May 20th, 2009 04:21
sudo vi /etc/vmware/hostd/authorization.xml
edit line 8: <ACEDataUser>x</ACEDataUser>

change x (your username)
to your preferred user

I had to reboot
then tell Firefox to accept the self-signed cert…
Now it is time to see if VMWare Server will let me import and run my virtual machines.