CSIDE Demos, Maximo VM, Online VMs

CSIDE Demos are fantastic.

You can use SkyTape to access several online VMs which open in your browser and give feeling of working on a VM on you machine itself.

For this, you will need CSIDE Account i.e. SkyTape Account.

You need to send a mail to cside@us.ibm.com to create a SkyTape account which you will use to access VMs having Maximo and other applications.

Error 500: java.lang.NullPointerException

Error:

Error 500: java.lang.NullPointerException


Solution:

Check if your Database is working and getting connected using maximo user.

Difference between ASSETID and ASSETUID

Difference between ASSETID and ASSETUID

I got confused when I saw ASSET table having extra unique column ASSETUID. Now, I could see 3 unique identifiers for Asset Number in Asset Table in Maximo (v6 onwards).

• ASSETNUM - is SITE specific and Unique at Site Level (well known, nothing new)
• ASSETID - default field, created by DB Configuration in Maximo when you create an MBO, associated with a Sequence
• ASSETUID - this is ACTUALLY the UNIQUE field of ASSET table in Maximo, this is also associated with a Sequence

Key things which I noticed in Maximo:

• When you add a Long Description to an Asset record, it's ASSETUID is copied to LDKEY attribute of LONGDESCRIPTION table. (in other objects e.g. LOCATIONS, LOCATIONSID is copied to LDKEY)
• When you Move/Modify any Asset from one Site to another, Asset record gets copied to the other Site and the existing one is set to DECOMMISSIONED. In this case, ASSETID value of both the records will be same but ASSETUID for the new (moved) Asset record will be changed.

So, it can be said that ASSETUID is the UNIQUE field of ASSET table.

thanks for reading...

Maximo or WebSphere Installation stopped in between...

Running taskrunner.bat file with parameter

what to do next....

This solution will work for following 2 problem scenarios:

1. If Maximo/WebSphere/Fix Pack Installation has stopped in between due to some issue/error
2. If during the installation, you have deferred the Application Deployment or Updatedb (as shown in the screen grab)

Solution:

After Installation is complete whether Successful or Unsuccessful, you can run TaskRunner.bat file. It resumes the installation from the point of the failure or deferred point.

To Run TaskRunner:

1. Using a command prompt, go to  ibm\smp\scripts folder

2. Run TaskRunner command as below:

taskrunner.bat CONTINUE STOPONERROR 

Thanks for reading...

IWAE0008E An error occurred reading mbojava.jar

IWAE0008E An error occurred reading mbojava.jar

MxServer got started but maximo application is not starting in WebSphere.

I wrote a class file for Maximo Customization for one of the business requirement. I could build maximo.ear successfully. Later, I deployed it in WebSphere 7 which was also done successfully. Howerver, after starting MXServer I noticed - MXServer is UP but Maximo application is not due to which I was unable to login to my Maximo application.

Following are the errors which were reported in systemout.log file.

org.eclipse.jst.j2ee.commonarchivecore.internal.exception.NestedJarException: IWAE0008E An error occurred reading mbojava.jar from \IBM\WebSphere\AppServer\profiles\ctgAppSrv01\config\cells\ctgCell01\applications\maximo.ear\deployments\maximo

Stack trace of nested exception:
java.io.FileNotFoundException: \IBM\WebSphere\AppServer\profiles\ctgAppSrv01\installedApps\ctgCell01\maximo.ear\mbojava.jar (The system cannot find the file specified.)
    at java.io.FileInputStream.<init>(FileInputStream.java:123)
    at java.io.FileInputStream.<init>(FileInputStream.java:83)
    at org.eclipse.jst.j2ee.commonarchivecore.internal.strategy.DirectoryLoadStrategyImpl.getInputStream(DirectoryLoadStrategyImpl.java:827)
    at org.eclipse.jst.j2ee.commonarchivecore.internal.strategy.NestedArchiveLoadStrategyImpl.getZipInputStream(NestedArchiveLoadStrategyImpl.java:296)
    at org.eclipse.jst.j2ee.commonarchivecore.internal.strategy.NestedArchiveLoadStrategyImpl.safeGetZipInputStream(NestedArchiveLoadStrategyImpl.java:336)
.................................
................................. not writing the entire trace







First, I tried to look for the solution and explored here and there. Finally, I restarted the Node and Resynchronized the nodes and it worked.

Then I restarted my MxServer and it got up along with maximo application and I could log in.

Still finding the reason why this happened....your comments will help me to understand this.

Thank you for reading...

SRVE0068E

SRVE0068E: Uncaught exception created in one of the service methods of the servlet /webclient/login/login.jsp in application MAXIMO

Environment: WebSphere 7, Maximo 7.5, Maximo Anywhere, DB2 9.7

I got this error after installing Worklight Server while installing Maximo Anywhere in my development environment. I could install and see newly created WorkLight Server in WebSphere (where MXServer is displayed). I started both MXServer and newly created WorkLight Server, they both started. However, one of them was only working at a time.

When checked in Systemout.log of MXServer, complete error stack track looked like:

E com.ibm.ws.webcontainer.servlet.ServletWrapper service SRVE0068E: Uncaught exception created in one of the service methods of the servlet /webclient/login/login.jsp in application MAXIMO. Exception created : java.lang.NullPointerException
    at psdi.server.MXServer.getProperty(MXServer.java:4093)
    at psdi.webclient.system.runtime.WebClientRuntime.getWebClientSystemProperty(WebClientRuntime.java:1736)
    at psdi.webclient.system.runtime.WebClientRuntime.getWebClientSystemProperty(WebClientRuntime.java:1719)
    at com.ibm._jsp._login._jspService(_login.java:246)


Looked for solution, found one link:

http://www-01.ibm.com/support/docview.wss?uid=swg1PK92140

Then came to know that issue is with the number of concurrent database allowed by DB2

I checked if my database is working, to my surprise-my database was not getting connected.

Found one more very interesting blog:

http://db2commerce.com/2012/03/07/introducing-parameter-wednesday-dbm-cfg-numdb/

So it was basically DB2 parameter NUMDB which was stopping me to start my application. By default the value of this parameter was 2 which I changed to 5 using the following command:

db2 update dbm cfg using NUMDB 5

After updating the value, I restarted the DB2 service and I could start both the applications successfull.

Thanks for reading....