Removing temporary data : -When installing Maximo Base Services 7.5 or Base Services Fixpack 7.1 you get an error: CTGIN2489E.

Removing temporary data

If you have modified the Maximo database since you installed another product or component, make sure all of your changes are completed before you begin a new upgrade or installation procedure.

All changes must be committed to the database before you can upgrade an existing product or install a new product or component. Tables whose names begin with "XX" are temporary tables that must be dropped before installing. If these tables exist, you will see error CTGIN2489E when you run an upgrade or installation procedure.

Temporary data can exist in your database in these situations:

• You are upgrading an existing product after configuring and using it.
• You are installing a new product or component in an environment where you have already installed another product, and configured and used that product.
• You are using the installer to add a feature or function that you did not implement when you first installed your product.

If you are in one of these situations, check whether you have any uncommitted changes or temporary tables in your database.

1. To confirm that all changes have been committed, run the following SQL query against the Maximo database:

   SELECT count(*) from maxobjectcfg where changed != 'N'

   'N' indicates that a change has been committed. For this query, if entries are returned with a value of 0 instead of N, you must commit those changes. Follow these steps to commit the changes:
   1. Click Go To > System Configuration > Platform Configuration > Database Configuration.
   2. From the Select Action menu, click Manage Admin Mode.
   3. Click Turn Admin Mode ON.
   4. Click OK, then wait for a few minutes for the change to take effect.
   5. From the Select Action menu, click Apply Configuration Changes. Monitor the process to completion.
   6. From the Select Action menu, click Manage Admin Mode.
   7. Click Turn Admin Mode OFF.
   8. Stop the MXServer.
   9. On the administrative Workstation, open a command prompt. Change to the directory c:\ibm\smp\maximo\tools\maximo.
   10. Run the following commands:

       configdb.bat
       dropbackup.bat
       dropbackup.bat

       The dropbackup.bat command is run twice. This should complete the commitment of all database changes.
2. Determine whether any temporary tables exist in your database, using the command appropriate to your database:

   DB2®

   select count(*) from sysibm.systables where name like 'XX%' and 
   creator = 'MAXIMO'

   Microsoft SQL Server

   SELECT count(*) FROM sysobjects WHERE xtype = 'U' AND name like 'XX%'

   Oracle

   SELECT count(*) from all_tables where table_name like 'XX%'

   If the returned value is not 0, follow these steps to drop the temporary tables:
   1. On the administrative Workstation, open a command prompt. Change to the directory c:\ibm\smp\maximo\tools\maximo.
   2. Run the following commands:

      configdb.bat
      restorefrombackup.bat
      dropbackup.bat
      dropbackup.bat 

      The dropbackup.bat command is run twice. This should drop all the temporary tables in the database.

Now you can proceed with your upgrade or installation procedure.

Integrity Checker reports BMXAA0494E errors on table COMMLOG.

Problem

After upgrading a Maximo 6.2 database to 7.1, several columns on table COMMLOG do not match the way that the columns are defined in Maximo.

Issue

In Integrity Checker report:
BMXAA0443E -- ERROR -- BMXAA0494E -- The Maximo definition of this column does not match the actual column:
BMXAA6841I - COMMLOG.BCC, Maximo definition is CLOB, Database column is VARCHAR2(4000)
BMXAA0443E -- ERROR -- BMXAA0494E -- The Maximo definition of this column does not match the actual column:
BMXAA6841I - COMMLOG.CC, Maximo definition is CLOB, Database column is VARCHAR2(4000)
BMXAA0443E -- ERROR -- BMXAA0494E -- The Maximo definition of this column does not match the actual column:
BMXAA6841I - COMMLOG.SENDTO, Maximo definition is CLOB, Database column is VARCHAR2(4000)

Resolving the problem

1. For each column, add to table COMMLOG a new column with data type CLOB. For example:
Alter Table commlog Add bccnew CLOB;
2. Copy the original column to the new column. For example:
Update commlog Set bccnew = bcc ;
3. Drop the original column. For example:
Alter Table commlog Drop Column bcc ;
4. Rename the new column to the original name. For example:
Alter Table commlog Rename Column bccnew To bcc ;
5. Run Integrity Checker again to verify that the errors are no longer reported.

