your log files are providing useful information....
This null pointer error in the [err] stream is potentially quite important although I can't tell if it is from the UI code or from an external interface.
You would need to reconfigure your server to provide some extra information - read the full post for instructions about how to reconfigure this.
Lets assume that the error is relevant.
The error is telling us that Maximo received a request (possibly from one of the new Graphite based applications) and that the InventoryService is trying to issue items.
It is calling the psdi.app.inventory.InventoryService.getItemSetIdFromSite method which is then trying to build a SQL statement to be executed. Presumably the SQL relies on the Site being populated to help determine the ItemSetId
The SqlFormat class is unable to build the SQL statement because an object is null.
So the code needs to be checked to ensure that all the appropriate data is provided
[err] java.lang.NullPointerException [err] at psdi.mbo.SqlFormat.setObject(SqlFormat.java:582) [err] at psdi.mbo.SqlFormat.setObject(SqlFormat.java:557)
[err] at psdi.app.inventory.InventoryService.getItemSetIdFromSite(InventoryService.java:291) [err] at psdi.app.inventory.InventoryService.createIssue(InventoryService.java:228) [err] at psdi.iface.app.isu.MaxISUProcess.createMboSet(MaxISUProcess.java:214) [err] at psdi.iface.mos.MosProcessImpl.processMboSet(MosProcessImpl.java:1850) [err] at psdi.iface.mos.MosProcessImpl.setMainMaximoTable(MosProcessImpl.java:1044) [err] at psdi.iface.mos.MosProcessImpl.fillMaximoTables(MosProcessImpl.java:808) [err] at psdi.iface.mos.MosProcessImpl.processExternalData(MosProcessImpl.java:346) [err] at psdi.iface.mos.MosProcessImpl.processObjectStructureService(MosProcessImpl.java:241) [err] at psdi.iface.mic.MicService.processObjectStructureData(MicService.java:937) [err] at psdi.iface.mic.MicService.processOSLCAsJSON(MicService.java:638) [err] at com.ibm.tivoli.maximo.oslc.provider.OSPOSTRouteHandler.handleRequest(OSPOSTRouteHandler.java:914) [err] at com.ibm.tivoli.maximo.oslc.provider.MaximoOslcProviderServlet.handleRoute(MaximoOslcProviderServlet.java:1378) [err] at com.ibm.tivoli.maximo.oslc.provider.MaximoOslcProviderServlet.processPostPut(MaximoOslcProviderServlet.java:1491) [err] at
I can't be sure if the err entry is related to your automation script error because there are no time/thread details.
Adding the following configuration will change the MAS configuration so that the WebSphere logger records the date/time/thread for all entries regardless of the source. Then you need to check the threadid in the revised log entries to see if the log entries were generated by the same thread and in the same time period
It is important to configure WebSphere so it can provide the most information for support staff.
Several sections require the POD to be stopped and a new POD started. All the settings can be applied in one operation with a single restart at the end of the configuration work – there is no need to restart the PODs after each change.
The key change here for your system are the references to "tbasic" as these will provide extra information.
1. Log in to MAS Suite Administration
2. Go To Workspaces, select Manage
3. From the Actions menu, select Update configuration
4. Click on the edit button next to Server Bundles
5. For each of the bundles:
a. Click on the “View” link in column Additional properties
b. In the box “Additional server config”, paste the following xml:
<?xml version='1.0' encoding='UTF-8'?>
<server>
<logging logDirectory="/logs" messageFileName="${env.HOSTNAME}_messages.log" maxFileSize="5" maxFiles="10" traceFormat="tbasic" consoleFormat="tbasic" messageFormat="tbasic" />
</server>
~
c. Click Save
6. Scroll to the top of the page and lick Apply Changes. This starts Activation of the Manage app and eventually restarts all Manage pods.