| Author |
Message
|
| ivanachukapawn |
 Posted: Mon Nov 27, 2006 10:14 am Post subject: WPS default messaging vs full MQSeries |
 |
|
Knight
Joined: 27 Oct 2003
Posts: 561
|
| I currently have a WPS installation and configuration which uses 'default messaging' as a JMS Provider. Can I reconfigure WPS to use MQSeries as the JMS provider? I mean, is WPS constricted in any way to use default messaging? |
|
| Back to top |
|
 |
| vennela |
| Posted: Mon Nov 27, 2006 10:56 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| Quote: |
| Can I reconfigure WPS to use MQSeries as the JMS provider? |
Sure
It is also well documented, so you shouldn't have a lot of trouble doing that. |
|
| Back to top |
|
|
| ivanachukapawn |
| Posted: Mon Nov 27, 2006 11:36 am Post subject: |
|
|
Knight
Joined: 27 Oct 2003
Posts: 561
|
I thought that I should be able to do this OK, but got worried when I saw some paragraphs in the WPS installation manual that recommended that Websphere MQ should not be selected if the Websphere MQ Queue Managers were clustered, and also, a paragraph that indicates that 'default messaging' would still need to be configured to support the SCA stuff.
We are thinking about having MQSeries Queue Managers clustered (for easy of administration, not for load balancing) and controlled by HACMP for availability - these queue managers being connected to by WPS instances via Websphere MQ JMS client mode. |
|
| Back to top |
|
|
| vennela |
| Posted: Mon Nov 27, 2006 11:51 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
I am trying to understand your infrastructure architecture, but are you saying that you will have a QMGR on a box that is different from the box where you install WPS?
If yes, then why?
| Quote: |
| but got worried when I saw some paragraphs in the WPS installation manual that recommended that Websphere MQ should not be selected if the Websphere MQ Queue Managers were clustered |
Can you point me to some of those?
I know the doc says a lot about MQ clustering, but the doc is referring to 5.3 and v6 clustering has different characteristics that can be exploited by WPS.
It would be easier if you tell us what you are planning and we can definitely come up with suggestions.
Are you planning to use WPS in a stand alone mode?
Are you planning to use WPS' process choreography piece in an ND cluster?
Are you planning for a WPS-PC HACMP or just the DB HACMP or MQ HACMP or as much HA as permitted by the configuration
| Quote: |
| a paragraph that indicates that 'default messaging' would still need to be configured to support the SCA stuff. |
AFAIK, this is automatically done when you create the profile (I mean even if you don't use any PC or Human Task or anything like that). This is how WPS is designed I guess. Infact, there are four BUSes that are created by default. You don't have to do anything to configure this, it is automatically done for you when you create the profile. I am not very good in this area, so if you have asked a different question then my apologies here. |
|
| Back to top |
|
|
| ivanachukapawn |
| Posted: Mon Nov 27, 2006 12:44 pm Post subject: |
|
|
Knight
Joined: 27 Oct 2003
Posts: 561
|
We want to use HACMP for MQ only and have dedicated server nodes which handle Enterprise App MQ traffic for many apps as well as WPS. That is why we want to have the 'WPS' process choreography piece in an ND cluster' client connect (via Websphere MQ MQConnectionFactory as JMS Provider) to the HACMP controlled Websphere MQ Queue Manager.
The WPS installation manual section which has me worried is:
| Quote: |
Business Process Choreographer can use WebSphere MQ queues for receiving requests and sending replies. WebSphere MQ is not recommended as the JMS provider if a clustered scenario is used. If you use WebSphere MQ, you must still configure the default messaging for the Service Component Architecture (SCA), which Business Process Choreographer uses for inbound and outbound service invocation. Each application server that hosts Business Process Choreographer requires one of the following options: v Access to a central queue manager that hosts all queues v A local queue manager that is not a member of a WebSphere MQ cluster v Two local queue managers that are members of a WebSphere MQ cluster |
|
|
| Back to top |
|
|
| vennela |
| Posted: Mon Nov 27, 2006 1:02 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
Your scenario probably requires the client mode (the first option in the above quote)
Now, don't worry about the next two cluster options described there if you are using MQ6.
| Quote: |
| (via Websphere MQ MQConnectionFactory as JMS Provider) |
That is the way to go. Just remember to set the MQ_INSTALL_ROOT WebSphere variable (install needed MQ Java/JMS component ) |
|
| Back to top |
|
|
|
|