Upgrade to Maximo 7.5 fails in UpdateDB script V7500_343.

Problem(Abstract)

When upgrading the Maximo database to 7.5.0.x, UpdateDB can fail in script V7500_343.dbc:


BMXAA7025E -- Script failed while running.;

A statement failed to execute inside a freeform statement;

sql#1407;
ORA-01407: cannot update ("INVENTORY"."COSTTYPE") to NULL

-- BEGINUPDATEDBERROR

-- Product: Tivoli's process automation engine
-- Error running file: V7500_343
-- UPDATEDBFILE:V7500_343.dbc

Symptom

The V7500_343 freeform statement that fails is:

update inventory set inventory.costtype = case
when ( select maxvars.varvalue from maxvars where maxvars.varname = 'COSTFROMASSET' and maxvars.siteid = inventory.siteid ) = '1'
and ( select item.rotating from item where item.itemnum = inventory.itemnum and item.itemsetid = inventory.itemsetid ) = 1
then ( select value from synonymdomain where synonymdomain.domainid = 'COSTTYPE' and synonymdomain.maxvalue = 'ASSET' and synonymdomain.defaults = 1 )
when ( select maxvars.varvalue from maxvars where maxvars.varname = 'DEFISSUECOST' and maxvars.siteid = inventory.siteid ) = 'AVGCOST'
then ( select value from synonymdomain where synonymdomain.domainid = 'COSTTYPE' and synonymdomain.maxvalue = 'AVERAGE' and synonymdomain.defaults = 1 )
when ( select maxvars.varvalue from maxvars where maxvars.varname = 'DEFISSUECOST' and maxvars.siteid = inventory.siteid ) = 'STDCOST'
then ( select value from synonymdomain where synonymdomain.domainid = 'COSTTYPE' and synonymdomain.maxvalue = 'STANDARD' and synonymdomain.defaults = 1 )
else ( select maxvars.varvalue from maxvars where maxvars.varname = 'DEFISSUECOST' and maxvars.siteid = inventory.siteid ) end

If the Maximo database was originally built using MAXDEMO data, rows can exist in the Inventory table that do not have a valid SiteID. As UpdateDB populates new column Inventory.CostType, the invalid SiteID values prevent the script from determining values to populate CostType for these old MAXDEMO records.

Upgrade 7.1 to 7.5.

Diagnosing the problem

If this query returns any values, then your database contains Inventory records with invalid SiteIDs:

Select siteid From inventory Where siteid Not In (Select siteid From maxvars Where varname In
('COSTFROMASSET', 'DEFISSUECOST') ) ;

Resolving the problem

Since these Inventory records are old MAXDEMO data, they serve no purpose and should be removed from your database. Replace XX in the following statement with any invalid SiteID values returned from the query above:

Delete From inventory Where siteid='XX'

Restore your database to pre-upgrade 7.1, remove the bad rows from the Inventory table, and run UpdateDB over again.

Using the middleware installation program to install DB2 9.7 on a Red Hat v6 system results in an error related to missing prerequisites

Problem(Abstract)

Using the middleware installation program to install DB2 9.7 on a Red Hat v6 system results in the following error:

CTGIN9080E: libaio.so.1, libstdc++.so.5 and libstdc++.so.6 packages are
required for DB2.

This error can occur even if the prerequisite checking tool was used to verify prerequisites on the system.

Resolving the problem

The problem is solved by installing libstdc++-4.4.4-13.el6.i686.rpm

which installs /usr/lib/libstdc++.so.6 and /usr/lib/libstdc++.so.6.0.13.

Error CTGIN9053E reported when using the middleware installation program

Problem(Abstract)

When using the middleware installation program, an error similar to the following is displayed:

CTGIN9053E: The partition /data has 100618240 bytes free space, but the
deployment plan requires 1073741824 bytes free space on that partition.
Increase available space in /data.

In this scenario, the middleware installation program was launched from the /data directory, but was not selected as the destination directory for the installation.

Resolving the problem

