September 30, 2013

Translate workflow messages and labels

Translated messages and labels are not enabled by default on Maximo workflows. This means that if you have a multilanguage environment all the users will see the same task descriptions interaction messages when using workflows.
To be able to insert translated labels and messages for workflows you have to enable the multi-language option for the following attributes:
  • WFACTION.INSTRUCTION
  • WFASSIGNMENT.DESCRIPTION
  • WFINTERACTION.DIRECTIONS
  • WFINTERACTION.DIRECTIONS_LONGDESCRIPTION


To set multi-language option go to System Configuration > Platform Configuration > Database Configuration find each attribute and set the 'Multilanguage in use?' flag. Enable the admin-mode and apply database changes.
After having done this you should be able to login as MAXADMIN with a different language and set different labels for actions and tasks using the standard 'Workflow Designer'.



Reference IBM TechNote: Setting up Multilanguage for Workflow

September 21, 2013

How to disable the 7.5 Rich Text editor

TPAE 7.5 has introduced a nice Rich Text editor control for editing and formatting long descriptions. This applies to both Maximo and SmartCloud Control Desk starting from version 7.5.
This feature is very cool in some cases but may cause some troubles. I personally do not like the effects of pasting text into such RTF text boxes.

To disable the formatting features of these controls you can just add the following attributes to the richtexteditor element in the application XML definition: plugins="[]" extra_plugins="[]"

Here are the steps.
  1. Open the Application Designer.
  2. Open the application you want to modify.
  3. Export the XML definition.
  4. Open the XML with a text editor.
  5. For each richtexteditor element add the plugins and extra_plugins attributes (look at the example below).
  6. Save the XML file.
  7. Update the application definition importing the XML in the Application Designer.

Example

Before
<richtexteditor dataattribute="description_longdescription" id="main_grid3a_col1_2"/>

After
<richtexteditor dataattribute="description_longdescription" id="main_grid3a_col1_2" plugins="[]" extra_plugins="[]"/>


References


September 11, 2013

Automatically start Maximo or SCCD server

To automatically start Maximo or SmartCloud Control Desk (SCCD) when the hosting server starts you need to configure the WebSphere Node Agent to start automatically start at server boot.

Automatically start WebSphere Node Agent

This can be achieved on Windows setting up the WebSphere Node Agent as a Windows service using the WASService command located in the [APPSRVDIR]\bin directory.

WASService -add "Node Agent"
-servername nodeagent -profilePath "[APPSRVDIR]\profiles\[PROFILENAME]"
-wasHome "[APPSRVDIR]"
-logRoot "[APPSRVDIR]\profiles\[PROFILENAME]\logs\nodeagent"
-logFile "[APPSRVDIR]\profiles\[PROFILENAME]\logs\nodeagent\startNode.log"
-restart true -startType automatic

If WebSphere is installed on D:\IBM\WebSphere and the profile is named ctgAppServer the command will look like this:

cd D:\IBM\Websphere\Appserver\bin
D:
WASService -add "Node Agent" -servername nodeagent -profilePath "D:\IBM\WebSphere\AppServer\profiles\ctgAppSrv01" -wasHome "D:\IBM\Websphere\Appserver" -logRoot "D:\IBM\WebSphere\AppServer\profiles\ctgAppSrv01\logs\nodeagent" -logFile "D:\IBM\WebSphere\AppServer\profiles\ctgAppSrv01\logs\nodeagent\startNode.log" -restart true -startType automatic 


Automatically start Maximo application server

The Maximo application server can now be configured to automatically start when the Node Agent is started using WebSphere Node Monitoring as described in this article.
To implement Node Monitoring use the following steps:
  1. Log into WebSphere Integrated Solutions Console.
  2. From the left navigation select Servers > Application Servers.
  3. Click the appropriate Maximo Application Server (default name MXServer).
  4. Expand Java and Process Management and click on Monitoring Policy.
  5. Change the Node restart state to RUNNING
  6. Click Apply
  7. Click Save to save the master configuration
  8. Repeat for each server in the cluster.

An alternative approach is to configure the application server to be started as a windows service as described in this IBM TechNote.