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.
Has anyone used interface tables in MIF? We have managed to setup the queues and messages properly. We have created the interface tables and both the table queues (MXOUT and MXIN). We are trying to export the PERSON table (using the MAXIMO out of box Object Structure).
We tried exporting using XML as the endpoint and it is working fine. However in the Publish Channel when we change the endpoint to Interface table, it does not seem to populate the tables. I noticed that it still creates the XML file though.
We have setup everything as per the documentation as follows:
1. Enabled the JMSQSEQCONSUMER
2. Enabled the IFACETABLECONSUMER
3. Enabled the listener in the Publish Channel
4. Checked the Support Flat Structure in the Object Structure
We have setup the interface tables in the local database.
Regards,
PK
We are using WEBLOGIC as the application server.
Regards,
--- In MAXIMO@yahoogroups.com, "Priyaranjandas" <pkk0574@...> wrote:
>
> Has anyone used interface tables in MIF? We have managed to setup the queues and messages properly. We have created the interface tables and both the table queues (MXOUT and MXIN). We are trying to export the PERSON table (using the MAXIMO out of box Object Structure).
>
> We tried exporting using XML as the endpoint and it is working fine. However in the Publish Channel when we change the endpoint to Interface table, it does not seem to populate the tables. I noticed that it still creates the XML file though.
>
> We have setup everything as per the documentation as follows:
>
> 1. Enabled the JMSQSEQCONSUMER
> 2. Enabled the IFACETABLECONSUMER
> 3. Enabled the listener in the Publish Channel
> 4. Checked the Support Flat Structure in the Object Structure
>
> We have setup the interface tables in the local database.
>
> Regards,
> PK
>
When you said you enabled the JMSQSEQCONSUMER, I assume you enabled the sqout instance, right?
I don't understand when you said "However in the Publish Channel when we change the endpoint to Interface table, it does not seem to populate the tables". You specify the end point in the external system, not the publish channel. Just to make sure you aren't missing anything, did you specify the interface table name in the publish channel you wish to export?
When you modify a person record, can you see in the log file where it says it wrote to the queue?
________________________________
From: Priyaranjandas <pkk0574@yahoo.com>
To: MAXIMO@yahoogroups.com
Sent: Monday, July 16, 2012 1:53 AM
Subject: [MAXIMO List] Re: MIF using Interface tables - MAXIMO version 7.1
We are using WEBLOGIC as the application server.
Regards,
--- In MAXIMO@yahoogroups.com, "Priyaranjandas" <pkk0574@...> wrote:
>
> Has anyone used interface tables in MIF? We have managed to setup the queues and messages properly. We have created the interface tables and both the table queues (MXOUT and MXIN). We are trying to export the PERSON table (using the MAXIMO out of box Object Structure).
>
> We tried exporting using XML as the endpoint and it is working fine. However in the Publish Channel when we change the endpoint to Interface table, it does not seem to populate the tables. I noticed that it still creates the XML file though.
>
> We have setup everything as per the documentation as follows:
>
> 1. Enabled the JMSQSEQCONSUMER
> 2. Enabled the IFACETABLECONSUMER
> 3. Enabled the listener in the Publish Channel
> 4. Checked the Support Flat Structure in the Object Structure
>
> We have setup the interface tables in the local database.
>
> Regards,
> PK
>
Hi Greg,
We have enabled the SEQOUT instance in the JMSSEQCONSUMER (checked the active flag).
Excuse me for the confusion about endpoint in the Publish Channel. What I meant was that I have specified the endpoint in the "Publish Channel" tab in the External System application and not in the Publish Channel application itself.
I was using the Data Export feature under the Publish Channel tab in the External System application to test it. Also to be honest, since I am relatively new, I am not aware how to access the log file and look for where it has written to the queue. If you would be able to let me know how to, I can check and find it out.
Thanks & Regards,
PK
--- In MAXIMO@yahoogroups.com, Greg Robinson <robigd2923@...> wrote:
>
> When you said you enabled the JMSQSEQCONSUMER, I assume you enabled the sqout instance, right?Â
>
> I don't understand when you said "However in the Publish Channel when we change the endpoint to Interface table, it does not seem to populate the tables". You specify the end point in the external system, not the publish channel. Just to make sure you aren't missing anything, did you specify the interface table name in the publish channel you wish to export?Â
>
> When you modify a person record, can you see in the log file where it says it wrote to the queue?
>
>
> ________________________________
> From: Priyaranjandas <pkk0574@...>
> To: MAXIMO@yahoogroups.com
> Sent: Monday, July 16, 2012 1:53 AM
> Subject: [MAXIMO List] Re: MIF using Interface tables - MAXIMO version 7.1
>
>
> Â
> We are using WEBLOGIC as the application server.
>
> Regards,
>
> --- In MAXIMO@yahoogroups.com, "Priyaranjandas" <pkk0574@> wrote:
> >
> > Has anyone used interface tables in MIF? We have managed to setup the queues and messages properly. We have created the interface tables and both the table queues (MXOUT and MXIN). We are trying to export the PERSON table (using the MAXIMO out of box Object Structure).
> >
> > We tried exporting using XML as the endpoint and it is working fine. However in the Publish Channel when we change the endpoint to Interface table, it does not seem to populate the tables. I noticed that it still creates the XML file though.
> >
> > We have setup everything as per the documentation as follows:
> >
> > 1. Enabled the JMSQSEQCONSUMER
> > 2. Enabled the IFACETABLECONSUMER
> > 3. Enabled the listener in the Publish Channel
> > 4. Checked the Support Flat Structure in the Object Structure
> >
> > We have setup the interface tables in the local database.
> >
> > Regards,
> > PK
> >
>
>
>
>
>
>