MQSeries.net :: View topic - WBI Development / System Manager Problems

Smiler · Posted: Tue Mar 20, 2007 9:02 am Post subject:

Hi all,

I have been working on a large worldwide rollout of a WBI Middleware solution for around 18 months. The project has been fairly successful, but I find the IBM software to be very slow and very buggy.

I have finally come across this forum, which seems to be full of active developers so I thought I would share some of the problems I'm having and see if any of you have any resolutions. I find the IBM support web site, and the actual IBM support personnel useless and more interested in closing tickets than solving problems.

Here are a few of my problems :-

- Database ASBOs lose their "TN=tablename" attribute randomly. They then have to be entered in & redeployed....

- I have around 20 collabs, 7 connectors, 150 BOs, 400 maps and it can take around 10-15 mins to do a full deploy. Is there any way to improve this? ICS is running on a Dual Xeon 3GHz, 8GB Ram, under Windows.

- The ICS server tree is unreliable in terms of indicating whether colloborations are started, stopped etc....

- After deployment, sometimes I get an error akin of "Could not find Version 3.0.0 of the Business Object", even though it is Version 3! A full deletion of the repository and redeploy seems to be the only way for it to work.

- I have a few colloborations which join onto one other. When making changes, there seem to be so many dependencies that it's impossible to re-deploy one object without redeploying the entire solution. Is there any way around this?

- When an event fails and is held in Flow Manager, I can sometimes retrieve the original BO to test my mappings, however sometimes this fails and I can't retrieve the BO.

- WBI error log - perhaps this is down to the way my colloboration templates are set up, but whenever their is an error given it is always "Colloboration Exception", without any further detail. This then involves tediously tracing the log file for the last step which started, but failed to complete. And even then, this is not obvious. Can anyone point me to some examples of developing colloboration templates which can log a meaningful error when it fails?

[This is our biggest hold up to development, if we had better error logging we could develop a lot faster]

- When in production, it would very helpful for the connector & WBI logs to log to a database instead of files. Is this possible?

- Many many problems can only seem to be fixed with a complete deletion of the repository, restarting WebSphere ICS and redeploying

- Libraries + Projects

As I mentioned above, the project I am working on is having a worldwide rollout. The collaborations and connectors need different configuration for different locations. Is there an easy way to split these into a different library? I have tried this, but with limited succcess as obviously when editing the connectors & collaborations the other objects are not present in that library.

The best I have been able to do is develop it in one library and then split it out to two for deployment. Anyone got any ideas?

I would appreciate your replies. I'll be staying active on this forum as this project has a long way to go and I'll attempt to help others with their problems if I can.

Thanks

James