jtonline 110000B6Y8 Tags:  rational-software-archite... user-interface-generator rsa user-modelling preferences uml diagram user-model 5,370 Views
This is a very quick tip that came up in a usability session today. The UML diagram editor in Rational Software Architect has popup bars which can save time creating diagrams compared to using the palette. For example:
One downside is that they can catch you out if you are trying to select part of the diagram and they pop up unexpectedly. It turns out that there's a simple way to disable these popup bars if you don't want to use them. Open Window > Preferences and navigate to the Modeling > UML Diagrams page.
Deselect the Show popup bars option and click OK. I tend to use the Add User Modeling UML context menu anyway, so I won't miss the popup bars at all!
This is a great tip for the User Interface Generator which Iain showed me earlier this week. In the past I have right clicked on a model element and used Visualize > Explore in Browse Diagram to see how it is related to other parts of the user model. That works quite nicely but you don't get a diagram to keep afterwards, which means I often end up using a Freeform Diagram to manually drag on the elements I want to work with.
Instead, right click on a model element in a diagram and choose Filters > Show Related Elements... , on a user task for example. I created a new diagram for the task I was interested in but this is also a good way to extend existing diagrams.
You can just click on OK in the Show Related Elements in Diagram dialog box but there are a few useful options if you use the Details >> button. For example, deselect the Owned Element checkbox from Custom Query [Default] to avoid including task activity diagrams.
You should see the diagram update to include all the parts of the user model relating to your task, which is ideal for making modifications or documenting parts of your model.
You can also increase the number of levels to include, however that can result in some pretty large diagrams!
When writing code to work inside the User Interface Generator that comes with MDM Server and MIH it is necessary to use interfaces declared by the UIG framework. For instance all command beans need to implement the Command interface and work with data types in the com.ibm.usermodeling.attribute.types package. Unlike the interfaces and classes from core Java classes the Javadoc does not appear for these internal UIG classes when you hover over them in the Java editor although they are supplied as part of the Help Contents within RSA. The steps below outline how to make the Javadoc appear in the Java editor.
The Javadoc for the interfaces and types declared in this Jar should now appear in your Java editor. You can repeat the process for other Jars supplied by UIG, for instance if you are writting new Widget Generators you may want to include the Javadoc for the com.ibm.uig.runtime.jsf.jar which is a Web App Library in the web project. The Javadoc for all of the Jar files is supplied within the same zip file.
The User Interface Generator that comes with MIH and MDM version 9 comes with a sample application showing how to connect to MDM Server. The sample works by declaring a JNDI name inside the sample application that enables the DWLServiceController EJB to be loaded. This technique will only work when the sample EAR is deployed to the same web application server as the MDM EAR, otherwise the JNDI lookup will not be able to find the EJB
These instructions outline the steps necessary to change this approach so the sample works with a remote MDM installation on a different machine or application server. As well as setting up the code to do a remote lookup of the EJB it will also use the JNDI name declared in the MDM EAR.
Initial when I used this code I got the following error with details of the machine name instead of the host name (nala.hursley.ibm.com) that I had supplied:
Forwarded IOR failed with: java.net.UnknownHostException
As described in this forum post this problem is caused by WAS forwarding the request to a different port. When it does this it uses the computer name rather than the host name. To solve this problem I added mapping from the computer name to its IP address in the C:\windows\system32\drivers\etc\hosts file.
jtonline 110000B6Y8 Tags:  websphere jms messages sibexplorer admin-console sib mdm 1 Comment 14,444 Views
I was recently asked about ways to check the contents of JMS queues while doing MDM development. If you only need to do this on an ad hoc basis, you can simply use the WebSphere administration console. Acording to the help, their are two paths you can follow to reach the same place:
Service integration > Buses > bus_name > [Destination resources] Destinations > queue_name > [Message points] Queue points > queue_point_name > Runtime > Messages
I took the second route, as follows:
You should see this screen of MDM queues:
Open the queue you're interested in and click on Messages in the Additional Properties section.
That's one way to do it but if you're going to be working with JMS a lot, SIBExplorer is probably a better alternative. This gives you a Java client to work with the Service Integration Bus, which looks like this:
There are a few more details about these options on the SOA Tips ‘n’ Tricks blog.