Author |
Message
|
tczielke |
Posted: Wed Jun 03, 2015 12:36 pm Post subject: MQI or API? |
|
|
Guardian
Joined: 08 Jul 2010 Posts: 941 Location: Illinois, USA
|
I am probably being pedantic, but the MQ manual seems to switch terminology between the use of the terms MQI (Message Queue Interface) and API (Application Programming Interface) in different parts of the manual. In my mind, MQI = API. Does anyone disagree? I am trying to make sure I am not missing a subtlety here between the two terms, or if they are indeed synonymous. _________________ Working with MQ since 2010. |
|
Back to top |
|
 |
mqjeff |
Posted: Thu Jun 04, 2015 4:26 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
The MQI is a specific API.
The Java classes are a separate API.
The JMS support is a third API.
The .NET support is a fourth API.
etc. etc. etc...
PCF and mqsc are an administrative API. |
|
Back to top |
|
 |
tczielke |
Posted: Thu Jun 04, 2015 4:30 am Post subject: |
|
|
Guardian
Joined: 08 Jul 2010 Posts: 941 Location: Illinois, USA
|
Ok, so the MQI is the API for procedural languages then? Thanks, that helps! _________________ Working with MQ since 2010. |
|
Back to top |
|
 |
mqjeff |
Posted: Thu Jun 04, 2015 4:36 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
tczielke wrote: |
Ok, so the MQI is the API for procedural languages then? Thanks, that helps! |
The MQI is the API for procedural languages, or that can bind to C libraries. |
|
Back to top |
|
 |
bruce2359 |
Posted: Thu Jun 04, 2015 4:43 am Post subject: Re: MQI or API? |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
tczielke wrote: |
I am probably being pedantic, but ... |
More categorical than pedantic. Hereabouts we strive for precision and clarity. _________________ I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
Back to top |
|
 |
tczielke |
Posted: Thu Jun 04, 2015 7:12 am Post subject: Re: MQI or API? |
|
|
Guardian
Joined: 08 Jul 2010 Posts: 941 Location: Illinois, USA
|
bruce2359 wrote: |
tczielke wrote: |
I am probably being pedantic, but ... |
More categorical than pedantic. Hereabouts we strive for precision and clarity. |
Thanks for the encouragement, but I still do plan on attending my PA (Pedants Anonymous) meetings.  _________________ Working with MQ since 2010. |
|
Back to top |
|
 |
georgesmt |
Posted: Thu Aug 19, 2021 12:13 am Post subject: |
|
|
Newbie
Joined: 17 Dec 2020 Posts: 2
|
|
Back to top |
|
 |
bruce2359 |
Posted: Thu Aug 19, 2021 5:14 am Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
Your URL demands that I accept your cookies - no choice. Sorry, I only accept cookies from trusted sites.
IBM MQ product base API calls are collectively referred to as the MQI - Message Queue Interface. _________________ I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
Back to top |
|
 |
gbaddeley |
Posted: Thu Aug 19, 2021 3:37 pm Post subject: |
|
|
 Jedi Knight
Joined: 25 Mar 2003 Posts: 2538 Location: Melbourne, Australia
|
The early MQ programming references and guides (v5.0 and older) use the term "MQI", although the "API crossing exit" existed at that time.
The MQ 7.5 programming guide refers to "MQI", but acknowledges that it is an "API":
Quote: |
WebSphere MQ classes for Java encapsulates the Message Queue Interface (MQI), the native WebSphere MQ API, and uses the same object model as other object-oriented interfaces,... |
_________________ Glenn |
|
Back to top |
|
 |
NiaSmith |
Posted: Sat Oct 23, 2021 5:12 am Post subject: |
|
|
Newbie
Joined: 23 Oct 2021 Posts: 2
|
I am bit new to the Messaging world ...I was just reading about the WebSphere MQ and found that 'MQ' supported API for Java are
JMS and IBM's own Messaging API' (Message Queue Interface) ....
Can anyone please clear me on the question?
Which one is more better (JMS Vs MQI) to use ? What are the advantages of Using JMS API's at dissertation services uk...
Appreciate your responses ..!
Last edited by NiaSmith on Sun Oct 24, 2021 10:18 pm; edited 1 time in total |
|
Back to top |
|
 |
gbaddeley |
Posted: Sat Oct 23, 2021 4:36 pm Post subject: |
|
|
 Jedi Knight
Joined: 25 Mar 2003 Posts: 2538 Location: Melbourne, Australia
|
JMS (with MQ provider) and MQI are both commonly used in Java apps.
JMS is fairly generic and easy to use.
MQI code needs to deal with object instances for MQ connection, queue, options, etc, the various methods and properties, and MQ exception handling.
JMS does not expose all MQI features, so YMMV. _________________ Glenn |
|
Back to top |
|
 |
bruce2359 |
Posted: Sat Oct 23, 2021 6:23 pm Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
|
Back to top |
|
 |
gbaddeley |
Posted: Sun Oct 24, 2021 2:06 pm Post subject: |
|
|
 Jedi Knight
Joined: 25 Mar 2003 Posts: 2538 Location: Melbourne, Australia
|
|
Back to top |
|
 |
bruce2359 |
Posted: Sun Oct 24, 2021 2:49 pm Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
API is a generic term for user-programmable interface to some service. SQL is an example.
Function calls for O/S’s are also API’s. _________________ I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
Back to top |
|
 |
bruce2359 |
Posted: Mon Apr 04, 2022 3:57 am Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
In what way(s) are they different? _________________ I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
Back to top |
|
 |
|