This is an archive of the Maximo Yahoo Community. The content of this pages may be a sometimes obsolete so please check post dates.
Thanks to the community owner Christopher Wanko for providing the content.
I made the following changes to enable MEA/MIF processing in MAXIMO 7.5.
In file C:\ibm\SMP\maximo\applications\maximo\mboejb\ejbmodule\META-INF\ejb-jar.xml, I un-commented the following sections.
<!-- MEA MDB uncommented to enable Queue -->
<message-driven id="MessageDriven_JMSContQueueProcessor_1">
<ejb-name>JMSContQueueProcessor-1</ejb-name>
<ejb-class>psdi.iface.jms.JMSContQueueProcessor</ejb-class>
<transaction-type>Container</transaction-type>
<message-destination-type>javax.jms.Queue</message-destination-type>
<env-entry>
<env-entry-name>MESSAGEPROCESSOR</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>psdi.iface.jms.QueueToMaximoProcessor</env-entry-value>
</env-entry>
<security-identity>
<run-as>
<role-name>maximouser</role-name>
</run-as>
</security-identity>
</message-driven>
<!-- MEA MDB for error queue uncommented to enable Queue -->
<message-driven id="MessageDriven_JMSContQueueProcessor_2">
<ejb-name>JMSContQueueProcessor-2</ejb-name>
<ejb-class>psdi.iface.jms.JMSContQueueProcessor</ejb-class>
<transaction-type>Container</transaction-type>
<message-destination-type>javax.jms.Queue</message-destination-type>
<env-entry>
<env-entry-name>MESSAGEPROCESSOR</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>psdi.iface.jms.QueueToMaximoProcessor</env-entry-value>
</env-entry>
<env-entry>
<env-entry-name>MDBDELAY</env-entry-name>
<env-entry-type>java.lang.Long</env-entry-type>
<env-entry-value>30000</env-entry-value>
</env-entry>
<env-entry>
<env-entry-name>ERRORQUEUE</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>1</env-entry-value>
</env-entry>
</message-driven>
<!-- MEA MDB -->
<container-transaction>
<method>
<ejb-name>JMSContQueueProcessor-1</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
<!-- MEA MDB for error queue -->
<container-transaction>
<method>
<ejb-name>JMSContQueueProcessor-2</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
In files C:\ibm\SMP\maximo\applications\maximo\mboejb\ejbmodule\META-INF\ibm-ejb-jar-bnd.xmi, I un-commented the following sections.
<!-- MEA MDB -->
<ejbBindings xmi:type="ejbbnd:MessageDrivenBeanBinding" xmi:id="MessageDrivenBeanBinding_1" activationSpecJndiName="intjmsact">
<enterpriseBean xmi:type="ejb:MessageDriven" href="META-INF/ejb-jar.xml#MessageDriven_JMSContQueueProcessor_1"/>
</ejbBindings>
<!-- MEA MDB -->
<ejbBindings xmi:type="ejbbnd:MessageDrivenBeanBinding" xmi:id="MessageDrivenBeanBinding_1" activationSpecJndiName="intjmsacterr">
<enterpriseBean xmi:type="ejb:MessageDriven" href="META-INF/ejb-jar.xml#MessageDriven_JMSContQueueProcessor_2"/>
</ejbBindings>
Don't forget to rebuilt EAR and redeploy after you make the changes.
Hope this helps.
Jun Chen
--- In MAXIMO@yahoogroups.com, "raj_631" wrote:
>
> Hi Rae Simpson,
>
> Can you give more clearly, exactly where to enable these XML files.I'm bit confusing.
>
> Thanks in advance for your kind help.
>
> Thanks
>
> --- In MAXIMO@yahoogroups.com, "Rae Simpson" wrote:
> >
> > Here are the gory details of the solution:
> >
> >
> > Browse to: C:\ibm\SMP\maximo\applications\maximo\mboejb\ejbmodule\META-INF
> >
> > 2 files need to have XML enabled: ejb-jar.xml and ibm-ejb-jar-bnd.xmi
> >
> > Scan down to find sections - and
> >
> >
> > Uncomment those sections in both files. Rebuild the EAR, Deploy and away she goes.
> >
> > Thanks to Eugene Bonks at IBM support!
> >
> >
> > --- In MAXIMO@yahoogroups.com, "dave.littley" wrote:
> > >
> > > Figured it out... had to enable some code in a couple of XML files and then rebuild the ear file.
> > >
> > > Dave
> > >
> > > --- In MAXIMO@yahoogroups.com, Brian Swanson wrote:
> > > >
> > > > HI Dave,
> > > > Have you checked the interface tables and logic to make sure that the new
> > > > functionality like reorder field is being accounted for. I had the
> > > > similar thing happen in early development when I did not account for some
> > > > new functionality..
> > > >
> > > >
> > > >
> > > > Brian Swanson
> > > > Systems Analyst-Maximo
> > > > Information Technology
> > > >
> > > >
> > > > HermanMiller
> > > >
> > > >
> > > >
> > > > From: "dave.littley"
> > > > To: MAXIMO@yahoogroups.com
> > > > Date: 01/04/2012 01:28 PM
> > > > Subject: [MAXIMO List] Maximo 7.5 Upgrade - Integration Stopped
> > > > Working
> > > > Sent by: MAXIMO@yahoogroups.com
> > > >
> > > >
> > > >
> > > >
> > > > We recently upgraded to Maximo 7.5.
> > > >
> > > > Prior to the upgrade, we had the integration set up to use interface
> > > > tables for the items, inventory, and meters. After the upgrade, it stopped
> > > > working.
> > > >
> > > > The tricky part is that it seems to run fine. The entries get put into the
> > > > interface table and the queue table. Maximo processes the queue and the
> > > > record is removed from the queue table. No errors get put into the message
> > > > reprocessing log.
> > > >
> > > > But unfortunately, nothing is changed in the data. I dug through the log
> > > > files a bit and see where it attempted to change the data, but it gives a
> > > > 'Data array returned without transformation. bidiFormat is null' message
> > > > (error?). I've attached the portion of the log file below.
> > > >
> > > > Has anyone had a similar problem, or have any ideas how to fix it? Any
> > > > help would be greatly appreciated.
> > > >
> > > > Dave Littley
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > >
> >
>