This error occurs when the middleware installation program is started from a directory that does not include the free space required to install the middleware selected. This error will be reported even if you select a different file system to install the middleware into that does have sufficient space.

The solution to this error is to start the middleware installation program from the same partition as the default home location for users. For example, /home.

The middleware installation program crashes during the WebSphere installation step for the authentication service on Red Hat v6 platforms.

Problem(Abstract)

The middleware installation program crashes during the WebSphere installation step for the authentication service.

Symptom

The middleware installation program crashes. The following error is reported in the console window where the middleware installation program was started:

./mwi_zlinux.bin: line 1965: 13290 Killed -Djava.io.tmpdir=?/tm? -Dtemp.dir=?/tmp? -Dis.jvm.home=?/tmp/istemp/_bundlesJRE_? -Dis.jvm.tmp=?1? -Dis.media.home=?? -Dis.launcher.file=?/mwi_zlinux.bin -Dis.jvm.file=?/tmp/istmp/_bundledJRE_/jvm? -Dis.externel.home=?? run 1>&1 2>&1

Resolving the problem

1. Start the middleware installer and choose the partial undeploy option to undeploy the J2EE server.

2. Once the J2EE server (WebSphere) undeployment is successful, start the middleware installer again and proceed with the Restart the plan option.

If the middleware installer crashes again during installation of the authentication service, restart the middleware installer and proceed with the Restart the plan option, which will result in a successful deployment.

Making specific attributes from Classifications required

In Maximo 7.x, you have an option that allows you to mark specific classification attributes as required, however, there are some steps that can help you on achieving this functionality, and make some of your classification attributes as "Required". For this, you will need to use the Conditional Expression Manager application.

First off, make sure you are logged into Maximo as user Maxadmin.

You need to create your own Classification record, in Classifications application, as below (i.e. BOBCLASS01, in this example to be used with ASSET object).
Then, create some attributes for this Classification record, such as AT1, AT2 and AT3 below. (in this example we will make the AT2 required)




Then, a record was created on the CLASSSTRUCTURE table for the Classification you added. (Note that the CLASSSTRUCTUREID value for it is 1322)
You can check it by using a SQL Editor against you Maximo database, as below.





Go to Conditional Expression Manager application and insert a new Condition record like this one below (where you would like to have the AT2 attribute required, for the BOBCLASS01 classification):




Go to Security Groups application, search for the security group that your user belongs to, and add a Data Restriction for it, setting the condition for the ASSETSPEC.ALNVALUE (just because all of the classification attributes were set to ALN data type) to become REQUIRED where the attribute name is AT2 (The classification BOBCLASS01 has AT1, AT2 and AT3 as valid attributes)



Save record in Security Groups application, then log out and log into Maximo as an user which belongs to the Security Group you just updated. (BOBGROUP1, in my example)




Go to Assets application, add a new asset, select the BOBCLASS01 classification.

After filling alphanumeric values for AT1 and AT3 fields , except AT2 , this is the message that you will get :






Then once you fill an alphanumeric value for AT2 , the record can be saved fine.

Configuring Maximo in Internet Explorer to use the file prompt for attaching files that are not being uploaded

There have been security changes in more recent browsers that prevent us from using the file select prompter when the user wants to attach a file but NOT upload it.  Because of this, now when the user chooses not to upload the file to the server, the file prompter is replaced by a text box.  In this text box the user must enter the full file path and file name manually.  This is not controlled by Maximo Asset Management; it is based on browser security tightening. 

In Firefox there is no way to change that behavior.  However, in Internet Explorer we can allow the user to retain the usage of the file prompter. There is a new system property added mxe.doclink.usefileprompt to enable a browse button to select file attachments that are not copied to the default location.

To retain use of the file prompter, complete the following steps:

1. Locate the mxe.doclink.usefileprompt property.
2. Set the property to 1 to display the browse button on Internet Explorer. (The browse button will not work on Firefox.)
3. Additionally, complete the following steps to change an Internet Explorer security setting on the client machine:
   1. Navigate to Tools > Internet Options.
   2. On the Security tab select the zone you want.
   3. Click Custom Level.
   4. Under Miscellaneous, select Enable for the following property:

