On January 27, 2020, Interloc Solutions released the Mobile Informer 5.8 Product Update. The new 5.8 version of Mobile Informer makes partitioned Catalogs a first-class feature, providing significant backend performance improvements in environments delivering data strictly via clearly-defined partitions for offline usage. This is especially relevant for customers with separate, disjoint data sets who need that data available offline at all times. An example being assets spread across factories or inventory spread between storerooms at different sites. When Catalog Partitioning was introduced in 5.6, it was an an “alternative” or “additional” way to track and deliver Catalog data. It is now possible for developers and administrators to define partitioned Catalogs as available strictly and solely via partitions. Doing to allows Informer to optimize data tracking, reduce storage costs, reduce the cost of preloads, and be generally “smarter” about when Preloads are generated and/or invalidated. Doing so lifts the practical limitation on how large (in sum across all partitions) any given Catalog can be. In addition to the Catalog Partitioning improvements, and some quality of life improvements and bug fixes, version 5.8 also: 1. Unifies and simplifies Informer queue configuration across the cluster, by reducing the number of parameters and leveraging Maximo’s “Global” and “Instance” system properties. 2. Allows the balance different types of Notifications processors to be specified, which allows for further optimization, as well as the ability to concentrate queue processing on fewer JVMs when desired (rather than being forced to spread across clusters). 3. Adds support for PostgreSQL as another supported database for externalized Informer Queue tables. You can download the update's Release Notes for a listing of defect corrections and functional enhancements. To obtain this product update or request additional information, please go to our Support site.
In the new IBM SmartCloud Control Desk (SCCD), there are very good Service Catalog and offerings applications that you can take advantage of and use in a production environment. In this blog, Interloc's Pete Morell shows you how to create a Service Catalog offering and add it to a catalog.
A while ago, I wrote an article on my personal blog on how Use Ant to Deploy Automation Scripts. In the article, I walked through configuring a Publish Channel to export and an Enterprise Service to import Script and LaunchPoint information. I then provided an Ant script that could post data to the Enterprise Service. The reason for this script is to make it easy to deploy Automation Scripts from a source control repository like SVN or Git. While Migration Manager make it easy to migrate changes from one environment to another, it does not integrate nicely with a source control tool.
I recently needed to diagnose out of memory problems with Maximo. There is some information in the Maximo logs that can help. Maximo can display mbo counts and free memory information. Maximo will also log the number of active users and when crons execute.
We’ve all seen the dreaded “Record has been updated by another user. Refetch and try again.” It can happen when the record has been updated by another user, but it can also happen when the record is updated by the same user more than once. In memory, an MboSet owns zero or more MBOs. Each of those MBOs can have zero or more MboSets which in turn own zero or more MBOs. Naturally, if your MboSets contain zero MBOs you won’t have problems with records updated by another user. Problems will arise if two different MBOs reference the same database record and both MBOs attempt to update data. In memory, these MBOs will be represented as separate Java objects and will be owned by different MboSets. If only one MBO is updated, it won’t be a problem. If both MBOs are updated, the first will update the database record and change the ROWSTAMP value. The second will attempt to update the record but will fail because the ROWSTAMP doesn’t match. This will trigger an MXRowUpdateException.
When deciding to expand Maximo usage to a mobile deployment, one of the primary considerations is ensuring the system will be both scalable and secure. Delivering data updates securely is important. Mobile Informer uses TLS transport encryption end to end. Supporting a complete offline experience requires supporting all of the Maximo business rules and supporting data by preemptively synchronizing all relevant data.