Why do I not receive the memo via email?

In Maximo, :WFASSIGNMENT.CURRENTMEMO can be used as a way to include memo's in communications that are sent out. The current memo tag was designed to work from task nodes and will not work with other nodes. If added to other nodes, the memo added when the record is routed will not be included in the communications sent.

How can I make a field required conditionally for a specific group of users?

Using a Data Restriction to make a field 

Conditionally Required by Security Group

• In the Security Groups application there is a Data Restriction tab.
• In this tab there are three tabs, select the Attribute tab.
• The attribute tab allows you to create an attribute level restriction.
• Select the Attribute tab and select the New Row button.
• Enter the object value for the table the attribute belongs to.
• Enter the attribute value.
• If you want the restriction to be specific to an application enter an application value.
• Leave this blank for it to restrict in all applications it appears in.
• Select the type, in this case Required
• Use the double arrows next to the Condition field to launch to the Condition Expression Manager application to create your condition or if you already have a condition associate it.
• Save
• After all active user sessions that existed before the change end, the users will see this change take effect. ( Better to re-start Server once )

On what topic you want me to explain?

Dear Friends;

On what topic you want me to write next post for you. I will fell happy to help you guys. Please fell free to write me.

Email : ratnesh1982singh@gmail.com

Enabling auditing for Application Designer

Many time during my implementation, I found issue how to track changes done in application designer, It is very clear that as Maximo Implementer we are more worried about tracking changes which we had not done in application designer. Many times we use external system to maintain versions of XMLs and all.

One answer of this concern is “Enabling auditing for Application Designer”

Resolving the problem

1. Go to Database Configuration app and bring up the MAXPRESENTATION object.

2. Mark the 'Audit Enabled' field to true.

3. In the Attributes tab, mark the checkbox 'Audit Enabled' for the 3 attributes in the list.

4. Save it and apply the configuration changes.

5. Do some tests in the Application Designer, import some XML files and query the A_MAXPRESENTATION in the database.

Changing the default port in WebSphere Application Server

Changing the default port in WebSphere Application Server

Sometimes we may need to change the default port of a WebSphere Application Server installation as a security precaution or for some other reasons like for coexisting with another WAS installation on the same machine. Moreover it’s always better to change the default ports in production environments. You can follow the below steps to change the default http port.

1.       Logon to your admin console 

2.       Click on Servers à Application servers à .

3.       Click on Ports link under communications, under the Configuration tab. (If you expand the Ports section click on details).

4.       Click on the port name you want to change. Here I am changing the default http transport port. So I clicked on WC_defaulthost port.

5.       Enter the port number you want to use in port text box. (Please make sure that port is not already used by someone else). Apply and save the changes. After entering the new port the WC_defaulthost will look like the one in the below image.

6.       Now click on Environment à Virtual Hosts. This page would display all the virtual hosts present in the system.

7.       Click on default_host.

8.       Click on Host Aliases.

9.       Click on the port you want to change.

10.   Enter the new port number.

Apply and Save the changes to Master Repository. You are done. Restart the server and now the server will start binding to the new port.

BMXAA6454E - Database configuration is in process. The ConfigDB and RestoreFromBackup actions must complete before the Maximo server can start.

If you restart the server while an action is being performed on the database, the server restart may fail. You will see a message similar to the following in the SystemOut log files: "java.lang.Exception: BMXAA6454E - Database configuration is in process.

The ConfigDB and RestoreFromBackup action s must complete before the Maximo server can start.

 Or sometime It is possible for configdb to leave a flag set, which can stop Maximo from starting.

Run the following SQL

select * from MAXVARS where varname='CONFIGURING';

Check the VARVALUE returned. It will be a '1' to signify that configdb is running . If it is not, then do not continue and call into support to report the error.

update MAXVARS set varvalue='0' where varname='CONFIGURING';

This will reset the flag that signifies configdb to be running.

Maximo should now start.

How is the field -Life to Date for Asset(ASSETMETER.LIFETODATE)-calculated?

The assetmeter.lifetodate (Life to Date for Asset) calculation is done in a java class (DeployedMeter.class) that can be found in the Maximo root directory, e.g:

\Maximo\applications\maximo\businessobjects\classes\psdi\app\meter folder.
In this class, the method (calculateAverageALL) will do the calculation.

It first gets the meter lifetodate.

Then it will check if (newDate !=null && newDate.before(earliestReadingDate))

If it is true, then it will set:

lifetodate = lifetodate - new Meter Reading

Otherwise, it will set:

lifetodate = lifetodate - oldest DB Reading

At last, it will return the Average ALL as:

return lifetodate / denominator

With the Denominator being the date Delta between earliest and recent time.