Your session will time out in 60 seconds   That is the message that not many people love to see when you are not working on a Maximo window for a moment and the process that you are testing is still not finished.   By default, client sessions are timed out after 30 minutes of inactivity.  You are lucky that t here is a way to disable that.  ;-)   That would be possible if you configure the timeout setting to a negative value, such as -1.   This following instructions outlines the steps to change the timeout... [More]

Tags:  maximo disable timeout

System Property could  be set  to 0 or 1  When value is set to 1  whether using External System Publish Channel  export or Event Listener  the    value in  SENDERSYSID  field  of the Main  Object in Object Structure  is set to  MX or to  value MXSYSID variable is set to. The property is to control if we update   field SENDERSYSID back to Maximo or not.

Maximo has a lot of integration abilities and one of them is the REST API. One of the really great thing about the REST API is that it is a very simple protocol that can be used to communicate with Internet of Things devices. It is compact and light weight and does not need much resources. There are many IoT devices to pick from but my personal favorite is the BeagleBone Black (BBB). It is a low cost credit card size computer and the best part is that it does not need much setup to communicate with Maximo. To try the example you only need a... [More]

Tags:  rest maximo beaglebone iot

Hi All, I have created an Object Structure with SR and Worklog. I am able to trigger request to the other system when there is any change made on worklog and it sends only the latest worklog entry.  But the issue is, even if there is no change on the worklog it still sends the latest worklog entry which is creating duplicates on the system which is on the other side..  How do I restrict the worklog to be sent only when there is any change made on it.  Your help is much appreciated!   Regards, Pallavi

Today I am going to talk about and show you the basics steps I like to use when diagnosing a Maximo won't start or you can't login to Maximo issue.  See the steps I have put together:   1. Login to WebSphere console and stop the MXServer 2. Navigate to the systemout.log which is by default in \ Program Files\IBM\WebSphere\AppServer\profiles\ ctgAppServer01 \logs\MXServer and delete this systemout.log file. 3. Go back to WebSphere console and restart the MXServer creating a new fresh systemout.log 4. If you get the green arrow... [More]

It was brought to my attention that after installing Maximo Anywhere 7.5.2.1 a new plug in file is copied to the Installation Manager shared folders, once installed only this plug in will be read when displaying the installation panels. Now the problem with this is, if you decide to install another version of Maximo Anywhere to the same server under a new package group which is supported by the Installation Manager some panels may be missing from the installation process.  Specifically panels regarding the Android SDK.  With this... [More]

Tags:  install #supmax anywere maximo installation manager mobile

In most of the core Maximo applications, the process of changing status of a record is fairly standard. Usually, the record starts it's life in WAPPR (Waiting for Approval), DRAFT or INACTIVE. You have a Change Status Toolbar button and you can proceed to change the status as per the options available in this Change Status dialog. There are some applications however, where the process of changing status is different and a bit more complicated to the one mentioned above.  In this blog entry, I am going to show you an example where a... [More]

Activating the Escalation is a two step process. In the script you have to:   1) Set the escalation attribute ACTIVE to true. 2) Call actDeactEscalation() method on the Escalation MBO. This method will handle all the validation and Cron Task creation behind the scenes.

Please creates an Object Structure with LOCATIONS object only. You can duplicate an out of the box MXOPERLOC and delete un-wanted objects. Please use the attached flat file as a data sample.   EXTSYS1,LOCATIONS,AddChange... [More]

When users are synchronized from different domains, you want to have a customized field keep information where users are came from.   In order to achieve this requirement, 1. need to separate VMMSYNC crontask instance. For,  one to synchronize users from A domain, the other to synchronize users from B domain.   2.  Create a customized field in PERSON object - Go to the Database Configuration application. - Open PERSON object - Create the attribute named  'SOURCEDOMAIN'  having ALN(10) Type. - Apply Database... [More]

As some of you may already know Maximo Anywhere 7.5.2.1 was released this week. Along with the usual bug fixes and enhancements that are included in the Maximo Anywhere fix packs this release also brings support for Windows Tablets, to add to the current supported Android and iOS platforms.    It's important to note the following information from the README around the supported Windows OS platforms. Windows tablets running on the Windows OS 8.1 are supported, however 8.0 is not a supported tablet operating system. The Maximo... [More]

Tags:  anywhere mobilefirst maximo+anywhere mobile maximo worklight supmax

As many of you may know Maximo TPAE (Base) fixes are bundled with Scheduler fixes. I just wanted to make this quick blog entry to share what each base version had bundled with it. Maximo version 7504 and lower comes with fixes for scheduler version 751, versions 7505 and higher come with fixes for scheduler 752. My co-worker pointed out that Maximo 7.6.0.0 has Scheduler 7.5.3.   What this means if upgrading from a previous version of Maximo to a newer version you will need to plan to upgrade your scheduler version at the same time.... [More]

Tags:  maximo tpae #supmax ifix scheduler base

  The instructions for enabling security created by my colleague included in the blog entry link below describe the steps necessary to enable application server security including modifications to web.xml files for the associated war modules, updates to system properties,  rebuild/redeployment of the maximo.ear, enabling global security within the WebSphere Administrative Console, and restarting the application servers.   ... [More]

Tags:  deployment security hot web.xml maximo

On Oracle database, the default optimizer_mode is ALL_ROWS.  This optimizer_mode is inefficient for Maximo SQL queries, especially users screen response.   Here is an explanation of Oracle optimizer_mode from oracle documentation -- http://docs.oracle.com/database/121/TGSQL/tgsql_influence.htm Relevant information extracted from the above link Best throughput (default) When you set the OPTIMIZER_MODE value to ALL_ROWS , the database uses the least amount of resources necessary to process all rows that the statement accessed. For batch... [More]

Tags:  performance optimizer_mode oracle maximo