Author |
Message
|
Trugga |
Posted: Wed Apr 12, 2006 2:49 am Post subject: SOLVED - V6 Message Broker Toolkit - New M.S.Project missing |
|
|
Novice
Joined: 30 Mar 2006 Posts: 15 Location: West Midlands (UK)
|
Having recently installed MQ V6, I have finally got round to creating a first project on a Windows 2000 test machine.
Having created a Message Flow Project, I now need to create a Message Set Project but that option does not exist, either on the File-New menu or the right-click in the Resource Navigator.
From the Message Borker Toolkit V6 installation Launchpad, all 5 express installation tasks show as installed, on the Advanced Installtion option, I do not have Rational Agent Controller, Sybase or MS SQL 2000 installed.
MS Windows 2000 SP4
IBM Websphere Eclipse Platform 3.0
IBM Websphere Message Broker 6.0
IBM Websphere Message Broker Toolkit 6.0.0.1
IBM Websphere MQ
DB2 Enterprise Server Edition
I have another Windows 2000 machine with the above installed (by a contractor who has since left) and that machine has the New Message Set Project option.
Any help or pointers would be appreciated.
Lawrence
[edited to include "SOLVED" in the topic title]
Last edited by Trugga on Wed Apr 19, 2006 2:28 am; edited 1 time in total |
|
Back to top |
|
 |
wschutz |
Posted: Wed Apr 12, 2006 3:20 am Post subject: |
|
|
 Jedi Knight
Joined: 02 Jun 2005 Posts: 3316 Location: IBM (retired)
|
What happens if you do CTRL+N and then expand "Message Brokers", what do you see? _________________ -wayne |
|
Back to top |
|
 |
Trugga |
Posted: Wed Apr 12, 2006 4:49 am Post subject: |
|
|
Novice
Joined: 30 Mar 2006 Posts: 15 Location: West Midlands (UK)
|
wschutz wrote: |
What happens if you do CTRL+N and then expand "Message Brokers", what do you see? |
Children of Message Brokers are:Broker Schema
Engueue Message File
Message Broker Archive
Message Flow
Message Flow Project
RDB Definition Files
Does that help ?
Lawrence |
|
Back to top |
|
 |
wschutz |
Posted: Wed Apr 12, 2006 5:22 am Post subject: |
|
|
 Jedi Knight
Joined: 02 Jun 2005 Posts: 3316 Location: IBM (retired)
|
The standard order of things to try are:
1. start the toolkit with the -clean option
2. erase your .metadata dirctory in the workspace
3. re-install ithe toolil,t. _________________ -wayne |
|
Back to top |
|
 |
Trugga |
Posted: Wed Apr 12, 2006 5:44 am Post subject: |
|
|
Novice
Joined: 30 Mar 2006 Posts: 15 Location: West Midlands (UK)
|
wschutz wrote: |
1. start the toolkit with the -clean option |
Hmm, stumped at the first hurdle.
How do I start the toolkit with the -clean option (I currently just doubleclick a desktop icon, but I guess I need to know the command prompt command to do the same, with -clean at the end)
Lawrence |
|
Back to top |
|
 |
jefflowrey |
Posted: Wed Apr 12, 2006 6:02 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
edit the shortcut. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
Trugga |
Posted: Wed Apr 12, 2006 6:29 am Post subject: |
|
|
Novice
Joined: 30 Mar 2006 Posts: 15 Location: West Midlands (UK)
|
D'oh (it's been a long time since I did that)
Loading...
Lawrence |
|
Back to top |
|
 |
Trugga |
Posted: Wed Apr 12, 2006 6:32 am Post subject: |
|
|
Novice
Joined: 30 Mar 2006 Posts: 15 Location: West Midlands (UK)
|
Hmm, no joy, onto plan B then
wschutz wrote: |
2. erase your .metadata dirctory in the workspace |
I can't see a .metadata directory in the workspace, so I'll search the hard disk structure...
Lawrence |
|
Back to top |
|
 |
Trugga |
Posted: Wed Apr 12, 2006 6:52 am Post subject: |
|
|
Novice
Joined: 30 Mar 2006 Posts: 15 Location: West Midlands (UK)
|
Hmm, no joy, onto plan C then :
wschutz wrote: |
3. re-install the toolkit. |
I daresay I'll catch up with you tomorrow.
Lawrence |
|
Back to top |
|
 |
