Author |
Message
|
EKhalil |
Posted: Wed Apr 13, 2005 9:20 am Post subject: WBIMB 5.0 Fix Pack 6 ??? |
|
|
Voyager
Joined: 29 Apr 2003 Posts: 99 Location: Boston, MA
|
We're in the mid April now...and I was just wondering if anyone has a word on the FP 6 release dates. |
|
Back to top |
|
 |
jefflowrey |
Posted: Wed Apr 13, 2005 9:30 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
I think you mean FixPack 5.
Since the current FP is FP4.
And I haven't heard anything. I remember seeing a posting a few months ago from an IBMer (maybe JasonE?) talking about the general release schedule for FPs - without being specific about exact dates. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
EKhalil |
Posted: Wed Apr 13, 2005 9:42 am Post subject: |
|
|
Voyager
Joined: 29 Apr 2003 Posts: 99 Location: Boston, MA
|
|
Back to top |
|
 |
shra_k |
Posted: Fri Apr 15, 2005 3:51 am Post subject: |
|
|
Apprentice
Joined: 30 Dec 2002 Posts: 37
|
it should have been by now...else mostly next week.... |
|
Back to top |
|
 |
Bill.Matthews |
Posted: Fri Apr 15, 2005 10:09 am Post subject: WBIMB FP5 now available |
|
|
 Master
Joined: 23 Sep 2003 Posts: 232 Location: IBM (Retired)
|
FP5 is now available (Friday, March 15) _________________ Bill Matthews |
|
Back to top |
|
 |
jefflowrey |
Posted: Fri Apr 15, 2005 10:18 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
A couple of fairly interesting notes in the Readme
Quote: |
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
IC43091 - DOMAINAWARE FLAG FOR TOOLKIT NEEDS TO BE DOCUMENTED.
A new section entitled 'Turning off the toolkit domain awareness'
will be added to 'Considering security for the workbench' (ap03985_)
as follows :-
The toolkit will send the user and domain name through to the
configmgr queue manager regardless of the domain awareness setting
on the configmgr. This can cause problems connecting with the queue
manager because of the security required to connect/put/get messages.
To turn off domain awareness run the toolkit as follows:
1) change to the \eclipse directory.
2) Run the toolkit using the command:
mqsistudio -vmargs -DDomainAware=0
Alternatively, modify the short cut that runs the toolkit and add on
-vmargs -DDomainAware=0 |
And for those running on Linux, you now have to use an ODBC connection for the broker, and there is now an mqsi_setupdatabase command
Quote: |
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Essential information if you are installing Fix Pack 5 on Linux
In Fix Pack 5 the broker connects to IBM DB2 databases through an ODBC
connection defined to DataDirect Database Manager. Direct access to a
broker database or any user data database is no longer supported. You
must configure an odbc.ini file to define broker and user database
connections after you have installed this fix pack.
For details of the actions required, refer to the section "Configuring
for first use" in the Fix Pack 5 information center.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
37666 - Ship mqsi_setupdatabase on Linux Intel v5 |
_________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
PeterPotkay |
Posted: Fri Apr 15, 2005 2:17 pm Post subject: |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
Is it just me, or is the read me just a loooong list of defects in CSD05? Where is the list of what was fixed?
I like this one under Debugger:
Quote: |
Do not debug the production brokers.
|
What is that supposed to mean? Presumably debugger is not safe to use? And its OK when it dies in DEV and QA, where you are going to use it the most anyway?!?!?! _________________ Peter Potkay
Keep Calm and MQ On |
|
Back to top |
|
 |
Michael Dag |
Posted: Sat Apr 16, 2005 1:03 am Post subject: |
|
|
 Jedi Knight
Joined: 13 Jun 2002 Posts: 2607 Location: The Netherlands (Amsterdam)
|
PeterPotkay wrote: |
Is it just me, or is the read me just a loooong list of defects in CSD05? Where is the list of what was fixed? |
yeah it would be nice to have a list of what is different/new...
or are we supposed to find that out ourselves...  _________________ Michael
MQSystems Facebook page |
|
Back to top |
|
 |
