Adding an Image to any Application in Maximo

The procedure to add an image in User application like we have in Item Master application is given in this link,

 https://www-304.ibm.com/support/docview.wss?mynp=OCSSWK4A&mync=R&uid=swg21426888&myns=swgtiv

Using this, we can extend this to have Image feature in any application in Maximo.
 

Platform Configuration Matrix

IBM recommends Configurations for Maximo versions 6.2,7.1 and 7.5.

The document will help us to suggest customers for the Hardware configuration required for specific Maximo version. This matrix file have minimum hardware requirement details for Client machines, Administration and Application server workstations.

 
For example: If client want to use Maximo 7.5, then it will be supported only in Websphere 7.0 and Oracle Weblogic 10.3.3 (and higher) with JRE 1.6.
 

https://www-304.ibm.com/support/docview.wss?uid=swg27014419

MBO Development link

There are some of the best practices that can be implemented while developing Maximo codes or writing queries.

https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/IBM%20Maximo%20Asset%20Management/page/Maximo%20business%20object%20development

Some of points from this link are:

1.  Avoid using Yes\No\Cancel Exception. It is memory intensive since it repeats.  If you are forced to use, call Yes\No\Cancel logic in the code as early as possible.
2. "not in()" in the query will take much time to execute than "in()".
3. Setting of Field Flag (example: making Readonly) should not be done in the init() of mbo. It should be done in the initFieldFlagsonMbo();

Maximo Failed Deliveries - WAS & Try Count

When you define a bus(Service Integration) in the Websphere, where MXServer application can attach and exchanges messages.The Bus will have a property Maximum Failed Deliveries.

This is the maximum number of times you want the system to process a failed messaging attempt before forwarding the message to the exception destination(can be a system, file in a folder path or none).

Maximum Try Count in Maximo

This property specifies the number of times that the Maximo system tries to reprocess an error.
In this case, the error is some Maximo business validation failed to create/process records into Maximo. 

For example, Asset inbound records passed the queues, but inside Maximo it throws an error like the Asset number already present.  

Plan CPU and RAM for Server Machine in Maximo 7.5

When we plan to set up a new Infrastructure to host Maximo, we need to check whether sufficient CPU and JVM requirements available to run the application without lag in performance and memory issues.

•  Gather information from Client on number of concurrent Users [say, suppose 100 concurrent users]
•  IBM recommends to have 50 concurrent users per JVM. So, there will be a cluster will 2 UI application servers needed for UI services of 100 concurrent users
• We plan to have separate servers for MIF, Report and Cron tasks. So a total of 5 application servers [2 UI, 1 MIF, 1 Reports, 1 corn task]. So there will be 5 separate JVMs
• As a rule from IBM, 1 JVM = 2 GB RAM[for a 32-bit machine], 1 CPU Processor. So, in our case, for 5 JVMs, we need a physical machine of 5 CPU processors and 10 GB RAM memory.
• For 64 bit machines, 1 JVM can be of 3.5-4 GB of RAM size. 
• If an application server is configured for MIF or data loading, where it require some heavy processing of data, we can have its JVM of 4 GB of RAM

http://www-01.ibm.com/support/docview.wss?uid=swg21329219

Report Runtime Error in Clustered Environment in Maximo 7.5

If the BIRT report runs for a longer duration of time,  it runs successfully in a single application server environment. 

But it fails with error "org.eclipse.birt.report.service.api.ReportServiceException" 

when tried in a Clustered Environment.

We need to increase the server Time Out parameter to make it work in Clustered Environment.

Edit the ServerIOTimeout parameter within your Web server(s) in WAS under:

Servers -> Server Types -> Websphere Application Servers -> Click on [server_name] -> Web server plug-in properties (under 'Additional Properties') -> Read/Write timeout.

Increase this value accordingly until you no longer see errors running reports. Make this change to all JVMs necessary.

After making this change, be sure to re-generate and propagate the plugin-cfg.xml under:

Servers -> Server Types -> Websphere Servers

and clicking the Generate Plug-in, then Propagate Plug-in and restarting the server.

Check the new plugin-cfg.xml on your web server to ensure the change has made it to the web server.

http://www-01.ibm.com/support/docview.wss?uid=swg21607119