Include local directory path when uploading files to a server.

Configuring the type-ahead feature

Overview

Are you a Maximo Asset Management customer at fixpack 7.5.0.2 or above? Would your Asset Management users like to complete their day-to-day activities more quickly AND type less?  Then you should consider configuring the type-ahead feature on your Maximo Asset Management server.

 

Sample Type-ahead

The type-ahead feature is enabled as part of the Client-Side validation feature delivered in Maximo Asset Management 7.5.0.2.  By default this feature is disabled on upgrade as it changes the user experience for your users. It also requires asynchronous data validation to be enabled on your server, which also changes the user experience.  You should read the blog entry Enabling the asynchronous data validation functionality in IBM Maximo Enterprise to understand asynchronous validation. 

 

Enabling Type-ahead

Client-side validation can be enabled for all domain-backed fields by changing one system property.  Change the mxe.webclient.ClientDataValidation to 1.

After you enable the property shown above and restart your server, if your users start typing values in any field backed by a SYNONYM, ALN, or NUMERIC domain, they will receive suggestions that match the value or description of those domain choices based on their input.  Here’s a screenshot of the Reported Priority field from the Create SR application after I’ve typed ‘1’.

Your end users can use the up and down arrow keys to select the appropriate matching option from the suggested options.  If your end users clear the typed value, they can see all the options and use the up and down arrow keys to select the desired value.

Finally if I type a string, it will also match on the description of the NUMERIC domain choices attached to this Reported Priority field.

Notice if I type ‘i’ for instance, both High and Medium will match:

This is a nice way to give your users an easier way to find the correct Numeric value.

 

Adding Type-ahead to fields

You also have the option of adding type-ahead to other fields in your user interface.  A common use case is adding type-ahead to Reported By field of the Create Service Request application.

To add type-ahead to this field, first define a table domain for this field to limit your choices.  Type-ahead will send all potential choices that match the field to the end-user's browser and currently has a hard-coded limit of 10,000 records.  Because you might have more than 10,000 people in the system, limit the available choices by defining a new table domain in the Domains application. Set the List Where Clause of the domain to a sql filter that limits the person records returned.

Now go to the Database Configuration application and associate this table domain with the Reported By field of the SR object and apply your changes (Turn on Admin Mode, apply your database changes, and turn off Admin Mode).

Now go to the Application Designer application, open the Create Service Request application, and launch the properties pane for this field.

Under the Advanced tab, click Configure Type-Ahead.

First add the PERSONID field as a Key.  Then add any additional attributes you want to display (and search) in the type-ahead contents beneath.  You’ll notice if you select the Reported By field, it also automatically adds the phone and email underneath; if you want this to be automatically set by the type-ahead, you’ll need to use the Configure Set Values option.  (If you don’t do this, eventually the asynchronous logic will set it, but the user experience is a little weird.)

i

Now save your updated application in Application Designer.

When you type any string in the Reported By field, it will match on these fields and you can use the up and down arrows to select the correct match.

UI framework event handling

Application Event Model

Overview

Events are sent to the user interface framework whenever an end user clicks a toolbar button in the application toolbar, selects an action listed in the Select Action menu, clicks a push button within the user interface, or selects an option from a menu next to a field.  Many other types of user interactions also send events to the user interface framework, but those widgets previously listed are the ones that application developers are mostly likely to configure.

This article explains what events are sent to the user Interface framework when your end users interact with those types of widgets. We will also explain how the user interface event handling framework handles those events.  This article should allow you adjust your user interface to use a wide variety of widgets to fire and handle events to best meet your end users usability needs.

Toolbar Button Events

       Example "Save" Toolbar Button

       Find the Signature Option that corresponds to the Save button

Select Action Menu Events

       Example Menu Action “Duplicate Action”

Choosing a Select Action menu item causes the user Interface framework to receive an event that matches the Signature Option id associated with this Select Action menu item.   In the example above, the user Interface framework would receive an event called “DUPLICATE” based on the details of the configured Signature Option as shown below.

       Translating a Select Action to the Underlying Event