jefflowrey |
Posted: Sat Apr 16, 2005 1:32 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
PeterPotkay wrote: |
Where is the list of what was fixed? |
In the Memo.PTF _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
KSkelton |
Posted: Wed Apr 20, 2005 6:08 am Post subject: |
|
|
Apprentice
Joined: 28 Oct 2001 Posts: 45
|
This is the defect that killed me:
Defect 34930
Platforms affected: Windows only.
If you already have the Message Brokers Toolkit installed and the INSTALL_PATH\eclipse\workspace\.metadata exists, you might find that after you have installed Fix Pack 5, when you open the Message Brokers Toolkit, the Update Manager is launched correctly, but any updates to your plug-ins fail. As a result of this, the Message Brokers Toolkit does not open with the correct plug-in levels, and failures of the toolkit might occur.
For example, when you are in the Broker Application Development Perspective, you might find that the Message Definition File menu item is missing from the list produced by File > New Menu. This is an indication that your installation does not contain the correct level or version of plug-ins for the Message Brokers Toolkit.
You can check that the levels of plug-ins that you are using is correct by clicking Help > About Message Brokers Toolkit for WebSphere Studio - Message Broker in the Message Brokers Toolkit for WebSphere Studio window. Under the heading "Message Brokers Toolkit for WebSphere Studio", a version number is displayed. If the correct versions of the plug-ins are being used after you have installed Fix Pack 4, the version that is displayed is 5.0.4. If the version that is displayed is less than this, follow the instructions given below.
Delete the .metadata directory.
Reopen the Message Brokers Toolkit.
Re-import your existing projects into the workspace by doing the following for each project:
Click File > Import.
When the Import wizard appears, select the Existing Project into Workspace option and click Next.
Click Browse and define the location of the project in your workspace.
Click Finish.
-----
Yes, that says for EACH project. If you have over 100 message set projects in your workspace this is real fun.
Then I realized that my connection to my SCM tool was not restored. So I had to make a NEW connection for each and every project anyway!
It would have been easier to just blow away my entire workspace and start over by selecting what I needed from my SCM tool.
Make sure you check in your source before applying the Fix Pack. |
|
Back to top |
|
 |
jefflowrey |
Posted: Wed Apr 20, 2005 8:31 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
That bug is a carryover from FP4.
Also, it is a good reason to use a different workspace location than INSTALL_PATH\eclipse\workspace\... _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
KSkelton |
Posted: Wed Apr 20, 2005 8:40 am Post subject: |
|
|
Apprentice
Joined: 28 Oct 2001 Posts: 45
|
Thanks Jeff.
I didn't realize that if I placed my workspace somewhere other than INSTALL_PATH that this bug would not manifest itself.
Thanks for the clarification |
|
Back to top |
|
 |
alechko |
Posted: Sun Apr 24, 2005 1:34 pm Post subject: |
|
|
Apprentice
Joined: 12 Jan 2005 Posts: 37
|
Quote: |
Re-import your existing projects into the workspace by doing the following for each project: |
I can suggest a solution for this specific problem:
1. Copy the workspace directory aside.
2. Create a directory c:\dummy with an empty file bla.xml
3. Make a script with these commands for each project:
mqsimigratemsgflows -p ProjectName1 -d c:\dummy
mqsimigratemsgflows -p ProjectName2 -d c:\dummy
mqsimigratemsgflows -p ProjectName3 -d c:\dummy
4. Execute the script (you will receive several error messages)
5. Copy the projects you saved before on top of the projects created in the workspace directory.
6. Open the toolkit and open all the projs
The Msgsets projects is a different story ...
If you are using Team Project Set you can import them all together.
I hope it helps. |
|
Back to top |
|
 |
BineBlue |
Posted: Mon Apr 25, 2005 6:13 am Post subject: |
|
|
Novice
Joined: 12 Nov 2003 Posts: 17
|
|
Back to top |
|
 |
KSkelton |
Posted: Tue May 03, 2005 9:40 am Post subject: |
|
|
Apprentice
Joined: 28 Oct 2001 Posts: 45
|
BineBlue,
I tried installing this plug-in and received an error that it could not update the install because it would invalidate the current configuration. How did you get this installed on your version of the toolkit? |
|
Back to top |
|
 |
|