MQ and SAP Business Connector
Title: MQ and SAP Business Connector Hi, I would like to know if there is anyone out there using SAP Business connector to send messages to / from WMQ? And if so, is there a specific adaptor required to set it up or can Business Connector be configured to communicate with WMQ directly? Thanks Andre = Disclaimer "The opinions contained in this message are those of the sender only and do not reflect those of Sappi Limited or any of its subsidiary or associated companies. This message may contain information which is private, privileged or confidential. If you are not the intended recipient of this message, please notify the sender thereof and destroy/delete the message. You may not copy, distribute or disclose the contents to anyone nor take any action in reliance on the content. Neither the sender nor Sappi Limited (including its subsidiaries and associated companies) shall incur any liability resulting directly or indirectly from accessing any of the attached files which may contain a virus or the like". Director names A list of Sappi companies and the names of their directors can be retrieved from http://www.sappi.com/home.asp?pid=644 =
Re: XML CDATA
Thanks Raul, that is what I was looking for. Don't know how I missed that. Andre -Original Message-From: MQSeries List [mailto:[EMAIL PROTECTED]Sent: Wednesday, November 17, 2004 11:07 PMTo: [EMAIL PROTECTED]Subject: Re: XML CDATA -- Insert the input message tree as CDATA embedded XML in the messageData element set OutputRoot.XML.RibMessages.ribMessage.messageData.(XML.CDataSection) = BlobToChar(BITSTREAM(InputRoot.XML.*[1])); Raul L. AcevedoSenior IT ArchitectEAI Application Innovation ServicesIBM Global Services818 230 5859 Office818-599-6626 Mobile[EMAIL PROTECTED] = Disclaimer "The opinions contained in this message are those of the sender only and do not reflect those of Sappi Limited or any of its subsidiary or associated companies. This message may contain information which is private, privileged or confidential. If you are not the intended recipient of this message, please notify the sender thereof and destroy/delete the message. You may not copy, distribute or disclose the contents to anyone nor take any action in reliance on the content. Neither the sender nor Sappi Limited (including its subsidiaries and associated companies) shall incur any liability resulting directly or indirectly from accessing any of the attached files which may contain a virus or the like". Director names A list of Sappi companies and the names of their directors can be retrieved from http://www.sappi.com/home.asp?pid=644 =
XML CDATA
I am creating an outbound XML message in which I want one of the elements to look something like this ... To simply create the element without CDATA I would use "set "OutputRoot"."XML"."Root".element1 = '#%^& any text '; How do I do the CDATA bit? I had a look at the ESQL reference and tried a few options like (XML.pcdata) and (XML.Content) but it does not do what I want. Your assistence would be appreciated. Thanks Andre = Disclaimer "The opinions contained in this message are those of the sender only and do not reflect those of Sappi Limited or any of its subsidiary or associated companies. This message may contain information which is private, privileged or confidential. If you are not the intended recipient of this message, please notify the sender thereof and destroy/delete the message. You may not copy, distribute or disclose the contents to anyone nor take any action in reliance on the content. Neither the sender nor Sappi Limited (including its subsidiaries and associated companies) shall incur any liability resulting directly or indirectly from accessing any of the attached files which may contain a virus or the like". Director names A list of Sappi companies and the names of their directors can be retrieved from http://www.sappi.com/home.asp?pid=644 =
Re: MMC/Any GUI for administering MQ on AIX
Title: RE: MMC/Any GUI for administering MQ on AIX Yes. All you need to do is create your user ID on the AIX box and add to the mqm user group(remember to refresh security). Then you should be able to add the AIX queue manager in your windows MQ explorer and manage it from there. You must be sure that on AIX you have started both the command server and listener. Also see the MQ documentation on remote administration. Andre van Zyl -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED]] Sent: 09 September 2004 02:28 To: [EMAIL PROTECTED] Subject: MMC/Any GUI for administering MQ on AIX Hello, I am relatively new to MQ. I have MQ Series setup on AIX box. Now, i want a way to administer it from my windows box by using some kind of GUI. I have MMC on my windows box that i am able to use to administer MQ Series on my local desktop. Can i use it to connect to MQ Series on AIX box to administer it. How ? I am not able to figure this out. Any other ideas on what kind of UI i can use for this purpose ? A Java UI running on AIX is ok too. Thanks Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive = Disclaimer This message may contain information which is private, privileged or confidential and is intended solely for the use of the individual or entity named in the message. If you are not the intended recipient of this message, please notify the sender thereof and destroy/delete the message. Neither the sender nor Sappi Limited (including its subsidiaries and associated companies) shall incur any liability resulting directly or indirectly from accessing any of the attached files which may contain a virus or the like. Director names A list of Sappi companies and the names of their directors can be retrieved from http://www.sappi.com/home.asp?pid=644 =
Re: Link for R/3 v1.2 on WMQ R530
Title: RE: Link for R/3 v1.2 on WMQ R530 Hi Kerry, We use SAP R3Link v1.2 on an AIX platform on MQ v5.2 (CSD4). The current installation has been running for a couple of years now without any problems. We have 2 outbound servers running for each SAP processor ( currently have 14 outbound servers running ). The open count on the R3LINK_OUT.TRANS queue is equal to the number of R3Link servers running. The Transmition queues however show the same symptoms as in your case. (eg The open output count on one of them is 517 although there are only about 80 remote queues). The maximum open handles setting on the queue manager is 256, but we have never had any errors like you have (and as I said, its been running for a couple of years now). The remote queue names' lengths are not all the same. Although I was initially concerned about this, it was working perfectly and I therefore did not do anything about it. We also do not ever stop/restart the servers - we have a restart script to ensure they are restarted if there was an SAP communication error that caused any of the servers to end. Hope this helps! Regards Andre -Original Message- From: Kerry Swemmer [mailto:[EMAIL PROTECTED]] Sent: 23 June 2004 01:08 To: [EMAIL PROTECTED] Subject: Link for R/3 v1.2 on WMQ R530 Hi All, I would like to ask a favour of those with SAPLink v1.2 running with MQ v5.3 We have a problem where outbound SAPLink servers are falling over intermittently with MQ reason code 2017, MaxHandles reached. We are running 2 outbound servers and I can see the open output counts on the XMITQ's continuously increasing during the day to numbers way above double the number of remote queue definitions on the qmgr. Looking at the output of an SMQ trace I suspect that SAPLink is not initialising the target queue name correctly and therefore opening queues that are already open, eventually reaching MaxHandles. I have tried logging a call with IBM but they refuse to help us because we (our customer) are on the "EOS" version 5.2 of MQ. They won't even try recreating the problem using WMQ R530 while we go through the lengthy process of getting MQ upgraded. I eventually asked them a question specific to the behaviour of SAPLink in the SMQ trace, also to no avail. All this on a "supported" version of MQSeries Link for R/3. The platform we are having the problem on is Sun Solaris, but I can see the same symptom on our other SAP platform, HP_UX, but those SAPLink servers get bounced every morning and don't use as many remote queues. So, firstly, has anybody come across the same problem before. Secondly, would those of you running SAPlink on MQ5.3 please have a look at your open output counts on your XMITQ's, try correlate this with your number of outbound servers and remote queues and let me know what you find. If all your remote queue names are the same length, and my theory is correct, you will not have this problem. Much appreciated. Cheers, Kerry Swemmer T-Systems South Africa (Pty) Ltd Database Administrator Computing and Desktop Services Address: DaimlerChrysler, 7 Settlers Way, East London, South Africa Postal Address: PO Box 671, East London, 5200 Phone: +27 (43) 706 2549 Fax: +27 (43) 706 2085 Mobile: +27 (83) 657 4151 E-mail: [EMAIL PROTECTED] Internet: www.t-systems.co.za Any views expressed in this message are those of the individual sender, and T-Systems South Africa (Pty) Ltd accepts no liability therefore, except where the sender specifically states them to be those of T-Systems South Africa (Pty) Ltd. Although this message has been scanned for the possible presence of computer viruses prior to despatch, T-Systems South Africa (Pty) Ltd cannot be held responsible for any viruses or other material transmitted with, or as part of, this message. Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive = Disclaimer This message may contain information which is private, privileged or confidential and is intended solely for the use of the individual or entity named in the message. If you are not the intended recipient of this message, please notify the sender thereof and destroy / delete the message. Neither the sender nor Sappi Limited (including its subsidiaries and associated companies) shall incur any liability resulting directly or indirectly from accessing any of the attached files which may contain a virus or the like. Director Names A list of Sappi companies and the names of their directors can be retrieved from http://www.sappi.com/home.asp?pid=644 =
Re: CSD 7 Now Available for MQ 5.3
Not as far as I know. Asked the IBM passport advantage support staff and they also said that there is no formal notification procedure - you should regularly watch the IBM webshpere web site or mailing lists like this one. Andre -Original Message-From: Mike Kenny - BCX - Infrastructure Services [mailto:[EMAIL PROTECTED]Sent: 15 June 2004 02:42To: [EMAIL PROTECTED]Subject: Re: CSD 7 Now Available for MQ 5.3 Is there some service/mailing list that one can subscribe to be informed of the availability of CSDs and the implications of applying/not applying the CSD? Thanks, Mike -Original Message-From: Anthony G Allison [mailto:[EMAIL PROTECTED]Sent: Tuesday, June 15, 2004 2:25 PMTo: [EMAIL PROTECTED]Subject: CSD 7 Now Available for MQ 5.3CSD 7 is now available for download from IBM for Websphere MQ 5.3. Lets hope this fixes all of the issues with CSD6! = Disclaimer This message may contain information which is private, privileged or confidential and is intended solely for the use of the individual or entity named in the message. If you are not the intended recipient of this message, please notify the sender thereof and destroy / delete the message. Neither the sender nor Sappi Limited (including its subsidiaries and associated companies) shall incur any liability resulting directly or indirectly from accessing any of the attached files which may contain a virus or the like. Director Names A list of Sappi companies and the names of their directors can be retrieved from http://www.sappi.com/home.asp?pid=644 =
Re: XML encoding="ibm-437"
Title: XML encoding="ibm-437" Yes, I used the reset content descriptor to change from MRM to XML and then changed the XML encoding setting. The MRM structure was created from a DTD which I imported. -Original Message-From: Govender Magendran [mailto:[EMAIL PROTECTED]Sent: 26 May 2004 12:22To: [EMAIL PROTECTED]Subject: Re: XML encoding="ibm-437" Hi I am not sure how you would do it in the MRM Domain. But before you output to the queue, you can reset to XML Domain and use SET OutputRoot.XML.(XML.XmlDecl).(XML.Encoding) = 'UTF-8'; Hope this helps. Regards Magendran Govender -----Original Message-From: van Zyl, Andre [mailto:[EMAIL PROTECTED]Sent: 25 May 2004 03:21To: [EMAIL PROTECTED]Subject: XML encoding="ibm-437"Importance: High Hi, I have an XML DTD which I imported into WMQ (version 2.1) and created a message type for it in MRM and I am using this to generate an XML output message. It works well, except for the fact that it somehow defaults to encoding="ibm-437". How do I change this to encoding="UTF-8"?? I checked in the "working with messages" manual, but could not find any details on this. Thanks Andre van Zyl = Disclaimer This message may contain information which is private, privileged or confidential and is intended solely for the use of the individual or entity named in the message. If you are not the intended recipient of this message, please notify the sender thereof and destroy / delete the message. Neither the sender nor Sappi Limited (including its subsidiaries and associated companies) shall incur any liability resulting directly or indirectly from accessing any of the attached files which may contain a virus or the like. Director Names A list of Sappi companies and the names of their directors can be retrieved from http://www.sappi.com/home.asp?pid=644 = Please click on the following link to read the Old Mutual legal notice: <http://www.oldmutual.co.za/e-mail_legal_notice> Alternatively, send a "blank" e-mail to <mailto:[EMAIL PROTECTED]> = Disclaimer This message may contain information which is private, privileged or confidential and is intended solely for the use of the individual or entity named in the message. If you are not the intended recipient of this message, please notify the sender thereof and destroy / delete the message. Neither the sender nor Sappi Limited (including its subsidiaries and associated companies) shall incur any liability resulting directly or indirectly from accessing any of the attached files which may contain a virus or the like. Director Names A list of Sappi companies and the names of their directors can be retrieved from http://www.sappi.com/home.asp?pid=644 =
Re: XML encoding="ibm-437"
Title: XML encoding="ibm-437" Problem solved. Instead of using "set OutputRoot.XML.XML.(XML."Encoding") = 'UTF-8' " I said "set OutputRoot.XML.(XML."Encoding") = 'UTF-8' " which did not work. -Original Message-From: van Zyl, Andre [mailto:[EMAIL PROTECTED]Sent: 25 May 2004 03:21To: [EMAIL PROTECTED]Subject: XML encoding="ibm-437"Importance: High Hi, I have an XML DTD which I imported into WMQ (version 2.1) and created a message type for it in MRM and I am using this to generate an XML output message. It works well, except for the fact that it somehow defaults to encoding="ibm-437". How do I change this to encoding="UTF-8"?? I checked in the "working with messages" manual, but could not find any details on this. Thanks Andre van Zyl = Disclaimer This message may contain information which is private, privileged or confidential and is intended solely for the use of the individual or entity named in the message. If you are not the intended recipient of this message, please notify the sender thereof and destroy / delete the message. Neither the sender nor Sappi Limited (including its subsidiaries and associated companies) shall incur any liability resulting directly or indirectly from accessing any of the attached files which may contain a virus or the like. Director Names A list of Sappi companies and the names of their directors can be retrieved from http://www.sappi.com/home.asp?pid=644 = = Disclaimer This message may contain information which is private, privileged or confidential and is intended solely for the use of the individual or entity named in the message. If you are not the intended recipient of this message, please notify the sender thereof and destroy / delete the message. Neither the sender nor Sappi Limited (including its subsidiaries and associated companies) shall incur any liability resulting directly or indirectly from accessing any of the attached files which may contain a virus or the like. Director Names A list of Sappi companies and the names of their directors can be retrieved from http://www.sappi.com/home.asp?pid=644 =
XML encoding="ibm-437"
Title: XML encoding="ibm-437" Hi, I have an XML DTD which I imported into WMQ (version 2.1) and created a message type for it in MRM and I am using this to generate an XML output message. It works well, except for the fact that it somehow defaults to encoding="ibm-437". How do I change this to encoding="UTF-8"?? I checked in the "working with messages" manual, but could not find any details on this. Thanks Andre van Zyl = Disclaimer This message may contain information which is private, privileged or confidential and is intended solely for the use of the individual or entity named in the message. If you are not the intended recipient of this message, please notify the sender thereof and destroy / delete the message. Neither the sender nor Sappi Limited (including its subsidiaries and associated companies) shall incur any liability resulting directly or indirectly from accessing any of the attached files which may contain a virus or the like. Director Names A list of Sappi companies and the names of their directors can be retrieved from http://www.sappi.com/home.asp?pid=644 =
Re: MQ Message statistics
Title: MQ Message statistics Thanks for all the ideas. I think that the best would be to purchase some lightweight WMQ monitoring tool, else if 100% accuracy is not an issue, one can simply look at channel / queue stats figures at regular intervals to compile the required information as required. Andre -Original Message-From: Adiraju, Rao [mailto:[EMAIL PROTECTED]Sent: 02 March 2004 11:03To: [EMAIL PROTECTED]Subject: Re: MQ Message statistics One simple option I can think off, is gathering the statistics from "Channel Status". Channel status will give you the number of messages and number of bytes transmitted. In absence of monitoring tools, I suggest to run a query every night to take a snap shot of channel status and analyse the figures from there (either through a script or program). I do know that channel sequence number gets reset after reaching it's maximum defined on the channel definition and you have to factor this in counting the messages. However, I am not sure how big are the other fields and when do they get reset - you have to give a go at them and see (unless somebody add some info from this forum). The fields of interest are: LSTSEQNO, BYTSSENT, BYTSRCVD, BUFSSENT, BUFSRCVD (and of course buffer size if you need). Let us know, how it goes. Cheers Rao From: van Zyl, Andre [mailto:[EMAIL PROTECTED] Sent: 2 March 2004 10:19 PMTo: [EMAIL PROTECTED]Subject: MQ Message statisticsImportance: High My client has requested that I give them statistics on MQSeries messages ( volumes etc) on a monthly basis. There is no MQ monitoring / admin software installed other than the standard MQ. We have a hub and spoke architecture, and all mq messages currently flow through the central windows 2000 server and use circular logging. No clustering or MQclients are involved at this stage. On the hub we have WMQI flows for message transformation and distribution purposes. I would like to find out what the most optimal way would be to gather statistics on message volumes passing through our central HUB server. The 2 options I am considering at the moment is to either use channel exits or to actually modify the message flows to add another destination for each message flow. This additional queue will trigger a program which will collect stats for monthly reporting. Any advice will be much appreciated! (WMQI version 2.1 and WMQ version 5.3) Andre van Zyl = Disclaimer This message may contain information which is private, privileged or confidential and is intended solely for the use of the individual or entity named in the message. If you are not the intended recipient of this message, please notify the sender thereof and destroy / delete the message. Neither the sender nor Sappi Limited (including its subsidiaries and associated companies) shall incur any liability resulting directly or indirectly from accessing any of the attached files which may contain a virus or the like. Director Names A list of Sappi companies and the names of their directors can be retrieved from http://www.sappi.com/home.asp?pid=644 = This communication is confidential and may contain privileged material. If you are not the intended recipient you must not use, disclose, copy or retain it. If you have received it in error please immediately notify me by return email and delete the emails.Thank you. = Disclaimer This message may contain information which is private, privileged or confidential and is intended solely for the use of the individual or entity named in the message. If you are not the intended recipient of this message, please notify the sender thereof and destroy / delete the message. Neither the sender nor Sappi Limited (including its subsidiaries and associated companies) shall incur any liability resulting directly or indirectly from accessing any of the attached files which may contain a virus or the like. Director Names A list of Sappi companies and the names of their directors can be retrieved from http://www.sappi.com/home.asp?pid=644 =
MQ Message statistics
Title: MQ Message statistics My client has requested that I give them statistics on MQSeries messages ( volumes etc) on a monthly basis. There is no MQ monitoring / admin software installed other than the standard MQ. We have a hub and spoke architecture, and all mq messages currently flow through the central windows 2000 server and use circular logging. No clustering or MQclients are involved at this stage. On the hub we have WMQI flows for message transformation and distribution purposes. I would like to find out what the most optimal way would be to gather statistics on message volumes passing through our central HUB server. The 2 options I am considering at the moment is to either use channel exits or to actually modify the message flows to add another destination for each message flow. This additional queue will trigger a program which will collect stats for monthly reporting. Any advice will be much appreciated! (WMQI version 2.1 and WMQ version 5.3) Andre van Zyl = Disclaimer This message may contain information which is private, privileged or confidential and is intended solely for the use of the individual or entity named in the message. If you are not the intended recipient of this message, please notify the sender thereof and destroy / delete the message. Neither the sender nor Sappi Limited (including its subsidiaries and associated companies) shall incur any liability resulting directly or indirectly from accessing any of the attached files which may contain a virus or the like. Director Names A list of Sappi companies and the names of their directors can be retrieved from http://www.sappi.com/home.asp?pid=644 =
Re: MQSeries 5.3 on XP
Title: RE: MQSeries 5.3 on XP Hi, I recently also tried this. According to the CSD you should run the command "x:\setup.exe AMQ_XP_INSTALL_PENDING_CSD=1" from DOS-ptompt to install, but this still did not work. I found a note in the archives which solved the problem - you should run the command "mqparms.exe AMQ_XP_INSTALL_PENDING_CSD=1" - I tried it and it worked. Andre -Original Message- From: "Rodríguez Alvarez-Querol, Manuel Carlos" [mailto:[EMAIL PROTECTED]] Sent: 05 February 2004 03:58 To: [EMAIL PROTECTED] Subject: Re: MQSeries 5.3 on XP Hi, WebSphere MQ 5.3 GA does not support XP. Then, to install it, just install mq with the following command line and install the latest csd. x:\setup.exe AMQ_XP_INSTALL_PENDING_CSD=1 You could also take a look to http://www-1.ibm.com/support/docview.wss?uid=swg27004410&aid=1 which is the latest CSD readme file. > -Mensaje original- > De: Kerry Swemmer [SMTP:[EMAIL PROTECTED] > Enviado el: Thursday, 05 February, 2004 2:45 PM > Para: [EMAIL PROTECTED] > Asunto: MQSeries 5.3 on XP > > Hi All, > > I am trying to install 5.3 on Windows XP and am getting the following > > AMQ4755 This version of IBM WebSphere MQ > does not yet support Windows XP. A > CSD will provide this support. > > Any ideas? I cannot find any related CSD. > > Thanx, > Kerry. > > -Original Message- > From: MQSeries List [mailto:[EMAIL PROTECTED]]On Behalf Of John > Scott > Sent: 18 November 2003 10:49 > To: [EMAIL PROTECTED] > Subject: Re: Impact of Syncpoint? > > > You still get an improvement by using syncpoint after every message. The > test I did reduced the time for 1000 persistent messages from 25 to 15 > seconds... > > Regards > John Scott > IBM Certified Specialist - MQSeries > Argos Ltd > > > -Original Message- > From: Ruzi R [mailto:[EMAIL PROTECTED]] > Sent: 17 November 2003 19:03 > To: [EMAIL PROTECTED] > Subject: Re: Impact of Syncpoint? > > > Paul, > > Thanks for the response. But the requirement is that > we have to do a commit after every persistent message > read off the queue (as opposed to after a batch of > messages read). > > Thanks, > > Ruzi > > --- Paul Clarke <[EMAIL PROTECTED]> wrote: > > Depends what you mean by 'impact'. I assume you're > > talking about persistent > > messages here. Generally speaking the addition of > > syncpoint to persistent > > message operations will increase the performance > > since we only need to > > force the log at commit time rather than for every > > message. > > > > Download my MA01 support pac if you want to have a > > play. > > Choose a local queue, say Q1 > > Load the queue with messages :- > > > > q -oQ1 -ap > > > > at the prompt type > > #1000 > > > > you now have 1000 persistent messages on your queue. > > > > Get them off by specifying :- > > > > q -IQ1 -t -q > > > > this will printout something like > > > > 1000 Interations in 441.00 ms, Average = 0.44ms or > > 2267.6 per second > > > > This is doing your gets outside of syncpoint. > > To do it inside of syncpoint you can tell queue how > > often to commit, let's > > say every 100 messages > > > > Load up your queue again and then type > > > > q -IQ1 -t -q -p100 > > > > The line now reads > > 1000 Interations in 90.00 ms, Average = 0.09ms or > > 1.1 per second > > > > By doing the gets under syncpoint (and quite a lot > > of them) we're now about > > 5 times faster. > > > > These were the numbers produced on my ThinkPad and > > will depend greatly on > > the speed of your disks, the type of disks, your CPU > > speed etc etc. > > > > There are also, I believe, a number of support pacs > > which detail the speed > > of MQ operations on the support pac website. > > > > Hope this helps, > > P. > > > > Paul G Clarke > > WebSphere MQ Development > > IBM Hursley > > > > > > > > |-+> > > | | Ruzi R | > > | | <[EMAIL PROTECTED]| > > | | M> | > > | | Sent by: MQSeries| > > | | List | > > | | <[EMAIL PROTECTED]| > > | | N.AC.AT> | > > | | | > > | | | > > | | 17/11/2003 16:59 | > > | | Please respond to| > > | | MQSeries List | > > |-+> > > > > > >- > -- > | > > | > > > > | > > | To: [EMAIL PROTECTED] > > > > | > > | cc: > > > > | > > | Subject: Impact of Syncpoint? > > > > | > > | > > > > | > > | > > > > | > > > > > >- > -- > --
Re: WMQI Versions
Title: RE: WMQI Versions Hi Robert, Basically it has to do with our local IBM support that did not really know WBI 5.0 and could not tell us if we are able to migrate from MQSI 2.0.1 to WBI 5.0. They suggested we first upgrade to 2.1. I did however speak to someone else at IBM earlier this afternoon, and we are now going to investigate the possibility of upgrading directly to 5.0. Andre Sappi Integration Team Tel. Direct: +27 (0)11 407 4088 Tel. Mobile: +27 (0)82 880 6860 Fax: +27 (0)11 403 8105 eMail (Sappi): [EMAIL PROTECTED] -Original Message- From: Robert Broderick [mailto:[EMAIL PROTECTED]] Sent: 09 December 2003 02:46 To: [EMAIL PROTECTED] Subject: Re: WMQI Versions Surprised nobody said this. The current version of WBI is 5.0. Is there a reason you are not moving to that?? Except for the slight learning curve for the Eclipse interface!! bobbee >From: "van Zyl, Andre" <[EMAIL PROTECTED]> >Reply-To: MQSeries List <[EMAIL PROTECTED]> >To: [EMAIL PROTECTED] >Subject: WMQI Versions >Date: Tue, 9 Dec 2003 08:42:57 +0200 > > > > We are in the process of upgrading from MQSI 2.0.1 to WMQI 2.1. > > > > I would just like to clarify something regarding the WMQI versions. > > On the support summary page of IBM website I see that there is a >Websphere > > MQ Integrator for Windows NT 2.1 (latest CSD level 5) and also a >Websphere > > MQ Integrator Broker for Windows NT and Windows 2000 2.1 (latest CSD >level > > 6). > > What is the difference - the local IBM represenative here has told me >that > > there is no difference, but why are they at different CSD levels? - why > > are there seperate CSD's if these products are the same? > > I would really appreciate it if someone could assist. > > Thanks > > Andre > > > > > > > > > > >= > >Disclaimer > >This message may contain information which is private, privileged or >confidential and is intended solely for the use of the individual or entity >named in the message. If you are not the intended recipient of this >message, >please notify the sender thereof and destroy / delete the message. Neither >the sender nor Sappi Limited (including its subsidiaries and associated >companies) shall incur any liability resulting directly or indirectly from >accessing any of the attached files which may contain a virus or the like. > >Director Names > > A list of Sappi companies and the names of their directors can be >retrieved >from http://www.sappi.com/home.asp?pid=644 >= > > _ Our best dial-up offer is back. Get MSN Dial-up Internet Service for 6 months @ $9.95/month now! http://join.msn.com/?page=dept/dialup Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive = Disclaimer This message may contain information which is private, privileged or confidential and is intended solely for the use of the individual or entity named in the message. If you are not the intended recipient of this message, please notify the sender thereof and destroy / delete the message. Neither the sender nor Sappi Limited (including its subsidiaries and associated companies) shall incur any liability resulting directly or indirectly from accessing any of the attached files which may contain a virus or the like. Director Names A list of Sappi companies and the names of their directors can be retrieved from http://www.sappi.com/home.asp?pid=644 =
WMQI Versions
Title: WMQI Versions We are in the process of upgrading from MQSI 2.0.1 to WMQI 2.1. I would just like to clarify something regarding the WMQI versions. On the support summary page of IBM website I see that there is a Websphere MQ Integrator for Windows NT 2.1 (latest CSD level 5) and also a Websphere MQ Integrator Broker for Windows NT and Windows 2000 2.1 (latest CSD level 6). What is the difference - the local IBM represenative here has told me that there is no difference, but why are they at different CSD levels? - why are there seperate CSD's if these products are the same? I would really appreciate it if someone could assist. Thanks Andre = Disclaimer This message may contain information which is private, privileged or confidential and is intended solely for the use of the individual or entity named in the message. If you are not the intended recipient of this message, please notify the sender thereof and destroy / delete the message. Neither the sender nor Sappi Limited (including its subsidiaries and associated companies) shall incur any liability resulting directly or indirectly from accessing any of the attached files which may contain a virus or the like. Director Names A list of Sappi companies and the names of their directors can be retrieved from http://www.sappi.com/home.asp?pid=644 =
[no subject]
signoff MQSERIES = Disclaimer This message may contain information which is private, privileged or confidential and is intended solely for the use of the individual or entity named in the message. If you are not the intended recipient of this message, please notify the sender thereof and destroy / delete the message. Neither the sender nor Sappi Limited (including its subsidiaries and associated companies) shall incur any liability resulting directly or indirectly from accessing any of the attached files which may contain a virus or the like. Director Names A list of Sappi companies and the names of their directors can be retrieved from http://www.sappi.com/home.asp?pid=644 =
Execition Group Problem
Hi, Yesterday I encountered a strange problem which I hope soemone out there might be able to help me with. I am running MQSI v2.0.1 CSD 6. I had 3 execution groups - we decided to remove the flows from 1 execution group and add them to another which worked fine. Before deleting the redundant execution group I first deployed to ensure that the message flows were active in the new execution group. I then checked out the broker and deleted the now redundant execution group, checked in the broker and deployed (delta). The deploy seemed to work, but the execution group still appeared in the Operations Tab and the log indicated an error concerning the fact that the the configuration manager is unable to determine the status of the deleted execution group. Subsequently I deployed again. The configuration of the remaining 2 execution groups and the broker deploys OK but for some reason it still searches for the deleted execution group and returns the following in the log: *** This message is generated at 2003-08-07 14:16:56 BIP4040I: The Execution Group 'MES' has processed a configuration message successfully. A configuration message has been processed successfully. Any configuration changes have been made and stored persistently. No user action required. *** This message is generated at 2003-08-07 14:16:56 BIP2066E: Broker MQ_CENTRAL_BK (UUID 63a9290f-e600--0080-8f8d393d2d9a) was unable to retrieve an internal configuration response message for execution group 'MES' within the 300 second Configuration Timeout. The execution group did not respond within the Configuration Timeout period. A negative response is returned to the Configuration Manager for this execution group. The Configuration Timeout is the maximum length of time that an execution group is allowed to apply a deployed configuration change. By default the Configuration Timeout period is 300 seconds. This value can be altered by setting environment variable MQSI_TIMEOUT to the number of seconds required. You should not use a value less than 300. Investigate why the execution group was unable to respond before being timed out. Use the system log messages to determine if there is a problem with the execution group. You should check that your system is not running short of resources, for example, you may need to increase the MQSeries log size. Reducing the complexity of the deploy by reducing the number of execution groups may also help to alleviate this problem. Correct the problem and redeploy the broker's configuration from the Control Center. If there are no other failure diagnostics then you should consider increasing the Configuration Timeout, increase this value in units of 300 until this message no longer occurs. For example export MQSI_TIMEOUT=600. Contact your IBM support center if you are unable to resolve the problem. *** This message is generated at 2003-08-07 14:16:57 BIP4040I: The Execution Group 'default' has processed a configuration message successfully. A configuration message has been processed successfully. Any configuration changes have been made and stored persistently. No user action required. *** This message is generated at 2003-08-07 14:16:57 BIP4040I: The Execution Group 'proteus' has processed a configuration message successfully. A configuration message has been processed successfully. Any configuration changes have been made and stored persistently. No user action required. *** This message is generated at 2003-08-07 14:22:36 BIP1536S: Configuration Manager unable to register for internal subscriptions with broker MQ_CENTRAL_BK. Although the preceding deploy operation was successful, a subsequent attempt by the Configuration Manager to register for internal subscriptions with broker MQ_CENTRAL_BK was not successful. This means that the Control Center Operations view may not reliably show the correct status of the resources assigned to broker MQ_CENTRAL_BK. The Configuration Manager also writes this message to the system event log, accompanied by other messages giving details of the problem. Look at the messages for this problem in the system event log. Determine and correct the cause of the problem before attempting to deploy to this broker again. If this problem persists, contact your IBM support center. *** This message is generated at 2003-08-07 15:26:23 BIP2086I: Broker MQ_CENTRAL_BK could only process parts of the internal configuration message. Parts of the internal configuration message were not processed successfully. This response indicates that one or more Execution Groups could not process the
XML to MRM
Hi, MQSI v2.0.1 - CSD6: I have an XML message which I need to convert to MRM (in SAP IDOC format). We have been working with SAP IDOCs in MRM format for quite a while, but the inbound data we have received up to now has always been in fixed length string format which makes it easy to convert it to IDOC (MRM) format. The problem I am having now is that the inbound messages are in XML format (not fixed length). One solution I tried was to first create an MRM message which resembles the XML structure (The reason for this was so I could add all the necessary padding character details by using this "interim" MRM message). I then map the XML tagged fields to each respective MRM element in this interim MRM message and in another Compute I concatenate these elements as required to create the required SAP IDOC format. Unfortunately what now happens is that the elements seem to be "trimmed" before concatenation but in SAP the IDOC data is expected to be in a pre-determined fixed length format (including all the padding characters specified in the "interim" MRM message). I have set the custom wire format of the "interim" MRM message to fixed length and specified a padding character of "space" - however the element padding doesn't seem to be holding during concatenation. Then I tried something else - in a compute node (same compute as where I do the concatenation) I declare a temporary field for each of the elements before concatenation and use PAD to obtain the required padding (spaces or zero's). Concatenating these temporary padded fields worked 100% with no leading or trailing spaces being trimmed. I would like to know if there is a simpler way to ensure that when an element of a message is used in concatenation, the entire element length (including padding characters) is used and not only the "trimmed" actual data. Thanks Andre Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: "Export Queue Manager Definitions"
Hi, We use support pac ms03 (saveqmgr) - tried and tested on AIX and Windows operating systems. It is a very simple pplication to save all your queue manager objects to a text file with a simple import utility on another server (same or different OS) As I said, we only use AIX and Window - don't know anything about OS/390 but assume IBM will probably have the same functionality on OS/390. Andre -Original Message- From: Fleck, Michael [mailto:[EMAIL PROTECTED] Sent: 12 June 2003 08:43 To: [EMAIL PROTECTED] Subject: "Export Queue Manager Definitions" Hi list members, I'm not very experienced dealing with MQSeries. We are running MQ-Series Server on OS/390. We want to migrate our server to Windows 2000. Is there a possibility to extract the MQ-Definitions (Queues, Channels etc.) from one server to import them on another server. Thanks in advance. Best regards, Michael Fleck Landschaftsverband Rheinland InfoKom Datenbanken, Ressourcen, OS/390 Tel: 0221/809/2826 email: [EMAIL PROTECTED] Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive == Disclaimer === "This message may contain information which is private, privileged or confidential and is intended solely for the use of the individual or entity named in the message. If you are not the intended recipient of this message, please notify the sender thereof and destroy / delete the message. Neither the sender nor Sappi Limited (including its subsidiaries and associated companies) shall incur any liability resulting directly or indirectly from accessing any of the attached files which may contain a virus or the like". = Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
XML Schema Import
Could anyone please tell me where I might be able to get documentation on the use of WMQI 2.1 XML schema import utility (MqsiImpXMLSchema). I was told by IBM that the WMQI 2.1 documentation is updated from CSD 3, but I have already installed CSD 4 and cannot find any info in the documentation on this subject. Thanks Andre == Disclaimer === "This message may contain information which is private, privileged or confidential and is intended solely for the use of the individual or entity named in the message. If you are not the intended recipient of this message, please notify the sender thereof and destroy / delete the message. Neither the sender nor Sappi Limited (including its subsidiaries and associated companies) shall incur any liability resulting directly or indirectly from accessing any of the attached files which may contain a virus or the like". = Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
ID04 - import xml schema
Hi, I am trying to import an xml schema (supplied by papiNet) into MQSI v2.0.1 using the support pack ID04. I had to modify the schema slightly since some tag names were not acceptable according to MQSI naming standards, but I now seem to have overcome that problem. The error I am now getting is as follows: "Instruction at 0x0040971c referenced memory at 0x00b9a10c - memory could not be read." It is definately not a memory hardware problem since I tested it on 3 different machines with exactly the same result. Also when I look at the log file it stops at exactly the same position each time. Therefore I am assuming that there is a size limitation since the schema I am trying to inport is quite big. I there anyone that can confirm this limitation or is there any other problem that I am overlooking. Thanks Andre == Disclaimer === "This message may contain information which is private, privileged or confidential and is intended solely for the use of the individual or entity named in the message. If you are not the intended recipient of this message, please notify the sender thereof and destroy / delete the message. Neither the sender nor Sappi Limited (including its subsidiaries and associated companies) shall incur any liability resulting directly or indirectly from accessing any of the attached files which may contain a virus or the like". = Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: MQ Client
Dankie Francois. The ideal solution for my client would be to have MQServers at all the remote locations, but unfortunately the client is VERY price sensitive and will not be able to afford it. He does however still want assured one time message delivery and that is where the concern about assured message delivery using clients came from. Thanks for everyone's comments. Regards Andre van Zyl -Original Message- From: Francois Van der Merwe1 [mailto:[EMAIL PROTECTED] Sent: 27 May 2003 12:53 To: [EMAIL PROTECTED] Subject: Re: MQ Client Andre, I think one of the concerns in the "server concentrator" setup is that the "window of opportunity for something to go wrong" is bigger when the clients connect to a server that is a long way from it or when the client connections are slow. Yes, you must use syncpoint, and yes, you must use COA or COD or both, but you need to think about what must you do when something goes wrong. For instance, say you receive a COA but no COD and then the connection brake? Is that good enough reason to resend the message or not? Maybe it will be best if the "server" side application know how to handle duplicates, so that if the client does not know what to do, then it can just resend. Also, if the volume is high, then server to server connections is usually faster. Some pros for client connection: Client can connect to more than one QM at a time. Client can automatically use alternate channels when primary is down Client is really cheap Simpler admin Cons Performance suffers No DB XA stuff No local Q's Expose to network outages memory overhead on server for every client connection no clustering no UOW coordination Client is synchronous less control over channels, no keepalive, No batching of high volume messages Francois van der Merwe Senior IT Specialist: IBM MQSeries Certified Specialist, Solutions Expert & Developer IBM, Cape Town, South Africa +27 (0)82 556 9467 / +27 (0)21 402 5597 [EMAIL PROTECTED] "van Zyl, Andre" <[EMAIL PROTECTED]To: [EMAIL PROTECTED] .SAPPI.COM> cc: Sent by: MQSeriesSubject: Re: MQ Client List <[EMAIL PROTECTED] N.AC.AT> 05/27/2003 03:46 PM Please respond to MQSeries List Thanks -Original Message- From: Paul Clarke [mailto:[EMAIL PROTECTED] Sent: 27 May 2003 02:30 To: [EMAIL PROTECTED] Subject: Re: MQ Client >The question / concern I have has to do with assured message delivery when >using MQClients. >We are starting a new project which involves one central MQServer with >several distributed MQClients (all connected via a secure WAN). >We know that with MQServer, message delivery is assured. It is however >expensive to have many queue managers all over the show if the same >objective can be obtained by means of MQClients. >The only issue which now arises is how do I ensure assured message delivery? Andre, The semantics of messaging is exactly the same for a client as for a locally connected application. In other words, in order to do reliable messaging in a local application you must follow a certain set of rules like issuing MQPUTs and MQGETs under transactions etc. These rules are exactly the same for a client. One area which often concerns programmers is the MQCMIT call. What happens if you lose your network half way through an MQCMIT verb and get a MQRC_CONNECTION_BROKEN reason code. Did the transaction commit or didn't it ? Well, this is the same for a local application, you are not guaranteed to get a definitive answer on your transaction commit even for the local application. If you really care, you must do some 'known' action (like put a message to a queue) that you can subsequently check the next time you connect. The principle difference between a client and a local application is that clients (at least the free ones) can not have other resource managers involved in the transaction. So if you want a client application to update a database in the same transaction as an MQPUT call then you should either have a real Queue Manager or use the new Transactional Client product (which costs money). So, on the face of it, you can now do pretty much everything as a client that you can do locally. This does not mean however that regardless of the size of your organisation or the location of your applications that you should just have one server in the middle and everyone else connect as clients. There are many reasons why you might want queues more localised to your applications quite apart from the limiting factor of how many applications is it reasonable to have a single server serve. Hope this helps, P. Paul G Clarke WebSphere MQ Devel
Re: MQSI 2.1 WIN2K
I have WMQI 2.1 (CSD02) on my Laptop with Windows 2000 Professional(IBM Thinkpad P3 512Mb memory) and MQ 5.2 . I recently imported about 100 message flows and also 6 message sets and deployed without any problems. For what it's worth, I do not think its an OS problem. Andre -Original Message- From: Robert Broderick [mailto:[EMAIL PROTECTED] Sent: 18 March 2003 09:55 To: [EMAIL PROTECTED] Subject: MQSI 2.1 WIN2K Can WMQI 2.1 run on WIN2K Professional. We have two laptops one VAIO, one Thinkpad. Both 512RAM, one WIN2K Server one WIN2K Professional. Both at SP3 and WMQI CSD03 and MQ 5.3. VAIO works great. WMQI on the Professional (Thinkpad) WMQI works and comes up by when doing 2 of 4 mqsiimpexpmsgset importing MRM's an error message generates indicating not enough memory and not enough virtual memory. The VAIO was orig running 256RAM and worked ok. Checked the system settings and all the memory settings are up to snuff. Also, The filesize of the MRM we are importing is 170K one of the ones that worked is 2Meg? Is it the Professional / Server difference? Wierd! bobbee _ Add photos to your e-mail with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive = Disclaimer = "This message may contain information which is private, privileged or confidential and is intended solely for the use of the individual or entity named in the message. If you are not the intended recipient of this message, please notify the sender thereof and destroy / delete the message. Neither the sender nor Sappi Limited (including its subsidiaries and associated companies) shall incur any liability resulting directly or indirectly from accessing any of the attached files which may contain a virus or the like." Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
WMQ5.3 with MQSI 2.0.1
Hi, Is it possible to use MQSI 2.0.1 together with MQ5.3? When MQ5.3 is installed, MA88 is automatically deleted. After installation I tried starting the MQSI control center but it complained about Java classes not being found. I re-installed MA88 and set the Classpath, but still get the same error. It seems as though MQ5.3 and MQSI 2.0.1 do not work together. Thanks Andre = Disclaimer = "This message may contain information which is private, privileged or confidential and is intended solely for the use of the individual or entity named in the message. If you are not the intended recipient of this message, please notify the sender thereof and destroy / delete the message. Neither the sender nor Sappi Limited (including its subsidiaries and associated companies) shall incur any liability resulting directly or indirectly from accessing any of the attached files which may contain a virus or the like." Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
R/3 Link And XML IDOC's
Hi, Is there anyone out there using the SAP R/3 Link (V1.2) for sending IDOC's in XML format into and from SAP via MQSeries? ( Specifically SAP version 3.1). I basically would like to know if this is possible. Thanks Andre = Disclaimer = "This message may contain information which is private, privileged or confidential and is intended solely for the use of the individual or entity named in the message. If you are not the intended recipient of this message, please notify the sender thereof and destroy / delete the message. Neither the sender nor Sappi Limited (including its subsidiaries and associated companies) shall incur any liability resulting directly or indirectly from accessing any of the attached files which may contain a virus or the like." Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Cannot clear a queue
Why is it that even though a queue's "open input" and "open output" counts are 0, I cannot clear the messages from a queue? I get an AMQ4070 error - Object is Open. MQ 5.2 CSD3. This has been working for the last year, but now I get this error. All the messages on the queue were put there by MQSI (V2.0.1) due to data errors. I stopped and restarted the broker execution group but still have the same problem. Thanks Andre = Disclaimer = "This message may contain information which is private, privileged or confidential and is intended solely for the use of the individual or entity named in the message. If you are not the intended recipient of this message, please notify the sender thereof and destroy / delete the message. Neither the sender nor Sappi Limited (including its subsidiaries and associated companies) shall incur any liability resulting directly or indirectly from accessing any of the attached files which may contain a virus or the like." Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
