Feeds:
Posts
Comments

Archive for December, 2009

Don’t know what google did but my openmaximo.net site is dead. Been a fan for a while but things R changing. Time 2 change provider.

Read Full Post »

A comprehensive list of recommended fixes for Maximo Asset Management and Maximo Asset Management for IT.

http://ow.ly/MWPc

Reblog this post [with Zemanta]

Read Full Post »

This IBM technote shows the security tables for CCMDB 7.

http://ow.ly/MWNp

Reblog this post [with Zemanta]

Read Full Post »

Question: What are beans in IBM Maximo

The information provided in this post is based on my Maximo 6 experience. I don’t know if or to which extent it has changed in Maximo 7.
Answer
There are 2 types of Beans in IBM Maximo, AppBean and DataBean.

presentation-xml

AppBean
The AppBean manage application functionality, such as WOTRACK or ASSET. This class is defined in the beanclass attribute of the presentation tag in the application’s XML.

wotrack-action-xml

If you export the WOTRACK application xml and go to the bottom of the file you can see a group of actions (action tag) defining actions and their corresponding method in the AppBean beanclass.

For instance if you’d like to add a button on WOTRACK to approve a workorder (OOTB in Maximo 7 but not in 6) besides of creating the SIGOPTION and TOOLBAR records for that operation you’d also have to develop custom Java code for it, this would be done in the AppBean. 

DataBean

dialog-xmlImage by jacobdotcosta via Flickr

Data Beans can manage both dialog boxes and tables. The DataBean class associated is defined in the beanclass attribute of both the dialog and table tags in the application’s XML.

For instance, on dialog boxes you can use a DataBean to control what to do when the OK button is pressed (submit() method).

On tables you can do things such as custom the way to load the MBOSet on that table (getMboSet() method).

table-xml

You have to have in mind that the flow control of the dialog’s execution is quite complex. For instance, if you don’t provide a submit() method on your dialog’s bean class, Maximo will try executing other methods and will end up executing the execute() (I think this is the method) method of the MBOSet asociated with your dialog (defined with the mboname attribute of the dialog tag).

Reblog this post [with Zemanta]

Read Full Post »

Check this IBM® Redbooks® publication that attempts to provide a broad view of how Tivoli® system management products work together for use in several common scenarios


More information on the IBM Redbooks site: http://ow.ly/KvHn

Reblog this post [with Zemanta]

Read Full Post »

Post by w


Related articles by Zemanta

Reblog this post [with Zemanta]

Read Full Post »

I have an application that connects to Maximo via RMI and needed to use Maximo’s translation engine. This post explains how to do this.

In this example we’ll get Maximo’s greeting message.

    psdi.util.MXSession mxSession = (…);
    (…)
    // LANGCODE
    String langCode = “PT”;
    // Name of the user currently logged in, to present in the message.
    String usrDisplayName[] = { mxSession.getUserInfo().getDisplayName() };
    // MAXMESSAGE object constructor with the target langcode.
    psdi.mbo.MaxMessage message = new MaxMessage(langCode);
    // Message group
    message.setGroup(“login”);
    // Message key
    message.setKey(“welcomeusername”);
    // Obtain Maximo’s message text using the MXSession instance used to connect to Maximo.
    msgS = mxSession.getMessage(“login”, “welcomeusername”);
    // Fill in the messages parameters
    message.setValue(msgS);
    // Get the translated text.
    msgS = message.getMessage(usrDisplayName);
    // Print the message
    System.out.println(msgS);

Reblog this post [with Zemanta]

Read Full Post »

Older Posts »