Problem: In LDAPSYNC, if a large chunk of data takes a long time to process and the processing time exceeds the Active Directory’s idle connection timeout setting ( MaxConnIdleTime ), it can cause the Active Directory to close the connection which leads to synchronization failure.   Symptoms: LDAPSYNC fails with errors like these:   BMXAA6752E - Group synchronization could not be performed because of error connection closed. The error count was 148. See the associated message. Correct the problem and try to synchronize again.... [More]

Tags:  maximo ldapsync

When you plan to use application server security to authenticate TPAE/Maximo users against an external directory you also have the option to synchronize users and/or groups and group memberships. There are a few decisions you need to make before you begin.   Who will be synchronized? You can use a standard LDAP filter to synchronize a subset of users into the system. These users can be in a pre-defined OU, role or group or can simply meet a standard query. Synchronizing a subset of users will improve the performance of the sync and also improve... [More]

Tags:  security asset-management ism service-management ldap servicemanagement maximo eam tivoli

Trouble rendering Microsoft Office attachments in Maximo, selecting attached filed to open.   You may face a scenario where when opening an attachment for a work order that is Word or Excel, it  opens in the browser which does not render it correctly.   These  attachments used to open outside of the browser in the correct  Microsoft Office application and render correctly.    Picture this scenario :  As an   overview, Maximo users open a work order, select an attachment to open, and it opens in the browser but t hey want it to open outside of... [More]

Tags:  ibm-blog

You may have encountered the Launch Entry Name Field In Work Order Tracking application and wondered what is it there for. Here's a simple explanation: In out-of-the-box Maximo , the Work Order Tracking application's Work Order tab, includes a editable field entitled Launch Entry Name. You can select a value for the field from the Launch in Context application. The Launch In Context was initally implemented as part of the interface... [More]

  IBM Maximo Spatial Asset Management 7.6.0 IBM Maximo Spatial Asset Management is an add-on solution sold in combination with Maximo Asset Management and Maximo Industry Solutions – except – Maximo for Utilities which includes the spatial applications. Maximo Spatial provides a GIS solution that allows users to visualize, question, analyze, and interpret data to understand relationships, patterns, and trends. It allows users to look at data in a way that is quickly understood and easily shared on a map.   What’s New... [More]

Tags:  maximo spatial ibmeam

If large files are getting created in a tmp directory all the time, or  some of the time, it  is because users execute long running reports that cause these files to get created in the temp directory. Even Query-based reporting, or QBR, can cause this to happen. However, this is by design. Generally speaking, Birt will clean up after itself.    It is only an issue once these large files start filling up the drive and the server runs out of space. Two known causes when these temp files do -not- get auto... [More]

Tags:  hangs tmp qbr server maximo v76 temp files maximo+7.5

To better understand what the title mentions, let me explain some content.   FIXPACK Fixpacks deliver product defect fixes that have undergone a full development release cycle and the most extensive QA testing of all maintenance releases. Fixpacks are cumulative and each new fixpack contains all fixes from all previous fixpacks/interim fixes for that release. An example of a Fixpack is :   Maximo 7.6.0.6 Feature Pack   INTERIM FIX (IFIX) Interim Fixes go by many names like; Hotfix, Cumulative Hotfix, IFIX.  They all relate to the same type of... [More]

Tags:  ibm-blog

Labor Reporting field is not searchable in List tab after upgrade to Maximo 7.6   In Maximo 7.5 the STARTDATE attribute in LABTRANS object was a persistante attribute in the database. So, being persistante, the field is searchable in the database so in the UI.   However, the structure changed in Maximo 7.6. Now the STARTDATE attribute in LABTRANS object is not a persistante attribute in the database.   Instead, there is a new attribute called STARTDATEENTERED. This is a new attribute which is same as STARTDATE but persistante.... [More]

In Maximo support, we often get various questions on the functionality of these 3 apps,however also the question what will be the best to use. As we do not provide guidance on what app is the best to use, I like to set them out on their functionality,so you can choose yourself which one would be suitable to your needs. There are lots of methods to do a configuration or customize Maximo Base Services from the UI down to the object level with Java programming.   With so many options available out there , I like to touch on the core 3 core... [More]