WebSphere 8 on Windows as Standard User

While I doubt this is supported usage, I had a goal of using MyEclipse Bling (MyEclipse Blue combined with MyEclipse for Spring), along with IBM WebSphere Application Server v8 on Windows 7 as a standard user.

Here's what I did:

• Install WebSphere 8 and MyEclipse Bling


• Grant users full control of the AppServer directory


• Create a WebSphere profile however you prefer


• Open the command prompt as an admin to create a service for the profile


• 'cd' to your WAS home bin (e.x. cd C:\IBM\WebSphere\AppServer\bin)


• WASService.exe -add AppSrv01 -serverName server1 -profilePath C:\IBM\WebSphere\AppServer\profiles\AppSrv01 -startType manual (replace AppSrv01 and the profile path with yours of course)


• Download SetACL


• Open Services, right click your WAS service and click properties. In Path to executable copy the actual name of the service (e.x. "IBMWAS80Service - AppSrv01")


• In the command prompt: SetACL.exe -on "IBMWAS80Service - AppSrv01" -ot srv -actn ace -ace "n:S-1-1-0;p:full;s:y;i:np;m:grant;w:dacl"

The n: part you define the SID of the user you want to grant access. S-1-1-0 is the SID for everyone.

At this point, WAS starts just fine when a standard user starts it via services management, however by using WASService -start (which MyEclipse Blue uses) it still does not work. Update soon when I figure it out.

Local WebSphere Message Broker Maintenance on Windows Domain

As a follow-up to http://craigstjean.blogspot.com/2011/03/local-websphere-message-broker-install.html, here are some maintenance tips:

After changing your domain password:

1. Change your local Windows user password to be the same
2. Open the ODBC Control Panel and update your user in the System DSN
3. Open the Broker Command Console and type:
   mqsichangebroker -i -a -p

Local WebSphere Message Broker Install on Windows Domain

After having a lot of difficulty setting up a local WMQ and WMB install on my domain account, here is what I did:

• Install MQ and its fixpacks


• Install WMB runtime and its fixpacks


• Install the Broker Toolkit


• Created a local Windows user with the same username/password as my domain user


• Add user to mqbrkrs and mqm groups


• Install latest DB2 Express


• Start the broker command console

MQSI 6.1.0.5
C:\IBM\MQSI\6.1
Start broker Command Console

C:\IBM\MQSI\6.1>cd c:\IBM\WMQ\bin

c:\IBM\WMQ\bin>crtmqm.exe -u DLQ ESBBKL
WebSphere MQ queue manager created.
Creating or replacing default objects for ESBBKL.
Default objects statistics : 43 created. 0 replaced. 0 failed.
Completing setup.
Setup completed.

c:\IBM\WMQ\bin>strmqm ESBBKL
WebSphere MQ queue manager 'ESBBKL' starting.
5 log records accessed on queue manager 'ESBBKL' during the log replay phase.
Log replay for queue manager 'ESBBKL' complete.
Transaction manager state recovered for queue manager 'ESBBKL'.
WebSphere MQ queue manager 'ESBBKL' started.

c:\IBM\WMQ\bin>call mqsicreatedb ESBBKLDB -e DB2
BIP9809I: Creating DB2 Database 'ESBBKLDB', this may take a while.
BIP9825I: Creating the ODBC Data Source name 'ESBBKLDB'.
BIP9817I: The DB2 database engine was used to create the 'ESBBKLDB' database.

BIP8071I: Successful command completion.

c:\IBM\WMQ\bin>call mqsicreateconfigmgr ESBBKL_CFGMGR -i <USERNAME> -a <PASSWORD> -q ESBBKL
AMQ8110: WebSphere MQ queue manager already exists.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
BIP8071I: Successful command completion.

c:\IBM\WMQ\bin>call mqsicreatebroker ESBBKLBKR -i <USERNAME> -a <PASSWORD> -q ESBBKL -n ESBBKLDB
AMQ8110: WebSphere MQ queue manager already exis
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
BIP8071I: Successful command completion.

c:\IBM\WMQ\bin>call mqsistart ESBBKL_CFGMGR
BIP8096I: Successful command initiation, check the system log to ensure that the component started without problem and that it continues to run without problem.

c:\IBM\WMQ\bin>call mqsistart ESBBKLBKR
BIP8096I: Successful command initiation, check the system log to ensure that the component started without problem and that it continues to run without problem.

• Open MQ Explorer


• Create new queue named DLQ in ESBBKL


• Create new TCP Listener (I used port 1414, the default)


• In the toolkit, add new Domain Connection to ESBBKL port 1414 on localhost


• Connect to the new Domain


• Add new broker reference to the topology, ESBBKLBKR on ESBBKL


• Enjoy!

Note: if you want to delete and start over, do NOT delete the database first. If you do, call mqsicreatedb again, then use mqsichangebroker and set your username and password again.

The steps I follow to delete are:

• Start broker command console and cd c:\IBM\WMQ\bin


• call mqsistop ESBBKLBKR


• call mqsideletebroker ESBBKLBKR


• call mqsistop ESBBKL_CFGMGR


• call mqsideleteconfigmgr -w -q ESBBKL_CFGMGR


• call mqsideletedb -d DeleteAllDatabases