Inserting into Long Description

ibm maximo a3jgroup

To start off with, long descriptions are essential for multiple different reasons.  They are often used for extra space to write out a descriptive description or used to map multiple fields from a data migration project. In my case we were mapping multiple different fields into the long description. There are some key steps you must follow for the long description to show up with your values.  In my case I followed most steps I found online but missed one crucial step. Let’s breakdown the steps.

Figure out which attribute in Maximo will have the long description tied to. (In my example we will be tying it to the DESCRIPTION attribute.)

We must make sure ISLDOWNER is checked in the database configuration for the specific attribute in the specific object you chose.


Next is to insert the long description data. In my case we are inserting from a different database to Maximo database. (You must have access to Maximo database)Next is to insert the long description data. In my case we are inserting from a different database to Maximo database. (You must have access to Maximo database)

insert into longdescription (ldkey, ldownertable, ldownercol, ldtext, langcode, contentuid, longdescriptionid) 
    select a.assetuid, 'ASSET','DESCRIPTION','Comments: '|| ld."Cmnt"|| CHR(10) ,'EN', longdescriptionseq.nextval, longdescriptionseq.nextval
from tblAssetHdrs@cmmsdev asset
inner join a3j_vwtblAssetTabCmnts@CMMSDEV ld on asset.EMID = ld.EMID and ld."TABID" = 41006
Most important step is updating the hasld to 1 per records that had long description. This will be an update statement in the database.

This will only update records that have a corresponding record in the long description table.


update asset set hasld=1 where exists(select 1 from longdescription where ldownertable='ASSET' and ldownercol='DESCRIPTION' and ldkey = asset.assetuid)


Now confirm that your long description is showing through the front end of Maximo. Click on the green box to the right of the description to open the long description.

It was successfully inserted above you will see the long description that was inserted.

In conclusion it is important to follow these steps thoroughly. If you miss one of these steps you won’t be able to see the long description from the front end.  This could cause more problems if you don’t know which step you missed.  Make sure to follow those steps when inserting into the long description.

Be sure to sign up here to be first to hear about any new blogs.

A3J Group, LLC is a boutique consulting firm specializing in enterprise asset management systems. Our experts have over 20 years experience in the space. We focus on all aspects of your maintenance projects from Functional to Technical to Executive and more.  We are a tech forward company with suites of in-house solutions developed to help maintenance systems deliver the most value possible. Want to learn more? Visit us at We look forward to working with you and coupling our expertise with your goals.

Using a Global System Properties in an Automation Script

Maximo has a neat feature where you can set any value in the global property, and it will default to that value you have entered. In order to use a global property, you first must create one. In our example we created a global property for the person who does the PO Reorder.

After you create the global property, ensure you click on Live Refresh, so you can use the new global property created.

This is helpful because I could now use this global property in my automation script.  In order to get the global property, First must create a variable like down below. “configData = MXServer.getMXServer().getSystemProperties()”

After that create another variable and get the property you have created.

“reorderAgent = configData.getProperty(“POReorderBuyer”)”

Once you completed these steps you can now use the variable “reorderAgent” which is grabbing the system property and you could use in the automation script any where you want. In our case we are setting the “PURCHASEAGENT” to the “reorderAgent” when the po description has reorder in it.

I highly recommend using this as it is helpful because now you don’t have to create a variable with the value hardcoded. So, example if this person ever goes on vacation, we could simply just adjust the global property value and this automation script will adjust the reorderAgent based on the new person we put. Instead of going into the automation script and changing the variable that was hardcoded.

We have a culture of education and paying it forward at A3J Group. Subscribe below to be the first to get the latest releases from our knowledge bank.

Log4J Security Vulnerability System Patching for WebSphere

At the end of 2021, many companies were faced with the log4j security vulnerabilities. This was a worldwide security that has caused a lot of problems. For users of IBM Maximo, their Maximo environments were not affected, however WebSphere was impacted. The vulnerability caused Apache Log4j to allow a remote attacker to execute arbitrary code on the system. If an attacker were to access the system they would be able to write access to the Log4j configuration and de-serialize untrusted data. If the deployed application is configured to use JMSAppender, an attacker could exploit this vulnerability to execute arbitrary code on the system. IBM has released a fixed for this issue in which the update removes the Apache Log4j from Admin Console and UDDI Registry application. The Log4j security vulnerability is resolved by upgrading WebSphere to or newer versions. If you are running on any 8.0 version of WebSphere then upgrading to or newer version will remedy the issue as well.


How to update WebSphere to the current version.

  1. Log into Maximo and go to System Information. Observe the WebSphere version.

ibm maximo system information websphere log4j security vulnerability blog

  1. Next, open the Services application and stop the following WebSphere services: IBM HTTP Server V9.0, IBM WebSphere Application Server V9.0-ctgCellManager01, IBM WebSphere Application Server V9.0-ctgNode01.

ibm maximo security patch log4j update fix

  1. Open the application, “IBM Installation Manager”.

a3j group troubleshooting ibm maximo blog log4j issue update

  1. After IBM Installation Manager opens, Click on “Update”

ibm installation manager update ibm maximo websphere log4j issue

5. Observe to see all of the packages that are available for an update. Click on the checkbox, “Update all packages with recommended updates and recommended fixes”

troubleshoot ibm maximo update websphere log4j issue a3j group

6. Log into your IBM account to download the recommended updates and fixes, then click “Next” after it finishes searching for the updates.

a3j group blog ibm maximo issue fix log4j websphere update

7. Accept the terms in the license agreements to proceed with the update.

ibm maximo patch log4j issue websphere update system

  1. In this view you can observe all of the updates that are going to occur before you click on the “Update” button. Then, click on Update.

a3j group blog patch ibm maximo log4j security vulnerability websphere update

  1. At this point, we have successfully updated WebSphere with all the recommended fixes and updates. Click “Finish”

ibm maximo blog a3j group websphere fix log4j security update

  1. Open the Services application, Start WebSphere back up by starting the following services: IBM HTTP Server V9.0, IBM WebSphere Application Server V9.0-ctgCellManager01, IBM WebSphere Application Server V9.0-ctgNode01.

security patch ibm maximo websphere integration log4j update a3j group blog

  1. Log into Maximo and go to System Information. Observe the new WebSphere version.

ibm maximo websphere integration security patch log4j issue blog update a3j group

Once, you have confirmed that your WebSphere system has been updated, you can rest assured that your Log4J security vulnerability has been remedied. As humans become more involved with technology and dependent on systems to run daily business operations, it is increasingly important to stay mindful of these types of breach opportunities. Emphasizing monitoring and remaining informed on the latest security vulnerabilities is imperative if you want your systems to remain impenetrable. Hopefully, this guide served you well in patching the Log4J security vulnerability! If you would like to receive an email when we post a new blog, subscribe below.