| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Lotus Script and message/queue handling |
« View previous topic :: View next topic » |
| Author |
Message
|
| becosgrove |
 Posted: Mon Mar 17, 2003 7:04 am Post subject: Lotus Script and message/queue handling |
 |
|
Newbie
Joined: 12 Mar 2003
Posts: 2
Location: Buffalo, NY, USA
|
Calling all gurus.... Or anyone with more experience in this than I.....
I'm currently managing a development team that is building a Lotus Notes workflow that uses MQ Series from the NT Server to the mainframe (OS/390) to gather customer information. We then go back to the NT Server via MQ and proceed through the workflow. Finally, we send approved finalized "transactions" back to the mainframe via MQ. I call them "transactions" because it's really just data that is used to formulate transactions on the mainframe side, and we don't have huge volumes like you'd normally see in a true transaction system.
We're having difficulting in a number of fronts. It seems we have most of our trouble in the MQ scripts - processing all messages in the queue going back to the NT and getting agents to run in a timely manner.
We also have trouble with the amount of time it takes queues to become active again after periods of inactivity. It seems our Lotus script can either wait long enough for the queue to become active again every time (long delay for the users) or satisfy our users requests for response, and not become active fast enough for the first transaction.
We don't have any NT MQ expertise in our organization, and I'm currently waiting for my account on IBM's InfoLink to become active, so I thought I'd try this.
I have the details of our queue setups and I have copies of our Lotus script, but I didn't want to bog down this posting with unnecessary detail.
Any suggestions would be appreciated. I'll be monitoring closely for any requests for additional information.
Thanks in advance! |
|
| Back to top |
|
 |
| mqonnet |
| Posted: Mon Mar 17, 2003 7:17 am Post subject: |
|
|
Grand Master
Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.
|
There are few things that need more info.
1) What is the actual problem that you are facing. From your description, i undestand it is response time. And if so, what do you think is causing it to be slow(i know we are trying to probably figure this out here, but was wondering if you guess something around, because you are physically with the systems).
2) What you mean when you say "trouble witgh amount of time it takes queues to become active". Does that mean, your scripts take longer to retrive messages off the queue. Because "queue" in its own is never inactive. It is an object that is there for you to access, put/get messages to/from.
3) Good idea not to post all the details in your first post, as that would have confused the scenario than solving it. What i think is needed here is, the description of what your lotus scripts do as far as mq processing is concerned.
4) Lastly. Is this a new program that you are running and getting problems. Or was it running for a while and noticed this issue just recently. Any errors/FD files on your QM.
I have not played myself a lot with Lotus scripts(only a little). Just trying to help you as much as i can.
Cheers
Kumar
_________________
IBM Certified WebSphere MQ V5.3 Developer
IBM Certified WebSphere MQ V5.3 Solution Designer
IBM Certified WebSphere MQ V5.3 System Administrator |
|
| Back to top |
|
|
| zpat |
| Posted: Mon Mar 17, 2003 8:26 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
I have used Lotuscript on NT with MQSeries on OS/390 extensively.
How are the agents executed?
1 - As workstation agents?
2 - As scheduled server agents?
3 - Triggered agents?
Does the MQLSX use MQ client or MQ server?
Does the LS agent have any interaction with the Notes user in real-time or is it a background agent?
Do you want to wait for a response in the LS code, or invoke an agent when a message arrives? What is the message model here (datagram, request/reply etc)?
We use both scheduled execution of agents and triggering from OS/390 queues. Using support pac MA7K for the NT trigger monitor.
Works perfectly for us. |
|
| Back to top |
|
|
| becosgrove |
| Posted: Mon Mar 17, 2003 9:17 am Post subject: |
|
|
Newbie
Joined: 12 Mar 2003
Posts: 2
Location: Buffalo, NY, USA
|
Our two basic problems are response time and stability. This is a new system we are testing - due to go live in about 2 weeks.
We originally set our channel to go inactive after 1 hour of non-use. The first transaction in the morning going from Notes to the mainframe would "wake" the channel up, but the Lotus script waiting for a reply from the mainframe would send back a time out message. We could see the message in the queue going back to Notes on the mainframe side.
On the outbound side (sending out the "transactions") - at the end of last week, we were seeing one go out per hour. My understanding is that there's a setting for how often the agent runs, but there's a coordinating setting in the channel. Possibly we don't have them in synch. But I also think there's evidence that our Lotus Script is not processing all database entries that are waiting to be processed and sent out every time the agent runs.
The agent for sending the initial message to the mainframe is triggered, and it waits for a reply (message model: request/reply). The agent that sends the final transactions back to the mainframe is a scheduled server agent (message model: datagram).
The MQLSX uses MQ Server.
Hopefully this helps! THANKS! |
|
| Back to top |
|
|
| zpat |
| Posted: Tue Mar 18, 2003 4:46 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
You might consider using MQ client (and the OS/390 queue manager as the server). This means that you won't have these channel problems.
I don't recommend LS agents waiting a long time for messages, you can use a mainframe queue to trigger a MQ client NT based Notes agent (with MA7K). That's what we do.
It sounds like you have some basic MQ server channel set up issues - which to be honest I am not the best person to answer MQ server configuration questions.
You can invoke LS agents in several ways.
Triggering (probably the best way for immediate reaction to events).
Scheduled (by Notes) - this works well as a "sweep up" in case triggering did not work for some reason.
Workstation - part of a Notes action or button code. Useful for testing.
I can't answer the server channel configuration question - but if you have something specific to MQ and Notes then I will able be to help.
I recommend using SYNCPOINTs in the LS code, so that (as far as possible) the Notes database operations and the MQ operations are linked together so that (for example) the GETs from the queue are only committed when the database updates have been successful.
You can't use a single UoW for MQ and Notes, but you can reduce the chance of losing data by careful use of SYNCPOINT and COMMIT.
Always code MQGET with CONVERT so that applications can operate directly from OS/390 queues as well as from NT queues. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
