Maximo EAR building and deployment takes too much time to complete

Hi,

There could be many reason for this but one of the reason I found is "Antivirus scanning every new file getting created on the server". During EAR building several files will be created, every file will be scanned by the antivirus software on the server. This can make whole process of EAR building slow. You can prevent this by following steps below.

Antivirus software considered in the explanation below is symantec endpoint protection. You can follow similar steps for the antivirus on your server.

1. Open Symantec endpoint protection console
2. Click on the options button
3. Select change settings
4. Goto "File-Systems auto protect" tab
5. Click on centralized exceptions button
6. Click on "Add->Security Risk Exception->Folder"
7. Select "D:\IBM\" or the maximo installation folder
8. Click Close
9. Click OK
10. Done, for next time when you build and deploy EAR. It will be very fast.
 

Add an attribute to maximo table from backend.

Hi,

You can use simple script below to add attribute to maximo table from backend. Follow the steps below.

1. Make sure you have write permission to the maximo database.
2. Connect to maximo database using utility like SQL Developer or TOAD
3. Execute two SQL statements below

insert into maxattributecfg (OBJECTNAME,ATTRIBUTENAME,ALIAS,AUTOKEYNAME,ATTRIBUTENO,CANAUTONUM,CLASSNAME,COLUMNNAME,DEFAULTVALUE,DOMAINID,EAUDITENABLED,ENTITYNAME,ESIGENABLED,ISLDOWNER,ISPOSITIVE,LENGTH,MAXTYPE,MUSTBE,REQUIRED,PERSISTENT,PRIMARYKEYCOLSEQ,REMARKS,SAMEASATTRIBUTE,SAMEASOBJECT,SCALE,TITLE,USERDEFINED,CHANGED,SEARCHTYPE,MLSUPPORTED,MLINUSE,HANDLECOLUMNNAME,MAXATTRIBUTEID,RESTRICTED,LOCALIZABLE,TEXTDIRECTION,COMPLEXEXPRESSION)
values ('MAXSESSION', 'XUNIT', 'XUNIT', null, 19, 0, null,'XUNIT', null, null, 0, 'MAXSESSION',0,0,0,20,'UPPER',0,0,1,null,'Unit of the current session',null,null,0,'Session Unit',1,'I','NONE',0,0,null,MAXATTRIBUTECFGSEQ.NEXTVAL,0,0,null,null);

update maxobjectcfg set changed = 'A' where objectname = 'MAXSESSION';

4. Commit changes.
5. Run configDB from database configuration application or stop application server and run it from command prompt. (configdb.bat)
6. Done