ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » Workflow Engines - IBM MQ Workflow & Business Process Choreographer » Do I need JNDI?

Post new topic  Reply to topic
 Do I need JNDI? « View previous topic :: View next topic » 
Author Message
technok
PostPosted: Fri Nov 14, 2003 6:47 pm    Post subject: Do I need JNDI? Reply with quote

Novice

Joined: 14 Oct 2001
Posts: 17
Location: Hong Kong

Why RMI-IIOP?
Why use WMQ Workflow JAVA agent?

Performance? Scalability? JAVA-hungry?

Please advise!
_________________
Techno K
IBM Certified MQ/WMQI Specialist
Back to top
View user's profile Send private message
dsim
PostPosted: Sat Nov 15, 2003 7:41 am    Post subject: Reply with quote

Acolyte

Joined: 11 Aug 2003
Posts: 67
Location: Toronto

Quote:
Why use WMQ Workflow JAVA agent?

... to integrate with application servers
Back to top
View user's profile Send private message
technok
PostPosted: Sat Nov 15, 2003 5:16 pm    Post subject: Reply with quote

Novice

Joined: 14 Oct 2001
Posts: 17
Location: Hong Kong

haha, well , I should re-define my question.

Why not LOCAL_LOCATOR?
Why don't let MQ as a middleman in between App Server and MQWF?

Any good reason to use JNDI_LOCATOR?
_________________
Techno K
IBM Certified MQ/WMQI Specialist
Back to top
View user's profile Send private message
dsim
PostPosted: Sat Nov 15, 2003 7:13 pm    Post subject: Reply with quote

Acolyte

Joined: 11 Aug 2003
Posts: 67
Location: Toronto

Quote:
Why not LOCAL_LOCATOR?
Why don't let MQ as a middleman in between App Server and MQWF?

For sure LOC locator policy can be used when the application server runs on a machine that has MQSeries installed.
This is the recommended locator policy - it uses MQSeries between the Application Server (acting as MQWF Client) and MQWF Server.
In this case the agent is local, embedded in the JNI layer (MQWF code is C/C++ based)

Quote:
Any good reason to use JNDI_LOCATOR?

Only in cases when MQSeries is not available on the machine where the application server is running.
In this case the application server (acting as MQWF client) uses RMI over IIOP to communicate with a remote agent.
The Java agent can run either a different machine that has MQWF Client with Queue Manager or on the server machine.
Not recommended because the performance and scalability are not as good as the configuration using LOC locator policy.
Back to top
View user's profile Send private message
technok
PostPosted: Sun Nov 16, 2003 5:42 am    Post subject: Reply with quote

Novice

Joined: 14 Oct 2001
Posts: 17
Location: Hong Kong

Thanks dsim, got it!

It means except money for MQ license and JAVA-hunger, no really good reason to use JNDI_LOCATOR. Right!
_________________
Techno K
IBM Certified MQ/WMQI Specialist
Back to top
View user's profile Send private message
dsim
PostPosted: Sun Nov 16, 2003 6:28 am    Post subject: Reply with quote

Acolyte

Joined: 11 Aug 2003
Posts: 67
Location: Toronto

MQ license shouldn't be an issue: as i know MQWF comes with MQSeries licenses included for each 'Client with Queue Manager'.

Dan
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » Workflow Engines - IBM MQ Workflow & Business Process Choreographer » Do I need JNDI?
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.