Configuring Push Button Events

Example Select Members Push Button

You can associate a push button with an event using the “Event” field in Application Designer or using the “mxevent” attribute in the presentation xml. You can optionally specify the ID of a control that processes the event using the “Target ID” field in Application Designer or “targetid” in the presentation xml.

When an end user clicks the button, the event ID specified in that panel above “selectmembers” is received by the user interface event handling framework.

Popup Menu Events

Each field-level popup menu has underlying mxevents associated with each of the menu choices.

       Example Popup Menu

       Configuration of Popup Menu for this Field

       Actual Popup Menu for this Field (from Menus.xml)

Notice the events listed for each of the choices shown.  That event string is the event that gets sent to the underlying user Interface framework when this menu choice is clicked.

User Interface Framework Event Handling

The user interface framework processes the event received in this order:

1. First the framework checks to see if the event matches a signature option (sigoption) ID.
   1. If the event does match, the user interface framework checks to see if the user has privileges for that signature option.
   2. If they do have security privileges, the framework checks to see if there is a special flag set to handle the Signature option in an Advanced way.  If the Signature option does have a flag the user interface handles that flag accordingly.  So if the Signature Option is flagged as an Action then the User Interface invokes that action. Here is an example of a menu option that would start a System Configuration->Platform Configuration->Action called “INSERT” for the Action object instead of firing the default INSERT event. 

                      Setting Advanced Options to point a Signature option to an Action

                       The Underlying Action that would get called by the Advanced Sigoption Metadata Above

2. If there is not an “Advanced” Flag for this sigoption then the framework checks the target control/component to see if it handles such an event (by implementing a method that matches the event name.)  Events sent from Select Action and Toolbar buttons will rarely match this check as the target control/component for the Select Action and Toolbar buttons is the Application Toolbar, and it rarely handles the event directly.
3. If the control or component doesn’t have a method that matches then the framework will check to see if the DataBean or ApplicationBean associated with the target component/control has such a method; if it does then that method will be called.  The Select Action or Toolbar buttons are bound to the ApplicationBean, so will check there for a method that matches.  Buttons and Button groups can be bound to other Databeans based on where they are placed within the application.
4. If a targetid is not configured in the Application Designer for the events, the framework will check the Application Bean for the application to find a matching method.

                    Example Application Bean method to handle the INSERT signature option event

5. If the Application Bean doesn’t contain a matching method, the Mbo and MboSet of the DataBean will be checked for a matching method as well. 
6. If no such method exists or the method returns the integer constant for EVENT_CONTINUE, the framework will then check to see if there is a dialog in the current application with a dialog id that matches the event name.  If such a dialog exists then that dialog will be displayed.
7. Finally the framework will check to see if there is a dialog in the System Libraries that has a dialog ID that matches the event, and it will display the dialog in that case.

If all of these checks fail, NOTHING will happen when the event is received by the user Interface framework.

Example

So putting all this information together, let’s go through the use case where an Application Developer may want to add a button to the user interface that would expose a functionality that is also exposed in the Select Action menu.  For example, in the Inventory application, let’s add a button on the main Inventory tab that would trigger the 'Adjust Current Balance' that is typically available only from the Select Action menu.

First we’ll look at the Sigoptions defined in the Inventory application in Application Designer to find the right event:

       Event is CURBALADJ

Drag and drop a button group and push button onto the main Inventory tab and set the event to CURBALADJ to match the signature option above.

       Configuring the Pushbutton Event and Label

Save the Application.

Now from within the Available Balance section, your end users can click the Adjust Current Balance button and pop up that dialog.

       Current Balance Adjustment window

With all the information you learned above, you could even put a field-level menu next to the current balance that let you fire this event (rather than a push button.)

Hopefully this explanation of the event model will help you enhance your user interfaces to meet your end user requirements.

More Detailed Information

Technically when the end user interacts with each of those widgets above, a click event is sent to the component, and the component translates that click event into a queued event that matches the description given above.  Sometimes to help debug issues in the field, the user interface team might turn on javascript event tracking and you might see these click events being sent from the client.