Topic
7 replies Latest Post - ‏2013-03-26T22:27:30Z by DMathews
SystemAdmin
SystemAdmin
5842 Posts
ACCEPTED ANSWER

Pinned topic Preventive Maintenance PM Import

‏2013-03-21T12:50:49Z |
Good timing

I'm trying to import new PM's with PMseasons using xml file.
I've created Object Structure with objects PM and PMSEASONS (with appropriate relationships).
Authorized Application is PM, consumed by INTEGRATION and Outbound Definition and Inbound Processing Classes fields is empty.
Then I created Publish Channel using my object structure. Through external system - publish channel - xmlfile end point exported file to get the xml schema.
After I created Enterprise Service with Sync operation and my object structure. Enabled Message Tracking. All other fields is empty.
In External Systems - Enterprise Services I've added my Enterprise Service, pressed Data Import (xml file, Import Preview) and selected xml file. Message about successful queuing appeared.
Then in Crone Tasks I rebooted JMS queue but there is no changes in PM list.

How can I find out what happens?

My xml is in attachments, there is Russian names, I already imported items this way - everything was fine
Updated on 2013-03-26T22:27:30Z at 2013-03-26T22:27:30Z by DMathews
  • SystemAdmin
    SystemAdmin
    5842 Posts
    ACCEPTED ANSWER

    Re: Preventive Maintenance PM Import

    ‏2013-03-21T13:17:28Z  in response to SystemAdmin
    Is it ok that Outbound Definition and Inbound Processing Classes fiels are empty? It probably problem is

    I tried psdi.app.pm and of course this class not found
  • andrejm
    andrejm
    52 Posts
    ACCEPTED ANSWER

    Re: Preventive Maintenance PM Import

    ‏2013-03-21T14:53:18Z  in response to SystemAdmin
    Hi,

    First of all, you don't need the publish channel since it is only for outgoing messages (export). However, it does not hurt to have it, so that's not the problem. How is your enterprise service setup within the external system? Does it have the "Use Continuous Queue" checkbox checked? If so, then the messages will not require a cron task to be processed, they will be processed directly by the MDB. For a correct MDB setup, please refer to this: http://publib.boulder.ibm.com/infocenter/tivihelp/v27r1/index.jsp?topic=%2Fcom.ibm.itam_upgrWas.doc%2Finstall%2Ft_tamit_modifying_before.html

    You have enabled message tracking, which is good. Do you have any entries in the Message Reprocessing application (Go To > Integration > Message Reprocessing)? If the messages are failing at the entry level, this is where you will get a notification about the error. Unfortunately I cannot test your XML because of specific values (like ASSETNUM, SITEID, ORGID, STORELOC etc.) which are obviously not in my system. I was however able to test it once I substituted those with the values which can be found in the test system which I used.

    Andrej Marinic | Maximo Consultant @ Code Development Ltd.
    • SystemAdmin
      SystemAdmin
      5842 Posts
      ACCEPTED ANSWER

      Re: Preventive Maintenance PM Import

      ‏2013-03-22T08:35:48Z  in response to andrejm
      I tried both use and do not use Continuous Queue. When I was importing Items it worked only with *un*checked "Use Continuous Queue". All Items imported successfully, so shall I perform changes from publib.boulder.ibm.com?

      And what I found - there is no lines
      <container-transaction>
      <method>
      <ejb-name>JMSContQueueProcessor-1</ejb-name>
      <method-name>*</method-name>
      </method>

      <trans-attribute>Required</trans-attribute>

      </container-transaction>
      in ibm-ejb-jar-bnd.xmi, should I add this lines or skip this part of change?

      Anyway, are In/Outbound classes needed to be specified in *object structure*?
      • SystemAdmin
        SystemAdmin
        5842 Posts
        ACCEPTED ANSWER

        Re: Preventive Maintenance PM Import

        ‏2013-03-22T09:00:49Z  in response to SystemAdmin
        Also there is no sign of PM importing in tracked messages
    • SystemAdmin
      SystemAdmin
      5842 Posts
      ACCEPTED ANSWER

      Re: Preventive Maintenance PM Import

      ‏2013-03-25T07:51:07Z  in response to andrejm
      What I found in log file:

      25 Мар 2013 10:07:48:682 INFO cronAction start for Integration crontask JMSQSEQCONSUMER.SEQQOUT for queue=jms/maximo/int/queues/sqout with selector= for server MXServer
      25 Мар 2013 10:07:48:682 INFO cronAction end for Integration crontask JMSQSEQCONSUMER.SEQQOUT for queue=jms/maximo/int/queues/sqout with selector= for server MXServer
      25 Мар 2013 10:07:48:713 INFO cronAction start for Integration crontask JMSQSEQCONSUMER.SEQQIN for queue=jms/maximo/int/queues/sqin with selector= for server MXServer
      25 Мар 2013 10:07:48:713 INFO cronAction end for Integration crontask JMSQSEQCONSUMER.SEQQIN for queue=jms/maximo/int/queues/sqin with selector= for server MXServer
      25 Мар 2013 10:08:13:838 INFO ASSET: mbosets (24), mbos (null)
      25 Мар 2013 10:08:13:838 INFO CRONTASKDEF: mbosets (22), mbos (44)
      25 Мар 2013 10:08:13:838 INFO CRONTASKINSTANCE: mbosets (18), mbos (62)
      25 Мар 2013 10:08:13:838 INFO CRONTASKPARAM: mbosets (44), mbos (128)
      25 Мар 2013 10:08:13:838 INFO EMAIL: mbosets (20), mbos (20)
      25 Мар 2013 10:08:13:838 INFO ESCALATION: mbosets (19), mbos (38)
      25 Мар 2013 10:08:13:838 INFO ESCREFPOINT: mbosets (19), mbos (38)
      25 Мар 2013 10:08:13:838 INFO ESCSTATUS: mbosets (19), mbos (19)
      25 Мар 2013 10:08:13:838 INFO INVENTORY: mbosets (12), mbos (16)
      25 Мар 2013 10:08:13:838 INFO LOCATIONMETER: mbosets (6), mbos (12)
      25 Мар 2013 10:08:13:838 INFO LOCATIONS: mbosets (28), mbos (36)
      25 Мар 2013 10:08:13:838 INFO MAXAPPS: mbosets (10), mbos (137)
      25 Мар 2013 10:08:13:838 INFO MAXGROUP: mbosets (4), mbos (15)
      25 Мар 2013 10:08:13:838 INFO MAXMENU: mbosets (25), mbos (4625)
      25 Мар 2013 10:08:13:838 INFO MAXMESSAGES: mbosets (1), mbos (null)
      25 Мар 2013 10:08:13:838 INFO MAXMODULES: mbosets (2), mbos (46)
      25 Мар 2013 10:08:13:838 INFO MAXOBJECT: mbosets (19), mbos (38)
      25 Мар 2013 10:08:13:838 INFO MAXSESSION: mbosets (2), mbos (4)
      25 Мар 2013 10:08:13:838 INFO MAXUSER: mbosets (16), mbos (32)
      25 Мар 2013 10:08:13:838 INFO MAXVARS: mbosets (18), mbos (44)
      25 Мар 2013 10:08:13:838 INFO METER: mbosets (6), mbos (12)
      25 Мар 2013 10:08:13:838 INFO PERSON: mbosets (20), mbos (40)
      25 Мар 2013 10:08:13:838 INFO PM: mbosets (49), mbos (108)
      25 Мар 2013 10:08:13:838 INFO PMFORECAST: mbosets (46), mbos (48)
      25 Мар 2013 10:08:13:838 INFO PMMETER: mbosets (78), mbos (84)
      25 Мар 2013 10:08:13:838 INFO REORDERITEMS: mbosets (4), mbos (4)
      25 Мар 2013 10:08:13:838 INFO REORDERMUTEX: mbosets (12), mbos (16)
      25 Мар 2013 10:08:13:838 INFO REORDERPAD: mbosets (4), mbos (4)
      25 Мар 2013 10:08:13:838 INFO REPORTRUNLOCK: mbosets (1), mbos (1)
      25 Мар 2013 10:08:13:838 INFO REPORTRUNQUEUE: mbosets (2), mbos (2)
      25 Мар 2013 10:08:13:838 INFO SIGOPTION: mbosets (1), mbos (3708)
      25 Мар 2013 10:08:13:838 INFO SITE: mbosets (43), mbos (102)
      25 Мар 2013 10:08:13:838 INFO SYNONYMDOMAIN: mbosets (19), mbos (38)
      25 Мар 2013 10:08:13:838 INFO WFAPPTOOLBAR: mbosets (1), mbos (1)
      25 Мар 2013 10:08:13:838 INFO WOGEN: mbosets (6), mbos (null)
      25 Мар 2013 10:08:13:838 INFO WORKORDER: mbosets (23), mbos (23)
      25 Мар 2013 10:08:13:838 INFO BMXAA6372I - Host name: 172.17.218.138. Server name: MXServer. Cronetask name: REPORTLOCKRELEASE.REPORTLOCKRELEASE1. Последнее выполнение: 2013-03-25 10:07:48.0
      25 Мар 2013 10:08:13:838 INFO BMXAA6372I - Host name: 172.17.218.138. Server name: MXServer. Cronetask name: REPORTUSAGECLEANUP.REPORTUSAGECLEANUP1. Последнее выполнение: 2013-03-25 10:00:09.0
      25 Мар 2013 10:08:13:838 INFO BMXAA6372I - Host name: 172.17.218.138. Server name: MXServer. Cronetask name: BBCron.BBCRON1. Последнее выполнение: 2013-03-25 10:00:44.0
      25 Мар 2013 10:08:13:838 INFO BMXAA6372I - Host name: 172.17.218.138. Server name: MXServer. Cronetask name: XMLFILECONSUMER.BULK_LOAD. Последнее выполнение: 2013-03-25 10:07:43.0
      25 Мар 2013 10:08:13:838 INFO BMXAA6372I - Host name: 172.17.218.138. Server name: MXServer. Cronetask name: KPICronTask.KPINONREALTIME. Последнее выполнение: 2013-03-22 00:00:00.0
      25 Мар 2013 10:08:13:838 INFO BMXAA6372I - Host name: 172.17.218.138. Server name: MXServer. Cronetask name: ESCALATION.ESC1039. Последнее выполнение: 2013-03-25 10:08:13.0
      25 Мар 2013 10:08:13:838 INFO BMXAA6372I - Host name: 172.17.218.138. Server name: MXServer. Cronetask name: PMWoGenCronTask.PM.УАТ.01. Последнее выполнение: 2013-03-25 10:07:48.0
      25 Мар 2013 10:08:13:838 INFO BMXAA6372I - Host name: 172.17.218.138. Server name: MXServer. Cronetask name: KPICronTask.KPI.HRS.ПР1.УАТ. Последнее выполнение: 2013-03-25 10:00:08.0
      25 Мар 2013 10:08:13:838 INFO BMXAA6372I - Host name: 172.17.218.138. Server name: MXServer. Cronetask name: ReorderCronTask.СКЛ_ЭЛЦ. Последнее выполнение: 2013-03-25 10:07:48.0
      25 Мар 2013 10:08:13:838 INFO BMXAA6372I - Host name: 172.17.218.138. Server name: MXServer. Cronetask name: AsyncImmediateJobCron.AsyncImmediate. Последнее выполнение: 2013-03-25 10:08:06.0
      25 Мар 2013 10:08:13:838 INFO BMXAA6372I - Host name: 172.17.218.138. Server name: MXServer. Cronetask name: JMSQSEQCONSUMER.SEQQIN. Последнее выполнение: 2013-03-25 10:07:48.0
      25 Мар 2013 10:08:13:838 INFO BMXAA6372I - Host name: 172.17.218.138. Server name: MXServer. Cronetask name: PMWoGenCronTask.PMWoGenCronTask. Последнее выполнение: 2013-03-21 16:38:56.0
      25 Мар 2013 10:08:13:838 INFO BMXAA6372I - Host name: 172.17.218.138. Server name: MXServer. Cronetask name: ESCALATION.ESC1037. Последнее выполнение: 2013-03-25 10:08:08.0
      25 Мар 2013 10:08:13:838 INFO BMXAA6372I - Host name: 172.17.218.138. Server name: MXServer. Cronetask name: AsyncScheduledJobCron.AsyncScheduled. Последнее выполнение: 2013-03-25 10:07:48.0
      25 Мар 2013 10:08:13:838 INFO BMXAA6372I - Host name: 172.17.218.138. Server name: MXServer. Cronetask name: JMSQSEQCONSUMER.SEQQOUT. Последнее выполнение: 2013-03-25 10:07:48.0
      25 Мар 2013 10:08:13:838 INFO BMXAA6372I - Host name: 172.17.218.138. Server name: MXServer. Cronetask name: ESCALATION.ESC1038. Последнее выполнение: 2013-03-25 10:08:06.0
      25 Мар 2013 10:08:13:838 INFO BMXAA6372I - Host name: 172.17.218.138. Server name: MXServer. Cronetask name: ESCALATION.ESCESCBLTNEXP. Последнее выполнение: 2013-03-24 17:00:37.0
      25 Мар 2013 10:08:13:838 INFO BMXAA6372I - Host name: 172.17.218.138. Server name: MXServer. Cronetask name: AsyncJobCleanupCron.AsyncJobCleanup. Последнее выполнение: 2013-03-25 05:00:37.0
      25 Мар 2013 10:08:13:838 INFO BMXAA6372I - Host name: 172.17.218.138. Server name: MXServer. Cronetask name: ESCALATION.ESCWO CHECKBACKLOG. Последнее выполнение: 2013-03-22 17:31:39.0
      25 Мар 2013 10:08:13:838 INFO BMXAA6369I - Хост сервера: 172.30.67.200. Server name: MXServer. Число пользователей: 1
      25 Мар 2013 10:08:13:838 INFO BMXAA6369I - Хост сервера: 172.17.218.138. Server name: MXServer. Число пользователей: 1. WebClientSessions: (1)
      25 Мар 2013 10:08:13:838 INFO BMXAA6370I - Общее число пользователей, подключенных к системе: 2
      25 Мар 2013 10:08:13:838 INFO BMXAA7019I - Общий объем памяти - 536870912, а объем доступной памяти - 217914600.
      25 Мар 2013 10:08:18:682 INFO cronAction start for Integration crontask JMSQSEQCONSUMER.SEQQIN for queue=jms/maximo/int/queues/sqin with selector= for server MXServer
      25 Мар 2013 10:08:18:682 INFO cronAction end for Integration crontask JMSQSEQCONSUMER.SEQQIN for queue=jms/maximo/int/queues/sqin with selector= for server MXServer
      25 Мар 2013 10:08:18:682 INFO cronAction start for Integration crontask JMSQSEQCONSUMER.SEQQOUT for queue=jms/maximo/int/queues/sqout with selector= for server MXServer
      25 Мар 2013 10:08:18:682 INFO cronAction end for Integration crontask JMSQSEQCONSUMER.SEQQOUT for queue=jms/maximo/int/queues/sqout with selector= for server MXServer
      25 Мар 2013 10:08:43:682 ERROR Invalid Expression
      java.lang.RuntimeException: Invalid Expression
      at psdi.iface.stax.MXStAXParser.evaluateXPath(MXStAXParser.java:294)
      at psdi.iface.stax.MXStAXParser.evaluateXPath(MXStAXParser.java:435)
      at psdi.iface.mic.MicUtil.prepareEntSrvMsgTrkInfo(MicUtil.java:1232)
      at psdi.iface.load.FileLoaderProcess.writeToQueue(FileLoaderProcess.java:247)
      at psdi.iface.load.FileLoaderProcess.processData(FileLoaderProcess.java:514)
      at psdi.iface.load.DefaultInboundXMLSplitter.splitPerformed(DefaultInboundXMLSplitter.java:145)
      at psdi.iface.stax.EventStAXSplitter.fireSplitEvent(EventStAXSplitter.java:359)
      at psdi.iface.stax.EventStAXSplitter.populateRepeatBlocks(EventStAXSplitter.java:334)
      at psdi.iface.stax.EventStAXSplitter.traverseToRepeatBlock(EventStAXSplitter.java:251)
      at psdi.iface.stax.EventStAXSplitter.split(EventStAXSplitter.java:93)
      at psdi.iface.load.XmlFileLoaderImpl.processXMLData(XmlFileLoaderImpl.java:107)
      at psdi.iface.load.LoadXMLFileCronTask.processData(LoadXMLFileCronTask.java:398)
      at psdi.iface.load.LoadXMLFileCronTask.cronAction(LoadXMLFileCronTask.java:218)
      at psdi.server.CronTaskManager.callCronMethod(CronTaskManager.java:1552)
      at psdi.server.CronTaskManager.access$400(CronTaskManager.java:83)
      at psdi.server.CronTaskManager$CronThread.run(CronTaskManager.java:2070)
      25 Мар 2013 10:08:43:682 INFO BMXAA4199E - The remote object of the server cannot be accessed. A network error has occured.
      Invalid Expression
      psdi.util.MXSystemException: BMXAA4199E - The remote object of the server cannot be accessed. A network error has occured
      Invalid Expression
      at psdi.iface.mic.MicUtil.prepareEntSrvMsgTrkInfo(MicUtil.java:1263)
      at psdi.iface.load.FileLoaderProcess.writeToQueue(FileLoaderProcess.java:247)
      at psdi.iface.load.FileLoaderProcess.processData(FileLoaderProcess.java:514)
      at psdi.iface.load.DefaultInboundXMLSplitter.splitPerformed(DefaultInboundXMLSplitter.java:145)
      at psdi.iface.stax.EventStAXSplitter.fireSplitEvent(EventStAXSplitter.java:359)
      at psdi.iface.stax.EventStAXSplitter.populateRepeatBlocks(EventStAXSplitter.java:334)
      at psdi.iface.stax.EventStAXSplitter.traverseToRepeatBlock(EventStAXSplitter.java:251)
      at psdi.iface.stax.EventStAXSplitter.split(EventStAXSplitter.java:93)
      at psdi.iface.load.XmlFileLoaderImpl.processXMLData(XmlFileLoaderImpl.java:107)
      at psdi.iface.load.LoadXMLFileCronTask.processData(LoadXMLFileCronTask.java:398)
      at psdi.iface.load.LoadXMLFileCronTask.cronAction(LoadXMLFileCronTask.java:218)
      at psdi.server.CronTaskManager.callCronMethod(CronTaskManager.java:1552)
      at psdi.server.CronTaskManager.access$400(CronTaskManager.java:83)
      at psdi.server.CronTaskManager$CronThread.run(CronTaskManager.java:2070)
      Caused by:
      java.lang.RuntimeException: Invalid Expression
      at psdi.iface.stax.MXStAXParser.evaluateXPath(MXStAXParser.java:294)
      at psdi.iface.stax.MXStAXParser.evaluateXPath(MXStAXParser.java:435)
      at psdi.iface.mic.MicUtil.prepareEntSrvMsgTrkInfo(MicUtil.java:1232)
      ... 13 more
      25 Мар 2013 10:08:43:682 INFO Error writing to queue inbound transaction's document/line 1. system#exception. system#exception
      psdi.util.MXSystemException: system#exception
      at psdi.iface.load.FileLoaderProcess.writeToQueue(FileLoaderProcess.java:334)
      at psdi.iface.load.FileLoaderProcess.processData(FileLoaderProcess.java:514)
      at psdi.iface.load.DefaultInboundXMLSplitter.splitPerformed(DefaultInboundXMLSplitter.java:145)
      at psdi.iface.stax.EventStAXSplitter.fireSplitEvent(EventStAXSplitter.java:359)
      at psdi.iface.stax.EventStAXSplitter.populateRepeatBlocks(EventStAXSplitter.java:334)
      at psdi.iface.stax.EventStAXSplitter.traverseToRepeatBlock(EventStAXSplitter.java:251)
      at psdi.iface.stax.EventStAXSplitter.split(EventStAXSplitter.java:93)
      at psdi.iface.load.XmlFileLoaderImpl.processXMLData(XmlFileLoaderImpl.java:107)
      at psdi.iface.load.LoadXMLFileCronTask.processData(LoadXMLFileCronTask.java:398)
      at psdi.iface.load.LoadXMLFileCronTask.cronAction(LoadXMLFileCronTask.java:218)
      at psdi.server.CronTaskManager.callCronMethod(CronTaskManager.java:1552)
      at psdi.server.CronTaskManager.access$400(CronTaskManager.java:83)
      at psdi.server.CronTaskManager$CronThread.run(CronTaskManager.java:2070)
      Caused by:
      psdi.util.MXSystemException: BMXAA4199E - The remote object of the server cannot be accessed. A network error has occured.
      Invalid Expression
      at psdi.iface.mic.MicUtil.prepareEntSrvMsgTrkInfo(MicUtil.java:1263)
      at psdi.iface.load.FileLoaderProcess.writeToQueue(FileLoaderProcess.java:247)
      ... 12 more
      Caused by:
      java.lang.RuntimeException: Invalid Expression
      at psdi.iface.stax.MXStAXParser.evaluateXPath(MXStAXParser.java:294)
      at psdi.iface.stax.MXStAXParser.evaluateXPath(MXStAXParser.java:435)
      at psdi.iface.mic.MicUtil.prepareEntSrvMsgTrkInfo(MicUtil.java:1232)
      ... 13 more
    • SystemAdmin
      SystemAdmin
      5842 Posts
      ACCEPTED ANSWER

      Re: Preventive Maintenance PM Import

      ‏2013-03-25T09:18:45Z  in response to andrejm
      Changed External Message ID and Search ID to "PM" value instead incorrect value - error in log file disapeared, there is no errors in log file now, but PM still not imported
      • DMathews
        DMathews
        4 Posts
        ACCEPTED ANSWER

        Re: Preventive Maintenance PM Import

        ‏2013-03-26T22:27:30Z  in response to SystemAdmin
        Check your inbound queue to see if there are messages in the queue. I have had experiences where a message was "stuck" in my queue. Once I cleared out the queue the messages began processing normally.

        You can go to your web host (WebLogic/WebSphere) to view your queue, or you can view the queue (in Maximo 7.x) by going to Integration -> External Systems, Select Action -> Add/Modify Queues.

        From there you can click on a queue and either view the data inside of it, or delete the data in the queue (which is what I had to do).