jefflowrey |
Posted: Wed Apr 12, 2006 6:56 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
The .metadata directory by default will be in "c:\Documents and Settings\<username>\IBM\wmbt6.0\workspace". _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
Trugga |
Posted: Thu Apr 13, 2006 2:22 am Post subject: |
|
|
Novice
Joined: 30 Mar 2006 Posts: 15 Location: West Midlands (UK)
|
I think I might have found the problem.
Whilst reinstalling the toolkit, it reported an error. A look at the run_wmbt_rad_update_errout.log log shows the following:
Code: |
Unable to complete action for feature "IBM WebSphere Message Brokers Toolkit 6.0.0.1" due to errors.
Unable to complete action for feature "updater.customization.ini.update.6001" due to errors.
Command failed: "C:\Program Files\IBM\MessageBrokersToolkit\6.0/eclipse/jre/bin/java" -cp updateini.jar com.ibm.rational.update.ini.ChangeProperties updater.customization.ini.update.v6001 "C:\Program Files\IBM\MessageBrokersToolkit\6.0\updater\workspace\proxies\eclipse\features\updater.customization.ini.update.6001_1.0.0\temp" "C:\Program Files\IBM\MessageBrokersToolkit\6.0/eclipse/default/plugin_customization.ini"
[ Unable to allocate an initial java heap of 4194304 bytes. ]
[ **Out of memory, aborting** ]
[ ]
[ *** panic: JVMST016: Cannot allocate memory for initial java heap ]
abnormal program termination |
The PC is a P4 1.7 with 512MB, page file is currently 409MB and free disk space is 4.85GB
I'll play about with vitual memory and disk space (unless someone has a better idea )
Lawrence |
|
Back to top |
|
 |
wschutz |
Posted: Thu Apr 13, 2006 2:32 am Post subject: |
|
|
 Jedi Knight
Joined: 02 Jun 2005 Posts: 3316 Location: IBM (retired)
|
Well, i realise that 512MB is the recommended minimum:
Quote: |
512 MB of RAM are required to support Message Broker Toolkit operations on Linux (x86 platform) or Windows. This specification is the minimum supported level; for improved performance, provide 1 GB (1 GB equals approximately 1 000 000 000 bytes). |
But to me, in my experience, that is simply too little real memory.... any chance you can upgrade the real memory size or get a "larger" machine. Even if you do get it to install, I don't think the performance is going to make you happy.
btw...how much memory is on the machine that "works"?? _________________ -wayne |
|
Back to top |
|
 |
Trugga |
Posted: Thu Apr 13, 2006 2:39 am Post subject: |
|
|
Novice
Joined: 30 Mar 2006 Posts: 15 Location: West Midlands (UK)
|
I'll have a chat with the desktop engineers and see what I can scrounge.
The machine that works has 512 as well (8.5GB free space, 385 page file)
Lawrence |
|
Back to top |
|
 |
Trugga |
Posted: Wed Apr 19, 2006 2:27 am Post subject: |
|
|
Novice
Joined: 30 Mar 2006 Posts: 15 Location: West Midlands (UK)
|
Well, it's taken a week, but I've solved the issue - I now have the option to create a new message set
Investigation/Resolution.
Having uninstalled the Webspher Message Broker Toolkit (WMBT) and reinstalled it, I noted the installation reported errors. A look in the logs first suggested Java heap size issues - I upped the Windows 2000 virtual memory to 766MB - that seemed to cure the problem without adding more physical memory (currently 512MB)
Reinstalling WMBT again produced another error. The logs suggested the installation process could not install the upgrade (from 6.0.0.1 to 6.0.1.2). As our company firewall does not permit dowloading of executeables, I disconnected the network lead and tried again = that solved that problem.
Finally, another failed install log suggested that a jre archire file already existed, So I deleted the \program files\messagebrtokertoolkit directory and reinstalled - this time it took much longer to install... without any reported errors.
Tips:
Don't just click the OK/Next button - read the dialog box contents first.
Read the log files following an error - there difficult to understand at first, but keep at it.
Don't give up.
Thanks for support/suggestions - we got there in the end.
Lawrence |
|
Back to top |
|
 |
|